Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Hi Ken, > and the first release candidate is now available! Well done. > You can download it here: > > http://download-mirror.savannah.gnu.org/releases/nmh/nmh-1.7-RC1.tar.gz I used https and it worked fine. Can we switch to that from now on; those that can't handle TLS for some odd

[Nmh-workers] _GNU_SOURCE Comes and Goes.

Hi, I've seen this on and off and can now describe when it happens. I normally run ./configure in a git checkout of master. #! /bin/sh cc='ccache cc' # -pg opt=-O3 bs= #-DBUFSIZ=225 tls=yes oauth=yes readline=yes rm -f config.cache ./configure \

Re: [Nmh-workers] _GNU_SOURCE Comes and Goes.

>So, something about flipping back and forth with checkout triggers make >to configure, and that configure doesn't spot the need for _GNU_SOURCE. Looks like the magic is in m4/cppflags.m4. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Congratulations and many thanks to you and all the others who made this possible. Norman Shapiro ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

Norm wrote: > scan applied to an Email like the attached dumps core. I will send more > particulars, on request. Doesn't dump core for me, and valgrind doesn't notice anything unusual. I also tried with your .mh_profile that you posted 16 Nov 2016, with no problems. If you have updated it

Re: [Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

David Levine writes: >Norm wrote: > >> scan applied to an Email like the attached dumps core. I will send more >> particulars, on request. > >Doesn't dump core for me, and valgrind doesn't notice anything unusual. > >I also tried with your .mh_profile that you posted 16 Nov

Re: [Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

>Does the following command produce readable output, or a complaint? > >$ printf %s >8J+VtlN1buKAmXMgb3V0LCBzYXZpbmdzIE9O4oCUc2hvcCBtYWpvciBhcHBsaWFuY2UgZGVhbHMgbm93 > | base64 -d | iconv -f utf-8 For me, that works fine. Since I can reproduce it I'll gladly dig into it, but not for a week or

Re: [Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

Norm wrote: > % locale > LANG=en_US.utf8 So is mine. Does the following command produce readable output, or a complaint? $ printf %s 8J+VtlN1buKAmXMgb3V0LCBzYXZpbmdzIE9O4oCUc2hvcCBtYWpvciBhcHBsaWFuY2UgZGVhbHMgbm93 | base64 -d | iconv -f utf-8 David

[Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

scan applied to an Email like the attached dumps core. I will send more particulars, on request. Norman Shapiro --- Begin Message --- View as a Web page:

[Nmh-workers] Better way to write a script

For nmh 1.7, I just had to modify a one line script from scan -form /usr/local/nmh/etc/scan.time "$@" to scan -form /usr/local/nmh/etc/nmh/scan.time "$@" What would have been a better way to do that? Norman Shapiro ___ Nmh-workers mailing

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Ken Hornstein writes: > >I am pleased to announce that after three years we are finally starting >the release cycle for nmh 1.7 and the first release candidate is now >available! You can download it here: I am running Red Hat Enterprise Linux Workstation release 6.9. After a

Re: [Nmh-workers] packf ..map files

Conrad wrote: > packf leaves "..map" files lying around my mail directory; this > is documented in the man page as a "binary index". Not after this commit: commit e6c917710e4318949cb4174cabca51a8d1822dbd Author: Ralph Corderoy Date: Thu May 25 13:53:27 2017

Re: [Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

Hi Ken, > Ooof, I get: Like David, I don't. The Subject is two lots of base64 that I think decode to f0 9f 95 b6 53 75 6e e2 80 99 73 20 6f 75 74 2c |Sun...s out,| 0010 20 73 61 76 69 6e 67 73 20 4f 4e e2 80 94 73 68 | savings ON...sh| 0020 6f 70 20 6d 61 6a 6f 72

Re: [Nmh-workers] packf ..map files

Hi Conrad, > packf leaves "..map" files lying around my mail directory; this > is documented in the man page as a "binary index". Is there a point to > this file? Better documented elsewhere? Support was deleted in

Re: [Nmh-workers] Better way to write a script

Ken Hornstein writes: >>For nmh 1.7, >>I just had to modify a one line script from >> >>scan -form /usr/local/nmh/etc/scan.time "$@" >> >>to >> >>scan -form /usr/local/nmh/etc/nmh/scan.time "$@" >> >>What would have been a better way to do that? > >I think if you just did -form

[Nmh-workers] packf ..map files

packf leaves "..map" files lying around my mail directory; this is documented in the man page as a "binary index". Is there a point to this file? Better documented elsewhere? Conrad ___ Nmh-workers mailing list Nmh-workers@nongnu.org

Re: [Nmh-workers] nmh-1.7-RC1: scan with complex subjects dumps core

>scan applied to an Email like the attached dumps core. I will send more >particulars, on request. Ooof, I get: Assertion failed: (w >= 0), function cpstripped, file ../nmh/sbr/fmt_scan.c, line 291. Abort (core dumped) Okay! That will get worked on! --Ken

Re: [Nmh-workers] Better way to write a script

>For nmh 1.7, >I just had to modify a one line script from > >scan -form /usr/local/nmh/etc/scan.time "$@" > >to > >scan -form /usr/local/nmh/etc/nmh/scan.time "$@" > >What would have been a better way to do that? I think if you just did -form scan.time it will look in the "etc" directory,

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Hi Ken, > I guess I was thinking if the concern is the distribution has been > compromised by attackers they could produce a bogus hash file, but not > a GPG signature (at least hopefully not one signed by me). True, but some won't bother with checking a GPG signature, is it `gpg --verify

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

>True, but some won't bother with checking a GPG signature, is it `gpg >--verify foo.sig foo'?, but will run sha1sum(1) or similar, so the more >the merrier. And it's more being able to check this file is complete >and correct, especially if I've dredged it up some years later and want >to check

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Hi Ken, > Ah, I remember why I use GPG; that's a savannah requirement that they > put in place after a break-in. I think, when I looked at it, there > wasn't an obvious cross-platform checksum program. No, they've all slightly different names, but produce the same digest. > To me, that's one

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

>SHA-1 and SHA-256 might be what folks are more used to checking against. >The more encrypted traffic the better, was my thinking. I guess I was thinking if the concern is the distribution has been compromised by attackers they could produce a bogus hash file, but not a GPG signature (at least

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

>I used https and it worked fine. Can we switch to that from now on; >those that can't handle TLS for some odd reason will know to knock it >off. Fair enough; the links to the download area are all http, and the release DOES have a GPG signature (which I suppose we don't advertise), so I didn't

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Hello Ken, Ken Hornstein writes: > [...] > I am pleased to announce that after three years we are finally starting > the release cycle for nmh 1.7 and the first release candidate is now > available! You can download it here: > >

Re: [Nmh-workers] The first release candidate of nmh 1.7 is now available!

Hi Ken, > > I used https and it worked fine. > > Fair enough; the links to the download area are all http, and the > release DOES have a GPG signature (which I suppose we don't > advertise), so I didn't think about it. SHA-1 and SHA-256 might be what folks are more used to checking against. The

[Nmh-workers] mhfixmsg(1) Shrinking Images.

Hi, Corporations are increasing slapping needless, bloated, branding images onto their emails, ones I want to keep. I've a crude `shrinkimg' script that replaces the image's data with a tiny one whilst keeping the type, e.g. PNG, so any internal references to it are still valid. I was thinking