Evgeniy Berdnikov <bd4@???> (Mo 06 Mai 2013 21:48:19 CEST):
> On Mon, May 06, 2013 at 07:04:36PM +0100, Klaus Ethgen wrote:
> > I need to write special logs to a database when the mail is received and
> > after it has been (successful or not) delivered as well as when it
> > bounces.
> >
> > For the first I can use a condition in acl to call a own embedded perl
> > script that is doing the stuff. But for the other two logging issues I
> > did not found any way to call a perl subroutine. The best I can archive
> > is to have a condition in the router. But this gives me no way to see
> > the status of the delivered mail.
> >
> > Do you see any way to do it?
>
> It seems me you have no chances to catch ALL the bounce cases in routers
> and transports: there may be situations such as insufficient memory for
> Exim, disk overflow and others... I belive the only reliable solution is
> to parse logs and extract relevant entries.
A bounce will go through a transport, otherwise the bounce isn't a
bounce, is it?
> Parsing may be done on the fly, via exim -> syslog -> program(pipe),
> of logging to program via named pipe (man fifo), or some other way.
If you're interested in reliable logging, you should not use logging to
syslog. Exim has no feedback, if the log entry is really written.
I'd say, the built-in logging facility of Exim is much more mature,
since it stops message reception in face of logging problems. IMHO a
very crucial element of a safe and secure mail service.
Parsing the logs with some kind of daemon or cronjob is probably the most
simplistic approach.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: 7CBF764A -
gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
