Your message dated Sat, 23 May 2009 21:15:41 +0200
with message-id <[email protected]>
and subject line Re: Bug#275164: Sympa MIME footer breaks multipart/signed
message format (OpenPGP signatures).
has caused the Debian Bug report #275164,
regarding Sympa MIME footer breaks multipart/signed message format (OpenPGP
signatures).
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
275164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275164
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sympa
Version: 4.1.2-1
I have configured /var/lib/sympa/expl/.../message.footer.mime for some mailing
list. Sympa's algorithm, that governs the addition of that footer, is
documented in
file:///usr/share/doc/sympa/html/node14.html#SECTION0014100000000000000000 as
follows:
if message is not multipart/signed
if footer_type==append
if message is text/plain
append header/footer to it
else if message is multipart AND first part is text/plain
append header/footer to first part
if footer_type==mime
if message is not multipart/alternative
add header/footer as a new MIME part
As, in my case, footer_type is mime, this should result in the addition of the
footer as a new MIME part if the message is neither multipart/signed nor
multipart/alternative.
However, that is not what happens. I have send a message to the mailing list
with MIME header
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig6E39F8C2021757A6B1CFE704"
which should have been left alone. But sympa added the footer as a new
MIME-part.
In detail, RFC3156 http://www.ietf.org/rfc/rfc3156.txt says:
The multipart/signed body MUST consist of exactly two parts. The
first part contains the signed data in MIME canonical format,
including a set of appropriate content headers describing the data.
The second body MUST contain the OpenPGP digital signature. It MUST
be labeled with a content type of "application/pgp-signature".
What sympa did was to add a third part to the multipart/signed message, thus
breaking OpenPGP's multipart/signed format.
If you need a test message to verify the bug, ask the Debian bug tracking system
to extract this bug report as a mailbox, and extract this message. It has the
same structure as did the message that caused the algorithm not to be followed,
so should provide you with the test message you need.
Regards, and thank you for providing fine software
Andreas
--
Dr. Andreas Krüger, [email protected]
GPG/PGP Fingerprint 8063 4A9B 362D 4220 A546 14C1 EA19 AADC FD44 5EB7
DV-RATIO Nordwest GmbH, Tel.: +49 211 577 996-0, Fax: +49 211 559 1617
Leostraße 31, 40545 Düsseldorf, Germany
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
This is a four years old bug and the submitter can't help us to fix it
as he stopped using sympa. Hence i'm closing the bug.
Feel free to reopen it if necessary.
Regards,
--
Emmanuel Bouthenot
--- End Message ---
