- Mailman-users - lists.mailman3.org

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

Verification Failed Error
by brian＠emwd.com 23 Dec '18

23 Dec '18

I am trying to get the reset password function to work but I am getting this error message: smtplib.SMTPRecipientsRefused: {'email(a)address.com': (550, b'Verification failed for <postorius(a)mailman3.hostname.com>\nUnknown user\nSender verify failed')} Brian

4 31

Docker Installation of Mailman -- The Hyperkitty Chronicles
by brian＠emwd.com 23 Dec '18

23 Dec '18

Using Maxking's docker project to install mailman3, I have a fairly functional mailman3 installation. However Hyperkitty is not archiving or showing list participants like: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ This is my page: https://mailman3.emwd.com/hyperkitty/list/testlist@mailman3.emwd.com/ The docker documents really don't say much about getting HK up and running. Brian

3 9

Mailman3 and Exim setup
by brian＠emwd.com 21 Dec '18

21 Dec '18

I am installing Mailman3 via the Docker image provided by maxking. In his instructions he says: "To use Exim4, it should be setup to relay emails from 172.19.199.3 and 172.19.199.2." I am not sure where in the exim.conf file this is done. I took a guess at: hostlist relay_from_hosts = localhost : 172.19.199.3 : 172.19.199.2 Was my guess wrong?

4 4

ONLY moderator senders messages
by erlonmz＠hotmail.com 21 Dec '18

21 Dec '18

how to configure the mailman 3 for only moderators to send messages?

1 0

Mailman3 via Docker and NGINX
by brian＠emwd.com 19 Dec '18

19 Dec '18

I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there: server { listen 80; server_name `sitename.com`; location /static/ { alias /opt/mailman/web/static/; } location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation? Thank you for any assistance, Brian Carpenter

4 9