Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/26/20 12:33 AM, Alan So wrote: > Thanks. Just filed an issue: > https://gitlab.com/mailman/mailman/-/issues/725 Thank you for your "well formed" issue. I have started to work on this, but I have run into a snag. The patch at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> doesn't work. The problem is msg.get_all(header, []) does not parse the header and return a list of addresses. It just returns a list, the items of which are the raw values if the header instances in msg. I.e., if there is only one Cc: header, msg.get_all('cc', []) returns a list of one string which is the raw value of that header. If there were two Cc: headers in the message it would return a list of two strings with the two raw values. Thus, we would need to parse the strings returned into the individual email addresses. The simple minded way to do that is addrs = [] for hdr in msg.get_all(header, []): for addr in hdr.split(','): addrs.append(parseaddr(re.sub('[\r\n]', '', addr))) but that will fail if the header contains a quoted display name containing a comma such as "last, first" <user(a)example.com> So, I need to go back to using getaddresses, but do the unfolding first. Watch the issue for the final fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: List in list, mutiple reply-to addresses

by Mark Sapiro

On 11/25/21 11:00 PM, Stefan Bauer wrote: > Mother: > Anonymous list: No > First strip reply to: No > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > > > > Daughter: > Anonymous list: No > First strip reply to: Yes > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > Because of DMARC mitigation, you can't do what you want. With the settings you have the mother list puts the original From: in Reply-To: and it's own address in From:. Then regardless of what the daughter does with the incoming Reply-To:, it will add the incoming From: to Reply-To: so the Reply-To: of a message from the daughter will always contain the address of the mother. The best you can do, unless you are willing to set DMARC mitigation action: to No DMARC mitigations is what you started with which is First strip reply to: No on the daughter which will at least put the original From: to the mother in Reply-To: from the daughter along with the mother's address, but you can't remove the mother's address from the daughter's Reply-To: because DMARC mitigation will always put it there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 10:59, bob B via Mailman-users wrote: > We had an issue where a program went rogue and sent out 30k email alerts to one of our lists, so now I have a few questions. > > When the issue happened I turned on emergency moderation and we have resolved the issue so.. > > 1. How do I easily delete 30k of held messages? It looks like the GUI only allows me to do 200 at a time? is there a way to flush all held messages easily? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the thread containing it. > 2. When I enabled Emergency moderation, I expected it to stop notifying the admin on every held message, but it appears that is not the case? Also, does it reply to the sender of every held message when Emergency moderation is on? > > it seems like the steps are: > turn on "Emergency moderation" > turn OFF "Notify users of held messages" > turn OFF "Admin immed notify" MM 2.1 didn't notify the admins of emergency holds. This is not the case in MM 3. It probably should be, but isn't. Senders are or aren't notified per "Notify users of held messages". So the steps above are correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: using SSH/TLS with external MTA

by Mark Sapiro

On 7/24/24 06:35, Roland Giesler via Mailman-users wrote: > I have managed thus far to get things working on my new install, but I > need to use a secure logon to send mail from an external MTA. I have > set up: > > /etc/mailman/mailman.cfg: > > smtp_host: box2.gtahardware.co.za > smtp_port: 465 > smtp_user: roland(a)giesler.za.net > smtp_pass: <hidden> > smtp_secure_mode: smtps > smtp_verify_cert: no > smtp_verify_hostname: no This looks OK, but > I'll get a cert installed later, for now just want to get it going. The `no` values for smtp_verify_cert and smtp_verify_hostname may be part of your issue. ... > "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line > 125, in _send > self.connection.sendmail(from_email, recipients, > message.as_bytes(linesep='\r\n')) > File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail > raise SMTPRecipientsRefused(senderrs) > smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, b'4.7.1 > <roland(a)giesler.za.net>: Relay access denied')} > > However, the mailserver is in daily use and accept logon all the time. I > believe I'm missing something that should be installed to make SMTPS > (SSL) work, but what? It is the mail server at box2.gtahardware.co.za that is refusing to relay this message. I think this issue needs to be resolved in that MTA's configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/27/25 12:36, Kim Sunggun via Mailman-users wrote: > script: > #!/usr/bin/env python3 > import smtplib > > host = 'localhost' > port = 25 > connection = smtplib.SMTP(host=host, port=port) > connection.ehlo() > connection.quit() > > result: > Traceback (most recent call last): > File "/opt/mailman/./testone.py", line 7, in <module> > connection = smtplib.SMTP(host=host, port=port) > File "/usr/lib64/python3.9/smtplib.py", line 255, in __init__ > (code, msg) = self.connect(host, port) > File "/usr/lib64/python3.9/smtplib.py", line 341, in connect > self.sock = self._get_socket(host, port, self.timeout) > File "/usr/lib64/python3.9/smtplib.py", line 312, in _get_socket > return socket.create_connection((host, port), timeout, > File "/usr/lib64/python3.9/socket.py", line 856, in create_connection > raise err > File "/usr/lib64/python3.9/socket.py", line 844, in create_connection > sock.connect(sa) > ConnectionRefusedError: [Errno 111] Connection refused So you are doing the same thing Django allauth is doing with the same result. Do you even have an MTA listening on localhost, port 25? You need to figure out what settings you need to be able to connect to your outgoing MTA and set EMAIL_HOST EMAIL_PORT and maybe some of EMAIL_HOST_USER EMAIL_HOST_PASSWORD EMAIL_USE_TLS EMAIL_USE_SSL EMAIL_SSL_CERTFILE EMAIL_SSL_KEYFILE appropriately so you can connect to the MTA. If outgoing mail from Mailman works, look in the [mta] section in mailman.cfg for the appropriate settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/15/19 3:45 AM, Wolfgang Bock via Mailman-users wrote: > > That doesn't solve the problem. I changed that in mailman-web.py > (MAILMAN_REST_API_URL = https://localhost:8001) and after that in > mailman.cfg (use_https: yes). But got the same errormessage on postorius > website. You posted this log excerpt: Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type The first 3 GETs are a normal sequence of GETs from Postorius when you go to the Mailing Lists view. That should be followed by a GET like "GET /3.1/domains/domain.tld HTTP/1.1" where domain.tld is a configured domain. Do you have any domains configured?/0.9'? I'm not sure what the issue is. You have an older version of mailmanclient < 3.2.3a1 which uses httplib2 rather than requests. https://pypi.org/project/httplib2/ says: HTTP and HTTPS HTTPS support is only available if the socket module was compiled with SSL support. but I don't think this can be the issue because the first 3 GETs work. You might try upgrading mailmanclient to 3.3.0. I don't know if that will help, but it may. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 6/30/20 7:03 AM, Brian Carpenter wrote: > On 6/30/20 9:56 AM, tom(a)gather.coop wrote: >> I have a Mailman 3 server up and running but I'm terrified to migrate >> to it from my existing Mailman 2 provider for fear that services like >> Gmail will randomly start blacklisting my IP with little I can do >> about it. I have SPF records set up so I'm hoping I'll be Ok but I'd >> like to have a backup plan. ... > There is no reason to be afraid if you are sending out legitimate > communications. SPF records will help. You will also need to enable > DMARC mitigation on your lists and Mailman 3 does that very well as > Mailman 2 did. It also helps if you sign your outbound mail with DKIM. > With those 3 things in place, you should have no problem sending mail. > Keep in mind AT&T will probably block you if the IP address you are > using is new. That is standard practice for them. It's easy to get that > block remove. Same goes for Comcast using their Vader RBL. You also need to ensure you have full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. That together with SPF and DKIM signing of outbound mail is virtually essential for deliverability. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Mark Sapiro

On 3/29/24 12:34, bob B via Mailman-users wrote: > Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. ... > So where can I look to try to determine a cause? > If it happens again, what and where can I cook to troubleshoot before restarting the service? One of the runners has died, most likely the `out` runner, but possibly another. The missing messages are stuck in a queue. Do ``` ls -laR /opt/mailman/core/var/queue ``` to see in which queue the messages are. The runner that processes that queue is gone or possibly stuck. Do ``` ps -fwwu mailman|grep runner= ``` when things are working to get a list of what runners should be there. Do it again when things aren't working to see what's missing. There also should be something in mailman.log about why the runner died, but if it was killed for some external reason, there may not be anything. Look in `syslog` for something like an out of memory (OOM) or other issue that caused the runner to die. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/14/24 21:40, adam.heathcote(a)utas.edu.au wrote: > Hi Mark, > > Sorry about the delay in replying. > > You're correct, I am clicking on the list in the Mailing List view. > > Navigating to the list URL directly while not logged in produces the same error and even produces the error when a different user is logged in. Now it's my turn to apologize. I've been traveling. In your original post you wrote "I've tried removing it and reimporting it to no avail." What exactly does this mean. You removed the list how? Then you reran the import21. Was the list broken at that point, or only after removing the old owners and adding yourself? What if you try the following steps in order and try to view the list in Postorius after each step. - remove the list with `mailman remove list(a)example.com` and recreate it with `mailman create list(a)example.com` - run `mailman import21 list(a)example.com path/to/config.pck` - in Postorius, add yourself as owner. - in Postorius, delete one of the other owners. - repeat the deletion and viewing the list for the other unwanted owners one at a time. If the view throws the error at some point, after which step? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Customise Postorius templates?

by Mark Sapiro

On 2/1/22 09:47, Duane Raymond wrote: > Hi, > > I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying > venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html > to > var/templates/lists/summary.html > > As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. The var/templates directory has a specific structure and is only for custom list specific, domain specific and sitewide templates used for notifications from Mailman core. It has nothing to do with Postorius or HyperKitty templates. > Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!) I don't know about a `best` way, but the way I do this is to keep all local mods as patches to the base and apply those patches as part of the upgrade process. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Problem replying via Hyperkitty

by Mark Sapiro

On 6/30/22 10:07 AM, Jeff wrote: > Hello Everyone, > > A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: > > [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) This looks like the post of the reply to HyperKitty. What does the user see in response to that? There should be a brief alert popup indicating the message was sent. > A couple of basic questions: > > 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? To the list. > 2) what log files could I check to see what — if anything — happens to these emails? Mailman's var/logs/mailman.log, The MTA logs and the Django logs. > 3) Are there any settings that need to be set to make this work? There shouldn't be as long as the list and archiving work. Note, a user can select 'Use email software' when replying which should open a composition dialog in their email client to post a reply yto the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: No e-mail distribution after import of archive

by Mark Sapiro

On 11/12/24 00:52, Markus Grandpré wrote: > > In smtp.log I found: > > Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO > mailman-app-test.kim.uni-konstanz.de' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL > FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: > markus.grandpre(a)uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT > TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: > Import_mm3_testliste(a)mailman-test.uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost > during _handle_client() > > I have no idea why there is a "connection lost". What do you think? How > can I increase the log level? This is delivery of the message to Mailman. `connection lost` is normal and not a problem. This has nothing to do with your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Which folder should I share between pods with kubernetees persistentVolumeClaim ?

by Mark Sapiro

On 2/6/25 02:37, antoine.depoisier--- via Mailman-users wrote: > > There are all the folders in mailman > archives cache data etc lists locks logs master.pid messages queue templates Here's my opinion. archives - If the prototype archiver is enabled for a list, its posts are archived here in maildir format. This should be shared for consistency, but if you don't care about this, you can put `enable: no` in the [archiver.prototype] section of mailman.cfg to disable it. cache - you're already sharing data - doesn't need to be shared unless it contains a sqlite mailman.db that's actually used. etc - doesn't need to be shared. lists - should be shared as it contains the mailboxes (digest.mmdf) for accumulating messages for a list's digest locks - should be shared master.pid - must not be shared as it contains the pip of the master process running on that node. messages - you're already sharing which you should. queue - this is tricky. If it isn't shared once a message gets queued in virgin/ or in/ on a node, only that node's runners will process it through its queues. This may have an impact on load balancing. templates - doesn't need to be shared, but should be synced between nodes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/2/21 12:48 AM, klillipuu(a)gmail.com wrote: > Hello All! > > I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. > So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). > I also mention, that hyperkitty is a pretty old version - 1.1.4. > The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. > Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? It would be good to upgrade. Current HyperKitty/Postorius/Django is Python3 which will remove your dependency on Python 2.7. Also, there have been many performance improvements in more recent versions which may solve your issue. Your gateway timeout issue is a uwsgi time limit. You can increase that in your uwsgi configuration. > Extra information: > * I have also noticed some memory violation issues which has caused by uwsgi. > * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Are these coincident with the gateway timeouts or do they occur at different times? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/14/24 08:42, jkoral(a)luc.edu wrote: > joetest(a)listservnew.luc.edu is the list, but in postfix_lmtp, it is showing up as joetest(a)luc.edu. Where can I change that? I tried changing the domain and site, but it still has not changed. The list has a mail_host attribute which is set when the list is created. Presumably, you created the list as `joetest(a)luc.edu`. You have to change the mail_host attribute of the list, but it may be easier to just delete it and create a new joetest(a)listservnew.luc.edu list. Then you can ignore everything below. To change the mail_host for the list you can do a database query or use `mailman shell`. The database query is ``` UPDATE mailinglist SET mail_host = 'listservnew.luc.edu' where list_name = 'joetest'; ``` The `mailman shell interaction is ``` $ mailman shell -l joetest(a)luc.edu Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> m.mail_host = 'listservnew.luc.edu' >>> commit() ``` If you do either of the above to change the mail host, you probably need to do `mailman aliases` to regenerate the files for Postfix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 15:49, Christian via Mailman-users wrote: > Mail.log > > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from > box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: > client=box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: > header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; > from=<christian(a)naturalintelligence.us> > to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP > helo=<box.ecovillage.cc> > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: > message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: > from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from > box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: > to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces(a)lists.ccalternatives.org? Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Moving existing lists to a new domain

by Mark Sapiro

On 9/18/24 10:13, Jeremy Stanley wrote: > > Since all the lists for the given domain will be moving to the same > unused new domain on the existing server, and can move at the same > time, I suppose this could be done through (offline if necessary) > backend database update queries. Yes. For the mailing list, the only changes needed are to the mailinglist table; A query like ``` UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = 'old_domain'; ``` would do, but this leaves the question of list_id. According to RFC 2919, section 4, the list_id should not change, but this is problematic in that if it isn't changed, a Postorius URL like https://example.com/mailman3/lists/list_name@new.domain will retrieve the list, but https://example.com/mailman3/lists/list_name.new.domain will not work. It would need to be https://example.com/mailman3/lists/list_name.old.domain so to reduce confusion, it may be better to update the list_id values A query like the following after the above should do it ``` UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE mail_host = 'new_domain'; ``` For HyperKitty, similar changes need to be made to the hyperkitty_mailinglist table. The `name` column entries need to be changed from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column entries need to be changed from `listname.old.domain` to `listname.new.domain` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/28/20 10:20 AM, Shashikanth Komandoor wrote: > > I tried for the command to know if any entry in the "address" table for > which 'id' is not an integer. > > But unfortunately, I could not get any command or idea how to find that. > > But out of my extra talent, I tried the below commands which, I thought, > may print the records which contain a non integer id value. ... > select id,email from address where id NOT BETWEEN 1 AND 84203; > id | email > ----+-------(0 rows) > mailman=# select id,email from address where id NOT BETWEEN 1 AND 84202; > id | emai> -------+-----------------------------> 84203 | user(a)exampl.com > > *1 and 84203 are the minimum and maximum values of the id:* > > Please see the above outputs and suggest if anything possible or please let > me know the command what should I run to find a non integer id value. > The above looks qood to determine if there is a non-integer value. > I also doubt this error as if my REST API is contacting postgresql in a > delayed manner. If possible, can you say what optimal setting I can do at > Postgresql so that faster responses would be given to REST API. I'm out of ideas. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Docker-Setup: example.com in test mails

by Mark Sapiro

On 3/28/22 00:04, Bjoern Franke via Mailman-users wrote: > > Thanks for your reply. It seems the probes were triggered by some > rejected example.com mails and I have no idea where the example.com > mails are coming from. I think what you are seeing must be some kind of spam. If not if you could post the complete raw message of one of these probes or probe bounces, I'll look further. > Some users also reported they got some "unsubscribed due to bounces" > messages but the bounce.log contained only entries for them 7 days ago. And were they unsubscribed? In general, unsubscription does not occur until some time after bounces are recorded. At some point, bounce score reaches threshold and a probe is sent. The probe may not bounce for days if the bounce is some downstream timeout. When the probe bounce is received, the user's delivery is disabled by bounce. This starts a process where the user is sent a warning at intervals until a limit is reached and the user is finally removed. The default settings are: bounce_you_are_disabled_warnings = 3 bounce_you_are_disabled_warnings_interval = timedelta(days=7) which means the user is sent 3 warnings, one immediately, one after 7 days and one after 14 days until finally being unsubscribed after 21 days. An entry 7 days ago could be a bounce of a warning message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Mark Sapiro

On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > --------------------------------------------------------------------------- > First issue:Postfix v3.5.8 on RHEL 8. > The below is from journalctl -xe: > --------------------------------------------------------------------------- > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > directory > > I manually created the var_dir: /opt/mailman3/mm/var directory > specified in the mailman.cfg file. > How do I find out how to populate the postfix_domains.db files, and > the postfix_lmtp.db file? The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. > --------------------------------------------------------------------------- > Second issue: Postgresql authentication. > PostgreSQL v10.23. > --------------------------------------------------------------------------- > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > same complex password in the mailman3 config file: > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 I don't think you should have two /mailman3 at the end the form is `postgresql://user:password@host:port/database_name` The default port is 5432. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Dropdown problem in postorius due to bootstrap

by Mark Sapiro

On 7/9/24 1:18 PM, Greg Newby wrote: > (My first post) > > As has been observed, the Ubuntu 24.04 LTS packaging for native Mailman3 > can be challenging. I've been solving all kinds of issues, and I'm writing > here about something I've so far been unable to solve. Are you using the Debian/Ubuntu packages? If so, this may be a Debian issue. See https://wiki.list.org/x/12812344 ... > I've dug deeply into this. The relevant <script> is bootstrap.min.js. > Postorius (via django) is using version 5.3.1 via package libjs-bootstrap5: > > ** This is what django is using: > /usr/share/bootstrap-html/js/bootstrap.bundle.min.js -- version 5.3.1, > linked to: > /usr/share/javascript/bootstrap5/js/bootstrap.bundle.min.js > > /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js The Gnu Mailman project's postorius ships with postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js version 5.1.3 ... > By temporarily replacing > /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js > I have tried moving back to 4.6.1 (from libjs-bootstrap4). I have also > retrieved the latest 5.3.1 from the CDN, which is slightly different but > doesn't change the error: > https://cdn.jsdelivr.net/npm/bootstrap@5.3.1/dist/js/bootstrap.bundle.min.js Try using the ones from https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/static/pos… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Moderation of posts via email is not working in mailman 3

by Shashikanth Komandoor

Thank you Mark Sapiro for your response. After going through the discussion at the link you provided, I understood as of now, it is not possible to moderate the posts through the mails in Mailman 3. But since the user is getting the "confirm" attachment to the mail, the users are getting confused. Is there any work around to achieve this? or Is there any way to remove that "confirm" attachment so that users would not get an idea of confirming via email? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 30, 2020 at 2:46 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/29/20 12:24 AM, Shashikanth Komandoor wrote: > > > > Is there any bug or limitation in mailman 3 or if I am doing > > any wrong at the server side? Please suggest. > > > > This is a known issue in Mailman 3. See > <https://gitlab.com/mailman/mailman/-/issues/169>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years, 1 month

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: > I'm trying to set up mailman3 on two hosts, one of which runs core + > exim, the other runs postorius (&possibly hyperkitty). > > I have I think got core set up correctly, and postorius is sort of > usable, but anything in the web ui that talks to core ends up with a > white screen. > > I think what is happening is a postorius URL ends up with the core (or > perhaps no) hostname, and as there's nothing there to answer it fails. What are your Django settings for MAILMAN_REST_API_URL, MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with the [webservice] settings for hostname, port, use_https, admin_user and admin_pass in mailman.cfg in core and is the port open to the outside on the core machine? > I've checked the settings and I don't think I have misconfigured > postorius. Is it possible that the bad url is being passed from core to > postorius in some way and reused without changing the host? > > In the config at present, both hosts are visible to the browser, and > each host can communicate with the other. > > Any ideas on how to pin down the problem better? Do you see REST requests from the Postorius machine in core's mailman.log and access.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Change Member's Address

by Mark Sapiro

On 1/13/26 9:08 AM, dap1--- via Mailman-users wrote: > I got a different user set up as superuser using a gmail address. However, I get to the member's management page but cannot change anything. I see update buttons but they don''t seem to so anything although I get a banner at the top saying the user was updated. What am I doing wrong? You can't change the user's address that way. You can only update the display name, the verified status of the address and the moderation and delivery mode of subscriptions. I think you can do it in `mailman shell` like this ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> um = getUtility(IUserManager) >>> addr = um.get_address('address_to_change') >>> addr.email = 'new_address' >>> commit() ``` However, the preferred way is for the user to log in, go to https://whatever/accounts/email/, add the new address to their account, make it primary, go to the list info page at https://whatever/lists/LIST, and if their Subscription Address is still the old address (because they weren't subscribed by primary address), click Manage Subscription and change it, and then possibly remove the prior address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users] Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:21 AM, Nate Coraor wrote: > > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. I'm trying to get a new > list to behave the same way so I can figure out what's going on without > spamming a production list, but have been unsuccessful: despite setting > nearly all the list options the same as the old lists, new lists pass HTML > portions and attachments just fine. > > I've verified the settings using mailing list objects directly with > `mailman withlist` on the command line and the only differences are things > that I can't imagine would be related like admin_notify_mchanges, > advertised, and archive_policy. Are there are really old options that can't > be accessed via mailing list objects obtained with `withlist` on the > command line? No, there aren't "hidden settings" The relevant settings are filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext These are exactly analogous to the MM 2.1 settings filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext and should behave the same way. Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: MM3 templates

by Mark Sapiro

On 2/15/23 08:09, Odhiambo Washington wrote: > > [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > total 48 > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. > -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt This template is used in a domain context. It will never be accessed here. It needs to be in /opt/mailman/mm/var/templates/site/en/ or /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ > -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt > -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt > -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt > -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt The generic footer is used for both regular messages and digests if there isn't a specific regular or digest footer. In this case, you have both so the generic footer won't ever be used. > -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt > -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt > -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt > -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt > -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt Are the other templates such as list:member:regular:footer.txt used? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Problems getting started with postorius

by Mark Sapiro

On 11/13/24 16:46, Alain D D Williams wrote: > > I eventually tracked it down. The problem was that I had signed in with an > account "addw@localhost". That, for some reason, failed validation above. > I hacked the database and changed to "addw(a)localhost.localdomain" and creating > the new domain worked. > > I could send email to addw@localhost - so at the MTA level it is correct. > > So please can the initial account creation do the same validation as does > adding a new domain. Mailman doesn't allow local, unqualified addresses, see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/validate… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/emai… On the other hand, Account creation/validation is done by django-allauth over which we have no control. > I have looked but cannot find any documentation on postorius than > https://docs.mailman3.org/projects/postorius/en/latest/ > which is not helpful for a user or system admin. Can you point me to something > better. Unfortunately, there is not user/list owner documentation for Postorius. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I did it via pip and all seems to be working, but when I try to discard > or accept any message via postorius it shows a Forbidden 403 error CSRF > verification failed. > > In my settings.py I have commented out these variables: > > # Other security settings > # SECURE_SSL_REDIRECT = True > # If you set SECURE_SSL_REDIRECT to True, make sure the > SECURE_REDIRECT_EXEMPT > # contains at least this line: > # SECURE_REDIRECT_EXEMPT = [ > # "archives/api/mailman/.*", # Request from Mailman. > # ] > # SESSION_COOKIE_SECURE = True > # SECURE_CONTENT_TYPE_NOSNIFF = True > # SECURE_BROWSER_XSS_FILTER = True > # CSRF_COOKIE_SECURE = True > # CSRF_COOKIE_HTTPONLY = True > # X_FRAME_OPTIONS = 'DENY' > > I've been messing with them whith no results. It's like it lacked some > value in some template... It's not an issue with the code per se or the templates. These updates are all installed on mail.python.org and lists.mailman3.org and are working fine. After upgrading did you run django-admin collectstatic --clear django-admin compress django admin migrate If you have and it doesn't help, you probably need to add CSRF_TRUSTED_ORIGINS to your settings.py. See https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins and note the differences between Django <4.0 and >=4.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 10:12, andrea.janna.unipd(a)gmail.com wrote: > >>From the database debug log I guess that mailman gatenews abruptly terminates the database connections. > For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry. > > 70759 Connect mailman3web@localhost on mailman3web using Socket > 70759 Query SET sql_mode='STRICT_TRANS_TABLES' > ... > 240131 18:54:34 70759 Quit > > There is a "Quit" at the end. > While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end. You could try the following in `mailman shell` ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager).mailing_lists: ... print(mlist.fqdn_listname) ... (here should be a list of your mailing lists) >>> ``` Does this produce the expected list of mailing lists and does it produce the error in the database debug log? If it does produce the expected list of mailing lists and the error in the database debug log, I'd say this is some issue between SQLAlchemy and MariaDB, but it seems harmless. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users]New Mailman 3 users list

by Mark Sapiro

I'm happy to announce a new list for Mailman 3 users and others interested in Mailman 3. This list is running on a new Mailman 3 installation at lists.mailman3.org. The list's posting address is <mailman-users(a)mailman3.org>. The list's info page is <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> and its archives are at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/>. The top level Postorius page is <https://lists.mailman3.org/mailman3/> and the HyperKitty archiver is at <https://lists.mailman3.org/archives/>. You can subscribe by email by sending a blank message to <mailman-users-join(a)mailman3.org> and responding to the resulting confirmation request. You can also subscribe by going to the info page at <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>, logging in and subscribing. Log in offers three options. There are Google and Facebook OAuth2 login links on the log in page to log in with a Google or Facebook account, and there is a 'Login by email' link to login via Persona with any address you register and confirm with Persona. This is a new installation of Mailman 3 so there are still kinks to work out, and any issues can be discussed on the list or reported to the trackers at <https://gitlab.com/mailman/postorius/issues>, <https://gitlab.com/mailman/hyperkitty/issues> or <https://gitlab.com/mailman/mailman/issues> as appropriate. Enjoy! -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 4 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Mark Sapiro

