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

[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

1 year, 2 months

[MM3-users] Re: How to create (or change) certain member preferences (in a list, or for all lists) by command line "mailman create [OPTIONS] LISTNAME" ? (Suggestion: modification of this command)

by Mark Sapiro

On 8/4/25 12:09, Wikinaut wrote: > Some member preferences - such as hide_address - cannot be set with the [OPTIONS] in the command line. > > I suggest to modify the code so that all member preferences can be set via the command line. > What do you think? > > This is how I currently patch (some) member preferences (hide_address is a variable here) in a python script, but this takes a lot of time, depending on the number of users.... YMMV. If you do this via a `mailman shell` script rather than the REST API, it should be significantly faster as it will avoid the per-user network connections. Note that changing various list options such as preferred_language does not affect existing members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 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

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

1 year, 4 months

[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

10 months

[MM3-users] Re: clearing pending db

by Mark Sapiro

On 8/8/25 09:59, Morris Jones wrote: > > But pendingdb.evict() doesn't seem to clear the list. For example, on > one of my lists: > > >>> from mailman.interfaces.pending import IPendings > >>> > >>> from zope.component import getUtility > >>> > >>> pendingdb = getUtility(IPendings) > >>> pendingdb.count() > 5040 > >>> pendingdb.evict() > >>> pendingdb.count() > 5040 > >>> pendingdb.evict() only deletes expired pendings, but by default subscriptions pending confirmation expire after 3 days, but this is set by pending_request_life in the [mailman] section of mailman.cfg. Have you set that to a long time? On the other hand in Mailman 3.3.2, subscriptions pending approval were pended with a 10 year lifetime. This was changed in 3.3.5 to a new moderator_request_life setting (default 180 days). If you just want to delete all pendings you could do ``` pendingdb = getUtility(IPendings) for pending in pendingdb: pendingdb.confirm(pending[0], expunge=True) # and if doing this in mailman shell commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 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

6 years, 6 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, 11 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, 11 months

Search results for query "sapiro"