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

 subscribe
 done

X Zerothly, I have prefixed all of the non-command lines in this email
X with an X to avoid Malone 34339.  (My first attempt only prefixed
X the quotes from earlier LP mails, but the forbidden word `status'
X happened to wordwrap to the beginning of one of the lines in my list
X of bullet points at the bottom.)
X
X Firstly, I think that 29209 and 31586 are the same problem.
X 
X Secondly, I have another nice example of a broken behaviour:
X 
X I sent this message:
X 
X    From: Ian Jackson <email address hidden>
X    To: <email address hidden>,
X        <email address hidden>,
X        <email address hidden>,
X        <email address hidden>
X    Subject: firefox bugfixes
X    Date: Fri, 10 Mar 2006 16:28:08 +0000
X    Message-ID: <email address hidden>
X
X    -----BEGIN PGP SIGNED MESSAGE-----
X    Hash: SHA1
X
X     affects /distros/ubuntu/firefox
X     status fixreleased
X     done
X
X
X    I believe I have fixed these bugs in dapper, [...]
X 
X When these mails came back to me from Malone, they looked like this:
X 
X    From: Ian Jackson <email address hidden>
X    Sender: <email address hidden>
X    To: <email address hidden>
X    Subject: [Bug 30603] "Comment" in .desktop file doubly utf-8 encoded
X    Date: Fri, 10 Mar 2006 16:30:07 -0000
X    Message-Id: <email address hidden>
X
X    Public bug report changed:
X    https://launchpad.net/malone/bugs/30603
X
X    Comment:
X    -----BEGIN PGP SIGNED MESSAGE-----
X    Hash: SHA1
X
X     affects /distros/ubuntu/firefox
X     status fixreleased
X     done
X
X
X    I believe I have fixed these bugs in dapper, [...]
X 
X plus
X 
X    From: Ian Jackson <email address hidden>
X    Sender: <email address hidden>
X    To: <email address hidden>
X    Subject: [Bug 30603] "Comment" in .desktop file doubly utf-8 encoded
X    Date: Fri, 10 Mar 2006 16:30:07 -0000
X    Message-Id: <20060310163007.30701.37383.launchpad@<email address hidden>>
X
X    Public bug report changed:
X    https://launchpad.net/malone/bugs/30603
X
X    Task: ubuntu firefox
X             Status: Unconfirmed => Fix Released
X 
X for each of the four bugs I was addressing.
X 
X This is completely wrong in almost every possible respect !  Note how
X the mail that the subscribers of 30603 get is so garbled they can't
X see where else the mail went, nor the originally quoted email address
X of the person who sent it.
X 
X 
X These mails should have looked like this one mail:
X 
X    Resent-From: Ian Jackson <email address hidden>
X    Resent-To: Ian Jackson <email address hidden> (subscriber to 30603),
X               David Farning <....[etc]>
X               [etc]
X    Resent-Date: Fri, 10 Mar 2006 16:28:08 +0000
X    Resent-Message-ID: <[something]@gangotri.ubuntu.com>
X    Resent-Sender: Malone Bug Tracking System <email address hidden>
X    Reply-To: <email address hidden>
X    X-Malone-PR-Path: /malone/bugs/30603
X    X-Malone-PR-Affects: /distros/ubuntu/firefox
X    X-Loop: <email address hidden>
X    From: Ian Jackson <email address hidden>
X    To: <email address hidden>,
X        <email address hidden>,
X        <email address hidden>,
X        <email address hidden>
X    Subject: [Bug 30603] firefox bugfixes
X    Date: Fri, 10 Mar 2006 16:28:08 +0000
X    Message-Id: <email address hidden>
X    [ Public bug report changed:
X      https://launchpad.net/malone/bugs/30603
X
X      Task: ubuntu firefox
X              Status: Unconfirmed => Fix Released
X      - Malone Bug Tracker]
X
X    -----BEGIN PGP SIGNED MESSAGE-----
X    Hash: SHA1
X
X     affects /distros/ubuntu/firefox
X     status fixreleased
X     done
X
X
X    I believe I have fixed these bugs in dapper, [...]
X 
X _That_ would be how it would have looked if it was a mailing list.
X 
X Note:
X 
X 1. A complete set of Resent-* headers is mandatory.
X 2. Nearly all of the original headers are completley preserved.
X    In particular, not-understood headers must be preserved, and
X    Received fields must be preserved.
X 3. Malone should try to send as few separate messages as possible and
X    try to send the same mail to several people wherever possible; this
X    makes things work better when people reply to these emails.
X 4. An appropriate Reply-To has been added.
X 5. Some X-Malone-* headers have been added to make end-user filtering
X    possible.
X 6. The text inserted into the body by Malone has been marked the same
X    way a human list moderator would mark their comments, if they
X    inserted any.  A reasonable alternative would be to send two
X    separate mails as at present, but in that case the copy with the
X    comment should contain _only_ the comment and not `Public bug
X    report changed:' or `Comment:' or anything.  In that case the
X    status change email should NOT have a From: naming the user making
X    the change.  Cf debbugs and bugzilla status change mails.
X 6. An X-Loop header has been added.  Any existing X-Loop headers
X    should be retained (and checked that none of them are
X    <email address hidden>).
X 7. Note that Resent-CC is available as well as Resent-To.  The Malone
X    designers should consider where a CC is more appropriate (there is
X    a semantic difference to the two and many email programs and
X    filtering systems treat them differently in subtle ways).
X 8. The current Message-IDs on the synthetic emails, such as
X     Message-Id: <20060310163007.30701.37383.launchpad@<email address hidden>>
X    are syntactically invalid !
X 
X Ian.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFEEbjd8jyP9GfyNQARAj2HAJ0VOvhONW5ZDch0S6yGVVIBYCnHAACfc1xJ
aBpEW98aKgABhqA2KoqZp/w=
=/rNy
-----END PGP SIGNATURE-----