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

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 10:51 PM, joseverde(a)gmail.com wrote: > Okay, I *think* I killed the processes. When I run > > ps -fwwA|egrep 'master|runner' > > I just get > > root 7595 1 0 Jul26 ? 00:00:04 /usr/lib/postfix/sbin/master -w > mailer 21851 21001 0 22:45 pts/1 00:00:00 grep -E --color=auto master|runner Yes, there are no mailman processes running. > As far as the permissions, you asked does your systemd script set the user to the Mailman user? I don't know how to check that, but I saw many files in /var/lib/mailman3 were owned by a user named list. Last time I tried to run mailman status, it threw a permission error on mailman.cfg, which was owned by root. I changed owner to list, and it produced a different error. So I'm guessing we are on the right path? There was no mention of a user named mailman in the system before, but maybe I need to check something. You are apparently using the Debian/Ubuntu packages. In those, the Mailman user is `list`. There is no `mailman` user. As far as what user the systemd script sets, just look at the script, but if it was installed by the Debian/Ubuntu package, it's probably OK. The script is named xxx.service where 'xxx' is the name you might use in systemctl commands (probably 'mailman3'). It should be at /etc/systemd/service/ or one of the subdirectories. > Lastly, I deleted everything in /var/lib/mailman3/locks. > > However, running mailman status now throws this permission error > > 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 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 188, in initialize > initialize_1(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 123, in initialize_1 > mailman.config.config.load(config_path) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 107, in load > self.push(filename, user_config.read()) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 113, in push > self._post_process() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 125, in _post_process > self.ensure_directories_exist() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 227, in ensure_directories_exist > with Lock(lock_file): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 203, in lock > self._write() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 417, in _write > with open(self._claimfile, 'w') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/mailman-cfg.lck|[redacted server name]|21787|3720843219351355903' > > That file was removed when you told me to clear the locks folder (I save a copy, however). So I'm stuck again. Sorry for all the questions and thanks very much for the help. Does the `list` user own /var/lib/mailman3/ and /var/lib/mailman3/locks/? Are you running `mailman` commands as user `list`? Also see <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/27/20 2:48 AM, Shashikanth Komandoor wrote: > Hi Mark, > > Thank you for your response. And sorry for not giving you > complete information as I am not sue what to share with you. > > I am using Postgresql-11.7 as my backend database. The below is > the structure of the address table in* mailman *database: > > mailman=# \d address; > Table "public.address" > Column | Type | Collation | Nullable | > Default > ----------------+-----------------------------+-----------+----------+------------------------------------- > id | integer | | not null | > nextval('address_id_seq'::regclass) > email | character varying | | | > _original | character varying | | | > display_name | character varying | | | > verified_on | timestamp without time zone | | | > registered_on | timestamp without time zone | | | > user_id | integer | | | > preferences_id | integer | | | > Indexes: > "address_pkey" PRIMARY KEY, btree (id) > "ix_address_email" UNIQUE, btree (email) > "ix_address_preferences_id" btree (preferences_id) > "ix_address_user_id" btree (user_id) > Foreign-key constraints: > "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) > Referenced by: > TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY > (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL > TABLE "autoresponserecord" CONSTRAINT > "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES > address(id) > TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY > (address_id) REFERENCES address(id) > TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" > FOREIGN KEY (address_id) REFERENCES address(id) > > The below is the structure of *user* table: > > mailman=# \d user; > Table "public.user" > Column | Type | Collation | Nullable > | Default > -----------------------+-----------------------------+-----------+----------+---------------------------------- > id | integer | | not null > | nextval('user_id_seq'::regclass) > display_name | character varying | | > | > password | character varying | | > | > _user_id | uuid | | > | > _created_on | timestamp without time zone | | > | > is_server_owner | boolean | | > | > _preferred_address_id | integer | | > | > preferences_id | integer | | > | > Indexes: > "user_pkey" PRIMARY KEY, btree (id) > "ix_user__user_id" btree (_user_id) > "ix_user_preferences_id" btree (preferences_id) > Foreign-key constraints: > "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES > address(id) ON DELETE SET NULL > "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > Referenced by: > TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN KEY > (user_id) REFERENCES "user"(id) > TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > > mailman=# \dn > List of schemas > Name | Owner > --------+---------- > public | postgres > (1 row) > > mailman=# select * from user; > user > ---------- > postgres > (1 row) > > *The above command output is not showing any fields. But if use the table > as public.user (schema.tablename) with select command, it is showing the > data. But without schema name this table is not showing those fields. Not > sure if this the expected behavior or not.* This is expected. psql gets confused because it has its own user table. The above table definitions look fine. Is there any entry in the `address` table for which `id` is not an integer? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 11:56 AM, David Newman wrote: > > I created a pending subscription request on a test list. Here is the > text I'm using in a file called 'list:admin:action:subscribe.txt' (minus > the rows of hypens): > > ---------- > > > As list administrator, your authorization is required for a mailing list > subscription request approval: > > For: $member > List: $listname > > At your convenience, visit: > > https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ This looks like a Mailman 2.1 URL. Are you sure you don't want something like https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > to approve or deny the request. > > ---------- > > Instead the message that goes out at midnight daily reads like this: That's a different message. It is sent from the `mailman notify` command run by cron. It's built from the list:admin:notice:pending template. > > On successive nights I have placed copies of the > 'list:admin:action:subscribe.txt' file above in these locations: > > mm/var/templates/lists/test.lists.domain.tld/en I hope you mean /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en > /opt/mailman/mm/var/templates/site/en Either of those should work. The lists one will take priority over the site one for that list. > and then in Postorius, with the same contents as above. If you set a template in Postorius, it takes priority. If you later decide you want to use one in /opt/mailman/mm/var/templates/ you have to delete the postorius one. > The file > versions are owned by the mailman user, and have 0644 permissions. Not > sure this is necessary but I've restarted the mailman3 and mailmanweb > services each time after a change. > > There is no sign of trouble in the MM3 or web logs. The only thing I see > is in the Postfix log, where the shorter and less helpful message goes > out each night. I don't see anything in the template docs about this. > > Questions: > > 1. What to do to get the custom message working? It should work. I suspect you need to go to the list's Settings -> Automatic Responses and set `Admin immed notify` to Yes. > 2. Is there a way to trigger a subscribe reminder for one list only? If by subscribe reminder you mean the `list:admin:action:subscribe.txt` message, yes that's the above list setting. If you mean the one sent from the `mailman notify` command, see `mailman notify --help` for the options. You can specify one or more lists (default is all lists) via options and put them in your cron. > Asking because there are other lists on this server with other requests > pending, and I don't want to bother other moderators with multiple > reminders per day. Not a big deal, but it would be nice to test this > with one list rather than waiting up to 24 hours after each change. You can test `mailman notify` at any time by running it by hand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

