On 2022-08-05 20:13, J David wrote:
I noticed something in our mail logs that I thought was unusual.

What does it mean when smtpd reports a NOQUEUE without any kind of
reject: reason?  All that's there is the client.

Aug  5 17:42:58 b1 postfix/smtpd[18503]: NOQUEUE:
client=a26-70.smtp-out.us-west-2.amazonses.com[54.240.26.70]
Aug  5 17:43:34 b1 postfix/smtpd[18632]: NOQUEUE:
client=mail-mw2nam12on2054.outbound.protection.outlook.com[40.107.244.54]
Aug  5 17:44:59 b1 postfix/smtpd[18653]: NOQUEUE:
client=mail-io1-f54.google.com[209.85.166.54]

I don't see any rhyme or reason to the affected clients.  There are
plenty of big email providers, small ones, etc.  I even found an
internal connection from another server, which helped me see that the
same connection *does* go on to send a message successfully after the
NOQUEUE.  Here's an example from outlook.com:

Aug  5 18:06:59 b1 postfix/smtpd[20637]: connect from
mail-mw2nam12olkn2071.outbound.protection.outlook.com[40.92.23.71]
Aug  5 18:07:00 b1 postfix/smtpd[20637]: Trusted TLS connection
established from
mail-mw2nam12olkn2071.outbound.protection.outlook.com[40.92.23.71]:
TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)
Aug  5 18:07:00 b1 postfix/smtpd[20637]: NOQUEUE:
client=mail-mw2nam12olkn2071.outbound.protection.outlook.com[40.92.23.71]
Aug  5 18:07:04 b1 postfix/smtpd[20637]: proxy-accept: END-OF-MESSAGE:
250 2.6.0 from MTA(smtp:[127.0.0.1]:10027): 250 Queued on server;
from=<redacted> to=<redacted> proto=ESMTP
helo=<NAM12-MW2-obe.outbound.protection.outlook.com>

What is listening on 127.0.0.1:10027?

Aug  5 18:07:04 b1 postfix/smtpd[20637]: disconnect from
mail-mw2nam12olkn2071.outbound.protection.outlook.com[40.92.23.71]
ehlo=2 starttls=1 mail=1 rcpt=1 bdat=1 quit=1 commands=7

There's only one mail, one rcpt, etc shown in the disconnect summary,
and one actual message with one recipient did go through, so I just
don't understand where the NOQUEUE came from.

This appears to happen ~25,000 times a day, so I'd like to better
understand what's causing it and if it represents a problem.  Or if
I've just left a debug setting enabled somewhere. :-)

If it matters, this is on Postfix 3.7.2.

Thanks for any advice!

--
 Christian Kivalo

Reply via email to