Search results for "2021" - Mailman-users

Re: HyperKitty archiver <h1>Server Error (500</h1>

by Mark Sapiro

On 11/1/21 3:01 PM, Daniel Erlendson wrote: > ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > Traceback (most recent call last): > > plus a bunch of python errors and this: > > ValueError: A string literal cannot contain NUL (0x00) characters. This appears to be https://gitlab.com/mailman/hyperkitty/-/issues/271 fixed in HyperKitty 1.3.2 by https://gitlab.com/mailman/hyperkitty/-/merge_requests/215 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: Current status and issue deleting Archives in Mailman3

by Seth Seeger

> On Nov 2, 2021, at 2:50 PM, bob B <bader(a)cchmc.org> wrote: > > > $ docker exec -it mailman-web /bin/bash I always use "-u mailman" to keep file permissions correct: docker exec -it -u mailman mailman-web bash That may or may not be your problem, but it might keep you from having permission issues down the road. -Seth

3 years, 8 months

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Joel Lord

I got one of these yesterday as well. On 11/9/2021 7:06 PM, dancab(a)caltech.edu wrote: > We're also getting bit by this due to messages being replaced with the notice below. > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list". > > I'm looking to apply the patch above. > _______________________________________________ > 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/ > -- Joel Lord

3 years, 7 months

Re: Bug in 2.1.36?

by Joel Lord

On 11/12/2021 5:25 PM, Mark Sapiro wrote: > > > Thanks for the report. I think the issue is caused by the fix for > https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a > list admin is trying to handle moderator requests on a list that has no > moderator password. I'll investigate and try to put out another fix > later today. > The list definitely has a moderator password, but I'm not certain that the site had a sitepass set. I had to set one to get in and look around. -- Joel Lord

3 years, 7 months

Re: Bug in 2.1.36?

by Joel Lord

On 11/12/2021 5:25 PM, Mark Sapiro wrote: > Thanks for the report. I think the issue is caused by the fix for > https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a > list admin is trying to handle moderator requests on a list that has no > moderator password. I'll investigate and try to put out another fix > later today. > Just realized I misread your statement. No, these lists don't have any "moderators", so they don't have a moderator password set. Just admins, doing both roles. -- Joel Lord

3 years, 7 months

Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 11:55 -0500, William Oliver wrote: > > Another data point. When Ichange the port number in mailman.cfg, the > error changes to reflect it. When I change the port to 8055, I get: > > The mail system > > <"lmtp:[mail.libertyfp.org]:8055"@libertyfp.org> (expanded from > <fplist(a)libertyfp.org>): unknown user: > "lmtp:[mail.libertyfp.org]:8055@libertyfp.org" > Also, mail works fine outside of the mailing list.

3 years, 6 months

Re: [SOLVED] Re: Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Mon, 2021-12-27 at 16:38 -0800, Mark Sapiro wrote: > > > > Because you set > > smtp_host: mail.libertyfp.org > > in mailman.cfg. If you leave the default settings > > smtp_host: localhost > smtp_port: 25 > > you won't have this issue. > Aha. I thought I was being smart. You are right. billo

3 years, 6 months

Re: Lessons learned and a couple little gotcha for newbies

by William Oliver

On Tue, 2021-12-28 at 17:50 -0800, Mark Sapiro wrote: > The recommended uwsgi.ini includes > > pythonpath = /etc/mailman3/ > > according to > https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… > > this should work. Did you have that? If you did and it doesn't work, > perhaps adding > > env = PYTHONPATH=/etc/mailman3 > Yes, I had the first, and does not work. The second entry works. This is on debian 11/nginx/postgres/postfix system. Thanks, billo

3 years, 6 months

Re: is there a mailman command/setting to periodically clean archives?

by William Oliver

On Wed, 2021-12-29 at 16:11 -0800, Mark Sapiro wrote: > > > The cron will work for the prototype archives, but it's probably > easier > to just disable the prototype archiver. For HyperKitty, see the > thread > at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Cool. Thanks for the script. I'll give it a shot once I accumulate some archives. billo

3 years, 6 months

Re: Message-Footer after migrating to Mailman3

by Peter Münster

On Mon, May 24 2021, Mark Sapiro wrote: > To disable adding footers entirely, sitewide, create an empty file, > readable by Mailman at Mailman's > ``` > var/templates/site/de/list:member:generic:footer.txt > ``` > More about templates and search rules is at > templates/de/list:member:generic:footer.txt and > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… Hi, I have created an empty file /var/lib/mailman/templates/site/en/list:member:generic:footer.txt But there is still the default footer in the messages. How could I debug this issue please? TIA for any hints, -- Peter

2 years, 10 months

Mailman-users search results for query "2021"