Re: [nmh-workers] logging outgoing messages

2019-07-10 Thread Ralph Corderoy
Hi Ronald, > It is MUCH faster than trying to feed the message to Postfix (aka > Sendmail) via SMTP/587 because in the case of just piping the message, > Postfix doesn't make me wait until it has done the DNS lookups it > thinks it needs to do in order to process the message. I have send(1)

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

Re: [nmh-workers] Ordinal Indicators.

2019-07-08 Thread Ralph Corderoy
Hi, Is -42nd handled? IIRC we demand C99 so we know rounding is towards zero. But C's remainder operator, ‘%’, returns the sign of the dividend, unlike modulo. And then there's two's complement so INT_MIN can't be made positive. $ for a in ' -' ' '; do > for b in ' -' ' '; do

Re: [nmh-workers] Ordinal Indicators.

2019-07-08 Thread Ralph Corderoy
> Geez, you could have just SAID that Now where would be the fun in that. :-) -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] Ordinal Indicators.

2019-07-08 Thread Ralph Corderoy
Hi Ken, > > Were you paying attention to kre's sh and my sed? :-) > > I mean ... yeah? Steal from the best, and all that! I had a few free > minutes, I thought, "Oh, huh, nmh SHOULD have a function to output the > ordinal string for dates and such", and I though it should be pretty > easy and

Re: [nmh-workers] Ordinal Indicators.

2019-07-08 Thread Ralph Corderoy
Hi Ken, > > This is true. To correct that, I note mh-format(5) too has no > > function to produce the ordinal suffix. :-) > > Fixed. Impressively quick work. + int digit = value % 10; + const char *suffix; + + switch (digit) { +

Re: [nmh-workers] Ordinal Indicators.

2019-07-08 Thread Ralph Corderoy
Hi kre, > D=$(date +%d) > case "$D" in > [023]1) ORD=st;; > [02]2) ORD=nd;; > [02]3) ORD=rd;; > *) ORD=th;; > esac > case "$D" in > 0*) SP=;; > *) SP=' ';; > esac I ended up with $ cat ~/bin/ordsuff #!

Re: [nmh-workers] Ordinal Indicators.

2019-07-08 Thread Ralph Corderoy
Hi kre, > LC_TIME says how time (of day) is represented (d/m/y m/d/y, 12 or 24 > hour, etc) I had a need today to have date(1) produce ‘8th’ for today and find its interpreted sequences don't support the https://en.wikipedia.org/wiki/Ordinal_indicator, but then neither does POSIX's LC_TIME, it

Re: [nmh-workers] Formatting HTML to Text: netrik.

2019-07-07 Thread Ralph Corderoy
Hi Ken, > > Here is what I have set. is this what you are talking about? Or do > > I need to fiddle sonmething else entirely? > > > > % env | fgrep LOCALE > > XTERM_LOCALE=en_US.UTF-8 > > Yeah, that's correct. Is it? That's only xterm(1)'s locale. I think rfg should show us the output of

Re: [nmh-workers] Formatting HTML to Text: netrik.

2019-07-07 Thread Ralph Corderoy
Hi, rfg wrote: > I have trouble believe that in this day and age, when we have had > REALLY widespread use of HTML for around a couple of decades now, that > there are still -zero- tools tyat can quicky render HTML into plain > text without mucking it up somehow. I found

Re: [nmh-workers] Formatting HTML to Text: netrik.

2019-07-07 Thread Ralph Corderoy
Hi David, rfg wrote: > > All these in combination you end with a reasonable reply to HTML > > emails. The downside is that you don't get to keep the original > > email unless you make a copy of it and it's fairly hacky. > > Thanks for all the tips, but this is a non-starter for me. I need to >

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

2019-07-07 Thread Ralph Corderoy
Hi Ken, > 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] fetchmail and SNI (and pop.gmail.com)

2019-06-28 Thread Ralph Corderoy
Hi Ken, > I guess the core issue is that for Google servers when using TLS 1.2 > SNI isn't required, but for TLS 1.3 it is; well, let me rephrase that. > If you negotiate TLS 1.3 you get the bogus certificate if you don't > send a SNI. But it seems like the 'right' solution is we should be >

Re: [nmh-workers] burst behavior

2019-06-28 Thread Ralph Corderoy
Hi Ken, > Yes ... but I would personally prefer if it was more generic. Like if > the -endofdigest switch took a regular expression That's an improvement. An alternative is a -preproc that took a command that preprocessed each MIME-decoded part before being read for bursting; only used in

