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

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

by Mark Sapiro

On 5/14/19 12:18 AM, Alan So wrote: > One more finding. If the user select "All" in the "Filter by role" box, nothing can be shown. So, that shouldn't be related to the default limit of 50 with find_lists. Otherwise, at least some lists should be displayed. If you are saying no lists are shown when the user selects "all", is it possible that no lists are advertised? I.e., all lists have Settings -> List Identity -> Show list on index page = No. If that is not the case the advertised list should be shown on the "all" view or when not logged in. I don't see an issue at <https://lists.mailman3.org/mailman3/lists/> or <https://mail.python.org/mailman3/lists/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Language Support In Templates

by Mark Sapiro

On 1/25/21 12:18 PM, Brian Carpenter wrote: > Hello MM3 Users, > > I have a question regarding the use of templates in different languages. > I created a template for the unsubscribe notification in Postorius in > Greek. The template shows up fine in Greek via Postorius. However the > email that is sent out has a bunch of question marks where the Greek > should be: This is a bug in Postorius. I just reported it at <https://gitlab.com/mailman/postorius/-/issues/465>. There are a couple of workarounds. Assuming the list's preferred language is Greek (el), You can put the template in Mailman's var/templates/lists/<list-id>/el/ directory (creating it if necessary and ensuring it's readable by the Mailman user. You can set ``` [language.master] charset: utf-8 ``` in mailman.cfg to change the default character set from ascii to utf-8 -- 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: Dealing with recipients' servers spam filtering

by Mark Sapiro

On 2/13/21 7:31 AM, Gilles Filippini wrote: > > Writing down what I've learned so far, in case it may help others: > > 1- The lists server DNS record (lists.example.com) should be of 'A' type > (no 'ALIAS' or 'CNAME') Not only that, reverse lookup of the IP in the A record must point back to the same (lists.example.com) domain. See, e.g., <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. > 2- The SPF record should be set for the very same DNS name; e.g. > lists.example.com (not just example.com) > 3- This record seems to work for my server: > lists.example.com. IN TXT "v=spf1 ip4:123.123.123.123 -all" > Where the IP address is the same as the one registered for the 'A' > record. And you should also DKIM sign outgoing mail. -- 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: 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, 6 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

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

3 years, 7 months

[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

[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

2 years, 8 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 6:07 PM, David Newman wrote: > On 1/7/22 4:32 PM, Mark Sapiro wrote: > >> I suspect an issue trying to connect to the MTA to send the messages. >> This can be caused by permission errors. Check permissions on >> Mailman's var/templates/* > > Bingo. This list had regular and digest footer templates with 0644 > permissions owned by root:root, and there was an exception and traceback > for the most recent message in shunt about the permissions issue. That comes from running `mailman import21` as `root`. Always run `mailman` commands as the Mailman user. > I've changed ownership to mailman:mailman and restarted the mailman3 > service. > > As soon as I fixed this, my inbox filled with test messages... Good! >> Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in >> mailman.log? > > Yes, lots. This might or might not be a different issue. It is exactly this issue which is now corrected. > As I mentioned earlier, the most recent message in shunt was from 0000 > hours today. There are many "Cannot connect" messages since then, but > none since fixing the issue above. The Cannot connect messages are from the issue of ownership of the templates and Mailman's out runner continually retrying the send. This is separate from the shunted messages. > Seems OK now. The superuser sees all posts after the unshunt action. So it appears that you ran `mailman unshunt` and the shunted messages were successfully processed, so whatever caused them to be shunted in the first place is fixed. Individual messages don't get shunted because of this template ownership issue, but it may be that digests do get shunted for this reason. -- 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: 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, 4 months

Search results for query "sapiro"