[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [nmh-workers] logging outgoing messages

From: Ken Hornstein
Subject: Re: [nmh-workers] logging outgoing messages
Date: Wed, 10 Jul 2019 11:28:20 -0400

>I grovel around MTA logs on a machine hosting Mailman for all the UK LUG
>lists and the queue ID is the key thing.  It's the first thing I have to
>work out if it's not provided.

But do the users provide you the queue-id?  That's what I'm really curious

>I'd keep the 250 as I expect we'd be doing this for 25x and its value is
>significant.  Also, there might be multiple lines of 25x.

Sigh.  It's these sorts of things that make stuff spin off the rails.
I am aware that in theory any 2xx code can be returned by the DATA
command, but I think 99.9% of the time it will just be a 250.  And there's
no way we should return a multiline response; I think just the last
output of the positive repsonse code (after the 2xx) is fine.

>Is it just 25x that should trigger this hook, or 4xx, etc., too?

To me this hook should only be triggered if the post is successful.
None of the other hooks are triggered on failure.

>I agree.  Something specialising in queueing locally and then forwarding
>on will do a better job and offer more options than extending nmh to
>include those options over time.  I see that nmh has to talk TLS SMTP to
>submit an email locally, e.g. same host or company, and that can be used
>to also submit across the Internet, but that doesn't mean it's a good

First ... what unreliable email providers do you guys use that go down
all of the time?  Secondly ... I am seeing more and more authentication
methods that require keeping some kind of state and possibly user
interaction in the MUA (GSSAPI and XOAUTH2 are two examples that I have
personally encountered), and that makes doing authentication in the MTA
very problematic.  I think the days of embedded plaintext passwords in
your MTA configuration file are slowly coming to an end.

Like I said in my previous email ... we'll continue to support that.
But I can't recommend it to the average nmh user.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]