From rob-launchpad.net at tigertech.com Wed Nov 1 19:10:59 2017 From: rob-launchpad.net at tigertech.com (Robert Mathews) Date: Wed, 01 Nov 2017 23:10:59 -0000 Subject: [Bug 558128] Re: remove 552 exception for SMTP perm/temp References: <20100408090629.1687.57975.launchpad@loganberry.canonical.com> Message-ID: <150957785946.9171.17239251988307988193.malone@wampee.canonical.com> >It is one retry every DELIVERY_RETRY_WAIT (default one hour) for DELIVERY_RETRY_PERIOD >(default 5 days) before giving up and returning failure. Granted, this is perhaps 719 >unnecessary retries, but is far from "infinite". Thanks for looking at this! It's definitely possible I'm just being an idiot here, but DELIVERY_RETRY_WAIT doesn't seem to be working properly. Mine was retrying nonstop, and I had tens of thousands of delivery attempts before I stopped it. A grep of the code indicates DELIVERY_RETRY_WAIT is defined in "Mailman/Defaults.py.in" but not used anywhere. "Mailman/Queue/OutgoingRunner.py" has some code that is trying to check the "deliver_after" time of a message, but that never gets set anywhere I can see. Is the code perhaps supposed to set a message's "deliver_after" to "time + DELIVERY_RETRY_WAIT" after a failure? But you're right that it would have eventually stopped by itself after five days, now that I look more closely at the code. My apologies for the hyperbolic description. >Also note the problem of an oversize digest can be entirely avoided by setting >digest_size_threshhold to a reasonable maximum. I agree. It *was* set to a reasonable default for the list in question, and then the list owner changed it to 0 for some reason. Grrr. I may have to patch our copy to prevent this. Perhaps there could be a mm.cfg.py option that allows site administrators to limit the maximum size that can be set, and prevent setting it to 0? >Finally. consider what happens if this is considered a "hard bounce". It means every >innocent digest member whose ISP rejects the oversize digest with a 552 will record a bounce >for that digest. In extreme cases, it could result in users delivery being disabled >and ultimately unsubscribed through no fault of their own. Yes, that's a reasonable concern. Of course, the same problem can happen for many other reasons too (digests rejected for spam, etc.). The only thing I can think of is that a hard "maximum digest limit" size set to a reasonable number sitewide would minimize this risk. However: while searching my logs for how many messages generate a 552 error, I came across this unfortunately common horror: "host smtp.secureserver.net[68.178.213.203] said: 552 5.2.0 Uczf1w00J3GnVuQ01 - Uczf1w00J3GnVuQ01czf95 This message has been rejected due to content judged to be spam by the internet community IB212" This is an awful abuse of the SMTP standard; it means that removing the magic "treat 552 as 452" code would trigger bounces in cases like this. So perhaps this bears more thinking about. Or perhaps the solution is simpler: When DELIVERY_RETRY_PERIOD is reached due to repeated 552 errors treated as 4xx errors, it looks like Mailman currently discards the message without incrementing the bounce count. Perhaps the code should maintain that special "don't increment the bounce score" treatment of 552 errors, but not retry delivery of the message? Or perhaps this is all irrelevant and the real problem is merely that I noticed high CPU usage on a server because DELIVERY_RETRY_WAIT is broken, and fixing that would make me and others neither notice nor care about the 552 thing. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558128 Title: remove 552 exception for SMTP perm/temp To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558128/+subscriptions From rob-launchpad.net at tigertech.com Wed Nov 1 19:37:13 2017 From: rob-launchpad.net at tigertech.com (Robert Mathews) Date: Wed, 01 Nov 2017 23:37:13 -0000 Subject: [Bug 558128] Re: remove 552 exception for SMTP perm/temp References: <20100408090629.1687.57975.launchpad@loganberry.canonical.com> Message-ID: <150957943394.4385.7040617517346589562.malone@chaenomeles.canonical.com> Just to add a little more: I checked the code and it appears that DELIVERY_RETRY_WAIT was added in 2.1.2, but then removed in 2.1.3 in favor of the RetryRunner having a 15 minute fixed delay: SLEEPTIME = mm_cfg.minutes(15) Unfortunately it looks like the DELIVERY_RETRY_WAIT constant was not removed then even though it stopped being used in the code. Perhaps this was intended to be: SLEEPTIME = mm_cfg.minutes(mm_cfg.DELIVERY_RETRY_WAIT) Looking more closely at my high CPU usage that triggered all this, it turns out that because we use VERP_PERSONALIZED_DELIVERIES and the list has hundreds of digest members, it was consuming almost that entire 15 minutes trying to send them all before starting again. :-( Still seems like DELIVERY_RETRY_WAIT should be fixed or removed, though. If it worked I'd increase it to several hours in my situation. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558128 Title: remove 552 exception for SMTP perm/temp To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558128/+subscriptions From mark at msapiro.net Wed Nov 1 20:08:49 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Nov 2017 00:08:49 -0000 Subject: [Bug 1729472] [NEW] The DELIVERY_RETRY_WAIT setting is ignored Message-ID: <150958133023.4803.5355005426737371068.malonedeb@chaenomeles.canonical.com> Public bug reported: DELIVERY_RETRY_WAIT is supposed to set the delay between retries of SMTP temp failures, but it currently has no effect. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1729472 Title: The DELIVERY_RETRY_WAIT setting is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1729472/+subscriptions From mark at msapiro.net Wed Nov 1 20:12:22 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Nov 2017 00:12:22 -0000 Subject: [Bug 558128] Re: remove 552 exception for SMTP perm/temp References: <20100408090629.1687.57975.launchpad@loganberry.canonical.com> Message-ID: <150958154243.4240.13143363191920949308.malone@gac.canonical.com> You are correct about DELIVERY_RETRY_WAIT being ignored. It could be implemented by changing line 33 of Mailman/Queue/RetryRunner.py from SLEEPTIME = mm_cfg.minutes(15) to SLEEPTIME = mm_cfg.DELIVERY_RETRY_WAIT however that doesn't explain why in your case the retries were continuous as they should be only once in 15 minutes. > Is the code perhaps supposed to set a message's "deliver_after" to "time + DELIVERY_RETRY_WAIT" after a failure? That would be another (and better) way to implement DELIVERY_RETRY_WAIT and may be the intent of deliver_after as it currently isn't set anywhere. It would also avoid the possibility of too frequent retrying if somehow the time.sleep call is interrupted. I have opened https://bugs.launchpad.net/mailman/+bug/1729472 for the issue of DELIVERY_RETRY_WAIT being ignored and I will fix that. I'm marking this "won't fix" as I don't intend to change the treatment of 552, at least for now. ** Changed in: mailman Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558128 Title: remove 552 exception for SMTP perm/temp To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558128/+subscriptions From rob-launchpad.net at tigertech.com Wed Nov 1 23:50:57 2017 From: rob-launchpad.net at tigertech.com (Robert Mathews) Date: Thu, 02 Nov 2017 03:50:57 -0000 Subject: [Bug 558128] Re: remove 552 exception for SMTP perm/temp References: <20100408090629.1687.57975.launchpad@loganberry.canonical.com> Message-ID: <150959465765.9512.15697064549918772618.malone@wampee.canonical.com> >that doesn't explain why in your case the retries were continuous as they should be only once >in 15 minutes. I'm pretty sure it was because we use VERP_PERSONALIZED_DELIVERIES and the list has hundreds of digest members. It took it most of the 15 minutes to sequentially try to deliver the hundreds of separate copies to different recipients, logging a separate smtp-failure.log error message for each. In the log it looks like it's going constantly, but now I see that there are sometimes gaps of a couple of minutes. Anyway, thanks for opening the other bug. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558128 Title: remove 552 exception for SMTP perm/temp To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558128/+subscriptions From mark at msapiro.net Thu Nov 2 00:17:48 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Nov 2017 04:17:48 -0000 Subject: [Bug 558128] Re: remove 552 exception for SMTP perm/temp References: <20100408090629.1687.57975.launchpad@loganberry.canonical.com> Message-ID: <150959626900.3981.5010596426032079179.malone@gac.canonical.com> > I'm pretty sure it was because we use VERP_PERSONALIZED_DELIVERIES and the list has hundreds of digest members. Right, I missed that in https://bugs.launchpad.net/mailman/+bug/558128/comments/5 when I wrote https://bugs.launchpad.net/mailman/+bug/558128/comments/6 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558128 Title: remove 552 exception for SMTP perm/temp To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558128/+subscriptions From 1696066 at bugs.launchpad.net Thu Nov 2 06:53:41 2017 From: 1696066 at bugs.launchpad.net (ChristianEhrhardt) Date: Thu, 02 Nov 2017 10:53:41 -0000 Subject: [Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files References: <149673486419.28883.14597965095773088289.malonedeb@wampee.canonical.com> Message-ID: <150962002157.20599.14332886245009178217.malone@soybean.canonical.com> Ok, I'm not gettign to this soon, but there are also a few steps we have to wait for. So for now I document the next steps and subscribe the team to look at this again later on: 1. 2.1.25 in Debian 2. 2.1.25 in Ubuntu (Bionic) 3. SRU fix into X-A releases ** Also affects: mailman (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mailman (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: mailman (Ubuntu Zesty) Importance: Undecided Status: New ** Tags added: server-next -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1696066 Title: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1696066/+subscriptions From 1729472 at bugs.launchpad.net Thu Nov 2 23:40:47 2017 From: 1729472 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 03 Nov 2017 03:40:47 -0000 Subject: [Bug 1729472] Re: The DELIVERY_RETRY_WAIT setting is ignored References: <150958133023.4803.5355005426737371068.malonedeb@chaenomeles.canonical.com> Message-ID: <150968045184.15041.13671310909032904887.launchpad@ackee.canonical.com> ** 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/1729472 Title: The DELIVERY_RETRY_WAIT setting is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1729472/+subscriptions From mark at msapiro.net Thu Nov 2 23:41:05 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 03 Nov 2017 03:41:05 -0000 Subject: [Bug 1729472] Re: The DELIVERY_RETRY_WAIT setting is ignored References: <150958133023.4803.5355005426737371068.malonedeb@chaenomeles.canonical.com> Message-ID: <150968046569.4240.7987448761760956614.launchpad@gac.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/1729472 Title: The DELIVERY_RETRY_WAIT setting is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1729472/+subscriptions From futatuki at poem.co.jp Wed Nov 8 04:05:39 2017 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Wed, 08 Nov 2017 09:05:39 -0000 Subject: [Merge] lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1 Message-ID: <151013193726.31099.34344330526833516.launchpad@ackee.canonical.com> Yasuhito FUTATSUKI at POEM has proposed merging lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-ja-translation/+merge/333362 messages/ja/doc/Defaults.py.in, Japanese translation of Mailman/Defaults.py.in for reference, has been updated up to rev 1727 change. (Including 1 typo fix) -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 3196 bytes Desc: not available URL: From ralph at inputplus.co.uk Thu Nov 9 07:04:03 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Thu, 09 Nov 2017 12:04:03 -0000 Subject: [Bug 1731246] [NEW] Feature: Optional terse list of pending admin held messages Message-ID: <151022904332.2986.9302360940084310236.malonedeb@gac.canonical.com> Public bug reported: I often tend to the "Held messages". Each messages has a lot of vertical screen estate due to all the various options. The From: is separate from the Subject: because several emails mail be grouped by one From:. The Reason: is long and wordy. This is all fine for detailed examination. But the common use is to scan down the list, see all should be discarded, and select the very handy "Discard all messages marked Defer". The problem is, scanning the list is slow. It would be nice if there was a "show me the terse version" button that reloaded the page, perhaps the same URL with a query parameter, and presented just one row per message with columns Reason:, From:, and Subject:. The Reason: would be an abbreviated form, e.g. "non-member". At the start of the row is a checkbox, selected by default, to "Defer", and the existing "Discard all messages marked Defer" would again be top and bottom. A button to return to the verbose presentation would be needed. This would allow rapid scanning vertically. It would be obvious all the Reason:s were non-member. The From:s, even with there being duplicates, would similarly be easier. And the start of the Subject:s would line up; the ends are often unimportant. Tab would move between the Defer checkboxes and not to any other item within the row. ** 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/1731246 Title: Feature: Optional terse list of pending admin held messages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1731246/+subscriptions From mark at msapiro.net Thu Nov 9 14:39:28 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 09 Nov 2017 19:39:28 -0000 Subject: [Bug 1731246] Re: Feature: Optional terse list of pending admin held messages References: <151022904332.2986.9302360940084310236.malonedeb@gac.canonical.com> Message-ID: <151025636891.3019.8224554137161151809.malone@gac.canonical.com> If you have shell access to the Mailman server, you may find the script at https://www.msapiro.net/scripts/list_requests (mirrored at https://fog.ccsf.edu/~msapiro/scripts/list_requests) to be helpful. Also, beginning with Mailman 2.1.16 there is a mm_cfg.py setting DISPLAY_HELD_SUMMARY_SORT_BUTTONS that can be set to control how the held message display is grouped and sorted. See the documentation in Defaults.py for more info. Otherwise, Mailman 2.1 is basically end of life and changes of this scope are unlikely to be made. ** Changed in: mailman Importance: Undecided => Wishlist ** Changed in: mailman Status: New => Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1731246 Title: Feature: Optional terse list of pending admin held messages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1731246/+subscriptions From mark at msapiro.net Sat Nov 11 01:27:12 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 11 Nov 2017 06:27:12 -0000 Subject: [Bug 1731604] [NEW] VERP fails if the recipient address local part is quoted. Message-ID: <151038163229.934.12641910175503585284.malonedeb@chaenomeles.canonical.com> Public bug reported: We have seen (very rarely) cases where a recipient address has a quoted local part such as "jr."@example.org. This results in a VERPed sender address like list-bounces+"jr."=example.org at example.com which is syntactically invalid. The VERPed sender should be "list- bounces+jr.=example.org"@example.com in this case. I.e., the entire VERPed sender local part should be quoted, not just the recipient local part. This also requires BounceRunner to recognize this and restore the original local part. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1731604 Title: VERP fails if the recipient address local part is quoted. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1731604/+subscriptions From 1251495 at bugs.launchpad.net Wed Nov 15 09:38:09 2017 From: 1251495 at bugs.launchpad.net (ChristianEhrhardt) Date: Wed, 15 Nov 2017 14:38:09 -0000 Subject: [Bug 1251495] Re: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. References: <20131115020913.18410.66201.malonedeb@wampee.canonical.com> Message-ID: <151075668922.7650.17484781511632639710.malone@soybean.canonical.com> Got an ack on the MP and pushed the fix to Trusty as SRU. Somewhat sad but better late than never. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions From brian at ubuntu.com Wed Nov 22 12:02:21 2017 From: brian at ubuntu.com (Brian Murray) Date: Wed, 22 Nov 2017 17:02:21 -0000 Subject: [Bug 1251495] Re: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. References: <20131115020913.18410.66201.malonedeb@wampee.canonical.com> Message-ID: <151137014163.18764.12209726309139707540.malone@gac.canonical.com> Hello Mark, or anyone else affected, Accepted mailman into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mailman/1:2.1.16-2ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mailman (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions From philip.colmer at linaro.org Thu Nov 23 04:34:36 2017 From: philip.colmer at linaro.org (Philip Colmer) Date: Thu, 23 Nov 2017 09:34:36 -0000 Subject: [Bug 1251495] Re: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. References: <20131115020913.18410.66201.malonedeb@wampee.canonical.com> Message-ID: <151142967662.7449.3030336350214757751.malone@chaenomeles.canonical.com> I have tested 2.1.16 on trusty and I can confirm that it replaces "Delete=False" with "delete=False" in /var/lib/mailman/Mailman/Handlers/Tagger.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/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions From 1251495 at bugs.launchpad.net Thu Nov 23 09:41:17 2017 From: 1251495 at bugs.launchpad.net (ChristianEhrhardt) Date: Thu, 23 Nov 2017 14:41:17 -0000 Subject: [Bug 1251495] Re: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. References: <20131115020913.18410.66201.malonedeb@wampee.canonical.com> Message-ID: <151144807726.7976.7279246402882331838.malone@chaenomeles.canonical.com> Also chacked the same, thanks Phillip! Setting verified. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions From mark at msapiro.net Thu Nov 23 12:23:41 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 23 Nov 2017 17:23:41 -0000 Subject: [Bug 1734162] [NEW] OSError in Mailman/MTA/Postfix.py when updating maps. Message-ID: <151145782114.7560.14612148944401178995.malonedeb@chaenomeles.canonical.com> Public bug reported: The fix for lp:1696066 assumes that the Postfix aliases and virtual- mailman mappings are hash tables with .db extension. If they are, e.g., cdb tables with .cdb extension, the attempt to stat the .db file throws OSError. Since there are various possibilities for the table format and extension, and since all the documentation of Mailman-Postfix integration refers only to hash tables, we'll just catch the error and ignore the file. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1734162 Title: OSError in Mailman/MTA/Postfix.py when updating maps. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1734162/+subscriptions From 1734162 at bugs.launchpad.net Thu Nov 23 12:44:33 2017 From: 1734162 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 23 Nov 2017 17:44:33 -0000 Subject: [Bug 1734162] Re: OSError in Mailman/MTA/Postfix.py when updating maps. References: <151145782114.7560.14612148944401178995.malonedeb@chaenomeles.canonical.com> Message-ID: <151145907654.19320.5041359478118991217.launchpad@ackee.canonical.com> ** 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/1734162 Title: OSError in Mailman/MTA/Postfix.py when updating maps. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1734162/+subscriptions From mark at msapiro.net Thu Nov 23 12:44:39 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 23 Nov 2017 17:44:39 -0000 Subject: [Bug 1734162] Re: OSError in Mailman/MTA/Postfix.py when updating maps. References: <151145782114.7560.14612148944401178995.malonedeb@chaenomeles.canonical.com> Message-ID: <151145907963.14317.5983783148955990830.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/1734162 Title: OSError in Mailman/MTA/Postfix.py when updating maps. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1734162/+subscriptions From 1251495 at bugs.launchpad.net Wed Nov 29 18:44:12 2017 From: 1251495 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 29 Nov 2017 23:44:12 -0000 Subject: [Bug 1251495] Re: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. References: <20131115020913.18410.66201.malonedeb@wampee.canonical.com> Message-ID: <151199905462.22729.6738495599428857874.malone@ackee.canonical.com> This bug was fixed in the package mailman - 1:2.1.16-2ubuntu0.3 --------------- mailman (1:2.1.16-2ubuntu0.3) trusty; urgency=medium * Fixed a misspelling in Tagger.py that breaks Lists with topics enabled (LP: #1251495) -- Christian Ehrhardt Wed, 25 Oct 2017 16:46:47 +0200 ** Changed in: mailman (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions From brian at ubuntu.com Wed Nov 29 18:44:16 2017 From: brian at ubuntu.com (Brian Murray) Date: Wed, 29 Nov 2017 23:44:16 -0000 Subject: [Bug 1251495] Update Released References: <20131115020913.18410.66201.malonedeb@wampee.canonical.com> Message-ID: <151199905657.10497.13666441184701486516.malone@wampee.canonical.com> The verification of the Stable Release Update for mailman has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions From 1735645 at bugs.launchpad.net Thu Nov 30 23:51:48 2017 From: 1735645 at bugs.launchpad.net (Troy Reid) Date: Fri, 01 Dec 2017 04:51:48 -0000 Subject: [Bug 1735645] [NEW] regular_include_lists not found error Message-ID: <151210390890.10571.6511483784038415696.malonedeb@soybean.canonical.com> Public bug reported: mailman reports sublists as not found in the error file Two sublists (active-members at domain.com and inactive-members at domain.com) are configured as regular_include_lists for list members at domain.com When posting to members at domain.com, mailman reports the errors: Include list active-members at domain.com not found. Include list inactive-members at domain.com not found. ** 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/1735645 Title: regular_include_lists not found error To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1735645/+subscriptions