From mboxrd@z Thu Jan 1 00:00:00 1970 From: gtaylor@tnetconsulting.net (Grant Taylor) Date: Wed, 20 Sep 2017 19:52:13 -0600 Subject: [TUHS] Who is running their own mail server and what do you run? In-Reply-To: References: <20170920162502.GN25650@mcvoy.com> <201709201639.v8KGdGhC024387@darkstar.fourwinds.com> <83CD6BB4-9617-47F9-A87E-55C447D5F1CC@bitblocks.com> <5156de95-caf9-f7e2-6e85-37d957e406bd@tnetconsulting.net> Message-ID: 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