Search results for "2021" - Mailman-users

Re: Hyperkitty download mbox

by Mark Sapiro

On 4/26/21 2:00 AM, Andrew Hodgson wrote: > > Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: > > [2021-04-26 08:53:12 +0000] [28181] [ERROR] Error handling request > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request > for item in respiter: > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox > msg = email.as_message() > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message > msg["Message-ID"] = "<%s>" % self.message_id > File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ > self._headers.append(self.policy.header_store_parse(name, val)) > File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse > raise ValueError("Header values may not contain linefeed " > ValueError: Header values may not contain linefeed or carriage return characters Thanks for the traceback. The issue appears to be with folded headers that should either be unfolded before storing in HyperKitty's database or upon retrieval for this process. This is probably because of outlook.com folding Message-ID: headers. See https://gitlab.com/mailman/mailman/-/issues/844 for one manifestation of this. I think if you replace the ``` msg["Message-ID"] = "<%s>" % self.message_id ``` line at 178 in /opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py with ``` msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') ``` it will avoid this issue. Please try it and report. > I do still have the original mbox files for the imported lists which were on Mailman 2.1. The other thing is when downloading these mbox files I noticed they aren't the raw messages as we had in Mailman 2.1 but modified with headers stripped and email addresses modified. Is there any way to get the raw mbox back as in the option we had in Mailman 2.1? Not from HyperKitty. It doesn't store the raw messages anywhere, but if you enable the prototype archiver for a list, the raw messages will be stored in maildir format in var/archives/prototype/list(a)example.com/ for each enabled list. Messages imported with hyperkitty_import won't be there, but all posts to the list, at least since enabling the prototype archiver, will be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: External Mail-Server?

by Abhilash Raj

On 9/12/21 12:21 AM, Florian Schulze wrote: > Hi! > > But LMTP is the "Local" Mail Transfer Protocol. I only have access to > IMAP, POP3 and SMTP. Outgoing seems to be simple, but what about incoming? For incoming, you'd have to have a local MTA that can receive emails over SMTP and deliver it to Mailman over LMTP. Mailman also accepts emails over HTTP API, but you'd have to have a separate application listening for incoming mails and sending it to Mailman with appropriate parameters. Mailman by itself doesn't have a way to listen for incoming emails or fetch emails from a remote mailbox. > > Regards, > Florian Schulze > > > On 11 Sep 2021, at 21:21, Jörg Michael Schulz via Mailman-users wrote: > >> Hi, >> >> yes, this should be possible. >> >> See the parameters in your mailman.cfg: >> >> [mta] >> # The class defining the interface to the incoming mail transport agent. >> incoming: mailman.mta.exim4.LMTP >> #incoming: mailman.mta.postfix.LMTP >> >> # The callable implementing delivery to the outgoing mail transport >> agent. >> # This must accept three arguments, the mailing list, the message, and >> the >> # message metadata dictionary. >> outgoing: mailman.mta.deliver.deliver >> >> smtp_host: mail.yourfavoritedomain.de >> smtp_port: 25 >> smtp_user: >> smtp_pass: >> >> Am 11.09.21 um 19:53 schrieb Florian Schulze: >>> Hi! >>> >>> Is it possible to use an external Mail-Server? Does mailman3 support >>> that directly, or would I have to setup a local MTA which somehow >>> fetches incoming mails from the external inbox and uses the external >>> Mail-Server for delivery? >>> >>> Does anyone do that and have example configurations? >>> >>> Regards, >>> Florian Schulze >>> _______________________________________________ >>> 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/ >> >> >> _______________________________________________ >> 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/ > _______________________________________________ > 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)

3 years, 9 months

Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Michael Heseltine

Thanks Philip and Steven, with your indications, I've found out that the mailman user password was listed in the settings.py files, but not in the mailman.cfg. I copied the samples from the Howto site and customized it for my local system, but did miss that config item. Now, get a proper reply (I think) from "mailman info" > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.8.10 (default, Nov 26 2021, 20:14:08) > [GCC 9.3.0] > config file: /opt/mailman/mm/mailman.cfg > db url: postgres://mailman:<REDACTED>@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:<REDACTED> and have created the necessary files under /etc/systemd/service/, but run into problems when trying to execute "/opt/mailman/mm/bin/mailman-post-update" (I've "chmod +x /opt/mailman/mm/bin/*" before that in order to be able to execute the script files): > + '[' False == False ']' > + mkdir -p /opt/mailman/mm/static > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> > sys.exit(execute_from_command_line()) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in > execute_from_command_line > utility.execute() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in > execute > django.setup() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/__init__.py", line 24, in setup > apps.populate(settings.INSTALLED_APPS) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/apps/registry.py", line 91, in populate > app_config = AppConfig.create(entry) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/apps/config.py", line 224, in create > import_module(entry) > File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1014, in _gcd_import > File "<frozen importlib._bootstrap>", line 991, in _find_and_load > File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 671, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 848, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/__init__.py", line 43, in <module> > raise ImproperlyConfigured("The HAYSTACK_CONNECTIONS setting is required.") > django.core.exceptions.ImproperlyConfigured: The HAYSTACK_CONNECTIONS setting is required. I have no idea whatsoever what this HAYSTACK_CONNECTIONS thing is, nor have I found anything in the HowTo. Can you help me any further? Cheers, Michael.

3 years, 6 months

Re: Mailman issues after re-boot

by paulrubin37＠gmail.com

Ok, I edited request.txt for -lock and -in8 and got: (venv) mailman@mail:~> mailman info GNU Mailman 3.3.8 (Tom Sawyer) Python 3.8.10 (default, May 05 2021, 15:36:36) [GCC] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:xxxxx@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@mail:~> That got me: mail:/opt # systemctl start mailman3 mail:/opt # systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2023-09-29 15:36:13 EDT; 4s ago Process: 20268 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Main PID: 20271 (python3) Tasks: 15 (limit: 4622) CPU: 16.548s CGroup: /system.slice/mailman3.service ├─20271 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg ├─20277 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─20278 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─20279 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─20280 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─20281 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 ├─20282 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─20283 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─20284 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─20285 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─20286 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─20287 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 ├─20288 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 ├─20289 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 └─20306 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg gatenews Sep 29 15:36:11 mail systemd[1]: Starting GNU Mailing List Manager... Sep 29 15:36:12 mail mailman[20268]: Starting Mailman's master runner Sep 29 15:36:12 mail mailman[20268]: Generating MTA alias maps Sep 29 15:36:12 mail systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted Sep 29 15:36:13 mail systemd[1]: Started GNU Mailing List Manager. YEAH! progress. When I tried to use mailman-web I get this error: django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE Which config file is this and what do I need to add?

1 year, 9 months

Re: External Mail-Server?

by Ruth Ivimey-Cook

On 12/09/2021 09:08, Jörg Michael Schulz via Mailman-users wrote: > Hi, > > in my humble opinion: > > re: incoming: you only need to configure the process that serves your > incoming mail to route/forward it to the LMTP port of mailman as > described in the docs, for example here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > in > > > # /etc/exim4/conf.d/transport/55_mm3_transport > mailman3_transport: > driver = smtp > protocol = lmtp > allow_localhost > hosts = localhost > port = MM3_LMTP_PORT > rcpt_include_affixes = true If you are in a position to set up Exim as the local MTA, you could use my ansible config: https://github.com/rivimey/ansible-exim4 to install it very simply. Ansible is a generic tool to configure software on hosts, and this config tries to abstract a lot of the knowledge I have gained into a very simple config. For example, this is the config I use to set up as a 'smarthost', accepting and forwarding all mail: ######################### EXIM SMARTHOST exim_server_name: "{{ hostname_fqdn }}" exim_disable_ipv6: no # TCP/IP ports on which exim should listen for mail. Keep things simple. exim_listen_ports: [ 25 ] exim_tls_ports: [] exim_local_domains: [] # These define the basic operation: here, a non-local smarthost. exim_deliver_direct: no exim_deliver_smarthost: yes exim_deliver_localuser: no # Where is the smarthost? exim_smarthost_authenticated: no exim_smarthost_address: post.ivimey.org # Pi doesn't include spamd support. exim_use_spamassassin: no exim_use_dkim: no While this is a fragment of my main mailserver config, which deals with mailman, multiple email domains, TLS, DKIM, user auth, spam detection, and delivery to dovecot: ######################### EXIM # TCP/IP ports on which exim should listen for mail exim_listen_ports: - 25 - 465 - 587 # Ports (in exim_listen_ports) that are TLS by default. exim_tls_ports: - 587 # User/password lookup on local mysql server: exim_mysql_hostname: localhost exim_mysql_database: mail exim_mysql_user: post exim_disable_ipv6: true exim_server_name: ivimey.org exim_intercommand_delay: 1s exim_auth_store_mysql: yes exim_deliver_direct: yes exim_deliver_smarthost: no exim_imap_transport: yes exim_local_parts_suffix: yes exim_use_antivirus: no exim_use_dkim: yes exim_use_spamassassin: yes # see also dovecot_dir_storage exim_virtual_homes: /opt/mail/home # Optional parts: exim_mailman_transport: v3 exim_mailman_transport_host: mailman.ivimey.org exim_mailman_transport_port: 8024 exim_mailman_root: "{{ mailman3_var_dir }}/lists" exim_procmail_transport: no For the interested, I also have an ansible config for mailman itself, though it is not necessary to use both together: https://github.com/rivimey/ansible-mailman3 Whether or not you use my configs, I would definitely recommend trying Ansible out as a good way to configure software in (a) a repeatable and sane way, and (b) to take advantage of the experience of those who have created the configs, so you don't make too many mistakes! Best regards, Ruth -- Ruth Ivimey-Cook Magazine Editor, Software Consultant Blog: http://www.ivimey.org/blog

3 years, 9 months

Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/18/21 12:30 PM, sarah.hartt(a)ionica.ca wrote: > I have been trying to get a mailman 3 installation working for longer than I'd like to admit. Core appears to be installed and working as desired but Postorius (and hyperkitty, but I haven't even started troubleshooting it while trying to get the web interface working) is only loading the main page with no lists shown and all remaining links return a server error (specific text is: "Server error > An error occurred while processing your request." with the error text highlighted). I think I followed all of the installation instructions, including the updated pythonpath line in the systemd module, but it's entirely possible that there is an error somewhere along the way. Is there more information in logs? (nginx and django) > I have had to make two minor tweaks, the /static/ location was moved from /opt/mailman/web/static to /var/www/mailman/ (owner mailman:nginx) as nginx was giving permissions errors (even if it owned the files or with the mod set to 777) with the default location and wouldn't load the css, and installed postgres directly from their repo as the method in the guide doesn't create the user. Aside from that everything should be exactly as laid out in the installation guide. The permissions is probably a SELinux or apparmor issue. Which installation guide are you following? I'm guessing https://docs.mailman3.org/en/latest/install/virtualenv.html. Are you saying that ``` sudo apt install postgresql ``` doesn't create a `postgres` user? It should. > The logs are showing everything running and the DB logs show all the queries going through successfully, there are no errors in the web logs corresponding with the errors being served on the site aside an entry for a 500 in the access logs > > [18/May/2021:12:13:01] "GET /archives/ HTTP/1.1" 500 1102 "http://mailman3/mailman3/lists/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.91 Safari/537.36" "-" This is a GET of /archives/ which is HyperKitty. Django should log something for this with more detail. > when I took a look in the DB tables many of them appear to be empty, I have a few lists in core that were imported from 2.1 but no new lists created. Empty tables per se is not necessarily a problem depending on which ones. > Mailman: 3.3.4 > Postorius: 1.3.4 > OS: Oracle Linux 8.3 > Python: 3.6 > postgres: 13.2 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 3:33 PM, Mark Dadgar wrote: >> >> Any thoughts on how to salvage ~20 years of list archives? > > > The archives shouldn't be an issue. I don't think they are involved in > the corruption, but anyway, hopefully you still have the archive mbox > you imported. Then for the messages since then, you should be able to > get a mbox from hyperkitty with something like > > https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… > > with the obvious substitutions and appropriate start and end dates. So in trying to download the recent archives ("export/trackjunkies-new.mbox.gz?start=2019-10-10&end=2020-06-28”), I end up with an 8.5MB file with one day’s worth of posts in it (2019-10-10). I see these errors in the mailman-web.log: Traceback (most recent call last): File "/usr/lib/python3.8/email/_header_value_parser.py", line 2060, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1325, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found ' <BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>>' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 332, in stream_mbox msg = email.as_message() File "/usr/lib/python3/dist-packages/hyperkitty/models/email.py", line 175, in as_message msg["Message-ID"] = "<%s>" % self.message_id File "/usr/lib/python3.8/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.8/email/policy.py", line 148, in header_store_parse return (name, self.header_factory(name, value)) File "/usr/lib/python3.8/email/headerregistry.py", line 602, in __call__ return self[name](name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 197, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.8/email/headerregistry.py", line 530, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2117, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2064, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1509, in get_obs_local_part obs_local_part[1].token_type=='dot'): IndexError: list index out of range [pid: 1359|app: 0|req: 12933/12933] 76.102.110.193 () {60 vars in 1504 bytes} [Sun Jun 28 19:52:57 2020] GET /mailman3/hyperkitty/list/trackjunkies@pdc-racing.net/export/trackjunkies-new.mbox.gz?start=2019-10-10&end=2020-06-28 => generated 5572382 bytes in 4271 msecs (HTTP/1.1 200) 5 headers in 203 bytes (377 switches on core 1) Thoughts? It would be nice to salvage the last 8 months of archives. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

Re: postfix malformed address with confirm replies

by Stephen Mats Mats

> On Feb 28, 2021, at 01:32, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Mark Sapiro writes: >> On 2/27/21 4:36 AM, Stephen J. Turnbull wrote: > >>> is legal, and I think that most servers will accept it, but RFC >>> 5321 sets a limit of 64 octets on mailboxes[1], and your >>> confirmation mailbox is 67 octets. >> >> Since the -confirm+<token> part is fixed at 49 octets, this would imply >> a limit in list names of 15 octets. Ouch! > > I'm pretty sure we would have run into this before, if there were a > lot of servers out there imposing this limit. 15 octets is pretty > darn short, there are probably quite a few list names out there longer > than that. Not to mention that the RFC itself says "you SHOULD NOT be > a jerk about this". :-) So I don't think this is a big problem in > practice, and I hope Steve can reconfigure the obstructive server to > not be so picky. > To be clear the 'obstructive server’ is mailman-core. :) [ec2-user@ip-172-31-18-xxx ~]$ telnet 172.19.199.2 8024 Trying 172.19.199.2... Connected to 172.19.199.2. Escape character is '^]'. 220 mailman-core GNU Mailman LMTP runner 2.0 LHLO ip-172-31-18-xxx.us-west-2.compute.internal 250-mailman-core 250-SIZE 33554432 250-8BITMIME 250 HELP MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> 250 OK RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu> 553 5.1.3 Error: malformed address RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55(a)mm3.aca-aws.s.uw.edu> 250 OK quit 221 Bye Didn’t really dig but my guess would be the LMTP from aiosmtpd.lmtp is actually throwing the 553. For a bit of context, of the 25,801 mailman2 lists we have here at University of Washington 5,211 have names longer than 15 characters (we don’t have any lists with multibyte characters in their names). Our longest list name is 33 characters. I didn’t dump every config to see the number of lists that subscribe_policy set to confirm or confirm and approve. But I expect it’s a small minority. steve > For Mailman, I doubt we need a full SHA1 (?) for the purpose. We can > truncate the thing, probably opportunistically (ie, so the whole > confirmation mailbox fits in 64 octets, or we could even parse the > bounce message and resend only if we run into a problem). > > Steve > _______________________________________________ > 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, 4 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 1/28/21 5:33 AM, David Partain via Mailman-users wrote: > I wrote: >> I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: >> >> DATABASES = { >> 'default': { >> 'ENGINE': 'django.db.backends.mysql', >> 'NAME': 'mailman3web', >> 'USER': 'mailman3web', >> 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', >> 'HOST': 'localhost', >> 'PORT': '', >> 'OPTIONS': { >> 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", >> 'charset': 'utf8mb4', >> }, >> } >> } >> >> and restarted stuff, but I cannot tell that it has changed anything. > > You responded: >> That should do it. I think the original message should have been saved >> as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. > > That directory has all of the messages sent to that list: > > # ls /var/lib/mailman3/archives/hyperkitty/spool/ > 1611827925.8030825+925c996b9b6020ee18e9a689ce23384855159f77.pck 1611827926.1923075+e728f3c29c1fe6eeeca641314cdba7007cb6e132.pck > 1611827925.8917305+d16b7004bdbbef98ce40fb8ee70e492715d1607d.pck 1611827926.2623458+1aac13b50d8e7f32eb14d13e6559656aa8f3bd10.pck > 1611827925.9594557+7ad2a910b5ee9142c88f0bf26c60c6df960d4262.pck 1611827926.3488555+04a540651c5f829751518433e1c54168ab63a38b.pck > 1611827926.0404096+a5e745f51a9f7d541aeb770a89604be17019f3c5.pck 1611827926.4206145+de861eec6404d0c8f9f8bdb180e29bff2de7c52b.pck > 1611827926.1167526+0aa63639a4ec102bf63522827637e75e6a2b092a.pck This is what's expected since the underlying issue isn't yet fixed. > Yes, I'm still seeing the errors. When I send mail to a list with a cute emoji, I see the following in /var/log/mailman3/web/mailman-web.log: > > ERROR 2021-01-28 10:58:45,708 16923 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > (bunch of python errors omitted) > DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column 'content' at row 1") OK. The issue is with your database it doesn't like '\xF0\x9F\x98\x8A' which is a 4-byte utf-8 encoding for a smiley face emoji. The issue is with MySQL and MariaDB which do not accept 4-byte utf-8 encodings by default. The settings you show above should be sufficient to allow 4-byte utf-8 encodings. I'm not that familiar with how the Debian/Ubuntu package sets things up. Are you sure that /etc/mailman3/mailman-web.py is the settings file used by Django, and if so does it have at the end something like ``` try: from settings_local import * except ImportError: pass ``` and if so is there something there that overrides the DATABASES setting? If all that is OK, you may need to do something like ``` ALTER DATABASE mailman3web CHARACTER SET utf8mb4; ALTER TABLE hyperkitty_email CHARACTER SET utf8mb4; ``` on the database itself. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: Confirmation emails to Users has wrong domain name (example.com!)

by Abhilash Raj

On Wed, Sep 29, 2021, at 9:50 AM, Odhiambo Washington wrote: > 1. Confirmation emails to Users has wrong domain name (example.com!) > <https://docs.mailman3.org/en/latest/faq.html#id1> > <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> > > This happens when your reverse (SSL) proxy isn’t setting up the correct > headers when proxying requests. Fix this by setting the right > proxy_set_header directives: > > # For Nginx. > location / { > proxy_set_header X-Forwarded-Proto $scheme; > proxy_set_header X-Forwarded-Host $host; > proxy_pass http://localhost:8000/; > } > > Appropriate headers for different web servers needs to be set if something > other the > > > > How is this supposed to be mitigated in Apache when using WSGI? It seems like Apache has this `ProxyPassReverse` thing, which should do the same job: https://www.nginx.com/resources/wiki/start/topics/examples/likeapache/ I haven't tried it myself, but it might help! > > My config: > > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > user=mailman group=mailman > WSGIPythonHome "/usr/local" > WSGIProcessGroup hyperkitty > > <VirtualHost *:443> > ServerName lists.doma.ain > ServerAdmin odhiambo(a)gmail.com > > SSLEngine on > SSLCipherSuite > ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL > SSLCertificateFile > "/usr/local/etc/letsencrypt/live/lists.doma.ain/cert.pem" > SSLCertificateKeyFile > "/usr/local/etc/letsencrypt/live/lists.doma.ain/privkey.pem" > SSLCertificateChainFile > "/usr/local/etc/letsencrypt/live/lists.doma.ain/chain.pem" > > CustomLog /var/log/mm3-lists-access.log combined > ErrorLog /var/log/mm3-lists-error.log > LogLevel info > > Alias /favicon.ico /usr/local/mailman/static/hyperkitty/favicon.ico > Alias /static /usr/local/mailman/static > > > <Directory "/usr/local/mailman/static"> > Order Allow,Deny > Require all granted > Allow from all > </Directory> > > WSGIScriptAlias /mailman3 /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /hyperkitty /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /postorius /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /archives /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > > <Directory "/usr/local/mailman/"> > <Files wsgi.py> > Require all granted > </Files> > WSGIProcessGroup mailman-web > </Directory> > > </VirtualHost> > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' :-) > _______________________________________________ > 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)

3 years, 9 months

Mailman-users search results for query "2021"