0

Possible Duplicate:
How to send emails and avoid them being classified as spam
Email postfix marked as spam by google

I'm having a few issues sending email from our mail server. Most seem to work, but some addresses are getting picked up as Junk/Unsafe.

We run our own mail server sitting on Ubuntu on IP 192.168.0.9, and on this mail server(Zimbra) we have approx 15 different domains for sending emails.

Our emails are then send from our server, via our fibre router(so via the external IP of the router).

Our external IP's RDSN resolves to mail.ourmaindomainname.com which we want it to.

All of our domain names(hosted on a different external web server) have A records and MX records.

e.g if we had test-domain.co.uk the following occurs:

MX points to mail.test-domain.co.uk and the A record (mail.test-domain.co.uk) points to the external ip address of our email server, which is what we need it to be.

Any suggestions how I can work out whats going on, or how I can stop these being picked up by spam/junk etc?

I've seen one thing, on mxtoolbox, whereby I did an SMTP test, and it says: Warning - Reverse DNS does not match SMTP Banner

I think this could be because i'm sending from say test-domain.co.uk but the server is setup to ourmaindomainname.com but as we only have 1 IP address, I need the rdns to be from mail.ourmaindomainname.com

Thanks for the help

  • 2
    You should try to actually catch a message which was filtered and then examine that as to why it was filtered. There are far too many possibilities as to just "poke around" – MichelZ Jul 17 '12 at 08:56
  • This is asked very frequently and different answeres have slightly different slants - you need to look at PTR and SPF records, and rate lmiting for some recipient domains. But these still won't solve all the prolems. – symcbean Jul 17 '12 at 11:54
  • Also, to note, A while back when we migrated to Fibre, we asked BT(our fibre supplier) to setup the PTR records: EXTERNALIP > mail.ourmaindomain.com so that is already in place. Nothing todo with SPF though.. – MercJones Jul 17 '12 at 12:24

2 Answers2

1

In this thread you find 2 tools: Email test and Mx toolbox these tools give very good info to check all relevant stuff you need to configure your email server. (like SPF/DKIM/Reverse DNS/etc..)

Good luck!

Joost Verdaasdonk
  • 471
  • 1
  • 10
  • 24
  • I just notice you mention mxtoolbox in your question. This reverse DNS doesn't match SMTP banner problem I explain also in the link I gave in the above question – Joost Verdaasdonk Jul 17 '12 at 09:00
  • I've done a PTR check on the IP address(main external ip) and it resolves to mail.ourmaindomainname.com, should the SPF record be checked against the main domain(mail.ourmaindomain.com) or the domain i'm having problems with? – MercJones Jul 17 '12 at 12:17
  • I've 2 domain's and created SPF for both domain and sub domain but here: http://serverfault.com/questions/322949/do-spf-records-for-primary-domain-apply-to-subdomains another option include is used. Never used it before but perhaps you can try. What I normaly do with setting up a mail server is used the above tools and setup everything so all is validated. After this I start testing if my mail works ok. ;-) Good luck – Joost Verdaasdonk Jul 17 '12 at 12:41
  • I've now added a SPF record for that domain, which is: v=spf1 a mx ip4:EXTERNALIP/32 -all its picked up the SPF record straight away, but when emailing hotmail, it's still going to the junk account – MercJones Jul 17 '12 at 15:44
  • I think hotmail is using these rules: http://mail.live.com/mail/services.aspx Perhaps you can give me the domain your sending email with so I can try out some tools to help you find clues. – Joost Verdaasdonk Jul 17 '12 at 16:19
  • To clarify, SPF relates to the domain of the email address email is being sent for, while forward-confirmed reverse DNS (fcrDNS) and matching banner/PTR relate to the fully-qualified domain name that identifies the mail server. For example, if you have the email address example@hotmail.com the SPF record in hotmail.com would identify servers permitted to send its mail. The server might be someserver.outlook.com, which resolves to 10.2.3.4, while the PTR record for that IP resolves back to someserver.outlook.com. Connecting to the server gives an SMTP banner of someserver.outlook.com. – Sam_Butler Nov 12 '18 at 18:28
0

Something like this happened with my web hosting provider as well and I think after I switched to a dedicated server the problem stopped. So it might be that the same is happening with your servers.

Regards, Ihsan

  • We host our own email internally, and we have a dedicated server where all our domains are registered to/hosted and have all the A/MX records etc configured on. – MercJones Jul 17 '12 at 12:19