4 ms·
It is somewhat different because you need to convince other mail servers to cooperate with yours whereas the HTTPS server works directly with clients (browsers)
by blfr 10y ago
It is somewhat different because you need to convince other mail servers to cooperate with yours whereas the HTTPS server works directly with clients (browsers) and may function completely independently.
- gcr 10y agoI run my own mail server. It's simple enough to set up SPF in your DNS records to avoid landing in Gmail's spam, at least. Not sure about other providers. I send so little mail that I'm basically background noise.
- seanp2k2 10y agoIt also matters if you host it at a reputable place (DO or AWS or Linode work) and if you want it easy, just wire up your mail server to a transactional email service or smtp.google.com : https://zapier.com/learn/ultimate-guide-to-email-marketing-apps/best-transactional-email-sending-services/ https://zapier.com/learn/ultimate-guide-to-email-marketing-a... It's possible to configure DKIM and SPF and your server correctly, and hopefully stay off blacklists, but if inbox deliverability really matters to you, a [no-cost] plan with a Mandrill or MailGun service should do well for you. It's what I use to have home servers and IoT things send me email, to gmail, and I never have deliverability issues.