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

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 12:58 PM, Simon Coggins wrote: > > Please file an issue for this at > https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a > better solution. Your approach of munging Message-IDs will create other > issues. Consider a post to a list with direct CC to userx. userx > replies-all to the message received directly. the In-Reply-To of this > reply is the unmunged Message-ID which will affect threading in the > archives and other recipient's MUAs. I realize this is preferable to > losing the message, but I hope we can do better. > > > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. -- 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: Getting connection timed out

by Mark Sapiro

On 5/22/21 11:29 AM, blackout69 wrote: > Hello everybody, > > for a couple of days I have been seeing several lines calling these on > /var/log/mail.log > > May 22 18:22:57 glugct postfix/qmgr[21205]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:06 glugct postfix/qmgr[27175]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:36 glugct postfix/smtp[27177]: 0ACE641C1B: > to=<myaddress(a)simail.it>, relay=none, delay=55152, > delays=55122/0.07/30/0, dsn=4.4.1, status=deferred (connect to > mail.simail.it[217.27.113.30]:25: Connection timed out) ... > But always on a single email address.What could it depend on?Probable > that the mail.simail.it server is blacklisted? It's probably not blacklisting. It's not getting that far. Your `glugct` is attempting to connect to port 25 at mail.simail.it and the connect is not being answered. Normal blacklisting will not occur until after the remote MTA answers the connect and determines the IP of the caller. And in any case, if it is some kind of blacklisting it is your `glugct` server that is blacklisted by mail.simail.it. I just did the following ``` $ telnet mail.simail.it 25 Trying 217.27.113.30... Connected to mail.simail.it. Escape character is '^]'. 220 mail.simail.it ESMTP ready. quit 221 mail.simail.it closing connection Connection closed by foreign host. ``` so it did answer my connect. In any case, this is not a Mailman issue. It is between Postfix on your server and the remote server at mail.simail.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, 2 months

[MM3-users] Re: Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface

by Mark Sapiro

On 9/30/23 10:53, Wikinaut wrote: > I use mailman3 since a while, for some of my lists I have been using > > - list:member:digest:footer.txt > - list:member:regular:footer.txt > > When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! Postorius templates are handled differently from file system templates. When you set a template in Postorius, that template becomes available in Postorius' API and an entry for the template in the template table in the database is created with a URI pointing to the template in Postorius' API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for info about template URIs. The fact that Postorius doesn't show the file system template as the initial value when creating a template in Postorius is https://gitlab.com/mailman/postorius/-/issues/366 > When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. They are not created as files - see above. The fact that they aren't working is probably because your Django setting for POSTORIUS_TEMPLATE_BASE_URL is not correct. This should be set to the scheme and host part of the URL you use to access Postorius, e.g., https://lists.mailman3.org for this list's installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Single-Sign-out for List member

by Mark Sapiro

On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > It does not seam to be possible, to put this into effect with mailman 3. > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. You can set the list's unsubscription_policy to open and set the link as a mailto: to the list-leave address, but that still requires a second click to send the mail. The solution is to create a web based CGI script which is called with a URL like <https://example.com/unsub_script/list.example.com/user@example.net> and have that script invoke the appropriate `mailman` command to remove the member from the list. Beginning with Mailman 3.3.2, this would be mailman delmembers -l list.example.com -m user(a)example.net -g to remove the member and send a goodbye message. In older Mailman, it would be something like echo user(a)example.net | mailman members -x - list.example.com I understand you may have a legal requirement do do this, but these "one-click - no user confirmation" links are a bad idea because usera will reply to a list post or forward it and not remove the link and userb will receive usera's reply and click usera's unsubscribe link either maliciously or thinking it will unsubscribe userb. -- 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: New releases

by Abhilash Raj

On Thu, Jun 25, 2020, at 8:59 AM, Danil Smirnov wrote: > The issue has confirmed by other users: > > https://github.com/maxking/docker-mailman/issues/382 The issue seems to happen because the static files that are present at the default staticfile locations aren't valid anymore and aren't removed automatically on upgrades. You can run: sudo rm -rf /opt/mailman/web/static To remove them manually and then it should be re-created properly on the next start. I'll try to work on a fix for this in some automated fashion. > > вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > > > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > >>> COMPRESS_OFFLINE = True > > >>> COMPRESS_ENABLED = True > > >> > > > > > > These two are commented out. > > > > > > Then compress shouldn't be trying to do anything. I can't explain what's > > going on. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

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

by Mark Sapiro

On 7/30/20 11:24 AM, Odhiambo Washington wrote: > This works - I mean changes the error message to > > [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] > /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) I'm not sure why you are getting this warning, and it's non-fatal, but you can get rid of it by pip install cmarkgfm in your virtualenv. > [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client > 197.232.81.246:63962] AH01630: client denied by server configuration: > /var/spool/mailman-web, referer: > http://mm3-lists.my.server/mm3/mailman3/lists/ > > There is NO /var/spool/mailman-web anywhere. It has not been created. > You mentioned that it should be created automatically, IIRC. No. I think I told you that the references to /var/spool/mailman-web/static in your Apache config should be changed to /opt/mailman/mm/static and that directory would be created/populated by mailman-post-update. I think you still have Alias /static "/var/spool/mailman-web/static" in your Apache config and it needs to be Alias /static "/opt/mailman/mm/static" That may be my fault as when I recently edited <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>, I missed that line. -- 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: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. ``` Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is ``` Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Mark Sapiro

On 3/18/19 2:19 PM, Ralph Seichter wrote: > Hello list. > > I have read [1] and [2], but I am not quite sure what the recommended > method is to completely disable message headers/footers and subject > modifications for *all* lists tied to a specific domain. Being new to > Mailman 3, I was actually surprised that there are no configuration > switches in the Web UI's settings for mailing lists that allow me to get > rid of unwanted message decorations. It's still a work in progress. You can do it via list settings except for one issue [1]. See that issue and also the post referenced in it's description [2]. To not modify the Subject for a list, on the list's Settings -> List Identity tab, set 'Subject prefix' empty. To not add headers and or footers, you need empty templates for them. These could be created via the list's Templates form except until [1] is fixed, you can't make empty templates. You can use the method in [2] to create empty var/templates/domains/DOMAIN.NAME/LC/list:member:generic:footer.txt and var/templates/domains/DOMAIN.NAME/LC/list:member:generic:header.txt files for the domain and language. Then as long as no list specific templates are created for lists in that domain, no headers or footers will be added. [1] <https://gitlab.com/mailman/postorius/issues/331> [2] <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

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

by Mark Sapiro

On 9/22/20 12:20 AM, r.woithe(a)callassoftware.com wrote: > Hello, > this is the complete email we get every night: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs > job().execute() > File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 36, in execute > sync_with_mailman() > File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 146, in sync_with_mailman > sender.set_mailman_id() > File "/usr/lib/python3/dist-packages/hyperkitty/models/sender.py", line 55, in set_mailman_id > mm_user = client.get_user(self.address) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 320, in get_user > response, content = self._connection.call( > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1948, in request > (response, content) = self._request( > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1621, in _request > (response, content) = self._conn_request( > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1560, in _conn_request > response = conn.getresponse() > File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse > raise ResponseNotReady(self.__state) > http.client.ResponseNotReady: Request-started > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > START TRACEBACK: > END TRACEBACK OK. So python2.7 in the Subject: is not relevant. The issue is probably a timeout in mailmanclient's REST request. See <https://wiki.list.org/x/17892072> for info on how to increase 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, 10 months

[MM3-users] Re: hyperkitty_import Unicode Errors - Drop all Archives and Start Over?

by Mark Sapiro

On 5/16/23 08:49, Dave Hall via Mailman-users wrote: > > What I would really like to do is to drop all of the previous archives and > start fresh. Looking at the table list for the database, It would appear > that all of the archive content is stored in the tables with names that > start with 'hyperkitty_' I'm wondering if I could just wipe the content of > these tables, or exclude them from a backup, and then start fresh. It is correct that all the HyperKitty tables start with `hyperkitty_`. I *think* it would be safe to just drop the content of these tables, but I won't guarantee that there aren't `django_mailman3_` tables with foreign keys into the hyperkitty tables. As a superuser logged in to hyperkitty, you should see a Delete Archive button at the top level overview for a list. It would be safer to delete the archives that way. > Alternatively, if I restore the exiting archives to the new database with > the correct unicode settings, could I re-run the hyperkitty-import tool and > get it to pick up all of the messages it skipped due to the unicode problem? This will work too. You will need to specify the --since option to hyperkitty_import because the default for `since` is the date of the newest message in the archive. The import will not reimport a message whose Message-ID: is already in the archive. -- 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: Remove old bounces in bouncedir

by Mark Sapiro

On 3/10/22 00:31, Stephan Krinetzki wrote: > Mark Sapiro wrote: > >> If you are referring to messages in Mailman's bounces queue, if these >> are not processed and removed within 15 minutes of arrival, Mailman's >> bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > ``` > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > ``` > > The process it self is there > > ``` > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > ``` I don't understand what's happening. If the bounces runner is processing it's queue, those .pck files should be processed and deleted. Are there errors in /opt/mailman/var/logs/mailman? If you examine (some of) those files with `mailman qfile` do you see anything strange? Is there an ownership/permissions issue? Sometimes people run Mailman or some Mailman command as `root` and things get owned by root and then when Mailman is later run as `mailman` it can't delete or maybe even read them. >> If you are referring to bounce messages in the message store >> (var/messages/), there have been issues with those not being removed, >> but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. Is the size of the /opt/mailman/var/messages directory very big? -- 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: mailman break DKIM signature by modifying body

by Mark Sapiro

On 6/5/23 07:06, Peter Münster wrote: > Hi, > > I'm using mailman 3.3.8. > > Some messages with attachments from Google users get rejected by spam > filters because of invalid DKIM signatures. > > It seems, that mailman alters some lines in the body. Here an example: > > Original message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2031 > > --000000000000f846c505fc494b7a-- > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > Altered message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2032 > > --000000000000f846c505fc494b7a-- > > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > An empty line is added, and the spaces after the semicolons are removed. > > Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. > > What could I do please, to prevent such modifications of the body? Changes like those above are due to Python's stdlib email module. Short of actually modifying the email module, there's nothing you can do to prevent them. Instead, you should be DKIM signing your outgoing mail and perhaps applying Mailman's DMARC mitigations if DMARC is an issue. If you are DKIM signing your outgoing mail and mail is being rejected because of prior invalid signatures, you can remove those by adding `remove_dkim_headers: yes` to the [mta] section of mailman.cfg. Also, ARC signing <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…> may 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, 1 month

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 7/4/20 9:03 AM, tom(a)gather.coop wrote: > > So I hope there is not an expectation that the rDNS domain match the email sender domain. If so I'm toast. Is it just sort of a smell test to see if the server looks legitimate? Probably part of your confusion is the ambiguity of the term `sender` which can refer to any of: - the actual individual sending the original mail (the From: header) - the envelope sender (the listname-bounces@listdomain address in the case of list mail) - the sending server. In the case of FCrDNS we're talking about the server (MTA) delivering the message to the recipient MX. I.e., that server's IP should have a PTR to its name and its name should have a A (or AAAA in the case of IPv6) record with the same IP. That's what FCrDNS implies. Quoting from <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>: "... the requirement is the forward and reverse lookup for the sending relay have to match, it does not have to be related to the from-field or sending domain of messages it relays." It is also good if the name by which the MTA identifies itself (the myhostname setting in Postfix) is the same as the server's name. Quoting from the same article: "Some e-mail mail transfer agents will perform FCrDNS verification on the domain name given on the SMTP HELO and EHLO commands. This can violate RFC 2821 and so e-mail is usually not rejected by default." -- 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: hyperkitty.lib.utils Failed to update the fulltext index

by Mark Sapiro

On 4/17/19 8:10 AM, Abhilash Raj wrote: > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: >>> >>> Which version of Hyperkitty are you using? >>> >>> Did you upgrade the version of Hyperkitty when you migrated to the >>> new host? >> >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple >> releases), so it's hyperkitty 1.1.4. >> >> I didn't upgrade anything with the move. > > I am not sure where does Debian packaged version store it's fulltext index, but > I am assuming the move somehow makes Hyperkitty not be able to read the > index. I think this is a known incompatibility between the Python 2.7 and Python 3 versions of Whoosh. From the tracebacks, the current HyperKitty is running under Python 2.7. If the prior server was running HyperKitty with Python 3, that would explain this. > Can you try removing and re-building the entire index? I don't know again > the right command for Django there, but the hyperkitty command you want > to run is called `rebuild_index`. For source package, something like: > > $ python manage.py rebuild_index > > Do note that this will take a lot of time if you have a big archive. If this is the incompatibility, rebuilding the index will fix 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, 3 months

[MM3-users] Re: How to remove global ban using API?

by Mark Sapiro

On 5/15/19 9:46 AM, Nathan Dixon wrote: > > I can create the ban fine by the following: > > from mailmanclient import Client > client = Client(URI,apiuser,apipass) > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") This is apparently a typo - missing ')' - in the re as you have it correct below. > However, I cannot seem to be able to remove it using the api: >>>> client.bans[0].delete() ... >>>> client.bans.remove(str(client.bans[0])) ... >>>> > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") All of the above work for me with both API 3.0 and 3.1 in a non-docker install of the current GitLab HEADs > And also, when I now try and go into the mailman-core docker image to use > the mailman.interfaces.bans, it will not let me see the global bans: > >>>> from mailman.interfaces.bans import IBanManager >>>> global_bans = IBanManager(None) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: ('Could not adapt', None, <InterfaceClass > mailman.interfaces.bans.IBanManager>) I don't see this either. > I have opened an issue in Gitlab for this as I feel it may be a bug related > to regex and global bans (there was a similar one for list banned > addresses): https://gitlab.com/mailman/mailman/issues/598 I also commented on the GitLab issue. I think this must be an issue with the docker images. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

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

by Mark Sapiro

On 12/18/23 6:24 AM, Helio Loureiro wrote: > Hi, > > Indeed it was the configuration. It was placed into > /etc/mailman3/mailman-web.py. After a I changed to > /etc/mailman3/settings.py a few things advanced a little bit more. > > I had to figure out how to fix mysqlclient installation since there isn't a > mention about it and the simple "pip install mysqclient" was breaking with > pkg-config issues. But it did work at the end. > > Now I can see further messages on mailman3-web than before. > > (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate > System check identified some issues: > > WARNINGS: > account.EmailAddress: (models.W036) MariaDB does not support unique > constraints with conditions. > HINT: A constraint won't be created. Silence this warning if you don't care > about it. > account.EmailAddress: (models.W043) MariaDB does not support indexes on > expressions. > HINT: An index won't be created. Silence this warning if you don't care > about it. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > Applying account.0004_alter_emailaddress_drop_unique_email...Traceback > (most recent call last): I'm not sure why there would be an issue with this migration, but there is a possible compatibility issue depending on how you installed things. django-mailman3<=1.3.11 is not compatible with django-allauth>=0.58. In your venv, try ``` pip install django-allauth\<0.58 ``` -- 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: Hyperkitty - Non-ascii sender address

by Mark Sapiro

On 10/28/18 12:03 PM, Guiseppin Thomas wrote: > Hi, > > I imported some mbox archives in Hyperkitty. > > I have lot issues like: > > /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: > ('Non-ascii sender address', <email.message.EmailMessage object at > 0x7f05f1606048>)// > //Non-ascii sender address from "Stéphane blipblop <stlablipblop at > gmail.com>" about [HATLAB][It] Re: A débarrasser ! / > > It's probably because "Stéphane". The 'Non-ascii sender address' message comes from > try: > from_str = header_to_unicode(message['From']) > from_name, from_email = parseaddr(from_str) > from_name = from_name.strip() > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > raise ValueError("Non-ascii sender address", message) Possibly the exception is thrown in parseaddr(), but much more likely, the email address, not the display name contains non-ascii. > Some advise to fix it ? All the other messages should have been imported. If you can find and fix the 'bad' ones in the mbox, you can make a new mbox with just those and import that. You could also import the entire mbox with fixed messages. The already added ones won't be re-imported because of duplicate Message-ID:, but it's extra processing. If the actual bad message From: header is From: Stéphane blipblop <stlablipblop(a)gmail.com> or From: Stéphane blipblop <stlablipblop at gmail.com> That shouldn't cause the error, so I'g guessing that 'blipblop' is not the actual value and the actual value in <stlablipblop at gmail.com> has non-ascii. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Changing Mailman's "from" domain

by Mark Sapiro

On 5/16/19 8:21 AM, Roger Hislop (IS) wrote: > > If I subscribed an address, no confirmation email would come through. Checked the Postfix log and see this: > > May 16 14:34:50 ip-172-31-23-250 postfix/smtp[5025]: 15B87A35FB: to=<iotic-za(a)reasondigital.co.za>, relay=email-smtp.eu-west-1.amazonaws.com[52.51.155.83]:587, delay=0.22, delays=0.01/0.02/0.1/0.1, dsn=5.0.0, status=bounced (host email-smtp.eu-west-1.amazonaws.com[52.51.155.83] said: 554 Message rejected: Email address is not verified. The following identities failed the check in region EU-WEST-1: test-list-request(a)iotcouncil.org.za, test-list-bounces(a)iotcouncil.org.za (in reply to end of DATA command)) > > I've verified the domain listman.iotcouncil.org.za, so it would seem the obvious solution is to change the domain the mails come from. > > It appeared that I just change the postfix config to specify domain list so: Those addresses are the From: address (test-list-request(a)iotcouncil.org.za) and the envelope sender (test-list-bounces(a)iotcouncil.org.za) These are set by Mailman in the message and the SMTP transaction. Postfix doesn't normally rewrite them. The domain in these addresses is 'web host' defined in Mailman's domain record associated with the list which is also the domain in the list's posting address If you want Postfix to rewrite the envelope sender domain, see <http://www.postfix.org/ADDRESS_REWRITING_README.html#generic> > I see that messages TO the mailman server are also not being delivered ("-- 5.1.1 Requested action not taken: mailbox unavailable"). So there's another problem. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/24/22 10:57, sascha.rissel(a)gmail.com wrote: > Hello, > > I have newly set up Mailman 3 on Ubuntu 20.04. > Sending and receiving mails between list members does work, but I am currently experiencing two issues: > 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. > 2) Archiving is activated within list settings, but there isn't any archive created. > > I found this thread, where the first of these issues is also described: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. > I am running Mailman 3.2.2 on Python 3 .8.10. This is only one of the issues with the Debian/Ubuntu packages. > So I need to either upgrade Mailman Core or downgrade Python. > I already did >> apt-get upgrade >> apt-get update > Unfortunately this didn't upgrade Mailman Core's version. > > Which steps do I have to undertake to upgrade Mailman Core? I suggest first removing the Debian/Ubuntu packages and installing the PyPI packages following docs at https://docs.mailman3.org/en/latest/install/virtualenv.html. There are also other takes on this at https://wiki.list.org/x/17891998; https://wiki.list.org/x/17892066 and https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… This will require some effort, but you will be freed from dependence on out of date packages. -- 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: digests are created but not sent out

by Mark Sapiro

On 1/9/19 12:20 PM, "Jörg M. Schulz" wrote: > when I use the lines below, the templates are looked for in //var. > When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. //var refers to the directory defined in mailman.cfg (or the default in mailman/config/schema.cfg) as [paths.master] var_dir: Exactly which of the following lines did you add and then comment out? Just the three lines > [language.en] > charset: utf-8 > enabled: yes or something more? > mailman.cfg: > > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: help(a)elternserver.de > > # This is the local-part of an email address used in the From field whenever a > # message comes from some entity to which there is no natural reply recipient. > # Mailman will append '@' and the host name of the list involved. This > # address must not bounce and it must not point to a Mailman process. > noreply_address: noreply > > # The default language for this server. > default_language: en > [language.en] > charset: utf-8 > enabled: yes > > [language.de] > description: German > charset: iso-8859-1 > enabled: yes -- 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: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/29/20 5:23 AM, Brian Carpenter wrote: > I have a list owner who had his subscription policy set to confirm. > Apparently that was too hard for his list members to handle so he > changed it to moderate only. If someone sent a subscription request that > needed to be confirm, did not respond to it, and then tried subscribing > again after the member policy changed to moderate, their 2nd > subscription attempt still shows up in the confirmation queue. Is that > normal behavior. My understanding is it is. Please let me know if I am > wrong here. Are you certain that the request waiting confirmation is the second one and not the first? > The real mystery here is when someone tried subscribing again > (listname-subscribe@listdomain) hours after the subscription policy was > changed to moderate and they still showed up in the confirm queue. How > is that possible? I tested the list with two of my addresses and both > showed up in the moderation queue as expected. As far as I can tell from > the mailman logs, this was the person's first attempt at subscribing. I suspect it was not the first attempt and that the subscription waiting confirmation was requested when the policy was confirm. The real question is if a user has a subscription waiting confirmation and the policy is changed to moderate, is a second request rejected because of the request waiting confirmation. If so, I think this is a bug which should be fixed. -- 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: no bounce-processing with verp_probes: yes

by Mark Sapiro

On 12/6/23 06:26, Stefan Bauer wrote: > Dear Users, > > during one of our upgrades to 3.3.x we set verp_probes: yes according to > upgrade notes[1]. > > However it looks like this disabled bounce handling completely. > > Howto verify (MM 3.3.9): > > Set > verp_probes: yes > verp_delivery_interval: 1 > restart mailman3 > create test-list > add an undeliverable recipient to the list that is known to bounce. > send 6 mails to list. Bounce score is only incremented on the first bounce for that day. > see, that all the bounce-messages are received by mailman according to > postfix log[2] So they are delivered. At this point, having set `verp_probes: yes` has no effect on the processing. It only comes in to play when the threshhold is reached. > check bounce.log - no entry. > get bounce_score from API[3] - shows bounce_score 0. This says bounces are not being processed. Is the bounces runner running? If it is there should be entries like Member undeliverable-recipient(a)realdomain.tld on list v-test.lists.lists.tld, bounce score = 1. and Member undeliverable-recipient(a)realdomain.tld already scored a bounce on list v-test.lists.lists.tld today. in bounce.log. and bounce score should be 1. This is independent of `verp_probes: yes`. If the bounce runner is not running, stop and start Mailman core. You must stop and then start, not restart. Also check mailman.log for a reason why bounces runner is not running. If bounces runner is running, check mailman.log for possible errors relating to 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, 7 months

[MM3-users] Re: changing the main template for subscriptions and more

by Mark Sapiro

On 2/1/22 12:40, Paul Paulchen wrote: > Hi Mark, > > thanks for your advice. Unfortunately we need some more clues. > First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman I do not know what the file layout is in the Docker container, so I can't verify paths. > Our version: > Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > > We put an example footer.txt into the templates folder as you mentioned: > mailman3_core => var/templates/sites/de/list:member:regular:footer.txt > Mailman user can read them As I said, I can't give you an absolute path. If you can run `mailman info` in the container, that will show the location of mailman.cfg which may help Installing the template as you have should work if it's the correct path. > Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt The default templates are in the mailman/templates/ directory where the mailman/ directory is where all the Mailman core software is. Hopefully someone familiar with Docker and the Mailman Docker container can provide better information. -- 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: Apache+mod_wsgi issue

by Mark Sapiro

On 12/25/22 01:14, Odhiambo Washington wrote: > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> How about https://mm3-lists.kictanet.or.ke/user_profile/ ? >> > > I have uncommented the line "WSGIScriptAlias /user-profile > /opt/mailman/mm/wsgi.py", > I don't see any definition for it in urls.py as well. Perhaps that's the > issue? It is defined in django_mailman3/urls.py which is referenced by re_path(r'', include('django_mailman3.urls')), > When I uncomment /user-profile, I end up with an ugly URL: > https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ > > So instead of aliasing the /user-profile, I have decided to add another > definition to urls.py: > re_path(r'^user-profile/', include('allauth.urls')), > Which I think gives me a cleaner URL: > https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ It shouldn't include `allauth.urls`. That URL is appropriate if you aren't logged in, but what do you get when you are? Go to https://lists.mailman3.org/user-profile/ and log in if necessary and you'll see what it should look like. > I also had to alias /accounts, which then brings me to: > https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I believe > is fine because one gets the > option to either login or signup. > > And I think that "/account" and "/user-profile" are synonymous. They are in your instance because of re_path(r'^user-profile/', include('allauth.urls')), but they should not be. >> It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time >> (I now use gunicorn on all the sites I manage), but when I did I think I >> had > > >> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py >> >> and all the URLs were like https://example.com/mm3/mailman3/..., >> https://example.com/mm3/archives/..., etc. >> > > I already had gunicorn working too, but I just need to also figure out this > mod_wsgi. Why? Intellectual curiosity or do you have an actual need. The bottom line is with mod_wsgi, whatever you have in your WSGIScriptAlias is going to be prepended to the URL path. If you don't want anything prepended, you need ``` WSGIScriptAlias / /opt/mailman/mm/wsgi.py ``` but then in order for user-profile to work, you need to replace ``` re_path(r'', include('django_mailman3.urls')), ``` in urls.py with the urlpatterns from django_mailman3/urls.py ``` re_path(r'^user-profile/delete$', delete_account, name='mm_user_account_delete'), re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), ``` and also add ``` from django_mailman3.views.profile import delete_account, user_profile ``` to the imports 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

2 years, 7 months

[MM3-users] Re: unwanted chunked delivery

by Mark Sapiro

On 1/7/22 11:04 AM, mm3-omf(a)sh.werbittewas.de wrote: > debian-dist mailman3 3.3.3-1. > > every post to this list will be chunked into one delivery with 60 > recipients and one delivery with 21 recipients. > > we've searched a bit and found a config-option "max_recipients" for > bulk-transfers, but we haven't set it and (as we understand the > explaination for this option) then there should be no limit in one > transfer to the MTA. If you haven't set max_recipients, you get the default which is 500. To set it unlimited you set it to 0 > nevertheless, we've tried to set it to a high value, but even this > doesn't change anything in behaviour. Right, because chunking isn't arbitrary. Chunking is done by recipient domain. The addresses are placed in `buckets` by TLD. All `.com` goes in one bucket; `.net` and `.org` in another; `.edu`, `.us` and `.ca` in a third, and all the rest in a fourth. Then the buckets are chunked with the maximum chunk determined by max_recipients. In your case, 60 recipients are in one bucket and 21 in another. The buckets are defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L29 and the work is done at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L56 My question is why is this important to you? See the FAQ article at https://wiki.list.org/x/4030582 (which is for Mailman 2.1 so it talks about SMTP_MAX_RCPTS which is what max_recipients used to be called) which suggests a much smaller number. -- 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: Installing mailman 3

by Rafael Mora

I think you have to open a new issue to modify the website for the mailman-suite git clone, it should be: git clone https://gitlab.com/mailman/mailman-suite.git El vie., 21 jul. 2017 a las 14:07, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Installing mailman-suite for web ui. I did this: > > (env) [mailman@localhost ~]$ git clone > https://gitlab.com/mailman/mailman-suite/ > Cloning into 'mailman-suite'... > error: RPC failed; result=22, HTTP code = 404 > fatal: The remote end hung up unexpectedly > > > but it returned an error, what should I do?? > > Thanks > > > > > > > > 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 > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Template path

by Mark Sapiro

On 9/17/20 9:33 AM, Seth Seeger wrote: > Hello everyone, > > I’m running Mailman from Docker containers, without much customization. (Postorius 1.3.3, Core 3.3.1, API 3.1, Python 3.8.5). I’ve created a list:user:notice:welcome template, and when I try to confirm a subscription, I get an error. > > I followed previous emails on this list which told me to set POSTORIUS_TEMPLATE_BASE_URL in /opt/mailman/web/settings_local.py, but that doesn’t seem to make any difference. (I set it to a different value and the error message didn’t change. I also tried setting it in /opt/mailman/core/settings_local.py to no effect. After each change, I restarted mailman-web and mailman-core containers.) How did you create the template? In Postorius or by manually creating a file somewhere? If by creating a file, POSTORIUS_TEMPLATE_BASE_URL is not relevant, but ensure that the file is findable and readable by Mailman. > From within mailman-web and mailman-core containers, I can reach “mailman-web:8000”. > > In the webpage, I see: Mailman REST API not available. Please start Mailman core. The REST APT is normally exposed on port 8001, not 8000 (See `port` in `mailman conf -s webservice`. What is your setting for MAILMAN_REST_API_URL? does the port match? > In /opt/mailman/core/var/logs/mailman.log, I get: > > [17/Sep/2020:16:23:29 +0000] "GET /3.1/lists/xxx.example.com HTTP/1.1" 200 416 "-" "GNU Mailman REST client v3.3.1" It appears you are connecting to the REST API, but ... ... > urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) Something appears to be trying to connect to REST on port 8000 -- 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: "held for moderation" - alias domain details sought

by Mark Sapiro

On 11/1/24 11:14, Jeremy Stanley wrote: > On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: >> Hi friends. I've viewed this old thread: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> and documentation here: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… >> (and the Postfix docs it links to). Those documents don't seem to guide my >> situation, or maybe I just need a more specific example. The alias domain discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has nothing to do with what you are doing. >> The problem is that when messages are delivered to the alias domain, they >> are held for moderation. I.e., mail to the alias domain like >> testlist(a)domain.tld is held for moderation, but mail from the same >> subscribed, non-moderated user to testlist(a)lists.domain.tld is posted >> immediately without moderation. > [...] > > I manage a similar setup (though with Exim instead of Postfix), and > when migrating from Mailman v2 to v3 kept the same basic settings > which seemed to work: notably, under Message Acceptance I set the > alias addresses for the list in the Acceptable aliases field. If > memory serves, not doing that caused messages addressed to those > aliases to be unconditionally held for moderation. This is the correct solution. Just add `testlist(a)domain.tld` to the acceptable aliases setting of the `testlist(a)lists.domain.tld` list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 02:14 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users (< > mailman-users(a)mailman3.org>) escribió: > >> You've said you're working with labbrands.com. >> >> labbrands.com has address 192.185.51.89 >> mail.labbrands.com has address 192.185.51.89 >> www.labbrands.com is an alias for labbrands.com. >> >> telnet proves that Exim is running on that IP address. Either you're >> running it, or hostgator is redirecting the SMTP ports. >> >> You added: >> lists.labbrands.com has address 190.145.27.66 >> >> Presumably that's a different machine. >> >> So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > [image: image.png] > > Is it correct??? Your screen shot, along with the excessive quoting, only caused your post to be "too big". All the screen shot says is you have two MX records. The higher priority, 0, is mail.labbrands.com and the lower priority , 1, is lists.labbrands.com. What this means is mail to the domain will be delivered to mail.labbrands.com unless that server is somehow unreachable in which case lists.labbrands.com will be tried. This is probably not what you want. I hate to say this at this point, but you are on a cPanel host. cPanel provides a functional Mailman 2.1 service. You might save yourself a lot of grief by just using that. -- 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: django request error

by Mark Sapiro

On 10/13/21 3:38 AM, eggert--- via Mailman-users wrote: > What's strange, my mailman-web is referred to by > https://lists.tdl/mailman3/ > this show the message as above: > This page either doesn't exist, or it moved somewhere else. > The links in that page refer to urls like: > https://lists.tld/mailman/postorius/lists/ > This URL does not exist, of course. Where is the mailman3 replaced by mailman? All my config files refer to mailman3. How have you installed Mailman? We usually use links like https://example.com/mailman3 and https://example.com/archives in docs for Postorius and HyperKitty respectively. These are the ones in urlpatterns in mailman-web/urls.py We have also used https://example.com/postorius and https://example.com/hyperkitty as alternatives. To enable these, you need to add ``` url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ``` to the definition of urlpatterns in urls.py so it becomes something like ``` urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ] However, that doesn't explain why your `mailman3` URLs get munged to `mailman`. That is apparently a uWSGI thing, and since I've never used uWSGI, only gunicorn and mod_wsgi, I can't help with that other than to suggest that you might have neglected to restart uWSGI after removing the trailing slash. -- 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: Missing whitespace in postfix_vmap after mailman genaliases

by Mark Sapiro

On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 > .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe@lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscribe@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no whitespace.ce in the last line and I made a > new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- 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] Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 1/25/21 11:42 PM, David Partain via Mailman-users wrote: > Hi Gordon (and Mark)! > > I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: > > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.mysql', > 'NAME': 'mailman3web', > 'USER': 'mailman3web', > 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', > 'HOST': 'localhost', > 'PORT': '', > 'OPTIONS': { > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > 'charset': 'utf8mb4', > }, > } > } > > and restarted stuff, but I cannot tell that it has changed anything. That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. If this is the case, it would have been retried and produced the same error with each new post, and after you made the above change, it would have been archived and the errors stopped. > Do I need to do something with the database itself (which is somewhat outside my comfort zone...) to make this work? Are you saying you are still seeing these errors? If so, it may be a different error. What is the exact error message? We don't need all the Django stuff, just the part equivalent to > 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") from the OP. -- 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: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/1/22 18:52, Philippe B wrote: > > But in a few very rare cases, at some point during the convoluted delivery path to the mailbox of the actual human owner of OURLIST, the recipient is changed from OURLIST-owner(a)OUR.DOMAIN to mailman(a)OUR.DOMAIN. ... > Received: from [172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78]) > by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 9E8DE207053B > for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) > > DKIM-Filter: OpenDKIM Filter v2.11.0 SMTP-SERVER.OUR.DOMAIN 9E8DE207053B > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OUR.DOMAIN; > s=unixmail; t=**********; > bh=*******************************************=; > h=Subject:From:To:Date:List-Id:List-Help:List-Owner:List-Subscribe: > List-Unsubscribe:From; > b=***************************************************************** > ****************************************************************** > ****************************************= > > Received: from SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [6.7.8.9]) > by MAILMAN-SERVER.OUR.DOMAIN (Postfix) with ESMTP id B138C1A288F > for <OURLIST-owner(a)lists.OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) The above is where the change occurs. The message is received by Postfix at MAILMAN-SERVER.OUR.DOMAIN for OURLIST-owner(a)lists.OUR.DOMAIN. Then a DKIM signature is added, presumably by `DKIM-Filter: OpenDKIM Filter v2.11.0` working on Postfix queue ID 9E8DE207053B on SMTP-SERVER.OUR.DOMAIN which is the message received from `[172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78])` with destination mailman(a)OUR.DOMAIN. It appears to me that the message is somehow relayed from SMTP-SERVER.OUR.DOMAIN to SMTP-SERVER.OUR.DOMAIN via `(ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78])` and that that's where the change in recipient occurs. -- 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: I don't get my posts with Gmail