Re: [nmh-workers] fetchmail and SNI (and pop.gmail.com)

2019-06-27 Thread Ralph Corderoy
Hi Michael, > I have used: > >fetchmail --verbose --sslcertpath="/etc/ssl/certs" --sslcertck >--proto POP3 --mda "rcvstore -sequence gmail +inbox" >--logfile /var/tmp/gmail.log pop.gmail.com > > to get my gmail downloaded for some time now. Has your OpenSSL been upgraded

Re: [nmh-workers] burst behavior

2019-06-27 Thread Ralph Corderoy
Hi Paul, > An obvious fix (for me) is to pre-process the digest, and > hyphen-escape all lines which follow the "END OF DIGEST" line and > which begin with a '-', by adding an extra '- ' at the start of line. > If I do that, then burst will do the right thing, and ignore all of > the trailer

[nmh-workers] Formatting HTML to Text: netrik.

2019-06-27 Thread Ralph Corderoy
Hi, Revisiting once again the issue of nice text from horrible HTML emails, I found another textual web browser, like lynx(1), etc., but http://netrik.sourceforge.net/ uses colour in its --dump output. It doesn't list the URL destinations though, e.g. the noisy `[42]' that links prefixes to the

Re: [nmh-workers] localhost anomaly

2019-06-18 Thread Ralph Corderoy
> Ralph wrote: > > so you need a `post: -port 25' in your ~/.mh_profile. > > That should be `send: -port 25' !! Thanks David. You're right. I think I'm always led astray by being in post(8) by the time I read the option's description. :-) -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] localhost anomaly

2019-06-18 Thread Ralph Corderoy
Hi rfg, > even though this may turn out to be a "support" type question. Not a problem. https://lists.nongnu.org/mailman/listinfo/nmh-workers says All the chat amongst nmh users, new and old, happens here, as does discussion amongst the developers about the future direction of nmh. >

Re: [nmh-workers] Problems compiling on SPARC Sun Solaris 10 compile with ANSI C SUN compiler.

2019-06-13 Thread Ralph Corderoy
Hi Masud, > > grep -i bool config.h > /* Define to 1 if you have the header file. */ > #define HAVE_STDBOOL_H 1 ... > "/usr/include/curses.h", line 86: invalid type combination > cc: acomp failed for sbr/terminal.c From your first email: 85 #if !defined(__cplusplus) && !defined(_BOOL)

Re: [nmh-workers] Problems compiling on SPARC Sun Solaris 10 compile with ANSI C SUN compiler.

2019-06-13 Thread Ralph Corderoy
Hi Masud, > Wrt to is the stdbool being found - yes see yellow highlight below. ... > checking stdbool.h usability... yes > checking stdbool.h presence... yes > checking for stdbool.h... yes ... > config.status: creating config.h What's the output of `grep -i bool config.h'? Just to make sure

Re: [nmh-workers] Problems compiling on SPARC Sun Solaris 10 compile with ANSI C SUN compiler.

2019-06-13 Thread Ralph Corderoy
Hi, Masud wrote: > Undefined first referenced > symbol in file > memmem sbr/libmh.a(sbr_libmh_a-m_getfld.o) > stpcpy sbr/libmh.a(sbr_libmh_a-concat.o) > strnlen

Re: [nmh-workers] Superhuman MUA.

2019-06-13 Thread Ralph Corderoy
Hi chad, > FWIW, this (quietly add a small delay to send, and an undo button) > seems to be a common feature in big webmail/MS email systems these > days. As long as there's a means to override it for when I know others are waiting, e.g. I'm talking to them at the time, or to save them wasted

Re: [nmh-workers] Stupid 'pick' question...

