Skip to contentSkip to conversation

digest separation

DISCUSSION Mads Martin Joergensen 4 participants 5 messages Sep 1, 2004

lore
Share & tools
lore
#0 lore raw

What seperates every mail in a digest of several mails?

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                -- A. P. J.
#1 lore raw
Quoted 1 line · Mads Martin Joergensen

What seperates every mail in a digest of several mails?

I think the correct (as in RFC 2046) way to do it is to make the digest mail a multipart/digest, and have each mail be a part with content type message/rfc822.

Best regards,
Morten

Signature · 2 lines
Morten K. Poulsen <[email protected]>
http://www.afdelingp.dk/
#2 lore raw
In reply to Mads Martin Joergensen
Quoted 5 lines · Morten K. Poulsen
Quoted 1 line

What seperates every mail in a digest of several mails?

I think the correct (as in RFC 2046) way to do it is to make the digest mail a multipart/digest, and have each mail be a part with content type message/rfc822.

Ok. Have an example of how such an RFC conformant thing actually looks?

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                -- A. P. J.
#3 lore raw
In reply to Mads Martin Joergensen
Quoted 8 lines · * Mads Martin Joergensen ([email protected]) [040901 07:36]:
Quoted 5 lines · Morten K. Poulsen
Quoted 1 line

What seperates every mail in a digest of several mails?

I think the correct (as in RFC 2046) way to do it is to make the digest mail a multipart/digest, and have each mail be a part with content type message/rfc822.

Ok. Have an example of how such an RFC conformant thing actually looks?

That's what the SuSE lists are doing. E.g.,

        echo|mail [email protected]

It's basically just a multipart message with the first part containing the index of the messages and then a part for each message with a content-type of 'message/rfc822' and a unique filename for each. These are nice because it's easy to split into a mailbox with formail although ezmlm+idx offers the choice between this and a single 822 message.

Signature · 1 line
-ckm
#4 lore raw
In reply to Mads Martin Joergensen

Quoting Mads Martin Joergensen <[email protected]>:

Quoted 5 lines
Quoted 3 lines

I think the correct (as in RFC 2046) way to do it is to make the digest mail a multipart/digest, and have each mail be a part with content type message/rfc822.

Ok. Have an example of how such an RFC conformant thing actually looks?

http://rfc.net/rfc1521.html#s7.2.4.
http://rfc.net/rfc2046.html#s5.1.5.

The example in 1521 is only multipart/digest, and the one in 2046 is a multipart/mixed with a text/plain part and a multipart/digest part.

I *think* ezmlm-idx creats a single multipart/digest (in MIME, VIRGIN and NATIVE modes), but I am not sure. As far as I can see, it also includes a MIXED mode, which is the same as the others, but with a content type of multipart/mixed on the main part, to work around a bug in Pine. RFC 1153 (oh, I love this kind of research) also describes a digest format, but it is non-MIME and ugly IMO. Let's ignore it :-)

Do we need a text part, or is multipart/{digest,mixed} enough?

Best regards,
Morten

--
Morten K. Poulsen <[email protected]>
http://www.afdelingp.dk/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.