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

[MM3-users] Re: Template's encoding setup

by Mark Sapiro

On 9/15/19 3:33 AM, Ugnius S wrote: > > This noticed only on HTML text messages. If message comes in HTML the > header does not add extra <enter> new line, new paragraph > and footer as well. For example if message body has no additional, list's > decorated message looks next: > > TEST HEADER > _____________________Hello, > > text text text, pictures, text > > regards > Ugnius____________________ > TEST FOOTER > > I have tried to add more empty lines in "The footer for a regular > (non-digest) message.", but mailman removes these empty lines. > Work around is put dot "." and then several empty lines. The stripping of leading whitespace from templates created in Postorius is <https://gitlab.com/mailman/postorius/issues/301> to be fixed by <https://gitlab.com/mailman/postorius/merge_requests/434> > Mark, I have found Your post about HTML headers and footers: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > YES, that works good, I have tested it, but only in cases if message comes > in HTML. If sender sends plain text message, > mailman adds footer with all HTML code: > > <BR>__________________<BR> > <B> LIST NAME </B> > > Could it be possible that decorate.py would recognise message and if it > has HTML text body, then just would add header/footer and if not (if > message body is plain text) , then would strip header/footer "html to plain > text" may removing html code from it? As it says in the post you reference: message and digest footers and headers are always added either to a MIME text/plain message body or as separate MIME text/plain parts. HTML tags will just be displayed as plain text and will not be rendered as HTML. Also see <https://wiki.list.org/x/4030707>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/2/22 16:17, dancab(a)caltech.edu wrote: > Mark, please correct if I'm wrong but is the log data below produced by LMTP via Mailman core? Yes, indirectly. Mailman's LMTP runner which receives messages form the MTA via LMTP uses aiosmtpd.controller.Controller and aiosmtpd.lmtp.LMTP classes to create the actual LMTP server and it is those classes that write those log messages. > This is from the Mailman smtp.log file. Could this somehow be an issue with how we've configured Mailman for LMTP? > > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) >> b'LHLO aeedf7ad9f48.caltech.edu' > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) >> b'MAIL FROM:<snap_wl-bounces+mailman=caltech.edu(a)caltech.edu> SIZE=4289' > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) sender: snap_wl-bounces+mailman=caltech.edu(a)caltech.edu > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) >> b'RCPT TO:<mailman(a)lists.caltech.edu>' > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) recip: mailman(a)lists.caltech.edu > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) >> b'DATA' > Feb 01 21:36:45 2022 (289) ('127.0.0.1', 36132) >> b'QUIT' These are normal messages. They are also normally followed by two additional messages like Jan 30 22:04:10 2022 (1329492) ('127.0.0.1', 34924) connection lost Jan 30 22:04:10 2022 (1329492) ('127.0.0.1', 34924) Connection lost during _handle_client() These are also normal and not a concern. Are you thinking there is an issue because of the presence of these messages or the content. The messages are normal. If you're concerned about the content, it appears there is a `mailman(a)caltech.edu` list and a `snap_wl(a)caltech.edu` list and the `snap_wl` list is sending something to the `mailman` list. This also seems OK and not at all relevant to the original issue in this thread. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: How to disable global templates for all lists

by Mark Sapiro

On 3/13/24 16:28, christopher.claus(a)tgcamberg1848.de wrote: > Hallo togeher, > > I´m using the docker version from maxking and mailman core-version 3.3.9. I was wondering why there were messages in the list with "non-configured" footers. I found the files >> > mailman-core:/opt/mailman# find / -name "*list:member:*" > /usr/lib/python3.11/site-packages/mailman/templates/de/list:member:generic:footer.txt > /usr/lib/python3.11/site-packages/mailman/templates/de/list:member:digest:masthead.txt > /usr/lib/python3.11/site-packages/mailman/templates/ca/list:member:generic:footer.txt > /usr/lib/python3.11/site-packages/mailman/templates/ca/list:member:digest:masthead.txt > /usr/lib/python3.11/site-packages/mailman/templates/nl/list:member:generic:footer.txt > > but I found no option to disable them. How can I disable these global list-configuration? First, those are only a few. The default English templates are templates/en/list:member:digest:masthead.txt templates/en/list:member:generic:footer.txt templates/en/list:member:digest:header.txt templates/en/list:member:regular:header.txt and there are translations of them in many more than the de, ca and nl languages. The default English list:member:digest:header.txt and list:member:regular:header.txt are empty so most languages do not translate them. You can't disable them other than removing them, but you don't want to do that as these are only used as fall back in cases where there is no list, domain or site specific template. If you have messages delivered that use one of the default templates, it's because you don't have a custom template that matches the context for that message. When a template is required, first the template table in the database is searched for a template matching the list, domain or site context. If no match is found, the file system is searched as described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Hyperkitty_import.py Error

by Mark Sapiro

On 2/7/21 10:03 AM, Brian Carpenter wrote: > I am trying to import some old archives (going back to 2003) into a > Mailman 3 list. The import job is terminating very early in the process > with the following error: > > IndexError: string index out of range > > 1. Is there a way to fix a mbox file that is generating this type of error? Yes, but you need to understand what message is causing the error and why. The full traceback from the error can help. So can the script at <https://www.msapiro.net/scripts/check_hk_import>. > 2. If a message is causing this error, is there a way to import the rest > of the mbox file by importing messages after a certain date within the > mbox file? I know the --since flag should be able to do that but I am > unsure what the date/time format should be. There are things you can do. The --since date syntax is very flexible. It uses dateutil.parser.parse. See <https://dateutil.readthedocs.io/en/stable/parser.html#module-dateutil.parser> You can also just make a new mbox which deletes the messages up to and including the offending one or just delete/fix the offending message. hyperkitty_import won't re-import message that are already in the archive, and without a --since option won't import messages older than the newest in the existing archive. > 3. The --no-sync--mailman flag indicates the possibility of doing batch > imports. What are batch imports and how do you do them? Batch imports means running hyperkitty_import multiple times wiuth multiple mbox inputs (batches). It is only necessary to run the sync_mailman job once after all the imports are done (even if importing to multiple lists). I.e. specify --no-sync--mailman on all but the last import, or on all and then run sync_mailman after done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Installing MM3 requires Django<1.11

by Mark Sapiro

On 04/12/2017 02:22 AM, Henrik Rasmussen wrote: > Two questions regarding Mailman 3 installation: > > 1) > The Mail server setup at http://docs.mailman3.org/en/latest/devsetup.html#set-up-a-mail-server isn't described yet. Instead it refers to https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends, but it doesn't say which file I have to change. That link doesn't belong there. Mailman doesn't use Django to send mail. > According to https://www.webforefront.com/django/setupdjangoemail.html the file is called settings.py, but the only settings.py I can find at this stage is the /opt/mailman/postorius/example_project/settings.py file. > > According to http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-postorius, "Postorius and HyperKitty both come with example_project directories with basic configuration so you can try them out. For this tutorial, however, we'll be using a project that combines both instead.". > > In what file should I change the mail settings then? Nothing in <https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends> or <https://www.webforefront.com/django/setupdjangoemail.html> is relevant to Mailman. A more appropriate discussion is at <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> > 2) > While installing Hyperkitty*) I got the error message "Django 1.11rc1 is installed but Django<1.11 is required by {'django-haystack'}". > > As I have slavishly followed the installation guide including http://docs.mailman3.org/en/latest/devsetup.html#set-up-django-mailman3, I wonder why a non-supported Django version was installed. > > *) http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-hyperkitty This is an issue. The various setup.py files for django-mailman3, hyperkitty and postorius all have Django>=1.8 as a requirement. Only postorius also has Django<1.11. django-mailman3 and hyperkitty should have that restriction too. I have submitted <https://gitlab.com/mailman/django-mailman3/issues/4> and <https://gitlab.com/mailman/hyperkitty/issues/128> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 18:53, Bryan Fields wrote: > On 7/26/24 4:01 PM, Mark Sapiro wrote: > >> If this returns just the one message_id, I would then >> >> DELETE FROM hyperkitty_thread WHERE id = 35670; >> DELETE FROM hyperkitty_email WHERE id = 150555; > > It's giving an error due to a fk constraint on another table. I'm not > familiar with the db structure enough to be certain how to clean/fix it. Yes, you need to do these first. DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; DELETE FROM hyperkitty_vote WHERE email_id = 150555; Not all those will exist, but then you should be able to DELETE FROM hyperkitty_thread WHERE id = 35670; DELETE FROM hyperkitty_email WHERE id = 150555; > I'm actually thinking I need to fix the archive mbox, then delete them and > re-import them once they are cleaned. Actually, that would be safest. Fix the mbox, delete the entire archive and re-run the import. >> Also, FYI, assuming those messages with very old Date: headers had >> reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script >> would fix them, except you have to get the script from >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… >> or https://www.msapiro.net/scripts/cleanarch3 because the script in the >> latest release has a bug. > > I tried the dry run option on your script and it gave a bunch of output > for bad > dates. This was absent on the one shipping with the source. What's > interesting > is that pipermail seems to have no issue with this, detecting the date > correctly. If I recall correctly, pipermail checks date skew and 'fixes' the dates in the archive, but they remain off in the mbox. > https://mailman.nanog.org/pipermail/nanog/2000-January/137630.html > One other thing, I did notice a number of archives not showing up in > sequence > due to missing "In-Reply-To:" headers from the source. The first > message in > this is one like this, and pipermail in mmm2 seems to handle this by > referencing > the subject, > https://mailman.nanog.org/pipermail/nanog/2002-April/151325.html, > where as in hyperkitty it's an orphaned thread. Yes, HyperKitty does not do threading by subject matching. It only threads based on In-Reply-To: and absent In-Reply-To:, only the last entry in References: if any. > Is the archive tool in pipermail's import more robust in this manner? > I'd argue > it's common to have missing In-Reply-To: headers where the subject and time > would need to be used to infer the likely thread. I'll agree this is a > major > violation of the relevant RFC's to be missing this, but many MUA's (M$) are > famous for doing just this. Yes, it's arguably a defect in HyperKitty to not implement Jamie Zawinski's threading algorithm <https://www.jwz.org/doc/threading.html>, but it doesn't. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/5/21 10:19 AM, Duane Raymond wrote: > fairsayforum.com = mail site domain (working fine for lists, archives and web) > > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > always_add_missing_headers = yes > append_dot_mydomain = no > biff = no > compatibility_level = 2 > default_destination_concurrency_limit = 15 > default_destination_recipient_limit = 30 > delay_warning_time = 1h > header_checks = regexp:/etc/postfix/header_checks > inet_interfaces = all > inet_protocols = all > local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > mailbox_size_limit = 0 > milter_default_action = accept > milter_protocol = 2 > mydestination = $myhostname, mail.fairsayforum.com, localhost.fairsayforum.com, localhost > myhostname = mail.fairsayforum.com > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > myorigin = /etc/mailname > non_smtpd_milters = inet:localhost:8892 > owner_request_special = no > readme_directory = no > recipient_delimiter = + > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > relayhost = > smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache > smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) > smtpd_milters = inet:localhost:8892 > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem > smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key > smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache > smtpd_use_tls = yes > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > unknown_local_recipient_reject_code = 550 And previously > > <test(a)oldlist.com> (expanded from <test(a)emaillistA.com>): host > oldlisthost.com[ip] said: 550 5.1.1 > <test(a)oldlist.com>: Recipient address rejected: User unknown in > virtual alias table (in reply to RCPT TO command) > > But I can't find oldlist.com in the configuration settings. It was set as an alias for emaillistA.com domain, but was removed. Have you removed the alias domain from the emaillistA.com domain and similarly for the others and then regenerated the maps with `mailman aliases` or `mailman start -g`after removing the alias domains. Also, I'm confused about "User unknown in virtual alias table" since there are no virtual_alias_domains in your Postfix main.cf. Have you reloaded Postfix since updating main.cf? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 1/2/22 4:34 AM, horvath.arpad.szfvar(a)gmail.com wrote: >> Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a >> response from Django REST framework which is a json representation of >> your mailing lists info? > > In this list I have just one list that I created for testing. And I can't see there the two lists I've imported from mailman2, e.g. korus. I guess because of admin is not a list list member there. I can see the korus at https://lists.xxx.hu/hyperkitty/ , but not at https://lists.xxx.hu/postorius/lists/ . when you view https://lists.xxx.hu/postorius/lists/ is there a Filter by Role dropdown at the top of the listing? If so, if you select `All` do you then see the lists. Postorius by default shows only those lists in which you have a role. If you still don't see the lists, what does the command `mailman lists` show? > I guess the setting below is not good. > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Should I set it to > ('https://lists.xxx.hu/hyperkitty', '::1') ? Doesn't seem to work, like that. It needs to be an IP. Set it to `('xxx.xxx.xxx.xxx', '127.0.0.1', '::1')` where xxx.xxx.xxx.xxx is the IP of lists.xxx.hu or just `('xxx.xxx.xxx.xxx',)` would probably work. > And what about MAILMAN_REST_API_URL? > How can I found its proper value? It's currently the default value > but if I try to reach it with > wget http://localhost:8001 > I get a 404. not found. How can I find the right value? If Postorius works, It's good. `wget http://localhost:8001` returns a 404 as it should because this is a REST API and `/` is not a known endpoint. Something like `wget --user restadmin --password restpass http://localhost:8001/3.1/lists` should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 9:10 AM, eboltz(a)lhtservices.com wrote: > Mark, > > Here is my postconf -n > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > always_add_missing_headers = yes > append_dot_mydomain = no > biff = no > compatibility_level = 2 > default_destination_concurrency_limit = 15 > default_destination_recipient_limit = 30 > header_checks = regexp:/etc/postfix/header_checks > header_size_limit = 409600 > inet_interfaces = all > inet_protocols = ipv4 > local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp > mailbox_size_limit = 0 > mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain > myhostname = lists.example.com > mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 > myorigin = /etc/mailname > readme_directory = no > recipient_delimiter = + > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > relayhost = [mail.smtp2go.com]:587 > smtp_always_send_ehlo = yes > smtp_sasl_security_options = noanonymous > smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem > smtp_tls_security_level = may > smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache > smtp_use_tls = yes > smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem > smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key > smtpd_tls_security_level = may > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > unknown_local_recipient_reject_code = 550 > virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap It looks like you are now following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. > What would I have to do to ensure that MM3 and postfix (same new server) use the newly created lists.example.org domain, which only exists within Postfix when setting up the Postorius domain and lists? > I want to have it so that whatever the list name is, for example 'Staff(a)lists.example.org' will route through Postfix correctly. Have you set an alias_domain for the lists.example.org domain? What are the contents of /var/lib/mailman3/data/postfix_vmap and /var/lib/mailman3/data/postfix_lmtp? If you feel it is necessary to anonymize the domains in these, please only change the tld so we can see the actual subdomains. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Mark Sapiro

On 6/26/23 8:09 PM, Allan Hansen wrote: > Hi all, > > One of my subscribers is trying to send a message to a list, but it is not being posted. > The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not: > > mailman@list:~/logs$ grep herName smtp.log > Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=40109' > Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName(a)hotmail.com > Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA(a)CH3PR12MB8259.namprd12.prod.outlook.com> post to theList(a)domain.tlc from herName(a)hotmail.com, 40061 bytes > Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18343' > Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName(a)hotmail.com > Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=19123' > Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName(a)hotmail.com > Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18930' > Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName(a)hotmail.com > > At the second retry she copied me and I saw nothing untowards in her message. > She's not getting any error return messages and her subscription is OK. > Both messages were multipart/alternative and both contained Hebrew text. > > I told her I'd look at this, but I'm at a loss. smtp.log is not very useful for diagnosing things like this. It only says a message was received, not why it didn't result in a post from the list as in the first case. What's in mailman.log with those timestamps? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

Sadly, no cron output emails. On 6/13/2023 1:53 PM, Mark Sapiro wrote: > On 6/13/23 10:46, Mark Sapiro wrote: >> >> If there is nothing in Mailman's mailman.log, I don't know what the >> issue is unless the list's digest_send_periodic flag is False. > > One more thought. Output from these cron jobs written to stdout and/or > stderr will be emailed. You can control to where with a `MAILTO=...` > line in the crontab. Otherwise, they will be mailed to the owner of the > crontab, probably `list` or maybe `root`. Check your MTA logs from > 23:00+ to see if any emails are sent and to where. > -- Joel Lord

1 year, 11 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Mark Sapiro

On 12/12/19 12:42 AM, Marvin Gülker wrote: > > But I now have a different problem. I've removed all offending messages > (it were more than just one that caused the UnicodeEncodeError), but I > still can't access the page for the held messages queue. It gives an > error 500, now with a different exception in the log. I've included it > below. It looks to me that the messages haven't properly been deleted. They have, but I apologize - more is required. > What I did was this: for each offending message hash > > 1. I ran the DELETE query > 2. I deleted the file from the file system > 3. I ran the delete_message() function > > I originally wanted to run only the delete_message() function, but a > quick check on the DB and the file system after running it for one hash > told me that it neither deletes the message from the DB nor from the > file system. The argument for delete_message() is not the hash, it is the <message-id> including the angle brackets. So I did everything at once. I do have a backup of both the > DB and the filesystem from before I started this, in case this broke > something. > > Is there something left that I have to do now? Yes, my bad for not realizing this. There are still references to these messages in the _request table. The columns in that table are id | key | request_type | data_hash | mailing_list_id key is the <message-id> of the request message request_type is 1 for a held message mailing_list_id is a numeric index into the mailinglist table The issue is there are still held message requests there for the messages you removed. You need to delete those entries from the _request table. -- 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: getting all registered users and their lists

by Mark Sapiro

On 1/26/22 00:16, IOhannes m zmoelnig wrote: > > hi, > > TL;DR > is there a scriptable way to get all users that have registered in my > mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? It's in Postorius >= 1.3.6 > longer version: > > we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that > this is not the newest version; at this point, please refrain from > asking me to upgrade my Debian installation or even to switch to a venv > installation of mailman3: i'll eventually do that but right now i've gt > a problem to solve :-)) See above. ... > for this i would like to get a listing of all users that are not > subscribed to any mailinglist. > i would also like to query, when a given user has signed up (so i can > reduce the number of false positives) > > how would i do that? > ideally i would rather not work on an SQL level. You can do this in mailman shell ``` $ bin/mailman shell 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. >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` Or to skip older ones ``` >>> from datetime import datetime >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... if usr.created_on < datetime(2022, 1, 1): ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Programmatic Creation of Users

by Mark Sapiro

On 7/30/22 05:25, jciesla(a)techsupportme.com wrote: > > After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Almost correct. A User does have preferences but does not have roles. Roles are associated with list memberships, not users. > Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. The simple view is that Django users and Mailman Users are unrelated. Either can exist without the other. They only tie together if they have the same email address. That is the only connection between them. > If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? See the script at https://www.msapiro.net/scripts/clean_users.py. This is an example that deals with Django users and Mailman Users and deletes some Django users. See https://docs.djangoproject.com/en/4.0/topics/db/queries/#creating-objects for information about creating objects. Also see the UserManager class in django/contrib/auth/models.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: The paradox of VERP probe messages

by Mark Sapiro

On 1/28/25 13:04, Jeremy Stanley wrote: > tl;dr: Is there a way to have VERP probe messages not include copies > of the bounce message that triggered them? Currently you'd need to patch code. This would do it. ``` --- a/src/mailman/model/bounce.py +++ b/src/mailman/model/bounce.py @@ -231,7 +231,7 @@ class BounceProcessor: # Try to get the dsn from the message store. It should be there. msg = getUtility(IMessageStore).get_message_by_id(event.message_id) if as_boolean(config.mta.verp_probes): - send_probe(member, msg=msg, message_id=event.message_id) + send_probe(member, message_id=event.message_id) action = 'sending probe' else: # Bounce score is reset by sending a probe but needs to be ``` You could submit an issue at https://gitlab.com/mailman/mailman/-/issues/new to make this configurable. ... > This behavior raises a more significant concern as well. The MTA on > the Mailman server in this case (Exim if it matters) wants to > perform batch deliveries when there are multiple subscribers who all > share the same remote MTAs. If multiples of those reject a list > post, then the NDR back to Mailman aggregates those multiple > rejections into a single message. If that incident triggers a VERP > probe, the bulk NDR enumerating the addresses of all the subscribers > who were rejected gets forwarded along as part of the VERP probe, > disclosing a potentially sensitive litany of random subscriber > addresses to other subscribers within that batch. I don't know > whether this is a misconfiguration, or an unintended consequence of > the intersection of Mailman and MTA features. I'm sure you can configure Exim to not do that. For Postfix it's ``` smtp_destination_recipient_limit = 1 ``` Also if you configure Mailman to VERP all deliveries ``` [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 ``` each recipient will be sent separately with a different envelope sender so the MTA can't combine them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: The Use of Hyperkitty as a Forum and Archiver

by Mark Sapiro

On 7/14/20 6:51 AM, Brian Carpenter wrote: > Dear Mailman 3 Users, > > Since Mailman 3 includes a forum feature via Hyperkitty, I would like to > know the following: > > - Has the forum feature (Hyperkitty) of MM3 been received well by your > list members or is it mostly ignored? > > - Do you see an increase in the use of HK as a forum from your list > members? For this list, I don't know other than myself, and for myself I receive the list and read it by email. I will occasionally reply from HyperKitty if I have reson to reply to a post that I have deleted from my mail server. For mail.python.org, there are multiple list members (including Guido) on multiple lists who use HyperKitty exclusively in lieu of mail. For my bicycling club lists, very few users use HyperKitty for anything and most didn't use pipermail either even though we had htdig integration. Those few that do use it probably use it primarily for search. > - What kind of feedback have you received from your list members > considering the forum function of MM3? Positive or negative? They find warts, in part due to the still developmental markdown rendering <https://gitlab.com/mailman/hyperkitty/-/merge_requests/160> that's installed there and on this list too, but overall those that use it, like it and prefer the forum model to the email list model. > - Do you think HK is received well by your list members as an archiver > and do you think it provides a better user experience for > viewing/searching archives vs Pipermail of MM2? Yes and Yes. > Thank you for anything you shared. I am very curious to know the state > of Hyperkitty among the Mailman 3 user community. > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 13:26, Christian via Mailman-users wrote: > I am only having issues with the new list. > > > > Below are logfile entries > > > > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client() This is the post being delivered to mailman and is expected. > > > Access.log Irrelevant. > Mailman.log > > ++++++++ > > Mar 09 20:57:09 2023 (9400) ACCEPT: <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> > > Mar 09 13:03:42 2023 (9397) HyperKitty archived message <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternat… These are the expected messages (there seems to be a time zone difference) and in the absence of any other error type messages say the message should have been delivered to the eligible recipients. Are there any? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… or the results from ``` mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org ``` > mailmansuite.log not relevant. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Mark Sapiro

On 3/24/22 01:11, Stanisław Findeisen via Mailman-users wrote: > Hi > > I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: > > client.create_domain(name) > > Is this a bug? Or did I mess something up? > What significance do those SITE_IDs have? The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of the table entry. See `sites` in the Django admin UI. So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` > What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... FILTER_VHOST = True is imperfect. Lists have no Web Host attribute, only a Mail Host. Thus, with FILTER_VHOST = True, we get the Mail Host from the domains that have a Web Host matching the host in the http request. If that results in only one Mail Host, we limit the display to only those lists with that Mail Host, but otherwise we don't limit by domain. In other words, FILTER_VHOST = True only works if each Mail Host domain has a unique Web Host. If you have multiple Mail Host domains with the same Web Host (SITE_ID), FILTER_VHOST won't work for that Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok I'll take a look at it Thanks El mar., 25 jul. 2017 a las 16:14, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:43 PM, Rafael Mora wrote: > > Ok, should I install the SASL authentication daemon saslauthd and start > it? > > > Probably not. > > If you are trying to configure Postfix to send via a remote server, see > <http://www.postfix.org/SOHO_README.html#client_sasl_enable>. > > -- > 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

7 years, 10 months

[MM3-users] Re: Receiving 8bit-clean mail

by Mark Sapiro

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. This is handled fine by my MTA and MUA, but Mailman > seems to have trouble with it. When mail is sent out from Mailman, the > « character is replaced by ??. > > Is this a bug, or is there just a configuration option or something I > need to set? I couldn't find anything in the documentation. It works for me. I created this message > From: Mark <mark(a)example.net> > To: test(a)example.net > Date: Thu, 17 Oct 2019 22:02:04 +0000 > Message-ID: <87wod39gkj.fsf(a)alyssa.is> > MIME-Version: 1.0 > Subject: [MM3-users] Receiving 8bit-clean mail > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further 8bit / base64 / > etc. encoding. This is handled fine by my MTA and MUA, but Mailman > seems to have trouble with it. When mail is sent out from Mailman, the > « character is replaced by ??. > > Is this a bug, or is there just a configuration option or something I > need to set? I couldn't find anything in the documentation. > and posted it to a test list. The message was delivered and archived. The delivered message had the list footer added and was base64 encoded, but in both the delivered and archived message, the « character was intact. In what other ways does Mailman modify the message. Does it add a msg_header and/or msg_footer, if so, are they added to a simple text/plain message body or is the message more complex so they are added as separate mime parts. Does content filtering remove anything? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/17/20 11:24 AM, Mohsen Masoudfar wrote: > [mta] ... > configuration: python:mailman.config.postfix What's in this configuration file (mailman/config/postfix.cfg)? ... > in main.cf: > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > transport_maps = hash:/opt/mailman/var/data/postfix_lmtp > virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap > > Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess. This leads me to think that your mailman/config/postfix.cfg contains transport_file_type: regex in which case all of the Mailman mappings defined in main.cf should be regexp: tables rather than hash: tables. If you had transport_file_type: hash The .db files would be generated/updated whenever the corresponding text files are generated/updated. > I restarted the whole stack and added a new list. In postfix logs I see: > Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Where are you even referencing that? Did you forget relay_domains = hash:/path-to-mailman/var/data/postfix_domains in the above list? ... > In addition, I found out this : > > On my old mailman2 I have a setting in postfix main.cf: > alias_maps = dbm:/usr/local/mailman/data/aliases > > the file /usr/local/mailman/data/aliases says in its first line: > # This file is generated by Mailman, and is kept in sync with the > # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE > > This makes a lot of sense to me. > > The point is I am missing any similar settings on postfix on mailman3. Mailman 2.1's data/aliases and data/virtual-mailman files have been replaced by the data/postfix* files in Mailman 3. I think your whole issue is you've configured Postfix with hash: tables but Mailman is generating regexp: tables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Disable user registration

by Mark Sapiro

On 3/20/21 1:22 PM, mailman3(a)digicrime.com wrote: > I believe that your patch was for the web front end, but that would still allow people to join by sending email to listname-join(a)example.com. We wouldn't be running any web interface anyway. I wanted to disable all methods of users joining and only rely upon an administrative process to handle who joins. It's easy to imagine a corporate use case for this, such as "all people with offices in building 43" or "all employees with dependents on health insurance" where the definition of who is on a list is maintained in an external system. We're not actually a corporation - we're a professional society with different member classes in our membership database. In any case, the decision of who belongs on a list is not made by the user. I understand these scenarios, but unless there is a high volume of spurious subscriptions, can't this be handled by setting the subscription police to include moderator approval? > In the interim I discovered another problem with DMARC failures in gmail when mail is sent through mailman3. Mail sent directly from our exim instance doesn't have this problem, so perhaps it's a problem with SRS. I won't be investigating this further, but I'm sure that SPF hard fails will be causing more problems for mailing lists in the future. SPF always fails DMARC alignment on forwarded mail, whether from a mailing list or other forwarding mechanism because even though SPF may pass, the domain is that of the forwarding server, not the original sender. While it is possible for a domain to set a DMARC policy and to rely only on SPF for validation, any domain with a DMARC policy should also be DKIM signing the mail because DKIM signatures will survive simple forwarding such as via .forward files or MTA aliases. -- 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

[MM3-users] Re: MM3 templates

by Mark Sapiro

On 2/15/23 23:04, Odhiambo Washington wrote: > > The last time I referred to the link, I deliberately duplicated the <LC> > folder in two locations: > [09:51 ~ ]$ ls -al /opt/mailman/mm/var/templates/site/en/ > total 48 > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:53 .. > -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt > -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt > -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt > -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt > -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt > -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt > -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt > -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt > -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt > -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > > Yet, it is NOT being picked. So definitely something is wrong somewhere. If you have the same list:* file in both /opt/mailman/mm/var/templates/site/en/ and /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ the ones in the lists directory will take precedence for that list over the ones in the site directory. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… for a discussion of the search order. >> >> Are the other templates such as list:member:regular:footer.txt used? >> > > I do see that in posts to the list, but I believe that is perhaps only > working because the list had that footer when it was imported from MM2. A template from import21 of the kictanet(a)lists.kictanet.or.ke list will be stored in the /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: how to administrate mailman3 in CLI ?

by Mark Sapiro

On 9/23/23 07:40, testeur via Mailman-users wrote: > > |# mailman shell -l testlist(a)domain.tld | It looks like you are running `mailman shell` as `root`. You should always run mailman commands including starting mailman as the Mailman user, never as root. Running thing as root can create things that later can't be read by the mailman user. > ||>>> from mailman.interfaces.action import Action >>> for mbr in > m.members.members: mbr.moderation_action = Action.defer |||commit()| > > |||>>> from mailman.interfaces.action import Action |||||||>>> english = > getUtility(ILanguageManager).get('en')| >>> for mbr in > m.members.members: || mbr.preferences.acknowledge_posts = False > mbr.preferences.delivery_mode = DeliveryMode.regular > mbr.preferences.delivery_status = DeliveryStatus.enabled > mbr.preferences.hide_address = False mbr.preferences.preferred_language > = english mbr.preferences.receive_list_copy = False > mbr.preferences.receive_own_postings = True|commit()|| I'm not sure what the above actually says. The interaction should look like ``` >>> from mailman.interfaces.action import Action >>> english = getUtility(ILanguageManager).get('en') >>> for mbr in m.members.members: ... mbr.preferences.acknowledge_posts = False ... mbr.preferences.delivery_mode = DeliveryMode.regular ... mbr.preferences.delivery_status = DeliveryStatus.enabled ... mbr.preferences.hide_address = False ... mbr.preferences.preferred_language = english ... mbr.preferences.receive_list_copy = False ... mbr.preferences.receive_own_postings = True ... >>> commit() ``` Actually, importing Action is not necessary as it is among the things defined by default in `mailman shell` in interactive mode. > Before the shell command, the web interface was with an other language > (i tested with italian one) and other options preferences, but after the > shell command, after a web interface refresh, it doesn't change. The above shell interaction sets the preferred_language for all list members to english. This has nothing to do with the language for the web UI. This is set by Django. See <https://docs.djangoproject.com/en/4.2/topics/i18n/translation/#how-django-d…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: rest api runner not running

by Mark Sapiro

On 3/27/21 5:13 AM, Christine wrote: > Hi, > I have been using mailman for about ten years, now I want to move the > lists to another server, I have installed mailman3 there, most of it > seems to be running, but the "rest api runner" is not. Nothing is > listening on port 8001. What have I missed? What do I do to start the > restapi runner? I checked the logs, I don't see anything suspicious. > > this is what systemctl status says: > > root@lists:~# systemctl status mailman3 > ● mailman3.service - Mailman3 server > Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; > vendor preset: enabled) > Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; > 6min ago > Docs: man:mailman(1) > https://mailman.readthedocs.io/ > Process: 173111 ExecStart=/usr/bin/mailman -C > /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM) > > Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... > Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation > timed out. Terminating. > Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result > 'timeout'. > Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server. Nothing is listening on port 8001 because apparently Mailman core failed to start. > There is nothing in mailman.log, nor in smtp.log What Mailman package is installed? Perhaps you should contact the packager for support. Can you run the mailman command manually, e.g. ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg ``` where `xxx` is the Mailman user which if I'm guessing correctly that this is a debian/ubuntu package, is `list`. Otherwise it might be `mailman`. That should just produce a list of `mailman` subcommands. If that works, try ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg info ``` and ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg start ``` and see what they produce. -- 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