Yes, I have django_mailman3/templatetags/d_gravatar.py in my installation. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:11 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org > <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- 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/

4 years

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Tue, Dec 24, 2024 at 8:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> I saw that too. Reported > >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > > > > It isn't clear to me what I should do to mitigate the error. > > > Apply this patch: > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - dn = address.display_name or member.user.display_name > + # Non-members may have empty address.display_name and > member.user can > + # be None resulting in AttributeError on member.user.display_name. > + try: > + dn = address.display_name or member.user.display_name > + except AttributeError: > + dn = '' > if email_only or not dn: > print(address.original_email, file=outfp) > else: > ``` > Thank you. Now only if you can help me reconcile the fact that Postorius tells me that I have ``` List Nonmembers (872) ``` ..while the CLI command gives me only 13 addresses. -- 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]

10 months, 1 week

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

Got it. Is there a command that one can manually run to test/expedite the process? ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, July 28, 2025 12:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/28/25 7:07 AM, willie.castillo(a)caemilusa.com wrote: > Looks like "hyperkitty" stopped archiving right after the CERT for the mailman3 website expired, How can I make the missing archives visible on the website? I see there "*pck" files in the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The list archive does not show that last posting [of 25 July 2025. > > ~$ ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 98215 Jul 25 12:01 1753459289.7901242+f3fd7ee77272862f8c1023394bf88d0d4bbe9053.pck > -rw-rw---- 1 mailman mailman 98109 Jul 25 12:01 1753459289.7726512+ee1264c36a194eb0ec1a52089f053e6963f24369.pck > -rw-rw---- 1 mailman mailman 88479 Jul 25 12:01 1753459289.7564857+2e27f35a57f757f058dc95e34c56722a76307900.pck > > The CERT on the website is now up-to-date Those queued messages will be reprocessed on the next post. -- 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://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

3 months

[MM3-users] Re: Mailman 3 Installation

by Mark Sapiro

On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: > I am trying to set up Mailman 3 on a new server. So far I have run: > > pip3 install Django==3.1.5 This will be a minor issue. django-mailman3 requires Django>=2.0,<3.2; HyperKitty requires Django>=2.2,<3.2, but postorius requires Django>=1.11,<3.1. We really should be more consistent with these requirements, but what this means is > pip3 install postorius will install Django 3.0.11 alongside Django 3.1.5. > pip3 install Hyperkitty > pip3 install mailman > pip3 install uwsgi > > All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. > > I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? You can use sqlite, but if you don't already have a mysql/mariadb database on the server, we recommend postgresql for performance and robustness. I personally have had issues with mysql and use postgresql on one production server that uses mysql for other applications. > I think I can follow the instructions to set up postfix. > > In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. There should be a 'mailman' user that is the user under which you run things. Don't run things as root. sudo chown -R mailman:mailman /srv/mailman For settings.py and some others, see <https://gitlab.com/mailman/mailman-suite/-/tree/master/mailman-suite_project>. The end of settings.py imports from settings_local so you put your local overrides in settings_local.py in the same directory as settings.py > Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. Postorius and HyperKitty. See settings.py. These files, settings.py and settings_local.py need to be in a directory that also includes an empty __init__.py so python can import from it and this directory needs to be in the path that Django runs with. This is a shell script I use to run django. It uses a virtualenv, but that isn't necessary. Also my stuff is in /opt/mailman/mm/, but it could just as well be /srv/mailman. #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ > I would appreciate advice or a pointer to where I can figure this out. Thanks. There is a work in progress you may find more helpful. See <https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/55#note_48712…> and the 'Rendered documentation' linked therefrom. You might also find <https://wiki.list.org/x/17891998> and/or the docs linked from its first paragraph to be helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I want to use Mailman to send emails to our customers. I´m getting this error when I click on sign up and log in: FilterError at /accounts/login/ /bin/sh: sassc: command not found Request Method: GET Request URL: http://192.168.1.42:8000/accounts/login/?next=/postorius/lists/ Django Version: 1.11.3 Exception Type: FilterError Exception Value: /bin/sh: sassc: command not found Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py in input, line 196 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 What's missing??? El vie., 21 jul. 2017 a las 19:57, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:57 PM, Rafael Mora wrote: > > Should Sign Up ?? Log In?? > > > Yes. > > > > El vie., 21 jul. 2017 a las 18:56, Rafael Mora (< > rafael.mora.guti(a)gmail.com>) > > escribió: > > > >> Nice! Up and running! > >> > >> How do I start using mailman? what are the steps?? > > > What do you want to do with Mailman? This is the key question. > > There is some list subscriber documentation at > <http://docs.list.org/en/latest/userguide.html>. > > You can create domains and lists via Postorius or via the core's > bin/mailman commands ('bin/mailman --help' for a list). > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by William Oliver

On Tue, 2021-12-28 at 20:05 -0800, Mark Sapiro wrote: > On 12/28/21 5:58 PM, William Oliver wrote: > > On Tue, 2021-12-28 at 17:50 -0800, Mark Sapiro wrote: > > > The recommended uwsgi.ini includes > > > > > > pythonpath = /etc/mailman3/ > > > > > > according to > > > https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… > > > > > > this should work. Did you have that? If you did and it doesn't > > > work, > > > perhaps adding > > > > > > env = PYTHONPATH=/etc/mailman3 > > > > > > > Yes, I had the first, and does not work. The second entry works. > > > I updated the doc to use > > env = PYTHONPATH=/etc/mailman3 > > I don't know enough about uwsgi to know for sure, but the issue may > be > that setting pythonpath in a running python process doesn't work - > it's > too late as the path is already set in python's initialization. > You might add that it may be necessary to do it in .bashrc for linux folk -- I got it to work but as I've demonstrated, I can sometimes make mistakes and leave detritus around. I may not have successfully cleared my previous setting. That being said, I think it works. I am, I am afraid not a details-oriented guy, which is a bit of a drawback for someone doing system admin...

3 years, 10 months

[MM3-users] Re: 'str' object has no attribute 'token_type'

by Mark Sapiro

On 11/15/21 6:06 AM, Marco Marinello wrote: > Hi everybody, > > I'm sorry for being always the strange guy with strange errors here but for some reason... I am. > On a Mailman installation that was doing just fine for more than a year, I started receiving error messages per email. It happens when mailman daemon archives a messages. Although the messages is correctly archived, this exception is thrown by Hyperkitty: > > > Traceback (most recent call last): > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/exception.py", line 47, in inner > response = get_response(request) > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/http.py", line 40, in inner > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 118, in _decorator > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view > return view_func(*args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 164, in archive > add_to_list(mlist_fqdn, msg) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/lib/incoming.py", line 79, in add_to_list > from_str = header_to_unicode(message['From']) > File "/usr/lib/python3.9/email/message.py", line 391, in __getitem__ > the values matching a header field name. > File "/usr/lib/python3.9/email/message.py", line 471, in get > for k, v in self._headers: > File "/usr/lib/python3.9/email/policy.py", line 163, in header_fetch_parse > return self.header_factory(name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 601, in __call__ > return self[name](name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 196, in __new__ > cls.parse(value, kwds) > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in parse > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in <listcomp> > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/_header_value_parser.py", line 462, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 393, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 574, in display_name > if res[-1][-1].token_type == 'cfws': > > Exception Type: AttributeError at /hyperkitty/api/mailman/archive > Exception Value: 'str' object has no attribute 'token_type' > Request information: > USER: AnonymousUser > > > I upgraded both to Debian 11 (from 10) and to latest versions of Hyperkitty, mailman-hyperkitty and mailman but still getting the error. Other installations with same specs I'm managing to do not encounter this problem. > Any clue of what could have happened, why and how to fix it? The exception is thrown in the Python email package on HyperKitty's attempt to get the From: header of the message. This looks like https://bugs.python.org/issue43501 and/or https://bugs.python.org/issue30988. These issues refer to display names beginning or ending with a dot. Is that the case with the From: header of the problem messages? Note that display names containing dot should be quoted. It appears that at least one of the people posting posts with the problem From: header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Search results for query "sapiro"