From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Who is running their own mail server and what do you run?
Date: Wed, 20 Sep 2017 13:01:55 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1709201300480.95826@frieza.hoshinet.org> (raw)
In-Reply-To: <CANCZdfqzRWGEyj2cFYz5_sH8OW=OdjbSh=7Tb1Li9S4gJjv_9w@mail.gmail.com>
On Wed, 20 Sep 2017, Warner Losh wrote:
> On Wed, Sep 20, 2017 at 10:25 AM, Larry McVoy <lm at mcvoy.com> wrote:
>
>> I tried running my own server on mcvoy.com but eventually gave up, the
>> spam filtering was a non-ending task.
>>
>
> I ran my own server for bsdimp.com and village.org form the early 90s until
> 2009 or so. I switched to gmail when I was seriously looking at dropping
> $10k for a server that had enough horse power to filter the 50k-75k spam I
> was getting a month at that time. Switching to google was easier and I
> didn't have to spend the $10k nor the 4 hours a week on the care and
> feeding of the black lists, etc.
>
> Warner
>
I've run my own server for over a decade. I don't get an unmanageable
amount of spam, though if there's a way I can make it easier to filter the
crud out using the tools (postfix, alpine) I have, ...sure
-uso.
next prev parent reply other threads:[~2017-09-20 17:01 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 [this message]
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
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=alpine.BSF.2.02.1709201300480.95826@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).