Excuse me if this has been noted before. I just joined the list today, and could not find this discussed in the last 3 months of archives, although there were some similar.
Observation: The same signed mail (sent from Apple Mail 4.4) to Gmail, Mobile Me and my own server, arrives unscathed at two of them all the time and some of the time via me.com. I'm therefore pretty sure the problem is Apple's but I'd like to confirm my hypothesis before I log a bug with them. Messages that fail to validate appear to have a few strings UPCASED inside what I think is the boundary of the signed message part (That's what I am asking to get confirmed.) I threw the raw text of what came back to me from my .me and gmail accounts from a signed test message I sent from my own server at Emac's EDIFF. Here's what .me gave me ________________________________ Date: Thu, 03 Mar 2011 15:58:37 +0000 Message-id: <[email protected]> To: Elliott Roper <[email protected]>, Elliott Roper <[email protected]> MIME-version: 1.0 (Apple Message framework v1082) Content-transfer-encoding: 7bit X-Pgp-Agent: GPGMail 1.3.2 X-Mailer: Apple Mail (2.1082) --Apple-Mail-11-885654614 Content-Type: multipart/MIXED; boundary=Apple-Mail-10-885654566 --Apple-Mail-10-885654566 Content-Transfer-Encoding: 7BIT Content-Type: TEXT/PLAIN; charset=us-ascii 1558 --Apple-Mail-10-885654566 Content-Disposition: INLINE; filename="Emacs NEWS.23.1 snippet.jpg" Content-Type: IMAGE/JPG; x-unix-mode=0644; x-mac-type=4A504547; x-mac-creator=474B4F4E; name="Emacs NEWS.23.1 snippet.jpg" Content-Transfer-Encoding: BASE64 /9j/4AAQSkZJRgABAQEASABIAAD//gAMQXBwbGVNYXJrCv/bAIQAAgICAgICAgICAgMCAgMDBQQD AwMDBgUFBAUHBggHBwYHBwgJCwoICAsIBwcKDQoLCwwMDQwICQ4ODQwOCwwMDAECAwMDAwMGBAQG ...etc ____________________________________________________________________ and this is what came back from gmail. __________________________________________________________________ Date: Thu, 3 Mar 2011 15:58:37 +0000 Message-Id: <[email protected]> To: Elliott Roper <[email protected]>, Elliott Roper <[email protected]> Mime-Version: 1.0 (Apple Message framework v1082) Content-Transfer-Encoding: 7bit X-Pgp-Agent: GPGMail 1.3.2 X-Mailer: Apple Mail (2.1082) This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-11-885654614 Content-Type: multipart/mixed; boundary=Apple-Mail-10-885654566 --Apple-Mail-10-885654566 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii 1558 --Apple-Mail-10-885654566 Content-Disposition: inline; filename="Emacs NEWS.23.1 snippet.jpg" Content-Type: image/jpg; x-mac-type=4A504547; x-mac-creator=474B4F4E; x-unix-mode=0644; name="Emacs NEWS.23.1 snippet.jpg" Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAQEASABIAAD//gAMQXBwbGVNYXJrCv/bAIQAAgICAgICAgICAgMCAgMDBQQD ...usw ____________________________________________________________________________ What I'm after getting confirmed is that the line --Apple-Mail-10-885654566 is the start of the signed region, and that mobile me's server was naughty uppercasing 7BIT, TEXT/PLAIN and BASE64 Elliott Roper phone: +44 1663 747334 mobile +44 7796 171018 www.yrl.co.uk _______________________________________________ gpgtools-users mailing list [email protected] FAQ: http://www.gpgtools.org/faq.html Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users Unsubscribe: http://lists.gpgtools.org/mailman/options/gpgtools-users/[email protected]?unsub=Unsubscribe&unsubconfirm=1 This email sent to: [email protected]