by Mark Sapiro

On 10/18/20 5:46 AM, Allan Hansen wrote: > I was pleased to see the advice below on how to get your own list messages sent from a Google client, as my subscribers complain about their messages going AWOL all the time. > Alas, it has the following note at the bottom: > > "I have tested this and while it seems to work, it doesn't. What the filter does is put a copy of the sent message in your inbox as it is sent so it appears that you received the list post, but the message in your inbox is the same message that's in your sent folder. It's not the message received from the list.” > > Do those messages really show up in the spam folder without this filter? (I don’t use Gmail). No, they do not. > If so, then the server is, indeed, sending the message to the mail client, and the mail client is doing the message ID linking locally, discarding the incoming duplicate. > Would a change in mail client solve that? This is a Google thing. It does not depend on the client. I.e., it is the same regardless of whether your client is Gmail's web mail or a Gmail phone app or some other imap or pop3 client accessing gmail. The message is sent from the list server to the recipient's gmail/googlemail MTA and that MTA determines the Message-ID is a dup of one in the sent folder and discards 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: Default values for lists in Mailman 3

by Mark Sapiro

On 9/30/24 02:17, Markus Grandpré wrote: > Dear Mark, dear list, > > in Menu "Mass Operations / Mass Subscription" I have set the default > value for checkbox "Invitation" in file > </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on > Debian 12) as you had suggested: > > > invitation = forms.BooleanField( > label=_('Invitation'), > initial=True, > required=False, > help_text=_( > 'If checked, the other checkboxes are ignored and the users > will ' > 'be sent an invitation to join the list and will be > subscribed ' > 'upon acceptance thereof.' > ), > widget=forms.CheckboxInput(), > ) This is correct. > However, administrators of mailing lists on our Mailman3 demo system > report that the invitation is still sent, even if they have deactivated > the sending of the invitation via the “Invitation” checkbox. If the admin is unchecking the Invitation box but not checking the Pre Verified box, the user will still be sent an address confirmation request. Perhaps the admins are mistaking this for an invitation. It the desire is to immediately subscribe the user with no further interaction, in addition to the Invitation box being unchecked, all three of the Pre confirm, Pre approved and Pre verified boxes must be checked. You may wish to set the Pre Verified default to checked in a manner similar to the above, or with Postorius >=1.3.14 (not yet released) you will be able to add ``` POSTORIUS_DEFAULTS = { 'mass_subscription_pre_verify': True } ``` to your Django settings to accomplish this. -- 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: Server 500 error for just one list, just one page

by Mark Sapiro

On 6/28/20 4:05 PM, kelly.close(a)lrewater.com wrote: > I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). Neither do I, but you want to look in Mailman core's mailman.log and Django's log. mailman.log is in a directory with others including smtp.log and subscribe.log. If you don't know where to find that, look in the output from `mailman conf`. The first thing to look for is [mailman] layout: which will have a value like `fhs`, `dev`, `here` or `local`. then look at [paths.xxx] log_dir: where xxx is the layout value, and if that includes $var_dir, look at [paths.xxx] var_dir: For the Django log look in settings_local.py and settings.py or whatever they're called in your case for LOGGING['handlers']['file']['filename'] > So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… That page should be the same as <https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org…>. Can you go there? Where are you finding that link? What postorius version is this? -- 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: Upgrade Mailmam Core from

by Mark Sapiro

On 9/28/22 23:18, sascha.rissel(a)gmail.com wrote: > > After this, I deleted the venv again and startet anew, again. > But this time, I explicitly did (as Stephen suggested above) >> pip install wheel > prior to >> pip install wheel mailman psycopg2-binary\<2.9 > > This time, it ran through without errors, although "wheel" is also contained in the latter command. > Can you explain that? Apparently, if you run `pip install wheel mailman psycopg2-binary\<2.9` pip attempts to build `lazr.delegates` which is a `mailman` dependency before it fully installs `wheel`. Thus the need to `pip install wheel` first. However, with both `virtualenv 20.0.17/python 3.8.10` and `virtualenv 20.4.2/python 3.9.10` `virtualenv venv` installs `wheel` in site-packages in the venv as does `python3 -m virtualenv venv`, but `python3 -m venv venv` does not. But, at least in my case, with venv built with `python3 -m venv venv` and not containing `wheel` in `site-packages` `pip install wheel mailman psycopg2-binary\<2.9` runs without error. > Second question: > There is still no directory "/etc/mailman3" created, where I can create mailman.cfg in. > Does this maybe result from the fact that in first instance, I tried to install mailman3-full via "apt-get install" and removed it again via "apt-get remove"; with manually deleting /etc/mailman3 afterwards. > > Shall I create /etc/mailman3 manually and adding "mailman" system user permissions? Yes, as the doc says at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, "After this, create a configuration file at /etc/mailman3/mailman.cfg for Mailman Core:" -- 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: Moderation Action Changed After Import

by Mark Sapiro

> > I can't confirm what was set on the old MM2 list as it is no longer > accessible. I am just going on the word of the List Owner. My opinion is > that the moderation for those list members were set to Reject on the > previous MM2 list. I am mainly interested to see if you know of this > happening to anyone else and/or perhaps there is an existing bug that > could impact the moderation settings of imported MM2 lists. If you have the config.pck and any MM 2.1 installation, you can get all the info from the config.pck. For example > /path/tp/mm2.1/bin/dumpdb /path/to/config.pck|grep member_moderation_action will show the setting with 0 = Hold, 1 = Reject and 2= Discard. Finding which members are moderated is more difficult as there is a dictionary named user_options with keys = to email addresses and integer values and the integer is a bit field defined as follows (from Defaults.py) > # Bitfield for user options. See DEFAULT_NEW_MEMBER_OPTIONS above to set > # defaults for all new lists. > Digests = 0 # handled by other mechanism, doesn't need a flag. > DisableDelivery = 1 # Obsolete; use set/getDeliveryStatus() > DontReceiveOwnPosts = 2 # Non-digesters only > AcknowledgePosts = 4 > DisableMime = 8 # Digesters only > ConcealSubscription = 16 > SuppressPasswordReminder = 32 > ReceiveNonmatchingTopics = 64 > Moderate = 128 > DontReceiveDuplicates = 256 However, to address your concern, As far as I know, import21 is doing the right thing. If you want to send me the config.pck you imported, I can try to verify that. -- 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: REST API authorization failed

by Mark Sapiro

On 1/9/22 5:57 AM, Axel Rau wrote: >> >> Does the `mailman info` command report what you think for REST credentials? > yes. ... > I used curl: > - - - > (mailman_33) [root@lists5 /usr/local/mailman3]# curl -v -u restadmin:??? http://localhost:8001/3.1/lists > * Trying 127.0.0.1:8001... > * Connected to localhost (91.216.35.42) port 8001 (#0) > * Server auth using Basic with user 'restadmin' >> GET /3.1/lists HTTP/1.1 >> Host: localhost:8001 >> Authorization: Basic cmVzdGFkbWluOnc2cmtuQXpJZmVRc1o4WnlkMFpBcmNjcm55OA== >> User-Agent: curl/7.80.0 >> Accept: */* >> > * Mark bundle as not supporting multiuse > < HTTP/1.1 401 Unauthorized > < Server: gunicorn > < Date: Sun, 09 Jan 2022 13:51:43 GMT > < Connection: close > * Authentication problem. Ignoring this. > < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" > < content-type: application/json > < vary: Accept > < content-length: 77 > < > * Closing connection 0 > {"title": "401 Unauthorized", "description": "REST API authorization failed“} > - - - > I see "Server: gunicorn“, does this mean, I must install gunicorn? As you later reported, gunicorn is installed. It is installed as a dependency of Mailman core to serve as the REST server which is what's going on here. It also may or may not be used as the wsgi server for Django depending on how you configured that, but this is independent. Anyway, the above is saying that restadmin:??? doesn't match what's configured in Mailman core and reported by `mailman info`. Please check carefully that these are the same in both mailman.cfg admin_pass and settings MAILMAN_REST_API_PASS. -- 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: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/10/2018 02:18 AM, Henrik Rasmussen wrote: > I have set up Postfix to DKIM sign outgoing mails from GNU Mailman 3.2.0a1 which validates nicely ("dkim=pass (signature was verified)"), but DMARC fails ("dmarc=fail action=none") on the recipient end, probably because the "header.from=gmail.com;" (or similar) which means that DKIM d= will not match. Right. DMARC deals with the From: domain. For DMARC to pass, either a valid DKIM sig or SPF with domain 'aligned' with the From: domain must be true. I.e., your DKIM sig and/or SPF won't do if the From: domain is not your domain. > According to dmarc.org*) "Mailing lists usually do not take authorship of the emails they relay" so I should "consider to apply specific rules for emails coming from mailing lists". Also according to dmarc.org*) Mailman (Mailman 2 that is, and I presume Mailman 3 does too) "include features to interoperate with DMARC senders". > > I assume that the dmarc mitigations list settings in Mailman is for incoming messages, but how do I set Mailman to cope with this on outgoing messages? I'm not sure I understand what you are saying. Mailman's (both 2 and 3) DMARC mitigations allow modifying the outgoing message in some or all cases so the From: domain is the list's domain so the message won't be dealt with by the recipient MTA according to the original From: domain's DMARC policy. See <https://wiki.list.org/DEV/DMARC>. Also, <https://wiki.list.org/x/17891458> may be of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Importing Mailman 2 Lists apart from Django

by Mark Sapiro

On 4/30/20 7:59 AM, Brian Carpenter wrote: > Hello Mailman Users, > > Are there instructions on importing a Mailman 2 list into a Mailman 3 > core installation only? Does the import21 script not need > Django/Postorius/Hyperkitty? import21 requires only Mailman core. > It seems Django is required to import archives I guess because of the > use of Hyperkitty. How about importing archives without having a Django > installation? Is that what the prototype archiver for? The only current archive import we support is `django-admin hyperkitty_import` which imports archive .mbox files into HyperKitty. The prototype archiver is just a maildir format collection of messages. Converting an mbox file to a maildir is trivial. from mailbox import Maildir, mbox mb = mbox('/path/to/mbox', create=False) md = Maildir('/path/to/maildir', create=True) for msg in mb: md.add(msg) > We are getting ready to start working on a custom forum application for > Mailman 3 (called Empathy) and I am would like to import some mailman 2 > archives into the development server to work with. First you have to decide how Empathy will store messages. Look at <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. This is how HyperKitty gets messages from a mbox and adds them to its database. It's actually fairly simple - a lot of the code is handling exceptions due to defective messages. Presumably Empathy will have a method for adding a message to the archive, so importing is just getting messages from the mbox and using Empathy's method to add 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, 3 months

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/10/21 10:22 AM, David Newman wrote: > > 1. At least on my system, the proxy_pass statement will only run without > errors if I change this to a fully formed URL, e.g., 'proxy_pass > http://127.0.0.1:8000'. Is this a typo in the docs? I changed it at https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… but I wonder if we shouldn't be using `uwsgi_pass` instead of proxy_pass. See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass Are you using uwsgi or some other wsgi server. > 2. What document root(s) and alias(es) to use for Postorius and > Hyperkitty and the Django admin on a server that also runs other > services (e.g., Postfix for non-list mail and Roundcubemail)? If you can separate Mailman from other services by subdomain, you can configure them separately and for Mailman, root is irrelevant as everything is proxied or aliased in a location directive. For example, Mailman on the server that supports this list uses the lists.mailman3.org domain and we have (excerpted) ``` server { listen 443 default_server; root /usr/share/nginx/html; index index.html index.htm; # root and index are probably irrelevant as we never go there server_name lists.mailman3.org; ssl on; #ssl stuff location / { proxy_pass http://127.0.0.1:8000/; # other proxy stuff } location /static/ { alias /var/spool/mailman-web/static/; } location /robots.txt { alias /usr/share/nginx/html/robots.txt; } location /favicon.ico { alias /var/www/listorg/images/favicon.ico; } } ``` And for the other stuff we have ``` server { listen 443; server_name .list.org mirror.list.org mirror.mailman3.org; root /var/www/listorg; ssl on; # ssl stuff } -- 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: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/26/22 00:11, Stephan Krinetzki wrote: > > After we enabled the "slow query log", we got in the postgresql database the following output: > > 2022-01-25 12:49:41.538 CET [16126] LOG: unexpected EOF on client connection with an open transaction > 2022-01-25 15:34:36.047 CET [16864] LOG: duration: 30760.028 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > 2022-01-25 15:34:36.047 CET [3900] LOG: duration: 9372.471 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > 2022-01-25 16:42:07.243 CET [3900] LOG: unexpected EOF on client connection with an open transaction > > Pretty sounds like a database problem? The unexpected EOF is because the gunicorn worker timed out and was killed. There are two `DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX` transactions because the first one timed out. These came from https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… The `accept` action is processed and ultimately we get to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… and that in turn is doing the DELETE at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.… There must be some kind of database locking causing this, but I have no clue as to what it might be. If you haven't done so, I would stop all the mailman services and the database server and then start them again. I don't know if that would help, but it might. > sometimes the log (mailmansuite.log) show us this error That too is from the gunicorn worker timing out and being killed. -- 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: unique key violation because of case sensitivity of email address

by Mark Sapiro

On 6/15/24 11:47, Jörg Schulz wrote: > After updating to the most recent version of mailman-web, the migrations > script issued an error: > > > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > mailman-web | Running migrations: > mailman-web | Traceback (most recent call last): > mailman-web | File > "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line > 89, in _execute > mailman-web | return self.cursor.execute(sql, params) > mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > mailman-web | psycopg2.errors.UniqueViolation: duplicate key value > violates unique constraint > "account_emailaddress_user_id_email_987c8728_uniq" > mailman-web | DETAIL: Key (user_id, email)=(27, > John.Doe(a)mynicedomain.de) already exists. > mailman-web |(...) Presumably you upgraded django-allauth to a version >=0.62. Beginnin then, email addresses were no longer stored case-sensitively and the migration was dealing with that. There were other issues when addresses were store case sensitively. See https://github.com/pennersr/django-allauth/issues/3019 > Digging into the db, I found the duplicate to result from a duplicate > entry using john.doe(a)mynicedomain.de > > > Obviously, the process that originally created the entry, took case > sensitivity literally which doesn't seem to be the case any longer for > the migration script. > > I fixed this by removing one of the duplicates hoping no further errors > will come up.... > > > What would have been the better approach? Removing one of the duplicates is the solution, and beginning with django-allauth>=0.62, duplicates should no longer occur. -- 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: Single-Sign-out for List member

by Mark Sapiro

On 8/13/20 7:45 PM, Stephen J. Turnbull wrote: > > That said, I have some ideas for how to make this safe for corporate > Germany, specifically, keep a database of user-specific OTKs. (These > could be time-limited -- with the server returning a "use a more > recent message's URL message -- or permanent.) For the usera/userb > reasons Mark gives, and the preview-url reason you give, this is > *still* not going to be safe for discussion lists. But if the From: > is <noreply(a)DeutscheKompany.co.de>, so you have to shoulder surf and > have a photographic memory to get the user's unsubscribe URL, it > should be reasonably secure for announce lists and newsletters. I have experience with a one way email newsletter from Constant Contact. These have a link to unsubscribe and also a link to forward the email to someone else. We ultimately added our own ``` If you want to forward this email, please press the Constant Contact "Forward this email" link below. If you use your "forward" button, you might be unsubscribed. ``` note just above those links because people were forwarding the mail and getting unsubscribed when the person they forwarded it to clicked the unsubscribe link. The real pain is once a user is unsubscribed in this way, the mailing manager can't add her back. She has to personally deal with Constant Contact do get them to remove her from their "do not mail this address" list. FWIW, our note seems to help reduce if not eliminate 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: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:22 AM, Torge Riedel wrote: > > I like to ask what to do with other packages when upgrading mailman. I > noted, that after upgrading mailman, all requirements are fulfilled, but > a lot updates are available: > > (venv) mailman@basis2:~/core$ pip3 list --outdated > Package Version Latest Type > ------------------- ------- ------ ----- > aiosmtpd 1.2 1.2.2 sdist > alembic 1.4.2 1.4.3 wheel > atpublic 1.0 2.1.1 sdist > dkimpy 1.0.4 1.0.5 sdist > dnspython 1.16.0 2.0.0 wheel > flufl.i18n 2.0.2 3.1.3 sdist > flufl.lock 3.2 5.0.3 sdist > idna 2.9 2.10 wheel > importlib-metadata 1.6.1 2.0.0 wheel > importlib-resources 2.0.1 3.3.0 wheel > passlib 1.7.2 1.7.4 wheel > PyMySQL 0.9.3 0.10.1 wheel > requests 2.23.0 2.25.0 wheel > SQLAlchemy 1.3.17 1.3.20 wheel > urllib3 1.25.9 1.26.2 wheel > zipp 3.1.0 3.4.0 wheel > zope.component 4.6.1 4.6.2 wheel > zope.event 4.4 4.5.0 wheel > zope.interface 5.1.0 5.2.0 wheel > > Should I update them (regularly) or may I break something in mailman? In some cases and at some times, Mailman itself specifies a version <= something for a dependency. There have been issues where an upgraded dependency is not compatible with current Mailman. You can look at the install_requires section of setup.py to see if there are any specific version requirements, but this is not fool proof. For example, flufl.lock 5.0 broke Mailman core (See https://gitlab.com/mailman/mailman/-/issues/754) This was fixed in core version 3.3.2. Thus, If Mailman is working with the set of installed dependencies that you have and all of them satisfy >= requirements in setup.py, it's probably safest to leave them as is. -- 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: Change digest frequency and default threshold

by Mark Sapiro

On 10/12/2018 03:46 AM, Henrik Rasmussen wrote: > > As of /opt/mailman/core/var/queue/digest/ and /opt/mailman/core/var/queue/shunt/ no, but there is three files in /opt/mailman/core/var/queue/bad/ > > -rw-rw---- 1 root root 398 Oct 10 14:42 1539175326.8246331+4b7e80db0d22f01c2d4363e323320fcd34560657.psv > -rw-rw---- 1 root root 398 Oct 11 12:11 1539252672.3947155+ae2631d9f6514d74c77a38f09f821ee71515f9d9.psv > -rw-rw---- 1 root root 398 Oct 11 12:24 1539253469.5928977+15b0842462ddd3abcac8d688e5bbb195b07409bc.psv > > They seems to be binary, ... They are Python pickles. The fact that they are owned by 'root' probably means 'mailman digest' was run as 'root'. it should be run as 'mailman'. The files are preserved 'unparseable' queue files - probably unparseable because they can't be read because of the permissions error. You can view them with 'mailman qfile'. I expect this will show an 'empty' message and metadata containing in this case listid: 'test.lists.example.com' digest_path: '/opt/mailman/var/lists/test.lists.example.com/digest.1.9.mmdf' volume: 1 digest_number: 9 and a few other things like version and _parsemsg This is the 'digest' queue entry that tells DigestRunner to produce digests from the file in digest_path. > It seem to say PermissionError: [Errno 13] Permission denied, but inside the container, the directoried in /opt/mailman/var/queue is The permissions error is possibly on these files: -rw-rw---- 1 100 nogroup 103433 Oct 10 14:36 digest.1.7.mmdf -rw-rw---- 1 100 nogroup 155540 Oct 11 11:29 digest.1.8.mmdf -rw-rw---- 1 100 nogroup 104002 Oct 11 12:21 digest.1.9.mmdf or on the digest queue entries and it is because 'mailman digests' is not being run as 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

6 years, 9 months

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/3/20 8:13 PM, Samir Faci wrote: > > Postfix Failed Logs. > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > May 4 03:07:36 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:36 lists postfix/smtpd[1968155]: 745B31473C6: > client=unknown[198.199.98.177] > May 4 03:07:36 lists postfix/cleanup[1968158]: 745B31473C6: > message-id=<158856165549.136760.840427238489827082@lists> > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: > from=<booh-bounces(a)lists.domain.org So mailman and Postfix are on different machines. That may complicate things, but > <mailto:booh-bounces@lists.domain.org>>, size=5474, nrcpt=1 (queue active) > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > May 4 03:07:36 lists postfix/lmtp[1968159]: 745B31473C6: > to=<booh-owner(a)lists.domain.org <mailto:booh-owner@lists.domain.org>>, > relay=lists.domain.org <http://lists.domain.org>[198.199.98.177]:8024, > delay=0.03, delays=0/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) This was a successful delivery. > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: removed > May 4 03:07:38 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from > unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com > <mailto:csgeek@domain.com>>: Relay access denied; > from=<booh-bounces+csgeek=domain.com(a)lists.domain.org > <mailto:domain.com@lists.domain.org>> to=<csgeek(a)domain.com > <mailto:csgeek@domain.com>> proto=ESMTP helo=<[127.0.1.1]> You are sending from a remote machine 198.199.98.177 to a presumably remote domain domain.com so relay access is denied as it should be. You need to add 198.199.98.177 to mynetworks in Postfix. -- 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: Updating from Ubuntu-20.04 LTE installation

by Mark Sapiro

On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > running MM 3.2.2 (and python 3.8.2). > > Do you have any advise, how to upgrade from there to your current > version? I know this might be a bit dangerous, but with today's VMs the > risk is much less than it used to be: It shouldn't be difficult, but I can't give you details because I don't know exactly how the Debian/Ubuntu package installs things. Also I don't know whether "current version" refers to the 3.3.1 release or the head of the https://gitlab.com/mailman/mailman master branch. > Do you think it would be possible, just to replace the code and library > parts, keeping the database and config files as is? Yes. It should be fairly straightforward. You first need to find where the Mailman Core package is. You should be able to just replace the contents of the `mailman` package directory with ours. You may be able to do this via pip pip install --upgrade mailman globally or within Mailman's virtualenv if it is installed in a virtualenv. However, there are caveats. There are Debian patches at <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` patch replaces importlib_resources with importlib.resources because importlib_resources is not available in Debian. Most of the patches apply to tests, and for the actual working code, we fixed this differently as of Mailman 3.3.1, so I don't think you need the Debian patches. -- 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: Adding members to a mailman3 mailing list

by Mark Sapiro

On 10/15/20 2:07 AM, Onyeibo Oku wrote: > > In the meantime, I moved to option #3 (recommended for production). > I hit a grey area when setting up the virtual environment. At > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, > I see: > > $ cd /opt/mailman > $ python3 -m venv venv > > The documentation imply that a 'user' creates the virtual environment > but is not explicit about that 'user'. The user can be any user you want. I use `mailman` on my production installations and `mark` on my development installation. The key is that user should be set as owner of /opt/mailman and then creating the venv and subsequent steps are all done as that user. > (1) Is it better to have a dedicated user (say 'mailman') then use that > while following the docs? I see a lot of docs referring to a 'mailman' > user. Installing mailman3 from distribution repository introduced a > 'mailman' user to my box (with special UID). There has to be reasons > for that. Yes, a dedicated Mailman user is best. > (2) Should the setup proceed with 'root'? (why do I get the feeling > that this is not the design?) No. setup should proceed as the Mailman user. > (3) How about using an already existing local user? What are the > implications? That's OK, but there are potential security implications due to the fact that the Mailman processes running as that user have access to all that user's non-mailman stuff. -- 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: Moderation -- implicit destination behavior

by Mark Sapiro

On 5/21/25 9:31 AM, Steve Bachinsky wrote: > Hi. We have noticed some posts being held for moderation (even though user has permission to post to list) and Mailman reports: > > moderation_reasons: ['Message has implicit destination’] > > The lists are configured for “require_explicit_destination”. However, the email address of the list is clearly in the CC: header of the email (no alias or subdomain). Is there some other reason why Mailman would hold an email for moderation with the reason of “implicit destination”? No. The rule looks at all the addresses in To:, Cc:, Resent-To: and Resent-Cc: headers using standard Python email library methods, lower cases them any if any lc address matches the list posting address or an acceptable_alias, the rule misses, i.e. doesn't hold the message. There is no other reason. > This moderation is not consistent for same list and poster. The emails come from a large domain with multiple load-balancing email servers. I suspect that it may be something with one or more of the servers being misconfigured, but unable to see anything obvious from the headers and confused why Mailman states the reason to be implicit destination when that does not seem to be the cause. I'm sorry, but I have no idea why this is happening. If the headers of the held message contain the explicit address, I have no clue as to why it is held for that reason. Maybe there is some other reason why the message is held, and the reason is misstated, but I don't know how that could happen. -- 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: Subscribing via email

by Mark Sapiro

On 04/19/2016 11:31 AM, Andrew Hodgson wrote: > Hi, > > I subscribed to this list the other day via email, and I didn't get any email back suggesting I was subscribed. I logged in today via Google accounts, and it said I was subscribed to the list, but all the options for receiving list traffic, my own posts etc weren't filled in - I had to fill them in manually. 1 - You should have received a list welcome message and a 'results of your email commands' message in response to your email subscribe request. I'm Ccing you directly as it appears you can't get any list mail[1]. Visit <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> to see the aechives. 2 - The non-filling in of your options is a known issue. See <https://gitlab.com/mailman/mailman/issues/187>. Basically, you get 'default' settings, but they aren't explicitly set for your subscription by the Mailman core. [1] Here's a log message: Apr 6 23:42:22 mailman postfix/smtp[6809]: A9C9B800D9: to=<andrew(a)hodgsonfamily.org>, relay=hodgsonfamily-org.mail.protection.outlook.com[213.199.154.23]:25, delay=5.5, delays=0.05/0.05/0.29/5.1, dsn=5.7.606, status=bounced (host hodgsonfamily-org.mail.protection.outlook.com[213.199.154.23] said: 550 5.7.606 Access denied, banned sending IP [104.239.228.201]. To request removal from this list please visit https://sender.office.com/ and follow the directions. For more information please go to http://go.microsoft.com/fwlink/?LinkID=526653 (AS16012609) (in reply to RCPT TO command)) I have just now gone to https://sender.office.com/ and gone through the delisting process with this result: "Your IP 104.239.228.201 was successfully delisted. This may take up to 30 minutes to take effect." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: Upgrading packages

by Mark Sapiro

On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > All packages were upgraded fine. I applied the patch to > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py It shouldn't have been necessary to apply any patch. The head of the GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > to change the mistune import line. When I run now > mailman-web migrate > I get: > *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration > graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* > *To fix them run 'python manage.py makemigrations --merge'* > > However, when I run the suggested command as: > $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- > merge > No conflicts detected to merge. There's something strange here. If you look at the migrations at the head of the gitlab branch at https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/migrations, you'll see that migration 17 is named 0017_alter_emailtemplate_language.py, not 0017_auto_20220628_1132. I suggest comparing the content of your postorius/migrations/ directory with the GitLab head and resolving any differences. > Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my > production system. Would be nice to shed some light on this. I'm guessing at some point you installed something which required you to manually make this migration and that produced this conflict. Do you have both 0017_alter_emailtemplate_language.py and 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, probably just removing 0017_auto_20220628_1132 will fix this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

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

by Mark Sapiro

On 6/21/20 9:38 AM, Ruth Ivimey-Cook wrote: > > > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 (it obviously recognises that > as the , and so cannot be connected to by anything. That is why I set it > to 0.0.0.0 to begin with, and what the documentation implies (fairly > strongly) that this parameter is about. What documentation? I do understand what you are saying and I see the issue. I don't understand why it works for this poster <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> but maybe that's specific to Docker containers. > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed hosts to get the right connectivity, too. Try something like this and let us know if it works? If so, we can do something like add a config setting for this. > --- a/src/mailman/rest/gunicorn.py > +++ b/src/mailman/rest/gunicorn.py > @@ -53,7 +53,7 @@ def make_gunicorn_server(): > # We load some options from config.webservice, while other extended options > # for gunicorn can be defined in configuration: section. We also load up > # some logging options since gunicorn sets up it's own loggers. > - host = config.webservice.hostname > + host = '0.0.0.0' > port = int(config.webservice.port) > log_path = os.path.join(config.LOG_DIR, config.logging.http['path']) > options = { -- 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: Mails are stuck in Mailman Pipeline Queue

by Mark Sapiro

On 3/26/22 10:28, Shashikanth Komandoor wrote: > Hi Team, > > We have restarted the services as well but no change. Odd. > We tried manually moving the pck file from pipeline queue to > out queue but the file disappeared from out queue but is not getting > delivered. This is expected because if the message hasn't been processed through the pipeline, it has no recipients in the metadata, so the outgoing runner delivered it to no one. Also, it skipped archiving and digesting. > We moved the pck file from pipeline queue to out queue with the > extension .bak still no use. Same as above. > Not sure what to try next. Please help. Mi first guess is the pipeline runner isn't running, but you restarted the services, presumably Mailman core, and that might fix it, but there are various ways the pipeline runner could have died that would cause the master to not restart it. You need to stop Mailman core and then start it rather than just restarting. That may help. Also look in mailman.log. Assuming the pipeline runner died at some point, there should be a log entry and possible an exception with traceback indicating why. You can see which runners are running with something like ``` ps -fwwA|grep runner=|sed s/.*runner=// ``` This should produce a list something like ``` archive:0:1 bounces:0:1 command:0:1 in:0:1 lmtp:0:1 nntp:0:1 out:0:1 pipeline:0:1 rest:0:1 retry:0:1 task:0:1 virgin:0:1 digest:0:1 rest:0:1 rest:0:1 ``` except depending on version, `task` may not be 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, 4 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 11:00, Jered Floyd wrote: > > These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! For me, on a test installation with SITE_ID = 0, this only occurs at https://example.com/accounts/social/connections/ Other URLs such as https://example.com/accounts/password/change/ and https://example.com/accounts/email/ do not throw this exception. Here's the code: ``` def get_current(self, request=None): """ Return the current Site based on the SITE_ID in the project's settings. If SITE_ID isn't defined, return the site with domain matching request.get_host(). The ``Site`` object is cached the first time it's retrieved from the database. """ from django.conf import settings if getattr(settings, "SITE_ID", ""): site_id = settings.SITE_ID return self._get_site_by_id(site_id) elif request: return self._get_site_by_request(request) raise ImproperlyConfigured( 'You\'re using the Django "sites framework" without having ' "set the SITE_ID setting. Create a site in your database and " "set the SITE_ID setting or pass a request to " "Site.objects.get_current() to fix this error." ) ``` I tried patching it from ``` if getattr(settings, "SITE_ID", ""): ``` to ``` if getattr(settings, "SITE_ID", None) is not None: ``` but that's even worse. It throws a bunch of "django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist." errors. Somehow, get_current is being called without a request object in the cases where it fails. -- 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 rewrite the Cc header incorrectly

by Mark Sapiro

On 5/24/20 7:20 PM, Alan So wrote: > Really thanks for your hard work Mark! It is a bit strange that parseaddr behave differently with CRLF and LF. Maybe if the server is a Windows, the behavior is consistent. It might be that on Windows, `mailman inject` would create the message with CRLF line endings. > May I know when or whether will this patch be committed to the repository so that it will be effective in future release of Mailman? Thanks. In the absence of an issue at <https://gitlab.com/mailman/mailman/-/issues>, probably never. <hint> The bottom line is the original mail created by Outlook is defective.[1] While Mailman could defend against this defect, starting to do that opens the possibility that there are other areas of the code that need a similar defense. Have you asked Microsoft to fix Outlook to not create these defective messages? That's the real solution. That said, if an issue is filed, someone might consider adding something along the lines of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> to the code base. [1] given an address of the form display-name (comment) <addr-spec> in a header, it can be folded either between the display-name and the (comment) or between the (comment) and the <addr-spec>, but if display-name (comment) is quoted as in "display-name (comment)" <addr-spec> "display-name (comment)" is now a phrase within which folding is not allowed and this can only be folded between the "display-name (comment)" and the <addr-spec>. -- 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: Change language to welcome message in mailman3

by Mark Sapiro

On 7/24/20 2:10 PM, Massimo Zappalà wrote: > Hi everyone, > > My Version installed on Debian buster: > mailman3: 3.2.1 > postorius: 1.2.4 > hyperkitty: 1.2.2 > > All interfaces work well in Italian language, but "Welcome message" is in English. First question: Is the Subject: in English or Italian? If the Subject: is in English you need to compile the Italian message catalog as I described in my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Then, as far as the message body is concerned, it is built from a template. At present, in the Mailman source distribution, the only templates that are translated are French and German You will find the complete set of English templates at /usr/lib/python3/dist-packages/mailman/templates/en/. You have choices. 1) You can create /usr/lib/python3/dist-packages/mailman/templates/it/ and make Italian translations of all the English templates in the it/ directory in files of the same names, and submit a merge request at <https://gitlab.com/mailman/mailman/-/merge_requests> to merge them into the source distribution. If you are not familiar with software development in general and Mailman development in particular, this is probably beyond what you can do. 2) Find Mailman's var/ directory. This is the directory containing archives/, data/, etc/, lists/, locks/, logs/ and perhaps other sub-directories. You then need to create the full path to var/templates/site/it/ and place Italian translations of some or all the templates there. When doing so, you can add site customizations. 3) You can use Postorius to create templates for individual lists. -- 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: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/24/20 7:22 PM, Abhilash Raj wrote: > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). It's more complicated than that. Sometimes the fragment name is the heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor #3.3.3 work at all as these are #id2 and #id1 respectively. Currently the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but when a Command line section is added under 3.3.3, that will probably get the command-line id. Thus, the note "Permalink to this headline" es misleading at best because it isn't very permanent fo an evolving document. > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. I too think this is correct. I suppose it might be worth doing for NEWS.rst in particular since Sphinx doesn't seem to like fragments like n.n.n. Another way to deal with this would be to always use code names. It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` -- 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: what process creates webui tables (mailmanweb db)?

