>>>>> "Malcolm" == Malcolm Beattie <mbeattie@???> writes:
<perl/exim proof-of-concept snipped>
This is truly amazing.
Malcolm> If anyone can think of any real applications, I'd be
Malcolm> interested (and only slightly surprised). I'd imagine a
Malcolm> perl transport (which let you do fancy things and
Malcolm> "deliver" a message in the context of exim itself) may be
Malcolm> the most likely perl driver to be of use. Or maybe a
Malcolm> generic Perl code "lookup" thing (${lookup {key} perl
Malcolm> {some_perl_sub} {arg}}).
Something that springs to mind is using DBI for user/host lookups. At
work were starting a project next year to replace our X400/SMTP mixed
email setup with (presumably) full SMTP, and seeing as am half way
through a perl/DBI/Tk based message switch system had begun to wonder
about our email users being stored in a database (ie. all new
employees would be registered into our Oracle personel system and have
a "computer system user" automtically generated and stored in another
DB which the email system could use for lookups).
Perhaps there are ways to do this in exim already ? Of course, doing
it in perl would certainly add extra flexibility for doing "fancier"
things whatever they maybe.
<patch snipped>
This may not be a totally viable concept though due to the increase in
footprint size of the combined perl/exim - do others think this may be
a problem ?
Sincerely,
Adrian Phillips
--
*** Exim information can be found at
http://www.exim.org/ ***
