Search results for "Postorius" - Mailman-users

FILTER_VHOST for 3.2.1 not working after install

by Élodie BOSSIER

Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french.

6 years, 2 months

Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Thu, Apr 11, 2024 at 11:00 PM Ron / BCLUG <admin(a)bclug.ca> wrote: > Mark Sapiro wrote on 2024-04-10 14:09: > > > I suspect you are not starting the services with your venv active. > > What's in your mailman3.service and mailman3-web.service files? > > Thanks for the pointer! > > I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` > somehow. > > > I changed that to match the docs, did the `systemctl daemon-reload`, > etc. but still had similar problems. > > > I went through all my config files carefully, I wiped the static folder > completely and rebuilt it, and I finally have the last piece of the > puzzle in place and my web interface is working! > > I'm not sure which change actually fixed the issue though. > > > (When looking at "Available lists" my header has "example.com" in the > top-left corner?!?) > See also this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… But read it as "example.com", not example.org :-) I think I need to backup what I have and do a clean re-install so I have > a better grasp of what's going on with all these components. > Way to go! Before I got MM3 working on the sites that I manage, it took me lots of installs and wipes until I could figure out what's going on. I was literally being hand-held by the good developers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 11 months

Re: Error when sending customized welcome message template

by Mark Sapiro

On 3/13/25 2:54 PM, Markus Grandpré wrote: > Dear List, > > As soon as a template "[list:user:notice:welcome]" exists, and at least > one email address is provided during mass subscribe, while sending an > invitation is disabled and sending a welcome message is enabled, the > following error occurs: > > HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, > 'Connection reset by peer')) Was this template set in Postorius? If so, there is an issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. The default is ``` POSTORIUS_TEMPLATE_BASE_URL = http://localhost:8000/ ``` which should work if your wsgi server is listening on the local host, port 8000, but setting it to the base scheme and host you use to access Postorius is generally good. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: error changed after restart

by Abhilash Raj

