Mailman Core merge requestshttps://staging.gitlab.com/mailman/mailman/-/merge_requests2016-11-30T20:57:32Zhttps://staging.gitlab.com/mailman/mailman/-/merge_requests/221Pay off some tech debt2016-11-30T20:57:32Zusername-removed-56772Pay off some tech debtThis cleans up a few things.
* Use `flufl.testing`'s flake8 and nose2 plugins instead of Mailman's copies.
* Use `atpublic`'s `@public` decorator instead of Mailman's copies.This cleans up a few things.
* Use `flufl.testing`'s flake8 and nose2 plugins instead of Mailman's copies.
* Use `atpublic`'s `@public` decorator instead of Mailman's copies.3.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/219Porting to Python 3.62016-11-29T01:29:49Zusername-removed-56772Porting to Python 3.6For issue #295For issue #2953.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/163Cover another header match import case2016-11-26T05:13:53Zusername-removed-35210Cover another header match import caseThis branch just covers one more import conversion case seen in the wild.This branch just covers one more import conversion case seen in the wild.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/87Don't show the disabled archivers in the REST API2016-11-26T05:05:48Zusername-removed-35210Don't show the disabled archivers in the REST APIPreviously, system-disabled archivers were shown in the REST API. As a result it was possible to enable them without a validation error, but they would stay disabled on the next API GET call (their actual activation status depends on the...Previously, system-disabled archivers were shown in the REST API. As a result it was possible to enable them without a validation error, but they would stay disabled on the next API GET call (their actual activation status depends on the list-specific *and* the system-wide status).
Because one can't add a configuration overlay to the running REST server
in testing mode, the prototype archiver was disabled in the testing
configuration. This is where most of the changes in this commit come
from.3.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/216Fix sphinx-build for output formats "man" and "latex".2016-11-25T15:48:53Zusername-removed-822425Fix sphinx-build for output formats "man" and "latex".The current version of conf.py use source "index" for the manpage
and Latex-output. This source does not exist. This commit fixes the
build by using the source "README".The current version of conf.py use source "index" for the manpage
and Latex-output. This source does not exist. This commit fixes the
build by using the source "README".3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/220Switch to aiosmtpd2016-11-24T18:08:14Zusername-removed-56772Switch to aiosmtpdFixes #296Fixes #2963.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/190Handle a missing user when a workflow is restored2016-11-24T16:08:22Zusername-removed-35210Handle a missing user when a workflow is restoredBetween the creation of a subscription workflow and its approval, the user may have been merged with another user (it did happen). In this case, use the associated address to find the new user.
This requires that the address be restored...Between the creation of a subscription workflow and its approval, the user may have been merged with another user (it did happen). In this case, use the associated address to find the new user.
This requires that the address be restored before the user. The current method to restore does not guarantee the order, so I changed it to allow attributes to depend on one another.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/218Ignore some Flake8 errors2016-11-21T14:08:05Zusername-removed-35210Ignore some Flake8 errorsFlake8 implicitely ignores some errors, and new versions tend to add new errors. This change explicitely lists the errors we want to ignore.Flake8 implicitely ignores some errors, and new versions tend to add new errors. This change explicitely lists the errors we want to ignore.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/217Closes #682016-11-14T03:30:57Zusername-removed-56772Closes #68Supersedes mailman/mailman!181 with a manual merge and clean up.Supersedes mailman/mailman!181 with a manual merge and clean up.3.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/214Remove digest mboxes after digest is sent2016-10-31T22:40:54Zusername-removed-56772Remove digest mboxes after digest is sentManual merge of !194
Closes #259 - really given by @abompardManual merge of !194
Closes #259 - really given by @abompard3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/213Use HTTP/1.1 by default2016-10-30T22:36:20Zusername-removed-56772Use HTTP/1.1 by defaultFixes #288Fixes #2883.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/196Prevent posting from banned addresses2016-10-27T12:57:05Zusername-removed-35210Prevent posting from banned addressesFixes #283Fixes #2833.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/209Change default unsubscription_policy to SubscriptionPolicy.confirm2016-10-26T12:17:03Zusername-removed-107958Change default unsubscription_policy to SubscriptionPolicy.confirmFixes #292
Need to change default unsubscription_policy to SubscriptionPolicy.confirm for new lists, not just migrated ones.Fixes #292
Need to change default unsubscription_policy to SubscriptionPolicy.confirm for new lists, not just migrated ones.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/208Confirm unsubscriptions by default.2016-10-26T00:30:48Zusername-removed-56772Confirm unsubscriptions by default.https://staging.gitlab.com/mailman/mailman/-/merge_requests/205Implement PUT/PATCH for domain.2016-10-24T13:58:27Zusername-removed-107958Implement PUT/PATCH for domain.Fixes https://gitlab.com/mailman/mailman/issues/290
This is an implementation of PUT/Patch for a domain. It actually only allows updating description and owner (and alias_domain will be included when that is ready). mail_host shouldn'...Fixes https://gitlab.com/mailman/mailman/issues/290
This is an implementation of PUT/Patch for a domain. It actually only allows updating description and owner (and alias_domain will be included when that is ready). mail_host shouldn't be changed and mailing_lists probably shouldn't be manipulated this way.3.1https://staging.gitlab.com/mailman/mailman/-/merge_requests/207MySQL doesn't need collate set explicitly.2016-10-21T22:43:57Zusername-removed-262MySQL doesn't need collate set explicitly.Fixes #276.
Just remove the incorrect text.Fixes #276.
Just remove the incorrect text.https://staging.gitlab.com/mailman/mailman/-/merge_requests/203Unsubscribe workflow2016-10-21T18:27:59Zusername-removed-56772Unsubscribe workflowThis is my unsubscribe workflow branch, based on @maxking 's original branch. It closes #213 but it doesn't pass all its tests. Specifically, a couple of database migration tests fail, and I haven't figure out why yet. Maybe @maxking ...This is my unsubscribe workflow branch, based on @maxking 's original branch. It closes #213 but it doesn't pass all its tests. Specifically, a couple of database migration tests fail, and I haven't figure out why yet. Maybe @maxking has some insight.
I'd like to get the tests passing and then do a final cleanup pass on the code. In the meantime, all other comments welcome of course.3.1username-removed-56772username-removed-56772https://staging.gitlab.com/mailman/mailman/-/merge_requests/200Fix build in CI because of a Falcon pre-release2016-10-08T12:48:05Zusername-removed-35210Fix build in CI because of a Falcon pre-releaseThis change has falcon installed by pip instead of the develop command, to avoid getting the pre-release version.This change has falcon installed by pip instead of the develop command, to avoid getting the pre-release version.https://staging.gitlab.com/mailman/mailman/-/merge_requests/187REST: allow MailingList.info to be set2016-08-31T16:49:27Zusername-removed-35210REST: allow MailingList.info to be sethttps://staging.gitlab.com/mailman/mailman/-/merge_requests/186Added unsubscribe instructions to list:member:generic:footer.txt2016-08-26T23:58:06Zusername-removed-681857Added unsubscribe instructions to list:member:generic:footer.txtAfter witnessing yet another ["please unsubscribe me from this list" message](https://lists.gnupg.org/pipermail/gnupg-users/2016-August/056533.html) sent to a Mailmain mailing list, I decided to propose this change to the generic footer...After witnessing yet another ["please unsubscribe me from this list" message](https://lists.gnupg.org/pipermail/gnupg-users/2016-August/056533.html) sent to a Mailmain mailing list, I decided to propose this change to the generic footer.
I believe this is a sane default, as:
- it allows even the least technically-versed (or most absent-minded) user to immediately reognize how unsubscribe
- it doesn't point to web interface (which some ML don't have)
- the footer is no bigger than before the commit (I shifted ``$listname`` on the line above)
- if Listmaster isn't happy, they are free to change it to something else
This should avoid frustration to a bunch of users who are not used to mailing lists.3.1