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

[MM3-users] Re: Moving existing lists to a new domain

by Jeremy Stanley

On 2024-11-21 14:22:27 -0800 (-0800), Mark Sapiro wrote: > On 11/21/24 07:43, Jeremy Stanley wrote: > > > > Preparing to test this, I poked around the schema a bit and noticed > > that the domain names are also embedded as strings in the following > > fields: > > > > django_mailman3_maildomain.mail_domain > > django_site.domain > > django_site.name > > These are all Django things. You can modify those values in the db. > > Note that django_site.name is just a name and doesn't need to be the exact > domain name. > > > domain.mail_host > > This is Mailman core's domain table. Again, you can modify the value in the > db. Yeah, I was planning to address all of those with additional SQL update queries, just wanted to make sure I found all relevant references to the domain name. > > Can anyone think of any additional tables/columns which would need > > updating for this? I'll see if scanning a dump of the full DB > > content turns up anything I might be missing too. Thanks again! > > I don't think there's anything else. Awesome, thanks again, as always! -- Jeremy Stanley

1 year, 8 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

Okay, so the issue has been fixed by updating the data to an empty list equivalent (after finding, confirming and copying another lists empty value): MySQL [mailman]> SELECT accept_these_nonmembers INTO @newatn FROM mailinglist WHERE list_name='foo_is_a_good_list_with_emptyval'; MySQL [mailman]> UPDATE mailinglist SET accept_these_nonmembers=@newatn WHERE list_name='the_borked_list'; Query OK, 1 row affected (0.02 sec) Rows matched: 1 Changed: 1 Warnings: 0 Thanks for the help on troubleshooting that! Based on your import21 comments, I'm realizing the issue may be caused by multiple runs of import21. I have been (although I've stopped it for some time now) running import21 nightly to sync up my Mailman3 list data with Mailman2. I've been doing the same for archiving as well. I've noticed now that some lists have duplicate acceptable alias entries (looks to be like <number of aliases> x <number of import21 runs>) and the same goes for *_these_nonmembers entries. Is this a symptom of running the old(er) import21 command pre-3.3.2? Will the 3.3.2 import21 work as expected w/out the duplications if I was to clear out the appropriate lists col data (i.e., is it okay to run import21 multiple times)? I tried to figure out if there were any other duplicative data, but did not come across any. Is there more that I'm missing? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:28 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 21:58 : > On 6/15/20 12:37 PM, Gilles Filippini wrote: >> >> There are 4 emails stored into this folder. 3 of them are spam, and the >> last one is a legitimate email. This is annoying that such emails could >> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >> more and more hyperkitty errors. >> >> Any idea how to make their processing more error proof? > > > Change the offending .encode() method to add errors='replace'. > > The traceback from the error should tell you where it is. > > You could also open an issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If > you do that, please include an error traceback if possible. If there is > not a traceback in mailman.log associated with the error, there might be > one in HyperKitty's log (configured in Django's settings). Also, > including enough of a message to duplicate the issue is very helpful. I've now deleted the offending messages. Will open an issue with related details the next time this error occurs. Thanks a lot, _g.

6 years, 2 months

[MM3-users] Re: Welcome message template errors

by Mark

>> On 2024-04-23 11:33, Mark Sapiro wrote: >> That URI should have been; >> >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > I think you are saying the what you reported originally was not > correct and the URL in the template table was in fact the latter URL. I meant when I typed the URL in my first email I had unintentionally omitted the name of the list (mytestlist) when I redacted the real domain name to 'lists.mydomain.com'. ...emplates/list/lists.mydomain.com/list:user:noti... I should have written ...emplates/list/mytestlist.lists.mydomain.com/list:user:noti... >> If I go to the above URL, the text of the list's Custom welcome >> message displays on an otherwise empty webpage. > > > And that's what is expected. So you can go to that URL and get the > template, but when Mailman Core tries to do the same thing, it gets a > timeout. Is there some firewall or other security software blocking > this access? #ufw disable Firewall stopped and disabled on system startup Then restarted everything... # ufw status verbose Status: inactive And still getting the error in the Postorius webpage ... HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', port=443): Read timed out. (read timeout=5)

2 years, 3 months

[MM3-users] Re: Header Filter madness

by Brian Carpenter

On 1/11/21 8:48 PM, Mark Sapiro wrote: > On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >> I have a client whose header filters seemed to have stop working. No >> matter what I try, it seems none of their header filters are being >> applied. Other lists on the same server that use header filters, are >> working fine. This particular header is the subject header. I can >> duplicate their problem but only with their list. If I create the exact >> >> same header on a test list using the exact same subject line, the >> header >> filter does its job (moderate). Just not with this one list. > Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules. > > The "Default action to take when a member posts to the list " is set to Default Processing for the problematic list. The list members moderation action is set to "List Default" for the problematic list. I duplicated the same settings using another list. Header filters works fine on the test list, does not on the production list. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 7 months

[MM3-users] Re: clearing pending db

by Morris Jones

On 8/8/25 11:48 AM, Mark Sapiro wrote: > On 8/8/25 09:59, Morris Jones wrote: >> >> But pendingdb.evict() doesn't seem to clear the list. For example, on >> one of my lists: >> >> >>> from mailman.interfaces.pending import IPendings >> >>> >> >>> from zope.component import getUtility >> >>> >> >>> pendingdb = getUtility(IPendings) >> >>> pendingdb.count() >> 5040 >> >>> pendingdb.evict() >> >>> pendingdb.count() >> 5040 >> >>> > > > pendingdb.evict() only deletes expired pendings, but by default > subscriptions pending confirmation expire after 3 days, but this is set > by pending_request_life in the [mailman] section of mailman.cfg. Have > you set that to a long time? > > On the other hand in Mailman 3.3.2, subscriptions pending approval were > pended with a 10 year lifetime. This was changed in 3.3.5 to a new > moderator_request_life setting (default 180 days). > > If you just want to delete all pendings you could do > ``` > pendingdb = getUtility(IPendings) > for pending in pendingdb: > pendingdb.confirm(pending[0], expunge=True) > # and if doing this in mailman shell > commit() > Perfect, thank you Mark. :) Mojo -- Morris Jones, Monrovia, CA

1 year

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/10/25 04:13, Mark Sapiro wrote: > >> I have deleted site - group - list now. And created the site again. If >> I go to 'view site' I see all mailing lists on the server and not only >> from this site/domain. This is the first thing where it shows >> irregularities. > > I'm not sure what you mean by `view site` but if you mean the VIEW SITE > link at the top of the Django admin UI, that is just a link to the host > site. I.e., if the Django admin page is https://www.example.com/admin/ > site/, its VIEW SITE link just goes to https://www.example.com/ and it's > always the same link regardless of what Django admin page you are on. > The url of the Django view is lists.example.com/mailman3/admin. The 'VIEW SITE' is in the header on the right side. It's a link to lists.example.com/mailman3 which apparently gets redirected to lists.example.com/mailman3/postorius/lists. The difference I am talking about is that lists.example1.com/postorius/lists shows only its mailing lists while lists.example2.com/postorius/lists shows all mailing lists on the server (ie. also mailing lists of example1.com) Flo

10 months, 1 week

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Fri, Nov 3, 2017, at 08:29 AM, Fabian A. Santiago wrote: > October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > > > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: > > > >> That was it. Perfect. I manually modified my regexp map and it works > >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh > >> those maps or only as I add new domains / lists? > > > > Only when you make changes to domains or lists. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> > > Sent from my Not_an_iThing with standards compliant, open source software. > > Mark, > > I've noticed that even simply restarting the mm3 components those alias > maps get rewritten and the problem returns until I can manually edit it. Yeah, that is true. Transport maps are re-generated everytime the container restarts. I don't think think there is any way around this right now :( > > -- > > Thanks, > > Fabian S. > > OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 9 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Barry Warsaw

On Sep 21, 2017, at 18:35, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: >> On 09/21/2017 01:29 PM, Andrew Hodder wrote: >>> >>> I keep getting around this by creating symlinks to the pid file and then >>> the stop works, but it's getting silly. It seems like mailman just assumes >>> CWD + /var/ + master.pid must be the location. Once I realized this, I >>> found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since >>> it'd then add /var/master.pid). But that seems a little nonsensical. >> >> That is the normal expected behavior if devmode is enabled. Check your >> configs for this. > > I don't think `devmode` has anything to do with this, it only disables > sending out emails by accident and routes all emails to a pre-defined > address. Haven't looked at the relevant portion of the source so I might > be wrong. That’s correct. The [paths.*] sections are what control the file system layout, and [mailman]layout is what defines which of the [paths.*] sections to use. Cheers, -Barry

8 years, 10 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

I top post just for confirming that all your recommendations worked well and I am aplying them in the rest of servers Thanks a lot and all of you have a happy new year. El 27/12/22 a las 9:23, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: >> ... >>> I don't want to put more noise in the list. But I'm confused because >>> I always updated via pip the apache mod_wsgi thinking is was needed >>> for my configuration. If it is not, I will stop updating it. >> >> Based on the above you ARE using Apache mod_wsgi and if you are still >> also running uwsgi as >> >> /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & >> >> that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) > and see how it goes. > > Again, thanks for your kind support. > > > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 7 months

Search results for query "sapiro"