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

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

On 12/20/19 1:31 AM, Dieter Leupold via Mailman-users wrote: > Hi Mark, > > Thanks for your information. But, how I said, I'm new to MM3 and I have > problems with the syntax of the mailman shell. Please, could you give me > an example to set "pass_types" via MM-Shell? > Thank you very much! The documentation of Mailman shell is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…>. A simple example in for setting pass_types is ``` $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the list(a)example.com mailing list >>> m.pass_types <generator object MailingList.pass_types at 0x7fd7e1489840> >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain'] >>> list(m.pass_types) ['multipart', 'text/plain'] >>> At this prompt you can enter commit() to commit your changes, abort() to reverse your changes or control-D to commit and exit. You can also enter exit() to exit, but your changes will not be saved unless you have done a prior commit() -- 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: Correcting name spellings in a list

by Mark Sapiro

On 2/23/21 9:40 PM, Morris Jones wrote: > I typo'd some full names in a mailing list. I want to correct them ... > > I can't see a way to do that in the Member Options, so I thought I'd try > "remove" and re-add, either from the command line or the UI. > > But the name gets readded with the typo intact. :( > > Is there a way to fix it without writing SQL? You can do it with mailman shell. The basic issue is the display name is a property of the user or the user's address, which ever is subscribed to the list. When you add a previously unknown user to a list, Mailman creates these user and address records, but they belong to the user, not the list. There are some threads around this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and a somewhat protracted one 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

4 years, 9 months

[MM3-users] Re: Special Characters Issue when using Wordpress HTML messages

by Mark Sapiro

ryan.anderson.4--- via Mailman-users wrote: > > Thanks for the reply. I changed the language.master in the schema.cfg. > > [language.master] > # Template for language definitions. The section name must be [language.xx] > # where xx is the 2-character ISO code for the language. > > # The English name for the language. > description: English (USA) > # And the default character set for the language. > charset: utf-8 > # Whether the language is enabled or not. > enabled: yes And I replied but didn't include the list. My reply, reconstructed from memory: That change together with restarting Mailman core should allow those characters unreplaced as long as it isn't overridden in mailman.cfg. Note that it will apply only to new messages and not to previously archived ones. However, there are two issues with editing the master this way. It will affect the default settings for all languages, and it will be undone with any upgrade. It is much better to add ``` [language.en] charset: utf-8 ``` to your mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Include receipant address as a variable

by Mark Sapiro

On 6/4/22 09:22, chucka(a)blackforest-co.com wrote: > Thanks for the quick reply - I'm going to need a bit of schooling. I've looked at the page you point to and ... I'm lost - do I need to create a NL template? Can you give an example? &lt a href=https://mysite.com/my.pdf? &gt CLICK HERE ... The bad news is list headers and footers are plain text so HTML tags don't work. The good news is that many if not most MUAs will render things that look like URLs as clickable links. So, if you create a list:member:regular:header or list:member:regular:footer footer template that contains a line like ``` Go to https://mysite.com/my.pdf?$user_email to ... ``` That will replace the $use_email part with the recipient's lower cased email address. If you want the case-preserved email address, use `$user_delivered_to` instead of `$user_email`. For this to work, the list's Settings -> Alter Messages -> Personalize setting must be `individualize` or `full`. Also see https://wiki.list.org/x/4030707 for some caveats. -- 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: No option 'postmap_command' in section: 'postfix'

by Mark Sapiro

On 1/30/23 10:12, Odhiambo Washington wrote: > > So, since the creation of that file is prominent in the doco, maybe a note > can be added to that effect? I'm looking at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and my thought is at the paragraph Regular Expression tables remove the additional dependency of having postmap command available to Mailman. If you want to use regexp or Regular Expression tables, then add the following to Postfix’s main.cf file: add another section header Regular Expression Tables ------------------------- and change that text to Regular Expression tables are less efficient than hash tables, but they remove the additional dependency of having ``postmap`` command available to Mailman. If you want to use ``regexp`` or Regular Expression tables, then add the following to Postfix's ``main.cf`` file My thought is adding the section header makes it more clear that everything down to the Postfix + Dovecot section is for Regular Expression Tables and adding the `less efficient` phrasing notes the down side. What do you think? -- 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: mail loops back to myself

by Mark Sapiro

On 6/11/25 13:51, Florian Sukup wrote: > I have now elimiated reverse.rrr.com. But there isn't much change: > > vvvvvvvvvvvvvvvvvvvvvvvvv > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: initializing the > client-side TLS engine > Jun 11 22:19:57 arvak postfix/smtpd[1015581]: initializing the > server-side TLS engine > Jun 11 22:19:57 arvak postfix/smtpd[1015581]: connect from > host.xxx.com[m.y.i.p] > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: warning: host > host.xxx.com[m.y.i.p]:25 greeted me with my own hostname host.xxx.com > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: warning: host > host.xxx.com[m.y.i.p]:25 replied to HELO/EHLO with my own hostname > host.xxx.com > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: 29FCF5F867: > to=<mylists(a)lists.yyy.com>, relay=host.xxx.com[m.y.i.p]:25, delay=0.2, > delays=0.06/0.01/0.13/0, dsn=5.4.6, status=bounced (mail for > lists.yyy.com loops back to myself) > Jun 11 22:19:57 arvak postfix/smtpd[1015581]: disconnect from > host.xxx.com[m.y.i.p] ehlo=1 quit=1 commands=2 I think you need to add host.xxx.com to mydestinations. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: How to disable the password reset email, from being sent to an address not in our database?

by Mark Sapiro

On 11/26/25 11:21 AM, mrl(a)psfc.mit.edu wrote: > Hi - Someone just requested a password reset, for an email address not in the mailman database. Mailman sent a message to them, but the email was invalid. I would like to disable an email from being sent to a user not in the mailman database. How to do this? Thanks. - Mark There are Mailman users and Django users. Mailman users are people known to Mailman as members, nonmembers, moderators or owners of lists. Django users are people who've signed up for web accounts. Django users don't have to be Mailman users and vice versa. You can prevent Django-allauth from sending mail to unknown Django accounts with the ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS setting - see https://docs.allauth.org/en/latest/account/configuration.html#sending-email Also, there is an example script at https://www.msapiro.net/scripts/clean_users.py that can be used to remove Django users for which there is no corresponding Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 3 days

[MM3-users] Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/8/19 9:13 AM, Nick W wrote: > I've got a couple things I need help with: The Symptom and The Problem. > > The Symptom: > > Postorius has gotten quite slow to load, taking more than 30s to load the > Subscription Requests tab. Having zero pending subscription requests (I'm on > v1.2.5), I started investigating unconfirmed subscriptions. > > I followed the commands from here[1] and got this: > > mailman shell -l your.list.id > util = getUtility(IPendings) > print(len(list(util.find(mlist=m,pend_type='subscription')))) > 1816 > > Wow, 1816 pending subscription requests. I can say for certain that my list is > not popular so these requests must have been submitted by bots. Let's get there > in The Problem. > > How can I "purge" this list? I'm willing to assume that none of these requests > are valid and would reject all unconfirmed user requests. mailman shell -l your.list.id util = getUtility(IPendings) for token, data in util.find(mlist=m, pend_type='subscription'): util.confirm(token, expunge=True) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: > > I might also add the rule number or config filename:line, as in > > Header "{name}": rule in {file}:{n} matched value "{value}" > > This would be helpful when backtracking from a rejected message to the > cause. > > A sample expansion might be: > > Header "X-Spam": rule in foo.conf:83 matched value "yes" These rules are not in a configuration file. They are in the headermatch table in the database and the rules for a particular list are exposed on the Header filters tab in Postorius or at the REST lists/LISTNAME/header-matches endpoint. Perhaps something like {name}: header match rule, pattern "{pattern}" matched value "{value}" example: subject: header match rule, pattern "sex|long|list|of|other|bad|words" matched value "This is a post about filtering based on words like sex in the subject." but that could be just adding more clutter. -- 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: List is down - RemovedInDjango30Warning

by Mark Sapiro

On 2/15/21 9:07 PM, Mark Dadgar wrote: > So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. > > The resulted in a broken web interface. > > Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. > > Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. > > Anyone got a solution to this? From the tracebacks it looks like Django is broken. I would suggest starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ aside and create a new venv virtualenv /opt/mailman/mm/venv/ and then activate it and pip install everything. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > – but the existing directory /opt/mailman/fulltext_index (and its > contents) are readable and writeable by mailman:mailman: > >> drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ >> >> -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc >> -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg >> -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg >> -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg >> -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg >> -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg >> -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > I fail to see where haystack tries (and fails) to create the directory. > FWIW, deleting threads is not a problem. It is uwsgi trying to do this. What user is it running as? Maybe you need to add that user to the `mailman` group. Deleting threads is not an issue, apparently because it doesn't try to update the search index. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Mark Sapiro

On 12/6/21 2:51 AM, Stefan Bauer wrote: > Need to bring this up again. Django now sends with STARTTLS, but mailman > itself, does still only drop mails in cleartext. > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > No starttls=1 at all :( > > Does the above settings work for anyone? > > etc/mailman3/mailman.cfg > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > smtp_verify_hostname: false > smtp_verify_cert: false > smtp_secure_mode: starttls This should work. What do you see in Mailman's smtp.log if you add ``` [logging.smtp] level: debug ``` to mailman.cfg. However, do you really need this. It will only affect delivery from Mailman to Postfix via the loopback interface on the localhost. -- 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: Poor rendering of disabled registration page

by Mark Sapiro

On 12/22/24 04:16, Torge Riedel via Mailman-users wrote: > > 1. The page has a poor rendering, as far as I can see not css is referenced > 2. A would prefer that I am able to hide the registration button > > Is either of this possible to be fixed in the future? The lack of styling is fixed for django-mailman3 1.3.16 by https://gitlab.com/mailman/django-mailman3/-/merge_requests/303 You can fix it by adding the django_mailman3/templates/account/signup_closed.html file as in this patch: ``` diff --git a/django_mailman3/templates/account/signup_closed.html b/django_mailman3/templates/account/signup_closed.html new file mode 100644 index 0000000..bc83950 --- /dev/null +++ b/django_mailman3/templates/account/signup_closed.html @@ -0,0 +1,11 @@ +{% extends "account/base.html" %} + +{% load i18n %} + +{% block head_title %}{% trans "Sign Up Closed" %}{% endblock %} + +{% block content %} +<h1>{% trans "Sign Up Closed" %}</h1> + +<p>{% trans "We are sorry, but the sign up is currently closed." %}</p> +{% endblock %} ``` Disabling the signup button on the resultant page is trickier as that currently comes from the hyperkitty/templates/hyperkitty/base.html which is used all over. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by Mark Sapiro

On 1/26/22 22:21, dave--- via Mailman-users wrote: > > Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. > > The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). The password reset is for a Django user, which is distinct from a Mailman user. The users you added via the web API are Mailman users, but in order to access their lists via the web UI they have to `sign up` to create a Django account. -- 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: Mails sent by mailman-web runjobs hourly

by Mark Sapiro

On 6/16/22 03:44, Eggert Ehmke wrote: > I get lots of mails originating from the mailman-web runjobs hourly. They are > sent to mailman@<mytld>. The content looks like > > 07:00:03 [Q] INFO Enqueued 12571 > 07:00:03 [Q] INFO Enqueued 12572 > 07:00:03 [Q] INFO Enqueued 12573 > > How can I disable these emails? These message come from Django Q, https://django-q.readthedocs.io/en/latest/ I don't think there is a way to disable those specific messages which occur at times when tasks are queued instead of started immediately. They are sent to `mailman` because `mailman` owns the crontab and the crontab has no MAILTO=. You can redirect these and all other messages from hourly jobs by surrounding the hourly jobs command in the crontab with MAILTO= as in ``` MAILTO=other(a)example.com @hourly /opt/mailman/mm/bin/django-admin runjobs hourly MAILTO=mailman ``` or possibly discard them with something like ``` @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > /dev/null ``` but either of these could redirect or discard other messages from hourly jobs which you might want. -- 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: spanish localization

by Mark Sapiro

On 2/12/21 3:21 AM, Victoriano Giralt wrote: > > I just wanted to make visible that the .mo files were a "bit old". For > example, Guillermo, in this thread, pointed that the Spanish > translation was quite compelte. Actualy, I spent some hours bringing > them to 100% around Christmas. But, the .mo file for es from the pip > install --update i did recently is dated November 7th. I have > definitely added a lot of translated material from then until the end > of the year. Why do you say the .mo files are old. The timestamps are all Feb 3 02:47 which is when the package was built for PyPI. > I know the translation happens outside the development community. I > tried to point that there might be some synchronisation problem, so to > say, between the translation site and the packaging of the latest > mailman release. When things are changed on weblate, we get automatically generated merge requests to update our source. We don't always merge them immediately, but we certainly do merge all the outstanding ones before making a release. -- 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: Schedule for a resolution of #406, #410 and #437

by Mark Sapiro

On 12/14/2017 02:14 PM, Abhilash Raj wrote: > On Wed, Dec 13, 2017, at 12:11 AM, Henrik Rasmussen wrote: >> I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, >> #410<https://gitlab.com/mailman/mailman/issues/410> and >> #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It >> seems that it would not be far, as >> !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to >> be merged. > > Merged right now! :) And I have updated lists.mailman3.org and mail.python.org. Note however that <https://gitlab.com/mailman/mailman/merge_requests/322> does not fix <https://gitlab.com/mailman/mailman/issues/437> as noted at <https://gitlab.com/mailman/mailman/issues/437#note_46539617>. It also doesn't fix <https://gitlab.com/mailman/mailman/issues/441>. That appears due to a new bug related to <https://bugs.python.org/issue27321>, but which is a different message defect that causes UnicodeEncodeError to be thrown instead of KeyError. I have reported this at <https://bugs.python.org/issue32330>. I have created <https://gitlab.com/mailman/mailman/merge_requests/350> and <https://gitlab.com/mailman/mailman/merge_requests/351> to fix these issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: So near, and yet so far (Configuring Mailman)

by Mark Sapiro

On 1/29/21 3:52 PM, Jack Lenox via Mailman-users wrote: > > Good news everyone! I've got it working. It turns out my issue was with > the mynetwork IP settings in my Postfix config. Things do now appear to > be working. Good. Thanks for the update. > My only remaining issue is that the posts aren't appearing > in the archive. Hmm. If you want our help with that, tell us if you have any non-default [archiver.*] settings in mailman.cfg and what the list's Settings -> Archiving settings are. If you are expecting HyperKitty archiving, are messages remaining queued in Mailman's var/archives/hyperkitty/spool/ directory and if so, what kind of errors do you see in Django's log? Does the value for MAILMAN_ARCHIVER_KEY in your Django settings match the api_key in the [general] section of the mailman-hyperkitty.cfg (or whatever you call it), quoted in MAILMAN_ARCHIVER_KEY but not in api_key, and is the base_url setting in the [general] section of the mailman-hyperkitty.cfg a URL that can actually access hyperkitty? -- 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: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/21/23 14:50, ceo(a)sartrack.nz wrote: > I copied the wrong debug data in my original post, it should be this: > > --------> mailman3_router router <-------- > 2023-05-22 05:13:59 115223 local_part=templist domain=sartrack.nz > 2023-05-22 05:13:59 115223 checking domains > 2023-05-22 05:13:59 115223 sartrack.nz in "sartrack.nz"? yes (matched "sartrack.nz") > 2023-05-22 05:13:59 115223 data from lookup saved for cache for +mm_domains: key 'sartrack.nz' value 'sartrack.nz' > 2023-05-22 05:13:59 115223 sartrack.nz in "+mm_domains"? yes (matched "+mm_domains") > 2023-05-22 05:13:59 115223 checking require_files > 2023-05-22 05:13:59 115223 file check: /var/lib/mailman3/lists/${local_part}@${domain} > 2023-05-22 05:13:59 115223 expanded file: /var/lib/mailman3/lists/templist(a)sartrack.nz > 2023-05-22 05:13:59 115223 stat() yielded -1 I'm not an Exim expert although I have used it. The above says Exim was unable to stat /var/lib/mailman3/lists/templist(a)sartrack.nz - does that file exist. Does exim have search permission on all the directories in the path and read permission on the file? > 2023-05-22 05:13:59 115223 errno = 2 > 2023-05-22 05:13:59 115223 mailman3_router router skipped: file check -- 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: Migration of the e-mail templates

by Mark Sapiro

On 3/6/25 2:24 PM, Markus Grandpré wrote: > > Thank you for your prompt reply. Based on a customer request, it seems > that custom templates need to be copied manually. Could you kindly > indicate which files and locations should be considered when > transferring them from the source to the target system? In MM 2.1, you could have list specific templates in directories like lists/<listname>/<language>/, domain specific templates in directories like templates/<list.host_name>/<language> and sitewide templates in directories like templates/site/<language>. In MM 3 You can create list and domain specific templates in Postorius or you can create them in sub-directories of Mailman's var/templates/ directory. List specific templates in lists/<list-id>/<language>/, domain specific templates in directories like domains/<mail-host>/<language>/ and sitewide templates in directories like site/<language>/. However, you can't just copy MM 2.1 templates because the variable replacement syntax is different and the template file names are different. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documentation of the MM 3 templating system. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Reg Archive Inactive Status and not working in Mailman

by Mark Sapiro

