From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Who is running their own mail server and what do you run?
Date: Wed, 20 Sep 2017 13:47:26 -0400 [thread overview]
Message-ID: <CAC20D2N9tAQAR_LddweoA1idMpb6YgO-76Jykx6CtnmL95XhPg@mail.gmail.com> (raw)
In-Reply-To: <20170920162502.GN25650@mcvoy.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
On Wed, Sep 20, 2017 at 12:25 PM, 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.
for ccc.com - as a 40 year old domain and a 3 letter one at that, spam
was never ending. I gave up when Google asked me to beta test Google Apps
for business. Now the cost of having them do it for me is so cheap, I
really can not justify running it myself. Same for my DNS for my class C,
I moved it all upstream to easyDNS in Canada (great bunch BTW and pricing
is super).
Now I live downstream of a 1G fiber. The Firewall is fairly hot because
of my domain, so many nut cases tap on it; but my logs show its been stable
for a long time since I have it locked down pretty tight. At one time, I
had some of Ches's mapping stuff running that gave me a pseudo-real time
map of where the attacks were come each day (mostly script kiddies). But,
we had a flood in the basement and that system got decommission since I got
bore looking at it. I fear, those bits are rotted.
Anyway moving Mail and DNS upstream did clean up spam and while it did not
rid of the attacks, but it certainly let the primary defense be done at
places better set up to handle them me personally and I bought back much of
my day.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170920/ea4931de/attachment.html>
next prev parent reply other threads:[~2017-09-20 17:47 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 [this message]
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=CAC20D2N9tAQAR_LddweoA1idMpb6YgO-76Jykx6CtnmL95XhPg@mail.gmail.com \
--to=clemc@ccc.com \
/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).