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

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 12/1/22 01:43, Jan Eden via Mailman-users wrote: > > There are currently 5 (test) threads in the archive. After changing the > PATH in the HAYSTACK_CONNECTIONS dict to /opt/mailman/fulltext_index, > and fixing the issue with MAILMAN_ARCHIVER_FROM above, > /opt/mailman/web/logs/mailmanweb.log does not display new error > messages, but I do not get any suggestions for reattaching threads, and > a search for a specific thread subject ("Third test") does not return > any results. By "search for a specific thread subject", do you mean searching via the search box at the top of HyperKitty pages? This relies on the search index for Haystack (Whoosh in your case). This index is updated by the HyperKitty update_index job. Assuming you have set up the cron jobs for Django <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>, this will be run hourly and posts added to the archive in the last hour won't be indexed. > So reattachment works in principle, but the suggest/search function does > not. Reattachment suggest doesn't depend on the search index, but it does depend on loosely matching thread subjects. -- 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: content filtering in version 3.1

by Mark Sapiro

Resending with proper inline code quoting for the archive. 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, 11 months

[MM3-users] Re: Announce Only List

by Mark Sapiro

On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > So if we want to make a list announce only (e.g. only specific folks) can post, I've found I can set the list settings to automatically discard messages from members and non-members. Then I go into the individual permissions on each user to be allowed to post without moderation. This works fine, however it seems cumbersome. My expected solution was to make the announce only members moderators - however it appears being a moderator does not give any special ability to post to the list (nor does it appear to make you a 'member' from the point of mailman when sending messages to the list, since a moderator who is not a subscriber gets treated like a nonmember from the posting permissions perspective). Is this correct? Yes, your observations are correct. This is how it's always been, at least from the beginning of Mailman 2.1. There is an alternative. Set a moderator_password for the list. Then anyone can successfully post with an `Approved: <password>` header or pseudo header if they know the password. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…>. -- 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: Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?

by Mark Sapiro

On 5/24/24 7:41 PM, Keith Christian wrote: > > mailman3 was installed into the below virtual environment: > (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary > Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or > any other supporting programs be installed into this virtual > environment ? If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you will install Mailman core, psycopg2-binary, mailman-web and mailman-hyperkitty in the venv. mailman-web will install Django, django-mailman3, MailmanClient, HyperKitty and Postorius as dependencies in the venv. > PostgreSQL and Postfix have been successfully installed outside of the > mailman3 virtual environment and start properly, I assume this is > correct. Since these are not python packages, they and sassc (or Dart-Sass) are installed outside the venv. Also, Postfix in particular and possibly PostgreSQL may be used by things other than Mailman so you don't want them in the venv even if they could be installed there. -- 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: 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

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

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

1 year, 2 months

[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, 8 months

Search results for query "sapiro"