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

[David Levine]

Ken wrote:

> If it is fixed in newer versions of file and is only triggered by a small
> subset of inputs, I am fine with leaving it.

I don't know if the older version supports ~/.magic.mgc or ~/.magic, but if
it does, maybe that could be used to work around the problem.

David

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[valdis . kletnieks]

On Fri, 25 Aug 2017 15:28:37 -0700, Kevin Cosgrove said:

> That's coming from my 'xhost -SI:localuser:kevinc' setting which
> I use exclusively to keep exmh happy.  Ironic.

Weird.  I've had that commented out in my .xsession for quite
some time.  I'm using exmh to reply, and:

0 [/usr/share/doc/tk] xhost
access control enabled, only authorized clients can connect
SI:localuser:valdis
0 [/usr/share/doc/tk] 

(Digging into exmh source)

Looks like that isn't needed if you have 'Separate background process'
set to "off" in the "Background processing" section of "Exmh Preferences".



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>Ken, I guess pre-1.7 nmh's are bust in the same manner on jerry's
>system, so 1.7 is no worse?  Do we fudge around `binary'?

Sigh.  I am gathering it is short inputs that cause the problem.  I am
thinking maybe we should just do as David suggested and leave it?  If
it is fixed in newer versions of file and is only triggered by a small
subset of inputs, I am fine with leaving it.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[heymanj]

On 26 August 2017 at 12:36, David Levine wrote:

> Ken wrote:
>
>> What do people think we should do about this?  We could make
>> Autoconf reject this file command if it returns something other than
>> "application/octet-stream" for the "nulls" file.
>
> That would be fine.  Or, just leave it.  Based on Ralph's research,
> it looks like it's been fixed.

Apparently my Mageia file command issue has existed for a long time.
I just rebuilt 1.6 and ran 'make check' - which I didn't know was
available, and it also failed for the same reason on the same test.

I don't often use the command line capabilities of nmh any longer (have
been using Sylpheed Mail Client), so obviously the problem isn't one
I came across.  I wouldn't be too concerned about it - other than to
mention it in the TODOs.  Don't stop 1.7 release on my behalf.

jerry
 // Jerry Heyman   | If you preach hatred and intolerance
//  Amigan Forever :-) | towards others, don't then play the
\\ //   heymanj at acm dot org | victim if the others react badly to you
 \X/http://www.hobbeshollow.com| -- JMH

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

Ken wrote:

> What do people think we should do about this?  We could make
> Autoconf reject this file command if it returns something other than
> "application/octet-stream" for the "nulls" file.

That would be fine.  Or, just leave it.  Based on Ralph's research,
it looks like it's been fixed.

David

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

> Here is the information on the file command:
>
> $ file --version
> file-5.16
> magic file from /usr/share/misc/magic
> $ rpm -qf /usr/bin/file
> file-5.16-1.10.mga4

Thanks, jerry.  The commit comments on https://github.com/file/file are
poor, but

git log -p FILE5_15..HEAD src/funcs.c

certainly shows changes that could be turning `binary' into
`application/octet-stream'.

commit 5d2da614ae412d9a9016629b39d00d09e3edc297
PR/328: Shane Carr: fix echo -ne "\012\013\014" | file -i -
which printed "binary" instead of "application/octet-stream"

commit bca3d66faad9a63e9c13d86541d0736d7ca8fb36
PR/294: Fix file [--special-files]|[--mime-encoding] 
|

Ken, I guess pre-1.7 nmh's are bust in the same manner on jerry's
system, so 1.7 is no worse?  Do we fudge around `binary'?

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>[jerry@unix nmh-1.7-RC3]$ file --brief --dereference --mime-type 
>test/mhbuild/nulls
>binary

Well, that would do it.  Sigh.  It might be interesting to see what the
man pages says for that version of file.  But FWIW, on CentOS 7 I have
"file 5.11" and it works just fine.  I guess these are all based on:

http://www.darwinsys.com/file/

What do people think we should do about this?  We could make
Autoconf reject this file command if it returns something other than
"application/octet-stream" for the "nulls" file.  Open to suggestions here.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

On 26 August 2017 at 11:28, Ralph Corderoy  wrote:

