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

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 4:37 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 00:32, Odhiambo Washington wrote: > > > > Apparently so, because: > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists > > No matching mailing lists found > > mailman@lists:~$ > > > > Which is surprising, given this: https://imgur.com/a/LPrh42K > > > Postfix is talking to a different Mailman core. > There isn't any other. This server has only been running Mailam21. > > root@lists:/home/wash# su - mailman > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create > > skunkworks(a)lists.my.co.ke > > sh: 1: /usr/sbin/postmap: not found > > sh: 1: /usr/sbin/postmap: not found > > Traceback (most recent call last): > ... > > RuntimeError: command failure: /usr/sbin/postmap > > /opt/mailman/var/data/postfix_lmtp, 127, Key has expired > > command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, > > 127, Key has expired > > > > Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. > > > In the [mta] section of mailman.cfg, put > ``` > incoming: mailman.mta.exim4.LMTP > configuration: python:mailman.config.exim4 > ``` > See > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… That is exactly what I have in my mailman.cfg Installing Postfix suppresses that message though. I installed Postfix and then disabled it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Stephen J. Turnbull

Mark Sapiro writes: > Of course it is logical. You, the person, are a member of the list > so you post to the list should be treated as from a member > regardless of which of your addresses it comes from. > > Why is that a problem? People are not particularly logical about this kind of thing. They want what they want at the moment (compare the discussion with Odhiambo where he wanted the same address to correspond to different users). People with multiple addresses frequently want to separate their outgoing messages as well as incoming messages into separate streams. (Eg, one of the addresses is for specific use on an anonymous list.) But in many cases what they want is as you say, "I" am subscribed so any of my addresses should do. While your explanation that a (human) person who wants that behavior should link separate addresses to separate Users is a perfectly good technical answer, I would not expect typical folks to figure that out for themselves. I don't have a suggestion for a user-friendly UI for this; I think it's just a hard concept to grasp with the amount of effort we generally want to put into a mailing list subscription. It might be a good idea to add this issue to the documentation on anonymous lists. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 day, 10 hours

[MM3-users] Re: Hiding the "subscribe without creating an account"

by Matthew Blissett

On 13/07/2024 07:17, Mark Sapiro wrote: > On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >> >> Is there a configuration option that does this, or was it a custom >> change made in >> the templates? Was the change made to reduce fake registrations? Did >> it work? > > > It was added in Postorius 1.3.9. See the UI section at > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 > > Yes, the change was made in an attempt to reduce fake registrations. > > We haven't really studied it's effectiveness. It seems to help > somewhat, but it also seems that bots may already have a template to > POST so removing it from the UI is not a complete solution. They would be missing the CSRF token (a hidden field on the anonymous signup form) so this ought to fail. > There is also a lot of email to innocent third parties and > non-existent addresses from attempts to register them for an account. There are patches to integrate a Captcha system here: https://gitlab.com/mailman/django-mailman3/-/issues/33 I think it's needed, as less than 24 hours after migrating to Mailman 3 I already see bots retrieving the signup form to get the CSRF token (GET /accounts/signup/?next=/postorius/lists/) then POSTing the request for a new user account (POST /accounts/signup/). There's also the setting ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False, which prevents spam from the "forgot password" address, see https://gitlab.com/mailman/postorius/-/issues/591 -- Matt

1 year, 1 month

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Wed, Dec 25, 2024 at 8:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 23:35, Odhiambo Washington via Mailman-users wrote: > > > > Now only if you can help me reconcile the fact that Postorius tells me > that > > I have > > ``` > > List Nonmembers (872) > > > > ``` > > > > ..while the CLI command gives me only 13 addresses. > > > How are you invoking the `mailman nonmembers` command? I suspect it is > not using the proper mailman.cfg. Does `mailman info` show the correct > mailman.cfg. > ``` (venv) mailman@eu:~$ whoami mailman (venv) mailman@eu:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman:XXXXXXXXX@localhost /mailmansuite?charset=utf8mb4&use_unicode=1 devmode: DISABLED REST root url: https://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC Agnes <agnesa(a)REDACTED.com> Angela M <angelam(a)REDACTED.org> <beatiemaina!!(a)REDACTED.com> <psgimode(a)REDACTED.ke> <jwothaxxx(a)\REDACTED.ke> <lgichdhdh(a)REDACTED.ke> <mrussher(a)REDACTED.org> <mutwiXXj3(a)REDACTED.com> <news@REDACTED> Nesema <xxxxxx(a)kictanet.or.ke> Robert M <xxxxxxo(a)yahoo.com> <telasalma17@ REDACTED > <wambdddddd(a)REDACTED.ke> (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC | wc -l 13 (venv) mailman@eu:~$ ``` It uses the correct config file. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

7 months, 4 weeks

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Odhiambo Washington

On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what is documented so that the issue doesn't recur: ``` [general] base_url: http://127.0.0.1:8000/archives/ api_key: Secret_Hyperkitty_API_Key ``` PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s questions quoted below: ``` Did the new post get archived? If so, why is last post at still July 25, 2025? If no, why not. The post must go to the archiver to cause the queue to be processed. If the post was archived and the July 25 messages are still queued, what's in Mailman's mailman.log. There should be error messages and tracebacks indicating the issue. ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 weeks, 6 days

