ACL/Exim Retry rule for 550 error

[Hemant Jain]

Hi,

Can someone help me with a ACL/Exim retry rule which would defer an email and retry after X hours in case we receive a 550, "5.7.1", blocked error from gmail.

Currently on receiving this error from gmail the email is bounced back to the original sender.

Using CentOS and Exim.

Regards

 

[cPanelMichael]

Hello,

Email messages that are bounced by the receiver are considered complete since the message was already delivered. The better approach would be to address whatever issue is leading to the delivery failure. Could you let us know the specific error message included with the bounced message?

Thank you.

 

[Hemant Jain]

This is not about an email bounced by the receiver.

May be the error message would clarify the issue:

  [email protected]

    host gmail-smtp-in.l.google.com [74.125.22.27]

    SMTP error from remote mail server after end of data:

    550-5.7.1 [192.64.82.XX      12] Our system has detected that this message is

    550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail,

    550-5.7.1 this message has been blocked. Please visit

    550-5.7.1  Why has Gmail blocked my messages? - Gmail Help

    550 5.7.1  for more information. y78si611055qka.94 - gsmtp

This message comes primarily due to gmail rate limiting. What I am looking for is rather than the original email being bounced to the sender with an error, if gmail blocks or rejects the email and sends out a 550-5.7.1 after SMTP DATA this message should remain in the queue and retried after XX hours.

Hope this clarifies.

 

[cPanelMichael]

This message comes primarily due to gmail rate limiting. What I am looking for is rather than the original email being bounced to the sender with an error, if gmail blocks or rejects the email and sends out a 550-5.7.1 after SMTP DATA this message should remain in the queue and retried after XX hours.

Hello,

Google is rejecting the email message and thus it won't remain in the mail queue. In these cases, the sender must attempt to send the message again after fixing whichever issue resulted in Google rejecting the message.

Thank you.