On 9/23/25 04:40, nirmal--- via Mailman-users wrote: > I am having the issue with Mailman Archive not working. Kindly help me to solve the issue. > > > Errors Found in:- > File "/usr/lib/python3/dist-packages/requests/adapters.py", line 489, in send > resp = conn.urlopen( > ^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 789, in urlopen > retries = retries.increment( > ^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 594, in increment > raise MaxRetryError(_pool, url, error or ResponseError(cause)) > urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive?key=n%2FZZnR5bRgNdUEyNK4p731C1%2BgWJLw0%2F (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)'))) Your setting for base_url in mailman-hyperkitty.cfg is an https url, but the addressed server is not configured properly to handle https. If the setting is something like base_url: https://localhost:8000/hyperkitty/ change it to http or change the url to the one used to access hyperkitty from a web browser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 2 weeks

[MM3-users] Re: Setup Mailman3 on shared webhost

by Mark Sapiro

On 11/5/18 5:42 AM, Keyra wrote: > Iam trying to setup mailman3 on a shared webhost (with ssh access). I > could use > > pip3.6 install mailman --user > > and also > > mailman info > > But when I try to start mailman using > > mailman start > > I will first get the error message > > TypeError: expected str, bytes or os.PathLike object, not NoneType > > and when I try it a second (and third etc.) time, it throws > > Starting Mailman's master runner > /usr/bin/python3.6: can't open file '/usr/bin/master': [Errno 2] No > such file or directory > > I didn't get any error messages during installation, so I guess whatever > mailman is looking for in /user/bin/master is available in my > /home/user/ folder, but I have no idea where and how to tell mailman to > look there. For more infos, this is the output of `mailman info` The 'master' command should be in the same directory as the 'mailman' command that you run. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 05/18/2018 03:50 AM, Henrik Rasmussen wrote: > > What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. Setting the policy to Confirm or Confirm, then Moderate will do that as long as admins don't use the mass subscribe feature without a confirmed request from the user. > Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Manually. I.e.post a request to the list with a deadline for response and remove those that don't respond. Or, post to the list that everyone will need to resubscribe and then remove everyone. -- 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: Can't remove footer(s)

by Mark Sapiro

On 10/02/2018 01:03 AM, Henrik Rasmussen wrote: > > Copying /dev/null doesn't help. It seems to be the same old content of the footer files before I removed the files and restarted Mailman, as if Mailman keeps the cache. > > I've just (again) ran > # docker exec -it mailman-core mailman shell -l [LISTNAME_FQDN] >>>> getUtility(ITemplateManager).delete('list:member:digest:footer', m.list_id) >>>> getUtility(ITemplateManager).delete('list:member:regular:footer', m.list_id) > > after copying /dev/null to the files in /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/list_member_digest_footer.txt and list_member_regular_footer.txt ,but that doesn't change anything. The templates named list_member_digest_footer.txt and list_member_regular_footer.txt (with underscores) were created by import21 and set as the URIs for those templates. Had you just copied /dev/null (or otherwise made empty) those files and done nothing else, that would have done what you wanted, but since you deleted the template URIs for the list, the template names are now the default list:member:digest:footer.txt and list:member:regular:footer.txt names (with colons) and those are the empty files you need to create. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/27/21 4:04 AM, Henrik Rasmussen wrote: >> Thanks for the hint Steve. There is a Spanish message catalog as >> evidenced by the fact that the reason was translated to Spanish, but the >> issue is almost certainly that there is no >> mailman/templates/es/list:user:notice:post.txt template so we fall back >> to the one for the list's language. > > I should note that my tests on same list with same language setup did not mix languages, for some reason and I can't replicate the problem. I wonder if it could have been a timing issue or the order that I changed languages on list language and user preference. I really think it has to do with two conditions: 1) the user's preferred language is Spanish 2) there was no mailman/templates/es/list:user:notice:post.txt template There were Spanish templates in Mailman core 3.3.4, but they were misnamed, e.g. list_user_notice_post.txt instead of list:user:notice:post.txt. Did you somehow add a mailman/templates/es/list:user:notice:post.txt template after the initial test? -- 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: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 6:20 PM, David Newman wrote: > > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… although that's with apache and not nginx so it may not be. > Adding a stanza for 'location /mailman/' to the nginx config above > clears the 404 error, but Postorius returns "Page not found" with no > entry in the web or MM3 logs, and a 200 OK in the Nginx logs. > > I think the URL is supposed to go to the list page in Postorius. How to > configure this so that list owners and moderators get a valid URL for > list management? I'm not sure what the solution is in this case, but a workaround would be to add url(r'^mailman/', include('postorius.urls')), to the urlpatterns list in urls.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, 11 months

[MM3-users] Re: deleting a list of spammers from non-member list

by Mark Sapiro

On 10/2/25 11:41, Philip Bondi via Mailman-users wrote: > Hello to all: > > I've studied the following: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > ```bash > mailman shell -l mmlist.domain.ca << EOF | tr , '\012' > nonmember.txt > list(m.nonmembers.members) > EOF > ``` > > I was able to produce a clean list of 50 non-member email addresses that are spammers. > > How would I take this list of non-members and delete them? I was unable to use mailman delmembers Assuming you want to delete all the nonmembers, just do it all in mailman shell. Using the above ```bash mailman shell -l mmlist.domain.ca << EOF for member in m.nonmembers.members: member.unsubscribe() EOF ``` If your 50 addresses are not all the nonmembers and you only want to delete those 50, the bash script could be ```bash mailman shell -l mmlist.domain.ca << EOF for addr in open('nonmember.txt').readlines() member = m.nonmembers.get_member(addr.strip()) member.unsubscribe() EOF ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Mark Sapiro

On 8/2/20 12:42 PM, Odhiambo Washington wrote: >> >> It is currently linked from the first paragraph at >> <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. >> > > I followed the steps outlined in the subject document and got mailman3 > running. > However, what is missing in that document is the process of setting up a > webserver for accessing the MM3 UI. > I have spent two days trying to figure out that aspect and discovered a few > things (I could be wrong in what I think): Which document are you talking about? If you mean <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…>, that talks about the Debian/Upuntu package installation and that package is quite behind the current releases. I thought that after mush back and forth with you following <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you got Mailman 3 up and running, so why would you now be trying to install the Debian/Ubuntu package? If you have issues with the <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…> document, you should contact its author. See <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 11:10 AM, dancab(a)caltech.edu wrote: > > We do have mailman(a)caltech.edu configured with valid members/owners. > We're using Postfix for the MTA. Is it possible there's a misconfiguration there? > > We've been testing the system with a handful of lists for months. The bounce you saw From: Mailman mailman(a)example.com To: Mailman Bounces mailman-bounces(a)example.com Subject: SMTP Delivery Failure may have sent because you have VERP probes enabled (verp_probes: yes in the mta section of mailman.cfg) and a user on some list reached the bounce score threshold and a Mailman attempted to send a probe and the MTA refused the message, or it may have been sent because Mailman attempted to send a message to the user and the MTA refused it. In either case, the bounce message (fake DSN) should have contained a message body like Mail to user(a)example.com failed at outgoing SMTP with the actual user's address. These fake DSNs are sent in the case where the outgoing MTA refuses a message from Mailman so there is no actual failure DSN. -- 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: EMWD Mailing Lists Down

by Mark Sapiro

On 1/15/22 5:49 PM, Sherry Xie wrote: > Hi all, > > I am an EMWD Mailman 3 customer, and I recently realized my mailing lists > are no longer working (the last email that went through was sent on > December 25, 2021). Emails I send to the lists do not show up in archives > or reach subscribers. It seems like others have had this issue before > since ownership of the company was transferred following Brian Carpenter's > passing – has anyone been able to get in touch with support or get their > issues resolved? > > I've submitted a support ticket but have no idea if this is being > monitored. I also have no way to contact the current management team, as > only their names were announced in the November 5, 2021 email from Barbara > Carpenter. Any help would be greatly appreciated – thanks in advance! There is a recent thread on this started at https://mail.python.org/archives/list/mailman-users@python.org/thread/N7NJL… and continued at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You might find something helpful there. -- 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: MM3+Python3.11

by Mark Sapiro

On 3/6/23 03:38, Odhiambo Washington wrote: > Has MM3 been tested with Python3.11? Yes, but not with uWSGI which is not part of Mailman per se. > I updated a Debian VM to Python3.11, installed MM3 and migrated the > configs. However, I am unable to get past the following error: > ... > Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/wsgi.py", line > 10, in <module> > from django.core.wsgi import get_wsgi_application > File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", > line 1, in <module> > from django.utils.version import get_version > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/utils/version.py", > line 1, in <module> > import datetime > File "/usr/lib/python3.11/datetime.py", line 12, in <module> > import math as _math > ModuleNotFoundError: No module named 'math' > unable to load app 0 (mountpoint='') (callable not found or import error) This error says /usr/lib/python3.11/datetime.py can't import math. math is part of the python 3.11 standard library <https://docs.python.org/3/library/math.html>. There is something wrong with your Python 3.11 installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: OS upgrade - anything to take care of?

by Mark Sapiro

On 5/13/21 1:58 PM, Ruth Ivimey-Cook wrote: > > Sadly they aren't - they link to python3.6 or whatever... and even if > not, the /lib/ naming gets you as well. > > And even if that can be worked around (eg by renaming the mailman > /lib/python3.6 folder to /lib/python3.8), the python .pyc files are > /also/ versioned, so you then have to find & delete them all to force > the new interpreter to rebuild them or python falls down in a heap. Maybe I'm missing something, but it seems to me that if /usr/lib/python3.6 and /user/bin/python3.6 are gone, just creating symlinks from /usr/lib/python3.6 and /user/bin/python3.6 to the corresponding python3.8 directories would work. The .pyc files in __pycache__ should not be an issue. They are versioned and placed in a __pycache__ directory specifically so multiple python versions can coexist. See <https://www.python.org/dev/peps/pep-3147/>. Python3.8 will just make new ones. If there is some issue with this, one can always do ``` find /path/to/venv -name '*.pyc' -delete ``` -- 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: Problem with digests not being sent daily

by Mark Sapiro

On 6/22/24 20:04, Mark wrote: > > Oh? I was indeed assuming that 0 meant unlimited. The threshold was set > at 0. > > My thinking was that meant the file size was not a factor in > determining when the digest was sent and that the sending would be > triggered by the daily cron. If Send Digest Periodically is Yes, digests will be sent by the daily (or whatever schedule) cron. If a digest reaches threshold in between runnings of the cron, one will be sent at that time. > When I set the threshold very low - 10kB - it sends a digest on every post. This is expected and the same should occur if the threshold is 0. > So my understanding of what you are saying is: if the threshold is set > very large, say 100,000 kB - then a digest will be be sent by the daily > cron even if it is smaller than 100,000 kB. Correct. If Send Digest Periodically is Yes, any accumulated digest will be sent when `mailman digests --periodic` runs, regardless of size. -- 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: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 4:24 PM, Seth Seeger wrote: > > Ah hah! Right you are. I removed the offending fancy apostrophe. What about that traceback pointed to the template? (Is it something I could have figured out?) The key is this entry in the traceback. > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), This says we are trying to make a MIME text message part based on expanding the substitutions in a template. A look at the source at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… says the template is list:admin:action:post. > Is it possible to filter out UTF-8 chars from the templates when they are saved in Postorius? Not really. Postorius would have to know the character set of the list's preferred_language in order to filter anything from the template that wasn't a valid character in that character set, and I don't think it has a way to get that information from Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 05:25, Odhiambo Washington wrote: > I looked at my list archives and saw that the latest post was on Dec 8, > 2022. > Then, because I wanted to import any posts that happened from 8th to now(), > I looked at two posts: > 1. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > This talks about 'hyperkitty_import *--since=01.01.2022* -l mylist@mydomain > my-mbox-file' > > 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html > Which talks about 'hyperkitty_import *--since='1990-01-01'* -l > mylist@mydomain my-mbox-file' The default without the since= option is to import only those messages from the mbox which are newer than the newest message in the existing archive which is exactly what you want. > I am concerned about the implication of the date format here, especially > because our species from America write their dates differently than the > British, even though > the British colonized us all :P hyperkitty_import uses python-dateutil <https://dateutil.readthedocs.io/en/stable/> to parse the since date. See <https://dateutil.readthedocs.io/en/stable/parser.html> for info on formats. -- 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: Add member to a list by email

by Mark Sapiro

On 11/12/24 02:00, via Mailman-users wrote: > Hello, > > I'm trying to add members by email with the following content. > > Recipient: testlist-request(a)xxxxxxxx.de > Email content: join address=max.mustermann(a)xxxxxxxx.de > > After I've sent this email, it still has to be confirmed in the Postorius web interface under member requests. How can I confirm membership by email, or deactivate this confirmation for moderators? You can use the email `confirm` command to confirm the request, but you need the token associated with the request to confirm it, and there is no good way to find it as it is not in the confirmation request notice sent to the list admins. To not require moderator confirmation at all, you can set the list's subscription policy. Normally, subscriptions should require confirmation by the user, a list admin or both. You can set it to require neither, but this is normally a bad idea if list addresses are accessible from outside your local network as it allows anyone to subscribe anyone else by spoofing their address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/2/22 12:04 PM, Andy Smith wrote: > > For ~6k messages it still took approx 16 hours to run that monthly > job, and during that time spewed out thousands of these errors: > > Failed to remove document 'hyperkitty.email.29351' from Whoosh: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove > self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query > w = self.writer() > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer > return SegmentWriter(self, **kwargs) > File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ > raise LockError > whoosh.index.LockError > > …so I'm not even sure if it worked. I think the warnings come from the hourly update_index job which can't obtain a lock on the index because the update_and_clean_index job already has it locked. Once the update_and_clean_index job finishes the update_index job should run and do the right thing. -- 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: Owner's or Moderator's Lists

by Mark Sapiro

On 7/31/20 11:09 AM, Johnny Cison wrote: > > It's 1.1.2, which is the python3-django-postorius version included with the > package manager on Ubuntu 18.04. > > Is there by chance a mechanism for viewing that information in 1.1.2? You have several choices. 1) Do nothing and wait for Debian/Ubuntu to upgrade the package and backport it. 2) Try upgrading Postorius from source or with pip. This will probably result in disaster, and even if it doesn't, will probably also require upgrading django-mailman3, mailmanclient and mailman core to support new features in Postorius. 3) See the merge requests at <https://gitlab.com/mailman/postorius/-/merge_requests/349>, and if you have >50 lists, <https://gitlab.com/mailman/postorius/-/merge_requests/437> and try patching installing those changes as patches. Note that!349 patches 15 files, but one of them is the change log and 12 are related to tests. The only ones you need to patch are postorius/templates/postorius/index.html and postorius/views/list.py. Likewise, these two are all you need from !437. 4) Abandon the Debian/Ubunto package and install the whole suite from source or with pip. -- 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: Question about adding addresses using the REST API

by Mark Sapiro

On 1/15/22 10:03 AM, Stephen Daniel wrote: > > The only way I've found to create a standalone address (not linked to any > user) is to create a user with that address, unlink the address, then > delete the user. > > Is there a more straightforward way to just create an address with no user? The more straightforward way is via the IUserManager create_address method. This method is not exposed directly in REST, so you can't do it via REST. My question is why do you want to? Granted when an unknown nonmember address posts to a list we create a standalone address record, but maybe we should be creating a user too. We don't because it's tricky. Suppose User A with address A posts to a list from nonmember address B. We create the standalone address B record as a nonmember, but now user A can add address B as another address. If we also created User B, this would not be possible. But again, what is your use case for creating standalone addresses? -- 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: How to fix lists with characters errors?

by Mark Sapiro

On 3/22/24 05:37, Helio Loureiro wrote: > Hi, > > I just found several lists have the issue like this regarding charset: > > (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members ... > Traceback (most recent call last): ... > line 109, in display_members > print(f'{address.display_name} <{address.original_email}>', > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > position 9: ordinal not in range(256) There is something in your python that has set the encoding for stdout to latin1 instead of the default utf-8. E.g. ``` $ python3.10 Python 3.10.9 (main, Dec 11 2022, 12:59:24) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> name = 'abc\u0142def' >>> print (f'{name}') abcłdef >>> import sys >>> sys.stdout.reconfigure(encoding='latin1') >>> print (f'{name}') Traceback (most recent call last): File "<stdin>", line 1, in <module> UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in position 3: ordinal not in range(256) >>> ``` -- 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: Upgrade to 3.3.2 fails

by Mark Sapiro

On 12/27/20 12:12 AM, Torge Riedel wrote: > > Nice to hear, but I fear you could be hit by this issues again, > depending on changes in the future on the table. Either when more > columns are added or on runtime when rows are added / updated. It seems that is a possibility with MySQL. It may not be an issue with MariaDB. It isn't completely clear to me from <https://mariadb.com/kb/en/innodb-limitations/#limitations-on-size>, but it seems that VARBINARY, VARCHAR, BLOB and TEXT columns are only counted as a few bytes in the "roughly half the page size" calculation. > @Mark: Would it be a good approach to split the table 'mailinglist'? I > see some groups of columns like "bounce_*" or "dmarc_*" which could be > managed in separate tables. Currently, those list attributes which are stored in tables separate from the mailinglist table are (some of) those that have lists of values rather than a simple value, but it would certainly be possible to separate groups of related attributes into separate tables. Care to submit 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, 11 months

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

by Mark Sapiro

On 4/25/24 04:35, Thomas Stein wrote: > > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE This is a packaging issue in the Debian/Ubuntu package and should be reported to Debian. See the BREAKING CHANGE item in the 1.3.10 section at <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. You need to add `allauth.account.middleware.AccountMiddleware` to the MIDDLEWARE setting in your Django settings. -- 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: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > Is nntp common enough these days to be a useful default runner? > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > resources (yet another Python interpreter running) for a fairly edge > case of mailing list <--> nntp transits. You raise an interesting point. By default, the runner runs, but if there are no lists gating to usenet, its queue is always empty and it mostly sleeps between waking, finding its queue empty and going back to sleep. A more significant use of resources is every (default) 5 minutes spawning `mailman gatenews` which goes through a startup process and then looks at every list figuring out there's nothing to do. We could default mailman.cfg to contain `start: no` in the runner.nntp section so people would need to enable it if they wanted it. What do others think? -- 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: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/9/19 11:16 AM, kelly.close(a)lrewater.com wrote: > I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. > > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… Thank you for this. I'm sure it will be helpful. One caveat. The Mailman 3 package for Ubuntu 18.04 is core version 3.1.1. This version when used with the MySQL back end database can have a serious issue. It doesn't affect the PostgreSQL back end database, only MySQL and maybe MariaDB, and it is fixed in Mailan core 3.2.0. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> 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

6 years, 8 months

[MM3-users] Re: Can't open PID file after start.

by Mark Sapiro

On 4/21/20 10:16 PM, Torge Riedel wrote: > Hi, > > today there were some package upgrades on my server for python3. Just to > be safe I did a "systemctl restart mailman" afterwards. Calling > "systemctl status mailman" gave me the following output: > ... > Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... > Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner > Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file > /opt/mailman/var/master.pid (yet?) after start: No such file or directory > Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. > > Should I treat the PID message as an info or is it an error and > something is now broken? The file is there (content is 24182) and > timestamp is from the time where I restarted mailman. It's normal and just info. The key is "yet?" The [Service] section in Mailman's systemd service file references /opt/mailman/var/master.pid as PIDFile and systemd looks for it before Mailman has created it. -- 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: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 10:49 AM, Mark Dadgar wrote: > > Here’s what I get when I attempt the above commands: > > root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell > Python 3.8.2 (default, Apr 27 2020, 15:53:34) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. The `django-admin` command that is being run doesn't itself point to your settings. In my case, I run django-admin via a wrapper that contains ``` #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ ``` The critical things are the exports of PYTHONPATH and DJANGO_SETTINGS_MODULE. The former is the path to where your settings module lives and the latter is its name without the .py extension. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: aborted connection

by Mark Sapiro

On 2/19/22 14:14, Sandor Dibuz wrote: > > It's the mailman quarterly cron job: > > # 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 > > And I have no gateway enabled for any of them. Will have to find out > what mailman exactly does. And change MariaDB to verbose logging. First, If your Mailman core version is >= 3.3.5, you shouldn't be running gatenews via cron. Mailman's nntp runner runs it. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… But, that probably isn't it because in Mailman >= 3.3.5, running gatenews via cron should produce this error The gatenews command is run periodically by the nntp runner. If you are running it via cron, you should remove it from the crontab. If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the environment. However, since you have no lists using a news->mail gateway, you don't need to run gatenews at all so just remove it from the crontab. -- 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: How to let mailman log every single email that it sends out?

by Mark Sapiro

On 9/9/23 09:13, Mohsen Masoudfar wrote: > Thank you, Mark, but Sorry, I don't see them there. > I read that the mta log level should be set to debug in order to see them. > When I send an email to a list with +3000 subscribers and need to see in the log email has been sent to each of those email addresses If you want to see individual recipient emails in /var/log/mail.log, the best way is to enable VERP in mailman. I.e., set ``` verp_delivery_interval: 1 ``` in the [mta] section of mailman.cfg. Then you should see entries like: > Sep 9 16:14:31 mail postfix/qmgr[1158516]: 7561EFC0A5: from=<mailman-users-bounces+mmasoudf=aaas.org(a)mailman3.org>, size=1276, nrcpt=1 (queue active) > Sep 9 16:14:33 mail postfix/smtp[1831181]: 7561EFC0A5: to=<mmasoudf(a)aaas.org>, relay=aaas-org.mail.protection.outlook.com[104.47.59.138]:25, delay=1.6, delays=0.01/0/0.35/1.2, dsn=2.6.0, status=sent (250 2.6.0 <169427602883.1158168.2180174954874478353(a)mail.mailman3.org> [InternalId=4823248279498, Hostname=IA1PR20MB6503.namprd20.prod.outlook.com] 10538 bytes in 0.177, 58.037 KB/sec Queued mail for delivery) in /var/log/mail.log for each recipient. -- 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: mail loops back to myself

by Mark Sapiro

On 6/9/25 05:06, Florian Sukup wrote: > > The setup has historic reasons. However I can eliminate reverse.rrr.com > completely and replace it by host.xxx.com. Right now reverse.rrr.com has > an A-record pointing to the host's ip address. Eliminating reverse.rrr.com completely and replacing it by host.xxx.com would be good. This will help. Also if I look up the A record for reverse.rrr.com either locally or at aaron.ns.cloudflare.com there isn't one. This will be moot if you replace reverse.rrr.com with host.xxx.com. >> What is the output from `postconf -n`? >> > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > append_dot_mydomain = no > biff = no > compatibility_level = 2 > inet_interfaces = all > inet_protocols = all > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/var/lib/mailman3/data/postfix_lmtp > mailbox_size_limit = 0 > message_size_limit = 0 > mydestination = localhost, localhost.localdomain, arvak This needs to include $myhostname Also, including reverse.rrr.com would help with your current setup, but instead you should just eliminate reverse.rrr.com completely and replace it by host.xxx.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > Hi, > > I have installed mailman3 with postfix. The server is working fine. To > protect the IPs from blacklisting, I want to relay all emails from > postfix/mailman to external SMTP servers like O365, Gmail, or our exchange > server. I would not recommend using O365 or Gmail as outgoing MTAs. I don't really know about )365, but I don't think Gmail likes you to send mail via a gmail server if it is not From: (or maybe envelope from or both) a gmail or googlemail address. > Could you please confirm is this possible. And how to do its configuration. It is possible and there are two ways to do it. You can configure this in Postfix to relay all outgoing mail via some other server. You can configure it in Mailman by setting in the [mta] section of mailman.cfg smtp_host: smtp_port: and presumably for authentication smtp_user: smtp_pass: Also see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… and following for other relevant settings. -- 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: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:01 PM, maszap(a)tin.it wrote: > Thank you, > but using roundcube, i can send email to all domains. That doesn't mean Mailman can. > These are just the lines I added to /etc/postfix/main.cf > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp You may need to add relay_domains = hash:/var/lib/mailman3/data/postfix_domains to your postfix main.cf. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Look in Mailman's smtp.log. You are looking for messages like: <timestamp> (pid) <message-id > post to <list-id> from <poster> nnn bytes and <timestamp> (pid) <message-id > smtp to <list-id> for nn recips, completed in nn.nnn seconds If the 'nn recips' matches the expected number of list members, the message was delivered to the MTA for all the recipients. If it then wasn't delivered to some of them, that's an issue with the MTA. Check the MTA's logs. -- 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: Discard all mail with the subject "The resutls of your email commands"

by Mark Sapiro

On 9/25/20 1:16 AM, w.schoener(a)alp.dillingen.de wrote: > Hello, > I am using mailman 3.2.1 for several mailing lists. My colleagues want me to stop all mails with the subject "The results of your email commands". > I found some contributions here, but nowhere a solution for this question. > Does anybody has any suggestion? > Maybe I could try to handle this outside of mailman, but then I would have to pass this task on to someone I dont know .... :-( > Thanks for all hints. :-) Doing it in the MTA, even though you don't want to, may be best as, with postfix for example, you can do it with header_checks. To do it in Mailman 3, patch mailman/runners/command.py and comment out or remove the last line ``` reply.send(mlist) ``` Are you really sure you want to do this at all. It means for example that one can't get a response to a `help` or the new `who` command among others sent to the -request address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: using SSH/TLS with external MTA

by Mark Sapiro

On 7/28/24 09:54, Roland Giesler via Mailman-users wrote: > > These settings from the Django docs look like the ones in mailman.cfg. > Do I have to set them somewhere else too? Yes. The settings in mailman.cfg only affect mail from Mailman. For mail from Django, you have to set things like EMAIL_HOST = 'box2.gtahardware.co.za' EMAIL_PORT = 465 EMAIL_HOST_USER = 'roland(a)giesler.za.net' EMAIL_HOST_PASSWORD = '...' and possibly others as desired, See the links to the Django docs for these. > * |use_tls|:|EMAIL_USE_TLS| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T…> > * |use_ssl|:|EMAIL_USE_SSL| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S…> > * |timeout|:|EMAIL_TIMEOUT| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO…> > * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K…> > * |ssl_certfile|:|EMAIL_SSL_CERTFILE| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C…> This all goes in your Django settings which from other posts I gather is /etc/mailman3/mailman3-web.py. I'm guessing you are using the Debian packages and that's where the package puts the Django settings. -- 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: Can't deliver mails in queue

by Mark Sapiro

On 5/20/21 4:01 AM, Nathanael Schneider wrote: > > It would have been nice though to have a more refined error to figure > this out. But its solved now and hopefully this will help someone else > as well. I'm glad you resolved it, and I'm sorry I didn't consider the template issue myself. You actually had two separate template issues. If you created templates in Postorius, they were inaccessible because of the POSTORIUS_TEMPLATE_BASE_URL issue, but your initial problem with imported lists is different. It probably resulted from running the `mailman import21` command as root which you should never do. You should always run `mailman` commands as the Mailman user. This is mentioned at https://docs.mailman3.org/en/latest/migration.html#id1 The `mailman import21` command can create list specific templates in Mailman's var/templates/lists/LIST_ID/LC/ directory and if run as root these will be user:group root:root and not world readable and therefore can't be read by Mailman. Also, deleting and recreating the list with the same LIST_ID doesn't remove those templates, so the list still doesn't work. -- 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: Question to add "alias" address in list by group

by Mark Sapiro

On 4/28/22 08:43, Pierre Malard via Mailman-users wrote: > > These are authorized alternate email addresses. For example A@domain is subscribed to the Z list of which only members can contribute but we also want to authorize some other address of A (A@domain2, …) as an « alternative" email contributor. > In the Mailman2 version this was called "accept_these_nonmembers" and it actually got added to that "non-members" list in mailman3. There is still an accept_these_nonmembers list in MM 3, but it is intended to support only regexps. For individual addresses, the preferred method is to create a nonmember record and set it's moderation action to default processing. The current import21 will import *_these_nonmembers in this way. I.e., import regexps into *_these_nonmembers and create nonmembers with appropriate moderation action for non-regexp addresses. However, the better method for your use case is for A@domain to add A@domain2, … as additional addresses. This can be done by the user via the web UI or via REST https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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: About the link destination of the logo image of the homepage

by Mark Sapiro

On 09/29/2018 09:06 AM, Ooyama Yosiyuki wrote: > At next page: > https://www.gnu.org/software/mailman/ > > Despite the fact that "Mailman" is written in the logo on the upper left of the screen, > However if I click the logo image on the upper left of the screen,then it is to move to https://www.gnu.org/software/ > > I think it is strange. Yes it is strange, but it is an artifact of the fact that the same page is used at all of <http://www.list.org/>, <https://www.gnu.org/software/mailman/>, <http://www.list.org/>, <http://mailman.sourceforge.net/> and <http://mirror.list.org/>, and only the www.gnu.org site has extra pieces in the path to the home page. However, it can be fixed and I've done so. Thanks for the report. > In the Wikipedia English version, the following address is introduced as mailman's website. > www.gnu.org/software/mailman/ It probably should be <http://www.list.org/>, but that's up to wikipedia. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Where to find disabled members?

by Mark Sapiro

On 11/4/24 19:28, Bill Oliver wrote: > > a) See who is disabled, and > b) un-disable them by hand > > or... do I just have to wait seven days for them to automatically get > un-disabled? They do not get automatically re-enabled ever the user or you has to manually re-enable delivery. For an individual user, in Postorius you can click the user in the members list and see their delivery status and reset it. To deal with the whole list membership for a list, you can do ``` $ shell -l list(a)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(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` If you just want to list them ``` >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: disabled users

by Mark Sapiro

On 10/25/23 11:58 PM, Servizio Informatico U.I.C.I. Sezione territoriale di Brescia wrote: > Hello, > > Thank you for your answers. The problem is: > > I have a lot of user disabled for too many bounces. These users have the > same provider that, probably, has some limits of number of mail that can > be delivered from the same server. This causes timeout connections and, > mailman creates correctly a bounce. Timeouts and other types of throttling should be retried and not result in a permanent failure until the retries fail for days. > So I would like to discover a way to reset bounce limits so they can be > re enabled to receive. I tried also to unsubscribe and resubscribe users > but it does not change anything. Unsubscribing and resubscribing a user creates a new subscription with delivery enabled and bounce score of zero, but this is not necessary. As Steve pointed out in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you can re-enable delivery for a user by clicking the address in the membership list and then setting Delivery status to enabled. -- 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: Welcome message template errors

by Mark Sapiro

On 4/30/24 17:54, Mark wrote: > > In the new installation, are the template.uri (in the mailman DB) > records written as http://localhost:8000/... ? No. In both the installation that worked and the one that didn't, they were https://msapiro.net/..., but I don't think it would have mattered. When I reinstalled, I kept the same database, I only rebuilt the venv. As I have said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, this is all strange. My logs from the failure show the web server getting the request and serving the template with a 200 status and then after 5 seconds which is the specified timeout a requests.exceptions.ReadTimeout error is logged in mailman.log. The exact same code is executed whether by a rest runner gunicorn worker or via some other Mailman core runner, but only the rest runner fails. Further, a reinstalled venv on the failing server has no error, and another server which has a venv identical to the failing one except for Python micro version also has no error. I can't begin to understand what the underlying cause might be. -- 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: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try > using --force > mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… -- 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: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/6/25 14:40, via Mailman-users wrote: >> Is your login a member of the list? > > It's supposed to be – when I click „Manage subscription” in the very same thread, it reveals that I'm subscribed. This is why I can't subscribe again. Yet I still can't post from HyperKitty, however I can by e-mail. > > However, when I checked the member list, I also found my address as a „nonmember” (besides being listed as „member” too). I removed myself as „nonmember”, but I still can't post to the list from HyperKitty. What response do you get when you click `reply` on a message? and what when you click `Start a new thread`. Do you get an error immediately or do you get a composition dialog and only get an error when you click `Send`. What do the errors look like? What do you see in Django's logs when you do this? What HyperKitty version is this and is it installed from PyPI or is it a downstream package? -- 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: migration from 2.1 - owners and moderators

by Mark Sapiro

On 10/23/20 5:31 PM, Alex Schuilenburg via Mailman-users wrote: > > Most of the lists migrated so far don't have moderators, just owners. > However, when these lists have messages requiring moderation, the owners > dont get notified of held messages - unlike 2.1 where they did. Is this > a change or is there something I am missing in the configuration? As Brian said, owners as well as moderators should be notified. These notices are sent immediately if admin_immed_notify is True. If not, only periodic notices are sent. This needs to be run by cron. > I have the minute/quarterly/hourly etc cron jobs running, although I > have had to tune down the frequency of minute to hourly as it takes 6.5 > minutes to run* - but I doubt this is the cause. Those are Django tasks and don't affect this. You also need to run `mailman digests --periodic` to send periodic digests (see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>) and `mailman notify` to send periodic moderator notices (see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>). -- 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: Postorius & multi domain

by Mark Sapiro

On 4/22/20 8:14 AM, Gelpi Andrea wrote: > > I search internet for a while and I discovered that using > FILTER_VHOST = True > seems to solve the problem. > >>From posotrius config page: > > FILTER_VHOST > Filter the list of available lists in Postorius and Hyperkitty > depending on the domain they are being currently served from. Mailman 3 > supports multiple domains in a single installation. > > But it doesn't work. I got err 500 form apache. FILTER_VHOST is currently broken unless each domain has the same value for the web and email domains. See the thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > Were can I find an explanation or a how to configure the system to have > 2 webserver with different domains working on the some server as it was > with mailman 2? If each domain has the same value for the web and email hosts, FILTER_VHOST will work. Currently though if you have domains like web host = lists.example.com and email host = example.com, FILTER_VHOST is broken. -- 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: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Sapiro

On 5/8/20 2:11 PM, Mark Dadgar wrote: > > The easy fix was to edit the [mta] setting in mailman.cfg to deliver email via the submit port instead, which has no filtering applied to it: > > smtp_host: localhost > # using the submit port bypasses spamassassin filtering on outgoing list email > smtp_port: 587 > smtp_user: mm3send <— I created this user for this purpose > smtp_pass: <password-for-mm3send-user> > > This works great and can be applied to any email filtering. We tend to do this differently. For example, on mail.python.org which currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends about 135,000 individual messages per day from the two Mailman instances, we define in /etc/postfix/master.cf 127.0.0.1:8026 inet n - - - - smtpd -o smtpd_authorized_xforward_hosts=127.0.0.0/8 -o mynetworks=127.0.0.0/8 -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_data_restrictions= -o receive_override_options=no_unknown_recipient_checks -o smtpd_milters=inet:127.0.0.1:8891 Then port 8026 only accepts locally generated mail and only does dkim signing (milter on port 8891) and essentially no other checks. Then in the [mta] section in mailman.cfg we only need smtp_port: 8026 -- 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: Database Schema - v3.2.1 to v3.3.3

by Mark Sapiro

On 4/4/23 21:28, Dave Hall via Mailman-users wrote: > Hello. > > Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external > MySql databases for Mailman3 and Mailman3-web. I am in the process of > migrating to v3.3.3. It would be easiest to perform this upgrade one > server at a time, but this would mean that for a short time I would have > v3.2.1 and v3.3.3 using the same databases. > > I am wondering if there are any MySql schema differences between the two > versions. If there are, having the two different versions 'cohabitating' > won't work.. As far as the Mailman3 database is concerned there are at least 3 migrations between 3.2.1 and 3.3.3 in mailman/database/alembic/versions. Namely: 2d2d0ef0828f_add_tag_column.py, 83339e4039da_add_usenet_watermark.py and d151c0b8d6f7_bounce_parameters.py. As far as Mailman3-web is concerned, this is presumably a Debian/Ubuntu Mailman3-web package upgrade. There may be migrations in django_mailman3/migrations/, hyperkitty/migrations/ and postorius/migrations/ that affect this depending on what the specific version updates are in that upgrade. In any case, there are schema differences for Mailman core between 3.2.1 and 3.3.3. -- 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: Hyperkitty on Debian 12

by Mark Sapiro

On 3/26/24 00:06, Markus Grandpré wrote: > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... This warning is harmless, but to eliminate it set ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your django settings. > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available Probably Debian creates the `list` user without a login shell. ``` sudo -i -u list ``` may work. If not, you can always prefix commands with `sudo -u list ` as in ``` sudo -u list mailman-web hyperkitty_import \ -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ /var/mailman21/testlist.mbox ``` -- 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: Disabled by bounce

by Mark Sapiro

On 9/11/24 15:21, Dan Caballero wrote: > Mark, > > Do you have any tips for scripting the setting changes via mailman shell -l somelist(a)caltech.edu or a python script to run. eg. mailman shell -r dmarcsettings.py? > > We have a number of lists that email Gmail addresses either directly or via aliases and virtual email domains using Google Workspace. If your Mailman version is >=3.3.9 you can add `^.*(a)gmail\.com` to each list's `dmarc_addresses` to apply `dmarc_mitigate_action` to any mail From: a `(a)gmail.com` address. A `mailman shell` interaction to do that and set `dmarc_mitigate_action` to munge_from for all lists is like ``` $ /opt/mailman/mm/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): ... mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') ... mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from ... >>> commit() ``` If your Mailman is older than 3.3.9 or you don't want to use dmarc_addresses, replace the line ``` ... m mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') with ... mlist.dmarc_mitigate_unconditionally = True ``` -- 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: Mailmansuite.log Entries

