[MAILSERVER] Mail reported as spam by GMail, Outlook, Yahoo
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[MAILSERVER] Mail reported as spam by GMail, Outlook, Yahoo
Hello,
I'm trying to configure a mailserver for 2 weeks, but I still have a problem: the mails I (or my users) send to Gmail, Outlook or Yahoo as flagged as spam.
Config details
I use Postfix + Dovecot for the mail management.
Everything is hosted on a container, visualized in a dedicated server.
This container have a dedicated IP address (let's call it 1.2.3.4), different than the dedicated server's one (let's call it 111.222.333.444).
My DNS logic is
*.mydomain.tld -> IP of the dedicated server
mydomain.tld -> IP of the dedicated server
mail.mydomail.tld -> IP of the mail container
Reverse DNS from this IP to mail.mydomain.tld
MX mydomain.tld -> mail.mydomain.tld
Here my DNS zone file:
Code:
$TTL 3600
@ IN SOA dns200.anycast.me. tech.ovh.net. (2017053100 86400 3600 3600000 300)
IN NS ns200.anycast.me.
IN NS dns200.anycast.me.
IN MX 1 mail.mydomain.tld.
IN A 111.222.333.444
IN TXT "v=spf1 a mx a:mail.mydomain.tld a:mydomain.tld mx:mail.mydomain.tld mx:mydomain.tld ip4:1.2.3.4 ip4:111.222.333.444 ~all"
600 IN TXT "1|www.mydomain.tld"
* IN A 111.222.333.444
_adsp._domainkey IN TXT "dkim=all"
_dmarc IN TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:admin@mydomain.tld!8m; ruf=mailto:admin@mydomain.tld!10m; rf=afrf; pct=100; ri=86400"
mail IN A 1.2.3.4
mail._domainkey IN TXT "v=DKIM1; k=rsa; p=MYDOMAINKEY"
www IN TXT "3|welcome"
www IN TXT "l|fr"
Do you send out a lot of emails? If a few users on those services mark your mail as spam then it can end up being marked as spam for everyone using the service. I had that problem with AOL even though my DNS/SPF/DKIM/DMARC was all fine. It just took one person marking mails as spam (who was an elderly friend who thought she was pressing the delete button) and then I had to contact AOL to unblock my mail server.
edit: It could also just be that you have been sending a large amount of mail and you are using a new IP address which isn't trusted as mentioned on the outlook.com postmaster site https://mail.live.com/mail/troubleshooting.aspx
The MX record in YOUR dns may not matter. Are you registered as a proper mail domain with your ISP so they forward the valid record. Newer major DNS services check things like this before forwarding mail. (Due to the amount of spam arriving from temporary invalid mail servers.)
98.210.109.176 also looks like it's an ISP dynamic assigned IP and doesn't "reverse" back to the FQDN of the mail server.
This seems to be the IP address of the client PC which submitted the mail to the mail server. The mail server IP address has been replaced by 1.2.3.4. If we did know the IP address and domain name of the mail server it might make finding the problem easier
This seems to be the IP address of the client PC which submitted the mail to the mail server. The mail server IP address has been replaced by 1.2.3.4. If we did know the IP address and domain name of the mail server it might make finding the problem easier
Do you send out a lot of emails? If a few users on those services mark your mail as spam then it can end up being marked as spam for everyone using the service. I had that problem with AOL even though my DNS/SPF/DKIM/DMARC was all fine. It just took one person marking mails as spam (who was an elderly friend who thought she was pressing the delete button) and then I had to contact AOL to unblock my mail server.
edit: It could also just be that you have been sending a large amount of mail and you are using a new IP address which isn't trusted as mentioned on the outlook.com postmaster site https://mail.live.com/mail/troubleshooting.aspx
It's a new service that I'm launching, still in beta. So if we sent 20 mails to these providers, it's a max.
At the beginning of the service (3 weeks ago), I used another IP address (the one of the dedicated server: 111.222.333.444), maybe we sent a few mails with this IP, and now the new one.
Quote:
Originally Posted by wpeckham
The MX record in YOUR dns may not matter. Are you registered as a proper mail domain with your ISP so they forward the valid record. Newer major DNS services check things like this before forwarding mail. (Due to the amount of spam arriving from temporary invalid mail servers.)
I'm not sure to understand this part. Actually I have my domain and it's DNS zone managed on my host company system.
Quote:
Originally Posted by af7567
This seems to be the IP address of the client PC which submitted the mail to the mail server. The mail server IP address has been replaced by 1.2.3.4. If we did know the IP address and domain name of the mail server it might make finding the problem easier
Yep exactly.
The domain is: mail.nebulae.co and the IP 217.182.239.228, if that could help.
The domain is: mail.nebulae.co and the IP 217.182.239.228, if that could help.
A dedicated IP hosted by OVH in France. I get quite a bit of spam from OVH IP addresses, but I find them to be very responsive to abuse reports and seldom need to block them.
The domain TLD is Columbian. South American TLDs tend to be abusive as well...but as you say, neither the IP nor the domain seem to be block-listed in several RBLs I checked.
Also, I don't see anything in the headers you posted indicating that the emails were spammy.
The email is not being *rejected* by Yahoo! or gmail, right? Only routed to the spam folder of the receiving user? (which is you, I presume). That is usually managed by settings over which the recipient has control. Have you looked at the spam settings on the receiving accounts?
For example, adding the sending email address to the allowed senders might [should] prevent the email from being flagged as spam.
A dedicated IP hosted by OVH in France. I get quite a bit of spam from OVH IP addresses, but I find them to be very responsive to abuse reports and seldom need to block them.
The domain TLD is Columbian. South American TLDs tend to be abusive as well...but as you say, neither the IP nor the domain seem to be block-listed in several RBLs I checked.
Also, I don't see anything in the headers you posted indicating that the emails were spammy.
The email is not being *rejected* by Yahoo! or gmail, right? Only routed to the spam folder of the receiving user? (which is you, I presume). That is usually managed by settings over which the recipient has control. Have you looked at the spam settings on the receiving accounts?
For example, adding the sending email address to the allowed senders might [should] prevent the email from being flagged as spam.
Generally, everything else looks good to me.
Thanks for this details!
Right, the emails are not being *rejected*, just moved to spam folder (so in my server log, I have a 250 code, saying everything is okay).
The receiving user is me and some of my betatesters.
My concern is that the mails are tagged as spam with the default configuration. So all my users will have to tell all their contact to unspam them, it doesn't seem to be a viable solution.
Right, the emails are not being *rejected*, just moved to spam folder (so in my server log, I have a 250 code, saying everything is okay).
The receiving user is me and some of my betatesters.
My concern is that the mails are tagged as spam with the default configuration. So all my users will have to tell all their contact to unspam them, it doesn't seem to be a viable solution.
All your user's contacts are on Yahoo or Gmail? Do you have somewhere else to send a test email? Does it get marked there?
My point is that if the mail is being delivered successfully, then there is nothing you can do to "fix" anything. IMO, it's not *your* problem. Your server is delivering the mail and it's being accepted.
All your user's contacts are on Yahoo or Gmail? Do you have somewhere else to send a test email? Does it get marked there?
Yep, almost all other providers are working well!
Quote:
Originally Posted by scasey
My point is that if the mail is being delivered successfully, then there is nothing you can do to "fix" anything. IMO, it's not *your* problem. Your server is delivering the mail and it's being accepted.
Damn, that sucks. Okay then. But I don't understand how other people achieve to send emails to this providers without been tagged as spam (with similar configurations). That's really strange..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.