I can’t speak for Google, but a few accounts I have with them were getting hit pretty hard with DKIM replay attacks recently. Not sure how isolated these were, but if they were widespread I wouldn’t be surprised if this is the result of a reaction to those attacks.
Regards, Brian On Aug 2, 2016, at 3:30 PM, Sridhar Kakkillaya <[email protected]<mailto:[email protected]>> wrote: I just sent a separate email outlining the exact same issue. Google seems to be have changed some policy this weekend. -- Sridhar Kakkillaya Director of Operations & Partnerships, MailChannels Tel: +1 604 685 7488 x 509 www.mailchannels.com<http://www.mailchannels.com/> Twitter<https://twitter.com/mailchannels> | LinkedIn<http://www.linkedin.com/company/mailchannels> On Tue, Aug 2, 2016 at 12:23 PM, Ryan Harris via mailop <[email protected]<mailto:[email protected]>> wrote: Hi Zube, I've also noticed an issue similar to this. Some abuse reports we get go through a Google Apps domain. I've noticed receiving an initial abuse@ sample through google apps works just fine and the message is delivered. However, if I reply to that email, or if I forward it along, Google gives me a bounce back message stating they can't send the message b/c it's spam. Only if I remove the previous content entirely can I reply to these emails. This does not seem to effect the initial messages delivery, only when I reply/forward the email will Google Apps let me know the message cannot be delivered. Unsure if this is exactly related to what you are bringing up, though it sounds similar and it's a change I've noticed in the last 2-3 weeks. Ryan On Tue, Aug 2, 2016 at 1:11 PM, Zube <[email protected]<mailto:[email protected]>> wrote: Starting this weekend, mail sent from a google apps domain to a user on my server who has her email forwarded to a google.com<http://google.com/> address has the email deferred forever with a possibly spurious message: ** relay=alt4.gmail-smtp-in.l.google.com<http://alt4.gmail-smtp-in.l.google.com/>. [64.233.186.27], dsn=4.0.0, stat=Deferred: 421-4.7.0 [129.82.129.115 15] Our system has detected an unusual rate of ** I've seen the rate-limiting message before when spam has gotten through, but it was always temporary and in this case, it is almost certainly not related to spam. Consider an unused account on the google apps domain (blah) and a newly created alias on my server (pm) that forwards to a testing account at google that receives essentially no mail. blah mails to pm, my server accepts it and tries to send it along to the testing account, but google instantly gives the above rate-limiting message and the mail stays in the queue forever. This problem is almost certainly not a problem with blah since it's never used. It can't be with the pm alias because it hadn't existed before. It can't be with my mail server in general because gmail is still accepting mail from it; from a local account, I can send without issue. The cruncher is that if I send to pm from a @gmail.com<http://gmail.com/> account rather than a google apps domain account, everything gets forwarded just fine. I've come to understand that email forwarding is going away and I should start preparing people for it. But the odd error message and that fact that it still works from gmail.com<http://gmail.com/> addresses has me more than a little perplexed. Did something recently change with google and accepting mail from their apps domains? Any clues greatly appreciated. Cheers, Zube _______________________________________________ mailop mailing list [email protected]<mailto:[email protected]> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list [email protected]<mailto:[email protected]> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list [email protected]<mailto:[email protected]> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
