June 2019 - Mailman-users - lists.mailman3.org

Default values for new lists
by Sten Aus 11 Jan '20

11 Jan '20

Hi I haven't found out where I could choose or edit default list values (when creating new list). For example I would like that all new lists would be with *private archive* (and change this when it is needed). This is great that I can choose not to advertise list in Index (which I can choose from list creation interface) but I would like to choose other options too. Right now only solution is to create list and then choose Archiving and then select "private archives". Another thing is that I would like to choose default subscription policy to "Moderate". If anyone has encountered this problem, let me know! All the best Sten

4 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

bounces with empty message-id
by Peter Münster 12 Dec '19

12 Dec '19

Hi, It seems, that mailman bounces the bounces, so that the list-owner never sees them: --8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) postfix/qmgr[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8--- What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses... TIA for any hints, -- Peter

3 8

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

Mailman 3 Installation Assistance
by brian＠emwd.com 26 Jul '19

26 Jul '19

I am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server: https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/ I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell: curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; Connection refused I assume this has something to do with uwsgi which I have no experience with. Appreciate any assistance with getting Mailman 3 up and running. Thanks! Brian Carpenter

4 28

Delete a single email or thread from hyperkitty archive
by andrew.bernard＠gmail.com 15 Jul '19

15 Jul '19

How can one do this? Raw database access gets you involved in all the usual foreign key constraints. I don't know how to make use of this information: https://gitlab.com/mailman/hyperkitty/commit/6e3e6a5270f37543a757d76c0aee12… After a very large import of decades of data, I need to delete just one wrong mail that is corrupt. I think it is a valid case. I could run the import again after fixing the import mbox, but it takes many hours to load. Andrew

4 7

Unable to get mailman3-full on Debian
by Frank Yappa 15 Jul '19

15 Jul '19

When trying apt-get install on Debian, I get E: Unable to locate package mailman3-full. What am I doing wrong? I have run apt-get update.

3 2

delete examples.com site
by enrique.terrazas＠utsa.edu 09 Jul '19

09 Jul '19

Hello, I've been working on setting up Mailman3 on a RHEL 7.5 vm using the guides and documentation found here: http://docs.mailman3.org/en/latest/index.html https://mailman.readthedocs.io/en/latest/README.html http://docs.mailman3.org/projects/postorius/en/latest/index.html http://docs.mailman3.org/projects/mailmanclient/en/latest/README.html https://hyperkitty.readthedocs.io/en/latest/index.html https://gitlab.com/mailman/mailman-hyperkitty nginx is serving the Django applications via uwsgi. I was able to get mailman, postorius + hyperkitty, running and test sending out email verifications. In an attempt to set the default domain to something other than example.com I deleted the site: example.com, I did have another site. Unfortunately, this seems to have broken the Django applications. At the moment I am preparing to delete the virtual environment and set things up again. Unless there is something that can be done in the current virtual environment to "reset" things back to start. I was also running into an issue where the verification emails were successfully sent out. The url to verify the email looks like this: http://my.domain.com:8000/accounts/confirm-email/xxxxxxxxxxxx/ Replacing my.domain.com with the domain I added. How can I get the outgoing verification emails to not reference port 8000? If I take that same link and remove the port, I get the desired page. Port 8000 is blocked at our sites permitter firewall, I don't necessarily want to open it. I'd rather the URL just obfuscate the port and send it to https... Thank you in advance for your attention and assistance. Best regards, Enrique J. Terrazas

3 4

Rich Text support in Hyperkitty
by Abhilash Raj 08 Jul '19

08 Jul '19

Hi All, I have been recently working on adding rich text support through markdown in Hyperkitty so that emails can be made easier to read. The core design idea in my mind when working on this was building something that doesn't bother writers of plain text emails too much, but allows people to write emails in markdown. The supported syntax is limited Markdown, for example: Hyperkitty's Markdown Syntax ============================ - List items are supported - Even nested ones - Headers with `#` aren't supported, mostly due to their widespread use as comments in code shared on mailing lists. - You can **emphasize** text and _itcalize_ them too - Block code and `inline code` works. - URLs work like they usually do. - Images _do work_, but are disabled by default because of their potential for tracking users. They need to be enabled by administrators through a configuration flag. ``` def sample(): return "yay" ``` While text intentionally written for Markdown rending looks pretty good, plain text sometimes isn't as good. I have applied my branch[1] on both the Mailman installations for these two lists (mail.python.org & lists.mailman3.org). Any feedback or bug reports on weird looking stuff is welcome here or directly [on my PR][1] [1]: https://gitlab.com/mailman/hyperkitty/merge_requests/160 -- thanks, Abhilash Raj (maxking)

4 9

Mandatory First and Last Name
by andrew.bernard＠gmail.com 08 Jul '19

08 Jul '19

Is there a way to make the profile require users to fill out their name? Andrew

3 3