Hi,

We use the EASendmail Component and the EASendMailService to send email newsletters to subscribers. Recently, GMail has started marking these as spam.

We have investigated this, and found that if EASendMailService is configured to send direct - acting as it's own SMTP server, then we see the problem.

However, we also have another SMTP server on the same box, and if we configure EASendMailService to relay through the other SMTP server (which has the same IP address and hostname) then GMail doesn't mark the mail as Spam.

In testing, using the same HTML content for both, the only differences that we can find in the Headers of the Email are that the EASendMailService connects to GMail using HELO, and our other SMTP Server uses EHLO, and also there is an extra step in the received path where the EASendMail SMTP Component sends the mail to the EASendMail Service, which appears in the headers like this:

Received: from mx.tractivity.co.uk ([127.0.0.1]) by mx.tractivity.co.uk ([127.0.0.1]) with SMTPSVC;

This line, and specifically the localhost address, doesn't appear in the emails sent using the relay.

We believe that it is the inclusion of the localhost IP in the headers which is causing GMail to mark emails as Spam.


Can anyone suggest how we might address this issue?

Thanks very much

Al.

Hi Ivan, we already have DKIM and SPF on the domain, but the mail is still marked as spam when the EASendmail Service sends direct.

Thanks,

Al.