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

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 9:51 AM, alopez(a)ac.upc.edu wrote: > Now I have created the mailing list with 'mailman create' but I get this error: > > postmap: warning: /etc/postfix/main.cf, line 65: overriding earlier entry: virtual_alias_maps=hash:/etc/postfix/virtual_alias/example.edu, hash:/etc/postfix/virtual_alias/example.org > > in my postfix file I have the following code: > > virtual_alias_maps = hash:/etc/postfix/virtual_alias/example.edu, > hash:/etc/postfix/virtual_alias/example.org, > hash:/var/lib/mailman3/data/postfix_vmap > > Should I remove hash:/etc/postfix/virtual_alias/example.edu, and hash:/etc/postfix/virtual_alias/example.org, ? In that case how I create alias not related to mailman? Without seeing the contents of those files, I can't say, but something in /var/lib/mailman3/data/postfix_vmap is conflicting with and overriding something in the other two files. Since the only things in /var/lib/mailman3/data/postfix_vmap are specific list addresses, they are probably what you want, and you could just ignore the warning, but you probably do want to examine and remove conflicts from the other two files. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/1/24 13:17, jkoral(a)luc.edu wrote: > Here is my plan for forwarding. Let me know if this looks correct. First off, I deleted the list off of the old server, so I am assuming that removed the alias as well. > > -Create new alias file in /var/lib/mailman/data/ called migratedaliases (this directory is where the aliases file is currently located, but under the aliases file). > -Edit /etc/postfix/main.cf and add the path to migratedaliases to alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases. After editing, it will look like this: alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases, hash:/var/lib/mailman/data/migratedaliases. > -Run newaliases command to update the aliases db. > -Then add the alias for the the migratedaliases file the way you posted above. > > Does that make sense? Yes On 10/1/24 13:19, jkoral(a)luc.edu wrote: > Or can I just put the forwarding alias in /etc/aliases? Yes. -- 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: List description as sender

by Mark Sapiro

On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- 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: Emergency Moderation

by Mark Sapiro

On 5/25/20 8:21 PM, Allan Hansen wrote: > > Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. `emergency` moderation is meant for emergencies such as flame wars on and otherwise open list. It trumps essentially everything else except pre-approval with and Approved: <password> header. It is not really intended as a "normal" list setting, although it can be used that way if you want to hold all posts. The default action "Hold for moderation" for members and non-members only applies to those whose individual moderation is set to "List default". To fully understand the difference, you have to know the order in which the various checks are applied. This is defined at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. You will see for example that emergency with a hold action comes before banned-address with a discard action. This means that if emergency is True, a post from a banned address will be held and not discarded, at least initially. -- 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 to MM3 migration

by Mark Sapiro

On 1/31/23 13:34, David Newman wrote: > > Is this really as simple as building the new server, creating the same > lists on the new server, and rsync’ing the archives from the old server? > If not, how to do the migration? If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff. To do only selected lists is much more difficult and there are no scripts that I am aware of. HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Moderated unsub requests are not provided by mailman3 service

by Mark Sapiro