2019-06-13 Thread Ralph Corderoy
Hi Bakul, > The reason being the body was MIME encoded because of UTF-8 even > though it is plain text. I think that's why David and others runs all their emails on delivery through mhfixmsg(1)'s `-decodetext'. > Content-Transfer-Encoding: base64 Which of us hasn't worked out the possible

[nmh-workers] OT: Poking SMTP: Swaks.

2019-06-11 Thread Ralph Corderoy
Hi, Given a few of us here probably has to prod and poke at SMTP servers and their ilk, I thought Swaks might be of interest. http://jetmore.org/john/code/swaks/ man page: http://jetmore.org/john/code/swaks/latest/doc/ref.txt -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] Superhuman MUA.

2019-06-11 Thread Ralph Corderoy
Hi Ken, > It implies you can "Undo Send" anything. That's adtistic licence. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] Superhuman MUA.

2019-06-10 Thread Ralph Corderoy
Hi Ken, > The web site sure does look great, and features rocket engines, > sparklers, and attractive people playing tennis. Which ... I guess is > related to email? I think we're meant to recognise ourselves in the photos and therefore realise it's the product for us. > Like "Undo Send" ...

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-10 Thread Ralph Corderoy
Hi Ken, > In the "old days", it was common for the mail spool to only be > writable by group 'mail' (or something similar) and if you did dot > locking you couldn't create a lock file in the spool directory unless > your mail program was setgid mail (you can see this code in the > original MH).

[nmh-workers] Superhuman MUA.

2019-06-10 Thread Ralph Corderoy
Hi, I heard of this Gmail-competitor MUA recently. https://superhuman.com/ Reading through its list of features, it seems quite easy to think of scripting some of them, e.g. delayed sending by refiling into a to-send folder that's posted in the background, or appending a future reminder to a

Re: [nmh-workers] Stupid 'pick' question...

2019-06-09 Thread Ralph Corderoy
Hi Valdis, > In a world of Microsoft Office attachments, is having -search go > through the body by default as well still a good idea? Maybe having a > separate -searchbody would be better? I think -search should be left alone, but there's previous discussion on this list about a -header and

Re: [nmh-workers] Stupid 'pick' question...

2019-06-09 Thread Ralph Corderoy
Hi Bakul, > So pick runs -search on header lines as well as the body a header > specific option is only run against headers. pick(1): This means that the pattern specified for a -search will be found everywhere in the message, including the header and the body, while the other pattern

Re: [nmh-workers] Stupid 'pick' question...

2019-06-09 Thread Ralph Corderoy
Hi kre, > > Which it what happens at the moment, so it wouldn't be backwards > > compatible. > > No, it wouldn't - but does anyone really think that matters? Only to the extent it's worthy of a line in the release notes. I send myself short emails with leading punctuation in the Subject field

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-09 Thread Ralph Corderoy
Hi Valdis, > At which point the other user can't use their preferred mail tools on > /var/spool/mail/otheruser, so if they aren't also nmh users they're in > trouble I'm surprised you think I'd allow a non-nmh-user user on this machine. -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-09 Thread Ralph Corderoy
Hi Bakul, > > Regardless of whether it's a good idea, since the kernel is using > > effective user and group IDs for testing permissions, if a user ID > > is used to determine what files to access then it should be the > > effective one rather than the real one. Do you agree? > > I haven't

Re: [nmh-workers] Stupid 'pick' question...

2019-06-09 Thread Ralph Corderoy
Hi Valdis, > > -search 'Subject[ \t]:[ \t]*\[PATCH [45]\.[0-9]' > > [~] grep ^Subject Mail/linux-kernel/321805 > Subject: Re: [PATCH 4.9 04/20] net: Fix for_each_netdev_feature on Big endian > [~] scan `pick +linux-kernel 321805 -search 'Subject: \[PATCH [45]\.[0-9]' > -and -from

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-08 Thread Ralph Corderoy
Hi Bakul, > Privilege escalation should be done externally. Regardless of whether it's a good idea, since the kernel is using effective user and group IDs for testing permissions, if a user ID is used to determine what files to access then it should be the effective one rather than the real one.

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-08 Thread Ralph Corderoy
Hi Bakul, > I can not think of one reason why inc shoud be set{g,u}id'ed. I often switch to another user to see if they've any new email they'd like to know about. All I really need for that is setuid inc that scans the From and Subject fields. And I think Ken's point was about all nmh, as was

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-08 Thread Ralph Corderoy
Hi Ken, > But even though the person who did this had su'd to root, some of > their user environment variables were inherited by their root shell > and then inherited by inetd That sounds like user error; they ran `su' rather than the more commonly wanted `su -'. Similarly today, `sudo -i'. --

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-08 Thread Ralph Corderoy
Hi Ken, > > I notice that a setuid inc(1) has various troubles due to the use of > > real user ID rather than effective. > > Like ... what? It's simple to copy inc and make it setuid to another user and then run it. $ ./inc

Re: [nmh-workers] Stupid 'pick' question...

2019-06-08 Thread Ralph Corderoy
Hi kre, > Maybe it would be possible to look for a leading ^ in the user's > pattern (for other than -search), and if found, remove it, and replace > the ".*" that's inserted into the RE with "[ \t]*" ? Sounds like a good idea. > Certainly no-one who uses a leading ^ is expecting it to attempt

Re: [nmh-workers] Flagging messages

