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

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 2:05): > On 4/6/25 16:00, MegaBrutal via Mailman-users wrote: > > I get a composition dialog and can type my message, but when I click > send, > > I get the error message: „This list is moderated, please subscribe to it > > before posting.”. Upon reply, a red rectangle appears to enclose this > > message. Upon trying to create a new thread, a white page loads which > only > > contains this error message. > > In that composition dialog below the text box, it should say > ``` > This message will be sent as: user(a)example.com Link another address > If you aren't a current list member, sending this message will subscribe > you. > ``` > > No, it doesn't say anything like that. It says if I'm not subscribed, sending the message would subscribe me – no address is shown there at all. > > What do you see in Django's logs when you do this? > >> > > > > I don't know where to look – I don't see anything outstanding, only a few > > HTTP requests appear in mailman.log on mailman side and uwsgi.log on web > > side. None of these indicate any error. > > > If you configured your settings.py per > > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > your Django log which is where HyperKitty logs is at > /opt/mailman/web/logs/mailmanweb.log. However, I don't think there will > be anything useful there. Yeah, I checked that, nothing useful.

1 year, 5 months

[MM3-users] Re: MM3 not starting afte an upgrade -addendum

by Gelpi Andrea

the last problem was due to the VHOST parameter. I had to remove it to hace postorius run. Is anything changed since two month aggo when I applied some pathces? Thanks and regards -- AG Il 24/07/20 10:13, Gelpi Andrea ha scritto: > > > Il 23/07/20 23:05, Mark Sapiro ha scritto: >> On 7/23/20 4:35 AM, Gelpi Andrea wrote: >>> Hi, >>> to day in a Debian system I upgraded some packages. >>> >>> After the MM3 doesn't start anymore. > > . . . > >>> Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0) >>> Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1] >>> Operation not permitted >> >> >> I think you have a stale lock issue and the master is trying to >> determine if the process that set it still exists. >> >> Remove Mailman's var/locks/master.lck* >> > > Thanks Mark, now MM3 star but postorius is not working. > > The web pagge return: An error occurred while processing your request. > > I receive an email with: > ... > Exception Type: KeyError at /postorius/lists/ > Exception Value: 'file' > Request information: > USER: AnonymousUser > > GET: No GET data > > POST: No POST data > > FILES: No FILES data > > COOKIES: No cookie data > > Is that related to Django id setting or there is a passphrase mismach > some where? > > How can I check? > > > -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

6 years, 1 month

[MM3-users] Re: configuring postfix local recipient table

by Odhiambo Washington

