> On 16 Feb 2016, at 08:04, Gilles Chehade <[email protected]> wrote: > > On Mon, Feb 15, 2016 at 06:49:05PM -0800, Steve Conrad wrote: >> Has anyone else noticed how gmail dumps messages from new mailservers into >> the spam heap by default? >> >> A bit of a slap in the face after going to all the trouble of setting up my >> own domain and hosting it on my own smtp server. >> >> I can see where it fits into google's panoptic vision of global domination >> to undermine the efforts of independant operators, but this still seems a >> bit over the top. >> >> While I have no interest in salting google's data mine with my personal >> correspondence, unfortunately, many of those with whom I correspond seem >> cheerfully oblivious to the down side of total surveilence. I grow tired of >> telling them to go fish my mail out of their spam folder. >> >> Eventually, if they mark a few of them as not spam, it starts to work as >> expected. Still, I can't help but feel that google is abusing its position >> of market dominance in order to make perfectly standards compliant, well >> configured mail servers look like such a shabby hack that people are really >> better off sticking with gmail and leaving smtp to the experts. >> >> Thoughts? >> Work arounds? >> > > Unless you send large volumes, dkim-signing your mail, setting up a SPF > record and making sure you have a proper rDNS and matching EHLO is just > enough to get you inbox if your message is a regular mail.
Agreed. For IPv4 I do not even seem to need DKIM here. But with native IPv6 delivery, it is a different story and may require slightly more effort. > -- > Gilles Chehade > > https://www.poolp.org @poolpOrg > > -- > You received this mail because you are subscribed to [email protected] > To unsubscribe, send a mail to: [email protected] > -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