2019-06-08 Thread Ralph Corderoy
Hi, Arthur wrote: > In the end, I’ve decided not to accomplish this through nmh but rather > use Diane Skoll’s remind program. I think it sums my needs better in > the long run. That's https://dianne.skoll.ca/projects/remind/ -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] Stupid 'pick' question...

2019-06-08 Thread Ralph Corderoy
Hi Valdis, > pick -from -subject '\[PATCH [45]\.[0-9]' ... > However, it *also* catches messages of the form 'Subject: Re: [PATCH > ' which is unacceptable for the use case in question. Bakul answered about the anchors. Another approach is to rule out replies. -sub foo -and -not -sub

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-04 Thread Ralph Corderoy
Hi Ken, > getusername() (the nmh function) is called by programs like slocal and > rcvtty, which may not have a controlling terminal and I am unclear > what LOGNAME would mean in their environment as well. True. cron(8) here sets $LOGNAME, but does .forward, etc? > I am thinking that falling

Re: [nmh-workers] nmh 1.7.1 compile errors

2019-06-03 Thread Ralph Corderoy
Hi Masud, > cc -DHAVE_CONFIG_H -I. -I./sbr > -DNMHBINDIR='"/export/home/edcs/nmh/bin"' > -DNMHLIBEXECDIR='"/export/home/edcs/nmh/libexec/nmh"' > -DNMHETCDIR='"/export/home/edcs/nmh/etc/nmh"' > -DNMHDOCDIR='"/export/home/edcs/nmh/share/doc/nmh"' > -DMAILSPOOL='"/var/mail"'

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-03 Thread Ralph Corderoy
Hi Bakul, > > Should we simplify the code to demand $LOGNAME exists and use that? > > You can use getlogin(3) or getlogin_r(3) as per ISO/IEC 9945-1:1996. That seems worse. Linux's getlogin(3) says in Description that $LOGNAME is often more useful, and its Bugs section is an amusing read.

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-03 Thread Ralph Corderoy
Hi Ken, > > /var/mail/$USER Location of the system mail drop. > > But we don't actually use $USER (we call getpwuid(getuid()) and use > that). And even then it's not that simple. > I personally interpreted the use of $USER as "the username goes here", > not "we use the value of the $USER

Re: [nmh-workers] I Could Have Sworn that the inc Command used to work.

2019-06-02 Thread Ralph Corderoy
Hi Bakul, > Looks like inc pays attention to $MAILDROP and if it is not set and > profile entry MailDrop is not set, it looks into /var/mail/$USER. That's pretty much right. > Not sure if it ever checks $MAIL or $MAILPATH. It doesn't, and it doesn't use $USER, or $LOGNAME, either. inc(1) says

Re: [nmh-workers] Flagging messages

2019-05-27 Thread Ralph Corderoy
Hi Valdis, > Note that '--component pattern' has 'component' bolded as if it is a > keyword rather than a user-supplied value. Yes, that's wrong. fmttest(1) too. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] mhl.format mystery

2019-05-26 Thread Ralph Corderoy
Hi Jude, > The following mhl.format file works fine for only message 31 and no > other messages downloaded. It is located in /home/jude/Mail and was > first copied from /etc/nmh in order to have a correct first version. > Once done I did two edits on /home/jude/Mail/mhl.format. I think we need

Re: [nmh-workers] Flagging messages

2019-05-26 Thread Ralph Corderoy
Hi aalinovi, > In mutt, new messages and messages that have been flagged are > indicated in the sidebar. You have seen scan(1) highlight the current message with a `+' after its number. That's done using the, somewhat unique, formatting language that tests each message to see if it's the

Re: [nmh-workers] Flagging messages

2019-05-26 Thread Ralph Corderoy
Hi Valdis, > Hmm.. 'anno +folder cur -component X-Reminder -text "Pay This Bill" > and then run scan `pick -component X-Reminder` anno does have a -component option, but pick doesn't. I think you mean scan `pick --x-reminder bill` with the double dash. The discrepancy is odd. It

Re: [nmh-workers] Flagging messages

2019-05-25 Thread Ralph Corderoy
Hi aalinovi, > Scenario: you receive an email from Geico informing you your car > insurance payment is due in 4 weeks. In mutt or Apple Mail you can > flag that message so you're reminded of it each time you log in. How does it remind you? A pop-up per message? Highlighting then when you

Re: [nmh-workers] real basic nmh question

2019-05-23 Thread Ralph Corderoy
Hi Jude, > I got getmail working when I found most of my braille notes on > .fetchmailrc were gone and decided to try a fetchmail competitor. I > found in getmail the mboxrd type could be used for the inbox then I > figured I could use nmh with this set up. That's similar to my configuration.

Re: [nmh-workers] real basic nmh question

2019-05-22 Thread Ralph Corderoy
Hi Jude, > What is a user's default nmh directory? See the output of `mhparam path'; probably ~/Mail. > My folder hierarchy is ~/Mail/inbox/new ~/Mail/inbox/cur ~/Mail/inbox/tmp. That sounds more like a Maildir arrangement of three directories, {new,cur,tmp}, for the delivery of mail to your