On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)

by Mark Sapiro

On 3/8/24 11:29 AM, Wikinaut wrote: > Is there a possibility to > > > - to discard the present mail ; and > - accept this sender (non-member) for further mails ? > > The reason: > - Member has sent from their office mail (= not yet known address) - mail 1 on hold and > - sent successfully mail 2 (copy of mail 1) from the known address > > So I want to discard the mail #1 (because the copy mail #2 was sent already) but I want to add his office address as member or to the whitelist. > > Can this be done in one step? It would be nice, at least. This was answered in the message to which you replied, found at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. To reiterate, go to the held messages view. Click the subject of the message, pull down the `--- Set member moderation ---` dropdown and select `Default processing` or if you really want to bypass additional checks, `Accept immediately (bypass other rules)`, and click the `Discard` button. It doesn't matter that the address wasn't known beforehand. The post itself created a non-member record for the sender, and the above will set that non-member's moderation action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Hyperkitty tracebacks: possible DB corruption?

by Mark Sapiro

On 3/12/24 11:12 PM, peter--- via Mailman-users wrote: > FOr the other issue, I changed > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/thread… > > From: ``` > if request.user.is_authenticated: > last_view_obj, created = LastView.objects.get_or_create( > thread=thread, user=request.user) > if not created: > last_view = last_view_obj.view_date > last_view_obj.save() # update timestamp ``` > to: ``` > if request.user.is_authenticated: > try: > last_view_obj, created = LastView.objects.get_or_create( > thread=thread, user=request.user) > except LastView.MultipleObjectsReturned: > last_view_duplicate, last_view_obj = LastView.objects.filter( > thread=thread, user=request.user).order_by("view_date").all() > last_view_duplicate.delete() > created = False > > if not created: > last_view = last_view_obj.view_date > last_view_obj.save() # update timestamp ``` > > and that seems to have fixed it. Wrapping the last_view_obj, created = LastView.objects.get_or_create() in a try, except seems appropriate, but your code in the except clause assumes there will be exactly 2 objects returned. Something like ``` except LastView.MultipleObjectsReturned: last_view_objects = LastView.objects.filter( thread=thread, user=request.user).order_by("view_date").all() last_view_obj = last_view_objects[-1] for object in last_view_objects[:-1]: object.delete() ``` might be better. > I've been thinking though that it'd be better to fix duplicates in the > LastView class rather than on every get() or get_or_create() call. That might be good, but these exceptions are rare. I'm not sure how they even occur, so catching them on the get() or get_or_create() calls seems OK. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 1:59 PM, Quanah Gibson-Mount wrote: > >> Click on the subject in the held messages list. At the bottom of the >> dialog that opens, there is a drop down to set the user's moderation. >> Normally, you would set it to 'default processing'. > > I do not see any such option. After clicking on the header the only > options available at the bottom are: > > Accept, Reject, Discard, Show Source, Show Header > > There are zero drop downs anywhere. This was implemented by <https://gitlab.com/mailman/postorius/-/merge_requests/397> and released in Postorius 1.3.0. >> This was not "removed". It just hasn't been implemented in MM 3 yet. > > So in terms of available functionality that was present in MM2, it was > removed. It may need to be re-implemented, but this was a core feature > that was present in the prior version that is no longer available. Yes, we are aware of many things that are not yet exposed/implemented in Postorius and elsewhere. There are currently 580 open issues at <https://gitlab.com/groups/mailman/-/issues>. We are working on these things as we can. We would love to have your help in fixing these. In the mean time, there are really only 2 or 3 core developers working on this and we are all volunteers, so it takes time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Sapiro

On 5/18/21 4:06 PM, Mark Dadgar wrote: > I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. > > Any ideas what’s going on here? ... > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login > emailaddress = EmailAddress.objects.get_for_user(user, email) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user > ret = self.get(user=user, email__iexact=email) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get > raise self.model.MultipleObjectsReturned( > > Exception Type: MultipleObjectsReturned at /accounts/login/ > Exception Value: get() returned more than one EmailAddress -- it returned 2! > Request information: > USER: AnonymousUser Go to the Django admin users page - something like http(s)://example.com/admin/auth/user/ - and search for the email address. This search is case-insensitive and I'm guessing it will find two users differing in case. In any event, django allauth is trying to find this user and is finding multiple EmailAddress.objects for this address or username. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Hyperkitty

by Mark Sapiro

On 1/30/23 13:17, Onyeibo wrote: > > The mails don't have that header. I suspect I may have to investigate > SELinux. I think it's unlikely a SELinux issue unless you mean it's an issue writing the log, but if there are any entries at all in mailman.log, that should be OK. what does `mailman conf -s archiver.hyperkitty -k configuration` show? The default is `/etc/mailman3/mailman-hyperkitty.cfg`. Whatever it is, what's in that file. It should be something like ``` [general] base_url: http://127.0.0.1:8000/archives/ api_key: some_key ``` some_key needs to match ``` MAILMAN_ARCHIVER_KEY = 'some_key' ``` in /etc/mailman3/settings.py and the base_url setting needs to access hyperkitty. It could be as above or it could be the URL that accesses HyperKitty externally as in ``` base_url: http:://example.com/archives/ ``` Is all of that correct? To verify base_url, you can do ``` curl http://127.0.0.1:8000/archives/api/ ``` where the initial part of that is the base_url setting. That should return the html for a page of documentation. Look at https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperki…. This is Mailman Core's interface to the archiver. If any of the methods there fail to connect to HyperKitty or get an appropriate response, they all log errors. In particular, the archive_message() method at line 171 is saving the message in the spool queue. Immediately before that at lines 164 and 167 it is writing log messages. You should be seeing them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: troubleshooting hyperkitty

by Mark Sapiro

On 12/9/20 5:01 PM, Morris Jones wrote: > > did that as well ... > > base_url: https://mailman.whiteoaks.com/hyperkitty/ > > (Though the configuration comment on this suggests it should not be > publicly accessible, I don't see any alternative endpoint that's private.) The comments in mailman-hyperkitty/mailman-hyperkitty.cfg say in part # ... It does not need to be publicly available, in fact it's # better if it is not. but they add # However, if your Mailman installation is accessed via HTTPS, the URL needs # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty) > I added both my public IP address and my domain name to > MAILMAN_ARCHIVER_FROM. > > So this part is all set, it would seem ... > > [archive.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg > > [logging.archiver] > path: /opt/mailman/var/logs/archiver.log api_key What is api_key? Is your setting for api_key somehow garbled. Note it needs to be set in the general section of mailman-hyperkitty.cfg and not in mailman.cfg > My archiver log continues empty > > The API keys match in settings_local.py MAILMAN_ARCHIVER_FROM and > mailman-hyperkitty.cfg The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not MAILMAN_ARCHIVER_FROM, a typo in your mail or ?? Anyway, in settings_local.py the key is a python string and must be quoted, but the api_key setting in mailman-hyperkitty.cfg is not quoted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/17/20 10:39 AM, Torge Riedel wrote: > > The message is being held because: > > Header "Yes" matched a header rule > > At your convenience, visit your dashboard to approve or deny the > request. > > I think this is wrong, it should read 'Header "x-spam" matched a header > rule'. Cause the header rule is configured for header "x-spam" and > pattern "Yes". The message is defined as 'Header "{}" matched a header rule' where {} is replaced with the value of the matching header. I agree it would be better if it were something like 'Header value "{}" matched a header rule for {}:' with {}s replaced with the header value and name. That would make it in your case 'Header value "Yes" matched a header rule for x-spam:' > I haven't found a bug report for this yet on gitlab. If someone of the > developers confirm this is wrong, I will file a bug on gitlab for it. Please do file a bug. It won't be fixed until after the upcoming 3.3.2 final release because we not making i18n changes between the candidate and final releases. Also, if you don't like my suggestion, feel free to suggest something else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Upgrade to 3.3.2 fails

by Mark Sapiro

On 12/26/20 11:28 AM, Joel Lord wrote: > innodb_page_size of 16384 is the default, so that is what I'm working > with as well. The row size limit is half the page size minus some > overhead, so it comes out to 8126 and I bet that is yours as well. > > Yes, I am utf8mb4 at the database and table levels, and I bet you are > right. Just to confirm, between 3.2.1 and 3.2.2 the column archive_rendering_mode was added to the mailinglist table. This column is type - integer (4 bytes), but could be enough to push the row over the limit. As far as utf8mb4 vs. utf8 is concerned. There will be issues with the hyperkitty_email table subject and content columns in particular and maybe others if email messages contain 4-byte utf-8 unicodes. However, as I read the MySQL docs, for columns like VARCHAR(255) and VARCHAR(510), the difference affects only the number of characters that can be stored in the column and not the actual column width. I.e., a VARCHAR(255) column is actually up to 256 bytes wide (1 byte for length and up to 255 butes of data) and can thus hold up to 85 3-byte utf-8 encodings or up to 63 4-byte utf-8 encodings, but since any string normally contains only a few if any (probably none in the case of the mailinglist table) the actual limit is much closer to 85. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Archive search failing on one list

by Mark Sapiro

On 10/9/23 22:50, Mark wrote: > > I'm still on this problem of one list's archive-search not returning > any results. I created a new list today and it also has the same > problem. > > In short, the older lists all seem fine -- their search results are up- > to-date so that tells me the cron is okay. It's just these 2 newer > lists that have the problem. > > It's taken me while to get my head around the Django admin command you > have suggested, as I kept getting an error when starting: Steve has addressed your issues with multiple Django admin commands, some of which apparently don't reference the correct settings. > The format of my final line is different to yours ... > > Mine: <MailingList: <MailingList thepost(a)example.com>> > > Yours: <MailingList listname(a)domain.com (listname.domain.com)> > > Does this (missing list_id) give any clue as to why the archive-search > isn't working, or is just that starting with "# python3 manage.py > shell" is the wrong thing to do? It is not a clue as to the problem. The format of that `representation` changed in HyperKitty 1.3.5. What is your version? What happens if you do, with the appropriate Django admin and list name, ``` python3 manage.py update_index_one_list thepost(a)example.com ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Pre-approved howto

by Mark Sapiro

On 7/5/18 6:14 AM, thor.rustad(a)gmail.com wrote: > I have tried to understand the concept of pre-approved messages, but I'm spending way too much trying to figure it out. Help! There is a list attribute, moderator_password, which is not currently exposed in Postorius and therefore must be set via 'mailman shell'. Here's a sample session. > $ mailman shell -l junk(a)msapiro.net > Welcome to the GNU Mailman shell > The variable 'm' is the junk(a)msapiro.net mailing list >>>> m.moderator_password >>>> from mailman.config import config >>>> m.moderator_password = config.password_context.encrypt('xxx123').encode('us-ascii') >>>> m.moderator_password > b'$6$rounds=656000$SKMqTlPybIZSBjYB$wCga5qALCv8oobp4cDql2iKEg8T6qIgk8XEKYbkk9QXENeFQDHZ1M4AtmqfureYQDB5g.Az.nZPrWAr9N9g1N0' >>>> commit() That will set the list's moderator_password to the encrypted value of 'xxx123'. Then, if a post to the list contains Approved: xxx123 either as a header in the message (recommended if possible) or as the first non-blank line in the first text/plain part of the message, the post will be 'pre-approved'. The header can actually be any of Approve:, Approved:, X-Approve: or X-Approved: and if it is not a header, but is found in the first text/plain part of the message, it will be removed from that part and a best effort will be made to remove it from other text/* body parts in case it is also in an alternative part. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Removing the footer from mails

by Mark Sapiro

On 10/21/2017 01:46 PM, Peter Mueller wrote: > Hi, > > mailman2 had the configuration variable "msg_footer" to edit/remove the > footer. How can I get rid of the footer in mailman3? The doc is at <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/decorate.…>, but it's a bit complex. First, the message footer template name is 'list:member:regular:footer' and the digest footer template name is 'list:member:digest:footer' and if you want the same template for both, the name 'list:member:generic:footer' will do. The easiest way to set these is to create a template for the desired language (probably 'en') or an empty file if you want no footer. Then, there is a 'var' directory in the Mailman installation which contains sub directories named 'archives', 'cache' 'data', 'etc', 'ext', 'lists', 'locks', 'logs', 'messages', 'queue' and 'templates'. You can put list specific templates in var/templates/lists/LIST.ID/en/, domain specific templates in var/templates/domains/DOMAIN/en/ and sitewide templates in var/templates/site/en/. For example if you put an empty file at var/templates/site/en/list:member:generic:footer and a non-empty file at var/templates/lists/list.example.com/en/list:member:regular:footer, all messages and digests will have no footer except for regular deliveries from the list.example.com list which will use it's template. list overrides domain overrides site overrides default. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, > > Mailman settings page giving me below error. > > Server error > An error occurred while processing your request. > > Error logs: > > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306, in user_subscriptions > mm_user = MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in get_or_create_from_django > return self.get(address=user.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in get > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET /users/user(a)example.com (or whatever the user's address is). It appears that that user doesn't exist in core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: # comment allowed in a template file?

by Mark Sapiro

On 7/27/20 5:15 AM, skenny(a)scss.tcd.ie wrote: > > The effect of the template files not being readable by user "mailman" was interesting. Hundreds of lines like the following got written to mailman-core's var/log/smtp.log file at the rate of 4 per second: > > Jul 23 17:09:54 2020 (25) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fdf9e7b5f28> > > (the hex number was different each time). That's a `debug` level log message written for every delivery. It has nothing to do with the unreadable templates except that the unreadable template causes looping in an attempt to send the message. Did you perhaps set [logging.smtp] level: debug in an effort to diagnose the template issue? > Having excessively restrictive permissions on the template files is a silly - but easy enough - mistake to make. If it were possible to add it to Mailman 3, a more descriptive logging message could point others who make it in the right direction, perhaps. I spent a long time trying to figure out why messages weren't getting sent out from Mailman core, and in the end it was luck in form of a colleague's suggestion about file permissions that got me out of the rut. There is clearly a bug in that an unreadable template should just be skipped and the fact logged. I have reported <https://gitlab.com/mailman/mailman/-/issues/745>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: urls.py location on venv install

by Mark Sapiro

On 8/11/26 22:46, Torsten wrote: > > But it seems that 3.3.10 depends on nntplib >= 3.13 which could not be > fetched via pip: That's a bug. The requirement in Mailman 3.3.10's pyproject.toml is ``` 'nntplib; python_version>="3.13"', ``` This is wrong. it should be ``` 'standard-nntplib; python_version>="3.13"', ``` nntplib was dropped from the standard library in Python 3.13 and replaced by standard-nntplib from pip. Because of the above error, a pip install of mailman 3.3.10 will not work with Python >= 3.13. Also note that currently, Mailman core is not compatible with Python >= 3.14 because it depends on aiosmtpd which is not compatible with Python 3.14. The aiosmtpd incompatibility is fixed in GitHub but the fix is not yet released. The incompatibility is fixed by <https://github.com/aio-libs/aiosmtpd/pull/575> and <https://github.com/aio-libs/aiosmtpd/pull/595> > I have, nevertheless, standard-nntplib 3.13 already installed but there > is no nntplib on Pypi. I suggest the following depending on your Python version For Python 3.13 or 3.14 ``` pip install git+https://gitlab.com/mailman/mailman.git ``` and for Python 3.14 ``` pip install git+https://github.com/aio-libs/aiosmtpd.git ``` Installing Mailman from GitLab with Python 3.13 should work fine. Both this list and the lists at mail.python.org run the latest GitLab version with no problems. The installation of aiosmtpd from GitHub is more of an unknown, but should be OK. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 days, 4 hours

[MM3-users] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/30/21 6:23 AM, Lucia Moreno wrote: > Hi Mark, > > We are facing the same issue. My postgres database is growing too fast and > I would need to do some creaning of old archives dated from 2001 and keep > only the last, lets say... 5 years. > > Could you please help us with the development of such a script? I have no > experience in python. The attached script is a rough idea. It assumes your Mailman is installed in a virtualenv at /opt/mailman/mm/venv and the django settings module is /opt/mailman/mm/settings.py. The pruned messages will be in a mbox at /opt/mailman/pruned.mbox. The age of messages to prune is defined by the days=365*5 argument in CUTOFF = datetime.datetime.today() - datetime.timedelta(days=365*5) All these things may need adjustment for your purpose. There is also a commented bit showing how you could do just one list. It's probably good to do just one list at a time since it's not clear how useful the pruned.mbox will be if it contains messages from multiple lists. I.e., run it for one list and move the pruned.mbox aside before doing the next list. Note that I've tested that this works, but it's possible that it will leave HyperKitty in a bad state. Backup your database before running this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Archive download - unexpected end of file

by Mark Sapiro

On 3/1/25 13:58, Mark wrote: > > I have a MM3 list to whose archive I recently added an mbox file of > older emails. > > Viewing/searching the archive (Hyperkitty) is working fine. > > Downloading archives "for the month" or "last 30 days" delivers the > expected ".mbox.gz" file and those are fine. > > However, when I download the "Entire archive" and attempt to gunzip that > ".mbox.gz" file I get the error: " ... unexpected end of file". The process creating the zip for download times out. You can increase the timeout. If your wsgi server is Gunicorn, see https://docs.gunicorn.org/en/stable/settings.html#timeout - for uwsgi see https://uwsgi-docs-additions.readthedocs.io/en/latest/Options.html#harakiri However, it's probably easier to get it in pieces. You can prpbably get chunks bigger than a month. Look at the URL for a month, e.g. for Jun, 2005 it will be something like https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2025-02.mbox.gz?start=2025-01-01&end=2025-02-01 The <fqdn-listname>-2025-02.mbox.gz can be any arbitrary file name. The start and end parameters determine what's included. E.g. for all of 2024 https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2024.mbox.gz?start=2024-01-01&end=2025-01-01 Note that the end date is the first date not included, i.e. the day after the last date included. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Questions regarding message acceptance

by Mark Sapiro

On 7/28/20 6:35 AM, Pawel Grzywaczewski wrote: > Hello, > > I have few questions regarding usage of Mailman3: > > 1) We have list1 and list2 with members. Can we specify that all members of list1 can post messages to list2? This is a Mailman 2.1 feature that does not currently exist in Mailman 3. > 2) In explanation of “Accept these non-members” it’s written: “While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing”. > > I noticed that if someone posts to a list then he is added automatically to non-members. Which means that next time he will be able to post. > My understanding is that it’s better to use the feature “Accept these non-members”. Am I correct? You are mistaken. When a non-member attempts to post to a list she is automatically added to non-members with a moderation action of list default, which means that this and subsequent posts will be handled according to the list's "Default action to take when a non-member posts to the list" If you want to accept a non-member's posts you need to set that non-member's moderation action to "Default Processing" to still apply other tests that might hold the message or to "Accept" if you want to accept anything from that non-member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 9/30/24 14:44, jkoral(a)luc.edu wrote: > That makes sense. Are there instructions on how to do this? It depends on the MTA. For Postfix you probably have a set of aliases for each of the form: mailman: "|/path/to/mail/mailman post mailman" mailman-admin: "|/path/to/mail/mailman admin mailman" mailman-bounces: "|/path/to/mail/mailman bounces mailman" mailman-confirm: "|/path/to/mail/mailman confirm mailman" mailman-join: "|/path/to/mail/mailman join mailman" mailman-leave: "|/path/to/mail/mailman leave mailman" mailman-owner: "|/path/to/mail/mailman owner mailman" mailman-request: "|/path/to/mail/mailman request mailman" mailman-subscribe: "|/path/to/mail/mailman subscribe mailman" mailman-unsubscribe: "|/path/to/mail/mailman unsubscribe mailman" You could change these, preferably in a separate aliases file so Mailman's genaliases won't overwrite them, to mailman: mailman@new_server mailman-admin: mailman-admin@new-server mailman-bounces: mailman-bounces@new-server mailman-confirm: mailman-confirm@new-server mailman-join: mailman-join@new-server mailman-leave: mailman-leave@new-server mailman-owner: mailman-owner@new-server mailman-request: mailman-request@new-server mailman-subscribe: mailman-subscribe@new-server mailman-unsubscribe: mailman-unsubscribe@new-server For exim, you would need to add another Mailman router ahead of the existing one which would match only the migrated lists and specify an smtp transport which relays to the new server. > Then once we are done migrating to the new server, then we can just change the DNS, correct? Yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: How to process emails with Mailman3?

by Kyle Lahnakoski

Thank you for this answer. In both the inject case and the netcat case I must know the recipient. My complex setup looses that metadata; leaving me with only the message. I guess I will be parsing the message to find that recipient. Thanks again On 2025-03-09 10:50 p.m., Mark Sapiro wrote: > Mark Sapiro wrote: >> The issue is you are not using nc correctly. >> When you do >> >> $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr >> >> you are telling nc to take commands from the file >> /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send >> the file. > Actually, what I said is not correct. The issue is you are just sending the data rather than engaging in an LMTP dialog. > > You need to send LMTP commands so you might prepend the message with > ``` > LHLO mymaillist.org > MAIL FROM: <sender(a)example.com> > RCPT TO: <all-request(a)mymaillist.org> > DATA > ``` > and append to the message > ``` > . > QUIT > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kyle(a)lahnakoski.com >

1 year, 5 months

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Mark Sapiro

On 8/3/25 00:09, Odhiambo Washington via Mailman-users wrote: > I wonder what this means and whether it's fatal. > > How do I fix it? > > ``` > ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) ... > *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() > returned more than one EmailAddress -- it returned 2!* It appears you created a new list, and that list' owner email address has two Django user records with emails differing only in case. See https://www.msapiro.net/scripts/UC_fix for a script to fix this or you can just go to the Django web UI and delete the mixed case user. > I suspect it's something to do with my action yesterday while attempting to > reply to a thread from HyperKitty. Possibly, if hyperkitty was looking at a mixed case email address that it didn't recognize as a list member and subscribed it. > The superuser account uses my address - odhiambo at gmail dot com.I am also > the listowner for most lists. > I tried unsuccessfully to create an account on Postorious using the same > email address. > I kept getting sent links to verify the account, over and over. > Finally, I was able to verify the account, but cannot login with it. This too is probably because there are two accounts with email addresses differing only in case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Attack on Mailman Server?

by Mark Sapiro

On 3/9/23 11:34, Eggert Ehmke via Mailman-users wrote: > I had some attacks on my wordpress homepage today, I added some IPs to the > blacklist of my firewall. At the same time, I got several reports like this: > > Internal Server Error: /accounts/signup/ > > TemplateDoesNotExist at /accounts/signup/ > 429.html I suspect that's a coincidence. > Request Method: OPTIONS > Request URL: https://lists.eehmke.de/accounts/signup/ > Django Version: 3.2.16 > Python Executable: /opt/mailman/venv/bin/uwsgi > Python Version: 3.9.2 > Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/ > python3.9', '/usr/lib/python3.9/lib-dynload', '/opt/mailman/venv/lib/ > python3.9/site-packages'] > Server time: Thu, 09 Mar 2023 13:09:34 +0100 > > So it seems there were attempts to register new users but this caused this > internal error. Where can I send the complete error message? I would look in the web server logs to see what the actual accesses were. I'm guessing you'll find that some bot or script kiddies did a GET of /accounts/signup/429.html. You could also look for more detail in whatever log Django writes. This is defined in Django's settings as LOGGING['handlers']['file']['filename'] and is often Mailman's var/logs/mailmansuite.log. If you followed https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it is /opt/mailman/web/logs/mailmanweb.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I'm NOT blaming any of the parts involved... Sure, most probably is my > fault. But the last upgrade shows that the process that fail is involved > with mailman upgrade. The last server was working smoothly and it has > higher traffic than the first I tried. It cannot be that I missed that > something was not working for weeks (since the last upgrade of the OS) It depends on what you did. Mailman's lmtp runner would only encounter this issue at startup, so unless you restarted Mailman or rebooted the server, lmtp runner would have continued without issue even if there was an underlying OS problem. Also, I don't think the problem is with Mailman per se. The underlying issue is in the Python library socket module. Try the following in a Python 3 shell ``` $ python3 Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() ``` This is essentially what aiosmtpd does and I expect that `sock = makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] Protocol not supported` exception. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 20:53, Bryan Fields wrote: > mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; > ERROR: update or delete on table "hyperkitty_thread" violates foreign > key constraint > "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table > "hyperkitty_email" > DETAIL: Key (id)=(35670) is still referenced from table > "hyperkitty_email". > mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; > ERROR: update or delete on table "hyperkitty_email" violates foreign > key constraint > "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table > "hyperkitty_thread" > DETAIL: Key (id)=(150555) is still referenced from table > "hyperkitty_thread". Well, that's a catch 22, you can't delete the email because it's referenced by the thread and you can't delete the thread because it's referenced by the email. You could always update those entries to remove the references, but deleting and reimporting is probably better. > I'll attempt to clean this up tomorrow an clean it up/re-import. > > Is there a quick/easy way to drop the entire archive from the db or must I > delete the entire list? If you can get to https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/ as a Django staff user or superuser, there is a Delete Archive button to delete the entire archive. Even if you can't get there, you may be able to get to the confirmation page at https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/del… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: AttributeError: ,> 'ReopenableFileHandler' object has no attribute '_stream'

by Mark Sapiro

