The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
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 19:52:13 -0600	[thread overview]
Message-ID: <c828e69a-8fa1-ac14-ce62-920e7b4a9dfd@tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.1709211044510.89458@aneurin.horsfall.org>

On 09/20/2017 06:55 PM, Dave Horsfall wrote:
> Dunno, as I've never used it, but there are some clever tricks that can 
> be used to enforce RFC-compliancy (a lot of spamware is written by 
> idiots who don't understand the finer points of SMTP):

Some of the ones that I've seen make me understand SMTP at all, or if 
they are using a library to abstract it.

>      Enforce proper DNS configuration e.g. must resolve etc, and must
>      actually exist.
> 
>      Make 'em wait a few seconds before sending your own banner, and drop
>      the connection if they send beforehand.

I do both of those.

>      Set up an enormous greeting banner (many long lines); there is nothing
>      in the RFC that says it has to be a single short line.

I've never thought about a long, multi-line banner.

> These simple measures alone cut out most of the crap; the rest are 
> handled by various DNSBLs and my private access list.

I agree with the first two, and I'd like to know more about the 
effectiveness of the third.



-- 
Grant. . . .
unix || die


  reply	other threads:[~2017-09-21  1:52 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 [this message]
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=c828e69a-8fa1-ac14-ce62-920e7b4a9dfd@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).