Re: S/MIME oddness

["Arne Jørgensen" <arne@arnested.dk>]

Simon Josefsson <jas@extundo.com> writes:

> Arne Jørgensen <arne@arnested.dk> writes:

[...]

>> But the version that i Gcc to my self does not have an extra blank
>
> Perhaps ^M isn't treated as newline by the Gcc backend?  Some backends
> either replace \r\n with \n, or uses \r?\n as the newline regexp.
>
>> and switching to smtpmail.el made the problem go away.
>
> SMTP uses \r\n as newline, perhaps \r\r\n is treated as a single
> newline by some implementations.
>
>> I think that doesn't make OpenSSL an usual suspect.
>
> Still not impossible, I think, although the OpenSSL version that had
> this bug is quite old and insecure, so it is only a remote
> possibility.
>
> Hm.  Can you reproduce the added newline bug by previewing a S/MIME
> signed message?

I have previewed the message and found no extra newlines. Besides I
have a rather new OpenSSL (0.9.7c 30 Sep 2003).

I still suspect Postfix to be the problem. Here is what I tried:

I copied the GCC-ed version (which doesn't have an extra line) to a
file and piped it to Postfix sendmail:

     cat testmail.txt | /usr/lib/sendmail -t

When the mail arrives in my inbox it has the extra line. This was all
done on one machine (delivery to local user).

Then I logged in to another machine (with Sendmail) and did the same
trick. The message had no extra blank line.

The testmail.txt can be located at <http://arnested.dk/testmail.txt>.

So I think this is not a Gnus problem (unless Gnus produces some
invalid MIME that only some mail servers stumble across).

I think I'll try reporting this to a postfix mailing list.

-- 
Arne Jørgensen
Valby Langgade 272, 1. tv., DK-2500 Valby, Denmark
phone: +45 36 44 18 03, mobile: +45 21 65 01 13
email: arne@arnested.dk, <http://arnested.dk/>