Search results for "Postorius" - Mailman-users

Mailman backend maintenance task

by Stephen J. Turnbull

Hi, Eugenio, I wrote this earlier but am in the middle of moving my office so my mail has been intermittent. I have been following your discussion with Abhilash, and he's definitely the expert, especially if you are using the containers he creates and distributes. But there's some information here he hasn't mentioned yet. Please consider the following discussion to be background that allows you to understand some of the considerations. I've only run the Mailman 3 suite with all three running constantly on the same host, so I have no experience with this kind of issue. eugenio.jordan(a)esa.int writes: > Our customer is currently using PostGRESQL as backend, and we would > like to perform some maintenance tasks, namely running vacuum full, > or at least trying to rebuild hyperkitty_email primary key related > index. We have been asked on the real impact of putting in place > such initiative. Though the latter is related to archiving, I > haven't found a way to stop just Hyperkitty or Django related > processes other than stopping Mailman's core, hence preventing > mails addressed to distribution lists from being delivered, could > you please confirm if I am correct? Mailman core can certainly run without either Postorius or HyperKitty. Controlling Mailman core (moderation, helping users) without Postorius is annoying, but it can be done. If you stop the HyperKitty process, what should happen, I believe, is that posts for archiving will accumulate in the 'archive' queue until HyperKitty is available again. It's been a while since I studied this so I could be completely wrong, but as I understand it HyperKitty and Postorius are not daemon processes. Rather, they are WSGI applications, which means they are subprocesses spawned by your webserver, and controlled by it. In order to keep them from running, you would reconfigure the webserver to not call those WSGI applications. How that is done is specific to the webserver and the WSGI module. If you are running from Docker containers, most likely, you can just stop their containers. The larger problem is that Mailman core uses a RDBMS. Normally both Django and Mailman are referring to the same RDBMS, PostgreSQL in your case. I'm not familiar with the vaccuum operation; if it requires taking the whole RDBMS down, and Mailman is running on that RDBMS, you're out of luck. Mailman can accept posts and queue them, but it can't deliver them to subscribers without access to the RDBMS tables. If it's just a matter of locking some tables while other are available, then it should work because the tables used by core and HyperKitty are disjoint as far as I know. (I think Postorius and HyperKitty both use Django's user tables for authorization, so at least for those tables both Postorius and HyperKitty will have to be down, but core can continue running because its database is completely separate.) > Regarding the former, as far as I have read, the "mappings" lists > -> addresses are stored just in the database, so if we run some > kind of procedure or task like vacuum which will lock exclusively > tables, or want anyway to have the database stopped for a cold > backup or whatever, Mailman willl not work, that is, again the > mails addressed to the distribution lists will not be > delivered. Will you please confirm this point, too? That depends on how "vacuum" works. If you can tell the RDBMS not to lock Mailman core's tables, it can continue to run. Definitely if the database is not running, Mailman will continue to receive and store the posts, but it won't be able to distribute mail to subscribers until its tables are available again. At that point the queued posts will be processed normally, except that if there's a large backlog, they won't go out in a quick burst, it may take a while. One possible worry, depending on how you are connected to the Internet, is that your provider may interpret the sudden burst of outgoing mail when Mailman comes back on line as spam or some other sort of mischief. Mailman has no way to throttle this: it feeds messages to the MTA until the MTA says "stop". Then it waits until the MTA is ready again. Regards, Steve

5 years

Re: only show mail domains from web host on web-host-url

by Abhilash Raj

> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html You seem to have landed on a very old version of the docs that I didn’t unfortunately knew was even available. I have disabled that page now. The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > > I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > How could I check, that the setting is used!? > > But maybe some additional information: > - I use the Debian installation on a stable buster, so mailman is version 3.2.1 > - I use apache2 as my web-server and use the given alias-conf-file > - Python is version 3.7.3 > - Postorius is Version 1.2.4 > - HyperKitty is version 1.2.2 > > -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de > -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above > -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de > -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de > -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains > > What do I miss? Or where to investigate? > > Thank you in advance, best regards. > > By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to individual projects. The second one is the individual Mailman Core project. Historically, Core was the only project and hence claims the name “mailman” in most places. > > Am 18.03.21 um 21:52 schrieb Mark Sapiro: >> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >> Set FILTER_VHOST = True in your settings_local.py or where ever you put >> your site Django settings. > _______________________________________________ > 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)

