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

[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

[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

1 month, 2 weeks

[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

9 years, 10 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, 5 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, 1 month

[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

6 years, 9 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

5 years, 7 months

[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

[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

1 year, 11 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

6 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

3 months, 3 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

2 weeks, 1 day

[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

2 years, 11 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

7 years, 10 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, 5 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

5 years, 8 months

[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

[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

5 years, 8 months

[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

1 year, 10 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, 2 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

1 year, 8 months

[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

6 years, 10 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, 5 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

3 years, 11 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

[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, 3 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

1 year, 8 months

[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, 2 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

5 years, 7 months

[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

2 years, 9 months

[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, 4 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, 2 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, 2 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, 2 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

3 years, 9 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, 6 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, 4 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

[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, 4 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

3 years, 7 months

[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, 2 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, 5 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, 4 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, 1 month

[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, 5 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, 1 month

[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, 6 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, 1 month

[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

[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, 2 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

6 years, 11 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

[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

6 years, 10 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, 3 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

5 years, 10 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, 1 month

[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

3 years, 11 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, 2 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, 5 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, 2 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

3 years, 8 months

[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

[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

[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

6 years, 7 months

[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

2 years, 8 months

[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

9 months, 3 weeks

[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, 2 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

5 years, 9 months

[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, 1 month

[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, 1 month

[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, 5 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, 4 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

4 years, 9 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, 5 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

5 years, 7 months

[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)

5 years, 8 months

[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

5 years, 7 months

[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

2 years, 11 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

[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, 5 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

2 years, 10 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

[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

2 years, 9 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

5 years, 8 months

[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

6 years, 11 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

6 years, 10 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, 3 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

7 months, 2 weeks

[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, 4 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

6 years, 9 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, 5 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

1 month

[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, 2 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, 4 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, 3 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, 1 month

[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, 2 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, 2 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

8 years, 8 months

[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, 6 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, 4 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

8 years, 7 months

[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, 5 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

1 month, 2 weeks

[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, 6 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, 1 month

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

by Mark Sapiro

On 2/1/22 18:52, Philippe B wrote: > > But in a few very rare cases, at some point during the convoluted delivery path to the mailbox of the actual human owner of OURLIST, the recipient is changed from OURLIST-owner(a)OUR.DOMAIN to mailman(a)OUR.DOMAIN. ... > Received: from [172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78]) > by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 9E8DE207053B > for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) > > DKIM-Filter: OpenDKIM Filter v2.11.0 SMTP-SERVER.OUR.DOMAIN 9E8DE207053B > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OUR.DOMAIN; > s=unixmail; t=**********; > bh=*******************************************=; > h=Subject:From:To:Date:List-Id:List-Help:List-Owner:List-Subscribe: > List-Unsubscribe:From; > b=***************************************************************** > ****************************************************************** > ****************************************= > > Received: from SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [6.7.8.9]) > by MAILMAN-SERVER.OUR.DOMAIN (Postfix) with ESMTP id B138C1A288F > for <OURLIST-owner(a)lists.OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) The above is where the change occurs. The message is received by Postfix at MAILMAN-SERVER.OUR.DOMAIN for OURLIST-owner(a)lists.OUR.DOMAIN. Then a DKIM signature is added, presumably by `DKIM-Filter: OpenDKIM Filter v2.11.0` working on Postfix queue ID 9E8DE207053B on SMTP-SERVER.OUR.DOMAIN which is the message received from `[172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78])` with destination mailman(a)OUR.DOMAIN. It appears to me that the message is somehow relayed from SMTP-SERVER.OUR.DOMAIN to SMTP-SERVER.OUR.DOMAIN via `(ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78])` and that that's where the change in recipient occurs. -- 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: I don't get my posts with Gmail

by Mark Sapiro

On 10/18/20 5:46 AM, Allan Hansen wrote: > I was pleased to see the advice below on how to get your own list messages sent from a Google client, as my subscribers complain about their messages going AWOL all the time. > Alas, it has the following note at the bottom: > > "I have tested this and while it seems to work, it doesn't. What the filter does is put a copy of the sent message in your inbox as it is sent so it appears that you received the list post, but the message in your inbox is the same message that's in your sent folder. It's not the message received from the list.” > > Do those messages really show up in the spam folder without this filter? (I don’t use Gmail). No, they do not. > If so, then the server is, indeed, sending the message to the mail client, and the mail client is doing the message ID linking locally, discarding the incoming duplicate. > Would a change in mail client solve that? This is a Google thing. It does not depend on the client. I.e., it is the same regardless of whether your client is Gmail's web mail or a Gmail phone app or some other imap or pop3 client accessing gmail. The message is sent from the list server to the recipient's gmail/googlemail MTA and that MTA determines the Message-ID is a dup of one in the sent folder and discards 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, 5 months

[MM3-users] Re: Default values for lists in Mailman 3

by Mark Sapiro

On 9/30/24 02:17, Markus Grandpré wrote: > Dear Mark, dear list, > > in Menu "Mass Operations / Mass Subscription" I have set the default > value for checkbox "Invitation" in file > </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on > Debian 12) as you had suggested: > > > invitation = forms.BooleanField( > label=_('Invitation'), > initial=True, > required=False, > help_text=_( > 'If checked, the other checkboxes are ignored and the users > will ' > 'be sent an invitation to join the list and will be > subscribed ' > 'upon acceptance thereof.' > ), > widget=forms.CheckboxInput(), > ) This is correct. > However, administrators of mailing lists on our Mailman3 demo system > report that the invitation is still sent, even if they have deactivated > the sending of the invitation via the “Invitation” checkbox. If the admin is unchecking the Invitation box but not checking the Pre Verified box, the user will still be sent an address confirmation request. Perhaps the admins are mistaking this for an invitation. It the desire is to immediately subscribe the user with no further interaction, in addition to the Invitation box being unchecked, all three of the Pre confirm, Pre approved and Pre verified boxes must be checked. You may wish to set the Pre Verified default to checked in a manner similar to the above, or with Postorius >=1.3.14 (not yet released) you will be able to add ``` POSTORIUS_DEFAULTS = { 'mass_subscription_pre_verify': True } ``` to your Django settings to accomplish 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: Server 500 error for just one list, just one page

by Mark Sapiro

On 6/28/20 4:05 PM, kelly.close(a)lrewater.com wrote: > I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). Neither do I, but you want to look in Mailman core's mailman.log and Django's log. mailman.log is in a directory with others including smtp.log and subscribe.log. If you don't know where to find that, look in the output from `mailman conf`. The first thing to look for is [mailman] layout: which will have a value like `fhs`, `dev`, `here` or `local`. then look at [paths.xxx] log_dir: where xxx is the layout value, and if that includes $var_dir, look at [paths.xxx] var_dir: For the Django log look in settings_local.py and settings.py or whatever they're called in your case for LOGGING['handlers']['file']['filename'] > So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… That page should be the same as <https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org…>. Can you go there? Where are you finding that link? What postorius version is 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, 8 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 11/6/25 16:21, Cathryn McGuire wrote: > Many of them say: > > 1. The message is being held because: > > Message has more than 1 recipients I don't know where in affinity you find this setting, but there is a setting for Maximum number of recipients which is set to one and that is exceeded. This setting may be intentional on your part. > Post to a moderated newsgroup gateway There are also settings for a newsgroup gateway. These settings should be Gateway to mail No Gateway to news No Linked Newsgroup empty Newsgroup moderation not moderated It appears in your case that Gateway to news is Yes and Newsgroup moderation is Moderated. > But there's no cc showing. Could be a bcc, but we wouldn't be able to tell. We don't think so, though. > > 2. The following are new today (makes us wonder if EMWD is working on something): > > The message is being held because: > > Header "neighbours > <neighbours(a)mailist.dunbar-vancouver.org>" matched a > header rule > > Saw the cc when we opened the message. Was the Cc: to <neighbours(a)mailist.dunbar-vancouver.org>? If so this is a match to your Cc: header filter, and the reason should be Header "cc: <neighbours(a)mailist.dunbar-vancouver.org>" matched a header rule. If the reason was actually what is posted above with 'neighbors' rather than 'cc:', that's a problem with EMWD's Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/28/22 23:18, sascha.rissel(a)gmail.com wrote: > > After this, I deleted the venv again and startet anew, again. > But this time, I explicitly did (as Stephen suggested above) >> pip install wheel > prior to >> pip install wheel mailman psycopg2-binary\<2.9 > > This time, it ran through without errors, although "wheel" is also contained in the latter command. > Can you explain that? Apparently, if you run `pip install wheel mailman psycopg2-binary\<2.9` pip attempts to build `lazr.delegates` which is a `mailman` dependency before it fully installs `wheel`. Thus the need to `pip install wheel` first. However, with both `virtualenv 20.0.17/python 3.8.10` and `virtualenv 20.4.2/python 3.9.10` `virtualenv venv` installs `wheel` in site-packages in the venv as does `python3 -m virtualenv venv`, but `python3 -m venv venv` does not. But, at least in my case, with venv built with `python3 -m venv venv` and not containing `wheel` in `site-packages` `pip install wheel mailman psycopg2-binary\<2.9` runs without error. > Second question: > There is still no directory "/etc/mailman3" created, where I can create mailman.cfg in. > Does this maybe result from the fact that in first instance, I tried to install mailman3-full via "apt-get install" and removed it again via "apt-get remove"; with manually deleting /etc/mailman3 afterwards. > > Shall I create /etc/mailman3 manually and adding "mailman" system user permissions? Yes, as the doc says at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, "After this, create a configuration file at /etc/mailman3/mailman.cfg for Mailman Core:" -- 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: Mailman and Postfix Conflicting Information

by Mark Sapiro

On 2/6/26 10:49, dap1--- via Mailman-users wrote: > mailman.log > > Feb 06 10:33:50 2026 (137333) ACCEPT: <ed25cdc2-81ea-4e9a-a9f3-03e5aab685ff(a)myisp.net> Mailman Accepted the message. > Feb 06 10:33:53 2026 (137328) HyperKitty archived message <ed25cdc2-81ea-4e9a-a9f3-03e5aab685ff(a)myisp.net> to https: > //gmail.com/archives/list/llllllllll(a)gmail.com/message/DVXWCJVGONYAXYHWSYKVZJABR3OG5SDT/ And HyperKitty archived it. > smtp.log > > Feb 06 10:33:49 2026 (137334) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Feb 06 10:33:49 2026 (137334) Peer: ('127.0.0.1', 34218) > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) handling connection > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) >> b'LHLO dap002.localdomain' > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) >> b'MAIL FROM:<uuuu(a)myisp.net> SIZE=10502' > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) sender: uuuu(a)myisp.net > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) >> b'RCPT TO:<lllllllll(a)gmail.com>' > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) recip: clllllllll(a)gmail.com > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) >> b'DATA' > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) >> b'QUIT' > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) connection lost > Feb 06 10:33:49 2026 (137334) ('127.0.0.1', 34218) Connection lost during _handle_client() > > Hmmmm. Connection lost? Those Connection lost messages are normal and expected as a result of the QUIT command. However, missing are messages like smtp to lllllllll(a)gmail.com for nn recips, completed in nn.nn seconds post to lllllllll(a)gmail.com from uuuu(a)myisp.net, nnn bytes Is Mailman's out runner running? Are messages queued in Mailman's var/queue/out/ directory? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Moderation Action Changed After Import

by Mark Sapiro

> > I can't confirm what was set on the old MM2 list as it is no longer > accessible. I am just going on the word of the List Owner. My opinion is > that the moderation for those list members were set to Reject on the > previous MM2 list. I am mainly interested to see if you know of this > happening to anyone else and/or perhaps there is an existing bug that > could impact the moderation settings of imported MM2 lists. If you have the config.pck and any MM 2.1 installation, you can get all the info from the config.pck. For example > /path/tp/mm2.1/bin/dumpdb /path/to/config.pck|grep member_moderation_action will show the setting with 0 = Hold, 1 = Reject and 2= Discard. Finding which members are moderated is more difficult as there is a dictionary named user_options with keys = to email addresses and integer values and the integer is a bit field defined as follows (from Defaults.py) > # Bitfield for user options. See DEFAULT_NEW_MEMBER_OPTIONS above to set > # defaults for all new lists. > Digests = 0 # handled by other mechanism, doesn't need a flag. > DisableDelivery = 1 # Obsolete; use set/getDeliveryStatus() > DontReceiveOwnPosts = 2 # Non-digesters only > AcknowledgePosts = 4 > DisableMime = 8 # Digesters only > ConcealSubscription = 16 > SuppressPasswordReminder = 32 > ReceiveNonmatchingTopics = 64 > Moderate = 128 > DontReceiveDuplicates = 256 However, to address your concern, As far as I know, import21 is doing the right thing. If you want to send me the config.pck you imported, I can try to verify that. -- 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: REST API authorization failed

by Mark Sapiro

On 1/9/22 5:57 AM, Axel Rau wrote: >> >> Does the `mailman info` command report what you think for REST credentials? > yes. ... > I used curl: > - - - > (mailman_33) [root@lists5 /usr/local/mailman3]# curl -v -u restadmin:??? http://localhost:8001/3.1/lists > * Trying 127.0.0.1:8001... > * Connected to localhost (91.216.35.42) port 8001 (#0) > * Server auth using Basic with user 'restadmin' >> GET /3.1/lists HTTP/1.1 >> Host: localhost:8001 >> Authorization: Basic cmVzdGFkbWluOnc2cmtuQXpJZmVRc1o4WnlkMFpBcmNjcm55OA== >> User-Agent: curl/7.80.0 >> Accept: */* >> > * Mark bundle as not supporting multiuse > < HTTP/1.1 401 Unauthorized > < Server: gunicorn > < Date: Sun, 09 Jan 2022 13:51:43 GMT > < Connection: close > * Authentication problem. Ignoring this. > < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" > < content-type: application/json > < vary: Accept > < content-length: 77 > < > * Closing connection 0 > {"title": "401 Unauthorized", "description": "REST API authorization failed“} > - - - > I see "Server: gunicorn“, does this mean, I must install gunicorn? As you later reported, gunicorn is installed. It is installed as a dependency of Mailman core to serve as the REST server which is what's going on here. It also may or may not be used as the wsgi server for Django depending on how you configured that, but this is independent. Anyway, the above is saying that restadmin:??? doesn't match what's configured in Mailman core and reported by `mailman info`. Please check carefully that these are the same in both mailman.cfg admin_pass and settings MAILMAN_REST_API_PASS. -- 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: Postfix Hooks and Fetchmail

by Mark Sapiro

On 11/13/25 10:25, dap1--- via Mailman-users wrote: > I am not understanding the documentation. I already have this in my main.cf: > > transport_maps = hash:/opt/mailman/var/data/postfix_lmtp > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/var/data/postfix_domains > > What is not explained is where/how to add the alias_domain parameter. Does it go in /opt/mailman/var/data/postfix_domains? Is it added as a new domain or as an append to the existing domain line? The doc says in part "In order to enable this configuration, Mailman domains have an alias_domain attribute." In that sentence, `domains` is a link. did you follow it? In any case, the alias_domain is added to the existing ddddddddd.net entry at https://localhost/mailman3/domains/ or if you can't do that it is added to the domain table in the mailman database, e.g. UPDATE domain SET alias_domain = 'localhost' WHERE mail_host = 'ddddddddd.net'; After doing that, run `mailman aliases` to update the postfix files in /opt/mailman/mm/var/data including generating a new postfix_vmap file As far as Postfix is concerned, I don't know what's unclear about https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… but what you need to do is leave the current transport_maps and relay_domains as is, but add virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap and as long as your list domain is only ddddddddd.net you can remove the local_recipient_maps setting, but see the note at the end of the https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… section. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

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

by Mark Sapiro

On 8/4/25 00:21, Krinetzki, Stephan wrote: >> >> And for every one of those shunted messages there should be an exception with traceback logged in mailman.log. Those tracebacks should be helpful. > > If there were any. Maybe the "debug" level should be "info". But for which logs? The standard logging levels from lowest to highest are debug info warning error critical Whatever level is set for a log results in all messages of that level or higher being logged. I.e. if the log's level is debug, all messages for that log of any level should be logged. For every shunted message, a message like `SHUNTING: <file name without the .pck extention>` preceded by the exception and traceback is logged to error.log with level error. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/runner.py… > Maybe the restart at night after the lograte maybe the issue. As I said before, blindly restarting Mailman is a bad idea. On servers that I maintain, I always verify that all queues are empty before stopping or restarting Mailman. If necessary, I'll kill the incoming runner and wait for the out queue to empty and then stop mailman. If you want to do this daily, you could automate that., e.g. ``` if queues empty: restart Mailman else: when in queue is empty, sigterm incoming runner when out queue is empty, stop Mailman when Mailman stopped, start Mailman ``` The stop/start is needed because a simple restart at that point won't start the sigtermed incoming runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/10/2018 02:18 AM, Henrik Rasmussen wrote: > I have set up Postfix to DKIM sign outgoing mails from GNU Mailman 3.2.0a1 which validates nicely ("dkim=pass (signature was verified)"), but DMARC fails ("dmarc=fail action=none") on the recipient end, probably because the "header.from=gmail.com;" (or similar) which means that DKIM d= will not match. Right. DMARC deals with the From: domain. For DMARC to pass, either a valid DKIM sig or SPF with domain 'aligned' with the From: domain must be true. I.e., your DKIM sig and/or SPF won't do if the From: domain is not your domain. > According to dmarc.org*) "Mailing lists usually do not take authorship of the emails they relay" so I should "consider to apply specific rules for emails coming from mailing lists". Also according to dmarc.org*) Mailman (Mailman 2 that is, and I presume Mailman 3 does too) "include features to interoperate with DMARC senders". > > I assume that the dmarc mitigations list settings in Mailman is for incoming messages, but how do I set Mailman to cope with this on outgoing messages? I'm not sure I understand what you are saying. Mailman's (both 2 and 3) DMARC mitigations allow modifying the outgoing message in some or all cases so the From: domain is the list's domain so the message won't be dealt with by the recipient MTA according to the original From: domain's DMARC policy. See <https://wiki.list.org/DEV/DMARC>. Also, <https://wiki.list.org/x/17891458> may be of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Importing Mailman 2 Lists apart from Django

by Mark Sapiro

On 4/30/20 7:59 AM, Brian Carpenter wrote: > Hello Mailman Users, > > Are there instructions on importing a Mailman 2 list into a Mailman 3 > core installation only? Does the import21 script not need > Django/Postorius/Hyperkitty? import21 requires only Mailman core. > It seems Django is required to import archives I guess because of the > use of Hyperkitty. How about importing archives without having a Django > installation? Is that what the prototype archiver for? The only current archive import we support is `django-admin hyperkitty_import` which imports archive .mbox files into HyperKitty. The prototype archiver is just a maildir format collection of messages. Converting an mbox file to a maildir is trivial. from mailbox import Maildir, mbox mb = mbox('/path/to/mbox', create=False) md = Maildir('/path/to/maildir', create=True) for msg in mb: md.add(msg) > We are getting ready to start working on a custom forum application for > Mailman 3 (called Empathy) and I am would like to import some mailman 2 > archives into the development server to work with. First you have to decide how Empathy will store messages. Look at <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. This is how HyperKitty gets messages from a mbox and adds them to its database. It's actually fairly simple - a lot of the code is handling exceptions due to defective messages. Presumably Empathy will have a method for adding a message to the archive, so importing is just getting messages from the mbox and using Empathy's method to add 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: nginx configuration on a multitasking server

by Mark Sapiro

On 12/10/21 10:22 AM, David Newman wrote: > > 1. At least on my system, the proxy_pass statement will only run without > errors if I change this to a fully formed URL, e.g., 'proxy_pass > http://127.0.0.1:8000'. Is this a typo in the docs? I changed it at https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… but I wonder if we shouldn't be using `uwsgi_pass` instead of proxy_pass. See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass Are you using uwsgi or some other wsgi server. > 2. What document root(s) and alias(es) to use for Postorius and > Hyperkitty and the Django admin on a server that also runs other > services (e.g., Postfix for non-list mail and Roundcubemail)? If you can separate Mailman from other services by subdomain, you can configure them separately and for Mailman, root is irrelevant as everything is proxied or aliased in a location directive. For example, Mailman on the server that supports this list uses the lists.mailman3.org domain and we have (excerpted) ``` server { listen 443 default_server; root /usr/share/nginx/html; index index.html index.htm; # root and index are probably irrelevant as we never go there server_name lists.mailman3.org; ssl on; #ssl stuff location / { proxy_pass http://127.0.0.1:8000/; # other proxy stuff } location /static/ { alias /var/spool/mailman-web/static/; } location /robots.txt { alias /usr/share/nginx/html/robots.txt; } location /favicon.ico { alias /var/www/listorg/images/favicon.ico; } } ``` And for the other stuff we have ``` server { listen 443; server_name .list.org mirror.list.org mirror.mailman3.org; root /var/www/listorg; ssl on; # ssl stuff } -- 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: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/26/22 00:11, Stephan Krinetzki wrote: > > After we enabled the "slow query log", we got in the postgresql database the following output: > > 2022-01-25 12:49:41.538 CET [16126] LOG: unexpected EOF on client connection with an open transaction > 2022-01-25 15:34:36.047 CET [16864] LOG: duration: 30760.028 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > 2022-01-25 15:34:36.047 CET [3900] LOG: duration: 9372.471 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > 2022-01-25 16:42:07.243 CET [3900] LOG: unexpected EOF on client connection with an open transaction > > Pretty sounds like a database problem? The unexpected EOF is because the gunicorn worker timed out and was killed. There are two `DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX` transactions because the first one timed out. These came from https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… The `accept` action is processed and ultimately we get to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… and that in turn is doing the DELETE at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.… There must be some kind of database locking causing this, but I have no clue as to what it might be. If you haven't done so, I would stop all the mailman services and the database server and then start them again. I don't know if that would help, but it might. > sometimes the log (mailmansuite.log) show us this error That too is from the gunicorn worker timing out and being killed. -- 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: unique key violation because of case sensitivity of email address

by Mark Sapiro

On 6/15/24 11:47, Jörg Schulz wrote: > After updating to the most recent version of mailman-web, the migrations > script issued an error: > > > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > mailman-web | Running migrations: > mailman-web | Traceback (most recent call last): > mailman-web | File > "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line > 89, in _execute > mailman-web | return self.cursor.execute(sql, params) > mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > mailman-web | psycopg2.errors.UniqueViolation: duplicate key value > violates unique constraint > "account_emailaddress_user_id_email_987c8728_uniq" > mailman-web | DETAIL: Key (user_id, email)=(27, > John.Doe(a)mynicedomain.de) already exists. > mailman-web |(...) Presumably you upgraded django-allauth to a version >=0.62. Beginnin then, email addresses were no longer stored case-sensitively and the migration was dealing with that. There were other issues when addresses were store case sensitively. See https://github.com/pennersr/django-allauth/issues/3019 > Digging into the db, I found the duplicate to result from a duplicate > entry using john.doe(a)mynicedomain.de > > > Obviously, the process that originally created the entry, took case > sensitivity literally which doesn't seem to be the case any longer for > the migration script. > > I fixed this by removing one of the duplicates hoping no further errors > will come up.... > > > What would have been the better approach? Removing one of the duplicates is the solution, and beginning with django-allauth>=0.62, duplicates should no longer occur. -- 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: Single-Sign-out for List member

by Mark Sapiro

On 8/13/20 7:45 PM, Stephen J. Turnbull wrote: > > That said, I have some ideas for how to make this safe for corporate > Germany, specifically, keep a database of user-specific OTKs. (These > could be time-limited -- with the server returning a "use a more > recent message's URL message -- or permanent.) For the usera/userb > reasons Mark gives, and the preview-url reason you give, this is > *still* not going to be safe for discussion lists. But if the From: > is <noreply(a)DeutscheKompany.co.de>, so you have to shoulder surf and > have a photographic memory to get the user's unsubscribe URL, it > should be reasonably secure for announce lists and newsletters. I have experience with a one way email newsletter from Constant Contact. These have a link to unsubscribe and also a link to forward the email to someone else. We ultimately added our own ``` If you want to forward this email, please press the Constant Contact "Forward this email" link below. If you use your "forward" button, you might be unsubscribed. ``` note just above those links because people were forwarding the mail and getting unsubscribed when the person they forwarded it to clicked the unsubscribe link. The real pain is once a user is unsubscribed in this way, the mailing manager can't add her back. She has to personally deal with Constant Contact do get them to remove her from their "do not mail this address" list. FWIW, our note seems to help reduce if not eliminate the problem. -- 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: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:22 AM, Torge Riedel wrote: > > I like to ask what to do with other packages when upgrading mailman. I > noted, that after upgrading mailman, all requirements are fulfilled, but > a lot updates are available: > > (venv) mailman@basis2:~/core$ pip3 list --outdated > Package Version Latest Type > ------------------- ------- ------ ----- > aiosmtpd 1.2 1.2.2 sdist > alembic 1.4.2 1.4.3 wheel > atpublic 1.0 2.1.1 sdist > dkimpy 1.0.4 1.0.5 sdist > dnspython 1.16.0 2.0.0 wheel > flufl.i18n 2.0.2 3.1.3 sdist > flufl.lock 3.2 5.0.3 sdist > idna 2.9 2.10 wheel > importlib-metadata 1.6.1 2.0.0 wheel > importlib-resources 2.0.1 3.3.0 wheel > passlib 1.7.2 1.7.4 wheel > PyMySQL 0.9.3 0.10.1 wheel > requests 2.23.0 2.25.0 wheel > SQLAlchemy 1.3.17 1.3.20 wheel > urllib3 1.25.9 1.26.2 wheel > zipp 3.1.0 3.4.0 wheel > zope.component 4.6.1 4.6.2 wheel > zope.event 4.4 4.5.0 wheel > zope.interface 5.1.0 5.2.0 wheel > > Should I update them (regularly) or may I break something in mailman? In some cases and at some times, Mailman itself specifies a version <= something for a dependency. There have been issues where an upgraded dependency is not compatible with current Mailman. You can look at the install_requires section of setup.py to see if there are any specific version requirements, but this is not fool proof. For example, flufl.lock 5.0 broke Mailman core (See https://gitlab.com/mailman/mailman/-/issues/754) This was fixed in core version 3.3.2. Thus, If Mailman is working with the set of installed dependencies that you have and all of them satisfy >= requirements in setup.py, it's probably safest to leave them as is. -- 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: Change digest frequency and default threshold

by Mark Sapiro

On 10/12/2018 03:46 AM, Henrik Rasmussen wrote: > > As of /opt/mailman/core/var/queue/digest/ and /opt/mailman/core/var/queue/shunt/ no, but there is three files in /opt/mailman/core/var/queue/bad/ > > -rw-rw---- 1 root root 398 Oct 10 14:42 1539175326.8246331+4b7e80db0d22f01c2d4363e323320fcd34560657.psv > -rw-rw---- 1 root root 398 Oct 11 12:11 1539252672.3947155+ae2631d9f6514d74c77a38f09f821ee71515f9d9.psv > -rw-rw---- 1 root root 398 Oct 11 12:24 1539253469.5928977+15b0842462ddd3abcac8d688e5bbb195b07409bc.psv > > They seems to be binary, ... They are Python pickles. The fact that they are owned by 'root' probably means 'mailman digest' was run as 'root'. it should be run as 'mailman'. The files are preserved 'unparseable' queue files - probably unparseable because they can't be read because of the permissions error. You can view them with 'mailman qfile'. I expect this will show an 'empty' message and metadata containing in this case listid: 'test.lists.example.com' digest_path: '/opt/mailman/var/lists/test.lists.example.com/digest.1.9.mmdf' volume: 1 digest_number: 9 and a few other things like version and _parsemsg This is the 'digest' queue entry that tells DigestRunner to produce digests from the file in digest_path. > It seem to say PermissionError: [Errno 13] Permission denied, but inside the container, the directoried in /opt/mailman/var/queue is The permissions error is possibly on these files: -rw-rw---- 1 100 nogroup 103433 Oct 10 14:36 digest.1.7.mmdf -rw-rw---- 1 100 nogroup 155540 Oct 11 11:29 digest.1.8.mmdf -rw-rw---- 1 100 nogroup 104002 Oct 11 12:21 digest.1.9.mmdf or on the digest queue entries and it is because 'mailman digests' is not being run as the mailman user. -- 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: Installation Wooes

by Mark Sapiro

On 5/3/20 8:13 PM, Samir Faci wrote: > > Postfix Failed Logs. > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > May 4 03:07:36 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:36 lists postfix/smtpd[1968155]: 745B31473C6: > client=unknown[198.199.98.177] > May 4 03:07:36 lists postfix/cleanup[1968158]: 745B31473C6: > message-id=<158856165549.136760.840427238489827082@lists> > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: > from=<booh-bounces(a)lists.domain.org So mailman and Postfix are on different machines. That may complicate things, but > <mailto:booh-bounces@lists.domain.org>>, size=5474, nrcpt=1 (queue active) > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > May 4 03:07:36 lists postfix/lmtp[1968159]: 745B31473C6: > to=<booh-owner(a)lists.domain.org <mailto:booh-owner@lists.domain.org>>, > relay=lists.domain.org <http://lists.domain.org>[198.199.98.177]:8024, > delay=0.03, delays=0/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) This was a successful delivery. > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: removed > May 4 03:07:38 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from > unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com > <mailto:csgeek@domain.com>>: Relay access denied; > from=<booh-bounces+csgeek=domain.com(a)lists.domain.org > <mailto:domain.com@lists.domain.org>> to=<csgeek(a)domain.com > <mailto:csgeek@domain.com>> proto=ESMTP helo=<[127.0.1.1]> You are sending from a remote machine 198.199.98.177 to a presumably remote domain domain.com so relay access is denied as it should be. You need to add 198.199.98.177 to mynetworks in Postfix. -- 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: Updating from Ubuntu-20.04 LTE installation

by Mark Sapiro

On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > running MM 3.2.2 (and python 3.8.2). > > Do you have any advise, how to upgrade from there to your current > version? I know this might be a bit dangerous, but with today's VMs the > risk is much less than it used to be: It shouldn't be difficult, but I can't give you details because I don't know exactly how the Debian/Ubuntu package installs things. Also I don't know whether "current version" refers to the 3.3.1 release or the head of the https://gitlab.com/mailman/mailman master branch. > Do you think it would be possible, just to replace the code and library > parts, keeping the database and config files as is? Yes. It should be fairly straightforward. You first need to find where the Mailman Core package is. You should be able to just replace the contents of the `mailman` package directory with ours. You may be able to do this via pip pip install --upgrade mailman globally or within Mailman's virtualenv if it is installed in a virtualenv. However, there are caveats. There are Debian patches at <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` patch replaces importlib_resources with importlib.resources because importlib_resources is not available in Debian. Most of the patches apply to tests, and for the actual working code, we fixed this differently as of Mailman 3.3.1, so I don't think you need the Debian patches. -- 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: Adding members to a mailman3 mailing list

by Mark Sapiro

On 10/15/20 2:07 AM, Onyeibo Oku wrote: > > In the meantime, I moved to option #3 (recommended for production). > I hit a grey area when setting up the virtual environment. At > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, > I see: > > $ cd /opt/mailman > $ python3 -m venv venv > > The documentation imply that a 'user' creates the virtual environment > but is not explicit about that 'user'. The user can be any user you want. I use `mailman` on my production installations and `mark` on my development installation. The key is that user should be set as owner of /opt/mailman and then creating the venv and subsequent steps are all done as that user. > (1) Is it better to have a dedicated user (say 'mailman') then use that > while following the docs? I see a lot of docs referring to a 'mailman' > user. Installing mailman3 from distribution repository introduced a > 'mailman' user to my box (with special UID). There has to be reasons > for that. Yes, a dedicated Mailman user is best. > (2) Should the setup proceed with 'root'? (why do I get the feeling > that this is not the design?) No. setup should proceed as the Mailman user. > (3) How about using an already existing local user? What are the > implications? That's OK, but there are potential security implications due to the fact that the Mailman processes running as that user have access to all that user's non-mailman stuff. -- 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: Moderation -- implicit destination behavior

by Mark Sapiro

On 5/21/25 9:31 AM, Steve Bachinsky wrote: > Hi. We have noticed some posts being held for moderation (even though user has permission to post to list) and Mailman reports: > > moderation_reasons: ['Message has implicit destination’] > > The lists are configured for “require_explicit_destination”. However, the email address of the list is clearly in the CC: header of the email (no alias or subdomain). Is there some other reason why Mailman would hold an email for moderation with the reason of “implicit destination”? No. The rule looks at all the addresses in To:, Cc:, Resent-To: and Resent-Cc: headers using standard Python email library methods, lower cases them any if any lc address matches the list posting address or an acceptable_alias, the rule misses, i.e. doesn't hold the message. There is no other reason. > This moderation is not consistent for same list and poster. The emails come from a large domain with multiple load-balancing email servers. I suspect that it may be something with one or more of the servers being misconfigured, but unable to see anything obvious from the headers and confused why Mailman states the reason to be implicit destination when that does not seem to be the cause. I'm sorry, but I have no idea why this is happening. If the headers of the held message contain the explicit address, I have no clue as to why it is held for that reason. Maybe there is some other reason why the message is held, and the reason is misstated, but I don't know how that could happen. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users]Re: Subscribing via email

by Mark Sapiro

On 04/19/2016 11:31 AM, Andrew Hodgson wrote: > Hi, > > I subscribed to this list the other day via email, and I didn't get any email back suggesting I was subscribed. I logged in today via Google accounts, and it said I was subscribed to the list, but all the options for receiving list traffic, my own posts etc weren't filled in - I had to fill them in manually. 1 - You should have received a list welcome message and a 'results of your email commands' message in response to your email subscribe request. I'm Ccing you directly as it appears you can't get any list mail[1]. Visit <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> to see the aechives. 2 - The non-filling in of your options is a known issue. See <https://gitlab.com/mailman/mailman/issues/187>. Basically, you get 'default' settings, but they aren't explicitly set for your subscription by the Mailman core. [1] Here's a log message: Apr 6 23:42:22 mailman postfix/smtp[6809]: A9C9B800D9: to=<andrew(a)hodgsonfamily.org>, relay=hodgsonfamily-org.mail.protection.outlook.com[213.199.154.23]:25, delay=5.5, delays=0.05/0.05/0.29/5.1, dsn=5.7.606, status=bounced (host hodgsonfamily-org.mail.protection.outlook.com[213.199.154.23] said: 550 5.7.606 Access denied, banned sending IP [104.239.228.201]. To request removal from this list please visit https://sender.office.com/ and follow the directions. For more information please go to http://go.microsoft.com/fwlink/?LinkID=526653 (AS16012609) (in reply to RCPT TO command)) I have just now gone to https://sender.office.com/ and gone through the delisting process with this result: "Your IP 104.239.228.201 was successfully delisted. This may take up to 30 minutes to take effect." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 11 months

[MM3-users] Re: Upgrading packages

by Mark Sapiro

On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > All packages were upgraded fine. I applied the patch to > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py It shouldn't have been necessary to apply any patch. The head of the GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > to change the mistune import line. When I run now > mailman-web migrate > I get: > *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration > graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* > *To fix them run 'python manage.py makemigrations --merge'* > > However, when I run the suggested command as: > $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- > merge > No conflicts detected to merge. There's something strange here. If you look at the migrations at the head of the gitlab branch at https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/migrations, you'll see that migration 17 is named 0017_alter_emailtemplate_language.py, not 0017_auto_20220628_1132. I suggest comparing the content of your postorius/migrations/ directory with the GitLab head and resolving any differences. > Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my > production system. Would be nice to shed some light on this. I'm guessing at some point you installed something which required you to manually make this migration and that produced this conflict. Do you have both 0017_alter_emailtemplate_language.py and 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, probably just removing 0017_auto_20220628_1132 will fix this? -- 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: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/21/20 9:38 AM, Ruth Ivimey-Cook wrote: > > > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 (it obviously recognises that > as the , and so cannot be connected to by anything. That is why I set it > to 0.0.0.0 to begin with, and what the documentation implies (fairly > strongly) that this parameter is about. What documentation? I do understand what you are saying and I see the issue. I don't understand why it works for this poster <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> but maybe that's specific to Docker containers. > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed hosts to get the right connectivity, too. Try something like this and let us know if it works? If so, we can do something like add a config setting for this. > --- a/src/mailman/rest/gunicorn.py > +++ b/src/mailman/rest/gunicorn.py > @@ -53,7 +53,7 @@ def make_gunicorn_server(): > # We load some options from config.webservice, while other extended options > # for gunicorn can be defined in configuration: section. We also load up > # some logging options since gunicorn sets up it's own loggers. > - host = config.webservice.hostname > + host = '0.0.0.0' > port = int(config.webservice.port) > log_path = os.path.join(config.LOG_DIR, config.logging.http['path']) > options = { -- 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: Mails are stuck in Mailman Pipeline Queue

by Mark Sapiro

On 3/26/22 10:28, Shashikanth Komandoor wrote: > Hi Team, > > We have restarted the services as well but no change. Odd. > We tried manually moving the pck file from pipeline queue to > out queue but the file disappeared from out queue but is not getting > delivered. This is expected because if the message hasn't been processed through the pipeline, it has no recipients in the metadata, so the outgoing runner delivered it to no one. Also, it skipped archiving and digesting. > We moved the pck file from pipeline queue to out queue with the > extension .bak still no use. Same as above. > Not sure what to try next. Please help. Mi first guess is the pipeline runner isn't running, but you restarted the services, presumably Mailman core, and that might fix it, but there are various ways the pipeline runner could have died that would cause the master to not restart it. You need to stop Mailman core and then start it rather than just restarting. That may help. Also look in mailman.log. Assuming the pipeline runner died at some point, there should be a log entry and possible an exception with traceback indicating why. You can see which runners are running with something like ``` ps -fwwA|grep runner=|sed s/.*runner=// ``` This should produce a list something like ``` archive:0:1 bounces:0:1 command:0:1 in:0:1 lmtp:0:1 nntp:0:1 out:0:1 pipeline:0:1 rest:0:1 retry:0:1 task:0:1 virgin:0:1 digest:0:1 rest:0:1 rest:0:1 ``` except depending on version, `task` may not be there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 11:00, Jered Floyd wrote: > > These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! For me, on a test installation with SITE_ID = 0, this only occurs at https://example.com/accounts/social/connections/ Other URLs such as https://example.com/accounts/password/change/ and https://example.com/accounts/email/ do not throw this exception. Here's the code: ``` def get_current(self, request=None): """ Return the current Site based on the SITE_ID in the project's settings. If SITE_ID isn't defined, return the site with domain matching request.get_host(). The ``Site`` object is cached the first time it's retrieved from the database. """ from django.conf import settings if getattr(settings, "SITE_ID", ""): site_id = settings.SITE_ID return self._get_site_by_id(site_id) elif request: return self._get_site_by_request(request) raise ImproperlyConfigured( 'You\'re using the Django "sites framework" without having ' "set the SITE_ID setting. Create a site in your database and " "set the SITE_ID setting or pass a request to " "Site.objects.get_current() to fix this error." ) ``` I tried patching it from ``` if getattr(settings, "SITE_ID", ""): ``` to ``` if getattr(settings, "SITE_ID", None) is not None: ``` but that's even worse. It throws a bunch of "django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist." errors. Somehow, get_current is being called without a request object in the cases where it fails. -- 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: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/24/20 7:20 PM, Alan So wrote: > Really thanks for your hard work Mark! It is a bit strange that parseaddr behave differently with CRLF and LF. Maybe if the server is a Windows, the behavior is consistent. It might be that on Windows, `mailman inject` would create the message with CRLF line endings. > May I know when or whether will this patch be committed to the repository so that it will be effective in future release of Mailman? Thanks. In the absence of an issue at <https://gitlab.com/mailman/mailman/-/issues>, probably never. <hint> The bottom line is the original mail created by Outlook is defective.[1] While Mailman could defend against this defect, starting to do that opens the possibility that there are other areas of the code that need a similar defense. Have you asked Microsoft to fix Outlook to not create these defective messages? That's the real solution. That said, if an issue is filed, someone might consider adding something along the lines of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> to the code base. [1] given an address of the form display-name (comment) <addr-spec> in a header, it can be folded either between the display-name and the (comment) or between the (comment) and the <addr-spec>, but if display-name (comment) is quoted as in "display-name (comment)" <addr-spec> "display-name (comment)" is now a phrase within which folding is not allowed and this can only be folded between the "display-name (comment)" and the <addr-spec>. -- 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: Change language to welcome message in mailman3

by Mark Sapiro

On 7/24/20 2:10 PM, Massimo Zappalà wrote: > Hi everyone, > > My Version installed on Debian buster: > mailman3: 3.2.1 > postorius: 1.2.4 > hyperkitty: 1.2.2 > > All interfaces work well in Italian language, but "Welcome message" is in English. First question: Is the Subject: in English or Italian? If the Subject: is in English you need to compile the Italian message catalog as I described in my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Then, as far as the message body is concerned, it is built from a template. At present, in the Mailman source distribution, the only templates that are translated are French and German You will find the complete set of English templates at /usr/lib/python3/dist-packages/mailman/templates/en/. You have choices. 1) You can create /usr/lib/python3/dist-packages/mailman/templates/it/ and make Italian translations of all the English templates in the it/ directory in files of the same names, and submit a merge request at <https://gitlab.com/mailman/mailman/-/merge_requests> to merge them into the source distribution. If you are not familiar with software development in general and Mailman development in particular, this is probably beyond what you can do. 2) Find Mailman's var/ directory. This is the directory containing archives/, data/, etc/, lists/, locks/, logs/ and perhaps other sub-directories. You then need to create the full path to var/templates/site/it/ and place Italian translations of some or all the templates there. When doing so, you can add site customizations. 3) You can use Postorius to create templates for individual lists. -- 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: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/24/20 7:22 PM, Abhilash Raj wrote: > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). It's more complicated than that. Sometimes the fragment name is the heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor #3.3.3 work at all as these are #id2 and #id1 respectively. Currently the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but when a Command line section is added under 3.3.3, that will probably get the command-line id. Thus, the note "Permalink to this headline" es misleading at best because it isn't very permanent fo an evolving document. > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. I too think this is correct. I suppose it might be worth doing for NEWS.rst in particular since Sphinx doesn't seem to like fragments like n.n.n. Another way to deal with this would be to always use code names. It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` -- 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: what process creates webui tables (mailmanweb db)?

by Mark Sapiro

On 9/26/22 09:14, tflatley(a)gmail.com wrote: > hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate Probably not. First of all, `mailman-web migrate` will only affect the mailmanweb database, not the mailman database, migrations for which are run implicitly when Mailman core is started. Also, migrations will only affect tables for which there are migrations, not all tables. > this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file > > python3 manage.py migrate Yes. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. The above message saying you need to make migrations because of changes to models indicates that your Debian/Ubuntu package is broken as the packager should have created all necessary migrations. > i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? I am confused as to why you are trying to run an out of date and possibly broken Debian/Ubuntu package when it appears you have successfully installed the latest PyPI packages in a 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, 5 months

[MM3-users] Re: Deleting A List

by Mark Sapiro

On 5/3/24 03:59, Odhiambo Washington wrote: > On Thu, May 2, 2024 at 8:11 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/2/24 03:42, Odhiambo Washington wrote: >>> I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. >>> I can see from Django Admin UI that the archives are still intact. >>> I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke >>> Is there a way to move the archives from the old list to the new list? >> >> >> Change the `name` and `list_id` in the list's entry in the >> `hyperkitty_mailinglist` table in the database. If there is already an >> entry there for the new list, delete it >> >> > ``` > mysql> select id, name, list_id from hyperkitty_mailinglist; > +----+----------------------------+----------------------------+ > | id | name | list_id | > +----+----------------------------+----------------------------+ > | 1 | skunkworks(a)lists.my.co.ke | skunkworks.lists.my.co.ke | > | 2 | list(a)nog.ke | list.nog.ke | > | 3 | eanog(a)lists.my.co.ke | eanog.lists.my.co.ke | > | 4 | isoc(a)lists.my.co.ke | isoc.lists.my.co.ke | > | 5 | kazi(a)lists.my.co.ke | kazi.lists.my.co.ke | > | 6 | kenog(a)lists.my.co.ke | kenog.lists.my.co.ke | > | 7 | mechanics(a)lists.my.co.ke | mechanics.lists.my.co.ke | > | 8 | science(a)lists.my.co.ke | science.lists.my.co.ke | > | 9 | security(a)lists.my.co.ke | security.lists.my.co.ke | > | 10 | vmware_tech(a)lists.my.co.ke | vmware_tech.lists.my.co.ke | > | 11 | water(a)lists.my.co.ke | water.lists.my.co.ke | > | 12 | wordpress(a)lists.my.co.ke | wordpress.lists.my.co.ke | > | 13 | list(a)lists.nog.ke | list.lists.nog.ke | > +----+----------------------------+----------------------------+ > 13 rows in set (0.00 sec) > > mysql> delete from hyperkitty_mailinglist where id = 13; > ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key > constraint fails (`mailmansuite`.`hyperkitty_mailinglist_owners`, > CONSTRAINT `hyperkitty_mailingli_mailinglist_id_a47e04ec_fk_hyperkitt` > FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperkitty_mailinglist` (`id`)) > ``` > > Is there an easier way? > I need to delete id=13 then rename id=2 > There are several tables that reference the hyperkitty_mailinglist table by id. These are hyperkitty_email, hyperkitty_mailinglist_owners, hyperkitty_mailinglist_moderators and hyperkitty_thread. Ideally, you wouldn't have created the list(a)lists.nog.ke before updating the hyperkitty_mailinglist entry, but now, do the following: ``` update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_owners set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = 13; delete from hyperkitty_mailinglist where id = 13; update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = 'list.lists.nog.ke' where id = 2; ``` If there have been no posts to the list(a)lists.nog.ke list the updates of hyperkitty_email and hyperkitty_thread won't do anything, and likewise the update of hyperkitty_mailinglist_moderators if the list has no moderators -- 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: Place holders

by Mark Sapiro

On 5/27/25 23:23, Mark wrote: > Hi, > > The place holders listed as available on the "Add new template" page are: > > $hyperkitty_url > $listname > $list_id: > $display_name > $short_listname: > $domain > $info > $request_email > $owner_email > $site_email > $language What Postorius version is this? You may be missing some things added in 1.3.11. A more complete list including the ones that only work in certain contexts is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… a pointer to which was added in 1.3.11. > The only one that seems to sort of work on my template is $list_id - > which displays as "testlist". (I was expecting to see > "testlist(a)example.com"). $listname should be replaced with the fqdn list name like "testlist(a)example.com" and $short_listname should be replaced with the list name without the @domain as in "testlist". The others should all work as documented. I don't know why they wouldn't. Can you give an example of a template that doesn't get these substituted. > The others just get displayed as a variable. Eg. $owner_email > > Have I missed a setting somewhere? The actual substitution is done by the Python `string` library module Template class, safe_substitute method. See the doc at https://docs.python.org/3/library/string.html#template-strings Note that because we use the safe_substitute method, invalid substitutions don't produce errors, they just aren't substituted. In particular if `$identifier` is followed immediately by a letter, digit or underscore, `identifier` must be wrapped in `{}` to separate it from the following characters, e.g., `${identifier}x`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Mark Sapiro

On 7/23/20 12:38 AM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > I understood that gunicorn is a front end that is used like web server like > nginx. > > But I don't think I am using it instead I am using the httpd to redirect > requests to postorius. Steve has addressed this. > So, in this case, do you think configuring gunicorn as below would work: You do need to configure gunicorn timeout to solve your issue. > *calling gunicorn.cfg in mailman.cfg as below * > > *[webservice]* > *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* Do NOT do this. Make your own gunicorn.cfg outside of /var/lib/mailman/mailman/src/mailman/ and point to that. Otherwise any upgrade will reverse your changes. > > *and content of gunicorn.cfg as below* > > (venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg > [gunicorn] > # All the options that can be put here are available at > # http://docs.gunicorn.org/en/stable/settings.html#settings > # No of seconds to wait before killing the worker processes. > > workers = 4 > graceful_timeout = 90 > > Also what is the difference between timeout and graceful_timeout ? graceful_timeout is not what you want. It addresses something different. As it says in the comment, all the gunicorn settings are described at <http://docs.gunicorn.org/en/stable/settings.html#settings>. timeout and graceful_timeout are near the bottom of that page at <https://docs.gunicorn.org/en/stable/settings.html#timeout> and <https://docs.gunicorn.org/en/stable/settings.html#graceful-timeout>. -- 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: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 9:24 PM, Alan So wrote: > Just FYI. > > I omitted the "<" and ">" when I replace the real testing address with name(a)example.com. > > It should be, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> Actually, you didn't omit them. It's just the way HyperKitty renders what it thinks is an email address that makes it appear they aren't there. If you download the thread from HyperKitty, you'll see they are there. Anyway I am unable to duplicate your issue with your example data. I sent this raw message ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Cc: abc def (ghi) <abc(a)example.com> "abc def (ghi)" <def(a)example.com> Subject: test Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 Hi ``` and the message I received from the list included these headers ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 CC: "abc def (ghi)" <abc(a)example.com>, "abc def (ghi)" <def(a)example.com> Subject: [List] test ``` I do observe something similar to what you report that has nothing to do with folding. If I omit the trailing ">" in an address as in ``` From: Mark <mark(a)msapiro.net ``` the address becomes ``` From: "Mark <mark"@msapiro.net ``` So possibly your issue involves missing angle brackets. In order to say more, I'd need to see the actual headers as sent and received or at least an accurate munged representation. -- 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: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 4:19 PM, Ken Alker wrote: > > What else is stored in /var/messages, if not archives? I see 4711 > messages in that directory (which I presume would be as many messages > are in the archive database). If there is a write-up on this, feel free > to point me to it. I found > <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode…> but this isn't really answering my question. These are probably artifacts from your old Debian package. There have been issues in the past with handled messages not being removed from the message store. See https://gitlab.com/mailman/mailman/-/issues/257 This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes orphaned messages from the message store, but if they are still referenced in pendings they won't be deleted. > I didn't think so, but I'll certainly buy that. So, I'm assuming by > this you are implying that there is no helper function that needed to > run and the number of held messages should have dropped to zero > immediately upon a refresh of the web page? Correct, assuming your changes were committed. > So if I run the script, exist the shell, then come back in again, I > can't rely on the request.id being the same? I'd need to re-run the > script and get a new request.id? No. The request id for a given held message won't change. -- 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: HyperKitty/Mailman3 issues

by Mark Sapiro

On 11/22/18 2:58 AM, Florian Schulze wrote: > Hi! > > I tried setting up Scheduled Tasks as described in > <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> > > but the "runjobs" command can't be found. I see the hyperkitty and > mailman commands when using "help". Does "help" show a list under [django_extensions] including runjob and runjobs? Is 'django-extensions' in the list of INSTALLED_APPS in your Django settings? > The "qcluster" service is working. > > Using Django 2.1.1 and HyperKitty 1.2.1. > > Maybe related to that, I have two issues with archives. > > 1. Changing the archiving setting in the Web-UI to something else than > public seems to have no effect. The already archived messages are still > accessible in public. This is related. It is one of the "daily" jobs that updates this. Note that changing to "private" will require login after the "daily" jobs run, but changing to "do not archive" will leave the existing archive accessible. > 2. Related to 1., how can I remove a list archive without affecting > other lists? There's no easy way. For the "prototype" archiver, the archives for a list are in var/archives/prototype/listname(a)example.com/ and that directory can be removed, but that doesn't affect HyperKitty. HyperKitty's archives are in the Mailman database and multiple tables are involved. One could try just removing the row for the list from the hyperkitty_mailinglist table. That may render the list's archive inaccessible via the web UI, but I have no idea what would be broken by doing 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, 3 months

[MM3-users] Re: Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

On 7/26/19 6:20 AM, Robert Lister wrote: > > The change from Mailman2.x to Mailman3 means it's now using LMTP to > deliver to mailman instead of a local submission seems to have exposed > this issue. It is not the use of LMTP for delivery that is the issue. It is the fact that Mailman 3 uses a hash of the Message-ID: in various contexts to identify/retrieve a message. Thus, every message must have a Message-ID. See <https://gitlab.com/mailman/mailman/issues/490> for more on this. ... > My solution for now (apart from telling people not to use old broken > Outlook!) is to modify the exim mailman3_transport so that any message > with a missing Message-ID: will have one generated by exim before it's > passed to LMTP. This reproduces the same behaviour exim uses for locally > submitted messages. > > (headers_remove ensures that we end up only with one Message-ID: header > and not two, then we put back either the original Message-ID, or if > that's not there, use Exim's ID to generate a new Message-ID header.) > > Here's an updated version of the example at: > https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim ... > mailman3_transport: > driver = smtp > protocol = lmtp > allow_localhost > hosts = localhost > port = MM3_LMTP_PORT > rcpt_include_affixes = true > headers_remove = message-id > headers_add = "Message-ID: ${if def:header_message-id:{$h_message-id:}{<E${message_exim_id}@${qualify_domain}>}}" Thank you for this. I have created <https://gitlab.com/mailman/mailman/merge_requests/540> to add this to the doc. -- 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: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > Yes, the same problem. > I created the file __init__.py in /opt/mailman/mm > However, when I run using the wsgi.py I ended up (still do!) with the error: > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > application='mm3-lists.server.name|/mm3'): Loading Python script file > '/opt/mailman/mm/wsgi.py'. What is the contend of the file /opt/mailman/mm/wsgi.py? You previously posted the setting of WSGIDaemonProcess in your Apache config as: > WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman3 \ > group=mailman3 python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 \ > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var Is it still that? ... > 197.232.81.246:64709] mod_wsgi (pid=79132): Exception occurred processing > WSGI script '/opt/mailman/mm/wsgi.py'. > [Wed Jul 29 10:08:51.872754 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] Traceback (most recent call last): > [Wed Jul 29 10:08:51.872827 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File "/opt/mailman/mm/wsgi.py", line 38, in <module> > [Wed Jul 29 10:08:51.872835 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] application = get_wsgi_application() > [Wed Jul 29 10:08:51.872847 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/wsgi.py", > line 12, in get_wsgi_application ... > [Wed Jul 29 10:08:51.872984 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] ModuleNotFoundError: No module named 'settings' > > -- 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: Post-installation documentation?

by Mark Sapiro

On 11/25/21 10:56 AM, David Newman wrote: > > Thanks for this. After setting these variables and restarting mailman3 > and mailmanweb, the mailman user still cannot find a hyperkitty_import > command (neither can root, btw). Again, I installed MM3 and > Django/Postorius/Hyperkitty using the venv and web docs previously > referenced. Don't run mailman or django admin commands as root. This causes issues when files are created by root and can't be read by mailman. What django admin command are you running? If you don't set DJANGO_SETTINGS_MODULE in the environment and you have activated your virtualenv and run `mailman-web` as the django admin command it will set /etc/mailman3/settings.py as the settings. > On the plus side, all lists now appear in the admin web page. However, > lists created from the admin page do not appear in a site list page, > even though all lists are in the same site/domain. By default, only lists that you are owner, moderator or subscriber for are shown. What if you click Filter by Role and select All? > Finally, how to make these exports permanent? I did not see this covered > in the migration doc above. This is on a Debian system where the mailman > user's shell is bash. Is this simply a matter of adding environment > variables in the mailman user's .bashrc file? You can do that but as I note above, if you run `mailman-web` you shouldn't need to. You can add a `source /opt/mailman/venv/bin/activate` command as mentioned at https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtua…. -- 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: digest summary heavily cluttered with hrml code

by Mark Sapiro

On 10/15/20 11:13 AM, Mohsen Masoudfar wrote: > Hi Mark, > > Thanks again for your help! > > Yes, I meant "Today's Topic". The "Today's Topics" list is a plain text listing of the Subject: and sender of the messages in the digest. It is identical in both the plain text and MIME format digests. In what way is it cluttered with HTML. Please post an example. > I checked the link you sent, but could not see the solution to the issue. If the issue is HTML in the `Today's Topics:` list, then it is not <https://gitlab.com/mailman/mailman/-/issues/473>. If the HTML is in the messages themselves, then it is <https://gitlab.com/mailman/mailman/-/issues/473>, and that is currently not fixed and the workaround is to set Delivery mode to MIME digests. > You mentioned: > " They are in order of priority, list based, address based and global" > > Is this in descending or ascending priority? If I set it at list level, does it overwrite the member setting (address based?? )? It's descending order, I.e. list overrides address overrides global. > I set them along with "Delivery mode" at the member level and saved it, but when I get back to it, it still shows "Regular" and other fields like: > acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings > are empty, even though I set them and saved. What Postorius version is this? Is this user a member with more than one role - e.g. more than one of member, nonmember, owner or moderator. -- 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: mail stuck in "out" queue

by Mark Sapiro

On 6/9/20 7:24 AM, Kareem Zidane wrote: > We're facing a similar symptom where emails to a particular list won't go out and seem to be stuck in the out queue. We also noticed that mailman is hitting /hyperkitty/api/mailman/urls infinitely. I've attached some of strace's output. Any idea what might be the problem? > > Process 17171 attached > ioctl(20, FIONBIO, [0]) = 0 > sendto(20, "\272\10\0\0\3SELECT anon_1.member_id AS "..., 2238, 0, NULL, 0) = 2238 > ioctl(20, FIONBIO, [0]) = 0 > recvfrom(20, "\1\0\0\1\f5\0\0\2\3def\0\6anon_1\0\20anon_1_me"..., 8192, 0, NULL, NULL) = 937 > ioctl(20, FIONBIO, [0]) = 0 > ioctl(20, FIONBIO, [0]) = 0 > ioctl(20, FIONBIO, [0]) = 0 > ioctl(20, FIONBIO, [0]) = 0 ... There is way too much noise in that strace for me to find anything useful without having more of a clue as to what I'm looking for. And what process is 17171? As far as messages stuck in `out`, is Mailman's out runner running? for example, $ ps -fwwA|grep [r]unner=out mailman 6318 6272 0 Jun08 ? 00:03:28 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=out:0:1 Look in Mailman's mailman.log for messages mentioning `out runner` and for any error messages. As for `mailman is hitting /hyperkitty/api/mailman/urls infinitely` look for messages in mailman.log mentioning this. Are there messages queued in /opt/mailman/var/archives/hyperkitty/spool? if so, these are messages that failed archiving, probably because of an incorrect value for `base_url` in mailman-hyperkitty.cfg or a mismatch between `api_key` in mailman-hyperkitty.cfg and MAILMAN_ARCHIVER_KEY in your Django settings. -- 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: Detectors and Bounces

by Mark Sapiro

On 8/5/22 09:17, summersan(a)nclack.k12.or.us wrote: > > My Questions: > > Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? > > Should there normally be other detectors listed in the logs beyond the `DSN` one? > > If so, is there a setting I can change somewhere to make this happen? Prior to flufl-bounce 4.0, it would run all detectors on every message to the -bounces address. Beginning with 4.0, it runs the detectors in a defined order from most specific/authoritative to least. If you are seeing only or mostly the `DSN` one, you have 4.0 and the `DSN` detector recognizes a RFC 3464 compliant bounce. > For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Probably the upgrade also upgraded flufl.bounce to 4.0. So the real question is why are you seeing large numbers of bounces. Since it appears they are recognized by `DSN`, they probably aren't spam to the -bounces address. Do you have verp probes enabled (verp_probes = yes in the mta section of mailman.cfg)? If so, it's possible that you are getting bounces for spam and the like, but the probes don't bounce so the user's delivery is never disabled. -- 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: Invalid confirm text

by Mark Sapiro

On 8/17/20 4:53 AM, w.schoener(a)alp.dillingen.de wrote: > One thing I forgot to mention: > a week ago, the confirmation-mails still worked. > > And now: > All attempts to confirm the subscribe message failed. I used the list-request(a)list.domain and sent text-only message with the "confirm token" in the subject and/or in the body. This should work. What's in your MTA's logs? > So today I tried and used the Mailman shell to change the pending state to "confirmed", as you described here: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > After I submitted the command util.confirm('hex_token') and restarted mailman with > mailman stop > mailman start It isn't necessary to stop/star/ or restart mailman. How did you exit mailman shell. You must exit with ctrl-D or issue commit() or your transactions won't be committed. In particular, if you exit with exit() without first issuing commit(), nothing will be done. > the pending user wasnt confirmed but cleared, as if he never sent a subscribe-message. The only way to subscribe seems to be by logging in and using there the subscribe-form. What is the list's subscription_policy? It seems you successfully confirmed that token, but that may not be the last step if the list's subscription_policy is confirm_then_moderate. > Do you have any idea, whats going wrong here? I dont know what to do any more. Clearly something is broken, but I don't know what unless it is some permissions issue on the template directories/files you created. Have you looked at Mailman's mailman.log? -- 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: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 11:14 AM, Jens Günther wrote: > Just checked again and saw: > > - in the setup it works perfectly in Hyperkitty, that's nice > > - for the first web host I have 2 mail domains registered, so it also > matches (unfortunately) with what you said :-( > > Anyway, I dceleted one of it, still both lists are shown on either web > host, so it's generally not working. I don't know why this didn't work. If there is only one mail host in the domains that has the current web host as its web host, it should work. > If I can do something on this issue, please advise me. Thanks. The issue is that neither Postorius or HyperKitty as a direct way of getting lists by web host as the web host information is not an attribute of the list. We have to see which mail hosts are associated with the current web host and then display only those lists that match one of those mail hosts. The issue with Postorius is if there was more than one mail host associated with the web host, this code https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… could be relatively easily made to work by extending all_lists to include all the mail hosts, but it wasn't clear to me how to fix https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… in the case where there was more than one mail host. If you can suggest a fix, that would help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: template head/footer questions.

by Mark Sapiro

On 4/8/22 11:04, bob B via Mailman-users wrote: > I migrated from mailman 2 to mailman3 and had head/footer questions. > > In the mailman 3 GUI see the templates section, so where do those files get edited/stored? in the postorius_emailtemplate table in the database. > I added a footer to a list via the GUI, but I do not see it in: > /var/templates/lists/[listNAME]/en Because when you set a template in Postorius it makes an entry in the template table in the database with a URI pointing to its own API to retrieve the template. > I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. > > Bottom line, > > I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? That's up to you. The default search path for templates in the absence of a template table entry (or even with one with a mailman:/// URI) includes the var/templates/lists/list_id directory. is this directory leftover from migrating from mailman 2 to 3? No I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option. Again, it's up to you. If you have Postorius and want list admins to be able to create, modify, break, etc. templates without involving you, then Postorius is a good option, but it isn't in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Lookup Table Questions

by Mark Sapiro

On 12/7/21 4:09 PM, Peter Williams wrote: > > - The Mailman documentation notes that either hash or regexp tables are > supported. Is it ok to use LMDB or will I run into issues at some point? Mailman only supports hash and regexp tables for automatic maintenance of the tables as lists are created and removed. If you use LMDB tables you will need to maintain them yourself. The `mailman aliases` command won't do it. > - If LMDB tables are not a good idea to use, are there any drawbacks to > switching over to regexp tables? My main concern is that we currently have > 7000+ mailing lists, and I'm worried that switching over to regexp may > result in slower lookups. I am also wondering if there are potential issues > if the 'mailman aliases' command is run simultaneously alongside another > 'mailman aliases' command. In the past it seems like the hash table was > locked (which was good), and I'm not sure if this behavior is kept by > moving over to regexp. This may be more of a Postfix question and I > apologize in advance if I am asking the wrong mailing list for this. The locking is done in mailman/mta/postfix.py regardless of table type. I.e. it's the same for hash and regexp table updates. I wonder why you are manually running `mailman aliases`. This really shouldn't be necessary as the files are regenerated automatically as lists are created and removed. As far as performance of regexp vs hash tables, I have no idea. That's really a Postfix question. -- 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: Digests not working correctly

by Mark Sapiro

On 6/8/24 12:48 PM, Steve Brown wrote: > I'm a list administrator for a list hosted by mailmanlists.net on a server in Germany. Only one member uses the digest option, but she doesn't receive a digest until the Digest size threshold has been exceeded. (I also am subscribed as a member with the Mime Digest option and see the same behavior.) The option for Send Digest Periodically is checked but doesn't trigger a daily digest on the days that there is some activity if the aggregate size doesn't exceed the threshold. I think "periodically" means daily, and the administrator doesn't seem to have any way of checking or changing the periodicity. The hosting service has attempted several fixes, including fiddling with the cron settings, but hasn't found something that works. They even upgraded to ver. 3.3.9 recently, and that didn't fix the problem. Periodic digests are sent by the `mailman digests --periodic` command which should be run daily by cron. That and the `mailman notify` command should be run from mailman's crontab. See https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-cron-jobs I don't know what "fiddling with the cron settings" means, but if these commands are in mailman's crontab, including ``` MAILTO=some_human(a)example.com ``` at the beginning of the crontab will ensure any diagnostic output is sent to some_human(a)example.com where it will be seen. Also, putting ``` LANG=en_US.UTF-8 ``` near the beginning of the crontab may be required in some cases. See the Attention notice at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/insta… -- 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: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. Mailman 3 consists of several pieces. There is a core engine which is Python 3. The core does the basic email list management and exposes many options and settings via a RESTful API. There is also mailman.client which provides Python bindings for the REST API. This is Python 2. We also provide a web management UI, Postorius and an archiver, HyperKitty. These are Django applications and all of this is Python 2. There are other pieces as well. > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler. This is only the core. You can install it with python3 setup.py install either in a python 3 virtualenv or not, but this will only give you the core. I suggest you see the docs at <http://docs.list.org/en/latest/>, and if you don't want to use bundler, see <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the recommended way to set up a working, non-development Mailman suite. In short, the core requires Python 3.4, most of the rest of the suite requires Python 2.7 because of dependencies not yet ported to Python 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 9 months

[MM3-users] Re: Bounces

by David Krantz

Thank you for the tip. In the end I changed mailman/runners/bounce.py instead by moving the maybe_forward line so that it is always run. Smaller change (just removing one indention level) and preserves the handling. Might break something else, but I do not think so. diff --git a/src/mailman/runners/bounce.py b/src/mailman/runners/bounce.py index 57b259f..e772765 100644 --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -86,6 +86,6 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False Cheers // David On Sun, Nov 5, 2017 at 10:39 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/05/2017 01:29 PM, Mark Sapiro wrote: >> >> The bottom line is we aren't doing anything with bounces other than >> storing them. We need to fix that, and we will (It's targeted for 3.2). >> If you could help with code, that would be great. > > > As an interim work around, if you wanted to send ALL bounces to the list > owner instead of what little we currently do, at about line 65 in > mailman/runners/rest.py, you'll see > > SUBADDRESS_NAMES = dict( > admin='bounces', > bounces='bounces', > confirm='confirm', > ... > > If you change the > > bounces='bounces', > > line to > > bounces='owner', > > that will cause all bounces to be just sent to the list owner(s). > > -- > 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/

8 years, 4 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 5:43 PM, Ralph Seichter wrote: > With archiving enabled, mail is sent with headers like the following: > > Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> > List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> > List-Post: <mailto:foo-users@lists.example.com> > List-Subscribe: <mailto:foo-users-join@lists.example.com> > > The 'mailto:' entries are fine, but I need all 'https:' links to be > prefixed with https://lists.example.com instead of https://example.com . > > Does Mailman extract CN parts from the SSL certificate to populate the > header values (that would explain 'example.com' in my tests), or is this > something I can influence using configuration parameters? I searched the > docs for Mailman Suite and HyperKitty, but did not find an answer. It has nothing to do with the ssl certificate. It comes from _get_url in hyperkitty/views/mailman.py > def _get_url(mlist_fqdn, msg_id=None): > # We can't use HttpRequest.build_absolute_uri() because the mailman API may > # be accessed via localhost. > # https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.Htt… > # https://docs.djangoproject.com/en/dev/ref/contrib/sites/#getting-the-curren… > # result = urljoin(public_url, urlunquote( > # reverse('hk_list_overview', args=[mlist_fqdn]))) > # We use the MailDomain association from django_mailman3 to find out the > # proper domain. What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/ Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com -- 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: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:02 AM, Marc SCHAEFER wrote: > > I have a few questions: > > 1) persistence: as I can regenerate the configuration files (mailman, > mailman-web, hyperkitty), is all what's useful in the DB, or are some > things in /var/lib/mailman3 worth saving? > > obviously messages to be moderated, hyperkitty failed messages, > etc are stored there, but shall I assume that all mailing-lists > configuration, all users configuration and all archives are > in the DB? I don't know the details of where the Debian package puts things, but there may be Postfix related files in /var/lib/mailman3/data, but yes, all mailing-lists configuration, all users configuration and all HyperKitty archives are in the DB? > 2) I imported a list and all messages get a footer of: > %(web_page_url)slistinfo/%(_internal_name)s > which I guess changed between MM2 and MM3; however when I > look at that list configuration in the web interface of MM3, > I see no templates defined, nor any clue where this is > configured: where may I change this? import21 creates these templates in (I think in your case) /var/lib/mailman3/templates. > 3) is there a configuration somewhere that can allow someone to > create a mailman web account ONLY if he is already referenced > somewhere in a mailing-list, and not otherwise? (or to > create accounts that need approvals from an admin > before being usable?) No. > also, can a non-yet-referenced e-mail From: still subscribe to > a private list (confirm+moderate) via e-mail regardless of > the above? 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, 9 months

[MM3-users] Re: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 7:45 AM, robert.kydd(a)gmail.com wrote: > Hi Mark, thanks for this. I was away and only got back now. > It's great to get rid of the reason text. > Is there any way I can find out what is i18n message catalog. It would be nice to give a more pleasing message to the users I am still not clear on what Mailman version you are using. If it is Mailman 3, i18n translations for Mailman core are still a work in progress, and I can't tell you how to do this. For Mailman 2.1, you will find within Mailman's file system, a messages/ directory with several 'language code' subdirectories, but not 'en'. You need to create messages/en/ and messages/en/LC_MESSAGES/ and then create the file messages/en/LC_MESSAGES/mailman.po with contents like: ---------------------------------------------------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR ORGANIZATION # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: Sun Jun 17 12:22:07 2018\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: ENCODING\n" "Generated-By: pygettext.py 1.4\n" #: Mailman/Handlers/Hold.py:61 msgid "Post by non-member to a members-only list" msgstr "WHAT YOU WANT TO REPLACE IT WITH" ---------------------------------------------------------- with the various UPPERCASE things replaced appropriately and then 'compile' it via > msgfmt -o messages/en/LC_MESSAGES/mailman.mo messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Mirroring a mailman3 server

by Mark Sapiro

On 1/16/22 9:09 AM, Axel Rau wrote: > > What else must be synced (by rsync)? Aside from the database, there are multiple directories containing Mailman mutable data. Where these directories are depends on Mailman's layout configuration. For all layouts except `fhs` they are all in a single directory, but for `fhs` they are split. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/mailman… Depending on exactly what's going on between the two servers, you need to decide what needs to be synced. For example, you probably don't want to sync .pid files or or the locks directory. You probably should sync archives/, cache/, data/, etc/, lists/, messages/, templates/, public_suffix_list.dat and the search engine's (Whoosh, Xapian, whatever) index files. Syncing Mailman's queue files is problematic. They are very dynamic and it isn't practical to rsync them. The same is true to a lesser extent with messages/ > While creating a domain, what should I enter into the fields? > > Mail Host lists.framail.de (currently lists5.lrau.net) Mail Host is the FQDN of the host's email address. > Alias Domain listsl.framail.de Alias Domain is a special case to handle situations where Mail Host is a Postfix virtual domain rather than a local destination. It is normally None (not set), and if requires would never be the same as Mail Host. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > Web Host lists.framail.de (currently lists5.lrau.net) Web Host is the host name of the web web server, i.e., the host in the URL that accesses the web UI -- 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: List of "site admin" commands in Mailman 3.1 docker-mailman

by Mark Sapiro

On 07/17/2017 07:55 AM, Henrik Rasmussen wrote: > > On another note: Is it a setting in the mailman-users(a)mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."? I suspect this is something in the MTA/MDA chain between the lists.mailman3.org server and you. I suspect that something in that path doesn't like the fact that your original message's DKIM signature has been broken by such things as subject prefixing and addition of the list's msg_footer. When your message reaches my server at msapiro.net, it sees > Authentication-Results: sbh16.songbird.com; > dkim=pass (1024-bit key; unprotected) header.d=mailman3.org header.i=(a)mailman3.org header.b=QBeM9elY; > dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=alumni.onmicrosoft.com header.i=(a)alumni.onmicrosoft.com header.b=GeTpYnXK; > dkim-atps=neutral I.e., the list's DKIM sig is valid but your original sig is not, even though it was valid when received by the list > Authentication-Results: mail.mailman3.org; dkim=pass > reason="1024-bit key; unprotected key" > header.d=alumni.onmicrosoft.com header.i=(a)alumni.onmicrosoft.com > header.b=GeTpYnXK; dkim-atps=neutral If my suspicion is correct, you should be seeing the same thing with other people's posts such as this reply and your posts to other lists. If you don't then my suspicion about DKIM is not the reason and it is something else or the conditions are more complex. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] Re: Bounce handling after upgrade

by Mark Sapiro

On 7/8/20 6:05 AM, David Krantz wrote: > > To my surprise mailman core started by sending tens of mails and > blocking the corresponding users for very old bounces. What is worse > is that this happens every time I start mailman core. Now I have > blocked (almost) all outgoing mail in postfix using a transport map > which discards it but this is a temporary testing measure of course. Sorry about that. Yes this is an issue when first upgrading from a prior version to 3.3.1, there are lots of old unprocessed bounce events which all of a sudden get processed. See below for solutions. > When I deploy this server into production, I do not want these > recipients to be blocked as the old problems have been solved since > very long. My plan is to reload the database from a newer backup > anyway... Would it be enough to empty the bounce table (bounceevent) > or is there anything else driving this behaviour? Or is there a better > way to do this via the mailman shell? For me a "delete from > bounceevent" seems a lot simpler than anything via the shell but there > may be dependencies in the database. You are on the right track. The "delete from bounceevent" is a perfectly acceptable solution. So is "update bounceevent set processed = true". Another way to deal with this is to set [mta] verp_probes: yes in mailman.cfg. This will still send a lot of probe messages which may be undesirable, but if the probes don't bounce, the user's delivery won't be disabled. -- 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: Hyperkitty not receaving messages / empty archive [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/urls

by Mark Sapiro

On 1/21/25 05:44, Helge Baumgart wrote: > Hyperkitty-Api-Key in the docker-compose.yml is set via .env Variabel, > so it should be identical. I don't know how this works in the Docker image, but ... > Traceback (most recent call last): > File > "/usr/lib/python3.11/site-packages/django/core/handlers/exception.py", > line 56, in inner > response = get_response(request) > File > "/usr/lib/python3.11/site-packages/django/core/handlers/base.py", line > 197, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File "/usr/lib/python3.11/site-packages/hyperkitty/views/mailman.py", > line 109, in _decorator > not hmac.compare_digest( > > Exception Type: TypeError at /hyperkitty/api/mailman/urls > Exception Value: unsupported operand types(s) or combination of types: > 'str' and 'NoneType' The above code is doing auth = authorization.split() if (len(auth) != 2 or auth[0] != 'Token' or not hmac.compare_digest( auth[1], settings.MAILMAN_ARCHIVER_KEY)): and the exception says either auth[0] is None or auth[1] or settings.MAILMAN_ARCHIVER_KEY is None. But > META: ... > HTTP_AUTHORIZATION = 'Token (value)' and > Settings: > Using settings module settings ... > MAILMAN_ARCHIVER_KEY = '********************' So The Authorization header is the appropriate `Token value` which should result in auth[0] being 'Token', auth[1] being the value and MAILMAN_ARCHIVER_KEY is set > That is my docker-compose.yml: ... > mailman-web: ... > - HAYPERKITTY_API_KEY=${MM3_HYPERKITTY_API_KEY} #someapikey_longAndTrustworty I don't really understand why the above typo (HAYPERKITTY_API_KEY, not HYPERKITTY_API_KEY) would cause this error, but it needs to be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Mailman List Lost on URL transfer

by Mark Sapiro

On 09/20/2017 10:28 AM, heartsandbones(a)zoho.com wrote: > > Here’s the scoop: > I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. > > I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. As I have told you in other communications, you need a DNS A record for the mail.sbfriends.org pointing to the IP address of the Mailman server that hosts the list. We have no idea what that IP address is. You will have to ask your client what Mailman hosting service they were using for their sbfriends.org domain. That A record will probably suffice to get to the web UI for the list, but you will probably also need an MX record for the sbfriends.org domain pointing to mail.sbfriends.org for mail delivery to the list. > This is my first post to this forum, so I hope I’ve done so correctly. The correct list for Mailman 2.1 issues (http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org is a Mailman 2.1 URL) is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>. This list is for Mailman 3. However, you won't get a different answer from that list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Can login at /admin, but cannot login at the account/login page.

by Mark Sapiro

On 8/14/21 9:34 PM, Stephen J. Turnbull wrote: > I'm sorry, I'm in a "second vaccination" fog at the moment (mending > but concentration lasts only about 10 minutes), so I'll answer what I > know offhand since Abhilash is busy and Mark is probably offline for > vacation by now. Not quite, but very soon. > pabsta(a)gmail.com writes: > > > However, if logout and attempt to login from the postorius website, > > I get a « 502 bad gateway » error after roughly 30 seconds. The > > logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech > > free" error message > > I would guess this is also just a connection drop because it doesn't > receive the expected response within timeout. I'm sure that's right. > > and the nginx error logs just show a connection drop: > > > > 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: > > [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" > a > I see in the above `upstream: "http://127.0.0.1:8006/accounts/login/",` but in your settings ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" I suspect you may be getting a redirect from http to https which is losing POST data and you need to change proxy_pass http://127.0.0.1:8006; in your nginx configuration to proxy_pass https://127.0.0.1:8006; or set ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" -- 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: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 10/2/20 10:49 AM, Alex Schuilenburg via Mailman-users wrote: > > So something in the import has decided that the original message quote > is a header and the To: field has been modified to protect the sender > so has created the email <Firstname Surname@Company-UK> (note the > space). Not only that, it has decided this is a valid email address. > So a bug, filed as https://gitlab.com/mailman/mailman/-/issues/777 > Unfortunately I've been moving the lists over a clutch at a time, and > they are active, so I cannot just drop everything and start over. I can > munge the future .mbox files being imported to remove the quoted email > to stop this happening again, but ideally I also need to find and fix > the errors in the database. I'm very new to mm3, but handy with SQL > (I'm running on mariadb) so suggestions appreciated. There's much more detail in my reply at <https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422894486>, but you can fix the ResponseNotReady() issue from the sync_mailman job by finding the entries in the hyperkitty_sender table with invalid addresses in the address column and deleting them. We can try to address this specific issue in hyperkitty_import, but there are in general various mbox defects that we can't detect. mboxes need to be checked for unescaped `From ` lines in message bodies and other defects before importing them. The Mailman 2.1 bin/cleanarch script and the new hyperkitty/contrib/check_hk_import script can help with some of 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, 5 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/21/22 16:24, Dan Caballero wrote: > Mark, > > I'm seeing this issue pop up this week with several lists. You previously mentioned two conflicting browsers potentially causing the issue. Can you elaborate? That would only cause a transient issue which would not occur on a subsequent get of the held message view. I gather this is not the case here. I.e. once the error occurs on a get of the held message view, it is persistent. > In addition, is there a way for me to run this cleanup using mailman shell -r "somescript" so that I can check all the lists instead of one by one? For a -r script, try ``` # In non-interactive scripts, we need the explicit imports. from mailman.interfaces.listmanager import IListManager from mailman.interfaces.requests import IListRequests, RequestType from zope.component import getUtility def somescript(): for mlist in getUtility(IListManager): requestdb = IListRequests(mlist) for req in requestdb.held_requests: if req.request_type == RequestType.held_message: if not requestdb.get_request(req.id): print(f'List: {mlist.list_id}, Bad request id: {req.id}, deleting') requestdb.delete_request(req.id) ``` The real question here is what are these spurious requests and how are they occurring. If you do a query like ``` SELECT * FROM _request; ``` Are there entries with empty `data_hash` or entries with an `id` that is not the value of any `pended_id` in the `pendedkeyvalue` table. BTW, I understand why you thought an import was needed in the interactive script in my message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… - the `from mailman.interfaces.` line was a mistake on my part and shouldn't have been there. -- 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: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 5/18/22 10:48, dancab(a)caltech.edu wrote: > Mark, > > We have a question related to this thread. We use LDAP for authentication. It seems that the name attributes can only be edited via the LDAP synchronization when a user logs in for the first time and thus creates their user account. > > But what about list members that are not in LDAP? What happens behind the scenes when a member is added to a list? The user's display name is set when the user record is initially created. Assuming someone who is initially unknown, this can happen when the unknown user signs up for a web account, when the unknown user subscribes to a list via the web UI or when the unknown user is mass subscribed to a list. > Manually subscribing members has different results with our configuration. > > I've seen the manually entered name show up as "None" <foobar(a)caltech.edu>. There was a pre-existing user with that address and no display name. > I've seen the entry be accepted as is, eg. "John Doe" <jdoe(a)example.com> > I've seen the name entry be ignored but the email accepted eg. "Foo Bar" <foobar(a)caltech.edu> is subscribed but the member list only shows <foobar(a)caltech.edu> The display name has nothing to do with message acceptance. That is based only on the address. In Postorius >=1.3.6 there is a `Users` selection at the top of most pages if you are logged in as a superuser. This allows management of users including their display name. -- 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: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/15/21 11:31 AM, Kimmo L wrote: > > It seems that we have some perfomance issues on webUI, if we try to check archived messages. > Some lists, that contains low number of archives is not a problem but lists, that contains several thousand messages and grows faster are issue. Sometimes it loads so long, that i get "504 Gateway Time-Out" > I was also monitoring server perfomance and i didnt see any issues on that side. It seems that there might be some issues to read archived messages from database. But this is just my one opinion. > > I also debugged log files and found some error messages: > 1) mailmansuite.log -> django.db.utils.DatabaseError: out of memory for query result > # it happens when i try to open a lists in webui, to check archived messages. > nginx-error.log -> upstream timed out (110: Connection timed out) while reading response header from upstream > # also happens when i try to open list in hyperkitty and it takes long time to open > > If any information is more needed then let me know. My one thought was also, that maybe i need to try rebuild_indexes. Rebuilding indexes will affect only searches. It should have no effect on just opening a list. We have some large imported archives at https://mail.python.org/archives/ e.g. https://mail.python.org/archives/list/mailman-users@python.org/ with over 85,000 messages, and don't see these issues. It definitely looks like your server doesn't have enough memory. You might also run memcached and enable it for Django https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… -- 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: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > we are now getting feedback from people, who say that they are unable to > sign up, with mailman3 telling them: > > Subscription request already pending > > this is somewhat bad as: > > - at least some of the users (who reported the problem) tried to > subscribe 2 months ago (2022-01-04) - if they did not confirm their > email back then, i'm pretty sure that this email has been lost by now > - my /etc/mailman3/mailman.cfg has "pending_request_life: 3d" This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman 3.3.5. > - i (as administrator) do not see any "pending subscriptions" (the list > is setup with a simple "Confirm" subscription policy The count badge only counts subscriptions waiting moderator approval. If you pull down the Subscription requests tab and click Pending Confirmation you should see them and be able to discard them. > i wonder: > - why are the pending subscriptions not expired? (i guess they should > have expired after 3 days) It's a bug fixed in Mailman core 3.3.5 > - why can't people re-subscribe while there's a subscription pending > (e.g. if the confirmation mail got lost)? Because that's the way it was implemented. > - how can i list all pending subscriptions (for a given mailinglist)? Pull down the Subscription requests tab and click Pending Confirmation. > - how can i resolve the situtation (e.g. send out another reminder; > manually expire the pendings; manually confirm the pendings,...) If the above doesn't answer that. provide more detail. -- 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: How to add new Domain?

by Mark Sapiro

On 2/4/25 15:59, c.benner--- via Mailman-users wrote: > > After that I'll go to the admin page xxxx/mailman3/admin which brings django admin page up. > On that page I'll add "websites" and add testdomain2.net That tells Django that this is a known domain for accessing the web UI, but you also have to add it to the ALLOWED_HOSTS setting in your Django settings. > Last step is adding "mail domain" site: testdomain2.net mail domain: testdomain2.net > > After that I can add lists to that domain and mails to any list @testdomain2,net should be routed right? That's all correct. > Maybe I'm to old (56yrs) but I've read a lot of documentation and everything was clear and understandable. It was never a question of linux or windows OS but on who'S writing the doc. I can't find any doc about the web part? What about Users having no acces to the shell but the Web-Frontend? Some pictures and a "How to" and "what if" would be great! > > But it's alos possible that I'm not finding it and it's somewhere out there. You may find https://docs.djangoproject.com/en/5.1/ref/contrib/sites/to be helpful. Documentation of the Postorius UI is sorely lacking. The good news (hopefully) is the UI itself is fairly straight forward and self-documenting, but there is really no separate documentation for list owners or site admins. There is a user's manual for list members at https://docs.mailman3.org/en/latest/userguide.html but nothing similar for list admins. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Dealing with confirmation requests for unsubscribes

by Mark Sapiro

On 11/18/20 7:41 AM, Brian Carpenter wrote: > Hello List, > > I ran into the following issue for some mailman 3 lists that I am hosting: > > https://gitlab.com/mailman/mailman/-/issues/768 > > Since there is no way for a list owner to deal with a moderation request > for an unsubscription task, I assume I need to do something via the > command line. This is where I need some help with. How do I deal with > these moderation requests that are unable to be reviewed in an admin gui > (Postorius/Affinity)? mailman shell -l list(a)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 test.msapiro.net mailing list This >>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', token_owner=TokenOwner.moderator)) will return something like [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', 'list_id': 'list.example.com', 'email': 'user(a)example.com', 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': 'moderator'})] What you want is the token, in this case 'a8df55f557b5718505280d2613937e25a3109252' Then do >>> ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') which will return (None, <TokenOwner.no_one: 0>, None) and finally: >>> commit() > I do recommend removing such choices for Postorius for Member policy. I > will be doing this for Affinity until issue 768 is resolved. The correct thing to do is fix <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly will do that rather than remove the moderate and confirm then moderate unsubscription policies. -- 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: not correct language in subject(s)

by Mark Sapiro

On 5/24/23 14:36, Jens Günther wrote: > > - Shall I create all the mo-files (the other folders also only contain > the po)? If so, how would it be possible? > - How can I make it persistent? (probably it should be included in the > repo!? also another thread or an issue regarding maxxking's repo!?) We probably should distribute .mo files too, although currently they are explicitly excluded. I'll see if we have a good reason for not distributing them. > Exactly. What I was wondering: for the welcome-messages I did not have > explicit templates for those lists/domains/site that I wrote in German, > it has to be from the predefined templates, which are stored elsewhere > the in the mo-files!? (actually I don't get this point exactly but > wouldn't bother, if the above works). The templates are actually included in the mailman.po files so that they can be translated all in one place on weblate. However they are not retrieved from there. There are templates for some but not all supported languages in the mailman/templates/ directory in the installation and these are used by default, but these are not up to date in all cases with those in the mailman.po files. That should be fixed as well. In my case, for the servers I maintain, I update from the heads of the gitlab branches whenever there are significant changes and part of that process compiles the .mo files and updates the templates with scripts at https://gitlab.com/mailman/mailman/-/blob/master/generate_mo.sh and https://gitlab.com/mailman/mailman/-/blob/master/update_lang_templates.py -- 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: Connection lost during _handle_client()

by Mark Sapiro

On 11/28/24 9:17 AM, Alain D D Williams wrote: > > /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are > being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck > The process doing this is a 'qrunner' The .bak file is the one currently being processed by the `out` runner. The others are waiting to be sent. I don't know why they are continually being dequeued and requeued I suggest you stop Mailman core and then examine these files with `mailman qfile` to see if there is some issue with one or more of them, but this seems unlikely. More likely is some issue with the `out` runner itself, but I have no idea what that would be except that issues like this can be caused by files in Mailman's var/templates/ directory that aren't readable by the Mailman user (often caused by running `mailman import21` as root). > I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log > > [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) This looks like some kind of DOS attack. Look at the GET requests in the web server log. > /var/lib/mailman3/queue/shunt/ contains 4 .pck files. For each of these, there should be an entry in mailman.log indicating the exception with a traceback. Look for entries in the log ending with a `SHUNTING` message. -- 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: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu > sends an email to a list, Mailman gets the email, processes it and would try to send that email to all members with a sender field as: 'joe.student(a)university.edu'. plus listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- 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: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. This format vs. plain text digests was a user option in Mailman 2. > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius. If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool. > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 10 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/10/21 6:37 AM, Duane Raymond wrote: > Hi Mark, > > I think I have it working thanks to some hints in your questions. here is the process I took in case others experience it the same or in case anyone wishes to comment! > > When I use the mailman shell comment it seems to reflect just what you posted (I also tried test.campaigningforum.com and got the same result): > (venv) mailman@mail:/opt/mailman/mm$ mailman shell -l test(a)campaigningforum.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 test(a)campaigningforum.com mailing list > >>> > > Was there something beyond running this and getting the output I was supposed to enter? Was an error expected if one members doesn't have an associated address record? Did you enter this following the initial >>> prompt? >>> for mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... If so, it was expected to print the representation of the user object and that objects addresses list fo any member whose address attribute is None. ... > This time the posting was archived and I did get an acknowledgement of the post, but despite having the option "Receive own postings" set to "yes", I didn't receive it. As you have determined, this is a googlemail issue. See <https://wiki.list.org/x/4030680>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://gitlab.com/mailman/mailman/-/issues/385 which was fixed in Mailman 3.2.0 by https://gitlab.com/mailman/mailman/-/merge_requests/333. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- 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: Bug in 2.1.36?

by Mark Sapiro

On 11/12/21 1:06 PM, Joel Lord wrote: > I'm not sure if this is a bug or something about the new CSRF fix > doesn't get along with something I have (mis)configured, but this > definitely seems to be related. Sadly the script I use to backup > mailman before upgrading I recently stopped backing up the lists > themselves, so going back to 2.1.35 doesn't seem to be an option due to > the .pck file version bump. Here's the trace I get: > > Traceback (most recent call last): > File "/mailman/mailman-${domainslug}/scripts/driver", line 117, in > run_main > main() > File "/mailman/mailman-${domainslug}/Mailman/Cgi/admindb.py", line > 342, in main > print doc.Format() > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 352, in Format > output.append(Container.Format(self, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 267, in Format > output.append(HTMLFormatObject(item, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 53, > in HTMLFormatObject > return item.Format(indent) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 445, in Format > % csrf_token(self.mlist, self.contexts, self.user) > File "/mailman/mailman-${domainslug}/Mailman/CSRFcheck.py", line 53, > in csrf_token > mac = sha_new(secret + `issued`).hexdigest() > TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' > > Running Python 2.7.5 > . Thanks for the report. I think the issue is caused by the fix for https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a list admin is trying to handle moderator requests on a list that has no moderator password. I'll investigate and try to put out another fix later today. -- 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: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/16/23 05:34, Jeremy Stanley wrote: > > Clearly a total misreading on my part of the Django documentation to > which you referred earlier. It talks about having to feed Django > multiple settings.py files with different SITE_ID values and running > migrate to configure them, then links to the document on migrations > which starts out explaining how to use makemigrations to create > them. I took that to mean creating and configuring Django sites from > the command line required supplying customized database migrations. > > The particularly misleading bits are where it says: > > "To set the correct name and domain for your project, you can > use a data migration." > > "In order to serve different sites in production, you’d create a > separate settings file with each SITE_ID" > > It doesn't seem to talk about using django_admin at all (or if it > does, it's not mentioned by name, maybe assuming the reader knows to > use it in order to perform the necessary steps). Yes, that doc really isn't appropriate for your purpose, but it's the only one I could find on Django sites. Most of what it talks about is for more complex situations than ours and whatever bits are relevant are already done in Postorius/HyperKitty. Sorry for leading you astray. > Thanks for the clear examples! If these are available somewhere in > Django's documentation, I did a terrible job of searching for them. I don't think Django's docs address the simple task of adding a site. -- 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: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Mark Sapiro

On 3/5/26 23:25, Thomas Krichel wrote: > > I have > > root@darni /etc/mailman3 # head -15 /etc/mailman3/settings.py > # Mailman Web configuration file. > # /etc/mailman3/settings.py > > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > > # Settings below supplement or override the defaults. > # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > del ACCOUNT_EMAIL_REQUIRED > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] These are good. > root@darni /etc/mailman3 # tail -17 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/settings/mailman.py > ### added by ToK > > #: Django Allauth > #ACCOUNT_AUTHENTICATION_METHOD = "username_email" > #ACCOUNT_EMAIL_REQUIRED = True > #ACCOUNT_EMAIL_VERIFICATION = "mandatory" > #ACCOUNT_UNIQUE_EMAIL = True > > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', > 'password2*'] > ACCOUNT_EMAIL_VERIFICATION = "mandatory" > ACCOUNT_UNIQUE_EMAIL = True > ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False > > del ACCOUNT_EMAIL_REQUIRED > ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] These should be unnecessary as the ones that actually change anything are overridden by the above changes in /etc/mailman3/settings.py. > Restarted > > root@darni /etc/mailman3 # systemctl restart mailman3 ; systemctl restart mailmanweb > > Same old. > > (venv) root@darni ~ # mailman-web migrate > System check identified some issues: > > WARNINGS: > ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] what does mailman-web diffsettings|grep ACCOUNT report? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 1 day

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

On 7/28/20 5:40 AM, Brian Carpenter wrote: > Ok, I see the other thread concerning this was deleted, along with my reply. Here it is again. It wasn't deleted. It's on another list - mailman-users(a)python.org. Here's my reply to your post On 7/27/20 7:13 PM, Brian Carpenter wrote: > > This is the client that I asking about in my post. She said what I did, did not work. This is what I did: > > 1. Get into a venv as user mailman > > 2. #mailman shell >>>> from mailman.model.mailinglist import MailingList >>>> mlist = MailingList('listname(a)listdomain.org') >>>> mlist.emergency = False >>>> commit() > ctrl-d (just to be on the safe side) > > Did I not follow your instructions correctly? That should work. I don't know why the result would be any different from what Johanna did. On 7/27/20 8:58 PM, Johanna Amann wrote: > As a small followup for anyone encountering the same problem in the > future - I ended up just changing the value in the database directly. > > So - an “update mailinglist set emergency = FALSE;” (or the equivalent > in the dialect of the database one uses) removes the emergency flag from > all mailing lists. That is another approach which is valid, but why the `mailman shell` method I suggested wouldn't do the same thing, I don't know. Of course, if you're doing multiple lists, this method is easier because just one simple query does them all. -- 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: equivalent mailman 3 commands from 2.0

by Mark Sapiro

On 10/25/21 9:16 AM, bob B wrote: > For my 2.0 environment, I have scripts to dump list info, but i can't find the equivalent in mailman 3, for some commands, for example I use: > > /usr/lib/mailman/bin/list_lists which equates in mailman3 to "mailman lists" > /usr/lib/mailman/bin/list_members which equates in mailman3 to "mailman members [listname]" > > But I also use > /usr/lib/mailman/bin/list_admins [listname] > /usr/lib/mailman/bin/config_list [listname] > > Are there equivalent command line commands to get this info in mailman3? for list_admins you can use `mailman members --role administrator [listspec]`. See `mailman members --help`. There is no mailman command equivalent to config_list at this time > The mailman3 "mailman withlist [listname]" takes me into an interactive prompt not sure where to go from there. From there you enter Python statements to do what you want. e.g. ``` $ /opt/mailman/mm/bin/mailman withlist -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 property in dir(m): ... if not property.startswith('_'): ... print(f'{property}: {m.__getattribute__(property)}') ... ``` You can also create scripts to run with the --run option, See `mailman withlist --details`. > I can use the API > > curl --user [ADMIN]:[password] http://[IP]]/3.1/lists/[listname]/config | python3 -m json.tool > > > But just curious if there is a command line equivalent like in mailman2? Not at this time. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/12/22 22:03, Onyeibo Oku wrote: > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. I would suggest you not do that and just install mailman in `/opt/mailman` per https://docs.mailman3.org/en/latest/install/virtualenv.html. If you don't want to do that, you will have to replace all occurrences of `/opt/mailman` in the doc with `/usr/lib/mailman`. > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? Yes. The suggested change to .bashrc assumes you are logging in as the Mailman user, not switching via `su`. You might try `sudo -u mailman bash` or `sudo -u mailman -i` instead of `su`, but I'm sot sure if that will help. > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" I think if you have `var_dir: /usr/lib/mailman/mm/var` in the /etc/mailman3/mailman.cfg file you create per https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, then starting Mailman core `/usr/lib/mailman/venv/bin/mailman start` will create 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, 5 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 3/30/23 07:36, Gregory Edigarov wrote: > I have the same issue now. > that's happen when I try to open held messages > > This is what I have in my logs: > > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in _resource_as_dict > assert resource is not None, resource > AssertionError: None What is the full traceback? > that is the default mailman3 debian package. And your primary support resource should be Debian. > GNU Mailman 3.3.3 (Tom Sawyer) > > things were working smoothly for a very long time. it started after disk array disaster. we installed the thing to another server, and restored the database from backups. > > I've tried to use this magic: > ``` > The variable 'm' is the odoo_leads(a)qarea.org mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... if not requestdb.get_request(req.id): > ... print(f'Bad request id: {req.id}, deleting') > ... requestdb.delete_request(req.id) > ... >>>> ``` > but no success. > is there any way to fix this? I think you're on the right track with the above `mailman shell`, but evidently the issue is different. You might try ``` >>> requestdb = IListRequests(m) >>> for req in requestdb.of_type(RequestType.held_message): ... if not requestdb.get_request(req.id): ... print(f'Bad request id: {req.id}, deleting') ... requestdb.delete_request(req.id) ... else: ... print(f'Held request: {requestdb.get_request(req.id)} ... >>> ``` To see what the requests look like. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/28/25 01:14, Mark wrote: > > Then I created a template using Postorius and updated the uri in > mailman.templates to: > > file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… - and that works. Which says get the template from the file system at that location and don't ask for it from Postorius at all. This would be the default action if there were no entry for this template in the mailman.template table at all. I.e. you now have a template in Postorius, but it is not used. > It's looking promising. Now I just need to modify my script that > periodically copies the data from the > "mailmanweb.postorius_emailtemplate" table to a file and updates the uri. > > Why it won't handle the templates in the database I don't know. But at > least I can get a work-around solution in place now. If you want to continue to use the template at /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt just delete the template from Postorius and update that file directly. If Postorius template updates don't work because of web server caching or whatever, just don't use them and use templates in the /opt/mailman/mm/var/templates/ hierarchy instead. You can create sitewide templates at /opt/mailman/mm/var/templates/site/en/*, domain specific templates in /opt/mailman/mm/var/templates/domains/en/* and list specific templates in /opt/mailman/mm/var/templates/lists/<list-id>/en/ without any entries in the mailman.template table. Note that sitewide templates can be the most useful and can't be created in Postorius anyway. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/30/2017 02:27 PM, David Krantz wrote: > > I tried to upgrade today. The result is a broken install which fails > when trying to upgrade the database. > > > $> ./bin/mailman-post-update > [...] > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", > line 94, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > django.db.utils.IntegrityError: update or delete on table "auth_user" > violates foreign key constraint > "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on > table "social_auth_usersocialauth" > DETAIL: Key (id)=(3) is still referenced from table > "social_auth_usersocialauth". This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > I have tried to drop and recreate the databases but I get the above > result anyway. I'm not sure what you mean by drop and recreate the databases. You should just drop the `social_auth*` tables, or if there's nothing in the database you want, just starting with an empty database should work. > The description in > https://wiki.list.org/DOC/Mailman%203%20installation%20experience is > very hazy. The process of symlinking in libraries is fiddly to say the > least. I get mailman to start but not any web interface. I have not > tested mailman so if it works rather than just start I do not know. Sorry about that. The symlinking was due to my starting with bundler and then "undoing that" without trying to find everywhere the old paths might be referenced. -- 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: Invalid confirm text

by Mark Sapiro

On 8/14/20 3:28 AM, w.schoener(a)alp.dillingen.de wrote: > > Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: > return the message unchange. > > When I return the message, I get an answer: > Invalid confirm text. With current releases of Mailman, the confirm request you receive should be: From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token> with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678> > My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line confirm <hex-token> as either the Subject or body of the message to <listname>-request@<list.domain>. That should work. Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval. > Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l…> -- 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: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 10:11 AM, Massimo Zappalà wrote: > Hi everyone, > if I write a my lists from other email address I get the correct message: > opendkim[23516]: 8EEE440FFD: DKIM-Signature field added (s=mailselector, d=catania.linux.it). > > While if I write to a my lists from email address Gmail, on opendkim I get the following messages: > opendkim[23516]: BA95241952: no signing table match for 'maszap69(a)gmail.com' > opendkim[23516]: BA95241952: s=20161025 d=gmail.com SSL error:04091068:rsa routines:int_rsa_verify:bad signature > opendkim[23516]: BA95241952: bad signature data OpenDKIM on your server is not signing the message because it is not configured to sign messages From: 'maszap69(a)gmail.com' What's in your opendkim SigningTable and what's in your opendkim.conf for SenderHeaders. The recommend config is SenderHeaders List-Post,Sender,From to use the domain of the list for signing list mail and then to include that domain in SigningTable. > I also receive an email at superuser: > > [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/archive > > Internal Server Error: /hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") > ... This appears to be unrelated. HyperKitty is trying to store the message in the database hyperkitty_email table and gets this error. To say more, I'd need to see the complete raw message which you may be able to find in Mailman's var/archives/prototype/<list_address/new/ and if available, a full traceback and possibly more from the email you receive from Django or from the log file configured in your Django settings. -- 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: Confirmation emails aren't sent to users.

by Mark Sapiro

On 2/12/26 13:58, Ibiam Chihurumnaya via Mailman-users wrote: > > I created an admin user and when I try to sign in with that user, I get a page that tells me that a confirmation > email has been sent and I should confirm the user. > > I created another user with a different email, and I got the same thing, didn't receive the confirmation emails in my inbox. Do you mean you are creating these users by adding them as list owner or moderator or are you creating them via the https://example.com/accounts/signup/ page. > I looked at mailman smtp logs, and didn't see any event related to the confirmation emails. > The uwsgi logs show the events though. If this is the latter, it has nothing to do with Mailman core or the smtp log. It is via django-allauth and the mail comes from Django. > The only place I see something about it is in uwsgi; > 3050415 [pid: 1985548|app: 0|req: 518823/979759] 127.0.0.1 () {54 vars in 1197 bytes} [Thu Feb 12 21:52:32 2026] GET /accounts/confirm-email/ => generated 1556 bytes in 48 msecs (HTTP/1.0 200) 9 headers in 359 bytes (1 switches on core 0) OK, this is Django. The default EMAIL_BACKEND from mailman_web/settings/base.py is django.core.mail.backends.smtp.EmailBackend and unless you've changed that or added overrides various other defaults are EMAIL_HOST = "localhost" EMAIL_PORT = 25 EMAIL_HOST_USER = "" EMAIL_HOST_PASSWORD = "" EMAIL_USE_TLS = False EMAIL_USE_SSL = False EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = None Are those appropriate? Do you have an outgoing MTA listening on `localhost:25`? What's in it's logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/31/2018 01:52 PM, Ryan McClung wrote: > That explains a lot. Is there any documentation you can provide to show me > where I can set a static config/db? See <http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html> That may not specifically address your question, but it will explain the issue in detail. An example of what I do on several servers I support is this. First, I install Mailman in a virtualenv which is /opt/mailman/mm/venv. Then the commands I run are all put in /opt/mailman/mm/bin. the actual installed 'mailman' command is /opt/mailman/mm/venv/bin/mailman but I never run that directly or as 'mailman' with the venv active. My var/ directory is /opt/mailman/mm/var. My mailman.cfg is actually outside of the var/ directory in /opt/mailman/mm/mailman.cfg. (In some cases for historical reasons it's in /opt/mailman/mm/deployment/mailman.cfg, but ignore that.) In /opt/mailman/mm/bin/mailman, I have #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ The details such as installing in a venv or where things are are not the important things. The important thing is the only 'mailman' command I ever run invokes Mailman with a -C option that points to the only config I want to use and that in turn has a var_dir setting pointing to, in my case, /opt/mailman/mm/var. Also, the 'unset PYTHONSTARTUP' is there to address an issue with 'mailman shell' that would double the size of the shell history file each time it was run. I'm not certain that's still needed. -- 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: How to change the language in mailman3

by Mark Sapiro

On 7/20/20 5:19 PM, Massimo Zappalà wrote: > Hi everyone, > Debian buster run on my server. > I installed the apt install mailman3-full package and configured it. Everything works fine. > I'm trying to change the language (mailman3, postorius and hyperkitty) from English to Italian, but it's not clear what I'm missing. > These are the files that I modified to try to set the Italian language: > > /etc/mailman3/mailman.cfg > default_language: it > --------------------------------------------------------------- > /etc/mailman3/mailman-web.py > LANGUAGE_CODE = 'it-IT' > TIME_ZONE = 'Europe/Rome' > USE_I18N = True > USE_L10N = True > USE_TZ = True > --------------------------------------------------------------- Assuming this is the Debian packages Django settings file for mailman, it probably contains something like try: from settings_local import * except ImportError: pass at the end. You should put your local changes in the /etc/mailman3/settings_local.py file. > /usr/lib/python3/dist-packages/django/conf/global_settings.py > TIME_ZONE = 'Europe/Rome' > USE_TZ = True > LANGUAGE_CODE = 'it-IT' > --------------------------------------------------------------- This probably isn't needed as it should be overridden by the above. > With this command, I set the Italian language to the list. It takes the setting, but it doesn't work > sudo mailman shell -l test(a)pratico.work >>>> m.preferred_language='it' >>>> commit() >>>> CTRL-D > > Can anyone tell me what I'm missing? The source distribution for Mailman core does not contain the compiled message catalogs, and Debian's package probably doesn't either. Find the mailman/messages/it/LC_MESSAGES directory, cd to that directory and give the command msgfmt mailman.po -o mailman.mo -- 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: Cannot Create New List

by Mark Sapiro

On 11/8/25 10:35, dap1--- via Mailman-users wrote: > ~$ mailman info > GNU Mailman 3.3.10 (Tom Sawyer) > Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] > config file: /opt/mailman/var/etc/mailman.cfg What is /opt/mailman/var/etc/mailman.cfg? Is it a symlink to /etc/mailman3/mailman.cfg or is it a separate file. In any case `mailman info` should report /etc/mailman3/mailman.cfg as the config file. Are you running these commands as the mailman user with the venv active. That MUST always be the way you run them. > db url: sqlite:////opt/mailman/var/data/mailman.db Is this the sqlite db you are looking at? > I haven't replied to your link because the list apparently hasn't been created properly yet. If you are referring to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… the questions there were to help diagnose why the list was apparently not created, at least where you think it should be. They ask for more detail about how you ran the commands that didn't do what you expect. What they ask doesn't in any way require the list to be created where you think it should me. What is going on here is if I had root access to your server, I could probably figure this out in minutes, but I don't have that access and I would refuse it if offered for multiple reasons, so I need to ask you to do what I would do and report the results so I can move on to the next thing. So if you want to solve this, please do and report the things I ask. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

On 7/26/19 11:05 AM, Stephen J. Turnbull wrote: > The problem is that Mailman's LMTP server rejects malformed mail. I > seem to recall that in Mailman 2, Mailman itself would add a > Message-ID field if one was not present. I don't know how easy it > would be to provide this feature, since we would have to patch the > LMTP server code so the message could make it to Mailman proper > (Mailman 3 imports the LMTP server from the stdlib). It's a simple patch to the lmtp runner (Mailman's LMTP server). There's a closed issue on this at <https://gitlab.com/mailman/mailman/issues/490> - closed because I convinced the submitter it wasn't the right thing to do. > > My solution for now (apart from telling people not to use old > > broken Outlook!) is to modify the exim mailman3_transport so that > > any message with a missing Message-ID: will have one generated by > > exim before it's passed to LMTP. This reproduces the same behaviour > > exim uses for locally submitted messages. > > I'm not sure it's a good idea to do this (and certainly not by > default). The only times I've seen messages without a Message-ID are > spam messages. I suppose we can add this to the documentation. I added Robert's solution at <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#troubles…> The requirement for a Message-ID: is documented, albeit not very prominently, at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/runners/docs/lmt…>. -- 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: Hyperkitty download mbox

by Mark Sapiro

On 4/25/21 2:20 PM, Andrew Hodgson wrote: > Hi, > > Hyperkitty 1.3.4. > > I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. > > Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, do it in pieces by adjusting start and end. e.g. <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> fails the same way. If I try to get 2013 month by month, all work except December which gives me an internal server error. What's the traceback from that 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, 10 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 03/17/2017 03:59 AM, Anders Nilsson wrote: > > I do have problems with some lists occasionally going into some kind of > shunt mode, where alla mails sent to them gets shunted. In the Mailman > log I get entries for each shunted email: > > Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows > were found for one_or_none() ... > File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", > line 70, in process > archiver_set = IListArchiverSet(mlist) mailman/handlers/rfc_2369.py is adding the List-* headers. Here it is looking up all the archivers that are enabled for this list. ... > File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", > line 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() and here we are in code that is trying to see if there are any system enabled archivers that are not already associated with this mailing list and if so, add them to the archivers enabled for this list. The above is the last line of exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() which is querying the archivers enabled for this list for the name of a system enabled archiver and expects to find at most one entry > File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", > line 2733, in one_or_none > "Multiple rows were found for one_or_none()") but finds more than one. > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > Mar 17 11:54:11 2017 (6217) SHUNTING: > 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 So the cause is there appear to be multiple database entries for this list and some archiver name, but I don't know how that can happen. I have not seen this error. -- 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: Change digest frequency and default threshold

by Mark Sapiro

On 10/04/2018 12:19 AM, Henrik Rasmussen wrote: > > Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. 3.2.0a1 was never an 'official' release. It could be any HEAD version between June 4, 2017 and Jul 10, 2018. The --periodic option was added April 28, 2018. > When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). Are there accumulated messages for the digest when you run the command?. I.e., is there a var/lists/listname.lists.example.com/digest.mmdf file with messages in it? Are there list members receiving digests? If so, there should be something in Mailman's smtp.log. > As I understand, using --sent should send a digest immediately (except when used with --dry-run). Correct,if there is one to send. > As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? It is Kilobytes. > Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? The digest size threshold has no effect on whether or not a digest is sent by 'mailman digests'. -- 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: Add domain to Mailman, can't create list with that new domain

by Mark Sapiro

On 10/17/24 13:41, Andy Matthews wrote: > > and then rebuilt kubernetes, I found that when I hit the API to get all lists, the list mailman(a)foobar.com existed, and was the default. I could create lists against foobar.com but could no longer create them against mydomain.com. > > So it looks like when you're initially configuring mailman you have to create your first mailing list, and whatever domain you use becomes your "primary domain". I don't know where this is documented, but could someone confirm this behavior for me so that I know that I'm on the right path? And previously you wrote: > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> Did you commit() after doing the above? I'm not sure how kubernetes fits in to this, but `mailman create` for a list in an unknown domain will create the domain unless -D or --no-domain is specified. See `mailman create --help`. Mailman core has no concept of `primary domain` which is why it's not documented. Are you creating lists via REST as you posted previously. If so, the domain must exist, but if you created domains as above, they should exist as long as you committed your changes. -- 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: Disabling mail/news gateway was: Moderation action "None" is misleading

by Mark Sapiro

On 2/5/25 13:03, Ron / BCLUG wrote: > > I've been digging into MM3 resource usage vs MM2 and have been > wondering: are there any other runners that can be disabled, or invoked > via cron job to run every $interval then exit again? The task runner is a candidate. It only actually does anything at intervals defined by the run_tasks_every setting in the [mailman] section of mailman.cfg, default 1 hour https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…, but it still wakes up and comes into memory every sleep_time which defaults to 1 second. If just having the runners sleep longer works for you, you can set, e.g. ``` [runner.task] sleep_time: 10m ``` to only wake up the task runner every 10 minutes. If you really want it gone, you could put ``` [runner.task] start: no ``` in mailman.cfg to prevent starting it as a persistent runner, and make a python script like: ``` #!/opt/mailman/mm/venv/bin/python from mailman.core import initialize from mailman.runners.task import TaskRunner initialize.initialize() TaskRunner('task')._do_periodic() ``` and run that periodically via cron. I'm not certain, but I think task runner is the only runner for which it's that simple. > Second question, similar topic but MM2: how to disable NNTP? (if that's > what this is doing): > > /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Put this in mm_cfg.py del QRUNNERS[QRUNNERS.index(('NewsRunner', 1))] or if you already have some modifications to the QRUNNERS list in mm_cfg.py, make the appropriate adjustment to remove the NewsRunner 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, 1 month

Search results for query "sapiro"