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

[MM3-users] Re: How to store additional information about lists?

by Mark Sapiro

On 5/25/21 12:28 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > private: hand-selected people, think about e.g. board or steering > > committees internal discussions. Of course, the archive (if there is > > any) should be restricted to the actual members. Posting to these > > lists is currently not restricted, so no derivation needed from the > > current set in postorius. > > This is already possible by requiring admin approval, or by setting > the ban list to something that matches everything like "^.". The ban list can't be used in this way. A banned address can't be subscribed by any means including admin action. And even if an admin temporarily removes the ban, subscribes the address and then restores the ban, the now banned member can't post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: How to delete user completely?

by Mark Sapiro

On 1/21/22 4:32 PM, William Oliver wrote: > I have installed mailman3 and it's up and running great. However, I > noticed that, during a mass subscribe, I mis-typed an address, e.g. > name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe > the bad address, but I haven't found a "delete" option under Users or > anywhere else. How to I purge a user from the users list? You need to do it via REST or `mailman shell`. In mailman shell, ``` >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') >>> um.delete_user(usr) >>> commit() ``` > As a related question, in docs.mailman.org, I can find a list member's > manual, but I can't seem to find an admin manual. Is there one? No, not per se. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Pb with archive display

by Mark Sapiro

On 5/4/22 05:45, Pierre Malard via Mailman-users wrote: > > On the other hand Mailman3 does not seem to take into account the display of the archives. The contributions are indeed in the directory "/var/lib/mailman3/archives/hyperkitty/spool" but HyperKitty does not take them into account when displayed on the Web interface. > > Is this normal? No. The messages are in /var/lib/mailman3/archives/hyperkitty/spool because delivery to HyperKitty failed. There should be messages in Mailman's var/logs/mailman about the failures. The setting for api_key in mailman-hyperkitty.cfg must match the setting for MAILMAN_ARCHIVER_KEY in your Django settings. Also, the setting for base_url in mailman-hyperkitty.cfg must be good. If you append `/api` to that url, the result should return a page of documentation of HyperKitty's REST API. Also see this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 02:37, Odhiambo Washington wrote: > > Here again, Google-fu came to the rescue. I added the following line to > settings_local.py and the warnings were suppressed. > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > I need to understand how this affects everything and how this is likely to > impact the functionality of MM3. What is the proper solution for this? > And should it be django.db.models.BigAutoField or > django.db.models.AutoField? Which is which? Prior to Django 3.2 Django set default primary keys to 32 bit integers. In 3.2 Django introduced the possibility to set default primary keys to 64 bit integers by setting the type to django.db.models.BigAutoField. Thus, putting ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your settings will maintain compatibility with pre 3.2 versions and existing tables and this is the correct thing to do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/3/23 23:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 > > The upgrade procedure I did all the times is > > pip install --upgrade django-mailman3 mailman mailman-hyperkitty > mailmanclient postorius django hyperkitty uwsgi mod-wsgi > > and if I see some trouble I did it with a --force-reinstall parameter > (not that I remember it happened last times that I upgraded) > > (and then the collectstatic, etc.) > > If I missed something, I don't know. Mailman 3.3.5, 3.3.6 and 3.3.7 all required aiosmtpd>=1.4.1 so your prior upgrades should have installed aiosmtpd>=1.4.1. Possibly aiosmtpd>=1.4.1 was installed somewhere, but your jail configuration was such that it wasn't the one actually used by lmtp runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: How to change the language in mailman3

by Mark Sapiro

On 7/22/20 10:17 AM, blackout69 wrote: > Hi everybody, > > with > $sudo updatedb > $sudo locate,I don't find these path Mailman core in mailman/messages/ > Hyperkitty in hyperkitty/local/ > django-mailman3 in django-mailman3/local/ > postorius in postorius/local/from here > https://www.pratico.work/file.tar.xz you can download the following > files: my file /usr/share/mailman3-web/settings_local.py $sudo locate > it/LC_MESSAGES > mypath.txt I can't (re)generate the .mo files because > there are no path above. Thank You for help Max I'm having trouble deciphering what you are saying, however, the actual paths you are looking for are: For Mailman core: mailman/messages/it/LC_MESSAGES/mailman.po For HyperKitty: hyperkitty/locale/it/LC_MESSAGES/django.po For djangomailman3: django_mailman3/locale/it/LC_MESSAGES/django.po For Postorius: postorius/locale/it/LC_MESSAGES/django.po Note 'locale', not 'local' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Posterious membership listing for non-owner/moderators?

by Mark Sapiro

On 3/11/21 4:58 AM, Duane Raymond wrote: > Hi, > > I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? > > I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. > > (as usual before asking the question I explored a lot and searched the archives/documentation). Maybe you should also check issues. This is <https://gitlab.com/mailman/postorius/-/issues/369> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/14/22 21:33, Stephen J. Turnbull wrote: > > Whether we *want* to do that depends on how much trouble that causes > for our main constituency (list and site admins), and whether we can > provide discoverable documentation of the problem. My take is that > this seems to be an extremely rare problem, and at least some MUAs are > able to read the message, so we should let it through. First, we are not silently dropping this message. We are rejecting it at LMTP time so the sender should be notified. Then the broader question is should we accept all messages with defects, almost all of which are spam, or only certain defects and which ones. I note that Apple has now released Mail 16 so maybe they've fixed this. My macs are still on Big Sur, so I can't test this. -- 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: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 04:00, andrea.janna.unipd(a)gmail.com wrote: > > Yes it's mailman gatenews that triggers mariadbd "[Warning] Aborted connection" log entries. > I don't use this feature so as a workaround I set a large gatenews_every interval in mailman.cfg. > > [nntp] > gatenews_every: 1000000m Or you can do as Danil does <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and put ``` [runner.nntp] start: no ``` in mailman.cfg. However, it is unclear what in gatenews would do this. Assuming you have no lists for which gateway_to_mail is true, all gatenews will do is ``` def process_lists(glock): list_manager = getUtility(IListManager) for mlist in list_manager.mailing_lists: glock.refresh() listname = mlist.fqdn_listname if not mlist.gateway_to_mail: continue ``` The database operations involved in this are things Mailman core is doing all the time, presumably without issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/27/20 4:29 AM, Odhiambo Washington wrote: > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Is there an empty /opt/mailman/mm/__init__.py file? >> > > No. There has to be one. Create it and then Django will be able to import your settings. See the first line after Create directories: ... and files: at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69> > Yes. However, that also means the /opt/mailman should be owned by mailman3, > right? So I wasn't quite mistaken. It doesn't matter what user actually `owns` this directory and its subordinates as long as the Mailman user, mailman3 in your case, can read and write there. Of course, making everything owned by the Mailman user is the easiest way to ensure this. Note also that any commands in /opt/mailman/mm/bin need to be run as the Mailman user and not root. Running them as root can create things owned by root the can't be read by the Mailman user. > PS: There is the issue with qcluster, which doesn't seem to have been > documented in details from your "experience". > I see the configuration file and the init script, but not how to install > it, or whether the procedure already installed it. qcluster is part of Django. If you have this # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } or similar uncommented in your Django settings, and also 'django_q' in your INSTALLED_APPS, it's there and all you need to do is run /opt/mailman/mm/bin/django-admin qcluster to run it, but it should be run as a service via init or ?? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Search results for query "sapiro"