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

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

by Flo

On 10/9/25 19:19, Mark Sapiro wrote: > On 10/9/25 5:02 AM, Flo via Mailman-users wrote: >> Hi, >> >> I added a new site in Django: lists.example.com >> >> Usually I click on 'view site' and I can add a Domain in Postorios. In >> this case I get an error message and I need to add a Domain in Django. >> Then I can go to 'view site'. >> >> I can create a mailing list there. However when I send an email to be >> subscribed, I get the following in mailman.log (and nothing else >> happens): >> >> >> Oct 09 13:46:24 2025 (110452) deque: do_confirm_verify >> Traceback (most recent call last): > ... >> File "/usr/lib/python3/dist-packages/mailman/model/domain.py", line >> 177, in __getitem__ >> raise KeyError(mail_host) >> KeyError: 'lists.example.com' > > It appears you don't have a domain in Mailman core with mail_host = > 'lists.example.com'. > > Do you see one in Postorius' domains view? If not, perhaps you need to > add it. > I can see it in Postorius. I have created the a simialar site before and deleted the site and then again created this one. Maybe the database is messed up? I have deleted site - group - list now. And created the site again. If I go to 'view site' I see all mailing lists on the server and not only from this site/domain. This is the first thing where it shows irregularities. Flo

8 months, 1 week

[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. 8., K, 4:06): > On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > > > So it's even weirder – however, I'm really not sure if this is the > address > > HyperKitty is checking for, as I have 3 attached to my account! > > How may I know which one it's trying to use? > > If you go to https://example.com/user-profile/ what Primary email and > Other emails do you see? Do you see all three? And if you go to > https://example.com/mailman3/users and click Manage for your address, do > you see all 3 under Addresses? Now I see a difference here! User-profile shows my GMail address as primary and my own-domain address as secondary. The third address is not present, because I actually wanted to get rid of it, and it seems I succeeded in that. Mailman3/users shows me with the address I wanted to get rid of. If I click Manage, I see all 3 addresses, with (for some reason) only the GMail one being verified (strange because I'm sure I verified the other as well). And here's something interesting: it shows me as a member with my GMail address under subscriptions, but shows me with my megabrutal.com domain under ownerships. This might be the cause? Maybe HyperKitty wants to use my owner identity, which is not subscribed? Btw, is the owner not automatically considered as someone who can post to the list, they also need to be subscribed?

1 year, 2 months

[MM3-users] Re: mail stuck in "out" queue

by pdw＠mythic-beasts.com

Mark Sapiro wrote: > On 12/10/24 07:44, pdw(a)mythic-beasts.com wrote: > > First check to ensure there are no files in Mailman's var/templates/ > directory that are not readable by the Mailman user. That can cause this > issue. Checked, and I've also tried removing all templates for the affected list. > > After multiple restarts trying to get some debug information, the hard loop seems to have stopped recurring, and the messages are sat in the "shunt" queue. They've not been delivered to recipients, but they are in the hyperkitty archive. > > The shunted messages should have a SHUNTING entry with an exception and > traceback in mailman.log. If there were files unreadable by Mailman in > Mailman's var/templates/ directory and you have corrected that, you can > move the shunted messages back to their original queue with mailman unshunt. I've now found the SHUNT entries and the exceptions seem related to restarting mailman (see below) so that much makes sense. unshunting does indeed restore them, but unfortunately they're now back in the looping state. Paul Shunting exception: File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 278, in _process_one_file self.switchboard.enqueue(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 122, in enqueue filebase = now + '+' + hashlib.sha1(hashfood).hexdigest() ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 117, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Dec 17 21:25:51 2024 (1039773) SHUNTING: 1734470750.961038+b6946081a6c85ed7c03d221af87b87463eaf68e1 Dec 17 21:25:51 2024 (1039773) out runner exiting.

1 year, 6 months

[MM3-users] Re: How to delete non-users

by Stephen J. Turnbull

Mark Sapiro writes: > My original point is the presence of a nonmember role should not prevent > the user from subscribing. If there is an issue with subscribing it is > probably because of the outstanding subscription request waiting > moderator approval. I don't think it is likely, but is it possible that the moderator is not just refusing the subscription, but banning the address from subscribing? > I understand that you would like the nonmember role to disappear, but > that isn't going to happen in the distribution, and I can't undertake > the extensive effort required to figure out how you can do it for your site. It seems to me that explicitly displaying the nonmember role is an internal and/or administrative need, and most ordinary users are only interested in whether they are subscribed or not. If the list appears in "their" list of list, they're going to assume they're subscribed. (We've even had that confusion about moderators and owners in the past.) I haven't done any deep thinking about this, but perhaps we could provide a more streamlined view tuned to this specific need? That is, the role won't go away, but at least in some contexts you'll have to ask explicitly for that user-list relationship to be displayed. Also, IIRC Allan's community contains a substantial group of folks with visual impairments, presumably including admins and moderators. Especially to serve that circumstance I think it makes sense for us to provide streamlined views that are more easily grasped as a whole where we can.

