Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel@rubyforge.org
Subject: [sup-devel] RubyMail cannot handle multipart/signed messages
Date: Mon, 19 Apr 2010 09:43:49 +0200	[thread overview]
Message-ID: <1271662579-sup-4883@midna.zekjur.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

Hi,

yesterday I got a PGP/MIME message which had multiple attachments. Turns out
RubyMail cannot do multipart/signed (sup says RubyMail failed to decode the
document for some bizarre reason, when you try it in irb, you’ll see it
actually decodes the message parts as headers). I also tried 'mail' by the
same author which he claims can do multipart and is better in general, but
it seems it also cannot do multipart/signed (RFC 1847).

So, what are the plans in regard to RubyMail? Switching to something different
altogether? If so, to which library? I would then fix parsing of
multipart/signed messages for this library…

Best regards,
Michael

PS: I attached a minimum working example of a problematic message (decrypted
body only)

[-- Attachment #2: mwe --]
[-- Type: application/octet-stream, Size: 2099 bytes --]

Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_//bFY=D0OKHxcuPQV_U6beli"; protocol="application/pgp-signature"

--Sig_//bFY=D0OKHxcuPQV_U6beli
Content-Type: multipart/mixed; boundary="MP_/+kacMkT=yx+FKvl3YUds1sR"

--MP_/+kacMkT=yx+FKvl3YUds1sR
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline



--=20
ceterum censeo microsoftem esse delendam.

--MP_/+kacMkT=yx+FKvl3YUds1sR
Content-Type: text/plain; charset=US_ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="text1.txt"

/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsK
CwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRQBAwQEBQQFCQUFCRQNCw0UFBQUFBQUFBQU

--MP_/+kacMkT=yx+FKvl3YUds1sR
Content-Type: text/plain; charset=US_ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="text2.txt"

/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsK
CwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRQBAwQEBQQFCQUFCRQNCw0UFBQUFBQUFBQU

--MP_/+kacMkT=yx+FKvl3YUds1sR
Content-Type: text/plain; charset=US_ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="text3.txt"

/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsK
CwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRQBAwQEBQQFCQUFCRQNCw0UFBQUFBQUFBQU

--MP_/+kacMkT=yx+FKvl3YUds1sR
Content-Type: text/plain; charset=US_ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="text4.txt"

/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsK
d1awmU5G4oSBya92lg6cKcLGbqvaPQ//2Q==

--MP_/+kacMkT=yx+FKvl3YUds1sR--

--Sig_//bFY=D0OKHxcuPQV_U6beli
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

xIQAoI9H0qgqosPpYu96x/mMr6MO/5WA
-----END PGP SIGNATURE-----

--Sig_//bFY=D0OKHxcuPQV_U6beli--

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

             reply	other threads:[~2010-04-19  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  7:43 Michael Stapelberg [this message]
2010-04-19 12:55 ` Sam Hall
2010-04-19 15:57   ` Michael Stapelberg
2010-04-20  6:26     ` Sam Hall
2010-04-20  6:40       ` Michael Stapelberg
2010-04-20 15:27         ` Rich Lane

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=1271662579-sup-4883@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --cc=sup-devel@rubyforge.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