Op donderdag 5 juni 2014 14:36:26 schreef Viktor Dukhovni:
> On Thu, Jun 05, 2014 at 04:04:43PM +0200, Maarten Vanraes wrote:
> > Op woensdag 4 juni 2014 12:49:29 schreef Wietse Venema:
> > [...]
> >
> > > The pipe daemon expects a specific reponse format, and that
> > > format does not include SMTP reply codes. See pipe(8) manpage.
> > >
> > > I can see benefit in logging downstream status information, but it
> > > will necessarily have to be limited.
> >
> > It would be helpful, because if you're using pipe, to do anything with
> > email, it would help to have in that delivered logline a small piece of
> > text which then could be used to identify the mail in the downstream...
> >
> > eg: my script outputs as a first line to stdout:
> >
> > stored as 363752 and sent to 10.0.0.14 (250 2.0.0 queued as E0B375CA)
>
> Just pipe this line to "postlog", and include the queue-id of the input
> message (${queue_id} pipe(8) argument used *before* ${recipient} or
> similar which expands to multiple arguments and must be last unless
> the transport recipient limit is set to 1).
that is a possibility, but i don't have 2.11 yet.
but, iinm some other transports (not pipe) do have downstream information, so
wouldn't it be better to have a similar output?
Regards,
Maarten
--
BA NV
IT & Security
