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

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: I wound up taking a different approach. I check for other references to the message in the message store and only delete the message if there are none. The fix is at https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs> Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 6 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Abhilash Raj

On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: > On 9/18/19 3:32 AM, Henrik Rasmussen wrote: > > I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)). > > > > It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why. > > > > I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom. > > > I know nothing about Docker containers and how they communicate with > each other, but Postfix is trying to deliver mail via lmtp to > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > listening on port 8024. Either that is not the case or that port is not > exposed to Postfix on IP 172.19.199.2. Right, that is what I was wondering, you verify that by using telnet on the specified IP and Port (172.19.199.2:8024). `docker-compose ps` lists all the running containers, do you see all the containers running? You mentioned that Mailman is not receiving enough emails, do you get *any* emails from Mailman? I am trying to see if this is a perf problem or if Mailman's LMTP isn't reachable at all. > > -- > 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, Abhilash Raj (maxking)

6 years, 8 months

[MM3-users] Re: Weekend releases

by Abhilash Raj

On Tue, Dec 10, 2019, at 8:27 AM, Mark Sapiro wrote: > On 12/10/19 2:58 AM, Paul Arenson wrote: > > Thank you. The setup I am using now has Hyperkitty 1.3.0 and I just wanted to confirm. Somewhere I thought I read there is a facility in the Hyperkitty archive interface to format text. Probably I misunderstood, but if there is such a facility, I am not seeing it. Maybe I am looking for something like Tiny Ice and thus can't find it. > > > Markdown rendering of message bodies in Hyperkitty is > <https://gitlab.com/mailman/hyperkitty/merge_requests/160>. This is > installed on <https://lists.mailman3.org/mailman3/> and > <https://mail.python.org/mailman3> but is not yet released. > To add more, if you look at the merge request, there are some pieces missing before it can be merged. Especially, a mechanism to opt-out on a per-list basis from this. While markdown is pretty nice to look at when you are dealing with certain mailing lists which communicates in plain text, it can be horrible to look at if the users aren't aware about markdown and/or the special markdown syntax. In practice, there is only so much we can do to render a random email as HTML using markdown syntax. Maybe I can get to it this holiday season and it can go out for interested folks in the next Hyperkitty release :) > -- > 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, Abhilash Raj (maxking)

6 years, 5 months

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Odhiambo Washington

On Thu, Dec 29, 2022 at 2:54 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 12:22, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 22:00, Odhiambo Washington wrote: > >>> I worke up to 959 such entries in my mailmanweb.log: > >>> > >>> ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The > >>> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > >> ... > >>> > >>> What might have been the cause of this? > >>> > >> > >> Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= > >> 1.3.5 requires mailman-hyperkitty>=1.2.0. > > > Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a > different message so that isn't it. > > There is an issue with Apache. If you search the archives of this list > for the log message you'd find it, but see the last two posts in the > thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > But why these messages all of a sudden? Did you just change something? > I found a mismatch! MAILMAN_ARCHIVER_KEY != api_key A single quote character had sneaked in while copying the key over to the next file. I will watch what happens when the archiver is run next and whether I really need the ' WSGIPassAuthorization On'. Thank you very much as always. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 months

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

by Abhilash Raj

On Thu, Oct 26, 2017, at 06:39 PM, Mark Sapiro wrote: > On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > > > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. > > > This usually means that postfic is trying to deliver to an address and > the message already has a Delivered-To: header with that address. > > What are the headers of the "looping" message in the report? What are > the Postfix log messages related to that message? > > > > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > > > https://github.com/maxking/docker-mailman > > > I have essentially no knowledge of the docker container images, so I > can't be much help with issues specific to them. The Postfix integration in container images is basically just using regex instead of hash maps and everything else is same. I do remember atleast one other person facing a similar issue where Postfix wouldn't accept listname+token@domain addresses with our regex. I am thinking this is the same issue. > > -- > 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/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 7 months

[MM3-users] Re: Deleting default "example.com" domain breaks everything

by Abhilash Raj

On Fri, Jul 16, 2021, at 12:12 PM, Mark Sapiro wrote: > On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > > Hello. I'm new with v3 of mailman. > > Installed via aptitude on deb10. > > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > > I then deleted example.com, and everything broke. > > The only site I had was still using example.com. > > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? > > > Try setting `SITE = 0` in your Django settings file. If that doesn't > work, try successively 1, 2, etc. One of these should work. Usually, example.com is always 1 and then it increases sequentially. So, if this is the first one you created, I'd try using 2. > > Also going back to your prior thread, you had > > > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser > > Aside from the python/python3 issue, you should run any Mailman and > Django management commands as the Mailman user (probably `list` in your > case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 > and https://gitlab.com/mailman/mailman/-/issues/776. > > > -- > 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, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