by Mark Sapiro

On 12/1/20 5:16 PM, Brian Carpenter wrote: > I see the following log entries in mailmansuite.log: > > INFO 2020-11-28 00:00:52,242 29142 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-28 00:01:00,600 29142 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-11-29 00:00:52,135 15513 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-29 00:01:00,192 15513 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-11-30 00:00:52,484 22622 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-30 00:01:00,758 22622 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-12-01 00:00:50,246 11946 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-12-01 00:00:59,688 11946 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > > I assume this is a result of importing archives from a MM2 mbox file. > This happen months ago however. Why are these entries still showing up? Those come from the HyperKitty sync_mailman job which is run by hyperkitty_import if you don't specify --no-sync-mailman, but is also one of the Django daily jobs. -- 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: postfix malformed address with confirm replies

by Mark Sapiro

On 2/28/21 1:07 PM, Stephen Mats Mats wrote: > > > To be clear the 'obstructive server’ is mailman-core. :) > > [ec2-user@ip-172-31-18-xxx ~]$ telnet 172.19.199.2 8024 > Trying 172.19.199.2... > Connected to 172.19.199.2. > Escape character is '^]'. > 220 mailman-core GNU Mailman LMTP runner 2.0 > LHLO ip-172-31-18-xxx.us-west-2.compute.internal > 250-mailman-core > 250-SIZE 33554432 > 250-8BITMIME > 250 HELP > MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> > 250 OK > RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu> > 553 5.1.3 Error: malformed address > RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55(a)mm3.aca-aws.s.uw.edu> > 250 OK > quit > 221 Bye Thanks for the info. I'll investigate further. It looks as though the LMTP runner (server actually) is responding with the 553 and then the sending MTA is retrying with a truncated local part, but of course that doesn't work because the token won't be found. I will look at trying to convince Mailman's LMTP to accept the longer local part or barring that to get the confirm command to accept the truncated token. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Mark Sapiro

On 3/9/21 1:59 AM, Per Jessen wrote: > All, > > I am trying to figure why a particular outbound message was bounced, so > I'm looking for the text of the NDR that was sent - where do I find > that ? Mailman 2.1 would include the NDR in the notice to the admins when delivery was disabled or bounce score's incremented if those notices were requested. Mailman 3 has no such capability. If you have access to the server, this patch ``` > diff --git a/src/mailman/runners/lmtp.py b/src/mailman/runners/lmtp.py > index 6a0bdcf5e..eca474089 100644 > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -217,6 +217,8 @@ class LMTPHandler: > slog.debug('%s subaddress: %s, queue: %s', > message_id, canonical_subaddress, queue) > status.append('250 Ok') > + if queue == 'bounces': > + config.switchboards['bad'].enqueue(msg, msgdata) > except Exception: > slog.exception('Queue detection: %s', msg['message-id']) > config.db.abort() ``` will add all received bounces as queue files to var/queue/bad/ where they can be examined with `mailman qfile`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/10/24 1:55 PM, jkoral(a)luc.edu wrote: > The old server is trying to send, but I end up getting an undeliverable message saying no connection could be made. I know port 25 is open because I can telnet to it. I'm wondering if I'm missing something in my configuration. Can you take a look? Thank you. > > Here are the active settings in /etc/postfix/master.cf: ... > smtp inet n - y - - smtpd This says port 25 is for smtpd and that's good. > And here are the setting I have in /etc/mailman3/mailman.cfg > # /etc/mailman3/mailman.cfg This is irrelevant as the message never gets to Mailman. On 10/10/24 1:58 PM, jkoral(a)luc.edu wrote: > Here are the results from netstat: > > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3876896/master And Postfix master process is listening on port 25. You say you can telnet to port 25. Can you do that from the old MM 2.1 server? Can you connect and receive the greeting and send `EHLO hostname` and get a good response? -- 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: Default moderation for new members

by Mark Sapiro

On 11/14/19 7:37 AM, Seth Seeger wrote: > > I’m loving Mailman3 so far! Great work on it. Thank you. > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. In Postorius set Settings -> Message Acceptance -> "Default action to take when a member posts to the list" to Hold for moderation. This is the action which will be taken for a post from a member whose individual Moderation is List Default as it is for all new members. Then when a post from that member is held, if you click the subject in the held messages view, a dialog opens showing the message content with Accept, Reject and Discard buttons and a dropdown list you can use to set that member's Moderation to Default processing. Default processing is generally what you want as it bypasses the moderation hold but still applies other tests such as header filters, administrivia, implicit-dest, max-recipients, max-size, etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 8:51 AM, Marco Marinello wrote: > Hi everybody, > > as per subject, I'm getting this error in the hyperkitty log when mailman daemon tries to archive a mail. > I've setup the hyperkitty.cfg file with api_key = MAILMAN_ARCHIVER_KEY in settings_local.py but still nothing. > I've seen here and in GitLab issues some errors concerning a wrong api key but here it says that it wasn't sent at all. > All packages installed via pip install + latest .zip release, including mailman-hyperkitty. Currently running on apache with mod_wsgi_py3 without https. The following combinations should work: mailman-hyperkitty 1.2.0 with HyperKitty 1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty <1.3.5 The following will not work: mailman-hyperkitty 1.2.0 with HyperKitty <1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty 1.3.5 Do you see a message like 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer.' In your Django log and/or your mailman.log? These will only be logged with HyperKitty 1.3.5 and mailman-hyperkitty < 1.2.0 -- 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: Problems getting MM3 to work

by Mark Sapiro

On 4/24/23 4:53 PM, Mark London wrote: > > Mark - I encountered the same problem and it wasn't clear from the > documentation what to do about it. > > So I eventually changed the name from example.com using the /admin link. > > But if I now set SITE_ID = 0, and restart the server, it is not happy > and tells me it encountered an error. > > raise > self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: > Site matching query does not exist. I'm not sure about this. It may only work if there is more than one site. On the other hand, it requires that the requesting domain match a site. I.e., I think if the site's domain is example.com, but the request is from www.example.com, that could cause it to fail. Also, if proxying to a wsgi server, the web server has to pass the host. I.e., for nginx, proxy_set_header Host $host and for Apache ProxyPreserveHost On > I guess I should just let it be set to 1 and be done with it? - Mark Yes, I think so. -- 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: Congrats on the instructions for installation on ubuntu, what about migration?

by Mark Sapiro

On 10/8/24 5:45 PM, Bill Oliver wrote: > > Is there a tutorial/instructions on migrating data from an old system > to a new one? It's actually not the end of the world if I don't get > all the old emails transferred, but I'd like to get the email addresses > of the participants moved over easily... I believe that I set it up > in 2020, but did not do any version upgrades since then... There's no explicit doc, but there are some posts in the archives of this list, e.g. <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. The easiest scenario is if you want to migrate everything. You just dump the database on the old server and load it on the new one using the database manager's tools. If you only want to move some, but not all lists, it's more complicated, but possibly the easiest thing is to migrate everything and then delete the unwanted lists and their archives from Postorius and HyperKitty. -- 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: confirm mail rejected

by Mark Sapiro

On 10/02/2017 05:21 AM, Marc Sluiter wrote: > > In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. > Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? I think so. See the note I just added at <https://gitlab.com/mailman/mailman/issues/401#note_42163915>. > For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ > > Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? > Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) I'll be working on a fix. My inclination is to change all the regexp -confirm and -bounces table entries from, e.g., /^list-bounces(a)example\.com$/ to /^list-bounces(+.*)?(a)example\.com$/ -- 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: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/2/21 11:33 PM, David Partain via Mailman-users wrote: > > In this regard, I have three questions: > > 1. Am I correct in assuming that I can just use my favorite editor (vi) > to remove the offending characters from the file? No. The file is a Python pickle and you can't edit it. You would need to get the message and the metadata from the pickle (you could at least view it with the `mailman qfile` command), edit the message and then re-pickle the message and metadata. > 2. If I cannot find the offending character, is it safe to just remove > the file so that subsequent archiving can proceed? Yes. > 3. Can I do something to make hyperkitty go through the spool? I don't know what you mean. Every time there is a new post to any list, Mailman core invokes the mailman_hyperkitty process to archive the message and the forst thing that process does is attempt to reprocess all the messages in the spool which fails because of 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, 9 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/7/24 11:23, jkoral(a)luc.edu wrote: > HI Mark, I was off for a couple days. I have a feeling postfix is misconfigured because I see that port 25 is open. The server is not receiving mail at all. Are there any tips for things I can check. The logs are not showing much because the mail doesn't seem to reach it. According to Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test(a)listservnew.example.com>, orig_to=<olivertest(a)lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) The old server is attempting to send mail to the new server. Are there any `postfix/smtpd` messages in the mail.log on the new server. If so, they may help. If not, the port 25 connect is not reaching Postfix and the new server is disconnecting before connecting to Postfix. Is Postfix listening on port 25? Does `sudo netstat -lntp` show Postfix `master` process listening on port 25? If not check /etc/postfix/master.cf. -- 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: Broken paths

by Mark Sapiro

On 07/13/2016 12:30 PM, Jean-Luc Wasmer wrote: > > I followed the instructions on: https://gitlab.com/mailman/mailman-bundler/ > I didn't have Python 3.4 installed at all... had to install it to > complete Mailman's installation. So you should have two virtualenvs, a Python 2 virtualenv at /opt/mailman/mailman-bundler/venv and a Python 3 virtualenv at /opt/mailman/mailman-bundler/venv-3.4 (I'm pretty sure bundler won't install with Python 3.5). >>> - shell scripts expect bash to be at /bin/bash (mine is at >>> - /usr/local/bin/bash) >> >> Which shell scripts? Mailman itself doesn't ship any shell scripts, >> so again, >> I'm guessing you're talking about the ones in your vent? > > I'm referring to: > ./bin/mailman-post-update > ./bin/mailman-web-django-admin createsuperuser Those scripts are created by bundler you should be activating the Python 2 venv before running them. I.e., source ./venv/bin/activate I'm not sure this will help. It looks like bundler has #!/bin/bash hard-coded in the templates for these scripts. You might file an issue on this at <https://gitlab.com/mailman/mailman-bundler/issues>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 5 months

[MM3-users] Re: Mail going to Held Messaging even the moderation is set to Accept Immediately

by Mark Sapiro

On 7/21/20 8:09 AM, Shashikanth Komandoor wrote: > > As per my understanding on Mailman 3, if the moderation attribute is > set to "Accept immediately (bypass all other rules)" then without checking > any rules, it should be delivered to the recipients of the list > irrespective of the message or body of the message but is there any such > checking if the body content or subject or any thing else is checked even > if the moderation bit is set to "Accept immediately". Member moderation Accept Immediately does not bypass ALL rules. It only bypasses those rules after member-moderation. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. However, I don't think that's the issue here. I think the issue is the poster is both an owner and a member. There is an issue in Postorius such that in cases like this, setting the member's moderation action actually sets that of the owner which has no effect on posting. See <https://gitlab.com/mailman/mailman/-/issues/659> -- 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: spanish localization

by Mark Sapiro

