Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Strange URL in error message

by Mark Sapiro

On 7/14/24 9:14 AM, waps(a)tantalus.jena.thur.de wrote: > (Debian 12) > > I have the problem that the hyperkitty archive is empty. The file /var/log/mailman3/mailman.log show sometimes the message > > urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.XXXXX-project.demailman3', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa48b43a910>: Failed to establish a new connection: [Errno -2] Name or service not known')) > > (there is a slash missing between 'project.de' and 'mailman3'). My goal is, of course, to have an running archive. But I think the error message could be a hint about the reason) It appears that your setting for base_url in mailman-hyperkitty.cfg is missing the slash. I.e., it is http://www.XXXXX-project.demailman3/ and should be http://www.XXXXX-project.de/mailman3/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/2/24 20:33, jkoral(a)luc.edu wrote: > Not sure if this means anything. This is the log from old server after trying to send. I edited the FQDN and IP though. Any thoughts? I think it may be the configuration of postfix on the new server though. > > Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test(a)listservnew.example.com>, orig_to=<olivertest(a)lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) The message is deferred. Postfix will keep trying for maximal_queue_lifetime (default 5 days). Possible causes are a firewall on the new server blocking port 25 connects or some postfix misconfiguration on that server. Can that server receive mail at all? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Mark Sapiro

On 10/21/20 8:53 AM, Brian Carpenter wrote: > If you set the unsubscription policy to confirm then moderate for a list > and someone unsubscribes, they receive a confirmation request. That is > good. They respond to it. That is also working fine. However the list > owner/moderator than gets a request to approve the unsubscribe request > and well, unless I am missing something, I don't see an interface to > handles such requests via Postorius. This is <https://gitlab.com/mailman/postorius/-/issues/332>. > How does one handle an unsubscribe request that requires moderator > approval? I'm not sure at this point, I can look further later, but if the notice to the admin has a token, it might work to send a `confirm <token>` command to the list-request address. Otherwise, don't moderate unsubscription requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: High memory usage

by Mark Sapiro

On 2/16/22 00:18, Philip Colmer wrote: > Thank you for the replies from Mark and Stephen. > > One of the reasons why Prasanth & I are concerned with this specific system > is because the first time memory usage crept up, it got to the point where > oomkiller stepped in and, as is usual for that particular mechanism, one of > the processes it killed was sshd, thus removing access to the system :(. I > know that oomkiller can be tuned to stop it killing processes like sshd but > it will, nevertheless, start killing *some* processes if it sees an out of > memory situation. It sounds like there is a memory leak somewhere. This is an issue with some versions of Python. I know both Python 3.10.2 and 3.9.10 were released ahead of schedule to fix this. See https://bugs.python.org/issue46347 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 4 weeks

[MM3-users] Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Mark Sapiro

On 8/6/25 04:44, Wikinaut wrote: > Dear Mark, > > the problem has not gone. Now, in production during regular list upgrades, I got one member with 2(two) entries, one regularly encoded, the other double-escaped (can we call that so?). I'm interested in exactly what is done to produce these entries. Are you running `mailman syncmembers` or `mailman addmembers`? If so what is the input file that produces this. You can send it to me off list. > If you send me your private address, I can send you a screenshot. You can email me off list at the address in this and all my other posts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Difficulties setting up MM3 with Postfix MTA in Docker Environment: Invalid EHLO domain name & Authentification as lists.local

by Mark Sapiro

On 10/21/18 4:51 AM, Niklas Frühauf wrote: > > To me it seems like mailman is trying to authenticate as “lists.local” or “mail.local” or “localhost” to postfix (which of course isn’t working), then issues a EHLO/HELO to postfix which is not a FQDN. If the MTA requires authentication, you need to set smtp_user: and smtp_pass in the 'mta' section of mailman.cfg. By default, these are empty which means Mailman will not attempt to authenticate to the MTA for outgoing smtp. The actual connection to the MTA is via Python's smtplib. See <https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/authenticatio…> and <https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Mark Sapiro

On 7/28/25 13:07, Willie Castillo wrote: > I tried with a new post and still, not showing the messages from July 25th in the Archive. There must be a way to force the archiving of the messages from July 25th. > > List metrics > > Created at March 25, 2016, 11:15 a.m. > Last post at July 25, 2025, 12:01 p.m. > Digest last sent at July 25, 2025, 12:01 p.m. > Volume 135 Did the new post get archived? If so, why is last post at still July 25, 2025? If no, why not. The post must go to the archiver to cause the queue to be processed. If the post was archived and the July 25 messages are still queued, what's in Mailman's mailman.log. There should be error messages and tracebacks indicating the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/31/25 10:38, Odhiambo Washington via Mailman-users wrote: > > In one response, he mentioned that "Other mailinglists on the same host are > doing fine. Even a 1:1 copy of the list works - only the original list does > not work". > Does it mean that "the issue is in the outgoing runner" only for a single > list? So far we have not determined what the issue is. Until we do, we don't know in which module it is. It could be in outgoing runner involving something in the list's configuration or membership that isn't in the "1:1 copy" or it could be something to do with the message itself. It could even be an OS error such as "out of memory" due to the large number of list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

Search results for query "sapiro"