> Hi Kevin,
> 
> > - To: recipi...@example.com
> > - From: sen...@example.com
> > - Subject: mhfixmsg pass through on parse error
> > - MIME-Version: 1.0
> > - Content-Type: multipart/mixed; boundary="- =_aa0"
> > - 
> > - --- =_aa0
> > - Content-Type: text/plain; charset="iso-8859-1
> > - Content-Disposition: attachment; filename="test1.txt"
> > - Content-Transfer-Encoding: quoted-printable
> > - 
> > - This is the=
> > -  text/plain part.
> > - 
> > - --- =_aa0--
> ...
> > ./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-mhfixmsg32378.actual.
> > first named test failure: pass through message with relative folder
> > path with parse error
> > FAIL: test/mhfixmsg/test-mhfixmsg
> 
> Can you arrange to do a similar test but with strace?  Extract that
> 15-line email above into your current nmh folder.
> 
> sed '1,/unable to parse message 31/d' test/mhfixmsg/test-mhfixmsg |
> sed -n '1,/^cat/d; /^EOF$/q; p' >`mhpath new`
> 
> Running the local mhfixmsg that the test script uses should produce an
> empty output file based on how the test failed.
> 
> uip/mhfixmsg last -outfile /tmp/out   # Is /tmp/out zero bytes long?
> 
> If so, re-run, but under strace(1).
> 
> strace -o /tmp/st -e desc uip/mhfixmsg last -outfile /tmp/out
> 
> And send us /tmp/st.  You might want to peruse for secrets first.


Yes, I'll have a look at that.  But, I'm booked now until Wednesday.

--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[heymanj]

On 26 August 2017 at 14:38, Ralph Corderoy wrote:

> Hi jerry,
>
>> $ file --brief --dereference --mime-type test/mhbuild/nulls
>> binary
>
> Could you tell us about that file(1).  I found a site for Mageia
> packages, but it didn't have one called `file' so I wasn't sure what
> package contained the command, and where it got the source from, what
> version, etc.
>
> Here, with Arch Linux's file 5.31-1 package, I get
>
> $ file --brief --dereference --mime-type test/mhbuild/nulls
> application/octet-stream
> $ file --version
> file-5.31
> magic file from /usr/share/file/misc/magic
> $

Ralph,

The version of Mageia I'm running is back level.  It went out of support
over a year ago.  I generall upgrade to their even releases (once every
two years, rather than annually).

Here is the information on the file command:

[jerry@unix nmh-1.7-RC3]$ file --version
file-5.16
magic file from /usr/share/misc/magic
[jerry@unix nmh-1.7-RC3]$ rpm -qf /usr/bin/file
file-5.16-1.10.mga4

jerry
 // Jerry Heyman   | If you preach hatred and intolerance
//  Amigan Forever :-) | towards others, don't then play the
\\ //   heymanj at acm dot org | victim if the others react badly to you
 \X/http://www.hobbeshollow.com| -- JMH

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

Hi jerry,

> $ file --brief --dereference --mime-type test/mhbuild/nulls
> binary

Could you tell us about that file(1).  I found a site for Mageia
packages, but it didn't have one called `file' so I wasn't sure what
package contained the command, and where it got the source from, what
version, etc.

Here, with Arch Linux's file 5.31-1 package, I get

$ file --brief --dereference --mime-type test/mhbuild/nulls
application/octet-stream
$ file --version
file-5.31
magic file from /usr/share/file/misc/magic
$

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Thomas Levine]

Hah

Since I didn't see that, then I doubt that further usability design on
this topic could have helped much. What's more, even without a note,
I eventually would have found the NEWS file. So I think it's fine as-is.

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

Hi Kevin,

> - To: recipi...@example.com
> - From: sen...@example.com
> - Subject: mhfixmsg pass through on parse error
> - MIME-Version: 1.0
> - Content-Type: multipart/mixed; boundary="- =_aa0"
> - 
> - --- =_aa0
> - Content-Type: text/plain; charset="iso-8859-1
> - Content-Disposition: attachment; filename="test1.txt"
> - Content-Transfer-Encoding: quoted-printable
> - 
> - This is the=
> -  text/plain part.
> - 
> - --- =_aa0--
...
> ./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-mhfixmsg32378.actual.
> first named test failure: pass through message with relative folder
> path with parse error
> FAIL: test/mhfixmsg/test-mhfixmsg