5 years, 6 months

Re: restricting public lists per virtual domain

by David Newman

On 12/16/21 2:40 PM, Mark Sapiro wrote: > On 12/16/21 12:25 PM, David Newman wrote: >> Can lists set to be viewable on the index page be limited to the >> virtual domain they are a part of? >> > > > Have you set > > FILTER_VHOST = True > > in your Django settings? I had not, and this was the variable I was looking for. Thank you! This works for HyperKitty and works partially > for Postorius. For Postorius, it doesn't work if there are multiple > domains with different email hosts which have the visiting host as their > web host[1] but works otherwise. > > See https://gitlab.com/mailman/postorius/-/merge_requests/500 and > https://gitlab.com/mailman/postorius/-/issues/394 > > In your case, as long as the domains lists.dom1.tld and lists.dom2.tld > have different mail hosts, this should work. > > [1] An example of what doesn't work in Postorius is the following: > > Visit https://lists.example.com/mailman3/lists. If there are 2 domains > with web host lists.example.com, one of which has mail host example.com > and the other has mail host lists.example.com, all lists will be shown > regardless of domain. On the other hand, if all the domains with web > host lists.example.com have the same email host, say example.com, then > only lists with email host example.com will be shown. Awhile back Stephen Turnbull suggested a terminology guide that included an MM3-specific definition of FQDNs. Also in an MM3 context, I think it would be useful to distinguish between mail hosts and web hosts and domains (all in the general Internet sense) and mail domains and sites (in the MM3/Django/Postorious/Hyperkitty sense). Not sure I fully understand these distinctions yet, but I can take a crack at it. dn

4 years, 9 months

Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > Hi Team, > > I am currently running Mailman 3 with version 3.3.2rc2 and in > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > with default values. As of now, we don't have any lists and just installed > software components only. > > After the installation and configuration, I have tried > creating the domains and lists. I was successful in creating them but when > I tried to login and browse the lists using LDAP authentication, I am > getting the "Mailman REST API not available. Restart Mailman core". > > I see the below trace in the mailmansuite.log. > > *Traceback (most recent call last): File > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ return self._get(name) File > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count ... > > I don't see any error messages in the mailman.log. And I > also executed a few curl commands in getting the details of the lists > created and list info which I got their results successfully. > > Could you please guide where exactly I am missing or do I > need to make any changes in my customizations ? I think the issue is your mailmanclient is too old. The version of Postorius you are running requires mailmanclient >3.3.1 which is only available from GitLab <https://gitlab.com/mailman/mailmanclient>. What version of Postorius is this? It appears to be >1.3.3. If you install Postorius from unreleased code on GitLab, you have to install all of mailman, mailmanclient and django-mailman3 as well. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: mailqueue shows bounces for emails that are not on the mailing list

by Paul Ssekamatte

> > If "my-mail-server-IP" is in fact your mail server's IP, then you may > > have a problem: spammers may be using your server as a relay for > > spoofed emails. > > It is also possible, or even likely that these are the result of bad > actors maliciously requesting subscriptions for 3rd parties. Since this > is a 421 status, these mails should remain queued in your mail server > for a while and can be examined[1]. If this is the case, you may be able > to mitigate this by setting > SHOW_ANONYMOUS_SUBSCRIBE_FORM = False > in your Django settings. See > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 > [1] For example if your MTA is Postfix > postcat /var/spool/deferred/4/4d08rT4xMHzMCD6S > and if that shows a subscription or email verification request > postsuper -d 4d08rT4xMHzMCD6S > to delete it so it isn't retried. > -- this is most likely the case. I tried adding the setting in Django as suggested but it doesnot seem to work. I see the documentation is for Postorius 1.3.9 but my version is 1.3.8 I suppose I need to upgrade Postorius