Re: [nmh-workers] #ifdef UK

2019-05-19 Thread Ralph Corderoy
Hi spaceman, > > as an arg to scan (either via -format or -form) whether numeric > > dates are printed as D/M (the sane way) or M/D (stupid). > > It might be pure opinion but I don't think M/D is "stupid" when put in > context for example: > > -MM-DDTHH:MM:SS > 2019-05-18T23:43:15 But M/D's

Re: [nmh-workers] #ifdef UK

2019-05-18 Thread Ralph Corderoy
Hi Ken, > Apologies to our friends across the pond, but I noticed the #ifdef UK > in scansbr.h today, and I couldn't help wonder if anyone still uses > this. This imperialist never has. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] Office 365, redux

2019-05-17 Thread Ralph Corderoy
Hi Ken, > If anyone is required to use Office 365 for their $DAYJOB but still > wish to use your favorite MUA, here's a quick recipe that worked for > me and might work for you. Is there a man page for interfacing nmh to foreign odd-ball systems? Should there be? Or somewhere else in the

Re: [nmh-workers] Change {encrypted} to %(encrypted) in mh-format

2019-05-17 Thread Ralph Corderoy
Hi Ken, I favour removing the test for %{encrypted} from the default formats, without deprecation for a release since it's trivial for a user to add back in, and only add %(encrypted) if and when it's got a useful definition. -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] Can't forward MIME-encoded message

2019-05-10 Thread Ralph Corderoy
Hi Valdis, > My under-caffeinated mind is whispering about a myth regarding ancient > software > on SunOS that stuck in things like 'Content-Type: uuencode' when using its > pre-MIME scheme for sending non-text data. https://www.mhonarc.org/archive/html/ietf-822/1994-12/msg00167.html makes that

Re: [nmh-workers] Can't forward MIME-encoded message

2019-05-10 Thread Ralph Corderoy
Hi Ken, > > I agree the earliest git commit checks both, but the RFC says C-T-E > > is optional. I think the only mandatory MIME header is the version > > so can't we ditch the other test? Otherwise it just leads to calls > > to extend the list. ... > I find it odd that it bails out on a

Re: [nmh-workers] Can't forward MIME-encoded message

2019-05-10 Thread Ralph Corderoy
Hi Ken, > - If it was run on a message with a CTE or Mime-Version header, it would > error out. ... > Why that specific behavior? No idea! But it was very deliberate. I agree the earliest git commit checks both, but the RFC says C-T-E is optional. I think the only mandatory MIME header is

Re: [nmh-workers] detecting enclosed msg as spam - unicode regex help needed, I think; spam unicode chars in header

2019-05-05 Thread Ralph Corderoy
Hi Valdis, > You're probably better served by installing SpamAssassin That was my thought; training it over time. http://ix.io/1HZ8 does mention `spamfilter01' in the headers, but those headers look odd so I'm not sure how close to Tom it is. Open parenthesis, closing bracket. Received:

[nmh-workers] Autocrypt.

2019-04-29 Thread Ralph Corderoy
Hi, I'll have time to reply to nmh emails in a few days, but meanwhile I thought I'd mention Autocrypt having spotted once again its huge header in emails I receive. https://en.wikipedia.org/wiki/Autocrypt Perhaps one for (Ken's) https://www.nongnu.org/nmh/rfc.html page, if it wasn't just RFCs

Re: [nmh-workers] [nmh-commits] [SCM] The nmh Mail Handling System branch, master, updated. 1.7-branchpoint-531-gef0725f

2019-04-24 Thread Ralph Corderoy
Hi, > commit 43d9833bf1dcf38c7892a23951bf1d968028a15e > Author: Ken Hornstein > Date: Wed Apr 24 10:25:18 2019 -0400 > > Removal of Content-MD5 support > > The generation and verification of Content-MD5 headers is no longer > done. FINALLY. Bah. -- Cheers, Ralph. --

