For months, every email I send through my JAMES server to a gmail
account is flagged as spam. I've been setting up a completely separate
JAMES environment for a different client. I figured this
rebuild-from-scratch would be a good chance to verify that I'm following
all best practices. I thought the problem might have been related to
the fact I was using virtual hosting in the other environment, and there
might have been mismatches due to the sender domain vs. my hosting
domain. But this new environment has only one domain. I am DKIM
signing. I have an SPF record. I have a DMARC record. Yet every email
I send to gmail accounts is still sent to the gmail spam folder. I get
a 10 out of 10 score in mail-tester.com. And even when I open the email
source view in gmail it says DKIM:PASS, SPF:PASS. Yet there it sits...
in the spam folder with the spam flag. All of my environments are on
Amazon Web Services. I've tried requesting different IP addresses.
Nothing works. I even tried sending using my alternate out-of-the-box
JAMES version on the new domain. The out-of-the-box version doesn't
have DKIM. But it uses the same domain name, same ip address, and same
database. And mail sent with this version still goes to spam.
I would say it's just my stuff that gmail hates. But with a brand new
domain and latest build out-of-the-box JAMES, there's nothing specific
about my stuff here.
Can someone test sending mail from JAMES to a gmail account (that hasn't
already whitelisted the sender) and see if they can get an email to not
be sent to gmail spam?
I'm stuck. What else could be wrong? This new client is heavily
dependent upon account-verification via email. If all of the
verification emails end up in spam folders, it will be a disaster the
company.
Please help!
Thx
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
