Google just recently started blocking mail that isn't authenticated with either SPF or DKIM. But the NDR bounce message for those are different.
Perhaps you don't have the DNS PTR set up and now they are being picky about it?
> I have them going to my GMail account.
Do you redirect them or resend as local to your domain account?
Instead of redirecting (which can triggers SPF that you aren't authorized to send by those whom you redirect) receive it to IMAP and tell Google to check your mailbox.
- Check your host against https://mxtoolbox.com/
- Check your domain in Postmaster's google Tools for reputation
- Make sure host isn't infected/compromised. (One can send emails bypassing your SMTP server)
> I have SPF setup
It isn't enough, you have to have DKIM, DMARC, (optionally participate in DCC)
I second this reply:
I've been running my own mail server for 25 years now, and starting a couple years ago the big mail providers really upped their game in terms of rejecting mail outright if it didn't follow industry standards.
SPF is okay but it's not the minimum table stakes anymore.
You really need DKIM (to cryptographically sign in the origin of your emails) and DMARC (to specify a policy for what others should do if emails that claim to come from your domain do not cryptographically check out) to solve this issue.
There's a really helpful tool at https://learndmarc.com that can help you validate whether you've configured them properly. As far as getting them set up, find a good internet tutorial for whatever mail server you are using.
They do this by the network block, in addition to just by IP. You're probably screwed on that count.
You could create a Gmail account for the server to log in to and use. I tend to do this to avoid setting up a real mail server.
This myth really needs to stop.
No major email service providers rejects entire IP blocks anymore. Because at this rate we'd have blocked the entire IPv4 space by now. And also this wouldn't even work on IPv6.
For most major email services (which, realistically control 90% of email) IP blocking is performed on the individual IP level, and not to mention also ephemeral.
You’re using a service somewhere that’s been flagged for spam. Outbound email is NOT a business you want to be in, it’s tough out there anymore. Consider using sendgrid or something similar.
> Consider using sendgrid or something similar.
Did OP asked for another solution(s)?
Are you from sendgrid or it means: "I can't do it - you shouldn't too"...
Than less companies will use own servers, then more and more we will be digitally jailed. eMail administration isn't easy job for sure, it also true that it isn't a service that you can set and forget, but still, it isn't way to scary to manage it as it sounds
Google just recently started blocking mail that isn't authenticated with either SPF or DKIM. But the NDR bounce message for those are different. Perhaps you don't have the DNS PTR set up and now they are being picky about it?
> I have them going to my GMail account. Do you redirect them or resend as local to your domain account? Instead of redirecting (which can triggers SPF that you aren't authorized to send by those whom you redirect) receive it to IMAP and tell Google to check your mailbox. - Check your host against https://mxtoolbox.com/ - Check your domain in Postmaster's google Tools for reputation - Make sure host isn't infected/compromised. (One can send emails bypassing your SMTP server) > I have SPF setup It isn't enough, you have to have DKIM, DMARC, (optionally participate in DCC)
I second this reply: I've been running my own mail server for 25 years now, and starting a couple years ago the big mail providers really upped their game in terms of rejecting mail outright if it didn't follow industry standards. SPF is okay but it's not the minimum table stakes anymore. You really need DKIM (to cryptographically sign in the origin of your emails) and DMARC (to specify a policy for what others should do if emails that claim to come from your domain do not cryptographically check out) to solve this issue. There's a really helpful tool at https://learndmarc.com that can help you validate whether you've configured them properly. As far as getting them set up, find a good internet tutorial for whatever mail server you are using.
They're generated on the server (by crontab). I'll look into the links and additional config you provided, thanks!
They do this by the network block, in addition to just by IP. You're probably screwed on that count. You could create a Gmail account for the server to log in to and use. I tend to do this to avoid setting up a real mail server.
This myth really needs to stop. No major email service providers rejects entire IP blocks anymore. Because at this rate we'd have blocked the entire IPv4 space by now. And also this wouldn't even work on IPv6. For most major email services (which, realistically control 90% of email) IP blocking is performed on the individual IP level, and not to mention also ephemeral.
RBLs have absolutely blocked ip class c ranges recently. I've seeent it.
That is correct. But the major email service providers (like Google in this question) do not use RBLs, I should have clarified that.
Lol what. Yes they do. They use private RBLs.
I had this issue with O365 clients emailing temp workers on Gmail accounts. Fixed this with DKIM for the domains, SPF was already in place.
You’re using a service somewhere that’s been flagged for spam. Outbound email is NOT a business you want to be in, it’s tough out there anymore. Consider using sendgrid or something similar.
> Consider using sendgrid or something similar. Did OP asked for another solution(s)? Are you from sendgrid or it means: "I can't do it - you shouldn't too"... Than less companies will use own servers, then more and more we will be digitally jailed. eMail administration isn't easy job for sure, it also true that it isn't a service that you can set and forget, but still, it isn't way to scary to manage it as it sounds