by Mark Sapiro

On 9/26/22 09:14, tflatley(a)gmail.com wrote: > hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate Probably not. First of all, `mailman-web migrate` will only affect the mailmanweb database, not the mailman database, migrations for which are run implicitly when Mailman core is started. Also, migrations will only affect tables for which there are migrations, not all tables. > this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file > > python3 manage.py migrate Yes. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. The above message saying you need to make migrations because of changes to models indicates that your Debian/Ubuntu package is broken as the packager should have created all necessary migrations. > i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? I am confused as to why you are trying to run an out of date and possibly broken Debian/Ubuntu package when it appears you have successfully installed the latest PyPI packages in a venv. -- 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: Place holders

by Mark Sapiro

On 5/27/25 23:23, Mark wrote: > Hi, > > The place holders listed as available on the "Add new template" page are: > > $hyperkitty_url > $listname > $list_id: > $display_name > $short_listname: > $domain > $info > $request_email > $owner_email > $site_email > $language What Postorius version is this? You may be missing some things added in 1.3.11. A more complete list including the ones that only work in certain contexts is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… a pointer to which was added in 1.3.11. > The only one that seems to sort of work on my template is $list_id - > which displays as "testlist". (I was expecting to see > "testlist(a)example.com"). $listname should be replaced with the fqdn list name like "testlist(a)example.com" and $short_listname should be replaced with the list name without the @domain as in "testlist". The others should all work as documented. I don't know why they wouldn't. Can you give an example of a template that doesn't get these substituted. > The others just get displayed as a variable. Eg. $owner_email > > Have I missed a setting somewhere? The actual substitution is done by the Python `string` library module Template class, safe_substitute method. See the doc at https://docs.python.org/3/library/string.html#template-strings Note that because we use the safe_substitute method, invalid substitutions don't produce errors, they just aren't substituted. In particular if `$identifier` is followed immediately by a letter, digit or underscore, `identifier` must be wrapped in `{}` to separate it from the following characters, e.g., `${identifier}x`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[MM3-users] Re: Deleting A List

by Mark Sapiro

On 5/3/24 03:59, Odhiambo Washington wrote: > On Thu, May 2, 2024 at 8:11 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/2/24 03:42, Odhiambo Washington wrote: >>> I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. >>> I can see from Django Admin UI that the archives are still intact. >>> I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke >>> Is there a way to move the archives from the old list to the new list? >> >> >> Change the `name` and `list_id` in the list's entry in the >> `hyperkitty_mailinglist` table in the database. If there is already an >> entry there for the new list, delete it >> >> > ``` > mysql> select id, name, list_id from hyperkitty_mailinglist; > +----+----------------------------+----------------------------+ > | id | name | list_id | > +----+----------------------------+----------------------------+ > | 1 | skunkworks(a)lists.my.co.ke | skunkworks.lists.my.co.ke | > | 2 | list(a)nog.ke | list.nog.ke | > | 3 | eanog(a)lists.my.co.ke | eanog.lists.my.co.ke | > | 4 | isoc(a)lists.my.co.ke | isoc.lists.my.co.ke | > | 5 | kazi(a)lists.my.co.ke | kazi.lists.my.co.ke | > | 6 | kenog(a)lists.my.co.ke | kenog.lists.my.co.ke | > | 7 | mechanics(a)lists.my.co.ke | mechanics.lists.my.co.ke | > | 8 | science(a)lists.my.co.ke | science.lists.my.co.ke | > | 9 | security(a)lists.my.co.ke | security.lists.my.co.ke | > | 10 | vmware_tech(a)lists.my.co.ke | vmware_tech.lists.my.co.ke | > | 11 | water(a)lists.my.co.ke | water.lists.my.co.ke | > | 12 | wordpress(a)lists.my.co.ke | wordpress.lists.my.co.ke | > | 13 | list(a)lists.nog.ke | list.lists.nog.ke | > +----+----------------------------+----------------------------+ > 13 rows in set (0.00 sec) > > mysql> delete from hyperkitty_mailinglist where id = 13; > ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key > constraint fails (`mailmansuite`.`hyperkitty_mailinglist_owners`, > CONSTRAINT `hyperkitty_mailingli_mailinglist_id_a47e04ec_fk_hyperkitt` > FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperkitty_mailinglist` (`id`)) > ``` > > Is there an easier way? > I need to delete id=13 then rename id=2 > There are several tables that reference the hyperkitty_mailinglist table by id. These are hyperkitty_email, hyperkitty_mailinglist_owners, hyperkitty_mailinglist_moderators and hyperkitty_thread. Ideally, you wouldn't have created the list(a)lists.nog.ke before updating the hyperkitty_mailinglist entry, but now, do the following: ``` update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_owners set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = 13; delete from hyperkitty_mailinglist where id = 13; update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = 'list.lists.nog.ke' where id = 2; ``` If there have been no posts to the list(a)lists.nog.ke list the updates of hyperkitty_email and hyperkitty_thread won't do anything, and likewise the update of hyperkitty_mailinglist_moderators if the list has no moderators -- 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: Mailman REST API not available. Please start Mailman Core.

by Mark Sapiro

On 7/23/20 12:38 AM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > I understood that gunicorn is a front end that is used like web server like > nginx. > > But I don't think I am using it instead I am using the httpd to redirect > requests to postorius. Steve has addressed this. > So, in this case, do you think configuring gunicorn as below would work: You do need to configure gunicorn timeout to solve your issue. > *calling gunicorn.cfg in mailman.cfg as below * > > *[webservice]* > *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* Do NOT do this. Make your own gunicorn.cfg outside of /var/lib/mailman/mailman/src/mailman/ and point to that. Otherwise any upgrade will reverse your changes. > > *and content of gunicorn.cfg as below* > > (venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg > [gunicorn] > # All the options that can be put here are available at > # http://docs.gunicorn.org/en/stable/settings.html#settings > # No of seconds to wait before killing the worker processes. > > workers = 4 > graceful_timeout = 90 > > Also what is the difference between timeout and graceful_timeout ? graceful_timeout is not what you want. It addresses something different. As it says in the comment, all the gunicorn settings are described at <http://docs.gunicorn.org/en/stable/settings.html#settings>. timeout and graceful_timeout are near the bottom of that page at <https://docs.gunicorn.org/en/stable/settings.html#timeout> and <https://docs.gunicorn.org/en/stable/settings.html#graceful-timeout>. -- 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: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 9:24 PM, Alan So wrote: > Just FYI. > > I omitted the "<" and ">" when I replace the real testing address with name(a)example.com. > > It should be, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> Actually, you didn't omit them. It's just the way HyperKitty renders what it thinks is an email address that makes it appear they aren't there. If you download the thread from HyperKitty, you'll see they are there. Anyway I am unable to duplicate your issue with your example data. I sent this raw message ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Cc: abc def (ghi) <abc(a)example.com> "abc def (ghi)" <def(a)example.com> Subject: test Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 Hi ``` and the message I received from the list included these headers ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 CC: "abc def (ghi)" <abc(a)example.com>, "abc def (ghi)" <def(a)example.com> Subject: [List] test ``` I do observe something similar to what you report that has nothing to do with folding. If I omit the trailing ">" in an address as in ``` From: Mark <mark(a)msapiro.net ``` the address becomes ``` From: "Mark <mark"@msapiro.net ``` So possibly your issue involves missing angle brackets. In order to say more, I'd need to see the actual headers as sent and received or at least an accurate munged representation. -- 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: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 4:19 PM, Ken Alker wrote: > > What else is stored in /var/messages, if not archives? I see 4711 > messages in that directory (which I presume would be as many messages > are in the archive database). If there is a write-up on this, feel free > to point me to it. I found > <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode…> but this isn't really answering my question. These are probably artifacts from your old Debian package. There have been issues in the past with handled messages not being removed from the message store. See https://gitlab.com/mailman/mailman/-/issues/257 This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes orphaned messages from the message store, but if they are still referenced in pendings they won't be deleted. > I didn't think so, but I'll certainly buy that. So, I'm assuming by > this you are implying that there is no helper function that needed to > run and the number of held messages should have dropped to zero > immediately upon a refresh of the web page? Correct, assuming your changes were committed. > So if I run the script, exist the shell, then come back in again, I > can't rely on the request.id being the same? I'd need to re-run the > script and get a new request.id? No. The request id for a given held message won't change. -- 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: HyperKitty/Mailman3 issues

by Mark Sapiro

On 11/22/18 2:58 AM, Florian Schulze wrote: > Hi! > > I tried setting up Scheduled Tasks as described in > <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> > > but the "runjobs" command can't be found. I see the hyperkitty and > mailman commands when using "help". Does "help" show a list under [django_extensions] including runjob and runjobs? Is 'django-extensions' in the list of INSTALLED_APPS in your Django settings? > The "qcluster" service is working. > > Using Django 2.1.1 and HyperKitty 1.2.1. > > Maybe related to that, I have two issues with archives. > > 1. Changing the archiving setting in the Web-UI to something else than > public seems to have no effect. The already archived messages are still > accessible in public. This is related. It is one of the "daily" jobs that updates this. Note that changing to "private" will require login after the "daily" jobs run, but changing to "do not archive" will leave the existing archive accessible. > 2. Related to 1., how can I remove a list archive without affecting > other lists? There's no easy way. For the "prototype" archiver, the archives for a list are in var/archives/prototype/listname(a)example.com/ and that directory can be removed, but that doesn't affect HyperKitty. HyperKitty's archives are in the Mailman database and multiple tables are involved. One could try just removing the row for the list from the hyperkitty_mailinglist table. That may render the list's archive inaccessible via the web UI, but I have no idea what would be broken by doing this. -- 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: Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

On 7/26/19 6:20 AM, Robert Lister wrote: > > The change from Mailman2.x to Mailman3 means it's now using LMTP to > deliver to mailman instead of a local submission seems to have exposed > this issue. It is not the use of LMTP for delivery that is the issue. It is the fact that Mailman 3 uses a hash of the Message-ID: in various contexts to identify/retrieve a message. Thus, every message must have a Message-ID. See <https://gitlab.com/mailman/mailman/issues/490> for more on this. ... > My solution for now (apart from telling people not to use old broken > Outlook!) is to modify the exim mailman3_transport so that any message > with a missing Message-ID: will have one generated by exim before it's > passed to LMTP. This reproduces the same behaviour exim uses for locally > submitted messages. > > (headers_remove ensures that we end up only with one Message-ID: header > and not two, then we put back either the original Message-ID, or if > that's not there, use Exim's ID to generate a new Message-ID header.) > > Here's an updated version of the example at: > https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim ... > mailman3_transport: > driver = smtp > protocol = lmtp > allow_localhost > hosts = localhost > port = MM3_LMTP_PORT > rcpt_include_affixes = true > headers_remove = message-id > headers_add = "Message-ID: ${if def:header_message-id:{$h_message-id:}{<E${message_exim_id}@${qualify_domain}>}}" Thank you for this. I have created <https://gitlab.com/mailman/mailman/merge_requests/540> to add this to the doc. -- 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: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > Yes, the same problem. > I created the file __init__.py in /opt/mailman/mm > However, when I run using the wsgi.py I ended up (still do!) with the error: > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > application='mm3-lists.server.name|/mm3'): Loading Python script file > '/opt/mailman/mm/wsgi.py'. What is the contend of the file /opt/mailman/mm/wsgi.py? You previously posted the setting of WSGIDaemonProcess in your Apache config as: > WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman3 \ > group=mailman3 python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 \ > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var Is it still that? ... > 197.232.81.246:64709] mod_wsgi (pid=79132): Exception occurred processing > WSGI script '/opt/mailman/mm/wsgi.py'. > [Wed Jul 29 10:08:51.872754 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] Traceback (most recent call last): > [Wed Jul 29 10:08:51.872827 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File "/opt/mailman/mm/wsgi.py", line 38, in <module> > [Wed Jul 29 10:08:51.872835 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] application = get_wsgi_application() > [Wed Jul 29 10:08:51.872847 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/wsgi.py", > line 12, in get_wsgi_application ... > [Wed Jul 29 10:08:51.872984 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] ModuleNotFoundError: No module named '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

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

by Mark Sapiro

On 11/25/21 10:56 AM, David Newman wrote: > > Thanks for this. After setting these variables and restarting mailman3 > and mailmanweb, the mailman user still cannot find a hyperkitty_import > command (neither can root, btw). Again, I installed MM3 and > Django/Postorius/Hyperkitty using the venv and web docs previously > referenced. Don't run mailman or django admin commands as root. This causes issues when files are created by root and can't be read by mailman. What django admin command are you running? If you don't set DJANGO_SETTINGS_MODULE in the environment and you have activated your virtualenv and run `mailman-web` as the django admin command it will set /etc/mailman3/settings.py as the settings. > On the plus side, all lists now appear in the admin web page. However, > lists created from the admin page do not appear in a site list page, > even though all lists are in the same site/domain. By default, only lists that you are owner, moderator or subscriber for are shown. What if you click Filter by Role and select All? > Finally, how to make these exports permanent? I did not see this covered > in the migration doc above. This is on a Debian system where the mailman > user's shell is bash. Is this simply a matter of adding environment > variables in the mailman user's .bashrc file? You can do that but as I note above, if you run `mailman-web` you shouldn't need to. You can add a `source /opt/mailman/venv/bin/activate` command as mentioned at https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtua…. -- 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: digest summary heavily cluttered with hrml code

by Mark Sapiro

On 10/15/20 11:13 AM, Mohsen Masoudfar wrote: > Hi Mark, > > Thanks again for your help! > > Yes, I meant "Today's Topic". The "Today's Topics" list is a plain text listing of the Subject: and sender of the messages in the digest. It is identical in both the plain text and MIME format digests. In what way is it cluttered with HTML. Please post an example. > I checked the link you sent, but could not see the solution to the issue. If the issue is HTML in the `Today's Topics:` list, then it is not <https://gitlab.com/mailman/mailman/-/issues/473>. If the HTML is in the messages themselves, then it is <https://gitlab.com/mailman/mailman/-/issues/473>, and that is currently not fixed and the workaround is to set Delivery mode to MIME digests. > You mentioned: > " They are in order of priority, list based, address based and global" > > Is this in descending or ascending priority? If I set it at list level, does it overwrite the member setting (address based?? )? It's descending order, I.e. list overrides address overrides global. > I set them along with "Delivery mode" at the member level and saved it, but when I get back to it, it still shows "Regular" and other fields like: > acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings > are empty, even though I set them and saved. What Postorius version is this? Is this user a member with more than one role - e.g. more than one of member, nonmember, owner or moderator. -- 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: mail stuck in "out" queue

by Mark Sapiro

On 6/9/20 7:24 AM, Kareem Zidane wrote: > We're facing a similar symptom where emails to a particular list won't go out and seem to be stuck in the out queue. We also noticed that mailman is hitting /hyperkitty/api/mailman/urls infinitely. I've attached some of strace's output. Any idea what might be the problem? > > Process 17171 attached > ioctl(20, FIONBIO, [0]) = 0 > sendto(20, "\272\10\0\0\3SELECT anon_1.member_id AS "..., 2238, 0, NULL, 0) = 2238 > ioctl(20, FIONBIO, [0]) = 0 > recvfrom(20, "\1\0\0\1\f5\0\0\2\3def\0\6anon_1\0\20anon_1_me"..., 8192, 0, NULL, NULL) = 937 > ioctl(20, FIONBIO, [0]) = 0 > ioctl(20, FIONBIO, [0]) = 0 > ioctl(20, FIONBIO, [0]) = 0 > ioctl(20, FIONBIO, [0]) = 0 ... There is way too much noise in that strace for me to find anything useful without having more of a clue as to what I'm looking for. And what process is 17171? As far as messages stuck in `out`, is Mailman's out runner running? for example, $ ps -fwwA|grep [r]unner=out mailman 6318 6272 0 Jun08 ? 00:03:28 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=out:0:1 Look in Mailman's mailman.log for messages mentioning `out runner` and for any error messages. As for `mailman is hitting /hyperkitty/api/mailman/urls infinitely` look for messages in mailman.log mentioning this. Are there messages queued in /opt/mailman/var/archives/hyperkitty/spool? if so, these are messages that failed archiving, probably because of an incorrect value for `base_url` in mailman-hyperkitty.cfg or a mismatch between `api_key` in mailman-hyperkitty.cfg and MAILMAN_ARCHIVER_KEY 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

5 years, 1 month

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

On 8/5/22 09:17, summersan(a)nclack.k12.or.us wrote: > > My Questions: > > Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? > > Should there normally be other detectors listed in the logs beyond the `DSN` one? > > If so, is there a setting I can change somewhere to make this happen? Prior to flufl-bounce 4.0, it would run all detectors on every message to the -bounces address. Beginning with 4.0, it runs the detectors in a defined order from most specific/authoritative to least. If you are seeing only or mostly the `DSN` one, you have 4.0 and the `DSN` detector recognizes a RFC 3464 compliant bounce. > For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Probably the upgrade also upgraded flufl.bounce to 4.0. So the real question is why are you seeing large numbers of bounces. Since it appears they are recognized by `DSN`, they probably aren't spam to the -bounces address. Do you have verp probes enabled (verp_probes = yes in the mta section of mailman.cfg)? If so, it's possible that you are getting bounces for spam and the like, but the probes don't bounce so the user's delivery is never disabled. -- 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: Invalid confirm text

by Mark Sapiro

On 8/17/20 4:53 AM, w.schoener(a)alp.dillingen.de wrote: > One thing I forgot to mention: > a week ago, the confirmation-mails still worked. > > And now: > All attempts to confirm the subscribe message failed. I used the list-request(a)list.domain and sent text-only message with the "confirm token" in the subject and/or in the body. This should work. What's in your MTA's logs? > So today I tried and used the Mailman shell to change the pending state to "confirmed", as you described here: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > After I submitted the command util.confirm('hex_token') and restarted mailman with > mailman stop > mailman start It isn't necessary to stop/star/ or restart mailman. How did you exit mailman shell. You must exit with ctrl-D or issue commit() or your transactions won't be committed. In particular, if you exit with exit() without first issuing commit(), nothing will be done. > the pending user wasnt confirmed but cleared, as if he never sent a subscribe-message. The only way to subscribe seems to be by logging in and using there the subscribe-form. What is the list's subscription_policy? It seems you successfully confirmed that token, but that may not be the last step if the list's subscription_policy is confirm_then_moderate. > Do you have any idea, whats going wrong here? I dont know what to do any more. Clearly something is broken, but I don't know what unless it is some permissions issue on the template directories/files you created. Have you looked at Mailman's mailman.log? -- 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: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 11:14 AM, Jens Günther wrote: > Just checked again and saw: > > - in the setup it works perfectly in Hyperkitty, that's nice > > - for the first web host I have 2 mail domains registered, so it also > matches (unfortunately) with what you said :-( > > Anyway, I dceleted one of it, still both lists are shown on either web > host, so it's generally not working. I don't know why this didn't work. If there is only one mail host in the domains that has the current web host as its web host, it should work. > If I can do something on this issue, please advise me. Thanks. The issue is that neither Postorius or HyperKitty as a direct way of getting lists by web host as the web host information is not an attribute of the list. We have to see which mail hosts are associated with the current web host and then display only those lists that match one of those mail hosts. The issue with Postorius is if there was more than one mail host associated with the web host, this code https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… could be relatively easily made to work by extending all_lists to include all the mail hosts, but it wasn't clear to me how to fix https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… in the case where there was more than one mail host. If you can suggest a fix, that would help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: template head/footer questions.

by Mark Sapiro

On 4/8/22 11:04, bob B via Mailman-users wrote: > I migrated from mailman 2 to mailman3 and had head/footer questions. > > In the mailman 3 GUI see the templates section, so where do those files get edited/stored? in the postorius_emailtemplate table in the database. > I added a footer to a list via the GUI, but I do not see it in: > /var/templates/lists/[listNAME]/en Because when you set a template in Postorius it makes an entry in the template table in the database with a URI pointing to its own API to retrieve the template. > I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. > > Bottom line, > > I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? That's up to you. The default search path for templates in the absence of a template table entry (or even with one with a mailman:/// URI) includes the var/templates/lists/list_id directory. is this directory leftover from migrating from mailman 2 to 3? No I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option. Again, it's up to you. If you have Postorius and want list admins to be able to create, modify, break, etc. templates without involving you, then Postorius is a good option, but it isn't in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Lookup Table Questions

by Mark Sapiro

On 12/7/21 4:09 PM, Peter Williams wrote: > > - The Mailman documentation notes that either hash or regexp tables are > supported. Is it ok to use LMDB or will I run into issues at some point? Mailman only supports hash and regexp tables for automatic maintenance of the tables as lists are created and removed. If you use LMDB tables you will need to maintain them yourself. The `mailman aliases` command won't do it. > - If LMDB tables are not a good idea to use, are there any drawbacks to > switching over to regexp tables? My main concern is that we currently have > 7000+ mailing lists, and I'm worried that switching over to regexp may > result in slower lookups. I am also wondering if there are potential issues > if the 'mailman aliases' command is run simultaneously alongside another > 'mailman aliases' command. In the past it seems like the hash table was > locked (which was good), and I'm not sure if this behavior is kept by > moving over to regexp. This may be more of a Postfix question and I > apologize in advance if I am asking the wrong mailing list for this. The locking is done in mailman/mta/postfix.py regardless of table type. I.e. it's the same for hash and regexp table updates. I wonder why you are manually running `mailman aliases`. This really shouldn't be necessary as the files are regenerated automatically as lists are created and removed. As far as performance of regexp vs hash tables, I have no idea. That's really a Postfix question. -- 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: Digests not working correctly

