Re: [tlug] Cheap e-mail providers

[Curt Sampson <cjs@example.com>]

On 2019-03-26 11:10 +0900 (Tue), Stephen Lasseter wrote:

> > On Mar 26, 2019, at 10:03, Curt Sampson <cjs@example.com> wrote:
> >
> > Yes. And as mentioned before, in these days of having to handle spam,
> > both with incoming DNS blacklists (Spamhaus, etc.) and doing SPF and
> > similar for outgoing mail, even "basic" mail configuration is no
> > longer trivial.
>
> I keep hearing this, but I’ve been running mailcow for a number of
> domains on a vps for the past year with minimal fuss and few issues.
> It is a docker-compose setup with all the stuff you would expect for
> a mail server stack.  And if I decide I don’t like my vps provider,
> I can migrate to another pretty easily.  My spam levels have been
> just as low as they were when I was on gsuite.  My running costs are
> just \900/month for my current choice of vps in Japan.

I wasn't talking about incoming spam; I was talking about getting your
outgoing mail blocked.

I too have had few issues, perhaps in part because my mail server is
on a "business" connection and so presumably in an IP block with no
consumers in it. But the worry is always there; problems can rear
their head at any time and, if they do, might require some immediate
and painful fixes. It's a risk I'm willing to live with, but other may
not want to.

Containerizing your applications like this is definitely the way to go
these days. I've started working on that myself, albeit I've only
poked at it a bit. <https://github.com/0cjs/contapps>

> https://mailcow.email.   mail-in-a-box is another popular one, though it is not docker based.

But almost anything can be Docker-based if you want to make it so. :-)

cjs
-- 
Curt J. Sampson      <cjs@example.com>      +81 90 7737 2974

To iterate is human, to recurse divine.
    - L Peter Deutsch