Can you arrange to do a similar test but with strace?  Extract that
15-line email above into your current nmh folder.

sed '1,/unable to parse message 31/d' test/mhfixmsg/test-mhfixmsg |
sed -n '1,/^cat/d; /^EOF$/q; p' >`mhpath new`

Running the local mhfixmsg that the test script uses should produce an
empty output file based on how the test failed.

uip/mhfixmsg last -outfile /tmp/out   # Is /tmp/out zero bytes long?

If so, re-run, but under strace(1).

strace -o /tmp/st -e desc uip/mhfixmsg last -outfile /tmp/out

And send us /tmp/st.  You might want to peruse for secrets first.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

Hi David,

Ken wrote:
> The others are likely due to a xhost in your .cshrc/.tcshrc, so I
> think we can ignore them for now.

How about a test that's run at the start of all the test, i.e. before
ali(1)'s, that checks «$SHELL -c 'exit 42'» is silent and sets $? to 42?
If it's not silent then the error message could explain a bit to the
user what's wrong, rather than just the normal diff output.  Ditto if
`$? -ne 42'.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

Hi Thomas,

> Oh, oops, I clearly didn't look there. How about mentioning in the
> welcome that differences from version 1.6 are noted in
> "$PREFIX/share/doc/nmh/NEWS"

I think that already happens.

$ inc -version
inc -- nmh-1.7-RC3 1.7-RC3-0-g106e6652 built 2017-08-23 19:31:10 + on 
orac
$ sed -i /^Version:/d ~/mail/context
$ inc -version

Welcome to nmh version 1.7-RC3

 →  See the release notes in /usr/share/doc/nmh/NEWS

Send bug reports, questions, suggestions, and patches to
nmh-workers@nongnu.org.  That mailing list is relatively quiet, so user
questions are encouraged.  Users are also encouraged to subscribe, and
view the archives, at https://lists.gnu.org/mailman/listinfo/nmh-workers

This message will not be repeated until nmh is next updated.


Press enter to continue: 

inc -- nmh-1.7-RC3 1.7-RC3-0-g106e6652 built 2017-08-23 19:31:10 + on 
orac
$ 

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Leonardo Taccari]

Hello Thomas,

Thomas Levine writes:
> Oh, oops, I clearly didn't look there. How about mentioning in the
> welcome that differences from version 1.6 are noted in
> "$PREFIX/share/doc/nmh/NEWS", or just "/usr/local/share/doc/nmh/NEWS"?
> I am happy to contribute a patch that renders the former location.

If I'm not missing something this is already done, e.g.:

 % $EDITOR `mhpath +`/`mhparam context`
 [... change the `Version:' to something older, e.g. just an
  s/RC3/RC2/ will be enough if you're running 1.7-RC3 ...]
 % new
 
 Welcome to nmh version 1.7-RC3
 
 See the release notes in /usr/pkg/share/doc/nmh/NEWS

 [...]
 Press enter to continue:

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Thomas Levine]

Oh, oops, I clearly didn't look there. How about mentioning in the
welcome that differences from version 1.6 are noted in
"$PREFIX/share/doc/nmh/NEWS", or just "/usr/local/share/doc/nmh/NEWS"?
I am happy to contribute a patch that renders the former location.

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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.  This one, however, does look legitimate.
> Is it possible mhfixmsg is dumping core?  Is there a core file sitting
> around anywhere?  (it may get cleaned up post-test).

No core file, nor reference to a core file in the 'make check' log 
file.


--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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?  Is there a core file sitting
around anywhere?  (it may get cleaned up post-test).

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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 file or the welcome message.

It is mentioned in the NEWS file, under "NEW FEATURES".  Given what
appears in the INSTALL file and the welcome message, I'm not sure something
like that is appropriate in either one of those files.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Thomas Levine]

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 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 file or the welcome message.

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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 affects a bunch of things (the postfix configuration may be redundant).
> 
> But  in THEORY that shouldn't matter, because we should be
> overriding that configuration by setting MHMTSCONF in the test suite
> which means we should be using that and not an already-existing one.
> Unless you have done something really strange like patching the default
> etc/mts.conf.in file, we should never see that.