by Mark Sapiro

On 6/8/24 12:48 PM, Steve Brown wrote: > I'm a list administrator for a list hosted by mailmanlists.net on a server in Germany. Only one member uses the digest option, but she doesn't receive a digest until the Digest size threshold has been exceeded. (I also am subscribed as a member with the Mime Digest option and see the same behavior.) The option for Send Digest Periodically is checked but doesn't trigger a daily digest on the days that there is some activity if the aggregate size doesn't exceed the threshold. I think "periodically" means daily, and the administrator doesn't seem to have any way of checking or changing the periodicity. The hosting service has attempted several fixes, including fiddling with the cron settings, but hasn't found something that works. They even upgraded to ver. 3.3.9 recently, and that didn't fix the problem. Periodic digests are sent by the `mailman digests --periodic` command which should be run daily by cron. That and the `mailman notify` command should be run from mailman's crontab. See https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-cron-jobs I don't know what "fiddling with the cron settings" means, but if these commands are in mailman's crontab, including ``` MAILTO=some_human(a)example.com ``` at the beginning of the crontab will ensure any diagnostic output is sent to some_human(a)example.com where it will be seen. Also, putting ``` LANG=en_US.UTF-8 ``` near the beginning of the crontab may be required in some cases. See the Attention notice at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/insta… -- 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: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. Mailman 3 consists of several pieces. There is a core engine which is Python 3. The core does the basic email list management and exposes many options and settings via a RESTful API. There is also mailman.client which provides Python bindings for the REST API. This is Python 2. We also provide a web management UI, Postorius and an archiver, HyperKitty. These are Django applications and all of this is Python 2. There are other pieces as well. > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler. This is only the core. You can install it with python3 setup.py install either in a python 3 virtualenv or not, but this will only give you the core. I suggest you see the docs at <http://docs.list.org/en/latest/>, and if you don't want to use bundler, see <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the recommended way to set up a working, non-development Mailman suite. In short, the core requires Python 3.4, most of the rest of the suite requires Python 2.7 because of dependencies not yet ported to Python 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: Bounces

by David Krantz

Thank you for the tip. In the end I changed mailman/runners/bounce.py instead by moving the maybe_forward line so that it is always run. Smaller change (just removing one indention level) and preserves the handling. Might break something else, but I do not think so. diff --git a/src/mailman/runners/bounce.py b/src/mailman/runners/bounce.py index 57b259f..e772765 100644 --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -86,6 +86,6 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False Cheers // David On Sun, Nov 5, 2017 at 10:39 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/05/2017 01:29 PM, Mark Sapiro wrote: >> >> The bottom line is we aren't doing anything with bounces other than >> storing them. We need to fix that, and we will (It's targeted for 3.2). >> If you could help with code, that would be great. > > > As an interim work around, if you wanted to send ALL bounces to the list > owner instead of what little we currently do, at about line 65 in > mailman/runners/rest.py, you'll see > > SUBADDRESS_NAMES = dict( > admin='bounces', > bounces='bounces', > confirm='confirm', > ... > > If you change the > > bounces='bounces', > > line to > > bounces='owner', > > that will cause all bounces to be just sent to the list owner(s). > > -- > 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/

7 years, 8 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 5:43 PM, Ralph Seichter wrote: > With archiving enabled, mail is sent with headers like the following: > > Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> > List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> > List-Post: <mailto:foo-users@lists.example.com> > List-Subscribe: <mailto:foo-users-join@lists.example.com> > > The 'mailto:' entries are fine, but I need all 'https:' links to be > prefixed with https://lists.example.com instead of https://example.com . > > Does Mailman extract CN parts from the SSL certificate to populate the > header values (that would explain 'example.com' in my tests), or is this > something I can influence using configuration parameters? I searched the > docs for Mailman Suite and HyperKitty, but did not find an answer. It has nothing to do with the ssl certificate. It comes from _get_url in hyperkitty/views/mailman.py > def _get_url(mlist_fqdn, msg_id=None): > # We can't use HttpRequest.build_absolute_uri() because the mailman API may > # be accessed via localhost. > # https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.Htt… > # https://docs.djangoproject.com/en/dev/ref/contrib/sites/#getting-the-curren… > # result = urljoin(public_url, urlunquote( > # reverse('hk_list_overview', args=[mlist_fqdn]))) > # We use the MailDomain association from django_mailman3 to find out the > # proper domain. What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/ Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:02 AM, Marc SCHAEFER wrote: > > I have a few questions: > > 1) persistence: as I can regenerate the configuration files (mailman, > mailman-web, hyperkitty), is all what's useful in the DB, or are some > things in /var/lib/mailman3 worth saving? > > obviously messages to be moderated, hyperkitty failed messages, > etc are stored there, but shall I assume that all mailing-lists > configuration, all users configuration and all archives are > in the DB? I don't know the details of where the Debian package puts things, but there may be Postfix related files in /var/lib/mailman3/data, but yes, all mailing-lists configuration, all users configuration and all HyperKitty archives are in the DB? > 2) I imported a list and all messages get a footer of: > %(web_page_url)slistinfo/%(_internal_name)s > which I guess changed between MM2 and MM3; however when I > look at that list configuration in the web interface of MM3, > I see no templates defined, nor any clue where this is > configured: where may I change this? import21 creates these templates in (I think in your case) /var/lib/mailman3/templates. > 3) is there a configuration somewhere that can allow someone to > create a mailman web account ONLY if he is already referenced > somewhere in a mailing-list, and not otherwise? (or to > create accounts that need approvals from an admin > before being usable?) No. > also, can a non-yet-referenced e-mail From: still subscribe to > a private list (confirm+moderate) via e-mail regardless of > the above? Yes -- 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: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 7:45 AM, robert.kydd(a)gmail.com wrote: > Hi Mark, thanks for this. I was away and only got back now. > It's great to get rid of the reason text. > Is there any way I can find out what is i18n message catalog. It would be nice to give a more pleasing message to the users I am still not clear on what Mailman version you are using. If it is Mailman 3, i18n translations for Mailman core are still a work in progress, and I can't tell you how to do this. For Mailman 2.1, you will find within Mailman's file system, a messages/ directory with several 'language code' subdirectories, but not 'en'. You need to create messages/en/ and messages/en/LC_MESSAGES/ and then create the file messages/en/LC_MESSAGES/mailman.po with contents like: ---------------------------------------------------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR ORGANIZATION # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: Sun Jun 17 12:22:07 2018\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: ENCODING\n" "Generated-By: pygettext.py 1.4\n" #: Mailman/Handlers/Hold.py:61 msgid "Post by non-member to a members-only list" msgstr "WHAT YOU WANT TO REPLACE IT WITH" ---------------------------------------------------------- with the various UPPERCASE things replaced appropriately and then 'compile' it via > msgfmt -o messages/en/LC_MESSAGES/mailman.mo messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Mirroring a mailman3 server

by Mark Sapiro

On 1/16/22 9:09 AM, Axel Rau wrote: > > What else must be synced (by rsync)? Aside from the database, there are multiple directories containing Mailman mutable data. Where these directories are depends on Mailman's layout configuration. For all layouts except `fhs` they are all in a single directory, but for `fhs` they are split. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/mailman… Depending on exactly what's going on between the two servers, you need to decide what needs to be synced. For example, you probably don't want to sync .pid files or or the locks directory. You probably should sync archives/, cache/, data/, etc/, lists/, messages/, templates/, public_suffix_list.dat and the search engine's (Whoosh, Xapian, whatever) index files. Syncing Mailman's queue files is problematic. They are very dynamic and it isn't practical to rsync them. The same is true to a lesser extent with messages/ > While creating a domain, what should I enter into the fields? > > Mail Host lists.framail.de (currently lists5.lrau.net) Mail Host is the FQDN of the host's email address. > Alias Domain listsl.framail.de Alias Domain is a special case to handle situations where Mail Host is a Postfix virtual domain rather than a local destination. It is normally None (not set), and if requires would never be the same as Mail Host. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > Web Host lists.framail.de (currently lists5.lrau.net) Web Host is the host name of the web web server, i.e., the host in the URL that accesses the web UI -- 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: List of "site admin" commands in Mailman 3.1 docker-mailman

by Mark Sapiro

On 07/17/2017 07:55 AM, Henrik Rasmussen wrote: > > On another note: Is it a setting in the mailman-users(a)mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."? I suspect this is something in the MTA/MDA chain between the lists.mailman3.org server and you. I suspect that something in that path doesn't like the fact that your original message's DKIM signature has been broken by such things as subject prefixing and addition of the list's msg_footer. When your message reaches my server at msapiro.net, it sees > Authentication-Results: sbh16.songbird.com; > dkim=pass (1024-bit key; unprotected) header.d=mailman3.org header.i=(a)mailman3.org header.b=QBeM9elY; > dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=alumni.onmicrosoft.com header.i=(a)alumni.onmicrosoft.com header.b=GeTpYnXK; > dkim-atps=neutral I.e., the list's DKIM sig is valid but your original sig is not, even though it was valid when received by the list > Authentication-Results: mail.mailman3.org; dkim=pass > reason="1024-bit key; unprotected key" > header.d=alumni.onmicrosoft.com header.i=(a)alumni.onmicrosoft.com > header.b=GeTpYnXK; dkim-atps=neutral If my suspicion is correct, you should be seeing the same thing with other people's posts such as this reply and your posts to other lists. If you don't then my suspicion about DKIM is not the reason and it is something else or the conditions are more complex. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Bounce handling after upgrade

by Mark Sapiro

On 7/8/20 6:05 AM, David Krantz wrote: > > To my surprise mailman core started by sending tens of mails and > blocking the corresponding users for very old bounces. What is worse > is that this happens every time I start mailman core. Now I have > blocked (almost) all outgoing mail in postfix using a transport map > which discards it but this is a temporary testing measure of course. Sorry about that. Yes this is an issue when first upgrading from a prior version to 3.3.1, there are lots of old unprocessed bounce events which all of a sudden get processed. See below for solutions. > When I deploy this server into production, I do not want these > recipients to be blocked as the old problems have been solved since > very long. My plan is to reload the database from a newer backup > anyway... Would it be enough to empty the bounce table (bounceevent) > or is there anything else driving this behaviour? Or is there a better > way to do this via the mailman shell? For me a "delete from > bounceevent" seems a lot simpler than anything via the shell but there > may be dependencies in the database. You are on the right track. The "delete from bounceevent" is a perfectly acceptable solution. So is "update bounceevent set processed = true". Another way to deal with this is to set [mta] verp_probes: yes in mailman.cfg. This will still send a lot of probe messages which may be undesirable, but if the probes don't bounce, the user's delivery won't be disabled. -- 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: Hyperkitty not receaving messages / empty archive [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/urls

by Mark Sapiro

On 1/21/25 05:44, Helge Baumgart wrote: > Hyperkitty-Api-Key in the docker-compose.yml is set via .env Variabel, > so it should be identical. I don't know how this works in the Docker image, but ... > Traceback (most recent call last): > File > "/usr/lib/python3.11/site-packages/django/core/handlers/exception.py", > line 56, in inner > response = get_response(request) > File > "/usr/lib/python3.11/site-packages/django/core/handlers/base.py", line > 197, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File "/usr/lib/python3.11/site-packages/hyperkitty/views/mailman.py", > line 109, in _decorator > not hmac.compare_digest( > > Exception Type: TypeError at /hyperkitty/api/mailman/urls > Exception Value: unsupported operand types(s) or combination of types: > 'str' and 'NoneType' The above code is doing auth = authorization.split() if (len(auth) != 2 or auth[0] != 'Token' or not hmac.compare_digest( auth[1], settings.MAILMAN_ARCHIVER_KEY)): and the exception says either auth[0] is None or auth[1] or settings.MAILMAN_ARCHIVER_KEY is None. But > META: ... > HTTP_AUTHORIZATION = 'Token (value)' and > Settings: > Using settings module settings ... > MAILMAN_ARCHIVER_KEY = '********************' So The Authorization header is the appropriate `Token value` which should result in auth[0] being 'Token', auth[1] being the value and MAILMAN_ARCHIVER_KEY is set > That is my docker-compose.yml: ... > mailman-web: ... > - HAYPERKITTY_API_KEY=${MM3_HYPERKITTY_API_KEY} #someapikey_longAndTrustworty I don't really understand why the above typo (HAYPERKITTY_API_KEY, not HYPERKITTY_API_KEY) would cause this error, but it needs to be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Mailman List Lost on URL transfer

by Mark Sapiro

On 09/20/2017 10:28 AM, heartsandbones(a)zoho.com wrote: > > Here’s the scoop: > I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. > > I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. As I have told you in other communications, you need a DNS A record for the mail.sbfriends.org pointing to the IP address of the Mailman server that hosts the list. We have no idea what that IP address is. You will have to ask your client what Mailman hosting service they were using for their sbfriends.org domain. That A record will probably suffice to get to the web UI for the list, but you will probably also need an MX record for the sbfriends.org domain pointing to mail.sbfriends.org for mail delivery to the list. > This is my first post to this forum, so I hope I’ve done so correctly. The correct list for Mailman 2.1 issues (http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org is a Mailman 2.1 URL) is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>. This list is for Mailman 3. However, you won't get a different answer from that list. -- 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: Can login at /admin, but cannot login at the account/login page.

by Mark Sapiro

On 8/14/21 9:34 PM, Stephen J. Turnbull wrote: > I'm sorry, I'm in a "second vaccination" fog at the moment (mending > but concentration lasts only about 10 minutes), so I'll answer what I > know offhand since Abhilash is busy and Mark is probably offline for > vacation by now. Not quite, but very soon. > pabsta(a)gmail.com writes: > > > However, if logout and attempt to login from the postorius website, > > I get a « 502 bad gateway » error after roughly 30 seconds. The > > logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech > > free" error message > > I would guess this is also just a connection drop because it doesn't > receive the expected response within timeout. I'm sure that's right. > > and the nginx error logs just show a connection drop: > > > > 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: > > [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" > a > I see in the above `upstream: "http://127.0.0.1:8006/accounts/login/",` but in your settings ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" I suspect you may be getting a redirect from http to https which is losing POST data and you need to change proxy_pass http://127.0.0.1:8006; in your nginx configuration to proxy_pass https://127.0.0.1:8006; or set ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" -- 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: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 10/2/20 10:49 AM, Alex Schuilenburg via Mailman-users wrote: > > So something in the import has decided that the original message quote > is a header and the To: field has been modified to protect the sender > so has created the email <Firstname Surname@Company-UK> (note the > space). Not only that, it has decided this is a valid email address. > So a bug, filed as https://gitlab.com/mailman/mailman/-/issues/777 > Unfortunately I've been moving the lists over a clutch at a time, and > they are active, so I cannot just drop everything and start over. I can > munge the future .mbox files being imported to remove the quoted email > to stop this happening again, but ideally I also need to find and fix > the errors in the database. I'm very new to mm3, but handy with SQL > (I'm running on mariadb) so suggestions appreciated. There's much more detail in my reply at <https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422894486>, but you can fix the ResponseNotReady() issue from the sync_mailman job by finding the entries in the hyperkitty_sender table with invalid addresses in the address column and deleting them. We can try to address this specific issue in hyperkitty_import, but there are in general various mbox defects that we can't detect. mboxes need to be checked for unescaped `From ` lines in message bodies and other defects before importing them. The Mailman 2.1 bin/cleanarch script and the new hyperkitty/contrib/check_hk_import script can help with some of this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/21/22 16:24, Dan Caballero wrote: > Mark, > > I'm seeing this issue pop up this week with several lists. You previously mentioned two conflicting browsers potentially causing the issue. Can you elaborate? That would only cause a transient issue which would not occur on a subsequent get of the held message view. I gather this is not the case here. I.e. once the error occurs on a get of the held message view, it is persistent. > In addition, is there a way for me to run this cleanup using mailman shell -r "somescript" so that I can check all the lists instead of one by one? For a -r script, try ``` # In non-interactive scripts, we need the explicit imports. from mailman.interfaces.listmanager import IListManager from mailman.interfaces.requests import IListRequests, RequestType from zope.component import getUtility def somescript(): for mlist in getUtility(IListManager): requestdb = IListRequests(mlist) for req in requestdb.held_requests: if req.request_type == RequestType.held_message: if not requestdb.get_request(req.id): print(f'List: {mlist.list_id}, Bad request id: {req.id}, deleting') requestdb.delete_request(req.id) ``` The real question here is what are these spurious requests and how are they occurring. If you do a query like ``` SELECT * FROM _request; ``` Are there entries with empty `data_hash` or entries with an `id` that is not the value of any `pended_id` in the `pendedkeyvalue` table. BTW, I understand why you thought an import was needed in the interactive script in my message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… - the `from mailman.interfaces.` line was a mistake on my part and shouldn't have been there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

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

by Mark Sapiro

On 5/18/22 10:48, dancab(a)caltech.edu wrote: > Mark, > > We have a question related to this thread. We use LDAP for authentication. It seems that the name attributes can only be edited via the LDAP synchronization when a user logs in for the first time and thus creates their user account. > > But what about list members that are not in LDAP? What happens behind the scenes when a member is added to a list? The user's display name is set when the user record is initially created. Assuming someone who is initially unknown, this can happen when the unknown user signs up for a web account, when the unknown user subscribes to a list via the web UI or when the unknown user is mass subscribed to a list. > Manually subscribing members has different results with our configuration. > > I've seen the manually entered name show up as "None" <foobar(a)caltech.edu>. There was a pre-existing user with that address and no display name. > I've seen the entry be accepted as is, eg. "John Doe" <jdoe(a)example.com> > I've seen the name entry be ignored but the email accepted eg. "Foo Bar" <foobar(a)caltech.edu> is subscribed but the member list only shows <foobar(a)caltech.edu> The display name has nothing to do with message acceptance. That is based only on the address. In Postorius >=1.3.6 there is a `Users` selection at the top of most pages if you are logged in as a superuser. This allows management of users including their display name. -- 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: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/15/21 11:31 AM, Kimmo L wrote: > > It seems that we have some perfomance issues on webUI, if we try to check archived messages. > Some lists, that contains low number of archives is not a problem but lists, that contains several thousand messages and grows faster are issue. Sometimes it loads so long, that i get "504 Gateway Time-Out" > I was also monitoring server perfomance and i didnt see any issues on that side. It seems that there might be some issues to read archived messages from database. But this is just my one opinion. > > I also debugged log files and found some error messages: > 1) mailmansuite.log -> django.db.utils.DatabaseError: out of memory for query result > # it happens when i try to open a lists in webui, to check archived messages. > nginx-error.log -> upstream timed out (110: Connection timed out) while reading response header from upstream > # also happens when i try to open list in hyperkitty and it takes long time to open > > If any information is more needed then let me know. My one thought was also, that maybe i need to try rebuild_indexes. Rebuilding indexes will affect only searches. It should have no effect on just opening a list. We have some large imported archives at https://mail.python.org/archives/ e.g. https://mail.python.org/archives/list/mailman-users@python.org/ with over 85,000 messages, and don't see these issues. It definitely looks like your server doesn't have enough memory. You might also run memcached and enable it for Django https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… -- 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: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > we are now getting feedback from people, who say that they are unable to > sign up, with mailman3 telling them: > > Subscription request already pending > > this is somewhat bad as: > > - at least some of the users (who reported the problem) tried to > subscribe 2 months ago (2022-01-04) - if they did not confirm their > email back then, i'm pretty sure that this email has been lost by now > - my /etc/mailman3/mailman.cfg has "pending_request_life: 3d" This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman 3.3.5. > - i (as administrator) do not see any "pending subscriptions" (the list > is setup with a simple "Confirm" subscription policy The count badge only counts subscriptions waiting moderator approval. If you pull down the Subscription requests tab and click Pending Confirmation you should see them and be able to discard them. > i wonder: > - why are the pending subscriptions not expired? (i guess they should > have expired after 3 days) It's a bug fixed in Mailman core 3.3.5 > - why can't people re-subscribe while there's a subscription pending > (e.g. if the confirmation mail got lost)? Because that's the way it was implemented. > - how can i list all pending subscriptions (for a given mailinglist)? Pull down the Subscription requests tab and click Pending Confirmation. > - how can i resolve the situtation (e.g. send out another reminder; > manually expire the pendings; manually confirm the pendings,...) If the above doesn't answer that. provide more detail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: How to add new Domain?

by Mark Sapiro

On 2/4/25 15:59, c.benner--- via Mailman-users wrote: > > After that I'll go to the admin page xxxx/mailman3/admin which brings django admin page up. > On that page I'll add "websites" and add testdomain2.net That tells Django that this is a known domain for accessing the web UI, but you also have to add it to the ALLOWED_HOSTS setting in your Django settings. > Last step is adding "mail domain" site: testdomain2.net mail domain: testdomain2.net > > After that I can add lists to that domain and mails to any list @testdomain2,net should be routed right? That's all correct. > Maybe I'm to old (56yrs) but I've read a lot of documentation and everything was clear and understandable. It was never a question of linux or windows OS but on who'S writing the doc. I can't find any doc about the web part? What about Users having no acces to the shell but the Web-Frontend? Some pictures and a "How to" and "what if" would be great! > > But it's alos possible that I'm not finding it and it's somewhere out there. You may find https://docs.djangoproject.com/en/5.1/ref/contrib/sites/to be helpful. Documentation of the Postorius UI is sorely lacking. The good news (hopefully) is the UI itself is fairly straight forward and self-documenting, but there is really no separate documentation for list owners or site admins. There is a user's manual for list members at https://docs.mailman3.org/en/latest/userguide.html but nothing similar for list admins. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 4 weeks

[MM3-users] Re: Dealing with confirmation requests for unsubscribes

by Mark Sapiro

On 11/18/20 7:41 AM, Brian Carpenter wrote: > Hello List, > > I ran into the following issue for some mailman 3 lists that I am hosting: > > https://gitlab.com/mailman/mailman/-/issues/768 > > Since there is no way for a list owner to deal with a moderation request > for an unsubscription task, I assume I need to do something via the > command line. This is where I need some help with. How do I deal with > these moderation requests that are unable to be reviewed in an admin gui > (Postorius/Affinity)? mailman 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 test.msapiro.net mailing list This >>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', token_owner=TokenOwner.moderator)) will return something like [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', 'list_id': 'list.example.com', 'email': 'user(a)example.com', 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': 'moderator'})] What you want is the token, in this case 'a8df55f557b5718505280d2613937e25a3109252' Then do >>> ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') which will return (None, <TokenOwner.no_one: 0>, None) and finally: >>> commit() > I do recommend removing such choices for Postorius for Member policy. I > will be doing this for Affinity until issue 768 is resolved. The correct thing to do is fix <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly will do that rather than remove the moderate and confirm then moderate unsubscription policies. -- 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: not correct language in subject(s)

by Mark Sapiro

