Date: Tue, 10 Jun 2008 17:35:05 -0500 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: freebsd-questions@freebsd.org Subject: Re: Problems opening mail on this list Message-ID: <FE57A39A4D47C55B932C310F@utd65257.utdallas.edu> In-Reply-To: <20080610213245.GB79442@kokopelli.hydra> References: <FF8482A96323694490C194BABEAC24A002D7BDEE@Email.cbord.com> <CE393FEB-BDB5-4D32-A179-D2EF03493542@sentex.net> <FF8482A96323694490C194BABEAC24A002D7BEAC@Email.cbord.com> <8DFCF30B986212E9F5E6DE8E@utd65257.utdallas.edu> <DD4AAC52-219B-46C8-B2EE-A77ABE533D3E@sentex.net> <72CBB8D6BA493D195318D0D2@utd65257.utdallas.edu> <20080610213245.GB79442@kokopelli.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Tuesday, June 10, 2008 15:32:45 -0600 Chad Perrin <perrin@apotheon.com> wrote: > On Tue, Jun 10, 2008 at 03:34:59PM -0500, Paul Schmehl wrote: >> --On Tuesday, June 10, 2008 16:23:32 -0400 Andrew Berry >> <andrewberry@sentex.net> wrote: >> >> > On 10-Jun-08, at 1:07 PM, Paul Schmehl wrote: >> > >> >> Andrew, maybe you could send a signed message, state in the body >> >> that it was signed, and then I can look at the headers and tell you >> >> what's going on. >> > >> > Here is a message which has been signed. >> > >> >> There's no sig attached, so it's getting stripped off somewhere. >> This line in the headers looks to be the culprit: >> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 >> >> That will strip all attachments, including S/MIME. > > My PGP signatures seem to come through just fine, however. Yes it did. And it appears that this is the reason: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H1spWtNR+x+ondvy" Content-Disposition: inline Andrew's is like this: Content-Type: multipart/signed; boundary=Apple-Mail-1-746495031; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v924) Date: Tue, 10 Jun 2008 16:23:32 -0400 References: <FF8482A96323694490C194BABEAC24A002D7BDEE@Email.cbord.com> <CE393FEB-BDB5-4D32-A179-D2EF03493542@sentex.net> <FF8482A96323694490C194BABEAC24A002D7BEAC@Email.cbord.com> <8DFCF30B986212E9F5E6DE8E@utd65257.utdallas.edu> X-Mailer: Apple Mail (2.924) X-Spam-Scanner: SpamAssassin 3.000004 (http://www.spamassassin.org/) on batman.cs.uoguelph.ca X-Spam-Score: hits=0.0 X-Spam-Level: X-Spam-Tests: FORGED_RCVD_HELO,SPF_PASS X-Spam-Status: Suspected X-Scanned-By: MIMEDefang 2.63 on 131.104.94.198 X-Scanned-By: MIMEDefang 2.52 on 172.17.94.85 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Notice that his was processed through MIMEDefang twice and then Content Filtered by Mailman. Also, his content type is protocol="application/pkcs7-signature" whereas yours is "application/pgp-signature". There's also no Content-Disposition: line in Andrew's email headers, so it's possible that absence of that line makes a difference as well. By default, it appears that Mailman does not do content filtering. It also has pass rules (if filtering is enabled) for multipart/mixed, multipart/alternative and text/plain. So, it's possible that MIMEDefang is the culprit instead. -- Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE57A39A4D47C55B932C310F>