On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > very significant date for me (it is my wedding anniversary) and I'm 90% > sure that I dedicated time to Weblate after that date... With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical. If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>. > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, after > updating to the latest releases, are still in Englanish (more English than > Spanish). > > This is not a fight, we want to help, but do not know how. And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: manage.py runjobs hourly

by Mark Sapiro

On 6/11/20 11:04 AM, Mark Dadgar wrote: > I have started getting this emailed to root each hour from the cron job. > >> From: root(a)pdc-racing.net (Cron Daemon) >> Subject: Cron <www-data@mail> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly >> Date: June 11, 2020 at 11:00:06 AM PDT >> To: www-data(a)pdc-racing.net >> >> 18:00:03 [Q] INFO Enqueued 1350 >> 18:00:03 [Q] INFO Enqueued 1351 > > The Enqueued numbers do increment. > > Anyone know what this is? The short answer is you fixed your HyperKitty indexing issue so the hyperkitty update_index job has work to do and some of those tasks get queued by Django Q. See <https://gitlab.com/mailman/hyperkitty/-/issues/295> for another discussion around this. Those messages depend on system load. Sometimes you'll see bunches of them and sometimes (at least on mail.python.org which is the most busy server I am involved with) you won't see any for up to a week or longer. Run django-admin qifno to get the current django q stats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Missing mailman archives?

by Mark Sapiro

On 8/10/20 7:44 AM, Marco Marinello wrote: > I've recently migrated from Mailman 2 to Mailman 3 but I'm setting up Hyperkitty just now. I imported the old mbox and that worked fine but now I'm missing the mails in the time between Mailman 3 started working and now: mailman config reports > > [paths.custom] var_dir: /opt/mailman/var > > But > > root@mm:/opt/mailman/var# find . > . > [OMISS] > ./archives > > Where are the e-mails? Can I import them into Hyperkitty? If the prototype archiver was enabled for the list, the message should be in maildir format in /opt/mailman/var/archives/prototype/list(a)example.com/ If the prototype archiver was not enabled and the messages aren't there (which appears to be the case if I understand your `find`), they are only in the list member's mailboxes if they haven't been deleted. If you have the maildir messages, you can make a mbox containing the messages an import it into HyperKitty, but if there are newer message in Hyperkitty, you need to specify --since to hyperkitty_import to import messages older that the newest in the HyperKitty archive. -- 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: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 3:01 PM, Mohsen Masoudfar wrote: > It seems something is fundamentally wrong with Hyperkitty: > >>From /var/log/mailman3/mailman.log > > --- > 49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 50 <h1>Authorization Required</h1></body></html> (401) > 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 52 <h1>Authorization Required</h1></body></html> (401) > 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 54 <h1>Authorization Required</h1></body></html> (401) > 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> ... I doubt this has anything to do with the missing approved message, but what's in you mailman-hyperkitty.cfg file for api_key and does that match your settings_local.py setting for MAILMAN_ARCHIVER_KEY except for being quoted in settings_local.py and not in mailman-hyperkitty.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/20/24 1:08 PM, Keith Christian wrote: > Mark, > Good morning, > > If it matters, running Python3 3.6.8 on Red Hat Enterprise Linux > release 8.9 (Ootpa) > > [mailman3@wesnixtopmed mailman]$ mkdir > /home/mailman3/mailman/virtual_environment > [mailman3@wesnixtopmed mailman]$ python3 -m venv > /home/mailman3/mailman/virtual_environment > [mailman3@wesnixtopmed mailman]$ source > /home/mailman3/mailman/virtual_environment/bin/activate > (virtual_environment) [mailman3@wesnixtopmed mailman]$ pip install > /home/mailman3/mailman > > I tried to follow your instructions closely today, got these messages afterward: > > Directory '/home/mailman3/mailman' is not installable. File 'setup.py' > not found. > You are using pip version 9.0.3, however version 24.0 is available. > You should consider upgrading via the 'pip install --upgrade pip' command. Both pip and python are too old. Officially, current Mailman 3 requires Python 3 >= 3.9. It might work with older versions, but no guarantees. Also, 9.0.3 doesn't recognize pyproject.toml as replacing setup.py. It requires pip >= 10.0. see https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/ -- 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: Apache+mod_wsgi issue

by Mark Sapiro

On 12/26/22 11:08, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > El 26/12/22 a las 19:19, Mark Sapiro escribió: >> On 12/26/22 07:42, Odhiambo Washington wrote: >> >>> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> >>> >>> Does your https://site.name/user-profile/ work? >> >> Again, Guillermo is using uWSGI, not Apache mod_wsgi > > Well... now I am not sure, you know I've been confused before about that. I was looking at what you posted at https://forums.freebsd.org/threads/mailman-3.61050/#post-488128. I focused on the part beginning with - initiated the uwsgi with a /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & Which is running uwsgi. However I overlooked the mod_wsgi stuff. > In my httpd.conf I have: > > ############## > > LoadModule wsgi_module > "/usr/local/lib/python3.9/site-packages/mod_wsgi/server/mod_wsgi-py39.cpython-39.so" > WSGIPythonHome "/usr/local" > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 > user=mailman3 group=mailman > WSGIProcessGroup hyperkitty > ############### This is all mod_wsgi. > And in then end of my vhost definition file there is this line: > > Include "/usr/local/mailman3/apache24.uwsgi.conf" > > In that file I have: > > ######### begin of apache24.uwsgi.conf > > Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico > Alias /static /usr/local/mailman3/static > ######### > # for hyperkitty > Alias /static/admin /usr/local/mailman3/static/admin > Alias /static/CACHE /usr/local/mailman3/static/CACHE > Alias /static/django_extensions > /usr/local/mailman3/static/django_extensions > Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty > Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty > Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 > Alias /static/rest_framework /usr/local/mailman3/static/rest_framework > # for postorius > Alias /static/postorius /usr/local/mailman3/static/postorius > Alias /static/archives /usr/local/mailman3/static/postorius > ##### All the above between `#########` and `#####` is redundant as you already have Alias /static /usr/local/mailman3/static which will alias any /static/xxx to /usr/local/mailman3/static/xxx > ###ErrorLog /var/log/httpd/hyperkitty_error.log > ###CustomLog /var/log/httpd/hyperkitty_access.log combined > > <Directory "/usr/local/mailman3/static"> > Require all granted > </Directory> > #### esto va en el httpd.conf > ##WSGIDaemonProcess hyperkitty threads=25 > python-path=/usr/local/mailman3 user=mailman group=mailman > ## esta es la de Sapiro > #WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 > ####user=mailman group=mailman > ####python-path=/opt/mailman/mm/venv/lib/python3.6/site-packages:/opt/mailman/mm/venv/lib/python3.6 > ####python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > > #### agregado el 08/07/22 > WSGIPassAuthorization On > #### > > WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py > process-group=hyperkitty And this is also mod_wsgi. ... > I don't want to put more noise in the list. But I'm confused because I > always updated via pip the apache mod_wsgi thinking is was needed for my > configuration. If it is not, I will stop updating it. Based on the above you ARE using Apache mod_wsgi and if you are still also running uwsgi as /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & that is unnecessary. -- 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: signup / registration error - permissions and cert chains

by Mark Sapiro

On 12/31/21 5:37 PM, David Newman wrote: > > After stripping this down to the defaults: > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > > and restarting mailman3 (necessary?) No > and mailmanweb, the system emails > me (as alias for root) an error like the one pasted below after I try > creating a new user account. > > After changing EMAIL_HOST to the system's canonical FQDN and again > restarting mailman3 and mailmanweb, the error is the same, and still > from postorius@localhost. localhost is better. If you set it to the system's canonical FQDN you need to ensure that that name or IP is in Postfix mynetworks. ... > Internal Server Error: /accounts/signup/ > > SMTPRecipientsRefused at /accounts/signup/ > {'newuser(a)dom1.tld': (504, b'5.5.2 <postorius@localhost>: Sender address > rejected: need fully-qualified address')} ... > Settings: > Using settings module settings ... > DEFAULT_FROM_EMAIL = 'postorius@localhost' Try setting this to a fully qualified address, e.g., something(a)networktest.com, not @localhost. More info at https://docs.mailman3.org/en/latest/config-web.html#setting-up-email -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

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

by Mark Sapiro

On 4/21/22 14:56, Chris via Mailman-users wrote: > We had a mail loop on one of our lists and ended up with over 51k messages in pending (held due to post not form a list member) > > Trying to delete them from the web UI will take forever, as the largest pagination you can view is 200 at a time. > > Tried to delete them from the Python interactive shell, but it looks like the API times out after a while. > > Is there another way to delete all these unwanted held posts? I suggest the following in `mailman shell` ``` $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.app.moderator import handle_message >>> requestdb = IListRequests(m) >>> for id, type in requestdb.held_requests: ... if type == RequestType.held_message: ... handle_message(m, id, Action.discard) ... >>> commit() ``` -- 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: Lost in default style creation

by Mark Sapiro

On 6/2/22 02:44, kenneth.karlsson(a)eco.cept.org wrote: > > It shows me its there, then i proceed to quit() and go back in to the shell, and do this: >>>> quit() > ecoadmin@list01:/etc/mailman3$ sudo mailman shell > Welcome to the GNU Mailman shell > >>>> from zope.component import getUtility ... More recent versions of mailman shell will tell you what the problem is. ``` $ ./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. >>> ``` You need to exit the shell with control-D or issue a commit() before you exit. Also, NEVER run any `mailman` commands as root. Always run `mailman` as the Mailman user. Running `mailman` as root can create files owned by root that can't be read/modified by the Mailman user. More recent versions will tell you ``` $ sudo ./mailman Usage: mailman [OPTIONS] COMMAND [ARGS]... Try 'mailman -h' for help. Error: If you are sure you want to run as root, specify --run-as-root. ``` -- 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: Permission denied for fulltext_index

by Mark Sapiro

On 12/1/22 01:43, Jan Eden via Mailman-users wrote: > > There are currently 5 (test) threads in the archive. After changing the > PATH in the HAYSTACK_CONNECTIONS dict to /opt/mailman/fulltext_index, > and fixing the issue with MAILMAN_ARCHIVER_FROM above, > /opt/mailman/web/logs/mailmanweb.log does not display new error > messages, but I do not get any suggestions for reattaching threads, and > a search for a specific thread subject ("Third test") does not return > any results. By "search for a specific thread subject", do you mean searching via the search box at the top of HyperKitty pages? This relies on the search index for Haystack (Whoosh in your case). This index is updated by the HyperKitty update_index job. Assuming you have set up the cron jobs for Django <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>, this will be run hourly and posts added to the archive in the last hour won't be indexed. > So reattachment works in principle, but the suggest/search function does > not. Reattachment suggest doesn't depend on the search index, but it does depend on loosely matching thread subjects. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

Resending with proper inline code quoting for the archive. On 12/20/19 1:31 AM, Dieter Leupold via Mailman-users wrote: > Hi Mark, > > Thanks for your information. But, how I said, I'm new to MM3 and I have > problems with the syntax of the mailman shell. Please, could you give me > an example to set "pass_types" via MM-Shell? > Thank you very much! The documentation of Mailman shell is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…>. A simple example in for setting pass_types is ``` $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the list(a)example.com mailing list >>> m.pass_types <generator object MailingList.pass_types at 0x7fd7e1489840> >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain'] >>> list(m.pass_types) ['multipart', 'text/plain'] >>> ``` At this prompt you can enter commit() to commit your changes, abort() to reverse your changes or control-D to commit and exit. You can also enter exit() to exit, but your changes will not be saved unless you have done a prior commit() -- 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: Announce Only List

by Mark Sapiro

On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > So if we want to make a list announce only (e.g. only specific folks) can post, I've found I can set the list settings to automatically discard messages from members and non-members. Then I go into the individual permissions on each user to be allowed to post without moderation. This works fine, however it seems cumbersome. My expected solution was to make the announce only members moderators - however it appears being a moderator does not give any special ability to post to the list (nor does it appear to make you a 'member' from the point of mailman when sending messages to the list, since a moderator who is not a subscriber gets treated like a nonmember from the posting permissions perspective). Is this correct? Yes, your observations are correct. This is how it's always been, at least from the beginning of Mailman 2.1. There is an alternative. Set a moderator_password for the list. Then anyone can successfully post with an `Approved: <password>` header or pseudo header if they know the password. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…>. -- 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: Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?

by Mark Sapiro

On 5/24/24 7:41 PM, Keith Christian wrote: > > mailman3 was installed into the below virtual environment: > (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary > Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or > any other supporting programs be installed into this virtual > environment ? If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you will install Mailman core, psycopg2-binary, mailman-web and mailman-hyperkitty in the venv. mailman-web will install Django, django-mailman3, MailmanClient, HyperKitty and Postorius as dependencies in the venv. > PostgreSQL and Postfix have been successfully installed outside of the > mailman3 virtual environment and start properly, I assume this is > correct. Since these are not python packages, they and sassc (or Dart-Sass) are installed outside the venv. Also, Postfix in particular and possibly PostgreSQL may be used by things other than Mailman so you don't want them in the venv even if they could be installed there. -- 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: Caching problem with templates

by Mark Sapiro

On 6/26/25 15:12, Mark wrote: > > On 2025-06-26 16:10, Mark Sapiro wrote: > >> What does the database query >> ``` >> SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND >> context = '<IDENTIFIER>'; >> ``` >> return? > > ================================= > > The result of the query is: > +--- > uri > +---- > http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer > +---- > > I should have also said, if I delete the template, emails still use the > old footer -- not the Mailman default as I would have expected. As long as there is an entry in the template table with a uri which is not a `mailman://` scheme, that entry is cached in the file_cache table in the database with a key = the uri and a lifetime set by cache_life in the [mailman] section of mailman.cfg - default 7 days. You can delete the cached entry from the database via `mailman shell as in ``` $ 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. >>> cm = getUtility(ICacheManager) >>> uri = 'the_uri_from_the_template_table' >>> cm.get(uri, expunge=True) >>> commit() ``` You can also delete the entry from the file_cache table, but if you do that, the actual file containing the cached data will remain. To remove it, note that the file_cache table entry has a file_id. This will be a hex digest of the sha256 hash of the uri, something like `c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e` and the file is stored in the cache/ directory in Mailman's var/ directory with a path of `file_id[0:2]/file_id[2:4]/file_id`. I.e. for the above example file_id, the file will be `var/cache/c8/52/c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e`. If you remove the entry from the file_cache table without removing the file, the file will remain forever but will be overwritten if the same uri is cached again. Rather than doing any of the above, if you want to manipulate the database, just set the expires_on column in the file_cache table entry to a date in the past. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Post log?

by Mark Sapiro

On 5/5/20 5:28 PM, Mark Dadgar wrote: > Is there the equivalent of the post log from mailman 2.x available? It's not a separate log as it was in Mailman 2.1, but the information is in the smtp log. For example, here are a couple of entries relating to your post to which I'm replying: May 06 00:29:15 2020 (27320) <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> smtp to mailman-users(a)mailman3.org for 238 recips, completed in 39.014487743377686 seconds May 06 00:29:15 2020 (27320) <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> post to mailman-users(a)mailman3.org from mark(a)pdc-racing.net, 4429 bytes And here are a couple from a digest May 05 07:30:06 2020 (27320) <158866380359.27325.3146638341622587020(a)mailman.iad1.psf.io> smtp to mailman-users(a)mailman3.org for 7 recips, completed in 0.6532349586486816 seconds May 05 07:30:06 2020 (27320) <158866380359.27325.3146638341622587020(a)mailman.iad1.psf.io> post to mailman-users(a)mailman3.org from mailman-users-request(a)mailman3.org, 27406 bytes These timestamps are UTC. There are 4 categories of messages that can be customized as described at <https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm…>. There are also additional messages written by some other modules that aren't specifically configurable. The above are examples of 'every' and 'success' messages. -- 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: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 1/4/22 2:59 PM, David Newman wrote: > > As a followup: Is there any need or advantage to running both the > prototype and hyperkitty archivers? Only if you want to keep all the raw messages. HyperKitty only stores the message_id, subject, date, in_reply_to and sender information. Other header information is not stored in HyperKitty. The prototype archiver is intended to store messages to be delivered to some other third party archiver. > I did an installation following the venv directions, and it looks as > though the system now uses both archivers. > > If this is a duplication of effort and storage, is it safe to disable > the prototype archiver like this: > > # /etc/mailman3/mailman.cfg > .. > [archiver.prototype] > enable: no > > and then delete anything under here? > > /opt/mailman/mm/var/archives/prototype/ Yes, but you also have to go through all the lists Settings -> Archiving pages and uncheck prototype under Active archivers. You could also do this with a database query like UPDATE listarchiver SET _is_enabled = 'f' WHERE name = 'prototype'; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Mailman2 CLI commands for Mailman3

by Mark Sapiro

On 10/5/22 07:53, Dave Hall via Mailman-users wrote: > Hello. > > Sorry if this is an old topic. I'm in the process of migrating from 2.1 to > 3.2. In my use case one of the advantages of Mailman 2.1 vs services like > Google Groups has been the ability to manage lists from the command line. > Things like using sync_members to update the list for a committee when the > membership of the committee is updated one a year, or like using > find_members and remove_members to remove a user from all mailing lists > when they leave the organization. Even the ability to script mailing list > creation. > > So far I haven't found these commands in Mailman3. I hope there is a plan > to add these soon. They are there. In MM 3, the command line commands are all subcommands of the `mailman` command. See `mailman --help` where you will see subcommands including `syncmembers`, `findmember` and `delmembers`. Note that prior to 3.3.2 there were no `addmembers`, `delmembers` and `syncmembers` subcommands, but there were `modes` of the `mailman members` command that would accomplish these functions. -- 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: Managing users in postorius

by Mark Sapiro

On 9/25/24 11:08, Lieuallen, Thomas Otis wrote: > I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? In the Django admin web UI under Email addresses, you can add an address and associate it with an existing user. > Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? It should list both member and nonmember rolls. If you scroll down past Subscriptions to Ownerships, it lists owner and moderator rolls. > I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. In the Django admin UI, you can edit the user associated with an email address under Email addresses -- 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: Transaction failed: Duplicate header 'DKIM-Signature'

by Mark Sapiro

On 4/13/23 12:12, Mohsen Masoudfar wrote: > > In what log is that message? >>> in /var/log/mail.log > > Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. > > Postfix is running on the local host and in /etc/postfix/main.cf, this is defined: > relayhost = [email-smtp.us-east-1.amazonaws.com]:587 So Mailman is delivering to a local Postfix and that Postfix is relaying to amazonaws.com port 587. This would appear to be related somehow to the Postfix configuration. What does `postconf -n` show? Is the failing list's domain different from other lists? What happens if you set `verp_delivery_interval: 1` in the [mta] section in /etc/mailman3/mailman.cfg. This will cause Mailman to send a separate message with a VERPed envelope from to each recipient. You should then see separate mail.log messages for each recipient's delivery to amazonaws.com with success or failure for each. -- 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: Any known limit of number of lists that one can be owner/member of?

by Mark Sapiro

On 5/8/19 3:33 AM, Alan So wrote: > We have just migrated hundreds of lists from Mailman 2 to Mailman 3. It was smooth in most of the cases. However, we just notice that there are some abnormal behaviour of Postorius for particular users who are owner/member of a large number of lists. We further look into a particular user who is owner of 84 lists. When the user login Postorius, only 50 lists are displayed no matter what the number of "Results per page" is chosen. Prev/Next page cannot be clicked as there is only 1 page. See <https://gitlab.com/mailman/postorius/issues/335> > When I use the following mailman client snippet, it also displays the same 50 lists: > > lists = client.find_lists('xxx(a)yyy.com', 'owner') > for m_list in lists: > print(m_list.fqdn_listname) > > Did we hit any limit of find_lists? Is it a bug or are something wrong during the migration? find_lists defaults to count=50. What happens if you do lists = client.find_lists('xxx(a)yyy.com', 'owner', count=100) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Mark Sapiro

On 2/26/21 10:09 AM, Brian Carpenter wrote: > On 2/26/21 11:50 AM, Johannes Winter wrote: >> I didn't find any documentation on how to export list data from mm3 and >> import it into another mm3 instance. Have I missed something, or is it >> yet nonexistant? > > If you are referring to List Settings, then I don't think you can. As > Peter pointed out, you can export/import your list roster but I don't > believe that includes moderators/owners which is problematic. If you > wanted to migrate archives, then you can download an entire archive via > Hyperkitty which is exported in mbox format. You can then import that > mbox file into your new Mailman 3 list. Brian is correct. Essentially, you would need to run database queries to get all the relevant data from the database and then add it to the database of the new instance. A tool could be created to do the export and import, but it doesn't currently exist unless some user has developed one and not reported 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, 9 months

[MM3-users] Re: invalid parameter response of the rest-api

by Mark Sapiro

On 9/21/22 14:12, gioklr71(a)gmail.com wrote: > This is the code that produce the error: > > for mail, nom in email_D.items(): # Loop over new email > print(info.subscribe(mail, nom, pre_verified=True, pre_confirmed=True, send_welcome_message=False, pre_approved=True)) > > THIS IS THE ERROR MESSAGGE: > > Traceback (most recent call last): > File "./fill_list.py", line 74, in <module> > print(info.subscribe(mail, nom, pre_verified=True, pre_confirmed=True, send_welcome_message=False, pre_approved=True)) > File "/usr/local/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 492, in subscribe > response, content = self._connection.call('members', data) > File "/usr/local/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 161, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 400: Invalid Parameter "subscriber": . > > This code works perfectly before security update from provider.... Never changed from client side. > > I've tried update mailman client: Mailman client is not the issue. The issue is the REST endpoint 'members' doesn't like the value of `subscriber` in the post data. In particular, it looks like you have an entry in `email_D.items()` with an empty value for `mail` -- 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: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 12:17 PM, eboltz(a)lhtservices.com wrote: > Mark, > > Thanks for the assistance thus far. > > When I create a new Domain within Postorius. If I set the Mail Host to 'example.com' and the Alias Domain to 'lists.example.com', create a new list such as 'staff_test', it'll default to the 'example.com' domain (which is the real domain). Then when I subscribe, I'll get an email from 'staff_test(a)example.com', when I want it to be from 'staff_test(a)lists.example.com' instead, also if I reply back to the 'staff_test(a)example.com' then I"ll get a bounce-back that it doesn't exist, but if I send to 'staff_test(a)lists.example.com' it'll go to the newly created list. I'd like all defaults to be '@lists.example.com', if that makes sense. You want to create the list with Mail Host lists.example.com and no Alias domain. Then in Postfix you want no virtual_alias_maps setting. The rest of what you show for postconf -n at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… is good. -- 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: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Mark Sapiro

