From mark at msapiro.net Tue Nov 1 21:48:57 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 01 Nov 2011 20:48:57 -0000 Subject: [Bug 862675] Re: Changes to a list (subscribe, unsubscribe, etc.) can be lost. References: <20110929185908.15075.36468.malonedeb@chaenomeles.canonical.com> Message-ID: <20111101204858.25990.4273.launchpad@soybean.canonical.com> *** This bug is a duplicate of bug 266464 *** https://bugs.launchpad.net/bugs/266464 ** This bug has been marked a duplicate of bug 266464 Subscriber "disappears" after subscription -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/862675 Title: Changes to a list (subscribe, unsubscribe, etc.) can be lost. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/862675/+subscriptions From mark at msapiro.net Tue Nov 1 21:50:08 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 01 Nov 2011 20:50:08 -0000 Subject: [Bug 266464] Re: Subscriber "disappears" after subscription References: <20080905193221.27052.50410.launchpad@forster.canonical.com> Message-ID: <20111101205008.1648.23625.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Confirmed => Fix Committed ** Changed in: mailman Milestone: 2.1-stable => 2.1.15 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266464 Title: Subscriber "disappears" after subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266464/+subscriptions From 885715 at bugs.launchpad.net Thu Nov 3 15:45:01 2011 From: 885715 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 03 Nov 2011 14:45:01 -0000 Subject: [Bug 885715] [NEW] Mailman should add a Received header References: <20111103144501.6216.73421.malonedeb@gac.canonical.com> Message-ID: <20111103144501.6216.73421.malonedeb@gac.canonical.com> Public bug reported: When the LMTP runner or any other injection vector receives a message, it should add a Received header to indicate the time at which Mailman got the message. Use case: there is a spam filter between the incoming MTA and Mailman, and the message sits in the spam filter for a while before its administrator accepts the message. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/885715 Title: Mailman should add a Received header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/885715/+subscriptions From 886296 at bugs.launchpad.net Fri Nov 4 19:44:44 2011 From: 886296 at bugs.launchpad.net (Kevin Fenzi) Date: Fri, 04 Nov 2011 18:44:44 -0000 Subject: [Bug 886296] [NEW] Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Public bug reported: The DSN bouncer handler can't seem to parse out when a bounce is generated due to an inactive google account. See attached bounce file for example. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions From 886296 at bugs.launchpad.net Fri Nov 4 19:44:44 2011 From: 886296 at bugs.launchpad.net (Kevin Fenzi) Date: Fri, 04 Nov 2011 18:44:44 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111104184444.5805.6651.malone@gac.canonical.com> ** Attachment added: "bounce from a inactive googlemail user" https://bugs.launchpad.net/bugs/886296/+attachment/2585519/+files/googlebounce -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions From mark at msapiro.net Fri Nov 4 20:09:38 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 04 Nov 2011 19:09:38 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111104190938.18116.84454.malone@chaenomeles.canonical.com> The example DSN attached is a "delay" message. If Mailman did recognize it, it would just be ignored anyway. If we are going to recognize it, it would help if we had the entire, raw message source with all headers rather than what appears to be an MUA's rendering of it. More importantly, what does the ultimate "I give up" DSN look like? ** 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/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions From 886296 at bugs.launchpad.net Fri Nov 4 21:17:28 2011 From: 886296 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 04 Nov 2011 20:17:28 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111104201728.2288.46657.launchpad@wampee.canonical.com> ** Also affects: flufl.bounce Importance: Undecided Status: New ** Changed in: flufl.bounce Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/886296/+subscriptions From curtis.hovey at canonical.com Sun Nov 6 13:52:39 2011 From: curtis.hovey at canonical.com (Curtis Hovey) Date: Sun, 06 Nov 2011 12:52:39 -0000 Subject: [Bug 317453] Re: Atom (/RSS?) feeds of Mailing lists References: <20090115122938.10057.89695.malonedeb@gangotri.canonical.com> Message-ID: <20111106125240.4293.9552.launchpad@soybean.canonical.com> ** Tags added: ml-archive-sucks -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/317453 Title: Atom (/RSS?) feeds of Mailing lists To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/317453/+subscriptions From 886296 at bugs.launchpad.net Sun Nov 6 18:28:16 2011 From: 886296 at bugs.launchpad.net (Kevin Fenzi) Date: Sun, 06 Nov 2011 17:28:16 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111106172816.5631.4947.malone@soybean.canonical.com> Yes, I think ideally this kind of message would best be ignored instead of passed on to the admin unprocessed. >From downstream report about the ultimate "I give up" DSN: "I haven't seen any. Maybe the final error message is recognized properly, maybe the user can re-enable his Google account before time-out." Attaching email... -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/886296/+subscriptions From 886296 at bugs.launchpad.net Sun Nov 6 18:28:37 2011 From: 886296 at bugs.launchpad.net (Kevin Fenzi) Date: Sun, 06 Nov 2011 17:28:37 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111106172837.6933.1588.malone@gac.canonical.com> email showing issue ** Attachment added: "google-delay.mbox" https://bugs.launchpad.net/mailman/+bug/886296/+attachment/2587446/+files/google-delay.mbox -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/886296/+subscriptions From mark at msapiro.net Sun Nov 6 19:32:42 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 06 Nov 2011 18:32:42 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111106183242.17287.1297.malone@chaenomeles.canonical.com> What Mailman version is failing to recognize this DSN? It turns out that this DSN has been recognized as a warning only and ignored since Mailman 2.1.11. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: Incomplete => Fix Released ** Changed in: mailman Milestone: None => 2.1-stable -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/886296/+subscriptions From 886296 at bugs.launchpad.net Sun Nov 6 19:49:15 2011 From: 886296 at bugs.launchpad.net (Kevin Fenzi) Date: Sun, 06 Nov 2011 18:49:15 -0000 Subject: [Bug 886296] Re: Improve DSN handling for google 'inactive' accounts References: <20111104184444.5805.4293.malonedeb@gac.canonical.com> Message-ID: <20111106184915.17175.754.malone@chaenomeles.canonical.com> Looks like 2.1.9, so that would explain it. ;( -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/886296/+subscriptions From 317453 at bugs.launchpad.net Mon Nov 7 18:31:44 2011 From: 317453 at bugs.launchpad.net (Don Kirkby) Date: Mon, 07 Nov 2011 17:31:44 -0000 Subject: [Bug 317453] Re: Atom (/RSS?) feeds of Mailing lists References: <20090115122938.10057.89695.malonedeb@gangotri.canonical.com> Message-ID: <20111107173144.5805.94221.malone@gac.canonical.com> Glad to see this is in the planning stages. Good luck with it. One strange thing is that when I searched for RSS mailing list, I didn't find this bug. Maybe this comment will change that. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/317453 Title: Atom (/RSS?) feeds of Mailing lists To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/317453/+subscriptions From 317453 at bugs.launchpad.net Mon Nov 7 21:32:13 2011 From: 317453 at bugs.launchpad.net (Robert Collins) Date: Mon, 07 Nov 2011 20:32:13 -0000 Subject: [Bug 317453] Re: Atom (/RSS?) feeds of Mailing lists References: <20090115122938.10057.89695.malonedeb@gangotri.canonical.com> <20111107173144.5805.94221.malone@gac.canonical.com> Message-ID: We don't full text index comments (performance reasons) - we may in future when we upgrade our search engine. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/317453 Title: Atom (/RSS?) feeds of Mailing lists To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/317453/+subscriptions From 887610 at bugs.launchpad.net Tue Nov 8 16:26:53 2011 From: 887610 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 08 Nov 2011 15:26:53 -0000 Subject: [Bug 887610] [NEW] RFC 1153 digests should not work around VM bug References: <20111108152653.12565.65763.malonedeb@soybean.canonical.com> Message-ID: <20111108152653.12565.65763.malonedeb@soybean.canonical.com> Public bug reported: 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. ** Affects: mailman Importance: Medium Status: Triaged ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/887610 Title: RFC 1153 digests should not work around VM bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/887610/+subscriptions From mark at msapiro.net Tue Nov 8 17:22:26 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 08 Nov 2011 16:22:26 -0000 Subject: [Bug 887610] Re: RFC 1153 digests should not work around VM bug References: <20111108152653.12565.65763.malonedeb@soybean.canonical.com> Message-ID: <20111108162226.6835.54972.malone@gac.canonical.com> 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. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/887610 Title: RFC 1153 digests should not work around VM bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/887610/+subscriptions From 317453 at bugs.launchpad.net Tue Nov 8 19:12:08 2011 From: 317453 at bugs.launchpad.net (Don Kirkby) Date: Tue, 08 Nov 2011 18:12:08 -0000 Subject: [Bug 317453] Re: Atom or RSS feeds of Mailing lists References: <20090115122938.10057.89695.malonedeb@gangotri.canonical.com> Message-ID: <20111108181209.7423.74732.launchpad@chaenomeles.canonical.com> ** Summary changed: - Atom (/RSS?) feeds of Mailing lists + Atom or RSS feeds of Mailing lists -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/317453 Title: Atom or RSS feeds of Mailing lists To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/317453/+subscriptions From 266805 at bugs.launchpad.net Sat Nov 12 23:22:10 2011 From: 266805 at bugs.launchpad.net (Joseph Fall) Date: Sat, 12 Nov 2011 22:22:10 -0000 Subject: [Bug 266805] Re: Digest header / masthead.txt changes References: <20080905194251.1806.31287.launchpad@forster.canonical.com> Message-ID: <20111112222210.16107.51249.malone@chaenomeles.canonical.com> I ran into this one - and it was particularly vexing since I do not have access to my list's masthead.txt through my host. It seems to me, if the goal is to maintain the same basic default behaviour, this could be fixed most easily by: 1) setting the default digest_header to be the contents of masthead.txt 2) supplying an empty masthead.txt file This allows most site admins to edit the digest_header via the web interface, while still allowing a masthead to be defined, if needed. But I'm probably missing something crucial here.... -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266805 Title: Digest header / masthead.txt changes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266805/+subscriptions From 889635 at bugs.launchpad.net Sat Nov 12 23:45:04 2011 From: 889635 at bugs.launchpad.net (Joseph Fall) Date: Sat, 12 Nov 2011 22:45:04 -0000 Subject: [Bug 889635] [NEW] Per-list configurable message headers for digests References: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> Message-ID: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> Public bug reported: Digest messages are sent out with a partial set of headers for each message. The list of headers kept for each plain-text digested message is configured by the setting: PLAIN_DIGEST_KEEP_HEADERS = [ 'Message', 'Date', 'From', 'Subject', 'To', 'Cc', 'Message-ID', 'Keywords', 'Content-Type', ] My users are very perplexed and frustrated by the e-mail headers included in the digest - in particular, the Message-ID and Content-Type are meaningless, and the To header is repetitive. All this "noise" clutters up the content and makes the digest harder to read. Given that this is a plain-text digest, with the headers listed in the message body, I don't really see an RFC issue here? Yet they can only be configured using a list-wide override in mm_cfg.py I would be willing to work on this to allow a list admin to override the plain digest headers using the web interface, but want to hear from the development team if this is a patch they would be willing to consider before I invest the time. thanks. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions From mark at msapiro.net Sat Nov 12 23:55:09 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 12 Nov 2011 22:55:09 -0000 Subject: [Bug 266805] Re: Digest header / masthead.txt changes References: <20080905194251.1806.31287.launchpad@forster.canonical.com> Message-ID: <20111112225510.5621.33005.malone@wampee.canonical.com> I will add the digest masthead (masthead.txt template) to the files that can be edited via the "Edit the public HTML pages and text files" link on the list admin web pages. ** Changed in: mailman Importance: Medium => Wishlist ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.15 ** 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/266805 Title: Digest header / masthead.txt changes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266805/+subscriptions From mark at msapiro.net Sun Nov 13 00:41:28 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 12 Nov 2011 23:41:28 -0000 Subject: [Bug 889635] Re: Per-list configurable message headers for digests References: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> Message-ID: <20111112234128.4730.20100.malone@wampee.canonical.com> The format of the plain digest is specified in RFC 1153 which says in part "If they exist in the original message header, the following lines must be retained as-is in the reconstructed header: Date:, From:, To:, Cc:, Subject:, Message-ID:, and Keywords:, rearranged to appear in that order." The only headers included in the plain digest which are not in that list are Message: and Content-Type:. I can understand that Content-Type is not too useful since the message has been scrubbed to text/plain, but it can retain parameters such as format=flowed which might be useful to some. I would consider removing Content-Type: from the default list, but only after surveying the mailman-users at python.org list to see if there are objections. BTW, In current Mailman, the Defaults.py setting for PLAIN_DIGEST_KEEP_HEADERS is PLAIN_DIGEST_KEEP_HEADERS = [ 'Message', # RFC 1153 headers in order 'Date', 'From', 'To', 'Cc', 'Subject', 'Message-ID', 'Keywords', 'Content-Type', ] which puts the Subject: in the order specified by the RFC. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions From mark at msapiro.net Sun Nov 13 00:56:09 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 12 Nov 2011 23:56:09 -0000 Subject: [Bug 266805] Re: Digest header / masthead.txt changes References: <20080905194251.1806.31287.launchpad@forster.canonical.com> Message-ID: <20111112235609.26928.35801.launchpad@soybean.canonical.com> ** 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/266805 Title: Digest header / masthead.txt changes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266805/+subscriptions From 889635 at bugs.launchpad.net Sun Nov 13 01:30:08 2011 From: 889635 at bugs.launchpad.net (Joseph Fall) Date: Sun, 13 Nov 2011 00:30:08 -0000 Subject: [Bug 889635] Re: Per-list configurable message headers for digests References: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> <20111112234128.4730.20100.malone@wampee.canonical.com> Message-ID: <02DED8E9-4A98-45F9-9436-ECBFC3B22D30@gmail.com> Thanks Mark - excellent info. It's interesting that the example given in rfc1153 looks exactly like what I'd like to see - contrary to the actual spec... Date: ddd, dd mmm yy hh:mm:ss zzz From: Joe User Subject: Message One Subject This is the message body of the first message. Joe ------------------------------ Date: ddd, dd mmm yy hh:mm:ss zzz From: Jane User Subject: Message Two Subject This is the body of message two. Jane Appreciate the quick reply! ...Joseph On 12-Nov-11, at 3:41 PM, Mark Sapiro wrote: > The format of the plain digest is specified in RFC 1153 - > editor.org/rfc/rfc1153.txt> which says in part "If they exist in the > original message header, the following lines must be retained as-is in > the reconstructed header: Date:, From:, To:, Cc:, Subject:, Message- > ID:, > and Keywords:, rearranged to appear in that order." > > The only headers included in the plain digest which are not in that > list > are Message: and Content-Type:. I can understand that Content-Type is > not too useful since the message has been scrubbed to text/plain, > but it > can retain parameters such as format=flowed which might be useful to > some. > > I would consider removing Content-Type: from the default list, but > only > after surveying the mailman-users at python.org list to see if there are > objections. > > BTW, In current Mailman, the Defaults.py setting for > PLAIN_DIGEST_KEEP_HEADERS is > > PLAIN_DIGEST_KEEP_HEADERS = [ > 'Message', > # RFC 1153 headers in order > 'Date', 'From', 'To', 'Cc', 'Subject', 'Message-ID', 'Keywords', > 'Content-Type', > ] > > which puts the Subject: in the order specified by the RFC. > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/889635 > > Title: > Per-list configurable message headers for digests > > Status in GNU Mailman: > New > > Bug description: > Digest messages are sent out with a partial set of headers for each > message. > The list of headers kept for each plain-text digested message is > configured by the setting: > > PLAIN_DIGEST_KEEP_HEADERS = [ > 'Message', 'Date', 'From', > 'Subject', 'To', 'Cc', > 'Message-ID', 'Keywords', > 'Content-Type', > ] > > My users are very perplexed and frustrated by the e-mail headers > included in the digest - in particular, the Message-ID and Content- > Type are meaningless, and the To header is repetitive. All this > "noise" clutters up the content and makes the digest harder to read. > > Given that this is a plain-text digest, with the headers listed in > the > message body, I don't really see an RFC issue here? Yet they can > only be configured using a list-wide override in mm_cfg.py > > I would be willing to work on this to allow a list admin to > override the plain digest headers using the web interface, but want > to hear from the development team if this is a patch they would be > willing to consider before I invest the time. > thanks. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions From 889829 at bugs.launchpad.net Sun Nov 13 14:49:04 2011 From: 889829 at bugs.launchpad.net (Harry Enke) Date: Sun, 13 Nov 2011 13:49:04 -0000 Subject: [Bug 889829] [NEW] setup takes zope interface 3.5.1, but needs 3.8.0 References: <20111113134904.27435.80451.malonedeb@gac.canonical.com> Message-ID: <20111113134904.27435.80451.malonedeb@gac.canonical.com> Public bug reported: separate installation of zope interface 3.8.0 fixes the issue, afterwards mailman 3.0.0.8a OS: Scientific Linux 6.1, Python 2.6.6 ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889829 Title: setup takes zope interface 3.5.1, but needs 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889829/+subscriptions From 889829 at bugs.launchpad.net Sun Nov 13 17:51:50 2011 From: 889829 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 13 Nov 2011 16:51:50 -0000 Subject: [Bug 889829] Re: setup takes zope interface 3.5.1, but needs 3.8.0 References: <20111113134904.27435.80451.malonedeb@gac.canonical.com> Message-ID: <20111113165150.4730.53653.launchpad@wampee.canonical.com> ** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889829 Title: setup takes zope interface 3.5.1, but needs 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889829/+subscriptions From 889829 at bugs.launchpad.net Sun Nov 13 19:17:08 2011 From: 889829 at bugs.launchpad.net (Harry Enke) Date: Sun, 13 Nov 2011 18:17:08 -0000 Subject: [Bug 889829] Re: setup takes zope interface 3.5.1, but needs 3.8.0 References: <20111113134904.27435.80451.malonedeb@gac.canonical.com> Message-ID: <20111113181708.27657.64226.malone@soybean.canonical.com> no previous mailman installation, ran "python setup.py" -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889829 Title: setup takes zope interface 3.5.1, but needs 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889829/+subscriptions From 889635 at bugs.launchpad.net Sun Nov 13 20:06:04 2011 From: 889635 at bugs.launchpad.net (Joseph Fall) Date: Sun, 13 Nov 2011 19:06:04 -0000 Subject: [Bug 889635] Re: Per-list configurable message headers for digests References: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> Message-ID: <20111113190605.15513.40641.malone@chaenomeles.canonical.com> More information about RFC 1153... This is an "experimental" RFC, and a fairly old one at that. The IETF definition: "Experimental RFCs are for specifications that may be interesting, but for which it is unclear if there will be much interest in implementing them, or whether they will work once deployed. That is, a specification might solve a problem, but if it is not clear that many people think that the problem is important, or think that they will bother fixing the problem with the specification, the specification might be labeled an Experimental RFC. If, later, the specification becomes popular (or proves that it works well), it can be re-issued as a standards-track RFC. Experimental RFCs are also used to get people to experiment with a technology that looks like it might be standards-track material, but for which there are still unanswered questions. " http://www.ietf.org/tao.html#anchor45 Given its vintage and the decline of e-mail digests, seems unlikely to ever make it to "standards-track. So, while it does make a very reasonable choice for a default, I don't see there's much of a case for forcing list owners to adhere, especially for plain-text digests. So I'll pose the question again - if I push an enhancement to allow the DIGEST_KEEP_HEADERS to be administered on a per-list basis, would you be willing to review and consider merging it in? thanks Mark. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions From mark at msapiro.net Sun Nov 13 22:18:30 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 13 Nov 2011 21:18:30 -0000 Subject: [Bug 889968] [NEW] Response to email approval of held message is misleading References: <20111113211830.26626.67071.malonedeb@soybean.canonical.com> Message-ID: <20111113211830.26626.67071.malonedeb@soybean.canonical.com> Public bug reported: (From a recent post to mailman-users at python.org) I usually use the web interface for approving messages. But I occasionally do it via Email. When I do, I get a response back that looks like this: The results of your email command are provided below. Attached is your original message. - Results: Confirmation succeeded - Unprocessed: Approved: - Done. ---- CUT HERE ----------------------- To me at least, this suggests that the message has been rejected, not approved, as the text says that the approval command was not processed. I know this isn't the case because I see the message posted to the list, but when I initially saw it, I had a panic as I thought I'd lost a message for the list. Is it possible to fix this so that the message is more clear about what has happened? The "Confirmation succeeded" message is not very explanatory, and seen in isolation doesn't really tell you anythying about whether the message was approved or rejected. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Confirmed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889968 Title: Response to email approval of held message is misleading To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889968/+subscriptions From mark at msapiro.net Sun Nov 13 22:41:55 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 13 Nov 2011 21:41:55 -0000 Subject: [Bug 889968] Re: Response to email approval of held message is misleading References: <20111113211830.26626.67071.malonedeb@soybean.canonical.com> Message-ID: <20111113214156.16328.96306.malone@chaenomeles.canonical.com> Fixed by appending (Approve) or (Discard) as appropriate to the Confirmation succeeded line and removing any Approve(d): line from the Unprocessed: list. ** Changed in: mailman Status: Confirmed => 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/889968 Title: Response to email approval of held message is misleading To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889968/+subscriptions From noreply at launchpad.net Mon Nov 14 15:10:19 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Mon, 14 Nov 2011 14:10:19 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 22: fixed issue in get_domain method: return None if domain cannot be found, not an empty list. Message-ID: <20111114141019.4201.73693.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 22 committer: Florian Fuchs branch nick: mailman.client timestamp: Mon 2011-11-14 15:07:48 +0100 message: fixed issue in get_domain method: return None if domain cannot be found, not an empty list. modified: mailman/client/_client.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 486 bytes Desc: not available URL: From 889635 at bugs.launchpad.net Tue Nov 15 10:48:51 2011 From: 889635 at bugs.launchpad.net (Joseph Fall) Date: Tue, 15 Nov 2011 09:48:51 -0000 Subject: [Bug 889635] Re: Per-list configurable message headers for digests References: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> Message-ID: <20111115094851.2841.17791.malone@wampee.canonical.com> Browsing the source for the 3.x series, it looks like one possible way to handle this might be to add a new digest format - say "Flexible Plain Text Digest". class FlexibleTextDigester(RFC1153Digester): would simply override a few things in the init() method to pull in user- defined alternatives to the RFC1153 defaults from the mlist object to override the config settings, but otherwise rely on the base digester to do the work. That would ensure no existing lists using RFC1153 plain text digests would be affected in any way. Of course MailingList(Model) would need to define a new field(s) - DB schema change - that's a bummer. I saw a few other feature requests for non-compliant RFC1153 digests that might be consolidated with this approach? BTW - looks like there is a minor coding error (v. 3.0.0a8+ ) on line 242 in runners.digest.py class RFC1153Digester(Digester): def add_message(self, msg, count): .... for header in config.digests.plain_digest_keep_headers.split(): ... should read for header in self._keepers: I doubt this causes a bug at present, but has the potential to, if I've understood the code correctly. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions From 890675 at bugs.launchpad.net Tue Nov 15 14:12:54 2011 From: 890675 at bugs.launchpad.net (blacktav) Date: Tue, 15 Nov 2011 13:12:54 -0000 Subject: [Bug 890675] Re: test_moderation fails on approved_at date comparison References: <20111115131254.3573.65620.malonedeb@wampee.canonical.com> Message-ID: <20111115131255.3573.50578.malone@wampee.canonical.com> ** Patch added: "diff from "bzr diff -p1 test_moder..."" https://bugs.launchpad.net/bugs/890675/+attachment/2597687/+files/test_moderation.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/890675 Title: test_moderation fails on approved_at date comparison To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/890675/+subscriptions From 890675 at bugs.launchpad.net Tue Nov 15 14:12:54 2011 From: 890675 at bugs.launchpad.net (blacktav) Date: Tue, 15 Nov 2011 13:12:54 -0000 Subject: [Bug 890675] [NEW] test_moderation fails on approved_at date comparison References: <20111115131254.3573.65620.malonedeb@wampee.canonical.com> Message-ID: <20111115131254.3573.65620.malonedeb@wampee.canonical.com> Public bug reported: Tests fail with Failure in test test_accepted_message_gets_posted (mailman.app.tests.test_moderation.TestModeration) Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 318, in run testMethod() File "/home/devel/mailman/src/mailman/app/tests/test_moderation.py", line 83, in test_accepted_message_gets_posted 'Mon, 01 Aug 2005 07:49:23 -') File "/usr/lib64/python2.7/unittest/case.py", line 494, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib64/python2.7/unittest/case.py", line 487, in _baseAssertEqual raise self.failureException(msg) AssertionError: 'Mon, 01 Aug 2005 07:49:23 +' != u'Mon, 01 Aug 2005 07:49:23 -' which seems to include remnants of UTC offset in its comparison perhaps it should be mailman/src/mailman/app/tests/test_moderation.py: line 82 self.assertEqual(message['x-mailman-approved-at'][:-5], 'Mon, 01 Aug 2005 07:49:23 ') ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/890675 Title: test_moderation fails on approved_at date comparison To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/890675/+subscriptions From 890675 at bugs.launchpad.net Tue Nov 15 16:01:21 2011 From: 890675 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 15 Nov 2011 15:01:21 -0000 Subject: [Bug 890675] Re: test_moderation fails on approved_at date comparison References: <20111115131254.3573.65620.malonedeb@wampee.canonical.com> Message-ID: <20111115150122.21595.27399.launchpad@soybean.canonical.com> ** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/890675 Title: test_moderation fails on approved_at date comparison To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/890675/+subscriptions From 883193 at bugs.launchpad.net Wed Nov 16 03:41:40 2011 From: 883193 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 16 Nov 2011 02:41:40 -0000 Subject: [Bug 883193] Re: Remove the X- prefix from some headers References: <20111028171715.19571.45030.malonedeb@soybean.canonical.com> Message-ID: <20111116024140.2742.73313.malone@wampee.canonical.com> See http://www.faqs.org/rfcs/rfc2616.html User-Agent description for possible syntax of List-Agent. There's also currently some debate in the mailing list about whether it should be Mediator, User-Agent, or List-Agent. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions From 883193 at bugs.launchpad.net Wed Nov 16 03:44:00 2011 From: 883193 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 16 Nov 2011 02:44:00 -0000 Subject: [Bug 883193] Re: Remove the X- prefix from some headers References: <20111028171715.19571.45030.malonedeb@soybean.canonical.com> Message-ID: <20111116024400.3052.204.malone@wampee.canonical.com> See also this draft: http://www.blackops.org/~msk/draft-kucherawy- received-state.txt -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions From 885715 at bugs.launchpad.net Wed Nov 16 03:45:35 2011 From: 885715 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 16 Nov 2011 02:45:35 -0000 Subject: [Bug 885715] Re: Mailman should add a Received header References: <20111103144501.6216.73421.malonedeb@gac.canonical.com> Message-ID: <20111116024535.21792.40620.malone@soybean.canonical.com> See also http://www.blackops.org/~msk/draft-kucherawy-received-state.txt -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/885715 Title: Mailman should add a Received header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/885715/+subscriptions From 889635 at bugs.launchpad.net Wed Nov 16 04:01:22 2011 From: 889635 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 16 Nov 2011 03:01:22 -0000 Subject: [Bug 889635] Re: Per-list configurable message headers for digests References: <20111112224504.15810.47292.malonedeb@chaenomeles.canonical.com> Message-ID: <20111116030122.2886.52347.launchpad@gac.canonical.com> ** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions From 891676 at bugs.launchpad.net Thu Nov 17 16:49:40 2011 From: 891676 at bugs.launchpad.net (Roman Sokolkov) Date: Thu, 17 Nov 2011 15:49:40 -0000 Subject: [Bug 891676] [NEW] topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Public bug reported: Hi I use mailman-2.1.14-6 on fedora 15 When I use english regex topics, all works good. If I use russian regex, subscribers-members of a topic don't receive e-mails. Bacause subject doesn't match with regex. In source code(/usr/lib/mailman/Mailman/Handlers/Tagger.py) I found that subject doesn't modified from MIME format. If it english all seem good, but in my case I saw: pattern is "" line is "=?KOI8-R?Q?=C8=D5=CA?=" I create simple patch that use decode_header function from email module ** Affects: mailman Importance: Undecided Status: New ** Tags: charset header mailman topics -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From 891676 at bugs.launchpad.net Thu Nov 17 16:49:40 2011 From: 891676 at bugs.launchpad.net (Roman Sokolkov) Date: Thu, 17 Nov 2011 15:49:40 -0000 Subject: [Bug 891676] Re: topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111117154940.3920.97590.malone@wampee.canonical.com> ** Attachment added: "patch for topics" https://bugs.launchpad.net/bugs/891676/+attachment/2599733/+files/Tagger.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From mark at msapiro.net Thu Nov 17 17:40:00 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 17 Nov 2011 16:40:00 -0000 Subject: [Bug 891676] Re: topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111117164000.20665.71134.malone@soybean.canonical.com> Thanks for your report. This issue affects messages with RFC 2047 encoded Subject: and/or Keywords: headers as well as messages with encoded bodies containing Subject: and/or Keywords: pseudo-headers. The patch at comment #1 is incomplete as it doesn't take into account pseudo-headers and only decodes the first encoded word in an RFC 2047 encoded header. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.15 ** 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/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From mark at msapiro.net Thu Nov 17 18:12:16 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 17 Nov 2011 17:12:16 -0000 Subject: [Bug 891676] Re: topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111117171216.20863.72408.malone@soybean.canonical.com> Attached is a tentative patch for this issue. There will still be problems if the encoding of the regexp doesn't match that of the message header. E.g., if the characters in the regexp are encoded as koi8-r and the Subject header is encoded as utf-8. What do you think of this patch? ** Patch added: "Tentative patch for this issue" https://bugs.launchpad.net/mailman/+bug/891676/+attachment/2599840/+files/Tagger.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From mark at msapiro.net Thu Nov 17 21:46:36 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 17 Nov 2011 20:46:36 -0000 Subject: [Bug 891676] Re: topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111117204636.3810.84511.malone@wampee.canonical.com> I have revised the patch to decode the headers in the character set of the list's preferred language which should match the character set of the topics regexps. ** Patch added: "Patch for this issue." https://bugs.launchpad.net/mailman/+bug/891676/+attachment/2600032/+files/Tagger.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From mark at msapiro.net Thu Nov 17 22:06:08 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 17 Nov 2011 21:06:08 -0000 Subject: [Bug 891676] Re: topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111117210608.4156.43102.malone@wampee.canonical.com> I've committed the fix in Comment #4. Note that this still does not address the issue with pseudo-headers in the message body if the charset of the message body is not compatible with that of the list's preferred language. I don't intend to fix that unless it proves to be an issue in practice. ** 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/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From 891676 at bugs.launchpad.net Fri Nov 18 06:01:44 2011 From: 891676 at bugs.launchpad.net (Roman Sokolkov) Date: Fri, 18 Nov 2011 05:01:44 -0000 Subject: [Bug 891676] Re: topics don't work with national(russian) languages References: <20111117154940.3920.84558.malonedeb@wampee.canonical.com> Message-ID: <20111118050144.4177.81881.malone@soybean.canonical.com> Thanks for a patch, Mark! all works good. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/891676 Title: topics don't work with national(russian) languages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions From 893290 at bugs.launchpad.net Mon Nov 21 21:13:24 2011 From: 893290 at bugs.launchpad.net (=?utf-8?q?Ignacy_Gaw=C4=99dzki?=) Date: Mon, 21 Nov 2011 20:13:24 -0000 Subject: [Bug 893290] [NEW] "Re:" matching not liberal enough References: <20111121201324.477.84184.malonedeb@wampee.canonical.com> Message-ID: <20111121201324.477.84184.malonedeb@wampee.canonical.com> Public bug reported: In Handlers/CookHeaders.py, the regex to match a "Re" line is not liberal enough. French MUAs often use a "Re :" tag, with a space before the colon. I suggest that instead of '((RE|AW|SV|VS)(\[\d+\])?:\s*)+', it should be '((RE|AW|SV|VS)\s*(\[\d+\])?\s*:\s*)+'. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/893290 Title: "Re:" matching not liberal enough To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/893290/+subscriptions From mark at msapiro.net Wed Nov 23 01:54:05 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 23 Nov 2011 00:54:05 -0000 Subject: [Bug 893290] Re: "Re:" matching not liberal enough References: <20111121201324.477.84184.malonedeb@wampee.canonical.com> Message-ID: <20111123005406.32255.61439.launchpad@gac.canonical.com> ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.15 ** 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/893290 Title: "Re:" matching not liberal enough To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/893290/+subscriptions From 897103 at bugs.launchpad.net Mon Nov 28 09:15:18 2011 From: 897103 at bugs.launchpad.net (Bernd Wurst) Date: Mon, 28 Nov 2011 08:15:18 -0000 Subject: [Bug 897103] [NEW] Crash when moderating messages with empty sender address References: <20111128081518.24333.79010.malonedeb@soybean.canonical.com> Message-ID: <20111128081518.24333.79010.malonedeb@soybean.canonical.com> Public bug reported: A message in the moderation queue has had an empty sender address ("From: foobar <>"). This leads to the folowing traceback: admin(9230): [----- Mailman Version: 2.1.14 -----] admin(9230): [----- Traceback ------] admin(9230): Traceback (most recent call last): admin(9230): File "/home/.internal/mailman/scripts/driver", line 112, in run_main admin(9230): main() admin(9230): File "/home/.internal/mailman/Mailman/Cgi/admindb.py", line 167, in main admin(9230): process_form(mlist, doc, cgidata) admin(9230): File "/home/.internal/mailman/Mailman/Cgi/admindb.py", line 718, in process_form admin(9230): if id not in senderactions[sender]['message_ids']: admin(9230): KeyError: 'message_ids' ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/897103 Title: Crash when moderating messages with empty sender address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/897103/+subscriptions From 860159 at bugs.launchpad.net Tue Nov 29 11:18:17 2011 From: 860159 at bugs.launchpad.net (Stephane Wirtel (OpenERP)) Date: Tue, 29 Nov 2011 10:18:17 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111129101817.23025.16195.malone@wampee.canonical.com> Hi all, I'm interested by the support of PostgreSQL by Mailman, is there some news for a future release with this feature ? Regards, -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From barry at list.org Tue Nov 29 13:18:45 2011 From: barry at list.org (Barry Warsaw) Date: Tue, 29 Nov 2011 07:18:45 -0500 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres In-Reply-To: <20111129101817.23025.16195.malone@wampee.canonical.com> References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> <20111129101817.23025.16195.malone@wampee.canonical.com> Message-ID: <20111129071845.284587b9@limelight.wooz.org> On Nov 29, 2011, at 10:18 AM, Stephane Wirtel \(OpenERP\) wrote: >I'm interested by the support of PostgreSQL by Mailman, is there some >news for a future release with this feature ? PostgreSQL support is in Mailman 3 bzr. It will be available in beta 1, but I have no eta on that at the moment. -Barry From 860159 at bugs.launchpad.net Tue Nov 29 13:18:45 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 29 Nov 2011 12:18:45 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> <20111129101817.23025.16195.malone@wampee.canonical.com> Message-ID: <20111129071845.284587b9@limelight.wooz.org> On Nov 29, 2011, at 10:18 AM, Stephane Wirtel \(OpenERP\) wrote: >I'm interested by the support of PostgreSQL by Mailman, is there some >news for a future release with this feature ? PostgreSQL support is in Mailman 3 bzr. It will be available in beta 1, but I have no eta on that at the moment. -Barry -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From mark at msapiro.net Wed Nov 30 02:09:42 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 30 Nov 2011 01:09:42 -0000 Subject: [Bug 897103] Re: Crash when moderating messages with empty sender address References: <20111128081518.24333.79010.malonedeb@soybean.canonical.com> Message-ID: <20111130010942.20135.97102.malone@gac.canonical.com> I have fixed this by preventing the underlying cause from happening. If a message is held for which Mailman's Message.get_sender() method returns an empty string, the sender in the request.pck file will be recorded as ''. This will prevent the problem in the future, but it won't fix the crash if there is an existing held message entry in request.pck with a null sender. The crash can be avoided by going to the message detail page for the held message by following the number link next to the Subject: in the overview page and discarding the message from the detail page. Interestingly, for this issue to have occurred in the first place, in addition to the From: header having a null address, the same must have been true of a Sender: header if any and the envelope sender. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.15 ** 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/897103 Title: Crash when moderating messages with empty sender address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/897103/+subscriptions