Hmmm, thanks for the hint.  My source RPM, which I used to build nmh, 
does contain a patch for exactly that, and it's applied before the 
build and test.  I'd be the guilty one here.

Sorry.

Now I get only these errors, only one of which is free of the xhost 
issue.

FAIL: test/mhfixmsg/test-mhfixmsg
FAIL: test/whatnow/test-attach-detach
FAIL: test/whatnow/test-cd
FAIL: test/whatnow/test-ls


Details for these below.


*** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/Mail/inbox/31   
2017-08-25 20:38:23.471226637 -0700
--- 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/test-mhfixmsg32378.actual
   2017-08-25 20:38:23.479226912 -0700
***
*** 1,15 
- To: recipi...@example.com
- From: sen...@example.com
- Subject: mhfixmsg pass through on parse error
- MIME-Version: 1.0
- Content-Type: multipart/mixed; boundary="- =_aa0"
- 
- --- =_aa0
- Content-Type: text/plain; charset="iso-8859-1
- Content-Disposition: attachment; filename="test1.txt"
- Content-Transfer-Encoding: quoted-printable
- 
- This is the=
-  text/plain part.
- 
- --- =_aa0--
--- 0 

./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-mhfixmsg32378.actual.
first named test failure: pass through message with relative folder path with 
parse error
FAIL: test/mhfixmsg/test-mhfixmsg







*** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7836.expected   
Fri Aug 25 20:38:32 2017
--- /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7836.actual Fri Aug 
25 20:38:32 2017
***
*** 1,5 
--- 1,6 
  attach baz\'s\ boz
  alist
+ localuser:kevinc being removed from access control list
  baz's boz
  detach baz\'s\ boz
  alist

./test/whatnow/test-attach-detach: test failed, outputs are in 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7836.expected and 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7836.actual.
FAIL: test/whatnow/test-attach-detach








*** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7925.expected   
Fri Aug 25 20:38:32 2017
--- /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7925.actual Fri Aug 
25 20:38:32 2017
***
*** 1,3 
  cd /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/foo\'s\ bar
  pwd
! /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/foo's bar
--- 1,3 
  cd /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/foo\'s\ bar
  pwd
! localuser:kevinc being removed from access control list

./test/whatnow/test-cd: test failed, outputs are in 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7925.expected and 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7925.actual.
FAIL: test/whatnow/test-cd








*** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7995.expected   
Fri Aug 25 20:38:32 2017
--- /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7995.actual Fri Aug 
25 20:38:32 2017
***
*** 1,3 
--- 1,4 
  baz
  boz
+ localuser:kevinc being removed from access control list
  ls

./test/whatnow/test-ls: test failed, outputs are in 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7995.expected and 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7995.actual.
FAIL: test/whatnow/test-ls







--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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 THEORY that shouldn't matter, because we should be
overriding that configuration by setting MHMTSCONF in the test suite
which means we should be using that and not an already-existing one.
Unless you have done something really strange like patching the default
etc/mts.conf.in file, we should never see that.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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 the noise.

Right, in a perfect world you wouldn't need to do that, because the
dependencies would cause autoreconf to be run automatically.  But when
make tries to resolve all of the dependencies in the stale Makefile it
complains that it can't figure out how to build sigmsg.h and you never
get a chance to rebuild everything.  Once you get a new Makefile (or
clear out the dependency stuff) everything is okay.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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 Bentley why he added -notls
since he started that.  But I think Ralph covered that pretty well; to
align with best current practice we changed the default SMTP submission
port to 587.  You do not need to add -notls.

>>>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 ... interesting.
>>
>>>./test/mhbuild/test-attach: test failed, outputs are in 
>>>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and 
>>>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected.
>>>FAIL: test/mhbuild/test-attach
>>
>> I think that might have been cleaned up.  Could you do:
>>
>>  make check TESTS=test/mhbuild/test-attach
>>
>> And then let us know what the files that it claimed were different actually
>> contained?
>
>The difference was in the final section -
>
>(9052.expected contains)
>
>Content-Type: application/octet-stream; name="nulls"
>Content-Description: nulls
>Content-Disposition: attachment; filename="nulls"
>Content-Transfer-Encoding: base64
>
>
>
>--- =_aa0--
>
>(9052.draft contains):
>
>Content-Type: binary/; name="nulls"

