October 2018 - Mailman-users - lists.mailman3.org

by Marc Sluiter

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

3 weeks

4
4
0 0

Mailman 3 Installation Assistance

by brian＠emwd.com

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

2 months, 3 weeks

4
28
0 0

delete examples.com site

by enrique.terrazas＠utsa.edu

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 months, 2 weeks

3
4
0 0

Hyperkitty Archives - Sidebar years/months

by Enrique Terrazas

Hello, I’m going through importing archives from mm2 to mm3. One of the lists I’ve imported has messages going back to 11/2013. I was able to successfully import the lists settings using: mailman import21 lists(a)domain.com<mailto:lists@domain.com> /path/to/list/config.pck This successfully imported lists owners, moderators, subscribers, & settings. I then imported the messages with the following command: python /path/to/manage.py hyperkitty_import -l list(a)domain.com<mailto:list@domain.com> /path/to/list.mbox —since 10/01/2013 I used that date because it is older than the first message sent to the list: 11/13/2013 And followed that up with the update index command: python /path/to/manage.py update_index_one_list list(a)domain.com<mailto:list@domain.com> This successfully imported all the messages from 11/13/2013 through 09/30/2018. Here is where I’m facing two issues: * Messages from October 2018 were not imported * The sidebar only shows the year 2018. Fdasfds If I modify the URL to go to https://my.domain.org/hyperkitty/list/list@domain.com/2013/11 the archived emails show up fine. October 2018 shows two test messages I’ve sent but not any of the messages from October 2018 that should have been imported. Is there something additional that needs to be done to show the previous years and months in the sidebar? Thanks, Enrique

4 months

4
5
0 0

Flushing/syncing hyperkitty with mailman

by Eric Abrahamsen

I've got mailman running on Ubuntu 14.04, with systemd service files to govern the mailman and hyperkitty qcluster processes. I notice in the systemctl status call for the qcluster command that there are a bunch of errors like: [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Is there something more I should be doing to sync hyperkitty's database with mailman? I've got the crontab file in place, and that appears to be running without error. Anything else? Thanks, Eric

4 months

4
5
0 0

GDPR - save subscriptions confirmation emails

by contact＠maadix.net

Hi, I am new in the list. I have been looking for this topic in the archives in order to avoid duplicate, but I could not find any thread. According to the new GDPR rules, lists owners need to have a confirmation from subscribers, and this is easy to do with Mailman 3. What I can't figure out is how to save all the confirmation emails received from users. I only see the confirmations commands emails in the logs, Is there another place/way to store them? For GDPR compliance it is important to be able to demonstrate that you received the confirmation, in case you may need it in the future. Bests Maddish -- *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

5 months, 3 weeks

3
4
0 0

Change domain, easy?

by Thor Atle Rustad

Hello list, How can I change the domain (from spammedtodeath.example.org to newdomain.example.org. The change should apply to all relevant settings as well as existing lists. Sincerely, Thor Atle Rustad

9 months, 1 week

2
1
0 0

Auth question

by David Krantz

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

9 months, 2 weeks

5
19
0 0

Avoiding the List name in TO or CC headers

by Asaf Ohayon

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

9 months, 2 weeks

1
0
0 0

How to get Mailman core to provide more debug info in a running environment

by Henrik Rasmussen

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/threa... 2) http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.ht... Henrik Rasmussen

9 months, 2 weeks

3
4
0 0

2019

2018

2017

2016

Mailman-users October 2018