Mailman Core merge requestshttps://staging.gitlab.com/mailman/mailman/-/merge_requests2015-11-30T00:04:30Zhttps://staging.gitlab.com/mailman/mailman/-/merge_requests/65Allow list names to have command suffixes2015-11-30T00:04:30Zusername-removed-35210Allow list names to have command suffixesFixes #168Fixes #1683.0.2username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/58Optimize the roster SQL query2015-11-23T03:07:42Zusername-removed-35210Optimize the roster SQL queryMeasured improvement: about 100x faster. (!)Measured improvement: about 100x faster. (!)3.0.2https://staging.gitlab.com/mailman/mailman/-/merge_requests/56Fix address delete2015-11-22T04:29:08Zusername-removed-35210Fix address deleteSince we have not set cascade policies on our table relationships, dependencies must be removed first when user or addresses are removed. This branches does that. The unit tests will only fail on PostgreSQL, since SQLite does not enforce...Since we have not set cascade policies on our table relationships, dependencies must be removed first when user or addresses are removed. This branches does that. The unit tests will only fail on PostgreSQL, since SQLite does not enforce foreign key constraints.3.0.2username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/59Fix the approved rule when there is no list password2015-11-22T01:01:16Zusername-removed-35210Fix the approved rule when there is no list password3.0.2username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/60Reorder default posting chain2015-11-21T20:14:22Zusername-removed-35210Reorder default posting chainSee issue #163.See issue #163.3.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/55Add useful indexes on the member table2015-11-21T17:50:27Zusername-removed-35210Add useful indexes on the member tableThis patch add 3 very useful indexes on the `member` table. This patch add 3 very useful indexes on the `member` table. 3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/63Sort the JSON keys in dev mode2015-11-21T17:25:52Zusername-removed-35210Sort the JSON keys in dev modeThis makes it much easier to compare VCR tapes.This makes it much easier to compare VCR tapes.https://staging.gitlab.com/mailman/mailman/-/merge_requests/54REST: add a self_link entry to held messages2015-11-15T20:33:43Zusername-removed-35210REST: add a self_link entry to held messagesWe could do without it but this makes the REST API more coherent.We could do without it but this makes the REST API more coherent.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/52Fix for Issue 1472015-10-30T03:05:43Zusername-removed-107958Fix for Issue 147Updated mailman/src/mailman/handlers/subject_prefix.py to do a better job of collapsing multiple Re:. Also reordered the stripping of prefix and collapsing of Re:, otherwise the Re: regexp never matched.
Updated mailman/src/mailman/ha...Updated mailman/src/mailman/handlers/subject_prefix.py to do a better job of collapsing multiple Re:. Also reordered the stripping of prefix and collapsing of Re:, otherwise the Re: regexp never matched.
Updated mailman/src/mailman/handlers/docs/subject-munging.rst to test collapsing multiple Re: and to fix the last RFC2047 encoded Subject: test.3.0.1username-removed-107958username-removed-107958https://staging.gitlab.com/mailman/mailman/-/merge_requests/42Import header matches2015-10-21T03:00:27Zusername-removed-35210Import header matchesThis branch improve the header_matches to let them have rule-specific actions.This branch improve the header_matches to let them have rule-specific actions.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/47Fix the logging of the moderation reasons2015-09-24T01:38:34Zusername-removed-35210Fix the logging of the moderation reasonsThe logging of moderation reasons was wrongly using the `_compose_reasons` function and re-serializing the results afterwards, which caused log entries such as this:
```
HOLD: test@example.com post from anne@example.com held, message-i...The logging of moderation reasons was wrongly using the `_compose_reasons` function and re-serializing the results afterwards, which caused log entries such as this:
```
HOLD: test@example.com post from anne@example.com held, message-id=<ant>: ; ; ; ; T; E; S; T; -; R; E; A; S; O; N; -; 1; \n; ; ; ; ; T; E; S; T; -; R; E; A; S; O; N; -; 2\n'
```
This commit fixes it.3.0.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/46Also rename the migration file following 9806f9c72015-09-22T23:35:05Zusername-removed-35210Also rename the migration file following 9806f9c7This is a very simple fix. Changeset 9806f9c7 renamed a table column, but the corresponding migration file was forgotten.This is a very simple fix. Changeset 9806f9c7 renamed a table column, but the corresponding migration file was forgotten.3.0.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/33Add url to archives in the message footer (all that are enabled)2015-08-30T16:31:46Zusername-removed-262Add url to archives in the message footer (all that are enabled)I am little confused about how to write tests for this if needed at all?I am little confused about how to write tests for this if needed at all?3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/34Fix mhonarc stdin PIPE.2015-08-18T01:39:57Zusername-removed-218571Fix mhonarc stdin PIPE.Problem:
Aug 15 17:56:24 2015 (21609) This is MHonArc v2.6.19+, Perl 5.020002
linux
Reading database ...
Adding message to /srv/data/mhonarc/my@list.tld
No new messages
Apparently no data was coming in ove...Problem:
Aug 15 17:56:24 2015 (21609) This is MHonArc v2.6.19+, Perl 5.020002
linux
Reading database ...
Adding message to /srv/data/mhonarc/my@list.tld
No new messages
Apparently no data was coming in over stdin.
The cause was the missing stdin=PIPE in the Popen() call, resulting in
FD 0 from the process startup to be passed as stdin; as can be seen in
this listing from /proc/$$/fd:
lrwx------ 1 list list 64 Aug 15 17:56 0 -> /dev/pts/4 (deleted)
l-wx------ 1 list list 64 Aug 15 17:56 1 -> /tmp/output.fds
lr-x------ 1 list list 64 Aug 15 17:56 10 -> /usr/local/bin/mhonarc
l-wx------ 1 list list 64 Aug 15 17:56 11 -> pipe:[50142214]
l-wx------ 1 list list 64 Aug 15 17:56 2 -> pipe:[50142215]
The fix is to set `stdin=PIPE` as done here. The `close_fds=True`
argument needs not be set as well, since it's default on POSIX since
Python 3.3.0.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/29Fix #1372015-08-14T00:52:56Zusername-removed-262Fix #137`args` the output from command parser always has a default key, value like Namespace(config=None).`args` the output from command parser always has a default key, value like Namespace(config=None).https://staging.gitlab.com/mailman/mailman/-/merge_requests/22Testing Please Ignore2015-07-12T12:20:25Zusername-removed-262Testing Please IgnoreTesting Please IgnoreTesting Please Ignorehttps://staging.gitlab.com/mailman/mailman/-/merge_requests/18Fix import212015-06-24T23:25:00Zusername-removed-35210Fix import21This branch fixes the import of some configuration values from Mailman 2.1 dealing with members and nonmembers moderation.
- The member moderation bit was not interpreted and converted properly
- The `*_these_nonmembers` parameters wer...This branch fixes the import of some configuration values from Mailman 2.1 dealing with members and nonmembers moderation.
- The member moderation bit was not interpreted and converted properly
- The `*_these_nonmembers` parameters were not imported properly and not taken into account by the moderation rule
All tests pass, coverage is good.https://staging.gitlab.com/mailman/mailman/-/merge_requests/3Honor admin_notify_mchanges with subscription policy2015-05-02T15:19:18Zusername-removed-56772Honor admin_notify_mchanges with subscription policyThis fixes the problem where list owners weren't being notified of subscriptions when using the new subscription policy workflow. Closes #1This fixes the problem where list owners weren't being notified of subscriptions when using the new subscription policy workflow. Closes #13.0.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/1Add the styleguide for GNU Mailman2015-05-01T07:49:56Zusername-removed-262Add the styleguide for GNU MailmanPlease ignore this. I am sending this request to test the gitlab features.Please ignore this. I am sending this request to test the gitlab features.https://staging.gitlab.com/mailman/mailman/-/merge_requests/2New branch2015-05-01T07:49:32Zusername-removed-262New branchnew merge request to test things.new merge request to test things.