On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 6/2/21 21:19, Abhilash Raj wrote: > > > > > > On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via > > Mailman-users <mailman-users(a)mailman3.org> wrote: > >> On 6/2/21 18:08, Abhilash Raj wrote: > >> > >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via > >> Mailman-users wrote: > >> > >> I restarted de server and the error changed. Now the log > >> shows "KeyError: 'subscription_mode'": > >> > >> Did you also restart Mailman Core after the upgrade? > >> > >> Yes, indeed: I stopped mailman core and all the processes related. > >> Did the upgrades. Started all again. Find the errors in the web user > >> interface. Stopped all again. Looked for errors in the log. Restarted > >> the complete server. Found the second error that this second mail is > >> about to. It happens when, in the main page that shows all the lists > >> you click to see one of them. It seems to me that it has been > >> database structure changes in django that the upgrade is not aware... > >> but it's a very long shot from my side. > > `subscription_mode` was added in Mailman Core 3.3.2 and it is actually > > a derived atrribute and not stored in Database. Mailman's API should be > > returning this attribute for each Member, but for some reason it seems > > to me like it isn't doing that even though do have Mailman 3.3.3 running > > like you said. > > If you have Curl installed, can you send me the output of: > > $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 > > This is the output you asked for (it's the same you can see when you try > to interact with one list): > > /usr/local/mailman3 # curl -u XXXXXX:XXXXXX > http://localhost:8001/3.1/members?count=5&page=1 > /usr/local/mailman3 # <html> > <head> > <title>Internal Server Error</title> > </head> > <body> > <h1><p>Internal Server Error</p></h1> > > </body> > </html> > > No log entry has been produced... This is weird, if you have working Core, then there should be *some* json returned from the above command. Do you have the Gunicorn running? What is the output of `ps -ef | grep mailman`? Are you able to run `mailman members` command to list the members of a list? Also, how did you actually install Mailman? Abhilash. > TIA. > > > > > > It should ideally return an output that looks something like shown > > here[1]. You > > can put the username/password of Core's API server in the above command. > > [1]: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > > > Abhilash > >> I'm using sqlite as django database and mysql for mailman. > >> > >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal > >> Server Error: > >> /mailman3/mailman3/lists/name_and_domain.of.the.list > >> Traceback (most recent call last): File > >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > >> line 119, in __getattr__ return self._get(name) File > >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > >> line 86, in _get raise KeyError(key) KeyError: > >> 'subscription_mode' During handling of the above exception, > >> another exception occurred: Traceback (most recent call > >> last): File > >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", > >> line 34, in inner response = get_response(request) File > >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", > >> line 115, in _get_response response = > >> self.process_exception_by_middleware(e, request) File > >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", > >> line 113, in _get_response response = > >> wrapped_callback(request, *callback_args, **callback_kwargs) > >> File > >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", > >> line 71, in view return self.dispatch(request, *args, > >> **kwargs) File > >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", > >> line 74, in dispatch return super(MailingListView, > >> self).dispatch(request, *args, **kwargs) File > >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", > >> line 97, in dispatch return handler(request, *args, > >> **kwargs) File > >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", > >> line 295, in get member.subscription_mode == File > >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > >> line 124, in __getattr__ self.__class__.__name__, name)) > >> AttributeError: 'Member' object has no attribute > >> 'subscription_mode' *********************** some info about > >> the installed versions via pip list: pip list | grep django > >> django-allauth 0.44.0 > >> django-appconf 1.0.4 > >> django-compressor 2.4 > >> django-extensions 3.1.0 > >> django-gravatar2 1.4.4 > >> django-haystack 3.0 > >> django-mailman3 1.3.5 > >> django-picklefield 3.0.1 > >> django-q 1.3.4 > >> djangorestframework 3.12.2 pip list | grep mailman > >> django-mailman3 1.3.5 > >> mailman 3.3.3 > >> mailman-hyperkitty 1.1.0 > >> mailmanclient 3.3.2 pip list | grep postorius > >> postorius 1.3.4 On 6/2/21 11:12, > >> Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> > >> I've just upgrade mailman 3 installation following Mr. > >> Sapiro advice: did a pip install --upgrade > >> django-mailman3 hyperkitty mailman mailmanclient > >> mailman-hyperkitty postorius I did a "python3 manage.py > >> migrate" after, too. And all seemed to run well. All the > >> lists showed in postorius via web, but when I try to > >> accesss into one of them the browser shows an error. In > >> the log you can see: *-*-*-*-*-*-* Traceback (most recent > >> call last): File > >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > >> line 119, in __getattr__ return self._get(name) > >> File > >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > >> line 86, in _get raise KeyError(key) KeyError: > >> 'get_requests_count' .. (And after all the traceback > >> lines) AttributeError: 'MailingList' object has no > >> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists > >> seem to be distributing messeages well.. but I cannot > >> acces via web administration (django/postorius) Can > >> anyone point me in the right direction to solve this, > >> please? _______________________________________________ > >> Mailman-users mailing list -- mailman-users(a)mailman3.org > >> <mailto:mailman-users@mailman3.org> To unsubscribe send > >> an email to mailman-users-leave(a)mailman3.org > >> <mailto:mailman-users-leave@mailman3.org> > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> > >> > >> > >> _______________________________________________ Mailman-users > >> mailing list -- mailman-users(a)mailman3.org > >> <mailto:mailman-users@mailman3.org> To unsubscribe send an > >> email to mailman-users-leave(a)mailman3.org > >> <mailto:mailman-users-leave@mailman3.org> > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> > >> > >> > >> _______________________________________________ Mailman-users mailing > >> list -- mailman-users(a)mailman3.org > >> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to > >> mailman-users-leave(a)mailman3.org > >> <mailto:mailman-users-leave@mailman3.org> > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> > > > _______________________________________________ > 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, 1 month

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

