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

[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

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

1 year, 7 months

[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

10 months, 2 weeks

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/8/25 13:25, dap1--- via Mailman-users wrote: > Same as before. > > <venv> $ mailman info > GNU Mailman 3.3.10 (Tom Sawyer) > Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] > config file: /opt/mailman/var/etc/mailman.cfg And is /opt/mailman/var/etc/mailman.cfg now a symlink to /etc/mailman3/mailman.cfg? If not, make it so. If it is you could try rm /opt/mailman/var/etc/mailman.cfg cp /etc/mailman3/mailman.cfg /opt/mailman/var/etc/mailman.cfg > db url: sqlite:////opt/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > It is getting late here so I probably won't get back to this until tomorrow. Thanks for your help and sorry for being a PITA. We want to help. The only pain is when you don't provide requested information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: > On 2016-08-19 17:58, Mark Sapiro wrote: >> On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >>> >>> No matter what action I set for member posts (Hold for moderator, >>> Reject) they are always delivered. >> >> >> I don't know why this would be. Perhaps the member's moderation is set >> to Accept immediately - you can see this on ther member's options page >> in Postorius when logged in as a list owner. > > Apart from "Mode of Delivery" that is set to "Regular" for the user, > none of the following attributes are set: > > Mail Delivery > Receive own posts to the list > Receive acknowledgement mails > Conceal address from the subscriber list > Avoid duplicate copies of messages If you look at the user's options when logged in as a list owner, you should see an additional "Administration options" section below those with a "Moderation" setting. What is that set to? ... > By the way, I didn't mention before but in Settings | Message > Acceptance, the "Acceptable aliases:" box contains "[]". When I try to > Save changes after modifying something, I gut "An error occured: []" in > the yellow banner (instead of "The settings have been updated."). What happens if you clear the Acceptable aliases box before saving? ... >> This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> >> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> > > Any ETA when this will be pushed to "mailman-bundler"? I expect bundler will be updated when 3.1 is released and that should be soon. You may find <https://wiki.list.org/x/17891998> of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 10 months

[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

7 years, 8 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

10 months, 3 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

10 months, 3 weeks

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 9:29 PM, Mark Dadgar wrote: > On Jun 9, 2020, at 1:57 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> THANK YOU for all the help. >> >> >> I'm glad we finally got it resolved. > > > I may have spoken too soon: > > [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 729081): Term too long (> 245): XSUBJECT95251413 > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update > backend.update(index, current_qs, commit=commit) > File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 492, in update > database.replace_document(document_id, document) > xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 > > "XSUBJECT95251413“ has some serious weirdness embedded in it. > > Not sure how to search for that in the django shell? I suspect the issue here is the 'weirdness' is in the Subject: rather than the message body. The script we were using only looked at the body. The message you sent me had a Subject which visually looked like `[PDC] MEGAMillions- Ticket №7383246 9` but the № and the digits were interspersed with strings of unicode zero width spaces, so the decoded Subject: was actually '[PDC] MEGAMillions- Ticket №7\u200b\u200b\u200b\u200b\u200b\u200b\u200b3\u200b\u200b\u200b\u200b\u200b\u200b\u200b8\u200b\u200b\u200b\u200b\u200b\u200b\u200b3\u200b\u200b\u200b\u200b\u200b\u200b\u200b2\u200b\u200b\u200b\u200b\u200b\u200b\u200b4\u200b\u200b\u200b\u200b\u200b\u200b\u200b6\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b9\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b' where all the \u200b unicodes are the zero width spaces. I suspect your current issue is with the Subject:. Actually, looking back at the thread, the prior one probably was too, but we also found messages that had this in the body. To alter the specific script to look at the Subject: just change the line if email.content.find('\u200b'*5) >= 0: to if email.subject.find('\u200b'*5) >= 0: There's probably a reply there somewhere that has the Subject: but didn't quote the bad stuff in the body. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Memory footprint

by Mark Sapiro

On 04/10/2017 02:25 PM, David Krantz wrote: > Hi. > > Now running mailman 3 I am a bit surprised that the memory footprint > is so large. I count to 13 processes with each a virtual space of > 160-250MB and a reserved space of about 50MB each. Not much, but quite > much to run on smaller cloud instances which generally have limited > memory. This is (a lot) more than the corresponding postgres > installation uses, > > Is this normal? Those numbers seem "normal" but you really have to look deeper to understand if you just have a bunch of processes sitting in memory because the memory is available and nothing else wants it, or if there's real memory contention going on. The article at <https://wiki.list.org/x/4030711>, while written about Mailman 2.1, has some general information which may be of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

Search results for query "sapiro"