From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] Who is running their own mail server and what do you run?
Date: Wed, 20 Sep 2017 23:30:10 -0600 [thread overview]
Message-ID: <9fc7011a-b162-0b3c-62cb-731cab9a1f91@tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.1709211348380.89458@aneurin.horsfall.org>
On 09/20/2017 10:14 PM, Dave Horsfall wrote:
> Didn't I just see you somewhere else? :-)
Probably.
> Yep; as I recall, the RFC line length is no more than 254 chars (I
> think), with no limit on the number of continuation lines. Try
> connecting to my server at horsfall.org (I'll make you wait around 10
> seconds), then check out my RFC-compliant banner... I'll keep an eye
> out for you in my logs :-)
Very interesting.
I want to figure out how to make a multi-line banner. (In Sendmail.)
I feel like your greet_pause was more than 10 seconds, but so be it.
Still shouldn't be a problem.
> Check out www.horsfall.org/spamlog.pdf for a nice pretty graph; the
> rejects on "banner" is the purple one on the top; the "reject" line is
> the red one, and the "spam" line (stuff that gets through) is pink (for
> SPAM, geddit?).
>
> Note that many of the "banner" violations are from woodpeckers i.e. they
> keep trying until they either give up or I notice (and firewall them).
I've wondered about a more featureful syslog daemon that could pattern
match and watch for the log message for pre-greeting traffic, and
forward them to a script that would dynamically update an RBL. I just
haven't found enough round-tuits yet.
> The tools behind this are still a work in progress, so I don't currently
> log the number of "wait" violations etc (it was implemented fairly
> recently).
>
> (And yes, my HTML programming sucks.)
Interesting work. I'd be curious to see how you're doing some of that
and think about implementing it myself.
Thanks for sharing Dave.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2017-09-21 5:30 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 [this message]
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=9fc7011a-b162-0b3c-62cb-731cab9a1f91@tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
/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).