From: tytso@mit.edu (Theodore Ts'o)
Subject: [TUHS] Who is running their own mail server and what do you run?
Date: Wed, 20 Sep 2017 18:25:46 -0400 [thread overview]
Message-ID: <20170920222546.7zp2irz7xg6vhsrh@thunk.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1709201302190.6255@waffle.shalott.net>
On Wed, Sep 20, 2017 at 01:13:57PM -0700, jason-tuhs at shalott.net wrote:
> I run my own mail. Linux and FreeBSD servers, running qmail (plus lots of
> patches) and dovecot (and local, direct maildir access on the servers, for
> users who want to run alpine or mutt).
I run my own e-mail as well. I use Debian Stable on Linode, using
dovecot, exim, and spamassassin.
> The real challenge in hosting your own mail seems to be on the outbound
> side. Google seems to be pretty distrustful of small, hobbyist systems,
> even though none of my IPs has ever been used for spamming, and I took the
> time to setup stuff like SPF. I haven't heard too many complaints lately,
> but for a while, I had a number of users complaining that their emails were
> always being marked as spam for gmail users...
The big thing is to use SPF and DKIM (I use opendkim), and to make
sure your IP address (or IPv6 address block) is clean. If it is not,
you might have to ask your hosting provider to give you a clean IP
address.
- Ted
next prev parent reply other threads:[~2017-09-20 22:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 16:25 Larry McVoy
2017-09-20 16:39 ` Jon Steinhart
2017-09-20 19:59 ` Bakul Shah
2017-09-20 21:26 ` Jon Steinhart
2017-09-20 23:17 ` Robert Brockway
2017-09-21 0:00 ` Dave Horsfall
2017-09-21 0:08 ` Grant Taylor
2017-09-21 0:55 ` Dave Horsfall
2017-09-21 1:52 ` Grant Taylor
2017-09-21 4:14 ` Dave Horsfall
2017-09-21 5:30 ` Grant Taylor
2017-09-21 15:43 ` Ian Zimmerman
2017-09-21 0:38 ` Robert Brockway
2017-09-21 1:30 ` Lawrence Stewart
2017-09-21 1:57 ` Grant Taylor
2017-09-21 3:04 ` Robert Brockway
2017-09-21 5:20 ` Grant Taylor
[not found] ` <20170921042528.E12C5156E523@mail.bitblocks.com>
2017-09-21 4:45 ` Robert Brockway
2017-09-21 4:58 ` Dave Horsfall
2017-09-21 5:34 ` Grant Taylor
2017-09-21 15:49 ` Ian Zimmerman
2017-09-20 16:46 ` Warner Losh
2017-09-20 17:01 ` Steve Nickolas
2017-09-20 17:39 ` Henry Bent
2017-09-20 22:54 ` Greg 'groggy' Lehey
2017-09-20 16:59 ` Kurt H Maier
2017-09-20 17:10 ` Arthur Krewat
2017-09-20 17:14 ` Jon Steinhart
2017-09-20 18:15 ` Arthur Krewat
2017-09-20 23:45 ` Dave Horsfall
2017-09-20 22:54 ` Steve Simon
2017-09-20 23:31 ` Grant Taylor
2017-09-20 23:57 ` Bakul Shah
2017-09-21 0:02 ` Larry McVoy
2017-09-21 1:08 ` Ian Zimmerman
2017-09-21 12:36 ` Steve Simon
2017-09-20 17:47 ` Clem Cole
2017-09-20 17:54 ` Rico Pajarola
2017-09-20 17:57 ` Ian Zimmerman
2017-09-20 18:22 ` William Pechter
2017-09-20 19:11 ` Grant Taylor
2017-09-20 19:25 ` Ian Zimmerman
2017-09-20 19:54 ` William Pechter
2017-09-20 19:09 ` Grant Taylor
2017-09-20 23:26 ` Michael Parson
2017-09-20 18:21 ` Grant Taylor
2017-09-20 18:51 ` Corey Lindsly
2017-09-20 20:13 ` jason-tuhs
2017-09-20 22:25 ` Theodore Ts'o [this message]
2017-09-20 23:06 ` Dave Horsfall
2017-09-21 12:40 ` Ben Greenfield
2017-09-23 9:12 ` Dario Niedermann
2017-09-21 20:05 Norman Wilson
2017-09-21 21:02 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170920222546.7zp2irz7xg6vhsrh@thunk.org \
--to=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).