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

[MM3-users] Re: 12/24 hour clock ?

by Mark Sapiro

On 11/28/20 7:18 AM, Per Jessen wrote: > Hi all > > at openSUSE we have recently migrated to mailman3, and we seem to be > having a couple of teething issues: > > a) hyperkitty and postorius both seem to insist on using a 12 hour clock > format, no matter what the user has set. Is there a way of changing it > system-wide ? This is a Django setting. Try TIME_FORMAT = 'H' in settings_local.py. See https://docs.djangoproject.com/en/3.1/ref/settings/#time-format and https://docs.djangoproject.com/en/3.1/ref/templates/builtins/#std:templatef… > b) overriding the default set of footers - despite having set the > template "list:member:regular:footer" to empty for a specific list, I > am still getting the default footers attached. How did you set the template to empty? it works for me in Postorius from the HEAD of the gitlab branch and should work with any Postorius >= 1.3.0 Note that when you set a template in Postorius, it sets the URI in Mailman core for that template to https://<HOST>/<PATH>/api/templates/list/<LIST-ID>/<TEMPLATE-NAME> where the https://<HOST>/<PATH> part is the Django setting for POSTORIUS_TEMPLATE_BASE_URL. Is that URI accessible from the Mailman core host machine? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 6/6/24 11:22 AM, Marcus Bautze wrote: > Hi, > > Sorry, that was a wrong information in my mail . I already changed the base url to your suggestion as I wrote the mail (and forgot to change it in the mail) but i‘m getting the same error :-( I have some questions. At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "Thank you, archiver is now starting. Now there's another problem:". Does this mean messages are being archived in HyperKitty or are they accumulating in (I think the Debian path is) /var/lib/mailman/archives/hyperkitty/spool/? At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys." To be clear, in mailman-web.py the key is quoted and in mailman-hyperkitty.cfg it is not. E.g., in mailman-hyperkitty.cfg api_key: Some_key and in mailman-web.py MAILMAN_ARCHIVER_KEY = 'Some_key' What are your versions for mailman-hyperkitty and HyperKitty? HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 and if I recall corectly, at least one Debian package was shipped with this incompatibility -- 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: how to mass change users options ?

by Mark Sapiro

On 4/30/22 02:13, Yvan ♞ wrote: > Hello, I transfered a mailing list from mailman to mailman 3, how can I > change all users options in mass ? > delivery status and receive own posting are blank by default (250 > members is too long one by one..) The `blank` value for for a setting only means that the user has no list based setting for that property. This means either the user's address based value if any applies, otherwise the Mailman global value applies. That said, if you imported the list with `mailman import21`, the Mailman 2.1 settings should have been imported. Finally, you could change a setting for all list members using `mailman shell`. For example ``` $ bin/mailman shell -l list(a)example.com 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. The variable 'm' is the list(a)example.com mailing list >>> for member in m.members.members: ... member.preferences.delivery_status = DeliveryStatus.enabled ... member.preferences.receive_own_postings = True ... >>> commit() ``` But this is probably unnecessary as the global settings probably apply and are probably set appropriately. -- 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: New messages are not archived - may be a path issue

by Mark Sapiro