Re: [nmh-workers] closefds() _before_ fork?

2019-04-24 Thread Ralph Corderoy
Hi Ken, > > > they called getdtablesize() on Linux, which it seems returns a > > > smaller number than getrlimit(). > > > > That's surprising. I thought getdtablesize() was effectively > > > > return getrlimit(RLIMIT_NOFILE, ) < 0 ? OPEN_MAX : ru.rlim_cur; > > Hey, I don't make the news, I

[nmh-workers] Old MHs.

2019-04-24 Thread Ralph Corderoy
Hi, When Googling today, I found http://web.mit.edu/source-8.1/third/mh/papers/mh4/MHCHANGES which looks to be the same as the nmh repository's nmh/docs/historical/mh-6.8.5/papers/mh4/MHCHANGES. I wondered if there's anything else squirrelled away inside mit.edu, but any attempt to edit the URL

Re: [nmh-workers] closefds() _before_ fork?

2019-04-23 Thread Ralph Corderoy
Hi Ken, > I realize that dup2() clears the FD_CLOEXEC flag on the new file > descriptor so the "normal" case of an opened file being dup2() down to > 0 would work correctly, but the wrinkle is that it does NOT if the old > and new file descriptor are the same. That is admittedly unlikely, > but

Re: [nmh-workers] closefds() _before_ fork?

2019-04-23 Thread Ralph Corderoy
Hi Ken, > they called getdtablesize() on Linux, which it seems returns a smaller > number than getrlimit(). That's surprising. I thought getdtablesize() was effectively return getrlimit(RLIMIT_NOFILE, ) < 0 ? OPEN_MAX : ru.rlim_cur; That seems to match /lib/libc.a here, if I squint a

Re: [nmh-workers] closefds() _before_ fork?

2019-04-23 Thread Ralph Corderoy
Hi Ken, > but ALSO uses dup2() to make an additional copy of the input file > descriptor to descriptor 3 (!). Does anyone know why? It looks like > it has always done this. It's not the only one, e.g. docs/historical/mh-6.8.5/uip/post.c has 2622 if (fd != 0) 2623

Re: [nmh-workers] closefds() _before_ fork?

2019-04-23 Thread Ralph Corderoy
Hi, David wrote: > Ken wrote: > > I suggest we simply remove closefds() completely. ... > Ralph's suggestion of looking for only open fds addresses the > suboptimality of closefds(), though only for systems that use /proc. That was just meant as a temporary debugging aid to see what was sneaking

Re: [nmh-workers] send fails

2019-04-23 Thread Ralph Corderoy
Hi David, > > > send: -port 2525 -alias /home/wilson/.mh_aliases -server mail.eskimo.com > > > > Yes, that would work, though only for you and not any other users. > > The port can't be set in mts.conf, so it wouldn't be straightforward > to support that for all users. No, agreed. But I snipped

Re: [nmh-workers] Handling Configuration-file Read Errors.

2019-04-23 Thread Ralph Corderoy
Hi Ken, > I don't believe mts.conf is technically required, but I hear you. > So you're fine with erroring out if opening MHMTSCONF fails for any > reason ... and for the default mts.conf file, would you rather error > out if errno != ENOENT, or if errno == EACCES, or some other > condition?

Re: [nmh-workers] closefds() _before_ fork?

2019-04-22 Thread Ralph Corderoy
Hi Ken, > Can anyone think of a reason that for this specific case closefds() > should NOT be moved from whatnowbr.c (and send.c) into sendsbr.c, and > just in the child process? IT does seem odd to have it in the parent rather than just the child. The only thing I can think of is if it's

Re: [nmh-workers] Reply to Ralph Corderoy

2019-04-22 Thread Ralph Corderoy
Hi Stewart, > I used dnf to install nmh-1.7.1-2.fc28.x86_64 from a repository. > So I guess the bug was in there too. From https://fedora.pkgs.org/28/fedora-x86_64/nmh-1.7.1-2.fc28.x86_64.rpm.html I got

Re: [nmh-workers] Reply to Ralph Corderoy

2019-04-22 Thread Ralph Corderoy
Hi Valdis, > > ISTM it's also a bug to ignore problems opening a file that exists, > > and to ignore a file given in an environment variable not existing. > > I agree on the first. The second probably need to be more nuanced, > and "a *specific* file given in the environment". Consider how

Re: [nmh-workers] Reply to Ralph Corderoy