On 11/19/21 9:43 PM, David Newman wrote: > ((reposting with correct subject line -- sorry!)) Actually, the original Subject was probably closer to the problem. > Greetings. I am attempting a complete Mailman 3 installation on a Debian > 10 system that already runs Mailman 2, following this documentation: > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > Even following this guide, I'd had a lot of issues with permissions, > where directories and files were owned by list rather than mailman. > After correcting those issues, I then got to the point of checking > mailman3's status, and systemctl shows this error: > > Nov 19 20:09:57 [REDACTED] mailman[1463]: Error in atexit._run_exitfuncs: > Nov 19 20:09:57 [REDACTED] mailman[1463]: Traceback (most recent call > last): > Nov 19 20:09:57 [REDACTED] mailman[1463]: File > "/usr/lib/python3.7/logging/__init__.py", line 2038, in shutdown > Nov 19 20:09:57 [REDACTED] mailman[1463]: h.flush() > Nov 19 20:09:57 [REDACTED] mailman[1463]: File > "/opt/mailman/venv/lib/python3.7/site-packages/mailman/core/logging.py", > line 67, in flush > Nov 19 20:09:57 [REDACTED] mailman[1463]: if self._stream: > Nov 19 20:09:57 [REDACTED] mailman[1463]: AttributeError: > 'ReopenableFileHandler' object has no attribute '_stream' These generally stem from permissions errors preventing opening the log file. > There is an October 2019 thread on this error [1] but I think it's in a > different context, where the OP already had mailman3 running, and was > trying to migrate Mailman 2 lists. > > Also, regarding those permissions issues above, it matters which > "layout" value is in /etc/mailman3/mailman.cfg. I'd tried "dev" because > I saw a post from Mark Sapiro recommending that, I don't know in what context I recommended that. In my installs I use `layout: here` and in [paths.here] I specify an absolute path for var_dir. > but then mailman3 > wanted me to create a bunch of directories under /etc, even though > $var_dir was set to /var/lib/mailman3. Things seem to go better, except > for the confusion between lists/mailman ownership, when I set layout to > "debian", which was the default. It seems you may be using the Debian packages as our source has no `debian` layout. I.e., if you are installing with pip in a virtualenv, there would be no `debian` layout. If you are using Debian packages the Mailman user is `list` not `mailman`. > Thanks in advance for clues on addressing the ReopenableFileHandler > error above. Fix the underlying permissions error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Mark Sapiro

On 5/6/20 12:52 PM, Thomas Drillich wrote: > lines from exim4/mainlog > 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu > 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT > 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) It's not clear to me from the log what is happening. It all happens within a fraction of a second, so there don't seem to be any time outs involved. It seems the first two entries are the delivery of the message from th(a)drillich.com to exim for seebruecke(a)listen.td3.eu. I'm guessing here because I don't know that much about exim, but it looks like exim is trying to connect to listen.td3.eu rather than localhost to deliver the message and most likely, port 8024 is not open to the outside which is correct. I think you need to add hosts_override = true to your transport definition to tell exim to use `hosts = localhost` rather than the host part of the email address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/19/22 21:23, Stephen J. Turnbull wrote: > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > doesn't replicate that success. > > systemd doesn't know anything about venv. If it's possible to source > (not call as a command!) the venv bin/activate script via systemd, > that should fix it. If not, we'll have to figure out what it is that > the venv provides that the current systemd config does not. I would > guess that after sourcing the venv's bin/activate Our suggested systemd script at https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… has ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop /opt/mailman/venv/bin/mailman should work whether or not a venv is active. Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman is quite different from mine which is just ``` #!/opt/mailman/venv/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' __requires__ = 'mailman==3.3.5' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() ) ``` What is yours? and can you start mailman as the mailman user with ``` /opt/mailman/venv/bin/mailman start ``` without activating the venv? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: How to remove a message with an invalid Message-Id?

by Mark Sapiro

On 6/14/23 15:12, McGuire, Tommy M. (MSFC-IS61)[EAST2] via Mailman-users wrote: > I have a fun problem: apparently a message sent to a mailing list has an invalid Message-Id (I think), which is causing the message parse to fail while attempting to archive the message. Unfortunately, the message seems to be trapped somewhere and resulting in error logging every few minutes. Is there any way to find and remove the message? > > Literally, the only thing I've been able to find out about it is that the Message-Id contains the text "[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>". This is https://gitlab.com/mailman/mailman/-/issues/1065 which is fixed for the next release by https://gitlab.com/mailman/mailman/-/merge_requests/1099 You will find the message queued at Mailman's var/archives/hyperkitty/spool/ directory. You can examine the pickled message object with `mailman qfile` and you can simply remove the file. If you want to "fix" it and archive it, A `mailman shell` interaction like this will do it ``` >>> import pickle >>> with open('/path/to/.pck/file', 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Message-ID', '<83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com>') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Moving mm3 -> mm3 to different host

by Mark Sapiro

On 10/19/23 02:38, Axel Rau wrote: > Hi all, > > There are lots of threads for mm2 -> mm3 moves, but only one > thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining > the steps, but I can't find it again. > > I have created a working mm3 installation on the new host with both > mailman and mail-web dbs imported. > hyperkitty archive seems to in the db. > > What are the next steps to complete the transfer? > > - rsyncing messages, lists and templates to new host You may want to add archives/prototype to that. Also note that the contents of the messages/ directory should correspond to the entries in the message table in the mailman db. > - Setting up DNS CNAMES to the new server > - Adapting exim to accept mails to the aliased domain > > - Can I keep the old listname, with the old domain name? As long as mail to the list at that domain gets delivered to the new server. Note that in DNS if the domain has an MX record it must point to a domain with and A record and if there is no MX record, there must be an A record. CNAMEs won't do for mail delivery. > -What else has to be done ? I think that's it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: "Approved:" header from mailman2 times

by Mark Sapiro

On 04/09/2018 03:59 PM, Abhilash Raj wrote: > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: >> Hi, >> >> is there any equivalent to "Approved" header that was present in MM2 in >> MM3 land? Google is not very helpful in that. > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. I don't think it is broken, but it requires setting the moderator_password attribute for the list which can be set visa REST but I think not by mailmanclient. > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > Agreed. This is a shared password. and would be sent in plain text as a header or body line. It would be nice though to have some feature to enable, for example, spoof proof posting to a one-way (announce only) list. One thought on how to do this would be to have a list attribute that says posts from 'authenticated' owners and moderators can be auto approved and authentication could be by PGP signing the post. This would require Mailman to have the ability to verify a PGP signature from an owner or moderator which is not currently the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/22/23 12:42, ceo(a)sartrack.nz wrote: > I found the problem with Exim4. > The Exim4 config file should contain this: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > and NOT > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > Somewhere the documentation is wrong. The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} Where did you see MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > But I now have the next problem: > I send an email to a new mailing list called templist(a)sartrack.nz (I imported my old list members). > in /var/log/mailman3 I get an error regarding this; > The (final) error states: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/lists/templist.sartrack.nz/digest.mmdf' > > The file digest.mmdf does not exist there at all. Because Mailman was trying to create it and couldn't. I suspect you ran `mailman create` as root and the /var/lib/mailman3/lists/templist.sartrack.nz/ got created with user:group as root:root rather than the mailman user and group. Recent Mailman versions won't run the `mailman` command as root without a --run-as-root option for this reason. How are you installing Mailman? > The mailing server does not send out any emails for "templist" This is a separate issue from the above error, but it might also be a permissions error. What other errors do you see in /var/log/mailman3/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: share directories between postfix and mailman 3

by Mark Sapiro

On 1/23/24 12:30, Thomas Schachtner via Mailman-users wrote: > > > Mark Sapiro wrote: >> >> Why do you think Mailman needs the contents of the postfix >> configuration file.. I don't think so. > I thought so, as mailman does not start if there's not > /etc/postfix/main.cf file is there. > > The following messages are logged: > Jan 23 21:20:35 mailman mailman3[491404]: RuntimeError: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not > permitted > Jan 23 21:20:35 mailman mailman3[491404]: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation > not permitted Mailman itself is not looking for Postfix main.cf, but when Pustfix is the MTA, it invokes the postmap command to create the .db files for postfix_lmtp and postfix_domains. Apparently postmap fails if there is not a Postfix main.cf. You can avoid this by using regexp tables instead of hash tables. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. >>> This seemed to work pretty fine, as all files and directories seemed >>> to be available, but when starting mailman 3, the following error >>> message was shown: >>> FileExistsError: A race condition might have happened. >>> /var/lib/mailman3 actually exists and is not a directory. >>> >>> Any idea why this message is shown? >> >> Possibly because the uid and gid of /var/lib/mailman3 on the postfix >> machine do not map to the appropriate Mailman uid and gid on the >> mailman machine. > You refer to the uid and gid of the "list" user? They are both 38 (uid > and gid) on both machines. > Then that isn't the reason. I don't know then why Mailman would complain that /var/lib/mailman3 actually exists and is not a directory. This message comes from mailman.utilities.filesystem.makedirs(). The code is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/file…>. makedirs() calls first_inexistent_directory() which checks if the directory exists with os.path.isdir() which apparently says it isn't a directory which makes no sense unless there is an actual race condition and you are creating the /var/lib/mailman3 directory on the mailman machine at the same time as you are starting mailman. BTW, you say you are doing sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 on the mailman machine. Presumably on the mailman machine /var/lib/mailman3 has lots of content. How does that work? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/23/2017 08:16 AM, Rafael Mora wrote: > This is the content of my /var/log: > > > [root@localhost log]# pwd > /var/log > [root@localhost log]# ls > anaconda grubby messages-20170716 spooler-20170710 > audit grubby_prune_debug messages-20170723 spooler-20170716 > boot.log httpd mysqld.log spooler-20170723 > btmp lastlog php-fpm tallylog > btmp-20170701 letsencrypt ppp tuned > chrony maillog rhsm wtmp > cron maillog-20170702 samba xferlog > cron-20170702 maillog-20170710 secure xferlog-20170702 > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > cron-20170723 mailman secure-20170716 xferlog-20170723 > dmesg messages secure-20170723 yum.log > dmesg.old messages-20170702 spooler > firewalld messages-20170710 spooler-20170702 Your current postfix log is /var/log/maillog. The files like /var/log/maillog-20170702, etc are older versions rotated by logrotate. On 07/23/2017 08:14 AM, Rafael Mora wrote: > content of the file maillog-20170723 (I didn't find mail.log in /var/log): > > [root@localhost log]# cat maillog-20170723 You want to be looking at /var/log/maillog for current messages. ... > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Is this where these files are? You should have at least postfix_domains, postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the /var/lib/mailman/var/data/ directory. It this the case? > output command 'postconf -n': > ... > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp This is missing a / transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: configuring moderators per list

by Mark Sapiro

On 11/06/2017 02:33 PM, Dmitry Makovey wrote: > We're trying to configure moderator per list and so far we were only > able to add "superuser" accounts that can handle "Held messages", > "Members", "Banned addresses" etc. You can add ordinary users as Moderator or Owner of a list. I'm not sure what is and isn't currently working, but Moderators and Owners get notices of things like held messages and subscriptions and can approve or deny them. I think only Owners, not Moderators, should be able to change various list settings. Have you tried these things? Is it not working? > Is there a way to create special account per-list to manage some of the > aspects of particular ML without giving them all the permissions that > Superuser comes along with? An Owner of one list should not be able to do things to other lists. If you're looking for more granularity in permissions on a single list, Owners can do anything, and Moderators should only be able to deal with held requests, but there's no granularity beyond that. > In MM2 there was a ML password that moderator/list admin would use to > login to perform operations. > > Current setup allows list admins to add/delete existing lists which is > not desired. This was a site option in MM 2.1. I'm not sure about MM 3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:33 PM, Andrew Bernard wrote: > Hi Mark, > > Thanks for your great help. But despite decades of UNIX experience, my area > is not Django (yet). The nub of my question is that I thought you have to > have a manage.py file for Django to be able to set up the various affairs, > such as making the database migrations and so on. It is that that is > eluding me. Apologies for this hopelessly newbie question. The equivalent of manage.py in what I suggested is /opt/mailman/bin/django-admin. > I was impressed with your method of installation in the page referenced, > and I have foolwed that closely. But I am puzzled about the build script. > If I run as user mailman, not root, it wanted to install under /usr. which > of course results in permission denied. I had to modify the script to say > this: > > python setup.py install --prefix /opt/mailman/mm/venv If you want to install in the virtualenv, you should just activate the virtualenv and it should work. Perhaps the issue is that the build script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> assumes the virtualenv is at /opt/mailman/mm/venv. You need to insure that the '. ../mm/venv/bin/activate' line is actually pointing to your 'venv/bin/activate' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Bounce processing

by Mark Sapiro

On 4/23/20 2:27 PM, Andrew Hodgson wrote: > > When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. The message the user is sent in built from the list:user:notice:warning template. The next release of Postorius will offer that template as one you can edit, but the current release doesn't. You can make an edited template in the var/templates/ directory. The logged-in user can go to her settings pages in Postorius at accounts/subscriptions/ to set delivery status. The generic template can't be that specific because Mailman Core doesn't even know if you have Postorius. > I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. The bounce recognition for Mailman 3 is essentially the same as Mailman 2.1. If you post one of these complete bounce messages, we'll investigate why it isn't recognized. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 1/26/22 14:34, gordon(a)dickens.com wrote: > > However, mailman3-web (or mailman-web) is not working, I think because of a permissions issue. The installation instructions specify that mailman3-web (or mailman-web) run as user=mailman and group=mailman. However, the debian installation specifies the data files as user=www-data and group=www-data which is what apache runs as. For instance, I have my static files stored in the /var/lib/mailman3/web/static directory and the previous Debian mailman3 version set all the ownerships and groups to www-data for /var/lib/mailman3/web, /var/lib/mailman3/web/static along with all of the directories and files in the static subdirectory. So, > when I run "mailman-web collectstatic" it bombs on the following permissions error: > > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/web/static/hyperkitty/js/hyperkitty-common.js' > > So, my question is as follows. Should I continue to run mailman3-web as user mailman and change the ownership of the /var/lib/mailman3/web directory to mailman or should I leave the permissions of the /var/lib/mailman3/web directory alone and have mailman3-web run as user and group www-data? As David later said, owner and group of all Mailman's files and directories should be `mailman` and what ever the wsgi interface is (uwsgi, gunicorn, mod_wsgi) should run the wsgi process as user:group mailman:mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Removing all moderatortors (and owners) from a list in one go

by Mark Sapiro

On 8/12/24 04:07, Henrik Rasmussen wrote: > > Isn't there an easier way? And why not like https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… ? The next release of Mailman core will include a `mailman admins` command for adding and removing list owners and moderators. You could back port it simply by downloading and installing https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_a… The documentation is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… but I suspect this isn't what you want anyway because it does owners and moderators separately and you need to provide their email addresses. You could modify the script at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… to remove all owners and moderators from a list. E.g., ``` import os import sys from mailman.core import initialize from mailman.database.transaction import transaction from mailman.interfaces.listmanager import IListManager from zope.component import getUtility os.environ['MAILMAN_CONFIG_FILE'] = '/path/to/mailman.cfg' initialize.initialize() def delete_admins(list_id): mlist = getUtility(IListManager).get(list_id) if not mlist: print(f'No such list {list_id}', file = sys.stderr) sys.exit(1) with transaction(): for admin in mlist.administrators.members: admin.unsubscribe() if __name__ == '__main__': delete_admins(sys.argv[1]) ``` Running this with an argument of the list-id or list posting address will remove all owners and moderators from a list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Custom Archiver

by Mark Sapiro

On 4/1/23 09:39, pknowles(a)tpnsolutions.com wrote: > I'm playing around with installing Mailman Core, and want to have messages on a "per-list" basis sent to a special "archiver" address which I intend to make archives available at via a custom built "read-only" IMAP client. > > How would I go about having messages sent to this external address, short of adding the address as a subscriber? See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/archiving/prot… for an example of an archiver that implements Mailman's IArchiver interface. You could make something similar with an archive_message() method that sends the message to your IMAP server, or possibly you could just implement your IMAP client to serve messages from the existing var/archives/prototype/ hierarchy. Messages for lists with the prototype archiver enabled are stored there in maildir format by list name. To enable the prototype archiver, you may need to put [archiver.prototype] enable: yes in your mailman.cfg. To make your own archiver, create a python module, say my_archive.py, that defines a My_Archive class implementing the IArchiver interface. Put that module somewhere where mailman can import it and put something like [archiver.my_archiver] class: import.path.my_archive.My_Archive enable: yes where import.path.my_archive.My_Archive is the actual path that is imported. For example if Mailman is installed in a venv, you could put my_archiver.py in the venv's site-packages directory and then the class would be just class: my_archive.My_Archive -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Mark Sapiro

On 1/16/23 07:58, jaboyib556--- via Mailman-users wrote: > > However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? I have had some contact, but not much. As far as I know, they are still in business and offering list hosting including Mailman 3 lists with Affinity and Empathy. They no longer offer support for installation and maintenance of Mailman on other people's servers. When we first were developing Mailman 3, we designed it in a modular fashion with a REST API for the core engine so that users who were so inclined could develop their own web UIs for archiving and list management. We also recognized that we needed to develop our own to make a complete package. Thus, we developed HyperKitty and Postorius for that, but we have always hoped that the community would develop others (hopefully open source and Python based). As far as I know, it was only EMWD that did this and for business reasons, kept it proprietary. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: My django container keeps getting shutdown by oom-killer

by Mark Sapiro

On 11/12/25 17:10, Hirayama, Pat wrote: > > This always happens overnight, usually after midnight, though one time it was around 10:40. I don't see any crontab entries that correlate. And the after midnight issues don't always happen at the same time, so it seemed unlikely that it was a crontab job that was causing it > > I finally looked at the host (rather than the logs of each container) and realized that the oom-killer was killing django-admin. As a temporary workaround, I've limited memory on the mailman-django-uwsgi container to 4 GiB (though, since I just did that this morning, I won't know until after midnight (presumably) if it worked or not), and set the RestartPolicy to always. The above suggests it's one of the Django daily jobs that's hitting the OOM. These jobs are appname - jobname - when - help -------------------------------------------------------------------------------- django_extensions - cache_cleanup - daily - Cache (db) cleanup Job django_extensions - daily_cleanup - daily - Django Daily Cleanup Job hyperkitty - orphan_emails - daily - Reattach orphan emails hyperkitty - recent_threads_cache - daily - Refresh the recent threads cache hyperkitty - sync_mailman - daily - Sync user and list properties with Mailman I don't offhand know which of these might be a memory hog. Further, if one of these dies for out of memory, I don't see it affecting more than that job, not the entire service. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 9:42 AM, Mark Sapiro wrote: > On 12/17/23 9:10 AM, eboltz(a)lhtservices.com wrote: >> Mark, >> >> Here is my postconf -n >> >> alias_database = hash:/etc/aliases >> alias_maps = hash:/etc/aliases >> always_add_missing_headers = yes >> append_dot_mydomain = no >> biff = no >> compatibility_level = 2 >> default_destination_concurrency_limit = 15 >> default_destination_recipient_limit = 30 >> header_checks = regexp:/etc/postfix/header_checks >> header_size_limit = 409600 >> inet_interfaces = all >> inet_protocols = ipv4 >> local_recipient_maps = proxy:unix:passwd.byname $alias_maps >> hash:/var/lib/mailman3/data/postfix_lmtp >> mailbox_size_limit = 0 >> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >> myhostname = lists.example.com >> mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 >> myorigin = /etc/mailname >> readme_directory = no >> recipient_delimiter = + >> relay_domains = hash:/var/lib/mailman3/data/postfix_domains >> relayhost = [mail.smtp2go.com]:587 >> smtp_always_send_ehlo = yes >> smtp_sasl_security_options = noanonymous >> smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem >> smtp_tls_security_level = may >> smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache >> smtp_use_tls = yes >> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) >> smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated >> defer_unauth_destination >> smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem >> smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key >> smtpd_tls_security_level = may >> transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp >> unknown_local_recipient_reject_code = 550 >> virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap > > > It looks like you are now following > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. > > >> What would I have to do to ensure that MM3 and postfix (same new >> server) use the newly created lists.example.org domain, which only >> exists within Postfix when setting up the Postorius domain and lists? >> I want to have it so that whatever the list name is, for example >> 'Staff(a)lists.example.org' will route through Postfix correctly. > > > Have you set an alias_domain for the lists.example.org domain? > > What are the contents of /var/lib/mailman3/data/postfix_vmap and > /var/lib/mailman3/data/postfix_lmtp? If you feel it is necessary to > anonymize the domains in these, please only change the tld so we can see > the actual subdomains. However, it looks like you don't need to follow <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> as lists.example.org is not a virtual_alias_domain. You just need to add lists.example.org to mydestination, assuming lists.example.org and lists.example.com are actually different domains, and follow <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/27/21 1:36 PM, William Oliver wrote: > > When I send a message to the list from *any* of these three, the > mailman3 accepts it and attempts to broadcast it out. It is delivered > sucessfully to the local email address, but it looks like there's a > relaying problem with external addresses. > > In the syslog snippet below, note that the fp145(a)libertyfp.org mail is > delivered, but the mail to the recipients at billoblog.com get an > "Access denied" ...> > Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: NOQUEUE: reject: RCPT > from mail.libertyfp.org[2.56.57.28]: 554 5.7.1 <billo(a)billoblog.com>: > Recipient address rejected: Access denied; > from=<testlist-bounces+billo=billoblog.com(a)libertyfp.org> > to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> > > Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: disconnect from > mail.libertyfp.org[2.56.57.28] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 > quit=1 commands=7/8 It appears that the MX for billoblog.com is not accepting mail from your server. Can you send non-mailman mail from this server to this address? If not, you need to contact billoblog.com to fin wht they are blocking your mail. > I tried changing the smtp port in mailman.cfg to 587, but that didn't > change anything. because the issue is not in delivery from Mailman to Postfix. It is in delivery from Postfix to billoblog.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: CPU usage when idle

by Mark Sapiro

