Search results for "Postorius" - Mailman-users

Re: setup of URLs

by pmlists＠free.fr

> On Sun, Jan 28, 2018, at 12:24 PM, Peter Münster wrote: > This patch should do what you want: > > ``` > index a5ea108..bff54f3 100644 > --- a/example_project/urls.py > +++ b/example_project/urls.py > @@ -25,11 +25,10 @@ try: > except ImportError: > from django.urls import reverse_lazy > from django.views.generic import RedirectView > +from postorius.views.list import list_index > > urlpatterns = [ > - url(r'^$', RedirectView.as_view( > - url=reverse_lazy('list_index'), > - permanent=True)), > + url(r'^$', list_index), > url(r'^postorius/', include('postorius.urls')), Thank you. I've modified the patterns a bit, so that links to the list index, point also to "/": urlpatterns = [ url(r'^postorius/', include('postorius.urls')), url(r'^archive/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), url(r'^$', list_index, name='list_index'), ] > Just as an FYI, my browser would always re-direct me to /posotrius/lists, even after I > applied this patch, not sure if it was some sort of caching or something else. If it's Firefox, then you can right-click on the site in the history window, and select "Forget about this site". (Strange: I did not get your message by email. For this reply I use the web-interface.) -- Peter

8 years, 4 months

Re: MM3 on debian - redirect problem

by Gelpi Andrea

Il 28/04/20 18:31, Mark Sapiro ha scritto: > On 4/27/20 8:17 AM, Gelpi Andrea wrote: >> Hi, >> on a debian10 I have mm3 installed via apt-get >> >> apt-get install mailman3-full >> dpkg-reconfigure mailman3 >> dpkg-reconfigure mailman3-web >> >> I have this minor issue >> >> https://webserver/mailman3 redirects to >> http://webserver/mailman/postorius/lists/ >> >> that doesn't exist. >> >> The same problem form django admin page to return to lists >> >> https://website/mailman3/admin/sites/site >> >> In the upper right corner I have a link to https://webserver/mailman3 >> that redirects to https://mailman/postorius/lists/ >> >> I searched for a redirect but without success. > > > The redirection must be a web server issue. > > There is a urls.py file probably in the same directory as your django > settings - probably /usr/share/mailman3-web/urls.py in your case. > > You can make a URL like http://webserver/mailman/postorius/lists/ work > by adding > > url(r'^mailman/postorius/', include('postorius.urls')), > > to the urlpatterns list in the urls.py file. > > The problem seems to be inside the uwsgi proxy. Also django admin web interface has the some problem. I add /mailman in the apache mailman config installed by the debian package. --------------------------------------- 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/ ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> ------------------------------------- -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

6 years, 1 month

Re: cc'd e-mail addresses rewritten with @invalid.domain

by pwilliam＠fredhutch.org

Hi Mailman Users, I've done some more testing with this issue and have determined that this seems to be an issue with how commas within the display name in cc'd messages are being processed with messages sent from the Outlook client. Here are some test scenarios. Note I set the mailing list I was testing with to hold messages in moderation. Once the message was held I copied the information from the headers directly from Postorius held message information into the space below: Test Scenario 1: Display name in Outlook: Williamss, Peterr C Outcome: Does not work as intended. The CC address is formatted as Williamss(a)invalid.domain in messages received by mailing list members, oddly the "Peterr C" part of the display name is not present anywhere in the CC addresses received by mailing list members. Header information from held message in Postorius CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, "Williamss, Peterr C" <peterbw(a)test.com> Test Scenario 2: Display name in Outlook: Williams, Peter D Outcome: Does not work as intended. Interestingly, the CC address in the message received by mailing list members is formatted as two separate addresses in this case: Williams(a)invalid.domain and Peter(a)invalid.domain. "D" is not present anywhere. Could this issue be related to the number of characters? Header information from held message in Postorius: CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, "Williams, Peter B" <peterbw(a)test.com> Test Scenario 3: Display name in Outlook: Williamss Peterr C Outcome: Works properly. The CC address contains the correct address and display name information. The information in messages received from the mailing list contain the address formatted correctly as: "Williamss Peterr C peterbw(a)test.com" Header information from held message in Postorius: CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, Williamss Peterr C <peterbw(a)test.com>

5 years, 9 months

Mailman, etc. upgrade woes and persistent bugs

by hansen＠rc.org

I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: a. The ability of moderators to see the list membership (a bug). b. The ability of members to change their addresses for all lists they are subscribed to. and further, now: c. That when members go to look at their subscription info, they can actually see the settings. Thank you, Allan

5 years, 4 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, 4 months

Character set for postorius

by David Krantz

Hi, I'd like to have my descriptions of maillists with the correct characters for my languages... Where is the character set for this determined? If I input e.g. 'è' (è) or 'ö' (ö) it is substituted with a '?'. Of course the html entities are not allowed either, the ampersand '&' is escaped somewhere between output and input. Cheers // David

9 years, 1 month

Http/Https

by Bill

Hi folks, We're setting up Mailman 3.1 and so far installation has been good and we're now in the testing phase. We've run into a snag with the account signup function on Postorius. When Postorius sends an email to the user to confirm their address, it displays a link using the https protocol. This doesn't work. But, if we manually change the protocol to http it will work, confirm the address and take us back to Postorius. Is this a known bug or have we committed a configuration error? All assistance appreciated. Bill -- Sent using Icedove on Debian GNU/Linux.

9 years

Re: Acceptable aliases defaults to []

by Mark Sapiro

On 08/28/2017 11:30 PM, Henrik Rasmussen wrote: > > It happens in Postorius at https://example.com/postorius/lists/[LISTNAME].[DOMAIN]/settings/message_ac… in the top field "Acceptable aliases" (screenshot attached). This is reported at <https://gitlab.com/mailman/postorius/issues/58>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

Re: Django logins for new subscribers

by Simon Hanna

On 01/12/2018 09:17 PM, Alex McLean wrote: > to the discussion. The default welcome email didn't contain any web > links to postorius or hyperkitty. That's because neither are required to actually run Mailman. So I guess it's better to have the default not send anything, since the other way round would mean sending dead links. Currently the core component of Mailman doesn't have a way to know under which url Postorius is reachable...

8 years, 5 months

Re: Message Personalization: embed User name in header/footer‏

by Mark Sapiro

On 5/6/18 7:16 AM, Asaf Ohayon wrote: > Thanks, > I understand those features are not available (yet) on Postorius We're working on getting template editing in Postorius for release later this month. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Mailman-users search results for query "Postorius"