On 16.01.25 04:32, Scott Q. via mailop wrote:
Thanks, so despite the bounce saying it's a problem with the
recipient, it may very well be a problem with our sending IP ?
the "Recipient address rejected" usually means that your mail was rejected
at the RCPT stage of SMTP transaction.
MTAs do that to get addresses of recipient, not just the sender.
Recipient needs not to be the reason for rejection.
So most likely your address is the problem, even in case of badly designed
MTA
Another issue is that the MTA provides permanent error (550) but claims mail
is only temporarily blocked.
On Thu, Jan 16, 2025 at 03:46:12AM -0500, Scott Q. via mailop wrote:
A user is trying to e-mail someone at setunari.com but we get
this weird bounce:
85.13.157.168 does not like recipient.
Remote host said: 550 5.7.1 : Recipient address rejected: temporarily
blocked because of previous errors - retrying too fast. penalty: 30
seconds x 0 retries.
Giving up on 85.13.157.168.
I was thinking it's a problem with the recipient but it appears to
work from other locations (?).
On Thursday, 16/01/2025 at 04:27 Peter N. M. Hansteen wrote:
is NAT involved at all?
If the same client manages to send from a different location, I would
assume that their source IP address changed.
One likely or at least possible reason for the message is that in the
original location, they were sharing the routable address with something
noisy enough that the rate limiting was triggered.
Then again it could be that they were themselves the noisy one but their
activity at the alternative location had not yet the "classified as too
much" level.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
2B|!2B, that's a question!
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
