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

[MM3-users] Re: start_chain not present in migrated lists

by Mark Sapiro

On 1/21/20 6:22 AM, Paul Honig wrote: > > It seems like the start_chain has value 'None' and that prevents the > mail from processed, but I can't find where to correctly set the > start_chain. You are correct. Every list has a 'posting_chain' attribute and it seems for your imported lists, that attribute's value is None. I don't know how that can happen. How did you create the lists before importing them? > Please let me know how I can remedy this issue. You can use `mailman shell` mailman shell -l mltest(a)test.domain Welcome to the GNU Mailman shell The variable 'm' is the mltest(a)test.domain mailing list >>> print(m.posting_chain) None >>> m.posting_chain = 'default-posting-chain' >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/13/21 5:42 PM, Abhilash Raj wrote: > > You can actually translate the templates in Weblate too. That is > actually the whole > reason to go with monolingual template format in Mailman Core. > > Mailman uses the template file's name as the msgid for translations and > all in-tree > templates are copied into English's .po file when we re-generate them. > > For example in here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > The english .po file is considered as reference in Weblate and used for > source string. But it appears that we are lacking a mechanism (other than some manual process which isn't reliably done) to move the translated templates from the translated .po file to the appropriate templates/<lc>/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Help with Newbie error -- I think I deleted my server

by Mark Sapiro

On 12/24/21 8:22 PM, William Oliver wrote: > > I clicked on that, and it took me to a page where I could add servers. > So, I added my real domain (libertyfp.org) It successfully added it, > so I decided that I clearly didn't need "example.com" as a server, and > deleted it using the same page. > > Immediately, I got an "internal server error" and have now lost all web > interfaces. I tried restarting the daemons and rebooting the box, to > no avail. You have to set SITE_ID in your Django settings to the correct value for your site. See https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: [MM3-users][RESOLVED] HELP: mailman send empty mails

by Mark Sapiro

On 2/4/22 05:31, Axel Rau wrote: > Too many concurrent DB server connections seems to be the reason: > - - - > connection failed: FATAL: remaining connection slots are reserved for > non-replication superuser connections > - - - > A 2nd mailman instance was unintentionally activated and had stolen the > connections slots. Your analysis may be correct, but see https://gitlab.com/mailman/mailman/-/issues/955 >> The content of this message was lost. It was probably cross-posted to >> multiple lists and previously handled on another list. This is a dummy message which is returned on an attempt to get a message from the messagestore that doesn't exist. The message should only be in the message store in the first place if it was held for moderation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

Mark Sapiro wrote: > Thus, the issue occurs downstream of lmtp runner. It will take more > investigation to determine where. The issue occurs in mailman/handlers/avoid_duplicates.py. That module will rewrite the Cc: header after possibly deleting some of the entries. That module calls msg.get_all('cc') to get the original Ccs and calls email.utils.getaddresses() on that to get a list of all the name, address pairs. In our case, msg.get_all('cc') returns one of two things. If the message came via LMTP with CRLF line endings, it returns ['"ABC DEF\r\n (XYZ)" <mark(a)msapiro.net>'] If the message came from `mailman inject` with LF line endings, it returns ['"ABC DEF\n (XYZ)" <mark(a)msapiro.net>'] then email.utils.getaddresses() calls internally email.utils.parseaddr on each item in the list to make a list (of one in our case) of name, address pairs. The result is different depending on the line endings which explains why it works with `mailman inject` but not with LMTP. In the case where the line endings are LF, the return is [('ABC DEF\n (XYZ)', 'mark(a)msapiro.net')] but if the line endings are CRLF, the return is [('XYZ', 'ABC DEF')] If the "folding" is not quoted as in ABC DEF (XYZ) <mark(a)msapiro.net> then the return is ('ABC DEF (XYZ)', 'mark(a)msapiro.net') regardless of the line ending as it should be. I can't really fault parseaddr() here because the only time it produces an unexpected result is when the CRLF line folding occurs in the middle of a quoted string which is clearly non-compliant. For Mailman to defend against this, something like the attached patch would do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Mailmansuite.log Entries

by Mark Sapiro

On 12/1/20 5:31 PM, Brian Carpenter wrote: > > On 12/1/20 8:22 PM, Mark Sapiro wrote: >> Those come from the HyperKitty sync_mailman job which is run by >> hyperkitty_import if you don't specify --no-sync-mailman, but is also >> one of the Django daily jobs. > > Ok but those number are the same for thousands of entries and apparently > are being logged for weeks. That can't be good. How does one fix this? The sync_mailman job does two things. The first thing it does is for all lists known to HyperKitty, it gets the list attributes "display_name", "description", "subject_prefix", "archive_policy", "created_at" and "list_id" from Mailman core and updates the list properties in Hyperkitty. Then it gets every message sender known to Hyperkitty for which HK's sender.mailman_id is null, and, 1000 senders at a time, it tries to get and set the core user_id for the address to the sender's mailman_id. What happens when you import old archives, you archive a lot of posts with senders that are no longer list members and are not known to core, and every time sync_mailman runs, it tries again to get those core user_ids. You definitely want the first part to run to pick up changes like a change in archive_policy or a change in subject_prefix (to be able to strip it from Subject: headers. The second step could also find a newly registered core user, but is less important. Whether it is bad is a matter of opinion. At worst, it is a waste of some processing time, and at best it will pick up new users if there are any. "Fixing" it requires modification of the sync_with_mailman function in hyperkitty/libs/mailman.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Archiving error

by Mark Sapiro

On 10/05/2018 09:39 AM, Enrique Terrazas wrote: > > I have a follow up question, I tried setting the base_url to https but received SSL errors in the mailman.log. The nginx.conf is using a valid certificate from a CA and the sites(Django admin, Postorius, Hyperkitty) all load with https in the browser, they are redirected from http as well. But it seems that internal communication is failing when I try to specify https in the base_url > Is this something that I should be concerned about and can be configured? I have base_url: https://host.name/... without a port in mailman-hyperkitty.cfg on several servers and that works fine. I think the issue is when you specify https://host.name:8000/... you are going directly to Django and bypassing nginx and it's nginx that has your SSL certificates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/5/21 10:12 AM, Duane Raymond wrote: > Thanks for the continued input on this. It's really appreciated! > > I've reverted the changes I made with virtual domains and tried again (after restarting postfix and mailman). The result back was like > > <test(a)oldlist.com> (expanded from <test(a)emaillistA.com>): host > oldlisthost.com[ip] said: 550 5.1.1 > <test(a)oldlist.com>: Recipient address rejected: User unknown in > virtual alias table (in reply to RCPT TO command) > > But I can't find oldlist.com in the configuration settings. It was set as an alias for emaillistA.com domain, but was removed. > > So still looking for a solution...am considering a reinstall from scratch....but that seems rather drastic! Please post the output from `postconf -n` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: REST API - memberships of an address not linked to a user

by Mark Sapiro

On 10/13/26 1:57 PM, Bradford Bulger wrote: > I have an address that is no longer linked to any user. It was linked in the past, and it was added to a mailing list while linked. The link between the user and the address has since been deleted. Which is why > But if I query for the memberships of that address - addresses/bbulger(a)ozone.arc.nasa.gov/memberships - there are no results. That query first finds the user associated with that address and then returns the memberships of that user. There is a note to improve this to get the memberships by address, but it's not implemented. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/addresses…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 days, 20 hours

Search results for query "sapiro"