Search results for "Postorius" - Mailman-users

Re: Django: An error occurred while processing your request.

by Florian Sukup

Thank you both very much. On 5/26/25 18:30, Mark Sapiro wrote: > On 5/26/25 12:08 PM, Florian Sukup wrote: >> >> When I received emails from postorius, then it came from example.com >> which is nonsense as I worked with the real lists. So I deleted >> example.com. > > > Set DEFAULT_FROM_EMAIL and SERVER_EMAIL appropriately in your Django > settings. > seem to produce reasonable results >> When I call https://.../mailman3/admin or any of the lists, the result >> is: >> Server error >> An error occurred while processing your request. > > You need to set SITE_ID appropriately in your Django settings. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > This made the difference. I set it to 0 now as I have more than one site/domain. Thanks again, Florian.

9 months

Re: Mailman recovery test did not go as planned

by Stephen J. Turnbull

bob B via Mailman-users writes: > Is there a way to rebuild the archives for lists? If you keep a backup as an mbox file (this is what the "sample archiver" does), you can always reinitialize HyperKitty and reimport as if you were migrating a Pipermail archive from Mailman 2. HyperKitty (and Postorius) have data stores that are independent of those used by Mailman core. > What about rebuilding any static web pages outside the database, is > that even necessary? If you have changed any templates, you would need to reproduce those changes. Otherwise it's presumably just a matter of reinstalling the Django apps and running the "collectstatic" command in the Django manager. > I know in a real disaster the environment will not be down, so I > see three scenarios: They seem plausible (ie, covering all possibilities and the solutions) to me.

3 years, 6 months

Server 500 error for just one list, just one page

by kelly.close＠lrewater.com

I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… For a list called "alarms-all" obviously. Any ideas? I'm able to review the list, it's members, etc in the PostsgreSQL tables and I'm not seeing any members with funky characters in their address - the one thing I could think of to check. Thanks, ~Kelly

5 years, 8 months

Re: Installing mailman 3

by Rafael Mora

Look: [root@localhost mailman]# find / -name mailman.cfg /etc/mailman.cfg /root/var/etc/mailman.cfg /root/mailman/src/mailman/config/mailman.cfg /root/dev/mailman/mailman/src/mailman/config/mailman.cfg /var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/postorius/var/etc/mailman.cfg /mailman/mailman/src/mailman/config/mailman.cfg /mailman/mailman/build/lib/mailman/config/mailman.cfg /mailman/mailman/var/etc/mailman.cfg El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > There must be another config file being picked up. Have a look at the > mailman.cfg search order explained here [1]. > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' > to be sure. You'll want to delete any in the search path and then rerun > 'mailman info'. > > [1] > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > -Kyle > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

Countdown to the 3.1 release

by Barry Warsaw

Previously I mentioned the three big outstanding branches that I'd like to land for Mailman 3.1 Core, the templates branch, the MySQL support branch, and the unsubscription workflow branch. I've now also gone through all the bugs previously targeted to milestone 3.1, and there are only three left: https://gitlab.com/mailman/mailman/milestones/2 I think these are important enough to fix for 3.1 and I welcome merge requests while the other three branches are ongoing. Please take a look at any other bugs not assigned to milestone 3.1 and let me know if you think any are serious enough to block the 3.1 release. I'll say in advance that I'm going to be brutal in assessing them, because 3.1 really needs to be released soon! Note too that there may be blockers for Postorius, Hyperkitty, and mailman.client, but I haven't looked at those subprojects yet. How close are they to being release ready? Cheers, -Barry

9 years, 7 months

Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- 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

Re: [MM3-users]Re: Is it possible to grant all users the ability to Create List

by tibor.molnar＠waltoninstitute.ie

Hi, I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: Superuser: Can do everything. AnonymousUser: Can view list index and info pages. Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how?

4 years, 7 months

Re: Error downloading CSV for 1,300 members

by Mark Sapiro

On 2/23/23 10:45, Jose Bernal wrote: > Any suggestions on troubleshooting downloading a modest-size CSV file for a > list with 1,300 members? Clicking "CSV Export" on smaller lists works > fine, but on this larger list I get this error in mailman-web.log: > > Thu Feb 23 10:03:32 2023 - uwsgi_response_write_body_do(): Broken pipe > [core/writer.c line 429] during GET /mailman3/postorius/lists/ > members.list.ocdla.org/csv_view/ (172.31.54.89) > OSError: write error This is probably due to a timeout in uwsgi. This thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> is about timeouts when downloading archives, but the same considerations apply. To increase the worker timeout for uwsgi, set the harakiri option. See <https://uwsgi-docs.readthedocs.io/en/latest/Glossary.html#glossary> and <https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: Try to Implement Template for The message sent to subscribers when a subscription confirmation is required

by Stephen J. Turnbull

Gerald Vogt writes: > Why would you double book port 80? That's really a bad idea and > causes issues like the one you see... When I read that I assumed that nginx would resolve in favor of the narrower interface:port declaration. If double-booking is happening, nginx should be issuing an error, or (nginx being pretty picky in my experience) even refusing to start. Anyway, OP should look for messages about problems binding to ports in the nginx and uwsgi logs. > Your "INTERNAL" server binds to 127.0.0.1 port 80, only. That's not quite true. Normally the WSGI service will bind to another port for Postorius/HyperKitty, typically 8000. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 2 days

Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 01:22 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: >> >> You need to forward port 25 for SMTP mail delivery and if you want the >> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >> for http and/or port 443 for https >> < >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>> . >> > > I mean for incoming mail redirected from my hostgator hosting, because when > I suscribe an email address MM3 sends a confirmation email, so I have to > reply to be suscribed to the list. As I said, for mail delivery you need to forward port 25 to the Mailman server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Mailman-users search results for query "Postorius"