Is there a way to integrate Mailman3 user database with an already existing
Django application? And then, generate the list roster with a subset of
I've been scavenging the archives and failing to find an answer.
Victoriano Giralt CIO
University of Malaga
Note: signature.asc is the electronic signature of present message
> Q: Are you sure ?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email ?
I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)).
It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why.
I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom.
I have restarted all Mailman containers this morning, but this didn't help anything. Last entries in Mailman's smtp.log were when we restarted the containers:
Sep 18 08:30:02 2019 (36) Peer: ('172.19.199.1', 35454)
Sep 18 08:30:02 2019 (36) ('172.19.199.1', 35454) handling connection
Sep 18 08:30:13 2019 (36) ('172.19.199.1', 35454) EOF received
Sep 18 08:30:13 2019 (36) Connection lost during _handle_client()
Sep 18 08:30:13 2019 (36) ('172.19.199.1', 35454) connection lost
Sep 18 08:30:18 2019 (36) Peer: ('172.19.199.1', 37164)
Sep 18 08:30:18 2019 (36) ('172.19.199.1', 37164) handling connection
Sep 18 08:30:20 2019 (36) ('172.19.199.1', 37164) EOF received
Sep 18 08:30:20 2019 (36) Connection lost during _handle_client()
Sep 18 08:30:20 2019 (36) ('172.19.199.1', 37164) connection lost
The runners last ran at Sep 18 08:42:21 2019
The mailman.log updates constantly, but with "Sep 18 09:45:16 2019 (39) 172.19.199.3 - - "GET /3.0/users/" something something only or other http gets. A lot of them is 404 errors, but also a lot of "GET /3.0/lists/LISTNAME HTTP 200 responces, which should not be related.
In "uwsgi-error.log" I get some tracebacks, but since I don't think should be related to incoming mails, I'll leave the traceback for now.
Sep 18 10:07:47 postfix postfix/smtpd: connect from gateway[172.19.199.1]
Sep 18 10:07:47 postfix postfix/smtpd: 45DAA7E97BE94: client=gateway[172.19.199.1]
Sep 18 10:07:47 postfix postfix/cleanup: 45DAA7E97BE94: message-id=<A29DAD01610ED744A9D6F14880665668011C8A2C@P 1KITMBX01WC01.unicph.domain>
Sep 18 10:07:47 postfix opendkim: 45DAA7E97BE94: DKIM-Signature field added (s=default, d=listsgw.ku.dk)
Sep 18 10:07:47 postfix postfix/smtpd: disconnect from gateway[172.19.199.1]
Sep 18 10:07:47 postfix postfix/qmgr: 45DAA7E97BE94: from=<sender(a)example.com>, size=7988, nrcpt=1 (queue active)
Sep 18 10:07:47 postfix postfix/qmgr: warning: mail for [172.19.199.2]:8024 is using up 7844 of 7844 active queue entries
Sep 18 10:07:47 postfix postfix/qmgr: warning: you may need to reduce lmtp connect and helo timeouts
Sep 18 10:07:47 postfix postfix/qmgr: warning: so that Postfix quickly skips unavailable hosts
Sep 18 10:07:47 postfix postfix/qmgr: warning: you may need to increase the main.cf minimal_backoff_time and maximal_backoff_time
Sep 18 10:07:47 postfix postfix/qmgr: warning: so that Postfix wastes less time on undeliverable mail
Sep 18 10:07:47 postfix postfix/qmgr: warning: you may need to increase the master.cf lmtp process limit
Sep 18 10:07:47 postfix postfix/qmgr: warning: please avoid flushing the whole queue when you have
Sep 18 10:07:47 postfix postfix/qmgr: warning: lots of deferred mail, that is bad for performance
Sep 18 10:07:47 postfix postfix/qmgr: warning: to turn off these warnings specify: qmgr_clog_warn_time = 0
Sep 18 10:26:34 postfix postfix/qmgr: B34C07E980CA3: from=<LISTNAME(a)lists.example.com>, size=1219, nrcpt=1 (queue active)
Sep 18 10:26:34 postfix postfix/smtp: connect to sst-dk.mx1-dk.mailanyone.net[22.214.171.124]:25: Connection refused
Sep 18 10:26:34 postfix postfix/smtp: connect to sst-dk.mx1-dk.mailanyone.net[::ffff:126.96.36.199]:25: Connection refused
Sep 18 10:26:34 postfix postfix/smtp: connect to sst-dk.mx2-dk.mailanyone.net[::ffff:188.8.131.52]:25: Connection refused
Sep 18 10:26:34 postfix postfix/smtp: connect to sst-dk.mx2-dk.mailanyone.net[184.108.40.206]:25: Connection refused
Sep 18 10:26:34 postfix postfix/smtp: connect to sst-dk.mx3-dk.mailanyone.net[220.127.116.11]:25: Connection refused
Sep 18 10:26:34 postfix postfix/smtp: B34C07E980CA3: to=<RECIPIENT(a)foo.bar>, relay=none, delay=420673, delays=420673/0.05/0.2/0, dsn=4.4.1, status=deferred (connect to sst-dk.mx3-dk.mailanyone.net[18.104.22.168]:25: Connection refused)
/ Henrik Rasmussen
Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
Am I misunderstanding what a private archive is?
Is something wrong with my setup (which is hosted)?
Is there a way to create an additional mailing list field or lock down the current Description or Information fields so they are not modifiable by a list owner? The goal is to have a field that identifies the department or area a list belongs to so that it's easier to find if an owner leaves the organization and the owner needs to be updated on multiple lists.
I'm currently running a test setup of MM3 using Mark Sapiros approach with two venv. I also adopted his post-upgrade-script for the web part (django). Just some minutes ago I updated the packages of my test setup with pip3 where hyperkitty is now 1.3.0
When runnin the post-upgrade-script I get the following error message:
Execution of msgfmt failed: /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:630: duplicate message definition...
/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:273: ...this is the location of the first definition
msgfmt: found 1 fatal error
Not sure whether this is an error of MM3 or one of its dependency packages.
In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself?
2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below"
3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org
4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER?
5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows:
"Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account.
To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com"
6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list!
To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by
sending a message to....... I then get a notice:
"Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member"
7) While if they send FROM THE interface it goes through.
8) What I am confused about.
Signing up for an account should make them a member, right? Subscribing should make them a non member, no? But here it seems that both make them a non member. And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post.
Before I can move my actual members over from another mailing list provider, I want to make sure what works and what doesn't.
How does HyperKitty handle duplicate messages/message-ids across maillists?
We have quite a few lists that are members of other lists.
I'm in the process of importing our old Mailman 2.1 archives and seeing a
lot of duplicate message errors, and wondering if this is why.
Would new messages coming into Mailman be handled the same way?
I use Lithuanian language (it has special characters like ąčįū...) for regular message template feature. I noticed that some posts come correct, but some have question marks (?) in places of these characters. Looks like there is sittings trick. But footers adds mailman, so it should be always correct, or it depends on senders environment setup?
Both before and after upgrading tonight, my lists send out bizarre recipients that I cannot understand. It usually happens at the end of the distribution to other valid recipients.
Sep 5 10:05:54 www postfix/smtp: A5DF9FA14E: to=<0101016d00e302ec-4db56da5-fd69-4b5e-9327-292c55e13ea8-000000(a)us-west-2.amazonses.com>, relay=email-smtp.us-west-2.amazonaws.com[22.214.171.124]:587, delay=2.4, delays=0/0/2.2/0.22, dsn=5.0.0, status=bounced (host email-smtp.us-west-2.amazonaws.com[126.96.36.199] said: 501 Invalid MAIL FROM address provided (in reply to MAIL FROM command))
This behaviour is able to be replicated - it happens on every post.