From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2123 Path: news.gmane.org!not-for-mail From: Laurent Bercot Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: problem with mailing list and multipart/mime? Date: Sat, 22 Oct 2011 13:47:47 +0200 Message-ID: <20111022114747.GA10042@skarnet.org> References: <87aa8vblyz.fsf@servo.finestructure.net> <87vcrja2xj.fsf@servo.finestructure.net> <87y5we8fcd.fsf@servo.finestructure.net> <20111022013106.GC27171@home.power> <87pqhp6ayz.fsf@servo.finestructure.net> <20111022104356.GD27171@home.power> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1319283891 18294 80.91.229.12 (22 Oct 2011 11:44:51 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 22 Oct 2011 11:44:51 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-2357-gcsg-supervision=m.gmane.org@list.skarnet.org Sat Oct 22 13:44:46 2011 Return-path: Envelope-to: gcsg-supervision@lo.gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1RHa0M-0005xn-8S for gcsg-supervision@lo.gmane.org; Sat, 22 Oct 2011 13:44:46 +0200 Original-Received: (qmail 11812 invoked by uid 76); 22 Oct 2011 11:47:47 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 11804 invoked by uid 1000); 22 Oct 2011 11:47:47 -0000 Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20111022104356.GD27171@home.power> User-Agent: Mutt/1.4i Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2123 Archived-At: > 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