Hi! We use last mimedefang-2.79 and postfix-3.1.4 and have problem with definition of $QueueID vars in filter_begin.
For example case 1, when we have more than one rcpt to in SMTP session: May 24 12:20:29 mailsrv1 postfix/cleanup[89515]: 3B8F0286AE8: message-id=<df2a0a267c834f168cd822df171641cd@XXXXXXXXXXXXXXXX> May 24 12:20:29 mailsrv1 mimedefang-multiplexor[84421]: 3B8F0286AE8: copymail: connect=inbound message-id=<df2a0a267c834f168cd822df171641cd@XXXXXXXXXXXXXXXX> queue_id=3B8F0286AE8 May 24 12:20:30 mailsrv1 postfix/cleanup[89515]: 282FD2869A1: message-id=<df2a0a267c834f168cd822df171641cd@XXXXXXXXXXXXXXXX> May 24 12:20:30 mailsrv1 mimedefang-multiplexor[84421]: copymail: connect=inbound message-id=<df2a0a267c834f168cd822df171641cd@XXXXXXXXXXXXXXXX> queue_id=NOQUEUE Sometimes mimedefang can't define $QueueID for one recipient: May 25 10:25:29 mailsrv1 postfix/cleanup[72878]: 748F1177F89B: message-id=<c9fb40cb9746328ec2a30728a.698f77fc2c.20170525072031.e8d687df58.cb460...@mail28.atl71.mcdlv.net> May 25 10:25:29 mailsrv1 mimedefang-multiplexor[51288]: copymail: connect=inbound message-id=<c9fb40cb9746328ec2a30728a.698f77fc2c.20170525072031.e8d687df58.cb460...@mail28.atl71.mcdlv.net> queue_id=NOQUEUE Usually all work fine. It is the known problem or we not correctly use mimedefang? If it is required, I'm ready to get and provide detailed log data. We found similar discussion about this problem in postfix maillist: http://postfix.1071664.n5.nabble.com/Queue-ID-availability-for-milters-on-multi-message-connections-sessions-td89741.html Thanks! _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
