Search results for "Postorius" - Mailman-users

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

4 years, 5 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 1/18/24 05:36, samuel.d.darwin(a)gmail.com wrote: > > However our latest plan as of this moment is to revert back to a one-server implementation. mailman-core and mailman-web will be on the same machine. Thus, the enhancement is not critical. It still seems "theoretically" useful to implement the fix, unless the documentation states "it is recommended that core and web should be on the same machine" or similar. See the fourth paragraph at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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

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/ >

3 years, 9 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 5:02 AM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > >> >> >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >> wrote: >> >> /bin/sh: sass: Permission denied* >> >> >> >> Did you check the permissions on your sass binary? >> > > My mailman installed in /opt/mailman/mm > > find /opt/mailman/ -type f -name sass > > yielded nothing! Try `which sass` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > 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/ >

7 years, 2 months

Re: Mass un/subscribe optimization?

by Mark Sapiro

On 2/28/22 12:12, Bryan Loniewski wrote: > Hi -- > > We've noticed slowness in mass un/subscribing users; looking through the issue(s) log we see both #419 [1] and #627 [2] open and related. From the cmd line we get better performance, but with the subscriber size on many of our Faculty/Staff/Students ad-hoc lists (think 1k-15K subscribed addresses) and with our number of lists (2600) and unique owners utilizing these actions it would be helpful to optimize the mass actions. We wanted to get some thoughts and guidance on what needs to be optimized/redesigned/fixed? Or is there already something in the works, but needs more time? We may be able to provide resources to encourage and/or assist with any development and/or testing... > > We run a split core/web setup with Apache,mod_wsgi and MySQL backend (AWS hosted). > > [1] - https://gitlab.com/mailman/mailman/-/issues/419 > [2] - https://gitlab.com/mailman/mailman/-/issues/627 Regarding mass removal and #627, that should be fixed as of Postorius 1.3.5. What is your Postorius version. If you want to work on providing a REST endpoint for mass subscribe and supporting it in mailmanclient and Postorius, that would be great. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 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

5 months, 2 weeks

Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-01-30 12:08:10 -0800 (-0800), Mark Sapiro wrote: [...] > Domains can be created via Postorius or via the Mailman Core REST API that > postorius uses or implicitly by the `mailman create` command when creating a > list in a new domain. However, none of this can create a new site. You can > do this through the Django admin site at sites/site/add/. > > See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you > can use to do this programmatically. Thanks, I'm still doing my best to wrap my brain around how Django uses database migrations to create sites (seems like a very strange use of a migration, I'm only accustomed to seeing them applied for database schema updates). Once I work out how to script site creation, I'm still not completely finding the explanations I need for how to map them to domains in Mailman though. The Mailman documentation about domains says "Domains are how Mailman interacts with email host names and web host names" but doesn't actually go on to say (that I can find anywhere) how it actually associates them. I can see in the API docs that a POST to the domains endpoint will create a new domain with a specific mail_host FQDN, but there's some association somewhere of that to a web host (Django site), right? How is that set or manipulated through the API? Or is that something which has to be set directly in Django's data structures instead? To recap, on creation of a mailing list server I want to populate it automatically with multiple lists on different domains and have dynamic SITE_ID=0 domain guessing performed so that the correct site name and list filtering is performed depending on which domain name is used in a URL the client requests. I believe I need to have the automation perform the following steps: 1. Instantiate the Mailman installation and run initial migrations with SITE_ID=1 in order to avoid the problem mentioned in the docs about not using SITE_ID=0 until the tables have been populated, then switch the settings.py to use SITE_ID=0 once done. 2. Create the individual sites I need in Django (Mailman web hosts) by creating and applying database migrations. 3. Create the individual domains I need in Mailman (Mailman mail hosts) through its REST API. 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond to what web hosts. As I said, I'm still trying to understand how to make step 2 happen (Django has a steep learning curve for me), but beyond that I'm unsure how to do step 4 at all. I can do all of this through the WebUI of course, and have confirmed that it works as expected when I do, I'm just trying to work out the automation so that our other sysadmins don't have to perform these steps by hand the next time we need to rebuild the server. Thanks again for all the help so far, and for any additional insight anyone may have into how I can correct my mental model of all this. -- Jeremy Stanley

2 years, 5 months

Re: Hiding an ML from a site

by Mark Sapiro

On February 6, 2024 7:45:14 AM PST, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > >I had this set to True in settings_local.py, but False in settings.py. >So it seems to not make a difference in my setup. In a standard setup, anything set in settings_local.py overrides any corresponding setting in settings.py. That said, FILTER_VHOSTS is not perfect. It only works for Postorius if the separate web hosts also have different mail hosts. See lines 1051 et seq at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Re: Postorius & multi domain

by Mark Sapiro

On 4/22/20 11:37 AM, Gelpi Andrea wrote: > > I'm not a python programmer so I ask you if it'd be long to implement a > workaround like this. > > If the web server is a.example.com and the email domain is example.com > > It'd be possible to drop the "a" and send the email domain only in the > query? > > It's a workaround. Can you help me in this? I'm currently working on a better fix. I'll post here on my progress. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Mailman-users search results for query "Postorius"