On 5/24/23 14:36, Jens Günther wrote: > > - Shall I create all the mo-files (the other folders also only contain > the po)? If so, how would it be possible? > - How can I make it persistent? (probably it should be included in the > repo!? also another thread or an issue regarding maxxking's repo!?) We probably should distribute .mo files too, although currently they are explicitly excluded. I'll see if we have a good reason for not distributing them. > Exactly. What I was wondering: for the welcome-messages I did not have > explicit templates for those lists/domains/site that I wrote in German, > it has to be from the predefined templates, which are stored elsewhere > the in the mo-files!? (actually I don't get this point exactly but > wouldn't bother, if the above works). The templates are actually included in the mailman.po files so that they can be translated all in one place on weblate. However they are not retrieved from there. There are templates for some but not all supported languages in the mailman/templates/ directory in the installation and these are used by default, but these are not up to date in all cases with those in the mailman.po files. That should be fixed as well. In my case, for the servers I maintain, I update from the heads of the gitlab branches whenever there are significant changes and part of that process compiles the .mo files and updates the templates with scripts at https://gitlab.com/mailman/mailman/-/blob/master/generate_mo.sh and https://gitlab.com/mailman/mailman/-/blob/master/update_lang_templates.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Connection lost during _handle_client()

by Mark Sapiro

On 11/28/24 9:17 AM, Alain D D Williams wrote: > > /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are > being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck > The process doing this is a 'qrunner' The .bak file is the one currently being processed by the `out` runner. The others are waiting to be sent. I don't know why they are continually being dequeued and requeued I suggest you stop Mailman core and then examine these files with `mailman qfile` to see if there is some issue with one or more of them, but this seems unlikely. More likely is some issue with the `out` runner itself, but I have no idea what that would be except that issues like this can be caused by files in Mailman's var/templates/ directory that aren't readable by the Mailman user (often caused by running `mailman import21` as root). > I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log > > [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) This looks like some kind of DOS attack. Look at the GET requests in the web server log. > /var/lib/mailman3/queue/shunt/ contains 4 .pck files. For each of these, there should be an entry in mailman.log indicating the exception with a traceback. Look for entries in the log ending with a `SHUNTING` message. -- 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: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu > sends an email to a list, Mailman gets the email, processes it and would try to send that email to all members with a sender field as: 'joe.student(a)university.edu'. plus listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. This format vs. plain text digests was a user option in Mailman 2. > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius. If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool. > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

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

by Mark Sapiro

On 3/10/21 6:37 AM, Duane Raymond wrote: > Hi Mark, > > I think I have it working thanks to some hints in your questions. here is the process I took in case others experience it the same or in case anyone wishes to comment! > > When I use the mailman shell comment it seems to reflect just what you posted (I also tried test.campaigningforum.com and got the same result): > (venv) mailman@mail:/opt/mailman/mm$ mailman shell -l test(a)campaigningforum.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 test(a)campaigningforum.com mailing list > >>> > > Was there something beyond running this and getting the output I was supposed to enter? Was an error expected if one members doesn't have an associated address record? Did you enter this following the initial >>> prompt? >>> for mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... If so, it was expected to print the representation of the user object and that objects addresses list fo any member whose address attribute is None. ... > This time the posting was archived and I did get an acknowledgement of the post, but despite having the option "Receive own postings" set to "yes", I didn't receive it. As you have determined, this is a googlemail issue. See <https://wiki.list.org/x/4030680>. -- 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: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://gitlab.com/mailman/mailman/-/issues/385 which was fixed in Mailman 3.2.0 by https://gitlab.com/mailman/mailman/-/merge_requests/333. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- 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: Bug in 2.1.36?

by Mark Sapiro

On 11/12/21 1:06 PM, Joel Lord wrote: > I'm not sure if this is a bug or something about the new CSRF fix > doesn't get along with something I have (mis)configured, but this > definitely seems to be related. Sadly the script I use to backup > mailman before upgrading I recently stopped backing up the lists > themselves, so going back to 2.1.35 doesn't seem to be an option due to > the .pck file version bump. Here's the trace I get: > > Traceback (most recent call last): > File "/mailman/mailman-${domainslug}/scripts/driver", line 117, in > run_main > main() > File "/mailman/mailman-${domainslug}/Mailman/Cgi/admindb.py", line > 342, in main > print doc.Format() > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 352, in Format > output.append(Container.Format(self, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 267, in Format > output.append(HTMLFormatObject(item, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 53, > in HTMLFormatObject > return item.Format(indent) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 445, in Format > % csrf_token(self.mlist, self.contexts, self.user) > File "/mailman/mailman-${domainslug}/Mailman/CSRFcheck.py", line 53, > in csrf_token > mac = sha_new(secret + `issued`).hexdigest() > TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' > > Running Python 2.7.5 > . Thanks for the report. I think the issue is caused by the fix for https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a list admin is trying to handle moderator requests on a list that has no moderator password. I'll investigate and try to put out another fix later today. -- 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: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/16/23 05:34, Jeremy Stanley wrote: > > Clearly a total misreading on my part of the Django documentation to > which you referred earlier. It talks about having to feed Django > multiple settings.py files with different SITE_ID values and running > migrate to configure them, then links to the document on migrations > which starts out explaining how to use makemigrations to create > them. I took that to mean creating and configuring Django sites from > the command line required supplying customized database migrations. > > The particularly misleading bits are where it says: > > "To set the correct name and domain for your project, you can > use a data migration." > > "In order to serve different sites in production, you’d create a > separate settings file with each SITE_ID" > > It doesn't seem to talk about using django_admin at all (or if it > does, it's not mentioned by name, maybe assuming the reader knows to > use it in order to perform the necessary steps). Yes, that doc really isn't appropriate for your purpose, but it's the only one I could find on Django sites. Most of what it talks about is for more complex situations than ours and whatever bits are relevant are already done in Postorius/HyperKitty. Sorry for leading you astray. > Thanks for the clear examples! If these are available somewhere in > Django's documentation, I did a terrible job of searching for them. I don't think Django's docs address the simple task of adding a site. -- 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: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

On 7/28/20 5:40 AM, Brian Carpenter wrote: > Ok, I see the other thread concerning this was deleted, along with my reply. Here it is again. It wasn't deleted. It's on another list - mailman-users(a)python.org. Here's my reply to your post On 7/27/20 7:13 PM, Brian Carpenter wrote: > > This is the client that I asking about in my post. She said what I did, did not work. This is what I did: > > 1. Get into a venv as user mailman > > 2. #mailman shell >>>> from mailman.model.mailinglist import MailingList >>>> mlist = MailingList('listname(a)listdomain.org') >>>> mlist.emergency = False >>>> commit() > ctrl-d (just to be on the safe side) > > Did I not follow your instructions correctly? That should work. I don't know why the result would be any different from what Johanna did. On 7/27/20 8:58 PM, Johanna Amann wrote: > As a small followup for anyone encountering the same problem in the > future - I ended up just changing the value in the database directly. > > So - an “update mailinglist set emergency = FALSE;” (or the equivalent > in the dialect of the database one uses) removes the emergency flag from > all mailing lists. That is another approach which is valid, but why the `mailman shell` method I suggested wouldn't do the same thing, I don't know. Of course, if you're doing multiple lists, this method is easier because just one simple query does them all. -- 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: equivalent mailman 3 commands from 2.0

by Mark Sapiro

On 10/25/21 9:16 AM, bob B wrote: > For my 2.0 environment, I have scripts to dump list info, but i can't find the equivalent in mailman 3, for some commands, for example I use: > > /usr/lib/mailman/bin/list_lists which equates in mailman3 to "mailman lists" > /usr/lib/mailman/bin/list_members which equates in mailman3 to "mailman members [listname]" > > But I also use > /usr/lib/mailman/bin/list_admins [listname] > /usr/lib/mailman/bin/config_list [listname] > > Are there equivalent command line commands to get this info in mailman3? for list_admins you can use `mailman members --role administrator [listspec]`. See `mailman members --help`. There is no mailman command equivalent to config_list at this time > The mailman3 "mailman withlist [listname]" takes me into an interactive prompt not sure where to go from there. From there you enter Python statements to do what you want. e.g. ``` $ /opt/mailman/mm/bin/mailman withlist -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>>for property in dir(m): ... if not property.startswith('_'): ... print(f'{property}: {m.__getattribute__(property)}') ... ``` You can also create scripts to run with the --run option, See `mailman withlist --details`. > I can use the API > > curl --user [ADMIN]:[password] http://[IP]]/3.1/lists/[listname]/config | python3 -m json.tool > > > But just curious if there is a command line equivalent like in mailman2? Not at this time. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/12/22 22:03, Onyeibo Oku wrote: > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. I would suggest you not do that and just install mailman in `/opt/mailman` per https://docs.mailman3.org/en/latest/install/virtualenv.html. If you don't want to do that, you will have to replace all occurrences of `/opt/mailman` in the doc with `/usr/lib/mailman`. > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? Yes. The suggested change to .bashrc assumes you are logging in as the Mailman user, not switching via `su`. You might try `sudo -u mailman bash` or `sudo -u mailman -i` instead of `su`, but I'm sot sure if that will help. > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" I think if you have `var_dir: /usr/lib/mailman/mm/var` in the /etc/mailman3/mailman.cfg file you create per https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, then starting Mailman core `/usr/lib/mailman/venv/bin/mailman start` will create it. -- 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: 500 error on Held Messages page

by Mark Sapiro

On 3/30/23 07:36, Gregory Edigarov wrote: > I have the same issue now. > that's happen when I try to open held messages > > This is what I have in my logs: > > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in _resource_as_dict > assert resource is not None, resource > AssertionError: None What is the full traceback? > that is the default mailman3 debian package. And your primary support resource should be Debian. > GNU Mailman 3.3.3 (Tom Sawyer) > > things were working smoothly for a very long time. it started after disk array disaster. we installed the thing to another server, and restored the database from backups. > > I've tried to use this magic: > ``` > The variable 'm' is the odoo_leads(a)qarea.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: > ... if not requestdb.get_request(req.id): > ... print(f'Bad request id: {req.id}, deleting') > ... requestdb.delete_request(req.id) > ... >>>> ``` > but no success. > is there any way to fix this? I think you're on the right track with the above `mailman shell`, but evidently the issue is different. You might try ``` >>> requestdb = IListRequests(m) >>> for req in requestdb.of_type(RequestType.held_message): ... if not requestdb.get_request(req.id): ... print(f'Bad request id: {req.id}, deleting') ... requestdb.delete_request(req.id) ... else: ... print(f'Held request: {requestdb.get_request(req.id)} ... >>> ``` To see what the requests look like. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/28/25 01:14, Mark wrote: > > Then I created a template using Postorius and updated the uri in > mailman.templates to: > > file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… - and that works. Which says get the template from the file system at that location and don't ask for it from Postorius at all. This would be the default action if there were no entry for this template in the mailman.template table at all. I.e. you now have a template in Postorius, but it is not used. > It's looking promising. Now I just need to modify my script that > periodically copies the data from the > "mailmanweb.postorius_emailtemplate" table to a file and updates the uri. > > Why it won't handle the templates in the database I don't know. But at > least I can get a work-around solution in place now. If you want to continue to use the template at /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt just delete the template from Postorius and update that file directly. If Postorius template updates don't work because of web server caching or whatever, just don't use them and use templates in the /opt/mailman/mm/var/templates/ hierarchy instead. You can create sitewide templates at /opt/mailman/mm/var/templates/site/en/*, domain specific templates in /opt/mailman/mm/var/templates/domains/en/* and list specific templates in /opt/mailman/mm/var/templates/lists/<list-id>/en/ without any entries in the mailman.template table. Note that sitewide templates can be the most useful and can't be created in Postorius anyway. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/30/2017 02:27 PM, David Krantz wrote: > > I tried to upgrade today. The result is a broken install which fails > when trying to upgrade the database. > > > $> ./bin/mailman-post-update > [...] > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", > line 94, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > django.db.utils.IntegrityError: update or delete on table "auth_user" > violates foreign key constraint > "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on > table "social_auth_usersocialauth" > DETAIL: Key (id)=(3) is still referenced from table > "social_auth_usersocialauth". This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > I have tried to drop and recreate the databases but I get the above > result anyway. I'm not sure what you mean by drop and recreate the databases. You should just drop the `social_auth*` tables, or if there's nothing in the database you want, just starting with an empty database should work. > The description in > https://wiki.list.org/DOC/Mailman%203%20installation%20experience is > very hazy. The process of symlinking in libraries is fiddly to say the > least. I get mailman to start but not any web interface. I have not > tested mailman so if it works rather than just start I do not know. Sorry about that. The symlinking was due to my starting with bundler and then "undoing that" without trying to find everywhere the old paths might be referenced. -- 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: Invalid confirm text

by Mark Sapiro

On 8/14/20 3:28 AM, w.schoener(a)alp.dillingen.de wrote: > > Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: > return the message unchange. > > When I return the message, I get an answer: > Invalid confirm text. With current releases of Mailman, the confirm request you receive should be: From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token> with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678> > My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line confirm <hex-token> as either the Subject or body of the message to <listname>-request@<list.domain>. That should work. Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval. > Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l…> -- 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: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 10:11 AM, Massimo Zappalà wrote: > Hi everyone, > if I write a my lists from other email address I get the correct message: > opendkim[23516]: 8EEE440FFD: DKIM-Signature field added (s=mailselector, d=catania.linux.it). > > While if I write to a my lists from email address Gmail, on opendkim I get the following messages: > opendkim[23516]: BA95241952: no signing table match for 'maszap69(a)gmail.com' > opendkim[23516]: BA95241952: s=20161025 d=gmail.com SSL error:04091068:rsa routines:int_rsa_verify:bad signature > opendkim[23516]: BA95241952: bad signature data OpenDKIM on your server is not signing the message because it is not configured to sign messages From: 'maszap69(a)gmail.com' What's in your opendkim SigningTable and what's in your opendkim.conf for SenderHeaders. The recommend config is SenderHeaders List-Post,Sender,From to use the domain of the list for signing list mail and then to include that domain in SigningTable. > I also receive an email at superuser: > > [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/archive > > 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") > ... This appears to be unrelated. HyperKitty is trying to store the message in the database hyperkitty_email table and gets this error. To say more, I'd need to see the complete raw message which you may be able to find in Mailman's var/archives/prototype/<list_address/new/ and if available, a full traceback and possibly more from the email you receive from Django or from the log file configured 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

4 years, 10 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/31/2018 01:52 PM, Ryan McClung wrote: > That explains a lot. Is there any documentation you can provide to show me > where I can set a static config/db? See <http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html> That may not specifically address your question, but it will explain the issue in detail. An example of what I do on several servers I support is this. First, I install Mailman in a virtualenv which is /opt/mailman/mm/venv. Then the commands I run are all put in /opt/mailman/mm/bin. the actual installed 'mailman' command is /opt/mailman/mm/venv/bin/mailman but I never run that directly or as 'mailman' with the venv active. My var/ directory is /opt/mailman/mm/var. My mailman.cfg is actually outside of the var/ directory in /opt/mailman/mm/mailman.cfg. (In some cases for historical reasons it's in /opt/mailman/mm/deployment/mailman.cfg, but ignore that.) In /opt/mailman/mm/bin/mailman, I have #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ The details such as installing in a venv or where things are are not the important things. The important thing is the only 'mailman' command I ever run invokes Mailman with a -C option that points to the only config I want to use and that in turn has a var_dir setting pointing to, in my case, /opt/mailman/mm/var. Also, the 'unset PYTHONSTARTUP' is there to address an issue with 'mailman shell' that would double the size of the shell history file each time it was run. I'm not certain that's still needed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

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

by Mark Sapiro

On 7/20/20 5:19 PM, Massimo Zappalà wrote: > Hi everyone, > Debian buster run on my server. > I installed the apt install mailman3-full package and configured it. Everything works fine. > I'm trying to change the language (mailman3, postorius and hyperkitty) from English to Italian, but it's not clear what I'm missing. > These are the files that I modified to try to set the Italian language: > > /etc/mailman3/mailman.cfg > default_language: it > --------------------------------------------------------------- > /etc/mailman3/mailman-web.py > LANGUAGE_CODE = 'it-IT' > TIME_ZONE = 'Europe/Rome' > USE_I18N = True > USE_L10N = True > USE_TZ = True > --------------------------------------------------------------- Assuming this is the Debian packages Django settings file for mailman, it probably contains something like try: from settings_local import * except ImportError: pass at the end. You should put your local changes in the /etc/mailman3/settings_local.py file. > /usr/lib/python3/dist-packages/django/conf/global_settings.py > TIME_ZONE = 'Europe/Rome' > USE_TZ = True > LANGUAGE_CODE = 'it-IT' > --------------------------------------------------------------- This probably isn't needed as it should be overridden by the above. > With this command, I set the Italian language to the list. It takes the setting, but it doesn't work > sudo mailman shell -l test(a)pratico.work >>>> m.preferred_language='it' >>>> commit() >>>> CTRL-D > > Can anyone tell me what I'm missing? The source distribution for Mailman core does not contain the compiled message catalogs, and Debian's package probably doesn't either. Find the mailman/messages/it/LC_MESSAGES directory, cd to that directory and give the command msgfmt mailman.po -o mailman.mo -- 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: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

On 7/26/19 11:05 AM, Stephen J. Turnbull wrote: > The problem is that Mailman's LMTP server rejects malformed mail. I > seem to recall that in Mailman 2, Mailman itself would add a > Message-ID field if one was not present. I don't know how easy it > would be to provide this feature, since we would have to patch the > LMTP server code so the message could make it to Mailman proper > (Mailman 3 imports the LMTP server from the stdlib). It's a simple patch to the lmtp runner (Mailman's LMTP server). There's a closed issue on this at <https://gitlab.com/mailman/mailman/issues/490> - closed because I convinced the submitter it wasn't the right thing to do. > > My solution for now (apart from telling people not to use old > > broken Outlook!) is to modify the exim mailman3_transport so that > > any message with a missing Message-ID: will have one generated by > > exim before it's passed to LMTP. This reproduces the same behaviour > > exim uses for locally submitted messages. > > I'm not sure it's a good idea to do this (and certainly not by > default). The only times I've seen messages without a Message-ID are > spam messages. I suppose we can add this to the documentation. I added Robert's solution at <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#troubles…> The requirement for a Message-ID: is documented, albeit not very prominently, at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/runners/docs/lmt…>. -- 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 download mbox

by Mark Sapiro

On 4/25/21 2:20 PM, Andrew Hodgson wrote: > Hi, > > Hyperkitty 1.3.4. > > I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. > > Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, do it in pieces by adjusting start and end. e.g. <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> fails the same way. If I try to get 2013 month by month, all work except December which gives me an internal server error. What's 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

4 years, 3 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 03/17/2017 03:59 AM, Anders Nilsson wrote: > > I do have problems with some lists occasionally going into some kind of > shunt mode, where alla mails sent to them gets shunted. In the Mailman > log I get entries for each shunted email: > > Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows > were found for one_or_none() ... > File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", > line 70, in process > archiver_set = IListArchiverSet(mlist) mailman/handlers/rfc_2369.py is adding the List-* headers. Here it is looking up all the archivers that are enabled for this list. ... > File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", > line 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() and here we are in code that is trying to see if there are any system enabled archivers that are not already associated with this mailing list and if so, add them to the archivers enabled for this list. The above is the last line of exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() which is querying the archivers enabled for this list for the name of a system enabled archiver and expects to find at most one entry > File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", > line 2733, in one_or_none > "Multiple rows were found for one_or_none()") but finds more than one. > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > Mar 17 11:54:11 2017 (6217) SHUNTING: > 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 So the cause is there appear to be multiple database entries for this list and some archiver name, but I don't know how that can happen. I have not seen this error. -- 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: Change digest frequency and default threshold

by Mark Sapiro

On 10/04/2018 12:19 AM, Henrik Rasmussen wrote: > > Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. 3.2.0a1 was never an 'official' release. It could be any HEAD version between June 4, 2017 and Jul 10, 2018. The --periodic option was added April 28, 2018. > When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). Are there accumulated messages for the digest when you run the command?. I.e., is there a var/lists/listname.lists.example.com/digest.mmdf file with messages in it? Are there list members receiving digests? If so, there should be something in Mailman's smtp.log. > As I understand, using --sent should send a digest immediately (except when used with --dry-run). Correct,if there is one to send. > As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? It is Kilobytes. > Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? The digest size threshold has no effect on whether or not a digest is sent by 'mailman digests'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

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

by Mark Sapiro

On 10/17/24 13:41, Andy Matthews wrote: > > and then rebuilt kubernetes, I found that when I hit the API to get all lists, the list mailman(a)foobar.com existed, and was the default. I could create lists against foobar.com but could no longer create them against mydomain.com. > > So it looks like when you're initially configuring mailman you have to create your first mailing list, and whatever domain you use becomes your "primary domain". I don't know where this is documented, but could someone confirm this behavior for me so that I know that I'm on the right path? And previously you wrote: > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> Did you commit() after doing the above? I'm not sure how kubernetes fits in to this, but `mailman create` for a list in an unknown domain will create the domain unless -D or --no-domain is specified. See `mailman create --help`. Mailman core has no concept of `primary domain` which is why it's not documented. Are you creating lists via REST as you posted previously. If so, the domain must exist, but if you created domains as above, they should exist as long as you committed your changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

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

by Mark Sapiro

On 2/5/25 13:03, Ron / BCLUG wrote: > > I've been digging into MM3 resource usage vs MM2 and have been > wondering: are there any other runners that can be disabled, or invoked > via cron job to run every $interval then exit again? The task runner is a candidate. It only actually does anything at intervals defined by the run_tasks_every setting in the [mailman] section of mailman.cfg, default 1 hour https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…, but it still wakes up and comes into memory every sleep_time which defaults to 1 second. If just having the runners sleep longer works for you, you can set, e.g. ``` [runner.task] sleep_time: 10m ``` to only wake up the task runner every 10 minutes. If you really want it gone, you could put ``` [runner.task] start: no ``` in mailman.cfg to prevent starting it as a persistent runner, and make a python script like: ``` #!/opt/mailman/mm/venv/bin/python from mailman.core import initialize from mailman.runners.task import TaskRunner initialize.initialize() TaskRunner('task')._do_periodic() ``` and run that periodically via cron. I'm not certain, but I think task runner is the only runner for which it's that simple. > Second question, similar topic but MM2: how to disable NNTP? (if that's > what this is doing): > > /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Put this in mm_cfg.py del QRUNNERS[QRUNNERS.index(('NewsRunner', 1))] or if you already have some modifications to the QRUNNERS list in mm_cfg.py, make the appropriate adjustment to remove the NewsRunner entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/5/22 14:46, Allan Hansen wrote: > I asked the poster of one message what he had done. > Apparently, he had put the list address (just one list, according to him) in the Bcc: field. > The message was then held for moderator approval and, when approved, sent out without a body. > > Another message was stopped because it did not have a subject field. > Again, it was approved and then sent out without a body. I just did a test of a message with no Subject. It was held for no subject and when accepted was delivered. in all cases, the notice to the admin, the message in the held message view, the message delivered to the list members and the archived message; the message body was intact I did the same test with implicit destination with the same result. I even tried posting the same message to list(a)example.com and list+z(a)example.com resulting in two held messages which I accepted one at a time and the only difference was only the first accepted message was archived by HyperKitty because of the duplicate Message-ID:. Both were archived with content in the prototype archive. If you are really on Mailman 3.3.7, your result should be the same. Even on 3.3.5 which first introduced the possibility of content being lost, this shouldn't happen on posts to a single list You could try these same tests on a test list on your installation. I would be interested in your result. If it is the same as mine, there must be some other condition affecting this although I don't know what it would be. -- 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: mailman-core installation on debian stretch/maria-db

by Mark Sapiro

On 03/11/2018 03:11 PM, Wolfgang Bock wrote: > -> After I set a symlink to /sbin/master another errormessage occurs >>> 2. connection to maria-db >>> In debian stretch maria-db is running. In my mailman.cfg I set: >>> [database] >>> class: mailman.database.mysql.MySQLDatabase >>> url: >>> mysql+pmysql://#username#:#user-pawo#@localhost/#databasename#?charset=utf8&use_unicode=1 >>> >> should that be mysql+pymysql ? > -> Yes, according to: > http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html > -> Not right?? My point is you have 'mysql+pmysql' and you should have 'mysql+pymysql'. You are missing the first 'y' in 'pymysql'. > After that I decided to delete mailman via pip and took a new approach > via debians apt-get ... mailman 3 > > So far so good, now new errormessage: > > Traceback (most recent call last): ... > AttributeError: module 'mailman.database.mysql' has no attribute > 'MYSQLDatabase' Did you install the Debian dbconfig-mysql dependency? I don't know how installation of mailman3-core determines which if any of the database dependencies, but you need that for sure to support MySQL/MariaDB. > Another question is, where can I find the sql-command within the > database mailman3 like CREATE TABLE x and TABLE y as I created a > database mailman3 which is empty?? The database may be empty because of the above error and the fact you haven't yet done anything. All the database access is via SQLAlchemy and models defined in Mailman's mailman/models/ directory. See <http://mailman.readthedocs.io/en/latest/src/mailman/model/docs/model.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:04 AM, Andrew Bernard wrote: > > Where is the Django config area for the > pip installed modules? It is this that I find obscure. The short answer is wherever you put it. If you look at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which Abhilash mentioned, you'll see what I do. Abhilash mentioned creating the virtualenv in /opt/mailman/. I actually have another level below that, /opt/mailman/mm/, but this is only for convenience to separate things as I also have directories for the git branches and for local patches, so if we are just working with /opt/mailman/, you can put your Django settings.py and settings_local.py files there. I also put various other config things there like Mailman's var/ directory Django's static/ directory mailman.cfg mailman-hyperkitty.cfg gunicorn.conf and an empty __init__.py file so Django can import settings. Then I create a /opt/mailman/bin/ directory and in that I put small bash scripts to run things. for example: opt/mailman/bin/mailman contains #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ opt/mailman/bin/django-admin contains #!/bin/bash . /opt/mailman/venv/bin/activate cd /opt/mailman/ export PYTHONPATH=/opt/mailman/ export DJANGO_SETTINGS_MODULE=settings django-admin $@ and opt/mailman/bin/gunicorn contains #!/opt/mailman/venv/bin/python import sys sys.path[0:0] = [ '/opt/mailman/', ] import os os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' import gunicorn.app.wsgiapp if __name__ == '__main__': sys.exit(gunicorn.app.wsgiapp.run()) Then I use those commands to run Mailman, Django and gunicorn. Some of this may not be directly applicable to you, but I hope it gives you the basic idea. -- 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: How to change the language in mailman3

by Mark Sapiro

On 7/17/20 9:44 AM, Massimo Zappalà wrote: > Hi everyone, > Mark thanks for the reply. > My installation was done on Debian Buster by installing the mailman3-full package > > I can't find the path you indicated: >> Mailman core in mailman/messages/ >> Hyperkitty in hyperkitty/local/ >> django-mailman3 in django-mailman3/local/ >> postorius in postorius/local/ > Maybe some packages are missing? I doubt things are missing. I can't keep track of where all the downstream packages put things, but look in /usr/lib/mailman and/or /var/lib/mailman or use tools like `find` or `locate`. >> To set language for Django (i.e. hyperkitty and postorius) see >> https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-di.... > What are the files to be edited? settings_local.py >> For Mailman core, set [mailman] default_language: in mailman.cfg. > Ok Done > >> You also need to (re)generate the .mo file which can be done with the >> generate_mo.sh script. > I can't find the script It probably isn't included in the Debian package. This is what it does. #!/bin/bash # This script generates .mo files from all the .po files in the source. echo 'Generating mo files for GNU Mailman ...' for file in `find -name 'mailman.po'` do echo $file msgfmt $file -o ${file/po/mo} -v done >> For Django, you need to generate .mo files with >> django_admin compilemessages > Where should this be written? You give the compilemessages subcommand to whatever command you use for django-admin or manage.py or whatever the Debian package calls 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

[MM3-users] Re: mailman.log file owned by 'list' user

by Mark Sapiro

On 1/7/23 14:14, Mike Wertheim wrote: > I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 > that was done by someone else. > > Mailman is running as a non-privileged (non-root) user called 'xyz'. On the > day that Mailman was installed, that non-privileged 'xyz' user was able to > execute mailman commands successfully to create, view and modify lists. The Debian package uses 'list' as the Mailman User. Whoever did the installation apparently tried to change that to 'xyz' and did an incomplete job. > A couple of days later, when the 'xyz' user tried running those same > mailman commands, they failed with this error: PermissionError: [Errno 13] > Permission denied: '/var/log/mailman3/mailman.log' > > Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: > -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log > > When I did a 'ps' command, I saw that all of the mailman processes are > running as user 'xyz'. No processes were running as the user 'list'. > > It seems that some process is rotating the mailman.log file at midnight, > and the newly-created mailman.log is being owned by user 'list'. > > Can anyone explain why this is happening, and how to fix it? It is happening because the logrotate script (maybe /etc/logrotate.d/mailman3) sets the user to 'list'. change that to 'xyz'. Also sudo chown -R xyz:xyz /var/log/mailman3/ and wait for the next issue to arise. -- 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: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/27/25 05:44, Kim Sunggun via Mailman-users wrote: > Hello, > > /opt/mailman/venv/lib/python3.9/site-packages/django/conf/global_settings.py:EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/settings/base.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' OK. > I installed mailman3 in rhel 9 based on https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > I set up Postfix as the MTA. I added the code as mentioned in the document. > > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = > hash:/opt/mailman/mm/var/data/postfix_domains These are good but not relevant to your issue. They affect delivery of incoming mail to Mailman. Your issue is with outgoing mail from Django. There are various settings that affect this SMTP connection as described at https://docs.djangoproject.com/en/5.1/topics/email/#smtp-backend The defaults are EMAIL_HOST = "localhost" EMAIL_PORT = 25 and for the optional settings EMAIL_HOST_USER = "" EMAIL_HOST_PASSWORD = "" EMAIL_USE_TLS = False EMAIL_USE_SSL = False EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = None Have you set any of those to other than default in your Django settings? If not, what do you get if you run this python snippet as the Mailman user ``` import smtplib connection = smtplib.SMTP(host='localhost', port=25) ``` If you have, you can specify them as args to smtplib.SMTP, e.g. ``` connection = smtplib.SMTP(host='localhost', port=25, username='...', password='...') ``` or if EMAIL_USE_SSL is True, ``` connection = smtplib.SMTP_SSL(host='localhost', port=25, username='...', password='...', ssl_keyfile='...', ssl_certfile='...') ``` See https://github.com/django/django/blob/ea1e3703bee28bfbe4f32ceb39ad31763353b… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: list footer questions

by Mark Sapiro

On 6/7/20 9:40 AM, kelly.close(a)lrewater.com wrote: > > So I have a template file here: > /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list:member:regular:footer.txt > > I had to create everything below templates/ as that folder was empty on install. I made sure what I created had the same permissions as the templates folder. I'm not sure what else to do. Is there a configuration file somewhere perhaps the identifies the path of the templates folder and maybe I need to adjust it? There are two things. One is the location of the `templates/` directory. That is located in `$var_dir` and the value of that depends on the settings for ``` [mailman] layout: ``` and ``` [paths.<layout_value>] var_dir: ``` in mailman.cfg. I'm not certain, but I think `/var/lib/mailman3/` is correct for the Debian/Ubuntu package. The other thing that affects this is the value of the URI for the template in the database. This is somewhat tricky. The docs are at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>, but there isn't an example of retrieving URIs via REST. I.e. something like ``` curl -urestadmin:restpass http://localhost:8001/3.1/lists/f2p2-test.udfcd-lists.org/uris ``` should work, but returns a 404 when I try it on one of my lists that has a URI. I look in mailman's database with a query like ``` select name, context, uri from template; ``` What you are looking for is a row with `name` = `list:member:regular:footer` and `context` = `f2p2-test.udfcd-lists.org`. If there is one and it has a uri other than `mailman:///$listname/$language/list:member:regular:footer.txt` then Mailman will look there for the template. -- 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: Enable delivery

by Mark Sapiro

On 12/10/24 10:43, Hirayama, Pat wrote: > Apologies, I should've said my "Mailman 3" server, not listserv. > > MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs. > > As for the CLI commands, I keep getting Attribute Error when I try them, like: > > /opt/mailman # mailman shell -l listname(a)mailman.tld > 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 listname(a)mailman.tld mailing list >>>> from mailman.core.constants import system_preferences >>>> mbr = m.members.get_member('user(a)domain.com.') >>>> print(mbr.delivery_status) > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: 'NoneType' object has no attribute 'delivery_status' Are you literally typing mbr = m.members.get_member('user(a)domain.com.') That needs to be an actual list member's email without a trailing period. The fact that mbr is None means whatever you provided is not a member of the listname(a)mailman.tld list. Curious that the member(s) in question are not amongst the recipients delivered to the MTA even though >> when I run: >> >> mailman members --nomail any listname@listserv >> >> Nothing is returned. This should only happen if the members are digest members (are they) or are directly addressed in To: or Cc: of the post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/23/21 9:57 AM, David Newman wrote: > > The task-pending message that MM3 sends to list owners and moderators > just says generically to check the dashboard, without providing a URL. > > Can that be modified to provide an explicit URL, something like this? > > https://lists.example.com/mailman3/lists/listname Yes, That particular message is built from the list:admin:action:post template. You may wish to make custom versions of that and other templates. The templates and their default values are at https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en You can make custom versions of templates in two ways. You can create if necessary a /opt/mailman/mm/var/templates directory (it probably already exists). Within that directory, sitewide English templates are put in the site/en/ directory, domain specific English templates are put in the domains/<domain_name>/en/ directory and list specific English templates are put in the lists/<list_id>/en/ directory. For templates like this, you probably want sitewide ones. E.g., site/en/list:admin:action:post.txt --------------------------------------------------------------- As list administrator, your authorization is requested for the following mailing list posting: List: $listname From: $sender_email Subject: $subject The message is being held because: $reasons At your convenience, visit https://lists.example.com/mailman3/lists/$list_id/held_messages to approve or deny the request. --------------------------------------------------------------- The other way to create custom templates is via Postotrius, but Postorius only creates list and domain specific templates. Also, if you create a template in Postorius, it overrides any in /opt/mailman/mm/var/templates/ until you delete it in Postorius. Info about templates and what substitution variables can be used is at 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: Mailing list welcome message won't update

by Mark Sapiro

On 1/15/25 14:29, via Mailman-users wrote: > Thanks Stephen and Mark. > > I checked whether group and world have 'x' permission on every directory in the path to the files and found below: > > root@lists:/var/lib/mailman3/templates# ll > total 12 > drwxr-xr-x 3 list list 4096 Oct 10 2018 ./ > drwxr-xr-x 12 list list 4096 Jan 9 05:08 ../ > drwxr--r-- 5 list list 4096 Mar 30 2021 lists/ > > > root@lists:/var/lib/mailman3/templates# cd lists/ > root@lists:/var/lib/mailman3/templates/lists# ll > total 20 > drwxr--r-- 5 list list 4096 Mar 30 2021 ./ > drwxr-xr-x 3 list list 4096 Oct 10 2018 ../ > drwxr--r-- 3 list list 4096 Jan 8 01:14 [redacted].lists.[redacted].org.au/ > > > root@lists:/var/lib/mailman3/templates/lists# cd p[redacted].lists.[redacted].org.au/ > root@lists:/var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au# ll > total 12 > drwxr--r-- 3 list list 4096 Jan 8 01:14 ./ > drwxr--r-- 5 list list 4096 Mar 30 2021 ../ > drwxr--r-- 2 list list 4096 Jan 15 04:45 en/ > > So, group and world did not have 'x' permission to all the superordinate directories. I don't think that matters. As long as everything is running as user `list`. How are you testing. Are you running a `mailman` command and if so, are you running that as user `list`. Note that `mailman` commands should only ever be run as the Mailman user, `list` in your case. If that explains the issue, fine. Otherwise this seems to be an issue with the Debian package and should be reported to Debian. 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

6 months, 2 weeks

[MM3-users] Re: Filter question

by Mark Sapiro

On 2/7/25 17:32, Chris via Mailman-users wrote: > List has "filter content" set. > Filter Mime-Type [] > Filter Extensions exe bat cmd com pif scr vbs cpl > Accept Mime Media Types > > multipart > message/rfc822 > text/plain > text/html > application/pdf > application/nappdf > application/x-pdf > application/rtf > application/vnd.oasis.opendocument.spreadsheet > application/vnd.openxmlformats-officedocument.spreadsheetml.sheet > application/vnd.ms-excel > application/vnd.oasis.opendocument.text > application/vnd.openxmlformats-officedocument.wordprocessingml.document > application/msword > > Allow Extensions .zip .7z > > > Reduce Alternative No > Convert to Plain-Text No > > > > Now I'm sending an Message from outlook (html) with Inline Images. > Content Filter off: Works fine > Conent Filter On,: All except the image ist fine. The image gets lost and only a placeholder is shown > > > <img data-cid="image001.png(a)01D65210.566F56E0" height="51" id="Grafik_x0020_1" src="../../attachment/view/tmai1738975737149948386/aW1hZ2UwMDEucG5nQDAxRDY1MjEwLjU2NkY1NkUw;jsessionid=03FDBB0F16AFB10F7439822AB2C59450-n4.bap20a" style="width: 3.3437in;height: 0.5312in;" width="321"> This is removed because you don't have image/png in accept mime types. If you want to accept images, you should probably add just the `image` main type to accept mime types. > Even if MimeTypes filter is [] signature (p7s) gets filtered. > Any hint? To accept these, add application/x-pkcs7-signature application/pkcs7-signature and you may also want to add application/pgp-signature When accept mime types is non-empty, only those types will be accepted. Filtering on extensions only applies to mime parts with a filename parameter and again, if Allow Extensions is non-empty, only those filename extensions will be accepted. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/mime_… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

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

by Mark Sapiro

On 1/18/22 06:24, Stephan Krinetzki wrote: > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? There are two steps in handling the POST for a held message. The first step is accepting, rejecting or discarding the message. This is happening immediately. The second step is handling the poster's moderation action based on the choice from the Set member moderation dropdown in the view of the held message. This is processed by the code at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…>. If no selection has been made, the default value POSTed for moderation_choice is `no-action` and that code is skipped. If it is one of the choices `Hold for moderation`, `Reject (with notification)`, `Discard (no notification)`, `Accept immediately (bypass other rules)` or `Default processing` that is processed. So presumably a selection has been made and processing is stuck on getting the member or setting the member's moderation action. Possibly the logs of your database manager will have information. -- 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: REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST

by Mark Sapiro

On 4/13/23 13:21, Eric Vyncke wrote: > Humm after some more investigations, it seems that my mailman3 installation via debian packages is completely mixed up :-( This would explain the issue if the REST API is using 3.2.2 code and postorius is expecting 3.3.5... > > drwxr-xr-x 29 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman > drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman-3.2.2.egg-info > drwxr-xr-x 8 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient > drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient-3.2.2.egg-info > drwxr-xr-x 4 root root 4096 Apr 13 14:29 /usr/lib/python3/dist-packages/mailman_hyperkitty > drwxr-xr-x 2 root root 4096 Apr 13 14:28 /usr/lib/python3/dist-packages/mailman_hyperkitty-1.1.0.egg-info > drwxr-sr-x 30 root staff 4096 Apr 13 09:32 /usr/local/lib/python3.8/dist-packages/mailman > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman-3.3.5.dist-info > drwxr-sr-x 9 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient-3.3.3.dist-info > drwxr-sr-x 4 root staff 4096 Apr 12 20:47 /usr/local/lib/python3.8/dist-packages/mailman_web > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman_web-0.0.5.dist-info Yes, that would be the problem if the Python running Mailman core was using libraries in /usr/lib/python3/dist-packages/ and the Python running Django was using libraries in /usr/local/lib/python3.8/dist-packages/. The ability to get/set preferred_address via REST was added to Mailman core 3.3.0 and is not in 3.2.2. -- 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: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > > When I add new members through Mass operations -> Mass subscribe, the new members have a Moderation Action of `None`. Correct. > I've looked through the archives of this list, and from what I can tell: > > According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >> None does not mean no moderation. None means use the list default >> as opposed to one of the specific actions defined > > The thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… seems to also repeat the above, that `none` means the configured setting for the list. > > However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is `None`, but when I posted to the list from the address, it was not held for moderation, and went through. > > Am I missing something with the expected functionality? A member's moderation action of None means use the `Default action to take when a member posts to the list`. Is that set to `Hold for moderation`? Actually, it is good practice to set that to `Hold for moderation` for all lists or at least all those that don't require moderator approval for subscription to prevent a spammer from subscribing and spamming the list. Then, upon approving a member's post you can also set the member's moderation action to `default processing` and upon discarding a spammers post, you can also set the spammer's moderation action to `Discard`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Is it possible to grant all users the ability to Create List

by Mark Sapiro

On 7/12/21 8:25 AM, tibor.molnar(a)waltoninstitute.ie wrote: > Hi, > > I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: > > Superuser: Can do everything. > AnonymousUser: Can view list index and info pages. > Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. > > Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how? The user's `role` is a Django thing. A user can be given either `staff` or `superuser` status or both or neither. As far as Django is concerned, `staff` status only allows the user to visit the Django administration interface. Currently, Postorius has decorators @list_owner_required, @list_moderator_required and @superuser_required defined in postorius/auth/decorators.py. There is also a @login_required decorator in django.contrib.auth.decorators. Postorius decorates the list_new() function in postorius/views/list.py with @login_required and @superuser_required. It would be simple enough to create a new @staff_required decorator which would require staff or superuser status and replace the @superuser_required decorator on the list_new() function with @staff_required. Then any user with `staff` status could create lists. -- 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: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Mark Sapiro

On 9/30/23 15:23, Wikinaut wrote: > After having changed and re-changed "only" the line in /etc/mailman3/mailman-web.py (which looks to be only a "blinder" and the real problem could be a different one) > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' This should not include the mailman3/ path. If http://localhost/mailman3/ gets to Postorius, it should just be 'http://localhost/'. > the web access via Postorius is not working any more and throws "Error 500" > > My logfile /var/log/mailman3/web/mailman-web.log shows now > ...> from django.utils.encoding import force_bytes, force_str, force_text > ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) > > I already run pip install -U postorius to update that (looks okay to me): > > Requirement already satisfied: postorius in /usr/local/lib/python3.9/dist-packages (1.3.8) ... > Requirement already satisfied: django<4.2,>=3.2 in /usr/local/lib/python3.9/dist-packages (from postorius) (4.1.9) ... > dpkg -l | grep django > ii python3-django 2:2.2.28-1~deb11u2 all High-level Python web development framework Something is confused here. Your Django version from dpkg is 2.2.28, bit from your above `pip install`, it is 4.1.9. I'm not sure haw the Debian package installs, but probably in a venv. > ii python3-django-q 1.2.1-1 all Django multiprocessing distributed task queue (Python 3 version) I don't know what the django-q version in the venv is, but Django >=4.0 requires django-q >=1.3.0 If The Debian backage includes Django>=4.0 and django-q<1.3.0, it's a Debian packaging issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 12:12, Eggert Ehmke via Mailman-users wrote: > Hello Mark, > > I am also using MySql/MariaDb, I followed your suggestion. This would uninstall a lot of > other packages, is that safe? I did not continue. > > > $ pip uninstall psycopg2_binary > Found existing installation: psycopg2-binary 2.9.6 > Uninstalling psycopg2-binary-2.9.6: > Would remove: > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2/* > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary-2.9.6.dist-info/* > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libcom_err-2abe824b.so.2.1 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libcrypto-2cd0ac56.so.1.1 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libgssapi_krb5-497db0c6.so.2.2 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libk5crypto- > b1f99d5c.so.3.1 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkeyutils- > dfe70bd6.so.1.5 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5- > fcafa220.so.3.3 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5support- > d0bcff84.so.0.1 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > liblber-69811697.so.2.0.200 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libldap- > e7812872.so.2.0.200 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libpcre-9513aab5.so.1.2.0 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libpq-227f62f1.so.5.15 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libsasl2-883649fd.so.3.0.0 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libselinux-0922c95c.so.1 > /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ > libssl-0331cfe8.so.1.1 > Proceed (Y/n)? n Yes, it is safe. the things listed other than psycopg2/* are just installation information about psycopg2_binary. No other packages are actually involved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

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

by Mark Sapiro

On 10/2/20 2:58 PM, Alex Schuilenburg via Mailman-users wrote: > > I ran both on the original archive, cleanarch made no changes and > check_hk_import just retported the number of messages. That's actually expected with this mbox as there are apparantly no unescaped `From ` lines in the message body and no other serious defects. > As it turns out, the message was imported, but with the dodgy email as > sender which was fixed by the insert/update as per my comment. > > Hope you have some success with the redacted mbox example. As I mention at <https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422998204> I imported the mbox to a test list, and there were noe real issues. What issue there is is the mbox message's actual From: header is ``` From: Firstname Surname at example-UK <user(a)example.com> ``` Part of what's going on is some MM 2.1 archives has email addresses obfuscated by replacing `@` with ` at ` so the import process reverses this and changes the From: to header is ``` From: Firstname Surname@example-UK <user(a)example.com> ``` which now contains two email addresses albeit not separated by a comma and picks the first. The message then gets properly archived with sender `Firstname Surname@example-UK` which is a syntactically valid email address and doesn't cause the ResponseNotReady() exception in sync_mailman so I don't see that issue. The difference is either the fact that my test runs with the HEAD of the GitLab branch which may not have the issue or the difference between the real From: header and the sanitized one is significant. -- 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: Hyperkitty list overview error: thread matching query does not exist

by Mark Sapiro

On 5/23/22 11:11, Darren Hart via Mailman-users wrote: > When attempting to visit the hyperkitty archives list overview for one of my two lists: > > Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ > > The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). > > The following appears in /var/log/mailman3/web/mailman-web.log: > > > ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. > > The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. > > The hyper kitty archives for a second list on this Mailman3 instance is working correctly. > > How can I fix this view of the archives? Or how can I get more information on what might be failing? I'm not sure if this will help, but try running your django management command with arguments `runjob recent_threads_cache`. Note that this will be run daily if you are running the Cron Jobs for Mailman Web. See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=perio… -- 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: Importing mbox files into archive defect with lines with From

by Mark Sapiro

On 6/21/19 12:57 AM, andrew.bernard(a)gmail.com wrote: > A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. > > Is this a known bug? If not, how do I report it? As other responses in this thread have pointed out, it is a well known issue with mbox format in that lines beginning with 'From ' are message separators. There is a (Python 2) script at <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/bin/cle…> that will process a mbox and prefix with '>' all lines beginning with 'From ' that don't look like real 'From ' lines or which aren't immediately followed by a line that looks like a valid header line. It isn't perfect because it won't handle a message that contains in it's body a copy of another message containing a Unix From_ line, but it can helm with most unescaped From_ lines. If you want to use that script, replace lines 55 and 56 import paths from Mailman.i18n import C_ with def C_(s): return s -- 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: integrate subscribe form in Website -> CSRF-token

by Mark Sapiro

On 6/21/21 11:58 AM, Jens Günther wrote: > > We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): > > <form method="POST" > action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> > > <input name="email" value="" type="text"><br> > <input name="email-button" value="Anmelden" type="submit"> > </form> > > When I now enter a mailaddress, the quoted error occurs. This is Django protecting against CSRF. You need to GET the for with the (hidden) CSRF token before you can POST it. > Checking another answer directly to me, there seems to be another hint :-) > > > I believe you are attempting to use the MM Core API via http > GET/POST, rather than via Postorius? That you have tried and get the > CSRF error reported? > > > > Typically this is because you need to add a token to the request to > indicate to the MM Core that your request isn't a forgery. Typically > this token is requested from Core and then presented with subsequent > requests. Have you tried this? > > > > Therefor it is needed to send also a token!? Or use another URL, not > postorius in order to subscribe!? How can I submit such a token? To submit the Token, you need to first GET the form which will have the token. Then you can include it in the POST data. This is not a satisfactory solution for your case. As hinted above, you need to use the REST API. See 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

4 years, 1 month

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

by Mark Sapiro

On 7/19/21 9:42 AM, Sarah H wrote: > so there should be inside the docroot created by collectstatic a location /docroot/archives(or hyperkitty)/api? or is there another location that this particular page should be served from? at present the hyperkitty directory there is only css, fonts, img and js dirs. > > if I can find where this should be served from in the file system that'll give me some way to figure out what I'm actually looking for URL wise... Hyperkitty is not serving a web page. HyperKitty has an API at base_url/api with a few endpoints and generates responses to various GETs and POSTs to those endpoints. Mailman core makes calls to methods in mailman_hyperkitty/__init__.py which in turn call the HyperKitty APi and return the result. The `list_url(mlist)` method is called to get the URL to the list's archive for the List-Archive: header. It in turn does a GET for base_url/api/mailman/urls with query fragments key=<api_key> and mlist=<the fully qualified list name> to get the URL The `permalink(mlist, msg)` method is called to get the link to where HyperKitty will store the message for the Archived-At: header. It in turn does a GET for base_url/api/mailman/urls with query fragments key=<api_key>, mlist=<the fully qualified list name> and msgid=<the message-id from the message> to get the URL The `archive_message(mlist, msg)` method is called to actually archive the message. It in turn does a PUT for base_url/api/mailman/archive with the api_key, the fully qualified list name and the text of the message. See https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperki… for the full detail. -- 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: digest summary heavily cluttered with hrml code

by Mark Sapiro

On 10/14/20 8:46 AM, Mohsen Masoudfar wrote: > Hi, > > I am running Mailman 3.1.1 on Ubuntu 18.04. > > The user complains that the digest summary is cluttered with HTML code. What does 'summary' mean in this context? Are you referring to the 'Today's Topics:' list or the messages themselves? Is this perhaps <https://gitlab.com/mailman/mailman/-/issues/473>? > I thought, I may fix it by: > Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. There are actually 3 sets of user preferences. They are in order of priority, list based, address based and global. You can see these if you are logged in to the web UI as the user and go to 'Mailman settings' in the pull down at the top right. There are issues in Postorius if a user is a member of a list with more than one role - see <https://gitlab.com/mailman/mailman/-/issues/659>. > Question 1: How may I be sure that the value is set, if it is set? Examine the settings with `mailman shell` > Question 2: How may set it for all members of the list? Create a `mailman shell` script. > Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Again, `mailman shell`, but this is low level and requires some knowledge of Mailman internals. -- 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: MTA setup

by Mark Sapiro

On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: > Output from mailman log after sending a test message to the list: > > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > line 158, in _archive_message > url = self._send_message(mlist, msg) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > line 228, in _send_message > raise ValueError(result.text) > ValueError: > <!doctype html> > <html lang="en"> > <head> > <title>Bad Request (400)</title> > </head> > <body> > <h1>Bad Request (400)</h1><p></p> > </body> > </html> mailman_hyperkitty is sending the message to hyperkitty to be archived and receiving the 400 response. Presumably it has previously requested and received the list_url and the permalink to put in the message headers. This can be confirmed by the presence of List-Archive: and Archived-At: headers with values in the messages from the list. So the configuration seems to be correct to allow mailman_hyperkitty to communicate with hyperkitty. It is not clear why, but this code https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… is getting the ValueError. That can come from one of three places in https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. The lack of a Message-ID: is not it because Mailman's lmtp runner will add one. Most likely it is the non-ascii sender address from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… What do you get from ``` mailman qfile var/archives/hyperkitty/spool/xxx.pck ``` where xxx.pck is one of the (hopefully smaller) files. In particular, what is the From: header in that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/11/23 5:00 PM, bryan.kartzman(a)yu.edu wrote: > Thanks. That worked. I converted the sqlite3 database to a postgresql database and I configured the database in the DATABASES definition of the Django settings. The database lock errors have disappeared but I am getting a Django warning of an improper datetime field. I assume that is related to the database conversion. Any advice for a possible solution? These are the error messages: > ... > /usr/lib/python3/dist-packages/django/db/models/fields/__init__.py:1424: RuntimeWarning: DateTimeField MailingList.created_at received a naive datetime (2023-06-18 18:51:09.290256) while time zone support is active. > warnings.warn("DateTimeField %s received a naive datetime (%s)" > ... > /usr/lib/python3/dist-packages/django/db/models/fields/__init__.py:1424: RuntimeWarning: DateTimeField OrmQ.lock received a naive datetime (2023-09-11 20:29:35.702222) while time zone support is active. > warnings.warn("DateTimeField %s received a naive datetime (%s)" > ... These fields and perhaps others need to be defined in Postgresql as timestamp with time zone. E.g. ``` Table "public.hyperkitty_mailinglist" Column | Type | Collation | Nullable | Default ------------------------+--------------------------+-----------+----------+---------------------------------------------------- id | integer | | not null | nextval('hyperkitty_mailinglist_id_seq'::regclass) name | character varying(254) | | not null | display_name | character varying(255) | | not null | description | text | | | subject_prefix | character varying(255) | | not null | archive_policy | integer | | not null | created_at | timestamp with time zone | | not null | list_id | character varying(254) | | | archive_rendering_mode | character varying(255) | | | ... Table "public.django_q_ormq" Column | Type | Collation | Nullable | Default ---------+--------------------------+-----------+----------+------------------------------------------- id | integer | | not null | nextval('django_q_ormq_id_seq'::regclass) key | character varying(100) | | not null | payload | text | | not null | lock | timestamp with time zone | | | Indexes: "django_q_ormq_pkey" PRIMARY KEY, btree (id) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/19/20 6:11 PM, Brian Carpenter wrote: > > No one set their preferred address here at all. The first incident was > an imported list member who was not a registered user. And the import21 created the user and address records for this user. > They wanted their > real name changed to something else. The list owner tried to figured out > how to do that, found no way to do it, figured out it was just easier to > unsubscribe them, and resubscribed them to the list using a different > name. The old name showed up again. This is a bug and please fix it > soon. If you feel this is a bug that needs to be fixed, file an issue or issues reporting it. > This has nothing to do with being subscribed to other lists. In your particular instance that's true. > I can > probably come up with a workaround using Affinity (one of the benefits > of moving away from Postorius) but I can't imagine this not being a > serious issue as Mailman 3/Postorius is more widely adopted. File an issue at https://gitlab.com/mailman/postorius/-/issues asking for the ability to change the display name associated with an address and/or an issue at <https://gitlab.com/mailman/mailman/-/issues> requesting that adding an address with a display_name as a member, non-member, moderator or owner of a list override an existing display_name for that address. I don't think you can do this in affinity because I don't think there is currently a REST endpoint to do it. You can do it easily in mailman shell, but that doesn't help the user or list admin. -- 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: So near, and yet so far (Configuring Mailman)

by Mark Sapiro

On 1/29/21 9:01 AM, Jack Lenox via Mailman-users wrote: > Hello all, > > I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails. > > When I try to send emails to lists I'm rebuffed with undelivered notices with: > > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found > and: > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again > > This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that: > > lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. > lists.fiftyshadesof.green. 0 IN A 193.37.35.191 > > I have driven myself mad with this and would very much appreciate any advice anyone can offer. It appears this is strictly a Postfix issue. I.e. it is rejecting the incoming mail. There are a few things to consider. Have you restarted Postfix? I don't offhand remember details, but Postfix keeps its own internal notion of some things (not sure if DNS is among them). Beyond that, what does `postconf -n` report and for things in that that reference Mailman stuff, what's in the referenced files? And, what's in /var/log/mail.log when you send to testlist(a)lists.fiftyshadesof.green? -- 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: Bottom line of message footer

by Mark Sapiro

On 2/14/21 5:40 PM, Tom Stoddard wrote: > Here's another question that I have. A regular message just came into my > email from one of the lists I'm a member of and it had a 3 line footer. > The first two lines are fine, they just include the list's email address > and an address to send unsubscribe requests to. The third line is this: > > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > It looks to me like it should be a link to the group's list info page. > Is this a bug or is there something I can do to fix it? It looks like it > might be missing a forward slash after the first "s". This is a list whose msg_footer was imported by The Mailman 3 process that imports Mailman 2.1 lists. This import process will recognize the default msg_footer and not create a list specific template for it, but other things in the footer result in a list specific template which needs to be reviewed for issues like this. The way for you to fix it is to create a list:member:regular:footer (and maybe a list:member:digest:footer) template in your web UI which will then override the existing list specific template. The available replacements are listed at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. In templates they are all $ strings, e.g. $name. The %(name)s replacements are Mailman 2.1 and won't work. Also, there is no replacement for web_page_url because Mailman Core doesn't know what that is, so you have to include the actual 'https://.../' value if you want to include a web link. -- 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: cleanup lost users completly - mailman shell

by Mark Sapiro

On 2/21/22 03:28, Paul Paulchen wrote: > > Thanks to this thread, I know how to find the lost souls in our mailman environment > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > >>> um = getUtility(IUserManager) > >>> for usr in um.users: > ... if len(list(usr.memberships.members)) > 0: > ... continue > ... adr = usr.addresses[0] > ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') > > So I can see them now. Is there a technique, to clean them up? To get rid of them out of the system? > I am not a python programmer, but I guess there is a way to use, instead of a single user, a list of users in the delete command of the mailman shell? The replies by Guillermo and Andrew both point to a message/thread containing the same clean_users.py script. This script will do some of what you want, but maybe not all of it. It will delete Django users who have no corresponding Mailman user or have a corresponding Mailman user that has no role on any list, and optionally delete the Mailman user as well. What it won't do is delete a Mailman user that has no role on any list if there is no corresponding Django user. For that you would want to add to the above fragment so it becomes: ``` >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... um.delete_user(usr) ... print(' Deleted.) ... >>> 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, 5 months

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

by Mark Sapiro

On 7/7/20 10:23 AM, Shashikanth Komandoor wrote: > > I did not see any log records based on that message id in mailman.log. > There is a lot much of shunt queue but I don't see any file with the > required message id. The same is the bad queue also. The message-id will not be logged in mailman.log for these issued. For each such issue, there will be a log message indicating the exception with a traceback and a 'shunting' message. To see the actual problem message, you can use `mailman qfile` to examine the shunted .pck file. > I find below two lines at that particular time stamp by when the log > recorded in vette.log > > > > *Uncaught runner exception: sequence item 0: expected str instance, Header > foundTypeError: sequence item 0: expected str instance, Header found* > > But I am not sure if the above lines are related to that missing message or > not. Almost certainly, but examine the shunted message with `mailman qfile` to be sure. > I am using postgresql as database. FYI, if it brings an idea to you to help > me. That's not relevant to this issue. Examine the tracebacks and shunted messages. If the problem is not obvious from that, you can post here for help. We need the complete error message with full traceback and the raw message text. For the message, we are primarily interested in all the headers including sub-part headers. Sub-part bodies can be truncated and headers sanitized for privacy if necessary, but the fewer changes you make to the raw message text, the better. -- 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: list footer questions

by Kelly Close

I agree Mark. I can't see the issue but those search rules are clear. I'm glad to know I can "force" it to work with the table records but I would like to figure out the more systemic issue in case it could affect other things. ~Kelly -- K. Kelly Close, P. E. Senior Project Manager | Water Rights Engineer | Technology Team Lead Office: 303-455-9589 | Direct: 303-867-7665 Kelly.Close(a)LREwater.com <http://www.lrewater.com/> LREWATER.COM <http://lrewater.com/> 1221 Auraria Parkway, Denver, CO 80204 ***CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.* On Sun, Jun 7, 2020 at 5:14 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/7/20 3:47 PM, Mark Sapiro wrote: > > > > 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. > > > > The search rules are documented in the code at > < > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > >. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

5 years, 1 month

[MM3-users] Re: Active archivers and archiving and thread question.

by Mark Sapiro

On 3/30/22 11:21, bob B via Mailman-users wrote: > Digging into the mailman3 world, and want to check my logic... > > We normally don't use archives, so I have "archive policy" set to "Do not archive this list" for our lists. However, the "archives" button is still there on the list info page, and if users go into it, they don't see anything, But they can click "start a new thread" which sends a message to the list, but since archiving is turned off, that message does not show up there. > Am I understanding that correctly? > > if I have "Active archivers" disabled, that hides that area from the users, correct? You need to have hyperkitty unchecked in Active archivers to prevent the Archive button from appearing on the info page. Archive policy = Do not archive this list will prevent HyperKitty from creating an archive for that list. If there is one at, e.g., https://example.com/archives/list/list@example.com/ you can delete it and Archive policy = Do not archive this list will keep it from being recreated. > Any reason why these are separated? why have an active archiver, if archiving is turned off -OR- archives are turned on, but no active archiver? They probably shouldn't be completely independent. If Archive policy = Do not archive this list, that should probably deactivate any Active archivers for the list, but arguably, one might want to temporarily stop archiving and then restart it without having to remember which archivers were active. At a minimum, setting Archive policy = Do not archive this list should probably remove the Archive button from the info page. -- 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: Emails about moderation are sent to list owners, want them sent to moderators instead

by Mark Sapiro

On 7/2/22 1:56 AM, Elias Rudberg wrote: > Hello, > > This is about GNU Mailman 3.3.3 (Tom Sawyer). > > For each list there are both "owners" and "moderators". As I understand > it, the idea is that owners have the power to change configuration for > the list, while moderators have more limited power, they can only > moderate but not change configuration. Correct. > When an email is sent from a non-member to a list that requires > moderation in such a case, an email with subject like "[listname] post > from [sender] requires approval" is sent to the list owners. I would > like those emails to be sent to moderators instead. Such notices are actually sent to the LISTNAME-owner@... address, received by Mailman and resent to all the owners and moderators. Both owners and moderators should receive the message. > The reason why I want it to work that way is that list owners sometimes > want to delegate the work of moderating to the moderators. List owners > then want to keep the power to change list configuration, but they do > not want to be bothered by individual moderation emails. > > Is there a way to configure mailman3 to make it send moderation emails > to moderators instead of owners? As I said, the notices are sent to both owners and moderators. There is no simple configuration to change this. Change would require modifying mailman/handlers/owner_recipients.py or possibly defining a sub-class of mailman.pipelines.OwnerPipeline which overrides the _default_handlers method and arranging for that to be used. -- 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: Member Issue Discovered

by Mark Sapiro

On 10/19/20 7:42 PM, Brian Carpenter wrote: > On 10/19/20 10:23 PM, Mark Sapiro wrote: >> And the import21 created the user and address records for this user. > > Does the same thing for a new subscriber as well. So there is no pathway > to change a real name that is associated with an email address. None. > Zilch. Mailman 2 made this so easy and Mailman 3 made it impossible. I > will let someone else file the bug report. You don't really think that > this is an issue which means it will be years before it is addressed. So > I will save me some time. I will learn to live with it. I didn't say I didn't think it was a real issue. I mostly questioned whether a new subscription should change an existing display_name. I agree that there should be a way for a user to change the display_name associated with her address. I'm not so sure about a list admin. And in any case, I'm only one person. I'm not the only one deciding what's important and what's not. I only decide what I want to work on, not what anyone else thinks is important or wants to work on, so even if I think something is not worth doing, that doesn't mean it won't get done, and once again for emphasis, I do thing a user should be able to change the display name associated with her address(es). Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman 2.1 had no concept of user. All it knew was addresses subscribed to lists and an address subscribed to one list had no connection to the same address subscribed to another list or being an owner or moderator of a list. Mailman 3 does have a concept of user and addresses belonging to a user. This complicates things in some ways. In Mailman 2.1 we could have "The Boss <user(a)example.com" as a member of one list and "Just a Peon <user(a)example.com>" as a member of another list. In Mailman 3 that is not possible unless the addresses are tweaked in some way to make them different. You don't seem to be concerned about the case where I subscribe to a second list with a different display name and am surprised to find my display name changed on the first list, but it's something that I have to consider. As far as filing or not filing an issue, issues in the GitLab trackers are how we track these things. Threads on mailing lists are appropriate for discussion of issues, but if something is going to get changed or fixed, an issue in the tracker is the way to ensure it doesn't get put aside and forgotten. If this is as important to you as it seems to be, please file the 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: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/5/21 6:43 AM, marcus.granath(a)gmail.com wrote: > > So what I basically try do achieve is to have only the following addresses to be allowed to send announcements (e-mails) on the mailman3 list, and all others that are member of the mailman3 list will just receive the e-mails. The usual "announcements" are sent out as the "no-reply" address (that actually are not really part of the mailman3 list) ;-) > > no-reply(a)abc.com ("fake address" that actually are not really part of the mailing-list) > peter(a)abc.com > david(a)abc.com > marcus(a)abc.com > > How to achieve this kind of filter with mailman3? Header filters is not the way to do this. First set both "Default action to take when a non-member posts to thelist" and "Default action to take when a member posts to the list" to either Hold for moderation or Discard (no notification). Reject is not recommended because of backscatter from spam posts with spoofed From: addresses. Then ensure all members Moderation Action is set to None or List Default (two names for the same thing). Now, no one can post. To allow your set of users to post, you have choices. The easy way but not secure against spoofing is to set the Maderation Action for the three allowed members to List Default and toi create a non-member for no-reply(a)abc.com and set it's moderation action to List Default. The more secure way is to leave everyone moderated, set a moderator password for the list and post with an Approved: header or pseudo header. 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

4 years, 3 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/27/22 01:23, Odhiambo Washington wrote: > > I have actually deactivated mine, and life is still good with my MM3. > > And just so that my mind is in the clear, there are three ways of getting > the full MM3 functionality, viz: > 1. Mailman core, Django's cluster, and Gunicorn > 2. Mailman core, Django's cluster, and uWSGI > 3. Mailman core, Django's cluster, and mod_wsgi Yes, and possibly there are other WSGI interfaces, but offhand I don't know. > And something that has not been quite clear to me: What is the purpose of > Django's cluster in all this? django_q <https://django-q.readthedocs.io/en/latest/> is an app for Django that can process tasks asynchronously in the background so they don't block the foreground. qcluster manages those tasks. > I am asking because on my FreeBSD server, I usually see not less than 30 > PIDs for: > > /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/django-admin > qcluster --pythonpath /opt/mailman/mm/ --settings settings (python3.9) > > And there is a time I found it having 240 PIDs. > Would there be a problem if I limit the number of workers to "8"? Some of those may be orphaned. On servers I manage, I regularly stop all mailman3 services to install updates and on one of these servers (only mail.python.org) where there are resource issues, when the services are stopped, there are still orphaned qcluster processes. I have this ``` #! /bin/bash if status qcluster | grep -q 'running' ; then echo qcluster is running exit fi ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill ``` to get rid of the orphans -- 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: GDPR - save subscriptions confirmation emails

by Mark Sapiro

On 06/03/2018 12:34 PM, contact(a)maadix.net wrote: > Thanks Selva for you answer. > > In my Mailman 3 installation there is no /var/log/mailman/subscribe Correct. Mailman 2.1 had a subscribe log. Mailman 3 does not. Many things are logged in the 'mailman' log, but subscription confirmations are not. > I have logs about confirmations emails in > mailman/var/logs/smtp.log > > the format is the following: > > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO > mails.example.com' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL > FROM:<contact(a)maadix.net>' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: > contact(a)example.net > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT > TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: > prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' > > So, one solution that comes to my mind is to grep this log file. > > This is not a perfect solution and the full confirmation email is still > missing. > > I am not sure if this would be GDPR compliant. Also, while I don't think it is currently possible to confirm a subscription via REST, not to mention Postorius, it may be in the future and this would bypass email all together. I think the best thing is to implement logging. Of course, you might be able to get your MTA to save all mail to the LIST-confirm address to a separate mailbox in addition to delivering it to Mailman. -- 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 to backup?

by Mark Sapiro

On 5/26/19 12:17 PM, Alain Kohli wrote: > Thanks for the great explanation, that helped a lot! I'll try to work on > that issue if I find some time. In the meantime it would be neat to try > to clean up the old messages right before the backup. How can you > distinguish messages that have been moderated already? I couldn't really > find that in the database or the models. You could run the following in `mailman shell` $ /path/to/mailman shell Welcome to the GNU Mailman shell >>> lm = getUtility(IListManager) >>> ms = getUtility(IMessageStore) >>> for mlist in lm.mailing_lists: ... requestdb = IListRequests(mlist) ... for rq in requestdb.held_requests: ... key, msgdata = requestdb.get_request(rq.id) ... if msgdata['_request_type'] != 'held_message': ... continue ... msg = ms.get_message_by_id(key) ... print(msg['Message-ID-Hash']) ... U6QVO2GXMEQ5ZDQR2XCLDOH2FXPKJTWX 32HA6GKYE5FOVORLER7YAC3264BHG264 JM4NP3JRXBKKAL7UMM5XEXX644DQBAFJ L7FX6XKOOBP3YFFXUHA6EEJCQXX5BCHX DOJX55MRY6OYPZ4XFFTAQDD4I5MWJ3AD >>> What that prints is the names of all the files in the var/messages/ hierarchy which are currently held messages. Presumably the others are ones already handled. You could modify the above to write the list to a file and then wrap the whole thing in a shell script which would make the list and then do something like for f in `find var/messages -type f`;do n=`cut -d / -f5 <<<$f` for keep in `cat list` ;do k=0 if [ $n == $keep ] ;then k=1 break fi done if [ $k -eq 0 ]; then rm $f fi done in the above, list is the list of names to keep bade by the first script and -f5 in the cut command assumes the list from find is lines of the form var/messages/TJ/YF/TJYF5FETCRLOQZJ2H6Y4PMZP6M7GNLES. i.e. two subdirectories between messages/ and the file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

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

by Mark Sapiro

On 9/16/22 10:49, Dan Caballero wrote: > > We're seeing some messages having the .bak files in the out queue for up to 30, 40 or even 60 minutes. I've increased the number of in and out runners to 8 each. Is there a way to know which runner has which message? If the .bak files eventually go away, this is because the message has a large number of recipients and delivery to the MTA is slow. For the out runner, look in Mailman's smtp.log for messages of the form: <message-id> smtp to <list> for nn recips, completed in tt.ttt seconds to see how long it's taking. If it seems too long (even with full VERP, it should be at least 5 to 10 recips per second), there are things you can do in the MTA to speed processing. In particular, don't do recipient validation at incoming smtp time - possibly configure an alternate submission port for Mailman to use. It shouldn't be necessary to slice the in runner and it processes very quickly. To answer your question, queue entries have a name of the form <timestamp>+<hex hash> with a .pck or .bak extension. The entry is assigned to a particular runner based on the first bits of the hash. For 8 slices this is the first 3 bits of the hash, so if the first hex digit of the hash is 0 or 1, that out queue entry will be processed by the out:0:8 runner; if it's 2 or 3, that out queue entry will be processed by the out:1:8 runner and so on through e or f processed by the out:7:8 runner. -- 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: Mailman 3 database restore unexpected behavior

by Mark Sapiro

On 3/28/23 04:00, Tibor Molnar wrote: > Mailman3 built from source using virtual environment. > Version: > GNU Mailman 3.3.8 (Tom Sawyer) > Python 3.9.2 (default, Feb 28 2021, 17:03:44) > [GCC 10.2.1 20210110] > config file: /etc/mailman3/mailman.cfg > > Issue: > I have restored the database number of times recently and experienced that every time after restoration (an hour after) all members getting an email that they are unsubscribed due to bounces, however non of the users are actually unsubscribed from any lists. It looks like there are duplicates in database and all the duplicates are getting unsubscribed? > > Bounces message: > name(a)email.com unsubscribed from [listname] mailing list due to bounces That's an admin notice, not a notice to the user. > Only restoring two files: mailman3 and mailman3web > > Did anyone come acroos this behavior ? This seems sort of like <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, but it doesn't seem like that would be the issue here. > It is not right that after restoring a database all 1000 user get an email that they are unsubscribed, but they are actually not. > I may do something wrong during the restoring process. > Please advise me. The code that decides which users are to be removed is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p…> Somehow you must be restoring members whose delivery status is disabled by bounce and whose total_warnings_sent is >= the list's bounce_you_are_disabled_warnings. What do you get from this query on the mailman3 database SELECT email FROM member JOIN address ON address_id = address.id JOIN preferences ON member.preferences_id = preferences.id WHERE delivery_status = 3 AND total_warnings_sent > 0; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 6/10/19 6:21 PM, andrew.bernard(a)gmail.com wrote: > is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it? What documentation there is is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > Anything I try to do such as the following fails: > > $ mailman shell > Welcome to the GNU Mailman shell > >>>> command('mailman shell --details') > Traceback (most recent call last): > File "<console>", line 1, in <module> > NameError: name 'command' is not defined >>>> You could just do `mailman shell --details` at a command prompt. Perhaps you saw the `command('mailman shell --details')` line in the docs at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> in any case, that requires two things to precede it. The first is part of the doctest infrastructure and is not evident in the docs. that step is from mailman.testing.documentation import cli The second step is in the docs and is command = cli('mailman.commands.cli_withlist.shell') If you do those two steps within `mailman shell`, then the step command('mailman shell --details') will work, but as I said, this is just the same as doing `mailman shell --details` at a command prompt. Beyond that, actually doing stuff within `mailman shell` requires some knowledge of Mailman interfaces, methods and objects as well as Python. Some of this is covered throughout the documentation at <https://mailman.readthedocs.io/en/latest/> but some can only be found in the source code itself. That said, all the interfaces and a few other useful functions are imported for you in `mailman shell` interactive mode. do `dir()` to see what these are. -- 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: The future is here?

by Mark Sapiro

On 1/3/21 3:47 PM, ieso(a)johnwillson.com wrote: > > Any ideas on what might cause that? More context below.. > > [uwsgi-daemons] respawning "python3 manage.py qcluster" (uid: 33 gid: 33) > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 356, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 206, in fetch_command > klass = load_command_class(app_name, subcommand) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 40, in load_command_class > module = import_module('%s.management.commands.%s' % (app_name, name)) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/lib/python3/dist-packages/django_q/management/commands/qcluster.py", line 4, in <module> > from django_q.cluster import Cluster > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 24, in <module> > from django_q import tasks > File "/usr/lib/python3/dist-packages/django_q/tasks.py", line 12, in <module> > from django_q.cluster import worker, monitor > ImportError: cannot import name 'worker' from 'django_q.cluster' (/usr/lib/python3/dist-packages/django_q/cluster.py) This is a django_q issue. Apparently <https://github.com/Koed00/django-q/issues/331>, fixed by <https://github.com/Koed00/django-q/pull/356> -- 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: disabled users

by Mark Sapiro

On 10/25/23 10:44 AM, Stephen J. Turnbull wrote: > Servizio Informatico U.I.C.I. Sezione territoriale di Brescia writes: > > > Wher I find the disabled user of a mailing list and wher I can > > reactivate them? > > If you are the list owner or superuser, when you visit the list's > information page there will be a horizontal menu across the top. One > of the entries is Users. Click to open the dropdown menu and choose > Members. There doesn't seem to be an explicit notation for disabled > users, but if the entry in the far right column "bounce score" is > None, the member may be disabled. I don't think this is correct. Members with delivery disabled by bounce will normally show 0 rather than None for bounce score. If you have shell access to the server as the Mailman user, you can run this shell interaction to find members with delivery disabled by bounce. ``` $ mm/bin/mailman shell -l test(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 test(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member.address.email) ... >>> ``` But the question is, why do you want to re-enable their delivery. Granted, there are situations such as a misconfigured MTA or not applying needed DMARC mitigations that could result in 'spurious' bounced deliveries, but normally bounce processing disables delivery, sends warnings to the bouncing address and ultimately unsubscribes them because the address it truly not deliverable. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Running Mailman3 v3.2.1 on Devuan 10.0, getting a pid permissions error on Mailman3-web

by Mark Sapiro

On 2/9/21 10:17 AM, rainbear(a)gmail.com wrote: > # service mailman3-web stop > [....] Stopping Mailman3-web uWSGI service: mailman3-webstart-stop-daemon: matching on world-writable pidfile /run/mailman3-web/mailman3-web.pid is insecure > > # ls -l /run/mailman3-web/mailman3-web.pid > -rw-rw-rw- 1 root root 6 Feb 9 13:00 /run/mailman3-web/mailman3-web.pid This would appear to be either a Debian or uWSGI issue. In my case, I use gunicorn as the WSGI interface to Django, and on the server that supports this list, I have > $ cat /etc/init/gunicorn.conf > description "gunicorn for Mailman" > > start on runlevel [2345] > stop on runlevel [016] > > respawn > respawn limit 10 5 > > setuid mailman > setgid mailman > > chdir /opt/mailman/mm/ > > exec /opt/mailman/mm/bin/gunicorn -c /opt/mailman/mm/deployment/gunicorn.conf mailman_web.wsgi:application > $ cat /opt/mailman/mm/deployment/gunicorn.conf > bind = ['127.0.0.1:8000'] > proc_name = "mailman-web" > chdir = "/opt/mailman/mm" > pidfile = "/opt/mailman/mm/var/gunicorn.pid" > accesslog = "/opt/mailman/mm/var/logs/access.log" > errorlog = "/opt/mailman/mm/var/logs/error.log" > #daemon = True > workers = 4 > # Increase timout to allow downloading large archive mboxes. > # Note even 300 is not enough for the entire python-dev(a)python.org archive. > # I added 'disallow: /*/export/' to robots.txt to try to stop crawlers. > timeout = 120 > $ ll /opt/mailman/mm/var/gunicorn.pid > -rw-r--r-- 1 mailman mailman 6 Feb 7 00:13 /opt/mailman/mm/var/gunicorn.pid Some other servers I manage use systemd rather than upstart, but the permissions on the PIP file are the same. -- 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: mailman3 exim4 and debian 1 problem fconnection lost

by Mark Sapiro

On 5/6/21 12:03 AM, roberto Burceni wrote: > [Mailman-Users] mailman3 and exim4 problem in debian bullseye > Good evening, > I'm configuring mailman3 with exim4 on a debian 11. > I followed the official documentation on mailman for exim. It seems to > be all rights, but I have a problem: > when I send a message to a new lists in exim logs I see that exim uses > correctly mailman router and transport. > Unfortunately in smtp.log in mailman3 log folder I have the following > error: > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) sender: > servizioinformatico(a)uicbs.it > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) Data: b'RCPT TO: > <listtest-unsubscribe(a)uicbs.it>' > > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) recip: > listtest-unsubscribe(a)uicbs.it > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) Data: b'DATA' > May 04 16:51:02 2021 (2337) ('127.0.0.1', 34746) Data: b'QUIT' > May 04 16:51:02 2021 (2337) ('127.0.0.1', 34746) connection lost > May 04 16:51:02 2021 (2337) Connection lost during _handle_client() > > This causes that messages are not sent from mailman to users. Have you > an idea of the problem? The connection lost messages are normal and not an error and not the cause of the message not being delivered to the list members. > I have no other errors in other log files What other log messages are there that might relate to this? Is mailman core running? Are there any entries in mailman's queues? Is the message Archived? Without more information, I can't say why the message isn't delivered. I can only say for certain the the smtp.log messages you show above are not related to the 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, 2 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/22/23 07:44, Stephen J Turnbull wrote: > From: "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> > To: ceo(a)sartrack.nz > ... > > > But it fails with this: > > MM3_LISTCHK=/var/lib/mailman3/lists/${local_part}@${domain} > > For reasons I do not understand, although Mailman 3 keeps list > configurations in the RDBMS, when it creates a list it *also* > "touches" a directory for that list in the directory $var_dir/lists. > (If I remember correctly, these are empty. It's a real directory, not > "virtual".) Since I already knew how to search for the > lists/$LIST/config,pck file used by Mailman 2, I used the same method > for Mailman 3. That directory is used to store messages being accumulated for the next digest in a digest.mmdf mailbox file. > $var_dir is set somewhere near the top of mailman.cfg. I don't know > where to find that file in your installation, it's often in > /etc/mailman3. `mailman conf -k var_dir` will show the setting for $var_dir for various layouts and `mailman conf -k layout` will show the layout in use. > Later you wrote: > > > mailman3 create templist(a)sartrack.nz templist.lists.sartrack.nz (?) > > I tried to create it as: > > create templist(a)sartrack.nz templist(a)sartrack.nz > > but it would not accept that. > > I believe that's because "mailman create" wants the posting address > and the list ID. It just wants the posting address, not the list ID. I.e. mailman create templist(a)sartrack.nz `create` is a subcommand of the `mailman command. `create` by itself as opposed to `mailman create` looks like an artifact from cPanel's Mailman 2.1. -- 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: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote: > There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value. I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log. > I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." What if you look at "threads by month" and select the current month? > Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago? As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job) -- 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: Creating superuser - problem with documentation or it's just me?

by Mark Sapiro

On 7/26/20 9:39 AM, Odhiambo Washington wrote: > Hi, > > In my quest to create a superuser, I followed another HOWTO - > https://docs.mailman3.org/en/latest/devsetup.html > > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# > python manage.py migrate > Traceback (most recent call last): manage.py migrate (or django-admin migrate) is part if the mailman-post-update script. It doesn't work here because when you run it this way, it doesn't get your settings.py. > ModuleNotFoundError: No module named '_sqlite3' And it's looking for sqlite3 because that's the default database. > *<==============================================================* > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# pip > install pysqlite3 You don't need this. You need to run django-admin with the correct settings. > So I figured out that I need to put my own settings_local.py into the > directory and let the command rely on MySQL as the database backend since > by default, it uses sqlite3 backend. > > But the question then is WHY is this not documented on the above page??? Because that's not relevant to what you are doing. You are trying to install Mailman for production, not development. > How can I delete the superuser after creating it?? The only django-admin or manage.py you should run is /opt/mailman/mm/bin/djhango-admin. You can run `django-admin createsuperuser` to create a superuser. If you want to delete one, you need to go to the Django admin web UI - should be http://your.server/admin - login as a superuser and go to the Users page and delete it. You should probably do this as a different superuser -- 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: Badsignature on uwsgi-error.log

by Mark Sapiro

On 3/22/24 09:48, David Partain via Mailman-users wrote: > > Right now, archiving is not working on the new installation, both building the archive on the new installation after the move and for new messages. > > uwsgi-error.log is getting blasted with constant errors along the lines of what follows. I suspect that these errors are why archiving isn't working, but I obviously don't know that: > > Message: BadSignature('Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match') I'm not sure if this is the issue with archiving or not. > What we have in our config files on the old installation and new installation are (the quotes are exactly as they are in the files): ... > settings.py > > SECRET_KEY = 'somerandomstringiaintputtinginmail' > MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' > > mailman-hyperkitty.cfg > > api_key: somerandomstringiaintputtinginmail > > All of that says that the value is the same for all three (whether I should have done so or not...) and those settings were carried along to the new installation as well. See my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… As I say there, SECRET_KEY is not related in any way to MAILMAN_ARCHIVER_KEY and api_key. The latter two have to do with archiving and must match. The former is a Django thing and is completely separate. At this point, put ``` SECRET_KEY_FALLBACKS = [ 'F6V0Dr_SvBsx5-cY8vcvLXrX8tA', 'ZWBXqQmWZwHTfa390lLIacpp8NQ', ] ``` in your local Django settings file. If you continue to get BadSignature: Signature "..." does not match' errors, add those unmatched signatures to SECRET_KEY_FALLBACKS. Once you are no longer seeing BadSignature errors, if archiving is still not working, report any errors you are seeing from Mailman's mailman.log and Django's log. -- 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: Does hyperkitty show JPEGs in line and what about attachments?

by Mark Sapiro

On 07/12/2017 04:47 AM, Jason Glazer wrote: > > Does anyone know if Hyperkitty can be configured to allow for inline > images to be maintained so that an HTML file looks like a normal HTML > message? > > Also, can attachments to a message under Hyperkitty preserve their name > rather than being "scrubbed" into "attachment-*.*" files? The answer to some of this is at <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DC…>. One question unanswered by that post is what happens with an inline image in an HTML message body. In the original message, the image is referenced by an IMG tag with "src=" pointing to the image MIME part. Since this structure is not maintained in HyperKitty, inline images probably don't work. Also, with respect to Mailman 2.1, if you want the scrubber to preserve file names and extensions, set the following in mm_cfg.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True and if you want scrubbed HTML to not be HTML escaped so it renders rather than looking like raw html, set ARCHIVE_HTML_SANITIZER = 3 but note this comment from Defaults.py > # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this > # is very dangerous because it essentially means anybody can send an HTML > # email to your site containing evil JavaScript or web bugs, or other > # nasty things, and folks viewing your archives will be susceptible. You > # should only consider this option if you do heavy moderation of your list > # postings. This is an issue with HyperKitty as it appears this is what HyperKitty does and there's no way to turn it off. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Link to account

by Mark Sapiro

On 4/11/23 12:04, Lars Bjørndal wrote: > Thanks a lot. Maybe I've done a mistake, it doesn.t work. > > At the bottom of /etc/mailman3/settings.py I have: > > ROOT_URLCONF = 'urls' > > `cat /etc/mailman3/urls.py` > > [...] > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('lists/mailman3/', include('postorius.urls')), > path('lists/archives/', include('hyperkitty.urls')), > path('lists/', include('django_mailman3.urls')), > path('lists/accounts/', include('allauth.urls')), > path('lists/admin/', admin.site.urls), > ] > > In Apache config for the domain, I now have: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" > ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives" > ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts" > ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin" > ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile" > </IfModule> > > Restarted mailmanweb, httpd and mailman3. > > If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser. > > So what's wrong, do you think? You followed https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… literally. The literal instructions where to access everything via URLs like https://mydomain.org/lists/.... If you were to replace `lists` with `mailman3` everywhere in the abpve, you would then access HyperKitty via a URL like https://list.punktskriftutvalget.no/mailman3/archives/ and Postorius via https://list.punktskriftutvalget.no/mailman3/mailman3/ If that's not what you want, it's more complicated and some things might not be possible. What exactly do you want for access to Postorius, HyperKitty, user accounts, user profiles and the Django admin UI? -- 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: log rotation for bounce.log

by Mark Sapiro

On 1/22/24 14:50, Quanah Gibson-Mount wrote: > I noticed that our smtp.log and bounce.log files haven't been rotated in > years. I see the reason for smtp.log not being rotated is due to > <https://gitlab.com/mailman/mailman/-/issues/931>. Does this same issue > affect bounce.log or is it safe to rotate similar to mailman.log? Rotating all the logs in Mailman's var/logs/ directory is appropriate. This is the logrotate script I use. ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate if [ -r /opt/mailman/mm/var/master.pid ]; then PID=`cat /opt/mailman/mm/var/master.pid` kill -s HUP $PID fi if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` You will still have the issue #931 in that the smtp.log will rotate, but as it says in that issue, the runners that write smtp.log directly will write to the new generation, but aiosmtpd continues to write to the older log until such time as mailman core is restarted. I'm not sure what will happen if mailman core is not restarted before the log aiosmtpd is writing to is rotated out of existence, but that could be an issue too. You could avoid this by replacing ``` if [ -r /opt/mailman/mm/var/master.pid ]; then PID=`cat /opt/mailman/mm/var/master.pid` kill -s HUP $PID fi ``` in the above postrotate script with ``` if [ -r /opt/mailman/mm/var/master.pid ]; then sudo -u mailman /opt/mailman/mm/bin/mailman restart &>/dev/null || true fi ``` but there is a potential issue in that if Mailman is delivering list mail when the `mailman restart` command is issued, some recipients may receive duplicates. -- 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: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 10:41, Bryan Fields wrote: > On 7/26/24 1:30 PM, Bryan Fields wrote: > >> mailman=> \c mailmanweb >> You are now connected to database "mailmanweb" as user "mailman". >> mailmanweb=> SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM >> date_active) < 1000; >> id | thread_id | date_active | >> category_id | mailinglist_id | starting_email_id >> -------+----------------------------------+------------------------+-------------+----------------+------------------- >> 35670 | GHLCKUC7TDEBAI27SKRQN5PWX3TGB26Q | 0102-04-15 20:06:12+00 >> | | 3 | 150555 >> (1 row) >> >> mailmanweb=> SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM >> date) < 1000; >> id >> -------- >> 136872 >> 150555 >> (2 rows) >> >> Does this mean it imported archives with an invalid date somehow? Yes, I suspect this bad date is part of the issue. I would do a few things. First, SELECT message_id FROM hyperkitty_email WHERE thread_id = 35670; If this returns just the one message_id, I would then DELETE FROM hyperkitty_thread WHERE id = 35670; DELETE FROM hyperkitty_email WHERE id = 150555; and see if that fixes the internal server error when accessing the archive. I would also SELECT * FROM hyperkitty_email WHERE id = 136872; and maybe update the `date` in that entry. After deleting that one message and thread, you can make a mbox with just the one message with the date corrected and run hyperkitty_import with `--since 2000-01-01` and that mbox as input to add the message back to the archive. Also, FYI, assuming those messages with very old Date: headers had reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script would fix them, except you have to get the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… or https://www.msapiro.net/scripts/cleanarch3 because the script in the latest release has a bug. -- 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: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 10/1/20 3:23 PM, Mohsen Masoudfar wrote: > Hi Mark, > Thanks again for the helpful hint. It seems that I still miss something. I am running Mailman3.1.1. I ran the following on my test server. > I am trying, for test purpose only, to filter PDF attachments. > > First I just used the pass_type, assuming once this is set, everything else is filtered. That's how it should work. > # mailman withlist testlist3(a)x.com >>>> m.pass_types = ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>>> commit() >>>> print(list(m.pass_types)) > ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] > > This let PDF be send by Mailman3. Well, I need to add filter_types too, so I did this: It shouldn't unless athe Content-Type: of the PDF part was text/* or application/pgp-signature >>>> m.filter_types = ['application/pdf'] >>>> commit() >>>> print(list(m.filter_types)) > ['application/pdf'] This should allow ONLY the PDF and nothing else, not even the text/* message body parts. > Mailman3 still distributes PDF files as attachment. What am I doing wrong? > > This is the final settings: > >>>> print(list(m.pass_types)) > ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>>> print(list(m.filter_types)) > ['application/pdf'] This is wrong. set m.filter_types =[] Look at the raw message you receive from the list. What is the VConten-Type of the PDF part? Actually, what's m.filter_content? I suspect it's False which means don't do any content filtering. -- 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: Request for help debugging a hyperkitty connection issue

by Mark Sapiro

On 1/6/22 12:12 PM, Stephen Daniel wrote: > > I have two problems. One is with getting list mail out of GCP. I am > working on that. The issue I don't know how to address is a problem with > hyperkitty. Nothing is being archived. When I send an email through my > test list, this message shows up in the mailman log: > > Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver > > Traceback (most recent call last): > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", > line 175, in _new_conn > > (self._dns_host, self.port), self.timeout, **extra_kw > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", > line 73, in create_connection > > for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): > > File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo > > for res in _socket.getaddrinfo(host, port, family, type, proto, flags): > > socket.gaierror: [Errno -2] Name or service not known > > > This triggers a bunch more tracebacks. > > Then I get this: > > Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed: > HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', > port=443): Max retries exceeded with url: /archives/api/mailman/archive > (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object > at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name > or service not known')) What is your setting for base_url: in mailman-hyperkitty.cfg?. Can you get wget -O- xxx where xxx is base_url with `api/` appended. This should return an html page of API documentation. If your base_url: seems good and its scheme is `https`, try changing it to `http`. -- 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: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/26/23 12:25 AM, mrl(a)psfc.mit.edu wrote: > I've asked the wrong question. The correct question is that my MM2 imported mailing list, shows the setting "Default action to take when a member posts to the list" is set to "Hold for moderation". That is expected because your MM 2.1 list had member_moderation_action = Hold. > However, when I add a user via Mass Subscription, and view the user in the member's list, it states "None" in the moderation column for him. Doesn't that imply, not to hold for moderation? Or am I wrong? No. That means apply the list's default. > Note that when I look at the user's "Administration options Moderation" personal setting, it is set to "List Default." I assume that because the List's setting in the above first paragraph is "Hold for moderation", that this means the "List Default" is set for moderating. And that newly added email addresses should be moderated. Or am I wrong? Newly added users get their moderation action set to None. This means the same thing as the List Default you see as an admin looking at the user. If you set the user to something other than List Default and then set it back to List Default, the actual value set for the member's moderation_action is None. I.e., List Default is a more admin friendly way of displaying/setting None for the value. Presumably, your MM 2.1 list had default_member_moderation = Yes and member_moderation_action = Hold and this mimics that behavior. -- 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: Flushing/syncing hyperkitty with mailman

by Mark Sapiro

On 06/16/2018 06:38 PM, Eric Abrahamsen wrote: > > > A bump for this, I've been getting this series of errors once a minute > for weeks now. There must be some way to clear out dangling thread > references? And I take it that for the meantime we shouldn't be using > the "delete thread" feature of hyperkitty... > >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] >> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >> [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] >> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >> [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> >> Is there something more I should be doing to sync hyperkitty's database >> with mailman? I've got the crontab file in place, and that appears to be >> running without error. Anything else? Except that 'django-admin runjobs minutely' is probably what's producing the errors. You might try 'django-admin runjob empty_threads' (normally a monthly job) or 'django-admin runjob thread_order_depth' (normally a yearly job). I don't know if they will clear this up or not, but I don't think it would hurt to try. See 'django-admin runjob --list' to see the various jobs and note that 'django-admin runjob update_index' which runs minutely and does an incremental update is not the same as 'django-admin update_index' which only runs manually and does a full search index update. -- 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: Problem with missing MySQLDatabase

by Mark Sapiro

On 10/19/18 3:44 AM, Peter Sørensen wrote: > Hi, > > I have looked into installing this before without success but found > The Debian package Mailman3-full > > I installed this succesfully along with the mailman-suite. > I have configured varios setting but are stuck when trying to generate aliases > For mailman with: > > mailman aliases > Traceback (most recent call last): > File /usr/bin/mailman, line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File /usr/lib/python3/dist-packages/mailman/bin/mailman.py, line 94, in main > initialize(config_path) > File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line 189, in initialize > initialize_2(propagate_logs=propagate_logs) > File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line 160, in initialize_2 > config.db = getUtility(IDatabaseFactory, utility_name).create() > File /usr/lib/python3/dist-packages/mailman/database/factory.py, line 52, in create > database = call_name(database_class) > File /usr/lib/python3/dist-packages/mailman/utilities/modules.py, line 67, in call_name > named_callable = find_name(dotted_name) > File /usr/lib/python3/dist-packages/mailman/utilities/modules.py, line 50, in find_name > __import__(package_path) > ModuleNotFoundError: No module named 'mailman.database.mysql.MySQLDatabase\t\t\t#MOD(inserted ) 02'; 'mailman.database.mysql' is not a package > > I can see from the message that I’m missing a module but I can’t figure out. how to get > This installed. The mudule is referenced in the mailman.cfg as > class: mailman.database.mysql.MySQLDatabase The module mailman.database.mysql is part of mailman core. In your case, it should be /usr/lib/python3/dist-packages/mailman/database/mysql.py. If that file exists, I don't know what the problem might be. If not, there is something wrong with your installation. In any case, this is a Debian issue. You need to take it up with Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

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

by Mark Sapiro

On 7/12/22 6:12 AM, skooperit(a)gmail.com wrote: > Hi all, > > I have a few contradictory questions. > > 1. How to upgrade the 3.x version? > > 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1? > > 3. If so, what would be the best way to do that? > > > My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: > > django-mailman3 1.3.5 > mailman 3.3.2 > mailman-hyperkitty 1.1.0 > mailman-web 0.0.3 > mailmanclient 3.3.2 > postorius 1.3.3 > > We have ~200 lists with more than a decade of history. So you have installed Mailman 3, apparently following https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a caveat. Current released versions of HyperKitty (I don't see your version above) don't work with mistune >= 2.0.0. This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet released. If your installed mistune is not 2.0.0rc1, you can work around this with this patch ``` --- a/hyperkitty/lib/renderer.py +++ b/hyperkitty/lib/renderer.py @@ -4,7 +4,7 @@ from django.conf import settings import mistune from mistune.plugins.extra import plugin_url -from mistune.scanner import escape_html, escape_url +from mistune.util import escape_html, escape_url class MyRenderer(mistune.HTMLRenderer): ``` Or you can downgrade mistune with ``` pip install mistune==2.0.0rc1 ``` in your virtualenv. To answer your questions, to migrate your lists, you use `mailman import21` and to migrate archives, `mailman-web hyperkitty_import`. Give these commands with the `--help` option for more info. Downgrading lists from Mailman 3 to Mailman 2.1 is not currently possible. There is no inverse to `mailman import21`. You can export a HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. -- 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: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 11:04 AM, Ken Alker wrote: > > I've just taken on the project so I'm new to all of this, and one thing I noticed that caught my eye, and has left me curious, is that for the first a couple of seconds starting just after midnight every night (just after log rotation) mailman.log would have many (dozens, or hundreds) of lines entered in it just like this one: > > Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET /3.0/users/old-user(a)domain.tld HTTP/1.1" 404 58 > > where "old-user(a)domain.tld" is the email address of a user who either had unsubscribed or changed their email address (I don't know which, I just know they are no longer a member/subscriber to the list). Each successive entry in the log would have a different "old username" in it. I don't understand why these entries would be in the log and what they mean. Can someone shed some light on this for me? This is merely a question of curiosity, and not one of import. (Since migrating from 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.) This is the Django hyperkitty sync_mailman job which is one of the django admin jobs run daily. It goes through the HyperKitty 'sender' database table and tries to find the Mailman core user id for each sender address to add/update its mailman_id field with core's user_id. The 404s are addresses im HyperKitty's sender table for whih there is no corresponding Mailman user. There are multiple possible reasons for this. If the behavior has stopped it's probably because the periodic Django jobs are not being run - this is bad. -- 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: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > Hi Team, > > I am currently running Mailman 3 with version 3.3.2rc2 and in > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > with default values. As of now, we don't have any lists and just installed > software components only. > > After the installation and configuration, I have tried > creating the domains and lists. I was successful in creating them but when > I tried to login and browse the lists using LDAP authentication, I am > getting the "Mailman REST API not available. Restart Mailman core". > > I see the below trace in the mailmansuite.log. > > *Traceback (most recent call last): File > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ return self._get(name) File > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count ... > > I don't see any error messages in the mailman.log. And I > also executed a few curl commands in getting the details of the lists > created and list info which I got their results successfully. > > Could you please guide where exactly I am missing or do I > need to make any changes in my customizations ? I think the issue is your mailmanclient is too old. The version of Postorius you are running requires mailmanclient >3.3.1 which is only available from GitLab <https://gitlab.com/mailman/mailmanclient>. What version of Postorius is this? It appears to be >1.3.3. If you install Postorius from unreleased code on GitLab, you have to install all of mailman, mailmanclient and django-mailman3 as well. -- 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: Error while Approving a Post Through Email

by Alex A.J.

Hi Mark, Thanks for the reply. Didn't set the moderator password for the list. I was using the same password used for logging in to the UI. Let me see if I can properly set it up as you mentioned. Thanks. Alex. On Thu, Dec 15, 2022 at 5:11 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/22 09:41, Mark Sapiro wrote: > > > > I don't have more time to look at this now, but I think it's a bug. This > > patch > > ``` > > --- a/src/mailman/rules/approved.py > > +++ b/src/mailman/rules/approved.py > > @@ -140,6 +140,7 @@ class Approved: > > mpw = mlist.moderator_password > > else: > > mpw = mlist.moderator_password.decode('utf-8') > > + mpw = config.password_context.encrypt(mpw) > > is_valid, new_hash = config.password_context.verify(password, > > mpw) > > if is_valid and new_hash: > > # Hash algorithm migration. > > ``` > > may fix it. > > > It is a bug, but that isn't the correct fix. The list's > moderator_password attribute should already be encrypted. The bug is we > don't catch the passlib.exc.UnknownHashError. > > It appears you either have not set the lists moderator_password or you > have not set it to a properly encrypted value. Did you set it and if so, > how? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to malayalamtex(a)gmail.com >

2 years, 7 months

[MM3-users] Re: Random lmtp Timeout and Long Message Processing times

by Mark Sapiro

On 1/9/25 11:05, Taber, Douglas R via Mailman-users wrote: > Still stumped on this one, is there a way to increase the lmtp logging beyond debug? > > I’m trying to figure out what is causing the hang for incoming messages here: > > > Jan 09 13:38:32 2025 (342305) ('127.0.0.1', 48466) << b'250 OK' > > Jan 09 13:38:32 2025 (342305) _handle_client readline: b'RCPT TO:mailman@lists.renci.org<mailto:mailman@lists.renci.org>\r\n' > > Jan 09 13:38:32 2025 (342305) ('127.0.0.1', 48466) >> b'RCPT TO:mailman@lists.renci.org<mailto:mailman@lists.renci.org>' > > Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) recip: mailman(a)lists.renci.org<mailto:mailman@lists.renci.org> > > Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) << b'250 Ok' > > Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) EOF received > > Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) connection timeout > > It just hangs there until a timeout, then retries and immediately succeeds All those messages are actually logged by aiosmtpd which does the bulk of the work of lmtp runner. There are multiple modules involved here. Mailman's lmtp runner uses the aiosmtpd LMTP class which is a subclass of the aiosmtpd SMTP class which in turn is a subclass of asyncio.StreamReaderProtocol which is reading data from the socket connecting to the incoming MTA. It seems that after the MTA sends the `250 Ok` response to the `RCPT TO:` command the MTA closes the connection and asyncio.StreamReaderProtocol calls the eof_received method resulting in the `EOF received` log message and ultimately the timeout. Have you looked at the MTA logs? If there's not an answer there, that's where you should look to increase logging. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

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