On 5/14/25 11:50, Jan Eden via Mailman-users wrote: > > – and solved them with the additions to /etc/mailman3/settings.py > suggested by Mark: > > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_LOGIN_METHODS = {'email', 'username'} I suggested the above. > del ACCOUNT_EMAIL_REQUIRED > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] I didn't suggest these. That was from another poster in that thread. We don't set ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] in mailman_web/settings/mailman.py because the default is ACCOUNT_SIGNUP_FIELDS = ['username*', 'email', 'password1*', 'password2*'] and that plus ACCOUNT_EMAIL_REQUIRED = True is the same thing. However, it appears that there is a deprecation warning with django-allauth >= 65.5. I haven't seen this because the sites I manage are all using django-allauth 65.4.1 So to avoid the deprecations with django-allauth >= 65.5 it is appropriate to drop ACCOUNT_EMAIL_REQUIRED and set ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] However, that setting doesn't exist in django-allauth < 65.5 so we also need to require django-allauth >= 65.5. I will do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 4 weeks

[MM3-users] Re: Issues sending to gmail and yahoo e-mails

by Mark Sapiro

On 9/10/25 14:59, jkoral(a)luc.edu wrote: > OK, we successfully set this up on our mail domain and are able to send to gmail now, but we ran into another issue. After making those changes, when I create a new thread, instead of the e-mail coming from the list e-mail, it is now coming from my personal work e-mail. Can this be changed? You said in a prior post > I added DMARC mitigation to this list with "Replace From: with list address" and "DMARC Mitigate unconditinally - Yes" The DMARC Address I have in there is ^.*(a)gmail\.com$ Setting DMARC Addresses to ^.*(a)gmail\.com$ does no harm but is redundant as DMARC Mitigate unconditinally = Yes applies the DMARC mitigation action to all mail. How are you starting a new thread? Is this in HyperKitty? In any case, with those settings all mail from the list should be From: the list address. If that is not the case, I don't know why it would happen. If you posted by email, perhaps you are looking at a message received directly rather than from the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'

by Mark Sapiro

Putting this back on the list. On 5/19/21 9:46 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> ... >> Have you set >> ``` >> [mailman] >> sender_headers: ... >> ``` >> in mailman.cfg?, and if so, to what? > > We have not changed it: > > [mailman] sender_headers: from from_ reply-to sender > > According to the smtp.log, there was an envelope sender ("MAIL FROM:.."), which matched the From header. In the example I'm looking at right now, the sender was not a member of the list, but the Accept these non-members box in the list settings has a regexp that matches the sender's domain. In another example from this morning, to a different list, the envelope sender and From header match, and is a member of the list. > > I don't see any obvious reason or configuration setting that would make either address invalid. First of all, the discard has nothing to do with whether the sender has any connection to the list. It only says the message had no sender at all. Assuming the message had a From: with a syntactically valid email address, this discard should not occur. Also, if the envelope (MAIL FROM:) was a syntactically valid email address, this discard should not occur. The address is validated by mailman/email/validate.py by first splitting it into `local_part`, `@`, `[domain_parts]` where domain_parts are the `between dots` parts of the domain and then validating the local_part and domain with regexps defined per > # What other characters should be allowed? > _valid_local = re.compile("[-0-9a-z!#$%&'*+./=?@_`{}~]", re.IGNORECASE) > # Strictly speaking, both ^ and | are allowed and others are allowed in quoted > # local parts, but this can open the door to certain web exploits so we don't > # allow them. > _valid_domain = re.compile('[-a-z0-9]', re.IGNORECASE) > # These are the only characters allowed in domain parts. Does the From: local part or the MAIL FROM: contain any characters not in the [-0-9a-z!#$%&'*+./=?@_`{}~] class? -- 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] mail stuck in "out" queue

by Mark Sapiro

On 3/29/19 2:28 PM, Dmitry Makovey wrote: > I've had encountered this situation now twice: mail is being stuck in > "out" queue and nothing in the logs indicates the issue. Is there a way > to ask mailman-core politely to attempt delivery (perhaps with increased > debugging in the logs) *without* restarting the core (which does solve > *this* problem but creates other problems, like availability of the > mailman as a whole) Is the "out" runner running? ps -fwwA |grep runner=out If not, you should be able to start it as the Mailman user with a command like /path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg --runner=out:0:1 See 'ps -fwwA|grep runner' for examples. If the out runner is running, is there a file named *.bak along with all the *.pck files in queue/out/ And if it's not, is there anything in Mailman's logs to indicate why it died? Also, 'mailman restart' should only take a matter of seconds, but if the out runner is running but not processing its queue, I think sending it a SIGINT should restart it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

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

by Mark Sapiro

On 11/20/20 8:24 AM, Gordon Dickens wrote: > My mailman3 installation has now been up and running successfully for > several weeks without any issues and then the following error message > was emailed to me by my server. > What's up with this error message and what do I need to do? > Thanks, > Gordon > > -------- Forwarded Message -------- > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/hyperkitty/api/mailman/archive > Date: Fri, 20 Nov 2020 01:25:41 -0000 > From: [1]root(a)host2.mailhub4u.com > To: [2]gordon(a)mailhub4u.com > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\xA4\\xA3\\xF0\\x9F...' for > column `mailman3web`.`hyperkitty_email`.`content` at row 1") '\xF0\x9F\xA4\xA3' is a utf-8 encoding for the emoji '🤣'. For MySQL and MariaDB, 4-byte encodings require the database allow utf8mb4. If your Django database settings use the mysql database engine as in ``` DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', ``` You need to add ``` 'OPTIONS': {'charset': 'utf8mb4'} ``` -- 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: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/4/22 14:54, gordon(a)dickens.com wrote: > Hi Mark, > > Thanks very much for your prompt and helpful reply! > > I made the change to the mailman3 configuration for Apache that you recommended since I am using uwsgi. Now, I am able to start/status/stop the mailman3-web service without errors. However, now, when I then attempt to access the mailman installation on my server with my browser, I get the following message in the browser window: > > Internal Server Error > > I am unable to find any errors in the mailman3 logs or in the Apache error logs. However the Apache access logs have the following: > > 173.165.166.34 - - [04/Feb/2022:17:06:20 -0500] "GET /mailman3 HTTP/1.1" 500 21 > > Do you have any idea as to what is going on now? Any suggestions for troubleshooting this? Without more log info, I don't know what the issue is. Have you looked in /var/log/mailman3/mailman.log and /var/log/mailman3/web/mailman-web.log? Possibly there is a uwsgi log somewhere in /var/log that might have something relevant. -- 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: Removing the option to delete a list on the Postorious interface

by Mark Sapiro

On 6/14/22 13:43, Wong, Wesley wrote: > Hi, I have a question on the Postorious web interface in Mailman 3. I have found that a list owner can delete a list through the Postorious interface if they have the role of owner to the list. I wanted to have it either disabled or removed but I am not sure where to look to make changes to it. I would rather remove it from the interface totally so it would be done from the command line. Any help would be greatly appreciated. The simplest change would be to edit postorius/templates/postorius/menu/list_nav.html and remove the line. ``` <li role="tab" class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` In addition to the above, you could edit postorius/urls.py and remove the line ``` re_path(r'^delete$', list_views.list_delete, name='list_delete'), ``` or in older Postorius versions ``` url(r'^delete$', list_views.list_delete, name='list_delete'), ``` to render the `delete` URL unknown. -- 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: Trying to understand the mailman.cfg from the virtualenv installation guide

by Mark Sapiro

On 9/8/24 01:04, unite42--- via Mailman-users wrote: > Hello, > > I'm trying to install Mailman3 following the Virtualenv Installation guide. I would like to understand why the configurations in the displayed mailman.cfg are recommended. > > Especially the following two: > > [archiver.prototype] > enable: yes > > "The prototype archiver stores messages individually in > var/archives/prototype/LIST_NAME/." > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Do I need this, when using hyperkitty? Is this a fail-safe recommendation? The prototype archiver is separate from and independent of HyperKitty. If you are using HyperKitty as an archiver, you don't need the prototype archiver. Note however that if the prototype archiver is not enabled, it can't be used at all, but if it is enabled, it can still be enabled or disabled on a per-list basis. > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > > What is the background of these recommendations? These settings enable VERP for all list messages. This results in more reliable bounce processing. -- 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: Cannot Create New List

by Mark Sapiro

On 11/1/25 10:20, dap1--- via Mailman-users wrote: > I'm trying to create a list (on Ubuntu) and I'm getting this: > > <venv> $ python3 > Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. >>>> owners = ['xxxx(a)ddddddddd.net'] >>>> from mailman.app.lifecycle import create_list >>>> ant = create_list('llllllllllllll(a)dddddddd.net', owners) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 74, in create > _list > getUtility(IEmailValidator).validate(fqdn_listname) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 180, in getUtil > ity > raise ComponentLookupError(interface, name) > zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.address.IEmailVa > lidator>, '') I'm not sure why this doesn't work, but it probably will if you do it in `mailman shell` which defines a lot of things for you. However, it is much simpler to just use the `mailman create` command to create a list. See `mailman create --help` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Hyperkitty download mbox

by Mark Sapiro

On 4/30/21 1:00 PM, Andrew Hodgson wrote: > > I tried this but get the same error, hope I did the modification correctly. > > [2021-04-30 19:56:31 +0000] [22104] [ERROR] Error handling request > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request > for item in respiter: > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox > msg = email.as_message() > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message > msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') This is the change I suggested, so you did it correctly. > File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ > self._headers.append(self.policy.header_store_parse(name, val)) > File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse > raise ValueError("Header values may not contain linefeed " > ValueError: Header values may not contain linefeed or carriage return characters I don't understand why that change didn't work, but you could try replacing that line with ``` msg["Message-ID"] = "<%s>" % re.sub('[ <>\r\n]', '', self.message_id) ``` -- 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: mailman3 postorius cannot retrieve template

by Mark Sapiro

On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to a > suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because django > is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 (175334) > Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is impossible to > configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command which > includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- 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: Moderation of held emails vs. spam

by Mark Sapiro

On 7/25/20 12:33 AM, David Krantz wrote: > Hi, > > I now run Mailman 3.3.1, installed from pip. Is there now any way to > prevent Mailman from forwarding the contents of the held message when > notifying moderators of held messages? There is not now any configuration setting for this. > In my case these messages often > are spam messages and if the entire contents are forwarded it triggers > spam handling in the recipient address(es) which over time risks > classifying all moderation emails as spam or even classifying the list > domain or server as a spam source. > > Even my own outgoing filter classifies it as spam, which I will fix. So if you can recognize them as spam, why are you delivering them to to list in the first place? > I guess that this would be a simple change to make as a kludge but a > proper implementation as a setting would be a lot better. I'd like it > as a global setting but that might be too coarse. You can submit an issue at <https://gitlab.com/mailman/mailman/-/issues>. -- 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: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/12/21 8:38 AM, Tibor Molnar wrote: > Hello, > > I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 > I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. > The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated. These are all HyperKitty pages, not Postorius. Did you run all the post-upgrade tasks mentioned at <https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade> after upgrading? Also, it is possible, but not the likely cause of this, that there is an incompatibility between the latest hyperkitty and django-mailman3 in PyPI. See <https://gitlab.com/mailman/django-mailman3/-/issues/48>. You could try ``` pip install -U git+https://gitlab.com/mailman/hyperkitty.git ``` and see if that helps. -- 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: restricting public lists per virtual domain

by Mark Sapiro

On 12/16/21 12:25 PM, David Newman wrote: > Can lists set to be viewable on the index page be limited to the virtual > domain they are a part of? > Have you set FILTER_VHOST = True in your Django settings? This works for HyperKitty and works partially for Postorius. For Postorius, it doesn't work if there are multiple domains with different email hosts which have the visiting host as their web host[1] but works otherwise. See https://gitlab.com/mailman/postorius/-/merge_requests/500 and https://gitlab.com/mailman/postorius/-/issues/394 In your case, as long as the domains lists.dom1.tld and lists.dom2.tld have different mail hosts, this should work. [1] An example of what doesn't work in Postorius is the following: Visit https://lists.example.com/mailman3/lists. If there are 2 domains with web host lists.example.com, one of which has mail host example.com and the other has mail host lists.example.com, all lists will be shown regardless of domain. On the other hand, if all the domains with web host lists.example.com have the same email host, say example.com, then only lists with email host example.com will be shown. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Dealing with email bounces from web signups

by Mark Sapiro

On 3/16/22 12:07, Andrew Hodgson wrote: > > What I would ideally like is if we get a bounce from one of these confirmation mails we delete the user from the database but that is probably a future request. We don't get too many of these, around 20-30 a week. Since you are already directing these to a mailbox, you could do a couple of things. You could instead pipe them to a command or via cron run a command which reads the mailbox. In either case, this command could use flufl.bounce <https://pypi.org/project/flufl.bounce/> to extract the bounced address from the email message and then do whatever your current process does to remove the user. > What are other people doing with these messages? I basically do nothing. The issue of more concern to me is when the subscription uses a deliverable address. The owner of that address receives this unwanted confirmation email which is bad enough, but then sometimes reports it as spam to her ISP which affects my server's reputation. But, so far, I don't do anything about that either. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: FW: lists.arun@gmail.com's bounce score incremented on Degrowcali

by Mark Sapiro

On 11/6/25 07:38, Christian Stalberg via Mailman-users wrote: > Whenever I post to this list I get quite a few of these bounce score > messages. How can I obtain a list of actual unsubcribes based on bounce > scores to remaining subscribers please? What can I do to stop this behavior > please? The sending of bounce score incremented notices is controlled by the list's bounce_notify_owner_on_bounce_increment setting exposed in Postorius as Settings -> Bounce Processing -> Notify owner on bounce increment. All bounce processing settings are in Postorius' Settings -> Bounce Processing section. The Users -> members list in Postorius displays the current bounce score for all members. The head of the GitLab branch, not yet released, also displays the member's delivery status, see https://gitlab.com/mailman/postorius/-/merge_requests/953. Disabling delivery due to bounces is logged in Mailman's bounce.log with messages like Disabling delivery for user(a)example.com on list mailman-users.mailman3.org by bounce Members whose delivery is disabled by bounce will normally be removed from the list after (Bounce disabled warnings interval)*(Bounce disable warnings) days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/24/21 10:00 AM, dancab(a)caltech.edu wrote: > Thanks Mark. I can't see the held messages view at all for this list. > I don't think there's any sensitive info so I'm posting the entire message I get to the server admin email. Thanks for that, but it's not helpful, at least for me. I'm looking for a Traceback leading to the error, but it isn't there. > One more note... > We were attempting to test modifying the template for the footer in non-digest messages. So the user/owner of the list had created a template with a modified footer based on the template: "list:member:regular:footer" That shouldn't affect access to the held messages view. Is there anything in Mailman's mailman.log that might be helpful, such as a "GET /3.1/lists/cpa-announcement(a)caltech.edu/held/..." message with a non 200 status. Also, are there "GET /3.1/lists/cpa-announcement(a)caltech.edu/..." messages with 200 status? Also, you didn't answer my > Is it only this list that has an issue? Can you visit other pages for > this list? questions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: very few moderation capabilities for moderators

by Mark Sapiro

On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to provide the list moderators a way to change the moderation > flag for users from whichever it is (normally "list default processing") > to "hold for moderation" and viceversa (to "list default" or to "accept") > > I understand that it could be done via console script (That's the way I > did on mailman2: I made two commands using "withlist", one to hold, > moderar.py, and other one to accept, desmoderar.py. I show you below) Are you asking what the equivalent MM 3 scripts would be? > But I think I'm not the only one that could use as an improvement a way > to do this on postorius/web. Postorius allows a list owner or site admin to set Moderation for list members and non members at e.g. https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Currently, a list moderator who is not an owner cannot do this, but a moderator can set Moderation for the sender of a held post when handling the post. -- 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: Moderation request email from a non existing user

by Mark Sapiro

On 6/1/22 00:45, David Lopez via Mailman-users wrote: > I'm on postorius 1.3.4 so I tried to do via shell but after logging it shows a syntax error. > > mailman shell -l mylist@mydomain(dot)com > pendingsdb = getUtility(IPendings) >>>> for token, data in pendingsdb.find(m, pend_type='unsubscription'): > ... ... if data['token_owner'] == 'moderator': > File "<console>", line 2 > ... if data['token_owner'] == 'moderator': > ^ > IndentationError: expected an indented block >>>> ... pendingsdb.confirm(token) > File "<console>", line 1 > ... pendingsdb.confirm(token) You are entering the `... ` prompts that I showed in my example. You show ``` ... ... if data['token_owner'] == 'moderator': ``` the first `... ` is the actual prompt from mailman shell. The second `... ` is the prompt from my example which you shouldn't enter. You should only be entering ``` pendingsdb = getUtility(IPendings) for token, data in pendingsdb.find(m, pend_type='unsubscription'): if data['token_owner'] == 'moderator': pendingsdb.confirm(token) commit() ``` Indentation is important. After `pendingsdb.confirm(token)` enter an empty line at the last `... ` prompt. -- 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: including a template failed

by Mark Sapiro

On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the following > errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max retries > exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member > :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to establish > a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member:regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.l… on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Nice you opened a new issue, ok then... About this: Ideally, you want to use paths.fhs which is based on Filesystem Hierarchy Standard . To use this add the following to your configuration: [mailman] layout: fhs Should I do it???? is that for production?? Sometimes I wish the install process was easier, sorry for disturbing you guys but believe me I've been more than 2 weeks trying and it's been difficult El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 10:29 AM, Rafael Mora wrote: > > Can we modify the docs? > > > > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > >> > >> However, that said, the doc is wrong. The lines should be added to > >> main.cf, not master.cf. See > >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > > That's what the above issue and associated MR are for. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/9/22 8:48 AM, kisner(a)live.com wrote: > Thanks! > > OK, ran through again on a vanilla Debian 11.3 install, got this error (I'll try to create the directory and see if I can get past it): > > (venv) mailman@lists:~$ mailman-web migrate > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/config.py", line 564, in configure > handler = self.configure_handler(handlers[name]) > File "/usr/lib/python3.9/logging/config.py", line 745, in configure_handler > result = factory(**kwargs) > File "/usr/lib/python3.9/logging/handlers.py", line 445, in __init__ > logging.FileHandler.__init__(self, filename, mode=mode, > File "/usr/lib/python3.9/logging/__init__.py", line 1142, in __init__ > StreamHandler.__init__(self, self._open()) > File "/usr/lib/python3.9/logging/__init__.py", line 1171, in _open > return open(self.baseFilename, self.mode, encoding=self.encoding, > FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/web/logs/mailmanweb.log' Creation of the directory is documented. From https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… ``` # Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' ``` -- 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: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/10/25 09:40, Dan Caballero wrote: > > I've done some testing and this is close to what we need. However, I seem to be having an issue with the option for "Explicit Reply-to set; no Cc added". The messages are still including a Cc field with the sender's email. Is there another setting that affects the Cc field? The difference between "Explicit Reply-to header set" and "Explicit Reply-to set; no Cc added" only affects lists with Personalize = Full. For those cases, the To: in delivered posts is replaced with the recipient's address which means in some cases, the list's posting address is not exposed so we put it in Cc: unless Reply goes to list is "Explicit Reply-to set; no Cc added". This setting is intended for announce type lists where members normally do not post to the list. If DMARC mitigations are applied and Reply goes to list is anything other than No Munging, the original From: will always be added to Cc:. There is no setting to avoid this. This is so reply-all will include the original sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Renaming a server after building

by Mark Sapiro

On 11/26/21 1:46 AM, Philip Colmer wrote: > > However, although the above works, if I then go back to the *Mailman* > interface and go to /mailman3/domains/, the web interface recreates a > domain for the original domain name that was in place when the server was > created, i.e. we end up with "lists" and "new-lists". > > We've tried deleting that "new-lists" domain, rebooting and trying again > but "new-lists" keeps on being created again. > > What am I overlooking here? Is there a better/approved way to achieve what > we want to achieve? Each list has a mail_host attribute. this is not displayed in Postorius other than as the domain part of the list posting address which is displayed near the top of each page. Is this the new-lists.example.com domain? If so, you probably would need to change it. I think by having mailman domains like new-lists.example.com is asking for trouble. Why don't you set up Mailman on the new server(s) with domains like lists.example.com and just rely on DNS to get to the correct server. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/13/24 18:44, jkoral(a)luc.edu wrote: > > Now I am getting this error in mail.log. I have changed quite a few settings to try and not bother you anymore, but nothing seems to be working. Hopefully this will be an easy one for you. The unknown IP address is our F5 where the mail is coming through. > > 2024-11-13T20:31:15.988423-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] > 2024-11-13T20:31:16.486460-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=1 quit=1 commands=2 > 2024-11-13T20:31:18.246010-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] > 2024-11-13T20:31:18.708146-06:00 lstprdls01 postfix/smtpd[2261655]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 550 5.1.1 <joetest(a)listservnew.luc.edu>: Recipient address rejected: User unknown in local recipient table; from=<jkoral(a)luc.edu> to=<joetest(a)listservnew.luc.edu> proto=ESMTP helo=<CO1PR03CU002.outbound.protection.outlook.com> > 2024-11-13T20:31:18.852290-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=2 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 What is joetest(a)listservnew.luc.edu? Is that a list? If so, is it mentioned in Mailman's var/data/postfix_lmtp and is that included in transport_maps and in local_recipient_maps in Postfix main.cf? -- 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: task runjobs minutely uses 100% cpu

