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

[MM3-users] Re: User account issue after importing data from Mailman 2.x server

by Mark Sapiro

On 10/24/24 11:01, dgoldsmith--- via Mailman-users wrote: > We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. Mailman's import21 process creates Mailman users for the list memberships, but it does not create the Django user used for access to HyperKitty and Pustorius. Your users can't reset their Django (web UI) login password because they don't have a Django account. They need to `Sign up` rather than `Sign in`. > Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? It did create Mailman users, but these have nothing to do with the users that can log min to the web UI. It doesn't create these Django users. > To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Just tell the users to go to the web UI and `Sign up` rather than `Sign in`. Removing and resubscribing a user will not help. The users that are members of mailing lists are completely separate from the users that can log in to the web UI. This is in part due to the modular nature of Mailman 3 and the fact that a Mailman 3 installation doesn't necessarily even have a Django based web UI. You may also be interested in the thread at 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

1 year, 6 months

[MM3-users] Re: mailman_web/urls.py changes in Postorius 1.3.10

by Mark Sapiro

On 12/5/23 09:52, Lieuallen, Thomas Otis wrote: > The latest release of Postorius includes these lines in mailman_web/urls.py: > > > # Include alternate Postorius and HyperKitty URLs. > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > > It appears that these paths override the originals (/mailman3 & /archive). They were intended as optional additions, but it appears they do function as overrides for some purposes. > I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. This is apparently a side effect of this change that wasn't considered in making the change. The change was made because some docs and/or example projects used the /postorius and /hyperkitty URLs and some used the /mailman3 and /archives URLs. This was an attempt to make either set work. > If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). > > Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. > > One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? It was intended to just add the /postorius and /hyperkitty URLs as alternates. I had assumed the links on various pages would reflect the URL used to access the page, but this is apparently wrong. I could change the order of the path lines in the distributed urls.py, but at this point it just may cause more confusion. However, since the sample config at https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… shows only the /mailman3 and /archives URLs, I will change the order. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Handling of (un)subscribe mails for already (un)subscribed users

by Mark Sapiro

On 12/10/20 11:51 AM, Andreas Barth wrote: > Hi, > > I noticed that a mail to -subscribe for an already subscribed user > doesn't get any response (about line 225 in > mailman/src/mailman/app/subscriptions.py). Same but different for > unsubscribe for users not on the list. I tested and I see this, so there is a bug, but I don't know what the issue is. The code you point to should raise AlreadySubscribedError and <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> should catch it and report, but this doesn't seem to be happening.. Also, <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> should report an attempt to unsubscribe a non-member, but the issue here is <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/comman…> which supresses sending the response because it is redundant if the user gets a 'you have been removed' email, but in this case there isn't one. > I'd need these kind of mails however in hope that users complain less. > > Would that be generally interessting, and if so, any special > requirements for submitting patches, or should I just do that locally? These things should be fixed, but it's more involved than just a patch to fix the error. For all but trivial fixes, the workflow should be something along the lines of the following. There should be an issue on GitLab for the appropriate project; in this case at <https://gitlab.com/mailman/mailman/-/issues>. Then to develop a fix, there needs to be a fix, a test for the fixed code and a note in the NEWS.rst file about the fix. I generally prefer to start with a local clone of the GitLab branch and first create a test for the desired behavior. This test should fail. Then I create the fix, and now the test should pass. Finally, I create the NEWS item and commit those changes and create a merge request. -- 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

[MM3-users] Re: user mail not accepted

by Mark Sapiro

On 4/26/21 5:16 AM, Christian Stalberg via Mailman-users wrote: > I have a user whose moderation rule is 'Accept immediately' yet when they > send a message for distribution to the list, they only receive it and it is > not distributed via the list. Logfile entries below. Please advise. Btw I > have another list on this same instance which is running fine. Thank you. > > [26/Apr/2021:12:06:25 +0000] "GET /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=christian > %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1257 "-" "GNU Mailman REST > client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "PATCH > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=christian > %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1288 "-" "GNU Mailman REST > client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/requests/count?token_owner=moderato > r HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/held/count HTTP/1.1" 200 73 "-" > "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272/preferences HTTP/1.1" 200 295 > "-" "GNU Mailman REST client v3.3.2" These entries don't tell anything about a post to the list. They are all from Mailman's REST API relating to Postorius interactions with core. However the absence of messages like Apr 26 07:32:39 2021 (17860) ACCEPT: <message_id> and Apr 26 07:32:41 2021 (17857) HyperKitty archived message <message_id> to https://example.com/archives/list/list_adderss/message/message_id_hash/ assuming you are looking at the correct time span, says there wasn't an accepted list post. Mailman's smtp.log may have more info, but the complete, raw message that the user receives may be more helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Sending to mangled 'From' addresses.

