Why is 554 error not bounced and stays deferred?

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
Ace Suares
Advanced member
Advanced member
Posts: 63
Joined: Thu Aug 07, 2014 7:26 pm

Why is 554 error not bounced and stays deferred?

Post by Ace Suares »

I get a lot of these:

(host mx1.dhl.iphmx.com[68.232.135.103] refused to talk to me: 554-esa2.dhl.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)

Personally I think this specific spam filter is brain dead. It works with 'reputation' and if you had a breach in user passwords and sent out 10.000 spams, it takes days or more then a week to restore the reputation. (Thalos, Senderbase, Cisco)

But my problem is that these are not bounced to the sender, but stay in the deferred queueue and are retried a couple of days. But is a 5xx error, shouldn't that bounce right away?

Ace
User avatar
DualBoot
Elite member
Elite member
Posts: 1326
Joined: Mon Apr 18, 2016 8:18 pm
Location: France - Earth
ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
Contact:

Re: Why is 554 error not bounced and stays deferred?

Post by DualBoot »

maybe the server response is not formatted like it should be. So the Postfix can not understand the server response as a permanent error.
Post Reply