- Mailman-users - lists.mailman3.org

ARC support
by Marvin Gülker 05 Jan '19

05 Jan '19

Hi everyone, I just stumbled over an in-progress standard called ARC. It is appearently intended to solve the problems DMARC causes for mailinglists if I understand correctly. Since I've not seen a summary of it somewhere, I just give the plain links to it: * Website: http://arc-spec.org/ * Draft: https://datatracker.ietf.org/doc/draft-ietf-dmarc-arc-protocol/ Will Mailman at some point support this new standard? Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

2 1

Avoiding the List name in TO or CC headers
by Asaf Ohayon 04 Jan '19

04 Jan '19

Hello I've made a list personalized ( =2 in mailinglist table), So in TO: I see the actual member, But still I have the list address in CC header, Can this be removed ? 10x

3 2

no mails to list members
by Thomas Stein 04 Jan '19

04 Jan '19

Hi all. I'm trying to upgrade my mailman2 installation to version 3. I thought lets test with on list first. I imported the list with: mailman import21 bla(a)lists.blabla.de bla/config.pck. This went well. Now i try to send an email to bla(a)lists.blabla.de but the message only got delivered to the mailman host. Jan 03 14:43:44 2019 (10434) Peer: ('127.0.0.1', 38784) Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) handling connection Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'LHLO shinymail.eu' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'MAIL FROM:<himbeere(a)meine-oma.de>' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) sender: himbeere(a)meine-oma.de Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'RCPT TO:<bla(a)lists.blabla.de>' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) recip: bla(a)lists.blabla.de Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'DATA' Jan 03 14:43:45 2019 (10434) ('127.0.0.1', 38784) Data: b'QUIT' Jan 03 14:43:45 2019 (10434) ('127.0.0.1', 38784) connection lost Jan 03 14:43:45 2019 (10434) Connection lost during _handle_client() No messages ar actually delivered to the list members. Can someone tell me where i have to look to solve this problem? The "Delivery status" is set to enabled. thanks and cheers t.

5 16

mailman3-suite not sending confirmation emails
by ccehb＠nus.edu.sg 04 Jan '19

04 Jan '19

Hi, This is my first experience using mailman. I recently downloaded and setup mailman3 suite which comes with hyperkitty. I don't really understand why the email is not working. I had an external smtp server (mymailserver.com) residing on different IP from my web server that hosts mailman stuff. I had modified settings.py with debug = False and added the following: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'mymailserver.com' EMAIL_PORT = 25 I also added these inside mailman.cfg [mta] outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: mymailserver.com smtp_port: 25 Thanks for your help! I check the logs but there isn't anything. When I sign up, nothing happens and I can't figure out why?

2 1

mailman shell
by Alan So 03 Jan '19

03 Jan '19

Sorry for my ignorance. May I know what should be imported before using mailman shell within Python? $ python3.6 Python 3.6.6 (default, Aug 13 2018, 18:24:23) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> command = cli('mailman.commands.cli_withlist.shell') Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'cli' is not defined Link to documentation: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…

3 6

Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg)
by Abhijith PA 03 Jan '19

03 Jan '19

Hi On Thursday 03 January 2019 06:39 AM, kelly.close(a)lrewater.com wrote: > Yes - lists are known to Hyperkitty but no, no Archived-At header > in received posts. > > But, Bingo! > > I hadn't looked at the log file immediately after trying to post a > message so I missed this. I don't know the solution yet but ... > what is this telling me? Something doesn't have the permissions it > needs somewhere... > > Jan 02 18:01:15 2019 (616) 127.0.0.1 - - "GET > /3.0/lists/mailman3_test.udfcd-lists.org/member/udfcd.alert(a)gmail.com > HTTP/1.1" 200 484 Jan 02 18:01:18 2019 (609) ACCEPT: > <20190103010115.530.63813@udmailman> Jan 02 18:01:18 2019 (615) > HyperKitty failure on > https://udfcd-lists.org/mailman3/hyperkitty/api/mailman/urls: > <html><title>Auth required</title><bod$ <h1>Authorization > Required</h1></body></html> (401) ... (that line repeates 4 times) > Jan 02 18:01:20 2019 (606) Exception in the HyperKitty archiver: > <html><title>Auth required</title><body> <h1>Authorization > Required</h1></body></html> Jan 02 18:01:20 2019 (606) Traceback > (most recent call last): File > "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", > line 154, in _archive_message url = self._send_message(mlist, msg) > File > "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", > line 210, in _send_message raise ValueError(result.text) > ValueError: <html><title>Auth required</title><body> > <h1>Authorization Required</h1></body></html> What is your base_url in mailman-hyperkitty.cfg ? --a

2 2

Mailman3 and Centos 7
by brian＠emwd.com 03 Jan '19

03 Jan '19

Just a heads up for those wanting to install Mailman3 on a Centos 7 server, be aware of FirewallD. There are a number of ports and services you have to tell it to allow in order to get Mailman3 functional. More experienced sysadmins might know this but I did not.

2 2

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

Customizing Look and Feel?
by Joel Lord 31 Dec '18

31 Dec '18

Is it possible to customize the look at feel of the web interface at all? I have some lists that really require that subscription requests include full name, to make the workload on the moderators, well, workable in keeping a closed list tight. I've found where the "Your name (optional)" text is in list_forms.py, but modifying that strikes me as a poor plan. Changing that text would be lovely. Actually making that field required would be seriously awesome. Is this possible in the current code base (3.2.0) without doing ill-advised things modifying source code? Thanks! -- Joel Lord Web Administrator, Alpha Psi Omega Grand Cast etc... etc... etc...

2 1

Converting non-members to members
by Alan So 27 Dec '18

27 Dec '18

Postorius is not currently exposing non-members management. Our Mailman 2 users are currently using accept_these_nonmembers, hold_these_nonmembers and reject_these_nonmembers. We know that mailman import21 will change these to nonmembers entries in Mailman 3. Since list owners will still want to manage them, we tend to move all of them to members and turn off delivery status for them. However, we met some difficulties when we try to develop using mailman client. 1) If those non-members addresses already exist as members, we will encounter error when we subscribe for them: urllib.error.HTTPError: HTTP Error 409: b'Member already subscribed' 2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: moderation_action' 3) We cannot change the preference: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: delivery_status' Are there any better ways to enable the list owners to manage those previously configured nonmembers' addresses through the web? Otherwise, we probably need to have some manual effort to overcome the above three issues. We know that we can always do the above manually but we got a lot of lists to migrate to Mailman 3.

2 3