2019-04-21 Thread Ralph Corderoy
Hi, I wrote: > Looks like a bug in nmh's Makefile; it produces mts.conf by > re-directing the output of sed, but a umask of 077 would leave the > file as 600. ISTM it's also a bug to ignore problems opening a file that exists, and to ignore a file given in an environment variable not existing.

Re: [nmh-workers] Reply to Ralph Corderoy

2019-04-21 Thread Ralph Corderoy
Hi Stewart, > /etc/nmh/mts.conf, owned by root, has mod 600. Valdis guessed correctly in his email to the list then! Looks like a bug in nmh's Makefile; it produces mts.conf by re-directing the output of sed, but a umask of 077 would leave the file as 600. > I am very grateful for your help

Re: [nmh-workers] send fails

2019-04-21 Thread Ralph Corderoy
Hi Stewart, > send: -port 2525 -alias /home/wilson/.mh_aliases -server mail.eskimo.com Yes, that would work, though only for you and not any other users. > You proposed that mts.conf was not being read. Could that still be > the case? Yes, and it would mean other mts.conf settings you've

Re: [nmh-workers] Reply to Ralph Corderoy

2019-04-21 Thread Ralph Corderoy
Hi Stewart, > I did your optioned send below, except I used -port 2525 and it went! ... > What now? send -snoop -mts smtp -server mail.eskimo.com -port 2525 > Trying to connect to "mail.eskimo.com" ... > Connecting to 204.122.16.4:2525... > <= 220 mail.eskimo.com ESMTP Postfix > <= 250-AUTH PLAIN

Re: [nmh-workers] Reply to Ralph Corderoy

2019-04-21 Thread Ralph Corderoy
Hi Stewart, > The previous nmh was 1.4 That's a big jump. If you haven't already seen it, then the list of per-release changes in NEWS could be useful. http://git.savannah.nongnu.org/cgit/nmh.git/tree/NEWS > I changed the port to 25 from 2525, but the connection there was also > refused. I

Re: [nmh-workers] send fails

2019-04-21 Thread Ralph Corderoy
Hi Stewart, > Would you kindly send it again if you can? ... > https://lists.nongnu.org/mailman/listinfo/nmh-workers There's a copy in the archive of mailing-list emails: http://lists.nongnu.org/archive/html/nmh-workers/2019-04/msg2.html -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] send fails

2019-04-21 Thread Ralph Corderoy
Hi Stewart, > This week I installed nmh 1.7.1. Do you know what version you were on before? Was it a 1.6? > Trying to connect to "localhost" ... > Connecting to ::1:2525... > Connection failed: Connection refused > Connecting to 127.0.0.1:2525...

Re: [nmh-workers] Handling empty components

2019-03-30 Thread Ralph Corderoy
Hi Bob, > For example, build_nmh is failing during the "configuring" step > because one of the checks, which builds a small program that includes > "gdbm-ndbm.h", fails because that include file is no longer provided > with the libgdbm-dev package (only "gdbm.h" is).

Re: [nmh-workers] Handling empty components

2019-03-21 Thread Ralph Corderoy
Hi Bob, > Is there a concise way to specify "if X is not present or is just > white space?" in one's replcomps? I'd look into applying function `trim' first; see mh-format(5). -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] mhshow: invalid BASE64 encoding in --

2019-03-17 Thread Ralph Corderoy
Hi, David wrote: > In other words, I'd like to see all of the content or an error > message. This is the juncture where I normally take https://tools.ietf.org/html/draft-thomson-postel-was-wrong-00#section-1 out for a trot. -- Cheers, Ralph. -- nmh-workers

Re: [nmh-workers] Construction of outgoing from line

2019-03-14 Thread Ralph Corderoy
Hi Kevin, > Sorry for the top post (using gmail atm) It's been years for me. Doesn't it let one edit the quoted email? :-) > Re: mailx, it passes the message to postfix which then takes care of > the outgoing email form. And you don't wish nmh to pass the email to Postfix to get the same

Re: [nmh-workers] how might I make sequence 'bar' where 'bar' is all but msgs in seq 'foo'?

2019-03-13 Thread Ralph Corderoy
Hi Tom, kre's correct. Another way is pick -seq bar all mark -s bar -d foo That's an approach that extends to more complex set operations. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] send -split not working

2019-02-20 Thread Ralph Corderoy
Hi lambda, > post: message has no From: header ... > Does anyone know how to send partial messages? It seems like a really > cool feature but I cannot get it to work. I think you've found a bug in uip/sendsbr.c's splitmsg(), probably due to some re-work in a nearby area that didn't take it into

Re: [nmh-workers] nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe

2019-02-15 Thread Ralph Corderoy
Hi az, > > I'd be tempted to make it an if-then with no else clause by hoisting > > the "BCC:" prefix and "\n" suffix outside of the if-then. > > hmm. i see your point, but don't entirely agree. my aim here was to > contain all the related logic within the smallest possible/sensible > horizon. >

Re: [nmh-workers] nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe

2019-02-15 Thread Ralph Corderoy
Hi Valdis, > Am I the only guy who's been bitten by documentation that has single > and double quotes that look cut-n-paste-able but actually aren't? This is a combination of faulty man page source, a confusing area of troff implementation evolution over its many decades, and some faults being

Re: [nmh-workers] nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe

2019-02-15 Thread Ralph Corderoy
Hi kre, Sending to you directly so you see a version that Mailman doesn't touch. > | >The «"» around `Blind-Carbon-Copy' > > I am leaving that there just so you can see what happens... What I > see when composing this is (ignoring my "|" quoting marker, ">The " > (which I assume is fine