by Mark Sapiro

On 7/8/21 2:01 PM, Sarah H wrote: > > here are the current configs and the files in spool. > > in var/archives/hyperkitty/spool/ > > -rw-rw---- 1 mailman mailman 5.9K Jul 8 13:55 1625777713.5186543+0b1e6ae782342e699116994a4cc5968e8e01701c.pck > -rw-rw---- 1 mailman mailman 5.8K Jul 8 13:55 1625777713.642453+2e79e4d69d3f91f72646af26822566116a98f92e.pck There should be errors in Mailman's mailman.log for these. You can see the actual message in the .pck by pointing `mailman qfile` at it. > mailman.cfg: > ... > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /etc/mailman3/mailman-hyperkitty.cfg OK > mailman-hyperkitty.cfg > > # This is the mailman extension configuration file to enable HyperKitty as an > # archiver. Remember to add the following lines in the mailman.cfg file: > # > # [archiver.hyperkitty] > # class: mailman_hyperkitty.Archiver > # enable: yes > # configuration: /path/to/here/mailman-hyperkitty.cfg > # > > [general] > > # This is your HyperKitty installation, preferably on the localhost. This > # address will be used by Mailman to forward incoming emails to HyperKitty > # for archiving. It does not need to be publicly available, in fact it's > # better if it is not. > # However, if your Mailman installation is accessed via HTTPS, the URL needs > # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty) > base_url: https://lists.siteurl.org/archives/ I assume that you have the real URL to hyperkitty here. I'm not sure, but https might be an issue. > # Shared API key, must be the identical to the value in HyperKitty's > # settings. > api_key: thisisnotreallymykey > > settings.py > ... > MAILMAN_ARCHIVER_KEY = 'thisisnotreallymykey' OK It looks OK. You should now see log messages regarding the messages in var/archives/hyperkitty/spool/. They should help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 3/20/19 7:50 AM, Henrik Rasmussen wrote: > I assume this is by design, but is it correct that a list owner, who are not member, will always be allowed to post to the list, even though "Default action to take when a member posts to the list" and "Default action to take when a non-member posts to thelist" are both set to "Hold for moderation"? The owner is set as also moderator, by the way, which seems redundant. I have tried this in multiple ways: list with no members and owner X, post from X list with member Y and owner X, post from X list with member Y and owner X, moderator X, post from X In all three cases the post was held with reason "The message is not from a list member" and the expected notices were sent to the owner and poster. Note that the test for membership includes lots of addresses. The first group are the addresses in places defined by the config sender_headers in the [mailman] section which defaults to The From: header The envelope sender The Reply-To: header The Sender: header Then, for each address found, if the address is a member or if the address has a user record and any of the users addresses is a member, the post is considered to be from a member. However, this is apparently not relevant because both the Member and Non-Member actions are Hold. Thus, the post should be held unless it has an Approved: header with the list's moderator_password attribute if there is one, or it matches a Header filter rule with an accept action. What are the headers X-Mailman-Rule-Misses: and X-Mailman-Rule-Hits: in the message 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

