Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 25 August 2017 at 19:15, Ken Hornstein wrote: > > + localuser:kevinc being removed from access control list > > > >That's coming from my 'xhost -SI:localuser:kevinc' setting which > >I use exclusively to keep exmh happy. Ironic. > > I think Ralph has hit that one the head.

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

> + localuser:kevinc being removed from access control list I dug into this a bit more. What is your SHELL? Specifically, what is the "SHELL" environment variable set to? Boy, I just took a look at whatnowsbr.c, specifically how "cd", "pwd", and "ls" work. Talk about knowing how the sausage

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On Fri, Aug 25, 2017 at 4:53 AM, Ralph Corderoy wrote: > Hi everyone, > > > David's build_nmh script aims to make that first part easy. I've just > tried it. > > wget -nv > https://download.savannah.nongnu.org/releases/nmh/nmh-1.7-RC3.tar.gz > gzip -dc

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Kevin wrote: > ./test/format/test-myhost: local hostname test expected: > 'drums.cosgroves.us' > but instead got: > 'cosgroves.us' > FAIL: test/format/test-myhost That might be an /etc/hosts issue. And that could explain the test-mymbox failure, too. test/getcanon, which uses

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 24 August 2017 at 21:32, Ken Hornstein wrote: > I am feeling reasonably confident about the quality of nmh 1.7 release > candidate 3. To that end, I sure would appreciate it if you had not had > a chance yet to test any nmh 1.7 release candidates, that you give RC3 a > try.

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Hi Kevin, Thanks for trying RC3. > In some of the failures are lines like these in the diff's > > + localuser:kevinc being removed from access control list > > That's coming from my 'xhost -SI:localuser:kevinc' setting which I use > exclusively to keep exmh happy. Ironic. Yes, but where is

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

> + localuser:kevinc being removed from access control list > >That's coming from my 'xhost -SI:localuser:kevinc' setting which >I use exclusively to keep exmh happy. Ironic. I think Ralph has hit that one the head. >Here's what failed. >

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

tar -zxvf nmh-1.7-RC3.tar.gz cd nmh-1.7-RC3 ./configure make make check after resolving the send: -port 25 -notls issue in my .mh_profile I am here to report the following: Binary files /home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Jerry wrote: > Binary files /home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and > /home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected differ Can you look at those files and see how they differ? David ___ Nmh-workers mailing list

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>tar -zxvf nmh-1.7-RC3.tar.gz >cd nmh-1.7-RC3 >./configure >make >make check > >after resolving the send: -port 25 -notls issue in my .mh_profile I am >here to report the following: Silly question time ... why is everyone adding -notls? That's the default (and that hasn't changed). If our

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 25 August 2017 at 19:24, David Levine wrote: > Kevin wrote: > > > ./test/format/test-myhost: local hostname test expected: > > 'drums.cosgroves.us' > > but instead got: > > 'cosgroves.us' > > FAIL: test/format/test-myhost > > That might be an /etc/hosts

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Kevin wrote: > In /etc/postfix/main.cf > > mydomain = cosgroves.us > myorigin = $mydomain nmh won't see that. Do you set localname in mts.conf or your profile? David ___ Nmh-workers mailing list Nmh-workers@nongnu.org

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Ken wrote: > > ./test/mhfixmsg/test-mhfixmsg: test failed, outputs are in > > /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/Mail/inbox/31 and > > /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/test-mhfixmsg31454.actual. > > first named test failure: pass through message

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Hello Ken, Ken Hornstein writes: > [...] > I am feeling reasonably confident about the quality of nmh 1.7 release > candidate 3. To that end, I sure would appreciate it if you had not had > a chance yet to test any nmh 1.7 release candidates, that you give RC3 a > try. If there are no issues

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