On 5/28/25 08:27, roughnecks via Mailman-users wrote: > > It's the manage.py qcluster whatever is called. I have shut down MM for > the time being, because I'm not fully motivated to have it running, so I > can't be more accurate right now. I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend. Settings that control this are typically ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` and possibly a setting like `'workers': 2,` (default is the CPU count of the system but see <https://django-q2.readthedocs.io/en/master/configure.html#f1>). ``` CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION': '127.0.0.1:11211', } } ``` although the default if not set is ``` CACHES = { "default": { "BACKEND": "django.core.cache.backends.locmem.LocMemCache", } } ``` It is the `'orm': 'default'` setting that says to use Django's CACHES. See <https://django-q2.readthedocs.io/en/master/brokers.html#django-orm>. You can get info about what qcluster is doing with `manage.py qinfo` and monitor things with `manage.py qmemory` and `manage.py qmonitor`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 8:28 PM, dancab(a)caltech.edu wrote: >> In either case, the bounce message (fake DSN) should have contained a >> message body like >> Mail to user(a)example.com failed at outgoing SMTP >> with the actual user's address. These fake DSNs are sent in the case >> where the outgoing MTA refuses a message from Mailman so there is no >> actual failure DSN. > > Thanks. I think I'm missing how I can configure Mailman so that the actual user's address is used. I think you are missing the point. This is a pseudo DSN. If it were a real DSN it would be something like From: mailer-daemon@somewhere To: listname-bounces@listdomain However, there is no real DSN because Mailman has gotten a reject in it's attempt to deliver to the outgoing MTA so it creates it's own pseudo DSN for the failure. Another way of looking at this is if you configured Mailman to deliver to a local MTA and configured that MTA to relay to your remote MTA, your local MTA would accept the message and then receive the 5xx status upon delivery to the Remote MTA and would then send an appropriate DSN back to the list-bounces address. Since you are skipping the local MTA part, Mailman gets the 5xx status upon delivery to the remote MTA and creates it's own DSN for itself. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/5/25 13:00, megabrutal--- via Mailman-users wrote: > Hi Everyone, > > I've recently installed Mailman3 and still testing it. I tried to reply to a topic on my own list while also being a superuser from HyperKitty, but I got this error message: > > "This list is moderated, please subscribe to it before posting." Is your login a member of the list? > Then why I even see the archive of the private list? What might be wrong? You can see the private archive because you are logged in as a superuser. > One thing that might confuse the system is that I added a secondary e-mail to my account. I thought it would allow me to post from any of my addresses, but it seems like it's not the case, looks like I can only subscribe with one of the addresses. How did you add that email? When you find yourself at https://example.com/mailman3/users and click Manage, do you see the expected addresses? > It also looks like HyperKitty has trouble matching up the addresses, as it lists 4 participants for the conversation, while 2 of them is my account, the other 2 is my test address. In reality, it should list 2 posters. This is normal. Hyperkitty lists participants by address whether or not the addresses are linked to the same user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 2:27 PM, Ken Alker wrote: > --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> The 404s are addresses im HyperKitty's sender table for whih there is no >> corresponding Mailman user. There are multiple possible reasons for this. > > And that is OK, right? Sure. It only means that there are messages in the archive that are From: addresses that aren't currently Mailman users. >> If the behavior has stopped it's probably because the periodic Django >> jobs are not being run - this is bad. > > I see this in the logs from just after midnight: > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > Followed by a huge amount of HTML (strange). This is all from one post. The first is normal it just says that Mailman's var/public_suffix_list.dat doesn't exist, but it should be retrieved from https://publicsuffix.org/list/public_suffix_list.dat and then saved at var/public_suffix_list.dat so it doesn't need to be retrieved from the web again until the saved copy is older that the configured dmarc.cache_lifetime (default = 7 days, so that message) after which time the message will be 'Cached copy of public suffix list is out of date' The second is acceptance of the post. The third is a failure in archiving the message. Th HTML should contain an error message with a traceback which should help determine the problem. > Is there a way to kick it into re-running whatever it does at midnight > so I can test this again after putting the public suffix list back? I > assume I can just execute "mailman-web runjobs daily", but will this > mess things up, or is it OK to run it mid-day without stopping anything > first? Midnight is a coincidence in this case. the above are all due to the post with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> The cached var/public_suffix_list.dat should now be there with a timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) > Is the last (third) log line excerpt simply a result of the first, or do > I have something else messed up? The third is not because of the first. It is because of some issue with archiving that post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 06:24, Jens Günther wrote: > > I find those changes, but: in the merge request there is mentioned a > /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po > > -> but I don't find a mailman-de.po ... is it maybe that? That file was for a test only. The German message catalog is at mailman/messages/de/LC_MESSAGES/. That directory should contain a mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be created. The source distribution contains a generate_mo.sh script to generate these for all languages, but you can do the German one by changing to the mailman/messages/de/LC_MESSAGES/ directory in the running installation and doing msgfmt mailman.po -o mailman.mo >> Please be more specific than `all types of system mails`. Which >> specific message subjects are not translated. > > It's exactly as mentioned in issue 993 the welcome and goodbye-messages > that I don't see translated. > > But also other examples: > - bounce-mail for the user that moderator approval is necessary (there > the text is in german, but the reason is in english) > - approval-mail for moderator (also text is in german, but subject and > reason in english) I'll look into these. If you don't have the mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the reason, but there may be a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/3/23 00:31, Onyeibo Oku wrote: > > (1) Mailman refuses to resolve to a preferred subdomain. If the > server's domain is "website.tld", I'd like mailman's homepage to be > at "list.website.tld". Mailman insists that I add "website.tld" to > the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an > ALLOWED HOST (same VPS/IP address nonetheless). The result is that > the homepage ends up at "https://website.tld/mailman3/lists" when the > desired url is "https://lists.website.tld/mailman3/lists". This is a > conflict because the main domain is intended for another service. How > do I approach this? This is all configured in your web server. It needs to proxy requests for lists.website.tld to gunicorn and depending on the web server, may need more. E.g. see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for nginx. > (2) See the traceback below: > ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server > Error: /mailman3/lists/ Traceback (most recent call last): ... > "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", > line 650, in get raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. > > It seems a migration is missing. How should I approach this? Set SITE_ID = 0 in your Django settings. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/25/25 01:02, Alexander Inzinger-Zrock via Mailman-users wrote: >>>> 3.1 parameter for default lookup table type >>> 3.2 pointing to command ''postmap'' >>> Both entries must be present or Mailman will error out before creating >> the postfix_lmtp file. There should be a template (actually, you can >> probably use it "as is") in site-packages/mailman/mta/postfix.cfg (or >> maybe in config/postfix.cfg). >> This file can be located anywhere, but I recommend putting it where >> mailman.cfg is (usually /etc/mailman3), and pointing to it in the >> [mta] section of mailman.cfg with the full path. > > + this file seems to be missing in my setting > + also the postmap command seemed to be unavailable for the user ''mailman''. > + [X] placed file in same dir as mailman.cfg (/etc/mailman3/) > + [X] replaced old config and pointed to it in mailman.cfg with full path: > #+begin_src txt /etc/mailman3/mailman.cfg > #configuration: python:mailman.config.postfix > configuration: /etc/mailman3/postfix.cfg > #+end_src > command ''mailman conf'' will show the new configuration path for > [mta] but no results for search term 'postmap_command' nor 'transport_file_type'. What does `mailman info` show for config file:? What does `mailman conf -s mta` show for [mta] configuration: [mta] incoming: mailman.mta.postfix.LMTP What's in /etc/mailman3/postfix.cfg? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: looking for more detailed traceback for shunted message

by Mark Sapiro

On 4/27/23 1:23 PM, bob B via Mailman-users wrote: > Had a message get shunted in > /opt/mailman/core/var/queue/shunt/. *** but that is the location in the docker environment, which we are running. > > The mailman log shows: > > Apr 26 13:09:56 2023 (31) ACCEPT: 2e0e82a5-0924-1777-bed8-34862417fe7e@[Redacted] > Apr 26 13:09:56 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:09:56 2023 (35) Traceback (most recent call last): > Apr 26 13:09:56 2023 (35) SHUNTING: 1682514596.7976818+6067e5ddeb70e4aad97977071b5ed00c41999057 > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:16 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:10:16 2023 (35) Traceback (most recent call last): > Apr 26 13:10:16 2023 (35) SHUNTING: 1682514616.5346222+7292ba8b651bc1bd76a9098733a39090e092add2 > > > > Is there anyway to get more info, Is there a more detailed traceback somewhere? I have never seen anything like this. There should be a complete Traceback in between the `Traceback (most recent call last):` line and the `SHUNTING: ...` line. However, I'm pretty sure the issue is a defective email which has non-ascii bytes in an explicit or implicit ascii part. You can see the raw message by pointing `mailman qfile` at the shunted .pck file(s) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Timeouts

by Mark Sapiro

On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: > The described timeouts are something that hyperkitty ought to be able to > avoid. For apache, the timeout is idle time between blocks of output. > Hyperkitty can avoid this by generating the archive in segments (based > on size, or elapsed time), flushing its output buffer, generating a > multi-file archive, and/or using Transfer-Encoding: chunked (chunked > doesn't work for http/2). It ought to be able to break the work into > blocks of "n" messages & do something to generate output. Besides > avoiding timeouts, working in segments allows the GUI to display > meaningful progress (e.g. if you're loading with XMLHttpRequest, > "onprogress") It really oughtn't be up to the user to break up the > request. It is not the web server that times out. I'm not sure about uwsgi because I don't use it, but the timeouts I see are on servers that use gunicorn as the WSGI interface to Django and the timeout is in a gunicorn worker. This is controlled by the timeout setting in the gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> Note that even 300 seconds is not enough to download the entire <https://mail.python.org/archives/list/python-dev@python.org/> archive. It may be possible to get HyperKitty to chunk the output to avoid this, but it doesn't currently do that. Care to submit an MR? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Mark Sapiro

On 5/25/24 10:00 AM, schaefer(a)alphanet.ch wrote: > > How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database. As far as the comment/display name in From: is concerned, what specific emails are you talking about? I don't know where `example.com` would come from unless you mean email from Django in which case look at your setting for ADMINS in your Django settings. > Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. The `mailman import21` command will properly import the Mailman 2.1 from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. If you have some customization in this area, that probably won't be handled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg)

by Mark Sapiro

On 1/2/19 4:20 PM, kelly.close(a)lrewater.com wrote: > Happy New Year! > > What isn't working yet are the archives, specifically the messages sent to lists showing up at .../mailman3/hyperkitty. I'm at a loss and I'm hoping maybe the folks on this list can help me bring it home. > > Messages are distributed to subscribers as they should be - subscribers can send from their emails or from the web site. People can subscribe, etc. It's all working great. Just no archives. Presumably the list is known to HyperKitty since you appear to be able to post from there. > I'm not sure what to try next or what info to provide here for help - can anyone suggest where I can look to see why archives aren't getting created, or let me know what information would be essential for me to post to get help on this? I'm using PostgreSQL for the database, Postfix for mail and Apache2 for the web server. The first place to look is Mailman's mailman.log. Are there errors there with tracebacks? Are there messages there like <timestamp> 2018 (9606) HyperKitty archived message <message-ID> to <archive_URL> Also is there an Archived-At: header in received posts? If either or both of those, what happens if you go to the URLs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > Folks, > > For my own purposes I have created some patches which apply to the > current mailman pip package. I'm only responding here to the issue of how to suggest patches. If you hope that they could be incorporated into the distribution, posting them to this list is not very effective. It is too easy for list posts to get lost, buried or forgotten. The best thing to do is to create an issue or issues at <https://gitlab.com/mailman/mailman/-/issues> (each issue should address only one thing). Then you can either attach the suggested patch to the issue or better, create a merge request with the patch to fix the issue. Ideally, the merge request would also contain relevant additions to unit tests. The first advantage is open issues do not get lost. They are always there in the tracker. The second is that all of the above is work that needs to be done in order to actually get the patch into the master branch, and the more of it you do, the less of it needs to be done by someone else who may not be as motivated as you are. Granted, this may seem like a burden for you. After all, you fixed your problem so why bother, but open source works best if we all contribute what we can to improve the product. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Welcome message issue

by Mark Sapiro

On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 9:33 AM, "Jörg M. Schulz" wrote: > But, also in mailman log. > Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) > Jan 09 12:24:06 2019 (17491) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 324, in _dispose > mime = mime_digest.finish() > File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish > footer = MIMEText(footer_text.encode(self._charset), > so the footers may not contain special characters. > Will review this one. in the above, self._charset is the character set of the lists preferred_language. The footer can't contain characters not in the character set of the list's preferred_language. For English (en) this is us-ascii. For German (de) it is iso-8859-1. These are artifacts from Mailman 2.1 You can change this for English by putting [language.en] charset: utf-8 in your mailman.cfg. This works because us-ascii is a proper subset of utf-8. For other languages, a change like this might require recoding of templates and/or a message catalog, but since we don't currently ship any non-English templates or message catalogs, that is moot at the moment. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Unable to configure mailman . Please give any information

by Mark Sapiro

On 3/13/19 11:47 PM, pradeep Kumar xplorer wrote: > Subject: [Fwd: Please list the variables i need to modify in the configure.in] > From: "Pradeep Kumar Xplorer" pradeepkumarxplorer(a)pradeepkumarxplorer.com > Date: Mon, March 11, 2019 4:04 am > To: mailman-users(a)mailman3.org > Priority: High > Read Receipt: Requested [ Send Read Receipt Now ] > Options: View Full Header | Print | Download this as a file > ---------------------------- Original Message ---------------------------- > Subject: Please list the variables i need to modify in the configure.in > From: "Pradeep Kumar Xplorer" > pradeepkumarxplorer(a)pradeepkumarxplorer.com > Date: Thu, March 7, 2019 6:36 am > To: mailman-users(a)python.org It appears you originally posted this to mailman-users(a)python.org where it would have been rejected as a post from a non-subscriber. That was probably the correct place for this as is it a Mailman 2.1 question and this list is for Mailman 3. > before running the configure script > I changed > AC_PREFIX_DEFAULT(/home1/explodi4/public_html/MAILMAN) > and it still says /home/mailman does not exist. > > Pradeep Kumar Xplorer > http://www.dhyanayoga.info > http://www.pradeepkumarxplorer.com/2016/CyberCrime/index.php You should not need to touch either configure.in or configure. Start with an unmodified configure and run `./configure --help` to see the options. It appears you may be running configure with '--prefix=/home/mailman' and that directory doesn't exist. See <https://www.list.org/mailman-install/node3.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Ann: Mailman Core 3.3.5 is out

by Mark Sapiro

On 9/29/21 9:59 AM, Brett Delmage via Mailman-users wrote: > On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > >> Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I >> would have >> to bypass the Debian installer. Or will there be Debian packages >> available? >> Same question for Postorius 1.3.6 Since Mailman 3.3.4 has been out for over six months and the latest Mailman 3 in even Debian sid is still 3.3.3, I would expect a long wait before these latest releases are available in Debian/Ubuntu. > I am excited to see 3.3.5 with its many updates available. Thanks to all > the contributors. > > I would like to know this too, as I was just about to install parallel > to the Debian package(s). I expect there are many of us. > > Going forward, what is the best way to maintain a stable version of > 3.3.5 with security and defect fixes only, exluding new features? Is > picking and applying individual checkins on gitlab the only way? I would suggest abandoning the Debian packages and installing as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. You should be able to keep all your existing configuration files and the database. You could even keep `list` as the Mailman user if desired. Once you have done this, upgrading via pip from PyPI or even from GitLab is very simple. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 9:22 PM, David Newman wrote: > > On my system that file lives here: > > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py It appears that you have installed following https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… and in that case, this is the file. > But the error persists after this addition and restarting MM3 and > mailmanweb and nginx: > > url(r'^mailman/', include('postorius.urls')), > > There is this 404 error in uwsgi.log: > > [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed > Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 > bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on > core 0) However, that's not the issue. You originally reported and I didn't look closely enough: > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. That URL is from a Mailman 2.1 installation. Are you still running Mailman 2.1? If so, you need to support Mailman 2.1's CGIs. In Apache, this would be something like ScriptAlias /mailman/ /parh/to/mailman/cgi-bin/ but nginx doesn't do that. You would need something like location /mailman/ { proxy_pass <something that can serve Mailman 2.1's CGIs.> } The something could be apache or ?? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Messages Showing Up as "Forwarded"

by Mark Sapiro

On 7/21/22 14:08, Mail Person wrote: > Sorry if this is an easy question, but I've got mailman3 up and running and all my test messages show up with forwarding language around them rather than just the message, see below: > > ---------- Forwarded message ---------- > From: Person <person(a)gmail.com> > To: all(a)domain.com > Cc: > Bcc: > Date: Thu, 21 Jul 2022 13:56:22 -0700 > Subject: Hello Members > This is a wonderful test > > > > ---------- Forwarded message ---------- > From: Person <person(a)gmail.com> > To: all(a)domain.com > Cc: > Bcc: > Date: Thu, 21 Jul 2022 13:56:22 -0700 > Subject: Hello Members > _______________________________________________ > Mailing list footer Are you looking at a MIME format digest or individual messages? If you are looking at a MIME format digest, this is expected depending on your mail program. You might prefer Plain Text Digests. If you are looking at individual messages, you probably have in your list's Settings -> DMARC Mitigations, DMARC mitigation action = "Wrap the message in an outer message From: the list" and DMARC Mitigate unconditionally = Yes. If you set DMARC mitigation action = "Replace From: with list address", the From: will be replaced, but the message won't be an attachment, and if you set DMARC Mitigate unconditionally = No, the selected action will be applied only to messages whose From: domain publishes a DMARC policy of reject or quarantine. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/22/23 09:32, Stephen J. Turnbull wrote: > > To diagnose, we really need to see that in context of the raw message > as received by the user. It was posted. The issue is the message declares Content-Transfer-Encoding: base64 but the body is not base64 encoded so the MUA tries to base64 decode it and even though that's invalid, produces the garbled output. > The only other thing I can think of is it might have something to do > with your internationalization settings. What is the default language > of the list? (This is available in Postorius.) Have you changed the > default encoding for English on your site? (I think you need to look > in mailman.cfg for this.) What is the default language of the site? I note that the message also declares Content-Type: text/plain; charset="utf-8" and Python's email package will base64 encode utf-8 message bodies. I also note that the messages Subject: is RFC 2047 encoded as utf-8. These tell me that the user's preferred_language if set or the list's preferred_language is not English or the charset for English is changed to utf-8. I tried to duplicate this in a test installation with the charset for English set to utf-8, but I get a similar response but with Subject: =?utf-8?q?The_results_of_your_email_commands?= and Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: postfix virtual domain and mailman 3

by Mark Sapiro

On 12/25/19 1:53 PM, work(a)andrefincato.info wrote: > > question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. > > is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so > > ``` > virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap > ``` I think the above should work for you. As far as `dump_json` is not an available module goes, the docs reference a lot of helper functions that are described at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/docs/documentati…>. These need to be imported. I.e., for dump_json ``` from mailman.testing.documentation import dump_json ``` But, if you are just trying to set an alias_domain for the domain and you have Postorius, you can do that via Postorius. If not Postorius you can use `mailman shell`, For example ``` $ mailman shell Welcome to the GNU Mailman shell >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = 'x.example.com' >>> ``` Then you need to do `mailman aliases` to create/update the maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Mark Sapiro

On 3/16/21 11:34 AM, Per Jessen wrote: > > I'm trying with this: > > find /var/spool/mailman/bad -type f -name \*pck |\ > while read m > do > (mailman qfile $m | grep -q ad.dr@ess) && echo $m > done > > Is there a better way? Yes, as you've noticed there is a significant startup cost every time you invoke the `mailman` command. to invoke it only once first see ``` mailman shell --details ``` (that refers to `mailman withlist` which is just another way to spell `mailman shell`). You will want to create a script similar to the following: import pickle from os import listdir def findaddr(address): for fname in listdir('/var/spool/mailman/bad'): if not fname.endswith('.pck'): continue with open(fname, 'rb') as fp: msg = pickle.load(fp) if address in msg.as_string(): print(fname) That's your script. Save it as findaddr.py where `mailman shell` can import it and run ``` mailman shell -r findaddr.py -- ad.dr@ess ``` This should print the names of any pickles that contain 'ad.dr@ess' Note however that this may not be necessary. If all you want is the names of the .pck files that mention 'ad.dr@ess', ``` grep ad.dr@ess /var/spool/mailman/bad/*.pck ``` should actually work reporting things like Binary file /var/spool/mailman/bad/*.pck matches with the actual file name, not *. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Permissions Error on /var/mail/mailman

by Mark Sapiro

On 2/3/26 10:28, dap1--- via Mailman-users wrote: > I am going in circles between postfix issues and mailman. However, before I continue with postfix debugging I want to resolve this first as it may be related for all I know. I'm getting this error in the postfix mail log: > > 2026-02-01T11:00:10.106626-05:00 dap002 postfix/local[113730]: 01623500076: to=<mailman(a)myhost.localdomain>, orig_to=<mailman>, relay=local, delay=0.16, de > lays=0.11/0.01/0/0.04, dsn=5.2.0, status=bounced (cannot update mailbox /var/mail/mailman for user mailman. cannot open file: Permission denied) > > I'm not sure why mailman is trying to write to that file but it is owned by root:mail. It is obvious why permission is denied to mailman. Is that directory really part of mailman3 and if so what should ownership and permissions be? If not then why is mailman trying to write to it? That path does not appear in any of the files in /etc/mailman3. Postfix is trying to deliver mail to a mailman@... address to the local user `mailman`. The user:group of the file /var/lib/mailman should be mailman:mail. if you `sudo chown mailman /var/lib/mailman`, those messages will be delivered to that mailbox and you can see what they are. What are all the log messages from `grep 01623500076 /var/log/mail.log`? Possibly you have set site_owner: mailman in mailman.cfg which would cause Mailman to send various notices to the local `mailman` user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/12/16 3:46 PM, deu8yz2mpq(a)snkmail.com wrote: > My quibble is that the multipart/digest encapsulation level is > gone. > > Barry Warsaw wrote at 15:16 -0400 on May 12, 2016: > > The MIME format of MIME digests should roughly be: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > But mm 2 had: > > multipart/mixed > text/plain (the digest heading) > text/plain (the TOC) > multipart/digest <--- this is the part that's gone in mm3 > message/rfc822 > message-1 > message/rfc822 > message-2 > ... > text/plain (footer) > > So was that removal intentional, a bug or ?? I'm sorry. I missed the point of your OP. I think it's a bug. The doctest at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, the part just after "The MIME digest has lots of good stuff, all contained in the multipart." is clearly missing the multipart/digest part. It appears that this got lost in the refactoring of the MM2 code for MM3. Please file an issue at <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me (msapiro), but it any case, I'll work on fixing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 3 months

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 9:57 PM, Paul Arenson wrote: > Success. I first tried to send a sample here but it was over 40k so it is being held for moderation. Then I realized my own list is set to hold all messages now, including my own, so I sent it and I got a message telling me it was held for moderation. I could see the message and it looked perfect (have to look in mail client, not hyperkitty). > > Sent it out and it looks fine on both my computer and on my iPhone. > > > Hyperkitty archive is without the html view but it looks ok and the images show up as attachments. I have now accepted your held message. This list's content filtering collapses alternatives so what you see from the list and in HyperKitty is the plain text alternative that your MUA (Mac mail) created, but all the URLs seem to work as links even though displayed as truncated in the Hyperkitty view. Also this list will filter out images. HyperKitty will only display plain text parts in the message and thread views. Other parts such as html and images that pass the list's content filtering will appear as attachment links in HyperKitty. Anyway, it appears your issue is resolved by setting Filter content and Collapse alternatives to No. I'm glad it's working for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/11/22 13:32, gordon(a)dickens.com wrote: > Hi Mark, > > I think that I found a hint as to the cause of my problems. > > I changed the apache2 LogLevel to debug and the following was then generated in /var/log/apache2/ssl_error_log: > > [Fri Feb 11 15:40:18.325675 2022] [core:debug] [pid 3982011] core.c(5280): (95)Operation not supported: [remote /var/lib/mailman3/web/static/uwsgi.sock:12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY) > > Apparently, there appears to be a problem with uwsgi.sock. > > My uwsgi.ini file has the following: > > uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock > > Also, my apache.conf for mailman3 has the followig: > > ProxyPass /mailman3 unix:/var/lib/mailman3/web/static/uwsgi.sock|uwsgi://localhost > > So do you see a problem in my configuration files that would cause the Operation Not Supported error with the uwsgi.sock file. I don't use uWSGI and have no experience with it at all, however here are some things to consider: For Apache to support uwsgi protocol you may need ``` a2enmod mod_proxy_uwsgi ``` However, I would suggest you use http rather than a unix socket. In your uwsgi.ini file instead of ``` uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock ``` which requires Apache support for uwsgi protocol, put ``` http-socket = 0.0.0.0:8000 ``` which will tell uwsgi to listen on TCP port 8000 and in Apache, use ``` ProxyPass /mailman3 http://127.0.0.1:8000 ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Changing default message limit (max_message_size)

by Mark Sapiro

On 5/24/19 7:05 AM, roger(a)reasonal.com wrote: > > $ bin/mailman shell -l list(a)example.com // Welcome to the GNU Mailman shell // The variable 'm' is the list(a)example.com // mailing list m.max_message_size = nn // commit() > > Unfortunately this does not work in the containerised mailman. > > So I get the container ID and run: > docker exec 3373d426996d /usr/local/bin/mailman shell -i test-list(a)iotcouncil.org.za > > (in the post by Mark it says "-l" but I get "unrecognized argument" -- I assume it should be -i for "interactive"? It should be -l or --listspec followed by the list posting address or list ID. I can't explain why you get "unrecognized argument". > Either way, it fires up the mailman shell and then throws me straight out back to the command line: > > Welcome to the GNU Mailman shell > The variable 'm' is the test-list(a)iotcouncil.org.za mailing list > >>> > [root@listman ~]# The above indicates there was a recognized '-l test-list(a)iotcouncil.org.za' argument because it knew to instantiate the list and assign it to 'm'. > So that doesn't help... I really can't help with Docker, but there is some issue that causes the command to exit as soon as it asks for input. It is waiting for interactive input and gets an end of file. Maybe @maxking can help with this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: mailman2 import not working

by Mark Sapiro

On 7/29/20 10:16 AM, Abhijith PA via Mailman-users wrote: > > When I restarted mailman. I got, > > Jul 29 16:58:21 2020 (14473) SHUNTING: > 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d > >> I think Mailman's var/ directory in the Debian package is >> /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? >> Is there a .pck file either in shunt/ or in out/? > > There is many .pck files in /var/lib/mailman3/queue/shunt and > /var/lib/mailman3/queue/out. And a lot of .psv files in > /var/lib/mailman3/queue/bad The .pck and (presumably one) .bak files in queue/out are messages waiting to be processed by out runner, the .bak is the one currently being processed. It appears your out queue is backlogged, but that is a separate issue and may just be transient. For every message in queue/shunt there should be a SHUNTING message and also an exception with Traceback logged in mailman.log. It is these Tracebacks we need to see to know what the issue might be. (If they're all the same exception, we only need one.) The .psv files in queue/bad are unparseable messages. There should be a "Skipping and preserving unparseable message:" entry in mailman.log for each of these. The messages can be seen with `mailman qfile` pointing to the .psv file. If they look like legitimate messages, it is possible a permissions issue that caused them to be unparseable. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 13:26, Christian via Mailman-users wrote: > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client() > What else is in the smtp.log? There should be messages like <timestamp> (<pid>) <message-id> smtp to redlatinleg(a)lists.ccalternatives.org for nn recips, completed in n.nnn seconds <timestamp> (<pid>) <message-id> post to redlatinleg(a)lists.ccalternatives.org from christian(a)naturalintelligence.us nnn bytes If there aren't, try setting [logging.smtp] level: debug in mailman.cfg, restarting Mailman core and see what you then get in smtp.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: How to fix lists with characters errors?

by Mark Sapiro

On 3/23/24 11:56, Helio Loureiro wrote: > Hi, > it is python 3.10. Problem is... some mailing lists were created long ago, > with python2 something. Most probably 2.5. And the tables on mysql were > set to latin1. This has nothing to do with the data or the charsets/collation in the database. The issue is the locale setting in your python is causing stdout output from the `mailman members` command to be encoded as `latin1` and at least some user's display name contains a `\u0142` (i.e. `ł` character. > That I know. Question now is how to fix this. Any suggestion? What is > the table? I probably can run some script for these specific lists that > have the failure, import data as latim-1, and update back to the table as > utf-8. That's not the issue. The issue is the Python in your venv has sys.stdout.encoding set to latin1, probably for locale reasons. You ca apply this patch ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -17,6 +17,7 @@ """The 'members' subcommand.""" +import sys import click from mailman.core.i18n import _ @@ -30,6 +31,9 @@ from zope.component import getUtility from zope.interface import implementer +sys.stdout.reconfigure(encoding='utf-8') + + def display_members(ctx, mlist, role, regular, digest, nomail, outfp, email_only, count_only): # Which type of digest recipients should we display? ``` to mailman/commands/cli_members.py to fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: particular list member seems unmanageable from CLI

by Mark Sapiro

On 8/22/25 02:32, Stephan via Mailman-users wrote: > We have a list member that got disabled due to bounces, but that should be fixed after we implemented DMARC and SPF. > > So as I don't know how to access the disabled status from the CLI (we have no GUI), I tried to delete and re-subscribe them. But although they are listed as a member, they cannot be deleted: > > # sudo -u list mailman members list(a)domain.tld | grep "$x" > M... <M....@web...> > # sudo -u list mailman delmembers -m "$x" -l list(a)domain.tld > Member not subscribed (skipping): M... <M....@web...> It looks like $x is `M... <M....@web...>`. It should be just `M....@web...` > How can I fix this from the command line? Either by restoring their "disabled" status, or deleting and re-subscribing them? There is no `mailman` subcommand to change a members delivery status. You can do it in `mailman shell` with an interaction like ``` # sudo -u list mailman shell -l list(a)domain.tld Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)domain.tld mailing list >>> mbr = m.members.get('M....@web...') >>> mbr.preferences.delivery_status = DeliveryStatus.enabled >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Use own mail server

by Mark Sapiro

On 11/27/25 12:10 PM, johannes.wolf--- via Mailman-users wrote: > Thanks for your responses. > I just did a few tests and I changed my config the following way for the mailing: > > mailman.cfg > <<<<< looks OK >>>>>> > > postconf -n > <<<<< Looks OK >>>>>> > > When I try to subscribe to a list called "Smartcity" the email is processed and the smtp.log shows the following lines: > <<<<< All of which look as they should. >>>>>> > > mailman.log > <<<<< Looks OK >>>>>> > > On my relaying mail host the email is coming up in "MAIL FROM" is set "smartcity-bounces+johannes.wolf=tester.de(a)mailing.tester.de" but the fields "Header-From", "Recipient" and "subject" are empty. > Why is the e-mail passed to my MTA but the adresses are not resolved correctly from before in Mailman3? What's in your postfix mail.log or whatever it's called? What's in the relay host's log? What happens to the mail? You say the fields "Header-From", "Recipient" and "subject" are empty, but I don't know what this means. The relevant SMTP commands are MAIL FROM, RCPT TO and DATA. Any RFC 5122 headers such as Subject: are included in the message passed as DATA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Accept these non-members

by Mark Sapiro

On 3/6/26 02:43, Lars Bjørndal wrote: > Hi, list! > > I have an announce only Mailman3 list. When I log into the web interface > as an admin user, and go to the specified list, and choose Settings, I find > the Message Acceptance tab. There, I find the edit field Accept these > non-members. But this field is empty, although I know that some people > have permissions and are able to post to this list. How can I find the > list of these non-members and add more people or delete someone? > > I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. I don't know what mailman-web version 4.2.21 is. Is this some downstream package? These are nonmembers whose moderation action is accept or defer. If your Postorius is >= 1.3.6, and the number of nonmembers is manageable you can just view the nonmembers list in Postorius and see their moderation action. Otherwise a `mailman shell` interaction like ``` $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> for nm in m.nonmembers.members: ... if nm.moderation_action in (Action.accept, Action.defer): ... print(f'{nm} {nm.moderation_action}') ... >>> ``` will print those nonmembers with Action.accept or Action.defer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/22/23 03:42, thomas--- via Mailman-users wrote: > Hello, > very new to mailman3, I used to manage mailman2 on a Debian 10 server. > The server has been upgraded to Debian 11 and mailman2 disappear… > > I try fresh install of mailman3, prerequisite to data migration, but without success. > If some can help, I would be really greatful. > > <VirtualHost *:80> > ServerName newsletter.mydomain.tld > > Alias /static /var/lib/mailman3/web/static > Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > > DocumentRoot /var/lib/mailman3/web/static > <Directory "/var/lib/mailman3/web/static"> > Require all granted You can probably fix the below error by adding options +Indexes here, but see below. > And now I have a 404 answer when consulting my http page. > > When trying to access `/static` sub-path, I get `Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found`. It is unclear to me what is doing a GET of /static/admin/ and why. GETs should by of actual files, e.g., things like /static/admin/css/base.css > I am a bit lost with that. So are we. Questions about the Debian package are better asked of Debian. See https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… We can provide much better help and support if you install via the resources mentioned in the reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Rejecting held emails

by Mark Sapiro

On 04/26/2018 08:43 AM, Darren Smith wrote: > > We recently had a phishing message make it through our spam filters and > arrive at a mailing list. The good news is that since it was not from a > list member it was in the held message queue. > > I was able to find the message in the var/messages directory by searching > for a keyword in the subject. However, after rejecting the message from > Postorius, the message doesn't seem to be removed from the var/messages > directory. Do you mean Reject and not Discard? Phishing/Spam should never be "rejected" for backscatter reasons. Reject should only be used for somehow inappropriate posts from known people. > Is this expected behavior? I know that infosec people won't be too happy > about a phishing email sitting around on our disk. (Infosec guys are > notoriously paranoid. :) ) > > Is there some sort of cleanup process that would remove these messages? If > not, does this pose an issue where over time disk usage will creep up? This > could be a pretty significant problem if that is the case. It's not the behavior I would "expect", but it is the way it currently works, and yes, all your concerns are valid. This is <https://gitlab.com/mailman/mailman/issues/257> which I just edited to note that in addition to not removing the pending db entry, the message isn't removed either. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 7:03 PM, Paul Arenson wrote: > > MAILMAN 2 > What I got from the Mailman 2 Wiki is "How to restrict the list so only authorized persons can post (moderation). If there is an option like that in Mailman 3 I want that. There is, but you can't do it the best way. See below. > SUMMARY > I want to be able to reply personally to the user if necessary without his or her message going to the list. So something like moderation. > > So let me take a guess: > > Default action to take when a non-member posts to the list AND > Default action to take when a member posts to the list > > should be set to HOLD FOR MODERATION? That will work and is probably what you want anyway. Your own posts will also be held, but you can just accept them. Alternatively, you could set your own Moderation setting to Accept or Default Processing so your posts won't be held, but don't do that as it allows anyone to post by spoofing your address in From:, Sender: or Reply-To: or the envelope sender. The best way to post without the post being held is pre-approval with an Approved: <password> header, where <password> is the list's moderator_password, but you can't set that in postorius so it won't work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Confusing mailman user model

by Mark Sapiro

On 7/19/20 8:10 AM, Gilles Filippini wrote: > Hi, > > I'm trying to understand the Mailman user model, and I'm confused about > the respective roles of tables 'auth_user' and 'user'. auth_user is a Django auth table. These are the users listed in the Django admin web UI. user is Mailman core's users. > Both have an 'id' column referred to as 'user_id' when used as a foreign > key. But there seems to be no relation at all between them as they use > different ids for the same user. Right, they are unrelated. > Our mailman server was migrated from mailman2 to mailman3 about 1.5 year > ago, and there is an inconsistency I'd like to fix: > 2 of our users have a registered Mailman account with their respective > email addresses in table 'auth_user', but these very same addresses in > the 'address' table are linked to another old admin account in the > 'user' table. Their Mailman account is the 'old' one. the auth_user account is a Django account > > Then if add one of these addresses as a domain owner, it it the old > admin address which is selected instead. How could I fix that? That's because domain owner in a Mailman thing and involvs the Mailman user. You could delete the Django users via the Django admin UI and then re-register them via Postorius. That *might* work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 2/24/22 18:21, chucka(a)blackforest-co.com wrote: > I have this working: > > #!/bin/bash > H="http://lists.mysite.org/admin.cgi/newsletter-mysite.org/members" > case $1 in > 'add') curl "$H/add?subscribees=$2&adminpw=verysecret" ;; > 'del') curl "$H/del?subscribees=$2&adminpw=verysecret" ;; > esac > > and scan the return for "Successfully [Un]subscribed" Since the above is MM 2.1 I'm assuming you are asking how to do the above in MM 3 via REST. Here are some examples: To add a single user curl -urestadmin:restpass \ --request POST \ -H 'Content-Type: application/json' \ --data-binary '{"list_id": "list.example.com", "subscriber": "user(a)example.net", "display_name": "Joe User", "pre_verified": true, "pre_confirmed": true, "pre_approved": true}' \ http://localhost:8001/3.1/members Response is empty or a JSON object describing the error. To delete a single user: curl -urestadmin:restpass \ --request DELETE \ http://localhost:8001/3.1/lists/list.example.com/member/user@example.net Response as above To delete a list of users: curl -urestadmin:restpass \ --request DELETE \ -H 'Content-Type: application/json' \ --data-binary '{"emails": ["user(a)example.net","other(a)example.org"]}' \ http://localhost:8001/3.1/lists/list.example.com/roster/member Response is a JSON object similar to {"user(a)example.net": true, "other(a)example.org": false, "http_etag": "\"...\""} where success or failure is indicated by a true or false value for each address or a JSON object describing the error if any. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Null sender?

by Mark Sapiro

On 6/28/20 6:58 AM, tom(a)gather.coop wrote: > Does Mailman generally send email with a null sender? > > This is what I see in the log: > > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <> > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT' > > Notice the empty MAIL FROM. > > Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject. > > Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail. It isn't Mailman doing this. It is the MTA at mail.example.coop that is reporting the bounce of some message from the techque(a)example.org list. The log messages you see are Mailman's receipt of the bounce DSN. Bounce DSNs are always sent with a null envelope sender so if they are undeliverable, it doesn't result in another bounce. See <https://www.rfc-editor.org/rfc/rfc3461.html#section-6.1>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/25/24 23:07, Mark wrote: > > So, the template is all good, it can be accessed by Lynx, but the part > of the Mailman suite that sends out the custom Welcome message cannot > access it and spits out the error. > > Where are the custom templates stored? Is there a permissions issue > perhaps? A grep for the text of my Welcome message turns up zero results. They are stored in the postorius_emailtemplate table in the mailmanweb database. And yes, I think there is some permissions issue, but it is not simple. It probably involves apparmor or some other security manager. If it were simple, the mailman shell test I suggested at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… would fail. > By the way, in Lynx when the template's URI uses the public ip adress -- > ie. > > http://my-public-ip-address/mailman3/api/templates/list/mytestlist.mydomain… > > ... it returns a "404 page not found" in Lynx. Which is probably why that setting sent the welcome with empty content. > Given that this is pretty much an out-of-the-box installation (venv > installation as per the docs) and everything else works perfectly I'm > thinking surely others have encountered this. Or is it just me? I just did a test on my development system and I see the same timeout error, so it's not just you. I'll work on this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: slow restart time for mailmanweb

by Mark Sapiro

On 12/28/21 1:28 PM, William Oliver wrote: > > If I just stop the thing and then start it, it goes fast. Here's that > log: > > Dec 28 16:27:22 emergenus systemd[1]: Stopping GNU Mailing List > Manager... > Dec 28 16:27:24 emergenus mailman[23408]: Shutting down Mailman's > master runner > Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Succeeded. > Dec 28 16:27:27 emergenus systemd[1]: Stopped GNU Mailing List Manager. > Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Consumed > 42.834s CPU time. > Dec 28 16:27:27 emergenus systemd[1]: Starting GNU Mailing List > Manager... > Dec 28 16:27:29 emergenus kernel: [ 8076.868797] [UFW BLOCK] IN=eth0 > OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.108 > DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=58971 PROTO=TCP > SPT=44610 DPT=21987 WINDOW=1024 RES=0x00 SYN URGP=0 > Dec 28 16:27:29 emergenus mailman[23433]: Starting Mailman's master > runner > Dec 28 16:27:29 emergenus mailman[23433]: Generating MTA alias maps These log entries are from restarting mailman, not mailmanweb. > Dec 28 16:27:30 emergenus systemd[1]: mailman3.service: Can't open PID > file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not > permitted > > I don't know what's up with the pid thing -- it moves right on in about > 1 second. It's a race condition. systemd (systemctl start) is trying to read /opt/mailman/mm/var/master.pid before the master has created it. That's why it says (yet?). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: mailman findmember runs very slow

by Mark Sapiro

On 7/12/24 3:34 PM, Wong, Wesley wrote: > Hi, I am noticing a performance issue with Mailman 3 when using the "mailman findmember" CLI command to search for email address or name. On average, it takes about 15 - 20 seconds to run a query which is very slow IMHO. When searching through web administrator interface for Users, it takes only 1 -2 seconds. Is there a reason for such a discrepancy between the two interfaces? Is there any tuning to the CLI that could help with the performance issue? Here is the setup information regarding the VM hosting the Mailman 3 server: This is actually https://gitlab.com/mailman/mailman/-/issues/1095 The basic loop is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_f… and the time consuming part is https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_f… On mail.python.org which has about 75,000 users ``` for user in getUtility(IUserManager).users: continue ``` takes a few seconds, but ``` for user in getUtility(IUserManager).users: emails = [address.email for address in user.addresses] continue ``` takes almost 3 minutes which is about the time that `findmembers` takes in total. I've tried changing this to ``` for user in getUtility(IUserManager).users: if len(user.addresses) == 1: emails = [user.addresses[0].emails] else: emails = [address.email for address in user.addresses] continue ``` but it doesn't help. Just referencing user.addresses in the loop as in ``` for user in getUtility(IUserManager).users: x = user.addresses continue ``` takes 3 minutes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Creating and placing custom templates

by Mark Sapiro

On 5/2/19 12:45 PM, kelly.close(a)lrewater.com wrote: > > Here's what I'm doing: > > I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ What is the setting, if any, for 'layout' in your mailman.cfg? If, for example, you have layout: fhs The default var_dir in that layout is /var/lib/mailman, not /var/lib/mailman3, although that could be changed in a [paths.fhs] section. > In that folder I created the following folders and made sure they were properly owned (by list:list) > /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ > > Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". Yes, you do need the .txt extension. If this doesn't work, it's possible you have a different URI for the template. Try bin/mailman shell Welcome to the GNU Mailman shell'list:member:regular:footer', >>> tm = getUtility(ITemplateManager) >>> tm.raw('list:member:regular:footer', 'f2p2-test.udfcd-lists.org') This should return something like 'mailman:///$listname/$language/list:member:regular:footer.txt' Does it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

When I go to https://.../admin/ I get a Django Administration screen and in the upper right hand corner I see WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:55 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 5:11 PM, Mark Sapiro wrote: > On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: >> Is this anything to be concerned about? It seems like an attempted >> break-in as I have no user named alekos.pantazis. > > > First, this is a Django user, not a Mailman user.... > The error you see seems to say that > django_mailman3/templates/django_mailman3/profile/profile.py contains > {% load gravatar %} at line 3 but there is no > django_mailman3/templatetags/d_gravatar.py file. The above should say `contains {% > load d_gravatar %} at line 3` Regarding attempted breakin. It's not that. Just someone signing up or logging in at your web UI and visiting their user profile. If you go to your Django admin UI (https://.../admin/) you should see that user. The error seems to be something broken in your installation. Can you visit your user-profile? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 10 months

[MM3-users] Re: Special Characters Issue when using Wordpress HTML messages

by Mark Sapiro

On 3/22/22 07:46, ryan.anderson.4--- via Mailman-users wrote: > Hello, > > We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings. You can accept HTML and not convert it if in Postorius -> Settings -> Alter Messages, assuming Filter content is yes, ensure Pass types includes `text/html` or maybe `text` to include all text maintypes and both Collapse alternatives and Convert html to plaintext are set to No. > The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . They probably aren't ` and -, but rather things like Unicode Left Single Quote and En Dash. > We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything. When you say you changed the character set to UTF-8, what did you do? If you set ``` [language.en] charset: utf-8 ``` in mailman.cfg and restart mailman core, that should allow those characters without replacing them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Mark Sapiro

On 3/3/25 07:52, Stefan Bauer via Mailman-users wrote: > > trying to update mailman3 to lastest version, we fail during > > mailman-web migrate with: > > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, > django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > Applying account.0006_emailaddress_lower...Traceback (most recent call > last): > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", > line 89, in _execute > return self.cursor.execute(sql, params) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", > line 328, in execute > return super().execute(query, params) > sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang and replace psycopg2 with sqlite3. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… > We found a workaround to fake the migration with > > migrate --fake You should fix the issue with the DB and run the migrations. > Could this be some duplicate users with same mail-address? This is not related to Mailman users. It is Django users. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Mark Sapiro

On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: > We use a multi-hop SMTP system to go from the inside of our network out > to the Internet at the domain test.lists.example.com. > > The setup is this way for ingress: > > {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 Connector) > -> Mailman for delivery to listserv > > Egress is this: > > Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET > > -- > > When a message is sent an invalid list (we'll call it > invalid(a)test.lists.example.com) we end up with a nasty side effect in > the system. The "no such recipient" response gets sent to the smtpproxy > machine and then *it gets redelivered back to Mailman* as a redelivery > as if it isn't accepting a permanent-failure condition code. I don't understand why this is happening. Whatever MTA is seeing the "no such recipient" status and creating the response DSN should be sending it to the envelope sender of the original message so it should not be sent to the invalid mailman address. Is one of the MTAs in the delivery chain to Mailman rewriting the envelope sender? What are the MTA log messages from all the MTAs whos logs you have access to? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Subject Munging

by Mark Sapiro

On 7/5/24 08:34, Sam Darwin via Mailman-users wrote: > Hi, > > We have a user who is proposing that reply messages from a mailing list should be in the following format: > > Re: [MM3-users] Ubuntu 24.04 upgrade notes > > and not > > [MM3-users] Re: Ubuntu 24.04 upgrade notes > > Their reason... is that mailman2, and other lists, used to do it that way. > > I myself am agnostic about the difference, and probably prefer to keep things the way mailman3 recommends. > > The questions are: > 1. What could be explained to the user to convince them the new method is preferable. This is to support prefixes that contain %d for the message number. Suppose the prefix is [List #%d] and a post to the list has prefixed subject [List #501] A Subject. With old style, a reply a few posts later might have subject Re: [List #504] A Subject. But it is not a reply to [List #504], it is message [List #504] replying to `A Subject.` so the appropriate subject is [List #504] Re: A Subject. > 2. Can this be customized with a Setting? (Not that we will end up modifying it. Just curious). In mailman 2.1 this was called OLD_STYLE_PREFIXING and prefixes without %d could optionally do it the old way or the new way , but prefixes with %d always did it the new way. For Mailman 3 we always do it the new way even if the prefix does not contain %d. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Howto: Mass import of nonmembers in several lists?

by Mark Sapiro

On 1/10/22 4:00 AM, Paul Paulchen wrote: > > So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. > I thought so, because the import21 command did this as well when we migrated to mailman3. You could script it with `mailman shell`. If you really want this, I'll help. > I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. > But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! You can't without modifying the code. > Hope I explained my case properly. I appreciate your responds! Thanks in advance. My question is why do you want to add these nonmembers. The only thing gained by adding a nonmember is the ability to set the nonmember's moderation action to other than the default, and you can handle that with the legacy * these non-members settings which take priority over the nonmember's moderation action anyway. Note that if a nonmember posts to a list, she will automatically be added to the list as a nonmember with default moderation action if she isn't one of the list's nonmembers already. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > Thank you Mark. > > What you have said is right.. > > I found a list with two "hyperkitty" records in the listarchiver in the > database. I had removed the list and recreated it and now I found it is > working fine. The recreated list is having only one record. OK, but that's not a reasonable way to fix this in general. You can just remove the `extra` record using a direct database query which is probably the least disruptive way to fix this. > After searching the links you provided I found there is just a work around > but not the precaution to be taken for not getting the duplicate record. > > Can you say what might be the reason for this duplication? If I need to > provide any details, please let me know. As noted in the threads I referenced, we don't know the cause. Yours is the first report of this issue with the `hyperkitty` archiver. In all the other reports, the duplicate archiver has been `mhonarc`. If it happens again and you know the exact sequence of events that led to it, i.e. what was done with the list between the last time it worked and when it stopped working, that might give us clues, but currently we are at a total loss to understand how this happens. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mark Sapiro

On 6/17/23 17:02, Mike Wertheim wrote: > I set `remove_dkim_headers: yes` in the [mta] section of mailman.cfg. > > I'm seeing a bunch of these errors in the logs: > 2023-06-17 18:57:11 1qAbMA-005Y7W-HP ** mike.wertheim(a)gmail.com > <mailto:mike.wertheim@gmail.com> R=dnslookup_single_domain > T=remote_smtp_single_domain H=alt2.gmail-smtp-in.l.google.com > <http://alt2.gmail-smtp-in.l.google.com> [172.253.62.26]: SMTP error > from remote mail server after end of data: 550-5.7.26 Unauthenticated > email from gmail.com <http://gmail.com> is not accepted due to > domain's\n550-5.7.26 DMARC policy. Please contact the administrator of > gmail.com <http://gmail.com> domain\n550-5.7.26 if this was a legitimate > mail. Please visit\n550-5.7.26 > https://support.google.com/mail/answer/2451690 > <https://support.google.com/mail/answer/2451690> to learn about the\n550 > 5.7.26 DMARC initiative. > w13-20020a05622a190d00b003fde5babbf5si1170418qtc.14 - gsmtp Your issue is mail From: the gmail.com domain to the list and sent to gmail users is being bounced because it fails DMARC. I.e. Gmail applies a DMARC policy of p=reject to mail From: gmail.com even though it's published DMARC policy is p=none. You need to apply DMARC mitigations to this mail. Unfortunately, this requires setting DMARC Mitigate unconditionally to Yes. Mailman 2.1 has a feature to apply DMARC mitigation to messages From: specific domains regardless of any domain specific DMARC Policy. Unfortunately this hasn't been implemented in Mailman 3 yet. I just filed https://gitlab.com/mailman/mailman/-/issues/1084 for that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: How to keep virtualenv install secure?

by Mark Sapiro

On 11/7/24 01:31, Lichtinger, Bernhard wrote: > Hi, > > I am looking for some advice: If we use the virtualenv install method, how does one keep track of security updates for all the installed dependencies? > > I can think of: > - Upgrade regularly all installed packages inside the virtualenv. This might break mailman3 if there are incompatible updates. You can do in the venv ``` pip install --upgrade --upgrade-strategy eager mailman psycopg2-binary mailman-web mailman-hyperkitty ``` I'm not sure if this will update dependencies if there are no updates to the named package, but in any case, incompatibilities should be avoided because if a newer version of a dependency in incompatible, the dependency should be pinned to a compatible version in the project's requirements. > - Try to track all dependencies and check if there are security updates published. This might be impossible to achieve. It shouldn't be too difficult to script this. ``` Get the output from `pip freeze` in the venv for each line split it on `==` into PACKAGE and VERSION get https://pypi.org/rss/project/PACKAGE/releases.xml find the first <title>VERSION</title> and compare that VERSION to the VERSION from `pip freeze` ``` This won't tell you if the newer version is a security update, but it will tell you which packages have newer versions. > - Security updates are so rare, we do not need to bother. ;) For the Mailman dependencies, this is probably true. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Approve an email

by Mark Sapiro

On 12/26/22 12:08, Lars Bjørndal wrote: > Hi, list! > > I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and > postorius-1.3.6-2.fc36.noarch installed. with the command > > sudo -u mailman mailman3 create <listname> > > I was able to create a list. > > I'm not able to find out how to setup and configure the postorius > package. There's no mailman-web command. See <https://docs.mailman3.org/projects/postorius/en/latest/>. I don't know how you invoke the Django management command in the postorius-1.3.6-2.fc36.noarch package. It could be manage.py or django-admin or something else. > Hyperkitty will not installed du to a dependency conflict, but I dont > need archiving for the list. > > Here comes my quesitons: > > - What's the easiest way to approve an email sent to the list? Approving held messages via email requires Mailman core >= 3.3.5. See <https://gitlab.com/mailman/mailman/-/issues/169> Thus, the easiest way is via Postorius. > - How can I configure the list to accept messages also from non members? Set the list's default_nonmember_action to Action.defer. This can be done via Postorius, mailman shell or the REST API. > - How can I setup postorius to work on Fedora? I have django-admin, but > I'm not sure where to go. See the Postorius docs at https://docs.mailman3.org/projects/postorius/en/latest/setup.html#installat… to get started. (replace `python manage.py` with `django-admin`) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 10:37, Eggert Ehmke via Mailman-users wrote: > Hello Steve, > I really would appreciate to get some help on the withlist command. I really like to program python, but this interface is not at all intuitive. I also find it strange to do administrative tasks in a programming language. In this special case, I believe it should be possible to work on the display names in Postorius in the member settings. You can update user display names in Postorius via the Users tab at the top of the page, but it would be a tedious, one at a time process, and I don't think you can modify address display names in Postorius and those are the ones `mailman members` displays. I just posted a mailman shell (aka withlist) interaction at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Try that. > I also find it strange to do administrative tasks in a programming language. Understood, but there are a couple of things at work here. One is that this particular task is a one-off the correct the result of a bug, but perhaps more significantly, mailman developers (at least me) are comfortable with `withlist` (it's been around since MM 2.1) and if I can do it that way, it reduces the motivation to make something more friendly for the normal admin. Unfortunately doing things easily that way requires a lot of specialized knowledge of Mailman internals, so most admins need help with it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Mailman3 Docker persmission denied

by Mark Sapiro

On 1/6/25 13:09, Commander456 wrote: > Hello everyone, > > I recently installed the mailman-core Docker image (Version 0.5) and tried to create a list using the mailman commands inside the container. I used the --notify argument but doesn't receive any mail (I'm the list owner), However, inside the mailman.log I get the following error: > > Jan 06 20:54:25 2025 (156) Uncaught runner exception: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' > Jan 06 20:54:25 2025 (156) Traceback (most recent call last): > File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 164, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/site-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > ^^^^^^^^^^^^^^^^^^^^ > PermissionError: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' > Jan 06 20:54:25 2025 (156) Skipping and preserving unparseable message: 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8 Did you run `mailman create` as user `mailman`? Also did the command print a `Created mailing list:` message? In any case, it looks like the list was created and the command generated the notification which was queued in the virgin queue as 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck, but then virgin runner was unable to read it, but if there was no `Failed to unlink/preserve backup file:` message in the log the file should have been moved to /opt/mailman/var/queue/bad/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.psv. What is ownership and permissions of that file, and what is the user running the various runners? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Mailman3 Setup

by Mark Sapiro

On 6/11/22 06:02, George R. Kasica wrote: > Mark: > > These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. I virtualenv is not a "container", at least in the sense of a Docker container. It is just a way of isolating an environment from various OS things and vice versa. You do not need to install in a virtualenv. You can follow the procedure for installing in a virtualenv and just omit the bits about creating and activating the virtualenv However, if you do not install in a virtualenv, you are vulnerable to OS package updates breaking things. For example, installation of Mailman core installs SQLAlchemy <1.4 because Mailman core is not currently compatible with SQLAlchemy >=1.4. If an OS package upgrade installs SQLAlchemy >=1.4, that will break your Mailman installation. > If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? You actually don't need to remove anything because whatever is installed in the virtualenv will be what's used when the virtualenv is active. However, any Mailman specific stuff installed systemwide will not be used and is just wasted space and could be uninstalled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 9/16/23 5:29 AM, Paul Rubin wrote: > *I need to know what to remove, how to correctly update, etc., That said > the two scripts appear to be very similar:* > > mail:/opt/mailman # head /usr/bin/mailman > > #!/usr/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' > __requires__ = 'mailman==3.3.4' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( This is no good because it uses the system Python and won't have the venv's site-packages in its path. > mail:/opt/mailman # head /opt/mailman/venv/bin/mailman > #!/opt/mailman/venv/bin/python3 > # -*- coding: utf-8 -*- > import re > import sys > from mailman.bin.mailman import main > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) > sys.exit(main()) > mail:/opt/mailman # This one is good because it uses the venv python3 and thus uses site-packages from the venv. > *Given the two years since the last reboot I also tried following * > https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was > running the latest* > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web Thin may be part of the issue. The above may not upgrade dependencies as needed. You may need the `--upgrade-strategy eager` option. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 11/6/19 9:18 AM, josh(a)caluette.com wrote: > I just setup a new Mailman 3 server using maxking/docker-mailman from GitHub. I got everything working just right including changing the footer template for messages. However, when trying to set anything in a Welcome template, I am encountering these same errors. > > I have confirmed that the mailman-core container is able to download the template via curl using the http://mailman-web:8000/ api URL and gets the correct text, but anytime I try to mass subscribe, it fails with the errors that Brian had provided and I get an HTTP 500 error. > > If I remove the Welcome template, then I can do mass subscribe just fine. > > Here are the logs: > > Nov 06 17:10:13 2019 (29) deque: > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 384, in _make_request > six.raise_from(e, None) > File "<string>", line 2, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 380, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1331, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 297, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 258, in _read_status > line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") > File "/usr/lib/python3.6/socket.py", line 586, in readinto > return self._sock.recv_into(b) > socket.timeout: timed out Have you set POSTORIUS_TEMPLATE_BASE_URL appropriately in your settings_local.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/27/21 3:48 PM, Ruth Ivimey-Cook wrote: > > It is also possible to Alter existing databases and tables, but with one > catch: the maximum table row length is reduced, so some tables will need > to be adjusted (e.g. converting varchar(255) to varchar(230)). This is misleading. The maximum row length depends on the actual data stored in the row. The sum of the various column size limits for VARCHAR and other columns can well exceed the maximum row size as long as the sum of the lengths of the actual data stored in the row does not. The significant issue is all these limits are bytes, not characters, so in the worst case, a VARCHAR(255) column can only store 85 3-byte utf8 encoded unicodes or 63 4-byte utf8mb4 encoded unicodes, but this too is misleading an most strings contain single byte encodings with some 2 or 3 byte encodings and maybe at most one or two 4-byte encodings. Furthermore, the problem issues are essentially limited to emojis and possibly other 4-byte encoded symbols in email subject headers and bodies. Bodies are a TEXT field and the data are stored separately and do not affect the row size and subjects are defined with a maximum length of 512 bytes which should be sufficient. None of the data stored in rows is at all likely to exceed the maximum row length, even with a lot of 4-byte encodings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Mark Sapiro

On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ… although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Mailman recovery test did not go as planned

by Mark Sapiro

On 8/9/22 07:19, Stephen J. Turnbull wrote: > > You don't do it with HyperKitty (I'm pretty sure you can export mboxes > from HyperKitty, but I don't think it would be timely, you have to do > it by hand). The sample archiver (which you can enable in mailman.cfg > IIRC, haven't done it in a while) would make the mbox files directly > from the core at the same time that they are sent to HyperKitty. It's > possible to have both HyperKitty and the sample archiver enabled at > the same time. The `sample archiver` is actually called the prototype archiver and it is typically enabled by default. The messages are stored in maildir format in Mailman's var/archives/prototype/ directory in sub-directories with names of the list posting addresses. You would need to convert maildir to mbox format to import to hyperkitty. A simple script to do this is ``` #!/usr/bin/python3 """Run this with the list posting address as it's argument.""" import os import sys from mailbox import mbox, Maildir MDIR = '/path/to/mailman/var/archives/prototype/' MBOX = '/path/to/output_directory' if len(sys.argv) != 2: print(f'Usage: {sys.argv[0]} list_posting_address', file=sys.stderr) sys.exit(1) mdir = Maildir(os.path.join(MDIR, sys.argv[1]), create=False) mlbox = mbox(os.path.join(MBOX, sys.argv[1]), create=True) for msg in mdir: mlbox.add(msg) mdir.close() mlbox.close() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Time Zone Problem In Postorius

by Mark Sapiro

On 1/12/22 7:34 PM, Alan So wrote: > I notice that the template was updated to add the code. However, I still observe an issue. > > If the correct hold date is: 2022-01-13 10:16 GMT+8 or 2022-01-13 02:16 GMT > If I select my time zone as Asia/Hong_Kong, it is displayed as Jan. 13, 2022, 2:16 a.m. > If I select time zone as GMT, it is displayed as Jan. 12, 2022, 6:16 p.m. > > There is a shift of -8 hours when displaying the time in Postorius. I cannot find the detail of the held message from database tables yet. Not sure how the hold date was stored at this moment. As you note later, the hold time is stored in UTC. It should be rendered in Postorius held message view in the timezone that you have set in your user-profile. The timezone conversion is in Django. It is defined in the template as ``` {{ msg.hold_date|datetime_parse|localtime|date:"DATETIME_FORMAT"}} ``` where msg.hold_date is the time in UTC. I think the issue is that while msg.hold_date in in UTC, it is a naive datetime.datetime object (see https://docs.djangoproject.com/en/4.0/topics/i18n/timezones/#interpretation…) so if your Django setting for TIME_ZONE is Asia/Hong_Kong it is interpreted as UTC +0800 so that subtracts 8 hours and then conversion to your profile timezone if Asia/Hong_Kong adds 8 hours back. I think if you set `TIME_ZONE = 'UTC'` you will get the behavior you expect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails

by Mark Sapiro

On 10/12/24 1:44 AM, francesd919--- via Mailman-users wrote: > Hi everyone, > > I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. > These emails mentioned that the subscription was disabled due to bounce score. > Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > I have some questions: > > 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? > 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. > 3. What could have cuased functioning emails to bounce and therefore being disabled? The answer to all those is you upgraded from a Mailman core version prior to 3.3.1. Prior to that, bounces were recorded in the database but not processed. when you upgraded, they all got processed at once. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… which includes a `mailman shell` interaction to re-enable all the subscriptions disabled by bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

On 10/31/24 16:17, Hirayama, Pat wrote: > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Then for example if your list domain is example.com and its alias domain is x.example.com, you could modify one line in the postfix_vmap file for the `listname` mappings from ``` listname-bounces(a)example.com listname-bounces(a)x.example.com ``` to ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` and then run postmap on the file. The problem is any time you create or delete a list or run `mailman aliases` or run `mailman start` with the --generate-alias-file option, the file is regenerated and you will have to edit it again. To avoid that issue, you can create a separate vmap file containing only the ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Cannot locate manage.py

by Mark Sapiro

On 1/21/20 4:08 PM, Frank van den Heuvel wrote: > Hello, > > While following https://docs.mailman3.org/en/latest/migration.html, I > want to execute: > > python manage.py hyperkitty_import -l foo-list(a)example.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > Of course edited with values for my list. But I already get stuck in not > being able to locate "manage.py". > > When I run "locate manage.py", I get: > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl > > /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py > /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py > > Which one is the right one? Probably none of those. I'm not that familiar with the file layout in the Debian package if that's what you installed, but I would expect to find it in /opt/mailman/mm/venv/bin/ and I'd expect to find the files django_admin and django_admin.py. Both of those will run the Django management interface, but they won't work because they won't access your settings. I put the following executable in /opt/mailman/mm/bin #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ This assumes my settings.py file is /opt/mailman/mm/settings.py. If yours is elsewhere you may need to adjust PYTHONPATH and/or DJANGO_SETTINGS_MODULE. For example, on another server with the settings at /opt/mailman/mm/mailman_web/production.py I have export DJANGO_SETTINGS_MODULE=mailman_web.production -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Edit archived email? Is it possible?

by Mark Sapiro

On 9/28/21 6:02 AM, Prasanth Nair wrote: > Hello, > > Does anyone know how to edit an archived email in Mailman3? It is possible > in Mailman2 ( > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M…) > Is there any option similar to this in Mailman3? In some sense the process is the same but possibly even simpler in Mailman 3. You need to modify the underlying data which requires appropriate access to the server. In Mailman 3, the data are in the hyperkitty_email table in Mailman's database. You can get the Message-ID hash from the URL to the archived message, e.g. for the message to which I'm replying, the URL is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have access, you can do database queries like ``` SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; ``` and ``` UPDATE hyperkitty_email SET content = '<new content>' WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; UPDATE hyperkitty_email SET subject = '<new subject>' WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; ``` If the message has attachments, they are in the hyperkitty_attachment table and can be referenced by `email_id` which is the corresponding `id` from the hyperkitty_email entry. You can also do similar things via `django-admin shell`. E.g. ``` $ django-admin shell Python ... (InteractiveConsole) >>> from hyperkitty.models.email import Email >>> x = Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >>> print(x[0].content) ``` but this requires some knowledge of HyperKitty's models and Django's ORM. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/8/22 17:57, Philippe B wrote: > Thanks. I'm getting: > > >>> owner.delivery_status > <DeliveryStatus.by_moderator: 4> > > for the 2 lists with that odd behavior (as opposed to `<DeliveryStatus.enabled: 1>` for several other lists I checked). > > What does that 4 mean? It means that owner's delivery was disabled by moderator action[1]. You want to set it enabled as I indicated in my prior post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. That is why the owners don't get notices, and you need to set their delivery status enabled so they will. Note that this only affects notices. It doesn't affect list posts assuming they are list members. That is controlled by the member's delivery status And because there are no eligible owner or moderator recipients the notices go to the configured site_owner. [1] The disabled by moderator status can occur in the following way for a list imported from Mailman 2.1. If the address in MM 2.1 is both an owner or moderator and also a list member, and the list member's delivery was disabled in MM 2.1, both the imported member and owner/moderator will have delivery disabled. This is really a bug in import21 as in Mailman 2.1, owner/moderator delivery couldn't be disabled, it shouldn't be imported as disabled. I have just created https://gitlab.com/mailman/mailman/-/issues/977 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Mailman 3 bounce handling and DKIM mitigation

by Mark Sapiro

On 09/05/2017 01:14 PM, David Krantz wrote: > > I have a question on bounce handling. I get the impression that > bounces are just lost and neither handled nor forwarded to the list > admin. Is this a known problem? I am running mailman from git, but > about version 3.1 and use postfix. Bounce processing in Mailman 3 is currently not done. See <https://gitlab.com/mailman/mailman/issues/343>. > I find lots of things in the > bounceevents table. Is there any way to find out more on these events? > I probably can configure postfix to send listname-bounce@domain to an > admin adress. Or for that matter hack mailman to send it to the > correct admin. Your ideas are possible. Until it's fixed, you could just make postfix forward the listname-bounces address to listname-owner. I think this will then get the LMTP runner to send them to the owner. > Also the DKIM mitigation does not seem to detect DKIM domains. If I > force the mitigation for all mails it works but that of course has > annoying consequences although mostly cosmetic. This has caused quite > a number of bounces for my lists (as well as being temporarily banned > by at least Microsoft). I assume you mean DMARC mitigation. It should work for From: domains that publish DMARC policy 'reject' or 'quarantine' without setting DMARC Mitigate unconditionally. What if anything do you see in mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 08:33, William Oliver wrote: > > So... I run a small mailinglist using mailman3 that has been workiing > great for a couple of months. Last week, all my users from gmail got > kicked off because gmail decided that the list messages were > "unsolicited email". I didn't find out about it until the users hit > their mailman3 bounce limit. I *thought* would be seeing all the > bounce messages, but apparently not. I didn't see any config settings > for "see all the bounce messages" so i thought to myself, "Self, well > maybe that's because my mailinglist username doesn't have a mailbox in > /home/listname". Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, you will see settings like `Notify owner on bounce increment`, ` Notify owner on disable` and `Notify owner on removal` under `Bounce Processing`. Presumable you did get the notification of removal, so delivery to the owner works. Are the increment and disable (or maybe just disable if your versions are older) notices set to Yes? > So, I decided to try that. I created /home/listname/Maildir/* and > logged in as fplist to see if it would put mail there. In order to log > in as listname, I gave the user listname a password. Can't you just reverse those steps. I.e. remove /home/listname/ and remove the listname user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: How to promote non-members to members?

by Mark Sapiro

On 3/17/22 10:19, Quanah Gibson-Mount wrote: > > So then I ran your code to confirm it, and it blows up with an error: ``` >>>> for token, data in pendings.find(pend_type='subscription'): > ... if data['token_owner'] != 'subscriber': > ... continue > ... if data['email'] != 'xxxxxxxx(a)xxxxx.org': > ... continue > ... sub_mgr.confirm(token) > ... > Traceback (most recent call last): > File "<console>", line 6, in <module> > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 545, in confirm > workflow.restore() > File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line > 149, in restore > setattr(self, attr, data[attr]) > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 119, in address_key > assert self.address is not None > AssertionError ``` This says that there is no Address object with the email xxxxxxxx(a)xxxxx.org What do you get in `mailman shell` for ``` >>> um = getUtility(IUserManager) >>> um.get_address('xxxxxxxx(a)xxxxx.org') >>> um.get_user('xxxxxxxx(a)xxxxx.org') ``` These should return an Address and a User respectively. If they don't, did you perhaps run some process to delete the user? If the user is gone, you should be able to replace ``` ... sub_mgr.confirm(token) ``` in the above with ``` ... wfm = getUtility(IWorkflowStateManager) ... pendings.confirm(token, expunge=True) ... wfm.discard(token) ``` to clear the pending subscription and workflow and then be able to mass subscribe the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 1:37 AM, "Jörg M. Schulz" wrote: > > Normal, non-digest messages are sent correctly. Administrative messages as well. > > Using GNU Mailman 3.2.0 (La Villa Strangiato) > > Where could I look for errors / stuck queues? > > /var/lib/mailman3/lists > /var/lib/mailman3/lists/mailman.unswolke.de > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.3.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.2.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.2.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.6.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.4.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.1.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.1.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.3.mmdf When a digest is to be sent by 'mailman digests', the digest.mmdf file is renamed to digest.x.y.mmdf (x and y are the volume and issue numbers) and an entry placed in queue/digests to send that digest. The digest runner then picks up that entry, prepares the digest, queues it in queue/virgin to be sent to the recipients if any and removes the digest.x.y.mmdf file. Since the digest.x.y.mmdf files are not removed, either the digest runner is not running at all in which case there will still be entries in queue/digests or it is encountering an error in processing in which case there should be messages with tracebacks in Mailman's error log and probably messages in queue/shunt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 10:02 AM, brian(a)emwd.com wrote: > I followed Kelly's guide and ran into some issues but were able to resolve most of them. It seems I have one out standing issue: Hyperkitty. When I post to a list, I am getting the following in the /var/log/mailman3/mailman.log: > > Apr 11 14:01:15 2019 (1334) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF/$ > <html><head> > <title>503 Service Unavailable</title> > </head><body> > <h1>Service Unavailable</h1> > <p>The server is temporarily unable to service your > request due to maintenance downtime or capacity > problems. Please try again later.</p> > <hr> > <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> > </body></html> > (503) ... > Everything else works fine. Postfix is receiving and delivery mail to Mailman3. List members are receiving the posts. I can access the list on Hyperkitty just no archived messages. What URL do you use to access HyperKitty. The problem URL above, http://localhost/mailman3/hyperkitty/api/mailman/archive is based on the base_url setting in mailman-hyperkitty.cfg which in your case is http://localhost/mailman3/hyperkitty/, byt the web server listening on localhost:80 is returning the Service Unavailable. It probably doesn't like the IP or name 'localhost'. Set base_url in mailman-hyperkitty.cfg to use an acceptable host name instead of localhost or adjust your apache config to accept localhost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/11/22 09:37, Stanisław Findeisen via Mailman-users wrote: > Dear Experts > > What is the best way to go about reconciling GNU Mailman3-made message modifications (like message footers or subject prefixes) with sender-made DKIM signatures? I am aware of the "DMARC mitigations" tab in the list settings, not bad, but it looks that "replace From: with list address" doesn't help (of course), whereas wrapping the message in an outer message often looks ugly. Is there a better way?... > > BTW I would like to point out that broken DKIM signature can be a problem even with an easy DMARC policy; for example ProtonMail will display this flashy red warning: https://protonmail.com/support/knowledge-base/email-has-failed-its-domains-… in its webmail. (I guess nothing can be done about it except "DMARC Mitigate unconditionally"). ProtonMail is broken - see https://www.rfc-editor.org/rfc/rfc6376.html#section-6.1 That said, BCP recommends removing the signatures that the MLM will break https://www.rfc-editor.org/rfc/rfc6377.html#section-5.7 Mailman implements this with the mailman.cfg setting ``` [mta] remove_dkim_headers: yes ``` Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your valid DKIM signature and no prior Authentication-Results:. ARC <https://www.rfc-editor.org/rfc/rfc8617.html> is intended to address this while preserving prior authentication results and is supported by Mailman, but is not accepted by all receivers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 5/7/19 1:54 AM, Henrik Rasmussen wrote: > Do I have to make a commit or something? Even m.accept_these_nonmembers.remove removes the member from the list, it is right back when I return to the Mailman shell: > >> bash-4.3# mailman shell -l [LISTNAME].lists.example.com >> Welcome to the GNU Mailman shell >> The variable 'm' is the [LISTNAME].lists.example.com mailing list >>>>> m.accept_these_nonmembers >> ['listadmin(a)senderdep.example.com'] >>>>> m.accept_these_nonmembers.remove('listadmin(a)senderdep.example.com') >>>>> m.accept_these_nonmembers >> [] >> quit() There are potentially two issues here. First, the entire interaction is in the context of a database transaction and quit() exits without committing the transaction. abort() will also abandon the changes but not exit. commit() will commit the changes and not exit, and control-D will implicitly commit and exit. Thus, you need to exit with control-D or commit() before quit(). However, there is another potential issue and that is the one described at <https://stackoverflow.com/questions/37310770/sqlalchemy-committing-pickle-t…>. What this says is the way the *_these_nonmembers attributes are defined in the SQLAlchemy data model results in changes due to mutating the list (which .remove() does) aren't recognized. See <https://gitlab.com/mailman/mailman/merge_requests/505>. I think in your case, if you just do m.accept_these_nonmembers = [] commit() and then look at m.accept_these_nonmembers again which will show you what's in the database, you'll see that you have what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

by Mark Sapiro

On 12/4/19 6:15 AM, actionmystique(a)gmail.com wrote: > Ubuntu 20.04 > mailman3 3.2.2-1 > python3-django-hyperkitty 1.3.0-1ubuntu1 > > According to [Hyperkitty Asynchronous tasks paragraph](https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks), we can start a qcluster systemd service file: ... > [Service] > ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings > User=<user> > Group=<group> > Restart=always Did you replace <django_project_path>, <user> and <group> with appropriate values? ... > Starting it works fine: ... > However, the service fails after a few seconds: > ``` > # systemctl status qcluster > ● qcluster.service - HyperKitty async tasks runner > Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Wed 2019-12-04 15:09:48 CET; 1min 1s ago > Process: 1055961 ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings (code=exited, status=1/FAILURE) > Main PID: 1055961 (code=exited, status=1/FAILURE) It appears you haven't replaced <django_project_path> with the actual path to the directory containing your Django settings.py file Also, <user> and <group> should be those of the Mailman user, probably 'list' in Debian/Ubuntu packages. ... > Also, another doc paragraph [Running the task queue (required)](http://docs.mailman3.org/en/latest/config-web.html#running-the-t…) talks about another required command "python manage.py qcluster"; so which one is it? They should be the same thing. Usually manage.py is just configured to run the django-admin command for the particular project. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/19/20 4:09 AM, Alan So wrote: > It is exactly the file I used to test (listname and list server munged). I can send you the full header personally if you want. I did a similar test. I used this message exactly ``` From: mark(a)msapiro.net To: list(a)example.com CC: "ABC DEF (XYZ)" <ktso(a)cuhk.edu.hk> Subject: testing please ignore Message-ID: <sfhifdgdfdsjHHIHIo987sd(a)98vD9FVhdv.8shy65FGvsd> Hello ``` and I posted it to the list via `mailman inject`, and the message I received back from the list with some headers removed was: ``` From: mark(a)msapiro.net To: list(a)example.com Message-ID: <sfhifdgdfdsjHHIHIo987sd(a)98vD9FVhdv.8shy65FGvsd> Message-ID-Hash: NUQVMF52CDRIRH4RXEM2VV7MU3HYXASG X-Message-ID-Hash: NUQVMF52CDRIRH4RXEM2VV7MU3HYXASG Date: Tue, 19 May 2020 17:24:34 -0700 CC: "ABC DEF (XYZ)" <ktso(a)cuhk.edu.hk> X-Mailman-Version: 3.3.2b1 Precedence: list Subject: [List] testing please ignore List-Id: <list.example.com> Archived-At: <https://msapiro.net/archives/list/list@example.com/message/NUQVMF52CDRIRH4R…> List-Archive: <https://msapiro.net/archives/list/list@example.com/> List-Help: <mailto:list-request@example.com?subject=help> List-Post: <mailto:list@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello _______________________________________________ List mailing list -- list(a)example.com To unsubscribe send an email to list-leave(a)example.com ``` Note that the Folded CC: header in the received message is exactly the same as in the original message. Are you looking at the raw message received from the list or some MUA's rendering of it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Problem updating mailman

by Mark Sapiro

On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't remember consciously > installing that because it was never in the guide I followed (which is your > own writeup). > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > + '[' False == False ']' > + mkdir -p /opt/mailman/mm/static > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > --verbosity 0 > + /opt/mailman/mm/bin/django-admin compress > CommandError: An error occurred during rendering > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > */bin/sh: sass: not found* You can't just uninstall rubygem-sass. You have to replace it. Here's one recipe for Ubuntu cd /usr/local/lib # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the # appropriate version. wget https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5… sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz sudo chmod -R o-w dart-sass sudo ln -s dart-sass/sass /usr/local/bin/sass rm dart-sass-1.32.5-linux-x64.tar.gz Then you should see the command sass --version prints 1.32.5 Then, because dart-sass doesn't recognize the short form -t option for --style, you have to edit your settings(_local).py and change COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) to COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass --style compressed {infile} {outfile}'), ('text/x-sass', 'sass --style compressed {infile} {outfile}'), ) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Mark Sapiro