On 21/06/2020 04:52, Mark Sapiro wrote: > On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: >> ... the Body of reply, with the JSON text: >> >> { >> "start": 0, >> "total_size": 1, >> "entries": [ >> { >> "alias_domain": null, >> "description": null, >> "mail_host": "ch-bc.org.uk", >> "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", >> "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" >> } >> ], >> "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" >> } > > All these self_link references are generated from self.api.path_t which > is a reference to (in the case of 3.1) > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… > which gets the host portion from config.webservice.hostname, i.e. the > value of hostname in the webservice section of mailman.cfg, and actually > <sigh>, looking back at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > that's exactly where you said you set it to 0.0.0.0. > > Change that to greyarea-post Problem is, if I do that (which I did in the beginning), the core rest service listens on localhost / 127.0.0.1 (it obviously recognises that as the , and so cannot be connected to by anything. That is why I set it to 0.0.0.0 to begin with, and what the documentation implies (fairly strongly) that this parameter is about. IMO, the hostname parameter needs to be split up into a "what address should the rest of the world use to address me" and separately "what address(es) should I listen on". Multiple listen addresses enable multihomed hosts to get the right connectivity, too. Would that be hard? Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 8 months

Re: Multiple domain problem

by Odhiambo Washington

Are you by any chance doing redirection to https in your VHOSTS? For me I beg to see your VHOST configuration. Also is it absolutely necessary to hide your domain names? On Mon, Feb 13, 2023, 13:05 Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi, Marik! > > I realized that I had two variables in settings.py where the domains is > listed, and one of them had a preceding https. > > I've now followed the documentation for configuring Apache here: > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. > I want both domains to start mailman3 when contacting > example1.com/mailman3 and example2.com/mailman3. I have the sam > configuration in both virtualhost section in Apache. For > example1.com/mailman3, it works perfectly. For example2.com/mailman3 > however, the browser (elinks), reports Host not found: example2.commailman3 > e.g. without a slash after the domain name. What could cause this to happen? > > Thanks > Lars > > On Fri, Feb 10, 2023 at 11:59:02AM -0800, Mark Sapiro wrote: > > On 2/10/23 01:43, Lars Bjørndal wrote: > > > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > > > > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > > > > > > > If I connect to example2.com, the title is example2.com, without > the > > > > > preceding List index. And the body says Page not found. > > > > > > > > > > > > What's in the browser's address bar for that page? > > > > > > It's https://example2.com/mailman3/lists/ > > > > And when you get the Page not found, is it a browser 404 error or a > > Postorius error page? > > > > > > > > > > > What's in Postorius domains view? > > > > > > I realized that I have to change SIT_ID to 1 to be able to connect to > http://localhost:8000/. Then, when checking Domains, I have both domains > with different SIT_ID value (1 and 2). > > > > > > Why are you going to http://localhost:8000/? You should be able to see > the > > domain's view at https://example1.com/mailman3/domains/ or > > https://example1.com/mailman3/domains/ or by just clicking Domains in > > Postorius top nav bar. > > > > > > > Going to http://localhost:8000/admin and choosing Sites, I have both > domains listed. > > > > > > Again you should be able to go to https://example1.com/admin or > > https://example2.com/admin. If these don't work, you need to add > directives > > in your web server to proxy them to http://localhost:8000/admin > > > > -- > > 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/ > > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to lars(a)lamasti.net > _______________________________________________ > 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 odhiambo(a)gmail.com >

3 years, 1 month

Re: Whitelist non subscriber

by Mark Sapiro

