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

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

On Freitag, 7. Februar 2025 18:40:32 CET Mark Sapiro wrote: > On 2/7/25 03:19, Andreas Vetter wrote: > > Changing ACCOUNT_AUTHENTICATION_METHOD to ACCOUNT_LOGIN_METHODS in > > /etc/mailman3/settings.py is not enough. One has to edit > > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py > > You can do this in /etc/mailman3/settings.py only without editing > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py by adding > ``` > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_LOGIN_METHODS = {'email', 'username'} That is unfortunately not enough to get rid of the Warning, because venv/lib/ python3.11/site-packages/mailman_web/settings/mailman.py contains the old ACCOUNT_AUTHENTICATION_METHOD and allauth is complains about it. -- Mit freundlichen Gruessen, Andreas Vetter

3 months, 3 weeks

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 1:09 AM, David Krantz <david(a)krantz.dk> wrote: > On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > Very good! Thank you very much, I got a bit further. > > The database contained a couple of test lists that I can recreate, so > nothing of value. The strange thing was that drop database followed by > create database did not yield an empty database in Postgres. I > probably forgot a commit somewhere. > Never mind, now I got it to work. Some kind of intermittent server error (500) left but I guess that's solvable too. Thanks for all your help on this list! cheers // David

8 years, 2 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 10:25 AM, Mark Sapiro wrote: > I just upgraded from Django 3.2.11 to 3.2.14 on mail.python.org and > lists.mailman3.org. How to upgrade mailman-web to align with Django? I upgraded from Django 3.0.14 to 3.1.14 and then 3.2.14 using these docs: https://docs.djangoproject.com/en/4.0/howto/upgrade-version/ But then this upgrade command returned a complaint that mailman-web 0.0.5 requires Django<3.1: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi and it downgraded Django back to 3.0.14. I did not see anything about this in the Django for Mailman Admins doc, but I may have missed something. https://docs.mailman3.org/en/latest/django-primer.html Thanks. dn

2 years, 10 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Tue, 28 Jul 2020 at 06:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 4:29 AM, Odhiambo Washington wrote: > > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Is there an empty /opt/mailman/mm/__init__.py file? > >> > > > > No. > > > There has to be one. Create it and then Django will be able to import > your settings. > > See the first line after > > Create directories: > ... > and files: > > at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69 > > > I don't know why I didn't see that initially :-) > > Yes. However, that also means the /opt/mailman should be owned by > mailman3, > > right? So I wasn't quite mistaken. > > > It doesn't matter what user actually `owns` this directory and its > subordinates as long as the Mailman user, mailman3 in your case, can > read and write there. Of course, making everything owned by the Mailman > user is the easiest way to ensure this. > True. > > Note also that any commands in /opt/mailman/mm/bin need to be run as the > Mailman user and not root. Running them as root can create things owned > by root the can't be read by the Mailman user. > So, now I remember why I had to chown -R mailman3 /opt/mailman Then now it seems like I have been doing things incorrectly, because I have been doing a lot of operations as root by simply: cd /opt/mailman/mm virtualenv venv source venv/bin/activate Looks like the correct way is to start with su - mailman3 > > PS: There is the issue with qcluster, which doesn't seem to have been > > documented in details from your "experience". > > I see the configuration file and the init script, but not how to install > > it, or whether the procedure already installed it. > > > qcluster is part of Django. If you have this > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > or similar uncommented in your Django settings, and also 'django_q' in > your INSTALLED_APPS, it's there and all you need to do is run > > /opt/mailman/mm/bin/django-admin qcluster > > to run it, but it should be run as a service via init or ?? > I have run it from supervisord. It has forked 30 processes and refuses to kill them when I stop supervisord. I will look for options around it. Answering my own question I asked earlier, I have found "django-admin help --commands" to answer it. PS: Did you by any chance find time to look into the issue about wsgi.py that you had mentioned - the one that has me stuck using it?? Thanks again. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 10 months

[MM3-users] Re: Enable delivery

by Hirayama, Pat

No, I was obfuscating the addresses of the user and listname. And it was the trailing dot/period that was the problem. Sorry about that -- copy/pasting from the emailed report rather than typing the address myself. Now that I have the commands and order, I will look closer at some of those lists when additional reports come in. Thank you! -p > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, December 10, 2024 1:41 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Enable delivery > > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > On 12/10/24 10:43, Hirayama, Pat wrote: > > Apologies, I should've said my "Mailman 3" server, not listserv. > > > > MTA logs do not show messages being sent to the member(s) in question, > even though other members are being sent messages. Nothing out of the > mailman server, and nothing received by our outbound Postfix MTAs. > > > > As for the CLI commands, I keep getting Attribute Error when I try them, like: > > > > /opt/mailman # mailman shell -l listname(a)mailman.tld > > 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 listname(a)mailman.tld mailing list > >>>> from mailman.core.constants import system_preferences > >>>> mbr = m.members.get_member('user(a)domain.com.') > >>>> print(mbr.delivery_status) > > Traceback (most recent call last): > > File "<console>", line 1, in <module> > > AttributeError: 'NoneType' object has no attribute 'delivery_status' > > > Are you literally typing > > mbr = m.members.get_member('user(a)domain.com.') > > That needs to be an actual list member's email without a trailing > period. The fact that mbr is None means whatever you provided is not a > member of the listname(a)mailman.tld list. > > Curious that the member(s) in question are not amongst the recipients > delivered to the MTA even though > > >> when I run: > >> > >> mailman members --nomail any listname@listserv > >> > >> Nothing is returned. > > This should only happen if the members are digest members (are they) or > are directly addressed in To: or Cc: of the post. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mail > man- > users.mailman3.org/__;!!GuAItXPztq0!kBv3nt9E96ao_7FvkLnOsm_R9OWol1 > U4Lk0bnfCxTPiRuYdCv4jHRpx11tT3vx2cyFNW8ByfZlsvtwg$ > Archived at: > https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma > n- > users(a)mailman3.org/message/ET7NTZVDLCY6RBXHUIYRVTYQQX6SQ3KI/__; > !!GuAItXPztq0!kBv3nt9E96ao_7FvkLnOsm_R9OWol1U4Lk0bnfCxTPiRuYdCv4 > jHRpx11tT3vx2cyFNW8ByfwPhcXNc$ > > This message sent to phirayam(a)fredhutch.org

5 months, 3 weeks

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, Unfortunately the provided options didn't work out either: 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 ************* mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm workflow.restore() File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore raise LookupError(self.token) LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b I noticed that the mail address was also listed as a non-member. After deleting it there, I could not accept the subscription either. Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. I'll monitor if such cases will happen again. Thanks,Eric On Saturday, January 16, 2021, 06:05:19 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell 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 >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Johannes Rohr

Am 10.01.23 um 00:53 schrieb Mark Sapiro: > I recognize it's a significant regression for some, but we are a > small, all volunteer project and can't do everything. A well crafted > merge request would certainly be accepted. You are doing incredibly valuable work, and I sincerely apologize for being a total layman who just whines and doesn't have the skills to contribute any code! I could only explore options for organising a bounty on this. But I have no idea what amount of funding would be required realistically, or I could start nagging other Mailman users who have python skills. Cheers, Johannes

2 years, 4 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:38, Mark Sapiro escribió: > On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 21:14, Mark Sapiro escribió: >>> >>> If you had completely stopped Mailman core and then started it, lmtp >>> runner should have started. What are the complete log messages from >>> mailman.log following the start? >>> >> I sent them before > > > And there is no `lmtp runner started` message in the log, so it isn't > being started at all. > > >>> What does `mailman conf -s runner.lmtp` show? >>> >> Here it is: >> >> root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c >> "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg >> conf -s runner.lmtp" >> [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner >> [runner.lmtp] instances: 1 >> [runner.lmtp] max_restarts: 10 >> [runner.lmtp] path: >> [runner.lmtp] sleep_time: 1s >> [runner.lmtp] start: yes > > > This says the runner should be started. That is the command that > starts Mailman? is it Yes, indeed. > > /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C > /usr/local/mailman3/var/etc/mailman.cfg start" > > or is it something that perhaps uses a different config. > > What happens if you do > > /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C > /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" > I get the same error as before: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 2 months

[MM3-users] Re: Time Zone Issue in Postorius

by David Newman

On 2/4/22 10:29 AM, Mark Sapiro wrote: >> My Postorius account time zone is set to "US/Pacific". > > > The appropriate setting for Django is always `TIME_ZONE = 'UTC'`because > the time passed from Mailman core is a naive datetime.datetime object > and is actually UTC. Could use clarification on this. Are you referring to the settings.py file, or something else? Asking because my settings.py currently has: # Django time zones USE_TZ = True TIME_ZONE = 'America/Los_Angeles' and list timestamps appear to work OK both in Hyperkitty and as received by members' mail clients. This is with postorius 1.3.6 and Django 3.0.14. Is this setting incorrect? Thanks dn

3 years, 3 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Alex Schuilenburg

On Wed, 2020-10-07 at 06:03 -0700, Mark Sapiro wrote: > I don't know why the patch didn't work. It should have produced > warning > > level messages in the Django log as configured in > settings(_local).py. The patch did not give the warnings in the exception, because it was the wrong exception. The exception was not being caught. I just modified the warning to log email addresses before looking up their id (where the exception occurred), moving it up 3 lines or so, on the basis the last email shown would be the faulty one. And it was -- Alex

4 years, 7 months

Search results for query "sapiro"