On Wed, Apr 30, 2025 at 2:55 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users(a)mailman3.org> wrote: > Splitting up answer: > > Am 29.04.25 um 18:27 schrieb Mark Sapiro: > > Also, is there anything in Mailman's logs from the time you ran `mailman > > aliases`? > > Nothing in logs (before or) after command ''mailman aliases'' > and debug level everywhere is: info. > > What logs? > Everything under /opt/mailman/mm/var/logs: > > + bounce.log > + debug.log > + mailman.log > + plugins.log > + smtp.log > > All empty. > ^^^^^^^^^^^ mailman.log should never be empty. At the least, it will contain some entries about task runners, like: ``` [30/Apr/2025:14:00:01 +0300] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 477 "-" "GNU Mailman REST client v3.3.5" Apr 30 14:18:22 2025 (54456) Task runner evicted 0 expired pendings Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned workflows Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned requests Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned messages Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned message files Apr 30 14:18:22 2025 (54456) Task runner evicted 0 expired bounce events Apr 30 14:18:22 2025 (54456) Task runner evicted expired cache entries [30/Apr/2025:15:00:02 +0300] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 477 "-" "GNU Mailman REST client v3.3.5" ``` If those aren't there, then your installation has more problems than you think, IMHO. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 22:51:46 -0500, Mark Sapiro wrote: > > On 3/13/21 7:08 PM, John Covici wrote: > > On Sat, 13 Mar 2021 16:22:59 -0500, > > Abhilash Raj wrote: > >> > >> My guess is that you updated the database (perhaps, by invoking the mailman > >> command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > >> up and sees a new revision for the database migration added from 3.3.3 but > >> can’t find the same migration in its source (because it is 3.3.2). > > > > That is sort of what happened, except in the opposite direction, it > > was from 3.3.3 to 3.3.2. My question is therefore, do I have to > > update this alembic_version when I upgrade mailman to a newer version? > > That is what I was getting at. > > > Abhilash's conjecture is that the error was due to a Mailman version > accessing a database that had been previously accessed by a newer > version so that the version_num in the alembic_version table didn't > exist in mailman/database/alembic/versions/. This normally would not > occur on an upgrade of Mailman, but if you went from a gentoo Mailman > core to a version obtained by pip, it's possible that the gentoo Mailman > had an alembic version that wasn't known to the pip Mailman even though > the pip Mailman was newer. > OK, thanks. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 6 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 15:42, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>>> >>>> The server runs power-mailinabox, which uses Postfix indeed. All my >>>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>>> on port 465. Actually, this message is sent via that server too. >>>> So it's clear to me that MM3 is not authenticating for some reason. >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log The /etc/mailman3/mailman3-web.py file contains inter alia these lines: # Set default domain for email addresses. EMAILNAME = 'fast.za.net' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root@{}'.format(EMAILNAME) fast.za.net was giesler.za.net before, so I changed it.

2 years, 1 month

[MM3-users] Re: urls.py location on venv install

by Torsten

Am 2026-08-11 21:30, schrieb Mark Sapiro: > On 8/10/26 07:15, Torsten wrote: >> >> mailman throws this one: >> >> 2026-08-10 16:11:20 [FALCON] [ERROR] GET >> /3.1/lists?advertised=true&count=0&page=1 => Traceback (most recent >> call last): >> File >> "/opt/mailman/venv/lib/python3.13/site-packages/falcon/app.py", line >> 476, in __call__ >> process_resource(req, resp, resource, params) >> ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File >> "/opt/mailman/venv/lib/python3.13/site-packages/mailman/rest/wsgiapp.py", >> line 65, in process_resource >> raise HTTPUnauthorized( >> ~~~~~~~~~~~~~~~~^ >> '401 Unauthorized', >> ^^^^^^^^^^^^^^^^^^^ >> 'REST API authorization failed', >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> challenges=[realm]) >> ^^^^^^^^^^^^^^^^^^^ >> TypeError: HTTPUnauthorized.__init__() takes 1 positional argument but >> 3 positional arguments (and 1 keyword-only argument) were given > > > This is from a Mailman core version < 3.3.10. It was fixed for Mailman > >= 3.3.10 by <https://gitlab.com/mailman/mailman/-/merge_requests/1267>. > > It appears that you don't have the latest Mailman core. > The question then would by why pip did not install mailman core 3.3.10 but 3.3.9 >> and mailman-web this one: > > Which is a result of the one above. > >> >> I have taken the old database from the Debian configuration and moved >> it to /opt/mailman... where it should belong (I hope). > > The database(s) should be in the location(s) pointed to by the > [databases] section of mailman.cfg and the DATABASES attribute in > settings.py. In an installation per > https://docs.mailman3.org/en/latest/install/virtualenv.html these are > postgresql databases accessed via the postgresql server. My installation is rather small, therefore I am using SQLite here.

1 month

[MM3-users] Re: MM3 shunting mails

by Barry Warsaw

On Mar 17, 2017, at 11:22 AM, Mark Sapiro wrote: >The above is the last line of > > exists = store.query(ListArchiver).filter( > ListArchiver.mailing_list == mailing_list, > ListArchiver.name == archiver_name).one_or_none() > >which is querying the archivers enabled for this list for the name of a >system enabled archiver and expects to find at most one entry > >> File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", >> line 2733, in one_or_none >> "Multiple rows were found for one_or_none()") > >but finds more than one. > >> sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for >> one_or_none() >> Mar 17 11:54:11 2017 (6217) SHUNTING: >> 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 > >So the cause is there appear to be multiple database entries for this >list and some archiver name, but I don't know how that can happen. I don't know either, especially since ListArchiverSet.__init__() has this: # Add any system enabled archivers which aren't already associated # with the mailing list. for archiver_name in system_archivers: exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() if exists is None: store.add(ListArchiver(mailing_list, archiver_name, system_archivers[archiver_name])) It runs the exact same query, and only adds the archiver to the store if it doesn't already exist. What does the following give you? % mailman shell Welcome to the GNU Mailman shell >>> # You may have to use getUtility(...).get() to find the offending list >>> m = list(getUtility(IListManager).mailing_lists)[0] >>> m <mailing list "ant(a)example.com" at 0x7face8b2da20> >>> from mailman.model.mailinglist import ListArchiver >>> q = config.db.store.query(ListArchiver).filter( ... ListArchiver.mailing_list == m) >>> list(a.name for a in q) ['mhonarc', 'prototype', 'mail-archive'] Cheers, -Barry

9 years, 5 months

[MM3-users] Re: # comment allowed in a template file?

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > If you mean can you add a '#' line that won't be part of the actual > rendered template, the answer is No. OK, thanks for the clarification. > > Initially, I created the template files with owner set to "root". This resulted in > > postings to lists getting stuck in mailman-core. It's vital that these files are owned > > by user "mailman". Once I changed the owner of the file to the latter, everything > > worked. > I don't think they need to be owned by 'mailman' as long as they are > readable by 'mailman' Yes, your formulation is a more accurate statement than mine (I could have instead simply relaxed the permissions on the files to make them world-readable). The effect of the template files not being readable by user "mailman" was interesting. Hundreds of lines like the following got written to mailman-core's var/log/smtp.log file at the rate of 4 per second: Jul 23 17:09:54 2020 (25) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fdf9e7b5f28> (the hex number was different each time). Having excessively restrictive permissions on the template files is a silly - but easy enough - mistake to make. If it were possible to add it to Mailman 3, a more descriptive logging message could point others who make it in the right direction, perhaps. I spent a long time trying to figure out why messages weren't getting sent out from Mailman core, and in the end it was luck in form of a colleague's suggestion about file permissions that got me out of the rut. Thanks for the great support, Stephen Kenny

6 years, 1 month

[MM3-users] Re: Change the default value for the General Archive Policy

by Markus Grandpré

Dear Mr Hochstein, Thank you very much for providing the link. I'm afraid the same misunderstanding as with Marc Sapiro has occurred here. I'm aware that there are three different styles to choose from when creating a mailing list. However, the setting "Settings > Archiving > Archive policy" can be configured independently of the list creation process. Still, it would be beneficial if the default value after creating a list without an archive were not "Public archive", but rather "Do not archive this list". This would help prevent list administrators from being tempted to immediately enable a public archive when setting up an archive later—especially in cases where the list is intended to be private. Kind regards, Markus Grandpré Am 6/23/25 um 22:48 schrieb Thomas Hochstein: > Markus Grandpré wrote: > >> currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public archives". >> I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? > > Perhaps > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > has some pointers how to accomplish that? > > -thh > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

1 year, 2 months

[MM3-users] Re: Mailman not able to process "big" requests

by Jonas Felber

Thank you for your support, I got informed that we are now able to send out emails again. The problem was that the crashes we got while mass subscribing led to database corruptions. (From what I know, the problem was on our side, as we kubernetes did not properly restore some files after restarting so the database got corrupted (apparently we are running now a cleanup script on each restart)) There are still some problems, but I just wanted to send out a quick update. Thanks for your support, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch > On 24 Apr 2018, at 17:21, Darren Smith <silas.crutherton(a)gmail.com> wrote: > > Our installation at https://lists.rootsweb.ancestry.com has around 33,000 > lists and somewhere around 1.5 million members. We have lists with 5,000+ > members. > > Note that I haven't tried any mass subscriptions. When we upgraded from > mailman 2 to mailman 3, we used the old .pck files and ran the import on > each of the lists. It did take about 6 weeks to do the full import all > 33,000 lists. I'm not joking. > > As for sending messages - there isn't any problem sending that many > messages out, but then we are also not trying to subscribe list members at > the time. We are, though, in the process of importing the old archives from > our old mailman 2 system. This doesn't seem to affect the rest of the > system. > > We have seen some inefficiencies in the new system, such as the front page > of postorius - loading all of the information for 200 lists (if the user > set the "lists per page" to 200) was bringing down the system. We have our > own metadata system to be able to search for lists by state/region/surname > (ours is a genealogy mailing list system), so we had to replace the front > page with our own "find a list" functionality. > > The other main problem was the page where a user can see what lists they > subscribe to. That page was also a denial of service if the user had > several hundred lists they are subscribed to. And for a genealogy mailing > list system, this is common. > > We have actually ended up creating our own API layer (only accessible on > the local machine) and make certain calls to it for the most painful of the > issues. One of these days (when we get a moment to breathe) we are going to > post some of our changes to the project so that we can ditch our own API > and just use the internal REST API. > > To be fair, the inefficiencies are not necessarily with mailman or the rest > API itself - but with Postorius making hundreds of calls to load a single > page. Though if the API supported loading multiple lists at once instead of > having to load them serially, that might help as well. > > So while we have not seen any timeout issues on the call to mass subscribe > users, we HAVE found several other calls that are effectively a denial of > service and have gotten around them ourselves, with plans to contribute to > the project in the near future. > > -Darren > > >> On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 04/24/2018 12:36 AM, Abhilash Raj wrote: >>> On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> >>>> We also have a problem with sending out emails to "large" (>50) groups, >>>> as they seem to not getting sent out at all. Do you have any idea what >>>> the problem here could be? >>> >>> Which MTA are you using? What do you see in mailman's logs and MTA's >> logs? >>> >>> I haven't seen this kind of problem before with Mailman 3. This very >> list is hosted using Mailman 3 and I believe has more than 50 subscribers. >> >> >> Nor have I seen this issue. This list currently has 158 non-digest >> members. There are several @python.org Mailman 3 lists with over 100 >> non-digest members including the active yt-users(a)python.org list with >> 301 members, and I have gotten no reports of an issue like this. >> >> Also, there are over 600 lists at <https://lists.fedoraproject.org/>, >> and I don't think this is an issue there either. >> >> -- >> 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 >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 4 months

Search results for query "sapiro"