RFC 1153 digests should not work around VM bug

Bug #887610 reported by Barry Warsaw
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Mark Sapiro

Bug Description

In RFC1153Digester.finish(), we have this comment:

            # This is not strictly conformant RFC 1153. The trailer is only
            # supposed to contain two lines, i.e. the "End of ... Digest" line
            # and the row of asterisks. If this screws up MUAs, the solution
            # is to add the footer as the last message in the RFC 1153 digest.
            # I just hate the way that VM does that and I think it's confusing
            # to users, so don't do it unless there's a clamor.

It is bogus that Mailman works around VM this way, so the code should be fixed to fully conform to RFC 1153. While this bug report is specifically targeted to Mailman 3, it also affects MM2.1, but I'll let Mark decide the priority of that bugtask.

Tags: mailman3

Related branches

Revision history for this message
Mark Sapiro (msapiro) wrote :

I'll fix it for MM 2.1.15. I'll add digest_footer as the last RFC1153 message in the digest. I'm not completely sure how best to do this. I.e., should it be added as a message with an empty header, or with a single, non-standard (e.g.) "Footer:" header or with a "Subject: List footer" header. I lean towards the Subject: header, because it is clearly compliant with the RFC and probably works best in an exploded digest, but the empty header is probably best in an unexploded digest.

Barry Warsaw (barry)
Changed in mailman:
milestone: 3.0.0b1 → postponed
Barry Warsaw (barry)
Changed in mailman:
importance: Medium → Low
Mark Sapiro (msapiro)
Changed in mailman:
assignee: nobody → Mark Sapiro (msapiro)
milestone: postponed → 3.0.0b2
Mark Sapiro (msapiro)
Changed in mailman:
status: Triaged → In Progress
Barry Warsaw (barry)
Changed in mailman:
status: In Progress → Fix Committed
Barry Warsaw (barry)
Changed in mailman:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.