10 months, 2 weeks

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

Hi Eggert, thank you for your input. Unfortunately that did not work. After changing the line ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ and restarted apache2, still a similar behavior when accessing https://my.mailinglistserver.local/mailman/postorius/lists/ Page not found (404) Request Method: GET Request URL: https://mmy.mailinglistserver.local/mailma//postorius/lists/ What i find strange is that the URL is mangled. The 'n' from mailman is missing and now there is a second slash. This all must happen inside the uwsgi-container as my request is modified. Not Found: /mailma// [pid: 1346851|app: 0|req: 28/28] 10.254.253.13 () {52 vars in 827 bytes} [Mon Oct 25 17:47:21 2021] HEAD /mailman/ => generated 2773 bytes in 4 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1) Am Mo., 25. Okt. 2021 um 17:19 Uhr schrieb Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org>: > Hello Stefan, > > I had the same problem. While I did not find the reason for this strange > behavior, I found a workaround. I changed the lines in the apache vhost > file > like this: > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > Note I only changed the single ProxyPass line from mailman3 to mailman. > The > url to access the web gui also changes like this: > > https://my.mailinglistserver.local/mailman/postorius/lists/ > > This works for me, tell us your success. Would be nice when the problem > could > be solved finally, this happened to a few people. > > Cheers, Eggert > > Am Montag, 25. Oktober 2021, 10:45:50 CEST schrieb Stefan Bauer: > > 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) > > > > After enabling Debug, i see in the browser the following: > > > > > > Page not found (404) > > Request Method: GET > > Request URL: > https://my.mailinglistserver.local/mailman//postorius/lists/ > > > > Using the URLconf defined in urls, Django tried these URL patterns, in > this > > order: > > > > ^$ > > ^postorius/ > > ^hyperkitty/ > > ^user-profile/delete$ [name='mm_user_account_delete'] > > ^user-profile/$ [name='mm_user_profile'] > > ^accounts/ > > ^admin/ > > > > The current path, /postorius/lists/, didn't match any of these. > > > > You're seeing this error because you have DEBUG = True in your Django > > settings file. Change that to False, and Django will display a standard > 404 > > page. > > > > My apache configuration is very simply: > > > > # more /etc/apache2/conf-enabled/mailman3.conf > > Alias /mailman3/favicon.ico > > /var/lib/mailman3/web/static/postorius/img/favicon.ico > > Alias /mailman3/static /var/lib/mailman3/web/static > > > > <Directory "/var/lib/mailman3/web/static"> > > Require all granted > > </Directory> > > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > > > I dont see where the path gets traversed in the wrong way. Any help is > > greatly appreciated. > > > > thank you. > > > > Stefan > > _______________________________________________ > > 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/ > > > > > _______________________________________________ > 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, 10 months

Re: More Mailman releases!

by Jered Floyd

