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

[MM3-users] Re: Mailman core: basic internationalization howto?

by Mark Sapiro

On 10/04/2017 12:33 PM, thor.rustad(a)gmail.com wrote: > I finally got around to testing this setup. First I verified that the template in /var/templates/site/no was picked up when subscribing. Then I changed the text, and it stopped working. If I add one of these three Norwegian letters to list:user:action:subscribe.txt, I get the following in logs/mailman.log: > > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) Uncaught runner exception: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) ... > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 576, in _handle_confirmation_needed_events > msg = UserNotification(email_address, confirm_address, subject, text) > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", line 124, in __init__ > @public ??? > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) SHUNTING: 1507144721.896973+35dc93aa969a0934bf717ca07965b09924eca59d See my comment at <https://gitlab.com/mailman/mailman/issues/413#note_42453740>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] Re: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically it says > > "Pay attention to the config file output above and make sure that you see > /etc/mailman3/mailman.cfg there. If the config path is different, you should > make sure to create a new config file at /etc/mailman3/mailman.cfg and > re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) > [GCC 8.3.0] > config file: /opt/mailman/mm/mailman.cfg > db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- 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: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 9/5/25 03:37, Wikinaut wrote: > It's going about the variable $mailinglist_url in footers. Mark exlained, that in mm >= 3.3.10 this placeholder can be used in footers, given, that you have set up $base_url. > > This does not work for me. I need to know, WHERE to set $base_url to make $mailinglist_url become working and replaced in footers. The base url setting for this is an attribute of the domain. Setting it in the Domains view of Postorius or via REST will not be available until the next release, I.e. Mailman core 3.3.11, Postorius 1.3.14, Mailman Client 3.3.6. In the mean time with Mailman core 3.3.10, you can set this via `mailman shell` or by directly updating the `domain` table in the database. In mailman shell >>> d = getUtility(IDomainManager).get('mydomain') >>> d.base_url = 'https://mydomain/mailman3/lists' >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: stop mailmanweb

by Mark Sapiro

On 3/22/26 10:56 PM, Thomas Krichel wrote: > > But mailman-web processes are still running > > root@darni ~ # ps axf | grep mailman-web > 532703 pts/4 S+ 0:00 \_ grep mailman-web > 516993 ? Ss 0:00 /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings > 517012 ? S 0:05 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings > 517014 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings > 517015 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings > 517016 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings > 517017 ? S 2:09 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings These are qcluster processes. They are normally started and stopped separately from mailmanweb. See <https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s…>. You also need `systemctl stop qcluster` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: > > No matter what action I set for member posts (Hold for moderator, > Reject) they are always delivered. I don't know why this would be. Perhaps the member's moderation is set to Accept immediately - you can see this on ther member's options page in Postorius when logged in as a list owner. When the message is delivered, what are the X-Mailman-Rule-Hits: and X-Mailman-Rule-Misses: headers? > When I tried from a non-member email address, the message got held but > when I try to see it I get a Server Error (500) page. The log files shows: > > ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server > Error: /mailman3/lists/test.mydomain.com/held_messages > Traceback (most recent call last): ... > File > "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", > line 443, in held > moderation_reasons=entry['moderation_reasons'], > KeyError: u'moderation_reasons' This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 10 months

[MM3-users] dkim failing

by Mark Sapiro

On 10/15/18 8:37 PM, Abhijith PA via Mailman-users wrote: > > I am seeing dkim fail in mail that people send to lists > /dkim=fail reason="signature verification failed"/ > but it is not happening when the list solely sending mail to subscribers > (like digest, or subscribe/unsubscribe messages etc). I recently added a > new domain to the mailman3. After this I started noticing this issue. > Any help ? Are you saying the DKIM signature on the incoming post fails to validate in the post as sent from the list, or are you saying that a DKIM signature added by your MTA to the outgoing post fails to validate. If the former, this is probably expected. If your list does any content filtering, adds a subject prefix or adds a list header or footer, these transformations will break the incoming DKIM signature. This is why we offer DMARC mitigations. If the latter, you may be doing your own DKIM signing before Mailman applies transformations to the message. You need to sign the message on the way out, not before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 1:45 AM, Stefan Bauer wrote: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ... > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Others have found that removing the trailing slash from ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to make it ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixes the issue. -- 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: mass subscribers disablement!?

by Mark Sapiro

On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is > there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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: How to delete non-users

by Mark Sapiro

On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Search results for query "sapiro"