On 10/20/23 05:31, Wikinaut wrote: > > The built-in template (mailman-hyperkitty.cfg) perhaps needs to be fixed as well (hyperkitty wrong, archive correct)? > # However, if your Mailman installation is accessed via HTTPS, the URL needs > # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty) > # base_url: http://localhost/mailman3/hyperkitty/ > > this line perhaps needs to be changed to > # base_url: http://localhost/mailman3/archives/ I agree that this is confusing because some of our docs recommend that urls.py contain ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` and docs recommend ``` path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), ``` I.e. following the first suggestion, you would access Postorius and HyperKitty via `https://www.example.com/postorius/` and `https://www.example.com/hyperkitty/` respectively, but with the second, the urls would be `https://www.example.com/mailman3/` and `https://www.example.com/archives/` respectively. I'm going to address this by adding ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` to mailman_web's urls.py so the either urls will work. See https://gitlab.com/mailman/mailman-web/-/issues/24 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 23:20, Mark wrote: > > The issue is: > > A. With POSTORIUS_TEMPLATE_BASE_URL = > 'http://<REDACTED-PUBLIC-IPv4-ADDRESS>', it sends an empty Welcome > message when a new member is added. > > B. With POSTORIUS_TEMPLATE_BASE_URL = 'https://MYDOMAIN.COM', no Welcome > message gets sent and a timeout error appears on the webpage, although > the new member gets added. I think the difference is http vs https, not the IP vs domain name. Also, with either of these, you are addressing the web server and not the wsgi server. The wsgi server is presumable listening on port 8000 and in the beginning when you had the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' you also got the timeout error and you also got an email to the site owner with 'Site matching query does not exist.' for 'Request URL: http://<REDACTED-PUBLIC-IPv4-ADDRESS>/mailman3/lists/' This leads me to think 'localhost' resolves to <REDACTED-PUBLIC-IPv4-ADDRESS> instead of 127.0.0.1. Also, <REDACTED-PUBLIC-IPv4-ADDRESS> is not in ALLOWED_HOSTS. Have you set ALLOWED_HOSTS in your settings.py? It should be something like ``` ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "127.0.0.1", "<REDACTED-PUBLIC-IPv4-ADDRESS>", "MYDOMAIN.COM", ] ``` -- 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: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 11:40, Wikinaut wrote: > > Honestly, I don't think, that addresses (in my current case on top level, but as I understand, this could happen for every "user") should be treated as, sorry for uppercase, MEMBERS, when they are not expressly member of a list with a →distinct← address. > > please let us discuss. Mailman 3 is different from prior Mailman versions in that Mailman 3 has a concept of a person. The person is a user and a user has one or more email addresses one of which is preferred. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil…>. This corresponds more closely to real life than prior Mailman. If a user is a member of a list with delivery enabled, mail from that list is sent to that user's preferred address. Your own subject recognizes this. You say "Someone not a member of list is treated as member", but the 'Someone', i.e. the person, is a member of the list and should be treated as a member regardless of which of their email addresses they post from. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Re-enable member after bouce processed disable

by Mark Sapiro

On 1/5/22 12:48 AM, Henrik Rasmussen wrote: > > It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces. > > Using the `mailman members` command it is possible to list such members, however how do I enable them using either the `mailman shell` command (available) og the mailmanclient (needs first to be installed in the docker container)? There is a `mailman shell` session in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… that will re-enable all bounce disabled members on all lists. To do just a single list do something like ``` $ bin/mailman shell -l list.example.com 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. The variable 'm' is the list.example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print("Re-enabled delivery for bouncing member {} on list {}" ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/20/23 05:43, Wikinaut wrote: > it has: > > # Mailman Web configuration file. > # /etc/mailman3/settings.py > > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * As I said, I don't know what caused your original authentication failure or what fixed it, but it wasn't the addition of ``` MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' ``` to /etc/mailman3/settings.py. You can verify this by activating your venv and doing ``` >>> MAILMAN_REST_API_USER Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'MAILMAN_REST_API_USER' is not defined >>> MAILMAN_REST_API_USER Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'MAILMAN_REST_API_USER' is not defined >>> MAILMAN_REST_API_PASS Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'MAILMAN_REST_API_PASS' is not defined >>> from mailman_web.settings.mailman import * >>> MAILMAN_REST_API_USER 'restadmin' >>> MAILMAN_REST_API_PASS 'restpass' >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/9/25 2:29 PM, Flo via Mailman-users wrote: > > I can see it in Postorius. If the Postorius domains view shows a domain with `lists.example.com` as the email host, the KeyError: 'lists.example.com' exception should not occur. > I have created the a simialar site before and deleted the site and then > again created this one. Maybe the database is messed up? Probably not. The Postorius domains view shows you what's in the database. > I have deleted site - group - list now. And created the site again. If I > go to 'view site' I see all mailing lists on the server and not only > from this site/domain. This is the first thing where it shows > irregularities. I'm not sure what you mean by `view site` but if you mean the VIEW SITE link at the top of the Django admin UI, that is just a link to the host site. I.e., if the Django admin page is https://www.example.com/admin/site/, its VIEW SITE link just goes to https://www.example.com/ and it's always the same link regardless of what Django admin page you are on. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 4 weeks

[MM3-users] Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/2/22 06:39, Michael Hazan wrote: > Hello, > > When creating a list via postorius, i can see 3 style appear (announce, discussion, private). Is it possible to either create a new style and add it to that list or modify one of those style ? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Also, coming from mailman2, you could directly set the members post moderation action when subscribing, now you can only do it via the user menu, is there a way to automate this in mm3 ? I don't understand what you mean here. In MM 2.1 a member had only one setting - moderated yes or no and if moderated there was a list setting for the moderation action. There was also a list setting for whether new members were moderated by default. How were you setting the new member's moderation when subscribing? You are correct that when subscribing a new member, the member gets the default action for members and different action has to be set in a separate operation. I don't think this is significantly different from MM 2.1. Also, can you describe what you mean by "automate 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

Search results for query "sapiro"