<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I may have found something regarding this.</p>
<p>With debug enabled, I can see in the journalctl logs the
following error every time the server should send me an
autoresponse :</p>
<p>SMFIC_MAIL: bad packet</p>
<p>The message then repeat itself every minute or so until I
manually discard messages in the queue, then it doesn't reappear.
A google search for that error message leads me there: <br>
</p>
<p><a class="moz-txt-link-freetext" href="https://github.com/avar/sendmail-pmilter/issues/5">https://github.com/avar/sendmail-pmilter/issues/5</a></p>
<p>We are indeed working with non-smtp mail in this case, so could
it be hitting a similar bug? What I think could be happening is
that postfix tries to flush its queue every minute or so but can't
as it hits this bug, thus generating a recurring bad packet error
in MSmilter.<br>
</p>
<div class="moz-cite-prefix">On 5/4/23 18:16, Shawn Iverson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACg3fsaA72cJNE5hw1nC=8Ja_LtcfHVHCGPBvhgJ5W=1bQgGdw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">I'm not sure why that is happening and may require
setting Debug in MailScanner and restarting msmilter to see what
is happening via mail log or journalctl.
<div dir="auto"><br>
</div>
<div dir="auto">Another option since that is 127.0.0.1 is to set
Milter Ignore Loopback = true but I'm not sure you want that
behavior since emails will bypass MailScanner coming from the
localhost.<br>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, May 4, 2023, 6:05 PM
J-P Methot via MailScanner <<a
href="mailto:mailscanner@lists.mailscanner.info"
moz-do-not-send="true" class="moz-txt-link-freetext">mailscanner@lists.mailscanner.info</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm testing Mailscanner 5.3.3 and Postfix 3.6.2. Postfix and
Mailscanner <br>
are on two different servers. Everything works properly,
except if I set <br>
an autoresponse in roundcube, the email gets stuck in the
postfix queue <br>
with a temporary failure message :<br>
<br>
milter-reject: MAIL from localhost[127.0.0.1]: 4.7.1 Service
unavailable <br>
- try again later; from=<><br>
<br>
Postfix has three milter setup : opendkim, opendmarc and
MSMilter, <br>
though that last one is written as an IP + port. If I remove
MSMilter <br>
from the list, the email go through without issue. So what I
understand <br>
is that the Mailscanner milter is not even accepting my email
to scan <br>
it, but instead rejecting it with a temporary failure message,
as if the <br>
server was greylisted. Yet, nothing inside Mailscanner
indicates that, <br>
as the email just sits in queue inside postfix on the origin
server.<br>
<br>
<br>
What could explain this behavior? I've tried setting Treat
Invalid <br>
Watermarks With No Sender as Spam = nothing, but that didn't
change <br>
anything and as far as I'm aware, the email isn't even given a
score.<br>
<br>
<br>
-- <br>
Jean-Philippe Méthot<br>
Senior Openstack system administrator<br>
Administrateur système Openstack sénior<br>
PlanetHoster inc.<br>
<br>
<br>
<br>
-- <br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">mailscanner@lists.mailscanner.info</a><br>
<a
href="http://lists.mailscanner.info/mailman/listinfo/mailscanner"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
</blockquote>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Jean-Philippe Méthot
Senior Openstack system administrator
Administrateur système Openstack sénior
PlanetHoster inc.</pre>
</body>
</html>