3 years, 9 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi Mark, thanks for correcting my assumption. Based on your information I have been able to identify the suspect message file in /var/lib/mailman3/messages, replace the suspect file with another file, update the file permissions and successfully load the held messages page. This allowed me to discard the suspect message and other held messages are then available for review again. In case the steps below help someone else who is having this issue here are the steps I followed with my initial search string redacted: Searched all files in messages folder for matching string: cd /var/lib/mailman3/messages grep -ir [REDACTED] * Finds string in one file: Binary file HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV matches Check whether file can be parsed using mailman command: mailman qfile ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Throws a matching error: [----- start pickle -----] <----- start object 1 -----> Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 97, in main args.func(args) File "/usr/lib/python3/dist-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/lib/python3.6/pprint.py", line 161, in _format rep = self._repr(object, context, level) File "/usr/lib/python3.6/pprint.py", line 393, in _repr self._depth, level) File "/usr/lib/python3.6/pprint.py", line 405, in format return _safe_repr(object, context, maxlevels, level) File "/usr/lib/python3.6/pprint.py", line 555, in _safe_repr rep = repr(object) File "/usr/lib/python3/dist-packages/mailman/email/message.py", line 45, in __repr__ return self.__str__() File "/usr/lib/python3.6/email/message.py", line 135, in __str__ return self.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) Move suspicious file out of messages: mv ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV /root/20200914/ held_messages page still throws 500 error. Checking debug log, it is now because the database references a file that is no longer there. Can I just copy a parseable file to the path of the bad file so I can delete it or do I need to remove the reference from the database? Copy some other file: cp ZZ/B2/ZZB24ADTZ2BOKBWTQWI7KG4XACGR6DTJ HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Still throws an error but this time it's a permissions error. mailman can't access the copied file: ls -l HE/D7/ -rw-r----- 1 root root 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chown list:list HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chmod g+w HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV ls -l HE/D7/ -rw-rw---- 1 list list 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV held_messages now loads OK. Cheers, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, 12 September 2020 06:17 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

5 years, 9 months

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I think I found the bug; I have posted a comment to the issue mentioned by Mark https://gitlab.com/mailman/postorius/issues/58 Regards Claus Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: > Oh well. > > Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>> >>> Seemingly, at some point in the deep dungeons of the source code the >>> "Acceptable aliases" Text-Box is not interpreted correctly. >>> >>> Specifically, at the start it contains the string >>> >>> [] >> >> >> See <https://gitlab.com/mailman/postorius/issues/58>. > > there they talk about fancy "uni-code thinks" (email addresses?) where > the task is to convert a new-line separated text-field into an array. Oops. > > Kind thanks anyway. > >> >> In order to set things on this page, you need to clear the Acceptable >> aliases box before submitting changes. You can't actually set Acceptable >> aliases via Postorius until this is fixed. > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. > > Thanks > > Claus > > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years, 9 months

[MM3-users] Re: installation

by Henry S

Thanks Mark and Brian. I'll try the suggestions. My IP might have got blocked by CBL when testing mailman3 against a Gmail address. I have since removed it from CBL. I don't know how my IP got into the Outlook's block list. Maybe a used one. Will try DKIM signing and Microsoft programs. On 23/11/2020 11:59 am, Brian Carpenter wrote: > > On 11/22/20 6:54 PM, Henry S wrote: >> >> Now I am trying to figure out how to configure mailman+postfix to >> pass the unnecessarily convoluted world of spam-free certification >> and ip blockings by those 'security lawmakers'. >> >> Any suggestions on how to not be blocked by gmail, hotmail, etc? I >> have used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an >> appropriate question to this mailman list. > > Mark Sapiro provided some very good suggestions. > > Is this a new IP address or one that has been used for mail traffic > for a white? The only way Gmail and Hotmail will block an IP address > is if you have some major outgoing spamming problems or in the case of > a new IP address, the IP address has a sordid history which will be > reveal if you do a RBL check on it. > > Gmail likes SPF records and MTA's that utilizes SSL for outbound mail. > > For Hotmail deliveries, you will want to signed up for Microsoft's > Smart Network Data Service (SNDS) program which I find very good. Also > sign up for their JMRP program for your IP address. > >