On 11/29/24 4:47 PM, Joachim Schrod wrote: > > The unsubscriptions requests are not shown in the web interface. I > suppose they should appear in the UI section "Subscription requests", > either as "Pending Approval" or "Pending Confirmation". (Frankly, I > don't understand the difference between these two options at all.) Subscriptions pending confirmation are those waiting for the user to confirm. Those pending approval are waiting for moderator approval. Unsubscription requests not being shown is https://gitlab.com/mailman/postorius/-/issues/332 which was fixed in Postorius 1,3.6 released over 3 years ago. Current release is 1.3.13. > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > both on Debian 11 (bullseye). > > I know that this is out of date; thus a definitive info "this is fixed > by now" is quite OK for me. (Debian upgrade is planned as the next > action after getting Mailman3 to work for that use case.) Yes, this is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: Errors in MM3

by Mark Sapiro

On 4/7/25 04:08, Odhiambo Washington via Mailman-users wrote: > I am using uwsgi+APache2. > I am suddenly seeing hundreds of errors in my mailmanweb and uwsgi logfiles: > > 1. mailmanweb.log has hundreds of such lines: > [WARNING] [2025-04-07 13:01:50,162] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/message/YOPKCEWPHX4BV7U5MOTCVCNSWR2J2JOZ/vote ... > [WARNING] [2025-04-07 13:02:37,567] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/thread/MICNFIHVLOETVE4PXEDO5MBYWG7SN57H/favorite ... > > Any clues as to what needs to be done to mitigate the above? A web crawler is issuing GETs for those URLs which only allow POST. If you look in your web server logs, you can find the IPs they are coming from. If it's only a few, you can block them with a firewall or using access controls in your web server. If its a compliant web crawler, you may be able to use robots.txt to stop it. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 2 days

[MM3-users] Re: MM3 on debian - redirect problem

by Mark Sapiro

On 4/27/20 8:17 AM, Gelpi Andrea wrote: > Hi, > on a debian10 I have mm3 installed via apt-get > > apt-get install mailman3-full > dpkg-reconfigure mailman3 > dpkg-reconfigure mailman3-web > > I have this minor issue > > https://webserver/mailman3 redirects to > http://webserver/mailman/postorius/lists/ > > that doesn't exist. > > The same problem form django admin page to return to lists > > https://website/mailman3/admin/sites/site > > In the upper right corner I have a link to https://webserver/mailman3 > that redirects to https://mailman/postorius/lists/ > > I searched for a redirect but without success. The redirection must be a web server issue. There is a urls.py file probably in the same directory as your django settings - probably /usr/share/mailman3-web/urls.py in your case. You can make a URL like http://webserver/mailman/postorius/lists/ work by adding url(r'^mailman/postorius/', include('postorius.urls')), to the urlpatterns list in the urls.py file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Mark Sapiro

On 12/20/22 06:48, Odhiambo Washington wrote: > > There is a WARNING on > https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install > which says one must create the config file as /etc/mailman3/mailman.cfg > How to force mailman to read that file is something I haven't understood, > but turns out to be what has taken me days trying to get things right. If you run the `mailman` command without any -C option, it will look for a config in /etc/mailman3/mailman.cfg > Ultimately, when I did the import, there was only one email from the > archives that failed to be imported - which I honestly don't mind, but > maybe there is a solution for this > "'utf-8' codec can't encode character '\udcae' in position 331: surrogates > not allowed" ?? If you provide a copy of that message from the mbox, either on the list or to me directly, I'll investigate. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Change delivery_status of a member by using the rest api

by Mark Sapiro

On 5/4/23 12:30, Michael Schaarschmidt wrote: > Hello, > > I would like to set or change the delivery_status of a list member by > using the rest api. The curl request looks like > > curl \ > -X PATCH \ > -H "Content-Type: application/json“ \ > -H "Accept: application/json“ \ > -u restadmin:secret_password \ > -d "@./foo_patch.json“ \ > "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e“ > > With the json-file: > > { „delivery_status“: „by_user“ } I assume those fancy quotes are an artifact of your mail client. > I get an error message: > > {"title": "400 Bad Request", "description": "Unexpected parameters: > delivery_status“} > > > Is there a way to change the attribute `delivery_status` of an existing > member by using the rest api? You can't set a memnber's delivery status directly. It is an attribute of the member's preferences. The correct endpoint is "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e/preferen…" -- 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: Problems with mailman core translation and other details

by Mark Sapiro

On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: > It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. > > #: templates/postorius/lists/summary.html:88 > #, python-format > msgid "" > "\n" > " To subscribe you can send an email with 'subscribe' in the" > "subject to\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " or use the form below:\n" > "" > msgstr "" > "\n" > " Para se inscrever você pode enviar um e-mail com o assunto" > "'subscribe' para\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " ou use o formulário abaixo:\n" > > What am I doing wrong? Or what can I do to make things suitable? Is the rest of that page translated appropriately? -- 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: Moderation of held emails vs. spam

by Mark Sapiro

On 3/11/25 7:09 AM, ricola(a)poivron.org wrote: > > The problem is when spam is held for moderation and forwarded to the list owner, the mail provider of the list owner sometimes flags the moderation request as spam because it includes the original spam message. > > Sounds much safer to only forward a summary of the subject line, sender and size to the list owners and not the full message. This is https://gitlab.com/mailman/mailman/-/issues/670. https://gitlab.com/mailman/mailman/-/merge_requests/1332 and https://gitlab.com/mailman/mailman/-/merge_requests/1334 introduce a new admin_notify_held_with_attachment list attribute which if set False will not include the message in the admin notice. This will be in the next release. In the mean time, you can set the list's `Admin immed notify` setting to No to not send the immediate notice and only send the daily summary, but this doesn't completely solve the issue as sometimes the Subject: of the held message contains things that will trigger spam/malware filters. -- 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: content filtering in version 3.1

by Mark Sapiro

On 12/12/19 6:36 AM, Dieter Leupold via Mailman-users wrote: > Hi, > > I'm new to MM3. I installed version 3.1.1 on Ubuntu 18.04. All looks > fine. But i miss the setting "pass_mime_types" at content filtering. The settings are there in Mailman core but not exposed in Postorius. You can set them via `mailman shell`. MM 2.1 settings map to MM 3 as: filter_mime_types -> filter_types pass_mime_types -> pass_types filter_filename_extensions -> filter_extensions pass_filename_extensions -> pass_extensions collapse_alternatives -> collapse_alternatives * convert_html_to_plaintext -> convert_html_to_plaintext * filter_action -> filter_action * in Postorius Settings -> Alter Messages The mailman import21 command will properly import these settings when importing a Mailman 2.1 list. > Also i don't find the settings for bounce processing. Are these features > no longer supported at version 3.1.1? Bounce processing is not yet implemented in MM 2.1. See <https://gitlab.com/mailman/mailman/issues/343>. There was a recent GSOC project to address this. See <https://gitlab.com/mailman/mailman/merge_requests/538>. I don't know how close this is to being ready. -- 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: HyperKitty failure

by Mark Sapiro

On 12/30/21 1:30 PM, William Oliver wrote: > On Thu, 2021-12-30 at 21:19 +0000, horvath.arpad.szfvar(a)gmail.com > wrote: >> Hi, >> >> I try to connect mailman3 to hyperkitty, but there is no success so >> far. You can see the details below. How can I solve the problem? >> >> As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on >> the same server, so I guess localhost won't work. >> >> In mailman-hyperkitty.cfg there is a line: >> >> base_url: http://lists.xxx.hu/hyperkitty/ As noted in the thread that William references and also the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… the issue is probably that the above http url is being redirected to https and losing POST data. Set the above to base_url: https://lists.xxx.hu/hyperkitty/ > [snip] > > I'm no expert, but here's a previous discussion I found: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Mark Sapiro

On 1/6/22 12:52 PM, Stephen Daniel wrote: > > Sendgrid requires that the "From:" address on any email reference an > authenticated domain. > > In the old mailman2 implementation, emails sent by mailman are listed as > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > validated domain. > > However, in my mailman3 implementation, the From: header lists the original > email's sender. Sendgrid rejects this because the original email's > sender's address is not one of the validated domains. > > How do I configure mailman3 to generate headers in the same style as the > old mailman2 implementation? In the list's Settings -> DMARC mitigations, set DMARC mitigation action to Rrplace From: with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Lost posting in archives

by Mark Sapiro

On 1/21/22 3:06 PM, Axel Rau wrote: > I created a list, did migration from 2.1 and run update_index_one_list. > Then I posted a test mail to the list and it got distributed and was seen in the archive. > Now 2 days later it does no longer show up in the archive. > > What is going on here? > May this have to do with > HYPERKITTY_RENDER_INLINE_IMAGE > which I have turned on meanwhile. It may. Is there anything in Django's log about this? If you have the original message from the list, can you go to the URL in the Archived-At: header? is the message in the hyperkitty_email table in the database? E.g., SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx'; (xxx is the value of the Message-ID-Hash: header from the message) If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > > For the list I am talking about: > - Default action to take when a member posts to the list is set to "Hold for moderation" > - Default action to take when a non-member posts to the list is set to "Hold for moderation" > - When I am viewing all users, the migrated ones are set to Moderation Action: "Hold for moderation". The mass-added ones post-migration are set to Moderation Action: "None" > - When a mass-added post-migration user sent an email to the list it passed through without being held. This should not happen. In the message as delivered to the list what do you see in the X-Mailman-Rule-Misses: header and the X-Mailman-Rule-Hits: header if any? > Happy to check any logs if there might be something to hunt for. What if anything is in the lists Accept these non-members setting? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: Patch/kludge suggestion and a question on adding accepted addresses

by Mark Sapiro

On 04/24/2017 07:07 AM, David Krantz wrote: > On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: >> On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>> I have another question: In the old mailman you could add accepted >>> senders without adding them to the list. Is that possible in Mailman >>> 3/Postorius? >> >> You do this by creating a "nonmember" subscription for the sender, and then >> setting that member's moderation_action to Action.accept. > > Okay. I see no way of doing that in my instance of Postorius but in > this case it is okay to do it in the command prompt. Yes. There are still quite a few things that aren't yet exposed in Postorius and probably some not yet exposed in the rest API. In these cases you have to resort to mailman shell (aka mailman withlist). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

[MM3-users] Re: LMTP not listening

by Mark Sapiro

On 11/24/2017 04:40 AM, Bartosz Sawicki wrote: > > But messages send to the list address are not delivered to the list :( I've > started to investigate whats happening and realize that Postfix can not > connect to mailman using LMTP. It seems that mailman is not listening on > port 8024. > > Nov 24 13:12:31 lists postfix/lmtp[2737]: connect to > 127.0.0.1[127.0.0.1]:8024: Connection refused > > I've checked log files, but haven't realize anything unusual . Any ideas > where I could try to find cause of the problem ? Is Mailman, particularly the lmtp runner, running? $ ps -fwwu mailman|grep lmtp mailman 19107 19085 0 Nov16 ? 00:00:44 /usr/local/bin/python3 /usr/local/bin/runner -C /opt/mailman/mailman-bundler/deployment/mailman.cfg --runner=lmtp:0:1 If so, where is it listening $ sudo netstat -lntp|grep 19107 tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 19107/python3 where the 19107 in the grep is the PIP of the lmtp runner. If that's all OK, is there a firewall (iptables or ??) thats not allowing access to localhost:8024? -- 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: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/13/21 2:27 PM, Odhiambo Washington wrote: > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > > May I ask if this is a typo? > I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. > So is this new one version 3.3.3 or 3.3.5? The text you are quoting is from the Feb 2 announcement <https://mail.python.org/archives/list/mailman-announce@python.org/message/N…> of the release of Mailman core 3.3.3. Mailman 3.3.4 was released and announced at https://mail.python.org/archives/list/mailman-announce@python.org/message/H… on March 21 and is the current release. There is no "new one". -- 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: templates

by Mark Sapiro

On 5/4/23 11:15, Christian via Mailman-users wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Without further information, I can't say more than that. -- 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: Database permission problem?

by Mark Sapiro

On 10/15/24 14:45, Bill Oliver wrote: > > In any case, here it is changed back: > > ls -l > total 68 > -rw-rw-r-- 1 mailman mailman 0 Oct 15 12:53 postfic_vmap.db > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfic_vmap.db.db Were these created manually? They should not be there. Likewise the .db.db files below. > -rw-rw---- 1 mailman mailman 353 Oct 15 13:37 postfix_domains > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_domains.db > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfix_domains.db.db > -rw-rw---- 1 mailman mailman 1155 Oct 15 13:37 postfix_lmtp > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_lmtp.db > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfix_lmtp.db.db > -rw-rw---- 1 mailman mailman 1118 Oct 15 13:37 postfix_vmap > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_vmap.db Does Postfix have read and search ('x') on all of /opt, /opt/mailman, /opt/mailman/mm, /opt/mailman/mm/var and /opt/mailman/mm/var/data? Perhaps there is a SELinux issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Message getting held due to max number of recipients and maximum message size

by Mark Sapiro

On 9/22/23 14:56, Wong, Wesley wrote: > I can confirm that the list was set to 0 for max recipients and message size. In addition, I checked the base.py and the defaults are the ones in the message. If I went ahead and modified the settings in base.py, would this immediately to all existing lists in Mailman? No. It would only affect lists created after you did that. I suggest the following mailman shell interaction ``` $ ./mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager): ... if (mlist.max_num_recipients == 10 and ... mlist.max_message_size == 40): ... print(mlist.list_id) ... ``` This will print the list ids of all lists with max_num_recipients = 10 and max_message_size = 40 Your held message notice is for one of those lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

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

by Mark Sapiro

On 12/18/23 12:18 PM, eboltz(a)lhtservices.com wrote: > Mark, > > I don't think the setup will work, as the client uses O365 for the emails and doesn't appear to like the virtual lists domain on the MM3 server. I've tried both using the O365 email connector as well Smtp2Go, both have the same issue with headers. > > real email domain = example.org > MM3 virtual domain = lists.example.org Actually, lists.example.org is a real email domain. > The FROM: header is always what's causing the issue, plus it doesn't like any external emails as it can't send held messages or posts to users outside of the example.org domain. If you want to use these 3rd party smtp relays, you have to configure them to accept mail from the lists.example.org domain. It should not be difficult, but it is not a Mailman issue. It is strictly an issue with configuring the 3rd party relay to accept the mail. -- 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: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/5/24 10:30, Odhiambo Washington via Mailman-users wrote: > > Actually, what I mean is that CF is proxying requests to the host named > m3-lists.kictanet.or.ke. > I do not have any configuration other than DNS proxying at CF. ``` dig a mm3-lists.kictanet.or.ke ... mm3-lists.kictanet.or.ke. 300 IN A 172.67.167.73 mm3-lists.kictanet.or.ke. 300 IN A 104.21.11.217 ``` Both of those are cloudflare IPs, and why 2? > So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP who > you talk to and it in turn talks to the host directly. And how is that configured? > So the IP address you see in the logs is CF's IP address, not yours, not > mine and CF are doing some caching. That's why > they are requesting for expired files. Why is cloudfare trying to access /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css locally if all it is doing is proxying the request to the actual mailman server? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Login confusion

by Mark Sapiro

On 2/11/25 01:26, Stephen J. Turnbull wrote: > > That will work in the short run, but I'm not sure that's a long-term > solution. It's not clear to me that allauth won't do the same thing > again. Allauth since 0.62.0 and better since 0.63.0 no longer does this. See https://codeberg.org/allauth/django-allauth/src/branch/main/ChangeLog.rst#s… > > Could I have achieved the same deletion using the REST interface? > > I don't know. I would think not. That's correct. The issue is in the account_emailaddress database table which is an allauth table that Mailman core and hence the REST api know nothing about. Our latest recommendation is django-allauth>=65.4, but that requires changes, see https://gitlab.com/mailman/django-mailman3/-/merge_requests/316 and https://gitlab.com/mailman/mailman-web/-/merge_requests/58 although the changes only affect testing and a deprecation warning. Also, installing that django-allauth version may result in upgrading Django to a version which doesn't support django-haystack<3.3.0 and may also require manually upgrading django-haystack. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: How to separate bans for sending emails to lists and subscribing to them

by Mark Sapiro

On 5/29/19 9:29 AM, Nathan Dixon wrote: > Hi, > Our requirements for using Mailman are that we can have non-members send an > email to a list from any domain name, but only people who's email addresses > match a list of specific domains should be able to actually subscribe to > those lists. > > I can't seem to find any way of doing this. Any ideas? > > I have tried using the bans (global and on each list) but these appear to > stop all subscriptions and emails being sent to or from a list if the > address matches a ban. Right. The default posting rules chain includes 'banned-address' which discards posts from banned addresses. You can work around this by creating a new chain based on mailman/chains/builtin.py but without the 'banned-address' rule and setting the list's posting_chain to use 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: If you delete a list but not the HyperKitty archive

by Mark Sapiro

On 1/4/22 6:45 AM, Philip Colmer wrote: > > So ... should the archive be deleted when the list is deleted and it is a > bug that it isn't? Or is it expected that access to the archive is "frozen" > once a list is deleted? It is often desired to have a public archive available after the corresponding list has been deleted. Even for a private archive, it may be desirable for site admins to have access. Furthermore, a list might not even have a HyperKitty archive in the first place. Thus, what to do about a HyperKitty archive (or prototype archive or ...) when a list is deleted is an administrative decision and is best left up to the site admins to do it or not. As you note with a private archive, former members no longer have access when the list is gone, but unless an attempt throws some uncaught exception, that is not a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/26/22 07:08, Odhiambo Washington wrote: > > So it seems your WSGIDaemonProcess is defined somewhere outside the VHOST, > right? Or it wasn't necessary? > And what does your urls.py look like? Eggert's configuration is for uWSGI. This is completely different from Apache mod_wsgi. Background: Python PEP 333 defines the Python Web Server Gateway Interface (WSGI) which is a protocol for communication between web servers and applications. Django is one such WSGI application. Basic web servers typically do not support WSGI directly but need some kind of intermediary. Apache mod_wsgi is an Apache module that extends Apache to communicate with WSGI applications. Both uWSGI and gunicorn are separate applications that can receive http requests via proxy from a web server and communicate them to a WSGI application and receive responses from the application and return them to the web server. Thus Apache mod_wsgi, uWSGI ang gunicorn are three separate ways of providing the connection between the web server and Django (or other WSGI applications), each with their own separate configuration requirements. -- 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: Archive search failing on one list

by Mark Sapiro

On 9/23/23 19:19, Mark wrote: > > Yes, the query returns a result and the case in "name" matches that in > the query ... > > select * from hyperkitty_mailinglist where name like 'listname(a)domain.com' > > id | 91 > name | listname(a)domain.com > display_name | Listname > description | ... > subject_prefix | [Listname] > archive_policy | 1 > created_at | 2023-09-21 08:55:36.385239+2 > list_id | listname(a)domain.com Is that really what you get for list_id? It should have a dot, not at as listname.domain.com. What if you do something like the following where django-admin is whatever command you use for the Django admin command. ``` $ django-admin shell Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models.mailinglist import MailingList >>> mlist_name = 'listname(a)domain.com' >>> mlist = MailingList.objects.get(name=mlist_name) >>> mlist <MailingList listname(a)domain.com (listname.domain.com)> >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: out queue backlog and delivery rate

by Mark Sapiro

On 4/8/22 09:47, dancab(a)caltech.edu wrote: > For anyone coming across this thread. It seems increasing the runners did the job for us. The smtp.log is now showing smaller lists being completely processed while larger lists are still in progress of sending out to members. > > We edited the mailman.cfg to include the following and the mailman stop; mailman start > > [runner.in] > class: mailman.runners.incoming.IncomingRunner > instances: 2 There's probably no issue that would be helped by increasing in runner instances. > [runner.out] > class: mailman.runners.outgoing.OutgoingRunner > instances: 2 I would suggest larger, 4 or even 8. This is not a single queue/multiple server setup. It is multiple queue/multiple server. I.e. The queue entries are named based on a hash of the message and each instance processes its own slice of the hash space. So, with 2 slices and a large recipient message being processed, there's a 50% chance that the next message will wind up waiting. -- 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: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? When pip is doing an upgrade of the xyz package, it renames the existing package as ~yz and then ultimately deletes the old ~yz package after successfully installing the new xyz. In this case, the upgrade was aborted because of the Django<3.1 constraint in mailman-web and apparently pip then installed Django<3.1 and left the ~jango* directories behind. -- 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: Where to configure 'hostname' used in 'From:'-header?

by Mark Sapiro

On 3/10/23 01:55, Dmitri Heerdegen wrote: > > I've recently installed MM3 with Exim4 on, say, subdomain.myhost.tld > and configured MM3 to use lists.someotherdomain.tld as web host and mail > host. > Thus, the mailman.cfg contains: > > [mta] > smtp_host: lists.someotherdomain.tld > > When I send a message to test(a)lists.someotherdomain.tld it gets > delivered, however the 'From:'-header becomes "test(a)subdomain.myhost.tld". The From: should be unchanged from the incoming post unless the list is anonymous or DMARC mitigations are applied. In the case of anonymous lists, the From should be the list's address and in the case of DMARC mitigations it should be something like User Name via listname <list-address>. In either case, the list address should be list-name@list-domain where list-domain is the list's email domain. If the address is being rewritten as test(a)subdomain.myhost.tld it is probably Exim doing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: A poll: "Delete this thread"

by Mark Sapiro

On 6/21/24 07:45, Sam Darwin via Mailman-users wrote: > Thanks for the replies. Not yet a close match to what I have installed. Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago "20200530". I may need to dig into the code and attempt to debug, line by line. "Oh, of course, in your settings refresh_cache needs to be set to 1, you have it set to 0", or something obscure like that. Or who knows. I manage 3 production mailman 3 servers and a development server. All 4 are running the current (as of today) heads of the GitLab branches installed in a venv. The versions of some dependencies probably vary, but all use django_q2-1.6.2 one uses Django-4.2.11, two use Django-4.2.6 and one uses Django-4.1.13. They all use memcached as the cache backend. I don't know what you mean by the refresh_cache setting as I have no information about such setting. All 4 servers are able to delete threads in HyperKitty with no issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 4 weeks

[MM3-users] Re: Installation -- error on mailman-web migrate

by Mark Sapiro

On 9/16/21 7:27 PM, Mark Dale via Mailman-users wrote: > > I note that in the sample "settings.py" file, there are lines that have the directory "web" in the file paths ... > > STATIC_ROOT = '/opt/mailman/web/static' > > LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' > > > ... but as yet there is no directory "web". This appears to be an error in the docs. With ``` [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here ``` The logs are in `/opt/mailman/mm/var/logs/`, not `/opt/mailman/web/logs/` and `STATIC_ROOT` should probably be `/opt/mailman/mm/static`, but it could also be `/opt/mailman/mm/var/static`. > Was I meant to create the directories "web/logs/" and the "mailmanweb.log" file at some point, or were they meant to get created during the mailman-web install process? They should be created automatically, but in `var_dir` which is `/opt/mailman/mm/var`, not `/opt/mailman/web` > Should the owner/group be "mailman"? Yes -- 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: REST API authorization failed

by Mark Sapiro

On 1/8/22 10:40 AM, Axel Rau wrote: > Hi all, > > I’m going to do a mailman2->3 migration in a FreeBSD jail. > I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. > The above error happens when I try to open the base url of my server with a browser > (is redirected to postorius/lists/) > (no errors on admin/ and hyperkitty urls) > > Same passwords and users in mailman.cfg: > > [webservice] > hostname: localhost > port: 8001 > use_https: no > admin_user: restadmin > admin_pass: ??? > > and in settings.py: > > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = ??? > > Its a long password, created as secret key by manage.py Is the password unquoted in mailman.cfg as admin_pass: ??? and quoted in settings.py as MAILMAN_REST_API_PASS = '???' Does the `mailman info` command report what you think for REST credentials? To you get an appropriate JSON response from wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/13/23 09:42, Joel Lord wrote: > Now I'm on one of the lists in digest mode and I can see that it's a > mess. Periodic digests are definitely NOT working, so I'll lay that out > here. > ... > root@host2:/# grep digests /var/log/cron.log > Jun 11 23:00:01 host2 CRON[1632765]: (lists) CMD (/usr/local/bin/mailman > digests --periodic) > Jun 12 23:00:01 host2 CRON[2177286]: (lists) CMD (/usr/local/bin/mailman > digests --periodic) OK. > root@host2:/home/members/directory# su - lists > lists@host2:~$ /usr/local/bin/mailman digests --periodic > lists@host2:~$ ls var/lists/<list>/ > digest.mmdf If there is nothing in Mailman's mailman.log, I don't know what the issue is unless the list's digest_send_periodic flag is False. > How can I try and track this down? Try manually running ``` /usr/local/bin/mailman digests --periodic --verbose ``` to get more info. Also try ``` /usr/local/bin/mailman digests --send --verbose ``` to see what it reports and whether it sends the digest. -- 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: Execution of msgfmt failed when performing post upgrade steps

by Mark Sapiro

On 9/15/19 5:19 AM, Torge Riedel wrote: > > When runnin the post-upgrade-script I get the following error message: > > Execution of msgfmt failed: > /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:630: > duplicate message definition... > /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:273: > ...this is the location of the first definition > msgfmt: found 1 fatal error > > Not sure whether this is an error of MM3 or one of its dependency packages. The file hyperkitty/locale/nb_NO/LC_MESSAGES/django.po does contain a duplicate definition. This is a bug. lines 270,273 are: #: templates/hyperkitty/fragments/month_list.html:78 #: templates/hyperkitty/overview.html:75 msgid "All Threads" msgstr "" and lines 629,631 are: #: templates/hyperkitty/overview.html:75 msgid "All Threads" msgstr "Alle tråder" You can just delete lines 272,273 but if you want to be really fussy, you can delete lines 629,631 and change line 273 to msgstr "Alle tråder" See <https://gitlab.com/mailman/hyperkitty/merge_requests/185> -- 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: Cron of Mailman notify is not working

by Mark Sapiro

On 1/28/20 3:03 AM, Shashikanth Komandoor wrote: > Hello, > > With your help, I was able to setup mailman 3.3 on my RHEL 7.5 > machine and running well and good. > > For daily notification I have added the below line in the crontab: > > 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify > > But this cron job is not working while I was able to run the same > command manually at my CLI. Into exactly what crontab did you put it? That is the correct line if you put it in the mailman user's crontab, but if you put it in a system crontag, e.g./etc/cron.d/mailman, it needs a 'user_name' argument between the date/time fields and the commands. E.g., 00 08 * * * mailman /var/lib/mailman/venv3/bin/mailman notify although the Mailman user may not be 'mailman' in your case. You should see some errors from cron in /var/log/syslog at 08:00 that would give you a hint. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

by Mark Sapiro

On 9/23/20 7:02 AM, Brian Carpenter wrote: > On 9/23/20 7:33 AM, r.woithe(a)callassoftware.com wrote: >> Thank u for the hint ! >> The only one is that Ubuntu uses uWSGI and not gunicorn. >> I set the para socket-timeout = XXX. >> I hope thats the right parameter. >> _________________________________________ > > I think Mailman 3 core still has its own gunicorn process that it runs. > Brian is correct. The REST API does not use the web server and uWSGI is not involved. Since Mailman core 3.3.0, the REST API is served by Gunicorn processes that have nothing to do with the web server. The time limit for these processes needs to be set as described at <https://wiki.list.org/x/17892072>. Prior to 3.3.0, the REST API used the standard library wsgiref module which doesn't have timeouts. Since you said you have Mailman core 3.2.2, this may not be a REST timeout at all. -- 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: MIMEDefang to fix footers

by Mark Sapiro

On 11/13/20 9:51 AM, Ryan Morash wrote: > Does anyone know how to use MIMEDefang to fix the footer as attachment issue when using Mailman3? I've seen several guides/scripts referring to its use with Mailman2, but I'm unsure of how they would match with Mailman 3. I don't use MIMEDefang and don't specifically recommend it, but I have looked at <https://stuff.mit.edu/~jik/software/mailman_mimedefang/>, and it seems that the only Mailman specific things involved in the installation and configuration of this script are the addition of the "MAILMAN_MIMEDEFANG" lines as the first and last lines of the footer template. The only thing Mailman 3 specific in that is how to edit the footer template. This can be done on a per-list basis via Postorius since 1.2.0 or more directly in Mailman core by setting URIs, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or by creating templates in Mailman's var/templates directory, see <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…>. -- 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: mailman3-web language preference and translation settings

by Mark Sapiro

On 12/6/23 15:54, Nils wrote: > Thanks for your help, Mark. I've already tried that and it gave me this > message: > > # sudo -u www-data python3 /usr/bin/django-admin compilemessages > --pythonpath /usr/share/mailman3-web --settings settings > CommandError: This script should be run from the Django Git checkout or > your project or app tree, or with the settings module specified. > > I'm working on ubuntu and I don't have (venv)$ The other commands (migrate, collectstatic and compress) worked fine. Kind regards I don't know why this fails like that, particularly since the same thing works for migrate, collectstatic and compress. The only thing I can think of is you may need to cd to the directory containing django/ django_mailman3/ postorius/ and /hyperkitty before doing the above. This may be something like /usr/lib/python3.x/site-packages. If that doesn't work, since I think you are using the Debian/Ubuntu package, I suggest you try Debian for help. -- 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: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/18/20 4:15 AM, tlhackque via Mailman-users wrote: >> > I considered including the regex in each message, but that seemed > redundant - and potentially long. Thus the pointer. Perhaps number the > rules for each list, and use that index? The ROWID would seem to be a > candidate for the number. The number would be the `position` value from the headermatch table for the matched rule, but that's unreliable as the rules can be reordered (or the particular rule even deleted) between the rule being applied to a message and subsequently looking for the rule. ... > I may have some details wrong - I found mm3 not ready for my needs and > am thus out of date - but I hope the high level approach that I outlined > is useful. It seems to me that this is a great deal of additional implementation to solve a non-existent problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 11/22/24 13:46, Joshua Bushe wrote: > Both "Hide Inactive" and "Hide Private" are unchecked. I can view the lists without any issues, but when I click on a specific list, I see three loading icons. On the left side, there's an "All Threads" option, which lets me view all the archives for the list. > > My question is: why don’t the list appear in the "list overview"? I'm still confused. You say "I can view the lists without any issues", but then you say 'why don’t the list appear in the "list overview"?' By "list overview" I thought you meant a page like https://lists.mailman3.org/archives/, but now I think you see your lists on that page and the page you call "list overview" is one like https://lists.mailman3.org/archives/list/dummy@mailman3.org/. If your question is why don't you see a list of threads on that page, it only shows threads with posts in the last 30 days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 12/31/24 06:07, monochromec via Mailman-users wrote: > Further RCA reveals the fact that the archiver runner tries to archive the same message over and over again - hence the overhead during pipeline processing. The total # of attempts reaches well into five digits for a single message. This is not directly related to the pipeline runner issues but they may have the same underlying cause. All the pipeline runner does is put the message in the archive queue. It's the archive runner that is doing all these retries. However, the pipeline runner in processing the rfc_2369.py handler is also communicating with hyperkitty to get the values for the List-Archive: and Archived-At: headers. You need to focus on the communication between mailman_hyperkitty and HyperKitty. If there are significant delays there, it could explain your pipeline runner issue. Btw, I see https://gitlab.com/mailman/mailman/-/issues/1189 is also from you. I wondered at the time why you were trying to increase the number of pipeline runners which is not something that would normally be required. -- 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: Unknown templates being used

by Mark Sapiro

On 2/14/21 1:47 PM, Tom Stoddard wrote: > > On 2/14/2021 1:31 PM, Mark Sapiro wrote: >> >> I.e., we know it should be a template, but it currently isn't. > > That's fine but it doesn't explain why I have received messages that > were built by a template for some subscription requests. In other words, > why is there a template being used in some instances and on others a > "mailman notify command" is being used? The notice sent at the time the request is generated is built from a template. The `mailman notify` command is intended to be run periodically via cron set up by the site admins to send a summary of then outstanding requests to the list admins. You should receive the initial notice built from a template of each request as it is generated as long as the list is sent to send immediate notices. The notice sent by `mailman notify` is a summary of all requests outstanding at that time. If all the requests have been handled by the time `mailman notify` is run, it won't send you anything. > Are there different methods for people to use to request a subscription? Yes, but that's not the explanation for your question. Subscription can be requested via a web UI or via email to the list-join or list-subscribe address or via a join or subscribe command sent to the list-request address, but all methods result in the same notices to the admin. > By the way, Brian at EMWD has been extremely helpful to me already and, > as he stated, he informed me that this is an issue with Mailman 3 so I > thought I'd try getting the answer directly from this group. I agree and appreciate that Brian is very supportive. In my initial reply, it was not clear to me that Brian had referred you here which is the only reason I pointed out that he was your primary line of support. -- 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: Linking to a forum thread from a (news) website.

by Mark Sapiro

On 9/25/19 2:29 AM, Paul Arenson wrote: > SOLUTION > I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. ... > QUESTION > Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? Re: has nothing to do with it. Replies are not threaded by subject. Replies are threaded by In-Reply-To: and References: headers in the reply. These headers are generated by the sending MUA (mail client) when replying to a message. If you send a 'new' message without those headers, it will be a new thread regardless of whether or not the Subject: matches with or without the Re:. Also, there are broken MUAs that don't properly generate In-Reply-To: and References: headers and replies from these MUAs will never be properly threaded. -- 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: Cannot start lmtp runner due to error while attempting to bind on address ('127.0.0.1', 8024): address already in use

by Mark Sapiro

On 12/2/19 5:04 AM, actionmystique(a)gmail.com wrote: > > Of course the port is already in use: it is used by dovecot. > ``` > tcp6 0 0 ::1:8024 :::* LISTEN 0 1317360 129620/dovecot > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 0 1316324 129620/dovecot > ``` > I must be missing something. What is Dovecot listening for on the lmtp port? If this is Postfix communicating with Dovecot as the LDA or for address verification and using TCP port 8024, you have at least two choices. You can have Postfix/Dovecot communicate via a unix socket instead or you can configure Mailman to use a different port. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> which says in part: lmtp_port is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using 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, 4 months

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

by Mark Sapiro

On 1/30/24 10:46, andrea.janna.unipd(a)gmail.com wrote: > Same issue at my site. > I'm using mailman3 3.3.8 shipped with Debian 12. Then your first line of support should be Debian. See <https://wiki.list.org/x/12812344> > To debug the problem I stopped apache, cron, postfix and mailman3-web services. > But I still get the mariadb aborted connection warnings every 5 minutes. The only thing that runs every 5 minutes is `mailman gatenews`. The issue may be with that. You could try running it manually via ``` _MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews ``` ... > The regular mailman log doesn't show anything and I'm not sure about how to enable an appropriate debug log for mailman. Mailman has a number of virtual logs, most of which are written to the file mailman.log. You can enable debug level for those with ``` [logging.template] level:debug ``` See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for more info on logging. -- 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: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > Hi Team, > > Today, I found an error message like "Multiple rows were found > for one_or_none()" when a hold message is approved for a list. Until > yesterday the mails were accepted and delivered fine. We have seen this issue before. See <https://gitlab.com/mailman/mailman/-/issues/657>. There are also multiple threads on it in the archive, e.g., <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. We don't know how it happens, but the issue is that the `listarchiver` table in the database has multiple `mhonarc` entries for the same `mailing_list_id`. You can see the problem with the query select * from listarchiver where name = 'mhonarc'; There will be two entries with the same `mailing_list_id` and deleting one of them will fix this and you can run `mailman unshunt` to reprocess the shunted messages. The above referenced issue contains a script that can be run to remove the extra entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/9/20 6:39 PM, matthew(a)alberti.us wrote: > > For core, the connection string seems to accept a tailing > "?charset=utf8&use_unicode=1" per > https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So > for core, maybe just updating the connection string to include > "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the > recommend encoding... maybe that should be updated? I'm in the process of doing that update. > Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is > recommended, and it needs to be explicitly identified in the database > settings for BOTH core and web, and probably somehow at database creation > time? It's not as critical for core because barring things like 4-byte utf-8 unicode graphics in list configurations, core doesn't store anything like that in its tables. The major issue is with HyperKitty where messages have emojis and other 4-byte utf-8 encodings in message subjects and bodies. -- 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: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/21/23 17:30, Thomas Ward wrote: > > MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). > > If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 09:08, Wikinaut wrote: >>> In the Postorius held messages view, click on the message's subject to >> open a dialog showing the messages content > > Dear Mark, sorry: > How should I know this? Well, the subject of the message in the held messages view looks like a link. Maybe click it once to see what it does. > I'd rather prefer to have these both changes: > > i) relabel the existing one od three buttons from "accept" to "accept once" ; and > ii) add a fourth button "accept all messages from this sender (i.e. add to white list)" That wouldn't include options like "discard further posts from this user", "reject further posts from this user" and perhaps other possibilities. If I were going to do anything, it would probably be adding a line above the list of held messages saying something like "Click the message's subject for more options." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/26/22 21:29, Jan Eden via Mailman-users wrote: > > Replicating this setup on the server solved the KeyError problem, > everything works now! I just wonder why these uwsgi parameters need to > be passed explicitly when using a file socket, but not with a http > socket. You are doing more than just switching from a tcp socket to a unix socket. You are also switching from communicating with uwsgi via http protocol to uwsgi protocol. > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > files when using the virtualenv installation instructions > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, not mailman-web. If you want, you could put mailman-hyperkitty.cfg in /etc/mailman3/ by putting ``` configuration: /etc/mailman3/mailman-hyperkitty.cfg ``` in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Mark Sapiro

On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: > I noticed some unusual behavior in Mailman3 stable release on PyPI and > such. Namely, there are instances where replies are being processed and > the prefix tags are simply being **lost** and dropped by Mailman3, > instead of being properly prepended where they're supposed to go. > > Is this a known bug or does it need its own bug in the gitlab tracker? Are you sure you are looking at messages from the list and not messages received by direct To:, CC: or BCC:? I have never seen an issue where list posts would sometimes have the subject prefix prepended and sometimes not. If you are seeing this, we would ideally like to see a thread in the hyperkitty archive where some of the messages have the prefix in the message view and some don't, or at least see some of the raw Subject: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/17/24 16:57, Mark wrote: > > I can see the French text for the "Password Reset Email" in the > django.po file. And running the compilemessages command reports the > "django.po" for French is okay and up to date. Should I be recompiling > the ".mo" file? No, It's fine. The issue is the language context for this message has nothing to do with any Mailman list's preferred language. Again, see https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… If all the lists on your server are French, you could set LANGUAGE_CODE = 'fr' in your Django settings. Otherwise, the user's browser has to include an Accept-Language: header specifying French as the most preferred language in it's request. Also note the ordering of SessionMiddleware, LocaleMiddleware and CommonMiddleware in the above doc. I have recently updated the various places where we suggest or supply MIDDLEWARE settings, but you may find that your settings have LocaleMiddleware after CommonMiddleware and you should fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: Migrate from mysql to postgresql

by Mark Sapiro

On 03/17/2018 01:44 PM, Bjoern Franke wrote: > Hi, > > is it possible to migrate a mailman3-mysql-database to a > postgresql-database? > > I tried to convert it with pgloader, but some identifiers had to be cut off: > _address_id); > 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner > idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e > wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac > gekrzt I suspect the issue is due to the way Mailman supports different databases via SQLAlchemy. The bottom line is the table and column specifications are based on the Mailman database models, but are database specific. If I were doing this, I would dump the data from MySQL, but rather than using the CREATE TABLE queries from the dump, I would let Mailman create a new PostgreSQL database and then just load the existing tables from the MySQL dump. However, that may all be irrelevant. I don't know which table/column that specific item comes from, but it appears just visually that idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e is already truncated so further truncating it to idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac may not be a problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

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

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > > 1. If I do not set up 'individual' or 'full' personalisation, all is > well and the default footer templates are expanded as expected. However > setting up personalisation causes template expansion to fail > completely, and messages get sent with a blank expansion. Your mailman-debug.patch makes changes to mailman/handlers/decorate.py including wrapping all the relevant code in a try:/except: that logs any exception. If you set the level for logging.error to debug, what do you get in the log? This issue doesn't occur in the unpatched code on my servers - personalized footers work fine - so I think the problem must be something in your patch. > 2. I would find the postorius UI much easier to cope with if the > default template was 'populated' into the UI wherever it was non-blank, > rather than the UI starting off as if no templates were defined at all. This is <https://gitlab.com/mailman/postorius/-/issues/366>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: mailman-suite: Error 500 on Lists /setting/ pages

by Mark Sapiro

On 11/18/20 8:43 AM, ljsbw-it(a)riseup.net wrote: > I just installed Mailman3 (mailman-suite) on my Server following these instructions: https://lab.uberspace.de/guide_mailman-3.html Please see <https://wiki.list.org/x/12812344> > and everything works fine so far. I can create lists, subscribe people and send mails through lists but when I click the settings button and get redirected to /postorius/lists/listname/settings/ i get an Error 500 message. I couldn't find anything in the logs except the uwsgi log: > [pid: 20568|app: 0|req: 62/62] 100.64.115.1 () {48 vars in 1052 bytes} [Wed Nov 18 16:27:59 2020] GET /postorius/lists/listname/settings/ => generated 1102 bytes in 1438 msecs (HTTP/1.1 500) 6 headers in 209 bytes (1 switches on core 0) I think that uwsgi log message just refers to the delivery of the error page to your browser. What other logs are you looking at? There should be something in Mailman core's mailman.log or the Django log whose location is defined in settings(-local).py, probably mailman-suite/logs/mailmansuite.log. -- 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: messages with attachments, without text discarded silently

by Mark Sapiro

On 1/27/25 12:35, Schulz via Mailman-users wrote: > Using the current mailman version, I can reproduce the following: > - send a text-formatted email with attachment but without text body to a list. > - the msg will be received by mailman > - the msg shows up in shunt, the log shows: > ile "/usr/lib/python3.12/email/message.py", line 343, in set_payload > payload = payload.encode(charset.output_charset, 'surrogateescape') > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) Please provide the full traceback and the MIME structure of the message. > an attempt to unpickle the file leads to the same error. > I know it's uncommon to send emails without txt but with attachments - but it may happen; at least we would welcome an error message. Without more of the traceback I can't be sure which handler is doing this and without the MIME structure I can't be sure 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

2 months, 3 weeks

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/29/2017 03:46 PM, Barry Warsaw wrote: > On Mar 30, 2017, at 12:34 AM, David Krantz wrote: > >> When starting this as the recipe seems reasonable I find that I have >> no reliable source for git links for the parts. Some of the git links >> I find are marked with "do not use" so it is a bit hard having >> confidence in selecting one of the others. > > All the Mailman 3 suite subprojects are listed here: > > https://gitlab.com/mailman > > Those project links will take you to the active git repositories. The only > one you should not use is mailman-bundler. To be more specific, the projects that are required for a fully functioning Mailman installation with Postorius and Hyperkitty are Mailman (the core) Hyperkitty (the archiver) Postorius (the web list management UI) django-mailman3 (common django things used by Postorius and Hyperkitty) MailmanClient (python bindings for the core REST API used by Postorius and Hyperkitty) HyperKitty - Mailman plugin (plugin for the core to communicate with Hyperkitty) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: configure Mysql and postfix on mailman3

by Mark Sapiro

On 02/20/2018 10:01 AM, Abhilash Raj wrote: > > One _hack_ that I can think of is that when using maps for postfix, Core calls the "postmap" command to generate the maps from the files that it generates. You can potentially provide a script that updates the MySQL database with the same configuration instead of generating maps and specify that script in configuration to be called by Core instead of "postmap". More information on how to do this. On mail.python.org we want to do some manipulations to the various maps, so we have a script to do this. The first step is in your mailman.cfg file, add an [mta] section if there isn't one and in that section add configuration: /path/to/your/postfix.cfg That file is a copy of mailman/config/postfix.cfg except you change the line postmap_command: /usr/sbin/postmap to postmap_command: /path/to/your/script While you could just edit mailman/config/postfix.cfg directly, this is not advisable as your edits will be lost in an upgrade. -- 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: Mailman core: basic internationalization howto?

by Mark Sapiro

On 10/04/2017 12:33 PM, thor.rustad(a)gmail.com wrote: > I finally got around to testing this setup. First I verified that the template in /var/templates/site/no was picked up when subscribing. Then I changed the text, and it stopped working. If I add one of these three Norwegian letters to list:user:action:subscribe.txt, I get the following in logs/mailman.log: > > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) Uncaught runner exception: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) ... > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 576, in _handle_confirmation_needed_events > msg = UserNotification(email_address, confirm_address, subject, text) > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", line 124, in __init__ > @public ??? > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) SHUNTING: 1507144721.896973+35dc93aa969a0934bf717ca07965b09924eca59d See my comment at <https://gitlab.com/mailman/mailman/issues/413#note_42453740>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

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

by Mark Sapiro

On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically it says > > "Pay attention to the config file output above and make sure that you see > /etc/mailman3/mailman.cfg there. If the config path is different, you should > make sure to create a new config file at /etc/mailman3/mailman.cfg and > re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) > [GCC 8.3.0] > config file: /opt/mailman/mm/mailman.cfg > db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: > > No matter what action I set for member posts (Hold for moderator, > Reject) they are always delivered. I don't know why this would be. Perhaps the member's moderation is set to Accept immediately - you can see this on ther member's options page in Postorius when logged in as a list owner. When the message is delivered, what are the X-Mailman-Rule-Hits: and X-Mailman-Rule-Misses: headers? > When I tried from a non-member email address, the message got held but > when I try to see it I get a Server Error (500) page. The log files shows: > > ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server > Error: /mailman3/lists/test.mydomain.com/held_messages > Traceback (most recent call last): ... > File > "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", > line 443, in held > moderation_reasons=entry['moderation_reasons'], > KeyError: u'moderation_reasons' This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> -- 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] dkim failing

by Mark Sapiro

On 10/15/18 8:37 PM, Abhijith PA via Mailman-users wrote: > > I am seeing dkim fail in mail that people send to lists > /dkim=fail reason="signature verification failed"/ > but it is not happening when the list solely sending mail to subscribers > (like digest, or subscribe/unsubscribe messages etc). I recently added a > new domain to the mailman3. After this I started noticing this issue. > Any help ? Are you saying the DKIM signature on the incoming post fails to validate in the post as sent from the list, or are you saying that a DKIM signature added by your MTA to the outgoing post fails to validate. If the former, this is probably expected. If your list does any content filtering, adds a subject prefix or adds a list header or footer, these transformations will break the incoming DKIM signature. This is why we offer DMARC mitigations. If the latter, you may be doing your own DKIM signing before Mailman applies transformations to the message. You need to sign the message on the way out, not before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 1:45 AM, Stefan Bauer wrote: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ... > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Others have found that removing the trailing slash from ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to make it ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixes the issue. -- 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: mass subscribers disablement!?

by Mark Sapiro

On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is > there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: How to delete non-users

by Mark Sapiro

On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Mark Sapiro

On 1/26/24 07:06, Stephen J. Turnbull wrote: > > I'm pretty sure it will install dependencies. I think (everything I > say below is based on reading the README.md from pipx's pypa.io repo, > so caveat installer) that the complexity that will arise is that (for > example) a naive approach like > > $ pipx install mailman > $ pipx install mailmanweb > $ pipx install postorius > $ pipx install hyperkitty > > will create 4 separate venvs with 3 copies of mailmanclient, 3 copies > of django-mailman3, and two copies of Django. But postorius and hyperkitty are dependencies of mailmanweb so only $ pipx install mailman $ pipx install mailmanweb should be required. This should put core in one venv and everything else in another without redundancy. > Besides the space > waste, there's also the small problem that mailmanweb won't have copies > of postorius and hyperkitty in its venv. But it will because they are dependencies of mailmanweb. -- 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: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 8/19/24 16:24, eyoelz--- via Mailman-users wrote: > Error: > Aug 19 15:06:10 xxx-rocky9 postfix/smtpd[153746]: NOQUEUE: reject: RCPT from xxxx.xxxxxx-xx.iphmx.com[xx.x.xx.xxx]: 550 5.1.1 <devops(a)xxx.xxx.edu>: Recipient address rejected: User unknown in local recipient table; from=<xxx(a)xxxx.edu> to=<xxx(a)xx.xx.edu> proto=ESMTP helo=<xx.xx-xx.iphmx.com> Is xx.xx.edu in to=<xxx(a)xx.xx.edu> The same as > main.cf > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > myhostname = xxx.xxx.edu xxx.xxx.edu in myhostname? > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydestination = $myhostname, mailman, localhost.localdomain, , localhost > relayhost = [xx.xx.xx.xx] > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > recipient_delimiter = + > inet_interfaces = all > inet_protocols = all > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp What is the content of postfix_lmtp? In particular is there an entry for xxx(a)xx.xx.edu? > local_recipient_maps =$alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains Is this the complete main.cf? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Domain in welcome message

by Mark Sapiro

On 02/19/2017 02:05 PM, Maadix wrote: > Hi, > I'm having problems with customizing welcome message > > It's working fine for > var/templates/site/en/welcome.txt > > but not for domains or lists , so maybe I'm doing something worng > > I'm using a subdomain as mail_host which is different from the URL Host. > > I've been trying all these combination, with no success: > > var/templates/domains/sub.example.com/en/welcome.txt > var/templates/lists/listname.sub.example.com/en/welcome.txt > var/templates/lists/listname(a)sub.example.com/en/welcome.txt > > I'm running mailman-bundler version 3.0.0 Templating has changed for MM 3.1, and I don't have a 3.0 platform available for testing, but as far as I can recall, the paths var/templates/domains/sub.example.com/en/welcome.txt and var/templates/lists/listname.sub.example.com/en/welcome.txt should be valid for domain and list specific templates and the precedence should be (high to low) list, domain, site, default. I don't know why it isn't 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

8 years, 2 months

[MM3-users] Re: leaving Sympa for MM3

by Mark Sapiro

On 2/20/20 3:12 PM, rance.hall(a)esu10.org wrote: > > Now for the question/hard part. Migrating list archives. > > In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. > > I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this? It shouldn't be hard. HyperKitty has a function to import archive mbox files. It would be a simple matter to use Python's mailbox module to convert your archive. Something like import mailbox md = mailbox.Maildir('path/to/maildir/directory', create=False) mb = mailbox.mbox('path/to/mbox', create=True) for msg in md: mb.add(msg) mb.close() md.close() Then just run hyperkitty_import to import the mbox. run something like django-admin hyperkitty_import --help for details. Note that if there are already archived messages you need to specify --since to import older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: New releases

by Mark Sapiro

On 9/11/20 8:19 PM, brylon(a)oit.rutgers.edu wrote: > I already have ruby-sass installed and the compress command used to work as expected prior to my upgrading to the latest core, postorius, hyperkitty versions using pip in my venv. > > Does It matter at all when performing the Django-admin commands whether I've activated the venv or not? I think I've tried running them both activated and deactivated to no avail, but any other suggestions? I don't think that's the issue here, but the venv should be active when you run the Django-admin commands. Looking more closely at the error, I see it says ``` File "/opt/mailman/mm/venv/lib/python3.6/site-packages/compressor/base.py", line 282, in precompile mod = import_module(mod_name) ... ModuleNotFoundError: No module named 'sass -t compressed {infile} {outfile}' ``` Thus it appears that compressor is trying to import 'sass -t compressed {infile} {outfile}' as a module instead of executing it as a command. What version of compressor is this? It is working for me on 4 sites with django_compressor-2.4, django_compressor-2.3 and django_compressor-2.2. -- 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: spanish localization

by Mark Sapiro

On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > But... here is a thing that I can not understand: If the source (the .po > file) is from november 7th, it doesn't matter how many times you > recompile it: the result will be the same. Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears that the weblate translation hasn't changed since that time. If there are issues in this mailman.po, they exist in weblate too and need to be fixed there. Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> and submit a merge request to add them to a mailman/templates/es/ directory. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 2:55 PM, Jens Günther wrote: > > When I want to get to Mailman Starting Page now I need to Enter the > following URL: https://mailman.xyz.de/mailman3/ to be directly > redirected as expected to > https://mailman.xyz.de/mailman3/postorius/lists/ -> works. > > Problem: When leave out the slash at the end and I ONLY enter the > following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly > redirected to a page, taht does not exist: > https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Huh? that is the same URL as the one above that you say works. Do you mean https://mailman.xyz.de/mailman/postorius/lists without the slash or what. > Where can I change this misbehaviour? In Apache-conf everything seems as > it'S in the docs, for the vHost I do not have any other custom settings. What is the exact content of your RedirectMatch or ReweriteRule or whatebver you are using? -- 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 archive issues (Hyperkitty)

by Mark Sapiro

On 6/7/21 11:54 PM, Kimmo L wrote: > Hi! > > Thanks for the support and help! > But so far i havent been successful with upgrading my postorius, hyperkitty and django pip packages from python2.7 to python3.5 or higher. As i understand, it was installed 2018 and has not been updated (because it has been working without any problem). Perhaps we can help with that. How are these installed now? What issues are you having when trying to upgrade. > Maybe the easiest way is to create a new deployment and somehow transfer data from old server to new one ? It's up to you which way to go. If you create a new deployment, I recommend following https://docs.mailman3.org/en/latest/install/virtualenv.html. You might also consider Xapian as the search engine - see https://docs.mailman3.org/en/latest/config-web.html#enable-full-text-search… and https://github.com/notanumber/xapian-haystack/tree/master Transferring the data is easy as long as the database is compatible - just dump and load, plus copy some files from Mailman's var/ directory. -- 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: multiple sites on a mailman3 server question

by Mark Sapiro

On 12/29/21 8:48 AM, William Oliver wrote: > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. If you are following https://docs.mailman3.org/en/latest/install/virtualenv.html you have ``` location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ``` in your nginx config and everything goes to uwsgi. What you want is to put those proxy directives in only the mailman locations as at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and then configure your document root so other locations are served from 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, 3 months

[MM3-users] Re: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- 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: Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`

by Mark Sapiro

On 12/22/23 10:34 AM, Wikinaut wrote: > Wheras my older lists handled these format apparently correctly, I now cannot add any more > > "Givenname Familyname" <mailaddress> ; or > Givenname Familyname <mailaddress> > > In any of these cases, only the part <mailaddress> is added. > > Is this strange behaviour know? > What can be done to have the correct function back to working again? There haven't been any changes to this. The issue is almost certainly that when subscribing "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> if there is no Mailman user/address for <mailaddress>, one will be created with display name `Givenname Familyname`, but if there is an existing user/address for <mailaddress>, its display name won't be changed. In this case, you can find the user at https://www.example.com/mailman3/users, click the user's Manage button and update its display name. -- 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: Legit login attempts yield, "An error occurred while processing your request."

by Mark Sapiro

On 8/14/24 3:18 PM, Greg Newby wrote: > > My primary question is: *How can I find out what's causing this*? > > I've looked in all the MM and web logfiles, by "tail -f" while generating > the error, and nothing is logged there. Apache logs shows something like > this: > > x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ > HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" > "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log. > I've come across this error while trying to do authentication-related > activities that worked before the reboot: Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/31/2018 11:57 AM, Peter Münster wrote: > On Wed, Jan 31 2018, Mark Sapiro wrote: > >>> I have verp_delivery_interval = 10 ... >> >> Which says only every 10th message will be VERPed. You want >> verp_delivery_interval = 1 to VERP every message. > > Hi, > > Why? The smtp relay host would get much more outgoing messages. With > verp_delivery_interval = 10, only 10% of the messages would be > personalized. Shouldn't this be enough to detect sooner or later, that a > recipient address is no more valid? Or is it important, to detect such > failure immediately? Yes, VERP does increase the number of SMTP transactions to deliver the mail from mailman to the outgoing MTA, but in general it has mush less effect on deliveries from the outgoing MTA to the recipient MXs, but with modern hardware, most people seem to find the added overhead of VERP to be minimal. Also, it is possible to have the MTA do the VERPing rather than Mailman. See <https://bugs.launchpad.net/mailman/+bug/558067> for a way to do this in Mailman 2.1. There's nothing for Mailman 3, but all that's needed is to configure Postfix to do it and add an appropriate mail_options= to the smtplib.SMTP.sendmail() calls to enable it. In any case, consider (assuming automated bounce processing is working, which it currently isn't) a list with bounce_info_stale_after = 7 days that gets even a post per day and has a member who is bouncing with a DSN that can't be successfully parsed for the member address (maybe because the bounce is from a forward to a different address) so only a VERPed bounce will be successfully scored. At some point a VERPed post bounces for this member and the member gets a bounce score of 1. Now, the next 9 posts to this list will not be VERPed and by the time the 10th post bounces it's more than a week since the first bounce and the score is reset so this member'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

7 years, 2 months

[MM3-users] Re: API privileges question for mailman3

by Mark Sapiro

On 10/14/21 12:41 PM, bob B wrote: > In mailman3 documentation it says: > "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost." > > So I just wanted to confirm there is no way to limit API access? For example I have a group that wants to use API access to mange their mail lists, but from what I can gather, if I give them access to the API they would have access to ALL the mail lists etc.. I would suspect this is even true if I give them their own domain? > > Is there anyway to limit access via the API to certain lists etc..... No, there isn't. If Postorius is not suitable for some reason, you would need to implement an application on the host to provide a user interface to the API with appropriate authentication and controls. There are some ideas but no actual code at <https://gitlab.com/mailman/lemme>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

On 6/26/22 08:07, Andy Smith wrote: > > On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > >> Just to be sure: for this feature, is it necessary to click on the >> subject and to choose in the drop-down list “Discard (no >> notification)”, or is it enough, on the .../held_messages page, to >> select the messages and click on “Discard”? > > Doing it from the held messages page will be a one-time thing; it is > only by clicking on the individual message that you can choose an action > for future messages from that address. In case the above is not clear, selecting the message and clicking Discard will only discard that message. To automatically discard all future messages from that sender, you need to set that (non-)member's moderation action to Discard which you can do by clicking on the subject and selecting the Discard moderation action from the dropdown list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Mailman 3 Hyperkitty indexes not being built

by Mark Sapiro

On 10/18/22 05:27, tom(a)gather.coop wrote: > My config looks like this: > > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': os.path.join(BASE_DIR, "fulltext_index"), > ... > I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. > > What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. > > Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… And answered there. You need to be running several things periodically via cron. For Mailman core, see https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs and for Django, see https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required. The particular job which updates the search index is the hyperkitty update_index job which in current HyperKitty is one of the hourly jobs. -- 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: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/6/21 2:00 AM, marcus.granath(a)gmail.com wrote: > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? My fault. Sorry for the confusion. I wrote: > Now, no one can post. To allow your set of users to post, you have > choices. The easy way but not secure against spoofing is to set the > Maderation Action for the three allowed members to List Default and toi > create a non-member for no-reply(a)abc.com and set it's moderation action > to List Default. That should have said "set the Moderation Action for the three allowed members to Defer or Default Processing (again two names for the same thing) and to create a non-member for no-reply(a)abc.com and set it's moderation action also to Defer or Default Processing." -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 2:10 PM, Marco Marinello wrote: > Dear Mark, > > configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. > > # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip > # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… It appears that https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… is the latest mailman-hyperkitty, but https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip is missing some commits. It has https://gitlab.com/mailman/hyperkitty/-/commit/79b22a23d3390db741a8233fa1ff… but is missing https://gitlab.com/mailman/hyperkitty/-/commit/ec9c8ed18798cf8f7e89dfaba001… which is very strange because it does seem to have https://gitlab.com/mailman/hyperkitty/-/commit/705bdbb2fb27be60d17ada7cba84… I Suggest you do pip install -U HyperKitty pip install -U mailman-hyperkitty which will get the latest packages from PyPI or if you want the heads from gitlab, pip install git+https://gitlab.com/mailman/HyperKitty.git pip install git+https://gitlab.com/mailman/mailman-hyperkitty.git -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 1/31/23 23:33, Odhiambo Washington wrote: > Is this a race condition? > > <CUT> > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django_extensions/management/commands/runjobs.py", > line 40, in runjobs > job().execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/jobs/update_and_clean_index.py", > line 37, in execute > run_with_lock(update_index, remove=True) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", > line 181, in run_with_lock > log.exception("Failed to update the fulltext index: %s", e) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 470, in __exit__ > self.unlock() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 420, in unlock > raise NotLockedError('Already unlocked') > flufl.lock._lockfile.NotLockedError: Already unlocked > <CUT> Yes, it is a race between the monthly hyperkitty update_and_clean_index job and the hourly hyperkitty update_index job -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Mark Sapiro

On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > Dear Users, > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > However > > (venv) $ mailman-web migrate > > fails with: > > from rest_framework import mixins, views > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > line 15, in <module> > from rest_framework.request import Request > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > line 17, in <module> > from django.http.multipartparser import parse_header > ImportError: cannot import name 'parse_header' from > 'django.http.multipartparser' > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > (venv) mailman@edmmal03$ vi > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > Could this be a broken dependency? You have an incompatible configuration. django.http.multipartparser.parse_header was removed in Django 4.2. See https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous Your version of djangorestframework is incompatible with Django>=4.2. Try in your venv ``` pip install --upgrade djangorestframework ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Which crontab?

by Mark Sapiro

On 11/03/2017 11:43 AM, Pierre Abbat wrote: > According to http://docs.mailman3.org/en/latest/config-core.html, I have to > add "@daily mailman digests --send" to the crontab. Which crontab does it go > in? In the system crontab, the thing after the time is the username, and > there's no user named "mailman" in /etc/passwd. Or should I put a script in / > etc/cron.daily/? The partucular "@daily mailman digests --send" would have to go in the user crontab for the Mailman user. If this is not 'mailman' it is what ever user "owns" Mailman. Further it would require that the path to Mailman's bin/mailman command be in that users $PATH. If it were to go in the system /etc/crontab it would need to be something like @daily user /path/to/bin/mailman digests --send where 'user' is the Mailman user as above. That could also go in a file in /etc/cron.d/ Or you could put an executable script to run '/path/to/bin/mailman digests --send' in /etc/cron.daily Your choice. -- 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: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

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. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. 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. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: spf/dkim/dmarc

by Mark Sapiro

On 5/19/23 09:10, Christian via Mailman-users wrote: > > May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: > to=<billb6951(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, > delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host > gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM > domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard > fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: > [192.46.218.224]. To best protect our users from spam and 550-5.7.26 > phishing, the message has been blocked. Please visit 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for more 550 > 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - > gsmtp (in reply to end of DATA command)) `dig txt lists.ccalternatives.org` reports "v=spf1 a mx ip4=192.46.218.224 -all" It should be "v=spf1 a mx ip4:192.46.218.224 -all" i.e. :, not = > Could the hard fail policy be implicated in the gmail rejection? Yes but only because the ip4 is not effective due to the syntax error. ~all could help, but I suspect replacing the = with : will do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: List mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 10:45, Stephen J. Turnbull wrote: > > % host -t TXT _dmarc.gmx.net > _dmarc.gmx.net descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@gmx.net" > % host -t TXT _dmarc.web.de > _dmarc.web.de descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@web.de" > > The important part is "p=none", which says that GMX does not reject or > quarantine *solely* because of a DMARC fail.[1] Not exactly. These DMARC records specify policies suggested to be applied by any recipient server to mail From: addresses in these domains. They don't say anything about mail To: addresses in these domains From: addresses in other domains. > Footnotes: > [1] IIRC, the "sp=quarantine" means that some fraction of DMARC > failing mail should be quarantined for testing purposes, but the > default fraction is 0 so that is ignored. Actually "sp" is subdomain policy and specifies the policy to be applied to mail From: sub-domains of the main domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:11 PM, David Newman wrote: > On 1/14/22 4:54 PM, Mark Sapiro wrote: >> >> It should work. I suspect you need to go to the list's Settings -> >> Automatic Responses and set `Admin immed notify` to Yes. > > > It's enabled. I think this triggers notifications only for new > subscription requests, not pending ones. Yes. That will send a single notification at the time of the request using the `list:admin:action:subscribe.txt` template. Notices of pending requests are sent by the `mailman notify` command using the `list:admin:notice:pending.txt` template. ... >> You can test `mailman notify` at any time by running it by hand. > > > Thanks. This still isn't working as intended. I took these steps: > > 1. Created the file > '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' The template name is `list:admin:notice:pending.txt`, not `list:admin:action:pending.txt`. Thats why it didn't work. ... > 2. Restarted the mailman3 and mailmanweb services You only needed to restart Mailman core. ... > What I'm trying to do here is replicate a feature from MM2.1, where > pending notifications had URLs embedded in the message. That's not > available out of the box in MM3, and if there's a place for feature > requests I'd be glad to ask that this be made the default. The place for feature requests for Mailman core (which this is) is https://gitlab.com/mailman/mailman/-/issues, however, this is not straightforward as Mailman core doesn't know if you even have Postorius or some other web management UI installed or what the URL to access it might be. Thus it's not just a simple matter of editing templates. It would also require a configuration setting for the base URL for the web admin UI and changes in logic to provide an appropriate replacement depending on whether or not the base URL was configured. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/18/2018 02:07 AM, Sebastian Hagedorn wrote: > > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with > Alembic, as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? Alembic is used by Mailman core to migrate changes in Mailman's data models (database schema). It interfaces with SQLAlchemy <https://www.sqlalchemy.org/> which is used by Mailman core to interface with the underlying SQL database. Alembic is used by mailman developers to create migrations when table and column definitions are modified for some reason. It is not used by end users unless they are actually modifying Mailman's code and database schema. Alembic does not do migrations based on a change in the underlying database engine, e.g. SQLite -> PostgreSQL. -- 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: Hyperkitty performance problem

by Mark Sapiro

On 11/22/24 00:37, Odhiambo Washington via Mailman-users wrote: > On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: >> >> Are Mailman3/Postorius and Hyperkitty supposed to run in separated >> databases, or are they supposed to use the same database? ... > > The official documentation specifies two DBs - one for Mailman Core and the > other for Mailmanweb. > As far as I know, there are no conflicts in the tables so you could use the > same DB for both. And the mailmanweb DB is for HyperKitty and Postorius. I know of no doc suggesting separate databases for HyperKitty and Postorius and in fact accomplishing that would require separate Django instances for HyperKitty and Postorius. I.e., Postorius, HyperKitty and django-mailman3 are all Django applications and use the database configured in Django's settings. Mailman core is separate and uses the database configured in mailman.cfg. As Odhiambo says, there are no table conflicts between these databases so they can be either the same database or separate databases as you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 6/16/22 15:46, Dan Caballero wrote: > Which database table contains these pending subscriptions? I checked the "members" and "address" tables but no luck yet. > > I'm trying to help someone clear a few hundred of these. I can try writing a Python script to use the "hex_token" values in the Python dict. But maybe doing something via MySQL would be easier. The tables are `pended`, `pendedkeyvalue` and `workflowstate`, but don't do it via MySQL. A `mailman shell` interaction like this is better. ``` $ ./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 >>> util = getUtility(IPendings) >>> for token, data in util.find(mlist=m, pend_type='subscription'): ... if data.token_owner == 'subscriber': ... util.confirm(token, expunge=True) ... >>> commit() >>> ``` -- 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: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:14, mkummini(a)cmi.ac.in wrote: > > However, I get the following line each time I do a restart > Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 > I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. You only see this message once at startup because it is only issued once until there is a successful delivery. This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur. Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think `list` in a debian package) find and read them? -- 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: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 21:44, Stephen J. Turnbull wrote: > > I don't think that's the best we can do, though. Especially if > Convert HTML to plain is also yes, we want to preserve the HTML part > and convert it, don't we? Not if we're collapsing alternatives. If we're collapsing a multipart/alternative part with text/plain and text/html alternatives to just the first alternative we don't keep the text/html part. The only html parts we keep and possibly convert to plain text are ones that aren't a second or later alternative in a multipart/alternative part. > I think a better (or additional) strategy > would be to check the selected alternative for blank, and if so, drop > it and try again for an appropriate type. The collapsing of a two part multipart message with an empty first part into a single part message with just the second part is the last thing that's done after all other content filtering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 3 weeks

[MM3-users] Re: Good choice of defaults for content filtering?

by Mark Sapiro

On 7/30/20 5:00 PM, hansen(a)rc.org wrote: > Hi all, > > I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: > a. What were those MM2 defaults (My MM2 server is long gone now). You will find the content filtering defaults beginning at <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. These have been the defaults for new lists since Mailman 2.1.21. Prior th that, the the default for pass_mime_types was ['multipart/mixed', 'multipart/alternative', 'text/plain'] > b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. If you go with the current defaults, except of course for setting filter content on, you can add text/html to pass_types and any html parts that aren't collapsed out by collapse alternatives will be kept and converted to plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Internal Server Error on installing Mailman 3 using PIP

by Mark Sapiro

On 10/28/20 11:04 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As you have suggested in my earlier issue, I have implemented > the latest stable version of mailman 3 through the URL > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > . > > But after the installation through the above URL, when I > tried running the command *elinks http://localhost:8000/postorius/lists > <http://localhost:8000/postorius/lists>* or *elinks > http://localhost:8000/admin <http://localhost:8000/admin>*, I got the error > as *Internal Server Error*. > > I don't find any specific log in mailman.log or in > mailmansuite.log. > > Is there any way to solve this issue ? > You need to hire a consultant who understands Mailman 3 installation to help you with this. The help you need is beyond the scope of this list. I am not available as a paid consultant. I do not do that work. See <https://wiki.list.org/x/4489296> for a partial list of people who do. -- 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: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- 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: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > hmm. > the list-url (e.g. where you can subscribe to the list) for my instance > looks like https://$domain/postorius/lists/$list_id/ (that is: it spells > "postorius" rather than "mailman3"). > so i guess the URL should be > https://$domain/postorius/lists/$list_id/confirm/?token=$token, which > unfortunately returns 404. > > also, my postorius/urls.py does not contain an url-pattern for > "confirm", unlike the current one as found on > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> > > > > so i guess this was not possible yet with postorius 1.2.4 Yes, This was added in Postorius 1.3.4 (over a year ago) > yes. > the *current* template. > but not the template that came with mailman3 3.2.1 Which is over 3 years old. You should really be taking up these issues with Debian. Maybe if they got enough pressure from users, they would update their package. -- 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] {Spam?} Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/1/22 1:40 AM, Andy Smith wrote: > > In the job list I see: > > appname - jobname - when - help > -------------------------------------------------------------------------------- > hyperkitty - update_and_clean_index - monthly - Update the full-text index and clean old entries > > so I'm guessing it's that, but there is also: > > hyperkitty - update_index - hourly - Update the full-text index > > which hasn't been noitceably a problem so I wonder why the "and > clean old entries" bit is so much more heavyweight, what exactly it > dopes and if there's any way to make it lighter on resources? The difference is the update_and_clean_index job calls hyperkitty.search_indexes.update_index() with remove=True See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index…. The comments say "Setting remove to True is extremely slow, it needs to scan the entire index and database." I second Mark Dadgar's comment to replace whoosh with xapian. It will help, although it requires rebuilding the entire search index. -- 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: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/24/24 09:31, Arte Chambers via Mailman-users wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> I'm not sure what's going on. Previously, I said > Presumably it has previously requested and received the list_url and > the permalink to put in the message headers. This can be confirmed by > the presence of List-Archive: and Archived-At: headers with values > in the messages from the list. but they aren't there. ... > Archived-At: <> > List-Archive: <> I was able to add that message to a test list with no problem, so now it looks like the issue is possibly mailman_hyperkitty not able to communicate with hyperkitty, although the log messages aren't consistent with that. Possibly the issue is not with the message you sent, but with the first message in var/archives/hyperkitty/spool/. Is /1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck the first file in a listing of var/archives/hyperkitty/spool/? If not, what does `mailman qfile` show for the first one? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 4 weeks

[MM3-users] Re: Implementing threading [was: hyperkitty failed to create a thread]

by Mark Sapiro

On 2/12/19 8:09 AM, Stephen J. Turnbull wrote: > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. Hyperkitty uses In-Reply-To: and if absent falls back to the last item in References: to determine a message's parent. I haven't looked at what happens if the parent is not in the archive but arrives later. We could look at earlier References: items to try to find one we know, but this could result in bad threading if a later reference arrives after we think we've determined the parent. The unfolding of Message-ID: is now correct. See <https://gitlab.com/mailman/hyperkitty/merge_requests/125>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 11:38 PM, Peter Münster wrote: > On Tue, Jan 30 2018, Mark Sapiro wrote: > >> The underlying issue is the orange.fr domain is sending DSNs without a >> Message-ID: header. > > Yes. Is a Message-ID header required in a DSN by any RFC? It's not a MUST, just a SHOULD, but RFC 5322, sec 3.6.4 says Though listed as optional in the table in section 3.6, every message SHOULD have a "Message-ID:" field. >> If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] >> section of your config), this log message > > I have verp_delivery_interval = 10 ... Which says only every 10th message will be VERPed. You want verp_delivery_interval = 1 to VERP every message. >> would contain to=<test-bounces+user=example.com(a)my-domain.org> and you >> could identify the bouncing address (user(a)example.com in this case) that >> way. > > Yes, that's my intention, but first of all, mailman must receive the DSN. The message does appear in the mail log, but until the issues below are fixed, even if Mailman receives it, you won't see it. >> Beyond that, there are still other issues, the biggest of which is >> currently, Mailman is not processing bounces other than storing them in >> the database. See <https://gitlab.com/mailman/mailman/issues/343>. > > Shouldn't the DSNs be forwarded to the owner of the list? They should be processed by Mailman and scored as bounces for the recipient if recognized and forwarded if not (depending on settings), but they currently are only stored. >> if a recipient MTA can't create a DSN that has a Message-ID:, would >> you trust what else it does? > > I don't know. The question for me is: does the remote MTA needs a fix > (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN > without Message-ID should be acceptable)? I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Migration advice

by Mark Sapiro

On 08/28/2018 06:42 PM, Quanah Gibson-Mount wrote: > Hi, > > I'm looking at migrating from an old server running mailman 2.1.15 > (Debian wheezy) to a new Ubuntu 18.04 LTS system. I'd like to upgrade > to mailman3 as a part of this migration. I was reading the migration > docs (<http://docs.mailman3.org/en/latest/migration.html>), which seem > to require both mailman2 and mailman3 be installed concurrently on the > same system. Is that correct, or can I rsync the mailman2 list > information onto the new server without mailman2 itself being present, > and import from there? Short answer - Yes. You need only a Mailman 3 installation. You also need a copy of the Mailman 2 lists/LISTNAME/config.pck file for input to 'mailman import21' and a copy of the Mailman 2 archives/private/LISTNAME.mbox/LISTNAME.mbox file for input to the Django management hyperkitty_import command. It would be good to check the archives/private/LISTNAME.mbox/LISTNAME.mbox file with the Mailman 2 bin/cleanarch command, but you can do that on the Mailman 2 system before copying the mbox. -- 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: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 12/8/20 2:01 AM, Krešimir Mihalj wrote: > Hi ! > I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... Have you seen <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > To add member using CLI i tried this command: > > curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members Try this: > curl --user restadmin:restpass --data-raw 'list_id=list.domain.com&subscriber=user(a)email.com' http://localhost:8001/3.0/members > Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com First find the member_id with something like > curl -urestadmin:restpass http://localhost:8001/3.0/lists/list.domain/member/user@email.com which will return json including the value of member_id Then you can do > curl -urestadmin:restpass -X DELETE http://localhost:8001/3.0/members/xxxx where xxx is the member_id. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 3:12 PM, Jens Günther wrote: > > > -> the first one works and leeds to > https://mailman.xyz.de/mailman3/postorius/lists > -> the second one redirects to > https://mailman.xyz.de/mailman/postorius/lists > -> which does not exist, since Apache-alias is only for mailman3 Sorry, I missed that it was mailman vs mailman3. > > I only use the apache-conf given in the documentation: > > <code> > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 > unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > </code> I don't use uwsgi so I can't advise on its configuration, but do you have USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') 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

4 years, 1 month

[MM3-users] Re: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:09, bob B via Mailman-users wrote: > > Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key is now > File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > <h1>Authorization Required</h1><p>The archiver key is now > <h1>Authorization Required</h1><p>The archiver key is now The full message is <h1>Authorization Required</h1><p>The archiver key is now required to be sent over the Authorization HTTP header. You need to upgrade the mailman-hyperkitty package to 1.2.0 or newer. > HyperKitty version 1.3.5. As indicated in the above message, HyperKitty >= 1.3.5 requires mailman-hyperkitty >= 1.2.0 If your mailman-hyperkitty is < 1.2.0, you need to upgrade it. If it is 1.2.0, there is some issue with the http headers being dropped in the request from mailman-hyperkitty to HyperKitty. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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: hyperkitty failed to create a thread

by Mark Sapiro

On 2/17/19 2:13 AM, Danil Smirnov wrote: > > Could you advise how to rebuild the failing threads please? I've done index > update with 'django-admin update_index' command but it seems irrelevant to > the issue, I still have all those messages separated: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ I've not tried it and have no idea if it will work, but the query select message_id, message_id_hash, in_reply_to from hyperkitty_email; will show those things. You will see some (most) entries have a message_id of the form 'left-part@right-part' with no angle brackets, but some are of form ' <left-part@right-part>'. In those cases where 'left-part@right-part' of in_reply_to is in a message_id of form ' <left-part@right-part>', you could try altering that in_reply_to to ' <left-part@right-part>' After doing this, you probably need to run 'django-admin runjob thread_order_depth'. Obviously, make backups before you start. An alternative might be to 'fix' the message_id which may or may not require recomputing message_id_hash. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: mailman3 vs postfix

by Mark Sapiro

On 4/29/20 7:35 AM, Ralf Wiegand wrote: > hey Mark, that worked. Thank YOU. Got one step ahead. So after > creating a admin account and logging in via the GUI, I get this error > message: > > > IntegrityError at /accounts/login/ > > UNIQUE constraint failed: account_emailaddress.email > > Request Method: POST > Request URL: http://192.168.0.27:8000/accounts/login/ > Django Version: 2.2.12 > Exception Type: IntegrityError > Exception Value: > > UNIQUE constraint failed: account_emailaddress.email > > Exception Location: > /opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/sqlite3/base.py > in execute, line 383 > Python Executable: /opt/mailman/venv-3.6/bin/python > Python Version: 3.6.8 > > What does this mean? I think it means you have more than one Django account with the same email address. If you can log in to your django admin interface as the superuser, you may be abl to go to 'Users' and delete one. If you can't log in to your django admin interface as the superuser for this reason, you will probably need to create another superuser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: How to Unshunt Specific Message ?

by Mark Sapiro

On 8/11/20 9:55 PM, Shashikanth Komandoor wrote: > Hahahaha. > > Looks like a work around. Yes, it's a workaround. > I understood "moving out of the shunt queue" means "Moving the files from > /var/lib/mailman/mailman/var/shunt directory to any other directory say > /opt/...." in my environment. Because I installed mailman software inside > /var/lib/mailman only. It means first understand why the messages were shunted and fix whatever the underlying issue is or they will just be shunted again. You should look at each message in the shunt queue with `mailman qfile` and determine which ones you don't want at all, which ones you want to save for later and which ones you want to unshunt now. Just remove the ones you don't want at all. For the ones you want to save for later, move them to any other directory at all. Then run `mailman unshunt` for the remaining ones after which you can move the saved ones back or leave them where you moved them to. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 6:38 AM, Jens Günther wrote: > Thank you for your answer. I should have seen that in the Docs, but > somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > I set it in the corresponding file, but unfortunately it doesn't work > :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS > works, changed here from '*' to 'localhost' and my example-domains, this > works). It seems to be the same as this user describes (a while ago): > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… FILTER_VHOST is problematic. It works fairly well for HyperKitty, but not so well for Postorius. In particular with Postorius it doesn't work if there is more than one mail host domain with the current web host. See these issues and MRs for more detail. https://gitlab.com/mailman/hyperkitty/-/issues/254 https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs https://gitlab.com/mailman/postorius/-/issues/394 https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs -- 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: Strange problem in user lists

by Mark Sapiro

On 12/16/21 2:25 AM, Gelpi Andrea wrote: > > I cant' understand why, but I have two members with the wrong name. > > "A B" <C(a)dom.tld> > "D E" <F(a)dom.tld> > > My problem is that A and B must be associated with F(a)dom.tld and vice-versa. > > I tried to delete the user member and recreate it, but it has always the > wrong name. Because the display name is associated with the Mailman user and unsubscribing the user from the list doesn't change the user. > Is it possible to correct those errors? How? The user can log in to the web UI and go to the Account link in the dropdown at the username at the upper right and change the first and last name there. If you have a recent enough Postorius, a site admin can go to the Users link at the top of a page find the user, click Manage and change the Display Name. Otherwise, you can do this in `mailman shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/4/22 04:57, Stephan Krinetzki wrote: > > we have fixed the issue now: Good. > mailman shell -l list(a)lists.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. > Die Variable 'm' ist die list(a)lists.example.com Mailingliste > >>> lr = IListRequests(m) > >>> for req in lr.held_requests: > ... if lr.get_request(req.id) is None: > ... print(req.id) > ... > 32598 > 22449 > 66937 > 68261 > 92927 > >>> > > With this IDs > > DELETE FROM _request WHERE id IN (32598, 22449, 66937, 68261, 92927); > > And the 500 error is gone. I'm glad you were able to fix it. Do you happen to have the content of those rows in the db before you deleted them? It would be interesting to know what that was to try to determine how that situation happened in the first place. -- 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: Verification emails 'helo' rejected

by Mark Sapiro

On 10/14/24 12:42, Greg Newby via Mailman-users wrote: > > Here are the corresponding logfile entries from mailmanweb.log: > smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 <mail>: > Helo command rejected: need fully-qualified hostname')} > > and from mail.log: > Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from > localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need > fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost> > proto=ESMTP helo=<mail> > > lists.domain.tld is the domain for Mailman3. I don't know why it's trying > to send email from root@. I think the mail.log entry is for the DSN for the failure. The issue is the HELO/EHLO command. Try the following in your venv ``` (venv) ...:~$ python Python 3... Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> socket.getfqdn() ``` If that returns `localhost`, that's the issue. I think you can fix it by putting a fully qualified domain name in /etc/hostname. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/23/20 10:14 AM, Waqas Ahmed Khan wrote: > > Could you Please confirm, what should be hardware configuration (ram, > processor, disk) to run mailman3 server for medium size organization? This > server will have 10-15 lists and some lists having 10k to 20k members. Also > what should be DISK SPACE of the server for Archiving emails? We really don't have hard requirements and a lot depends on what else besides Mailman the server does. First of all, it appears from some reports that 2GB RAM is not enough, but for Mailman 3 alone, 4GB is ample and I suspect that would do for what you describe. For disk, consider mail.python.org This server currently supports 139 Mailman 3 lists. There are a total of over 36,000 known Mailman 3 users. There are archives going back in some cases, decades, with currently a total of over 673,000 archived messages. The Mailman 3 database with all the archived messages and user info is 8.7 GB. The Xapian archive search index is 18 GB. -- 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: Deleting default "example.com" domain breaks everything

by Mark Sapiro

On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > Hello. I'm new with v3 of mailman. > Installed via aptitude on deb10. > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > I then deleted example.com, and everything broke. > The only site I had was still using example.com. > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? Try setting `SITE = 0` in your Django settings file. If that doesn't work, try successively 1, 2, etc. One of these should work. Also going back to your prior thread, you had > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser Aside from the python/python3 issue, you should run any Mailman and Django management commands as the Mailman user (probably `list` in your case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 and https://gitlab.com/mailman/mailman/-/issues/776. -- 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: Hyperkitty Error

by Mark Sapiro

On 12/9/19 5:25 PM, Brian Carpenter wrote: > I am seeing the following error being repeated every 2 seconds in the uwsgi-error.log: > > 01:22:05 [Q] INFO Process-1:19112 processing [compute_thread_positions] > 01:22:05 [Q] ERROR Failed [compute_thread_positions] - 'DiGraph' object has no attribute 'node' : Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/django_q/cluster.py", line 381, in worker > res = f(*task['args'], **task['kwargs']) > File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.node[msgid]["obj"] > AttributeError: 'DiGraph' object has no attribute 'node' > > I am running the docker version of Mailman, version 1.3.0. Any suggestions? See <https://gitlab.com/mailman/hyperkitty/issues/268> fixed by <https://gitlab.com/mailman/hyperkitty/merge_requests/201>. You need to change 'graph.node' to 'graph.nodes' at both line 37 and line 44 in /usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py to accomodate networkx >= 2.0 -- 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: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 6/17/22 12:19, Dan Caballero wrote: > Thanks very much for the guidance. I ran the code and received the output for the list but after a commit and exit the members still weren't subscribed. That's expected. The process I posted only removes the pending request so a subsequent subscribe can succeed. > I then ran mailman syncmembers using a list I had. That was able to complete this time and make all the necessary additions. > > I'm going to see about making a wrapper script for future use. Thank you again. For Mailman core >=3.3.5 this should not be an issue. The underlying issue is https://gitlab.com/mailman/mailman/-/issues/729 which is fixed in 3.3.5. Now pending subscription confirmations expire after the configured pending_request_life (default 3 days) so they shouldn't hang around virtually for ever. I just added some sample scripts to https://www.msapiro.net/scripts/. The script at https://www.msapiro.net/scripts/delete_orphans_expireds.py will delete subscriptions pending user confirmation that are older than the current pending_request_life. -- 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: Can't Start Mailman3 Core on Fresh Install

by Mark Sapiro

On 7/21/22 10:09, Jonathan Green wrote: > I've triple checked the password in mailman.cfg and used the same > username/password directly in MySQL and was able to get to the mailman3 > database. I did run a test script in python3 using the PyMySQL connector > and got the same error. Is there some permissions issue I need to look for? > I ran the install as user root - perhaps the user running the python script > doesn't have access somehow? First, your primary support resource for the Debian/Ubuntu packages should be Debian. That said, the database access credentials are also configured in the DATABASES setting in your Django settings, although your OP indicates this error is in core. I'm not sure what running the install as `root` will do in the Debian/Ubuntu package, but with that package, the user that needs to access things is `list` and all the Mailman processes should run as `list`. Did your test script do pymysql.connect(user='list', ...)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: message awaits moderator approval

by Mark Sapiro

On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > database, in particular in the template table. I removed them using direct SQL > commands. > > Now my new mailing lists work as expected. > > Is this a bug in postorius? I think when I delete a mailing list, all relicts > should be deleted from the database. Were there Postorius custom templates for that list?, I.e. did the template table entries have Postorius URLs. If so, this is probably a Postorius issue. I haven't actually looked, but when Postorius deletes a list, it should delete any of it's templates from the postorius_emailtemplate table and revert the template table entries. Beyond that, Postorius is just telling Mailman core to delete the list, and when Mailman core does that it should probably also remove any var/templates/lists/<list_id> directory and any entries from the template table with context = the list_id. If it doesn't, this is a core issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: attachment.html

by Sam Darwin

Thanks for making this change! It's a big improvement! Another random idea, not required, - using javascript, literally disable or enable all the settings which are disabled or enabled by 'Filter content'. So if someone tries to set 'Convert html to plaintext', they can't, until 'Filter content' is enabled On Mon, Jun 26, 2023 at 10:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 6:22 PM, Mark Sapiro wrote: > > > > You are correct that the UI is not clear on what settings depend on > > Filter content. We need to fix that. > > I've created an issue for this at > https://gitlab.com/mailman/postorius/-/issues/584 and committed a fix at > https://gitlab.com/mailman/postorius/-/merge_requests/815 > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to samuel.d.darwin(a)gmail.com >

1 year, 9 months

[MM3-users] Re: Speed up importing mailman2 lists

by Mark Sapiro

On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > We are currently planning to migrate from mailman2 to mailman3 as a container, have around 1500 lists and would like to complete the migration ideally in a few hours. We would like to switch off mailman2 to have a defined state of the lists and import them to mailman3. The import of all lists via script takes about 3 days. Parallelizing the imports does not work due to lockings in the database. > However, we cannot accept a downtime of 3 days. Does anyone have tips on how we can speed up the procedure or are there best practices for larger environments? What Mailman 3 version are you importing to? I ask because prior to Mailman core 3.3.1, user's passwords were imported and the encryption of the password was quite time consuming. If in fact you are importing to Mailman <3.3.1, see https://gitlab.com/mailman/mailman/-/merge_requests/565 for a patch that will speed this up considerably and see https://mail.python.org/archives/list/mailman-developers@python.org/thread/… for discussion of this change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Mark Sapiro

On 05/29/2017 02:16 PM, Simon Liebold via Mailman-users wrote: > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > > True, this table doesn't exist in the database. It isn't created by > python manage.py migrate. > > The error is served with HTTP-200. No stack trace in mailmansuite.log. Do you have django_q in INSTALLED_APPLICATIONS in your Django config and do you have # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } in your Django config and are you running django-admin qcluster at startup? See <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/26/21 8:18 AM, Seth Seeger wrote: > > I have just upgraded to 3.3.4 from 3.3.2 (via docker). > > Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature). > > Is it just catching up on old bounces? There is no significant change in bounce processing from 3.3.2 to 3.3.4 If you really upgraded from 3.3.2, I don't know what would be responsible. On the other hand, it looks like you may in fact have upgraded from Mailman < 3.3.1 in which case, those are old, previously unprocessed bounces, and your log certainly looks like that. If you think some or all users shouldn't have had delivery disabled, you can run the mailman shell seccion in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… to re-enable them and let current bounce processing handle the truly undeliverable ones. -- 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: Broken web UI after upgrade

by Mark Sapiro

On 12/16/22 03:36, Odhiambo Washington wrote: > > I am probably getting closer to where the problem is. By looking at nginx > error_log while access the site, I see that there are > just two CSS files that are missing, as shown in the error lo here: > https://pastebin.ubuntu.com/p/7wbwMgqMyS/ > > Question is - why is it specifically looking for these two files > - /opt/mailman/mm/static/CACHE/css/output.93545e20bc30.css > -/opt/mailman/mm/static/CACHE/css/output.e1f0c6022e8f.css > > Where are these files supposed to come from and why are they missing? > I have looked at my current CACHE directory and compared with the backup of > the same site before upgrade and these files aren't the same either: They come from django admin `compress` which used files created by django admin collectstatic. I suggest you run ``` django-admin collectstatic --clear --noinput --verbosity 2 django-admin compress --verbosity 2 ``` where `django-admin` is your django admin command. If this doesn't fix the issue, perhaps the more verbose output will help find the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Speed up importing mailman2 lists

by Mark Sapiro

On 2/24/25 05:36, t.maintz(a)fz-juelich.de wrote: > > Can you tell me how to implement this in Postfix? Here's what we do on mail.python.org which supports both Mailman 2.1 and Mailman 3 lists. We also use an alias domain as described at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… because python.org is a virtual_alias_domain. The relevant settings in main.cf are alias_maps = ... hash:/srv/mailman/data/aliases lmtp_destination_recipient_limit = 1 recipient_delimiter = + relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains transport_maps = ... hash:/opt/mailman/mm/var/data/postfix_lmtp virtual_alias_domains = python.org ... virtual_alias_maps = ... hash:/srv/mailman/data/virtual-mailman hash:/opt/mailman/mm/var/data/postfix_vmap The alias_maps and the hash:/srv/mailman/data/virtual-mailman setting in virtual_alias_maps are MM 2.1 settings. The hash:/opt/mailman/mm/var/data/* settings are MM 3. Since transport_maps takes priority over aliases, if there is a MM 3 list in hash:/opt/mailman/mm/var/data/postfix_lmtp, mail for that list will be delivered to MM 3 via LMTP. If not, and the destination is a MM 2.1 list, delivery will be via the virtual_alias_mapping hash:/srv/mailman/data/virtual-mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 4 weeks

[MM3-users] Re: How can I remove anything added by Mailman 3 to the forwarded email

by Mark Sapiro

On 5/9/22 06:00, gscaglia(a)ksdata.it wrote: > I need to use Mailman 3 exclusively for forwarding emails to my customers divided by type. > > The emails must arrive exactly as they are, without any additions, and the lists are managed only by me: the customer ignores that he is subscribed to a list and receives the message as if it were one to one. > > How can I remove anything added by Mailman 3 to the forwarded message, therefore also the links for managing my membership (unsubscribe and modify)? In Postorius do the following: In Templates set list:member:regular:footer empty In Settings: in List Identity set Subject prefix empty in Alter Messages set Personalize None Filter content No Anonymous list No Include RFC2369 headers No Include the list post header No First strip reply to No Reply goes to list No Munging in DMARC Mitigations set DMARC mitigation action No DMARC mitigations in Archiving set Archive policy Do not archive this list -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Mailman not able to process "big" requests

by Mark Sapiro

On 04/24/2018 12:36 AM, Abhilash Raj wrote: > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> We also have a problem with sending out emails to "large" (>50) groups, >> as they seem to not getting sent out at all. Do you have any idea what >> the problem here could be? > > Which MTA are you using? What do you see in mailman's logs and MTA's logs? > > I haven't seen this kind of problem before with Mailman 3. This very list is hosted using Mailman 3 and I believe has more than 50 subscribers. Nor have I seen this issue. This list currently has 158 non-digest members. There are several @python.org Mailman 3 lists with over 100 non-digest members including the active yt-users(a)python.org list with 301 members, and I have gotten no reports of an issue like this. Also, there are over 600 lists at <https://lists.fedoraproject.org/>, and I don't think this is an issue there 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

[MM3-users] Re: installation

by Mark Sapiro

On 11/21/20 10:42 AM, Christian Stalberg via Mailman-users wrote: > I am working through installing mailman3 on Ubuntu 20.04.1 LTS / apache > 2.4.41 / postfix 3.4.13 and have a couple of questions. > > > > I've installed Django, cloned the mailman-suite repo, installed and tested > apache with Mod_wsgi [ according to > https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/ ] > and it worked fine. Now I am at 'Setting up a WSGI' server in the MM3 > instructions where it says I am to configure uwsgi.ini file. Does that .ini > file go in /opt/mailman/mailman where other .ini files reside? You are mixing apples and oranges. The doc at <https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/> uses mod_wsgi in apache, It doesn't use uwsgi at all. > In setting up the apache virtual server [ according to > https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl > ight=apache#apache-with-mod-wsgi ] I do not find a postorius.wsgi which > WSGIScriptAlias points to. The file in your WSGIScriptAlias directive should be the wsgi.py file in mailman-suite/mailman-suite_project/ -- 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: Importing issue from mailman2 to mailman3

by Mark Sapiro

On 3/7/21 3:42 AM, David Partain via Mailman-users wrote: > > Most of it's going fine, as best I can see. However, I get exceptions on some lists that look like this: > > Traceback (most recent call last): ... > pymysql.err.DataError: (1406, "Data too long for column 'info' at row 1") > > My assumption is that what's in the "Info" field on the old mailman2 config is simply too long. Is that correct? Yes. For MySQL and MariaDB the info column is VARCHAR(255). It probably should be defined as a type that allows a longer value, but for now with those DB engines, it is limited to 255 bytes. > In that case, I suppose the right thing is to (1) edit each one, reducing the size, which'll create a new config.pck, (2) pull it over to the new machine, and (3) run the import again. > > Seem reasonable? Yes, that's the workaround. Or you could start over with postgresql as the DB which doesn't have that limitation. -- 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: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass Those are headers for compiling some sass. Possibly you actually have a `sassc` installed in which case you may need COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) in your settings_local.py. See https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#instal… and the Sass compiler section at https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies. -- 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 - delete or backup old archived messages

by Mark Sapiro

On 6/17/21 1:00 AM, olenkoigetublim(a)gmail.com wrote: > > I have been using Mailman-Suite (Hyperkitty + Postorius) quite a long time now and now i was wondering if there is any way to erase or export old archived messages and back them up elsewhere (for example messages, that are older then 1 year). Didnt find any suitable option under "python3 manage.py" command and also didnt find any up to date post which related to mailman3 and python3. There isn't currently anything to do this but is shouldn't be difficult to create a script. You'd need to import the Email class from hyperkitty.models.email, set CUTOFF to a datetime.datetime instance with the cutoff date instantiate a mbox to receive the deleted messages and then do something like for email in Email.objects.filter(date<CUTOFF): msg = email.as_message() mbox.add(msg) email.delete() A lot of required housekeeping such as importing django and calling django.setup(), exception handling and reporting would need to be added to the above, but the basic loop should work. -- 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: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/6/22 1:20 AM, Michael Heseltine wrote: > Hi all, > I've done the additional steps > > /opt/mailman/mm/bin/django-admin migrate > /opt/mailman/mm/bin/django-admin createsuperuser > > without error, and also started the services mailman, qcluster and gunicorn without error messages. Did you see my post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and did you run /opt/mailman/mm/bin/django-admin migrate before starting services? > However, I just get an internal server error when I try to access https://lists.mydomain.com/ (which is served by a local apache virthost). > > The apache log shows just one error: > > [Thu Jan 06 10:01:39.201833 2022] [proxy:warn] [pid 3627279] [client 333.333.333.333:59328] AH01144: No protocol handler was valid for the URL / (scheme 'http'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule. Do you have all of these apache modules enabled, proxy.conf, proxy_http.load and proxy.load, in particular proxy_http.load? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Mark Sapiro

On 10/28/24 18:33, Bill Oliver wrote: > > Aha, I thought. I should have changed that. Then I noticed that I > didn't even have a mailman-hyperkitty.cfg file, and I can't find > mention of it in the venv instructions. I *have* installed mailman- > hyperkitty during the "pip install mailman-web mailman-hyperkitty" > step. I did a "find" on /opt/mailman, and it doesn't seem the file is > there at all. > > Do I need this file? Yes. See the last part of the section at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it says in part `And, create the /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: ...` > I found a template here: > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… > > > Do I need to copy and paste that in my installation? It, or something as mentioned in the above doc needs to be at the location defined in the `configuration:` setting in the `[archiver.hyperkitty]` section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Mark Sapiro

On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID 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_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 4 weeks

[MM3-users] Re: installation

by Mark Sapiro

On 11/22/20 3:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I have > used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. You need a fixed IP address and "full circle" aka "forward confirmed reverse DNS" <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. You also need to DKIM sign your outgoing mail from your domain and publish an SPF record allowing your IP as a sender for your domain. I'm not sure, but publishing a DMARC policy, even if it's p=none is possibly helpful with some recipient domains. Beyond that check your IP for blacklisting with a tool like <http://mxtoolbox.com/blacklists.aspx> and monitor your mail logs for blocked email and follow up with the blockers to get unblocked. Things get better over time as your server develops a reputation. -- 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: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 12/29/21 3:58 PM, William Oliver wrote: > > I'd like to delete all my archives that are more than a certain age, > e.g. more than a week old. I can easily do that with a cron job, > deleting old files in > > > /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* > > which is, as far as I can see the only place archive emails live. Those are emails archived in the prototype archiver. That's all the prototype archiver does - store the mail there. The HyperKitty archived emails are stored in the mailmanweb database in the hyperkitty_email table. Attachments are in the hyperkitty_attachment table and other tables are also involved. > However... I was wondering if there was some mailman command or config > variable that would accomplish this without using cron. The cron will work for the prototype archives, but it's probably easier to just disable the prototype archiver. For HyperKitty, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 06:52, Frank Steinberg wrote: > Hi, > > I’ve added links to some templates to give owners and moderators > shortcuts to the postorius UI for moderation tasks, e.g., I’ve added > > https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> > > Unfortunately those lines seem to exceed a certain limit and get > folded, so that they appear as, e.g. > > https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> > messages > > (or similar) and are not directly useful. How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? Also are those lines of the form https://... <https://...> what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. Is the folding actually in the raw message or is it an artifact of the mail client viewing the 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, 6 months

[MM3-users] Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 10:12 PM, Torge Riedel wrote: > Am 21.04.20 um 23:08 schrieb Brian Carpenter: >> Maybe I can get the client to agree to use the web domain as part of >> their list address. > > Hi, > > maybe it is a solution for you what I did on my side (since it was > already the setup for mailman2 my customer is happy with it): > > Set everything up in mailman3 with lists.domain.com and define in > postfix (if you use postfix, others should support it also) aliases from > - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail > list. > > In the list setup in mailman3 (available via postorius) define > list1(a)domain.com as an allowed alias for list1(a)lists.domain.com This is a good workaround, however to be complete, you may also want MTA aliases for the list1-*(a)domain.com addresses. Note, I'm currently working on a fix for <https://gitlab.com/mailman/postorius/-/issues/394>. Hopefully that will be in the next Postorius release. -- 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 3 - docker container - sync_members

by Mark Sapiro

On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > I would like to populate list members via the Mailman 3 sync_members script. > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? I'm not sure what version of Mailman core is in the Docker containers. According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman core is docker version 1.1.1 released Aug 9 2017 which is about the time of MM Core 3.1.0 which is quite old and has neither a `mailman syncmembers` (introduced in core 3.3.2) command nor the older `mailman members --sync` option (introduced in core 3.3.1). There are `rolling releases` <https://asynchronous.in/docker-mailman/#rolling-releases> which should have these. > Searching this list I found a reasonable approach: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Is there a different/preferred solution? The script at <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> seems fine. The alternative is to update your Docker container to one including the appropriate `mailman` sub-command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: hyperkitty url not found

by Mark Sapiro

On 3/14/22 12:24, Eggert Ehmke wrote: > So I have to use the external url via https? > > I can access the address > https://lists.[1]<tld>_/mailman3/archives/api/_ > > so I set: (<tld> is my existing domain) > > base_url: https://lists.<tld>/mailman3/archives > Now I get this in the mailman.log: > > Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> > Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ > api/mailman/urls: <html><title>Forbidden</title><body> > <h1>Access is forbidden</h1><p>Please check the IP addresses > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > </p></body></html> (403) > In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there? Is whatever is proxying to Django forwarding the IP and are you sure it matches the "my local IP" you set? You might instead try setting base_url to http://localhost:8000/mailman3/archives/ or more likely http://localhost:8000/archives/ (I.e. whatever your webserver proxies the https://lists.<tld>/mailman3/archives/ url to. -- 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: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

Rob's reply in this thread was garbled due to <https://gitlab.com/mailman/mailman/issues/616>. The text of the reply is quoted below. On 7/27/19 12:54 AM, Rob Lister wrote: > > One thing that does occur to me is that my exim header fudge will > probably cause the Message-ID header to move around from its original > position, and if someone is doing hashing or actually validating (gpg > signing?) the headers haven't been tampered with, then it might > complain, since although the message-id hasn't changed, it might be in a > different place in the headers. > > Then again, mailman can make plenty of other modifications and additions > to the headers anyway, so I'm not sure it matters. > > Probably the more correct way to do it is only add a new header if it's > missing, and if it's there, leave it alone. > > This is probably possible in exim with some more variables and a lot of > nested curly braces... -- 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: Delete Django profiles not signed up to a list

by Mark Sapiro

On 1/1/21 4:41 PM, Andrew Hodgson wrote: > > I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? I have attached a script that will delete users from Django's user database (the auth_user table) if there is no Mailman user with the Django user's email address or if there is a Mailman user but it's not a member, nonmember, owner or moderator of any lists. The setting DELETE_MAILMAN_USER controls whether it will also delete the corresponding Mailman user that's not a member, nonmember, owner or moderator of any lists. If set to True, it will. The script has a few installation specific paths that may need adjustment. Also, if Mailman is installed in a virtualenv, the script needs to be run by the python in that virtualenv so that the imports all work (as with the shebang in the script). -- 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: 400 Bad Request when administrator tries to selectively override member options

by Mark Sapiro

On 5/8/21 1:17 PM, ieso(a)johnwillson.com wrote: > This is probably Design Intent, but I'd just like to confirm. > > When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set. > > Screenshot: https://ibb.co/pzM5Z4m > > It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list. > > But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation. What Postorius version is this? I just tried it on Postorius 1.3.5b1 (The HEAD of the gitlab branch), and for a user with no options at all set at the list level, I was able to set `Receive own postings` only with no problem. I think this is https://gitlab.com/mailman/postorius/-/issues/178 fixed in Postorius 1.2.0 by https://gitlab.com/mailman/postorius/-/merge_requests/321 -- 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: # comment allowed in a template file?

by Mark Sapiro

On 7/24/20 3:19 AM, skenny(a)scss.tcd.ie wrote: > > I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: > # This file is managed by Puppet. > > Is it ok to do this? I may not have searched the docs enough, but I couldn't find anything relating to comments. If you mean can you add a '#' line that won't be part of the actual rendered template, the answer is No. > One other observation in case it's any use: Initially, I created the template files with owner set to "root". This resulted in postings to lists getting stuck in mailman-core. It's vital that these files are owned by user "mailman". Once I changed the owner of the file to the latter, everything worked. I don't think they need to be owned by 'mailman' as long as they are readable by 'mailman' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 4:36 AM, alopez(a)ac.upc.edu wrote: > Hello, > I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. > I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. Because you are leaving mailman shell with exit() which doesn't commit changes. You deed to either explicitly commit with `commit()` or exit with control-D. Recent mailman shell will report in its banner 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. > On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? Your Postorius is too old to support alias_domain, and your Mailman core may be too - requires core >= 3.2.0. -- 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: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > I resolved this myself with a search that turned up a 2018 post from Mark that suggested typing "mailman aliases" to create the hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where they are on Ubuntu 18.04). I looked in that folder and sure enough it was empty so I typed "sudo mailman aliases" which did indeed create the 4 things that needed to be there: > postfix_domans > postfix_domains.db > postfix_lmtp > postfix_lmtp.db > > But, they were owned by root:root and everything else under that /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the ownership on the 4 files to list:list. Because that's how you ran it. Run sudo -u list mailman aliases. > Seems to have worked! I was perplexed about why I had to do this though because these were created automatically last time I did this, but I figured that out too. Current `mailman start` should create the aliases. -- 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: Monthly job failure

by Mark Sapiro

On 6/25/19 4:08 PM, andrew.bernard(a)gmail.com wrote: > Yes I did. So something is out of sync, the job are referring to lists no longer existing. What is this? I'm confused. The subject of this thread is 'Monthly job failure', but your original post said 'I see this error on startup:' Perhaps you are confused in that the error occurs in 'rebuild_mailinglist_cache_for_month'. That is not a monthly job. That is a queued task to rebuild the cached data for a particular 'by month' view. That task is queued whenever a post is added to update the monthly cache for the year and month of the date of the post, and whenever a thread is deleted to update the monthly cache for the year and month of the date the thread was active. I'm guessing here, but I think you have a task queued for a list that no longer exists in HyperKitty. Go to the Django web admin and look at the DJANGO Q section, particularly Queued tasks, but maybe the others too. Maybe there's a task you can delete. -- 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: migration

by Mark Sapiro

On 7/30/21 12:06 PM, Dave McGuire wrote: > > Is there a way that I can "dump" the configuration from an existing > mailman3 server, and "import" it into a new instance? I'd really like > to avoid re-doing all of the configuration, etc, as there are quite a > few lists and everything is set up pretty much the way I want it. If you use the same database manager it should be no problem to get a dump of the existing Mailman database to load into the new instance, or if these are on the same server, just point the new instance to the existing database. In either case, the database should be loaded and the Django commands `migrate`, collectstatic`, `compress` and `compilemessages` run[1] before starting Mailman services. Mailman core will run any necessary updates to its database upon startup. You may also need to rebuild the HyperKitty search index with the `update_index` Django command, but you may be able to use the existing one if the search engine is the same. [1] See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… et seq. -- 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: Implicit destination

by Mark Sapiro

On 08/26/2018 12:54 PM, David Krantz wrote: > > I have a spam-problem like anyone else. Most of the spam my listserver > receives has some kind of impilict destination so the implicit rule > catches most of the spam that way. This is fine. What is not so fine, > however, is that this results in a moderation message to the sender. > I'd like to stop that so that the spammer has no confirmation that the > mail was received. That is not the issue. Sending the held message notice to a spammer, if it reaches the spammer, is probably inconsequential. The issue is that virtually always in spam the sender address is either undeliverable or is the address of an innocent 3rd party. Sending these notices to innocent 3rd parties is called backscatter and is a bad thing. To avoid this backscatter, you can set the list's respond_to_post_requests attribute to False. There are two problems here. One is this setting is not currently exposed in Postorius, and the other is this will also stop desired held message notices such as those from list members. -- 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: content filtering in version 3.1

by Mark Sapiro

On 12/20/19 1:31 AM, Dieter Leupold via Mailman-users wrote: > Hi Mark, > > Thanks for your information. But, how I said, I'm new to MM3 and I have > problems with the syntax of the mailman shell. Please, could you give me > an example to set "pass_types" via MM-Shell? > Thank you very much! The documentation of Mailman shell is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…>. A simple example in for setting pass_types is ``` $ 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.pass_types <generator object MailingList.pass_types at 0x7fd7e1489840> >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain'] >>> list(m.pass_types) ['multipart', 'text/plain'] >>> At this prompt you can enter commit() to commit your changes, abort() to reverse your changes or control-D to commit and exit. You can also enter exit() to exit, but your changes will not be saved unless you have done a prior commit() -- 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: Correcting name spellings in a list

by Mark Sapiro

On 2/23/21 9:40 PM, Morris Jones wrote: > I typo'd some full names in a mailing list. I want to correct them ... > > I can't see a way to do that in the Member Options, so I thought I'd try > "remove" and re-add, either from the command line or the UI. > > But the name gets readded with the typo intact. :( > > Is there a way to fix it without writing SQL? You can do it with mailman shell. The basic issue is the display name is a property of the user or the user's address, which ever is subscribed to the list. When you add a previously unknown user to a list, Mailman creates these user and address records, but they belong to the user, not the list. There are some threads around this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and a somewhat protracted one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. -- 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: Special Characters Issue when using Wordpress HTML messages

by Mark Sapiro

ryan.anderson.4--- via Mailman-users wrote: > > Thanks for the reply. I changed the language.master in the schema.cfg. > > [language.master] > # Template for language definitions. The section name must be [language.xx] > # where xx is the 2-character ISO code for the language. > > # The English name for the language. > description: English (USA) > # And the default character set for the language. > charset: utf-8 > # Whether the language is enabled or not. > enabled: yes And I replied but didn't include the list. My reply, reconstructed from memory: That change together with restarting Mailman core should allow those characters unreplaced as long as it isn't overridden in mailman.cfg. Note that it will apply only to new messages and not to previously archived ones. However, there are two issues with editing the master this way. It will affect the default settings for all languages, and it will be undone with any upgrade. It is much better to add ``` [language.en] charset: utf-8 ``` to your mailman.cfg -- 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: Include receipant address as a variable

by Mark Sapiro

On 6/4/22 09:22, chucka(a)blackforest-co.com wrote: > Thanks for the quick reply - I'm going to need a bit of schooling. I've looked at the page you point to and ... I'm lost - do I need to create a NL template? Can you give an example? &lt a href=https://mysite.com/my.pdf? &gt CLICK HERE ... The bad news is list headers and footers are plain text so HTML tags don't work. The good news is that many if not most MUAs will render things that look like URLs as clickable links. So, if you create a list:member:regular:header or list:member:regular:footer footer template that contains a line like ``` Go to https://mysite.com/my.pdf?$user_email to ... ``` That will replace the $use_email part with the recipient's lower cased email address. If you want the case-preserved email address, use `$user_delivered_to` instead of `$user_email`. For this to work, the list's Settings -> Alter Messages -> Personalize setting must be `individualize` or `full`. Also see https://wiki.list.org/x/4030707 for some caveats. -- 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: No option 'postmap_command' in section: 'postfix'

by Mark Sapiro

On 1/30/23 10:12, Odhiambo Washington wrote: > > So, since the creation of that file is prominent in the doco, maybe a note > can be added to that effect? I'm looking at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and my thought is at the paragraph Regular Expression tables remove the additional dependency of having postmap command available to Mailman. If you want to use regexp or Regular Expression tables, then add the following to Postfix’s main.cf file: add another section header Regular Expression Tables ------------------------- and change that text to Regular Expression tables are less efficient than hash tables, but they remove the additional dependency of having ``postmap`` command available to Mailman. If you want to use ``regexp`` or Regular Expression tables, then add the following to Postfix's ``main.cf`` file My thought is adding the section header makes it more clear that everything down to the Postfix + Dovecot section is for Regular Expression Tables and adding the `less efficient` phrasing notes the down side. What do you think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/8/19 9:13 AM, Nick W wrote: > I've got a couple things I need help with: The Symptom and The Problem. > > The Symptom: > > Postorius has gotten quite slow to load, taking more than 30s to load the > Subscription Requests tab. Having zero pending subscription requests (I'm on > v1.2.5), I started investigating unconfirmed subscriptions. > > I followed the commands from here[1] and got this: > > mailman shell -l your.list.id > util = getUtility(IPendings) > print(len(list(util.find(mlist=m,pend_type='subscription')))) > 1816 > > Wow, 1816 pending subscription requests. I can say for certain that my list is > not popular so these requests must have been submitted by bots. Let's get there > in The Problem. > > How can I "purge" this list? I'm willing to assume that none of these requests > are valid and would reject all unconfirmed user requests. mailman shell -l your.list.id util = getUtility(IPendings) for token, data in util.find(mlist=m, pend_type='subscription'): util.confirm(token, expunge=True) -- 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: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: > > I might also add the rule number or config filename:line, as in > > Header "{name}": rule in {file}:{n} matched value "{value}" > > This would be helpful when backtracking from a rejected message to the > cause. > > A sample expansion might be: > > Header "X-Spam": rule in foo.conf:83 matched value "yes" These rules are not in a configuration file. They are in the headermatch table in the database and the rules for a particular list are exposed on the Header filters tab in Postorius or at the REST lists/LISTNAME/header-matches endpoint. Perhaps something like {name}: header match rule, pattern "{pattern}" matched value "{value}" example: subject: header match rule, pattern "sex|long|list|of|other|bad|words" matched value "This is a post about filtering based on words like sex in the subject." but that could be just adding more clutter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Sapiro

On 2/15/21 9:07 PM, Mark Dadgar wrote: > So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. > > The resulted in a broken web interface. > > Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. > > Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. > > Anyone got a solution to this? From the tracebacks it looks like Django is broken. I would suggest starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ aside and create a new venv virtualenv /opt/mailman/mm/venv/ and then activate it and pip install everything. -- 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: Permission denied for fulltext_index

by Mark Sapiro

On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > – but the existing directory /opt/mailman/fulltext_index (and its > contents) are readable and writeable by mailman:mailman: > >> drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ >> >> -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc >> -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg >> -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg >> -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg >> -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg >> -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg >> -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > I fail to see where haystack tries (and fails) to create the directory. > FWIW, deleting threads is not a problem. It is uwsgi trying to do this. What user is it running as? Maybe you need to add that user to the `mailman` group. Deleting threads is not an issue, apparently because it doesn't try to update the search index. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

On 12/6/21 2:51 AM, Stefan Bauer wrote: > Need to bring this up again. Django now sends with STARTTLS, but mailman > itself, does still only drop mails in cleartext. > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > No starttls=1 at all :( > > Does the above settings work for anyone? > > etc/mailman3/mailman.cfg > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > smtp_verify_hostname: false > smtp_verify_cert: false > smtp_secure_mode: starttls This should work. What do you see in Mailman's smtp.log if you add ``` [logging.smtp] level: debug ``` to mailman.cfg. However, do you really need this. It will only affect delivery from Mailman to Postfix via the loopback interface on the localhost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Poor rendering of disabled registration page

by Mark Sapiro

On 12/22/24 04:16, Torge Riedel via Mailman-users wrote: > > 1. The page has a poor rendering, as far as I can see not css is referenced > 2. A would prefer that I am able to hide the registration button > > Is either of this possible to be fixed in the future? The lack of styling is fixed for django-mailman3 1.3.16 by https://gitlab.com/mailman/django-mailman3/-/merge_requests/303 You can fix it by adding the django_mailman3/templates/account/signup_closed.html file as in this patch: ``` diff --git a/django_mailman3/templates/account/signup_closed.html b/django_mailman3/templates/account/signup_closed.html new file mode 100644 index 0000000..bc83950 --- /dev/null +++ b/django_mailman3/templates/account/signup_closed.html @@ -0,0 +1,11 @@ +{% extends "account/base.html" %} + +{% load i18n %} + +{% block head_title %}{% trans "Sign Up Closed" %}{% endblock %} + +{% block content %} +<h1>{% trans "Sign Up Closed" %}</h1> + +<p>{% trans "We are sorry, but the sign up is currently closed." %}</p> +{% endblock %} ``` Disabling the signup button on the resultant page is trickier as that currently comes from the hyperkitty/templates/hyperkitty/base.html which is used all over. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by Mark Sapiro

On 1/26/22 22:21, dave--- via Mailman-users wrote: > > Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. > > The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). The password reset is for a Django user, which is distinct from a Mailman user. The users you added via the web API are Mailman users, but in order to access their lists via the web UI they have to `sign up` to create a Django account. -- 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: Mails sent by mailman-web runjobs hourly

by Mark Sapiro

On 6/16/22 03:44, Eggert Ehmke wrote: > I get lots of mails originating from the mailman-web runjobs hourly. They are > sent to mailman@<mytld>. The content looks like > > 07:00:03 [Q] INFO Enqueued 12571 > 07:00:03 [Q] INFO Enqueued 12572 > 07:00:03 [Q] INFO Enqueued 12573 > > How can I disable these emails? These message come from Django Q, https://django-q.readthedocs.io/en/latest/ I don't think there is a way to disable those specific messages which occur at times when tasks are queued instead of started immediately. They are sent to `mailman` because `mailman` owns the crontab and the crontab has no MAILTO=. You can redirect these and all other messages from hourly jobs by surrounding the hourly jobs command in the crontab with MAILTO= as in ``` MAILTO=other(a)example.com @hourly /opt/mailman/mm/bin/django-admin runjobs hourly MAILTO=mailman ``` or possibly discard them with something like ``` @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > /dev/null ``` but either of these could redirect or discard other messages from hourly jobs which you might want. -- 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: spanish localization

by Mark Sapiro

On 2/12/21 3:21 AM, Victoriano Giralt wrote: > > I just wanted to make visible that the .mo files were a "bit old". For > example, Guillermo, in this thread, pointed that the Spanish > translation was quite compelte. Actualy, I spent some hours bringing > them to 100% around Christmas. But, the .mo file for es from the pip > install --update i did recently is dated November 7th. I have > definitely added a lot of translated material from then until the end > of the year. Why do you say the .mo files are old. The timestamps are all Feb 3 02:47 which is when the package was built for PyPI. > I know the translation happens outside the development community. I > tried to point that there might be some synchronisation problem, so to > say, between the translation site and the packaging of the latest > mailman release. When things are changed on weblate, we get automatically generated merge requests to update our source. We don't always merge them immediately, but we certainly do merge all the outstanding ones before making a release. -- 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: Schedule for a resolution of #406, #410 and #437

by Mark Sapiro

On 12/14/2017 02:14 PM, Abhilash Raj wrote: > On Wed, Dec 13, 2017, at 12:11 AM, Henrik Rasmussen wrote: >> I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, >> #410<https://gitlab.com/mailman/mailman/issues/410> and >> #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It >> seems that it would not be far, as >> !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to >> be merged. > > Merged right now! :) And I have updated lists.mailman3.org and mail.python.org. Note however that <https://gitlab.com/mailman/mailman/merge_requests/322> does not fix <https://gitlab.com/mailman/mailman/issues/437> as noted at <https://gitlab.com/mailman/mailman/issues/437#note_46539617>. It also doesn't fix <https://gitlab.com/mailman/mailman/issues/441>. That appears due to a new bug related to <https://bugs.python.org/issue27321>, but which is a different message defect that causes UnicodeEncodeError to be thrown instead of KeyError. I have reported this at <https://bugs.python.org/issue32330>. I have created <https://gitlab.com/mailman/mailman/merge_requests/350> and <https://gitlab.com/mailman/mailman/merge_requests/351> to fix these issues. -- 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: So near, and yet so far (Configuring Mailman)

by Mark Sapiro

On 1/29/21 3:52 PM, Jack Lenox via Mailman-users wrote: > > Good news everyone! I've got it working. It turns out my issue was with > the mynetwork IP settings in my Postfix config. Things do now appear to > be working. Good. Thanks for the update. > My only remaining issue is that the posts aren't appearing > in the archive. Hmm. If you want our help with that, tell us if you have any non-default [archiver.*] settings in mailman.cfg and what the list's Settings -> Archiving settings are. If you are expecting HyperKitty archiving, are messages remaining queued in Mailman's var/archives/hyperkitty/spool/ directory and if so, what kind of errors do you see in Django's log? Does the value for MAILMAN_ARCHIVER_KEY in your Django settings match the api_key in the [general] section of the mailman-hyperkitty.cfg (or whatever you call it), quoted in MAILMAN_ARCHIVER_KEY but not in api_key, and is the base_url setting in the [general] section of the mailman-hyperkitty.cfg a URL that can actually access hyperkitty? -- 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: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/21/23 14:50, ceo(a)sartrack.nz wrote: > I copied the wrong debug data in my original post, it should be this: > > --------> mailman3_router router <-------- > 2023-05-22 05:13:59 115223 local_part=templist domain=sartrack.nz > 2023-05-22 05:13:59 115223 checking domains > 2023-05-22 05:13:59 115223 sartrack.nz in "sartrack.nz"? yes (matched "sartrack.nz") > 2023-05-22 05:13:59 115223 data from lookup saved for cache for +mm_domains: key 'sartrack.nz' value 'sartrack.nz' > 2023-05-22 05:13:59 115223 sartrack.nz in "+mm_domains"? yes (matched "+mm_domains") > 2023-05-22 05:13:59 115223 checking require_files > 2023-05-22 05:13:59 115223 file check: /var/lib/mailman3/lists/${local_part}@${domain} > 2023-05-22 05:13:59 115223 expanded file: /var/lib/mailman3/lists/templist(a)sartrack.nz > 2023-05-22 05:13:59 115223 stat() yielded -1 I'm not an Exim expert although I have used it. The above says Exim was unable to stat /var/lib/mailman3/lists/templist(a)sartrack.nz - does that file exist. Does exim have search permission on all the directories in the path and read permission on the file? > 2023-05-22 05:13:59 115223 errno = 2 > 2023-05-22 05:13:59 115223 mailman3_router router skipped: file check -- 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: Migration of the e-mail templates

by Mark Sapiro

On 3/6/25 2:24 PM, Markus Grandpré wrote: > > Thank you for your prompt reply. Based on a customer request, it seems > that custom templates need to be copied manually. Could you kindly > indicate which files and locations should be considered when > transferring them from the source to the target system? In MM 2.1, you could have list specific templates in directories like lists/<listname>/<language>/, domain specific templates in directories like templates/<list.host_name>/<language> and sitewide templates in directories like templates/site/<language>. In MM 3 You can create list and domain specific templates in Postorius or you can create them in sub-directories of Mailman's var/templates/ directory. List specific templates in lists/<list-id>/<language>/, domain specific templates in directories like domains/<mail-host>/<language>/ and sitewide templates in directories like site/<language>/. However, you can't just copy MM 2.1 templates because the variable replacement syntax is different and the template file names are different. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documentation of the MM 3 templating system. -- 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: Setup Mailman3 on shared webhost

by Mark Sapiro

On 11/5/18 5:42 AM, Keyra wrote: > Iam trying to setup mailman3 on a shared webhost (with ssh access). I > could use > > pip3.6 install mailman --user > > and also > > mailman info > > But when I try to start mailman using > > mailman start > > I will first get the error message > > TypeError: expected str, bytes or os.PathLike object, not NoneType > > and when I try it a second (and third etc.) time, it throws > > Starting Mailman's master runner > /usr/bin/python3.6: can't open file '/usr/bin/master': [Errno 2] No > such file or directory > > I didn't get any error messages during installation, so I guess whatever > mailman is looking for in /user/bin/master is available in my > /home/user/ folder, but I have no idea where and how to tell mailman to > look there. For more infos, this is the output of `mailman info` The 'master' command should be in the same directory as the 'mailman' command that you run. -- 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: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 05/18/2018 03:50 AM, Henrik Rasmussen wrote: > > What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. Setting the policy to Confirm or Confirm, then Moderate will do that as long as admins don't use the mass subscribe feature without a confirmed request from the user. > Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Manually. I.e.post a request to the list with a deadline for response and remove those that don't respond. Or, post to the list that everyone will need to resubscribe and then remove everyone. -- 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: Can't remove footer(s)

by Mark Sapiro

On 10/02/2018 01:03 AM, Henrik Rasmussen wrote: > > Copying /dev/null doesn't help. It seems to be the same old content of the footer files before I removed the files and restarted Mailman, as if Mailman keeps the cache. > > I've just (again) ran > # docker exec -it mailman-core mailman shell -l [LISTNAME_FQDN] >>>> getUtility(ITemplateManager).delete('list:member:digest:footer', m.list_id) >>>> getUtility(ITemplateManager).delete('list:member:regular:footer', m.list_id) > > after copying /dev/null to the files in /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/list_member_digest_footer.txt and list_member_regular_footer.txt ,but that doesn't change anything. The templates named list_member_digest_footer.txt and list_member_regular_footer.txt (with underscores) were created by import21 and set as the URIs for those templates. Had you just copied /dev/null (or otherwise made empty) those files and done nothing else, that would have done what you wanted, but since you deleted the template URIs for the list, the template names are now the default list:member:digest:footer.txt and list:member:regular:footer.txt names (with colons) and those are the empty files you need to create. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/27/21 4:04 AM, Henrik Rasmussen wrote: >> Thanks for the hint Steve. There is a Spanish message catalog as >> evidenced by the fact that the reason was translated to Spanish, but the >> issue is almost certainly that there is no >> mailman/templates/es/list:user:notice:post.txt template so we fall back >> to the one for the list's language. > > I should note that my tests on same list with same language setup did not mix languages, for some reason and I can't replicate the problem. I wonder if it could have been a timing issue or the order that I changed languages on list language and user preference. I really think it has to do with two conditions: 1) the user's preferred language is Spanish 2) there was no mailman/templates/es/list:user:notice:post.txt template There were Spanish templates in Mailman core 3.3.4, but they were misnamed, e.g. list_user_notice_post.txt instead of list:user:notice:post.txt. Did you somehow add a mailman/templates/es/list:user:notice:post.txt template after the initial test? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

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

by Mark Sapiro

On 12/22/21 6:20 PM, David Newman wrote: > > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… although that's with apache and not nginx so it may not be. > Adding a stanza for 'location /mailman/' to the nginx config above > clears the 404 error, but Postorius returns "Page not found" with no > entry in the web or MM3 logs, and a 200 OK in the Nginx logs. > > I think the URL is supposed to go to the list page in Postorius. How to > configure this so that list owners and moderators get a valid URL for > list management? I'm not sure what the solution is in this case, but a workaround would be to add url(r'^mailman/', include('postorius.urls')), to the urlpatterns list 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, 4 months

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Mark Sapiro

On 8/2/20 12:42 PM, Odhiambo Washington wrote: >> >> It is currently linked from the first paragraph at >> <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. >> > > I followed the steps outlined in the subject document and got mailman3 > running. > However, what is missing in that document is the process of setting up a > webserver for accessing the MM3 UI. > I have spent two days trying to figure out that aspect and discovered a few > things (I could be wrong in what I think): Which document are you talking about? If you mean <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…>, that talks about the Debian/Upuntu package installation and that package is quite behind the current releases. I thought that after mush back and forth with you following <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you got Mailman 3 up and running, so why would you now be trying to install the Debian/Ubuntu package? If you have issues with the <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…> document, you should contact its author. See <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

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

by Mark Sapiro

On 11/8/21 11:10 AM, dancab(a)caltech.edu wrote: > > We do have mailman(a)caltech.edu configured with valid members/owners. > We're using Postfix for the MTA. Is it possible there's a misconfiguration there? > > We've been testing the system with a handful of lists for months. The bounce you saw From: Mailman mailman(a)example.com To: Mailman Bounces mailman-bounces(a)example.com Subject: SMTP Delivery Failure may have sent because you have VERP probes enabled (verp_probes: yes in the mta section of mailman.cfg) and a user on some list reached the bounce score threshold and a Mailman attempted to send a probe and the MTA refused the message, or it may have been sent because Mailman attempted to send a message to the user and the MTA refused it. In either case, the bounce message (fake DSN) should have contained a message body like Mail to user(a)example.com failed at outgoing SMTP with the actual user's address. These fake DSNs are sent in the case where the outgoing MTA refuses a message from Mailman so there is no actual failure DSN. -- 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: EMWD Mailing Lists Down

by Mark Sapiro

On 1/15/22 5:49 PM, Sherry Xie wrote: > Hi all, > > I am an EMWD Mailman 3 customer, and I recently realized my mailing lists > are no longer working (the last email that went through was sent on > December 25, 2021). Emails I send to the lists do not show up in archives > or reach subscribers. It seems like others have had this issue before > since ownership of the company was transferred following Brian Carpenter's > passing – has anyone been able to get in touch with support or get their > issues resolved? > > I've submitted a support ticket but have no idea if this is being > monitored. I also have no way to contact the current management team, as > only their names were announced in the November 5, 2021 email from Barbara > Carpenter. Any help would be greatly appreciated – thanks in advance! There is a recent thread on this started at https://mail.python.org/archives/list/mailman-users@python.org/thread/N7NJL… and continued at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You might find something helpful 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, 3 months

[MM3-users] Re: MM3+Python3.11

by Mark Sapiro

On 3/6/23 03:38, Odhiambo Washington wrote: > Has MM3 been tested with Python3.11? Yes, but not with uWSGI which is not part of Mailman per se. > I updated a Debian VM to Python3.11, installed MM3 and migrated the > configs. However, I am unable to get past the following error: > ... > Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/wsgi.py", line > 10, in <module> > from django.core.wsgi import get_wsgi_application > File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", > line 1, in <module> > from django.utils.version import get_version > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/utils/version.py", > line 1, in <module> > import datetime > File "/usr/lib/python3.11/datetime.py", line 12, in <module> > import math as _math > ModuleNotFoundError: No module named 'math' > unable to load app 0 (mountpoint='') (callable not found or import error) This error says /usr/lib/python3.11/datetime.py can't import math. math is part of the python 3.11 standard library <https://docs.python.org/3/library/math.html>. There is something wrong with your Python 3.11 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, 1 month

[MM3-users] Re: OS upgrade - anything to take care of?

by Mark Sapiro

On 5/13/21 1:58 PM, Ruth Ivimey-Cook wrote: > > Sadly they aren't - they link to python3.6 or whatever... and even if > not, the /lib/ naming gets you as well. > > And even if that can be worked around (eg by renaming the mailman > /lib/python3.6 folder to /lib/python3.8), the python .pyc files are > /also/ versioned, so you then have to find & delete them all to force > the new interpreter to rebuild them or python falls down in a heap. Maybe I'm missing something, but it seems to me that if /usr/lib/python3.6 and /user/bin/python3.6 are gone, just creating symlinks from /usr/lib/python3.6 and /user/bin/python3.6 to the corresponding python3.8 directories would work. The .pyc files in __pycache__ should not be an issue. They are versioned and placed in a __pycache__ directory specifically so multiple python versions can coexist. See <https://www.python.org/dev/peps/pep-3147/>. Python3.8 will just make new ones. If there is some issue with this, one can always do ``` find /path/to/venv -name '*.pyc' -delete ``` -- 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: Problem with digests not being sent daily

by Mark Sapiro

On 6/22/24 20:04, Mark wrote: > > Oh? I was indeed assuming that 0 meant unlimited. The threshold was set > at 0. > > My thinking was that meant the file size was not a factor in > determining when the digest was sent and that the sending would be > triggered by the daily cron. If Send Digest Periodically is Yes, digests will be sent by the daily (or whatever schedule) cron. If a digest reaches threshold in between runnings of the cron, one will be sent at that time. > When I set the threshold very low - 10kB - it sends a digest on every post. This is expected and the same should occur if the threshold is 0. > So my understanding of what you are saying is: if the threshold is set > very large, say 100,000 kB - then a digest will be be sent by the daily > cron even if it is smaller than 100,000 kB. Correct. If Send Digest Periodically is Yes, any accumulated digest will be sent when `mailman digests --periodic` runs, regardless of size. -- 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: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 4:24 PM, Seth Seeger wrote: > > Ah hah! Right you are. I removed the offending fancy apostrophe. What about that traceback pointed to the template? (Is it something I could have figured out?) The key is this entry in the traceback. > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), This says we are trying to make a MIME text message part based on expanding the substitutions in a template. A look at the source at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… says the template is list:admin:action:post. > Is it possible to filter out UTF-8 chars from the templates when they are saved in Postorius? Not really. Postorius would have to know the character set of the list's preferred_language in order to filter anything from the template that wasn't a valid character in that character set, and I don't think it has a way to get that information from 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, 3 months

[MM3-users] Re: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 05:25, Odhiambo Washington wrote: > I looked at my list archives and saw that the latest post was on Dec 8, > 2022. > Then, because I wanted to import any posts that happened from 8th to now(), > I looked at two posts: > 1. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > This talks about 'hyperkitty_import *--since=01.01.2022* -l mylist@mydomain > my-mbox-file' > > 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html > Which talks about 'hyperkitty_import *--since='1990-01-01'* -l > mylist@mydomain my-mbox-file' The default without the since= option is to import only those messages from the mbox which are newer than the newest message in the existing archive which is exactly what you want. > I am concerned about the implication of the date format here, especially > because our species from America write their dates differently than the > British, even though > the British colonized us all :P hyperkitty_import uses python-dateutil <https://dateutil.readthedocs.io/en/stable/> to parse the since date. See <https://dateutil.readthedocs.io/en/stable/parser.html> for info on formats. -- 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: Add member to a list by email

by Mark Sapiro

On 11/12/24 02:00, via Mailman-users wrote: > Hello, > > I'm trying to add members by email with the following content. > > Recipient: testlist-request(a)xxxxxxxx.de > Email content: join address=max.mustermann(a)xxxxxxxx.de > > After I've sent this email, it still has to be confirmed in the Postorius web interface under member requests. How can I confirm membership by email, or deactivate this confirmation for moderators? You can use the email `confirm` command to confirm the request, but you need the token associated with the request to confirm it, and there is no good way to find it as it is not in the confirmation request notice sent to the list admins. To not require moderator confirmation at all, you can set the list's subscription policy. Normally, subscriptions should require confirmation by the user, a list admin or both. You can set it to require neither, but this is normally a bad idea if list addresses are accessible from outside your local network as it allows anyone to subscribe anyone else by spoofing their address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/2/22 12:04 PM, Andy Smith wrote: > > For ~6k messages it still took approx 16 hours to run that monthly > job, and during that time spewed out thousands of these errors: > > Failed to remove document 'hyperkitty.email.29351' from Whoosh: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove > self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query > w = self.writer() > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer > return SegmentWriter(self, **kwargs) > File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ > raise LockError > whoosh.index.LockError > > …so I'm not even sure if it worked. I think the warnings come from the hourly update_index job which can't obtain a lock on the index because the update_and_clean_index job already has it locked. Once the update_and_clean_index job finishes the update_index job should run and do the right thing. -- 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: Owner's or Moderator's Lists

by Mark Sapiro

On 7/31/20 11:09 AM, Johnny Cison wrote: > > It's 1.1.2, which is the python3-django-postorius version included with the > package manager on Ubuntu 18.04. > > Is there by chance a mechanism for viewing that information in 1.1.2? You have several choices. 1) Do nothing and wait for Debian/Ubuntu to upgrade the package and backport it. 2) Try upgrading Postorius from source or with pip. This will probably result in disaster, and even if it doesn't, will probably also require upgrading django-mailman3, mailmanclient and mailman core to support new features in Postorius. 3) See the merge requests at <https://gitlab.com/mailman/postorius/-/merge_requests/349>, and if you have >50 lists, <https://gitlab.com/mailman/postorius/-/merge_requests/437> and try patching installing those changes as patches. Note that!349 patches 15 files, but one of them is the change log and 12 are related to tests. The only ones you need to patch are postorius/templates/postorius/index.html and postorius/views/list.py. Likewise, these two are all you need from !437. 4) Abandon the Debian/Ubunto package and install the whole suite from source or with pip. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Question about adding addresses using the REST API

by Mark Sapiro

On 1/15/22 10:03 AM, Stephen Daniel wrote: > > The only way I've found to create a standalone address (not linked to any > user) is to create a user with that address, unlink the address, then > delete the user. > > Is there a more straightforward way to just create an address with no user? The more straightforward way is via the IUserManager create_address method. This method is not exposed directly in REST, so you can't do it via REST. My question is why do you want to? Granted when an unknown nonmember address posts to a list we create a standalone address record, but maybe we should be creating a user too. We don't because it's tricky. Suppose User A with address A posts to a list from nonmember address B. We create the standalone address B record as a nonmember, but now user A can add address B as another address. If we also created User B, this would not be possible. But again, what is your use case for creating standalone addresses? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Mark Sapiro

On 3/22/24 05:37, Helio Loureiro wrote: > Hi, > > I just found several lists have the issue like this regarding charset: > > (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members ... > Traceback (most recent call last): ... > line 109, in display_members > print(f'{address.display_name} <{address.original_email}>', > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > position 9: ordinal not in range(256) There is something in your python that has set the encoding for stdout to latin1 instead of the default utf-8. E.g. ``` $ python3.10 Python 3.10.9 (main, Dec 11 2022, 12:59:24) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> name = 'abc\u0142def' >>> print (f'{name}') abcłdef >>> import sys >>> sys.stdout.reconfigure(encoding='latin1') >>> print (f'{name}') Traceback (most recent call last): File "<stdin>", line 1, in <module> UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in position 3: ordinal not in range(256) >>> ``` -- 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: Upgrade to 3.3.2 fails

by Mark Sapiro

On 12/27/20 12:12 AM, Torge Riedel wrote: > > Nice to hear, but I fear you could be hit by this issues again, > depending on changes in the future on the table. Either when more > columns are added or on runtime when rows are added / updated. It seems that is a possibility with MySQL. It may not be an issue with MariaDB. It isn't completely clear to me from <https://mariadb.com/kb/en/innodb-limitations/#limitations-on-size>, but it seems that VARBINARY, VARCHAR, BLOB and TEXT columns are only counted as a few bytes in the "roughly half the page size" calculation. > @Mark: Would it be a good approach to split the table 'mailinglist'? I > see some groups of columns like "bounce_*" or "dmarc_*" which could be > managed in separate tables. Currently, those list attributes which are stored in tables separate from the mailinglist table are (some of) those that have lists of values rather than a simple value, but it would certainly be possible to separate groups of related attributes into separate tables. Care to submit a merge request? -- 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: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 04:35, Thomas Stein wrote: > > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE This is a packaging issue in the Debian/Ubuntu package and should be reported to Debian. See the BREAKING CHANGE item in the 1.3.10 section at <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. You need to add `allauth.account.middleware.AccountMiddleware` to the MIDDLEWARE setting 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

11 months, 4 weeks

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > Is nntp common enough these days to be a useful default runner? > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > resources (yet another Python interpreter running) for a fairly edge > case of mailing list <--> nntp transits. You raise an interesting point. By default, the runner runs, but if there are no lists gating to usenet, its queue is always empty and it mostly sleeps between waking, finding its queue empty and going back to sleep. A more significant use of resources is every (default) 5 minutes spawning `mailman gatenews` which goes through a startup process and then looks at every list figuring out there's nothing to do. We could default mailman.cfg to contain `start: no` in the runner.nntp section so people would need to enable it if they wanted it. What do others think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

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

by Mark Sapiro

On 4/9/19 11:16 AM, kelly.close(a)lrewater.com wrote: > I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. > > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… Thank you for this. I'm sure it will be helpful. One caveat. The Mailman 3 package for Ubuntu 18.04 is core version 3.1.1. This version when used with the MySQL back end database can have a serious issue. It doesn't affect the PostgreSQL back end database, only MySQL and maybe MariaDB, and it is fixed in Mailan core 3.2.0. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Can't open PID file after start.

by Mark Sapiro

On 4/21/20 10:16 PM, Torge Riedel wrote: > Hi, > > today there were some package upgrades on my server for python3. Just to > be safe I did a "systemctl restart mailman" afterwards. Calling > "systemctl status mailman" gave me the following output: > ... > Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... > Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner > Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file > /opt/mailman/var/master.pid (yet?) after start: No such file or directory > Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. > > Should I treat the PID message as an info or is it an error and > something is now broken? The file is there (content is 24182) and > timestamp is from the time where I restarted mailman. It's normal and just info. The key is "yet?" The [Service] section in Mailman's systemd service file references /opt/mailman/var/master.pid as PIDFile and systemd looks for it before Mailman has created 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

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 10:49 AM, Mark Dadgar wrote: > > Here’s what I get when I attempt the above commands: > > root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell > Python 3.8.2 (default, Apr 27 2020, 15:53:34) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. The `django-admin` command that is being run doesn't itself point to your settings. In my case, I run django-admin via a wrapper that contains ``` #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ ``` The critical things are the exports of PYTHONPATH and DJANGO_SETTINGS_MODULE. The former is the path to where your settings module lives and the latter is its name without the .py extension. -- 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: aborted connection

by Mark Sapiro

On 2/19/22 14:14, Sandor Dibuz wrote: > > It's the mailman quarterly cron job: > > # Every 15 minutes, gate messages from usenet to those lists which have > the gateway configured > */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman > gatenews; fi > > And I have no gateway enabled for any of them. Will have to find out > what mailman exactly does. And change MariaDB to verbose logging. First, If your Mailman core version is >= 3.3.5, you shouldn't be running gatenews via cron. Mailman's nntp runner runs it. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… But, that probably isn't it because in Mailman >= 3.3.5, running gatenews via cron should produce this error The gatenews command is run periodically by the nntp runner. If you are running it via cron, you should remove it from the crontab. If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the environment. However, since you have no lists using a news->mail gateway, you don't need to run gatenews at all so just remove it from the crontab. -- 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

Search results for query "sapiro"