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

[MM3-users] Re: Header and footer templates in MM3

by Mark Sapiro

On 1/19/20 1:15 AM, Gila Halpern wrote: > I read the earlier message from Peter Mueller about message decoration, and > where the templates are in the file system. However, when I edit the > header and footer templates in Postorius, those templates do not appear in > the location specified. Should I be looking somewhere else? The templates created in Postorius are created in the postorius_emailtemplate table in Mailman's database and referenced via URLs like 'https://example.com/mailman3/api/templates/list/<list-id>/<template-name>'. I.e., they are not stored in the file system. > (I intend to > write a program to rotate though several headers/footers, so I need to know > where to have it write to.) If Postorius has set a template for a list, it has set the URI for that template and list to one similar to that above and that URI ultimately references the template in the database. You have choices. You can set the templates in Postorius and your program can do database queries to rotate the template text, or you can set the template URIs via Mailman's TemplateManager to file system paths or not set them and use the default paths (deleting them in Postorius will leave them unset). See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Mark Sapiro

On 8/7/21 4:35 AM, Thomas Möhle via Mailman-users wrote: > Hey, > > I have set up mailman3 with mailman3-web on my mailserver and after > upgrading to Ubuntu 21.04 my setup stopped working. In what way? Do list posts get delivered? What works and what doesn't? What are the observable symptoms for things that don't work? > I can see repeating > log entries of mailman trying to reach something within hyperkitty and > getting an error. The same constant repeating cycle of log entries is > visible in my log files. It appears from your logs that Mailman core's attempts to reach the hyperkitty api may be failing. Mailman core uses the mailman_hyperkitty module to communicate with the hyperkitty api to get the url at which a message will be stored and to deliver a message to hyperkitty. This may not be working. There are probably unarchived messages in Mailman's var/archives/hyperkitty/spool/ directory. What do you get for example if you go in a web browser with hyperkitty running to https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… And please don't post secret keys and change the value of api_key: in mailman-hyperkitty.cfg and the corresponding value in MAILMAN_ARCHIVER_KEY in your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: messages in queue/shunt

by Mark Sapiro

On 5/7/23 08:39, Christian via Mailman-users wrote: > Can/should old messages residing in queue/shunt be manually removed? I see > they were delivered. Is there any reason to leave them there? Thank you!! If they were delivered, they shouldn't be in queue/shunt/. Messages are shunted (placed in queue/shunt/) because of some exception in processing that caused processing to be aborted. It is possible for a message to be shunted even though it was delivered if the exception that caused it to be shunted occurred in the archive runner or the digest runner. When a message is shunted, an entry is made in mailman.log indicating the reason and giving a traceback. This information can be used to determine if there is some issue in Mailman that caused the exception, and if so, that issue can be fixed and the message's processing continued via `mailman unshunt`. Also, pointing `mailman qfile` at the shunted .pck file will not only display the raw message, but also metadata indicating which queue was being processed when the exception occurred. In any case, If the message is not going to be unshunted because it was spam or too old to be relevant or whatever, it should be removed from queue/shunt/ if for no other reason than so a future `mailman unshunt` won't requeue 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: Uncaught runner exception

by Mark Sapiro

On 4/8/20 1:17 PM, Wolfgang Bock via Mailman-users wrote: > > Checked the ownership .... > ls -la: > /var/lib/mailman3/cache > drwxrwx--- 3 root root 4096 Nov 9 22:27 61 > drwxrwx--- 3 root root 4096 Feb 3 17:37 6c > drwxrwx--- 3 root root 4096 Nov 12 11:59 71 > drwxrwx--- 3 root root 4096 Nov 6 12:01 72 > drwxrwx--- 3 root root 4096 Feb 5 21:52 7d > drwxrwx--- 3 root root 4096 Feb 5 23:05 8b > drwxrwx--- 3 root root 4096 Nov 12 23:41 94 > drwxrwx--- 3 root root 4096 Nov 7 08:31 ae > drwxrwx--- 3 root root 4096 Nov 12 23:40 fa It seems at some point Mailman core was run as 'root' rather than 'list'. ... > Changed the ownership for /var/lib/mailman3/cache to list:list and from that point my lists are responding. > > Same problem occurs before fort he list-directory, which I corrected some days ago. > > Is the ownship misconfiguration a coincidence or did I made a mistake somewhere?? This is a Debian/Ubuntu package question. I'm guessing but all of Mailman core and Mailman web should always be run as user:group list:list in your case. It appears that at some point these were started as root. Whether this is something you did wrong or an issue with whatever init/systemd scripts run these things, I can't say. -- 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: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Mark Sapiro

On 9/23/20 4:59 AM, cristian.bianchi(a)usi.ch wrote: > I have a similar problem with mailman 3.2.1 (debian package): > > # mailman info > GNU Mailman 3.2.1 (La Villa Strangiato) > Python 3.7.3 (default, Jul 25 2020, 13:03:44) > [GCC 8.3.0] > > the messages are not archived even if the key is set and hyperkitty is checked as active archiver. > > To analyze the problem I set DEBUG = True in /etc/mailman3/mailman-web.py. > In debug mode the problem does not occur, but this second problem appears: > https://gitlab.com/mailman/hyperkitty/-/issues/84 I don't understand. https://gitlab.com/mailman/hyperkitty/-/issues/84 is supposed to be fixed. Are you saying it isn't. > How can I fix it? Start by finding all the log messages relating to this archiving failure. If there are exceptions with tracebacks, what are they? Also, are there messages in var/archives/hyperkitty/spool/? If so, there will also be ''Exception in the HyperKitty archiver:' messages with an exception logged in mailman.log for each such message every time there is a list post. Note that HyperKitty is not a service that runs like Mailman core. The only check is can you access it via the web? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: How to add new lists?

