News for hackers. Stuff that matters.
Re:Lessons learned while protecting Gmail by solotronics on Tuesday March 29, 2016 @09:23PM (#11386320)
there are plenty of examples and at this point it seems that Google has a vested interest in making life difficult for independent or self hosted email providers
Re:Lessons learned while protecting Gmail by techsupporter on Wednesday March 30, 2016 @02:15AM (#11387292)
This has been my experience. I run a very small email setup for a few friends and a couple of tiny businesses. (Yes, we should just pack it in and move to Fastmail but I am hard-headed and have been around the Internet long enough to still be idealistic about these things.)

Every couple of months, Gmail starts depositing any email from my users into spam. No warning, no rejection, just a vague yellow banner on the recipient's view that says "this message has the characteristics of spam." The message could be in plain text with no links, still the same. I have SPF, DKIM, and rDNS all configured. I send from a single IPv4 and single IPv6 address with matching records. No RBL entries. Even the headers on a "spam" message say that everything passes and is fine.

Oh, and it isn't a domain reputation problem: only one of the domains I host even has a web site and all of them are at least five years old. Two of my domains predate Google itself. :P

The real kicker? I can't use their postmaster site, either. Why? We don't generate enough email to rank a report!

Meanwhile, no problems at all from any other receiving hosts. I have to log into several Gmail accounts and click "this is not spam" on some test messages and then it is fine for another 50 days. After that, back to the bit bucket.

Grr.

Re:Lessons learned while protecting Gmail by JacobJans on Wednesday March 30, 2016 @02:01PM (#11391498)
I don't think it is a problem with independent or self hosted email.

I have this problem sending through:

* An email service such as Mailchimp

* My own server with SPF / DKIM and good reputation / deliverability for other domains

* Amazon AWS Simple Email Service

I think it is something on the domain level – perhaps they've flagged the domain.