Hi, Benoit,
On 09-06-17 09:30, Benoit Panizzon wrote:
Hello
We have a 'challenging' problem between two companies sending each other
emails.
The sender keeps getting notifications, that his emails to the
recipient are delayed. But this is not true. Analyzing the email
headers the recipient sent me I can confirm, the emails take about two
seconds! from sender to the recipient.
The sender, if I got that right from the headers, uses Lotus Notes and
is relaying messages via the SMTP server of his ISP, which relays it to
our postfix server.
I suspect the message "250 2.6.0 Bad message, but will be delivered
anyway" is somehow generated by lotus notes or an intermediary email
scanner and lotus notes translates this to 'your message could not be
delivered and is being delayed, the server will continue to try to
deliver the email'
The recipient uses an exchange server behind a postfix based email
scanner service. After sniffing the connections and looking at the logs,
I am pretty sure, the "250 2.6.0 Bad message, but will be delivered
anyway" is not generated from our postfix server, or from our
customer's exchange server.
But the sender tells me, that this message only shows, when he is
sending an email to our customer.
Has anyone seen such a message and has any clue what causes it, and
also what causes lotus notes to send an DSN telling the sender the
message could not be delivered, despite the message being delivered
perfectly in time?
Google tells me that "250 2.6.0 Bad message, but will be delivered
anyway" is an error message generated by ISPConfig. But as far as I
found out, no server relaying the email uses this mailer.
any firewall performing 'smtp content inspection' between sender and
recipient? Firewalls performing smtp content inspection are pretty nasty
and usually cause all sorts of problems...
/rolf
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
