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

[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

[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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 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, 1 month

[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, 4 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

5 months, 2 weeks

[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

10 months, 1 week

[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

5 years, 11 months

[MM3-users] Re: How to delete large numbers of held messages

by lists＠g1fef.co.uk

Mark Sapiro wrote: > On 4/22/22 02:11, Chris via Mailman-users wrote: > > Mark Sapiro wrote: > > I suggest the following in mailman shell > > >> $ bin/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 > >> >>> from mailman.app.moderator import handle_message > >> >>> requestdb = IListRequests(m) > >> >>> for id, type in requestdb.held_requests: > >> ... if type == RequestType.held_message: > >> ... handle_message(m, id, Action.discard) > >> ... > >> >>> commit() > > > Thanks for the reply, unfortunately that gives an error: > > Traceback (most recent call last): > > File "<console>", line 1, in <module> > > TypeError: cannot unpack non-iterable _Request object > > Sorry, my mistake. > Try this: > $ bin/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 > >>> from mailman.app.moderator import handle_message > >>> requestdb = IListRequests(m) > >>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > >>> commit() Perfect - thank you Chris

3 years, 7 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, 5 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Thomas Ward

Mark, As a person fluent in MS365 they are a catchall. The MS server tends to always accept the message. It then triggers a bounce after the fact because of the multilayered transit patterns MS365 uses for handing off messages. I know this because of custom mailing alert system integrations with MS365 not triggering SMTP transfer time alerts but receiving the bounces after MS365 has received the message and hands off to its edge transports to remote clients, then later sends a DSN. (I have spent three weeks digging on this for a FT Job task so I am unfortunately damned fluent in how MS365 processes SMTP to recipients that will decline or bounce...) MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. Thomas Sent from my Galaxy -------- Original message -------- From: Mark Sapiro <mark(a)msapiro.net> Date: 9/21/23 19:36 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? On 9/21/23 15:01, Andrew Hodgson wrote: > Mark Sapiro <mark(a)msapiro.net> wrote: > >> Can you provide one of the bounce report messages and the corresponding bounce message from the MTA log. > > I only have the message I would get as the owner of the list that the delivery has been disabled, That's the one I'm interested in. If possible I'd like to see the actual raw message, not some MUAs rendering of it. > I don't have the original bounce message. One thing to note is the bounce messages coming in from Gmail are being generated by Office 365 (as that is the outbound smarthost for the Mailman server), so it may be due to the format of those NDRs why we aren't seeing the original bounce messages attached to the email. So as I understand it, Office 365 is sending the mail to the gmail recipient which is presumably rejecting the mail at SMTP with a 5xx status. Does Office 365 report the failure to Mailman with a failure status at SMTP time or later with an emailed DSN. If the former, there should be log messages in Mailman's smtp.log indicating the number of failures '$msgid post to $listname from $sender, $size bytes, $refused failures' and the reason for each '$msgid delivery to $recip failed with code $smtpcode, $smtpmsg'. Also, we create a fake DSN. See https://gitlab.com/mailman/mailman/-/blame/master/src/mailman/runners/outgo… If the latter we have the DSN from Office 365. In either case, the DSN should be attached to the notice. I don't know why it wouldn't be. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 2 months

Search results for query "sapiro"