by Mark Sapiro

On 2/10/20 1:37 PM, Bjoern Franke wrote: > > I tried to switch to Xapian, but hyperkitty's update of the index fails > now: > ERROR 2020-02-10 22:35:24,787 25592 hyperkitty.lib.utils Failed to > update the fulltext index: update() got an unexpected keyword argument > 'commit' > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line > 179, in run_with_lock > fn(*args, **kwargs) > File "/usr/lib/python3/dist-packages/hyperkitty/search_indexes.py", > line 115, in update_index > update_cmd.update_backend("hyperkitty", "default") > File > "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", > line 276, in update_backend > last_max_pk=max_pk) > File > "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", > line 97, in do_update > backend.update(index, current_qs, commit=commit) > TypeError: update() got an unexpected keyword argument 'commit' > > I didn't find any further relevant configuration options in > https://github.com/notanumber/xapian-haystack/tree/master How did you install Xapian? Did you follow all the Installation and Configuration instructions at <https://github.com/notanumber/xapian-haystack/blob/master/README.rst>? Did you run the Django Admin rebuild_index command after installing and setting up Xapian? -- 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: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/18/22 08:43, gordon(a)dickens.com wrote: > > My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: > > "Server error > An error occurred while processing your request." > > Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: > > "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" > > This email and my logs now complain about: > > "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ > MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ > get() returned more than one EmailAddress -- it returned 3!" > > Also, I get the same errors after I create a new mailing list as well. > > I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! It seems like a database issue. I would like to help. What is the Traceback from that error? -- 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: Change 'from' server for outgoing messages

by Mark Sapiro

On 3/11/23 08:18, Benjamin Goldberg wrote: > > Signup confirmation and welcome emails are working. They appear to be coming from the intended host, which is 757pug.org Welcome messages are sent from Mailman core the same way as posts. > But emails from the mailing lists are being blocked by the smtp relay. I think it's because they are not coming from 757pug.org; They are coming from smart.bnmng.com Assuming the Mailman core list name is xxx(a)757pug.org, Mailman will send both posts and welcome messages with envelope from xxx-bounces(a)757pug.org if not VERPed or if VERPed, xxx-bounces+user=example.com(a)757pug.org. The only difference is the From: header. for a welcome message the From: address is xxx-request(a)757pug.org. For a post if the list is anonymous or if DMARC mitigations are applied the From: address is xxx(a)757pug.org. Otherwise it is the From: address of the incoming post. For failures from the smtp relay, there should be messages in Mailman's smtp.log of the form: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg with the appropriate substitutions. What are the error messages in these entries. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 14:59, Mark wrote: > > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# I don't know what the issue is. curl, running as user mailman, is able to get the url, but Mailman core, presumably running as user mailman, times out trying to get the url. I can't explain why. Try the following in `mailman shell` running as user mailman ``` (venv) $ 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. >>> import requests >>> r = requests.get( ... 'https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD…', ... timeout=5) >>> t.text ``` Note the URL above is all on one line. This is exactly what Mailman core is doing to get the template assuming the `uri` in the template` table entry is the argument of the requests.get(). If this times out, try increasing the timeout= value. -- 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: Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save

by Mark Sapiro

On 8/14/24 01:15, Henrik Rasmussen wrote: > I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache. > > At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload. > > It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug? The daily Django hyperkitty sync_mailman job will probably do it. Or, you can figure out what REST calls saving the settings in Postorius does and do that. -- 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: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/24/19 4:53 AM, Franklin Weng wrote: > > Thanks for your help. I did what you said above, but then I still got the > same result even after restarting mailman3 services. > > ~# mailman shell -l zh-l10n.lists.linux.org.tw > Welcome to the GNU Mailman shell > The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>>> m.preferred_language > <Language [zh_TW] Chinese (Taiwan)> >>>> quit() The issue is the list welcome message is sent in the character set of the new member's preferred language and if that is not set in the subscription request, and it's not possible to do that in Postorius, it defaults to the installation's preferred language. It should probably default to the list's preferred language. See <https://gitlab.com/mailman/mailman/issues/608> You have two choices: You can set the installation's default language by putting [mailman] default_language: zh_TW in your mailman.cfg, or you can leave the default language English and set the character set for English to utf-8 by putting [language.en] charset: utf-8 in your mailman.cfg. -- 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: Mass un/subscribe optimization?

by Mark Sapiro

On 2/28/22 12:12, Bryan Loniewski wrote: > Hi -- > > We've noticed slowness in mass un/subscribing users; looking through the issue(s) log we see both #419 [1] and #627 [2] open and related. From the cmd line we get better performance, but with the subscriber size on many of our Faculty/Staff/Students ad-hoc lists (think 1k-15K subscribed addresses) and with our number of lists (2600) and unique owners utilizing these actions it would be helpful to optimize the mass actions. We wanted to get some thoughts and guidance on what needs to be optimized/redesigned/fixed? Or is there already something in the works, but needs more time? We may be able to provide resources to encourage and/or assist with any development and/or testing... > > We run a split core/web setup with Apache,mod_wsgi and MySQL backend (AWS hosted). > > [1] - https://gitlab.com/mailman/mailman/-/issues/419 > [2] - https://gitlab.com/mailman/mailman/-/issues/627 Regarding mass removal and #627, that should be fixed as of Postorius 1.3.5. What is your Postorius version. If you want to work on providing a REST endpoint for mass subscribe and supporting it in mailmanclient and Postorius, that would be great. -- 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: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/12/22 03:33, Torsten R. wrote: > > But when I try to send a message (as a member of a list) to a list I always get a 401 in mailman.log and the message that I should check if I provided MAILMAN_ARCHIVER_KEY and if it is correct. > So far, I can say that the key is the same in mailman-web.py (with single quotes) and mailman-hyperkitty.cfg (without quotes). > in mailman-web.py I have: > MAILMAN_ARCHIVER_KEY = 'somesecretkeywithlotsofcharacters' > and in mailman-hyperkitty I have this: > api_key: somesecretkeywithlotsofcharacters > > I have some messages in $var_dir/archives/hyperkitty/spool but mailman qfile <messagefile> doesn't show anything that would catch my eye. The issue is not related to message content. One possibility is that there is an incompatibility between mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause this. What are your versions? What is your setting in mailman-hyperkitty.cfg for base_url: if you append `api/` to that and do something like curl base_url/api/ it should return a page of documentation of the API. If that is the case, the issue is almost certainly communicating the api key between mailman-hyperkitty and HyperKitty -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Mailman 3 questions (purge archives, list metrics, and auto discard held messages)

by Mark Sapiro

On 7/27/22 05:12, bob B via Mailman-users wrote: > Some quick mailman3 questions > > --Just wanted to check that there is still no way for mailman3 to automatically purge archived emails after a set amount of time? it looks like you have to export the database, purge the messages, then re-import, is this still the only/best way to purge old archived messages? Actually, there are better ways. I just put a simple script at https://www.msapiro.net/scripts/prune_arch3 that will delete all messages from HyperKitty with dates older than the given argument. Maybe if I get time, I can give it a bunch of options like the MM 2.1 script at https://www.msapiro.net/scripts/prune_arch > --I noticed on the list info page you have metrics, which is straightforward except for "volume" My volume number is not increasing? What is that counting exactly? Steve has answered this. > --Is there any way to auto discard held messages after x amount of time? I assume not but had a user ask if that was an option. Steve has answered this. -- 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: Weird hourly indexing error

by Mark Sapiro

On 5/12/20 3:02 PM, Mark Dadgar wrote: > > The second patch did not work either. Ahh, well. I think you need to do something like this: $ mm/bin/django-admin shell Python 3.7.1 (default, Dec 14 2018, 13:17:01) [GCC 5.4.0 20160609] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email >>> emails = Email.objects.all() >>> for email in emails: ... if email.content.find('\u200b'*5) >= 0: ... print('Found in ml {}, hash {}'.format( ... email.mailinglist.name, ... email.message_id_hash)) ... >>> _NAME/message/HASH/ This will print the mailing list and message id hash for messages found that contain at least 5 U+200B Unicodes in a row. You may need to adjust the '\u200b'*5 if it doesn't find anything. Once you know the list and hash you can go to something like https://example.com/hyperkitty/lists/LIST_NAME/message/HASH/ to see the message in the archive and delete it. Before deleting it, you might want to 'download' it. I'd be interested in seeing that to see if I can understand the issue better and why the patches don't work to solve it. -- 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: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Mark Sapiro

On 08/04/2017 02:54 AM, Cyprian Laskowski wrote: > Hi, > > On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example). This is <https://gitlab.com/mailman/hyperkitty/issues/134>. The fix is a one-liner at <https://gitlab.com/mailman/hyperkitty/commit/2034b937c438f66b465d86bebbbc12…> > Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers. The box is a bar graph of posts by day. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> for what it should look like. I'm not sure why it's empty in your case. Do you have cron running all the Django minutely, quarter-hourly, ... tasks? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Hyperkitty Archives - Sidebar years/months

by Mark Sapiro

On 11/7/18 4:18 PM, Enrique Terrazas wrote: > Thank you Mark > I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: > /bin/sh: django-admin: command not found So whatever django-admin you are trying to run is not in the path of the cron job. Try an absolute path to django-admin instead. > If I run: > django-admin --help > > I get the following: > > Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). I install Mailman in a virtualenv and the django-admin file I run contains #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ The main things are the directory containing settings.py is /opt/mailman/mm and I export that as PYTHONPATH so my settings module can be found. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/24/20 10:59 AM, Allan Hansen wrote: > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ If you imported your MM 2.1 lists with `mailman import21`, `emergency` was set appropriately for the imported list and should be working to hold posts regardless of other settings. > My own current top-of-the-list issues: > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. Editing membership beyond what could be done via the admindb interface (i.e. clearing a moderated poster's mod flag) was never allowed for a moderator in MM 2.1. In MM 3, a moderator can set a member's moderation when handling a held post. Do you think a non-owner moderator should be able to make other changes to a member? > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're working on it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 13:09, bob B via Mailman-users wrote: > Mark, > Thanks for the Assistance but a little lost in the interpreter, and no luck googling. How do Iget back to the >>> prompt? > > I enter > > bash-5.0$ mailman shell -l maillistappha(a)XXXXX.org > 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 maillistappha(a)XXXXX.org mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > ********* This is where I am stuck ********** I hit return it takes me to a new line with no characters? how do i get back up a level to the >>> prompt to enter commit() You wait until it finishes processing the 30K messages and then you'll get the >>> prompt. -- 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: Change digest frequency and default threshold

by Mark Sapiro

On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. > > 1) How do I set another default for Digest Size Threshold for new lists. It's hard coded in mailman/styles/base.py. It should be a config setting, but I think it's not. > 2) How do I change the default for existing lists Postorius -> Settings -> Digest > When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. No. digest_volume_frequency only controls how often the digest volume number increments (and issue number resets). In order to send periodic digests, you need to run 'mailman digests --periodic' via cron. > How do I change this setting, both on a single list and the default for new lists? The only setting is the lists digest_send_periodic which again is hard coded (to True) in mailman/styles/base.py. For existing lists, it is exposed in REST, but not yet in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

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

by Mark Sapiro

On 12/10/21 3:45 PM, dancab(a)caltech.edu wrote: > Thanks Mark. We're using https:// for the URLs. Mailman 3.3.5 is what we're running. > > (mailmanve) mailman@14ea21f6d4b1:/var/www/mailman-www$ mailman conf |grep tasks > [mailman] run_tasks_every: 1h > > We're using two containers behind a load balancer for Mailman so I suspect this is where the lost cache comes into play. Yes. The cache entry is stored in the database which presumably is shared, but the actual cached data may only be stored in the file system of the server that cached it so the other server will think it's lost. Are you sharing Mailman's var/ directory between the two servers? I think you need to do that. > Would it be safe to increase the task frequency to every 15 minutes via the setting below? > > run_tasks_every: 15m I don't think that will do what you hope. It won't hurt, but the task runner only evicts expired entries, and they have a life set by cache_life in the [mailman] section of mailman.cfg (not to be confused with cache_lifetime set in the [dmarc] section) with a default of 7 days. -- 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: Mailman web interface / uwsgi

by Mark Sapiro

On 11/25/22 23:00, Jan Eden via Mailman-users wrote: > > proxy_pass http://127.0.0.1:8000; â†’ proxy_pass http://unix:/opt/mailman/mm/var/mailman.sock; > > and received an error message (as expected): Because that won't work. You can't http to a unix socket in that way. Use ``` uwsgi_pass unix:/opt/mailman/mm/var/mailman.sock; ``` > There are obviously a couple of places where the http-socket on port > 8000 is referenced (e.g. mailman_web/settings/mailman.py, > /opt/mailman/mm/hyperkitty.cfg). Is there an overview of the > required changes when using a different (file) socket? If you configure uwsgi with only a unix `socket` and no `http-socket`, nothing will be listening on port 8000. Thus, you need to configure those references to public facing URLs and let ngnix determine where to go. e.g., for mailman-hyperkitty.cfg ``` [general] base_url: http://example.com/archives/ ``` and in settings.py ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' ``` to override the `localhost:8000` reference in mailman_web/settings/mailman.py. Those two are the only ones. While you might be able to change the references to something like ``` http+unix://%2fopt%2fmailman%2fmm%2fvar%2fmailman.sock/... ``` that may not work, and it's simpler to let ngnix handle 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

[MM3-users] Re: New installation, new issue: mailman3 migrate -- no module CommonMark

by Mark Sapiro

On 10/26/24 16:20, Bill Oliver wrote: > > (venv) mailman@mail:~$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site- > packages/django/template/backends/django.py", line 128, in > get_package_libraries > module = import_module(entry[1]) > File "/usr/lib/python3.10/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1050, in _gcd_import > File "<frozen importlib._bootstrap>", line 1027, in _find_and_load > File "<frozen importlib._bootstrap>", line 1006, in > _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 688, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 883, in > exec_module > File "<frozen importlib._bootstrap>", line 241, in > _call_with_frames_removed > File "/opt/mailman/venv/lib/python3.10/site- > packages/postorius/templatetags/markdown.py", line 21, in <module> > from readme_renderer import markdown as md_render > File "/opt/mailman/venv/lib/python3.10/site- > packages/readme_renderer/markdown.py", line 16, in <module> > from CommonMark import commonmark > ModuleNotFoundError: No module named 'CommonMark' What is your version of readme_renderer? I don't see readme_renderer importing from CommonMark in any recent version. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/6/25 16:00, MegaBrutal via Mailman-users wrote: > Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 0:44): > >> What response do you get when you click `reply` on a message? and what >> when you click `Start a new thread`. Do you get an error immediately or >> do you get a composition dialog and only get an error when you click >> `Send`. What do the errors look like? >> > > I get a composition dialog and can type my message, but when I click send, > I get the error message: „This list is moderated, please subscribe to it > before posting.”. Upon reply, a red rectangle appears to enclose this > message. Upon trying to create a new thread, a white page loads which only > contains this error message. In that composition dialog below the text box, it should say ``` This message will be sent as: user(a)example.com Link another address If you aren't a current list member, sending this message will subscribe you. ``` What the error is saying is it is checking if the sender is subscribed to the list and it finds that it is not subscribed. It wants to subscribe the sender but the list's subscription policy is "moderate" or "confirm_then_moderate" and it doesn't want to bypass moderation so it issues the error. Is the address I have shown as user(a)example.com what you expect and it it a list member? What if you click that address (it's a link) and chose another subscribed address. > What do you see in Django's logs when you do this? >> > > I don't know where to look – I don't see anything outstanding, only a few > HTTP requests appear in mailman.log on mailman side and uwsgi.log on web > side. None of these indicate any error. If you configured your settings.py per https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… your Django log which is where HyperKitty logs is at /opt/mailman/web/logs/mailmanweb.log. However, I don't think there will be anything useful there. -- 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: Backups & disaster recovery of mailman3

by Mark Sapiro

On 3/7/21 11:07 AM, David Partain via Mailman-users wrote: > Hi, > > So now I have a running mailman3 installation. Whew... > > Is there documentation of things like thorough backups and disaster recovery? I haven't yet found it. > > Backups: Obviously, I understand that I need to have datbase (mysql, in my case) dumps, and I'll have file system backups onto something that our IT folks will backup. Is there more I should think of? No, backing up the database with dumps and backing up Mailman's var/ directory and the various settings and mailman.cfg files should be sufficient. Backing up the entire Mailman installation might be useful should you need to restore it on a new server. > Disaster recovery: So, let's say my server (which is cloud-y) gets trashed and I need to get mailman back on a new server. Is this process described somewhere? I don't think so, but assuming you get all the Mailman pieces together on the new server, loading the database from a backup dump and restoring the var/ directory and the various settings and mailman.cfg files should do 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, 9 months

[MM3-users] Re: Problem with Gmail; bulk email

by Mark Sapiro

On 5/8/23 21:35, Lars Bjørndal wrote: > Does someone have tips in how to solve the problem? Look at the log: > mai 09 06:16:52 dalen.lamasti.net postfix/smtp[2174424]: 8163214C1740: to=<example(a)gmail.com>, relay=alt1.gmail-smtp-in.l.google.com[142.250.157.27]:25, delay=50885, delays=50875/0.04/6.5/3.7, dsn=4.7.28, status=deferred (host alt1.gmail-smtp-in.l.google.com[142.250.157.27] said: 421-4.7.28 [185.181.61.11 15] Our system has detected an unusual rate of 421-4.7.28 unsolicited mail originating from your IP address. To protect our 421-4.7.28 users from spam, mail sent from your IP address has been temporarily 421-4.7.28 rate limited. Please visit 421-4.7.28 https://support.google.com/mail/?p=UnsolicitedRateLimitError to 421 4.7.28 review our Bulk Email Senders Guidelines. 14-20020a63184e000000b00519f8ebcc5esi643336pgy.121 - gsmtp (in reply to end of DATA command)) First of all, that's just throttling/greylisting/whatever. It's a temp fail and your MTA should retry and the mail should ultimately be accepted. Was your server sending an unusual amount of mail to google users, perhaps an unusually large amount of traffic on a list? I'm only guessing, but I suspect this problem may go away after google gets more experience with your mail, but in any case, it should only result in delayed mail delivery. -- 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: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 8/16/25 8:14 PM, Wikinaut wrote: > and mails appear not to be processed any more. > > One mail came through, but look to the third lien of the footer, some variables are not replaced by their values: > > berlin mailing list -- berlin(a)xxxxx.de > To unsubscribe send an email to berlin-leave(a)xxxxx.de > %(web_page_url)slistinfo/%(_internal_name)s This line is from a msg_footer imported from Mailman 2.1 by 'mailman import21'. The substitutions are not replaced because they are MM 2.1 syntax which MM 3 doesn't recognize. If you have Mailman core >=3.3.10 and have set the Base Url parameter for the domain, you can replace that line in the template with simply $mailinglist_url If your Mailman core is older, you need to hardcode that as something like https://example.com/mailman3/lists/$list_id I'm only guessing here, but I suspect that you have some directories/files in the /opt/mailman/mm/var/templates/ hierarchy with mode and ownership such that they aren't readable by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/3/20 7:14 PM, Samir Faci wrote: > > Here's my next question. Hopefully this isn't off topic, but trying to get > postfix to work with mailman and I keep on getting relay denied issues. ... > These are the changes I have in postfix that seem relevant. > > /etc/postfix/master.cf > > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} postfix-to-mailman.py is Mailman 2.1 only. It doesn't work with Mailman3. > /etc/postfix/main.cf > > compatibility_level = 2 > > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains These mostly have to do with delivery of mail to Mailman rather than from Mailman. > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated > defer_unauth_destination > myhostname = lists.domain.org > mydestination = $myhostname, localhost.localdomain, localhost, $mydomain, > lists.domain.org The entire output from `postconf -n` might be helpful. Also the postfix log messages for the the failed deliveries would be helpful. Can you send mail to csgeek(a)domain.com in other ways, e.g. mutt or mail or sendmail? -- 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: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/25/20 6:36 AM, Odhiambo Washington wrote: > I decided to try this again, on FreeBSD-12.1 > > I still decided to follow > https://wiki.list.org/DOC/Mailman%203%20installation%20experience which I > know is not the main documentation, but I find the process easier to follow. > I am also taking notes to see if I could share if I manage to succeed. This > is important for me because Python-2.7 is being removed from FreeBSD in Dec > 2020. I need to bail > out of mailman-2.x before that happens so I am trying my hand again om MM3. > I have failed before :-) Even if it's not in FreeBSD, you can download Python 2.1.18 from <https://www.python.org/downloads/release/python-2718/> and install it. > (venv) [root@gw /opt/mailman/mm]# pip install flufl.lock ... > Even after the 'pip install flufl.lock' it still doesn't find it! This is a packaging glitch with the flufl modules. Remove and reinstall them. pip uninstall flufl.bounce flufl.i18n flufl.lock pip install flufl.bounce flufl.i18n flufl.lock -- 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: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Sapiro

On 5/18/21 7:28 PM, Mark Dadgar wrote: > > I had actually done this but checked the Users section and had overlooked the Email Addresses section. It was as you suggested - duplicate emails differing only in case. > > Given that there was only one user account, how does this happen? List subscription without associated user account creation with slightly different case? First, the Django users are separate from Mailman core users and don't have anything directly to do with list subscriptions. As far as how there got to be one User in Django with two EmailAddresses differing only in case, that's probably a bug in Django allauth. The page at accounts/email/ doesn't allow adding an address that differs only in case from an existing address, but possibly adding via a social auth provider bypasses that check. I couldn't find an issue at https://github.com/pennersr/django-allauth/issues but that doesn't mean there isn't one. In case you haven't done it, I think just deleting one of the addresses (the non-primary one) in Django's Email Addresses section will solve your 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, 6 months

[MM3-users] Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by Mark Sapiro

On 7/22/22 04:52, skenny(a)scss.tcd.ie wrote: > Thanks Mark, that didn't work out I'm afraid. This is what happened when I tried importing without deleting/recreating mailmandb: > > I imported the datatase using a psql command in the database container, and then ran "manage.py migrate", which I think does the same thing as the Django admin command with argument "migrate" (?). It reports "No migrations to apply." > > In the web interface the lists appear, but without any members, and as before when I the restart the core and web containers, they die after 15 seconds with the error messages as printed below. > > (As I mentioned earlier, removing the newly minted mailmandb database and then creating a new blank one, and importing into that does work well (c.f. Stephen Turnbull's remarks above)). My point was after you remove the newly minted mailmandb database and then create a new blank one, and import into that, you should then run `manage.py migrate` to apply any new migrations to the imported database. -- 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: Mailing list welcome message won't update

by Mark Sapiro

On 1/14/25 20:51, via Mailman-users wrote: > > "list:user:notice:welcome.bk" has the wrong welcome message. (I renamed it to back it up before correcting the welcome message) > "list:user:notice:welcome" and "list:user:notice:welcome.txt" has the identical correct welcome message. > > I removed "list:user:notice:welcome.bk". > > Now I have: > > -rwxr--r-- 1 list list 0 Oct 10 2018 list:member:generic:footer.txt* > -rwxr--r-- 1 list list 0 Mar 30 2021 list:member:regular:footer* > -rwxr--r-- 1 list list 507 Jan 9 01:35 list:user:notice:welcome* > -rwxr--r-- 1 list list 506 Jan 15 04:45 list:user:notice:welcome.txt* > > I restarted mailman3.service, mailman3-web and nginx.service. > > Tested and issue still persisted.... If list:user:notice:welcome and list:user:notice:welcome.txt have the identical content, why aren't they the same size? In any case, you can remove both list:user:notice:welcome and list:member:regular:footer as the won't be used in any case. As Steve suggests check that the `list` user:group has search and read access to all the superordinate directories. Is there anything relevant 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

10 months, 4 weeks

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 6/24/20 7:28 AM, kelly.close(a)lrewater.com wrote: > Hi Mark - could you elaborate on this just a little? One of the things I did try was to include the https:// prefix in my base URL setting and it did not affect the issue. Is there a different way to use an https scheme in the base_url setting than just adding the 's'? I tried every combination I could think of for that setting, restarting both mailman and apache2 between each try I think, but maybe I missed something. ~Kelly I don't know what the issue was in your case, but if it was fixed by changing the Appache config to not redirect http to https for requests from localhost, it should be fixed by just going to https in the first place unless there is some certificate issue at play. The relevant settings for this list are: mailman-hyperkitty.cfg: [general] base_url: https://lists.mailman3.org/archives api_key: xxx settings_local.py: MAILMAN_ARCHIVER_KEY = 'xxx' ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'lists.mailman3.org', 'mail.mailman3.org', 'mailman.iad1.psf.io', 'mail.falconframework.org', '104.239.228.201', ] (I'm sure the above is overkill, but ...) MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1', '::ffff:127.0.0.1', '104.239.228.201', ) ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' -- 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: Problems after Upgrade

by Mark Sapiro

On 10/30/22 12:24, Jeff wrote: > > When I run the command: > > mailman-web compress > > I get the following error: > > traceback (most recent call last): > File "bin/mailman-web", line 8, in <module> > sys.exit(main()) > File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 49, in load_command_class > return module.Command() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/base.py", line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > I have not been able to fix this and would appreciate any assistance. This is a bug in Django 4.1. See https://github.com/painless-software/django-probes/issues/24. Downgrading Django<4.1 should avoid this. -- 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: Archive search failing on one list

by Mark Sapiro

On 9/23/23 17:51, Mark wrote: > > For example, on searching for the word "Derbyshire" (which is mentioned > in one of the archived messages) the results page displays: > > "Sorry no email could be found for this query." > > The logs show: > > +++++++++++++++++++++++++++++++++++++ > /var/log/mailman3/web/mailman-web.log > +++++++++++++++++++++++++++++++++++++ > > [pid: 1156|app: 0|req: 55/55] 2001:8004:5310:2405:ce66:5ff:41fc:60db () > {76 vars in 1537 bytes} [Sat Sep 23 23:57:43 2023] GET > /mailman3/hyperkitty/search?mlist=LISTNAME-1%40DOMAIN.COM&q=Derbyshire > => generated 13752 bytes in 3188 msecs (HTTP/1.1 200) 5 headers in 164 > bytes (1 switches on core 0) ... > mlist = MailingList.objects.get(name=mlist_name) > File "/usr/lib/python3/dist-packages/django/db/models/manager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line > 406, in get > raise self.model.DoesNotExist( > hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList > matching query does not exist. What does this database query return ``` select * from hyperkitty_mailinglist where name like 'LISTNAME-1(a)DOMAIN.COM'; ``` If it returns a row, does case match for the name in the row and the query? -- 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: mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Mark Sapiro

On 3/14/25 3:55 AM, Stefan Bauer via Mailman-users wrote: > Dear Mark, > > thank you for your time. > > After patching your script according to > https://github.com/maxking/docker-mailman/issues/729#issuecomment-2447542238 > > It fails with > > /opt/mailman/venv/data# /usr/local/bin/UC_fix > /opt/mailman/venv/data/mailman3web.db > Traceback (most recent call last): > File "/usr/local/bin/UC_fix", line 77, in <module> > c.execute("delete from account_emailaddress where email = %s;", > sqlite3.OperationalError: near "%": syntax error That patch still assumes the database is PostgreSQL. You need to replace ``` import psycopg2 ``` with ``` import sqlite3 ``` and ``` db = psycopg2.connect(...) ``` with ``` db = sqlite3.connect(...) ``` but it appears you've done that. It appears that the sqlite3 module doesn't accept the '... %s', value' syntax. See https://docs.python.org/3/library/sqlite3.html You need to change things like ``` c.execute("""update account_emailaddress set "primary" = 't' where email = %s;""", [em1]) ``` to ``` c.execute("""update account_emailaddress set "primary" = 't' where email = %s;""" % em1) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 4 weeks

