PGP/MIME signatures cannot be verified on lists.ubuntu.com

[Aminda Suomalainen]

Mailing list software on lists.ubuntu.com seems to mess up with headers and make all PGP/MIME signed content unverifiable to email clients.

This can be a problem with security announcements list, where all messages seem to be PGP/MIME signed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/996581/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Aminda Suomalainen (mikaela)]

Users of email clients, which don't support GPG see signatures of
S/MIME messages as attachment called signature.asc.

GPG compatible email clients hide them and show is the signature valid
or not. With lists.ubuntu.com mailing lists GPG compatible clients show the
signature.asc file and cannot verify the signature, because they don't
recognize signature.asc as PGP/MIME signature, because the headers
have been modified by mailing list software.

[C de-Avillez (hggdh2)]

Cannot reproduce with Thunderbird 12.0.1+build1-0ubuntu0.12.04.1 (precise) and with Claws-mail 3.8.0-1ubuntu1 (precise).

[Aminda Suomalainen (mikaela)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14.06.2012 04:24, C de-Avillez wrote:
> Cannot reproduce with Thunderbird 12.0.1+build1-0ubuntu0.12.04.1
> (precise) and with Claws-mail 3.8.0-1ubuntu1 (precise).
>

This should be able to be verified with Thunderbird. I know that
Enigmail has this issue and when it's mentioned on their mailing list,
they say that it's problem with Mailman.

- --
[Mika Suomalainen](https://mkaysi.github.com/) ||

NOTICE! I am on mobile broadband with very limited time, so I cannot
read emails very much.
The best time to contact me is probably week ends when I have better
connectivity with good luck.

[gpg --keyserver pool.sks-keyservers.net --recv-keys
4DB53CFE82A46728](http://mkaysi.github.com/PGP/key.txt) ||
[Why do I sign my
emails?](http://mkaysi.github.com/PGP/WhyDoISignEmails.html) ||
[Please don't send
HTML.](http://mkaysi.github.com/articles/complaining/HTML.html) ||
[This signature](https://gist.github.com/2643070#file_icedove.md) ||

[Please reply below this
line](http://mkaysi.github.com/articles/complaining/topposting.html)

____________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Homepage: http://mkaysi.github.com/
Comment: gpg --keyserver pool.sks-keyservers.net --recv-keys 82A46728
Comment: Public key: http://mkaysi.github.com/PGP/key.txt
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJP22FJAAoJEE21PP6CpGcoGNEP/iw6MIohyZNB4VgQ0XXUvUIo
/Uv/4V+k6qAnB+vu5F8WGF5tb6CTP95Acf73ZtKHvuxCk1H2NT6wgkBJWDYcP53a
KLxkzxYE0uFDlCbkc783gA9xz3rZJGDOs/1IsDmOJzY3pJZ55NNd3G7GgsjRry7i
sgYd5Vnpud6D0IVLGV8o4NKzVPygf1tTvH/WShRWSUHsv+bnLwDB1evTJuz+9eOL
uWFbOR6/06KFu9rAS34MjRvtWykQ9/ChJ9U7/mhuUQVodVp1BLAWr9Q29p3prYmJ
GFMt66dHW9mOsl2CxB2f2eKbbPsVSZYh4xsCP1uh1QgpbAwvGEhaROeBPY6oOAo3
8NyEKjHCyrnAh1M2edUWuXF8DORskfKZbr++ULAL5yZ6QguK+GQ+cfZ2kVFltyUQ
vCvs4if5GnvMSSCwFGocOejetJ/sTBbOH0DTvVAaZH1xC7yuzVpPKPwef/pZ5C+m
om24IC/fVHgSGxy2pe2Xn8HmniT6IcwfMQ/8DSMHYJbjYsSwUVbVUe334zKNDOtj
O1W3krPnBkQfcpYrvmNyWnV/60cWPlRHwKFYoflyiMaReSrN6BcDcneGQmxVlK0t
0o7rnLaq7HVAm4ocyWcK7FN6vsaHjYjPBSNy3Ah8ppJYRis8afiVifPsGqrXfDLY
LuKTBHwHiFlqwThsBjwn
=lO70
-----END PGP SIGNATURE-----