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

AAAAAAAAAAAAAAAAAAAA

------- =_aaaaaaaaaa0--

(9052.draft contains):

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


------- =_aaaaaaaaaa0--

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