supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Laurent Bercot <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: problem with mailing list and multipart/mime?
Date: Sat, 22 Oct 2011 13:47:47 +0200	[thread overview]
Message-ID: <20111022114747.GA10042@skarnet.org> (raw)
In-Reply-To: <20111022104356.GD27171@home.power>

> I've received two copies of this email: one sent to me and second sent to
> maillist. Copy sent to me works ok - correct signed message. Copy sent to
> maillist is broken. So, looks like maillist bug.

 The mailing-list software *modifies* the message - namely, it adds a few
headers (such as List-Unsubscribe) and removes other headers (such as
Return-Path - for obvious reasons). So, it's normal that you cannot
verify the signature of a message after it goes through the list.

 The adding and removal of headers should be perfectly safe and I don't
think there's a bug in there. On the other hand, there *might* be a
problem with the handling of MIME types, because it's something
complex. The set of MIME types that are forbidden (i.e. if such a MIME
type is encountered in a multipart message, the corresponding part of
the message will be deleted) is the default set for the version of
ezmlm-idx I am using. It includes text/html; it does not include
text/plain, of course; and it does not include application/pgp-signature.

 Since messages are modified when going through the list, it makes no
sense to sign them, so I might as well add application/pgp-signature
to the list of removed MIME parts, and end this bit of confusion.

 If you think you have exhibited a real bug, such as a text/plain part
of a MIME message being removed, please send proof to me: a message
sent 1. to the list and 2. directly to me (using the address in the
"From:" header of this message, and replying to the confirmation
request), so I can compare the two and use it to investigate. But
ezmlm-idx has worked flawlessly for years, and the MIME filter has
being treating us pretty well, so I don't think there's a bug involved -
at most, a misconfiguration on my part is possible.

 Anyway I'll be away for the week-end, so we'll see this next Monday.

-- 
 Laurent


  reply	other threads:[~2011-10-22 11:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 16:26 Per-user service managers Mike Buland
2011-10-20 17:40 ` Jameson Graef Rollins
2011-10-20 18:11   ` Mike Buland
2011-10-20 19:16     ` Jameson Graef Rollins
2011-10-20 19:21       ` Mike Buland
2011-10-21 16:44       ` problem with mailing list and multipart/mime? Jameson Graef Rollins
2011-10-21 18:55         ` Uffe Jakobsen
2011-10-22  1:31         ` Alex Efros
2011-10-22  2:01           ` Jameson Graef Rollins
2011-10-22 10:43             ` Alex Efros
2011-10-22 11:47               ` Laurent Bercot [this message]
2011-10-22 19:43                 ` Jameson Graef Rollins
2011-10-22 19:49                   ` Jameson Graef Rollins
2012-03-10 16:34                   ` Laurent Bercot
2011-10-22 19:16             ` Jameson Graef Rollins
2011-10-22  7:24         ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111022114747.GA10042@skarnet.org \
    --to=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).