- Mailman-users - lists.mailman3.org

$member does not appear to be dereferencing correctly in moderated subscription requests
by Joel Lord Jan. 8, 2019

Jan. 8, 2019

So I'm having an issue with a new 3.2 install. All the lists I have are set to confirm + approve on new subscriptions, but it seems that no matter how a new subscription come in, it does not actually pass the applicant's name to the moderator. I've tested now with a new email address previously unknown to the system and made sure I filled in the name field in the form. I've tested with an email address previously KNOWN to the system (subscribed to other lists) that has its display name fields filled in AND filled in the name on the subscription form, and yet again with that account having cleared out the display name fields associated with the account. In all cases I was careful to be sure to fill in the name on the subscription form. Buried somewhere in the templates documenation I found that the $member template variable in the list:admin:action:subscribe.txt template is supposed to be both the email address and the display name of the person applying to subscribe, but it just doesn't appear to be coming up as more than just the email address. Have I missed something horribly, or did I come across a bug? -- Joel Lord

2 1

File Attachments
by brian＠emwd.com Jan. 8, 2019

Jan. 8, 2019

Happy Monday everyone. Are there any plans to include the ability to attach files via the web interface? Or did I miss something? Thanks, Brian

5 9

Mass subscriptions
by Enrique Terrazas Jan. 7, 2019

Jan. 7, 2019

Hello, One of our customers has requested a list that will include around 50,000 subscribers. The customers has provided the email addresses in a CSV file, is there a way to import this data to a mailman list from a CSV file or is the Mass Subscribe option the preferred method? Best regards, Enrique J. Terrazas

2 2

ARC support
by Marvin Gülker Jan. 5, 2019

Jan. 5, 2019

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 Jan. 4, 2019

Jan. 4, 2019

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 Jan. 4, 2019

Jan. 4, 2019

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 Jan. 4, 2019

Jan. 4, 2019

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 Jan. 3, 2019

Jan. 3, 2019

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 Jan. 3, 2019

Jan. 3, 2019

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 Jan. 3, 2019

Jan. 3, 2019

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