4 ms·
I'm still wondering why there's no go-to choice to spin up a docker container that has everything preconfigured.
by tiborsaas 4y ago
I'm still wondering why there's no go-to choice to spin up a docker container that has everything preconfigured.
- rglullis 4y agoBecause the problem is mostly about the reputation of the IP address. Setting up an email server is somewhat easy. Ensuring that other servers consider yours as legitimate that is the problem.
- cubesnooper 4y agoSpam is often sent from big providers, too. For several years I hosted my email the “middle ground” way (i.e., relaying outgoing mail via Google Workspace), and despite using DMARC correctly it was not infrequent that my emails would go to spam (even to GMail boxes) or never show up at all. Obviously GMail is such a giant that email providers have to be very careful when blocking it, but enough spam comes from there that receivers clearly use some heuristics to block some of it. I’ve even received multiple rejection notices because the GMail server my email was sent through happened to be on a blacklist! I switched last year to sending directly from my VPS. It was partly for privacy from Google, but moreso so I could enforce outgoing TLS. For the first few days they went to spam boxes or moderation queues, but I made sure they were rescued, and ever since I’ve had no deliverability issues sending to Google, some local ISPs, and even Microsoft (which seems crazy, as I never got a mail from my domain to show up in Outlook when I was relaying through Google). I can only speak for my own experience, of course. But that is what I experienced.
- Avamander 4y agoI have had very similar experiences. Doing things perfectly and building up "reputation" helps a lot.
- elorant 4y agoWould you trust it if there was one?
- tiborsaas 4y agoI'd trust it the same way as other open source projects.
- infomax 4y agoAt my company we are using dockerized mailcow on a Hetzner VPS and it has taken us some time to have the IP whitelisted in all major e-mail providers. The easiest to work with have been Microsoft and Yahoo. I still haven't found a way to whitelist our IP on centurylink.net, charter.net and att.com (please let me know if you have any ideas) Some links that might be of help to others: [1] https://sendersupport.olc.protection.outlook.com/snds/data.aspx https://sendersupport.olc.protection.outlook.com/snds/data.a... [2] https://io.help.yahoo.com/contact/index?page=confirmation&locale=en_US&key=1f5487f664e74b6483665dc3e84c1fc9 https://io.help.yahoo.com/contact/index?page=confirmation&lo... [3] https://postmaster.google.com/u/0/dashboards#st=userReportedSpamRate&dr=7 https://postmaster.google.com/u/0/dashboards#st=userReported... [4] https://support.microsoft.com/en-us/supportrequestform/8ad563e3-288e-2a61-8122-3ba03d6b8d75 https://support.microsoft.com/en-us/supportrequestform/8ad56... [5] https://www.mail-tester.com/ https://www.mail-tester.com/
- sirnoggin 4y agoCannot upvote you enough for the yahoo link.
- 3np 4y agoMailinabox and Mailu are both popular.
- hedora 4y agoYou could build one for SES. You'd need to write an Amazon CloudFormation template that configured all the things correctly. The result would be a screen or two of auditable gobbledygook that took a week or so to write. Somewhere in there, there'd be a pointer to an EC2 or ECS image, among other things. It'd be a learning experience, and very tied to AWS. I wonder if someone else already did this.