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

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/26/25 15:12, Mark wrote: > > On 2025-06-26 16:10, Mark Sapiro wrote: > >> What does the database query >> ``` >> SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND >> context = '<IDENTIFIER>'; >> ``` >> return? > > ================================= > > The result of the query is: > +--- > uri > +---- > http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer > +---- > > I should have also said, if I delete the template, emails still use the > old footer -- not the Mailman default as I would have expected. As long as there is an entry in the template table with a uri which is not a `mailman://` scheme, that entry is cached in the file_cache table in the database with a key = the uri and a lifetime set by cache_life in the [mailman] section of mailman.cfg - default 7 days. You can delete the cached entry from the database via `mailman shell as in ``` $ 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. >>> cm = getUtility(ICacheManager) >>> uri = 'the_uri_from_the_template_table' >>> cm.get(uri, expunge=True) >>> commit() ``` You can also delete the entry from the file_cache table, but if you do that, the actual file containing the cached data will remain. To remove it, note that the file_cache table entry has a file_id. This will be a hex digest of the sha256 hash of the uri, something like `c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e` and the file is stored in the cache/ directory in Mailman's var/ directory with a path of `file_id[0:2]/file_id[2:4]/file_id`. I.e. for the above example file_id, the file will be `var/cache/c8/52/c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e`. If you remove the entry from the file_cache table without removing the file, the file will remain forever but will be overwritten if the same uri is cached again. Rather than doing any of the above, if you want to manipulate the database, just set the expires_on column in the file_cache table entry to a date in the past. -- 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: Post log?

by Mark Sapiro

On 5/5/20 5:28 PM, Mark Dadgar wrote: > Is there the equivalent of the post log from mailman 2.x available? It's not a separate log as it was in Mailman 2.1, but the information is in the smtp log. For example, here are a couple of entries relating to your post to which I'm replying: May 06 00:29:15 2020 (27320) <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> smtp to mailman-users(a)mailman3.org for 238 recips, completed in 39.014487743377686 seconds May 06 00:29:15 2020 (27320) <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> post to mailman-users(a)mailman3.org from mark(a)pdc-racing.net, 4429 bytes And here are a couple from a digest May 05 07:30:06 2020 (27320) <158866380359.27325.3146638341622587020(a)mailman.iad1.psf.io> smtp to mailman-users(a)mailman3.org for 7 recips, completed in 0.6532349586486816 seconds May 05 07:30:06 2020 (27320) <158866380359.27325.3146638341622587020(a)mailman.iad1.psf.io> post to mailman-users(a)mailman3.org from mailman-users-request(a)mailman3.org, 27406 bytes These timestamps are UTC. There are 4 categories of messages that can be customized as described at <https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm…>. There are also additional messages written by some other modules that aren't specifically configurable. The above are examples of 'every' and 'success' 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, 4 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 1/4/22 2:59 PM, David Newman wrote: > > As a followup: Is there any need or advantage to running both the > prototype and hyperkitty archivers? Only if you want to keep all the raw messages. HyperKitty only stores the message_id, subject, date, in_reply_to and sender information. Other header information is not stored in HyperKitty. The prototype archiver is intended to store messages to be delivered to some other third party archiver. > I did an installation following the venv directions, and it looks as > though the system now uses both archivers. > > If this is a duplication of effort and storage, is it safe to disable > the prototype archiver like this: > > # /etc/mailman3/mailman.cfg > .. > [archiver.prototype] > enable: no > > and then delete anything under here? > > /opt/mailman/mm/var/archives/prototype/ Yes, but you also have to go through all the lists Settings -> Archiving pages and uncheck prototype under Active archivers. You could also do this with a database query like UPDATE listarchiver SET _is_enabled = 'f' WHERE name = 'prototype'; -- 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: Mailman2 CLI commands for Mailman3

by Mark Sapiro

On 10/5/22 07:53, Dave Hall via Mailman-users wrote: > Hello. > > Sorry if this is an old topic. I'm in the process of migrating from 2.1 to > 3.2. In my use case one of the advantages of Mailman 2.1 vs services like > Google Groups has been the ability to manage lists from the command line. > Things like using sync_members to update the list for a committee when the > membership of the committee is updated one a year, or like using > find_members and remove_members to remove a user from all mailing lists > when they leave the organization. Even the ability to script mailing list > creation. > > So far I haven't found these commands in Mailman3. I hope there is a plan > to add these soon. They are there. In MM 3, the command line commands are all subcommands of the `mailman` command. See `mailman --help` where you will see subcommands including `syncmembers`, `findmember` and `delmembers`. Note that prior to 3.3.2 there were no `addmembers`, `delmembers` and `syncmembers` subcommands, but there were `modes` of the `mailman members` command that would accomplish these functions. -- 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: Managing users in postorius

by Mark Sapiro

On 9/25/24 11:08, Lieuallen, Thomas Otis wrote: > I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? In the Django admin web UI under Email addresses, you can add an address and associate it with an existing user. > Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? It should list both member and nonmember rolls. If you scroll down past Subscriptions to Ownerships, it lists owner and moderator rolls. > I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. In the Django admin UI, you can edit the user associated with an email address under Email addresses -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mark Sapiro

On 4/13/23 12:12, Mohsen Masoudfar wrote: > > In what log is that message? >>> in /var/log/mail.log > > Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. > > Postfix is running on the local host and in /etc/postfix/main.cf, this is defined: > relayhost = [email-smtp.us-east-1.amazonaws.com]:587 So Mailman is delivering to a local Postfix and that Postfix is relaying to amazonaws.com port 587. This would appear to be related somehow to the Postfix configuration. What does `postconf -n` show? Is the failing list's domain different from other lists? What happens if you set `verp_delivery_interval: 1` in the [mta] section in /etc/mailman3/mailman.cfg. This will cause Mailman to send a separate message with a VERPed envelope from to each recipient. You should then see separate mail.log messages for each recipient's delivery to amazonaws.com with success or failure for each. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Any known limit of number of lists that one can be owner/member of?

by Mark Sapiro

On 5/8/19 3:33 AM, Alan So wrote: > We have just migrated hundreds of lists from Mailman 2 to Mailman 3. It was smooth in most of the cases. However, we just notice that there are some abnormal behaviour of Postorius for particular users who are owner/member of a large number of lists. We further look into a particular user who is owner of 84 lists. When the user login Postorius, only 50 lists are displayed no matter what the number of "Results per page" is chosen. Prev/Next page cannot be clicked as there is only 1 page. See <https://gitlab.com/mailman/postorius/issues/335> > When I use the following mailman client snippet, it also displays the same 50 lists: > > lists = client.find_lists('xxx(a)yyy.com', 'owner') > for m_list in lists: > print(m_list.fqdn_listname) > > Did we hit any limit of find_lists? Is it a bug or are something wrong during the migration? find_lists defaults to count=50. What happens if you do lists = client.find_lists('xxx(a)yyy.com', 'owner', count=100) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Mark Sapiro

On 2/26/21 10:09 AM, Brian Carpenter wrote: > On 2/26/21 11:50 AM, Johannes Winter wrote: >> I didn't find any documentation on how to export list data from mm3 and >> import it into another mm3 instance. Have I missed something, or is it >> yet nonexistant? > > If you are referring to List Settings, then I don't think you can. As > Peter pointed out, you can export/import your list roster but I don't > believe that includes moderators/owners which is problematic. If you > wanted to migrate archives, then you can download an entire archive via > Hyperkitty which is exported in mbox format. You can then import that > mbox file into your new Mailman 3 list. Brian is correct. Essentially, you would need to run database queries to get all the relevant data from the database and then add it to the database of the new instance. A tool could be created to do the export and import, but it doesn't currently exist unless some user has developed one and not reported it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: invalid parameter response of the rest-api

by Mark Sapiro

On 9/21/22 14:12, gioklr71(a)gmail.com wrote: > This is the code that produce the error: > > for mail, nom in email_D.items(): # Loop over new email > print(info.subscribe(mail, nom, pre_verified=True, pre_confirmed=True, send_welcome_message=False, pre_approved=True)) > > THIS IS THE ERROR MESSAGGE: > > Traceback (most recent call last): > File "./fill_list.py", line 74, in <module> > print(info.subscribe(mail, nom, pre_verified=True, pre_confirmed=True, send_welcome_message=False, pre_approved=True)) > File "/usr/local/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 492, in subscribe > response, content = self._connection.call('members', data) > File "/usr/local/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 161, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 400: Invalid Parameter "subscriber": . > > This code works perfectly before security update from provider.... Never changed from client side. > > I've tried update mailman client: Mailman client is not the issue. The issue is the REST endpoint 'members' doesn't like the value of `subscriber` in the post data. In particular, it looks like you have an entry in `email_D.items()` with an empty value for `mail` -- 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: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 12:17 PM, eboltz(a)lhtservices.com wrote: > Mark, > > Thanks for the assistance thus far. > > When I create a new Domain within Postorius. If I set the Mail Host to 'example.com' and the Alias Domain to 'lists.example.com', create a new list such as 'staff_test', it'll default to the 'example.com' domain (which is the real domain). Then when I subscribe, I'll get an email from 'staff_test(a)example.com', when I want it to be from 'staff_test(a)lists.example.com' instead, also if I reply back to the 'staff_test(a)example.com' then I"ll get a bounce-back that it doesn't exist, but if I send to 'staff_test(a)lists.example.com' it'll go to the newly created list. I'd like all defaults to be '@lists.example.com', if that makes sense. You want to create the list with Mail Host lists.example.com and no Alias domain. Then in Postfix you want no virtual_alias_maps setting. The rest of what you show for postconf -n at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… is good. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Search results for query "sapiro"