<div dir="auto"><div>That message means the mail was queued to mailscanner. Were both recepients in the same email? Were both recipients in the same domain?<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 11, 2018, 5:43 AM Nerijus Baliunas <<a href="mailto:nerijus@users.sourceforge.net">nerijus@users.sourceforge.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I had a few such messages in maillog:<br>
<br>
Oct 10 11:06:20 bluegene postfix/cleanup[2519]: 8AED1181849997: milter-discard: END-OF-MESSAGE from ip3 [192.168.0.3]: milter triggers DISCARD action; from=<<a href="mailto:g@example.com" target="_blank" rel="noreferrer">g@example.com</a>> to=<<a href="mailto:other@example.com" target="_blank" rel="noreferrer">other@example.com</a>> proto=ESMTP helo=<<a href="http://g.example.com" rel="noreferrer noreferrer" target="_blank">g.example.com</a>><br>
<br>
The message was sent to me and one other email address. I got it, but other didn't,<br>
and I don't see anything more in logs, so it seems the message was lost.<br>
Is is related to this issue?<br>
<br>
Regards,<br>
Nerijus<br>
<br>
On Sun, 7 Oct 2018 15:36:02 -0400 Shawn Iverson via MailScanner <<a href="mailto:mailscanner@lists.mailscanner.info" target="_blank" rel="noreferrer">mailscanner@lists.mailscanner.info</a>> wrote:<br>
<br>
> Mark,<br>
> <br>
> There's a performance fix in this commit that should help with most of<br>
> this. The crashing is likely from partially written messages in the<br>
> milterin queue as a result of not writing the file in a single pass. I<br>
> hope to get a few more issues resolved before doing another release.<br>
> <br>
> <a href="https://github.com/MailScanner/v5/commit/5083b4e0f0eecbec84a5ab94538b0ffbe35f90f1" rel="noreferrer noreferrer" target="_blank">https://github.com/MailScanner/v5/commit/5083b4e0f0eecbec84a5ab94538b0ffbe35f90f1</a><br>
> <br>
> <br>
> <br>
> On Sun, Oct 7, 2018 at 2:17 PM Mark Sapiro <<a href="mailto:mark@msapiro.net" target="_blank" rel="noreferrer">mark@msapiro.net</a>> wrote:<br>
> <br>
> > This is basically just a report of things I encountered with the milter<br>
> > option in MailScanner 5.1.1. I don't think I have enough information to<br>
> > actually debug these issues, and for now at least, I have reverted to<br>
> > the Postfix hold queue option.<br>
> ><br>
> > I first set up the milter option on a local test server. Mail wasn't<br>
> > being scanned, but this was because I was submitting the test mail from<br>
> > localhost. When I submitted mail remotely, all seemed to work well, so I<br>
> > then set up the milter option on my not too busy production server. I<br>
> > set it up at about 9:30 p.m. on Friday. It seemed to be working well.<br>
> ><br>
> > At some point Saturday, I noticed some delays so I began to investigate.<br>
> ><br>
> > I saw this in mail.log<br>
> ><br>
> > Oct 6 08:35:50 sbh16 MailScanner[3301]: Requeue: 2BA30E13AF.AAFEC to<br>
> > DB2E81180AC8<br>
> > Oct 6 08:35:50 sbh16 postfix/smtpd[6686]: connect from<br>
> > localhost.localdomain[127.0.0.1]<br>
> > Oct 6 08:36:20 sbh16 postfix/smtpd[6686]: warning: milter<br>
> > inet:<a href="http://127.0.0.1:33333" rel="noreferrer noreferrer" target="_blank">127.0.0.1:33333</a>: can't read SMFIC_OPTNEG reply packet header:<br>
> > Connection timed out<br>
> > Oct 6 08:36:20 sbh16 postfix/smtpd[6686]: warning: milter<br>
> > inet:<a href="http://127.0.0.1:33333" rel="noreferrer noreferrer" target="_blank">127.0.0.1:33333</a>: read error in initial handshake<br>
> ><br>
> > This seemed to be a one time occurrence. Mail was processed normally until<br>
> ><br>
> > Oct 6 11:16:39 sbh16 MailScanner[7312]: Requeue: B679E47A37.A9D7F to<br>
> > A7D441181110<br>
> > Oct 6 11:16:39 sbh16 postfix/smtpd[27861]: connect from<br>
> > localhost.localdomain[127.0.0.1]<br>
> > ...<br>
> > Oct 6 11:17:09 sbh16 postfix/smtpd[27861]: warning: milter<br>
> > inet:<a href="http://127.0.0.1:33333" rel="noreferrer noreferrer" target="_blank">127.0.0.1:33333</a>: can't read SMFIC_OPTNEG reply packet header:<br>
> > Connection timed out<br>
> > Oct 6 11:17:09 sbh16 postfix/smtpd[27861]: warning: milter<br>
> > inet:<a href="http://127.0.0.1:33333" rel="noreferrer noreferrer" target="_blank">127.0.0.1:33333</a>: read error in initial handshake<br>
> > ...<br>
> > Oct 6 11:17:10 sbh16 postfix/smtpd[27861]: connect from<br>
> > unknown[185.36.81.145]<br>
> > Oct 6 11:17:40 sbh16 postfix/smtpd[27861]: warning: milter<br>
> > inet:<a href="http://127.0.0.1:33333" rel="noreferrer noreferrer" target="_blank">127.0.0.1:33333</a>: can't read SMFIC_OPTNEG reply packet header:<br>
> > Connection timed out<br>
> > Oct 6 11:17:40 sbh16 postfix/smtpd[27861]: warning: milter<br>
> > inet:<a href="http://127.0.0.1:33333" rel="noreferrer noreferrer" target="_blank">127.0.0.1:33333</a>: read error in initial handshake<br>
> ><br>
> > at which point these seemed to occur with every connect even though<br>
> > 'netstat -lntp' showed the milter listening on port<br>
> ><br>
> > About an hour later, I reverted to the non-milter configuration and<br>
> > things became normal again.<br>
> ><br>
> > Also during the 14 hours that the milter was configured, I saw 4 of these<br>
> ><br>
> > Oct 5 22:58:44 sbh16 MailScanner[7746]: Quarantined message ... as it<br>
> > caused MailScanner to crash several times<br>
> ><br>
> > I have those 4 messages and have reprocessed them following reversion to<br>
> > the hold queue method with no problem. I also processed them through my<br>
> > test server running the milter without crashing MailScanner. On the test<br>
> > server, I did see<br>
> ><br>
> > Oct 6 15:21:39 msapiro MailScanner[13351]: Unable to kick message<br>
> > /var/spool/MailScanner/milterout/5ECA5340128, will retry soon...<br>
> ><br>
> > on 3 of the four messages which remained in milterout, but this may have<br>
> > been related to the fact that I submitted all 4 in one manual smtp<br>
> > session and then never submitted any more messages before reverting that<br>
> > to the hold queue method.<br>
> ><br>
> > So, I don't think that the "caused MailScanner to crash" issue was<br>
> > related to the actual message content.<br>
> ><br>
> > My milter config overrides defaults with<br>
> ><br>
> > ---------------------------------<br>
> > Incoming Queue Dir = /var/spool/MailScanner/milterin<br>
> > Outgoing Queue Dir = /var/spool/MailScanner/milterout<br>
> > MTA = msmail<br>
> > MSMail Queue Type = short<br>
> > Milter Scanner = yes<br>
> > Milter Max Children = 1<br>
> > ---------------------------------<br>
> ><br>
> > I wonder if people are successfully using this in production or if<br>
> > people have seen issues such as this?<br>
> ><br>
> > --<br>
> > Mark Sapiro <<a href="mailto:mark@msapiro.net" target="_blank" rel="noreferrer">mark@msapiro.net</a>> The highway is for gamblers,<br>
> > San Francisco Bay Area, California better use your sense - B. Dylan<br>
> ><br>
> ><br>
> > --<br>
> > MailScanner mailing list<br>
> > <a href="mailto:mailscanner@lists.mailscanner.info" target="_blank" rel="noreferrer">mailscanner@lists.mailscanner.info</a><br>
> > <a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" rel="noreferrer noreferrer" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
<br>
<br>
-- <br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info" target="_blank" rel="noreferrer">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" rel="noreferrer noreferrer" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
</blockquote></div></div></div>