I have a persistent problem for some of my customers who are using Gmail to collect and send email from their hosted sites. When their customers try to send them email to their domain, some ISPs refuse the email address as "forged" and bounce the message back to the sender. I have tried enabling domain keys and playing around with the settings in Cpanel, but haven't been able to get the right combination of things for them. And yet, I do the very same thing with my emails, and never get blocked.
Now they are also getting the same issue when people send email to their ISP address.
Here is an example of the bounce notice sent back to the sender:
In this case, the email was sent to their ISP email address, "emailaddr@roadrunner.com". The "Original-Recipient" is their ISP email address. The route should have been from that email address, to Gmail, to them.
I suspect it might be something in their Gmail configuration. Has anyone else run into this?
Now they are also getting the same issue when people send email to their ISP address.
Here is an example of the bounce notice sent back to the sender:
Recipient: <kathleen@customerdomain.com>
Reason: Blocked by ACL. Forged gmail.com email, connection denied!
Original-Recipient: RFC822;<emailaddr@roadrunner.com>
Final-Recipient: RFC822; <emailaddr@roadrunner.com>
Action: failed
Status: 5.1.1
Remote-MTA: dns; customerdomain.com (74.86.90.185)
Diagnostic-Code: smtp; 550 Blocked by ACL. Forged gmail.com email, connection denied!
X-Actual-Recipient: RFC822; <kathleen@customerdomain.com>
Reason: Blocked by ACL. Forged gmail.com email, connection denied!
Original-Recipient: RFC822;<emailaddr@roadrunner.com>
Final-Recipient: RFC822; <emailaddr@roadrunner.com>
Action: failed
Status: 5.1.1
Remote-MTA: dns; customerdomain.com (74.86.90.185)
Diagnostic-Code: smtp; 550 Blocked by ACL. Forged gmail.com email, connection denied!
X-Actual-Recipient: RFC822; <kathleen@customerdomain.com>
I suspect it might be something in their Gmail configuration. Has anyone else run into this?
Comment