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

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 00:21, Mark Sapiro ha scritto: > On 2/28/21 10:17 AM, blackout69 wrote: > It looks to me like a race condition of some kind or possibly an > incompletely deleted thread. Have you deleted any threads? I have not deleted threads > I'm curious as to how you happen to be going to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> > as opposed to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. > I know that ULS and similar ones are in HyperKitty's urls.py, but I > don't see them exposed on any pages. > > Anyway, when you say "from that moment the maiilan3 has stopped > working." (sic) exactly what stopped working. Did core stop delivering > messages? Did Postorius stop working. If so, this all may be related to > some underlying database issue or something like that that was fixed by > the restarts. I don't see how this HyperKitty error could affect > Postorius or Mailman core. When I say that it stops working, I mean that all members of the lists no longer receive messages. Postorius and Hyperkitty continue to work blackout69

4 years, 4 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 11:06 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: > On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On 2/16/21 9:59 PM, Mark Dadgar wrote: >>> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >>> >>> Error messages below. >>> >>> rebuild_index fails with the same error. >>> >>> This is with django version 3.0.12. >> >> >> django.utils.six was removed in Django 3.0. See >> <https://pypi.org/project/django-utils-six/> for a work around >> replacement. I.e. in your venv do >> >> pip install django-utils-six > > > OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. One last note on this for the next person who searches the list archives: I also ran into the “Key too long” error while re-indexing. Applying the patch linked here fixed it: https://gitlab.com/mailman/hyperkitty/-/issues/322 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 4 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: > > This is all because you are using the Ubuntu 18.04 package which is > about 4 years out of date and is from the era where HyperKitty, > Postorius and django_mailman3 still ran under Python 2.1.7. > > Unless you want to remove the Ubuntu package and install everything > with > pip, you need to just stick with what you have that at least partly > works and we'll try to determine how to fix the utf8mb4 issue. Hi Mark, You're a very patient soul. Thank you. Yes, I'm resigned to exactly that. The archives when folks send emojis will break, but that's just life. Mail will get sent. Heck, I guess I could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to get rid of the emoji in the worst case... Once I've migrated my 1500 mailing lists (this weekend) to the server, I'll think about how to get a new server set up that I can shift to and I'll install that with pip, since that'll clearly give me something more supportable. Is Ubuntu 20.04 a reasonable platform for that? Cheers, David

4 years, 4 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marcus Bautze

Hallo, Am 27.05.2024 um 14:33 schrieb Mark Sapiro: > Enabling archivers is done in mailman.cfg similarly to > ``` > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg Thank you, archiver is now starting. Now there's another problem: In mailman.log i'm finding: "Jun 06 10:16:16 2024 (3556489) ACCEPT: <d3072553-2f52-4bd7-b14a-2701863812c7@***> Jun 06 10:16:17 2024 (3556492) HyperKitty failure on https://[URL]/mailman3/hyperkitty/api/mailman/urls: <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>nginx</center> </body> </html> (403)" in mailman-hyperkitty.cfg there is: base_url: https://[URL]/mailman3/hyperkitty/api/mailman/urls an in mailman-web.py ALLOWED_HOSTS = [ #"localhost", # Archiving API from Mailman, keep it. # "lists.your-domain.org", # Add here all production URLs you may have. '*' ] MAILMAN_ARCHIVER_FROM = '*' (only for test, if it works i will use my domains/IPS) If i try lynx https://[URL]/mailman3/hyperkitty/api/mailman/urls i'm getting "The archiver key must be sent over the Authorization HTTP header." an no forbidden What's the problem? Where i have to change something to get it working? (I'm using plesk) CU -- Marcus Bautze marcus(a)mbautze.de

1 year, 1 month

[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

7 months, 2 weeks

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Shashikanth Komandoor

Dear Mark, As I already said, your suggestion worked well on one list. But when I tried to implement the same trick on another list, I found the below error messages in the mailman.log. > * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno > 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > > *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* > * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* > * f = open(self._path, 'rb+')* > *FileNotFoundError: [Errno 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > *During handling of the above exception, another exception occurred:* > *Traceback (most recent call last):* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, > in _one_iteration* > * self._process_one_file(msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, > in _process_one_file* > * keepqueued = self._dispose(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line > 37, in _dispose* > * process(mlist, msg, msgdata, pipeline)* > * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, > in process* > * handler.process(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line > 47, in process* > * with Mailbox(mailbox_path, create=True) as mbox:* > * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* > * _mboxMMDF.__init__(self, path, factory, create)* > * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* > * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such > file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > I ran in both the ways you suggested i.e. through "mailman shell" and "mailman remove". But no luck. Could you please suggest me at this point ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Sep 22, 2020 at 10:29 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > > Thank you Mark a lot. > > It worked awesome. You don't know how much you helped me. > > Thank you once again. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_8502129290396208734_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: >> > >> > But I am trying to delete a list on an urgent basis. Because of which I >> am >> > getting the above said errors. I tried to delete >> > through the interface, through curl command and through "mailman shell" >> but >> > nothing led me to a >> > positive result. Is there any work around to delete the list ? >> >> What have you tried in Mailman shell? This should do it. >> >> $ mailman shell -l list.example.com >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> The variable 'm' is the list.example.com mailing list >> >>> getUtility(IListManager).delete(m) >> >>> commit() >> >> So should just >> >> $ mailman remove list.example.com >> >> What happens if you do those? >> >> -- >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 9 months

[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.

5 years

[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)

1 year, 2 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

4 years, 5 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…

3 years, 11 months

Search results for query "sapiro"