6 years, 4 months

[MM3-users] Re: Imported Digest Settings

by Mark Sapiro

On 2/16/21 7:56 AM, Brian Carpenter wrote: > I am still seeing digest formatting issues with the import of Mailman 2 > lists into Mailman 3. I am running the latest stable version of Mailman > 3 core which is 3.3.3. This is what my client reported: > > >> For the last three REDACTED digests I have been getting unusual and >> unreadable characters? See example below. >> >>> Begin forwarded message: >>> >>> *From: *REDACTED >>> *Subject: *REDACTED*Digest, Vol 2453, Issue 2* >>> *Date: *February 13, 2021 at 12:30:24 AM PST >>> *To: *REDACTED@REDACTED >>> *Reply-To: *REDACTED@REDACTED >>> >>> �P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ ... > > So the questions I have are: > > 1. Why does the formatting of digests change for some members when > coming from MM2 to MM3? Could this be <https://gitlab.com/mailman/mailman/-/issues/473>? That should be fixed in Core 3.3.3. > 2. What proble does the above example reveal? Insufficient headers to begin to guess. > 3. What is the best approach to mitigate these issues? Depends what the issue is. The two most obvious approaches are upgrade to Mailman 3.3.3 if you aren't already there and switch from plain to MIME digests, but I would really like to see the full raw source of this digest messages to try to see if there is some other issue. > What I did: I had the client change the list member's digest setting > from plain-text to mime. Was that the right instruction to do? It will probably help, but if this is Mailman 3.3.3, there's still a bug somewhere that needs to be diagnosed and fixed. -- 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: missing graphics in Postorius