On 08/06/2018 06:43 AM, Stephan Krinetzki wrote: > The steps are as follows, right? > - Add users to the list and give the role "nonmember" > - Set moderation action ('defer' or 'accept') Right. > The only thing missing in the documentation is a note on how to do this via the Admin API. Who can explain that to me? Can you be more specific about what you are looking for? If by "Admin API" you mean the REST API, are you asking how to interact with it or what specific POST/PUT/PATCH commands to send? Or are you asking about the 'mailman shell' command? Also, we want to expose the nonmember role in Postorius and enable setting moderation action for nonmembers, but we didn't get that in MM 3.2/Postorius 1.2. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Re: Changing default message limit (max_message_size)

by Mark Sapiro

On 5/27/19 12:05 AM, roger(a)reasonal.com wrote: > I found the field in settings that would appear to do this, but it just throws an error for whatever I give it ("An error occured**: Unknown attribute: max_message_size"). This should be fixed at <https://gitlab.com/mailman/mailman/merge_requests/329>. Perhaps you need to update your Docker images <https://asynchronous.in/docker-mailman/> Also, see <https://gitlab.com/mailman/postorius/issues/246#note_69323948> for a not about changing this via `mailman shell` (withlist), but see the subsequent comment about `quit()` > PS As a suggestion, may be a good idea to indicate what units it's expecting... bytes? kB? Nybbles? Reported at <https://gitlab.com/mailman/postorius/issues/362>, thanks. > PPS ** Psst: occurred with two r's... Reported at <https://gitlab.com/mailman/postorius/issues/361>, thanks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

Mailman not able to process "big" requests

by Jonas Felber

Hi, We migrated from mailman2 to mailman3 a week ago. Since then we are unable to send messages the our students through the mailing list. Here are some symptoms: 1. I go to mass subscribe and subscribe 400 emails 2. I click subscribe, the browser (in my case safari) tries to load the page for a few seconds 3. The request times out 4. Once the service becomes responsible again, I see that only part of my emails got subscribed (~50 in this case). For me this really looks like the emails are sent on the "web-thread" that gets killed once the request times out. Looking at this https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p… <https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p…> seems to confirm my suspicions. Some quick overview of our infrastructure: The TCP endpoints are: browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes-ingress -> nginx in mailman -> mailman We mitigated the issue by giving it more CPU power and increasing the timeouts in one of the nginx endpoints. We also have a problem with sending out emails to "large" (>50) groups, as they seem to not getting sent out at all. Do you have any idea what the problem here could be? We would be really glad if you can help us getting our mailman up and running, as I currently have to send emails out by "hand". I will happily provide you with more details about our configuration, just let me know what you need. Kind regards, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch <mailto:jonas.felber@vis.ethz.ch>> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch <https://www.vis.ethz.ch/>

7 years, 10 months

Re: Your Dashboard

by Mark Sapiro

On 2/11/20 11:00 AM, Mark Dadgar wrote: > On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >> everytime I receive a mail for moderation it says: >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. There's no overall dashboard per se. The message actually refers to whatever web UI you use to manage the list. The default template for this message is non-specific because it comes from Mailman core, and core doesn't know if you are using Postorius or some other web management system or non at all, and even if it were to assume Postorius, it doesn't know the URL. >> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >> >> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? As I said, there is no overall dashboard in Postorius, just the individual list management pages. > This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. I explained above why this is the case, but you can fix it. You do so by making a sitewide template for this message. In the case of this list, we have a template in Mailman's var/templates/site/en/ directory (the default directory for sitewide english templates. This template is named list:admin:action:post.txt and its content on this site is: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: $listname > From: $sender_email > Subject: $subject > > The message is being held because: > > $reasons > > At your convenience, visit > https://lists.mailman3.org/mailman3/lists/$list_id/held_messages Of course, in your case the <https://lists.mailman3.org/mailman3/> part of the URL will be different. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> for the other templates I also install. You can also put domain specific templates in var/templates/domains/$domain/$lc/ which override site templates for the domain and list specific templates in var/templates/lists/$list_id/$lc/ which override site and domain templates for the list, and you can also set list templates via Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Mailman-users search results for query "Postorius"