Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Bakul Shah
On Jul 9, 2019, at 5:56 PM, Ronald F. Guilmette wrote: > > In message <20190710004749.89c1b163...@pb-smtp1.pobox.com>, > Ken Hornstein wrote: > >> If I could make sendmail/pipe punch the user in the face every time a >> message was sent using it... > > Please don't. I'm using it. > > It is

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Michael Richardson
Ronald F. Guilmette wrote: >> If I could make sendmail/pipe punch the user in the face every time a >> message was sent using it... > Please don't. I'm using it. > It is MUCH faster than trying to feed the message to Postfix > (aka Sendmail) via SMTP/587 because in the case

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Ronald F. Guilmette
In message <20190710004749.89c1b163...@pb-smtp1.pobox.com>, Ken Hornstein wrote: >If I could make sendmail/pipe punch the user in the face every time a >message was sent using it... Please don't. I'm using it. It is MUCH faster than trying to feed the message to Postfix (aka Sendmail) via

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Robert Elz
Date:Tue, 09 Jul 2019 19:39:08 -0400 From:Ken Hornstein Message-ID: <20190709233912.db2aa73...@pb-smtp20.pobox.com> | - We don't, in general, want to have any more #ifdefs in the code unless | they are completely unavoidable I agree with that, and even when

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Ken Hornstein
>Could we log the entire result, and let the post hook take care of the >various queue formats? That was what I suggested. Clearly nmh shouldn't be in the business of figuring out what (if any) the queue identifier is based on the SMTP DATA response message. >> I am neutral about this being

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Michael Richardson
Ken Hornstein wrote: > - It is not clear to me that you can state with certainly that the > 250 response code will contain the queue identifier (that is, in > fact, not a concept that appears anywhere that I can find in the SMTP > RFCs). As a practical matter I've never had to

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Valdis Klētnieks
On Tue, 09 Jul 2019 17:43:06 -0400, Steven Winikoff said: > sm_reply.length = rp - sm_reply.text; > sm_reply.text[sm_reply.length] = 0; > +#ifndef NOSYSLOG > +if (strncmp(sm_reply.text, "OK id=", 6) == 0) > +{ This is highly dependent on the remote MTA. Google, for

Re: [nmh-workers] logging outgoing messages

2019-07-09 Thread Ken Hornstein
>Is there any interest in adding an improved version of this to the code >base? So ... maybe? But, some thoughts. - We don't, in general, want to have any more #ifdefs in the code unless they are completely unavoidable (e.g., operating system differences or optional third-party libraries

[nmh-workers] logging outgoing messages

2019-07-09 Thread Steven Winikoff
I recently modified my configuration for nmh-1.7.1 to connect directly to my ISP's sendmail, rather than going through sendmail on my desktop Linux system. This works perfectly, but as a side effect I lost all logging of outgoing messages. This isn't the end of the world, but it's a pain because

Re: [nmh-workers] success using the OAUTH2 with gmail.

2019-07-09 Thread Ken Hornstein
>> Let's say in a hypothetical future we support IMAP. That means that >> nearly every command would take a whole pile of arguments like >> -initialtls, -host, -port, -sasl, and more. Obviously changing your >> profile for every nmh command would be awful. So there should be some >> way of

Re: [nmh-workers] Ordinal Indicators.

2019-07-09 Thread Ralph Corderoy
Hi Valdis, > > Is -42nd handled? > > I admit being totally mystified as to what situations require proper > handling of negative ordinals Well, from here the one after next is the 2nd, and the one before last is the -2nd. Regardless, the code and documentation should match, and it seems