> Any 5xx code is supposed to say that
That's clear now that's how it's supposed to work.
> Whether the recipient of the remote site's resulting bounce message is paying
> attention is another
matter.
That's the actual problem here I think.
> You're now down to something like Kevin McGrail's
robg...@nospammail.net wrote:
I have a milter set up to REJECT on some body content.
It works like it should and REJECTS with the message
Jul 25 14:41:13 mariner postfix/handoff/smtpd[56542]: proxy-reject: END-OF-MESSAGE: 554
5.7.1 id=12969-07 - Rejected by next-hop MTA on relaying, fr
On 7/25/2017 7:42 PM, /dev/rob0 wrote:
Oh, I disagree. The best thing to do is to reject anything you're
unwilling/unable to deliver. You're not causing any bounces; if a
connecting client does generate a bounce for your rejection that is
THEIR problem; or in the case of a human sender, that is
> On 7/25/2017 5:51 PM, robg...@nospammail.net wrote:
> >Depending on where I read about it that "554 5.7.1" error code
> >means "failed transaction".
554 is described in RFC 5321, yes, as "failed transaction".
5.7.1 is an Extended Mail System Status Code, described in RFC 3463:
https://tools.i
On 7/25/2017 5:51 PM, robg...@nospammail.net wrote:
Depending on where I read about it that "554 5.7.1" error code means "failed
transaction".
Unfortunately, you might need logic to accept and silently discard. We
do this, for example, with viruses to avoid blowback.
Regards,
KAM
robg...@nospammail.net:
> But they keep retrying to resend the email that's getting REJECTed.
> Every 15mins for the past 9+ hours since the 1st message was sent
> and got rejected.
RFC 5321, the definition of SMTP says:
4.2.1. Reply Code Severities and Theory
...
5yz Permanent Negative Comp
I have a milter set up to REJECT on some body content.
It works like it should and REJECTS with the message
Jul 25 14:41:13 mariner postfix/handoff/smtpd[56542]: proxy-reject:
END-OF-MESSAGE: 554 5.7.1 id=12969-07 - Rejected by next-hop MTA on relaying,
from MTA(smtp:[127.0.0.1]:16002):
