Alun,
Thanks for the validation. I've overcome the hurdle that initiated this
thread. The issue was my script breaking over DBM calls, which work
perfectly when running the script interactively. Like a dog with a bone, I
wanted this to work!!! I even tried all the different DBM managers, with no
success. Late yesterday, I gave up.
I've re-tooled my script to use text files instead. It's less efficient and
less elegant, but darned if it doesn't all work!! Now, I can start eating
and sleeping again <grin>.
I never did hear back from Malcolm Beattie, the engineer of the embedded
Perl thing. Perhaps he hasn't seen my message yet. I will post again if I
get a reply.
Thanks to all for their feedback on this topic!!
Mike
-----Original Message-----
From: exim-users-admin@??? [
mailto:exim-users-admin@exim.org]On
Behalf Of Alun
Sent: Thursday, June 26, 2003 8:53 AM
To: exim-users@???
Subject: Re: [Exim] limitations with embedded Perl
We use it hugely on the central mail service for Aber. This is partly, I
admit, because we've not yet been able to find the time to install Exim 4 -
quite a lot of the stuff we do would work better from ACLs. Spam scanning
was, until recently, done completely using the perl interface. We've got a
teergrube setup done inside a perl function and all sorts of other stuff.
Personally, I'd be very sorry to see embedded perl go away. It may impose
some small penalty on speed (though I've not noticed it) but it sure is
useful!
Cheers,
Alun.