On 4/13/22 10:04, bob B via Mailman-users wrote: > > So to confirm my assumptions/findings: > Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent > Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... Correct. > So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? > > If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? To send digests periodically regardless of size, you need to run `mailman digests --periodic` on the schedule you want. This will send the accumulated digest if any for every list that is configured to Send Digest Periodically. Normally, this is run daily via cron. If you want a different schedule for different lists you need to run `mailman digests --list list(a)example.com --periodic` per list on its own schedule. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: possible backscatter attack using Mailman3 servers

by Mark Sapiro

On 1/3/25 16:18, David Newman wrote: > Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing > about 20-30 entries per day in the Postfix queue where it appears a > Gmail user signs up for a mailing list that requires confirmation, and > Gmail responds that the user is too busy to handle requests. > > There are no publicly advertised email lists on this server, and I don't > ever see anything in the Mailman logs indicating the user ever tried > signing up. This is an attack mail bombing the user. The requests that result in the can come via web or email. Mailman's logging of subscribes has been missing most events through Mailman 3.3.10. See https://gitlab.com/mailman/mailman/-/issues/1143 which will be fixed in 3.3.11, but subscribes waiting user confirmation still won't be logged. However, the message with subject "Please Confirm Your Email Address" comes from Django allauth so it isn't actually Mailman sending it but rather Django allauth as a result of a request to sign up for a Django account at https://mail.example3.com/accounts/signup/. You can probably find that request in your web server logs, and you may find the user and/or email in the Django admin UI. Since django-mailman3 1.3.6, you can disable these signups by putting ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in your Django settings, but then your users won't be able to sign up for web accounts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 10/02/2017 05:25 AM, Henrik Rasmussen wrote: >> The bottom line is at this point, <https://bugs.python.org/issue27321> >> no longer affects Postorius, but it still affects message delivery. I >> have opened <https://gitlab.com/mailman/mailman/issues/406> about >> defending against that and also the UnicodeEncodeError you included in >> your OP. > > Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? There is no user or list admin workaround, but the defense is a fairly simple patch. See the MR at <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit at <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. The commit changes 7 files, but only two are needed. The rests are tests or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't necessary. The only changes you need are those to mailman/email/message.py and mailman/mta/connection.py. >> No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command >> is 'bin/show_qfiles'. > > I much be in the wrong place because when I do a 'docker exec -it mailman-core bash' and do a 'mailman --help' I don't see a 'queue' argument. The only bin/mailman I have inside the mailman-core container is /usr/local/bin/mailman, which is the same command. My bad. The name is 'qfile', not 'queue'. Sorry about that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 10 months