Um, wow.  A Content-Type of binary/ 

I am curious  if you grep through config.status for the following
variables:

MIMETYPEPROC
MIMEENCODINGPROC

What do they return?  It might be something like

file --brief --dereference --mime-type

And what happens when you run that command on the file test/mhbuild/nulls ?

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[heymanj]

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 ... interesting.
>
>>./test/mhbuild/test-attach: test failed, outputs are in 
>>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and 
>>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected.
>>FAIL: test/mhbuild/test-attach
>
> I think that might have been cleaned up.  Could you do:
>
>   make check TESTS=test/mhbuild/test-attach
>
> And then let us know what the files that it claimed were different actually
> contained?

The difference was in the final section -

(9052.expected contains)

Content-Type: application/octet-stream; name="nulls"
Content-Description: nulls
Content-Disposition: attachment; filename="nulls"
Content-Transfer-Encoding: base64



--- =_aa0--

(9052.draft contains):

Content-Type: binary/; name="nulls"
Content-Description: nulls
Content-Disposition: attachment; filename="nulls"


--- =_aa0--

If it doesn't come through, the .draft contains 15 ctrl-@ characters.
Apparently the base64 encoding is not being processed.


>
> --Ken
>

jerry
 // Jerry Heyman   | If you preach hatred and intolerance
//  Amigan Forever :-) | towards others, don't then play the
\\ //   heymanj at acm dot org | victim if the others react badly to you
 \X/http://www.hobbeshollow.com| -- JMH

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Alexander Zangerl]

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 the noise.

one autoreconf later and now branch master builds fine on debian 8,
and the testsuite runs through fine.

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
"Wenn ein Bürger glaubt, dass ein Terrorist ihm gefährlicher wird als 
ein autoritärer Staat, dann war die ganze politische Bildung für 
die Katz." -- Ilija Trojanow


signature.asc
Description: Digital Signature
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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, specifically how "cd", "pwd",
> and "ls" work.  Talk about knowing how the sausage is being made ...
> 
> Anyway, those commands invoke the user's shell instead of using /bin/sh,
> so if you use another shell the xhost command might get invoked that
> way.  Really, it's doing things like:
> 
>   $SHELL -c "cd&"
> 
> If that still prints out the xhost line if you do that from the command
> line, then that's the problem.