e. Saw it in another post. When using previous versions of nmh (1.6 and prior) I never had to have the send: line in my .mh_profile. >>Binary files /home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and >>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected differ > > That's ...

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>e. Hm ... was this supposed to be there? I only ask because if it wasn't and you're using 1.7, we should fix that. >Saw it in another post. When using previous versions of nmh (1.6 and >prior) I never had to have the send: line in my .mh_profile. Sigh. I guess I should have asked Anthony

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 25 August 2017 at 23:34, Ken Hornstein wrote: > >Thanks for mentioning mts.conf I find this > > > >localname: cosgroves.us > > > >There. Maybe redundant with my main.cf from postfix? > > Well, probably not since that affects what nmh thinks as the local name > which

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>Now I get only these errors, only one of which is free of the xhost >issue. > >FAIL: test/mhfixmsg/test-mhfixmsg The others are likely due to a xhost in your .cshrc/.tcshrc, so I think we can ignore them for now. This one, however, does look legitimate. Is it possible mhfixmsg is dumping core?

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On Fri, 25 Aug 2017 19:35:38 -0400, Ken Hornstein writes: >>tar -zxvf nmh-1.7-RC3.tar.gz >>cd nmh-1.7-RC3 >>./configure >>make i'm trying to test a build from git, but all branches that i looked at seem to be missing sbr/sigmsg.awk, without which sbr/sigmsg.h cannot be built. regards az --

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Thank you for reminding me I had no trouble installing it on OpenBSD; I updated the DISTNAME in the port, then I ran make makesum, make plist, and make install. I have found some things would be good to change in the port, but I have not been in the mood to edit it. The only issue so far for me

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 25 August 2017 at 23:42, Ralph Corderoy wrote: > Hi Kevin, > > Thanks for trying RC3. > > > In some of the failures are lines like these in the diff's > > > > + localuser:kevinc being removed from access control list > > > > That's coming from my 'xhost

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On Fri, 25 Aug 2017 21:26:55 -0400, Ken Hornstein writes: >We got rid of sbr/sigmsg.awk when we got rid of the code that used >sbr/sigmsg.h; I think you're getting bitten by stale dependencies. Try *lightbulb*. i had forgotten to autoreconf, so makefile.in had the stale stuff in it... sorry for

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>On Fri, 25 Aug 2017 21:26:55 -0400, Ken Hornstein writes: >>We got rid of sbr/sigmsg.awk when we got rid of the code that used >>sbr/sigmsg.h; I think you're getting bitten by stale dependencies. Try > >*lightbulb*. i had forgotten to autoreconf, so makefile.in had >the stale stuff in it...

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>Thanks for mentioning mts.conf I find this > >localname: cosgroves.us > >There. Maybe redundant with my main.cf from postfix? Well, probably not since that affects what nmh thinks as the local name which affects a bunch of things (the postfix configuration may be redundant). But in

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>The only issue so far for me is that some files are different places >than they are in version 1.6. For example, slocal moved from >libexec/slocal to libexec/nmh/slocal. This is already noted in the >ChangeLog, but I think it would be good to note it somewhere more >prominent, such as the INSTALL

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 26 August 2017 at 1:11, Ken Hornstein wrote: > >Now I get only these errors, only one of which is free of the xhost > >issue. > > > >FAIL: test/mhfixmsg/test-mhfixmsg > > The others are likely due to a xhost in your .cshrc/.tcshrc, so I think > we can ignore them for now.

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>i'm trying to test a build from git, but all branches that i looked at >seem to be missing sbr/sigmsg.awk, without which sbr/sigmsg.h >cannot be built. We got rid of sbr/sigmsg.awk when we got rid of the code that used sbr/sigmsg.h; I think you're getting bitten by stale dependencies. Try "make

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

On 25 August 2017 at 20:34, Ken Hornstein wrote: > > + localuser:kevinc being removed from access control list > > I dug into this a bit more. What is your SHELL? Specifically, what > is the "SHELL" environment variable set to? > > Boy, I just took a look at whatnowsbr.c,

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Hi everyone, Ken wrote: > I am feeling reasonably confident about the quality of nmh 1.7 release > candidate 3. I suspect Ken's waters have it right. There's two things you can do to help. Build nmh on the varying systems you have, even if you only normally use it on your main one, feeding us

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Ken Hornstein writes: >Everyone, > >I am feeling reasonably confident about the quality of nmh 1.7 release >candidate 3. To that end, I sure would appreciate it if you had not had >a chance yet to test any nmh 1.7 release candidates, that you give RC3 a >try. If there are no

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Hi Anthony, > > It looks like you got bit by this change in 1.7, Anthony: > > > > - post now defaults to port 587 on 'smtp' message submission. > > Thanks. Since the relay only accepts connections from localhost, I was > okay with adding "send: -port 25 -notls" In case, like me, you wondered why

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Anthony wrote: > Thanks. Since the relay only accepts connections from localhost, I was > okay with adding "send: -port 25 -notls" and "post: -port 25 -notls" to > my profile Note that post doesn't read the profile, so the line you added for it doesn't do anything useful. David

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Hi, On Thu, Aug 24, 2017 at 7:32 PM, Ken Hornstein wrote: > Everyone, > > I am feeling reasonably confident about the quality of nmh 1.7 release > candidate 3. To that end, I sure would appreciate it if you had not had > a chance yet to test any nmh 1.7 release candidates, that

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

Ken wrote: > It looks to me like you have nmh configured to connect to a SMTP server > running on port 587 on localhost, and there isn't one. It looks like you got bit by this change in 1.7, Anthony: - post now defaults to port 587 on 'smtp' message submission. The -port switch to send(1),

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

David Levine writes: > Ken wrote: > > > It looks to me like you have nmh configured to connect to a SMTP server > > running on port 587 on localhost, and there isn't one. > > It looks like you got bit by this change in 1.7, Anthony: > > - post now defaults to port 587 on 'smtp' message submission.

Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

>$ comp >What now? s -snoop >Trying to connect to "localhost" ... >Connecting to 127.0.0.1:587... >Connection failed: Connection refused It looks to me like you have nmh configured to connect to a SMTP server running on port 587 on localhost, and there isn't one. >I run OpenSMTPD as a relay to