Mailman 3 November 2017 - Mailman-coders

[Bug 1729472] [NEW] The DELIVERY_RETRY_WAIT setting is ignored
by Mark Sapiro 04 Feb '18

04 Feb '18

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

2 3

[Bug 1734162] [NEW] OSError in Mailman/MTA/Postfix.py when updating maps.
by Mark Sapiro 04 Feb '18

04 Feb '18

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

2 3

[Bug 1446881] [NEW] Require Falcon 0.3
by Barry Warsaw 06 Jan '18

06 Jan '18

Public bug reported: Falcon 0.2 contains a bug in parsing fields with commas and newlines. We will block the Mailman 3 final release on the release of Falcon 0.3 to PyPI. ** Affects: mailman Importance: Critical Assignee: Barry Warsaw (barry) Status: Triaged ** Tags: mailman3 mailman3-suite-blocker ** Branch linked: lp:~raj-abhilash1/mailman/bugfix ** Tags added: mailman3-suite-blocker -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1446881 Title: Require Falcon 0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1446881/+subscriptions

2 5

[Bug 1251495] [NEW] Lists with topics enabled can throw unexpected keyword argument 'Delete' exception.
by Mark Sapiro 29 Nov '17

29 Nov '17

Public bug reported: Code added to Tagger.py in 2.1.16 to support the from_is_list Wrap Message option contained a misspelling. ** Affects: mailman Importance: High 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/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

5 16

[Bug 1731246] [NEW] Feature: Optional terse list of pending admin held messages
by Ralph Corderoy 09 Nov '17

09 Nov '17

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

2 1

[Merge] lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1
by Yasuhito FUTATSUKI＠POEM 08 Nov '17

08 Nov '17

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/3333… 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.

1 0

[Bug 558128] Re: remove 552 exception for SMTP perm/temp
by Mark Sapiro 02 Nov '17

02 Nov '17

> 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

1 0

[Bug 558128] Re: remove 552 exception for SMTP perm/temp
by Robert Mathews 02 Nov '17

02 Nov '17

>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

1 0

[Bug 558128] Re: remove 552 exception for SMTP perm/temp
by Mark Sapiro 02 Nov '17

02 Nov '17

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

1 0

[Bug 558128] Re: remove 552 exception for SMTP perm/temp
by Robert Mathews 01 Nov '17

01 Nov '17

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

1 0