[kevinc@drums-temp #337] printenv SHELL
/bin/tcsh
[kevinc@drums-temp #338] $SHELL -c "cd&"
localuser:kevinc being removed from access control list
/home/kevinc
[kevinc@drums-temp #339] 

I think you nailed the debugging.


--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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 maintainer-clean" first (or finding and removing the dependency on
sbr/sigmsg.h in the appropriate dependency file if you don't want to do
that).  If that doesn't work, I am sure a fresh git checkout will.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Alexander Zangerl]

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


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
How do I set my LaserPrinter to "Stun"?!


signature.asc
Description: Digital Signature
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>  + 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 is being made ...

Anyway, those commands invoke the user's shell instead of using /bin/sh,
so if you use another shell the xhost command might get invoked that
way.  Really, it's doing things like:

$SHELL -c "cd&"

If that still prints out the xhost line if you do that from the command
line, then that's the problem.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

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
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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 issue.  And that could explain the
> test-mymbox failure, too.  test/getcanon, which uses
> gethostname(3p)/getaddrinfo(3p) to determine that
> drums.cosgroves.us is your canonical hostname.  So should
> `ap -format '%(myhost)' ignore`, but it outputs cosgroves.us.
> Unless you have a localname entry in your mts.conf?
> 
> David

Thanks for mentioning mts.conf   I find this

localname: cosgroves.us

There.  Maybe redundant with my main.cf from postfix?



--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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.

Agreed.


> These two are clearly related.  I thought maybe you had set MHMTSUSERCONF,
> but we unset that in the test suite.  We try hard to set up the test suite
> so it has a clean environment, but I guess something slipped through.  How
> do you configure nmh so it thinks your local hostname is just "cosgrove.us"?

In /etc/postfix/main.cf

mydomain = cosgroves.us
myorigin = $mydomain

I did that so that emails sent from my domain wouldn't advertise 
every hostname sending email from within the domain.

Peace...


--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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 -SI:localuser:kevinc' setting which I use
> > exclusively to keep exmh happy.  Ironic.
> 
> Yes, but where is that command?  It seems like running commands within
> the test suite is running your xhost.  Files like .cshrc and .bashrc are
> meant to be silent and produce no output, otherwise things like this,
> and `:e *.c' in old vi get confused as the $SHELL kicked off to expand
> globs, for example, produces not only foo.c and bar.c, but `...being
> removed from...' as well.

xhost is in my .login file.  I commented it out, started a new
shell, and the make check ran the same way.  My current shell might
be remembering or passing something.  When I get a chance to start a
completely fresh shell, then I'll try again.

> This was one reason why xterm(1) should be kicked off as a login shell
> with -l, or the equivalent resource setting, and one-off things done in
> a .profile rather than a per-shell .*rc file.

I can certainly see wanting to have a customization-free environment.

Cheerio...


--
Kevin



___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>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 documentation isn't clear,
fine, but I am just trying to understand how we got here.

>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 ... interesting.

>./test/mhbuild/test-attach: test failed, outputs are in 
>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and 
>/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected.
>FAIL: test/mhbuild/test-attach

I think that might have been cleaned up.  Could you do:

make check TESTS=test/mhbuild/test-attach

And then let us know what the files that it claimed were different actually
contained?

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

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
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

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 with relative folder path 
> > with parse error
> >  FAIL: test/mhfixmsg/test-mhfixmsg
>
> Hm.  Not sure what is happening there.

Me neither.  You might try "sh -x test/mhfixmsg/test-mhfixmsg", but it'll be
noisy.

David

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[heymanj]

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 
/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected differ

./test/mhbuild/test-attach: test failed, outputs are in 
/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.draft and 
/home/jerry/code/nmh-1.7-RC3/test/testdir/21786.expected.
FAIL: test/mhbuild/test-attach

1 failure out of 111 tests.

System:
Mageia 4
gcc v4.8.2

jerry
 // Jerry Heyman   | If you preach hatred and intolerance
//  Amigan Forever :-) | towards others, don't then play the
\\ //   heymanj at acm dot org | victim if the others react badly to you
 \X/http://www.hobbeshollow.com| -- JMH

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

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
gethostname(3p)/getaddrinfo(3p) to determine that
drums.cosgroves.us is your canonical hostname.  So should
`ap -format '%(myhost)' ignore`, but it outputs cosgroves.us.
Unless you have a localname entry in your mts.conf?

David

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>  + 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.
>
>=
>
>  ./test/format/test-myhost: local hostname test expected:
>  'drums.cosgroves.us'
>  but instead got:
>  'cosgroves.us'
>  FAIL: test/format/test-myhost
>
>=
>
>  ./test/format/test-mymbox: Basic user@host test expected:
>  '1'
>  but instead got:
>  '0'
>  FAIL: test/format/test-mymbox

These two are clearly related.  I thought maybe you had set MHMTSUSERCONF,
but we unset that in the test suite.  We try hard to set up the test suite
so it has a clean environment, but I guess something slipped through.  How
do you configure nmh so it thinks your local hostname is just "cosgrove.us"?

>  *** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/Mail/inbox/31
> 2017-08-25 14:45:07.979118674 -0700
>  --- 
> /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/test-mhfixmsg31454.actual
> 2017-08-25 14:45:07.988118977 -0700
>  ***
>  *** 1,15 
>  - To: recipi...@example.com
>  - From: sen...@example.com
>  - Subject: mhfixmsg pass through on parse error
>  - MIME-Version: 1.0
>  - Content-Type: multipart/mixed; boundary="- =_aa0"
>  - 
>  - --- =_aa0
>  - Content-Type: text/plain; charset="iso-8859-1
>  - Content-Disposition: attachment; filename="test1.txt"
>  - Content-Transfer-Encoding: quoted-printable
>  - 
>  - This is the=
>  -  text/plain part.
>  - 
>  - --- =_aa0--
>  --- 0 
>
>  ./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 with relative folder path 
> with parse error
>  FAIL: test/mhfixmsg/test-mhfixmsg

Hm.  Not sure what is happening there.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Howard Bampton]

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 nmh-1.7-RC3.tar.gz | tar xf -
> cd nmh-1.7-RC3
> ./build_nmh

I tried the above (thank you for making it easy) on an Ubuntu 16.04
LTS host (reasonably up to date patch-wise).

Once I figured out the missing dependencies, the build completes- all
tests passed (1 not run).

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

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 that command?  It seems like running commands within
the test suite is running your xhost.  Files like .cshrc and .bashrc are
meant to be silent and produce no output, otherwise things like this,
and `:e *.c' in old vi get confused as the $SHELL kicked off to expand
globs, for example, produces not only foo.c and bar.c, but `...being
removed from...' as well.

This was one reason why xterm(1) should be kicked off as a login shell
with -l, or the equivalent resource setting, and one-off things done in
a .profile rather than a per-shell .*rc file.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Kevin Cosgrove]

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.

