From: Warren Toomey <wkt@tuhs.org>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Testing Mail Connectivity
Date: Wed, 26 Jun 2019 12:50:23 +1000 [thread overview]
Message-ID: <20190626025023.GA17457@minnie.tuhs.org> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1906260938130.10033@aneurin.horsfall.org>
On Wed, Jun 26, 2019 at 10:26:31AM +1000, Dave Horsfall wrote:
> Are you still here, Warren? I did email you, but no reply so far (and no
> reject either, otherwise I would've spotted *that* too).
All, sorry for the off-topic reply and query. I'm posting this here
so that Dave can read it in the web archive. I'm guessing the problem is
the one Dave identified earlier:
> You need to grok Sendmail's log format (and SMTP in general), but it means
> that Minnie connected to my server, waited the requisite time for the greeting
> banner, and then shat herself when she saw my ginormous banner and dropped the
> connection without so much as a good-bye...
i.e.a multiline response to the HELO/EHLO which meets the RFC specs.
> That simple measure, along with the greeting pause and some simple RFC DNS
> checks, block a lot of the crap.
I've just subscribed to the Postfix mailing list, and I'll ask on there
if there is a configuration change I can make to allow my Postfix client
to deal properly with Dave's multiline HELO/EHLO response. And why it can't
at present.
But if someone here already knows, could they let me know?!
Thanks! Warren
next prev parent reply other threads:[~2019-06-26 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 1:17 [TUHS] Testing Dave Horsfall
2019-06-26 0:26 ` [TUHS] Testing... Or, Why I Did It My Way (tm) Dave Horsfall
2019-06-26 2:50 ` Warren Toomey [this message]
2019-06-26 4:07 ` [TUHS] Testing Mail Connectivity Grant Taylor via TUHS
2019-07-09 0:53 ` [TUHS] Testing... Or, Why I Did It My Way (tm) Dave Horsfall
2019-07-09 2:02 ` Grant Taylor via TUHS
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=20190626025023.GA17457@minnie.tuhs.org \
--to=wkt@tuhs.org \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/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).