The way this was implemented is very frustrating. I assisted a few orgs that, I had done consultancy for prior. But many out there are only just now, going to notice and go WTF?
And these are not black and white, meaning that is you move into a "compliant" state with regards to SPF, DKIM and blah signed TXT records. The "reputation" of the now tainted domain will take some time to correct itself. Google will not resolve this. The reputation will need to build back up, you can email my address direct. As I have Google Workspaces Enterprise with all the verbose logging for mail. Validating the delivery to gmail workspaces vs vanilla freemium gmail accounts would be interesting. You could also build a sub domain, marketing email comms often use this method of sending via [email protected] .. default policy allows then penalises if you do not tick the boxes (there are many others beyond just TXT signing .. reverse-dns etc. Could this all be a ploy to nudge small to medium biz to sign up for Google Workspaces as their business fails without email ? hmm Regards, Brad On Mon, 5 Feb 2024 at 19:35, DaZZa <[email protected]> wrote: > Google and Yahoo have implemented changes recently. > > AWS's summary is here > > > https://aws.amazon.com/blogs/messaging-and-targeting/an-overview-of-bulk-sender-changes-at-yahoo-gmail/ > > You're likely getting caught up in that. > > D > > On Mon, 5 Feb 2024, 5:52 pm Tim McCullagh, <[email protected]> > wrote: > >> Sorry for the noise, but is there anyone on the list from gmail? >> >> Is anyone else having trouble with delivery to gmail. My customers are >> getting the following messages >> >> <[email protected]>: host gmail-smtp-in.l.google.com[172.217.194.26] >> said: 550-5.7.1 [203.17.235.145 12] Gmail 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. For more >> information, go to 550 5.7.1 >> https://support.google.com/mail/?p=UnsolicitedMessageError >> bz9-20020a056a02060900b005cdffc2828esi7631435pgb.182 - gsmtp (in reply >> to >> end of DATA command) >> >> and >> >> >> <[email protected]>: host aspmx.l.google.com[172.253.118.26] said: >> 550-5.7.1 [203.17.235.145 19] Gmail has detected that this >> message >> is >> 550-5.7.1 likely suspicious due to the very low reputation of the >> sending >> 550-5.7.1 domain. To best protect our users from spam, the message >> has >> been >> 550-5.7.1 blocked. For more information, go to 550 5.7.1 >> https://support.google.com/mail/answer/188131 >> e13-20020a63f54d000000b005ce025116bbsi12152612pgk.858 - gsmtp (in >> reply >> to >> end of DATA command) >> >> >> Ive been through my mail logs and cant find any reason why email is being >> blocked from the mail server. There has been no misuse of late. There >> was on another hosting server which is in my spf record. The hosting >> server had a customer account misused via sasl auth. That >> was fixed 8 days ago. Are gmail blocking on domain name now and not IP >> address / host name >> >> I have added the google verification IN TXT in DNS >> >> >> Is anyone else having or had issues like this ? >> >> Can anyone recomend a contact for google / gmail? or a fix / work around >> >> >> >> Regards >> >> Tim >> >> HaleNET Internet >> ABN: 57 014 068 268 >> e-mail [email protected] >> http://www.halenet.com.au >> P.O. Box 554 Stanthorpe Q 4380 >> Phone (07) 46814999 Bus Hours >> Phone (07) 46852194 After Hours >> >> HaleNET Pty Ltd ACN (082 330 121) >> as trustee for the McCullagh Family Trust >> Trading as HaleNET >> _______________________________________________ >> AusNOG mailing list >> [email protected] >> https://lists.ausnog.net/mailman/listinfo/ausnog >> > _______________________________________________ > AusNOG mailing list > [email protected] > https://lists.ausnog.net/mailman/listinfo/ausnog >
_______________________________________________ AusNOG mailing list [email protected] https://lists.ausnog.net/mailman/listinfo/ausnog