[MM3-users] Re: From address of subscription notifications

by Abhilash Raj

On Wed, Feb 27, 2019, at 5:46 PM, worik wrote: > On 27/02/19 11:54 AM, Mark Sapiro wrote: > > On 2/26/19 2:11 PM, worik wrote: > >> When I subscribe some body to to a list I on I get a notification that > >> says it comes from changeme(a)example.com > >> > >> As far as I can tell no subscribers are getting mail with that, so this > >> is not a crises. But it is untidy and I cannot find where to change it. > >> > >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of > >> docker-compose.yaml (I am using the docker distribution...) > > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > > > > There is no `mailman/config/schema.cfg` on my system. Should I raise a > issue over at the docker-mailman github? > > I have: > > /opt/mailman/core/mailman-extra.cfg > /opt/mailman/core/var/etc/mailman.cfg > > Should I change it in the second one? /opt/mailman/core/mailman-extra.cfg Change it in this one. > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 5 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-25 19:05, schrieb Mark Sapiro: > On 4/25/24 04:35, Thomas Stein wrote: >> >> Traceback (most recent call last): >> File "/usr/bin/django-admin", line 33, in <module> >> sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', >> 'django-admin')()) >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File >> "/usr/lib/python3/dist-packages/django/core/management/__init__.py", >> line 442, in execute_from_command_line >> utility.execute() >> File >> "/usr/lib/python3/dist-packages/django/core/management/__init__.py", >> line 416, in execute >> django.setup() >> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, >> in setup >> apps.populate(settings.INSTALLED_APPS) >> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line >> 124, in populate >> app_config.ready() >> File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line >> 15, in ready >> raise ImproperlyConfigured( >> django.core.exceptions.ImproperlyConfigured: >> allauth.account.middleware.AccountMiddleware must be added to >> settings.MIDDLEWARE Thanks for you answer. > This is a packaging issue in the Debian/Ubuntu package and should be > reported to Debian. I already did. https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/2062960 > See the BREAKING CHANGE item in the 1.3.10 section at > <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. > > You need to add `allauth.account.middleware.AccountMiddleware` to the > MIDDLEWARE setting in your Django settings. I'm not sure how to add that to my django settings. Adding: x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x did not help. Any hints? thanks again, t.

1 year, 3 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Fri, May 14, 2021, at 2:16 PM, Odhiambo Washington wrote: > On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > > > /usr/local/include/sass > > > > > > That is the only thing found that is in the base system. > > > > And that's the one you want. What is it's mode? > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. This sounds like a result of you running `pip3 install sass`, probably with sudo which failed mid-way due to the exception you posted above. Which OS are you using? On debian/ubuntu, you can install: sudo apt install sassc I am not exactly sure how it got removed during your upgrade to the new version of Mailman since it shouldn't affect your system packages. Did you install Mailman initially using system packages or instructions provided at [1]? [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… -- thanks, Abhilash Raj (maxking)

4 years, 3 months

[MM3-users] Re: problem configuring mailman3 on debian bullseye

by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia

Hi, Thank you. I discovered tha I removed all templates but in the db table the template was not removed. It was pointing to localhost and this was the problem. Thanks to all for help! Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it Il 16/03/23 04:20, Mark Sapiro ha scritto: > On 3/15/23 09:55, Odhiambo Washington wrote: >> On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione >> territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: >> >>> Hi, >>> >>> I created a template but after some tests I deleted it. >>> >>> Now I created only a standard list without modifying any templates. >>> >>> So they are the standard templates coming with the distribution. I >>> did not >>> change also the language >>> >> Maybe you can start by deleting any templates in postorius_emailtemplate >> table in the DB? > > There shouldn't be any, but if the issue is with accessing postorius > templates, that might make it worse. > > If you want only the system default templates, you could do this > database query to remove any non-defaults: > > DELETE FROM templates; > > That will ensure that you aren't accessing Postorius for any templates. >

2 years, 5 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 9., Sze, 4:49): > ``` > $ 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. > > >>> um = getUtility(IUserManager) > >>> usr = um.get_user('user(a)example.com') # any of the three addresses > >>> usr.addresses > prints a list of the 3 addresses. These are indexed as 0, 1, 2 > >>> usr.preferred_address > prints the preferred address. If this is the one you want to delete, do > >>> usr.preferred_address = usr.addresses[n] # n is the index of one > you want > >>> del usr.addresses[n] # n is the index of the address you don't want > >>> usr.addresses.remove(n) # n is the index of the address you don't > want > >>> commit() > ``` Thanks, I successfully removed my unwanted address, so it now doesn't appear anywhere. (Looks like .remove(n) wasn't needed, it only gave an exception, and the settings were saved even without commit() – which is concerning because I would have assumed that I can cancel transactions by omitting it.) However, the problem still persists: I can't post to the list from HyperKitty. In this regard, nothing has changed since my original report. I'm subscribed to the list with my primary, preferred address, which is the GMail address right now.

4 months, 2 weeks

Search results for query "sapiro"