December 2017 - Mailman-users - lists.mailman3.org

[MM3-users]Is it possible to grant all users the ability to Create List
by Carrie Knox 13 Jul '21

13 Jul '21

Hello, Our company is evaluating mailman3 as an option for company internal list serving. One of the requirements is that anyone with access to the list server be allowed to create and manage lists. Is this possible? If so, how? Is there a "create list" role that can be added for all registered users? Thanks

5 5

MM3 shunting mails
by Anders Nilsson 03 Jan '20

03 Jan '20

I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using RPMs from https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/ I do have problems with some lists occasionally going into some kind of shunt mode, where alla mails sent to them gets shunted. In the Mailman log I get entries for each shunted email: Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.4/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 121, in process process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist) File "/usr/lib/python3.4/site-packages/zope/component/hookable.py", line 33, in __call__ return self.__implementation(*args, **kw) File "/usr/lib/python3.4/site-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib64/python3.4/site-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.4/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 And so far my Google-fu hasn't been good enough to give me any useful answers to why this happens. If I dump one of the pickles using qfile I cannot see any complaints. Most of the times, if I remove and recreate a failing list and run unshunt the shunted emails get processed and sent. Anyone seen something similar? Regards, Anders Nilsson -- Anders Nilsson, Ph.D. <andersn(a)control.lth.se> Dep. of Automatic Control, Lund University Phone: +46 (0)46 222 87 94, Fax: +46 (0)46 13 81 18 Mob: +46 (0)703 22 57 67

4 4

confirm mail rejected
by Marc Sluiter 29 Sep '19

29 Sep '19

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected: In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) Thanks and greetings, Marc

4 4

Auth question
by David Krantz 08 Jan '19

08 Jan '19

Hi, I have of course activated password login as it was not possible to get the provider based logins to work (might be but not worth the time for me right now). Is there any way for an user to request a new password when it is forgotten? I presume that the Persona login is removed now. I cannot hide it in my version or at least I do not know how. cheers // David

6 25

How to get Mailman core to provide more debug info in a running environment
by Henrik Rasmussen 03 Jan '19

03 Jan '19

Docker-mailman 0.1.1 I am using Mailman 3.1 in production and I am trying to debug a problem[1] so I tried to setting Mailman to provide more debug info in the smtp.log file[2]. I might have been doing it wrong, but in the mailman-extra.cfg I set [logging.smtp-failure] path: smtp.log and restarted Mailman, which stopped incoming mails until removing the added section. What is the correct way to get Mailman to provide more debug info in the smtp.log 1) https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… 2) http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html… Henrik Rasmussen

4 5

Templates
by David Krantz 19 Dec '18

19 Dec '18

Hi. How do I set a template for one specific list? I want one list to have a special footer template. I have tried updating the database (template table) without effect so apparently the database is not used for templates or some kind of fallback is used to set it to the generic footer. Of course I also tried to restart mailman after that operation to try to rule out any caching-related problem. I want to use a file://-path as that is the least painful way of doing it. I also would like a solution to place a file in a special location. My current templates are in a .../var/templates/site/en/ structure with names like list:member:generic:footer.txt Cheers // David

4 14

Whitelist non subscriber
by Mark Ziranski 27 Aug '18

27 Aug '18

Hello, I want to whitelist an email address on all lists to bypass moderation. The email address is not a subscriber. On google I found accept_these_nonmembers but I do not know how to use it. Please show me some examples how to whitelist someone(a)example.org. Thanks in advance. M.Z.

4 6

Mailman 3 localization
by Danil Smirnov 05 Jul '18

05 Jul '18

Hi! I saw in the docs: Localization > > We have it! We just don’t have proper documentation here yet. > Could you please be more specific - can I switch Mailman 3 installation to Spanish? Regards, Danil Smirnov

7 13

Unknown attribute: max_message_size
by Thor Atle Rustad 27 Jun '18

27 Jun '18

If I make changes here: https://example.com/postorius/lists/test2.example.com/settings/message_acce…, I get a warning that the Maximum Message Size field at the bottom is mandatory. However, if I put a number in that field and save, I get "Unknown attribute: max_message_size". That makes sense, since Mark states in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… that max_messages_size is not exposed in REST. What to do? I have Maxking mailman-docker but can easily copy files into the image if necessary. Thor

5 8

Disabling Gravatar
by Marvin Gülker 26 Apr '18

26 Apr '18

Hi everyone, I want to make you aware of a potential privacy problem in Mailman's Hyperkitty. Under the upcoming EU General Data Protection Regulation (GDPR)[1], which will be in force as of 2018-05-25, it is illegal to transmit data to third parties without a right to do so. Without going into the details, the inclusion of third party services into one's website is usually deemed such a transmission, and unless one has explicit consent of the user (e.g., by an optional (!), unticked ticking box) this is normally illegal (if one targets EU users). The GDPR does not affect private and family use (Art. 2(2)(c) GDPR), but the exact reach of that clause is yet to be determined; it certainly does not exclude company use of Mailman. I've found it's possible to disable the social login providers quite easily (we had this discussion here on the mailinglist recently), but I don't see an option to disable Gravatar. If there is one, please enlighten me, but anyway I want to propose this as a feature request against Hyperkitty. A GDPR-compliant implementation of Gravatar in Mailman would look like this: * In order to not transmit website visitor's data (IP address, browser info, etc) to Gravatar, Hyperkitty has to request the avatar image itself and not leave that to the user's browsers to do. In other words, the HTTP GET request needs to come from the server running Hyperkitty and the user's browser then just requests the avatar from the Hyperkitty server. Most likely easiest way to do this is to pre-download the avatar when an email is archived. * In order to not transmit the subscribers' data (email address, allows Gravatar to track the subscriber) to Gravatar illegally, the retrieval of the avatar image from Gravatar has to be disabled by default. Instead, an option needs to be added to the subscriber's control panel which he has to actively enable in order to have his Gravatar downloaded and thus used (privacy-by-default rule). I'm not saying Gravatar tracks people and sells the information gathered, though I have doubts on how Automattic makes money with the service. I'm just outlining the legal duties under the upcoming GDPR for service owners, which are independant of how Automattic processes the data in this specific case. Please don't dismiss this as some side feature not needed. The fines that can be imposed on service owners due to violation of the GDPR are very high (up to 20,000,000 € [that's 20 million euros, really]). Marvin [1]: http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX:… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

5 5

Mailman-users December 2017