From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Who is running their own mail server and what do you run?
Date: Wed, 20 Sep 2017 12:59:17 -0700 [thread overview]
Message-ID: <83CD6BB4-9617-47F9-A87E-55C447D5F1CC@bitblocks.com> (raw)
In-Reply-To: <201709201639.v8KGdGhC024387@darkstar.fourwinds.com>
> On Sep 20, 2017, at 9:39 AM, Jon Steinhart <jon at fourwinds.com> wrote:
>
> I run my own server using sendmail. Part of what makes it work is an accretion
> of crud that I have hooked to it over the years which I wouldn't particularly
> suggest to anyone else.
>
> So yes, spam is a big problem. I manage it in a crude but effective way. I
> have a milter (mail filter) that I cobbled together that is invoked by sendmail.
> I also have a separate "spam" user. What the milter does is to take anything
> that it considers to be spam and rewrites the address so that it goes to the
> spam user. I have permissions set up so that I can easily check on spam when I
> have time. Oh yeah, another of my curmudgeon credentials is that I use nmh for
> my MUA (I'm a maintainer).
I use postfix + postgrey. But greylisting doesn't seem to work
any more. I detect spam using various scripts. As you put it,
"accretion of crud"! I block spammer IP addrs via pf.
Probably not the right thing to do. Should look into various
anti-spamming mail filters again. It is trivial to manually
detect spam so probably should experiment with NN code for
this.
I too use nmh (and MH before then). But since my last upgrade
repl, comp, forw seem to bring up a blank X-MH-Attachment in
vi. Used to bring ~/Mail/drafts/<number> file, initialized
with interpreted contents of "components" or "replcomps" file.
Haven't gotten around to looking into this. [This is a
problem with many "maintained" software packages. Things
evolve and if you update only sporadically, you just may miss
a crucial update or two!]
next prev parent reply other threads:[~2017-09-20 19:59 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 [this message]
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
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=83CD6BB4-9617-47F9-A87E-55C447D5F1CC@bitblocks.com \
--to=bakul@bitblocks.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).