Most of my 'make check' tests passed.  6 of 111 failed.  This was 
built and checked on a Fedora 17 system.  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.

Here's what failed.

=

  ./test/format/test-myhost: local hostname test expected:
  'drums.cosgroves.us'
  but instead got:
  'cosgroves.us'
  FAIL: test/format/test-myhost

=

  ./test/format/test-mymbox: Basic user@host test expected:
  '1'
  but instead got:
  '0'
  FAIL: test/format/test-mymbox

=

  *** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/Mail/inbox/31 
2017-08-25 14:45:07.979118674 -0700
  --- 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/test-mhfixmsg31454.actual
 2017-08-25 14:45:07.988118977 -0700
  ***
  *** 1,15 
  - To: recipi...@example.com
  - From: sen...@example.com
  - Subject: mhfixmsg pass through on parse error
  - MIME-Version: 1.0
  - Content-Type: multipart/mixed; boundary="- =_aa0"
  - 
  - --- =_aa0
  - Content-Type: text/plain; charset="iso-8859-1
  - Content-Disposition: attachment; filename="test1.txt"
  - Content-Transfer-Encoding: quoted-printable
  - 
  - This is the=
  -  text/plain part.
  - 
  - --- =_aa0--
  --- 0 

  ./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 with relative folder path with 
parse error
  FAIL: test/mhfixmsg/test-mhfixmsg

=

  *** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/6934.expected 
Fri Aug 25 14:45:17 2017
  --- /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/6934.actual   
Fri Aug 25 14:45:17 2017
  ***
  *** 1,5 
  --- 1,6 
attach baz\'s\ boz
alist
  + localuser:kevinc being removed from access control list
baz's boz
detach baz\'s\ boz
alist

  ./test/whatnow/test-attach-detach: test failed, outputs are in 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/6934.expected and 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/6934.actual.
  FAIL: test/whatnow/test-attach-detach

=

  *** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7024.expected 
Fri Aug 25 14:45:17 2017
  --- /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7024.actual   
Fri Aug 25 14:45:17 2017
  ***
  *** 1,3 
cd /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/foo\'s\ bar
pwd
  ! /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/foo's bar
  --- 1,3 
cd /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/foo\'s\ bar
pwd
  ! localuser:kevinc being removed from access control list

  ./test/whatnow/test-cd: test failed, outputs are in 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7024.expected and 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7024.actual.
  FAIL: test/whatnow/test-cd

=

  *** /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7096.expected 
Fri Aug 25 14:45:17 2017
  --- /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7096.actual   
Fri Aug 25 14:45:17 2017
  ***
  *** 1,3 
  --- 1,4 
baz
boz
  + localuser:kevinc being removed from access control list
ls

  ./test/whatnow/test-ls: test failed, outputs are in 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7096.expected and 
/home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/7096.actual.
  FAIL: test/whatnow/test-ls

=



--
Kevin