[MM3-users] Re: How to get rid of footer (Mailman3)

by Mark Sapiro

On 2/11/20 11:31 PM, tarmokumar(a)gmail.com wrote: > Hi, I have read multiple posts in this forum that you should be able to get rid of the footer completely but I am unable to. > I have tried: > - adding the footer template to a list and not adding any "Data" to it. Result was a attachment with some "dfgdfgdfgdfg" text in it. Did you add this via Postorius. If so, it would seem to be a Postorius issue. > - adding/creating a blank "list:member:generic:footer" document to /var/templates/site/en, var/templates/lists/LIST.ID/en/ and var/templates/domains/DOMAIN/en/. Result is that the sent e-mail still has the original unsubscribe text in the footer (as an attachment) Did you name the file list:member:generic:footer.txt (with the .txt extension)? Putting a zero-length file of that name in any of those places should work. > - removing all the files from /mailman/src/mailman/templates/en, still no change If you restarted Mailman after doing this, this indicates something (Postorius?) may have set a URI for this template. What do you get from curl -urestadmin:restpass \ http://localhost:8001/3.1/lists/LIST.ID/uris -- 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: hyperkitty installation: Unclear instructions

by Mark Sapiro

On 1/5/23 15:00, Johannes Rohr wrote: > Dear all, > > I just installed mailman and mailman3-web in virtualenv as described in > https://docs.mailman3.org/en/latest/install/virtualenv.html > > Next I moved on to set up hyperkitty as described in > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html. I > got confused by the instructions: You are confused because you are mixing incompatible ways of installation. Installing mailman-web per https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-… installs both HyperKitty an Postorius as dependencies of mailman-web. > But then, hyperkitty seems to be already have been pulled in by > mailman-web, looking at its dependencies. Yes. > If that's the case, then neither the instructions at > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html nor > those at > https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html > are correct. They are correct, but they are for different methods of installation. > Can someone enlighten me on what the canonical way is of installing and > setting it up in virtualenv? Just follow the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. They are the current recommendation and will result in a complete installation. -- 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: mass remove pending confirmation

by Mark Sapiro

On 5/22/23 13:46, Jens Günther wrote: > > Since we migrate some lists from mailman2 to 3, there are a lot of new > users/subscribers and an admin made the mistake to not checkbox the 3. > option that the users don't need to verify their address. Are these newly added users since the migration? If you migrate a list with the `mailman import21` the users of the MM 2.1 list will be imported and there won't be confirmations. > Now we have a long list of pending confirmations in different lists. Is > there an easy way in the shell to mass remove these pending > mailaddresses so that we don't have to do that one by one? That would be > awsome. Do you want to remove them or confirm them. If you just remove them, the user's addresses will still be unconfirmed. If you just want to remove them so you can redo the mass subscribes, you could do something like the following in `mailman shell` ``` >>> pendings = getUtility(IPendings) >>> for token, data in pendings.find( token_owner=TokenOwner.subscriber, pend_type='subscription'): ... pendings.confirm(token, expunge=True) ... >>> commit() ``` -- 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: Setting base_url for the domain to use it in the templates.

by Mark Sapiro

On 8/27/24 11:27, Ondřej Brablc via Mailman-users wrote: > The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… shows that when the variable is not set it would come as `base_url: None` on GET request. > > But the my table `domain` does not even have column `base_url`. I have tried adding it `ALTER TABLE domain ADD COLUMN base_url CHARACTER VARYING;` but this did not help. The docs at https://docs.mailman3.org/ include documentation of the heads of the GitLab branches so they may contain documentation of things that are not yet released. When Mailman 3.3.10 is released and you upgrade (or when you upgrade from the head of the GitLab branch), a migration will run automatically to add the base_url column to the domain table. > So I believe this is just some WIP. Some related commits: > > - https://gitlab.com/mailman/mailman/-/commit/a80f6d32252b6cf174f836210bc2157… > - https://gitlab.com/mailman/mailman/-/commit/7c5294fe1245d927cb30c556beb2176… Yes, it is a WIP in that it hasn't yet been released as are all the changes at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… -- 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: Migrating Mailman 3 lists

by Mark Sapiro

On 5/19/20 7:25 PM, Mark Dadgar wrote: > > I get a bunch of these errors because identifiers in postgres are limited to 63 characters and mm3 creates some in sqlite that are longer than that: > > 2020-05-20T02:16:20.574000Z WARNING PostgreSQL warning: identifier "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6b632_uniq" will be truncated to "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6" ... > > etc. > > I killed the job before it finished and have not actually tried running against this database, but my question is this: > > How does mailman3 handle this limitation with postgres if I set up an instance from scratch using postgres? Does it just truncate the identifiers identically, in which case migrating via pgloader should work? Mailman doesn't make those names. Those are names in table index entries. Mailman specifies the columns in a table which are indexed, but the DBM itself manages the index. > For reference my pgloader script looks like: > > load database > from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db > into postgresql://mailman3:XXREDACTEDXX@localhost/mailman > > with include drop, create tables, create indexes, reset sequences, no truncate I'm not sure why this doesn't work. A brief look at the pgloader docs seems to say it should. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 12:33 PM, Massimo Zappalà wrote: > Hi Mark, thanks for the reply. > > my /etc/opendkim.conf > AutoRestart Yes > AutoRestartRate 10/1h > UMask 002 > Syslog yes > SyslogSuccess Yes > LogWhy Yes > Canonicalization relaxed/simple > ExternalIgnoreList refile:/etc/opendkim/TrustedHosts > InternalHosts refile:/etc/opendkim/TrustedHosts > KeyTable refile:/etc/opendkim/KeyTable > SigningTable refile:/etc/opendkim/SigningTable > Mode sv > PidFile /var/run/opendkim/opendkim.pid > SignatureAlgorithm rsa-sha256 > UserID opendkim:opendkim > Socket inet:12301@localhost > > > my /etc/opendkim/SigningTable > *(a)catania.linux.it mailselector._domainkey.catania.linux.it Assuminng your list's domain is catania.linux.it, what you need to do to enable DKIM signing of this message is add SenderHeaders List-Post,Sender,From to /etc/opendkim.conf > full email django error > Internal Server Error: /hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Unfortunately, the rest of the detail doesn't help. What we need to see is the raw message. You should be able to find it in Mailman's var/archives/prototype/<list_address/new/ directory, perhaps by timestamp or something in the headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Re-enable member after bouce processed disable

by Mark Sapiro

On 12/9/21 6:07 AM, Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. You are looking at the user's list based preferences. If one of these is unset, it falls back to address based preferences and from there to the user's global preferences. You can see all of these for yourself at the Mailman settings choice in the dropdown at your user name, but for another list member you only see the list based preferences. > How do I or the list admins re-enable a bounce-disabled member? Just set the member's delivery status on the page you see to Enabled. Even though it was not previously shown as Disabled by Bounces, it will be enabled. Likewise the member can set her Delivery status to Enabled. -- 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: mailing list aliases

by Mark Sapiro