Everything looks good to me in my multi-site install! I've updated my simple container install to pin the new versions: https://github.com/jeredfloyd/mailman-container --Jered ----- On Oct 22, 2023, at 2:10 AM, Abhilash Raj maxking(a)asynchronous.in wrote: > Hello, > > I missed one important merge request in django-mailman3, so here are a > couple more versions. > > I've released Django-mailman3 1.3.11 and Mailman-web 0.0.8 (which > requires django-mailman >= 1.3.11). > > Gitlab releases are available here: > > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.8 > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.11 > > I have also yanked mailman-web 0.0.7 since that'll cause spurious errors > due to change in session serializer. > > Abhilash > > > On 10/22/23 00:05, Abhilash Raj wrote: >> Hello Everyone, >> >> I am pleased to announce several new releases for GNU Mailman project. >> Thanks to all the contributors for making these releases possible! >> >> 1. Postorius 1.3.10 [1] >> 2. Hyperkitty 1.3.8 [2] >> 3. Django-mailman3 1.3.10 [3] >> 4. Mailman-web 0.0.7 [4] >> >> All the releases are published to PyPI and you can find links to all the >> PyPI projects: >> >> https://docs.mailman3.org/en/latest/ >> >> A full list of change logs are available below: >> >> [1]: >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 >> [2]: >> https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 >> [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst >> [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst >> >> Do note that for Postorius, I released 1.3.9, but I forgot to update >> dependency metadata to require `django-mailman3>=1.3.10` (which is >> required for the new bootstrap 5 upgrade across packages) and so I also >> released Postorius 1.3.10 just after. >> >> Installation documentation is available at >> >> https://docs.mailman3.org/en/latest/install/install.html >> >> and if you are upgrading an existing virtualenv install you can refer >> >> https://docs.mailman3.org/en/latest/upgrade-3.2.html >> >> If you find any issues, you can report them at the respective bug >> tracker for the projects. The links to issue trackers are available >> at https://docs.mailman3.org/en/latest/. >> >> Finally, similar to Mailman Core, note that PyPI doesn't accept >> signatures anymore so each packages' release page now has the tarball >> uploaded to them along with the signature: >> >> Django-mailman3: >> https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 >> Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 >> Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 >> Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 >> > > -- > thanks, > Abhilash Raj (maxking) > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 11 months

Re: Starting new thread in Postorius -> disappears

by Cameron Smith

