[Bug 1388614] [NEW] archive problem when an email got not subject

Public bug reported: Hey everybody, In one mailing list that use Mailman software, somebody send an empty email subject to mailing list. and this conversation completed without any problem, but seems links in archive pages got problem because that dude didn't use a subject for his email. you can see it here: http://lists.isfahanlug.org/pipermail/supervisors/2014-November/thread.html As i can see they use Mailman2 "version 2.1.15" on debian server. ** Affects: mailman Importance: Undecided Status: New ** Tags: archive mailman2 subject -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

I am unable to duplicate this problem. I see the problem in the archive index at http://lists.isfahanlug.org/pipermail/supervisors/2014-November/thread.html. I have downloaded the http://lists.isfahanlug.org/pipermail/supervisors/2014-November.txt.gz file (which by the way is doubly gzipped[1]) and can see the several messages therein with empty Subject: header, but when I process these through the pipermail Archiver, they get archived with a Subject: of 'No subject' (even in the 2014-November.txt file) and properly indexed. This may be a Debian Mailman bug, but it appears that this doesn't happen with standard GNU Mailman. You could try filing a Debian bug and see what they say. If you have access to the /var/lib/mailman/archives/private/supervisors.mbox/supervisors.mbox file, I would like to see at least one of these improperly indexed messages from that file. [1] The contents of http://lists.isfahanlug.org/pipermail/supervisors/2014-November.txt.gz is a file named 2014-November.txt, but this is actually a gzipped file which needs to be renamed 2014-November.txt.gz and gunzipped again to get the plain text. This may also be a Debian bug (I've seen it before). ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Incomplete ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

Note that the /var/lib/mailman/archives/private/supervisors.mbox/supervisors.mbox can be accessed at the URL http://lists.isfahanlug.org/mailman/private/supervisors.mbox/supervisors.mbo..., but this requires authentication with a list member's email address and list password. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

Here's the file you asked (only couple of emails that produce this bug). I will ask their sys admin to ungunzip that file again to see that would solve the problem or not. ** Attachment added: "mbox file" https://bugs.launchpad.net/mailman/+bug/1388614/+attachment/4253181/+files/s... -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

Thank you for the mbox. It is sufficient for me to duplicate the problem. I am working on it. ** Changed in: mailman Status: Incomplete => In Progress ** Changed in: mailman Milestone: None => 2.1.19 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

The problem was messages with 'Subject: Re:' only. The Re: fooled the archiver into thinking the message had a Subject: even though the Re: was later stripped leaving an empty Subject:. ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.19 => 2.1.19rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions
participants (3)
-
Bersam Karbasion
-
Launchpad Bug Tracker
-
Mark Sapiro