[MM3-users] Re: changeaddress command and nonmembers

by Mark Sapiro

On 2/2/23 09:28, Mike Wertheim wrote: > > Now that we're on Mailman 3 and the email list was migrated from MM2 to > MM3, we see that newaddress(a)gmail.com is a Member of the list, and we see > that oldaddress(a)hotmail.com is a NonMember of the list. That all makes > sense. > > But now, this person has decided that they actually want to go back to > using the old address. > > So I ran the command "mailman changeaddress newaddress(a)gmail.com > oldaddress(a)hotmail.com". But that gave me this output: > > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address oldaddress(a)hotmail.com already exists; can't change. > > > Can anyone explain how I can do what I'm trying to accomplish? The user needs to create an account in the web UI for newaddress(a)gmail.com and once that is done and she is logged in, she can add oldaddress(a)hotmail.com to her account. There are alternatives that you as list owner can do such as mass subscribing oldaddress(a)hotmail.com to the list and then disabling delivery to newaddress(a)gmail.com. There are also things you can do in `mailman shell` such as ``` $ 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 >>> mbr = m.nonmembers.get_member('oldaddress(a)hotmail.com') >>> mbr.role = MemberRole.member >>> commit() ``` > (Also, why is this error displaying the usage message? That seems odd, > since the number and type of arguments was correct.) That's the way the `mailman` command works. All errors start with the usage. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Mark Sapiro wrote: > On 3/18/25 3:39 PM, Johan Alsina via Mailman-users wrote: > > Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. > > See this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/7... > Some of that may be useful. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Hi Mark, i configured the paths to load all the files from /staticfiles/ but for some reason the .css files are loading but not showing again and i dont know why... https://freeimage.host/i/3ovaZgf https://freeimage.host/i/3ovaQ0G

2 months, 3 weeks

[MM3-users] Re: Default values for lists in Mailman 3

by Mark Sapiro

On 9/19/24 05:46, Markus Grandpré wrote: > Dear list, > > I would like to activate the invitation setting for all lists as > default. In Mailman 2.1 I have done this in the file > </etc/mailman/mm_cfg.py>: > > > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > > > How can I do this in Mailman 3? There is a draft merge request at https://gitlab.com/mailman/postorius/-/merge_requests/930 which implements a framework for setting Postorius defaults and creates a setting to set the default for pre-verified on the mass subscription page. Once merged, this can easily be extended to provide a default for Invitation. In the mean time, you can only do this by patching src/postorius/forms/list_forms.py like ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): invitation = forms.BooleanField( label=_('Invitation'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' ``` > Can I also transfer other default values > like: > > ... > DEFAULT_SERVER_LANGUAGE = 'en' > DEFAULT_SEND_REMINDERS = 1 > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > DEFAULT_PRIVATE_ROSTER = 2 > DEFAULT_ARCHIVE = Off > DEFAULT_ARCHIVE_PRIVATE = 1 > ... > > from the very same configuration file to Mailman 3? Is there a > documentation of the default values for lists in Mailman 3? This is done by creating a list style with the desired defaults. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for documentation of styles and see https://gitlab.com/mailman/example-mailman-plugin for an example of creating a plugin in Mailman core to make a persistent style. There is no specific doc for the list settings. You need to look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for the various settings and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default… to see which default classes are applied for various styles. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Pck files stuck in out queue

by Mark Sapiro

On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Mass subscribe gives HTTP Error 500 when using custom template

by Mark Sapiro

On 1/28/20 6:15 AM, Jeffrey D wrote: > Hi, > > I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. ... > requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) > > Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. What is your setting in settings(_local).py for POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' It should be the base URL for connecting to Postorius. I.e., if you normally connect to Postorius via https://www.example.com/postorius, it should be https://www.example.com You say Postorius/Mailman is running on port 8001. Mailman core's rest server should be listening on port 8001, but your web server can't proxy to Postorius on that port. Normally, the wsgi server that supports wsgi access to Django (Postorius and HyperKitty) listens on port 8000, at least if it is gunicorn or uwsgi proxied from your web server, or if it's Apache and mod_wsgi, proxying is not involved. Again, it looks like you may be using Apache and mod_wsgi in which case you could have POSTORIUS_TEMPLATE_BASE_URL set to something like https://www.example.com or even http://localhost or http://localhost:80, but not port 8000 if no wsgi server is listening there. Also, the URL is now in the database entry for this template in the postorius_emailtemplate table, so even after you fix POSTORIUS_TEMPLATE_BASE_URL, you'll probably have to delete and recreate the template in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/21/20 7:52 PM, Alan So wrote: > > Since the CC header remains unchanged if we test using "mailman inject", we may further check whether Mailman LMTP Runner change the CC header. You are correct. If I post your test via email rather than `mailman inject`, I see the issue. I'm working on figuring out why. (Sorry for spamming you with test Ccs.) I'm at a loss to explain why `mailman inject` doesn't show this. I have captured the queued message and the only differences I see between the one from the lmtp runner and the one from inject is the one from lmtp runner has an X-MailFrom: header and 'received_time': datetime.datetime(2020, 5, 22, 3, 45, 24, 532711), 'to_list': True, and I even tried running `mailman inject` with `-m to_list=True` and it still didn't fail. However, if I take the qfile that dumps as ``` > $ bin/mailman qfile 1590119124.5909426+9a002936a59e194f70187405ac624173cbf470b5.pck > [----- start pickle -----] > <----- start object 1 -----> > Received: by msapiro.net (Postfix, from userid 1000) > id 60624340253; Thu, 21 May 2020 20:45:24 -0700 (PDT) > From: mark(a)msapiro.net > To: list(a)example.com > CC: "ABC DEF > (XYZ)" <mark(a)msapiro.net> > Subject: testing please ignore > Message-ID: <something_more(a)example.net> > Date: Fri, 22 May 2020 09:53:58 +0800 (HKT) > Message-ID-Hash: NDG3FHLPO35F2Y4YXFAKFIKDXAC6FHGM > X-Message-ID-Hash: NDG3FHLPO35F2Y4YXFAKFIKDXAC6FHGM > X-MailFrom: mark(a)msapiro.net > > hello > > <----- start object 2 -----> > { '_parsemsg': False, > 'listid': 'list.example.com', > 'original_size': 326, > 'received_time': datetime.datetime(2020, 5, 22, 3, 45, 24, 532711), > 'to_list': True, > 'version': 3} > [----- end pickle -----] ``` and put it in the 'in' queue the received message from the list does contain CC: XYZ <ABCDEF(a)msapiro.net> Thus, the issue occurs downstream of lmtp runner. It will take more investigation to determine where. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 9/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > I am trying to find a way for content filtering to remove executables from the emails sent to the list. I found some hints under: > https://mailman.readthedocs.io/en/stable/build/lib/mailman/handlers/docs/fi… > > but still not clear how to do it for all type of excecutables. There are four list settings that affect this. They are pass_types, pass_extensions, filter_types and filter_extensions. the pass_* settings specify message parts the list will accept while the filter_* settings specify message parts the list won't accept. The page at <https://mailman.readthedocs.io/en/stable/src/mailman/handlers/docs/filterin…> only discusses filter_types and needs updating for the others. Filtering by extension only works on message parts that have an associated file name. Thus, while you can add things like 'exe', 'bat', 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it won't be completely effective. A better approach is to use MIME types[1] and only allow those you want. For a discussion list, a reasonable set is what this list uses: multipart message/rfc822 text application/pgp-signature This will accept any multipart and message/rfc822 parts for further analysis and ultimately accept only text/* and application/pgp-signature elemental parts. If you want to accept images and pdfs, you can add image application/pdf See <https://www.iana.org/assignments/media-types/media-types.xhtml> for a list of all registered MIME types. Note that these are all of the form main_type/sub_type and putting just main_type in *_types passes or filters all subtypes for that maintype. [1] You can use both, e.g. filter_extensions to remove those you don't want and pass_types to accept the MIME types you do want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Is it possible to use an authenticator with incorrect, missing, or changing email addresses?

by Mark Sapiro

On 05/23/2018 12:56 PM, andrew(a)fsf.org wrote: > Hello Mailman 3 users list, > > I was wondering if it's possible to set up a CAS authenticator with django-allauth ( https://pypi.org/project/django-allauth-cas/ ) even if we cannot guarantee the correctness of email addresses supplied by our CAS instance? Some contacts may also be missing an email address. I read about this here, and it seems like it wouldn't be possible: > > http://docs.mailman3.org/en/latest/config-web.html#configure-social-login > >> To see a list of all the providers, please have a look at the documentation of django-allauth. Make sure that the one you choose provides “email” as part of user data, otherwise it won’t work with Mailman. e.g. Twitter doesn’t give out emails. > > What if a user's email address changes on the CAS server? Will their email address in Mailman 3 be updated the next time they log in? If django-allauth-cas can't provide an email address, that user can't use it for Mailman authentication because authentication is for a registered email address. The way it works is a user registers an email address with Mailman. Once the address is registered, but not before, it can be linked to one or more configured django-allauth providers, and once linked, the user can log in to the Mailman web UI via a linked allauth provider. If the allauth provider doesn't supply the user's email address, I don't think it can be linked, but even if it can, it won't work. If the user's CAS email changes, the user would have to add the new address to her account in Mailman and could then link the new address to the CAS allauth provider. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Odd hold message

by Mark Sapiro

On 7/4/19 6:00 AM, Andrew Bernard wrote: > I received a very simple post today that was held with the following reason: > > The message is being held because: > > Message contains administrivia > > At your convenience, visit your dashboard to approve or deny the > request. > > > What is this all about? What does Mailman consider to be administrivia, of > all things, and why is this a reason to hold a message? The administrivia check is designed to detect messages posted to a list which look like they should have been sent to the list-request address instead. You can turn this check off in Postorius at Settings -> Message Acceptance -> Administrivia. > The only thing in the message I can see is that it mentioned '100 members'. > Is Mailman becoming sentient and developing an attitude? Seriously, I'd > like to know more about this. That's not the reason. The administrivia rule checks the Subject: header and the first N non-blank lines of the first text/plain part of the message for things that look like an email command. I.e., lines that begin with a command word followed by the appropriate number of 'arguments'. Here's the list EMAIL_COMMANDS = { # keyword: (minimum #args, maximum #args) 'confirm': (1, 1), 'help': (0, 0), 'info': (0, 0), 'lists': (0, 0), 'options': (0, 0), 'password': (2, 2), 'remove': (0, 0), 'set': (3, 3), 'subscribe': (0, 3), 'unsubscribe': (0, 1), 'who': (0, 2), } This is actuall not a valid list because it is from Mailman 2.1 and not all the above are valid Mailman 3 email commands, but that's what is checked. The N is the configured value for [mailman] email_commands_max_lines: (default 10) Thus, if the Subject: or one of the first 10 non-blank lines is who are you? the administrivia rule will hit. See the source in mailman/rules/administrivia.py for more detail. -- 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: Issues with migrating from Mailman2 to Mailman 3

by Mark Sapiro

On 9/22/19 10:29 AM, Uwe Grasshoff wrote: > Hello all, > > I'm currently trying to convert a Debian based mailman2 installation to > a docker based mailman3 installation. > I successfully running the mailman-web and mailman-core containers > together with the database container but I'm struggling with the import > of the old mailing lists. In the core container I'm running this two > commands for every mailing list: > > mailman create mailman(a)example.com > mailman import21 mailman(a)example.com > /oldmailman/lists/mailman/config.pck > > Then I'm switching over to the mailman-web container and running this > two commands: > > python3.6 manage.py hyperkitty_import -l mailman(a)example.com > /oldmailman/archives/private/mailman.mbox/mailman.mbox > python3.6 manage.py update_index_one_list mailman(a)example.com > > I'm getting no errors or something else which could indicate a problem. > After that I'm looking into the web interface > http://example.com/postorius/lists/ > There I can only see the public mailing list and the private ones are > not shown there (as expected). Everything up to this point is expected behavior. > When I then try to login with the List > Manager credentials of the lists (from mailman2) I can't login in. So I > thought maybe I have to "register" myself again to than get access to > the list management. > So I tried that but when I filled out the form and click "Register" I'm > presented with an error page which titles "Serverfehler" (Server error > in german) and the message "An error occurred while processing your > request." I'm not sure about the error, but the import21 process registered you so what you need to do is go to the Login page, click "Forgot Password?" and then request a password reset. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: One bounce, 5 bounce counts

by Mark Sapiro

On 1/13/22 6:17 AM, Henrik Rasmussen wrote: > > My problem, though, is that some subscribers may be disabled even they are able to receive mails (confirmed with sendmail -bv), and I have been looking at one subscriber in particular. > > > 1. Can there be (i'm not saying there are, maybe it's my lack of knowledge) somthing regarding Mailman? > 2. And what would the appropeiate per list bounce settings, if not default? Referring to the example below, it seems that your Postfix delivers successfully to the first hop MX of the recipient, but the mail bounces further downstream resulting in an emailed bounce. One thing you can do to help mitigate scoring of bounces of emails due to spam filtering is to set ``` [mta] verp_probes: yes ``` This will cause Mailman to not disable delivery when bounce score reaches threshold, but rather send a probe which hopefully won't be detected as spam and only disable delivery if the probe bounces. > Actual example: > > > * Mailman sent seemly 6 mails to a member on January 6th. > * I see one bouce message D1426CE22A in Postfix log that was delivered back to Mailman > * I see that Mailman is counting the bounce score from 1 to 5, one at the time, but that was day after receiving the bounce, and no other mails have been sent to the user on the 7th nor received as bounce on the 7th. I suspect that it must have been in the Postfix queue until then, but I wonder why that could be - but could be. > * The bounce would be in the Postfix queue until sent to Mailman and thus removed from the Postfix queue. I suspect the issue is something like a connection problem from the recipient MX to a relay MX that is not being reported as a bounce until the retry interval has expired. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 6:35 AM, Andy Smith wrote: > > I'm concerned that Mailman seems to have scored my address as > bouncing even though it isn't, merely because it appears inside a > message that was rejected. > > Is that expected? Is there any way to avoid it? No, it's not and it should not ever happen. > I see that Mailman has a bunch of heuristics to parse bounce > messages. In this case though, there shouldn't have been a bounce > message received to users-bounces@, as this was an SMTP-time > rejection. Mailman seems to have parsed addresses out of the actual > mail it was sending, rather than only scoring the subscriber address > it was trying to send a list posting to. Yes, flufl.bounce is used to parse messages delivered to the -bounces. There are a lot of hueristic recognizers, but RFC 3464 compliant DSNs should be recognized by the DSN detector which is tried first and which gets the failed address from the report. See https://gitlab.com/warsaw/flufl.bounce/-/blob/master/flufl/bounce/_scan.py#… However, SMTP failures do not result in DSNs to the -bounces address. If recipients are refused at SMTP time, this should result in a message in Mailman's smtp.log of the form ``` <message_id> recipients refused: <mta's message> ``` and we create a fake DSN (see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…) to be processed as a bounce for the failed recipient. In this case, no parsing of the failed message should occur. I can't explain what happened in your case. It seems that somehow the original post was delivered to the -bounces address and parsed by one of the heuristic recognizers (probably simplematch), but how could that happen? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Attachement processings questions

by Lars Schimmer

On 2020-02-04 19:15, Mark Sapiro wrote: > On 2/4/20 9:02 AM, Mark Sapiro wrote: >> >> You can fix it by patching the Python library email/generator.py as at >> <https://github.com/python/cpython/pull/18056/files#diff-220640ea02a24dfdbb0…>. > > > > And once you have patched email/generator.py and restarted Mailman core, > you can deliver the messages by running the `mailman unshunt` command, > but first look in var/queue/shunt/ to ensure you won't be unshunting any > unwanted messages. You can examine those files with `mailman qfile`. Great This did helped. Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

5 years, 4 months

[MM3-users] Re: Help with mailman user and mailman Web users

by Mark Sapiro

On 2/15/22 05:57, Sherin wrote: > > I have installed mailman3 server and configured MailmanWeb ( > hyperkity + Postorious ) . The service and everything works fine, but I > am little bit confuses with the user management in mailman3, > > 1) I created an owner user for a mailing list using the mailmanclient > api tools, # from mailmanclient.client import Client > 2) I can't login to the Mailmanweb with this user There are Mailman users and Django users. These are distinct. Creating a Mailman user does not automatically create a Django user and vice versa. In order to log in to the web UI, one must be a Django user, so this user has to go to the web UI and Sign Up. > For further investigation shows the mailman have its own database and > the web frontend have its own database too. > So my question is how to configure the webfrontend ( hyperkit+ > postorious ) to use the accounts logins created from the mailmanclient > api from the mailman core database. You can't. Well, I suppose you could modify the HyperKitty sync_mailman job or create another Django job to create Django users for Mailman users who aren't currently Django users, but short of that, there's no config for it. > Or is there a way to use only one user management system ? No. Mailman core and the web UI are separate applications by design in order to enable Mailman core to operate with any appropriate web UI. We provide Postorius and HyperKitty as web UIs for management and archiving and they are based on Django which has its own user management. It was our hope that other, perhaps more light weight, web UIs would be developed and available, but aside from EMWD's proprietary Harmony/Empathy PHP applications, we are not aware of any. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by Mark Sapiro

On 1/26/22 11:05, nate wrote: > > Can I suggest the messaging to new users be improved to communicate > this situation as it is not clear. > > The automated message I got said this was the reason my message was > held: The message comes from a moderated member. > > Which makes sense if I REALLY think about it(I was a moderated member > at first), but then the next question is why was I moderated. Your > explanation makes sense. > > It would be nice if it had more info along the lines of what you > said, or even better adjust the messaging for the "Welcome" email > to indicate your first message(s) will be held for moderation(I checked > both emails I got back from the list just now to verify this info is > not there). I was confused for a while(again 21 year veteran of mailman) > thinking I sent my message using the wrong email address, after confirming > I sent with the right one I just decided to wait to see what would > happen. The situation is no different in Mailman 2.1. The issue is that what may be appropriate in the held message to the user or the list welcome message depends on list configuration and the policies of the particular list. Thus, we can't really modify the default message templates in this way. It requires making list specific templates or possibly domain or site specific templates where all the lists in a domain or site have the same policies. This can be done by list, domain or site admins, but doing or suggesting this on a site like, e.g., mail.python.org which has 232 Mailman 2.1 lists with a total of 243 unique owners and 182 Mailman 3 lists with a total of 212 unique owners is a daunting prospect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 18:35, Joel Lord wrote: > > The periodic digests do seem to be coming out. I also now have > confirmation that the one message in this morning's digest that was from > May 4th was also included in the last digest back on May 4th, so it > seems that the one message was left behind in the digest queue when the > periodic digest was sent. I don't see how that can happen. The process that sends a digest renames the var/lists/<list-id>/digest.mmdf mailbox file in which the messages are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and <issue> are the volume and issue numbers of that digest, and then queues a message in the `digest` queue to tell the digest runner to create the digest from the messages in that mbox and send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that is created anew when the next post arrives. Further, if there is a non-empty digest.mmdf file, its messages should be sent no later than the next 11 PM `cron digests`. > There was one earlier message to the list > back on May 4th, before the one that got duplicated, but I can't tell if > that triggered a size-based digest to be sent: the logs aren't clear > enough on that detail for me to tell. OK > Just to inform things: > > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman > django-mailman3==1.3.9 > mailman==3.3.8 > mailman-hyperkitty==1.2.1 > mailman-web==0.0.6 > mailmanclient==3.3.5 > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper > mailman-hyperkitty==1.2.1 Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up to date as are the others. > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post > postorius==1.3.8 > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/28/20 12:55 PM, Mark Dadgar wrote: > > 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>>' If I'm reading the above correctly, it appears that there is a message in the archive database whose message_id value is 'BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>'. The trailing '>' is causing HyperKitty's Email.as_message() method to try to set a value of '<BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>>'. Or maybe there's leading white space in the value, or both. Try the following patch. --- a/hyperkitty/models/email.py +++ b/hyperkitty/models/email.py @@ -24,7 +24,7 @@ import logging import os import re from email.message import EmailMessage -from email.utils import formataddr +from email.utils import formataddr, make_msgid from django.conf import settings from django.db import IntegrityError, models @@ -175,7 +175,12 @@ class Email(models.Model): header_date = self.date.astimezone(tz).replace(microsecond=0) # Date format: http://tools.ietf.org/html/rfc5322#section-3.3 msg["Date"] = header_date.strftime("%a, %d %b %Y %H:%M:%S %z") - msg["Message-ID"] = "<%s>" % self.message_id + try: + msg["Message-ID"] = "<%s>" % re.sub('[<>\s]', '', + self.message_id) + except: + msg["Message-ID"] = make_msgid() if self.in_reply_to: msg["In-Reply-To"] = unfold(self.in_reply_to) Also note that if you got 8.5.MB for one day's messages, probably the entire range will time out and you'll have to get it in pieces. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/23/21 10:51 AM, David Bremner wrote: > > I'm getting (many) uncaught bounce messages for one user. Other than > forcibly unsubscribing them, is there anything I can do? I hesitate to > post this message publically, but here is what I can see, somewhat > anonymized If you send me the complete bounce message off list, I can see if it should be added to the recognition at https://gitlab.com/warsaw/flufl.bounce/. BTW, is flufl.bounce in your installation version 4.0? If not you can update via pip install -U flufl.bounce which may help. Actually, depending on how these where installed, it might be necessart=y to do pip install -U flufl.bounce flufl.lock flufl.i18n To avoid import errors due to packaging issues. > The MIME structure looks like > > └┬╴multipart/mixed 7030 bytes > ├─╴text/plain 442 bytes > ├─╴message/delivery-status 176 bytes > └─╴text/rfc822-headers 5301 bytes This is not a RFC 3464 compliant DSN which looks like the above except the top level is multipart/report, not multipart/mixed. However, our recognizer shouldn't care as it only looks at the message/delivery-status part. > In /var/log/mailman3/bounce.log I see lines like > > Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> <hex-digits(a)foo.bar> is the Message-ID: > In the delivery-status part I see A compliant DSN will also have a Reporting-MTA: section preceding the Final-Recipient: section. > Final-Recipient: rfc822; fub(a)foo.bar > Action: delayed > Status: 4.0.0 This is not a bounce. It is a 'delivery delayed' message. If delivery is not accomplished within an MTA configured time (days), it will turn into a 5.x.x failure which is a bounce, but since fub(a)foo.bar was not recognized, the DSN is non-compliant in some way. In any case, please send me a copy of the bounce so I can see about recognizing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: How do you remove the Hold on all non-member forwarded emails?

by Mark Sapiro

On 5/26/23 12:38 PM, Sean Westfall wrote: > > But I am having trouble using one of its configurations. I configured my mailmain3 instance to accept all non-member emails, as I want all emails that are sent to the mailman client to go to all subscribers without having it held for moderation -- I did this by setting this setting: > > https://i.imgur.com/PGzaD0k.png > > Action to take for postings from non-members for which no explicit action is defined. (Details for generic_nonmember_action) -> "Accept" That screen shot and language is from Mailman 2.1, not Mailman 3. > But this doesn't work for forwarded emails. Even if the email address that is being forwarded from is included in the "List of non-member addresses whose postings should be automatically accepted." > > I noticed that all emails that are forwarded to the mailing list are always held for moderation -- though this isn't the case for email that are sent to the mailing list directly. But I want it so that emails that are even forwarded to my mailman mailing list don't get held in moderation. > > How do I set mailman to do this? I was thinking if there is no way to configure this easily then I might have to do this from the code, which means I might have to ask on the developer mailing list -- or I have to go with an entirely different solution (using something other than mailman3). Please clarify whether you are using Mailman 2.1 or Mailman 3. There should be no difference between a message sent directly vs. a forwarded message. What is the reason given for why the message is held? Also, the appropriate list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Message does not appear in archive

by Mark Sapiro

On 09/03/2018 06:13 PM, Paul Arenson wrote: > Hi again. I take it the lack of responses mean I should wait it out a little longer? It's of course up to you, but I recommend Mailman 3. There are still some rough edges, and there are a number of settings not yet exposed in Postorius, but we are working on it and it is quite usable today. > I was considering, as mentioned, Fed Forum (but not much help in setting up), Slack and Flock. Would all mean more work than I can afford. > > Which is why upgrading from Mailman 2 to 2 still seems like the best idea. > > We would then have the perfect upgrade to Mailman 2, where people could more easily find their topics (aided by a lot of nudging to be proactive in choosing the topic to post in and not doing thread hijacking). Do you mean Mailman 3? > I looked to see if there was anyone doing this sort of service. All I could find is someone doing their own hosting called https://mailman3.com/. mailman3.com is a Mailman 3 hosting service unaffiliated with the GNU Mailman project. > I would much prefer to upgrade my C-Panel installation of the lists, which by the way are here: > > https://gale-sig.org/mailman/listinfo/galemembers_gale-sig.org > https://gale-sig.org/mailman/listinfo/galeexec_gale-sig.org > > Any estimate on if/when I would be able to upgrade these c-panel forums (or possibly get someone to help me move them?) I suspect it will be some time before Cpanel offers Mailman 3. It is fairly straightforward to migrate an existing Mailman 2.1 list and it's archives to Mailman 3, but it requires access to the underlying Mailman 2 file system which you may not have in a hosted cPanel environment. See <http://docs.list.org/en/latest/migration.html> for more on migration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/26/24 02:44, Marco van Tol wrote: > Op 25 jan 2024, om 14:16 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: >> >> Okay, so, I got a bit further, but something still gets stuck. >> >> Here’s what I did. >> Keep in mind I’m using containers that are built from some CI/CD pipeline, so I updated the pipeline to apply the patch attached to this email to `/usr/lib/python3.11/site-packages/xapian_backend.py`. >> >> Before I had 2 list servers with the “Term too long” issue, 1 got resolved by this, and the other did not. >> I opened a shell in the newly deployed container to confirm the patch was applied in it. >> >> The other attachment to this email is a copy/paste from the full error from `./manage.py rebuild_index`. >> >> Is there something else special in the email that makes it choke that evades the xapian patch? >> >> Thank you very much in advance! The message above with the attached "full error" never got to the list. What is the error report? > > I tried to change to ‘hash’, but the code in that bit of the function has not been tested enough. > > For example `hole = sha224(hole.encode('utf8')).hexdigest()` comes back with that the bytes object hole does not have an encode() method. > When I change it to `hole = sha224(hole).hexdigest()`, the following error is: That's only part of it. You need hole = sha224(hole).hexdigest().encode('utf8') > text = text[:match.start()] + hole + text[match.end():] > TypeError: can't concat str to bytes > > The ‘hash’ part of that function needs some debugging. Yes, presumably because no one sets `XAPIAN_LONG_TERM_METHOD=hash` in the environment. Do you have a reason for this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Mark Sapiro

On 1/30/23 02:44, Odhiambo Washington wrote: > The documentation > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> > says that I need to create /path/to/postfix-mailman.cfg containing: > [postfix] > transport_file_type: regex > > Then append the path to the [mta] section of mailman.cfg, viz: > > [mta] ... > configuration: /path/to/postfix-mailman.cfg > > That is exactly what I have done on my test platform, but I get the error > below when creating a list. > Perhaps I overlooked something? ... > "/opt/mailman/venv/lib/python3.9/site-packages/mailman/mta/postfix.py", > line 87, in __init__ > self.postmap_command = mta_config.get('postfix', 'postmap_command') > File "/usr/local/lib/python3.9/configparser.py", line 792, in get > raise NoOptionError(option, section) > configparser.NoOptionError: No option 'postmap_command' in section: > 'postfix' This is a bug. Whether it is a bug in documention or code is not completely clear. Current code requires there be a `postmap_command:` setting in the [postfix] configuration even though it isn't used if `transport_file_type:` is set to regex. You can fix this in one of two ways. Either apply this patch ``` --- a/src/mailman/mta/postfix.py +++ b/src/mailman/mta/postfix.py @@ -84,9 +84,10 @@ class LMTP: def __init__(self): # Locate and read the Postfix specific configuration file. mta_config = external_configuration(config.mta.configuration) - self.postmap_command = mta_config.get('postfix', 'postmap_command') self.transport_file_type = mta_config.get( 'postfix', 'transport_file_type') + if self.transport_file_type == 'hash': + self.postmap_command = mta_config.get('postfix', 'postmap_command') def create(self, mlist): """See `IMailTransportAgentLifecycle`.""" ``` (watch for possible wrapped lines in above) or add postmap_command: unused to /path/to/postfix-mailman.cfg. Note however that hash tables for Postfix are more efficient than regex tables and the only reason we support regex tables is for a Docker container that doesn't have Postfix installed in the Mailman container. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mohsen Masoudfar

Sorry, I found it! Thanks Mohsen -----Original Message----- From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, December 28, 2022 2:49 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] Thank you Mark for your help. I see fedora under Django administration: Home > Social Accounts > Social Accounts as a provider listed, but we do not use it and I would like to remove it. So far I did not find a way to delete it. We do not need Hyper Kitty either, because we do not archive any emails. I appreciate if you could point me how I may delete Fedora as a provider. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, December 27, 2022 4:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdjango-al… -- 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… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org _______________________________________________ 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… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org

2 years, 5 months

[MM3-users] Re: Custom Archiver

by Mark Sapiro

On 4/1/23 16:33, Peter Knowles wrote: > Mark, > > The whole reason I'm developing my own "frontend" for both "list management" and "archive" access is because Python isn't really the language I speak... I'm a PHP guy, and so I'm working to build with the language I know and love, while utilizing Mailman for what it does best... In addition to implementing the frontend the way I want it (expose/hide feature that are useful/unuseful to our users), I want to fully customize the visual appearance to represent the SaaS offering properly. This is exactly the reason why Mailman core was decoupled from archiving and the web UI. HyperKitty and Postorius were developed because we knew that almost no one would use Mailman core without archiving and a web management UI, but we always hoped that others might develop and contribute other web based archiving and management interfaces. Brian Carpenter of EMWD who tragically died of COVID did exactly that with his Affinity and Empathy PHP applications that interface with Mailman core via the REST API. EMWD hosts lists that use those interfaces, and had Brian not died, some version of those might be open sourced, but his initial thrust was to keep them proprietary for his business reasons. There is an early description of Brian's concept for Affinity at https://gitlab.com/mailman/affinity. > *** we're not try to hide that Mailman is in the equation, just how the overall interface is visually represented *** > > That all being said, on a slight segway... Aside from using the REST API, is it practical or possible to manipulate the database directly? That is, in doing so would it just work or are there extra moving parts when an API request is issued? It probably is possible, but I would definitely discourage it. The REST API should provide everything you need without your having to reimplement everything it does. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Setting up Admin Account

by Mark Sapiro