I would suggest that there is something very broken here: there seems to be a problem with communication between the email system (mailman core…?) and HyperKitty. On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. So, what’s going on? What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > On 2017.11.21, at 06:31 , Cameron Smith <ccsmith(a)mail2.cetsi.com> wrote: > > Thor, > > I, too, have been struggling with messages not showing up [1], although the conditions are somewhat different. > > What I have found works to make all of the messages appear is the following, which you might try: > > sudo docker-compose exec mailman-web ./manage.py runjobs yearly > > > [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > >> On 2017.11.21, at 04:41 , Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: >> >>> >>> >>>> When I send a message from the Postorius interface, it is neither sent >>> out >>>> or stored. I briefly see this message: "Your reply has been sent and is >>>> being processed.", and then nothing happens. Cameron Smith Nanaimo, BC tel:1.604.803.0051

8 years, 9 months

Re: Login confusion

by Markus Grandpré

Dear Steve, dear list > That's not true on the systems I've worked with most recently -- those > will be recognized as duplicate addresses (...) You are right. I am sorry for this confusion. Please let me correct my initial posting to this list from yesterday, saying: >> (...) <markus.grandpre(a)uni-konstanz.de> and <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate identities. That is not the case. Meanwhile I discovered an error with logging into Postorius when an account is associated with two semantically identical email addresses that differ in their formatting, e.g., <markus.grandpre(a)uni-konstanz.de> and <Markus.Grandpre(a)uni-konstanz.de>. In this case, the user is unable to log in, and I observed the following error message in the log file: (...) returned more than one EmailAddress -- it returned 2! Here is the complete stack trace of this error: ERROR 2025-02-10 14:29:55,599 211159 django.request Internal Server Error: /mailman3/accounts/login/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/decorators/debug.py", line 89, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 149, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 77, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 105, in post response = self.form_valid(form) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 162, in form_valid return form.login(self.request, redirect_url=success_url) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 196, in login ret = perform_login( ^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 168, in perform_login response = adapter.pre_login(request, user, **hook_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 411, in pre_login if not has_verified_email(user, email): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 130, in has_verified_email emailaddress = EmailAddress.objects.get_for_user(user, email) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/managers.py", line 54, in get_for_user ret = self.get(user=user, email__iexact=email) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 439, in get raise self.model.MultipleObjectsReturned( allauth.account.models.EmailAddress.MultipleObjectsReturned: get() returned more than one EmailAddress -- it returned 2! ERROR 2025-02-10 14:29:55,599 211159 django.request Internal Server Error: /mailman3/accounts/login/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/decorators/debug.py", line 89, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 149, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 77, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 105, in post response = self.form_valid(form) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 162, in form_valid return form.login(self.request, redirect_url=success_url) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 196, in login ret = perform_login( ^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 168, in perform_login response = adapter.pre_login(request, user, **hook_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 411, in pre_login if not has_verified_email(user, email): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 130, in has_verified_email emailaddress = EmailAddress.objects.get_for_user(user, email) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/managers.py", line 54, in get_for_user ret = self.get(user=user, email__iexact=email) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 439, in get raise self.model.MultipleObjectsReturned( allauth.account.models.EmailAddress.MultipleObjectsReturned: get() returned more than one EmailAddress -- it returned 2! To resolve the issue, the only solution I found was to manually delete the second email address from the database: mailman3web-prod=> select * from account_emailaddress where user_id = 93; id | email | verified | primary | user_id -----+---------------------------------+----------+---------+--------- 100 | Markus.Grandpre(a)uni-konstanz.de | t | t | 93 101 | markus.grandpre(a)uni-konstanz.de | t | f | 93 (2 rows) mailman3web-prod=> delete from account_emailaddress where id = 100; DELETE 1 mailman3web-prod=> select * from account_emailaddress where user_id = 93 ; id | email | verified | primary | user_id -----+---------------------------------+----------+---------+--------- 101 | markus.grandpre(a)uni-konstanz.de | t | f | 93 (1 row) Could I have achieved the same deletion using the REST interface? After the deletion login with <markus.grandpre(a)uni-konstanz.de> was possible again, and I set the remaining email address as 'primary' using Postorius. I am not entirely sure how the duplicate email address came into the system. During the data migration from Mailman 2.1 to Mailman 3, an account was created for <markus.grandpre(a)uni-konstanz.de>. It is most likely that during registration, the user provided <Markus.Grandpre(a)uni-konstanz.de> as username or email address, which resulted in both variations of the semantically same email address being stored under the same account. I apologize again for the incorrect information in my initial message to this list. I should have waited until I had a clearer understanding of this issue. Best regards, Markus Am 10.02.25 um 15:32 schrieb Stephen J. Turnbull: > Markus Grandpré writes: > > > We've encountered an issue with Postorius after migrating from > > Mailman 2.1. It appears that Postorius is treating email addresses > > with differing capitalization as distinct user accounts. For > > example, <markus.grandpre(a)uni-konstanz.de> and > > <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate > > identities. > > That's not true on the systems I've worked with most recently -- those > will be recognized as duplicate addresses, both at list import time and > at login on Postorius. Those are versions Mailman 3.3.9 and 3.3.11, > with corresponding Postorius. As far as I can tell the last case- > sensitivity bugs were fixed as of Mailman 3.2.1 (released 2019-02-22). > Postorius does not appear to have had any case sensitivity bugs (not > surprising since Postorius just passes them through to Mailman). > > I guess it's possible that this is a Debianism, or there was a > temporary regression around 3.3.8. > > > Is there a known configuration option or method within Postorius > > (or Mailman 3 itself) to normalize or unify account identification, > > effectively treating email addresses as case-insensitive for > > account matching? > > There is no such configuration option because Mailman has treated > email addresses as case insensitive for quite a while. All I can > recommend is an upgrade. > > Steve -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 7 months

Re: Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?

by Mark Sapiro

On 5/24/24 7:41 PM, Keith Christian wrote: > > mailman3 was installed into the below virtual environment: > (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary > Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or > any other supporting programs be installed into this virtual > environment ? If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you will install Mailman core, psycopg2-binary, mailman-web and mailman-hyperkitty in the venv. mailman-web will install Django, django-mailman3, MailmanClient, HyperKitty and Postorius as dependencies in the venv. > PostgreSQL and Postfix have been successfully installed outside of the > mailman3 virtual environment and start properly, I assume this is > correct. Since these are not python packages, they and sassc (or Dart-Sass) are installed outside the venv. Also, Postfix in particular and possibly PostgreSQL may be used by things other than Mailman so you don't want them in the venv even if they could be installed there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Mailman-users search results for query "Postorius"