by Mark Sapiro

On 11/2/22 15:21, fstltna--- via Mailman-users wrote: > I have been able to get the web interface up and the default "mailman@" address is there and appears in the list of lists, but when I add a list from the command line with a command like "mailman create foo(a)ourlists.gameplayer.club" it does not return a error and using "mailman lists" lists it as existing. However there is no new entries in the /etc/aliases file and the new list doesn't appear in the web interface... I am confused. How did you install Mailman. There is no default `mailman` address and Mailman doesn't create postfix mappings in /etc/aliases. If you have set ``` configuration: python:mailman.config.postfix ``` in the [mta] section of mailman.cfg, various mappings are created in Mailman's var/data directory? Configuration for Postfix is described at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. There is also information there about other MTAs. As far as your list created with `mailman create` not appearing in the web UI, is the web UI communicating with the Mailman core instance in which you created the list. What does `mailman info` show and in particular is the host and port in its `REST root url` the same as that set in `MAILMAN_REST_API_URL` in Django's settings? -- 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: Trouble Installing Mailman3

by Mark Sapiro

On 6/5/25 08:40, Henry Hartley via Mailman-users wrote: > > The other thing I had to do that was different to the instructions was to use pip to install setuptools. I got to a point where I had an error message that said "ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0" but when I ran "apt install python3-setuptools" it reported that it was "already the newest version (68.1.2-2ubuntu1.2)". However, running pip install setuptools (on a whim) installed version 80.9.0. After that "pip install mailman" worked. Perhaps I should have known this. I feel that making sure setuptools is properly installed might be something to add to the installation instructions. It depends how you create the venv. `virtualenv venv` will create the venv with `pip`, `setuptools` and `wheel` installed, but our install doc says do `python3 -m venv venv` and that only installs `pip` in the venv. I'll update the doc. > The next step in the instructions has me create /etc/mailman3/mailman.cfg. The first thing in that file is shown as: > > [paths.here] > var_dir: /opt/mailman/mm/var > > Looking in /opt/mailman, there is no mm directory. Should that have been created, or is that something I need to create myself? You need to create it. I'll update the doc for that too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 6 days

[MM3-users] Re: Templates

by Mark Sapiro

On 09/28/2017 01:56 PM, David Krantz wrote: > Hi again, > > I had the problem with getting two footers, i.e. two expansions of the > template. After some digging in the source code I found out that the > decorator made one expansion (without personalization) and that the > delivery handling made another (with personalization). So I hacked > pipelines/builtin.py with a new pipeline that excluded the decorate > step, recompiled and changed to that pipeline for my personalized > list. That worked. Nothing like a bit of shotgun debugging in > production. > > That solves my immediate problem. Is there a known and recommended way > of configuring personalized delivery so that you only get the > personalized footer? I have ideas, but I probably should share them > with the developer list instead. :-) This is clearly a bug and should be fixed. If you report this issue at <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. > Of course this very nice functionality is a bit buried. I activated it > using the interactive python shell, seems less risky than changing the > database directly. There are many core settings not (yet) exposed in Postorius. This is something we need to fix, but it takes time and resources. In the mean time, 'mailman shell' is probably the best way to set them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: trying to clean up the "held messages" mess

by Mark Sapiro

On 5/28/21 12:37 AM, Bjoern Franke wrote: > Hi, > > I migrated a Mailman3 installation on Debian10 yesterday evening from > Debian packages to PIP (thanks to [1]). > > I think some bugs which existed before are now cleaned out, but mailman > still threw exceptions when trying to get the "held messages". What exceptions? Note that there is a lot of cleanup in the as yet unreleased core 3.3.5. You might consider installing that. To do so, in your virtualenv as the Mailman user do ``` pip install --upgrade git+https://gitlab.com/mailman/mailman ``` > The amount of held messages is now reduced, but e.g. a list with 120 > held messages before has till 59 held messages. And now I'm confused: > where are they? The held message entries are in the _request table with `request_type` = 1. For those entries, `key` is the message-id and `data_hash` is the `token` in the pended table and the `id` in the pended table is the `pended_id` of the related entries in the pendedkeyvalue table. The message itself is stored in the file system and is pointed to by the entry in the message table with the corresponding message-id. The exceptions you see are because entries are missing from the pended, pendedkeyvalue and/or message tables. -- 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: trying to clean up the "held messages" mess

by Mark Sapiro

On 5/28/21 11:32 AM, Bjoern Franke wrote: > > But since the upgrade from 3.2.1 to 3.3.x the list owners are spammed with > > ---- > some.listmember(a)domain.tld's subscription has been disabled on > nordwest(a)lists.ffnw.de due to their bounce score > exceeding the mailing list's bounce_score_threshold. This should really be better documented (sigh) Prior to Mailman 3.3.1, bounces were recorded but not processed. Beginning with Mailman 3.3.1, bounces are now properly processed. The issue is all those unprocessed bounces were still in the bounceevent table in the database and even though they were old and likely irrelevant, upon upgrade they were all processed resulting in many spurious disabling of delivery. This is disruptive, but is a one time thing and in your case is now done. For those who haven't yet upgraded, there are two ways to avoid this. The best way is before starting Mailman after upgrading, set ``` [mta] verp_probes: yes ``` in mailman.cfg to enable bounce probes. With probes enabled, users whose score reaches threshold are sent a probe message and their delivery is only disabled if the probe bounces which will only happen for currently undeliverable addresses. The other way is before starting Mailman after upgrading, run a database query similar to ``` UPDATE bounceevent SET processed = 1; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Search results for query "sapiro"