Re: Queue ID availability for milters on multi-message connections/sessions?

Wietse Venema wrote: Below are the SMTP commands/responses, and the test-milter output showing that the second "DATA" event is reported with the correct queue ID. OK, thanks! I'll take it up further with the milter authors. -kgd

Re: Queue ID availability for milters on multi-message connections/sessions?

Below are the SMTP commands/responses, and the test-milter output showing that the second "DATA" event is reported with the correct queue ID. Wietse $ telnet 127.0.0.1 smtp Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 220-wzv.porcupine.org ESMTP Postfix 220

Re: Queue ID availability for milters on multi-message connections/sessions?

Kris Deugau: > Mar 29 16:35:14 jessie64 postfix/smtpd[17537]: connect from > localhost[127.0.0.1] > Mar 29 16:35:27 jessie64 postfix/smtpd[17537]: 26F5E428A4: > client=localhost[127.0.0.1] > Mar 29 16:36:02 jessie64 postfix/cleanup[17556]: 26F5E428A4: > message-id= > Mar 29

Re: Queue ID availability for milters on multi-message connections/sessions?

Wietse Venema wrote: Kris Deugau: I came across a bit of an information-passing glitch on a system that uses a milter (MIMEDefang) to glue together complex filter policies. MIMEDefang is configured to log sender, first recipient, Message-ID (if any), and the queue ID, along with some filter

Re: Queue ID availability for milters on multi-message connections/sessions?

Kris Deugau: > I came across a bit of an information-passing glitch on a system that > uses a milter (MIMEDefang) to glue together complex filter policies. > > MIMEDefang is configured to log sender, first recipient, Message-ID (if > any), and the queue ID, along with some filter result data,

Queue ID availability for milters on multi-message connections/sessions?

I came across a bit of an information-passing glitch on a system that uses a milter (MIMEDefang) to glue together complex filter policies. MIMEDefang is configured to log sender, first recipient, Message-ID (if any), and the queue ID, along with some filter result data, for each message.