by Mark Sapiro

On 5/31/24 22:23, hansen via Mailman-users wrote: > > Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. DMARC mitigation action ‘Replace From: with list address’ will also place the poster's address in Reply-To: (or Cc: depending on list configuration), so a simple `reply` from a reasonable MUA should go just to the poster. > For example, say the mail client captures my address as > > “Allan Hansen via <listname>” <listaddress> > > then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: > > “Allan Hansen via <listname>” > > and, to make it worse, the actual email address, <listaddress>, is often hidden. If this is the result of a `reply` and not `reply-all` the client is not behaving reasonably. > The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. That is a problem with the client, but I suppose such clients are not uncommon. > Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., > > "Allan Hansen via <listname>" You could add a header filter on the To header with a regexp like `^.*via <listname>` and the desired action. > Should I get onto the other list to request this as an enhancement? I don't think that's necessary in this case, as Header filters should do it. In general, the best way to request an enhancement is to file an issue with the appropriate GitLab project at `https://gitlab.com/mailman` -- 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: Mailman/Django-allauth integration with Yahoo

by Mark Sapiro

On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I'm logging with the mailman user and it says that it sent a confirmation email to my email account, but I don't see any activity in postfix with 'tail -f /var/log/maillog' command What do you suggest??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by Mark Sapiro

On 11/8/23 14:47, gordon(a)dickens.com wrote: > > Basically, it does not appear that mailman nor the runners are active and rebooting does not help. "/opt/mailman/venv/bin/mailman start" generates errors as follows: > >> Traceback (most recent call last): >> File "/opt/mailman/venv/bin/mailman", line 6, in <module> >> from pkg_resources import load_entry_point >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3248, in <module> >> @_call_aside >> ^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3223, in _call_aside >> f(*args, **kwargs) >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3261, in _initialize_master_working_set >> working_set = WorkingSet._build_master() >> ^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 617, in _build_master >> ws.require(__requires__) >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 956, in require >> needed = self.resolve(parse_requirements(requirements)) >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 815, in resolve >> dist = self._resolve_dist( >> ^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 856, in _resolve_dist >> raise DistributionNotFound(req, requirers) >> pkg_resources.DistributionNotFound: The 'mailman==3.3.5' distribution was not found and is required by the application First of all, when running /opt/mailman/venv/bin/mailman you need to specify the -C option with the path to mailman.cfg, i.e. ``` /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg start ``` Can you run the mailman command without a subcommand. I.e. ``` /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg ``` should just produce a list of subcommands. Does it do that or produce the same error as above? I don't understand the above error. I think the content of /opt/mailman/venv/bin/mailman should be ``` #!/opt/mailman/venv/bin/python # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) ``` Which doesn't correlate with the above traceback. What is yours? -- 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: How to configure an announce-only list?

by Mark Sapiro

On 4/28/26 5:17 PM, Craig Leres via Mailman-users wrote: > I want to create a mailing list that is used for announcements only. I'd > like attempts to post to be rejected with a notification. > > I was able to set the list pw and verify it works with the Approved > header using this reference: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/ > docs/approved.html > > I find that if both: > > Default action to take when a member posts to the list > Default action to take when a non-member posts to the list > > are set to "reject (with notification)", the approved header is ignored > and messages are always rejected (posted via "mailman inject") This should not be the case. The message is checked for an Approved: header prior to the member/nonmember checks. > Would it be bad to test the approved header before rejecting a message? > Essentially always accept a message with a valid approved header? Is > there another way for me to achieve this? That's the way it should be working. There is a potential issue if the password in the Approved: header when encrypted doesn't match the encrypted value in the lists moderator_password attribute, it is treated as if there were no Approved: header. This is a bug <https://gitlab.com/mailman/mailman/-/work_items/1276>. I.e., the message should be rejected but with a reason indicating the password was wrong. > On another front, I'm unable to have messages posted via "mailman > inject" use postorius created list templates. Would it be difficult to > add this functionality? That should not be the case. Are you saying messages posted via email use Postorius created templates, but messages posted via mailman inject do not? If the templates are used for messages posted via email, they should also me used for messages posted via mailman inject. Have you verified that the templates are used for messages posted via email? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 4 days

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Mark: These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? --- George R. Kasica Phone: +1 414 732 8503 Fax: +1 206 374 6482 Owner Netwrx Consulting Jackson, WI USA gkasica(a)netwrx1.com http://www.netwrx1.com<http://www.netwrx1.com/> From: George R. Kasica <gkasica(a)netwrx1.com> Sent: Sunday, June 5, 2022 10:32 To: mailman-users(a)mailman3.org; Mark Sapiro <mark(a)msapiro.net> Subject: Re: [MM3-users] Re: Mailman3 Setup Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 10 months

Search results for query "sapiro"