[MM3-users] Re: Archive import fails: "IndexError: list index out of range"

by Mark Sapiro

On 1/7/23 23:04, Stephen J. Turnbull wrote: > Johannes Rohr writes: > > > IndexError: list index out of range > > That isn't the problem, it's the earlier failure, I think: > > > File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, > > in get_msg_id > > token, value = get_dot_atom_text(value) > > File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, > > in get_dot_atom_text > > raise errors.HeaderParseError("expected atom at a start of " > > email.errors.HeaderParseError: expected atom at a start of dot-atom-text > > but found '@localhost>' > > It appears that HyperKitty is trying to find a domain name (the common > use for "dot_atom_text" in mail headers in a Message-ID), but is > finding "@localhost>" instead. Actually, this occurs after the message has been converted to an email.message with policy=policy.default. Getting the Message-ID attempts to parse it and in this case, the dot_atom_text it's looking for is the 'local part' which doesn't exist. I.e. <xxx@localhost> would be OK, but <@localhost> is not. > First I would try the check_hk_import script which is provided with > HyperKitty. HyperKitty's contrib/check_hk_import script didn't find this issue. The GitLab branch was updated yesterday, but that update is not yet released. An up to date script which does find this issue is at <https://www.msapiro.net/scripts/check_hk_import>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 7/5/22 12:32 PM, Kimmo L wrote: > Hello! > My plan is to install fresh Mailman3 host, which means that i need to migrate/transfer my existing mailman mailing lists + hyperkitty archives to new host. > Unfortunately i didnt find any good documentation about this. > I tried myself to export and import mailmanweb/mailman databases (from old PostgreSQL to new PostgreSQL) and recreate indexes(mailman-web update_index). Now i can see and search hyperkitty archives, but if try to open one of the mailing list, i get error - HTTP Error 500: {"title": "500 Internal Server Error"} > So im pretty sure, that I'm gonna have to transport some more stuff over, which I have no idea. Maybe existing users and user rights. Dumping the databases from the old serverr and loading them on the new server should work. There should be an exception and traceback logged in Mailman core's mailman.log or possibly in the Django (mailmanweb) log. What is logged? > If its not a big trouble, can someone kindly share, what exactly should i need to export/import and what would be the right steps/commands/moves. I thing just dumping and loading the databases and copying mailman.cfg and the Django settings should do it. Are the domains the same on the new server? If not there may be issues with that. I'd need to see the exception and traceback to say more. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Postfix problem with imported Mailman2 list

by Mark Sapiro

On 3/2/23 13:16, mailman3(a)outofoptions.net wrote: > I installed and tested Mailman3. I imported a Mailman2 list. All looks good but I get this error. > > Recipient address rejected: User unknown in virtual alias table; from=<hit(a)options.org> to=<atm(a)alist.net> > > The aliases seem to show up find in the GUI for the control panel software I use. Postfix virual file has a mapping of atm to atm(a)alist.net . > > It seems mailman at least sees the connection. From the smtp.log under mailman: Presumably there are LHLO, MAIL FROM, and RCPT TO entries before these next ones. > `Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) recip: atm(a)alist.net > Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) Data: b'DATA' > Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) Data: b'QUIT' > Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) connection lost > Mar 02 10:14:13 2023 (1242405) Connection lost during _handle_client() The connection lost entries are normal in the log. This all looks like Mailman's receiving of the message via LMTP from Postfix. This is inconsistent with Postfix reporting Recipient address rejected: User unknown in virtual alias table which would have occurred before any attempt to relay the message via LMTP. In order to understand more about this, I'd need to see at least the output from `postconf -n`. I'm just guessing here, but https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… may be applicable in your case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: urls.py location on venv install

by Mark Sapiro

On 8/9/26 09:08, Torsten wrote: > > In fact, my settings.py does contain these import lines: > > import os This should not be needed unless something further down references os. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > > BASE_DIR = ('/var/lib/mailman3/web') > > SECRET_KEY = '<MYSECRETKEY>' > DEBUG = False > > #: Default list of admins who receive the emails from error logging. > ADMINS = ( ('Mailman Suite Admin', 'torsten(a)bbadmin.de'),) > > ALLOWED_HOSTS = ['localhost', '127.0.0.1',] You may also want your public facing web domain here. > INSTALLED_APPS = [ > 'django_mailman3', > 'postorius', > 'hyperkitty', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', I'm hoping there's more to this file, but in any case unless you're adding or deleting something from the definition in mailman-web/settings/base.py, this is redundant and if you are adding, it's better to do ``` INSTALLED_APPS.append('app.to.add') ``` or to remove something, for example ``` del INSTALLED_APPS[INSTALLED_APPS.index(django.contrib.admin')] ``` > And I have the mailman_web/urls.py in the venv where mailman was installed. If you are using gunicorn as your wsgi server, I think there is an issue in the documentation. <https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-guni…> says etc/mailman3/gunicorn.conf should contain `chdir = "/opt/mailman/mm"`. I think this is wrong. It should be `chdir = "/etc/mailman3"`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 days, 21 hours

[MM3-users] Re: Hyperkitty Replies showing up as new posts

by Mark Sapiro

On 3/5/25 8:55 PM, Arte Chambers via Mailman-users wrote: > Hello, my Hyperkitty is creating a new post for each reply in a thread. I > would expect that new posts to a list would show up in the archive and once > you click on that thread you would see all replies. However in my > Hyperkitty each reply to a thread shows up as its own post usually with the > subject line saying RE: Original Message. How can I set up Hyperkitty to > behave more like the lists.mailman3.org archives where replies to topics > are filed under their respective threads? HyperKitty's threading is based solely on In-Reply-To: headers. It does not attempt to thread based on References: or Subject: matching. Usually this works, but it can fail if for example A posts to a list. B replies off list to A and A replies on list to B's off list reply. In this case, the In-Reply-To: of A's reply is the Message-ID: of B's reply which isn't on the archive, so A's reply starts a new thread, but this is unusual, and HyperKitty has a "Reattach this thread" feature that a list owner or superuser can use to attach one thread to another. However, if this non-threading occurs regularly, It may be that the replyer's MUA is not setting In-Reply-To:. I've seen some phone clients do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin

by Mark Sapiro

On 8/8/19 10:14 PM, Stephen J. Turnbull wrote: > maztec(a)gmail.com writes: > > > Issue: Postfix LMTP does not pass messages onto MM3:LMTP. > > I don't understand why this is a Mailman problem. Seems like Postfix > user lists would be a better venue to get expert help with this. > Among other things, our most responsive Postfix guy is out of cell > coverage for now. I have a window of availability - and it's longer than I thought because my second of three back-country trips has been canceled :( > I would post this To: the relevant Postfix list, Cc: this list, and > set Reply-To and Mail-Followups-To to the Postfix list to get > everybody who can contribute on the same page. I don't have much to add to what Steve has said except our recommended config includes transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp in Postfix main.cf. This should contain (per your log message) things like ListName-confirm(a)ListServer.TLD lmtp:[127.0.0.1]:8024 to tell Postfix to deliver that address via lmtp to port 8024 on the local host. Dovecot should not be involved. There is something in your config that trumps this and delivers via lmtp to Dovecot for mailman3:[127.0.0.1]:8024. Does your transport_maps look like the above or perhaps like ListName-confirm(a)ListServer.TLD mailman3:[127.0.0.1]:8024 If so, I don't know where mailman3 instead of lmtp: comes from. Also, even if it is lmtp: I don't know that Dovecot can deliver via lmtp. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: starting gunicorn per mailman.log yet gunicorn not installed

by Mark Sapiro

On 6/26/23 1:15 AM, Odhiambo Washington wrote: > On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Yes, it makes sense. Mailman 3 core is basically an application which >> manages a webserver that provides the REST API, a database of domains, >> users, and lists, an LMTP server for incoming posts and an SMTP client >> for outgoing distribution. Mailman uses gunicorn to provide the >> webserver. >> >> Installation of gunicorn is handled as a package dependency, so you >> probably wouldn't notice unless you were watching the installation >> process very carefully. >> > > It doesn't make sense, IMHO, because as the OP says, > 1. his ExecStart is: > ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and > not* > ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf > mailman_web.wsgi:application. > > 2. He has not knowingly created any gunicorn.conf > > Why would Gunicorn be Exec-ing itself? :-) As Steve says, Mailman core uses Gunicorn to manage it's REST API. This has nothing to do with whatever WSGI server (uWSGI, Gunicorn, Apache mod_wsgi, ...) is used to support the Django applications (django-mailman3, hyperkitty and postorius). I.e., there is always a Gunicorn instance configured and started by Mailman core, regardless of whatever WSGI server supports Django or even if one isn't running Django at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/27/25 18:54, Mark wrote: > > However when I update the template, the databases are updated correctly > but the Welcome message is still sent with the old template content. > > mailman.templates > mailmanweb.postorius_emailtemplate > > Additionally, if I delete the template and create a new one the old > content still gets sent. > > I cannot find where this content is written or is being cached. The content is stored in the mailmanweb.postorius_emailtemplate table. As far as Mailman core and Postorius are concerned, that's the only place. I'm guessing, but my guess is it's cached in your wsgi server. I.e., upon initial creation an entry is made in the mailman.template table with a uri like https://example.com/mailman3/api/templates/list/list.example.com/list:user:… and when Mailman core wants the template, it gets that uri which I'm guessing is then cached in the wsgi server. Then, if the content is changed, the GET returns the old cached value instead of getting the new value from Postorius. If the template is deleted, the mailman.template table entry is deleted and at that point Mailman core will get the template from the file system following it's normal search rules, but if the template is recreated in Postorius, a new table entry is made with the same uri which may still get a cached template from the wsgi server. If this is correct, restarting mailman-web or whatever controls the wsgi server should fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Hyperkitty import from mailman2

by Mark Sapiro

> > Now I wanted to try import from mailman2 mbox, so i did: > > python2 manage.py hyperkitty_import --settings settings --ignore-mtime > -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > > It shows that it have sucessfully imported all emails and I can see them > from database (sqlite3), but I cannot see them from GUI (hyperkitty). > Only thing I can see is this inactive "test" list. > > I have tried that I create list before importing, still same result. I have done this several times for several different lists and it has always worked with no problems. I have always created the list first. I do not use any of the options other than -l. My settings location is built in to the django admin script I run. So what I run is equivalent to python2 manage.py hyperkitty_import --settings .. -l .. mbox Do you have cron set up to run the periodic django tasks as in @hourly python2 manage.py runjobs --settings settings hourly @daily python2 manage.py runjobs --settings settings daily @weekly python2 manage.py runjobs --settings settings weekly @monthly python2 manage.py runjobs --settings settings monthly @yearly python2 manage.py runjobs --settings settings yearly 0,15,30,45 * * * * python2 manage.py runjobs --settings settings quarter_hourly * * * * * python2 manage.py runjobs --settings settings minutely If not, did you run python2 manage.py update_index --settings settings after the hyperkitty_import? I'm actually not sure any of this will help since it should only affect the search index, not the message display. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/18/20 3:33 PM, Mark Dadgar wrote: > > Any thoughts on how to salvage ~20 years of list archives? The archives shouldn't be an issue. I don't think they are involved in the corruption, but anyway, hopefully you still have the archive mbox you imported. Then for the messages since then, you should be able to get a mbox from hyperkitty with something like https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… with the obvious substitutions and appropriate start and end dates. The list is trickier. If you are going to start over with a clean install, and if you have a config.pck that you imported from MM 2.1, I suggest the following: Use the `mailman members` command to get a list of all members. Then depending on how much work you want to do, also get separate lists of plaintext and mime digest members and members with delivery disabled. Then on the new install, import the config.pck with `mailman import21` and import the archive mboxes with hyperkitty_import. Run `mailman members --sync` with the full current membership list, and record the [ADD]s. Then you can match the [ADD]s against the plain and mime digest members and those with delivery disabled and set their options. That's a lot to do, but it should get you close. On the other hand, if you can wait, we might be able to figure out how to fix this, and it's even possible the underlying issue isn't database corruption. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Moderator Approval Subscription template

by Mark Sapiro

On 2/8/21 5:55 PM, Brian Carpenter wrote: > Hey all, > > I am seeing a strange issue with the Moderator Approval Subscription > template. > > 1. First problem is that this template by default does not include a URL > to the list admin page of said mailing list. Mailman 2's notifications did. Mailman 2 was monolithic. Mailman 3 is Modular. Core, which sends this notice, doesn't know if you even have a web admin UI, much less how to access it. It has been suggested that we add a config setting for the web base URL and if that is set, include URLs in these messages and we may eventually do that, but in the mean time > 2. Problem 1 can be solved by editing the template and adding the List > Owner (admin) url to moderate the subscription. This is what you need to do. > However in the case of > long URLs, the URL is getting cut-off in Thunderbird. Not sure about > other email clients. That is an issue because the expanded template is filled and wrapped at column 70 with mailman.utilities.string.wrap(). However, you can avoid wrapping the URL by preceding it in the template with a space. Something like > Your authorization is required for a mailing list subscription request > approval: > > For: $member > List: $listname > > Visit > > https://list.redeacted.org/admin/list/oligodendroglioma.list.redacted.org > > to act on this request. Lines beginning with spaces aren't wrapped. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/17/22 15:15, Élodie BOSSIER via Mailman-users wrote: > Hello, > > My mailman3 installation is now functional, but the config "FILTER_VHOST > = True" doesn't work fine when I define "alias_domain" for the 2 > domains. I need to define that because I need to get "postfix_vmap" file. > > As you can see, list from others domains are visible on this URL : > https://ml.franceserv.fr/postorius/lists/ > > I would like https://ml.franceserv.fr/postorius/lists/ and > https://ml.viticreation.fr/postorius/lists/ with their own lists. There are issues with FILTER_VHOST due to the fact that mailing lists do not have a web host attribute. This means when you go to HyperKitty or Postorius when FILTER_VHOST is True, we look up the domain record for the web host you are visiting and show you all the lists whose mail host matches the mail host for the web host domain. This has nothing to do with alias domains. What that means is if all your domains records have a unique mail host, FILTER_VHOST will work as you expect, but if multiple domains have the same mail host FILTER_VHOST will show you the lists for the current web host plus all those with a matching mail host. I.e. if in your case, the ml.franceserv.fr domain and the ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't separate them. If they have different mail hosts FILTER_VHOST will separate them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 10/4/23 05:09, paulrubin37(a)gmail.com wrote: > Ok first I tried the force reinstall, that changed nothing. > > (venv) mailman@mail:~> pip install --force-reinstall psycopg2-binary\<2.9 > Collecting psycopg2-binary<2.9 > Using cached psycopg2_binary-2.8.6-cp311-cp311-linux_x86_64.whl You are forcing the version to be <2.9 which is why your venvs have 2.8.6. Note you are installing a cached version. That may be why it's broken. You could try ``` pip install --no-cache-dir --force-reinstall psycopg2-binary\<2.9 ``` or as I note below, if your Django is >=3.1 ``` pip install --no-cache-dir -U psycopg2-binary ``` ... > Here is what is in the file that is failing, If I read this right I need to check every single sub import. > > 50 > 51 from psycopg2._psycopg import ( # noqa > 52 BINARY, NUMBER, STRING, DATETIME, ROWID, > 53 > 54 Binary, Date, Time, Timestamp, > 55 DateFromTicks, TimeFromTicks, TimestampFromTicks, > 56 > 57 Error, Warning, DataError, DatabaseError, ProgrammingError, IntegrityError, > 58 InterfaceError, InternalError, NotSupportedError, OperationalError, > 59 > 60 _connect, apilevel, threadsafety, paramstyle, > 61 __version__, __libpq_version__, > 62 ) > 63 This is way too much detail. This psycopg2-binary is broken. You can't successfully import psycopg2 from it. You need to get a working psycopg2 installed rather than trying to fix your broken one. What is your Django version? The only reason for pinning psycopg2-binary<2.9 is for Django<3.1. See https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…. If your Django is >=3.1 try in your venv ``` pip install -U psycopg2-binary ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 12:58 PM, Simon Coggins wrote: > > Please file an issue for this at > https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a > better solution. Your approach of munging Message-IDs will create other > issues. Consider a post to a list with direct CC to userx. userx > replies-all to the message received directly. the In-Reply-To of this > reply is the unmunged Message-ID which will affect threading in the > archives and other recipient's MUAs. I realize this is preferable to > losing the message, but I hope we can do better. > > > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Getting connection timed out

by Mark Sapiro

On 5/22/21 11:29 AM, blackout69 wrote: > Hello everybody, > > for a couple of days I have been seeing several lines calling these on > /var/log/mail.log > > May 22 18:22:57 glugct postfix/qmgr[21205]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:06 glugct postfix/qmgr[27175]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:36 glugct postfix/smtp[27177]: 0ACE641C1B: > to=<myaddress(a)simail.it>, relay=none, delay=55152, > delays=55122/0.07/30/0, dsn=4.4.1, status=deferred (connect to > mail.simail.it[217.27.113.30]:25: Connection timed out) ... > But always on a single email address.What could it depend on?Probable > that the mail.simail.it server is blacklisted? It's probably not blacklisting. It's not getting that far. Your `glugct` is attempting to connect to port 25 at mail.simail.it and the connect is not being answered. Normal blacklisting will not occur until after the remote MTA answers the connect and determines the IP of the caller. And in any case, if it is some kind of blacklisting it is your `glugct` server that is blacklisted by mail.simail.it. I just did the following ``` $ telnet mail.simail.it 25 Trying 217.27.113.30... Connected to mail.simail.it. Escape character is '^]'. 220 mail.simail.it ESMTP ready. quit 221 mail.simail.it closing connection Connection closed by foreign host. ``` so it did answer my connect. In any case, this is not a Mailman issue. It is between Postfix on your server and the remote server at mail.simail.it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface

by Mark Sapiro

On 9/30/23 10:53, Wikinaut wrote: > I use mailman3 since a while, for some of my lists I have been using > > - list:member:digest:footer.txt > - list:member:regular:footer.txt > > When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! Postorius templates are handled differently from file system templates. When you set a template in Postorius, that template becomes available in Postorius' API and an entry for the template in the template table in the database is created with a URI pointing to the template in Postorius' API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for info about template URIs. The fact that Postorius doesn't show the file system template as the initial value when creating a template in Postorius is https://gitlab.com/mailman/postorius/-/issues/366 > When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. They are not created as files - see above. The fact that they aren't working is probably because your Django setting for POSTORIUS_TEMPLATE_BASE_URL is not correct. This should be set to the scheme and host part of the URL you use to access Postorius, e.g., https://lists.mailman3.org for this list's installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Single-Sign-out for List member

by Mark Sapiro

On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > It does not seam to be possible, to put this into effect with mailman 3. > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. You can set the list's unsubscription_policy to open and set the link as a mailto: to the list-leave address, but that still requires a second click to send the mail. The solution is to create a web based CGI script which is called with a URL like <https://example.com/unsub_script/list.example.com/user@example.net> and have that script invoke the appropriate `mailman` command to remove the member from the list. Beginning with Mailman 3.3.2, this would be mailman delmembers -l list.example.com -m user(a)example.net -g to remove the member and send a goodbye message. In older Mailman, it would be something like echo user(a)example.net | mailman members -x - list.example.com I understand you may have a legal requirement do do this, but these "one-click - no user confirmation" links are a bad idea because usera will reply to a list post or forward it and not remove the link and userb will receive usera's reply and click usera's unsubscribe link either maliciously or thinking it will unsubscribe userb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: New releases

by Abhilash Raj

On Thu, Jun 25, 2020, at 8:59 AM, Danil Smirnov wrote: > The issue has confirmed by other users: > > https://github.com/maxking/docker-mailman/issues/382 The issue seems to happen because the static files that are present at the default staticfile locations aren't valid anymore and aren't removed automatically on upgrades. You can run: sudo rm -rf /opt/mailman/web/static To remove them manually and then it should be re-created properly on the next start. I'll try to work on a fix for this in some automated fashion. > > вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > > > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > >>> COMPRESS_OFFLINE = True > > >>> COMPRESS_ENABLED = True > > >> > > > > > > These two are commented out. > > > > > > Then compress shouldn't be trying to do anything. I can't explain what's > > going on. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/30/20 11:24 AM, Odhiambo Washington wrote: > This works - I mean changes the error message to > > [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] > /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) I'm not sure why you are getting this warning, and it's non-fatal, but you can get rid of it by pip install cmarkgfm in your virtualenv. > [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client > 197.232.81.246:63962] AH01630: client denied by server configuration: > /var/spool/mailman-web, referer: > http://mm3-lists.my.server/mm3/mailman3/lists/ > > There is NO /var/spool/mailman-web anywhere. It has not been created. > You mentioned that it should be created automatically, IIRC. No. I think I told you that the references to /var/spool/mailman-web/static in your Apache config should be changed to /opt/mailman/mm/static and that directory would be created/populated by mailman-post-update. I think you still have Alias /static "/var/spool/mailman-web/static" in your Apache config and it needs to be Alias /static "/opt/mailman/mm/static" That may be my fault as when I recently edited <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>, I missed that line. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. ``` Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is ``` Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Remove old bounces in bouncedir

by Mark Sapiro

On 3/10/22 00:31, Stephan Krinetzki wrote: > Mark Sapiro wrote: > >> If you are referring to messages in Mailman's bounces queue, if these >> are not processed and removed within 15 minutes of arrival, Mailman's >> bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > ``` > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > ``` > > The process it self is there > > ``` > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > ``` I don't understand what's happening. If the bounces runner is processing it's queue, those .pck files should be processed and deleted. Are there errors in /opt/mailman/var/logs/mailman? If you examine (some of) those files with `mailman qfile` do you see anything strange? Is there an ownership/permissions issue? Sometimes people run Mailman or some Mailman command as `root` and things get owned by root and then when Mailman is later run as `mailman` it can't delete or maybe even read them. >> If you are referring to bounce messages in the message store >> (var/messages/), there have been issues with those not being removed, >> but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. Is the size of the /opt/mailman/var/messages directory very big? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Mark Sapiro

On 3/18/19 2:19 PM, Ralph Seichter wrote: > Hello list. > > I have read [1] and [2], but I am not quite sure what the recommended > method is to completely disable message headers/footers and subject > modifications for *all* lists tied to a specific domain. Being new to > Mailman 3, I was actually surprised that there are no configuration > switches in the Web UI's settings for mailing lists that allow me to get > rid of unwanted message decorations. It's still a work in progress. You can do it via list settings except for one issue [1]. See that issue and also the post referenced in it's description [2]. To not modify the Subject for a list, on the list's Settings -> List Identity tab, set 'Subject prefix' empty. To not add headers and or footers, you need empty templates for them. These could be created via the list's Templates form except until [1] is fixed, you can't make empty templates. You can use the method in [2] to create empty var/templates/domains/DOMAIN.NAME/LC/list:member:generic:footer.txt and var/templates/domains/DOMAIN.NAME/LC/list:member:generic:header.txt files for the domain and language. Then as long as no list specific templates are created for lists in that domain, no headers or footers will be added. [1] <https://gitlab.com/mailman/postorius/issues/331> [2] <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/22/20 12:20 AM, r.woithe(a)callassoftware.com wrote: > Hello, > this is the complete email we get every night: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs > job().execute() > File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 36, in execute > sync_with_mailman() > File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 146, in sync_with_mailman > sender.set_mailman_id() > File "/usr/lib/python3/dist-packages/hyperkitty/models/sender.py", line 55, in set_mailman_id > mm_user = client.get_user(self.address) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 320, in get_user > response, content = self._connection.call( > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1948, in request > (response, content) = self._request( > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1621, in _request > (response, content) = self._conn_request( > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1560, in _conn_request > response = conn.getresponse() > File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse > raise ResponseNotReady(self.__state) > http.client.ResponseNotReady: Request-started > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > START TRACEBACK: > END TRACEBACK OK. So python2.7 in the Subject: is not relevant. The issue is probably a timeout in mailmanclient's REST request. See <https://wiki.list.org/x/17892072> for info on how to increase it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: hyperkitty_import Unicode Errors - Drop all Archives and Start Over?

by Mark Sapiro

On 5/16/23 08:49, Dave Hall via Mailman-users wrote: > > What I would really like to do is to drop all of the previous archives and > start fresh. Looking at the table list for the database, It would appear > that all of the archive content is stored in the tables with names that > start with 'hyperkitty_' I'm wondering if I could just wipe the content of > these tables, or exclude them from a backup, and then start fresh. It is correct that all the HyperKitty tables start with `hyperkitty_`. I *think* it would be safe to just drop the content of these tables, but I won't guarantee that there aren't `django_mailman3_` tables with foreign keys into the hyperkitty tables. As a superuser logged in to hyperkitty, you should see a Delete Archive button at the top level overview for a list. It would be safer to delete the archives that way. > Alternatively, if I restore the exiting archives to the new database with > the correct unicode settings, could I re-run the hyperkitty-import tool and > get it to pick up all of the messages it skipped due to the unicode problem? This will work too. You will need to specify the --since option to hyperkitty_import because the default for `since` is the date of the newest message in the archive. The import will not reimport a message whose Message-ID: is already in the archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: mailman break DKIM signature by modifying body

by Mark Sapiro

On 6/5/23 07:06, Peter Münster wrote: > Hi, > > I'm using mailman 3.3.8. > > Some messages with attachments from Google users get rejected by spam > filters because of invalid DKIM signatures. > > It seems, that mailman alters some lines in the body. Here an example: > > Original message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2031 > > --000000000000f846c505fc494b7a-- > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > Altered message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2032 > > --000000000000f846c505fc494b7a-- > > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > An empty line is added, and the spaces after the semicolons are removed. > > Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. > > What could I do please, to prevent such modifications of the body? Changes like those above are due to Python's stdlib email module. Short of actually modifying the email module, there's nothing you can do to prevent them. Instead, you should be DKIM signing your outgoing mail and perhaps applying Mailman's DMARC mitigations if DMARC is an issue. If you are DKIM signing your outgoing mail and mail is being rejected because of prior invalid signatures, you can remove those by adding `remove_dkim_headers: yes` to the [mta] section of mailman.cfg. Also, ARC signing <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…> may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 7/4/20 9:03 AM, tom(a)gather.coop wrote: > > So I hope there is not an expectation that the rDNS domain match the email sender domain. If so I'm toast. Is it just sort of a smell test to see if the server looks legitimate? Probably part of your confusion is the ambiguity of the term `sender` which can refer to any of: - the actual individual sending the original mail (the From: header) - the envelope sender (the listname-bounces@listdomain address in the case of list mail) - the sending server. In the case of FCrDNS we're talking about the server (MTA) delivering the message to the recipient MX. I.e., that server's IP should have a PTR to its name and its name should have a A (or AAAA in the case of IPv6) record with the same IP. That's what FCrDNS implies. Quoting from <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>: "... the requirement is the forward and reverse lookup for the sending relay have to match, it does not have to be related to the from-field or sending domain of messages it relays." It is also good if the name by which the MTA identifies itself (the myhostname setting in Postfix) is the same as the server's name. Quoting from the same article: "Some e-mail mail transfer agents will perform FCrDNS verification on the domain name given on the SMTP HELO and EHLO commands. This can violate RFC 2821 and so e-mail is usually not rejected by default." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Mark Sapiro

On 4/17/19 8:10 AM, Abhilash Raj wrote: > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: >>> >>> Which version of Hyperkitty are you using? >>> >>> Did you upgrade the version of Hyperkitty when you migrated to the >>> new host? >> >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple >> releases), so it's hyperkitty 1.1.4. >> >> I didn't upgrade anything with the move. > > I am not sure where does Debian packaged version store it's fulltext index, but > I am assuming the move somehow makes Hyperkitty not be able to read the > index. I think this is a known incompatibility between the Python 2.7 and Python 3 versions of Whoosh. From the tracebacks, the current HyperKitty is running under Python 2.7. If the prior server was running HyperKitty with Python 3, that would explain this. > Can you try removing and re-building the entire index? I don't know again > the right command for Django there, but the hyperkitty command you want > to run is called `rebuild_index`. For source package, something like: > > $ python manage.py rebuild_index > > Do note that this will take a lot of time if you have a big archive. If this is the incompatibility, rebuilding the index will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: How to remove global ban using API?

by Mark Sapiro

On 5/15/19 9:46 AM, Nathan Dixon wrote: > > I can create the ban fine by the following: > > from mailmanclient import Client > client = Client(URI,apiuser,apipass) > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") This is apparently a typo - missing ')' - in the re as you have it correct below. > However, I cannot seem to be able to remove it using the api: >>>> client.bans[0].delete() ... >>>> client.bans.remove(str(client.bans[0])) ... >>>> > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") All of the above work for me with both API 3.0 and 3.1 in a non-docker install of the current GitLab HEADs > And also, when I now try and go into the mailman-core docker image to use > the mailman.interfaces.bans, it will not let me see the global bans: > >>>> from mailman.interfaces.bans import IBanManager >>>> global_bans = IBanManager(None) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: ('Could not adapt', None, <InterfaceClass > mailman.interfaces.bans.IBanManager>) I don't see this either. > I have opened an issue in Gitlab for this as I feel it may be a bug related > to regex and global bans (there was a similar one for list banned > addresses): https://gitlab.com/mailman/mailman/issues/598 I also commented on the GitLab issue. I think this must be an issue with the docker images. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/18/23 6:24 AM, Helio Loureiro wrote: > Hi, > > Indeed it was the configuration. It was placed into > /etc/mailman3/mailman-web.py. After a I changed to > /etc/mailman3/settings.py a few things advanced a little bit more. > > I had to figure out how to fix mysqlclient installation since there isn't a > mention about it and the simple "pip install mysqclient" was breaking with > pkg-config issues. But it did work at the end. > > Now I can see further messages on mailman3-web than before. > > (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate > System check identified some issues: > > WARNINGS: > account.EmailAddress: (models.W036) MariaDB does not support unique > constraints with conditions. > HINT: A constraint won't be created. Silence this warning if you don't care > about it. > account.EmailAddress: (models.W043) MariaDB does not support indexes on > expressions. > HINT: An index won't be created. Silence this warning if you don't care > about it. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > Applying account.0004_alter_emailaddress_drop_unique_email...Traceback > (most recent call last): I'm not sure why there would be an issue with this migration, but there is a possible compatibility issue depending on how you installed things. django-mailman3<=1.3.11 is not compatible with django-allauth>=0.58. In your venv, try ``` pip install django-allauth\<0.58 ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 8/2/25 01:51, Stephen J. Turnbull wrote: > > IIRC all of the shunted messages that Stephen looked at with qfiles > were those special digest messages (ie, message component empty, > pointer to lists/$LIST/something.mmdf in the msg_data component). So > something is going wrong in the to-digest handler. And for every one of those shunted messages there should be an exception with traceback logged in mailman.log. Those tracebacks should be helpful. > The number of .tmp files lying around bothers me. AFA grep CS, the > only place that can happen is in switchboard.py:136 in .enqueue: > > with open(tmpfile, 'wb') as fp: > fp.write(msgsave) > pickle.dump(data, fp, protocol) > fp.flush() > os.fsync(fp.fileno()) > os.rename(tmpfile, filename) > > where `msgsave` is already a pickled object. So either pickle.dump is > choking on something in data (the metadata, which I believe is all > primitive Python data types), or something (OOM kill?) is happening at > the OS level. A crash in pickle.dump should leave an exception log > and backtrace in the logs. > > AFAIK, Mailman does not clean up .tmp files at startup, right? That is correct. The *.pck.tmp file is created by the above code and immediately after writing is renamed to *.pck. It is done this way to prevent another process picking up a partially written *.pck. If a *.pck.tmp file is somehow left behind, it is never looked at or deleted by any Mailman code. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Mark Sapiro

On 10/28/18 12:03 PM, Guiseppin Thomas wrote: > Hi, > > I imported some mbox archives in Hyperkitty. > > I have lot issues like: > > /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: > ('Non-ascii sender address', <email.message.EmailMessage object at > 0x7f05f1606048>)// > //Non-ascii sender address from "Stéphane blipblop <stlablipblop at > gmail.com>" about [HATLAB][It] Re: A débarrasser ! / > > It's probably because "Stéphane". The 'Non-ascii sender address' message comes from > try: > from_str = header_to_unicode(message['From']) > from_name, from_email = parseaddr(from_str) > from_name = from_name.strip() > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > raise ValueError("Non-ascii sender address", message) Possibly the exception is thrown in parseaddr(), but much more likely, the email address, not the display name contains non-ascii. > Some advise to fix it ? All the other messages should have been imported. If you can find and fix the 'bad' ones in the mbox, you can make a new mbox with just those and import that. You could also import the entire mbox with fixed messages. The already added ones won't be re-imported because of duplicate Message-ID:, but it's extra processing. If the actual bad message From: header is From: Stéphane blipblop <stlablipblop(a)gmail.com> or From: Stéphane blipblop <stlablipblop at gmail.com> That shouldn't cause the error, so I'g guessing that 'blipblop' is not the actual value and the actual value in <stlablipblop at gmail.com> has non-ascii. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Changing Mailman's "from" domain

by Mark Sapiro

On 5/16/19 8:21 AM, Roger Hislop (IS) wrote: > > If I subscribed an address, no confirmation email would come through. Checked the Postfix log and see this: > > May 16 14:34:50 ip-172-31-23-250 postfix/smtp[5025]: 15B87A35FB: to=<iotic-za(a)reasondigital.co.za>, relay=email-smtp.eu-west-1.amazonaws.com[52.51.155.83]:587, delay=0.22, delays=0.01/0.02/0.1/0.1, dsn=5.0.0, status=bounced (host email-smtp.eu-west-1.amazonaws.com[52.51.155.83] said: 554 Message rejected: Email address is not verified. The following identities failed the check in region EU-WEST-1: test-list-request(a)iotcouncil.org.za, test-list-bounces(a)iotcouncil.org.za (in reply to end of DATA command)) > > I've verified the domain listman.iotcouncil.org.za, so it would seem the obvious solution is to change the domain the mails come from. > > It appeared that I just change the postfix config to specify domain list so: Those addresses are the From: address (test-list-request(a)iotcouncil.org.za) and the envelope sender (test-list-bounces(a)iotcouncil.org.za) These are set by Mailman in the message and the SMTP transaction. Postfix doesn't normally rewrite them. The domain in these addresses is 'web host' defined in Mailman's domain record associated with the list which is also the domain in the list's posting address If you want Postfix to rewrite the envelope sender domain, see <http://www.postfix.org/ADDRESS_REWRITING_README.html#generic> > I see that messages TO the mailman server are also not being delivered ("-- 5.1.1 Requested action not taken: mailbox unavailable"). So there's another problem. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/24/22 10:57, sascha.rissel(a)gmail.com wrote: > Hello, > > I have newly set up Mailman 3 on Ubuntu 20.04. > Sending and receiving mails between list members does work, but I am currently experiencing two issues: > 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. > 2) Archiving is activated within list settings, but there isn't any archive created. > > I found this thread, where the first of these issues is also described: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. > I am running Mailman 3.2.2 on Python 3 .8.10. This is only one of the issues with the Debian/Ubuntu packages. > So I need to either upgrade Mailman Core or downgrade Python. > I already did >> apt-get upgrade >> apt-get update > Unfortunately this didn't upgrade Mailman Core's version. > > Which steps do I have to undertake to upgrade Mailman Core? I suggest first removing the Debian/Ubuntu packages and installing the PyPI packages following docs at https://docs.mailman3.org/en/latest/install/virtualenv.html. There are also other takes on this at https://wiki.list.org/x/17891998; https://wiki.list.org/x/17892066 and https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… This will require some effort, but you will be freed from dependence on out of date packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Mailman3 Queues Documentation

by Mark Sapiro

On 2/18/26 12:03, msok--- via Mailman-users wrote: > Hi Everyone, > > I'm looking for a documentation for the explanation about the Queues in Mailman3. > By the way, I'm new, I just got 5 shunt under Queues. The entries in the shunt queue are messages that threw an uncaught exception in processing. The messages and their metadata can be examined with the `mailman qfile` command. For each of these messages there will be entries in mailman.log beginning with one saying Uncaught runner exception: ... followed by a traceback followed by a message saying SHUNTING: file_id where file_id is the name of the file in the shunt queue minus the .pck extension. The exception and traceback will identify the exception and the issue that caused it. If the issue is caused by the message itself and the message is spam, you can just delete the file from the var/queue/shunt/ directory. If the issue is something else like, e.g., a configuration problem or an unreadable template, you can fix the problem and then reprocess the messages with the `mailman unshunt` command. If you need help interpreting the exception and traceback, post the traceback here. Most of the queues (all except bad and shunt) hold messages to be or being processed by the corresponding runner. For an overview of how Mailman works, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/archi…> and <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil…>. For some detail on runners see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 4 weeks

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 12:20 PM, "Jörg M. Schulz" wrote: > when I use the lines below, the templates are looked for in //var. > When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. //var refers to the directory defined in mailman.cfg (or the default in mailman/config/schema.cfg) as [paths.master] var_dir: Exactly which of the following lines did you add and then comment out? Just the three lines > [language.en] > charset: utf-8 > enabled: yes or something more? > mailman.cfg: > > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: help(a)elternserver.de > > # This is the local-part of an email address used in the From field whenever a > # message comes from some entity to which there is no natural reply recipient. > # Mailman will append '@' and the host name of the list involved. This > # address must not bounce and it must not point to a Mailman process. > noreply_address: noreply > > # The default language for this server. > default_language: en > [language.en] > charset: utf-8 > enabled: yes > > [language.de] > description: German > charset: iso-8859-1 > enabled: yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/29/20 5:23 AM, Brian Carpenter wrote: > I have a list owner who had his subscription policy set to confirm. > Apparently that was too hard for his list members to handle so he > changed it to moderate only. If someone sent a subscription request that > needed to be confirm, did not respond to it, and then tried subscribing > again after the member policy changed to moderate, their 2nd > subscription attempt still shows up in the confirmation queue. Is that > normal behavior. My understanding is it is. Please let me know if I am > wrong here. Are you certain that the request waiting confirmation is the second one and not the first? > The real mystery here is when someone tried subscribing again > (listname-subscribe@listdomain) hours after the subscription policy was > changed to moderate and they still showed up in the confirm queue. How > is that possible? I tested the list with two of my addresses and both > showed up in the moderation queue as expected. As far as I can tell from > the mailman logs, this was the person's first attempt at subscribing. I suspect it was not the first attempt and that the subscription waiting confirmation was requested when the policy was confirm. The real question is if a user has a subscription waiting confirmation and the policy is changed to moderate, is a second request rejected because of the request waiting confirmation. If so, I think this is a bug which should be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: no bounce-processing with verp_probes: yes

by Mark Sapiro

On 12/6/23 06:26, Stefan Bauer wrote: > Dear Users, > > during one of our upgrades to 3.3.x we set verp_probes: yes according to > upgrade notes[1]. > > However it looks like this disabled bounce handling completely. > > Howto verify (MM 3.3.9): > > Set > verp_probes: yes > verp_delivery_interval: 1 > restart mailman3 > create test-list > add an undeliverable recipient to the list that is known to bounce. > send 6 mails to list. Bounce score is only incremented on the first bounce for that day. > see, that all the bounce-messages are received by mailman according to > postfix log[2] So they are delivered. At this point, having set `verp_probes: yes` has no effect on the processing. It only comes in to play when the threshhold is reached. > check bounce.log - no entry. > get bounce_score from API[3] - shows bounce_score 0. This says bounces are not being processed. Is the bounces runner running? If it is there should be entries like Member undeliverable-recipient(a)realdomain.tld on list v-test.lists.lists.tld, bounce score = 1. and Member undeliverable-recipient(a)realdomain.tld already scored a bounce on list v-test.lists.lists.tld today. in bounce.log. and bounce score should be 1. This is independent of `verp_probes: yes`. If the bounce runner is not running, stop and start Mailman core. You must stop and then start, not restart. Also check mailman.log for a reason why bounces runner is not running. If bounces runner is running, check mailman.log for possible errors relating to bounce processing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/25/22 01:14, Odhiambo Washington wrote: > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> How about https://mm3-lists.kictanet.or.ke/user_profile/ ? >> > > I have uncommented the line "WSGIScriptAlias /user-profile > /opt/mailman/mm/wsgi.py", > I don't see any definition for it in urls.py as well. Perhaps that's the > issue? It is defined in django_mailman3/urls.py which is referenced by re_path(r'', include('django_mailman3.urls')), > When I uncomment /user-profile, I end up with an ugly URL: > https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ > > So instead of aliasing the /user-profile, I have decided to add another > definition to urls.py: > re_path(r'^user-profile/', include('allauth.urls')), > Which I think gives me a cleaner URL: > https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ It shouldn't include `allauth.urls`. That URL is appropriate if you aren't logged in, but what do you get when you are? Go to https://lists.mailman3.org/user-profile/ and log in if necessary and you'll see what it should look like. > I also had to alias /accounts, which then brings me to: > https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I believe > is fine because one gets the > option to either login or signup. > > And I think that "/account" and "/user-profile" are synonymous. They are in your instance because of re_path(r'^user-profile/', include('allauth.urls')), but they should not be. >> It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time >> (I now use gunicorn on all the sites I manage), but when I did I think I >> had > > >> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py >> >> and all the URLs were like https://example.com/mm3/mailman3/..., >> https://example.com/mm3/archives/..., etc. >> > > I already had gunicorn working too, but I just need to also figure out this > mod_wsgi. Why? Intellectual curiosity or do you have an actual need. The bottom line is with mod_wsgi, whatever you have in your WSGIScriptAlias is going to be prepended to the URL path. If you don't want anything prepended, you need ``` WSGIScriptAlias / /opt/mailman/mm/wsgi.py ``` but then in order for user-profile to work, you need to replace ``` re_path(r'', include('django_mailman3.urls')), ``` in urls.py with the urlpatterns from django_mailman3/urls.py ``` re_path(r'^user-profile/delete$', delete_account, name='mm_user_account_delete'), re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), ``` and also add ``` from django_mailman3.views.profile import delete_account, user_profile ``` to the imports in urls.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: changing the main template for subscriptions and more

by Mark Sapiro

On 2/1/22 12:40, Paul Paulchen wrote: > Hi Mark, > > thanks for your advice. Unfortunately we need some more clues. > First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman I do not know what the file layout is in the Docker container, so I can't verify paths. > Our version: > Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > > We put an example footer.txt into the templates folder as you mentioned: > mailman3_core => var/templates/sites/de/list:member:regular:footer.txt > Mailman user can read them As I said, I can't give you an absolute path. If you can run `mailman info` in the container, that will show the location of mailman.cfg which may help Installing the template as you have should work if it's the correct path. > Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt The default templates are in the mailman/templates/ directory where the mailman/ directory is where all the Mailman core software is. Hopefully someone familiar with Docker and the Mailman Docker container can provide better information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: unwanted chunked delivery

by Mark Sapiro

On 1/7/22 11:04 AM, mm3-omf(a)sh.werbittewas.de wrote: > debian-dist mailman3 3.3.3-1. > > every post to this list will be chunked into one delivery with 60 > recipients and one delivery with 21 recipients. > > we've searched a bit and found a config-option "max_recipients" for > bulk-transfers, but we haven't set it and (as we understand the > explaination for this option) then there should be no limit in one > transfer to the MTA. If you haven't set max_recipients, you get the default which is 500. To set it unlimited you set it to 0 > nevertheless, we've tried to set it to a high value, but even this > doesn't change anything in behaviour. Right, because chunking isn't arbitrary. Chunking is done by recipient domain. The addresses are placed in `buckets` by TLD. All `.com` goes in one bucket; `.net` and `.org` in another; `.edu`, `.us` and `.ca` in a third, and all the rest in a fourth. Then the buckets are chunked with the maximum chunk determined by max_recipients. In your case, 60 recipients are in one bucket and 21 in another. The buckets are defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L29 and the work is done at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L56 My question is why is this important to you? See the FAQ article at https://wiki.list.org/x/4030582 (which is for Mailman 2.1 so it talks about SMTP_MAX_RCPTS which is what max_recipients used to be called) which suggests a much smaller number. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I think you have to open a new issue to modify the website for the mailman-suite git clone, it should be: git clone https://gitlab.com/mailman/mailman-suite.git El vie., 21 jul. 2017 a las 14:07, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Installing mailman-suite for web ui. I did this: > > (env) [mailman@localhost ~]$ git clone > https://gitlab.com/mailman/mailman-suite/ > Cloning into 'mailman-suite'... > error: RPC failed; result=22, HTTP code = 404 > fatal: The remote end hung up unexpectedly > > > but it returned an error, what should I do?? > > Thanks > > > > > > > > El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 10:29 AM, Rafael Mora wrote: >> > Can we modify the docs? >> > >> > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) >> > escribió: >> >> >> >> However, that said, the doc is wrong. The lines should be added to >> >> main.cf, not master.cf. See >> >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. >> >> >> That's what the above issue and associated MR are for. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- Atentamente / Best Regards Ing. Rafael Mora

9 years

[MM3-users] Re: Template path

by Mark Sapiro

On 9/17/20 9:33 AM, Seth Seeger wrote: > Hello everyone, > > I’m running Mailman from Docker containers, without much customization. (Postorius 1.3.3, Core 3.3.1, API 3.1, Python 3.8.5). I’ve created a list:user:notice:welcome template, and when I try to confirm a subscription, I get an error. > > I followed previous emails on this list which told me to set POSTORIUS_TEMPLATE_BASE_URL in /opt/mailman/web/settings_local.py, but that doesn’t seem to make any difference. (I set it to a different value and the error message didn’t change. I also tried setting it in /opt/mailman/core/settings_local.py to no effect. After each change, I restarted mailman-web and mailman-core containers.) How did you create the template? In Postorius or by manually creating a file somewhere? If by creating a file, POSTORIUS_TEMPLATE_BASE_URL is not relevant, but ensure that the file is findable and readable by Mailman. > From within mailman-web and mailman-core containers, I can reach “mailman-web:8000”. > > In the webpage, I see: Mailman REST API not available. Please start Mailman core. The REST APT is normally exposed on port 8001, not 8000 (See `port` in `mailman conf -s webservice`. What is your setting for MAILMAN_REST_API_URL? does the port match? > In /opt/mailman/core/var/logs/mailman.log, I get: > > [17/Sep/2020:16:23:29 +0000] "GET /3.1/lists/xxx.example.com HTTP/1.1" 200 416 "-" "GNU Mailman REST client v3.3.1" It appears you are connecting to the REST API, but ... ... > urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) Something appears to be trying to connect to REST on port 8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: "held for moderation" - alias domain details sought

by Mark Sapiro

On 11/1/24 11:14, Jeremy Stanley wrote: > On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: >> Hi friends. I've viewed this old thread: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> and documentation here: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… >> (and the Postfix docs it links to). Those documents don't seem to guide my >> situation, or maybe I just need a more specific example. The alias domain discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has nothing to do with what you are doing. >> The problem is that when messages are delivered to the alias domain, they >> are held for moderation. I.e., mail to the alias domain like >> testlist(a)domain.tld is held for moderation, but mail from the same >> subscribed, non-moderated user to testlist(a)lists.domain.tld is posted >> immediately without moderation. > [...] > > I manage a similar setup (though with Exim instead of Postfix), and > when migrating from Mailman v2 to v3 kept the same basic settings > which seemed to work: notably, under Message Acceptance I set the > alias addresses for the list in the Acceptable aliases field. If > memory serves, not doing that caused messages addressed to those > aliases to be unconditionally held for moderation. This is the correct solution. Just add `testlist(a)domain.tld` to the acceptable aliases setting of the `testlist(a)lists.domain.tld` list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 02:14 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users (< > mailman-users(a)mailman3.org>) escribió: > >> You've said you're working with labbrands.com. >> >> labbrands.com has address 192.185.51.89 >> mail.labbrands.com has address 192.185.51.89 >> www.labbrands.com is an alias for labbrands.com. >> >> telnet proves that Exim is running on that IP address. Either you're >> running it, or hostgator is redirecting the SMTP ports. >> >> You added: >> lists.labbrands.com has address 190.145.27.66 >> >> Presumably that's a different machine. >> >> So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > [image: image.png] > > Is it correct??? Your screen shot, along with the excessive quoting, only caused your post to be "too big". All the screen shot says is you have two MX records. The higher priority, 0, is mail.labbrands.com and the lower priority , 1, is lists.labbrands.com. What this means is mail to the domain will be delivered to mail.labbrands.com unless that server is somehow unreachable in which case lists.labbrands.com will be tried. This is probably not what you want. I hate to say this at this point, but you are on a cPanel host. cPanel provides a functional Mailman 2.1 service. You might save yourself a lot of grief by just using that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: django request error

by Mark Sapiro

On 10/13/21 3:38 AM, eggert--- via Mailman-users wrote: > What's strange, my mailman-web is referred to by > https://lists.tdl/mailman3/ > this show the message as above: > This page either doesn't exist, or it moved somewhere else. > The links in that page refer to urls like: > https://lists.tld/mailman/postorius/lists/ > This URL does not exist, of course. Where is the mailman3 replaced by mailman? All my config files refer to mailman3. How have you installed Mailman? We usually use links like https://example.com/mailman3 and https://example.com/archives in docs for Postorius and HyperKitty respectively. These are the ones in urlpatterns in mailman-web/urls.py We have also used https://example.com/postorius and https://example.com/hyperkitty as alternatives. To enable these, you need to add ``` url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ``` to the definition of urlpatterns in urls.py so it becomes something like ``` urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ] However, that doesn't explain why your `mailman3` URLs get munged to `mailman`. That is apparently a uWSGI thing, and since I've never used uWSGI, only gunicorn and mod_wsgi, I can't help with that other than to suggest that you might have neglected to restart uWSGI after removing the trailing slash. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Mailman and Postfix Conflicting Information

by Mark Sapiro

On 2/6/26 09:00, dap1--- via Mailman-users wrote: > I've been going in circles between mailman and postfix trying to get things working. My current condition is that either mailman is putting incoming mail in the bit bucket or postfix is not sending incoming mail to mailman. What does your mail.log say? There should be an entry like ... postfix/lmtp ... to=<lllllllllll(a)gmail.com>, relay=127.0.0.1[127.0.0.1]:8024 ... for mail to the list. > According to the postfix forum my mailman configuration is messed up but it was auto generated by the installer. Supposedly these entries should not be in /opt/mailman/mm/var/data/postfix_lmtp or rather transport_maps and/or local_recipient_maps. > > # Aliases which are visible only in the @gmail.com domain. > lllllllllll(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-bounces(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-confirm(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-join(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-leave(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-owner(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-request(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-subscribe(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-unsubscribe(a)gmail.com lmtp:[127.0.0.1]:8024 > > And relay_domains shouldn't have this entry either in /opt/mailman/mm/var/data/postfix_domains in relay_domains: > > gmail.com gmail.com > > Clearly my postfix configuration is messed up but since this was all auto generated I don't know what to do. I think the Postfix people are confused by the fact that your list domain is gmail.com and expect gmail.com mail to be delivered to Google, not Mailman. What you post above seems OK to me for what you are trying to do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases

by Mark Sapiro

On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 > .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe@lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscribe@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no whitespace.ce in the last line and I made a > new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 1/25/21 11:42 PM, David Partain via Mailman-users wrote: > Hi Gordon (and Mark)! > > I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: > > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.mysql', > 'NAME': 'mailman3web', > 'USER': 'mailman3web', > 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', > 'HOST': 'localhost', > 'PORT': '', > 'OPTIONS': { > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > 'charset': 'utf8mb4', > }, > } > } > > and restarted stuff, but I cannot tell that it has changed anything. That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. If this is the case, it would have been retried and produced the same error with each new post, and after you made the above change, it would have been archived and the errors stopped. > Do I need to do something with the database itself (which is somewhat outside my comfort zone...) to make this work? Are you saying you are still seeing these errors? If so, it may be a different error. What is the exact error message? We don't need all the Django stuff, just the part equivalent to > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\xF0\x9F\xA4\xA3\xF0\x9F...' for > column mailman3web.hyperkitty_email.content at row 1") from the OP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Search results for query "sapiro"