On 6/26/25 11:37, Hirayama, Pat wrote: > > When I look at the domains in mailman-core, I see: > >>>> show_domains() > <Domain fhcrc.org> > <Domain fredhutch.org> > <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> > <Domain lists.hanc.info, , alias: > > - owner: cit-sys-engineering(a)fredhutch.org This is part of the problem. The alias domain for a list should not be a real domain. Apparently, someone set this up so that mail to lists in the lists.fhcrc.org domain would go to the corresponding list in the lists.fredhutch.org domain. I think that may actually work, but you need more. In order to add recipients to the patest-bounces addresses, the recipient domains need to have an alias domain. In the cases below the domains lists.fredhutch.org and lists.hanc.info. E.g set an alias domain for lists.fredhutch.org to x.lists.fredhutch.org and for lists.hanc.info to x.lists.hanc.info. Then postfix_vmap will contain entries like > pattest(a)lists.fhcrc.org pattest(a)lists.fredhutch.org > pattest-bounces(a)lists.fhcrc.org pattest-bounces(a)lists.fredhutch.org > pattest-confirm(a)lists.fhcrc.org pattest-confirm(a)lists.fredhutch.org > pattest-join(a)lists.fhcrc.org pattest-join(a)lists.fredhutch.org > pattest-leave(a)lists.fhcrc.org pattest-leave(a)lists.fredhutch.org > pattest-owner(a)lists.fhcrc.org pattest-owner(a)lists.fredhutch.org > pattest-request(a)lists.fhcrc.org pattest-request(a)lists.fredhutch.org > pattest-subscribe(a)lists.fhcrc.org pattest-subscribe(a)lists.fredhutch.org > pattest-unsubscribe(a)lists.fhcrc.org pattest-unsubscribe@lists.fredhutch.orgpattest@lists.fredhutch.org > > pattest(a)lists.fredhutch.org pattest(a)x.lists.fredhutch.org > pattest-bounces(a)lists.fredhutch.org pattest-bounces(a)x.lists.fredhutch.org > pattest-confirm(a)lists.fredhutch.org pattest-confirm(a)x.lists.fredhutch.org > pattest-join(a)lists.fredhutch.org pattest-join(a)x.lists.fredhutch.org > pattest-leave(a)lists.fredhutch.org pattest-leave(a)x.lists.fredhutch.org > pattest-owner(a)lists.fredhutch.org pattest-owner(a)x.lists.fredhutch.org > pattest-request(a)lists.fredhutch.org pattest-request(a)x.lists.fredhutch.org > pattest-subscribe(a)lists.fredhutch.org pattest-subscribe(a)x.lists.fredhutch.org > pattest-unsubscribe(a)lists.fredhutch.org pattest-unsubscribe@x.lists.fredhutch.orgpattest@lists.fredhutch.org > > phtest(a)lists.hanc.info pattest(a)x.lists.hanc.info > phtest-bounces(a)lists.hanc.info pattest-bounces(a)x.lists.hanc.info > phtest-confirm(a)lists.hanc.info pattest-confirm(a)x.lists.hanc.info > phtest-join(a)lists.hanc.info pattest-join(a)x.lists.hanc.info > phtest-leave(a)lists.hanc.info pattest-leave(a)x.lists.hanc.info > phtest-owner(a)lists.hanc.info pattest-owner(a)x.lists.hanc.info > phtest-request(a)lists.hanc.info pattest-request(a)x.lists.hanc.info > phtest-subscribe(a)lists.hanc.info pattest-subscribe(a)x.lists.hanc.info > phtest-unsubscribe(a)lists.hanc.info pattest-unsubscribe@x.lists.hanc.infopattest@lists.hanc.info And I think postfix_lmtp will contain entries like > pattest(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-bounces(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-confirm(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-join(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-leave(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-owner(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-request(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-subscribe(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-unsubscribe(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > > phtest(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-bounces(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-confirm(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-join(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-leave(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-owner(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-request(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-subscribe(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-unsubscribe(a)x.lists.hanc.info lmtp:[mailman-core]:24 In any case you will then be able to add the additional recipient to the phtest-bounces(a)lists.hanc.info entry in postfix_vmap. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

[MM3-users] Re: Moderation action "None" is misleading

by Markus Grandpré

Dear Mr Sapiro, dear Mr Turnbull, thank you very much for your reply. For clarification I like to change: > What versions of Mailman and Postorius are you using? * mailman3, v3.3.8-2~deb12u2 * mailman3-web, v0+20200530-2.1 * python3-django-mailman3, v1.3.9-1 * python3-django-postorius, v1.3.8-3 * python3-mailman-hyperkitty, v1.2.1-1 * python3-mailmanclient, v3.3.5-1 with Debian GNU/Linux 12 (bookworm). So the newest changes: > This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in > Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ > merge_requests/811 are not yet available on our system. Hopefully we won't have to wait too long with Debian as there is already a lot of confusion among some of our many list administrators as we only started using Mailman3 for production a few days ago. Best Markus Am 04.02.25 um 19:25 schrieb Mark Sapiro: > On 2/4/25 02:51, Markus Grandpré wrote: >> Dear List, >> >> I find the use of the term 'None' (or 'Kein' in the German >> translation; see attachments) in the 'Moderation action' column of the >> member list misleading, as the term suggests that no moderation action >> is applied to the respective member. >> >> However, this is not necessarily the case. If you check a member’s >> "Administration options / Moderation" setting, a moderation action, >> such as "Moderation" or "List default", may be in effect. > > This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in > Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ > merge_requests/811 > > See the UI changes at https://docs.mailman3.org/projects/postorius/en/ > latest/news.html#news-1-3-9 > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 3 months

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/27/19 6:54 AM, brunol(a)agro.uba.ar wrote: >> What do you mean by constantly appearing? Do you mean endlessly > repeating or that they just repeat a number of times equal to the number > of expected recipients of the post? > > Sorry, I meant endlessly repeating. > > This is a piece from debug after sending an email to the list from a recipient that does not need moderation: > > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de264a8> > Dec 27 11:41:10 2019 (11468) [BounceRunner] starting oneloop > Dec 27 11:41:10 2019 (11468) [BounceRunner] ending oneloop: 0 > Dec 27 11:41:10 2019 (11473) Cannot connect to SMTP server 127.0.0.1 on port 25 This message is logged only once, but the issue occurs every time. deliver is getting a socket.error exception on its attempt to connect to the MTA. Thus, sending of this message fails and the message is requeued and the process repeats. Is an MTA listening on 127.0.0.1 on port 25? The only question is if we can't send this mail, how can we send the 'held for moderation' notices?. These are sent the same way. > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.0510046+6fe6039c1b0b65672aade3bfced1aca2fe8afa16 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26e10> > Dec 27 11:41:10 2019 (11470) [IncomingRunner] starting oneloop > Dec 27 11:41:10 2019 (11470) [IncomingRunner] ending oneloop: 0 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26f28> > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.6512213+13fe7854257bb1a494f797f480cb10733bd440ac > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3dd44390> > Dec 27 11:41:10 2019 (11469) [CommandRunner] starting oneloop > Dec 27 11:41:10 2019 (11469) [CommandRunner] ending oneloop: 0 > > This is endlessly repeating with different filebase > _______________________________________________ > 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/ > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Key Error when clicking on a list

by Mark Sapiro

On 6/19/20 9:02 AM, Jacob Bargery wrote: > I looked back and tried to see if this is related to the Filter_Vhost = true error. In the email log I received at the bottom where it lists settings I am seeing Filter_Vhost = false. So I am guessing it is not related I could be wrong though. > > I can see lists populated that have been created, but when I click to open them it immediately goes to page titled "Server Error" and reading "An error occurred while processing your request.". This is part of the email, I can include the rest with settings if that will help. > > > Internal Server Error: /mailman3/postorius/lists/testlist.groups.smccme.edu/ > > KeyError at /postorius/lists/testlist.groups.smccme.edu/ > 'file' As has been mentioned many times on this list, the KeyError at ... 'file' exception is not the issue. It is a result of Django encountering this issue in trying to log the real exception. > Request Method: GET > Request URL: http://groups.smccme.edu/mailman3/postorius/lists/testlist.groups.smccme.ed… You are trying to get the list view for the testlist.groups.smccme.edu list ant that causes: > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view > 71. return self.dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/generic.py" in dispatch > 65. return super(MailingListView, self).dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch > 97. return handler(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/list.py" in get > 252. 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 The above appears to be where the issue arises. The full code bit here is > if ('hyperkitty' in settings.INSTALLED_APPS and # noqa: W504 > 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 > self.mailing_list.archivers['hyperkitty']): > data['hyperkitty_enabled'] = True The condition `'hyperkitty' in self.mailing_list.archivers` is causing Postorius to try to get the archivers associated with this list, and that's where the 500 occurs. > File "/usr/lib/python3.8/_collections_abc.py" in __contains__ > 666. self[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __getitem__ > 151. return self._get(key) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in _get > 90. return self.rest_data[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data > 76. response, content = self._connection.call(self._url) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) this 500 return from Mailman core: > During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: This "another exception occurred" is irrelevant. For more information on exactly what caused the 500 from core, you have to look in var/logs/mailman.log. There is presumably something wrong with that list's archivers configuration. This shouldn't happen, but without the error and traceback information from mailman.log, we don't know what the problem is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Search results for query "sapiro"