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

[MM3-users] Re: Removing Moderators

by Mark Sapiro

On 7/21/24 13:39, steve.bachinsky(a)tena-sda.org wrote: > In the case of adding a moderator based on an email address, it is unclear whether there is already a user associated with that email address or not. So I tried to use the "moderator = user_manager.make_user(email)" interface. However, when trying to use "mlist.subscribe(moderator, MemberRole.moderator)", I get an error that User must have preferred address. And while I can set "moderator.preferred_address = email", I then get error that there is no attribute "verified_on", and I can't set that on the User. moderator.preferred_address needs to be set to an Address object, not an email. I.e. moderator.preferred_address = user_manager.get_address(email) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/26/25 04:25, Mark wrote: > > A footer template is created and initially it works as expected. > > Editing the footer template sees the new content written to the database, > > In addition to viewing the edited content in the database, the new > template can also be viewed in Lynx on localhost at: > > http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer > > The problem is that the original template is being cached somewhere and > the old footer persists in new emails. What does the database query ``` SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND context = '<IDENTIFIER>'; ``` return? -- 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: mail loops back to myself

by Mark Sapiro

On 6/13/25 01:59, Florian Sukup wrote: > > > On 6/13/25 01:58, Mark Sapiro wrote: > >> but I'm at a loss to understand the issue, unless your >> /etc/postfix/master.cf is missing an uncommented entry for lmtp like >> ``` >> lmtp unix - - y - - lmtp >> ``` >> > > I found it there, here is my master.cf: I realized after the fact that that probably wasn't the issue because it probably would have logged an error. > mailman unix - n n - - pipe > flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Is the last line a problem? It seems to be from mailman2. It's a Debian thing for an unsupported MM 2.1 process to deliver mail to Mailman. It doesn't do any harm if it's not referenced in main.cf. > Is there a possibility to debug in more detail? To find out when and > where it takes the wrong turn? I'm unable to see where this is going wrong. I think it is a Postfix issue, not a Mailman issue per se, and while we make a best effort to help with Postfix-Mailman integration issues we are not the primary support resource for Postfix which is the postfix-users(a)postfix.org mailing list. See https://www.postfix.org/lists.html for info on subscribing and posting. Also, since you are dealing with Debian packages, the primary support resource is Debian. 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

1 year, 2 months

[MM3-users] Re: howto reallow a banned email ?

by Mark Sapiro

On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: > > By mistake a user has been banned to post to mailman list. How can I > allow him not only to post but also to become a member of a list ? > > I have not found any info on the web, or I have been unable to search > correctly. Do you have the Postorius web UI in your installation? If so go to the list's Ban List and remove the unwanted entry. Or is this perhaps a Mailman 2 question? If so you'll find the ban_list in the web admin UI at Privacy options... -> Subscription rules. -- 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 REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/26/20 12:00 AM, joseverde(a)gmail.com wrote: > Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: > > Something went wrong > Mailman REST API not available. Please start Mailman core. Do your settings in the webservice section of mailman.cfg for things like: admin_pass: restpass admin_user: restadmin hostname: localhost port: 8001 (Defaults shoun) match your Django settings MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' MAILMAN_REST_API_URL = 'http://localhost:8001' Also, is Mailman's `rest` runner running ps -fwwA|grep runner=rest should show 3 processes. The runner and 2 workers. -- 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: Cron error

by Mark Sapiro

On 9/30/20 8:21 AM, gordon(a)dickens.com wrote: > The error has not re-occurred in the last 24 hours since I removed the lock file as Mark recommended. So, I am hopefull that the problem is solved. As I suggested at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, I don't think the underlying issue was with the `mailman digests --send` run by cron. I think any `mailman` command would have failed as long as the dbcreate.db lock residue was in /var/lib/mailman3/locks/. The question is what left that there in the first place. Did you manually run any `mailman` commands that terminated abnormally or were killed in the day before this started? -- 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: Migrating from debian package to Virtualenv

by Mark Sapiro

On 6/8/20 12:45 PM, Ryan Morash wrote: > We currently have our Mailman3 instance installed using the packages in Debian's repository. We want to migrate over to a virtualenv setup as described here: https://docs.mailman3.org/en/latest/install/virtualenv.html. Is there any thing we should be aware of for migrating data? Assuming you will be using the same DBM, I think you could just ensure that your mailman.cfg settings for ``` [mailman] layout: ``` and ``` [paths.<layout_value>] var_dir: ``` end up pointing var_dir at your existing Mailman var/ directory and the [database] section in mailman.cfg and the DATABASES definition in your Django settings reference your existing database(s). -- 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: Confirmation emails to Users has wrong domain name (example.com!)

by Mark Sapiro

On 10/2/21 4:26 AM, Odhiambo Washington wrote: > On Thu, Sep 30, 2021 at 4:09 PM Abhilash Raj <maxking(a)asynchronous.in> > wrote: >> >> Yes, please update it to have SITE_ID = 2 to correspond to the site you >> want and restart. > > > I did this, but there is still a problem: The hyperkitty URL still shows > example.com. > Maybe I need to re-import the database to clear this? The SITE_ID setting affects the domain displayed at the top left of HyperKitty pages. Is this the correct domain? What hyperkitty URL are you talking about? -- 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: Speed/progress of update_index_one_list?

by Mark Sapiro

On 1/14/22 12:38 AM, Philip Colmer wrote: > I have now switched to Xapian but, in a way, my original questions still > stand. Is there a way of monitoring the progress of > "update_index_one_list"? What can I do to the specification of the server > to make that process go (much) faster? HyperKitty does the indexing by calling the Haystack update_index command. See https://django-haystack.readthedocs.io/en/master/management_commands.html#u… This command has options such as --verbosity and --workers. I think verbosity is set from the option provided to update_index_one_list and if set to 2 will give some progress info. workers could increase parallelism but is unconditionally passed by hyperkitty as 0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Mailman3 Queues Documentation

by Mark Sapiro

On 2/19/26 14:18, msok--- via Mailman-users wrote: > Thanks, Mark, you are saving my life here. > > It's working now due to permission issued because I used root account to create mailing list in bash command. Never run the `mailman` command as `root` or any other than the Mailman user, `list` in your case. > by the way, my mailman3 installed on Debian 13 OS via Debian package. > I didn't create mailman user. Now, it is running under list:list That is the Debian way. Don't try to change it unless you want to rip out the Debian packages and reinstall following <https://docs.mailman3.org/en/latest/install/virtualenv.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

Search results for query "sapiro"