Re: [nmh-workers] nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe

2019-02-15 Thread Ralph Corderoy
Hi Ken, > > The «"» around `Blind-Carbon-Copy' should be \(lq and \(rq > > So, in a mostly unrelated note ... I couldn't help noticing that Ralph > used guillemets («») in one of his messages on this thread (way to > push non-US-ASCII characters, Ralph!) I find they're useful because they're

Re: [nmh-workers] nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe

2019-02-14 Thread Ralph Corderoy
Hi > > > > The «"» around `Blind-Carbon-Copy' should be \(lq and \(rq, or > > > > the equivalent strings for consistency with the style used at > > > > start of the paragraph. > ... > > > Am I the only guy who's been bitten by documentation that has > > > single and double quotes that look

Re: [nmh-workers] nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe

2019-02-14 Thread Ralph Corderoy
Hi az, Thanks for the patch, Ken knows the topic better than me, but the man page caught my eye. > If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for > delivery, and the \*(lqBcc:\*(rq field will be removed from the message > -sent to sighted recipients. The blind

Re: [nmh-workers] Gmail Bounces. (Was: nmh 1.7.1: both bcc and dcc broken for mts sendmail/pipe)

2019-02-14 Thread Ralph Corderoy
Hi, Two of az's recent emails to the list have been bounced by Gmail as spam, with no further detail why given. Both bounces were for the same gmail.com subscriber. I'm assuming the other 17 gmail.com subscribers received the email OK otherwise Gmail would have sent separate bounces? Perhaps

Re: [nmh-workers] ARC: Forwarding with DMARC, DKIM, and SPF.

2019-02-05 Thread Ralph Corderoy
Hi Ken, Happy New Year! :-) > And thinking about it ... I don't think the normal usage of dist(1) > SHOULD cause any problems. With regards to SPF, since it uses the > MAIL FROM header that should be fine, since your MAIL FROM should be > set properly to the identity of the dist(1)er. Since

[nmh-workers] ARC: Forwarding with DMARC, DKIM, and SPF.

2019-02-05 Thread Ralph Corderoy
Hi, Whilst investigating a friend's question about ~/.forward in the age of DMARC, etc., I came across Authenticated Received Chain for email that seems to be heading to an RFC. ARC is intended to be used by Internet Mail Handlers who forward or resend messages, with or without

Re: [nmh-workers] The State of exmh.

2018-11-08 Thread Ralph Corderoy
Hi, > Thanks, I now have > > $ b2sum exmh-2.9.0.tar.gz | cut -c-42 > a097b2e5c5cd44dd6d84e239bf6e674584e9eb4952 Reading through the notes, it appears metamail is pretty vital for display of MIME messages. (In particular, I was interested to see how exmh handled text/html.) metamail

Re: [nmh-workers] The State of exmh.

2018-11-08 Thread Ralph Corderoy
Hi Ken, > Even being on the list ... it's a pain. Because to access the list > archives I have to remember my "list password" Because there's so little value in the Mailman subscription password, I let Firefox remember them. > I mean, I don't get it ... why not make them public? I'm on a

Re: [nmh-workers] The State of exmh.

2018-11-07 Thread Ralph Corderoy
Hi valdis, > I'm tagging the current git tree as 2.9.0 and pushing out the tarballs Thanks, I now have $ b2sum exmh-2.9.0.tar.gz | cut -c-42 a097b2e5c5cd44dd6d84e239bf6e674584e9eb4952 -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy -- nmh-workers

<    1   2   3   4   5   6   7   8   9   10   >