___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

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 the switch, it seems port 25 is now
for SMTP between MTAs, mail transfer agents, and port 587 is for SMTP to
an MSA, mail submission agent, from an MUA, mail user agent, like nmh.
It's typically the same program, e.g. postfix, wearing two different
hats, but it allows 587 to only be localhost, say, and for Postfix to be
configured to do different things to those emails, e.g. fix up headers,
compared with 25 where it might take violation of the standards as a
cause to reject.

There's a mention of this, amongst many other things, in the NEWS file.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

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

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Anthony J. Bentley]

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.
>
> The -port switch to send(1), post(1), and whom(1) can be used to override.

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 and I seem to be able to send mail again.

-- 
Anthony J. Bentley

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[David Levine]

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), post(1), and whom(1) can be used to override.

> or change your 1.7 configuration to submit email directly to gmail (we
> have support for the XOAUTH2 authentication used by Gmail, if you want
> to do that).

See send(1) and mhlogin(1).

David

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>$ 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 GMail. If I manually pipe a message to
>OpenSMTPD's sendmail(8), it arrives at the destination. How do I get
>mail to send again?

Well, it seems like there are two options: change the 1.7 configuration
to match the configuration you had for 1.6 (I don't know how it was
configured before), or change your 1.7 configuration to submit email
directly to gmail (we have support for the XOAUTH2 authentication used
by Gmail, if you want to do that).  I don't want to get into the whole
ball of hair about which one is better; opinions differ on that, I have
one preference, other people have a different one.  But we haven't
removed any functionality, so you should still be able to change nmh's
configuration to match how 1.6 worked.

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Anthony J. Bentley]

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 you give RC3 a
> try.

I've been running nmh-1.6 on OpenBSD. After installing 1.7rc3, I can
no longer send mail:

$ comp
What now? s -snoop
Trying to connect to "localhost" ...
Connecting to 127.0.0.1:587...
Connection failed: Connection refused
Connecting to ::1:587...
Connection failed: Connection refused
post: problem initializing server; [BHST] no servers available (use
-snoop for details
send: message not delivered to anyone

I run OpenSMTPD as a relay to GMail. If I manually pipe a message to
OpenSMTPD's sendmail(8), it arrives at the destination. How do I get
mail to send again?

-- 
Anthony J. Bentley

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[norm]

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 issues with RC3 I hope to go to 1.7 final within
>a week or two; widespread testing would greatly assist this process.  So
>if you have a moment or two to spare, give RC3 a try and let us know how
>it works for you. If you've already done that, then thank you!

Yesterday, Aug 24, I installed it including a make check, all without
incident. I've been using it since yesterday at 7:29 AM PDT. I've seen no
problems. In particular, the two problems I reported earlier are now gone.

Norman Shapiro

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Leonardo Taccari]

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 with RC3 I hope to go to 1.7 final within
> a week or two; widespread testing would greatly assist this process.  So
> if you have a moment or two to spare, give RC3 a try and let us know how
> it works for you. If you've already done that, then thank you!
> [...]

That's a great news!

Back on how it works... I can confirm that the several bugs that
affected early 1.7 RCs and I was able to reproduce are fixed on 1.7RC3.
I have also run the tests on NetBSD/amd64 8.99.1 against 1.7RC3 and...:

 [...]
 
 All 110 tests passed
 (1 test was not run)
 
 [...]

(the 1 test not run was the one that required valgrind, so it was
expected and not a regression).


Thank you and all nmh developers and community that made that possible!
Keep up the good work!

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ralph Corderoy]

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 any build problems.  And
then running it instead of the version you're currently using.

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 nmh-1.7-RC3.tar.gz | tar xf -
cd nmh-1.7-RC3
./build_nmh

I accepted the defaults at the prompts by pressing Enter.  It pokes
around your existing nmh installation to help set those defaults if it's
in your PATH.  After the "TLS support" question it's silent for a while
as it builds until the shell prompt appears again.

There, nothing to it.  So dust off that Xenix and give it a spin.
build_nmh.log records the build platform, configure, make, and test
results, so if anything goes wrong then we'd like that.  Send it
privately if you don't want it on the list.  Feel free to debug the
issue further if you want, but your acting as a manual `buildbot' is
what we really appreciate.

If all went well then installing can be done with

./build_nmh -i

This will be quicker;  the make(1) will spot the hard work has already
been done.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers