diff options
| author | klm | 1998-05-02 19:20:36 +0000 |
|---|---|---|
| committer | klm | 1998-05-02 19:20:36 +0000 |
| commit | 526f751d8d0255d2c2142c2c8dfff528aa8de5ec (patch) | |
| tree | 8d1435f389d44068a4fdb3a01036213a3d00d16f /Mailman/Utils.py | |
| parent | fe1f893c8ff4a753f1d4e8d47133d9b0a38f12a9 (diff) | |
| download | mailman-526f751d8d0255d2c2142c2c8dfff528aa8de5ec.tar.gz mailman-526f751d8d0255d2c2142c2c8dfff528aa8de5ec.tar.zst mailman-526f751d8d0255d2c2142c2c8dfff528aa8de5ec.zip | |
.SaveForDigest():
- Digest messages now keep all headers except 'received',
'errors-to', and all 'x-*' ones (and any continuations of these).
- Mime digest messages now properly (i believe) contain mime
attachments. (The key was preserving the original content-type
header.)
- It may be that some more headers should be trimmed, ie for the sake
of the non-mime recipients - but actually, it doesn't look
cluttered, for the few sample messages i tried.
- The entries in the table-of-contents have the redundant
subject-prefix string removed.
Digest: Redundant "Vol" in masthead string removed.
I took a look at rfc 934 (thanks, barry), which is the pre-Mime standard
for encapsulating (nesting) messages in other messages, and it looks
like the key is to have an "encapsulation boundary" that starts with a
"-" dash - looks like mime extended from this. However, the old rule
for nesting an encapsulated message within another encapsulated
message is to insert a "- " space in front of the original
encapsulation boundary. Unfortunately, this would break mime
encapsulation, so i'm not implementing this part of the old
burstable-digests standard. The rest of it *may* be ok, though, in
case anyone has the old-style bursting readers...
Anyway, i've done about as much as i was hoping to do with the digests
format - i don't forsee devoting much more attention to features, just
to ironing out bugs.
Diffstat (limited to 'Mailman/Utils.py')
0 files changed, 0 insertions, 0 deletions