On 11/14/2017 08:13 PM, Pierre Abbat wrote: > So I installed a crontab for list and read about configuring the DB (I think > I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html > . Because of the dollar sign, I assume that the commands are to be run as > list. Here's what I did: > > root@lists:~# ls > root@lists:~# sudo list > sudo: list: command not found The command you want there is something like sudo -u list bash or whatever shell you want. > root@lists:~# su list > This account is currently not available. Probably because the default shell for list is nologin. But, I see you eventually figured it out. > root@lists:~# ls /var/list > ls: cannot access '/var/list': No such file or directory > root@lists:~# locate mailman-suite_project > root@lists:~# mkdir /var/list > root@lists:~# chown list.list /var/list > root@lists:~# su list > This account is currently not available. > root@lists:~# man su > root@lists:~# su -s /bin/bash list > list@lists:/root$ cd > list@lists:~$ cd mailman-suite_project > bash: cd: mailman-suite_project: No such file or directory > list@lists:~$ mkdir mailman-suite_project > list@lists:~$ cd mailman-suite_project > list@lists:~/mailman-suite_project$ python manage.py createsuperuser > python: can't open file 'manage.py': [Errno 2] No such file or directory > list@lists:~/mailman-suite_project$ locate manage.py > /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py > /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc > /usr/local/lib/python2.7/dist-packages/example_project/manage.py > /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc > /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py > > Which manage.py should I use? Probably /usr/local/lib/python2.7/dist-packages/example_project/manage.py but your apparent lack of basic system administration skills is not making things easy for you. You might be better off looking at <http://docs.list.org/en/latest/prodsetup.html#mailman-3-in-docker>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/15/21 12:55 PM, Sarah H wrote: > > The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius. The code is if result.status_code != 200: logger.error("HyperKitty failure on %s: %s (%s)", url, result.text, result.status_code) raise ValueError(result.text) > Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: So the above log entry should be followed by result.text and result.status_code. The next entry below is from the `raise ValueError(result.text)` What do you get from curl http://lists.client.org/hyperkitty/api/mailman/archive and what if you change the scheme in the base_url setting to https? > Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: And this one below is is because of the above exception. > Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver: > > I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines. > > [15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2" > > and at the start of the block: > > [15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" > Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname> These are from the Mailman REST API and are not relevant to your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Hyperkitty no longer archiving

by Mark Sapiro

First, my apologies for not taking note of your MAILMAN_ARCHIVER_FROM setting in your OP. On 11/22/22 08:52, Hirayama, Pat wrote: > Steve wrote: >> 2. Does settings.py have "from settings_local import *" in it? > > Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other related settings defined at the top of the settings.py file? Or should I update settings.py based on what is in settings_local.py? Assuming the `from settings_local import *` is at the end of settings.py, anything defined in settings_local.py will override the definition in settings.py. There's no need to change settings.py. >> 3. Are there multiple copies of settings.py lying around? > > Well, there are these: > > ./usr/local/lib/python3.8/site-packages/rest_framework/settings.py > > ./usr/local/lib/python3.8/site-packages/postorius/doc/settings.py > > ./usr/local/lib/python3.8/site-packages/django_q/tests/settings.py > > ./usr/local/lib/python3.8/site-packages/django_extensions/settings.py > > ./usr/local/lib/python3.8/site-packages/mailmanclient/restobjects/settings.py > > ./usr/local/lib/python3.8/site-packages/example_project/settings.py > > > Only the last has MAILMAN_ARCHIVER_FROM defined in it, but I was assuming from the example_project subdirectory name that this was just a sample file, and besides, "from settings_local import *" is also set in it. Yes, those are all samples. The ``` ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured ``` message comes from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… which only occurs if '172.31.0.1' is not in MAILMAN_ARCHIVER_FROM. Given that it is in MAILMAN_ARCHIVER_FROM as defined in settings_local.py, the only thing I can conclude is that the Django settings actually used is not the settings.py you think it is. I don't know offhand even what wsgi service is used in the docker container or how it is configured, but it needs to set its working directory to the directory containing settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Mark Sapiro

On 9/23/20 12:48 PM, pwilliam(a)fredhutch.org wrote: > Hi Mailman Users, > > I've done some more testing with this issue and have determined that this seems to be an issue with how commas within the display name in cc'd messages are being processed with messages sent from the Outlook client. > > Here are some test scenarios. Note I set the mailing list I was testing with to hold messages in moderation. Once the message was held I copied the information from the headers directly from Postorius held message information into the space below: > > Test Scenario 1: > Display name in Outlook: Williamss, Peterr C > Outcome: Does not work as intended. The CC address is formatted as Williamss(a)invalid.domain in messages received by mailing list members, oddly the "Peterr C" part of the display name is not present anywhere in the CC addresses received by mailing list members. > Header information from held message in Postorius > CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, > "Williamss, > Peterr C" <peterbw(a)test.com> "Williamss, Peterr C" <peterbw(a)test.com> is correct for how this address spec should be represented. If in fact, it is split into two lines "Williamss, Peterr C" <peterbw(a)test.com> as it appears above, it looks to me as if the actual header should be > CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, "Williamss, Peterr C" <peterbw(a)test.com> but is being folded on the whitespace between Williamss and Peterr. This is <https://gitlab.com/mailman/mailman/-/issues/725>, fixed at <https://gitlab.com/mailman/mailman/-/merge_requests/652>. The fix will be in the next (3.3.2) release of Mailman core. This is really an Outlook issue. See <https://gitlab.com/mailman/mailman/-/issues/725#note_351314868> for why folding within a quoted string is allowed, but in cases like this SHOULD not be done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

As Abhilash said I checked the django configuration for email but nothing happens when the program sends the confirmation email. Is there any other configuration file for django emails? On Tue, Aug 1, 2017, 23:18 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

7 years, 10 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/19/19 6:33 PM, kevin(a)coastalaska.org wrote: > We have a couple of people trying to subscribe to our list but receive an error similar to: > {"title": "409 Conflict", "description": "Subscription request already pending"} > > If I try to Mass Subscribe them in Postorius I get this error: > HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' > > In Postorius I don't see them hung up in Subscription requests. Postorius since 1.2.3 does not show subscription requests waiting user confirmation, only those waiting moderator approval. Thus, if the list's subscription policy is confirm or confirm then moderate, the subscribing user will be sent an email requesting confirmation. If the user hasn't answered that email, the request is pending user confirmation, and since 1.2.3, you won't see it in Postorius. [Update: this is fixed in 1.2.4] > What to do? 1) have the user find the confirmation request email and confirm, or 2) wait for the request to expire (default 3 days) 3) using mailman shell or the REST api or direct interaction with the database, find the token and confirm it. A shell example is ``` mailman shell -l your.list.id Welcome to the GNU Mailman shell The variable 'm' is the your.list.id mailing list >>> util = getUtility(IPendings) >>> list(util.find(mlist=m,pend_type='subscription')) ``` This returns a list of items like ('hex_token'), {'token_owner': 'subscriber', 'email': 'user(a)example.com', 'display_name': 'Jane User', 'when': '2019-04-09T01:26:08', 'type': 'subscription', 'list_id': 'your.list.id'}) You then do ``` >>> util.confirm('hex_token') ``` Note that https://gitlab.com/mailman/postorius/issues/314 which was responsible for removing the subs waiting user confirmation from the Postorius listing suggested "there could be a different place to see the ones pending user approval, so that a moderator can look and/or delete those.", but that hasn't been done. [Update: this is fixed in 1.2.4] -- Mark Sapiro mark(a)msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell 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 >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: FILTER_VHOST not working

by Mark Sapiro

On 3/22/21 1:03 PM, Johannes Rohr wrote: > In /etc/mailman3/mailman-web.py I have added > FILTER_VHOST = True > so that only the list for the current domain are shown. > > But this has no effect. The current situation with Postorius >=1.3.3 and Hyperkitty >=1.3.3 is for HyperKitty, FILTER_VHOST = True works. For Postorius, it works only if in the domains view, each mail host has a unique web host. It doesn't work. See this post <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and others in that thread for more info. Prior to Postorius 1.3.3 and Hyperkitty 1.3.3 it would only work if the mail host and web host values were identical for the domain. > > What's more, in hyperkitty I see at the top left the lable for the > default domain, even though I am visiting from another domain. That has nothing to do with FILTER_VHOST. The displayed there is the site referenced in the SITE_ID setting. > The web domains are exactly the same as the mail domans > (lists.[domain].[tld]) In that case, I'm not sure what's going on. > In the Nginx config I have added > > location / { > proxy_set_header X-Forwarded-Proto $scheme; > proxy_set_header X-Forwarded-Host $host; > proxy_pass http://localhost:8000/; > [....] > > } > > to make sure that mailman3 knows from which URL it is visited. > > Am I overlooking something? > > I am using the distribution packages on Ubuntu 20.04: > mailman3 3.2.2-1 > mailman3-web 0+20180916-10 > > I see, the mailman3-web package is quite dated. Is it recommended to > install via virtualenv instead? Yes, the issue is at least partially that that mailman3-web package doesn't have any of the FILTER_VHOST fixes. And yes, if you don't want to be stuck with dated packages tha don't include recent fixes, we recommend installation as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html> -- 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

[MM3-users] Re: Mm3 - new adventure

by Mark Sapiro

On 03/14/2017 09:14 AM, SP2L wrote: > > Lately started adventurous journey with Mailman3 > which is way, way different already from the beginning. > > Used Mailman bundler to install GNU Mailman, Postorius and HyperKitty > testing instance in virtual environment, mainly relaying on belows recipe: > > https://gitlab.com/mailman/mailman-bundler/ mailman-bundler is out of date and deprecated. You might find <https://wiki.list.org/x/17891998> of interest. > Present status. > > Above trio and MySQLServer are "talking" to each other > but because there isproper database on MySQLServer > I am facing strange and unexpected issues, Hi! > > Executing last two commands: > > (venv)$ ./bin/mailman start > (venv)$ ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 & > > I see Postorius and HyperKitty up & runningbut... > > Belowvery condensed messages from the console: > > > /HyperKitty/ > > DEBUG = False > > [12/Mar/2017 18:59:43] "GET /archives/ HTTP/1.1" 200 8002 > WARNING Not Found: > /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css ... Have you run the script that bundler installs as bin/mailman-post-update? > /mailman3/ > > DEBUG = False > > Server Error (500) > > > DEBUG = True > > HTTP Error 500: A server error occurred. Please contact the administrator. > > Exception Location: > /var/lib/mailman3/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py > in call, line 109 > > Then VERY, verylong list... Without knowing what the exception was and at least the start of the traceback, it's hard to say what this might be. > By means of PhpMyAdmin I created manually mailman3 database > and few tables (looking at 0001_initial.py) , but it is not working O.K. > This handmade table is not doing it's job. You shouldn't need to do this. If you have the proper settings and credentials in the DATABASES setting in mailman-web/settings_local.py and the [database] section in deployment/mailman.cfg, the tables should be created for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: Template's encoding setup

by Mark Sapiro

On 9/14/19 4:06 AM, Ugnius S wrote: > Yes, I have made several tests. I have set charset: iso-8859-13 > and default_language: lt in mailman.cfg. If you created the list before you set default_language: lt in mailman.cfg, the list's preferred_language is possibly 'en;' with character set us-ascii. > (Also I have set LANGUAGE_CODE = 'lt' in the settings_local.py, but I think > it is not related to this case.) Yes, LANGUAGE_CODE in settings_local.py is not relevant to this. > I have tried to set utf-8 as well in mailman.cfg as well. And I can > confirm - in all tested cases > text characters are correct (in footer as well) if sender sends text only. OK > If sender sends message in HTML (mostly all users send) then no > matter what the encoding is set in my mailman's > configuration or iso-8859-13, or utf-8 message body looks correct, but in > footer all national characters are replaced with > question marks " ? ". The addition of the footer is done by mailman/handlers/decorate.py. In the plain text case the message body is converted to unicode, the unicode footer is appended to the body and the new body is encoded for transmission. The encoding is the first of the list's character set, the incoming message's character set or utf-8 which produces no error. In the case where the incoming message is not a single plain text message part, the footer is added as a separate MIME part with the unicode footer encoded in the list's character set with errors='replace'. This is what produces the '?' characters. I suspect this happens because the list's preferred_language is 'en' with character set us-ascii. try running Mailman's bin/mailman shell -l your_list@domain at the prompt enter m.preferred_language if the response is not <Language [lt] Lithuanian> do m.preferred_language = 'lt' and then control-D to exit. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: restrict sending to owner/moderator

by Mark Sapiro

On 09/18/2017 02:28 AM, m.dohmen(a)xconnect.de wrote: > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. And on 09/19/2017 10:52 AM, David Krantz wrote: > > I have just tested a variant of this as I got curious: You find the > member you want to be able to send emails without moderation, then set > Administrative Options to "Accept Immediately (bypass other rules)". > That works. I have found no other ways, though. Or you may wish to set the owners/moderators subscriptions to "Default processing" which will still apply subsequent rule checks. I.e., set Default action to take when a member posts to the list to Reject (with notification) and set an appropriate notice (currently can't be set in Postorius - set it via 'mailman shell') and set Default action to take when a non-member posts to thelist to Discard or perhaps Reject but this creates backscatter. Then ordinary members have Moderation set to List default and owners/moderators have it set to Accept or Default. The problems with this are sall the owners/moderators need to be subscribers and there are maintenance issues with adding/removing owners/moderators. A better way to do this by sharing a "moderator password" for the list among the authorized posters. See <http://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.html> for how this is done to pre-approve posts. Then set the list to Discard/Reject all posts, and people who know the "moderator password" can still post. There is still an issue in that the password needs to be changed and redistributed when people become unauthorized, but this is more secure as regular moderation can be fooled by spoofing the sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 9:40 AM, David Newman wrote: > > IMO post-installation docs for list admins would be a big help in > Mailman3 adoption. I'm willing to help with this. Thank you for being willing to contribute. I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/. There is currently a userguide there at source/userguide.rst and referenced from source/index.rst. the addition of an adminguide.rst would be welcom if you want to work on that. > When I say "working": I'm looking to migrate Mailman2 mailing lists to > Mailman3, but am struggling with even basic setup tasks before we > attempt list migtration. > > For example, on admin page I've set up two lists, one public and one > private (each with unique list IDs), but neither appear in the site's > list index. Here are the steps to migrate a 2.1 list named `alist(a)example.com` and its archives. run Mailman's `bin/mailman create alist(a)example.com` follow that with ``` bin/mailman import21 alist(a)example.com /path/to/mailman2.1/lists/alist/config.pck ``` That will create the list and import its members and settings. To import archives run the Django admin command with arguments ``` hyperkitty_import -l alist(a)example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox ``` > And I don't know where to add list members. For imported lists, they are already added, but for new lists, you can add them in Postorius under Mass operations -> Mass subscribe or via the bin/mailman commands `addmembers` or `syncmembers`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > And clicking the site archives link throws this error: > > django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' > with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) > tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: users leaking across virtual hosts

by Mark Sapiro

On 3/25/22 12:49, Stanisław Findeisen via Mailman-users wrote: > Hi > > We are hosting several virtual hosts (mail host : web host is a 1:1 mapping with identical names), works fine, but it looks user accounts are somehow global, i.e. registering a new user in a new virtual host doesn't work if the user name or e-mail address are already in use in another virtual host. This happens on the Hyperkitty sign-up page: /accounts/signup/ , with the errors being "A user is already registered with this e-mail address." and "A user with that username already exists.". I am assuming this is a well-known limitation, which would require a serious internal redesign to fix; correct? These user registrations and logins are Django things so yes, they are global within the Django instance. > I was able to successfully login in the browser to a vhost using my user credentials from the original vhost (the one where the account was created) (the password was not auto-filled, of course, because of a different domain name). But how safe is this? How about subscribing to lists, posting etc.? Is this going to mess things up somehow? I don't think it's a problem. The user is a Django user for the web UI. The fact that there is or isn't a Django user with a particular email address has nothing to do with whether that address can post to a list. The user can subscribe to lists or not. The user can manage her subscriptions for lists to which she is subscribed and can subscribe to lists or not as controlled by list settings. Basically, registering as a user allows you to authenticate as that user for the web UI only. If you wanted to separate these user registrations by vhost, you'd need to run separate Django instances for each vhost, but I don't see a need to do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Mark Sapiro

On 12/20/22 22:25, Odhiambo Washington wrote: > > In my case, running `mailman` without any arguments just makes it grok :) > > (venv) [mailman@gw ~/mm]$ mailman info ... > *config file: /opt/mailman/mm/mailman.cfg* That's because it first looks in the current directory for `mailman.cfg` and only if it doesn't find it there does it look in /etc/mailman3. >> Ultimately, when I did the import, there was only one email from the >>> archives that failed to be imported - which I honestly don't mind, but >>> maybe there is a solution for this >>> "'utf-8' codec can't encode character '\udcae' in position 331: >> surrogates >>> not allowed" ?? >> >> >> If you provide a copy of that message from the mbox, either on the list >> or to me directly, I'll investigate. >> > > A mbox file containing that email and the associated thread can be > downloaded from here: > https://webmail.kictanet.or.ke/~wash/chunk_7.txt.gz The offending message is multipart with an attached message/rfc822 part and that part has a preamble which in bytes is b'This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Windows\xae Internet Explorer\xae.' The '\xae' is an iso-8859-1 encoding for '®', but no charset is specified for this preamble so email message parsing ends up decoding those as surrogates '\udcae' which throws the exception when hyperkitty.lib.incoming.add_to_list() in trying to save the attachment does `att.set_content(content)`. Normally, when messages to be archived arrive from core via mailman_hyperkitty, the surrogates are replaced by email.utils._sanitize(), but this doesn't happen with messages from hyperkitty_import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

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

by Mark Sapiro

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > Hello. > > I tried to remove random email address signing ups (which I signed up > while testing) via admin panel. After removing I tried to sign up again, > but I am getting, > > 'A user is already registered with this e-mail address' You removed the user's subscription from the list, but you didn't remove the user from the system. Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. User's have addresses and a user or one of the user's addresses can belong to a list with one or more roles (non-member, member, moderator or owner) > Combing through the database, I found auth_user table in mailman3web db > still contain those mail address. How to wipe email address entirely > from the db so I can signup again without the 'forget password' method There are a couple of things. If you log in to the web UI as a django superuser, you can go to the django admin UI -> Users section and delete the User, but I think that will only delete the web user and not delete the user from Mailman core. You can also log in to the web UI as the user and go to <https://lists.mailman3.org/user-profile/delete>, but that again only deletes the web user, and if you could do that, you could just subscribe once you're logged in, so I assume that's what you want to avoid. I don't think there is a way for a user as opposed to a site admin to delete her user record from Mailman core and even for a site admin, there's no way in Postorius to delete a user from core. It has to be done via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 9/30/22 12:41, Andy Smith wrote: > > This just happened again. As a refresher, the issue I'm seeing is > that Mailman registers a bounce against addresses that aren't > subscribed, including addresses for the list itself and for the > -leave address that is in some footer text. > > Here's the bounce.log: > > Sep 30 17:12:25 2022 (8428) Member [elided1](a)[elided1].force9.co.uk on list users.mailman.bitfolk.com, bounce score = 1. > Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com > Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email mailto:[elided2]@gmail.com is not a subcriber of users.mailman.bitfolk.com > Sep 30 17:12:25 2022 (8428) Member [elided2](a)gmail.com on list users.mailman.bitfolk.com, bounce score = 1. > Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com > Sep 30 17:12:25 2022 (8428) Member [elided3](a)[elided3].org.uk on list users.mailman.bitfolk.com, bounce score = 1. > > I have elided parts of the email addresses of real subscribers. > > Attached is the actual non-delivery report from the MTA that > triggered this. In it I have done my best to elide the names and > addresses of real people, but nothing else. They match the same > elisions from the bounce log. What is your version of flufl.bounce? I made one change to your attached DSN. In the message/selivery-status part, I changed Final-Recipient: rfc822;[elided1](a)[elided1].force9.co.uk to Final-Recipient: rfc822;elided1(a)elided1.force9.co.uk and processed the message with flufl.bounce.scan_message() which returned the single address elided1(a)elided1.force9.co.uk. I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: import21 detailed usage instructions in 2024

by Mark Sapiro

On 6/2/24 4:28 PM, Keith Christian wrote: > 1 Soon, I will be executing the first test imports from > Mailman2.1 to Mailman3.9. > > 2 Planning to copy over the entire production Mailman2.1 to a new > directory structure on the Mailman 3.9 machine. > > 3 Expecting that all .mbox and .pkl files will be present and no > special work has to be done to bring them over will a "full" > mailman2.1 copy. That's correct. > 4 Can the import21 program find the mailman2.1 .mbox and .pkl > files on its own and process them? No. `mailman import21` needs to be given the path to the config.pck to import and hyperkitty_import needs to be given the path to the .mbox. > 5 Other than the mailman2.1 instance being shut down, any other > prep that needs to be done? Ideally there are no held messages or other moderator requests for the MM 2.1 list, i.e. deal with these before shutting down the list. If there is a MM 2.1 digest.mbox it needs to be moved and converted for MM 3 I have attached a bash script I use on mail.python.org to migrate lists. Paths and some other things are specific to that installation, but you may find it useful. It calls a move_digest script which I've also attached > 6 Any special command line parameters to be aware of for import21? Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Import Mailman 2.1 list data. Requires the fully-qualified name of the list to import and the path to the Mailman 2.1 pickle file. Options: -c, --charset TEXT Specify the encoding of strings in PICKLE_FILE if not utf-8 or a subset thereof. This will normally be the Mailman 2.1 charset of the list's preferred_language. -h, --help Show this message and exit. > 7 Is there a list of troubleshooting steps for commonly > encountered migration issues? Not that I'm aware of. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/22/20 12:21 PM, Ruth Ivimey-Cook wrote: > > The localhost address is coming in via the hosts file, which is a > relatively standard practice IMO. I could change it, but then perhaps > other things would not work. I would prefer to be able to specify what I > need. There are also things like systemd-resolvd which will do the > localhost-substitution for you even if /etc/hosts doesn't. I have done further testing. See my comment at <https://gitlab.com/mailman/mailman/-/issues/735#note_366074014>. You need to set hostname: in mailman.cfg to the actual external IP address of the Mailman host machine or to a name which resolves to that IP both internally and externally, and also set that host name/IP in the MAILMAN_REST_API_URL setting on the Postorius machine. > I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and > changing the cfg file hostname back to the full name of the host, and > that now works!! -- in that the problem I showed earlier is gone. Remove that patch and do the above. > However I then get another issue. From the mailman.log file I now see in > the last few lines. For clarity I've numbered them like this "{1}": > > {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" > "GNU Mailman REST client v3.3.1" > {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk > HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" > {3} [22/Jun/2020:00:58:24 +0000] "GET > /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > At this point the browser screen reports "Something went wrong" and the > message "HTTP Error 404: {"title": "404 Not Found"}" Make the above changes and see if that solves this. If not, let us know and we'll try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/23/22 07:41, Josef Dietl wrote: >> >> The issue here is accessing the hyperkitty API. The base URL for these >> accesses is configured in mailman-hyperkitty.cfg. From what I see here, >> that is something like `http(s)://host.example.com/hyperkitty/` If you >> append `api/` to that base URL and go there in a web browser do you get >> a page of documentation of the HyperKitty API? If so, then figure out >> why it works from a web browser and not when Mailman core does it. If >> you get the 403, figure out why. This is probably an nginx issue. > > Seems like an nginx issue indeed. However, I'm an apache guy, trying to re-educate myself on nginx. > OK, here's the result of changing mailman-hyperkitty.cfg from `http(s)://host.example.com/hyperkitty/` to `http(s)://host.example.com/hyperkitty/api/` Do not make this change in mailman-hyperkitty.cfg. That will produce 404's for sure. This was only a suggestion to try from a browser. > Yes, if I open things from the web browser, I do get the HyperKitty API doc. OK. That means you can access HyperKitty's API from a browser at `http(s)://host.example.com/hyperkitty/api/`. This is the same thing Mailman core is doing if `base_url` is set to `http(s)://host.example.com/hyperkitty/`, so what's the difference between Mailman core's access via mailman-hyperkitty and your's via the web browser. For further diagnosis, you might try `wget -O- http(s)://host.example.com/hyperkitty/api/` on the Mailman server. > With what follows below, I guess it's a timeout: Processing a message takes longer than rendering a HTML document. > > Jan 22 20:26:27 2022 (149435) ACCEPT: > <AM0PR04MB4785365CA1BB735884E149CEC25C9(a)AM0PR04MB4785.eurprd04.prod.outlook.com> > Jan 22 20:26:28 2022 (149439) HyperKitty failure on https://[FQDN]/hyperkitty/api/api/mailman/urls: Do not include the api/ in base_url. That was just for testing with a web browser or wget/curl. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Pd CRON mailman gatenews

by Mark Sapiro

On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read > with open(self._lockfile) as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' > —————————————————————————————————————————————————— > > CRON content: > —————————————————————————————————————————————————— ... > # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured > */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. > I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". > When I run "/usr/bin/mailman gatenews" by hand everything is correct. Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. > The questions I have are these: > We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". > What are they for? > Can we delete them? They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. > We have 2 files "master.lck..." dated from the day after tomorrow ! > What is this date? > Aren't these files the problem? Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

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

by Mark Sapiro

On 3/2/21 12:33 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 20:07 +0000, David Partain via Mailman-users > wrote: >> On Tue, 2021-03-02 at 19:56 +0000, David Partain via Mailman-users >> wrote: >> >> I assume this is because /usr/share/mailman3-web/manage.py, which >> has: >> >> '#!/usr/bin/env python' >> >> resolves to Python 2.7.17. >> >> Should I could try changing that to '#!/usr/bin/env python3' and see >> what happens? :) I could also uninstall python2 but that becomes >> more of a nail-biter... NO! Do not do that. >> I can report that the above doesn't help. Neither does just making >> /usr/bin/python link to /usr/bin/python3.6 >> >> I still get errors in mailman-web.log pointing to 2.7 as shown in my >> previous mail. > > If I force the issue by linking /usr/bin/python to /usr/bin/python3.6, > I start seeing: > > ModuleNotFoundError: No module named 'hyperkitty > > in mailman-web.log. > > I know next to nothing about python. Is > > pip install hyperkitty > > the right answer? No. > I have the following installed now: > > # dpkg -l | grep hyperkitty > python-django-hyperkitty 1.1.4-4 > python3-mailman-hyperkitty 1.1.0-4 > > but this version of Ubuntu has no python3-django-hyperkitty or I'd just > try installing that... This is all because you are using the Ubuntu 18.04 package which is about 4 years out of date and is from the era where HyperKitty, Postorius and django_mailman3 still ran under Python 2.1.7. Unless you want to remove the Ubuntu package and install everything with pip, you need to just stick with what you have that at least partly works and we'll try to determine how to fix the utf8mb4 issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: import21: ModuleNotFoundError: No module named 'Mailman'

by Mark Sapiro

On 7/28/19 4:18 PM, Christian Schwarz wrote: > > Most mailing lists can be imported successfully using the `import21` subcommand, as described in the docs. Good. > Some mailing lists fail with the following error: > > sudo -u list mailman import21 REDACTEDLIST(a)example.org /var/lib/mailman/lists/REDACTEDLIST/config.pck > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailman/commands/cli_import.py", line 64, in import21 > pickle_file, encoding='utf-8', errors='ignore') > ModuleNotFoundError: No module named 'Mailman' I know what's happening, but I need more detail to do more than guess at how to fix it. The issue is there is a Mailman 2.1 Mailman.xxx.yyy object in the config.pck file. My best guess is that the list's bounce_info is the culprit. The list's bounce_info is a dictionary with keys equal to member addresses and values equal to the Mailman.Bouncer._BounceInfo object representing that member's bounce info. So when import21 calls pickle.load to load the config.pck, there is a reference to one or more Mailman.Bouncer._BounceInfo objects, but pickle.load can't find the definition of that object and that raises the exception. As to how to proceed, there are a couple of ways. One is to fix import21 so it ignores this issue. I just reported <https://gitlab.com/mailman/mailman/issues/618> on this, but I'm not sure how to fix it. I don't think it will work to try the pickle.load and pass the ModuleNotFoundError exception because I think the rest of the pickled data won't be returned. It looks like you still have the MM 2.1 installation, so you could use either MM 2.1's bin/withlist or bin/config_list to set the list's bounce_info to an empty dictionary. and then use the updated config.pck for the import. This assumes that bounce_info is the issue. You can verify that there is a non-empty bounce_info dictionary with either bin/withlist or bin/dumpdb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Pb with archive display

by Mark Sapiro

On 5/5/22 08:02, Pierre Malard via Mailman-users wrote: > > Unfortunately we still don't have any archives... > > Here are the logs retrieved from the mailman.log logs: > May 05 15:59:42 2022 (579075) Exception in the HyperKitty archiver: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} > raise ValueError(result.text) > ValueError: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} > > And in mailman-web.log: > WARNING 2022-05-05 13:58:52,996 579167 hyperkitty.views.mailman Could not archive the email with message-id '<C7E61653-D399-466A-BEC3-CE61D567E870(a)teledetection.fr>': character with byte sequence 0xe2 0x80 0x99 in encoding "UTF8" has no equivalent in encoding "LATIN1" > > Is it a way? > > I don't understand the message about LATIN1. > It seems to me that UTF-8 was the encoding retained in Mailman. I too don't understand what's trying to encode as LATIN1. The particular byte sequence is a utf-8 encoding of right single quote (’) which has no LATIN1 equivalent, but there's not enough info in the logs for me to determine exactly what's going on. There is an issue with MySQL and derivatives if that's the database you are using. You need the MySQL encoding to be UTF8MB4. in the DATABASES definition in your django settings you want ``` 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings. ``` but that doesn't seem to be the issue here. I suspect this issue has to do with the particular message. When mailman-hyperkitty processes the queue and a queued message throws an exception, it just dies. You might try moving aside the first (in alphanumeric sequence) message in /var/lib/mailman3/archives/hyperkitty/spool and see if the remaining messages can be processed. If that works I would like to see that message's .pck file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Mark Sapiro

On 3/12/21 7:36 PM, John Covici wrote: > Hi. I am having a great deal of difficulty installing mailman3 using > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > mailman3. > > What I have done so far is to install the mailman3 packages from my > repository and got this: > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > version 3.3.2 (apparently the core), postorius version 1.3.3 and > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. Are these gentoo packages? If so, I have no idea how they are configured. > Now trying to read your documentation, it seems it wants me to > reinstall some packages using pip in the home directory of the mailman > user in a python virtual environment, that was the first thing. But I > would like to avoid multiple package managers wherever possible -- > gentoo is already a lot of maintainance without dealing with pip's > maintainance. The binaries also seem to be different from my gentoo packages. Our documantation generally covers installing from source. If you are installing gentoo packages, you should be looking at gentoo docs and going to gentoo for help. We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB. > So, how do I proceed with getting mailman3 up and working, configuring > the database, configs, etc and I guess after doing that upgrading > mailman2 and getting sendmail to interface properly with mailman3? Importing lists from Mailman 2 is done with the `mailman import21` command. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. Importing archives is done with the Django management `hyperkitty_import` command. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> For sendmail, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> -- 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

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 12/14/22 13:40, Jeremy Stanley wrote: > > Once these entries are automatically added by visiting that page, > they're all associated with the one "web host" ("site" in Django) we > have for the server, and now the list filtering functionality in > Postorius breaks and any of the vhosts all display the full set of > mailing lists on the server rather than only those associated with a > particular vhost (note that this seems to only be confusing > Postorius, Hyperkitty has them correctly filtered still). See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and also below. > Okay, so it looks like this is because the mail hosts are all tied > to the one web host. Yes. > We can create additional "sites" in the Django > admin UI and then switch the association of the mail hosts to those > distinct web hosts. But after doing so, the first vhost still seems > to show an unfiltered list of all lists in Postorius (Hyperkitty > continues to be fine), while Postorius on the other vhosts correctly > shows their filtered sets of lists instead. > > I also noticed when mailman-web is starting up, its log claims the > first site is being set as the "default domain," so have to wonder > if that's related to this behavior. Should we create an extra web > host to serve as the "default" so that all our typical vhosts get > the expected list filtering behavior, or am I completely off-base > and there's a much better approach I've missed? I'm not really sure what's going on here. You could try creating a dummy default host to see if that fixes the issue for you. There are subtle differences in the implementation between HyperKitty and Postorius that allow HyperKitty to work better, but it too will exhibit some anomalous behaviors. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/12/21 12:01 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> But whatever is listening on port 8001 is apparently not Mailman's rest >> server. What does >> ps -fww 14080 >> or whatever PID is currently listening on port 8001 show. > > UID PID PPID C STIME TTY STAT TIME CMD > list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 I had asked "What does ps -fwwa|grep rest show?" and it didn't find this. That was my error. I meant 'ps -fwwA|grep rest' >>> OK. >> Perhaps instead you should have >> uid: list >> gid: list >> in your uwsgi configuration if you don't already. > > Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. All the mailman processes should run as `list` and all mailman related things should be readable and writable by `list`. >>> I'm not familiar enough with this form of ProxyPass using sockets to >> understand what the localhost:8001 does in this context, but uwsgi >> should not be doing anything with port 8001. In a configuration using >> TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API >> server listens. uwsgi should receive connects in your case via the unix >> socket and then pass them to Django via the application in wsgi.py >> Also, you may want other paths proxied to uwsgi, namely at least some of >> hyperkitty, postorius, archives, accounts, admin and user-profile. > > Ok, I removed that port again, now it's exctly like in the automatically generated config file. > And you mean like > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Yes, I meant if you want those URLs to work, you have to pass them to uwsgi. You don't need all of them. `mailman2` and `postorius` are synonyms as are `archives` and `hyperkitty` However, you could try using TCP to communicate with uwsgi rather than a Unix socket. This means replacing uwsgi-socket = /run/mailman3-web/uwsgi.sock with uwsgi-socket = 0.0.0.0:8000 in your uwsgi.ini file and using directives like ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/django" "http://127.0.0.1:8000/django" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" in apache. I am not familiar enough with apache/uwsgi configuration to be of more help. Have you seen https://wiki.list.org/x/12812344 and have you asked Debian for help with their package. They are the ones who should be supporting it <https://www.debian.org/support>. -- 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: Moderate mails from owner

by Mark Sapiro

On 3/22/19 6:10 AM, Malcolm Austen wrote: > On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj > <maxking(a)asynchronous.in> wrote: >> >> "Default Processing" means the default pipeline defined in > > Thanks, I will do some (more!) reading. > >> List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This >> pipeline is >> system wide and is defined in source code, so it can't be customized by >> site administrator. > > Unfortunately, that is not available to list-owners on the system > concerned. Ancestry must have removed it. It wouldn't help you anyway. All it shows are the choices 'default posting pipeline', 'default owner pipeline' and 'virgin', not the contents. See <https://mailman.readthedocs.io/en/latest/build/lib/mailman/app/docs/pipelin…> for info on pipelines. Also, when we're talking about Default Processing in the context of moderation, we're not really talking about pipelines; we're talking about rule chains. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html> and <https://mailman.readthedocs.io/en/latest/src/mailman/chains/docs/moderation…>. This latter doc mentions 'defer' which is another name for 'Default Processing'. Also in the latter doc in the example under "Anne’s post to the mailing list runs through the incoming runner’s default built-in chain. No rules hit and so the message is accepted." you'll see Hits: Misses: dmarc-mitigation no-senders approved emergency loop banned-address member-moderation nonmember-moderation administrivia implicit-dest max-recipients max-size news-moderation no-subject suspicious-header The misses are the rules processed in the normal chain in order. When you set a (non-)member's moderation to Accept, at the appropriate (non)member-moderation rule, the rest of the chain is skipped and the message is accepted. If the(non-)member's moderation is Default Processing, that rule passes, but the remaining administrivia implicit-dest max-recipients max-size news-moderation no-subject suspicious-header rules are checked before the message is accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Mailman3 Issue with Sending Mail to Yahoo/AOL

by Mark Sapiro

On 5/12/21 7:47 AM, chris--- via Mailman-users wrote: > Hi everyone. I have a dedicated Ubuntu box that is running mailman3. I have a single email list on it. The subscriber base is about 350 users. There is a good chunk of these users that are aol.com or yahoo.com users. I've been getting complaints from the Yahoo people that mail is delayed at times, or messages that come out of order. > > Looking at the mailq on the box, I can see there are plenty of emails stuck in the queue. I have all sorts of messages like this ... > > > -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > 3576C540CB4 9917 Tue May 11 11:27:13 pcho-bounces(a)pchochat.com > (host mta6.am0.yahoodns.net[67.195.204.74] said: 452 Too many recipients tnmpmscs (in reply to RCPT TO command)) This one's easy to fix. In mailman.cfg set ``` [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 ``` This will provide potentially better bounce processing detection, but will ensure that each message from Mailman has only one envelope recipient. If you don't want the verping, you can set `max_recipients` in the `[mta]` section to a small number like 5 or 10. > (host mta6.am0.yahoodns.net[67.195.204.74] said: 421 [IPTS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to end of DATA command)) The above changes may help with this too, but depending on where your Ubuntu box is located, you may have other issues. Presumably you have a fixed IP address, but even so, if that address is in a netblock that looks like `home networks` it may get blocked by some providers for that reason alone. Also, others in this thread have mentioned Verizon. Verizon recently sold AOL/Yahoo to a private equity firm, Apollo Global Management. What that means for the new Yahoo is still unclear. Search the web for `verizon sells aol` for more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 1/6/22 2:40 PM, gordon(a)dickens.com wrote: > I performed a distribution upgrade from Debian 10 Buster (which runs mailman 3.2.1) to Debian 11 Bullseye (which runs mailman 3.3.1) with the command "apt-get full-upgrade -y" and everything apparently worked properly except at the end of the upgrade when the following error dialog was generated by the mailman3-web and mailman3-full post-installation scripts: > > Setting up mailman3-web (0+20200530-2) ... > Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. > dbconfig-common: writing config to /etc/dbconfig-common/mailman3-web.conf > dbconfig-common: flushing administrative password > sed: -e expression #2, char 77: unterminated `s' command > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess returned error exit status 1 > dpkg: dependency problems prevent configuration of mailman3-full: > mailman3-full depends on mailman3-web; however: > Package mailman3-web is not configured yet. > > dpkg: error processing package mailman3-full (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > mailman3-web > mailman3-full > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Now, every time that I execute "apt-get upgrade" then I continue to get the above error dialog. Also, the command "dpkg-reconfigure mailman3-web" generates this output: > > /usr/sbin/dpkg-reconfigure: mailman3-web is broken or not fully installed > > So, I am now stuck since apt-get is saying that mailman3-web is not configured yet, however, neither apt-get nor dpkg-reconfigure will successfully configure mailman3-web. > > Does anybody have any idea how to fix this? I would very much appreciate some suggestions. This is a Debian packaging issue. It looks like the underlying error is sed: -e expression #2, char 77: unterminated `s' command which is an issue in one of the installation scripts in the .deb for mailman3-web. Your best source of help for this is Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/16/23 10:12 AM, Helio Loureiro wrote: > Hi, > > Well... not that good. Now it is mailman3-web that doesn't work. > > mailman@new-machine ~ (v3.3.9)> source venv/bin/activate.fish > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web > > Type 'mailman-web help <subcommand>' for help on a specific subcommand. > > Available subcommands: > > [django] > check > compilemessages > createcachetable > dbshell > diffsettings > dumpdata > flush > inspectdb > loaddata > makemessages > makemigrations > migrate > optimizemigration > runserver > sendtestemail > shell > showmigrations > sqlflush > sqlmigrate > sqlsequencereset > squashmigrations > startapp > startproject > test > testserver This response indicates that `mailman-web` is not getting settings.py. Have you configured /etc/mailman3/settings.py? See <https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu…>. > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > System check identified no issues (0 silenced). > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate You should run `mailman-web migrate` not `mailman-web check migrate` plus others. See <https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi…> et.seq. but first you need the appropriate settings so `mailman-web` returns something like ``` $ mailman-web Type 'mailman-web help <subcommand>' for help on a specific subcommand. Available subcommands: [account] account_unsetmultipleprimaryemails [auth] changepassword createsuperuser [compressor] compress mtime_cache [contenttypes] remove_stale_contenttypes [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate optimizemigration sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver [django_extensions] admin_generator clean_pyc clear_cache compile_pyc create_command create_jobs create_template_tags delete_squashed_migrations describe_form drop_test_database dumpscript export_emails find_template generate_password generate_secret_key graph_models list_model_info list_signals mail_debug managestate merge_model_instances notes pipchecker print_settings print_user_for_session raise_test_exception reset_db reset_schema runjob runjobs runprofileserver runscript runserver_plus set_default_site set_fake_emails set_fake_passwords shell_plus show_template_tags show_urls sqlcreate sqldiff sqldsn sync_s3 syncdata unreferenced_files update_permissions validate_templates [django_q] qcluster qinfo qmemory qmonitor [haystack] build_solr_schema clear_index haystack_info rebuild_index update_index [hyperkitty] attachments_to_file hyperkitty_import hyperkitty_warm_up_cache mailman_sync update_index_one_list [postorius] mmclient reset_passwords [rest_framework] generateschema [sessions] clearsessions [staticfiles] collectstatic findstatic runserver ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Internal Server Error: Reattach this thread

by Mark Sapiro

On 10/25/22 17:08, cold00water(a)gmail.com wrote: > Hey. > > Looking at other code, "subject" is a method. > > I fixed it by correcting the code. > is this a bug? python version issue? > > * /opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py > > 411 @check_mlist_private > 412 def reattach_suggest(request, mlist_fqdn, threadid): > 413 mlist = get_object_or_404(MailingList, name=mlist_fqdn) > 414 thread = get_object_or_404(Thread, mailinglist=mlist, thread_id=threadid) > 415 > 416 default_search_query = stripped_subject( > # change: thread.subject to thread.subject() > 417 mlist, thread.subject()).lower().replace("re:", "") > > * /opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/models/thread.py > > 69 def __str__(self): > # change: thread.subject to thread.subject() > 70 return self.subject() Did you test this?, How? I.e. where you able to produce the error without your change and then verify that your change fixed it? The existing code works in all but rare situations, and I think those are due to the thread object being instantiated with missing arguments. In any case, your changes cause the ReattachTestCase.test_suggestions test in hyperkitty/tests/views/test_thread.py to fail as follows. ``` hyperkitty/tests/views/test_thread.py:66: in test_suggestions response = self.client.get(reverse('hk_thread_reattach_suggest', .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:742: in get response = super().get(path, data=data, secure=secure, **extra) .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:396: in get return self.generic('GET', path, secure=secure, **{ .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:473: in generic return self.request(**r) .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:719: in request self.check_exception(response) .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:580: in check_exception raise exc_value .tox/py39-django32/lib/python3.9/site-packages/django/core/handlers/exception.py:47: in inner response = get_response(request) .tox/py39-django32/lib/python3.9/site-packages/django/core/handlers/base.py:181: in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) hyperkitty/lib/view_helpers.py:137: in inner return func(request, *args, **kwargs) hyperkitty/views/thread.py:445: in reattach_suggest mlist, thread.subject()).lower().replace("re:", "") E TypeError: 'str' object is not callable ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 1/3/19 5:33 PM, kelly.close(a)lrewater.com wrote: > Thanks Mark. I keep coming back to this and checking it again and again. The two keys match, and there are no quotes on the api_key. > > This is what I thought the problem was from the start but I just can't see anything wrong with those two settings. I'm going to look again - maybe entirely re-type the lines - what if there is a trailing space or something... I don't think trailing white space on the api_key setting is significant, and whitespace following the trailing quote in the MAILMAN_ARCHIVER_KEY setting is not significant, but embedded whitespace in the key itself could be an issue. Possibly Mailman and/or Hyperkitty aren't getting this info from the files you think they are. The command that you use to start Mailman should have a -C option pointing to Mailman's config. That in turn has a [archiver.hyperkitty] section pointing to the Mailman Hyperkitty config. That in turn contains the api_key. Then whatever process you use to run the wsgi application will set DJANGO_SETTINGS_MODULE in it's environment to point to settings.py or whatever you call it (without the .py extension) and that in turn imports overrides from settings_local.py. You need to understand what the working directory is of the process that imports the DJANGO_SETTINGS_MODULE. If you need more info, you could try modifying hyperkitty/hyperkitty/views/mailman.py at around lines 64 - 68 to: if request.GET.get("key") != settings.MAILMAN_ARCHIVER_KEY: return HttpResponse( """<html><title>Auth required</title><body> <h1>Authorization Required</h1> {} != {}</body></html>""" .format(request.GET.get("key"), settings.MAILMAN_ARCHIVER_KEY), content_type="text/html", status=401) This should display the values that don't match as part of the error response. Note that this is Python and leading whitespace is significant and if you're reading this in HyperKitty, you won't see it unless you "display in fixed font" (the "A" icon), and even then, there may be line wrap. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: mailman 3.x upgrade and downgrade

by C. Souza

Ok, thanks! On Tue, Jul 12, 2022 at 1:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/22 9:35 AM, C. Souza wrote: > > > > I can't see the mistune package, maybe it wasn't a requirement for that > > version of mm3. > > > > 1 Package Version > > 2 ------------------- ---------- > > ... > > 39 HyperKitty 1.3.3 > > > Correct. It is not a requirement until HyperKitty 1.3.5 > > -- > 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/ >

2 years, 10 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 5:40 PM, Paul Arenson wrote: > >> Assuming MUA means a mail application. And if that mail application has no reply list function then the setting doesn't work. MUA means Mail User Agent which is another name for mail application, YES. > Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) > >> It is the presence of the >> List-Post: header in the message that allows the MUA to offer/process >> the "reply-list" function. > > Ok, I asked how to make it ANNOUNCE ONLY and you said to use "allow_list_posts is False" which is the same as "Include the list post header". Not exactly. You asked what settings were different between discussion style and announce only style. What I answered was that the only setting that differed as set by the style was what Postorius calls "Include the list post header". What I didn't say explicitly was that this is not sufficient to prevent posting to the list. > So does this mean that for a subset of users I cannot make it ANNOUNCE ONLY? And is it some other setting (send to moderator) that prevents it from being a DISCUSSION list? What exactly do you want? You found some info on configuring an announce only list and I referred you to a FAQ on that subject. Both of these do not directly address Mailman 3, but they do give useful information. I am going to stop guessing at what you want to accomplish, so tell me what you want to happen when someone sends a post to the list either from HyperKitty or by email. What should happen to the message? What if anything should be sent to the user? Should this behavior be the same for all users or just a subset. If a subset, how do you identify that subset and what should happen when others attempt to post? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: moving lists to another server

by Mark Sapiro

On 11/20/23 00:58, Odhiambo Washington wrote: > > What is the command to export the archive as a mbox from the DB? > I can't figure out which option it is by looking at 'mailman-web -h'. Normally you do this on the old server via the HyperKitty web UI which has download buttons which do things like https://example.com/archives/list/list@example.com/export/list@example.com.… or for a partial archive https://example.com/archives/list/list@example.com/export/list@example.com-… However, in your case I don't think you have the old installation working any more so the above won't help. > BTW, how will ' mailman addmembers' treat a file containing: > ``` > Firstname Lastname <email@address> > Onlyname <email2@address> > ``` Correctly. It will import email@address with display name = 'Firstname Lastname' and email2@address with display name = 'Onlyname'. > I have opted for the simple way to do this: > 1. Create the site in Django Admin and create/configure the list in > Postorius > 2. Add the members from the file dump, with delivery set to regular. > 3. Send the members an email informing them that they need to set their > delivery preferences. > > I am stuck on the issue of exporting the archives to mbox file as already > stated above. Perhaps you can export the mbox via the web UI on the old server or maybe temporarily create a second mailman-web on your server with the old mailman-web database and use that web UI. Otherwise, if you have a working mailman-web that can access this database, you could try something like ``` $ mailman-web shell >>> from hyperkitty.lib.compat import get_list_by_name >>> mlist = get_list_by_name('list_name_only', 'list_domain') >>> with open('output.mbox', 'wb') as fp: ... for email in mlist.emails.order_by("archived_date").all(): ... fp.write(email.as_bytes() + b'\n') ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Update a member's display_name

by Mark Sapiro

On 1/17/19 8:45 AM, Nick Wynja wrote: >> user_manager = getUtility(IUserManager) >> u = user_manager.get_user('aperson(a)example.com') >> u.addresses[0].display_name = "Anne" >> commit() > > It seems this method updates the display_name for the user across all lists. Is there a way to update just a single instance of "member" of a list rather than the site-wide user? > > I've tried this: > > mailman shell -l test(a)example.com > >>>> mem = m.members.get_member('a(a)example.com') >>>> mem > <Member: a(a)example.com on test(a)example.com as MemberRole.member> >>>> mem.display_name > 'Anne' >>>> mem.display_name = "Anne P" > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: can't set attribute That's because mem.display_name is a "calculated" attribute. The definition of the IMember class says > display_name = Attribute( > """The best match of the member's display name. > > This will be `subscriber.display_name` if available, which means it > will either be the display name of the address or user that's > subscribed. If unavailable, and the address is the subscriber, then > the linked user's display name is given, if available. When all else > fails, the empty string is returned. > """) and > subscriber = Attribute( > """The object representing how this member is subscribed. > > This will be an ``IAddress`` if the user is subscribed via an explicit > address, otherwise if the the user is subscribed via their preferred > address, it will be an ``IUser``. > """) So there is no member display_name per se. The display_name is the display_name of the associated IUser or IAddress, and these are global. The bottom line is there is not a way to update just a single instance of "member" of a list rather than the site-wide user or address? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Johannes Rohr

Am 09.01.23 um 06:30 schrieb Mark Sapiro: > On 1/8/23 01:37, Johannes Rohr wrote: >> >> Am 16.09.21 um 01:13 schrieb Mark Sapiro: >>> >>> Currently Mailman 3 does not support whitelisting the members of >>> another list. >> >> Is this still true in the current version? I have been using this >> quite extensively with mailman2, so loosing it is the one major >> drawback of the migration. > > > Yes it is still true. This is > https://gitlab.com/mailman/mailman/-/issues/794 Thanks! I assume, there is a reason why this cannot be easily implemented, else it would have been. Asking because I know a number of people would make extensive use of this in MM2. Johannes

2 years, 5 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 3/31/23 14:17, Andrew Hodgson wrote: > Hi. > > Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in ``` --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 @@ -2,13 +2,13 @@ import os import sys -sys.path.insert(0, '/opt/mailman/mm') +sys.path.insert(0, '/etc/mailman3') # The above line is required. The next line doesn't hurt, but it doesn't work # because the PYTHONPATH environment setting is processed by Python's setup # and must be in the environment when Python starts to be effective. -os.environ['PYTHONPATH'] = '/opt/mailman/mm' +os.environ['PYTHONPATH'] = '/etc/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' import django django.setup() ``` Also, look at this ``` # If we delete the Django user and there is a Mailman user with no memberships # shall we delete the Mailman user too. DELETE_MAILMAN_USER = False # Shall we delete the Django user if there is a Mailman user with no # memberships or only if there is no Mailman user. DELETE_DJANGO_IF_MAILMAN = True ``` and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/26/24 09:21, Elias Rudberg wrote: > > Yes, there are strange-looking long queries there at the times when > these errors happen. > > Here is an example of what such a request URL looks like, where I have > replaced some parts with [...] to avoid including anything sensitive: > > Request URL: > https://[...ip-address...]/mailman3/postorius/lists/?widget=[...]svg[...]onload=confirm[...]xss-widget[...]&height=[...]svg[...]onload=confirm[...]xss-height[...]&screen=[...]svg[...]onload=confirm[...]xss-screen[...]&pass2=[...]svg[...]onload=confirm[...]xss-pass2[...]&redirect_to=[...]svg[...]onload=confirm[...]xss-redirect_to[...]&items=[...]svg[...]onload=confirm[...]xss-items[...]&string=[...]svg[...]onload=confirm[...]xss-string[...]&hidden=[...]svg[...]onload=confirm[...]xss-hidden[...]&f=[...]svg[...]onload=confirm[...]xss-f[...]&step=[...]svg[...]onload=confirm[...]xss-step[...]&role=[...]svg[...]onload=confirm[...]xss-role[...]&preview_nonce=[...]svg[...]onload=confirm[...]xss-preview_nonce[...]&date=[...]svg[...]onload=confirm[...]xss-date[...]&event=[...]svg[...]onload=confirm[...]xss-event[...] I see similar ones from time to time. > I looked up the IP address that those requests come from (all seem to > come from the same IP address) and that corresponds to a hostname called > something with "scanner" that looks like it belongs to some > cybersecurity company. There are also many other requests from that same > IP address, including things like "GET /file://etc/passwd" and similar, > so it looks like someone is bombarding us with various weird requests as > a form of "scanning" where they are trying to find vulnerabilities. That > could also explain why we see those "Internal Server Error" errors > recurring every day, if they run that vulnerability scan daily. Yes, I think these are attempts to find vulnerabilities. > So maybe those strange request URLs that lead to the error messages > "[Django] ERROR (EXTERNAL IP): Internal Server Error" that we are > seeing, are constructed by someone who is actively trying to trigger bugs. I don't think this is a DOS attack or an attempt to trigger bugs. I think they are attempts to find and then exploit vulnerabilities. > But anyway, no matter what strange request URL comes in, I guess the > "Internal Server Error" indicates something going wrong in Mailman or in > Django, a bug in how the request is processed? I'm not certain, but I think it's a Django issue rather than a Mailman issue. In my case, I don't get that many and I just ignore them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

sorry, in this directory: /var/lib/mailman/var/logs Thanks El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > 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

7 years, 10 months

[MM3-users] Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/7/22 16:11, Philippe B wrote: > I think that your last sentence helped us figure out what's going on. > > When Mailman generates a moderation message "To: LIST-owner" it actually delivers it to the address(es) of the LIST's moderator(s), which makes sense. No, it delivers the message to the union of the sets of owner addresses and moderator addresses. > In all the cases where we've seen that behavior, it turns out that the list involved didn't have any moderator, and we have site_owner set to "mailman"... You don't need to have moderators. The owners get the message too. > However, the lists had an owner, and we're not seeing those moderation messages being sent to their owner (instead). Is that something that needs to be configured explicitly somewhere? The only things that might affect this are if Settings -> Automatic Responses -> Autorespond to list owner is Respond and discard message or if the owners delivery_status is other than DeliveryStatus.enabled. Note that finding an owner's delivery status is tricky. The owner can find it in Postorius by going to https://www.example.com/mailman3/accounts/subscriptions/ and clicking on the entry for the list with role owner. This delivery status is not the same as the delivery status for the same address with a member role if there is one. For an admin you could do ``` $ 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 >>> owner = m.owners.get_member('user(a)example.com') >>> owner.delivery_status <DeliveryStatus.enabled: 1> If you needed to set it here, you could do >>> owner.preferences.delivery_status = DeliveryStatus.enabled >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

Jan Eden wrote: > I tried setting permissions on /opt/mailman/fulltext_index to 777 > temporarily, but the issue remained (as expected). It occurs in the > Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > > if self.use_file_storage and not os.path.exists(self.path): > > > > os.makedirs(self.path) > > > where self.path is referenced, which is defined in line 110 (as part of > the __init__ function): > > def __init__(self, connection_alias, **connection_options): > > super().__init__(connection_alias, **connection_options) > > self.setup_complete = False > > self.use_file_storage = True > > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > > self.path = connection_options.get("PATH") > > > > Unfortunately, I cannot see where the PATH key for connection_options is > defined. It is defined in the HAYSTACK_CONNECTIONS dictionary in your Django settings.

2 years, 6 months

[MM3-users] Re: The email confirming the registration of an account on postorius is not correctly translated in Italian

by Mark Sapiro

On 7/30/20 9:43 AM, Massimo Zappalà wrote: > > Everything works, except for this: > > When I register a new account on postorius, he sends me a confirmation email totally in English, except the following final block which is sent in Italian: > > in my /usr/lib/python3/dist-packages/allauth/locale/it/LC_MESSAGES/django.po > > #: templates/account/email/email_confirmation_message.txt:7 > #, python-format > msgid "" > "Thank you from %(site_name)s!\n" > "%(site_domain)s" > msgstr "" > "Grazie da %(site_name)s!\n" > "%(site_domain)s" OK. > By carefully analyzing the same file .po, I notice that the Italian translation of the whole text already exists. > Why does the confirmation email arrive in English? > > #: templates/account/email/email_confirmation_message.txt:1 > #, fuzzy, python-format This is marked fuzzy so it isn't used. If you believe the translation is correct, remove the above line (or remove ' fuzzy,' from it) and then recompile the django.mo with msgfmt. Note that the current HEAD on github <https://github.com/pennersr/django-allauth/blob/master/allauth/locale/it/LC…> has the above line as just #, python-format > #| msgid "" > #| "User %(user_display)s at %(site_name)s has given this as an email " > #| "address.\n" > #| "\n" > #| "To confirm this is correct, go to %(activate_url)s\n" > msgid "" > "Hello from %(site_name)s!\n" > "\n" > "You're receiving this e-mail because user %(user_display)s has given yours " > "as an e-mail address to connect their account.\n" > "\n" > "To confirm this is correct, go to %(activate_url)s\n" > msgstr "" > "Ciao da %(site_name)s!\n" > "\n" > "L'Utente %(user_display)s di %(site_name)s ha registrato questo indirizzo e-" > "mail.\n" > "Per confermare, clicca qui %(activate_url)s\n" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/4/21 6:30 AM, Duane Raymond wrote: > FYI: in the mailman log was also the following traceback > > Mar 04 14:08:24 2021 (5044) Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/pipelines.py", line 50, in process > handler.process(mlist, msg, msgdata) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 83, in <genexpr> > recipients = set(member.address.email > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 239, in members > yield from self._get_members(DeliveryMode.regular) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 226, in _get_members > if member.delivery_mode in delivery_modes: > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 212, in delivery_mode > return self._lookup('delivery_mode') > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup > pref = getattr(self.address.preferences, preference) > AttributeError: 'NoneType' object has no attribute 'preferences' > Mar 04 14:08:24 2021 (5044) SHUNTING: 1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4 Assuming this relates to the missing messages, there is no issue with delivery to Mailman. This message is getting to Mailman but throws the above exception during processing and is shunted. You can examine this messages with `mailman qfile var/queue/shunt/1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4.pck` and similarly for other shunted messages. The issue here is Mailman is going through the roster of regular (non-digest) list members to find those with delivery enabled and it finds a member that has no associated address. Can you view the members of this list? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Add domain to Mailman, can't create list with that new domain

by Mark Sapiro

On 10/17/24 15:06, Andy Matthews wrote: > Hey Mark, I'm looking at the documentation here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > > Which seems to indicate that adding a domain via the CLI is as easy as: > > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('example.org') > > It's not until much further down the page that there's any reference to "committing" a change. But sure enough when I add the following three lines to the previous 4, I'm able to create a mailing list with staging.mydomain.dev using the REST API. > > from mailman.config import config > transaction = config.db > transaction.commit() I don't know how you are running these Python interactions, but if you are using `mailman shell` interactively, things like IDomainManager, and getUtility and lots of other things are imported automatically and commit() and abort() are also predefined. > I created an issue suggesting as much on GitLab: > https://gitlab.com/mailman/mailman/-/issues/1178 Also when using `mailman shell`, at startup it says: ``` 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. ``` I've seen issue #1178. The issue is actually more widespread than that. There are lots of things done in the Python snippets in the docs to support the fact that they are all actually run as doctests as part of our CI to ensure they are correct. In practice it is generally easier to run these in `mailman shell`. However, the docs themselves don't say that. We say a bit at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… but I don't know a good way to say that globally. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Mark Sapiro

On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about: > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run. > I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size. > $ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add. How exactly did you install Mailman? The document you reference gives alternatives. You don't say exactly what you did. > 2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup. It appears that no MTA is listening on localhost port 25. Is your MTA even running? It is extremely unlikely that this has anything to do with adding a termplate in Postorius. You might be better off installing Debian's 'mailman3-full' package <https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Mailman 3 - Header Filter

by Mark Sapiro

On 9/25/23 06:30, Henrik Rasmussen wrote: > > In my case I would be more interested in holding or discarding mails with subject 'Out of Office' if the mail would otherewise be send the to the list members due to a non-moderated list. > > I would emagine that the order of "check for member moderation" and header_matches would not be significant if holding or discarding the mail due to header_matches, am I right? 🤞🏻 No. It depends on what the check for member moderation rule does. If the post is from a non-member or from a member and the members moderation is Default Processing or if it is List default and the list's Default action to take when a member posts to the list is Default Processing, then the Header Filters will be applied. However, if the post is from a member and the members moderation is directly or via list default any of Hold, Reject, Discard or Accept, that is the action that will be applied. > If so, I would think that Header "subject:" or "subject" with Pattern "^(?i)(.*)autosvar(.*)" - without the double quotes - and Function "Hold for moderation" or "Discard" should either hold or discard any message with "Autosvar" (danish word for "Out of Office reply") somewhere in the subject, but that doesn't happen. What is the correct syntax? Do not include the : in the header name. Other than that, your pattern should be OK but the ^, the (?i) and the parentheses around .* are all unnecessary. > *) In a prevous mail I was told that ^ would tell Mailman that it is a regex. That is true for lots of things where either a string value or a regexp is acceptable such as the * these nonmembers entries, but the Pattern entry for Header Filters is always a regexp and is searched with re.search with re.IGNORECASE, so while your pattern above should work, a much simpler pattern is just "autosvar" (w/o the quotes). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 1/11/20 2:43 AM, Jim Ward wrote: > I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: > > 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. > 2) The 'Search Members' function appears to be limited to the email address only and does not include display name > > These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. Part of this is because of the architecture of Mailman 3. In mailman 2.1, we have lists and members of those lists and no connection between a member of one list and a member of another list, even if their email addresses are the same. Thus, a member of a list and that member's display name are things associated only with that list, and can be manipulated by the list admin. Mailman 3 is different. In mailman 3 we have users and addresses. A user has a display name and one or more addresses, one of which is preferred, and each address has a display name. These are independent of any list and belong to the user. Then, a list member can be a user, in which case, the address associated with this member is the user's preferred address and the display name is the user's display name (or maybe the display name of that address, I'm not sure). Or, a list member can be an address in which case, the member's display name is the display name associated with that address. Thus, in Mailman 3 the display name associated with a list member can be one of several, and these belong to the user, not to the list. As far as not searching display names is concerned, this is <https://gitlab.com/mailman/postorius/issues/378>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: hyperkitty: "incorrect string value" for botched utf-8 encoding

by Mark Sapiro

On 5/25/20 9:47 AM, thoralf via Mailman-users wrote: > hi, > > my hyperkitty installation (3.2.1 from debian buster) started to act up > recently with > > (1366, "Incorrect string value: '\\xF0\\x9F\\x99\\x82\\x0AA...' for > column `mailman3web`.`hyperkitty_email`.`content` at row 1") > > for every new mail that is about to be archived, i'll quote the full > error mail at the end of this mail. > > i traced the issue to a slighty smiling face (aka u+1f642) in this > rather interestingly encoded email: > > […] > Content-Type: multipart/mixed; > boundary="===============2457401976140816263==" > > --===============2457401976140816263== > Content-Type: multipart/alternative; boundary="5ecb6fd9_327b23c6_2042" > > --5ecb6fd9_327b23c6_2042 > Content-Type: text/plain; charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > kann halt NIE am mittwoch. viel spass =F0=9F=99=82 > […] > --5ecb6fd9_327b23c6_2042 > Content-Type: text/html; charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > <html xmlns=3D=22http://www.w3.org/1999/xhtml=22> > […] > <div dir=3D=22auto=22>kann halt NIE am mittwoch. viel spass =F0=9F=99=82<= > /div> > --5ecb6fd9_327b23c6_2042-- > […] > --===============2457401976140816263==-- > > … which still lingers around in > /var/lib/mailman3/archives/hyperkitty/spool . > > is this to be expected, or might it be a good idea to amend mailman3 / > hyperkitty to deal with this more gracefully? When HyperKitty gets an exception like this in archiving a message, it queues it in /var/lib/mailman3/archives/hyperkitty/spool and on every new post, retries the queued messages. This message fails again on retry and is requeued. How would you suggest this be handled more gracefully? The underlying issue has been seen before. The basic problem is in MySQL and MariaDB the encoding is utf8 which only accepts utf8 encodings up to 3 bytes. It needs to be utf8mb4 to accept characters outside the base plane. I know there is a thread on this somewhere, but I can't find it right now. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Sender: header

by Mark Sapiro

On 11/30/21 7:51 PM, Philippe B wrote: > MM2 adds the header "Sender: LISTNAME-bounces@DOMAIN" to messages sent to list members. > > That causes Outlook (among others?) to display the "originator" of a message from a REAL POSTER as: > > LISTNAME-bounces@DOMAIN on behalf of REAL POSTER <REAL.POSTER@DOMAIN> > > That phrasing helps identify instantly what list a message is coming from, when that list doesn't use a Subject prefix and when its address isn't in the To: or Cc: headers. (And it turned out that some of our list members were even relying on it to trigger security alerts!) Mailman 2's adding of a Sender: header is an artifact from a time when some MTAs would return bounces to the Sender:. I think yours is the first comment I've seen that actually likes the way Outlook renders it. Most want to know how to prevent that which is why MM 2 has an option to not add it. As far as triggering alerts or filtering is concerned, there are other headers in list mail that can be used for that purpose. > It doesn't look like there's any current MM3 setting that would accomplish the same result, so the question is: How difficult would it be to revive the Sender: header? By revive, do you mean add a feature in MM 3 to add a Sender: header. If so, you could submit a request at `https://gitlab.com/mailman/mailman/-/issues`. If you mean how difficult would it be for you to do it. here's a one line patch that will unconditionally remove any pre-existing Sender: header and add one with the list posting address. ``` --- a/src/mailman/handlers/rfc_2369.py +++ b/src/mailman/handlers/rfc_2369.py @@ -67,6 +67,7 @@ def process(mlist, msg, msgdata): ('List-Owner', '<mailto:{}>'.format(mlist.owner_address)), ('List-Unsubscribe', '<mailto:{}>'.format(mlist.leave_address)), ('List-Subscribe', '<mailto:{}>'.format(mlist.join_address)), + ('Sender', mlist.posting_address), )) if not msgdata.get('reduced_list_headers'): # List-Post: is controlled by a separate attribute, which is somewhat ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 12:32 AM, adam.heathcote(a)utas.edu.au wrote: > Hey there, > > We have a Mailman3 server with quite a few lists all running with no issues. > Recently I imported a list from our old Mailman 2 server which went fine. > > I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. > > The output of /opt/mailman/web/logs/mailmanweb.log is here: > > ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner > response = get_response(request) ... > TypeError: sequence item 1: expected str instance, NoneType found Was there more in the log? I.e., a line like The above exception was the direct cause of the following exception: followed by another traceback. If so, what was that? Is there anything in Mailman core's mailman.log? > I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? What do you get from Mailman's ``` mailman members -R owner your_list(a)your.domain ``` If this doesn't list you, try something like this: ``` $ mailman shell -l your_list(a)your.domain 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 your_list(a)your.domain mailing list >>> from mailman.app.membership import add_member >>> um = getUtility(IUserManager) >>> usr = um.get_user('adam.heathcote(a)utas.edu.au') >>> rr = RequestRecord(usr.preferred_address.email, usr.display_name, None) >>> add_member(m, rr, MemberRole.owner) >>> commit() >>> exit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did that but I don't have a maillog for today 07.24.2017 Is there another place to look for? El lun., 24 jul. 2017 a las 16:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 07:41 AM, Rafael Mora wrote: > > Ok, I ran 'mailman aliases', what should I do now? > > > Assuming mail delivery is not working, look in /var/log/maillog for > messages with timestamps around the time that the mail was generated. > Then try to figure out what they are saying. > > -- > 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

7 years, 10 months

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/11/21 4:18 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> You are in a better position to answer that than am I. >> What does sudo netstat -lntp show? > > A lot. But since most of that isn't relevant here: > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 14076/python3 > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 14080/python3 So some python3 process is listening on port 8001 > tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 20241/master > tcp6 0 0 :::80 :::* LISTEN 13882/apache2 > tcp6 0 0 :::465 :::* LISTEN 20241/master > tcp6 0 0 :::25 :::* LISTEN 20241/master > tcp6 0 0 :::443 :::* LISTEN 13882/apache2 > tcp6 0 0 :::587 :::* LISTEN 20241/master > >> What does ps -fwwa|grep rest show? > > root 15055 14843 0 12:58 pts/1 00:00:00 grep rest > > So whatever it's supposed to find, it's not there But whatever is listening on port 8001 is apparently not Mailman's rest server. What does ps -fww 14080 or whatever PID is currently listening on port 8001 show. >>> mailman3-web.service must also run as list. > > I changed that. It didn't like it. OK. Perhaps instead you should have uid: list gid: list in your uwsgi configuration if you don't already. > >>> So, what do you have in your apache config for proxying to uwsgi and >> what's your uwsgi configuration. > > lists-ssl.conf: > <VirtualHost *:443> > ServerAdmin admin(a)domain.de > ServerName lists.domain.de > > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass "/mailman3" "unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost:8001/" I'm not familiar enough with this form of ProxyPass using sockets to understand what the localhost:8001 does in this context, but uwsgi should not be doing anything with port 8001. In a configuration using TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API server listens. uwsgi should receive connects in your case via the unix socket and then pass them to Django via the application in wsgi.py Also, you may want other paths proxied to uwsgi, namely at least some of hyperkitty, postorius, archives, accounts, admin and user-profile. > </IfModule> ... > I guess with uwsgi config you mean the /etc/mailman3/uwsgi.ini file? > [uwsgi] > # Port on which uwsgi will be listening. > uwsgi-socket = /run/mailman3-web/uwsgi.sock > > #Enable threading for python > enable-threads = true > > # Move to the directory wher the django files are. > chdir = /usr/share/mailman3-web > > # Use the wsgi file provided with the django project. > wsgi-file = wsgi.py > > # Setup default number of processes and threads per process. > master = true > process = 2 > threads = 2 > > # Drop privielges and don't run as root. > uid = www-data > gid = www-data These should be 'list', not 'www-data'. That's your permissions issue on settings.py -- 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: Installing mailman 3

by Rafael Mora

Yes, that was the problem, DEBUG was set to True, then it was changing to filebased the EMAIL_BACKEND. But after turning DEBUG to False I'm not getting the HyperKitty UI formatted, why is that happening?? Thanks El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

7 years, 10 months

[MM3-users] Re: Is there an easy way to set Reply-To to a lists owner?

by Mark Sapiro

On 12/4/22 01:50, Martin Lorenz wrote: > > Now the admin of theses lists (who happens to be my wife) asked me, if it was possible to change the settings such that all replys to one of these lists can only be sent to herself (i.e. the owner address) instead of being held for moderation. > > I thought of setting Reply-To to something like <list-owner> by "simply" entering a Variable into this field, instead of using the admins/owners literal email-address. First of all, you can't really control where replies will go. This is dependent on the user's MUA and what the user does. However, you can set things so that replies will likely go where you want. Here are various options for the Postorius -> Alter Messages `Explicit reply-to address` and `Reply goes to list` settings. If the sender of all the posts to the list is the list owner, just set `Reply goes to list` to `No Munging` and a `reply` will go to the sender, but `reply-all` will go to the sender and the list, and if the user's MUA offers it, `reply-list` will go to only the list. To avoid the `reply-list` issue, set `Include the list post header` to `No` and to avoid the `reply-all` issue, set `Message Acceptance -> Require Explicit Destination` to `No` and post with the list address in Bcc:. If the sender is someone else, set `Explicit reply-to address` to `LISTNAME-owner(a)LIST.DOMAIN` and set `Reply goes to list` to `Explicit Reply-to set; no Cc added`. Also set `Include the list post header` to `No` and consider setting `Message Acceptance -> Require Explicit Destination` to `No` and posting with the list address in Bcc: as above. Note that `LISTNAME-owner(a)LIST.DOMAIN` is the list posting address with `-owner` added to the local part. This address forwards to the list's owners and moderators. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 6/6/23 07:58, Nelson Strother wrote: > > No errors are being recorded in the mailman log files. This is GNU > Mailman 3.3.8 via `pip install mailman` on Debian 5.10.179-1 > (2023-05-12) running on a shared system where VMware gives this server > enough cycles that `mailman start` and `mailman stop` each consume from > 20 minutes to an hour of wall clock time, so I do not issue those > commands recreationally, attempting to keep the system available for > users. What should I do to help understand the cause for these failures? If a runner has died, its death and a reason should be logged in Mailman's var/logs/mailman.log with a message similar to Master detected subprocess exit (pid: 8617, why: SIGNAL 15, class: in, slice: 1/1) This may not be the case if the runner is killed by the OS for an out of memory or similar reason. For this, look in syslog. `mailman stop` can take a long time because it is waiting for a runner to stop. See https://gitlab.com/mailman/mailman/-/issues/255 but that issue was fixed long ago. I don't understand why `mailman start` would take more time than `mailman restart`. In fact, `mailman restart` effectively does `stop` and `start`, but only for those runners which are running. Since you seem to frequently have missing runners, I suspect something like an OOM condition is causing the OS to kill them. Although, I wonder if you are correctly interpreting the logs. While the absence of the `retry`, `task`, `nntp` and `archive` runners might not be noticed except for messages not being archived, if either the `in` or `pipeline` runner is not running, no list posts will be processed. > Would not it be helpful for this limitation of restart to be included in: > mailman restart --help > with a suggestion to use `mailman stop` and `mailman start` instead? I have just filed https://gitlab.com/mailman/mailman/-/issues/1082 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

awesome! Thank you a lot! Am Mo., 8. Nov. 2021 um 17:37 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/8/21 1:03 AM, Stefan Bauer wrote: > > > > how can we configure mailman3, to use STARTTLS when dropping mails to > local > > postfix for final delivery? > > > Set `smtp_secure_mode: starttls` in the `mta` section of mailman.cfg. > See > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > -- > 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/ >

3 years, 7 months

[MM3-users] Re: Problems configuring hyperkitty

by Mark Sapiro

On 11/18/24 09:29, Alain D D Williams wrote: > > I am running Debian 12 - Bookworm and have installed the Debian packages. The > database is Mysql. This is not a virtualenv setup. There is no documentation in > the hyperkitty package so I am following: > > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html The primary support resource for Debian packages is Debian. See https://wiki.list.org/x/12812344 > I read the following: > > "The database can be created with the following command: > > django-admin migrate --pythonpath example_project --settings settings > " > > I assume that that will create some database tables. Hopefully this will have > been done by installing package python3-mailman-hyperkitty. > > • What database & tables will that be ? It would be really useful to be told so > that I can check. The database is configured in the DATABASES setting in your Django settings. The HyperKitty tables all have names beginning with `hyperkitty_`. > • The config file is: /etc/mailman3/mailman-hyperkitty.cfg > This does not contain any comment about databases. Where does hyperkitty get > its database parameters from ? Django, see above. > • I have several different maildomains each with several lists. Some lists in > different domains have the same name. Do I need a different > example_project/settings.py for each domain, if so what changes ? I can't really speak to Debian, but you should be using the Django settings provided as part of Django's mailman-web package, not the ones in hyperkitty/example_project/settings.py as those don't include settings necessary for Postorius. > One of the next things that I will need to do is to import archives from > mailman2. How does the command below change for the different domains ? > > django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] In the `-l ADDRESS` argument the ADDRESS is the fully qualified list address and includes the domain. > > Is there some better documentation that I have failed to find ? Ask Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Abhilash Raj

On Thu, Aug 6, 2020, at 6:12 PM, Mark Sapiro wrote: > Mark Sapiro wrote: > > On 7/28/20 5:40 AM, Brian Carpenter wrote: > > > > > > This is the client that I asking about in my post. > > > She said what I > > > did, did not work. This is what I did: > > > > > > Get into a venv as user mailman > > > > > > #mailman shell > > > from mailman.model.mailinglist import MailingList > > > mlist = MailingList('listname(a)listdomain.org') > > > mlist.emergency = False > > > commit() > > > ctrl-d (just to be on the safe side) > > I half understand why this didn't work. Instantiating the list via > ``` > from mailman.model.mailinglist import MailingList > mlist = MailingList('listname(a)listdomain.org') > ``` > for some reason (that's the half I don't understand) does not get the > actual list object so changes you make to it don't affect the actual > list. It is because when you simply instantiate that class, it will create a new model instance, that you would need to persist by adding to database using `store.add(mlist)`. If you instead want to read that instance from database, you have to do `store.query()`, which is what the `.get()` method of IListManager does. > In `mailman shell` you need to do > ``` > mlist = getUtility(IListManager).get('listname(a)listdomain.org') > ``` > `getUtility` and `IListManager` are in the namespace in `mailman > shell`, but outside of that, e.g. just in `python` in your virtualenv, > you also need > ``` > from mailman.interfaces.listmanager import IListManager > from zope.component import getUtility > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: User account issue after importing data from Mailman 2.x server

by Mark Sapiro

On 10/24/24 11:01, dgoldsmith--- via Mailman-users wrote: > We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. Mailman's import21 process creates Mailman users for the list memberships, but it does not create the Django user used for access to HyperKitty and Pustorius. Your users can't reset their Django (web UI) login password because they don't have a Django account. They need to `Sign up` rather than `Sign in`. > Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? It did create Mailman users, but these have nothing to do with the users that can log min to the web UI. It doesn't create these Django users. > To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Just tell the users to go to the web UI and `Sign up` rather than `Sign in`. Removing and resubscribing a user will not help. The users that are members of mailing lists are completely separate from the users that can log in to the web UI. This is in part due to the modular nature of Mailman 3 and the fact that a Mailman 3 installation doesn't necessarily even have a Django based web UI. You may also be interested in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: mailman_web/urls.py changes in Postorius 1.3.10

by Mark Sapiro

On 12/5/23 09:52, Lieuallen, Thomas Otis wrote: > The latest release of Postorius includes these lines in mailman_web/urls.py: > > > # Include alternate Postorius and HyperKitty URLs. > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > > It appears that these paths override the originals (/mailman3 & /archive). They were intended as optional additions, but it appears they do function as overrides for some purposes. > I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. This is apparently a side effect of this change that wasn't considered in making the change. The change was made because some docs and/or example projects used the /postorius and /hyperkitty URLs and some used the /mailman3 and /archives URLs. This was an attempt to make either set work. > If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). > > Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. > > One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? It was intended to just add the /postorius and /hyperkitty URLs as alternates. I had assumed the links on various pages would reflect the URL used to access the page, but this is apparently wrong. I could change the order of the path lines in the distributed urls.py, but at this point it just may cause more confusion. However, since the sample config at https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… shows only the /mailman3 and /archives URLs, I will change the order. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Handling of (un)subscribe mails for already (un)subscribed users

by Mark Sapiro

On 12/10/20 11:51 AM, Andreas Barth wrote: > Hi, > > I noticed that a mail to -subscribe for an already subscribed user > doesn't get any response (about line 225 in > mailman/src/mailman/app/subscriptions.py). Same but different for > unsubscribe for users not on the list. I tested and I see this, so there is a bug, but I don't know what the issue is. The code you point to should raise AlreadySubscribedError and <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> should catch it and report, but this doesn't seem to be happening.. Also, <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> should report an attempt to unsubscribe a non-member, but the issue here is <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/comman…> which supresses sending the response because it is redundant if the user gets a 'you have been removed' email, but in this case there isn't one. > I'd need these kind of mails however in hope that users complain less. > > Would that be generally interessting, and if so, any special > requirements for submitting patches, or should I just do that locally? These things should be fixed, but it's more involved than just a patch to fix the error. For all but trivial fixes, the workflow should be something along the lines of the following. There should be an issue on GitLab for the appropriate project; in this case at <https://gitlab.com/mailman/mailman/-/issues>. Then to develop a fix, there needs to be a fix, a test for the fixed code and a note in the NEWS.rst file about the fix. I generally prefer to start with a local clone of the GitLab branch and first create a test for the desired behavior. This test should fail. Then I create the fix, and now the test should pass. Finally, I create the NEWS item and commit those changes and create a merge request. -- 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

[MM3-users] Re: user mail not accepted

by Mark Sapiro

On 4/26/21 5:16 AM, Christian Stalberg via Mailman-users wrote: > I have a user whose moderation rule is 'Accept immediately' yet when they > send a message for distribution to the list, they only receive it and it is > not distributed via the list. Logfile entries below. Please advise. Btw I > have another list on this same instance which is running fine. Thank you. > > [26/Apr/2021:12:06:25 +0000] "GET /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=christian > %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1257 "-" "GNU Mailman REST > client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "PATCH > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=christian > %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1288 "-" "GNU Mailman REST > client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/requests/count?token_owner=moderato > r HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/held/count HTTP/1.1" 200 73 "-" > "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272/preferences HTTP/1.1" 200 295 > "-" "GNU Mailman REST client v3.3.2" These entries don't tell anything about a post to the list. They are all from Mailman's REST API relating to Postorius interactions with core. However the absence of messages like Apr 26 07:32:39 2021 (17860) ACCEPT: <message_id> and Apr 26 07:32:41 2021 (17857) HyperKitty archived message <message_id> to https://example.com/archives/list/list_adderss/message/message_id_hash/ assuming you are looking at the correct time span, says there wasn't an accepted list post. Mailman's smtp.log may have more info, but the complete, raw message that the user receives may be more 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, 1 month

[MM3-users] Re: Sending to mangled 'From' addresses.

by Mark Sapiro

On 5/31/24 22:23, hansen via Mailman-users wrote: > > Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. DMARC mitigation action ‘Replace From: with list address’ will also place the poster's address in Reply-To: (or Cc: depending on list configuration), so a simple `reply` from a reasonable MUA should go just to the poster. > For example, say the mail client captures my address as > > “Allan Hansen via <listname>” <listaddress> > > then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: > > “Allan Hansen via <listname>” > > and, to make it worse, the actual email address, <listaddress>, is often hidden. If this is the result of a `reply` and not `reply-all` the client is not behaving reasonably. > The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. That is a problem with the client, but I suppose such clients are not uncommon. > Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., > > "Allan Hansen via <listname>" You could add a header filter on the To header with a regexp like `^.*via <listname>` and the desired action. > Should I get onto the other list to request this as an enhancement? I don't think that's necessary in this case, as Header filters should do it. In general, the best way to request an enhancement is to file an issue with the appropriate GitLab project at `https://gitlab.com/mailman` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I'm logging with the mailman user and it says that it sent a confirmation email to my email account, but I don't see any activity in postfix with 'tail -f /var/log/maillog' command What do you suggest??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

7 years, 10 months

[MM3-users] Re: Mailman/Django-allauth integration with Yahoo

by Mark Sapiro

On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by Mark Sapiro

On 11/8/23 14:47, gordon(a)dickens.com wrote: > > Basically, it does not appear that mailman nor the runners are active and rebooting does not help. "/opt/mailman/venv/bin/mailman start" generates errors as follows: > >> Traceback (most recent call last): >> File "/opt/mailman/venv/bin/mailman", line 6, in <module> >> from pkg_resources import load_entry_point >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3248, in <module> >> @_call_aside >> ^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3223, in _call_aside >> f(*args, **kwargs) >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3261, in _initialize_master_working_set >> working_set = WorkingSet._build_master() >> ^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 617, in _build_master >> ws.require(__requires__) >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 956, in require >> needed = self.resolve(parse_requirements(requirements)) >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 815, in resolve >> dist = self._resolve_dist( >> ^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 856, in _resolve_dist >> raise DistributionNotFound(req, requirers) >> pkg_resources.DistributionNotFound: The 'mailman==3.3.5' distribution was not found and is required by the application First of all, when running /opt/mailman/venv/bin/mailman you need to specify the -C option with the path to mailman.cfg, i.e. ``` /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg start ``` Can you run the mailman command without a subcommand. I.e. ``` /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg ``` should just produce a list of subcommands. Does it do that or produce the same error as above? I don't understand the above error. I think the content of /opt/mailman/venv/bin/mailman should be ``` #!/opt/mailman/venv/bin/python # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) ``` Which doesn't correlate with the above traceback. What is yours? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

Guillermo Hernandez (Oldno7) wrote: > I thought I said it: I reboot this server everyday at 06:40 CEST time. > That's why I'm sure it's not an undetected problem for weeks. The lists > in this last upgraded server are with daily traffic. I'm suscribed to all. I've looked at this a bit further. Prior to Mailman core 3.3.4 we required aiosmtpd>=1.1. In 3.3.4 we required aiosmtpd>=1.4.1 and now we require aiosmtpd>=1.4.3. The code in aiosmtpd that triggers the issue in the socket module was added in aiosmtpd==1.3.1. So it is likely that your prior Mailman core version was <3.3.4 and your aiosmtpd dependency was <1.3.1, so the Mailman upgrade would also have upgraded aiosmtpd to a version which triggered the socket issue.

2 years, 2 months

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Mark: These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? --- George R. Kasica Phone: +1 414 732 8503 Fax: +1 206 374 6482 Owner Netwrx Consulting Jackson, WI USA gkasica(a)netwrx1.com http://www.netwrx1.com<http://www.netwrx1.com/> From: George R. Kasica <gkasica(a)netwrx1.com> Sent: Sunday, June 5, 2022 10:32 To: mailman-users(a)mailman3.org; Mark Sapiro <mark(a)msapiro.net> Subject: Re: [MM3-users] Re: Mailman3 Setup Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 11 months

[MM3-users] Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Mark Sapiro

On 6/26/23 11:00 PM, Allan Hansen wrote: > > I also see this in queue/shunt: > > mailman@list:~/var/queue/shunt$ ls -ltr > total 88 > -rw-rw---- 1 mailman mailman 7168 Feb 17 23:03 1676703781.903885+fdcba88c680f50a0799c672cd0abe82e4bfe19b3.pck > -rw-rw---- 1 mailman mailman 19821 Apr 2 07:08 1680444501.0831451+e110b8c5c20ba3f87c1cea1c5f38e74a6cf8f1c5.pck > -rw-rw---- 1 mailman mailman 19489 Jun 18 11:52 1687114364.41209+1684717da96ff76d1ce773a0cf39c5f8b63e9078.pck > -rw-rw---- 1 mailman mailman 20274 Jun 18 19:01 1687140067.64057+7f77c1ebca490831f58ef9cfde06109081a4e7d6.pck > -rw-rw---- 1 mailman mailman 20085 Jun 26 17:18 1687825091.8457294+478565324778f2eb6f0fecaeccbd29596edaef53.pck > > The three last entries coincide with the captured messages. I suggest you examine those with `mailman qfile` and remove any irrelevant or duplicate messages. If you have mailman.log from Feb or Apr, you could find the error that caused the shunting and maybe fix it. > Finally, in the captured message source (the last which was Cc'd to me) I do see this: > > Content-Type: text/plain; charset="iso-8859-8-i" > > Which matches the complaint in the mailman log. If you want to fix and unshunt any of these, you could do, e.g., in `mailman shell` (watch out for wrapped lines) ``` >>> import pickle >>> file = '1687114364.41209+1684717da96ff76d1ce773a0cf39c5f8b63e9078.pck' >>> with open(file, 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Content-Type', 'text/plain; charset="iso-8859-8"') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` > Another difference: > The posted message shows > Content-Transfer-Encoding: base64 > The shunted message shows > Content-Transfer-Encoding: quoted-printable That's not important. > My question thus changes to: > > a. Should she be doing something special when sending to the lists? Get her mail client to send utf-8 or iso-8859-8 encoded messages, not iso-8859-8-i. > b. If not, is my setup in need of change? See Steve's reply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Sort Lists in Postorious

by Simon Coggins

A feature request to this for me would be to search the lists. We have over 200 lists and it's hard to find the one you need to work on as an admin :) Sent from my iPhone On 1 Dec 2021, at 08:45, Mark Sapiro <mark(a)msapiro.net> wrote: On 11/30/21 1:26 PM, Jonathan Wright via Mailman-users wrote: > Is there a way to sort the lists displayed on the main page of Postorious? They are sorted alphabetically by list name. There's not an option for another sequence. -- 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/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

3 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/19/20 12:03 PM, Brian Carpenter wrote: > Hi Everyone, > > If I subscribed to a MM3 list with barn(a)emwd.com with the name of Barn > Quilter. It shows up in the member roster. So far, so good. I then > unsubscribe barn(a)emwd.com. It no longer shows up in the member roster. > So far so good. I then resubscribe barn(a)emwd.com with either no name or > Barn User and it shows up in the member roster as barn(a)emwd.com with the > name of Barn Quilter. Is this a known bug and has been fixed with the > latest release? I suppose it could be considered a bug, but what's happening is your initial subscribe created a user and and address and set the user's preferred address to the created address. It also set the display_name of the address and it subscribed the user to the list or possibly the address to the list depending on what actually did the subscribe. When the user/address was unsubscribed, it is removed from the list's membership and the list was removed from the user's memberships, but the user and address still existed. Then when you resubscribed, the existing user/address was made a member of the list, but not updated so the "new" display_name was ignored. I think this is also the case if the original address had no display_name. You could say this is a bug and the display_name associated with this new subscription should replace the prior one, but what if that address was subscribed to other lists and didn't want the display_name changed on those lists. Ideally (perhaps) there could be multiple address records with the same email address and different display_names, but address records are keyed by email address, so this can't be. One workaround would be for a user who wanted to have an address with different display_names for different lists to have multiple addresses like address+list1(a)example.com, address+list2(a)example.com, etc. Is this really an issue that should be fixed or just a curiosity? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Implicit Destination Meaning

by Mark Sapiro

On 2/8/21 6:41 PM, Brian Carpenter wrote: > I just migrated a MM2 list to MM3. The client had no problem sending > posts to his list with MM2. However when he posted to his MM3 list, it > showed up in the moderation queue: > > ============ > Your mail to 'dogs(a)lists.redacted.org' with the subject > > mailing list changes > > Is being held until the list moderator can review it for approval. > > The message is being held because: > > Message has implicit destination > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. > =========== > > Is there a List Setting somewhere that needs to be adjusted to allow > this sender to post without moderation? There are a few things going on here. First, the list setting is require_explicit_destination. This is in Postorius under Settings -> Message Acceptance. If this is False or No, the implicit destination rule will never hit, but clearly it is Yes/True and should have been imported from the 2.1 list so it was probably True there too. When True, it means the list posting address or an acceptable alias must be explicitly addressed (in To:, Cc:, Resent-To: or Resent-Cc: of the post. An acceptable alias is a literal address or pattern matching addresses. These are also in Settings -> Message Acceptance and should have been imported from MM 2.1. For example, if the list's posting address is list(a)example.com, but you can also post to list(a)lists.example.com, list(a)lists.example.com should be in acceptable aliases. The most likely explanation here is that the post is being sent to a subdomain which is not the list's canonical posting address or vice versa. The reason this worked in MM 2.1 but not in MM 3 is in MM 2.1 if the list name matched, the check passed even if the domains didn't, but that is not the case in MM 3. The solution is to add the 'other' addresses to Acceptable aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Only held_messages for 1 (of 3) list has "Mailman REST API not available" message.

by Mark Sapiro

On 1/7/22 4:51 AM, Duane Raymond wrote: > Thanks Mark. > > This sounds like a database problem. What's in Mailman >> core's var/logs/mailman.log ? > > > In the var/logs/mailman.log there was a permission error for the messages/ > store folders. I noticed that some of the mm file and directories were > owned by root vs 'mailman' user (what Brian uses when he set up the mm3 > server). So after resetting all to mailman (I believe others use 'list') `list` is used by the Debian/Ubuntu packages. We recommend `mailman`. These ownership issues are often caused by running Mailman core as `root`. This causes certain things to be created/owned by `root` and when Mailman core is later run as `mailman`, it can't access these things. To guard against this, Mailman core >=3.3.5 will refuse to run Mailman as `root` unless a `--run_as_root` option is specified. > Now I get the error below with the error from mailman.log. ... > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", > line 77, in _make_resource > resource['msg'] = msg.as_string() > AttributeError: 'NoneType' object has no attribute 'as_string' This is https://gitlab.com/mailman/mailman/-/issues/856, fixed in Mailman 3.3.5 by https://gitlab.com/mailman/mailman/-/merge_requests/819. You can apply this patch to avoid the issue. ``` --- a/src/mailman/rest/post_moderation.py +++ b/src/mailman/rest/post_moderation.py @@ -74,7 +74,15 @@ class _HeldMessageBase(_ModerationBase): # resource. XXX See LP: #967954 key = resource.pop('key') msg = getUtility(IMessageStore).get_message_by_id(key) - resource['msg'] = msg.as_string() + if msg is None: + resource['msg'] = """\ +Subject: Message content lost +Message-ID: {} + +This held message has been lost. +""".format(key) + else: + resource['msg'] = msg.as_string() # Some of the _mod_* keys we want to rename and place into the JSON # resource. Others we can drop. Since we're mutating the dictionary, # we need to make a copy of the keys. When you port this to Python 3, ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/30/22 08:22, Jacob Sievert via Mailman-users wrote: >> Yes they should. This is >> https://gitlab.com/mailman/mailman/-/issues/257 fixed in Mailman core >> 3.3.5. Also in Mailman 3.3.5 is a new Task runner that runs periodic >> tasks, one of which is to remove orphaned pendings. > Hmm our running system right now already was on 3.3.5 since a few days > after release. > But maybe all of those were still from before. Task runner cleans some things, but not all. ...>> # Prior to Mailman 3.3.5, some tokens for user confirmations were >> pended with >> # too long a lifetime. This script removes those pendings based on >> when they >> # were pended and the configured pending_request_life rather than their >> # expiration. > With the script we went down to around 16k entries in pendedkeyvalue > removed were the following: > expunged 6932 orphaned pended held messages When a message is held, two tokens are pended; one for the moderator and one for the user. Notification to the user doesn't currently include the user's token or instructions on removing the held post; that needs to be done, but the token is pended anyway. Prior to 3.3.5, when a held message was handled, the moderator's token was removed, but not the user's. That's what these are. > expunged 254 expired held messages > expunged 21 expired (un)subscription confirmations Prior to 3.3.5, some things were pended with excessively long lifetimes. The script expires these based on 3 days for user confirmations and 180 days for moderator actions. The above were older than that. > This shows that there were a lot of things in an unfinished state to my > understanding in our system. > For a time this system was running with less RAM than it should have > had. So maybe some of the problems came from there. These were all problems with pre 3.3.5 Mailman, not specific to your system. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Hyperkitty is not archiving due to 405 error - GET instead of POST

by Mark Sapiro

On 2/12/24 8:46 AM, Matthias via Mailman-users wrote: > Hi there, > > I am running mailman3 on Debian 12 - latest package (GNU Mailman 3.3.8 (Tom Sawyer)). > Message handling in general is working fine, but as soon as a message is released, archiving with Hyperkitty is not working, due to a 405 error: > --- > Feb 11 16:18:48 2024 (3479662) HyperKitty failure on http://lists.domain.tld/mailman3/hyperkitty/api/mailman/archive: (405) > Feb 11 16:18:48 2024 (3479662) Could not archive the message with id <170766472771.3479669.4791049109141956450(a)otherdomain.tld> > Feb 11 16:18:48 2024 (3479662) archiving failed, re-queuing (mailing-list jahrgang.domain.tld, message <170766472771.3479669.4791049109141956450(a)otherdomain.tld>) > Feb 11 16:18:48 2024 (3479662) Exception in the HyperKitty archiver: > Feb 11 16:18:48 2024 (3479662) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message > url = self._send_message(mlist, msg) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message > raise ValueError(result.text) > ValueError > --- I would expect to see the text from the requests.post result here. > > When tracing this back, even the frontend Nginx server receives a get in his logs, hence I assume that hyperkitty is really creating a GET instead of a POST request? > --- > 217.72.204.162 - - [11/Feb/2024:16:18:48 +0100] "GET /mailman3/hyperkitty/api/mailman/archive HTTP/1.1" 405 0 "-" "python-requests/2.28.1" I don't know what's going on here. The code is doing a POST <https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperki…>. If in fact HyperKitty is seeing a GET and therefore returning a 405, that explains the above traceback, but I don't know why that would be. You could always try adding additional logging to mailman_hyperkitty/__init__.py to log the entire result, but I suspect the issue is that there is a redirect somewhere in the path from the configured HyperKitty base_url (see mailman_hyperkitty.cfg) and the actual HyperKitty API that is redirecting the POST to a GET and also dropping the POST data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: spf/dkim/dmarc

by Odhiambo Washington

Domain vs subdomain. At least I never mentioned subdomain. On Wed, May 17, 2023, 21:50 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/17/23 07:20, Odhiambo Washington wrote: > > > > You can only have 1 SPF record. > > For a domain. But as Jeremy Stanley noted, mail.ccalternatives.org and > lists.ccalternatives.org are different domains and it is fine for each > to have its own spf record. > > -- > 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 odhiambo(a)gmail.com >

2 years

[MM3-users] Re: HTML header / footer template

by Mark Sapiro

On 06/18/2018 02:33 AM, Asaf Ohayon wrote: > I understand Mailman 3 doesn't want to support HTML Emails, > This is perfectly legitimate, sadly however, This is a requirement of my client, > Which is in this case the Ministry of Education of Israel. Mailman does support HTML email. Just adjust content filtering to not remove HTML and not collapse alternatives. What Mailman does not support (and which I think is what you want) is the addition of headers and footers either as text/html parts or inserted into text/html message bodies. The former would be fairly easy. Look at mailman/handlers/decorate.py. If the messages you are decorating are text/html or multipart/alternative or something more complex, the header and footer are going to be separate MIME parts anyway, so where we have > if len(footer) > 0: > mimeftr = MIMEText( > footer.encode(lcset, errors='replace'), 'plain', lcset) > mimeftr['Content-Disposition'] = 'inline' > payload.append(mimeftr) > if len(header) > 0: > mimehdr = MIMEText( > header.encode(lcset, errors='replace'), 'plain', lcset) > mimehdr['Content-Disposition'] = 'inline' > payload.insert(0, mimehdr) in two different places, just change the 'plain' arguments to 'html' and then the headers and footers will be added as text/html and can include html tags to be rendered. On the other hand, if what you want is to insert headers and footers at the beginning and end of an existing HTML body part, We will not make Mailman do that because it is very difficult to do it right. This is because just prepending or appending some additional HTML to an existing HTML part gives unpredictable results. You need to actually parse or render the existing HTML to determine how to add your additions and in complex cases even that may not render as you wish in all various MUA renderings. If you want to try for HTML what decorate does for simple plain text, you can try it and you may find it works for you, but it is way to fragile for a Mailman feature. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Mailman do not honor non-members moderation setting sometimes

by Mark Sapiro

On 6/16/20 1:28 AM, Alan So wrote: > Some of our users reported that their list do not honor the nonmembers moderation setting sometimes. We were not able to repeat the issue consistently earlier. Luckily, we found the following way to repeat the issue: > > 1) Create a new list with user(a)example.com as owner. (Ordinary disussion mailing list style) > 2) Change the list Settings -> Message Acceptance -> Default action to take when a non-member posts to the list: Discard > 3) Add a non-member user(a)example.com and change the moderation setting to Hold for Moderation > 4) Send an email to the list using user(a)example.com. > > The message is discarded instead of being held. The above can also be repeated with the list setting Default action to take when a non-member posts to the list: Accept immediately. The message sent from user(a)example.com is accepted instead of being held. So, it looks like that the non-members moderation setting is ignored for this case. > > Further study indicate that the issue did not happen if the owner is set to user(a)example.com *after* adding the non-member. It looks like that we can avoid the issue during list creation. However, the issue can also be triggered through other ways such as adding the non-member as member and remove. There are also ways to resolve the issue by removing all corresponding member, non-member, owner setting and add them back in the following order: non-member, owner. However, it does not always work and so I do not go into the detail at this moment to complicate the issue. This is a known issue. See <https://gitlab.com/mailman/mailman/-/issues/659#note_270261964>. When the same user/address has both non-member and owner roles, setting moderation for the non-member in Postorius actually sets moderation for the owner which is meaningless because the owner role is never checked for moderation. Since the reference above is obscure, I have created https://gitlab.com/mailman/postorius/-/issues/436 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: share directories between postfix and mailman 3

by Mark Sapiro

On 1/22/24 13:05, Thomas Schachtner via Mailman-users wrote: > Hi there, > > But that's not the full deal. Postfix needs access to some hashed > configuration files containing the transport maps and the domains of the > mailman installation, and mailman needs the contents of the postfix > configuration file. Why do you think Mailman needs the contents of the postfix configuration file.. I don't think so. > As a quick and dirty solution, I've established a process which > periodically copies the /var/lib/mailman3 directory from the mailman box > to the postfix box using rsync. It appears you are using the Debian/Ubuntu package or at least have configured `layout: fhs` in the `[mailman]` section of mailman.cfg. This is OK, but in any case, all Postfix needs is /var/lib/mailman3/data/*. > But I would like to have a more professional solution, like a directly > shared directory between both. > I did not yet find any suggestions on how to achieve this. Are there any > best practices recommendations? > I already tried sharing the directories using sshfs, but that did not work. > > I connected the remote directory postfix.example.com:/var/lib/mailman3 > to my local directory /var/lib/mailman3 using > > sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 I would suggest the opposite. I.e. on the postfix machine ``` sshfs user@mailman_machine:/var/lib/mailman3/data /var/lib/mailman3/data ``` > This seemed to work pretty fine, as all files and directories seemed to > be available, but when starting mailman 3, the following error message > was shown: > FileExistsError: A race condition might have happened. /var/lib/mailman3 > actually exists and is not a directory. > > Any idea why this message is shown? Possibly because the uid and gid of /var/lib/mailman3 on the postfix machine do not map to the appropriate Mailman uid and gid on the mailman machine. > So, is it a bad idea to use sshfs? If you do it the other way, it might work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 12/28/24 05:19, monochromec via Mailman-users wrote: > Following the root cause analysis which Tobias started all those weeks ago we (the admin team behind the installation) are still struggling with the following phenomenon: messages on average take more than 24 hours to be processed, more precisely, the average lifetime of a pickled message object in `/var/lib/mailman3/queue/pipeline` clocks in at around 26 hours). This issue is with Mailman core's pipeline runner. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil… for an overview of message handling and queues in Mailman core. It seems that the pipeline runner(s) are taking an inordinately long time to process a message through the pipeline of handlers causing the pipeline queue to become backlogged. > Couple of stats of the installation: standard installation from Bookworm OS repos, Hyperkitty as archiver and Postorius as web frontend as explained above, running Python 3.11.2 from the standard systemd service as packaged with the Bookworm deb file. All backends (Core + Hyperkitty) are supported by Postgres version 15+248. The MTA is a standard Postfix installation, again from OS packages. The primary support for Debian packages is Debian. See https://wiki.list.org/x/12812344 > The underlying VM has 7 cores with just under 24 GB of main memory. This production instance is handling less than 130 mailing list (MLs) with an average of less than 10 postings per day per ML. CPU core utilisation hovers around 50% with the lion share allocated to the four pipeline runners as part of the MM configuration. This is an average of less than 1 message per minute. Processing a message through the pipeline should take nowhere near a minute. Possibly there is an issue in the rfc_2369.py handler. This handler communicates with HyperKitty via mailman_hyperkitty to obtain values for the List-Archive: and Archived-At: headers added to the message. Possibly there is some configuration issue with mailman_hyperkitty that causes these queries to take a long time and possibly eventually time out. Are there any `Connection to HyperKitty failed:`, `HyperKitty failure on ...` or `Invalid response from HyperKitty` type messages in mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/26/20 9:12 AM, Odhiambo Washington wrote: > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: >> >>> There is still some confusion on my part about the directives in the file >>> so allow me to seek some clarifications. >>> >>> The following are the contents of a file I have created and placed in my >>> Apache Includes/ directory. >>> I was hoping that with it, I can now access http://lists.my.server/mm3 >> and >>> get the UI. >>> >>> <CUT> >>> >>> # Global section >>> WSGIDaemonProcess mailman-web display-name=mailman-web >>> maximum-requests=1000 umask=0002 user=mailman3 \ >>> group=mailman3 >>> >> python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 >>> \ >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var >>> WSGIRestrictSignal Off >>> >>> <VirtualHost *:80> >>> ServerName lists.my.server >>> ServerAdmin odhiambo(a)gmail.com >>> >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in >> the >>> # provided example so I kept it. I also made changes to WSGIDaemonProcess >>> # based on my own mod_wsgi experience elsewhere.) >>> >>> ErrorLog /var/log/myserver-error.log >>> LogLevel debug >>> >>> # This goes in the VirtualHost block for the domain. >>> >>> # Mailman 3 stuff >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this >>> directory supposed to be and what/who creates it and with what >> permissions?* >> >> >> It is created/updated by the mailman-post-update script based on CONFDIR >> and STATIC_DIR. >> > > The fact that I have run the mailman-post-update script and these > directories aren't created means there is a problem in my setup, yes? If your mailman-post-update script is essentially the same as <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and it ran successfully, it would have created opt/mailman/mm/static and populated it. What was the output when you ran it? > Yes, I have these files: > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > /opt/mailman/mm/settings.py > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > /opt/mailman/mm/settings_local.py Is there an empty /opt/mailman/mm/__init__.py file? > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > confusion with the instructions at some point in the reading > of some documentation previously (in my previous attempt last year!) and > had noted that in my NOTES. I'll change this once things get clear for me. > Also, the fact that one of the init scripts > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > in your "reflection" page was calling sudo :) It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user as it should. Have you set USER=mailman3 in yours? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: moving individual list to different domain

by Mark Sapiro

On 3/21/23 06:21, Johannes Rohr wrote: > Dear all, > > on mailman2 it was possible to move a list to a different domain within > the same mailman instance. > > I have found no information on how the same can be accomplished on > mailman3. > > Is this possible at all? In mailman 2.1, a list was identified by its name only without the domain and those names had to be globally unique. A site could be configured to support multiple virtual hosts and a list had a host_name attribute which could be changed if desired to assign the list to a different virtual host, but there couldn't be two lists with the same name even if they had different host names. Mailman 3 is different. In order to remove the restriction that list names (without the domain) had to be globally unique, in MM 3 the domain is part of the list name. I.e., we can now have list(a)example.com and list(a)example.net as two distinct lists in the same installation. Suppose we want to rename list(a)example.com to list(a)example.net. This becomes involved in Mailman 3 because it affects not only Mailman core, but also mail delivery and archiving. Furthermore, the list with fqdn_listname list(a)example.com has the list_id list.example.com. If we change the fqdn_listname to list(a)example.net, the list_id should remain list.example.com per RFC 2919 Sec. 4. <https://www.rfc-editor.org/rfc/rfc2919>. We can just change the list's mail_host attribute via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or via a database query, but this leads to confusion. I.e., a URL like https://example.com/mailman3/lists/list.example.com/ will still work but https://example.com/mailman3/lists/list@example.com/. To avoid this, we could also change the list_id, but we can't do that via REST as it's a read-only property, and changing the list_id says this is really a new list, not the same list with a new name. Also, none of this addresses archiving. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: An archive/read-only list on a full setup?

by Mark Sapiro

On 4/11/23 09:36, Andreas Schamanek wrote: > > I have a working full installation of mailman3, postorius and hyperkitty > (on Debian 11). Now I wanted to host the archive of a remote list, and I > am wondering how to do this properly. > > After I found no documentation and no posting I simply created a list in > mailman3 with only 1 dummy member. The list address is subscribed to the > actual remote list. So, messages arrive and are archived. But that's not > optimal because hyperkitty thinks it's a normal list where it should be > read-only and do not allow subscriptions etc. > > What's the proper way to set up a hyperkitty-only list? There really isn't one as HyperKitty is intended to archive Mailman lists, however, it is possible to have a list in HyperKitty without a corresponding Mailman list. Thus, in your case you could just remove the Mailman 3 list you created and leave the HyperKitty list. Then you have an issue with posts, so you can keep sending the posts to be archived to the prior list address, but arrange for the incoming MTA to pipe mail to that address to a process. That process would do the following. Add a Unix From_ line at the beginning of the message and write the result to a temp file. Invoke a command like django-admin hyperkitty_import --no-sync-mailman --since 1990-01-01 \ -l list(a)example.com /path/to/the/tempfile where list(a)example.com is the actual HyperKitty list. This will archive the message. The addition of a Unix From_ line is to make the message file look like a mbox. Since there is no Mailman list, attempts to post or reply directly from HyperKitty will fail, although such attempts using email software will probably succeed in archiving the mail, and mail directly to that list address will be archived, but such messages won't go to the remote list. This may not be any better than what you're currently doing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Filter who can send on mailman3 list?

by Marcus Granath

Mark Sapiro wrote: > and to create a non-member for no-reply(a)abc.com and set it's > moderation action also to Defer or Default Processing." Thanks Mark Sapiro, now I got the "Moderation Action" set correct for the real users. BUT, I'm sorry to say that I'm still confused regarding how to add the "non-member" user ("no-reply(a)abc.com") - can you please guide some more here also? ;-) The whole idea (the Use Case) here is that we want our list to be an "announcement" list that will send announcement and the subscribers should not be able to send announcements themself - and usually the "announcements" are sent out with an e-mail address (i.e "no-reply(a)abc.com") that I just "dress" with a "special" name and "no-reply" address.. ;-)

4 years, 2 months

[MM3-users] Re: /hyperkitty/list/ shows "example.com" / mailman3 archives not updated

by Mark Sapiro

On 5/17/20 6:05 AM, patrick-mailinglists(a)whonix.org wrote: > /hyperkitty/list/ shows "example.com". Not the actual domain name that I configured. How can I fix this? Ensure that your actual domain is listed in the Django admin interface under Sites. Then ensure that your SITE_ID setting in your Django settings is correct. This is tricky because the site id might not be what you expect. You have to look in your database at the django_site table[1]. This table contains one row per site with columns id, domain and name, and the id values don't necessarily match what you'd think from looking at Sites in the Django admin interface. > I would not mind too much about hyperkitty showing "example.com". But the more important issue is that mailman3 archives are not updated. Therefore I guess it's a symptom of a more important issue. I doubt that these things are related. > E-mails to the list are delivered to e-mail subscribers, though. Seems only the web part is broken. What's in Mailman's log (var/logs/mailman.log) and are the messages all queued in var/archivers/hyperkitty/spool? If so, mailman-hyperkitty can't communicate with hyperkitty. Ensure that the settings in mailman-hyperkitty.cfg are correct. base_url: needs to be a URL that can access hyperkitty and api_key needs to match the MAILMAN_ARCHIVER_KEY setting in your Django settings except that it's quoted in the Django settings and not in mailman-hyperkitty.cfg. > Using Debian buster mailman3 packages. In configuration folder /etc/mailman3 I cannot find any textual string saying "example.com". > (`grep -r -i example /etc/mailman3`) > Therefore I don't know where mailman3 gets "example.com" from. Please see <https://wiki.list.org/x/12812344> [1] other ways to get this are a) increment the SITE_ID setting until you find the one that works or b) in a django admin shell do from django.contrib.sites.models import Site for site in Site.objects.all(): print('id: {}, name: {}, domain: {}'.format( site.id, site.name, site.domain)) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 1: ordinal not in range(128)

by Mark Sapiro

On 10/13/20 1:11 AM, r.woithe(a)callassoftware.com wrote: > Hello, > System: > Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0] > > all this runs on Ubuntu 20.04. > Our mailman3-web.log file is full of this error.Traceback: > > 00:00:17 [Q] ERROR reincarnated pusher Process-1:731365 after sudden death > 00:00:17 [Q] INFO Process-1:731366 pushing tasks at 3061233 > Process Process-1:731366: > Traceback (most recent call last): > File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap > self.run() > File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run > self._target(*self._args, **self._kwargs) > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 300, in pusher > task = SignedPackage.loads(task[1]) > File "/usr/lib/python3/dist-packages/django_q/signing.py", line 28, in loads > return signing.loads(obj, > File "/usr/lib/python3/dist-packages/django_q/core_signing.py", line 38, in loads > return serializer().loads(data) > File "/usr/lib/python3/dist-packages/django_q/signing.py", line 44, in loads > return pickle.loads(data) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 1: ordinal not in range(128) > > Is there a patch or workaround for this error or we are the one and only? This is a qcluster issue. Without knowing what it is that qcluster is looking at that is causing this, I have no idea what the problem is. You could try disabling qcluster. You probably have something like ``` Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } ``` in settings.py. You can comment out or remove this or I think you can just put `del Q_CLUSTER` in settings_local.py. Possibly this will avoid the error or move it somewhere else where we can get more information. Possibly you can also get more information on the error by implementing a simple error reporter for qcluster. See <https://django-q.readthedocs.io/en/latest/errors.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

YEEEES! At last!!! I can see the web UI. Now I´m getting this message in the web UI: Something went wrong Mailman REST API not available. Please start Mailman core. Where do I configure the REST API ????? Thank you El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:27 PM, Rafael Mora wrote: > > > > it says it needs whoosh > > > > How do I install that? on env2 with python2 or env with python3 ??? > > > In env2 do 'pip install whoosh' > > -- > 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

7 years, 10 months

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Franklin Weng

Yes, it is checked. Mark Sapiro <mark(a)msapiro.net> 於 2019年10月30日週三 11:19 寫道： > I haven't read this thread in detail. I've been off line for 3 days due > to a Public Safety Power Shutoff, but my first question is if you go the > the Pustorius web UI for the list(s) and look at Settings -> Archiving > -> Active archivers, is hyperkitty checked? > > -- > 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/ >

5 years, 7 months

[MM3-users] Re: Shorted Subjects in Mailman

by Mark Sapiro

On 7/26/22 03:44, Stephan Krinetzki wrote: > Victoriano Giralt wrote: >> On mar, 2022-07-26 at 10:09 +0000, Stephan Krinetzki wrote: >>> Hi, >>> Hi, >>> i tried now with a Postfix 3.x -> Mailman >>> Postfix has en extremely useful setting called debug_peer_list where >> you can list addresses of machines whose messages you are interested in >> and the level of detail can be set with debug_peer_level. this will >> result on very detailed logging of the SMTP conversation. >> But, before resorting to this very invasive method, I'd put messages on >> the HOLD queue and inspect them with postcat, before releasing them to >> be passed to Mailman. this way, you will be able to see if the subjects >> are cur "before" reaching Mailman. >>> Original to Mailman: https://pastebin.com/c4BHeEkJ >>> Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV- >> LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?= >>> After Recieving: https://pastebin.com/JG0NKbjq >>> Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV- >> LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?= >> Both of then show the same Subject: header. > > In https://pastebin.com/c4BHeEkJ, Line 79+80 it says > > `Subject: [SAV-LINUX] Notice from Sophos Anti-Virus on server.example.com > [DEMO1]` In the original message you posted at https://pastebin.com/c4BHeEkJ, the continuation line `[DEMO1]` is not indented and is thus not a continuation of the Subject: header but is a separate line. It appears that several other continuation lines are also not indented, so I can't tell what the original message to Mailman actually looked like. However, I did a test injecting directly to Mailman a message with ``` Subject: [SAV-LINUX] Notice from Sophos_Anti-Virus on server.example.com [DEMO1] ``` on a German language test list with subject prefix [Janinsliste] and I get the same result, I.e. the RFC 2047 encoded ``` Subject: =?utf-8?q?=5BJaninsliste=5D=5BSAV-LINUX=5D_Notice_from_Sophos=5FAnti-Virus_on_server=2Eexample=2Ecom?= ``` so this is definitely a Mailman bug (or a bug in the underlying Python email package. Thank you for the report. I have created https://gitlab.com/mailman/mailman/-/issues/1021 for this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Newbie hyperkitty question

by Mark Sapiro

On 1/11/22 8:27 AM, Stephen Daniel wrote: > Mailman users -- > > I am setting up a new mailman3 installation, and this is my first > experience with the suite. All of the software is up and running, but I > cannot tell if hyperkitty is actually running. In Postorius, in the list's `info` view can you click the Archives button and see archived messages? That's HyperKitty. If the messages aren't there with the hyperkitty archiving option enabled, check `mailman.log` for why. Also do messages from the list have an Archived-At: header? > When I look at my test mailing list, two archive options are available, > hyperkitty and "prototype", and both are enabled. I can see that my email > is being archived, but I think "prototype" is what is doing the archiving. > I see that a test message will end up in > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > and nowhere else. This suggests that "prototype" is archiving, but > hyperkitty is not. No this says the prototype archiver is working. It says nothing about Hyperkitty. > So, this opens up a raft of questions on hyperkitty: David Newman has answered some of this, but ... > - How do I tell if hyperkitty is actually running? It doesn't actually run. it is a Django web UI and a web API that serves things on request. > - Does hyperkitty have a web-UI for admins or users? How would I access > it? See above. > - I can not find any documentation on hyperkitty, other than > installation instructions and change logs. Does documentation exist? No, not really. > - How do I set policies on how long archives are kept? > - Assuming I want to back up my archives, what do I need to back up? Messages are kept forever unless you do something to delete them. HyperKitty's messages are stored in the database configured in the DATABASES setting in your Django settings. How you backup the database depends on the database manager. You already found the prototype archiver's messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 1/6/22 3:25 PM, gordon(a)dickens.com wrote: > > How do I uninstall the Debian version and then reinstall with the venv and web instructions so that all of my mailing lists and configuration data are preserved? I may elect to go that route if I can preserve all of my mailing list and data and you think that would be a quicker route to a solution. Is there a simple way to do this? It's probably not "simple", but here's how I would do it. First, follow https://docs.mailman3.org/en/latest/install/virtualenv.html to install Mailman in a virtualenv. You can use `list` as the Mailman user rather than `mailman` if you like. The doc uses Postgreql as the database manager, but you want to use whatever the current DBM is because you will want to use the existing database which is where all the list configuration, membership and archives are. One gotcha here is the instructions tell you to create /etc/mailman3/mailman.cfg and the Debian package already puts its mailman.cfg there. The Debian mailman.cfg may actually be appropriate although it puts things in different places, e.g. /var/lib/mailman3 instead of /opt/mailman/mm/var. The Debian package puts its Django settings in /etc/mailman3/mailman-web.py and the virtualenv doc puts them in /etc/mailman3/settings.py. You need to reconcile the differences keeping in mind that the recommended settings.py imports most settings from the mailman-web project and only contains things you want to change locally. The basic idea is you want the virtualenv install to use the existing databases and /var/lib/mailman3 stuff so you preserve all your existing list stuff. It probably involves several gotchas that might be difficult to resolve if you are less than intimate with the details of a Mailman installation. I actually spun up a small Ubuntu 20.04 droplet and installed the mailman3-full package to see what things looked like, but I destroyed it without examining the contents of some of the files or I might know more. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Hyperkitty using wrong email address in archive view

by Mark Sapiro

On 5/16/23 01:42, peter(a)chubb.wattle.id.au wrote: > Hi Folks, > I notice that for people with multiple email addresses, the email > address that appears as the 'FROM' address in the hyperkitty > archive is not the primary address, nor is it the address that the > email actually came from, but the address that was created first. > (Hyperkitty version 1.3.7) Where exactly do you see this address? Normally, if the From: header of the mail contains a display name, it is that name which is displayed as the author of the email. The display is only an address if the From: header of the mail had no display name or if it had a display name which was an email address as in From: user(a)example.com <user(a)example.com> > When I click on that from address in the archive view, I see all > the email addresses for the user -- these do not match up with the > ones in the django admin screen from .../admin/account/emailaddress/ Because they are not the Django user's email addresses, they are the Mailman user's email addresses. > When I see 'User profile for Fred Frog' > it shows obsolete addresses (not subscribed, not in the Django > profile for the user). Again these are the Mailman user's addresses. The Mailman users are listed at the Users tab on the top Postorius nav bar. > How can I as administrator get rid of bogus addresses? Or do I > have to ask each user to do this? The user can do it at https://example.com/accounts/email/ but the admin can't do it from Postorius. A site admin can do it via REST or `mailman shell`. > and how can I ensure that the email address displayed in the > archive is the primary address, not some address that no longer > works? Again, where do you see this? You may want to download that thread and see what that shows as the From: header of the email. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

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

by Mark Sapiro

On 9/22/23 04:47, Andrew Hodgson wrote: > > Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. > > However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. There is only one DSN that mentions several users (I haven't received that, but I don't need it). Mailman will process that as a bounce for each mentioned user. Now, when that results in delivery being disabled for the users, the admin receives a separate notice for each user. Each notice should have the DSN attached, but the issue is when the first notice is processed, the saved DSN is deleted from the message store, so it isn't available for the subsequent notices. This is now https://gitlab.com/mailman/mailman/-/issues/1101 > The message returned from Google was: > > user(a)gmail.com > 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' > 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' First, these appear to be due to some issue between the Server at PAVPR08MB9257.eurprd08.prod.outlook.com and the Server at gmail-smtp-in.l.google.com rather than gmail actually rejecting the message. Second, these are delayed bounces. PAVPR08MB9257.eurprd08.prod.outlook.com has been retrying the message for some time (perhaps as much as 5 days) and has finally given up and returned the bounce. Thus, you will probably see more of these from older messages as they finally bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Recently active discussions - Hyperkitty

by Mark Sapiro

On 5/31/24 13:06, Sam Darwin wrote: >> Are there messages with Date: headers in the last month? > > Well, there are definitely many messages from the last month. > > Hyperkitty, for each message, shows in the upper-right hand corner of the message "30 May 2024" "29 May 2024" "20 May 2024 3:00pm" and so on. Each message has a date shown. Those dates should be the ones used for recent threads. > "Threads by Month" is populated with messages from the last month. > "All Threads" is populated with messages from the last month. > However, "Recently Active Discussions" is empty. > > That is not conclusive regarding "Date: headers". But wouldn't "Threads by Month" use the same date information? Yes. Perhaps the hyperkitty recent_threads_cache job can fix this, but it is one of the jobs run daily by cron (assuming cron is running them) so after 24 hours, it should have run. > By the way, during the import "Message 04b901d993ca$d6cf3180$846d9480$(a)gmail.com failed to import, skipping" and "psycopg2.OperationalError: SSL connection has been closed unexpectedly". I'm guessing that was one message reported on two lines with the psycopg2... line indented 4 spaces. > However, the import continues past those errors. For example: Yes, that's a report that the one message with Message-ID: <04b901d993ca$d6cf3180$846d9480$(a)gmail.com> failed to import, but it doesn't affect the rest of the import. > It all eventually completes with exit code 0. Generally, successful. So it's unclear if a skipped message is the cause. It isn't, but the "psycopg2.OperationalError: SSL connection has been closed unexpectedly" message is curious. I would find that message in the mbox file and try to run the import again with a mbox containing just the one message with a --since option early enough to not skip it and also the --no-sync-mailman option to avoid that time consuming process which only will update HyperKitty's Sender record for this sender with Mailman core's user_id if it hasn't already been done for this sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, I got postfix installed and I can use the command mail to send emails. The thing is that mailman can't send the confimation mail yet, where should I look for the error?? Thanks El mar., 25 jul. 2017 a las 16:14, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:43 PM, Rafael Mora wrote: > > Ok, should I install the SASL authentication daemon saslauthd and start > it? > > > Probably not. > > If you are trying to configure Postfix to send via a remote server, see > <http://www.postfix.org/SOHO_README.html#client_sasl_enable>. > > -- > 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

7 years, 10 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 1/6/22 10:56 AM, jdanitxu(a)gmail.com wrote: > Hi, > we are writing from the NGO Engineering Without Borders - Spain. > After having migrated from mailman2 to mailman3 in a server with Debian 11, our domains are like these: > https://listas.isf.es/mailman3/ > https://listas.andalucia.isf.es/mailman3/ > https://listas.aragon.isf.es/mailman3/ > ... > I have set FILTER_VHOST = True and restarted postorius (systemctl restart mailman3-web), but when we enter in every URL, we see all the lists. Any hint to search? How did you install Mailman. If you are using the Debian packages, they are out of date. I'm not exactly sure the state of Postorius in them. The latest Debian mailman3-web package is 0+20200530-2 which may or may not include https://gitlab.com/mailman/postorius/-/merge_requests/500. What is your Postorius version? if it is less than 1.3.3, FILTER_VHOST doesn't work. Even if it is 1.3.3 or newer there is an issue with FILTER_VHOST. Namely, Postorius doesn't filter lists based directly on web domain. It filters based on the email host associated with the web host. There are two possibilities. If more than one domain has the same web host but different email hosts, no filtering is done. If domains with different web hosts have the same email host, all the lists with that email host will be shown. In short, FILTER_VHOST only works well with Postorius if each web host domain has a unique email host. I'm guessing that in your case, the email host for all three domains is `isf.es` so all lists are shown. > P.S: apart from this conversation, I suggest to include in documentation related to migrations the fact that is important to have 'charset': 'utf8mb4' if MariaDB/MySQL is used, in order not to get migration errors doubt to encodings. We had 75 GB of mbox messages and some of them have had trouble doubt to not setting it before. I think this should be fixed in Mailman core 3.3.5 which defines the charset and collation for many columns/tables as utf8mb4 for MariaDB/MySQL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Email verification

by Allan Hansen

Yep. That did it! Thank you! Yours, Allan Hansen hansen(a)rc.org > On Feb 9, 2020, at 13:41 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/9/20 1:29 PM, Abhilash Raj wrote: >> >> Finally, if you go into the Django’s admin interface, https://example.com/admin, you’ll find an EmailAddress table, where you can find and manually verify the user’s email address (check box to select “verified” and hit save). > > > Note that you need to click the user's address in the list to get the > page where you can verify it. > > -- > 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/

5 years, 3 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/4/20 12:31 AM, r.woithe(a)callassoftware.com wrote: > Hello, > every night at 00:00 i get an email by mailman3: > > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/django_extensions/management/commands/runjobs.py", line 34, in runjobs > job().execute() > File "/usr/lib/python2.7/dist-packages/hyperkitty/jobs/sync_mailman.py", line 37, in execute > sync_with_mailman() > File "/usr/lib/python2.7/dist-packages/hyperkitty/lib/mailman.py", line 147, in sync_with_mailman > sender.set_mailman_id() > File "/usr/lib/python2.7/dist-packages/hyperkitty/models/sender.py", line 57, in set_mailman_id > mm_user = client.get_user(self.address) > File "/usr/lib/python2.7/dist-packages/mailmanclient/client.py", line 192, in get_user > 'users/{0}'.format(address)) > File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/connection.py", line 99, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1616, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1358, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1314, in _conn_request > response = conn.getresponse() > File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse > raise ResponseNotReady() > ResponseNotReady > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > START TRACEBACK: > END TRACEBACK I'm partly guessing, but this may be a REST timeout. What Mailman core version is this? the version affects what the REST server is. > Therefor i would like to know can i neglect this message ? Or is this message a hint for an Error i should investigate and looking for a solution ? Archived messages have a `mailman_id` which is Mailman core's `user_id` for the user that posted the message. The job itself runs through all the archived messages and finds those which have a null `mailman_id` and attempts to get the `user-id` from core and set the `mailman_id`. Normally, I think messages with null `mailman_id` would only be messages added with hyperkitty_import as opposed to normally archived posts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: How to set up mailman 3

by Mark Sapiro

On 03/25/2017 04:23 PM, David Krantz wrote: > > I did get things working with the bundler at last. Quite tricky and I have > deactivated archival. But I suspect that I should retrace a bit of that > work and upgrade to the latest versions. I miss a few functions from > mailman2, especially setting a limit for message size to discourage sending > larger files to the list. I also notice that there are no modbits per user > that I can reach from the web as admin. See <https://wiki.list.org/x/17891998> for help in upgrading your bundler install. The lack of the ability to set a member's moderation option from the web UI is fixed in versions later than installed by bundler. Also see <https://gitlab.com/mailman/postorius/issues/127> A list's message_size can't currently be set in Postorius. File an issue at <https://gitlab.com/mailman/postorius/issues/new>. >> Where did you find out about the bundler? I'd like to make sure we steer >> people to the current best recommendations: > > The documentation can be found on several places. The one that is best > formatted is this one. I used a worse formatted version of the same text > but right now I cannot find the link. > > https://mailman-bundler.readthedocs.io/en/latest/ > > I notice that you changed the text on the githlab project. Better. > > Now I have no idea of how upgrading the different components. I might start > from scratch although it probably should be possible to upgrade the parts. > The best option is probably to switch to mailman2, but that has > disadvantages when handling lists for multiple domains if I am correctly > informed and I already have a few domains... See <https://wiki.list.org/x/17891998>. > I also found that sending mails manually (telnet to port 25) with no > headers other than "Subject:" causes the "Held messages" tab to crash with > a 500-error. Log below my signature. This is fixed: <https://gitlab.com/mailman/mailmanclient/merge_requests/16>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: Problem replying via Hyperkitty

by Mark Sapiro

On 7/26/22 07:39, Jeff wrote: > I am finally getting around to revisiting the problems I have been having with replying or posting through the web of my Mailman 3 installation. Posts or replies simply disappear. Here is the Django log section from when I did a test post today: > > [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b/addresses HTTP/1.1" 200 824 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 1195 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org HTTP/1.1" 200 480 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname(a)lists.domain.org/config HTTP/1.1" 200 3878 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org/member/address%40domain.com HTTP/1.1" 200 544 "-" "GNU Mailman REST client v3.3.3" These definitely look like messages from mailman.log, not Django's log. There should be a message like Jul 26 17:53:33 2022 (2868) ACCEPT: <165888320457.2073.7552187924254439941(a)msapiro.net> preceded by a GET for the poster and followed (not necessarily immediatly by a message like Jul 26 17:53:34 2022 (2865) HyperKitty archived message <165888320457.2073.7552187924254439941(a)msapiro.net> to https://msapiro.net/archives/list/list@example.com/message/FF35XYJNXTCDX5FW… The last message above may be the GET for the poster, but if the others are missing, it's not surprising as the message wasn't sent. There may be something useful in Django's log. This is the file defined in the LOGGING dictionary in the settings file as ['handlers']['file']['filename']. Normally, nothing is logged there for a web reply, but some error might be logged there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

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

by David Partain

On Tue, 2021-03-02 at 13:54 -0800, Mark Sapiro wrote: > On 3/2/21 1:43 PM, Mark Sapiro wrote: > > Unless you want to remove the Ubuntu package and install everything with > pip, you need to just stick with what you have that at least partly > works and we'll try to determine how to fix the utf8mb4 issue. > > > In that vein, you need to remove any settings_local.pyc files and > restart uWSGI or whatever provides the Django wsgi interface in your > system. and see if that helps. > Hi, I removed /usr/share/mailman3-web/settings_local.pyc quite some time ago, have restarted both mailman3 and mailman3-web numerous times since then, and today I restarted uwsgi this morning. No new settings_local.pyc has yet been created. Ideas..? Cheers, David

4 years, 3 months

[MM3-users] Re: clarifying configuration

by Mark Sapiro

On 6/30/20 11:29 AM, trewtus+200629maitr(a)gmail.com wrote: > Hey Team, > I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg > > [logging.template] > level: debug > > But that doesn't work for me. For example, after using that `mailman conf` doesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add > > [logging.smtp] > level: debug > > Invoking `mailman conf` will reflect that new loglevel. The settings in the logging.template section set defaults for the other logging.* sections. In particular, the logging.debug section sets `level: info` so setting [logging.template] level: debug will not affect the setting for logging.debug. See mailman/config/schema.cfg which is augmented by mailman/config/mailman.cfg and by your own mailman.cfg. > This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing. > > For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the `mailman conf` output. Why would that be? Because you have installed the Debian/Ubuntu package and that setting is specific to that package and probably only defined in their local mailman.cfg. The reason you don't see it in `mailman conf`, is it's broken. Without a `-s/--section` argument, it only lists sections defined in schema.cfg. See <https://gitlab.com/mailman/mailman/-/issues/736>, <https://gitlab.com/mailman/mailman/-/merge_requests/666> and <https://pythonhosted.org/lazr.config/lazr/config/docs/usage.html>. If you do `mailman conf -s logging.debian` you'll see it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: mailman3-web and the django middleware problem

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 4/25/24 14:01, Thomas Stein wrote: >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >>> >>> I don't know how things are arranged in the Debian/Ubuntu package, >>> but you may have a settings.py which at the end does something >>> like ``` try: from settings_local import * except ImportError: >>> pass ``` If that is the case, adding the above snippet to the end >>> of settings_local.py should work. This has been reported to Debian and is fixed upstream in the Debian repositories -- see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062707 It should hit a sefver soon, as it was uploaded yesterday. I don't know how soon after that it'll hit the Ubuntu repos. Peter C

1 year, 1 month

[MM3-users] Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 18:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > > > What I called "local admin" should have > > rights to add and remove members of, say, the poodle-regionA mailing > list. > > > By "local admin", do you mean "list owner", i.e., a list owner should be > able to see her own "hidden" lists. > > Is that what you mean, or to you envision some new category of user that > has more access than a list owner? > > -- > 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/ > I mean "list owner"

7 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Yes I did ran it in the env2 python2 virtualenv, it says: ERR_CONNECTION_REFUSED I stopped the firewalld service and it's still refused I installed uwsgi, should I put the config inside mailman.cfg?? El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 01:36 PM, Rafael Mora wrote: > > > > I visited http://192.168.1.42:8000 in my browser and I could not see the > > web UI. > > > What did you see? > > Did you run the Django web server? In your Python 2 virtualenv? > > python manage.py runserver > > -- > 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

7 years, 10 months

[MM3-users] Re: max_delivery_threads

by Sven Buesing

Hi, thank you for the clarification. Are there other ways to speed up the sending of personalized emails? Regards, Sven -----Ursprüngliche Nachricht----- Von: Mark Sapiro [mailto:mark@msapiro.net] Gesendet: Dienstag, 15. Oktober 2019 17:47 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: max_delivery_threads On 10/15/19 12:29 AM, Sven Buesing wrote: > Hi, > > we are currently running mailman version 3.3.0. > We want to enable max_delivery_threads - we want to send personalized mails > (To: ), and we hope that threading would speed things up - but it seems this > option has no functionality despite being documented in the schema.cfg. It is documented in schema.cfg, but it has never been implemented. -- 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/

5 years, 7 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Fri, Dec 30, 2022 at 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/30/22 03:12, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Try adding lists.kictanet.or.ke to Chosen sites along with > >> mm3-lists.kictanet.or.ke > > > > > > Even with that added, still same error. > > > Did you run `django-admin migrate` after uncommenting > 'allauth.socialaccount.providers.twitter', in your settings? > I always do whenever I change anything in settings. (venv) [mailman@gw ~/mm]$ /opt/mailman/mm/bin/django-admin migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. (venv) [mailman@gw ~/mm]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Crash while importing archives

by Mark Sapiro

On 7/7/20 7:42 PM, Mark Dadgar wrote: > This is actually an mbox file generated by mailman3. > > (venv) mailman@mail:/opt/mailman/mm$ /opt/mailman/mm/bin/django-admin hyperkitty_import --since 2020-02-19 -l trackjunkies(a)pdc-racing.net /temp/archive/trackjunkies-new-1.mbox > Importing from mbox file /temp/archive/trackjunkies-new-1.mbox to trackjunkies(a)pdc-racing.net > \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 381, in execute_from_command_line > utility.execute() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 375, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 323, in run_from_argv > self.execute(*args, **cmd_options) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 364, in execute > output = self.handle(*args, **options) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 327, in handle > importer.from_mbox(mbfile) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 152, in from_mbox > for msg in mbox: > File "/usr/lib/python3.8/mailbox.py", line 109, in itervalues > value = self[key] > File "/usr/lib/python3.8/mailbox.py", line 73, in __getitem__ > return self.get_message(key) > File "/usr/lib/python3.8/mailbox.py", line 781, in get_message > msg.set_from(from_line[5:].decode('ascii')) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 27: ordinal not in range(128) > > mailman 3.3.1 / core 3.1 > > Easy fix? I’m missing about 10 days' worth of archives as a result of this. There is a message in your mbox file with a '^From ' separator with non-ascii in the remainder of the line. This may be an unescaped '^From ' in a message body or an actual '^From ' separator. First get your mbox and find the last message successfully imported in the archive before this one. You can delete everything up to through that one. Then you can fix the bad message or just delete it from the remaining mbox and run hyperkitty_import start=... with this mbox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Two Questions: One General, the Other Specific

by Mark Sapiro

On 2/26/21 9:10 AM, David Wilson wrote: > > *Is there another site that might best communicate the future goals, > plans, objectives, and time frames for mailman3 or is the status of the > project at the state of being primarily reacting to problems, as > evidenced in this problem solving forum, at least as it seems to me, > with no offense meant or intended?* We are a small project with few volunteers and no paid staff. While we would like to be able to devote significant time to future goals, plans and objectives, often we only have time and resources to devote to fixing immediate issues. The way to get issues/objectives/etc. on our radar it to post them to the various sub-project issue trackers at <https://gitlab.com/groups/mailman>. > Something I find surprising is a problem described in an image grab > below relating to an inability to amend a list entry to include a name > to be associated with an email address, as if the data needs to be > immutable. When a workaround was unsuccessfully explored to delete the > entry and then resubmit an amended entry but with the same already > deleted email address, that was still refused, presumably because of > pointers to archived data don't permit, but this seems like a > particularly onerous restriction, or perhaps even a bug, or at least a > severe design constraint. *Is this item on an existing to do list?* There has been much discussion of this on this list. See for example the recent thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> This item is not on a ToDo list because even though <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> asked for an issue to be filed, the most interested person refused to do so because of his assessment of our priorities <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. And if you don't read the whole thread, at least see the response at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty

by Mark Sapiro

On 7/7/22 8:12 AM, tim(a)thecutts.org wrote: > Hi everyone, > > As we all know, mailman3 got dropped from Ubuntu 22. So I updated the operating system anyway, and decided to switch to a virtualenv setup, keeping the old Debian/Ubuntu database and log locations etc. > > With some lumps and bumps, this has gone OK; the web interface appears to be working, and I can use the mailman CLI to manipulate the lists. So far so good. > > However, there do seem to be two problems, which might be linked: > > 1. If I send a message to my test list, it does not get sent on to any members. I can see the lmtp delivery to mailman. But nothing comes out again. I can see the two test messages in the “shunt” directory Look in mailman.log. There will be exceptions and tracebacks associated with the shunted messages. What are these? > 2. Trying to look in the archives for my mailing lists does not work. On the web, I get "An error occurred while processing your request.”, and the log file seems to show a schema error in the hyper kitty table: > > ERROR 2022-07-07 13:18:41,634 116894 django.request Internal Server Error: /mailman3/archives/list/fairhaven-members(a)thecutts.org/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 86, in _execute > return self.cursor.execute(sql, params) > psycopg2.errors.UndefinedColumn: column hyperkitty_mailinglist.archive_rendering_mode does not exist > LINE 1: ...e_policy", "hyperkitty_mailinglist"."created_at", "hyperkitt... > ^ > > Do I need to run a database migration manually? If so, how? I’m not very familiar with Django, it seems a bit hideously complex to me. Yes. You need to run your Django admin command however you invoke it with the 'migrate' option. e.g. with your venv activated ``` django-admin migrate ``` or ``` python manage.py migrate ``` or ??? > Are these issues likely to be related, or do I have two things going on here? The shunted messages are not related to the Django migration issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Showing sender as ... via ... list

by Wolfgang Bock

Dear Mark, many thanks. Works! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Samstag, 6. November 2021 16:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Showing sender as ... via ... list On 11/6/21 4:40 AM, Wolfgang Bock via Mailman-users wrote: > > Here is my question: > > What do I have to configure to get my lists to show the sender like in > this > list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org In Postorius go to Settings->DMARC Mitigations and set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to Yes. -- 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/

3 years, 7 months

[MM3-users] Re: The msgtext argument in 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed to be a string containing only ascii characters.

by Mark Sapiro

On 10/03/2017 12:54 AM, Henrik Rasmussen wrote: > Hi Mark. > > This was originally from another thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, but as it isn't related to the problem in the thread, I'll split it in another thread. > > On 09/29/2017 05:46 AM Mark Sapiro wrote: > >>> In addition, the log contains other trace backs that might or might not associate to this problem: >>> >>> Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >>> Sep 24 21:11:28 2017 (34) Traceback (most recent call last): >>> File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration >>> self._process_one_file(msg, msgdata) >>> File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file >>> keepqueued = self._dispose(mlist, msg, msgdata) >>> File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose >>> self._func(mlist, msg, msgdata) >>> File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver >>> refused = agent.deliver(mlist, msg, msgdata) >>> File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver >>> mlist, msg, msgdata, recipients) >>> File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients >>> sender, sorted(recipients), msg.as_string()) >>> File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail >>> results = self._connection.sendmail(envsender, recipients, msgtext) >>> File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail >>> msg = _fix_eols(msg).encode('ascii') >>> UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >>> Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 >> >> >> This may be a bug. The msgtext argument in >> 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed >> to be a string containing only ascii characters. I'm interested in >> what's in Mailman's >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. >> You may be able to print the contents with Mailman's >> >> bin/mailman queue >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck >> >> There shouldn't be raw unicodes like \udcea in the text of the message, >> but we should defend against that anyway. > > [root@lstapp01pl ~]# docker exec -it mailman-core mailman qfile var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck > [----- start pickle -----] > <----- start object 1 -----> > Traceback (most recent call last): > File "/usr/local/bin/mailman", line 11, in <module> > sys.exit(main()) > File "/usr/local/lib/python3.6/site-packages/mailman/bin/mailman.py", line 100, in main > args.func(args) > File "/usr/local/lib/python3.6/site-packages/mailman/commands/cli_qfile.py", line 81, in process > printer.pprint(obj) > File "/usr/local/lib/python3.6/pprint.py", line 139, in pprint > self._format(object, self._stream, 0, 0, {}, 0) > File "/usr/local/lib/python3.6/pprint.py", line 176, in _format > stream.write(rep) > UnicodeEncodeError: 'utf-8' codec can't encode character '\udcea' in position 3025: surrogates not allowed And I have an MR to defend against this. See all of the following: <https://gitlab.com/mailman/mailman/issues/406> <https://gitlab.com/mailman/mailman/merge_requests/322> <https://gitlab.com/mailman/mailman/issues/410> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

Thank you, Mark! > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 3:37 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > <snip> > > Does that directory also contain __init__.py (probably empty)? It should. > That was it! No __init__.py in /opt/mailman/mailman-suite/mailman-suite_project. Creating an empty file there and restarting the containers caused hyperkitty to start archiving all of the queued messages. Thank you for your time, and Happy Thanksgiving! -p > -- > 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 Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

2 years, 6 months

[MM3-users] Re: Configure MM3 with separate IMAP Mailserver

by Mark Sapiro

On 1/2/23 11:18, Clemens Leider wrote: > Hi Mark, much appreciated! This is for sending messages, right? How about the recieving part…I read different things around that i need multiple mailboxes created, postfix installed, relays, ASMTPDirect etc…can you guide me a bit here, please? I havent found that one instruction that would solve this for me until now. Would just like to avoid to have to administer my own mailserver locally, if i have a perfectly configured one with my provider. CL Yes, what I posted is for outgoing mail from Mailman. Incoming mail is much more difficult. There are threads on this in the archives of this list. E.g., <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> The incoming MTA needs to relay the mail to Mailman's LMTP server for every address - that's 9 addresses per list. An example postfix transport_maps for one list is: ``` list(a)example.com lmtp:[127.0.0.1]:8024 list-bounces(a)example.com lmtp:[127.0.0.1]:8024 list-confirm(a)example.com lmtp:[127.0.0.1]:8024 list-join(a)example.com lmtp:[127.0.0.1]:8024 list-leave(a)example.com lmtp:[127.0.0.1]:8024 list-owner(a)example.com lmtp:[127.0.0.1]:8024 list-request(a)example.com lmtp:[127.0.0.1]:8024 list-subscribe(a)example.com lmtp:[127.0.0.1]:8024 list-unsubscribe(a)example.com lmtp:[127.0.0.1]:8024 ``` This relays mail to those addresses to Mailman's LMTP server listening on the localhost, port 8024. If you could arrange for the external IMAP server to do that, that would work, but I suspect you don't have access to even try. For MM 2.1 which is different in that it doesn't use LMTP in this way, some people have used fetchmail <https://www.fetchmail.info/> to do things like this. This requires setting up mailboxes on the remote server to receive the mail and using fetchmail to retrieve that mail and relay it to Mailman. The issues with this are keeping the remote mailboxes and fetchmail in sync with Mailman as lists are created and removed. Another possibility is to have all your lists in a dedicated domain and configure the remote MTA to forward all mail to that domain to the Mailman host and then configure an MTA on the Mailman host to simply relay all mail to Mailman via LMTP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: moving lists to another server

by Mark Sapiro

On 11/21/23 04:32, Odhiambo Washington wrote: > > I tested the above out of curiosity. It failed. There are 9 lists in the > setup, but I am only interested in 1. > > ``` > (venv) mailman@debian12:~$ mailman-web shell > Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] > Type 'copyright', 'credits' or 'license' for more information > IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help. > > In [1]: from hyperkitty.lib.compat import get_list_by_name > > In [2]: mlist = get_list_by_name('list_name_only', 'list_domain') You can't use literally ('list_name_only', 'list_domain'). If the list of interest is for example alist(a)example.com, the above should be mlist = get_list_by_name('alist', 'example.com') ... > Was I supposed to substitute something for the real listname of the list I > wanted? Yes. > Another thing - totally unrelated - that surprised me: > While using the commented-out block below, I could not click and get > anything beyond http://http://list.name/mailman3 as anything to do with > /postorius/xxxxx gave "Page not found" error. > However, with the second config block that uses the UNIX socket, I am able > to access everything > > ``` > #<IfModule mod_proxy.c> > # ProxyPreserveHost On > # ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3" > # ProxyPass "/archives" "http://127.0.0.1:8010/archives" > # ProxyPass "/accounts" "http://127.0.0.1:8010/accounts" > # ProxyPass "/admin" "http://127.0.0.1:8010/admin" > # ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile" > # </IfModule> > > ProxyPassMatch ^/static/ ! > ProxyPassMatch ^/favicon.ico ! > ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ > ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ > ``` > > Why is it that the UNIX socket option worked flawlessly while the other > option failed??? The first option does not have ProxyPass for urls matching /postorius or /hyperkitty so such urls don't work. The second option passes everything (ProxyPass / ) to uwsgi via the socket so all urls that uwsgi can handle will work. You could do something similar with the first option with simply ProxyPass "/" "http://127.0.0.1:8010/" assuming uwsgi is listening on port 8010. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: List in list, mutiple reply-to addresses

by Stefan Bauer

That is already set. No change. This completely removes the reply-to: header and sets the iu-all list-address as new and only reply-to. Am Mi., 24. Nov. 2021 um 04:18 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/23/21 2:24 AM, Stefan Bauer wrote: > > Unfurtunately, this completely removes the reply-to: header and sets the > > list-address as a new and only reply-to. > > Set Settings -> Alter Messages -> Reply goes to list to No Munging > in addition to First strip reply to = Yes > > -- > 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/ >

3 years, 6 months

[MM3-users] Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 5:40 PM, Brian Carpenter wrote: > Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. Abhilash (@maxking) is one person and he has a $DayJob. We're all doing the best we can. > I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. This is not a Docker issue per se. It is a consequence of upgrading Mailman core to 3.3.1+ and processing many old, stale, previously unprocessed bounces. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. > > I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: > > ### > The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: > > [webservice] > configuration: /path/to/gunicorn.cfg > > and then in the gunicorn.cfg you can add > > [gunicorn] > timeout = 90 > graceful_timeout = 30 > ### > > I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. > > After restarting docker-mailman, I can't access Postorius due to the following error: > > ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Is Mailman core running? If not, whats in core's mailman.log as to why not? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/16/20 10:34 AM, Mark Dadgar wrote: > If one of my users (including admin) goes to their user drop-down in the upper-right of Postorius and clicks Mailman Settings, it triggers an error: > > > > Here’s the error log: > > Internal Server Error: /mailman3/postorius/accounts/subscriptions/ > > KeyError at /postorius/accounts/subscriptions/ > 'file' The KeyError is bogus. It is an error that occurs in Django's logging when trying to log the real error. > Request Method: GET > Request URL: https://mail.pdc-racing.net/mailman3/postorius/accounts/subscriptions/ ... > 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/contrib/auth/decorators.py" in _wrapped_view > 21. return view_func(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/user.py" in user_subscriptions > 307. memberships = [m for m in mm_user.subscriptions] Here we're trying to grt all the user's subscriptions. Se we call mailmanclient for that. > File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py" in subscriptions > 62. for address in self.addresses: client is getting all the user's addresses > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __iter__ > 221. for entry in self.rest_data: It got the addresses and is now iterating over them. > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data > 197. response, content = self._connection.call(self._url) Which calls the REST API > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) And gets a 500 from core. > During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: Which we aren't interested in. The next step is to look in core's mailman.log to see what the rest call was and the exception and hopefully traceback the caused the 500 response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Mass unverified subscriptions end up as pending user confirmation instead.

by Mark Sapiro

On 2/25/20 2:34 PM, hansen(a)rc.org wrote: > After mass subscribing with these settings: > > Pre confirm: Yes, Pre approved: Yes, Pre Verified (sic): No > > the addresses appeared in the list's 'Pending user confirmation' list. They were pre-confirmed. > The addresses did not appear in the Django Admin's non-verified addresses list. They were not verified. It is actually pending verification, not confirmation. Postorius can't tell the difference. It only knows that it's waiting for some action either by a moderator (pending approval) or the user (pending confirmation or verification, but just called 'confirmation') This verification is for Mailman core to verify it's a valid address that the user wants to use with this mailman installation. Once this address is verified, it can be subscribed to other lists without further verification. This has nothing to do with Django verified addresses which are addresses associated with Django log-in that have been verified to Django. > Also why does Postorius lists just 'Pending Approval' and 'Pending Confirmation' but not 'Pending Verification'? As I said, it doesn't know the difference between 'Pending Confirmation' and 'Pending Verification'. You should note that the user you subscribed in this way received a 'verification' request like > Email Address Registration Confirmation > > Hello, this is the GNU Mailman server at example.com. > > We have received a registration request for the email address > > user(a)example.org > > Before you can start using GNU Mailman at this site, you must first confirm > that this is your email address. You can do this by replying to this message, > keeping the Subject header intact. > > If you do not wish to register this email address, simply disregard this > message. If you think you are being maliciously subscribed to the list, or > have any other questions, you may contact > > listname-owner(a)example.com and not a subscription confirmation request. Also, if any of the addresses had been already verified, they would have been subscribed immediately without confirmation or approval. -- 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: Delete a single email or thread from hyperkitty archive

by Abhilash Raj

On Fri, Jun 21, 2019, at 2:07 PM, Mark Sapiro wrote: > On 6/21/19 6:54 AM, andrew.bernard(a)gmail.com wrote: > > How can one do this? Raw database access gets you involved in all the usual foreign key constraints. > > > In the HyperKitty thread view there is a link to "Delete this thread". > In the message view there is a link to "Delete this message". Do note that this option is only visible to "Superuser" in Django, i.e. Admin accounts. > > -- > 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)

5 years, 11 months

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/17/21 2:15 PM, dancab(a)caltech.edu wrote: > Thank you. Should I be able to see the specific cache creation and expiration dates in the file_cache table of the database? Once I run the command you mentioned, should I then see that table cleared? > > MySQL [mailman3_prod]> select id, created_on, expires_on from file_cache; Yes. Also, you can see the file_id, and the key is the URL the template was retrieved from. The file_id is a 64 byte hex hash of the key and points to the cached content. If the file_id is, e.g., e4ff6a68a78b7ca911d5b16271980fa0cb816938fa187ec0f62bae707e541de0, the content it stored at /e4/ff/e4ff6a68a78b7ca911d5b16271980fa0cb816938fa187ec0f62bae707e541de0 relative to the cache_dir setting (or whatever it was when the content was stored). > +----+---------------------+---------------------+ > | id | created_on | expires_on | > +----+---------------------+---------------------+ > | 1 | 2021-03-03 23:02:48 | 2021-03-10 23:02:48 | > | 2 | 2021-03-03 23:42:49 | 2021-03-10 23:42:49 | > | 4 | 2021-03-05 21:13:07 | 2021-03-12 21:13:07 | > | 6 | 2021-03-05 22:30:33 | 2021-03-12 22:30:33 | > | 7 | 2021-11-23 00:11:23 | 2021-11-30 00:11:23 | > | 11 | 2021-11-23 23:09:36 | 2021-11-30 23:09:36 | > | 12 | 2021-11-23 23:23:28 | 2021-11-30 23:23:28 | > | 13 | 2021-11-23 23:48:51 | 2021-11-30 23:48:51 | > | 14 | 2021-11-23 23:53:30 | 2021-11-30 23:53:30 | > | 15 | 2021-11-24 00:03:40 | 2021-12-01 00:03:40 | > | 16 | 2021-11-24 00:14:03 | 2021-12-01 00:14:03 | > | 17 | 2021-11-30 22:50:14 | 2021-12-07 22:50:14 | > | 18 | 2021-12-01 15:57:48 | 2021-12-08 15:57:48 | > | 19 | 2021-12-01 15:57:48 | 2021-12-08 15:57:48 | > | 20 | 2021-12-01 17:01:09 | 2021-12-08 17:01:09 | > | 21 | 2021-12-01 17:41:42 | 2021-12-08 17:41:42 | > | 22 | 2021-12-02 23:09:58 | 2021-12-09 23:09:58 | > | 23 | 2021-12-03 22:52:10 | 2021-12-10 22:52:10 | > | 24 | 2021-12-04 02:54:06 | 2021-12-11 02:54:06 | > | 27 | 2021-12-08 14:28:41 | 2021-12-15 14:28:41 | > | 29 | 2021-12-10 17:43:16 | 2021-12-17 17:43:16 | > | 30 | 2021-12-11 02:00:04 | 2021-12-18 02:00:04 | > | 31 | 2021-12-13 09:02:44 | 2021-12-20 09:02:44 | > | 33 | 2021-12-16 20:07:11 | 2021-12-17 20:07:11 | > | 35 | 2021-12-17 19:21:19 | 2021-12-18 19:21:19 | > +----+---------------------+---------------------+ > 25 rows in set (0.001 sec) It is not clear to me why you have long expired entries in the file_cache table. The task runner should have expunged those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 5/1/21 4:58 AM, Andrew Hodgson wrote: >> Mark Sapiro wrote: >> >>> ``` >>> msg["Message-ID"] = "<%s>" % re.sub('[ <>\r\n]', '', self.message_id) >>> ``` >> >> Thanks that did the trick. Will this need to go in the upstream release or is there any way I could re-import those messages into the database with a newer version of the import command from the original mbox from 2.1 to fix this? > >Sorry for not following up sooner. This got deferred and then forgotten :( > >I would like to see the offending message from the original mbox so I can develop an appropriate fix. What is the best way of getting that to you? You can download the mbox from your end of course, or I can revert the change so you can see where the original stopped. Thanks. Andrew.

4 years

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/4/21 2:15 PM, Bryan Loniewski wrote: > Based on your import21 comments, I'm realizing the issue may be caused by multiple runs of import21. I have been (although I've stopped it for some time now) running import21 nightly to sync up my Mailman3 list data with Mailman2. I've been doing the same for archiving as well. import21 was never intended to be run more than once for a particular list. > I've noticed now that some lists have duplicate acceptable alias entries (looks to be like <number of aliases> x <number of import21 runs>) and the same goes for *_these_nonmembers entries. That's not surprising. There may be other attributes that are duplicated or otherwise corrupted from running import21 multiple times. > Is this a symptom of running the old(er) import21 command pre-3.3.2? Will the 3.3.2 import21 work as expected w/out the duplications if I was to clear out the appropriate lists col data (i.e., is it okay to run import21 multiple times)? I tried to figure out if there were any other duplicative data, but did not come across any. Is there more that I'm missing? I don't think the 3.3.2 changes to import21 will avoid the duplications. I think there will be other issues as well. For example, if there are changes in membership or ownership on the 2.1 list import21 will probably pick up the additions but not the deletions. The intended use of import21 is for a one time migration of a MM 2.1 list to MM 3. It is not intended to somehow sync parallel MM 2.1 and MM 3 lists. If the idea is to run import21 to create a test MM 3 list while still running the MM 2.1 list in production, I would suggest to run import21 once and then when ready for the final migration, delete the MM 3 list, create a new, 'empty' list and run import21 on that. As far as hyperkitty_import is concerned, it can be run multiple times. If --since is not specified, it will only consider messages newer than the newest in the existing archive, and in any case will skip duplicate Message-IDs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: reset bounce-scores?

by Mark Sapiro

On 10/3/24 01:15, IEM Network Operation Center (IOhannes m zmölnig) wrote: > i'm running a mailman-3.3.8 instance, and would like to reset the > bounce-score for a (number of) user(s). > i searched the internet and this list's archives, but haven't found > anything useful so far. > > due to a misconfiguration of our universities reverse DNS lookup, the > bounce score of some users has rocketed in the last days - some users > have already been unsubscribed because of that. > > could anybody please share how i can reset the bounce score? First of all, there are 3 categories of affected list members - those who are already unsubscribed, those who are still members but have delivery disabled by bounce, and those with delivery enabled but with bounce score > 0. For those that have been unsubscribed, you just have to re-subscribe them. For those that have delivery enabled but a non-zero bounce score, you may not need to do anything because they are presumably not currently bouncing so eventually the old bounce info will become stale and be ignored, but to guard against spurious bounces that may result in disabling, e.g.from an over aggressive user's spam filter, you can add `verp_probes: yes` to the `[mta]` section of mailman.cfg. The effect of this is when a members bounce score reaches threshold the score is reset and a special probe message is sent and delivery is disabled only if the probe bounces. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… That leaves those with delivery disabled by bounce. Assuming you want to enable delivery for all members of all lists with delivery disabled by bounce, the following `mailman shell` interaction will do it. ``` $ bin/mailman shell 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. >>> for mlist in getUtility(IListManager): ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` Watch out for a possible wrapped line above. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I changed them to 127.0.0.1 and localhost as you suggested El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > 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

7 years, 10 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/4/21 12:52 PM, Duane Raymond wrote: > > Virtual Domains: > So based on the Postfix virtual domain documentation and the Mailman3 specific "Unusual Postfix configuration' section, I added the following to my postfix main.cf file: > virtual_alias_domains = emaillistA.com emaillistB.com > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > and removed those domains from the 'mydestination' setting. You probably do not have a configuration that is a "Unusual Postfix configuration" Putting Mailman aside, is there some reason why emaillistA.com and emaillistB.com need to be virtual_alias_domains? If these domains are only for mail lists, they do not need to be virtual_alias_domains? > I then created the postfix_vmap file and added to it: > emaillistA.com DOMAIN > # > emaillistB.com DOMAIN You don't create these files. Mailman creates them in its var/data directory when you run `mailman aliases` or just start mailman core. > ...then ran postmap with the path and reloaded postfix. Mailman also runs the appropriate postmap commands. You should have one of two setups in Postfix depending on whether emaillistA.com and emaillistB.com need to be virtual_alias_domains or not. If they are only for list mail, they should not be virtual_alias_domains in Postfix and their domain definitions in Mailman should not have an alias domain. In that case, in Postfix you want transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp local_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains and you want Mailman to generate those files. Also see the note in <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> about adding hash:/path-to-mailman/var/data/postfix_lmtp to local_recipient_maps rather than replacing it. If emaillistA.com and emaillistB.com do need to be virtual_alias_domains, you configure them in postfix according to the normal postfix configurationfor virtual_alias_domains and virtual_alias_maps. Then each of these domains needs a corresponding, otherwise unused alias domain defined in Mailman and what you need in Postfix is transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap Where again if you have existing settings for these things, add the mailman files rather that replacing the existing with them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Current status and issue deleting Archives in Mailman3

by Mark Sapiro

On 11/2/21 9:30 AM, bob B wrote: > So just want to make sure I have the latest information after searching this list and googling or have I missed something? It appears there is no way in mailman3 to delete archives. There has been discussion on implementing this, but it has not been developed? is that correct? I'm not sure when it first appeared, but current Hyperkitty has Delete Archive button on the list overview page, but it is only available to Django superusers, not to list owners. > I saw references to: >>>> from hyperkitty.models import MailingList >>>> ml = MailingList.objects.get(name="test2(a)freeculture.org") >>>> ml.delete() > > > But how do I run this? I believe it is run in mailman-core (I am in a docker environment but that should not matter). I can get into the mailman shell, but that command does not work It is run in a Django management shell, not mailman shell. > ************** Question 2 > > What about pruning archives? I use to run a script for mailman2 to prune archives of messages older than X days for a list, Is that possible in mailman3 There are a few ways to do this. You can export the archive for a list as an mbox and edit the mbox to delete the messages you want to prune. Then delete the archive for this list and finally run hyperkitty_import to import the pruned mbox. Alternatively, in a django management shell, you could try something like ``` import datetime from hyperkitty.models import Email for msg in Email.objects.filter(mailinglist_id=X): if msg.date < datetime.datetime(Y, M, D, tzinfo=datetime.timezone.utc): msg.delete() ``` where X is the id of the mailing list you want to prune, or if you wanted to do all lists, just use Email.objects.all() instead of filtering on mailinglist_id. And, Y, M and D are integer Year, Month and Day for the cutoff. Note that something like ``` from hyperkitty.models import MailingList for ml in MailingList.objects.all(): print('{}: {}'.format(ml.name, ml.id)) ``` will print all the list names and their ids. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 7:44 PM, Alan So wrote: > I just notice that if I send an email to a list with a Cc header broken into multiple lines and the pair of double quotes are put in different lines, the email addresses afterwards will be wrongly rewritten. > > For example, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> tl;dr It is not valid to fold a header inside of a quotes string. First of all, the above is invalid. Presumably the address is intended to be "ABC DEF (XYZ)" <name(a)example.com> RFC 5322, sec 2.2.3 says in part: "The general rule is that wherever this specification allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP." and the definitions in sec 3.4 say in part: address = mailbox / group mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr angle-addr = [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr display-name = phrase In this case, the quoted-string "ABC DEF (XYZ)" is a phrase which is the display-name and the only places where comments or folding white space are allowed is immediately preceding the "<" or following the ">" surrounding the addr-spec. Folding in the middle of the quoted string is not allowed. Were there no quotes, e.g. ABC DEF (XYZ) <name(a)example.com> Then ABC DEF is a phrase and (XYZ) is a comment and folding between DEF and (XYZ) would be allowed > It will become the following after going through the mailing list: > > CC: XYZ <"ABC DEF"@mail.server.name> Which is clearly wrong, but GIGO. > It seems that Outlook often split the To/Cc header into multiple lines and they often add double quotes to the full name of the users. Is the rewriting of Cc header handled by Mailman's code or another Python class? I haven't looked at the code to see exactly what's responsible here. I do note that adding double quotes around a display name is not only allowed, but is required if the display name contains "specials". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Digest Formatting

by Mark Sapiro

On 11/7/20 9:08 AM, Stephen J. Turnbull wrote: > > I thought there was a way to trigger immediate distribution of a > digest immediately, but I guess I'm remembering that from Mailman 2. > Neither the Postorius management interface nor the core documentation > suggests there's such a trigger in Mailman 3. There is nothing in the web UI or REST, but the `mailman digests` command can send accumulated digests for one or more named lists or all lists unconditionally or only if the list's digest_send_periodic is set to True. see `mailkman digests --help` for details. > > 2) I have customized list:member:digest:header, but am not seeing > > the custom text where I thought it should be. The documentation > > seems to imply that both list:member:digest:header and > > list:member:digest:footer surround each message in the digest > > Which documentation do you mean? As far as I know (Mark will have > authoritative information if I'm wrong), the digest header and footer > appear at the top and bottom of the *whole* digest message (ie, once > each per digest), not surrounding or in the bodies of the component > messages. Steve is correct. The layout is as follows The masthead from the list:member:digest:masthead template. The digest header if any from the list:member:digest:header template. The table of contents. The individual messages. The digest footer from the list:member:digest:footer template. For the MIME digest, these are all separate MIME parts and the individual messages are message/rfc822 parts within a multipart/digest part. For the plain text digest, the digest is one text/plain part containing the above formatted par RFC 1153 And in another post, mailman(a)manygoodideas.com wrote: > I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks. This already exists, it is list:member:digest:footer. Your confusion seems to be because you think the list:member:digest:header template and list:member:digest:footer template are prepended/appended to each individual message in the digest which would not make sense and is not the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Attachement processings questions

by Mark Sapiro

On 2/4/20 1:17 AM, Lars Schimmer wrote: > > Those mails are in the mailinglist archives, not on hold or anything. > Just the attachement missing. > > > So, please, howto fix the ascii encoding error in mailman3? > > Full trace: > Jan 31 03:02:43 2020 (32591) Uncaught runner exception: 'ascii' codec > can't encode character '\xe9' in position 109: ordinal not in range(128) > Jan 31 03:02:43 2020 (32591) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line > 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line > 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/pipeline.py", > line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/usr/lib/python3/dist-packages/mailman/core/pipelines.py", line > 50, in process > handler.process(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/handlers/to_digest.py", > line 48, in process > mbox.add(msg) > File "/usr/lib/python3.7/mailbox.py", line 603, in add > self._toc[self._next_key] = self._append_message(message) > File "/usr/lib/python3.7/mailbox.py", line 758, in _append_message > offsets = self._install_message(message) > File "/usr/lib/python3.7/mailbox.py", line 830, in _install_message > self._dump_message(message, self._file, self._mangle_from_) > File "/usr/lib/python3.7/mailbox.py", line 215, in _dump_message > gen.flatten(message) > File "/usr/lib/python3.7/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.7/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.7/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.7/email/generator.py", line 432, in _handle_text > super(BytesGenerator,self)._handle_text(msg) > File "/usr/lib/python3.7/email/generator.py", line 249, in _handle_text > self._write_lines(payload) > File "/usr/lib/python3.7/email/generator.py", line 155, in _write_lines > self.write(line) > File "/usr/lib/python3.7/email/generator.py", line 406, in write > self._fp.write(s.encode('ascii', 'surrogateescape')) > UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in > position 109: ordinal not in range(128) This is <https://bugs.python.org/issue39384> You can fix it by patching the Python library email/generator.py as at <https://github.com/python/cpython/pull/18056/files#diff-220640ea02a24dfdbb0…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Mark Sapiro

On 2/5/25 15:59, Thomas Krichel wrote: >> >> ## dont't start nntp because library is missing >> >> [runner.nntp] >> start: no >> > > ok, but > > root@server~# systemctl status mailman3.service > × mailman3.service - Mailman3 server > Loaded: loaded (/usr/lib/systemd/system/mailman3.service; enabled; preset: enabled) > Active: failed (Result: exit-code) since Wed 2025-02-05 23:36:35 UTC; 9min ago > Duration: 2month 3w 6d 6h 21min 31.400s > Invocation: 746a7d496ddd47f6a63795e55348b6f9 > Docs: man:mailman(1) > https://mailman.readthedocs.io/ > Process: 416285 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) > Mem peak: 74.2M > CPU: 1.712s > > Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 935, in _load_unlocked > Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap_external>", line 1026, in exec_module > Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed > Feb 05 23:36:34 server mailman3[416285]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_gatenews.py", line 24, in <module> > Feb 05 23:36:34 server mailman3[416285]: import nntplib > Feb 05 23:36:34 server mailman3[416285]: ModuleNotFoundError: No module named 'nntplib' > Feb 05 23:36:35 server systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE > Feb 05 23:36:35 server systemd[1]: mailman3.service: Failed with result 'exit-code'. > Feb 05 23:36:35 server systemd[1]: Failed to start mailman3.service - Mailman3 server. > Feb 05 23:36:35 server systemd[1]: mailman3.service: Consumed 1.712s CPU time, 74.2M memory peak. Yes, my suggestion will prevent the nntp runner from running which in turn will prevent it from calling `mailman gatenews` in it's periodic task and will prevent it from trying to import nntplib, but it turns out that the `mailman start` command which is used to start Mailman tries to get all the components of all the subcommands. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/bin/mailman.py…. Since there is still a mailman/commands/cli_gatenews.py file, mailman.utilities.modules.add_components tries to import it so simply adding ``` [runner.nntp] start: no ``` to mailman.cfg is not sufficient if there is no nntplib module. Sorry for the confusion. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I'm looking in /var/etc/mailman.log but nothing occurs and in the postfix maillog nothing occurs as well Is it possible to look into another config or log file? Thanks El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > 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

7 years, 10 months

[MM3-users] Re: Random characters in "The results of your email commands" e-mail

by Mark Sapiro

On 2/17/20 3:00 AM, Jeffrey D wrote: > Hi, > > Today I sending an e-mail to "mylist-request(a)domain.tld" with the subject "help" and I received the expected e-mail with the following content; > > confirm - Confirm a subscription request. > echo - Echo back your arguments. > end - Stop processing commands. > help - Get help about available email commands. > join - Join this mailing list. > leave - Leave this mailing list. > stop - An alias for 'end'. > subscribe - An alias for 'join'. > unsubscribe - An alias for 'leave'. > No such command: -- > No such command: vriendelijke > > Only I think my mail signature broke something in Mailman (see the No such command). Something may be broken, but it was not your email command with signature that broke it. Mail to the -request address processes the Subject: as a command if it appears to be one and then processes each of the first several (default 10) lines of the body as a command until it encounters a 'stop' or 'end' command or other command whos process says don't continue. In this case your signature was reported as no such command. This is normal and expected. > Because every e-mail with a subject like "help", "stop" or "join", gives a reply with random characters. The Mailman logs doesn't show any error, so I'm not sure what is wrong. Deleting the mailinglist and create a new one won't fix the issue, also restarting Mailman doesn't help. > > An example of the random characters: > Nzzf&ju[zZ0:v,jzkb^}nJyazZCj}{m5t5Cx<{iysG5o[w}jgn+g[lrwf*mzrLk)rjwliazZZnjyW(fvrh{aXXWj+&j)b b-'jX+zwl&v{rx &~y6.r(fu4:' > > Is this a bug in Mailman? Or something in my Mailman config... To understand what's going on, We would like to see the complete, raw response message. Also, the headers of the message sent to the -request address, in particular the Content-Type: header of the first text/plain part and its charset param. -- 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: New releases

by Abhilash Raj

On Thu, Jun 25, 2020, at 10:35 PM, Abhilash Raj wrote: > > > On Thu, Jun 25, 2020, at 8:59 AM, Danil Smirnov wrote: > > The issue has confirmed by other users: > > > > https://github.com/maxking/docker-mailman/issues/382 > > The issue seems to happen because the static files that are present at > the default staticfile locations aren't valid anymore and aren't > removed automatically on upgrades. > > You can run: > > sudo rm -rf /opt/mailman/web/static > > To remove them manually and then it should be re-created properly on > the next start. I'll try to work on a fix for this in some automated > fashion. Seems like I wasn't using the right options like Mark pointed out above. --clear flag will automatically remove the old files. I have created a PR[1] to fix it and will try to get it out with a new release soon. [1]: https://github.com/maxking/docker-mailman/pull/384 > > > > > вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > > > > > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > >>> COMPRESS_OFFLINE = True > > > >>> COMPRESS_ENABLED = True > > > >> > > > > > > > > These two are commented out. > > > > > > > > > Then compress shouldn't be trying to do anything. I can't explain what's > > > going on. > > > > > > -- > > > 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/ > > > > > _______________________________________________ > > 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) -- thanks, Abhilash Raj (maxking)

4 years, 11 months

[MM3-users] Re: How to configure mailman3-web

by Mark Sapiro

On 6/14/22 10:19, robert.winkler(a)bioprocess.org wrote: > Hi, I just installed mailman3-web on my Ubuntu 20.04 LTS web server. By Mailman3-web, I assume you mean the Debian/Ubuntu package. If so, your primary support resources are Ubuntu and Debian. > Port 8001 is open, the service is running: > > root@localhost:/etc/mailman3# systemctl status mailman3-web.service > ● mailman3-web.service - Mailman3-web uWSGI service > Loaded: loaded (/lib/systemd/system/mailman3-web.service; enabled; vendor preset: enabled) > Active: active (running) since Tue 2022-06-14 17:05:06 UTC; 47s ago > Docs: file:///usr/share/doc/mailman3-web/README.rst > Main PID: 30135 (uwsgi) > Status: "uWSGI is ready" > Tasks: 10 (limit: 2306) > Memory: 147.7M > CGroup: /system.slice/mailman3-web.service > ├─30135 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini > ├─30152 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini > ├─30153 /bin/sh -c python3 manage.py qcluster > ├─30155 python3 manage.py qcluster > ├─30158 python3 manage.py qcluster > ├─30159 python3 manage.py qcluster > ├─30160 python3 manage.py qcluster > ├─30161 python3 manage.py qcluster > └─30162 python3 manage.py qcluster > > Jun 14 17:05:05 localhost systemd[1]: Starting Mailman3-web uWSGI service... > Jun 14 17:05:05 localhost uwsgi[30135]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini > Jun 14 17:05:06 localhost systemd[1]: Started Mailman3-web uWSGI service. > > in /etc/mailman3/mailman-web.py I changed localhost for my domain:port: > > MAILMAN_REST_API_URL = 'http://meteomex.com:8001' > POSTORIUS_TEMPLATE_BASE_URL = 'http://meteomex.com:8001/mailman3/ > > and restarted the service. > > on the server side, it looks fine, the mailman3 DB in postgresql exists. > > However, I cannot access the web interface, trying, e.g. > http://meteomex.com:8001/mailman3/ > 'http://meteomex.com/mailman3 > 'http://meteomex.com:8001 > > anything I am missing? E.g. concerning the Apache config? You should not be accessing port 8001 directly. Mailman core's REST API listens on port 8001 and Postorius is the one that accesses that API. uWSGI normally listens on port 8000 and Apache proxies to uWSGI on that port. What happens when you go to http://meteomex.com/mailman3? In order to say more, we would probably need to see your uWSGI configuration and the relevant parts of your Apache configuration -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Prototype import [was: Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)]

by Mark Sapiro

On 4/19/25 1:55 PM, Mihai Moldovan wrote: > > This eventually led me to realize that passing > mailman.email.message.Message as the factory to mbox() internally calls > factory(msg), and the base class of Message (email.message.Message) has > an __init__ function that takes the policy parameter, so it looks as if > it's registering the mailbox message incorrectly as the policy handler, > which is totally wrong of course. This appears to be a bug in mailbox.mbox. To work around it, try this: ``` from email import message_from_bytes mb = mbox(sys.argv[2], create=False) for key in mb.iterkeys(): msg = message_from_bytes(mb.get_bytes(key), Message) ``` > and indeed, if I let the import actually happen, it works. Still, it's probably better if the message is a mailman.email.message.Message object rather than an email.message.Message object. > The imported messages, do have a Message-ID-Hash, but the Archived-At > and List-Archive headers are empty (literally <>). Those headers are added by the rfc_2369 handler based on the archivers configured for the list. They will never point to the prototype archiver or the message in the prototype archive. Normally they will point to HyperKitty and to the archived message in HyperKitty. This is the case even for messages in the prototype archiver as those messages are just the message as delivered to the list members absent any personalization. > Do you have an example message that was archived through Prototype? What > are the proper header values for this module? I believe that Archived-At > should be the Message-ID-Hash and the List-Archive header contain... > well, given that the Prototype archiver is not meant to be publicly > available, probably a file:// URL? Typically they will be something like List-Archive: <https://example.com/archives/list/listname@example.com/> Archived-At: <https://example.com/archives/list/listname@example.com/message/xxxxxx/> where xxxxxx is the message-id hash value. Note that the generation of these headers by the rfc_2369 handler depends on this script being run in an installation that has hyperkitty and mailman-hyperkitty installed and the hyperkitty archiver enabled for the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Issues with international characters (replaced by ?) when mail is send as text/html

by Mark Sapiro

https://gitlab.com/mailman/mailman/-/issues/967 is now fixed. This is the patch to fix it. See https://gitlab.com/mailman/mailman/-/merge_requests/946 ``` diff --git a/src/mailman/handlers/decorate.py b/src/mailman/handlers/decorate.py index ec0ba8ed385e529b2b4c959e41d7d8985cc783e5..53ea861de13c76d1571c3664ec8358bf9c97b4e0 100644 --- a/src/mailman/handlers/decorate.py +++ b/src/mailman/handlers/decorate.py @@ -18,13 +18,13 @@ """Decorate a message by sticking the header and footer around it.""" import re +import copy import logging from email.mime.text import MIMEText from email.utils import formataddr from mailman.archiving.mailarchive import MailArchive from mailman.core.i18n import _ -from mailman.email.message import Message from mailman.interfaces.handler import IHandler from mailman.interfaces.mailinglist import IListArchiverSet from mailman.interfaces.template import ITemplateLoader @@ -176,26 +176,12 @@ def process(mlist, msg, msgdata): # Because of the way Message objects are passed around to process(), we # need to play tricks with the outer message -- i.e. the outer one must # remain the same instance. So we're going to create a clone of the outer - # message, with all the header chrome intact, then copy the payload to it. - # This will give us a clone of the original message, and it will form the - # basis of the interior, wrapped Message. - inner = Message() - # Which headers to copy? Let's just do the Content-* headers - for h, v in msg.items(): - if h.lower().startswith('content-'): - inner[h] = v - inner.set_payload(msg.get_payload()) - # For completeness - inner.set_unixfrom(msg.get_unixfrom()) - inner.preamble = msg.preamble - inner.epilogue = msg.epilogue - # Don't copy get_charset, as this might be None, even if - # get_content_charset isn't. However, do make sure there is a default - # content-type, even if the original message was not MIME. - inner.set_default_type(msg.get_default_type()) - # BAW: HACK ALERT. - if hasattr(msg, '__version__'): - inner.__version__ = msg.__version__ + # message, with all the header chrome intact, then delete unwanted headers. + inner = copy.deepcopy(msg) + # Which headers to keep? Let's just do the Content-* headers + for h, v in inner.items(): + if not h.lower().startswith('content-'): + del inner[h] # Now, play games with the outer message to make it contain three # subparts: the header (if any), the wrapped message, and the footer (if # any). ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Reply w/Email Clients - From: vs. Reply-To:

by Mark Sapiro

On 11/17/20 2:34 PM, j(a)manygoodideas.com wrote: > I'm setting up a new list, and a number of new list members are reporting a problem with replying to the thread. Their email clients seem to ignore the Reply-To: field and instead use from From: field. Are you saying that a 'reply' , not 'reply-all' will reply to the From: only and ignore Reply-To:? If so, the email clients that are doing that are badly behaved. I can't say they are non-compliant as RFC 5322 <https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.2> only says: The originator fields also provide the information required when replying to a message. When the "Reply-To:" field is present, it indicates the address(es) to which the author of the message suggests that replies be sent. I.e., Reply-To: is only a 'suggestion', but well behaved clients will follow it. > When they use Reply All, the email is addressed to both the From: and Reply-To:. Reply All should reply to the Reply-To:, To: and Cc: addresses and to From: if there is no Reply-To:. Whether Reply All should include From: if there is a Reply-To is not well defined. > Reading through previous threads here, I've tried a number of things: > > 1) DMARC mitigation action is "Replace From: with list address" > 2) For Alter Messages - Set "Reply goes to list" > > The goal is that we want a reply to go to the list, not the person posting. Since Reply-To seems to be ignored by some clients, I'm hoping there's a way to force the "From" field to become the list address. Thanks in advance for your suggestions! If Alter Messages -> Reply goes to list is set to Reply goes to list, Reply-To: will include the list posting address. What are the clients that ignore this? Complaints should go to the providers of those. Tf DMARC mitigation action is "Replace From: with list address", that will happen to messages to which DMARC mitigation action applies. If you want it to apply to all messages, set DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Mail control not given from Mailman 3 to postfix

by Mark Sapiro

On 7/6/20 11:07 PM, Shashikanth Komandoor wrote: > > Recently I observed a peculiar case. There is a list say > testlist(a)lists.testdom.com has a non member say testuser(a)testdom.com whose > Moderation attribute is set to "Accept immediately (bypass all other rules). > > This testuser(a)testdom.com has sent a mail to testlist(a)lists.testdom.com > and postfix of my Maliman 3 received the request and handed over to Mailman > at 0.0.0.0:8024 socket running on the same machine and the same is logged > in /var/log/maillog. So it was received by Postfix and delivered to Mailman. > Since the user has the moderation attribute set to Accept, the > /var/lib/mailman/mailman/var/logs/vette.log also displayed "ACCEPT" on > searching with the same message id. And the post was accepted. (Apparently you override the path for logging.vette in your mailman.cfg since the default logs these to mailman.log) > At this point, to my expectations, there should be 2 entries for this > message id in smtp.log one for smtp and one for post. But I don't find any > log records with this message id in smtp.log and of course the mail is not > delivered even. You don't find the message-id in the smtp.log for the incoming LMTP because the message-id is not logged in this entry. It only logs the actual LMTP commands and the envelope sender and recipient(s). You don't find the <messageid> post to testlist(a)lists.testdom.com ... and <message-id> smtp to testlist(a)lists.testdom.com for nn recips, ... entries because the post never got to that point in the processing (those are logged when the post is delivered to the list members). > Could you please help me out if I have missed any point or improperly > understood the mail flow while using the mailman 3? There was probably some exception in processing causing the message to be shunted. If so, the message is in the shunt queue and there is an entry in mailman.log for the exception and shunting with a traceback from the exception which will help in diagnosing the reason. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Mark Sapiro

On 5/4/20 11:07 AM, Samir Faci wrote: > The only way I've gotten it to work so far is by using the FQN. I can > switch back to 127.0.0.1 but that wasn't working. > > Here's the configuration I have. > > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > smtp_host: 127.0.0.1 > smtp_port: 25 > smtp_user: > smtp_pass: > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > > > and the end result: > > https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 which includes May 4 17:50:09 lists postfix/lmtp[2600677]: connect to lists.domain.org[198.199.98.177]:8024: Connection refused So the question is, why is Postfix trying to connect to lists.domain.org[198.199.98.177] and not to localhost[127.0.0.1] > smtp_host: 127.0.0.1 > lmtp_host: 127.0.0.1 > > #fail But it should work. > smtp_host: lists.domain.org > lmtp_host: lists.domain.org > > # success. And this should not be necessary. > The error I get if I don't open port 8024 is below and in the gist i linked > earlier. > > May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< > testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, > dsn=4.4.1, status=deferred (connect to lists.domain.org[198.199.98.177]:8024: > Connection refused) This is what is expected if port 8024 is not open and you are connecting to lists.domain.org. > The only way I've gotten it to work so far is by binding both the smtp_host > and lmtp_host to be lists.domain.org and opening up port 8024. > > I'd rather not have that port open but I'm open to suggestions on what else > to try. You need to get Postfix to use localhost[127.0.0.1] and not lists.domain.org[198.199.98.177]. One issue is when you change lmtp_host: lists.domain.org to lmtp_host: 127.0.0.1 you need to run `mailman aliases` to change the settings in var/data/postfix_lmtp. I think if you go back to smtp_host: 127.0.0.1 lmtp_host: 127.0.0.1 and run `mailman aliases`, restart mailman and reload Postfix, it should all work without opening port 8024 and probably without needing to put 198.199.98.177 explicitly in mynetworks in Postfix. I suspect you will have issues with mail not being accepted or treated as spam by some recipient ISPs however. See <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: anomalous behavior

by Mark Sapiro

On 10/5/24 04:14, donato(a)molino.it wrote: > Hi, > I installed mailman-full on debian 12. How? Did you follow https://docs.mailman3.org/en/latest/install/virtualenv.html or did you install the Debian packages. If the latter, please see https://wiki.list.org/x/12812344 > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > I have three MLs: > 1) example(a)example.com > 2) test(a)example.com > 3) hello(a)example.com > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > The configurations are identical for all 3: > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > I also enabled all debugging in mailman.cfg. > But everything is fine What's in the MTA log? Does list 1 have any non-digest members with delivery enabled `mailman members --regular --nomail enabled example(a)example.com` In addition to the above in smtp.log, I would expect to see entries similar to the following for your post to this list. ``` Oct 05 11:15:02 2024 (3390806) <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 seconds Oct 05 11:15:02 2024 (3390806) <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes Oct 05 15:22:57 2024 (3390806) <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 seconds Oct 05 15:22:57 2024 (3390806) <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes ``` (the delay between 11:15:02 and 15:22:57 above is the time between arrival and held message approval) Do you see things like that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I ran 'mailman aliases', what should I do now? Thanks El dom., 23 jul. 2017 a las 20:22, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 06:00 PM, Rafael Mora wrote: > > Hello guys, > > > > This is what I've got on ../var/data: > > > > [root@localhost data]# pwd > > /var/lib/mailman/var/data > > [root@localhost data]# ls -l > > total 76 > > -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db > > > > > > What should I do in order to let mailman install the DB files? > > > Run > > bin/mailman aliases > > -- > 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

7 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is what I did: (env2) [mailman@localhost mailman-suite_project]$ python2 manage.py runserver Performing system checks... System check identified no issues (0 silenced). July 21, 2017 - 20:50:29 Django version 1.11.3, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C. El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 01:36 PM, Rafael Mora wrote: > > > > I visited http://192.168.1.42:8000 in my browser and I could not see the > > web UI. > > > What did you see? > > Did you run the Django web server? In your Python 2 virtualenv? > > python manage.py runserver > > -- > 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

7 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

How do I tell mailman to connecto to postfix? Is mailman able to use the smtp I use for our emails service with hostgator? Instead of using postfix?? Thanks El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > 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

7 years, 10 months

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

by Mark Sapiro

On 7/26/20 10:56 AM, Shashikanth Komandoor wrote: > Hi Team, > > I am currently running Mailman 3 with version 3.3.1 and in built postfix > version 2.10.1-6 on RHEL 7.5 in production environment from the past 2 > months almost. > > From the past few days, I found my server is responding to the users > very slowly and throwing the Server Error page (of course getting the > required page after multiple refreshes) for almost every click on the > postorius pages (not yet observed on hyperkitty front end which in fact is > not so important for me as of now). > > During that time, I observed in the mailman.log an error message saying > "Could not locate column in row for column 'user.id'". The complete > traceback log is attached with the mail. The error message is generated for > almost all the lists and all the clicks. I don't understand what's going on. I suspect some kind of database corruption, but I don't know what. The traceback indicates Mailman is getting the Members of a list and in this process is trying to get the display_name for a member. The member's subscriber attribute doesn't have a display_name so it is trying to get is from the member's user attribute so it is trying to get the user record for the member's email address via IUserManager.get_user(). This in turn gets the Address record for the email address and returns it's user attribute. This leads to the sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'user.id'" error which I don't understand. There is no table with a 'user.id' column. user.id refers to the id column in the user table which comes from the user_id column in the address table which should be a reference to the id column in the user table, not a reference to ay 'user.id' column. What is your backend database and what is the structure of the address table in that database. Have you done any kind of direct database query that might have affected this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Problems with shunted Mails

by Mark Sapiro

On 4/19/22 03:47, Stephan Krinetzki wrote: > Hi all, > > we currently have a problem sending to an email list. The mailing list is an announcement list and is therefore moderated. The mail also arrives for moderation. However, when the mail is released, it is not delivered, but moved to the shunt queue. The error after an unshunt attempt in the log: > > Apr 19 12:31:43 2022 (17967) Uncaught runner exception: 'NoneType' object has no attribute 'email' > Apr 19 12:31:43 2022 (17967) Traceback (most recent call last): > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 176, in _one_iteration > self._process_one_file(msg, msgdata) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 269, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", line 50, in process > handler.process(mlist, msg, msgdata) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/handlers/member_recipients.py", line 85, in <genexpr> > if member.delivery_status == DeliveryStatus.enabled) > AttributeError: 'NoneType' object has no attribute 'email' > Apr 19 12:31:43 2022 (17967) SHUNTING: 1650364303.8361175+08bb48ae877019e8a4c9dff8024c1270782fceb3 > > Any hints how we can solve the problem here? One of the list's regular members has no associated address record. I don't know how this can happen. You could find the member with mailman shell, e.g. ``` 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 >>> for mbr in m.regular_members.members: ... if mbr.address is None: ... mbr.subscriber ... mbr.user ... mbr.user.addresses ... mbr.user.preferred_address ... ``` You might be able to fix this with something like ``` >>> for mbr in m.regular_members.members: ... if mbr.address is None: ... mbr.address = mbr.user.preferred_address or member.user.addresses[0] ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

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

by Mark Sapiro

On 10/12/22 01:24, Onyeibo Oku wrote: > > Good Morning Everyone, > > I installed and managed mailman 2 for about two years. I am now > ready to try Mailman 3. The documentation for version 2 was lucid and > this forum was quite helpful in the past. > > Now I'd like to proceed with installating MM3 but I doubt my > understanding of the docs. It seems to assume that users will know what > to do. > > Okay, don't laugh! I just want to be sure what I am doing. Does the > following sequence resemble the proper steps? As Eggert says, we aren't laughing ... > 1. Download the source from a git repo (I understood that one) > 2. Create a virtual environment (venv perhaps ... not stated explicitly) > 3. activate the virtual environment > 4. from the git project root, run: ./mailman start Step 4 is premature. More below. > I know, its stupid. I had to ask. Not stupid ... > It would really build my confidence > someone would confirm the above steps or counter then with something > very explicit. What about process ownership? Do I need to have a unix > mailman user? What else do I need to get mailman up and running > before proceeding to configuration. Ahaa! I perused the config docs a > bit. Where can I find the .cfg file? As Eggert suggests, see https://docs.mailman3.org/en/latest/install/virtualenv.html and follow that. You don't need to download the source from GitLab. Following that doc will get the latest releases from PyPI via pip. Those are still somewhat out of date - we really should make new releases - so if you want the latest from GitLab, there are a couple of ways to do it. Perhaps the easiest is to just run the various `pip install` commands as documented and then upgrade Mailman core in your venv with ``` pip install --upgrade git+https://gitlab.com/mailman/mailman@master ``` and update the various mailman web packages with ``` pip install --upgrade git+https://gitlab.com/mailman/xxx@master ``` where xxx is mailman-web, mailman-hyperkitty, django-mailman3, postorius, hyperkitty. I.e., run it 5 times, once for each value of xxx. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed

by Shashikanth Komandoor

Thank you Mark Sapiro. As per your suggestion, I have gone through the mentioned URLs and understood that the command "mailman notify" is responsible to send the periodic notifications to the owners of the list which of course should be as part of the cron job list (but it is not in my case). FYI, I am using mailman 3.2.3. And in my case, when I run the command "mailman notify" I am getting an error saying that the command "notify" is not present. *(venv3) [root@mailman3 commands]# mailman notifyUsage: mailman [OPTIONS] COMMAND [ARGS]...Try "mailman -h" for help.Error: No such command "notify".* And I also saw the help menu of mailman where I don't find any command displaying "notify" and its explanation. I don't understand where I had done wrong. Could you please help me in this regard? On Thu, Jan 23, 2020 at 11:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > > Hi, > > > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was > working > > fine. But I found that I am not getting daily summary notifications for > > which I learnt after browsing through different websites, there should be > > an entry of *checkdb* in the cron job list. > > > checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman > notify` > > > > But I did not find any such nor I don't find any cron job updated > after > > the installation of mailman 3. > > > See > < > https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs > > > and > < > https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > > > > If you installed Mailman from a package and the cron's weren't > installed, report this to the packager. > > -- > 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 & Regards, Shashi Kanth.K 9052671936

5 years, 4 months

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

On 4/1/23 09:55, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > postfix seems working well. I's just there is nothing listening on port > 8024 because lmtp runner is not running :) > > (from maillog): > > connect to 127.0.0.1[127.0.0.1]:8024: Connection refused > > (another simple test) > > root@www:/usr/local/mailman3 # telnet localhost 8024 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > > I'm running out of ideas. Any clue to somewhere to dig in? > > > *-*-*-*-*-*-*-*-*-*-* runners started > > Apr 01 17:24:40 2023 (4681) out runner started. > Apr 01 17:24:40 2023 (4680) virgin runner started. > Apr 01 17:24:41 2023 (4679) command runner started. > Apr 01 17:24:42 2023 (4688) retry runner started. > Apr 01 17:24:43 2023 (4686) in runner started. > Apr 01 17:24:44 2023 (4683) digest runner started. > Apr 01 17:24:44 2023 (4684) nntp runner started. > Apr 01 17:24:45 2023 (4682) archive runner started. > Apr 01 17:24:46 2023 (4685) bounces runner started. > Apr 01 17:24:47 2023 (4687) task runner started. > Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages > Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries > Apr 01 17:24:48 2023 (4678) pipeline runner started. > Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages > Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart. You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start. As to why it died in the first place, there should be something in mailman.log from the time it died. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Search results for query "sapiro"