5 years, 6 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Mon, 31 Oct 2022 09:38:37 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/22 00:17, Onyeibo Oku wrote: > > > > It is not finding the logger file. The other django project on this > > machine is running fine. I can confirm that the logger plugin is > > installed. I must be missing something. > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > take note of > ``` > # Make sure that this directory is created or Django will fail on > start. LOGGING['handlers']['file']['filename'] = > '/opt/mailman/web/logs/mailmanweb.log' > ``` > ` [Reviving this thread]. I abandoned the hyperkitty setup for a while and returned to it again today. I made progress. It turns out that I needed the uwsgi-logger-file rpm package and It wasn't installed with the uwsgi server. I adapted the settings also, since I was using Emperor mode (recall that there are other Django projects on the box). Currently, mailman, uwsgi and nginx are all running. They all seem to be happy until I assess the mailman-web home URL (e.g. http://my.server.com) The outcome: "502 Bad Gateway" Nothing shows in the logs except at /var/log/nginx/error.log: 2022/12/08 15:35:10 [error] 5879#5879: *7 upstream prematurely closed connection while reading response header from upstream, client: 105.113.33.89, server: my.server.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8000/favicon.ico", host: "my.server.com", referrer: "https://my.server.com/". Something seems to be wrong between uwsgi and mailman, but I don't know where to look. Regards Onyeibo

3 years, 6 months

[MM3-users] Re: Command Emails not Working

by Brinson, Jason T

Mark, First, thank you for your patience. So, I scoured my logs looking for mentions of -join or -request emails and couldn’t find anything. So I went back and checked the source for one the emails that was in moderation and found this: Received: from esa.hc4021-78.iphmx.com (esa.hc4021-78.iphmx.com [207.54.93.77]) by cc-postoffice-01.cc.gatech.edu (Postfix) with ESMTPS id AF674400A3C for <demo-list(a)mailman.cc.gatech.edu>; Wed, 22 Apr 2026 17:27:54 -0400 (EDT) Which in the logs looked like this: Apr 22 17:28:02 cc-postoffice-01 postfix/pickup[655521]: AB3E2400ACA: uid=1028 from=<mailman> Apr 22 17:28:02 cc-postoffice-01 postfix/cleanup[676116]: AB3E2400ACA: message-id=<20260422212802.AB3E2400ACA(a)cc-postoffice-01.cc.gatech.edu> Apr 22 17:28:02 cc-postoffice-01 postfix/qmgr[523389]: AB3E2400ACA: from=<mailman(a)cc-postoffice-01.cc.gatech.edu>, size=1537, nrcpt=1 (queue active) Apr 22 17:28:02 cc-postoffice-01 postfix/local[675259]: AB3E2400ACA: to=<mailman(a)cc-postoffice-01.cc.gatech.edu>, orig_to=<mailman>, relay=local, delay=0.63, delays=0.63/0/0/0, dsn=2.0.0, status=sent (delivered to mailbox) Apr 22 17:28:02 cc-postoffice-01 postfix/qmgr[523389]: AB3E2400ACA: removed [root@cc-postoffice-01 ~]# journalctl -u postfix | grep AF674400A3C Apr 22 17:27:54 cc-postoffice-01 postfix/smtpd[677096]: AF674400A3C: client=esa.hc4021-78.iphmx.com[207.54.93.77] Apr 22 17:27:54 cc-postoffice-01 postfix/cleanup[676116]: AF674400A3C: message-id=<BN0PR07MB876638D9CD221355993FF318A02D2(a)BN0PR07MB8766.namprd07.prod.outlook.com> Apr 22 17:27:54 cc-postoffice-01 postfix/qmgr[523389]: AF674400A3C: from=<shae(a)cc.gatech.edu>, size=14593, nrcpt=1 (queue active) Apr 22 17:27:54 cc-postoffice-01 postfix/lmtp[677032]: AF674400A3C: to=<demo-list(a)mailman.cc.gatech.edu>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.3, delays=0.28/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) Apr 22 17:27:54 cc-postoffice-01 postfix/qmgr[523389]: AF674400A3C: removed But when you dig into the source of the message the actual to field is: From: "Brinson, Jason T" <shae(a)cc.gatech.edu> To: "demo-list-join(a)cc.gatech.edu" <demo-list-join(a)cc.gatech.edu> Subject: Test Thread-Topic: Test Thread-Index: AQHc0p7SggqXD6aw1U2cnq5Fx0tjdg== Date: Wed, 22 Apr 2026 21:27:52 +0000 Message-ID: <BN0PR07MB876638D9CD221355993FF318A02D2(a)BN0PR07MB8766.namprd07.prod.outlook.com> The Message-ID matches what is in the log file, and it is obviously not addressed to just demo-list. I am missing something obvious here I feel. ----------------- Jason "Shae" Brinson (They/Them) IT Support Professional Sr. Georgia Institute of Technology College of Computing 801 Atlantic Drive NW Atlanta, GA 30332 Phone: 404-894-7065 Email: jason.brinson(a)cc.gatech.edu<mailto:jason.brinson@cc.gatech.edu> From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, April 22, 2026 at 15:59 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Command Emails not Working On 4/22/26 10:23 AM, Brinson, Jason T via Mailman-users wrote: > As requested: > > Posfix log (journalctl -u | grep demo-list): > Apr 22 11:14:16 cc-postoffice-01 postfix/qmgr[523389]: E6943400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1853, nrcpt=1 (queue active) > Apr 22 11:14:48 cc-postoffice-01 postfix/lmtp[523634]: F1957400A9D: to=<demo-list+1a65bace2719a299598865b8e3bf7b78d1ec0a5f(a)mailman.cc.gatech.edu<mailto:demo-list+1a65bace2719a299598865b8e3bf7b78d1ec0a5f@mailman.cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.59, delays=0.5/0.01/0.01/0.07, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:14:50 cc-postoffice-01 postfix/qmgr[523389]: 089D0400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=20898, nrcpt=1 (queue active) > Apr 22 11:14:50 cc-postoffice-01 postfix/lmtp[523634]: 089D0400A9D: to=<demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>>, orig_to=<demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:14:50 cc-postoffice-01 postfix/qmgr[523389]: 40995400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1322, nrcpt=1 (queue active) > Apr 22 11:14:52 cc-postoffice-01 postfix/qmgr[523389]: 1063C400A9D: from=<demo-list-bounces+jbrinson3=gatech.edu(a)cc.gatech.edu<mailto:demo-list-bounces+jbrinson3=gatech.edu@cc.gatech.edu>>, size=21257, nrcpt=1 (queue active) > Apr 22 11:20:47 cc-postoffice-01 postfix/qmgr[523389]: 9D5E0400A3C: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1860, nrcpt=1 (queue active) > Apr 22 11:21:56 cc-postoffice-01 postfix/lmtp[526023]: EEB2640083E: to=<demo-list+ae434bc0e6da7e08d0b66c8abf94e259e0c5e8a1(a)mailman.cc.gatech.edu<mailto:demo-list+ae434bc0e6da7e08d0b66c8abf94e259e0c5e8a1@mailman.cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.28, delays=0.26/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:21:57 cc-postoffice-01 postfix/qmgr[523389]: C12EA40083E: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1326, nrcpt=1 (queue active) > Apr 22 11:21:57 cc-postoffice-01 postfix/qmgr[523389]: C6D87400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=24425, nrcpt=1 (queue active) > Apr 22 11:21:57 cc-postoffice-01 postfix/lmtp[526023]: C6D87400A9D: to=<demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>>, orig_to=<demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:21:59 cc-postoffice-01 postfix/qmgr[523389]: A72C940083E: from=<demo-list-bounces+jbrinson3=gatech.edu(a)cc.gatech.edu<mailto:demo-list-bounces+jbrinson3=gatech.edu@cc.gatech.edu>>, size=24784, nrcpt=1 (queue active) I don't see any messages there about mail to=<demo-list-join(a)cc.gatech.edu> or to=<demo-list-request(a)cc.gatech.edu>. Don't use journalctl. do, e.g., grep 'demo-list-(join|request)' /var/log/mail.log and then grep the queue IDs of the messages found to see all the relevant messages. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to jbrinson3(a)gatech.edu

1 month, 4 weeks

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

> Fra: Mark Sapiro [mailto:mark@msapiro.net] > Sendt: 2. oktober 2017 17:26 > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > There is no user or list admin workaround, but the defense is a fairly > simple patch. See the MR at > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > at > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > The commit changes 7 files, but only two are needed. The rests are tests > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't >necessary. > > The only changes you need are those to mailman/email/message.py and > mailman/mta/connection.py. I am using Docker-mailman (not yet very familiar Docker and version control). I would expect I have to wait for a Docker-mailman release including this change, right? I have at least five+ lists which almost haven't been working since my switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am desperate trying to figure out whether it is best to fall back to the Mailman 2 server, for the time being, where the lists came from, or it is better to wait for an update to the Docker-image. Will https://github.com/maxking/docker-mailman/milestone/2 fix my problems regarding failed mail handling and will it become available soon (when?) (https://github.com/maxking/docker-mailman/issues/147)? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

8 years, 8 months

Search results for query "sapiro"