by Mark Sapiro

On 12/6/21 10:15 PM, David Newman wrote: > After installing MM3 on Debian 10 using the venv docs, no graphics > appear in the admin or list pages, just broken links. > > The mailmanweb log has lines like this: > > ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost > Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' > to ALLOWED_HOSTS. > > which is odd because there is the line for "localhost" in settings.py, > and /etc/hosts correctly ties this to 127.0.0.1. Add '127.0.0.1' to ALLOWED_HOSTS anyway. > There are entries like this in /var/log/nginx/error.log saying the files > just aren't there: > > 2021/12/06 22:00:30 [error] 18123#18123: *65 open() > "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" > failed (2: No such file or directory), client: x.x.x.x, server: > somehost.example.com, request: "GET > /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: > "somehost.example.com", referrer: > "https://somehost.example.com/mailman/lists/" > > (I've obfuscated names and addresses here, but "somehost.example.com" > refers to a valid FQDN in the log.) > > I thought I'd followed all the venv docs, but the > /opt/mailman/web/static/postorius directory doesn't exist. Did I miss > something? Assuming you have ``` STATIC_ROOT = '/opt/mailman/web/static' ``` in your /etc/mailman3/settings.py file, you may need to create that directory if it doesn't exist. You shouldn't need to manually create the /opt/mailman/web/static/postorius directory if the /opt/mailman/web/static directory exists and is writable/searchable by the Mailman user. That should enable ``` (venv)$ mailman-web collectstatic ``` to populate that directory. Be sure you've run all four commands at https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… et seq. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

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

by Mark Sapiro

On 5/31/23 22:49, justfixit(a)marilynstrother.com wrote: > FWIW, looking back at this time period in mailman.log the only instances of "runner exiting" are in groups, at the times when I had manually issued "mailman restart" to try a few different debug logging options. I.e. there was no single / multiple record of "runner exiting" from e.g. an unexpected program fault. When you issued a restart and the logs show runners restarting, did all the runners restart or was one or more missing. If you grep the log for `runner started`, you should see groups of messages like Jun 01 08:00:27 2023 (21930) in runner started. Jun 01 08:00:27 2023 (21938) virgin runner started. Jun 01 08:00:28 2023 (21932) bounces runner started. Jun 01 08:00:28 2023 (21935) command runner started. Jun 01 08:00:28 2023 (21941) retry runner started. Jun 01 08:00:28 2023 (21934) archive runner started. Jun 01 08:00:28 2023 (21931) lmtp runner started. Jun 01 08:00:28 2023 (21942) pipeline runner started. Jun 01 08:00:29 2023 (21939) out runner started. Jun 01 08:00:29 2023 (21936) digest runner started. Jun 01 08:00:29 2023 (21937) nntp runner started. Jun 01 08:00:30 2023 (21940) task runner started. and if any runners are sliced, there will be multiple entries for that runner, one per slice. Also, because of the way the `rest` runner is run, it will be in the list on a start but not on a restart. If a runner had previously died so it was not running when you did the restart, it won't be started and will be missing from the above list. In order to restart runners which have died, you need to do `mailman stop` followed by `mailman start` as opposed to `mailman restart` -- 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: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/10/25 18:30, MegaBrutal via Mailman-users wrote: > > Thanks, I successfully removed my unwanted address, so it now doesn't > appear anywhere. (Looks like .remove(n) wasn't needed, it only gave an > exception, and the settings were saved even without commit() – which is > concerning because I would have assumed that I can cancel transactions by > omitting it.) As it says when you first invoke `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. > However, the problem still persists: I can't post to the list from > HyperKitty. In this regard, nothing has changed since my original report. > I'm subscribed to the list with my primary, preferred address, which is the > GMail address right now. So your gmail.com address is a list member and your megabrutal.com address is only an owner. Is that correct? What if you add your megabrutal.com address as a list member - you can set delivery to disabled if you don't want it to get mail. Does that work? How are you logging in to the web UI. I am concerned, because if you are logging in to an account that has both addresses linked, you should see the ``` This message will be sent as: user(a)example.com Link another address ``` line below the text box in the message dialog and if you click on user(a)example.com, you should be able to pick the other address. Also, if you go to https://example.com/user-profile/ you should see a Primary email: and Other emails:. Do you see that? -- 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: Not able to start mailman server

by Mark Sapiro

On 8/5/21 12:53 AM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to setup postorius using this website - > > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/docs/W... That documentation is out of date. Start at https://docs.mailman3.org/en/latest/ > I am trying to create a mailling list and it web interface for the users in my group > > The command 'pip install -e ./'(python3) runs successfully but still i am not able to start the server Is the result the same as in your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, i.e., /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > my mailman info shows - > > GNU Mailman 3.3.5b1 (Tom Sawyer) > Python 3.9.5 (default, May 4 2021, 03:36:27) > [Clang 12.0.0 (clang-1200.0.32.29)] > config file: /Users/.../Documents/mailman/var/etc/mailman.cfg > db url: sqlite:////Users/.../Documents/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass We recommend following this guide https://docs.mailman3.org/en/latest/install/virtualenv.html What is the content of the /Users/.../Documents/mailman/var/etc/mailman.cfg file? The 'pip install -e ./' command should have created a bin/ directory containing both `mailman` and `master` executable files and this `mailman` command is the one you should be running. It appears the `mailman` command you are running is '/usr/local/opt/python(a)3.9/bin/mailman'. If that is in fact a symlink to a different bin/mailman file, there should also be a symlink from '/usr/local/opt/python(a)3.9/bin/master' to the existing bin/master or you should adjust your path. What do `which -a mailman` and `which -a master` 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, 11 months

[MM3-users] Re: Is there a reason not to implement the config_list command ?

by Mark Sapiro

On 6/10/18 11:54 PM, Asaf Ohayon wrote: > > Is it meant to be implemented ? > and if so, how is it recommended to do > (for someone new to mailman 3 programming) It depends what you are looking for. The Mailman 2.1 config_list command can do quite a lot. It has both an output (config dump) mode and an input (config load/alter/etc) mode. It would be a simple matter to implement a mailman sub-command to dump a list's config if all you want are list attributes and their values. If you want all the commentary that config_list produces, that is more difficult because config_list basically gets all that from the Mailman 2.1 web UI and in Mailman 3, the web UI is decoupled from the core and the core really knows nothing about it or if it even exists. You would need to get it from the various interface definitions in mailman/interfaces/mailinglist.py. For the input mode if all you wanted to support was input containing lines of the form attribute=value that wouldn't be too difficult to do, but config_list can to much more because it makes the list object available to the input script so the input script can do anything at all to the list. So, as I said, it depends on what config_list functionality you are looking for. If what you want is a way to configure a list for a particular "style", Mailman 3 has a concept of List Style to be applied when the list is created. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. This, rather than config_list is intended to be the way to configure a particular list style. -- 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: MM2 to MM3 on debian 10

by Mark Sapiro

On 4/27/20 8:26 AM, Gelpi Andrea wrote: > Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 > mailing lists. I know that not all can work. > > In my old lists I have email and regular expressions in > reject_these_nonmembers and discard_these_nonmembers > > After importing the list all these email are in non member list. > > All these email have Delivery status enabled. Delivery status is not relevant for non-members and only has to do with receiving list posts in any case. What version of Mailman core is this? There have been changes in `mailman import21` that may affect this, but an address in `reject_these_nonmembers` should be imported as a non-member with a moderation action of `reject` and similarly for `discard`. Note that regexps in *_these_nonmembers should be imported into the MM 3 legacy *_these_nonmembers attributes. Some older versions of import21 also imported non-regexp addresses here, but that was wrong. > Does this mean that all of them will receive any message sent to the list? > The moderation rule is correct, but if I understood correct Delivery > status should be disabled. Delivery status is irrelevant for non-members. Only members are candidates for delivery. > For migration I followed this link > https://docs.mailman3.org/en/latest/migration.html > > To migrate archives it states to run > > python manage.py hyperkitty ... > > I cant' find a manage.py on debian 10 manage.py is a Django generic term for the Django admin command. You probably want something called django-admin or similar. > A search shows the only /usr/share/mailman3-web/manage.py exists. > > Is there any documentation specific for debian? That would be up to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: bulk deletion of messages from Hyperkitty

by Mark Sapiro

On 7/10/24 12:27 PM, Danil Smirnov via Mailman-users wrote: > > I'm aware of the tools you mentioned and they were properly used. Your issue is almost certainly caused by unescaped `From ` lines in message bodies and preprocessing the mbox with the hyperkitty/contrib/cleanarch3 script should fix those. > Please let us focus on the question I asked - how do we delete messages of > a particular date if there are too many of them so using Hyperkitty UI > isn't an option? You can do ``` DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; ``` but as you note there are entries in the hyperkitty_thread table that need to be removed too. So, before doing the above, maybe something like ``` DELETE FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>); ``` but there are also possibly entries relating to these messages/threads in the hyperkitty_favorite, hyperkitty_tagging, hyperkitty_lastview and hyperkitty_vote tables. It seems unlikely that there would be such entries in your case, but if you are concerned about them, here in order are what you can do in the database. ``` DELETE FROM hyperkitty_favorite WHERE thread_id IN (SELECT id FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>)); DELETE FROM hyperkitty_tagging WHERE thread_id IN (SELECT id FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>)); DELETE FROM hyperkitty_lastview WHERE thread_id IN (SELECT id FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>)); DELETE FROM hyperkitty_vote WHERE email_id IN (SELECT id FROM hyperkitty_email WHERE archived_date = <your datetime>); DELETE FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>); DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; ``` -- 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: How to set the original sender to the Reply-To?

by Mark Sapiro

On 9/12/20 9:51 AM, Marcel Pietschmann wrote: > Hi everybody, > > I have a settings problem. Mailman adds the original sender to the Reply-To or Cc in the case where there's a reply to setting in force on the list. > > In my case, mailman sets the sender always to Cc. How can i change it? > > My settings: > Personalize = None > Anonymous list = No > Reply to list = No Munging > DMARC = Munge the From: header with list adress When DMARC is set to Munge From, Mailman puts the poster's address in either Cc: or Reply-To: to facilitate replying to the poster. The decision of which header to add the poster's address to is made to, as closely as possible for most MUAs, make the behavior of a 'reply' match the behavior when the From: is not munged. See the comments at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc…> for discussion of the goals for Munge From. The actual decision as to which header to use is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc…>. That says that the original From is added to Cc: whenever Reply to list is other than No Munging. You say that you have Reply to list = No Munging which means the original From should be added to Reply-To: and not to Cc:, so I don't understand why it's added to Cc: in your case. I have tested locally and with Reply to list = No Munging, the original From: is added to Reply-To: and with Reply to list = Reply goes to list, the original From: is added to Cc: as expected. -- 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: psycopg2 error?

by Mark Sapiro

On 10/26/23 01:03, Odhiambo Washington wrote: > > <CUT> > root@debian12:/home/wash# systemctl status mailman3.service > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Thu 2023-10-26 09:36:41 EAT; > 8s ago > Process: 1893842 ExecStart=/opt/mailman/venv/bin/mailman start > (code=exited, status=1/FAILURE) > CPU: 789ms > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: dbapi = > dbapi_meth(**dbapi_args) > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: > ^^^^^^^^^^^^^^^^^^^^^^^^ > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > line 690, in import_dbapi > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: import psycopg2 > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line > 51, in <module> > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: from > psycopg2._psycopg import ( # noqa > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: SystemError: > initialization of _psycopg raised unreported exception > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Control > process exited, code=exited, status=1/FAILURE > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Failed with > result 'exit-code'. > Oct 26 09:36:41 debian12.wash.lan systemd[1]: Failed to start > mailman3.service - GNU Mailing List Manager. > </CUT> Is your database PostgreSQL or some other? If it's not PostgreSQL, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… - particularly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Also see https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it now says in part "This will install latest release of Mailman Core, and Python bindings for Postgresql database. If you are using a different database manager, do not install psycopg2-binary." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/28/25 19:40, Mark wrote: > > I have jumped the gun on thinking that the template as a file was > working. It's not. It's the same story: the initial file template is > good, but it's for sure getting cached somewhere, and an updated file is > ignored. The same as when the template was being drawn from the database. Are you just updating the file /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt with nothing in Postorius and either no entry at all in the mailman.template table with name = 'list:user:notice:welcome' context = 'testlist.example.com' or if there is such an entry, with uri = 'file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use…' If so, editing the file /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt should work. > Restarting mailman3 and mailmanweb didn't help, neither did rebooting > the server. > > Looking at Gunicorn status, I see a failing connection to 127.0.0.1 > which is the error message I was getting when adding a new subscriber - > with the custom Welcome template in the database (which is why I moved > it to file). > > 127.0.0.1 and locahost are in the ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS > of the settings.py file > > I'm at a loss with this caching problem. Any other clues happily received. If as I say above, there is no entry in the mailman.template table for the name and context or if there is an entry with uri = 'file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use…', then gunicorn and mailman-web are not involved at all - mailman core will get the template from the file directly. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[MM3-users] Re: Default values for new lists

by Mark Sapiro

On 1/10/20 11:16 PM, hansen(a)rc.org wrote: > I just moved from MM2 to MM3. I have some 50 lists I need to configure and they all need the same settings (private archives, max 2 recipients, etc.). I often add and remove lists. I'm pleased that I now can set domain-level templates, but I really need domain-level default list settings as well. > The archived 'Deault values for new lists' thread indicates that a new version is needed to get this into the UI. Is there a back-door way to alter these defaults in the mean-time? For lists you import from Mailman 2.1 using the `mailman import21` command, the Mailman 2.1 list settings are applied to the Mailman 3 list. As far as new lists you create in MM 3 goes, you can define more styles to be applied to newly created lists. See <https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. However, you can't just create a style via `mailman shell` as described there because it won't persist. You need to create a plugin that implements the style. See <https://mailman.readthedocs.io/en/latest/src/mailman/plugins/docs/intro.html> for info on this. Note the Components section discusses adding a plugin implementing an IRule, but one implementing one or more IStyle classes would be similar. Another possibility, which I haven't tested but which may work is to create Mailman 2.1 lists with the desired styles, but no members, owners, moderators, etc and save their config.pck files. Then you should be able to apply those settings to a Mailman 3 list using the `mailman import21` command. This will probably still require fixing some things on the MM 3 list such as Description, Information, Display name and Subject prefix, but it may help. -- 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: Attachement processings questions

by Mark Sapiro

On 2/3/20 4:27 AM, Lars Schimmer wrote: > > In a mailinglist it seems some mails are not forwarded to a member, but > is listed in archive in hyperkitty. > That mail did include a PDF attachement, but HyperKitty does not list > any attachement. There are two issues here. Why wasn't the message delivered to list members?, and why is there no attachment in Hyperkitty? For the first issue, you need to examine mailman.log for the time of the post looking for errors and tracebacks. Also, the MTA logs may have useful info if the messages were sent but not delivered. For the second, there are many content filtering settings not (yet) exposed in Postorius. These include filter_extensions, filter_types, pass_extensions and pass_types which control which MIME parts are removed. For a newly created Mailman 3 list, these four settings are empty, but importing a Mailman 2.1 list will set them according to the corresponding MM 2.1 list's settings. > All I found was "convert HTML to plaintext", but does this setting > remove attachements? It would only affect HTML parts, not pdfs. > Is there any generel documentation about attachement processing in MM3? <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filterin…>. > I would like this mailinglist to accept mails with attachements, send it > to the members and archvie the attachments in HyperKitty, to. You can set Settings -> Alter Messages -> Filter content to No in Postorius to not do any content filtering at all. This will override the Collapse alternatives and Convert html to plaintext settings and pass the message without removing any MIME parts. But, I think you must have other issues, either with this mail in particular or in general as evidenced by the mail not being received by list members. -- 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 auto-disabling of subscriptions

by Mark Sapiro

On 6/16/23 20:04, Mike Wertheim wrote: > Thanks for the response. > > A while back I experimented with enabling verp-probes. The users on the > list were confused by the probe emails and sent me a lot of messages asking > about them, so I disabled it. But at least their delivery wasn't being disabled because the probes weren't being bounced. Further, the first sentence in the body of the probe is "This is a probe message. You can ignore this message." If you think the probe could be more explanatory, you can always set a list:user:notice:probe template to say what you want. > There is zero spam on the list. Ill try reducing "bounce info stale after" > to "2d". (Actually, would "1d" be even better?) Suppose you set it to 1d. This means that in order for a true bouncing user to have delivery disabled with threshold = 5 There have to be posts every day for 5 consecutive days. If it's set to 2d, there can only be one day out of 6 with no posts for a true bouncing user's delivery to be disabled. If you can't guarantee that condition, you might as well just set Process Bounces to No. I would ensure Notify owner on bounce increment and Notify owner on disable are set to Yes. Then, assuming Mailman core >= 3.3.5, when users scores are incremented the owner will get a notice containing the bounce DSN. With that information, you can figure out why these valid addresses are bouncing the mail. Or, if the bounces occur during your outgoing SMTP, your MTA logs will have the reason. Given that information, you may be able to fix whatever is causing the delivery issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Mailman stopping message distribution because of SMTP errors

by Mark Sapiro

On 2/11/20 10:28 PM, Victoriano Giralt wrote: > > I have recently migrated some lists from Mailman 2 to Mailman 3. Users have > been added using the mailman client as pre-verified addresses so the > migration happened "silently". Thus, there was a dozen "bad" addresses > (domains that did not exist anymore). It seems you rolled your own instead of using `mailman import21`. Is there a reason for this? > Unfortunately, Mailman got some of the "bad" addresses in the first message > batch for sending out, so, Postfix closed the connection because of "too > many errors" and this stopped the process completely, i.e. Mailman did not > continue sending messages to the rest of the list over 600 addresses. Is the message shunted? Is there a traceback and a shunting message in mailman.log? Normally, I would expect the message to be queued in Mailman's retry queue and retried by Mailman > There was no more information in the logs than the Postfix error messages > in smtp.log. What was in the smtp.log? Nothing in mailman.log? Nothing in var/queue/shunt? > Once the "bad" addresses were removed, the list started working as > expected. > > I consider this a bug. The bouncing addresses should have been marked as > "non deliverable" and the subscriptions "paused" and the rest should have > been delivered. Or, the list owner should have been notified that there was > a problem with message distribution. None of these happened. The HEAD of the https://gitlab.com/mailman/mailman master branch implements bounce processing. This will be in 3.3.1 which is not yet released. The place for a bug report is <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, 5 months

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

by Mark Sapiro

On 2/25/21 9:38 AM, dancab(a)caltech.edu wrote: > Mark, > > Is it only this list that has an issue? > > Yes, this is the only list that is having the issue. > > Can you visit other pages for this list? > > Yes, I'm able to view the members list, list settings, templates, etc. > > I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. > > > ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen > chunked=chunked, > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib64/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response This is from Django's log. What's in Mailman core's mailman.log? Since everything else is accessing the REST API with no problem, I think core must be stuck on something and timing out. Is there a time delay between trying to get the held messages view and the "Mailman REST API not available. Please start Mailman core." response? Also is there a non-zero count in the badge on the Held messages tab? -- 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

Search results for query "sapiro"