On 01/19/2018 03:09 PM, Dmitry Makovey wrote: > Not sure whether to mark this "SOLVED" yet - but when I manually updated > postgres DB with the aliases I wanted - everything started to work as > expected. > > so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or > was it already fixed in 3.3.1 (anouncement page didn't list that fix) As far as I know, this is not a bug in core. It is <https://gitlab.com/mailman/postorius/issues/58> however, this may in fact be a bug in the REST API in which case I don't think it's fixed in API 3.3.1 >> 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to >> foo(a)lists.my.com however we've preserved old addresses. But in new setup >> mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: >> implicit-dest" . What's the best course of action here to get mailing >> list respond to multiple email addresses? acceptable_aliases is the way to address this, but as you note, it can't be properly set via Postorius and possibly via REST. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: list footer questions

by Mark Sapiro

On 6/7/20 3:22 PM, kelly.close(a)lrewater.com wrote: > Well, Glory Be! My .cfg settings were fine but the public.template table was empty (I'm using PostgreSQL and accessing it with pgAdmin). I had not considered that there needed to be database content representing the template but it makes sense. Everything else is in there, which is the whole reason why we went with Mailman3 in the first place. > > After manually creating this record in the public.template table it WORKED!!! > name = list:member:regular:footer > context = f2p2-test.udfcd-lists.org > uri = file:////var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list… > (username and password were left blank) username and password are only required for basic auth to the URI if needed so blank is correct. However, you shouldn't have needed to do that. I only mentioned it in case there was an entry for the name and context with a URI pointing elsewhere. The default if there is no entry is to use Mailman's normal search rules which include templates/lists/<list-id>/en/list:member:regular:footer.txt. So I have to think that without that entry, it was searching a different templates/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 6/24/20 8:30 AM, Kelly Close wrote: > I suspect then that my MAILMAN_ARCHIVER_FROM setting is deficient or... > that ACCOUNT_DEFAULT_HTTP_PROTOCOL variable is a new one to me - I don't > think I have that set anyplace. Perhaps that would have helped? I don't think so. ACCOUNT_DEFAULT_HTTP_PROTOCOL is a Django allauth setting and I think only affects things like logging in to Django. MAILMAN_ARCHIVER_FROM is definitely relevant. > I'm going > to leave it be for now since the listener did the trick, but I will also > copy these remarks into my Ubuntu 18.04 Mailman3 setup guide which just > keeps getting better over time! Thanks. The bottom line here is if the only thing that changed that allowed things to work was creating a virtual host in Apache for 127.0.0.1:80 to not redirect to https, then Mailman core must have been (must be) going to port 80 (http). You've probably already done this more than once, but I suggest giving the following command mailman conf -s archiver.hyperkitty -k configuration This will print the path to the mailman-hyperkitty configuration file. Look in that file for the base_url: setting and verify that it has an https scheme. -- 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: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/7/21 11:27 PM, Marcus Granath wrote: > It seems like the version used is: Postorius Version 1.1.2 Current Postorius is 1.3.4. If you can't upgrade, someone with shell access to the server can do this with `mailman shell` > What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". > > But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). > Or can I use some other API (then the web-page) to do that kind of operation? ;-) Just add the no-reply(a)abc.com address as a member and set its delivery status to disabled. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/22/22 09:35, Onyeibo Oku wrote: > > Strangely, all files in /opt/mailman/venv belong to the mailman group > > ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope* > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.component-5.0.1-py3.8-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.configuration-4.4.1-py3.9-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.event-4.5.0-py3.6-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.hookable-5.2-py3.10-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.interface-5.5.0-py3.10-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.schema-6.2.1-py3.8-nspkg.pth > > and so it goes in the subdirectories. The specific error you reported refers tp /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO what does ``` ls -l /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO ``` show? -- 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: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Mark Sapiro

On 11/26/22 05:09, Daniel Böhmer wrote: > > During startup /var/log/mailman3/mailman.log receives: > >> Cannot connect to SMTP server localhost on port 25 ... > I found this article stating the the SMTP error message > might be misleading: > https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… > > How to further debug this? > What could be wrong with my Mailman3 instance and how to fix it? The article is relevant and mentions the most likely issue which is lack of permission on one or more message templates. Everything in Mailman's var/ directory should be owned by Mailman's user:group - normally `list:list` in Debian packages. I'm only guessing here, but I suspect you ran `mailman import21` at some point as `root`. Never run `mailman` commands as `root`. Only run them as the Mailman user - `list` in Debian packages. Note that Mailman core in Debian Buster is 3.2.1. Since 3.3.5, "The mailman command will refuse to run as root unless the new --run-as-root option is specified." in order to help avoid this 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

[Test] Re: What now -reply from web

by Mark Sapiro

On 03/20/2016 07:22 PM, mailman(a)mailman3.org wrote: > The last post with SSL = True and latest core still hits the same > underlying exception both in trying to get the archive URL and in > trying to archive the message. The core now handles these exceptions > and continues so the message goes to the list, but isn't archived and > has no archive headers. > > This is a post from hyperkitty which will probably be handled the > same, so we have to go back to SSL = False until we can fix the > certificate issue. Yes. Bottom line. With USE_SSL = True, core connects to hyperkitty via SSL to 127.0.0.1 and the certificates I installed don't include 127.0.0.1 in their domains, so urllib3 or requests (depending on where we're coming from) throws SSLError: hostname '127.0.0.1' doesn't match either of 'lists.mailman3.org', 'mirror.list.org', 'mirror.mailman3.org'. The core now handles the exceptions and the message is ultimately delivered but not archived. regardless of where it originated. We're back to USE_SSL = False now so this post should be archived, albeit the archive URLs will have 127.0.0.1 ast the host and not lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/19/20 3:02 AM, Carlo Landmeter wrote: > We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. > I also doubt the shown error is the problem as I see more template errors. > I have also tried to run the official docker images mailman-docker but im having the same issue. > > When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email. > > PS emails are send just fine via smtp posting. The error reported from hyperkitty/ajax/temp_message.html in the OP has nothing to do with the replies not being sent or archived. hyperkitty/templates/hyperkitty/ajax/temp_message.html is called to build the HTML response sent to the web browser after the reply has been sent to Mailman core. Abhilash's fix at <https://gitlab.com/mailman/hyperkitty/-/merge_requests/299> will get rid of that error, but I would be very surprised if it fixes the problem. -- 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: Mixing Mailman 3 with AWS SES

by Mark Sapiro

On 3/24/21 7:58 AM, Brian Carpenter wrote: > On 3/24/21 9:54 AM, Ralph Weber wrote: >> Comments received directly from one of the people who developed the >> AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively >> established that AWS Mailman is *not* intended to interact with AWS >> SES when receiving email messages > > I don't think there is a Mailman 4 and the person who is marketing his > services under that name is sending a confusing message to the public. Danil Smirnov owns both the mailman3.com and mailman4.com domains. Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". In response to our request, the following is included at the bottom of <https://mailman3.com/>: Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain used to coordinate development of the Mailman 3 free software suite. The Mailman 3 core developers are not involved with Mailman3.com, and cannot answer any questions or provide any support related to its operations. If you are looking for resources for development of the Mailman 3 free software suite, please see mailman3.org. Yes, this is all ripe for confusion ... -- 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: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 10:52 AM, Morris Jones wrote: > > In my virtual environment, I ran `pip list -o` and got a significant > list. I noticed that all of the mailman packages seemed to be "Type > sdist" and the framework packages "Type wheel". (Dunno what "Type" means > in this context.) Type is the package type. sdist is a source distribution. wheel is a form of binary distribution. Older forms are egg and bdist. > So I tried `pip list -o | grep sdist` and got a smaller list: > > (venv) mailman@mail:~$ pip list -o | grep sdist > atpublic 2.1.1 2.3 sdist > django-allauth 0.43.0 0.45.0 sdist > django-mailman3 1.3.4 1.3.7 sdist > flufl.i18n 3.1.3 3.2 sdist > flufl.lock 5.0.3 6.0 sdist > HyperKitty 1.3.3 1.3.4 sdist > lazr.config 2.2.2 2.2.3 sdist > mailman 3.3.2 3.3.5 sdist > mailmanclient 3.3.1 3.3.3 sdist > mysqlclient 2.0.1 2.0.3 sdist > postorius 1.3.3 1.3.6 sdist > > Is this a reasonable list of the packages that I should update? Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. -- 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: Multiple server replicas

by Mark Sapiro

On 5/23/23 19:33, Dave Hall via Mailman-users wrote: > > With Mailman 3 we would like to keep the same kind of setup. However, > things have changed quite a bit. Having both mailman and mailman-web > instances all share their respective MySql/MariaDB databases is the easy > part. For /var/lib/mailman3 it is a little less clear. So far I have > symlinked messages, archives, lists, data, and templates onto the NFS > share. I'm wondering about cache, locks, queue, and web/fulltext_index. cache is used to store the contents of templates which are retrieved by URI other than mailman:// URIs. I.e. mailman:// URIs refer to templates in the templates directory or in the Mailman installation itself so are cheap to retrieve. Other URIs can refer to possibly remote servers and may be expensive to retrieve so the contents are cached. In short, this should be shared. locks contains the master lock and others locking things used by this instance. This should not be shared. queue is the queues for this instance and should not be shared. In your installation, web/fulltext_index is the search index for whoosh which is apparently the hyperkitty configured search engine. This should be shared. -- 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: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 2:18 AM, marcus--- via Mailman-users wrote: > > The problem, however, is that it does not send out any mails, nor do they appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 This is a misleading error message. It can occur when Mailman's out runner can't read a template. You need to check ownership and permissions on mailman/templates in the code tree and Mailman's var/templates directory which probably has permissions errors from running inport21 as root. Also, if you've set any templates in Postorius, they may not be accessable if your setting for POSTORIUS_TEMPLATE_BASE_URL is not good. > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: > [Errno 111] Connection refused Are you gating messages to/from usenet for this list? If so, you have to set host: and port: and maybe user: and password in the nntp section of mailman.cfg -- 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: Database permission problem?

by Mark Sapiro

On 10/15/24 15:24, Bill Oliver wrote: > > Yeah, I saw that, too. The double db files are created by postmap. I > haven't worried about it too much yet, since the permissions are the > same. I don't know why postmap does this, but it's next on my list of > things to fix. You should not be running postmap manually and never on a *.db file in any case. Mailman should be creating postfix_domains, postfix_lmtp and postfix_vmap and calling postmap on those to create the .db files. > In my main.cf postfix_lmtp is mentioned four times: > > virtual_mailbox_maps = > proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, > > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf > #added 20241009 for mailman > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} > > virtual_alias_maps = > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, > > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c > f > #added 20241009 for mailman > hash:/opt/mailman/mm/var/data/postfix_vmap > > #Mailman transport stuff > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} Are you adding ${dovecot} to the local_recipient_maps and virtual_mailbox_maps mailman entries or was that there before? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: [Mailman-Users] Re: Member posting to a list but address not in membership list.

by Mark Sapiro

On 1/12/22 7:42 PM, Adam Morris wrote: > Hi Mark, > I've looked in all these places and the address isn't anywhere. (please keep the thread on the list) Then the address that's posting isn't what you think it is or something in your installation is broken. As I said, it could be that Reply-To: or Sender: is the list member, but depending on list settings, these things get overwritten in mail from the list, so you can't really know. If something is broken, you need to discuss this with your hosting provider who, unfortunately, may be no help. Many, not all, cPanel hosts offer mailman because it comes with cPanel, but actually know nothing about Mailman. See https://wiki.list.org/DOC/Mailman%20and%20CPanel > On 13-January-2022 11:31, Mark Sapiro wrote: >> On 1/11/22 7:51 PM, Adam Morris wrote: >>> I have someone who is posting to a list I run. >>> I subscribed them originally but their address doesn't show up in the >>> list of members so I can't change moderation status etc. >>> Where else could I look to find their address? >> >> >> The first check on a post is if any of the address in From:, Reply-To: >> or Sender: headers or the envelope sender is a list member, i.e. in >> the web admin Membership List. If so, that member's moderation is >> applied. If not, the next check is if the From:the *_these_nonmembers >> lists under Privacy options... -> Sender filters and finally Privacy >> options... -> Sender filters -> generic_nonmember_action. >> >> If a post to the list is being accepted without being held for >> moderation, either some address in From:, Reply-To: or Sender: headers >> or the envelope sender is in the Membership List with `mod` unchecked, >> or the From: or possibly Sender: address is in accept_these_nonmembers >> or generic_nonmember_action is Accept. >> > > -- > > Adam Morris > Mobile: 0414 431105 > Email, iMessage & FaceTime > adam(a)damorris.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, 11 months

[MM3-users] Re: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/19/2018 03:22 AM, Henrik Rasmussen wrote: > > Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. If DMARC Mitigate unconditionally is No, DMARC mitigation action will only be applied if the original From: domain publishes a DMARC policy of quarantine or reject. If the action is not being applied in this case, there is some issue in looking up the DMARC policy for the domain. Possibly, dnspython is not available or there is some other issue with this. In any case, errors should be logged in Mailman's log. > Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? You need to do this with list styles. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. At present, Postorius doesn't allow specifying a style when creating a list, so you may need to modify mailman/src/mailman/styles/base.py. -- 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: Adding / manipulating users

by Mark Sapiro

On 11/18/19 6:15 AM, Seth Seeger wrote: > > My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. You are correct that there is no existing command line tool or Postorius way to do this. If you have facility with Python, you can look at the mailman import21 command which is actually processed by mailman/utilities/importer.py. It shouldn't be too difficult to adapt the part that imports the list members to use your data and create a script to do what you want. Alternatively, you could create a script that would post the appropriate transactions to add a member and set moderation and delivery status to Mailman's REST API and use that to process your members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Hyperkitty: Error when rebuilding Index

by Mark Sapiro

On 11/26/21 4:35 AM, M4tze wrote: > Dear list members, > > if there is any Hyperkitty expert here, I have issues in Hyperkitty > (just updated Maxkings Docker images) when rebuilding the Index. > > Unfortunately, there are more than 25,000 mails and I do not know which > one is/might be broken. Does the error mean that the rebuilding process > is incomplete or does it simply skip the erroneous message? It means the process is incomplete. > Traceback (most recent call last): ... > return self._result.fetch_row(size, self._fetch_type) > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position > 3209: invalid continuation byte I'm not sure what's going on here. I suspect the issue is withe the `content` of some message in the hyperkitty_email table in the database. You could try a database query like ``` SELECT * FROM hyperkitty_email WHERE LEN(content) >= 3209; ``` If you're lucky, that may just return a few messages and enable you to find the problem one. Otherwise, you could try first running `mailman-web clear_index` and then run `mailman-web update_index` with --start and --end options to specify a date range and zero in on the offending 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

[MM3-users] Re: Mailman3-web/Postorius behind Lighttpd

by Mark Sapiro

On 2/16/22 10:00, Élodie BOSSIER via Mailman-users wrote: > > I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from > packages : When you install Debian packages, your primary support resource is Debian. ... > I can access from localhost to http://127.0.0.1:8000/ which move me > correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be > correct. > > But 127.0.0.1:8000 listen only in localhost : > #netstat -tanpu | grep 8000 > tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN > 626175/python3 Which is as it should be. > So I try to use my lighttpd as proxy as recommanded with this config : > > >> scgi.protocol = "uwsgi" >> scgi.server = ( >> "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => >> "disable" )), >> ) > > but it's return me a "502 Bad Gateway". I don't know anything about lighttpd, but the fact that you can access http://127.0.0.1:8000/ from localhost and that seems to work suggests that you shouldn't be using uwsgi protocol, but just a straight http proxy. See https://redmine.lighttpd.net/projects/lighttpd/wiki/HowToPythonWSGI#lighttp… and https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy -- 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: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/28/23 09:39, Odhiambo Washington wrote: > Now that you have mentioned > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…,, > please show me how to import it, edit. Then I can submit a diff. > Alternatively, I'd love to be given access to edit that document (and the > edit can be reviewed before getting published) to make it easy to follow by > someone with zero python background. > I am willing to invest some time in improving it for laymen. There are multiple ways to proceed. The simplest is to just download https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v… (there's a download button on that page), edit that and post the edited file somewhere where we can get it to look at. The better way is more complex. That way is for you to create a personal project space at https://gitlab.com/users/sign_up and clone the mailman/mailman-suite-doc project into your personal space and edit it there and then create a merge request to merge your edits into the mailman/mailman-suite-doc project. GitLab documentation is at https://gitlab.com/help -- 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: configuring postfix local recipient table

by Mark Sapiro

On 4/23/25 9:25 AM, Stephen J. Turnbull wrote: > Alexander Inzinger-Zrock via Mailman-users writes: > > and then i just found out that my postfix_lmpt file was empty > > 1. What database are you using?[1] Is it running? If not, yes, that > file is going to be empty. > 2. Do you have any lists configured for your Mailman 3 instance? If > not, that file will be empty. > 3. Is Mailman running? (This probably isn't necessary, just > checking.) > 4. Is there a postfix_lmtp.db file in the same place? (Postfix will > not read the plaintext version, it must be a .db file.) If you haven't set `incoming` in the `mta` section of mailman.cfg to other than the default `mailman.mta.postfix.LMTP`, the `mailman aliases` command will at least write ``` # AUTOMATICALLY GENERATED BY MAILMAN ON {} # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. ``` to the postfix_lmtp file. -- 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: Installation issues

by Mark Sapiro

On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > > I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? Sort of, but it's not (yet) public. The process I followed is very convoluted and not what I would recommend anyone follow. Part of the issue is I started with mailman-bundler not using a venv, but bundler still installs a lot of stuff in Python 2 and Python 3 venvs. I then proceeded to install the git master branches of mailman, mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their dependencies system wide and ripped out most of the venv stuff. Then there were issues because I'm running django 1.9 only and that's not compatible with django_haystack 2.4.1, so I upgraded that to 2.5.dev0 from GitHub, but that now has a compatibility issue with HyperKitty which I have worked around. As you can see this is not a clean process. If I were starting over with what I've learned, I'd probably let bundler install it all in venvs and then upgrade the venvs to the git master branches. There would still be issues, but it would be cleaner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 7 months

[MM3-users] Re: How to change the language in mailman3

by Mark Sapiro

On 7/17/20 8:22 AM, maszap(a)tin.it wrote: > Hi everyone, > from here: > https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/it/ > I see that there is a way to change the language of mailman3, postorius and hyperkitty > But I don't find how. > I read that you can download the .po files for the chosen language, but I didn't understand how to use these files. > Could anyone show me how to do it? The various message catalogs for Mailman core are in mailman/messages/ and those for hyperkitty, django-mailman3 and postorius are respectively in hyperkitty/locale/, django-mailman3/locale/ and postorius/locale/. The translations from weblate are incorporated in the distribution, but depending on how Mailman is installed, may be out of date. To set language for Django (i.e. hyperkitty and postorius) see <https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-d…>. For Mailman core, set `[mailman] default_language:` in mailman.cfg. You also need to (re)generate the .mo file which can be done with the generate_mo.sh script. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/inter…> For Django, you need to generate .mo files with `django_admin compilemessages` -- 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: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/17/24 12:06 PM, Keith Christian wrote: > The path to the mailman3.py file is: > /home/mailman3/mailman/src/mailman/bin/mailman.py > I created a mailman3 user, then, set the ownership on all directories > and files in /home/mailman3 and below to mailman3:mailman3. You need to install all the dependencies and also have /home/mailman3/mailman/src/mailman in your PYTHONPATH. If you just want Mailman Core and given that you've already cloned it from gitlab, I suggest creating a Python virtual environment as the mailman3 user with `python3 -m venv /path/to/your/venv` and then as the mailman3 user activate the venv, `source /path/to/your/venv/bin/activate`, and do `pip install /home/mailman3/mailman` to install Mailman and it's dependencies in the venv. Then you can just run `mailman info`. I suggest a venv for this to isolate the dependencies from things that might already be installed system wide with differing versions. To install the whole suite including the Postorius web UI for list management and the HyperKitty archiver, see 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

1 year, 6 months

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mark Sapiro

On 6/16/23 22:14, Stephen J. Turnbull wrote: > > @Mark > I've been seeing an unusual number of disabled subscriptions on > python.org and mailman3.org lists recently. Maybe we should look into > this. If you haven't seen this O365 breakage, I can send you some > samples. I haven't noticed this. I do receive notices when delivery is disabled, and I generally look at the attached DSN, and I don't recall any that have this issue. We do have an issue with mailman-users(a)mailman3.org messages for five users in the outlook.com, msn.com and hotmail.es domains. These are all since the server was moved last month and are all for the reason 550 5.7.1 Unfortunately, messages from [165.227.190.41] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [VI1EUR05FT020.eop-eur05.prod.protection.outlook.com 2023-06-17T05:14:54.401Z 08DB6E025E06C828] with differences only in the bracketed part at the end. The same five addresses keep getting disabled because I keep re-enabling them, and I have contacted Microsoft about this, so far with no results. -- 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: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/14/24 06:13, Gerald Vogt wrote: > Hi, > > sorry to bother, but does anyone have an idea why this doesn't work? I > am on mailman 3.3.10 by now but still not difference. I wonder why > nobody else has the same problem. I didn't think my setup would be so > special... > > Thanks, > > Gerald > > vogt＠spamcop.net wrote: >> >> Hi, >> >> I am running a mailman 3.3.9 server (pip installation). It's working >> fine so far. However, I have problems setting a template. I set a >> '[list:user:action:subscribe]' template for a list with some simple >> text like "test1234". How are you creating the template? If you are creating it via Postorius, what is your setting for POSTORIUS_TEMPLATE_BASE_URL and what does the entry in the template table in the database look like? POSTORIUS_TEMPLATE_BASE_URL should be the same URL you use to access Postorius up to but not including the `/postorius/` or `/mailman3/` part. I.e, for this list whose info page is at https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/, the setting is ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: MTA setup

by Mark Sapiro

On 11/17/24 19:32, Arte Chambers via Mailman-users wrote: > > Mailman is successfully sending invite emails however user messages sent to > the list are not being sent to subscribers. Also in Hyperkitty none of my > test messages to the list are showing up in the archive. Are there messages in Mailman's shunt queue? Check for errors in mailman.log. Are there messages for hyperkitty queued in Mailman's var/archives/hyperkitty/spool/ directory? > I am using Postfix with an SMTP relay hosted at Brevo.com (formally > sendinblue). Brevo's logs show the message getting rejected > > > Log from brevo.com (SMPT Relay) > Sent on 17-11-2024 21:49:16 >>From listmember(a)gmail.com > To listmember(a)gmail.com > Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= > BJ7Q(a)mail.gmail.com> > > 17-11-2024 21:49:16 > Sending has been rejected because the sender you used listmember(a)gmail.com > is not valid. Validate your sender or authenticate your domain This appears to be something you need to do for the MTA at smtp-relay.sendinblue.com, or possibly something more is needed in /etc/postfix/sasl_passwd. > #SMPT Relay Brevo > relayhost = [smtp-relay.sendinblue.com]:587 > smtp_sasl_auth_enable = yes > smtp_sasl_security_options = noanonymous > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd -- 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: Separating Lists by Domain

by Mark Sapiro

On 1/3/19 2:34 PM, Abhilash Raj wrote: > > > On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: >> So who manages Postorius? Is that a whole separate application from >> Mailman 3? Is there a way we can get whoever the developer is to update >> it where we can separate lists by domain the way Hyperkitty does? Mark >> Sapiro refers to this in the following post: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at https://gitlab.com/mailman/postorius/issues Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome. As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project. Not long ago I write in another context > MM3 is much more complex than MM2.1 and there's a lot that I don't fully > understand myself. > > There is a basic core engine which does all the work of > creating/managing lists and users and receiving and sending mail. It has > no web UI per se. It exposes a RESTful API on the host server. > > The web management UI is Postorius and it is based on the Django web > framework and communicates with core via the REST API. The Archiver is > HyperKitty and it is fairly independent. It is also based on the Django > web framework. Account creation and web login is via django-allauth. > > Postorius, HyperKitty and the core were all developed separately by > different people and no one understands all of it. That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time. And as I said, merge/pull requests for GitLab issues are always welcome. -- 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: Confirmation for subscriptions

by Mark Sapiro

On 6/23/19 7:24 AM, andrew.bernard(a)gmail.com wrote: > Suddenly stopped working. For all the lists I have created, suddenly the confirm setting is ignored for subscriptions and users are subscribed right away. I assume you are looking at the Postorius List Settings -> Subscription Policy. That should reflect the setting in core. How are these users requesting subscription/being subscribed? > This only happened after I added another domain - surely that can't be the cause? Unlikely, but not impossible. > Where to look to troubleshoot this? You could use `mailman shell` to examine the setting in Mailman core, but it's unlikely that would be different from what Postorius shows. Other than that, you can look in logs, but there is not very much logged for the subscription workflow. To be more help, I'd like to know exactly when this happens. First, for Postorius Mass subscribe, this is expected. Other than that, does it happen on email to the list-join address? Does it happen with subscription via the form on the Postorius list Info page? Is it possible the user has a 'vacation' program that is responding to the confirmation request? See <https://gitlab.com/mailman/mailman/issues/23> (we should fix that) -- 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: How to identify the exact reason behind the shunting of the mails ?

by Mark Sapiro

On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > Dear Mark, > > FYI, I observed this issue with the postfix that receives the > mails from the previous MTA and hands it over to the mailman. But I fixed > at postfix by upgrading it to the version postfix 3. > > But still Mailman is not able to understand Hindi (Indian local > language) in which language the display names of the email ids are there. > > So, now what to do at Mailman so that it can also understand > local languages or any work around or other alternate solutions for these > sort of cases. As noted in my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… the issue is a Mailman bug which is fixed in the next release. It has to do with the fact that the display names are RFC 2047 encoded and not the particular encoding. Actually, the fix at https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on https://gitlab.com/mailman/mailman/-/merge_requests/652 which was released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is attached. -- 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: Postorius no connection to REST API

by Mark Sapiro

On 8/13/21 7:18 AM, Richard Rosner wrote: > > I set them all to https. which solved the https error. But I still get Error 500. >>From apache log: > [Fri Aug 13 15:47:58.833305 2021] [mpm_event:notice] [pid 26720:tid 139986206332032] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 \ > Python/3.7 configured -- resuming normal operations > [Fri Aug 13 15:47:58.833436 2021] [core:notice] [pid 26720:tid 139986206332032] AH00094: Command line: '/usr/sbin/apache2' > [Fri Aug 13 15:49:41.673108 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ > rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] > [Fri Aug 13 15:49:41.905868 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ > 7.0.0.1) > [Fri Aug 13 15:59:25.049708 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ > rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] > [Fri Aug 13 15:59:25.059217 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ > 7.0.0.1) You need SSLProxyEngine on and possibly one or more of the SSLProxyMachineCertificate* directives in your apache config to proxy via https. See <https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslproxymachinecertifica…> et seq. -- 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: Problem creating list members using REST API

by Mark Sapiro

On 1/18/22 10:53 AM, Stephen Daniel wrote: > 2nd follow-up. Apologies for spamming this list. > > I went wandering through the code as suggested by the traceback. I > discovered that thee "as_boolean" routine is expecting a string argument > but getting a boolean argument. > > So, If I send the booleans as strings, with values "true" or "false", all > is well. > This is not what the API documentation suggests I should do. Can someone > either fix the documentation or the code? Those snippets in the documentation are doctests. That code is actually executed by unit testing and passes. In all those snippets, dump_json is passing the second argument as `data` to mailman.testing.documentation.dump_json() which in turn calls mailman.testing.documentation.call_http() which calls mailman.testing.helpers.call_api() which ultimately calls requests.request() with the same `data` argument. So basically, the issue is the difference between how requests.request() handles that `data` dictionary in creating the POST data and whatever you are doing. Possibly we could add some caveat to <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> or possibly elsewhere. Do you have a suggestion as to what? -- 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: Weird startup problem after upgrade

by Mark Sapiro

On 12/2/22 08:21, Odhiambo Washington wrote: > I am facing an odd situation in which MM3 doesn't start successfully on > reboot, but I can start it manually. > This is a venv install. > This started after I did an upgrade (pip install --upgrade mailman > postorius hyperkitty mailman-hyperkitty) followed by the requisite > collectstatic|compress|compilemessages|migrate > post-update commands. Was the venv activated when you ran pip? You should also include django-mailman3 and mailmanclient in the packages to be upgraded although they are dependencies and "should" upgrade anyway. Also, at least one person has noted that --force-reinstall was required to get all dependencies upgraded <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > Secondly, it appears that the upgrade did NOT change the versions for the > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > the latest. What does `pip freeze` in the venv show for versions? > Thanks in advance for any insights into what could be causing this. How do you start it manually? `mailman start` or `systemctl start mailman3`? What's the content of /etc/systemd/system/mailman3.service? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: default language ignored

by Mark Sapiro

On 10/02/2017 05:46 AM, Marc Sluiter wrote: > Hi, > > one last question for now: how do switch the language of the mails sent by mailman? > I have this in my configuration, but without effect: > > [language.de] charset: iso-8859-1 > [language.de] description: German > [language.de] enabled: yes > > [mailman] default_language: de It has no effect because there are as yet no translations in Mailman 3. You need to create templates in the desired language. See <http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html> That refers to setting URLs for templates which does work, but the easiest way is to put them in the default search path in Mailman's file hierarchy at $var-dir/templates/. Sitewide ones in $var-dir/templates/site/, Domain specific in $var-dir/templates/domains/ and list specific ones in $var-dir/templates/lists/. For example, a list specific, English language regular (non-digest) message footer might go in $var-dir/templates/lists/mymaillist.example.com/en/list:member:regular:footer > Is it also possible to change the language for a single list? Yes, although that is not yet exposed in Postorius. The list has a preferred_language attribute which you can set via REST or 'mailman withlist' aka 'mailman shell'. -- 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: list of subscribers

by Mark Sapiro

On 02/04/2018 11:37 AM (UTC -0800), Peter Münster wrote: > On Sun, Feb 04 2018, Simon Hanna wrote: > >> IIRC one person(postorius account) can also signup at different lists using >> different names (regardless of address). > > You mean the "display_name" of mailmanclient here? I won't use it. > For my usage, I prefer a clear association of email, first name and > last name in one account, no need for "display_name" here. This would seem to be specific to your use case. I think in general what we would want to display is the display_name from the list's member record. > Off topic: I have "Receive own postings = Yes", but I don't receive > copies of my postings to this list... We tried to send your copy of your post to you, but your MTA called it spam. Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command)) (time stamp is UTC -0000) I suspect it doesn't like the fact that it's From: you but not sent by your server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

Search results for query "sapiro"