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

[MM3-users] Re: Newbie hyperkitty question

by Mark Sapiro

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

3 years, 6 months

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

by Mark Sapiro

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

3 years, 6 months

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

by Mark Sapiro

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

2 years, 2 months

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

by Mark Sapiro

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

1 year, 10 months

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

by Mark Sapiro

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

1 year, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, I got postfix installed and I can use the command mail to send emails. The thing is that mailman can't send the confimation mail yet, where should I look for the error?? Thanks El mar., 25 jul. 2017 a las 16:14, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:43 PM, Rafael Mora wrote: > > Ok, should I install the SASL authentication daemon saslauthd and start > it? > > > Probably not. > > If you are trying to configure Postfix to send via a remote server, see > <http://www.postfix.org/SOHO_README.html#client_sasl_enable>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

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

by Mark Sapiro

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

3 years, 6 months

[MM3-users] Re: Email verification

by Allan Hansen

Yep. That did it! Thank you! Yours, Allan Hansen hansen(a)rc.org > On Feb 9, 2020, at 13:41 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/9/20 1:29 PM, Abhilash Raj wrote: >> >> Finally, if you go into the Django’s admin interface, https://example.com/admin, you’ll find an EmailAddress table, where you can find and manually verify the user’s email address (check box to select “verified” and hit save). > > > Note that you need to click the user's address in the list to get the > page where you can verify it. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 5 months

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

by Mark Sapiro

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

4 years, 10 months

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

by Mark Sapiro

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

8 years, 4 months

[MM3-users] Re: Problem replying via Hyperkitty

by Mark Sapiro

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

3 years

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

by David Partain

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

4 years, 4 months

[MM3-users] Re: clarifying configuration

by Mark Sapiro

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

5 years, 1 month

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/2/25 17:21, Steve Brown via Mailman-users wrote: > In a list I administer, the From line in an incoming email shows [Poster's Name] via [List Name] <address for posting a reply> . I use Outlook as my client, but at least some other clients behave similarly. However, I have at least one subscriber who uses Mozilla's Thunderbird as his client, and periodically the format changes to something else, most recently to just [List Name <address for posting a reply> . I suspect this occurs from some combination of the way Thunderbird parses the header and the way it populates some kind of address book that makes autofill work, but I'm not sure. Is this a known problem? Is there an easy fix that will be stable? In the past, putting an association in his address book and removing others worked, but it didn't hold and he is frustrated. This From: is the result of DMARC mitigations. The actual From: header in the email is From: [Poster's Name] via [List Name] <address for posting a reply> where [Poster's Name] is the first non-empty value from - the display name in the original From: - tne display name in the posters member record - the poster's email address with the domain replaced with `---` How this header is rendered by any particular mail client (MUA) is up to that MUA and not something you can control. Note however that I use T-bird as my MUA and T-bird displays the From: in your mail from the list as From Steve Brown via Mailman-users <mailman-users(a)mailman3.org> Also, Mailman puts your original From: in a Reply-To: which T-bird displays as Reply-To Steve Brown <drstephenlbrown(a)gmail.com> Depending on your list's settings, the original From: might be in Cc: rather than Reply-To: And, if the T-bird user really needs to see the poster's name and it's not in any displayed headers, they can always view the source of the message and see the From: there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 weeks, 2 days

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

by peter＠chubb.wattle.id.au

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

1 year, 3 months

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

by Thor Atle Rustad

2018-01-23 18:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > > > What I called "local admin" should have > > rights to add and remove members of, say, the poodle-regionA mailing > list. > > > By "local admin", do you mean "list owner", i.e., a list owner should be > able to see her own "hidden" lists. > > Is that what you mean, or to you envision some new category of user that > has more access than a list owner? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > I mean "list owner"

7 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Yes I did ran it in the env2 python2 virtualenv, it says: ERR_CONNECTION_REFUSED I stopped the firewalld service and it's still refused I installed uwsgi, should I put the config inside mailman.cfg?? El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 01:36 PM, Rafael Mora wrote: > > > > I visited http://192.168.1.42:8000 in my browser and I could not see the > > web UI. > > > What did you see? > > Did you run the Django web server? In your Python 2 virtualenv? > > python manage.py runserver > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: max_delivery_threads

by Sven Buesing

Hi, thank you for the clarification. Are there other ways to speed up the sending of personalized emails? Regards, Sven -----Ursprüngliche Nachricht----- Von: Mark Sapiro [mailto:mark@msapiro.net] Gesendet: Dienstag, 15. Oktober 2019 17:47 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: max_delivery_threads On 10/15/19 12:29 AM, Sven Buesing wrote: > Hi, > > we are currently running mailman version 3.3.0. > We want to enable max_delivery_threads - we want to send personalized mails > (To: ), and we hope that threading would speed things up - but it seems this > option has no functionality despite being documented in the schema.cfg. It is documented in schema.cfg, but it has never been implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 9 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

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

2 years, 7 months

[MM3-users] Re: Crash while importing archives

by Mark Sapiro

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

5 years

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

by Mark Sapiro

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

4 years, 5 months

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

by Mark Sapiro

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

3 years

[MM3-users] Re: footer template priority

by Mark Sapiro

On 6/19/25 14:30, Sam Darwin via Mailman-users wrote: > Thanks. That fixed it. > > Comments: > 1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'. As a reader, you are thinking, I'm running both hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at /mailman3/ . What about the path '/mailman3/ for postorius? > The doc could mention the path even if it's to explain why it's not needed. (The reason perhaps it's not needed is root will redirect to '/mailman3/'.) I'm guessing you are looking at https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail… Although the name of the setting includes Postorius, the definition there says "Base URL where Django/Mailman-web would be listening for requests." I.e., the base URL for accessing Django, not Postorius. > 2. This all seems very self-referential. The setting goes into settings.py which is the website for postorius itself. It is accessing itself. > Given that's the case do you really need to tell Django about it's own URL? Doesn't it know it's own URL already? Could Django just contact itself without being configured? It and in this case Postorius know the /mailman3/... part, but they don't necessarily know the appropriate base url for accessing the Django WSGI. > 3. Logging... when it can't find the templates, does it log an error anywhere? Mailman's outgoing runner logs an error to the mailman.error log, usually written to mailman.log. The not at all descriptive log message says "Cannot connect to SMTP server <configured smtp_host> on port <configured smtp_port>", but it only logs it the first time and not again until there is a successful delivery. This issue is https://gitlab.com/mailman/mailman/-/issues/514 which I am in the process of fixing. > 4. The server had been up for a year. After I rebooted, the problem vanished, even after removing the new setting. So either it's caching the setting in Redis, or else the problem is really gone. Very strange. See https://gitlab.com/mailman/mailman/-/issues/514#note_101644301 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

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

by Wolfgang Bock

Dear Mark, many thanks. Works! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Samstag, 6. November 2021 16:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Showing sender as ... via ... list On 11/6/21 4:40 AM, Wolfgang Bock via Mailman-users wrote: > > Here is my question: > > What do I have to configure to get my lists to show the sender like in > this > list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org In Postorius go to Settings->DMARC Mitigations and set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

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

by Mark Sapiro

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

7 years, 9 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

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

2 years, 8 months

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

by Mark Sapiro

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

2 years, 6 months

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

by Mark Sapiro

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

1 year, 8 months

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

by Stefan Bauer

That is already set. No change. This completely removes the reply-to: header and sets the iu-all list-address as new and only reply-to. Am Mi., 24. Nov. 2021 um 04:18 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/23/21 2:24 AM, Stefan Bauer wrote: > > Unfurtunately, this completely removes the reply-to: header and sets the > > list-address as a new and only reply-to. > > Set Settings -> Alter Messages -> Reply goes to list to No Munging > in addition to First strip reply to = Yes > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 8 months

[MM3-users] Re: Docker Support Sucks

by Mark Sapiro

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

5 years

[MM3-users] Re: User settings triggers error

by Mark Sapiro

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

5 years, 1 month

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

by Mark Sapiro

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

5 years, 5 months

[MM3-users] Re: Delete a single email or thread from hyperkitty archive

by Abhilash Raj

On Fri, Jun 21, 2019, at 2:07 PM, Mark Sapiro wrote: > On 6/21/19 6:54 AM, andrew.bernard(a)gmail.com wrote: > > How can one do this? Raw database access gets you involved in all the usual foreign key constraints. > > > In the HyperKitty thread view there is a link to "Delete this thread". > In the message view there is a link to "Delete this message". Do note that this option is only visible to "Superuser" in Django, i.e. Admin accounts. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

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

by Mark Sapiro

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

3 years, 7 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

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

4 years, 2 months

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

by Mark Sapiro

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

3 years, 11 months

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

by Mark Sapiro

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

9 months, 4 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I changed them to 127.0.0.1 and localhost as you suggested El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

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

by Mark Sapiro

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

4 years, 4 months

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

by Mark Sapiro

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

3 years, 8 months

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

by Mark Sapiro

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

5 years, 2 months

[MM3-users] Re: Digest Formatting

by Mark Sapiro

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

4 years, 8 months

[MM3-users] Re: Attachement processings questions

by Mark Sapiro

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

5 years, 5 months

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

by Mark Sapiro

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

5 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I'm looking in /var/etc/mailman.log but nothing occurs and in the postfix maillog nothing occurs as well Is it possible to look into another config or log file? Thanks El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

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

by Mark Sapiro

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

5 years, 5 months

[MM3-users] Re: New releases

by Abhilash Raj

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

5 years, 1 month

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

by Mark Sapiro

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

3 years, 1 month

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

by Mark Sapiro

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

3 months, 1 week

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

by Mark Sapiro

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

3 years, 6 months

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

by Mark Sapiro

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

4 years, 8 months

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

by Mark Sapiro

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

5 years

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

by Mark Sapiro

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

5 years, 2 months

[MM3-users] Re: anomalous behavior

by Mark Sapiro

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

9 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I ran 'mailman aliases', what should I do now? Thanks El dom., 23 jul. 2017 a las 20:22, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 06:00 PM, Rafael Mora wrote: > > Hello guys, > > > > This is what I've got on ../var/data: > > > > [root@localhost data]# pwd > > /var/lib/mailman/var/data > > [root@localhost data]# ls -l > > total 76 > > -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db > > > > > > What should I do in order to let mailman install the DB files? > > > Run > > bin/mailman aliases > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is what I did: (env2) [mailman@localhost mailman-suite_project]$ python2 manage.py runserver Performing system checks... System check identified no issues (0 silenced). July 21, 2017 - 20:50:29 Django version 1.11.3, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C. El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 01:36 PM, Rafael Mora wrote: > > > > I visited http://192.168.1.42:8000 in my browser and I could not see the > > web UI. > > > What did you see? > > Did you run the Django web server? In your Python 2 virtualenv? > > python manage.py runserver > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

How do I tell mailman to connecto to postfix? Is mailman able to use the smtp I use for our emails service with hostgator? Instead of using postfix?? Thanks El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

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

by Mark Sapiro

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

5 years

[MM3-users] Re: Problems with shunted Mails

by Mark Sapiro

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

3 years, 3 months

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

by Mark Sapiro

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

2 years, 9 months

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

by Shashikanth Komandoor

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

5 years, 6 months

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

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

2 years, 4 months

[MM3-users] Re: dedicated mailman3 list server on Ubuntu 18.04 LTS - questions after installation

by Mark Sapiro

On 08/05/2018 03:37 PM, John Seifarth via Mailman-users wrote: > > The installation allows me to sign into the web interface, create a host, create mailing lists, and mass subscribe members. When members send email to the list address, the server sends the messages normally to the other members of the list. That's the good news. That's cool. You have raised a lot of questions and I don't have time now to deal with them all. Maybe others can help. I will say a few things now and maybe more to follow. > However, when I look at the list archives, there are no posts. I deliberately mass-subscribed an invalid address, and I can see in /var/log/mail.log that the message bounces, but I get no notification, nor do I see any bounce info when I look at the member info. About Archiving: Are you running django qcluster <http://docs.list.org/en/latest/config-web.html#running-the-task-queue-requi…> and all the scheduled tasks <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>? About Bounce processing: Bounce processing is not functional in Mailman 3 yet. > 5) DKIM and DMARC > > I’ve got OpenDKIM running on inet:12345@localhost and OpenDMARC running on net:54321@localhost. > > How can I get mailman to use these milters and sign messages? How should DMARC munging be configured when signing? Your outgoing MTA should be doing the signing, not Mailman. Your signing outgoing messages won't help with DMARC if Mailman alters the message in any way, e.g. by subject prefixing, content filtering or addition of list headers and/or footers. Minimum DMARC settings would be DMARC mitigation action -> Replace From: with list address and DMARC Mitigate unconditionally -> No > 6) Is there an overview of how mailman3 works? > > Is there documentation which explains the path of an incoming post through the system, including initial reception, list processing, sending to members, processing bounces, and archiving posts? All the docs are at <http://docs.list.org/en/latest/> You may want to see <http://mailman.readthedocs.io/en/latest/src/mailman/docs/8-miles-high.html> amongst the many other things you'll find there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Is this the problem?????: # When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. if DEBUG == True: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') Shouldn't DEBUG be FALSE?? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 11 months

[MM3-users] Re: Is there an example of a complete installation for https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-install (ie. standard installation)?

by Mark Sapiro

On 2/1/22 14:34, matt(a)fes.org wrote: > It's close, the config contents are good, but doesn't appear to be using the standard installation locations...or I missed some things? The issue is there is no `standard` installation. > For instance, my mailman.cfg is in /etc/mailman3/mailman.cfg) vs /opt/mailman/mm/mailman.cfg (from link you provided), same with settings.py and settings_local.py. "mailman info" shows "config file: /etc/mailman3/mailman.cfg". Also, don't have an /opt/mailman/mm/bin... This all depends on how Mailman is installed. For example, for my installations I create /opt/mailman/mm/bin where I put scripts that execute the corresponding mm/venv/bin/ commands after setting appropriate environment variables and/or with options pointing to config files, etc. But even ignoring that, a lot of locations depend on the chosen setting for layout: in the [mailman] section of mailman.cfg. That controls locations based on https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/mailman… where the `xxx` in `paths.xxx` is the value of `layout`. > This sort of illustrates my issues - trying to resolve problems is a challenge if my config/files/paths are incorrect. Comparing to a (formerly) working installation would clear up many of these issues and i think would be a great reference for anyone making the switch to mailman3. There is no `one size fits all` answer. I support three different production installations of Mailman 3 at lists.mailman3.org, mail.python.org and the server for my bicycling club. They are all quite similar, but they all differ in detail, in part because some were initially installed using the obsolete mailman-bundler package, and in part because two use Apache and one uses nginx. At least they all use gunicorn as the web wsgi server, but mail.python.org used to use Apache mod_wsgi, and uWSGI is another possible choice. If I gave you one of these as an example, it might cause you to make a bunch of changes that aren't in fact necessary, just because you and I have made different, equally valid choices. -- 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 did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On 3/26/21 8:51 PM, Brian Carpenter wrote: > On 3/26/21 6:13 PM, Mark Sapiro wrote: >> Absolutely. At first MM3 wasn't processing bounces at all. A GSOC >> student did the bulk of the current implementation and we were happy >> to get that even though this piece was missing. We know we need it. If >> you don't think we're working fast enough, you can submit a merge >> request or dock our pay. > > I don't understand the sarcasm here at all. I am just trying to figure > out what the PRIORITIES are from the Mailman 3 developers. That's all. > BTW, I still haven't figured it out. OK, the "dock our pay" remark was uncalled for, but I was only trying to point out that for the most part, all of this work is being done by or in some cases mentored by Abhilash and me, and we are both volunteers with other responsibilities. This is a known issue <https://gitlab.com/mailman/mailman/-/issues/737> posted by me 8 months ago. There are no offers to help work on it, nor are there any comments to the effect that this should be higher priority than any of the 307 other open Mailman core issues in the tracker. I can't speak for Abhilash, but my priorities are fix things that are trivial to fix as they arise and work on the harder stuff as time and interest allow. I realize that doesn't help you much, but I'm a volunteer. This is (one of) my hobbies. If it's not fun or at least satisfying, I won't do it. > It still doesn't explain why Postfix is not recording the delivery > issues which I assume has nothing to do with Mailman 3. I see successful > deliveries with Postfix and bounces with Mailman 3 core. I never seen > that with Mailman 2 and Exim. They always matched. If you can help me to > understand that with out the petty sarcasms then that would be great. If > not, then ok. I don't know why you never saw this with MM 2.1 and Exim. Possibly because MM 2.1 sent you the DSN with the admin notification, you never looked. I told you in my initial reply in this thread "They are being bounced by a downstream MTA." To elaborate on that, Mailman's MTA be it Postfix, Exim or whatever, attempts to deliver the mail to the MX of the recipient domain. Sometimes this results in a 5xx status which is logged and reported as a bounce to the sender, i.e. the LIST-bounces address. Sometimes it results in a 4xx status which will cause the delivery to be retried at intervals until it is either accepted or exceeds a configured lifetime and is reported as a permanent failure. The rest of the time, the delivery succeeds, but that is only delivery to the MX for the domain. It may be that for that recipient, that MX is a relay to another MX in the delivery chain, and sometimes, either quickly or after some delay due to retries downstream eventually timing out, the ultimate delivery fails and a DSN is returned to the original envelope sender which is the LIST-bounces address. If you look in the Postfix logs around the time that Mailman recorded the bounce, you should see an incoming message from=<> (DSNs always have a null envelope sender) and to=<LIST-bounces(a)list.domain> or if you are VERPing to=<LIST-bounces+recip=recip.domain(a)list.domain> which is the DSN being returned by the downstream MTA. -- 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: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by Mark Sapiro

On 5/3/21 3:27 PM, summersan(a)nclack.k12.or.us wrote: > Hi Mark, > > Thank you for your quick response! > > When setting up Mailman 3, I went through much of this "how to" guide here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. Which uses gunicorn as the wsgi server for Django. > As far as I can tell, my current setup appears to be proxying from Nginx to Gunicorn, according to the related Nginx and mailman3-project-specific Gunicorn config files. Specifically, I checked the local address:port being used in the Nginx file and compared that to the mailman3-project-specific Gunicorn bind address. It looks like I might have "separated out" the REST API to a different server block in the Nginx config file, so I think I'm looking at the correct server block with this conclusion. Nginx has nothing to do with the REST API. The REST API is accessed by Postorius and HyperKitty via mailmanclient and django-mailmane which are installed by pip as dependencies of Postorius and Hyperkitty. > For what it's worth, I don't recall this type of "slow first visit startup" issue happening in the past when using web applications with uwsgi, and I've had the opportunity to use uwsgi with a variety of programs. I think Gunicorn is fairly new to me. I do, however, remember that something like this might have happened in the past when using Passenger (https://www.phusionpassenger.com/) a long time ago, but that might have been setting related on my part. > > Okay, thanks for the encouragement about the potential solution to periodically accessing the related "example.mailman.site/mailman3/lists/" type location (from my earlier email). Wanted to check on that and was also hoping that there might be some setting I'm missing in the overall Mailman 3 project setup related to the "slow first visit startup" issue. I'm not aware of anything you missed. I think this has to be a gunicorn issue or possibly related to Django, but I'm not specifically aware of any issues. There might be something you can set in gunicorn, but I don't know what. -- 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: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 5/31/23 06:17, justfixit(a)marilynstrother.com wrote: > Very interestng! Upon restarting the system (down momentarily for taking a snapshot) and starting Mailman again, all of these missing [List] messages emerged from their timewarp and were delivered to the members / subscribers. Just before shutting down the system I discovered that the apache2 webserver had been off the air due to a module not being enabled yet. > As of yet, I was unaware of any requirement for a web server to be online (beyond possibly gunicorn) in order for Mailman to run its lists. Does that speculation have a factual basis? Or do I risk starting a vicious rumor amongst the impatient readers who are not still here once we deduce this pair of observations were merely correlated in time, with no cause-and-effect relationship? > Before this situation healed itself, the thought had crossed my mind to peek and see if anything was stuck in the queues: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > While that could have provided peace of mind that email messages were merely delayed instead of vanished, even in hindsight I do not see how that would have led to repairing the situation. I suspect if you had looked, you would have found the messages in Mailman's `pipeline` queue, and they were not being processed because the `pipeline` runner wasn't running, although it is possible that the issue was with the `in` runner/queue. It wasn't the `out` runner/queue if welcome messages were being delivered. The fact that the web server wasn't running is just a coincidence. It has nothing to do with Mailman core's processing of messages with the one exception that Mailman core needs to communicate with HyperKitty's API via mailman_hyperkitty, but this only affects archiving to HyperKitty and the addition of an Archived-At: header to messages. > In the absence of a hypothetical command: > mailman status --verbose > about which diagnostic tools or clues should I learn? Logs are possibly the most useful. You might find something in mailman.log about the death of whatever runner had died. Looking at queues is also useful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Thank you, Mike. I will see how to get this across to my users. :-) With love, Allan > On Feb 12, 2021, at 11:55 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/12/21 10:27 AM, Allan Hansen wrote: >> They need to resubscribe to each list they want the new address to be used for. >> Subscriptions involves permissions from the moderators. It’s not a >> simple process, especially if you are on many lists. > > > Not true if they have a Django account. See my reply at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Mark Sapiro

On 9/9/24 15:12, Steve Brown via Mailman-users wrote: > > Looking at the headers of emails sent from steve(a)stevebrown.us to the list and boomeranged back to me, I see a line “X-MailFrom: bounce+66273f.99dcd9c-radg=lists.radg.us(a)stevebrown.xn--us-02t. I gather that it is designating the return path where a message would be sent if there was a delivery problem. From its position in the header, I suspect it is added as they pass through Mailgun, maybe related to DKIM. Without seeing the full headers in sequence I can't say much, but some MTA in the delivery chain (likely your MX, mx1.tmdhosting.com) is setting the envelope sender of the message to bounce+66273f.99dcd9c-radg=lists.radg.us(a)stevebrown.us so that it can receive DSNs at that address. Mailman's lmtp runner is adding the X-MailFrom: header as information. Then Mailman's incoming runner ensures that all of the messages senders are known to mailman by creating, if necessary, address records for all of them. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/incomi…>. The senders are defined as addresses in the headers listed in the configuration setting `sender_headers`, default = from, from_ meaning envelope sender, reply-to and sender. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> > I am hoping you might know why that bounce address is recognized by Mailman 3 as a real address for my emails, but not for others, even from my wife’s computer traversing the same path from our home to the Mailman 3 server. The Mailman installation does get and process the post, but also puts the “bounce+,,,” address in its list of nonmembers. Mailmanlists.net hasn’t figured out the behavior. I can provide full header information if that would help. My understanding of how headers work is very limited. Are you saying that the `bounce+...` address ends up as a nonmember of the list you are sending to. I don't think that should happen. Mailman will add the `sender` address as a nonmember of the list if it is not a member, but the `sender` is the first non-empty value in `senders` which normally would be the From: address unless the installation has changed the `sender_headers` setting -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error'))

by Mark Sapiro

On 11/28/23 18:01, Mark Labeste wrote: > Hi Admin, Any idea on this error? It happen when you wrote a tread it send the mail but not save on the archive. > > Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8406) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Could not archive the message with id <168853565119.17959.11384406081068301715(a)email1.example.com> > Nov 28 20:34:51 2023 (8400) archiving failed, re-queuing (mailing-list testmaillist.example.com, message <168853565119.17959.11384406081068301715(a)email1.example.com>) > Nov 28 20:34:51 2023 (8400) Exception in the HyperKitty archiver: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 710, in urlopen > chunked=chunked, > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 386, in _make_request > self._validate_conn(conn) > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn > conn.connect() > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connection.py", line 429, in connect > tls_in_tls=tls_in_tls, > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket > sock, context, tls_in_tls, server_hostname=server_hostname > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl > return ssl_context.wrap_socket(sock, server_hostname=server_hostname) > File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket > _context=self, _session=session) > File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ > self.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake > self._sslobj.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake > self._sslobj.do_handshake() > OSError: [Errno 0] Error mailman_hyperkitty is unable to connect to HYPERKITTY. Check your setting for base_url in mailman_hyperkitty.cfg. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#connec…> The messages that haven't been archived are queued in Mailman's var/archives/hyperkitty/spool/ directory and will be archived when you fix this 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, 8 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 10:27 PM, Ken Alker wrote: > > So is the only thing stored in var/messages/ the held messages, and > nothing more? Two kinds of messages are in the message store. They are messages which are held for moderator action and bounce DSN messages. Held messages should be removed from the message store when they are handled by a moderator. If there are no held messages in Postorius for any list, any in the message store can be safely removed. Bounce DSNs are only needed for a very short time. They are saved when a bounce is received and removed after a few days by the task runner, but they are only needed until they are attached to the admin notice which happens within minutes, and this was only implemented in Mailman 3.3.5. Prior to that bounce DSNs weren't saved. Probably most if not all of the messages in your message store are not needed and could be deleted, but it's more complicated than that because there are also entries in various database tables that should be removed as well. > Is there an outline as to how to clean up the var/messages hierarchy? > (I assume one has to be careful not to remove current held messages and > maybe old ones that have not been processed; or maybe "old ones" can all > be assumed orphaned, and thus, removed w/o concern?) You could try something like this in mailman shell ``` >>> pendings = getUtility(IPendings) >>> messages = getUtility(IMessageStore) >>> mids = [] >>> for mlist in getUtility(IListManager): ... requests = IListRequests(mlist) ... for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if data.get('_mod_message_id'): ... mids.append(data.get('_mod_message_id')) ... >>> for key, data in pendings: ... mid = data.get('_mod_message_id') ... if data['type'] != 'probe' and mid and mid not in mids: ... pendings.confirm(key, expunge=True) ... messages.delete_message(mid) ... >>> commit() This will find all the message ids from all held message requests, and then find those pendings for message ids not DSNs and not found in requests and delete the pending an the message store message. -- 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: Mails for 1 specific mailinglist not being send and looping in out queue

by Eric Broens

Thank you very much Mark! I removed the footer and that solved the issue. It appears that there was one single quote in the footer. I didn't test, but I suspect that caused the problem. Best Regards,Eric On Thursday, January 14, 2021, 08:24:44 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:26 AM, Eric Broens via Mailman-users wrote: > These mails keep looping for days in the out queue and are never shunted. > Looks to me as a serious bug. > Is there anything that can be done for this? Is this possibly <https://gitlab.com/mailman/mailman/-/issues/745> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 6 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 1/1/22 2:14 AM, horvath.arpad.szfvar(a)gmail.com wrote: > I changed base_url to the https one, reloaded nginx, restarted mailman3-web. > > Now there is an other error message in mailman.log (I can't find the a meaningful result for InvalidChunkLength error message in this list and in google search) > > Jan 01 10:54:40 2022 (126976) Connection to HyperKitty failed: ("Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)) This exception is raised by urllib3 and is documented at https://urllib3.readthedocs.io/en/stable/reference/urllib3.exceptions.html#… ... > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 198, in _send_message > result = requests.post( > File "/usr/lib/python3/dist-packages/requests/api.py", line 119, in post > return request('post', url, data=data, json=json, **kwargs) > File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request > return session.request(method=method, url=url, **kwargs) > File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request > resp = self.send(prep, **send_kwargs) > File "/usr/lib/python3/dist-packages/requests/sessions.py", line 697, in send > r.content > File "/usr/lib/python3/dist-packages/requests/models.py", line 831, in content > self._content = b''.join(self.iter_content(CONTENT_CHUNK_SIZE)) or b'' > File "/usr/lib/python3/dist-packages/requests/models.py", line 756, in generate > raise ChunkedEncodingError(e) > requests.exceptions.ChunkedEncodingError: ("Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)) We are trying to archive the message via a POST request to the URL https://lists.xxx.hu/hyperkitty/api/mailman/archive and the response is chunked with an invalid chunk length. What happens if you go to https://lists.xxx.hu/hyperkitty/api/ in a web browser. That should return a page of documentation of the API. Does it? Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a response from Django REST framework which is a json representation of your mailing lists info? I don't know what could be causing this error, but I suspect something in the configuration of the web server that is serving this request -- 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: DMARC DNS settings for MM3?

by Mark Sapiro

On 1/30/22 20:25, Jay Hamilton-Roth wrote: > Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). > > Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. > > Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). > > MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: > > v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com > > -or- > > v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com > > -or something else- Have you seen https://wiki.list.org/DEV/DMARC ? Nothing you publish as a DMARC policy or SPF will affect the DMARC actions of recipient domains for list mail unless you set DMARC mitigations for your lists to make the mail be From: your domain. As long as you leave the From: intact, it is the DMARC policy of the From: domain that counts, and if you make any transformation at all to the message (content filtering, subject prefixing, munging Reply-To:, etc) you will break the From: domain's DKIM signature and DMARC will fail at the receiving MTA. As far as recommendations go, what we do for this list for example is we set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to No. We publish SPF "v=spf1 mx a ~all" We publish DMARC "v=DMARC1\; p=none" and we DKIM sign all our outgoing mail. Our Python.org lists are similar except we publish DMARC "v=DMARC1\; p=none\; pct=100\; rua=mailto:rxxx@dmarc.postmarkapp.com\; sp=none\; aspf=r\;" because we've signed up with postmarkapp.com for their free reporting service. We do publish a DMARC policy and DKIM sign outgoing mail because we believe this helps mail delivery, but without DMARC mitigation action = Replace From with list address or Wrap the message ... it won't stop recipients from treating list mail as failing DMARC. -- 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: hyperkitty failed to create a thread

by Mark Sapiro

On 2/11/19 10:01 AM, Abhilash Raj wrote: > > Please create a bug report at https://gitlab.com/mailman/hyperkitty/issues with the affected messages. > > It would help us recreate the problem if you could attach a raw messages in the issue. I am > assuming the messages aren't sensitive since the archive are open. Otherwise, feel free to omit > any sensitive information. > > I haven't looked at the threading code in HK since a long time, but my impression is that it > looks at the 'In-Reply-To' header to figure out if the current email is a response to a previous > email that it received. > > In some cases, the order of the incoming messages can cause this to break, like when the > reply comes in first and the original messages comes in later. I am not sure exactly what is > happening here, but looking at the raw messages should help us reproduce and possibly > fix the issue. I downloaded the February mbox from <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> and imported it to a test list with 'django-admin hyperkitty_import and see the same issue. Examination of the mbox shows for the first message Message-ID: < <SN6PR01MB4719346533C08BF4FF62B880C36C0(a)SN6PR01MB4719.prod.exchangelabs.com>> This will be wrapped, so here's an excerpt Message-ID: < <SN6....prod.exchangelabs.com>> Note the folding of the header and the double angle brackets. The next message has (again excerpted to avoid wrapping) Message-ID: < <BL0....prod.exchangelabs.com>> In-Reply-To: SN6....prod.exchangelabs.com Note again the doubling of the angle brackets in the Message-ID and the absence of angle brackets in the In-Reply-To: The Message-ID: and In-Reply-To: headers of subsequent messages have the same issues. In looking at other mboxes downloaded from Hyperkitty, I see that the absence of References: and the dropping of the angle brackets from In-Reply-To: seem to be usual, and importing such a mbox preserves the threading. However, the doubling of the angle brackets is not usual and is almost certainly the cause of the problem. Do you have any of the original messages? What do the headers look like in those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Upgrade

by Darren Smith

Boy howdy did that work... Thanks! On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/16/2018 10:12 AM, Darren Smith wrote: > > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > sqlalchemy/engine/strategies.py", > > line 160, in create > > engineclass.__name__)) > > TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), > > using configuration PGDialect_psycopg2/QueuePool/Engine. Please check > that > > the keyword arguments are appropriate for this combination of > components." > > > > Anyone able to point me where to go to look for a solution for this? > > > You need to update SQLAlchemy to >= 1.2 for this, but there is another > issue that requires at least 1.2.3 (current is 1.2.6) > > > -- > 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, 3 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Am 16.06.23 um 01:10 schrieb Mark Sapiro: > On 6/15/23 14:03, Jens Günther wrote: >> >> >> Am 15.06.23 um 00:34 schrieb Mark Sapiro: >>>> - Then I tried settings_local.py with: >>>> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > Sorry, this is actually a different setting. There are actually two more > that control this. These are DEFAULT_FROM_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> > and SERVER_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note > that the defaults mentioned in the Django docs are probably overridden > in your settings.py, but you should set them in settings_local.py Thank you Mark. I changed now DEFAULT_FROM_EMAIL to my address, restartet container and it works. Also it works if I delete the EMAIL_CONFIRMATION_FROM-line again and do not put the SERVER_EMAIL, at least for the password-reset. Can you tell the diffenrence between the 3? Would you recommend to set all 3 to my admin-mailaddress?

2 years, 1 month

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Mark Sapiro

On 11/29/2017 05:05 PM, Cameron Smith wrote: > > On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Your post was received: Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) delivered to Mailman core: Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) and immediately discarded: Nov 21 14:31:21 2017 (19106) DISCARD: <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. Possibly you never received a list copy of his message because you were directly addressed and your list option "Receive list copies (possible duplicates)" is set to No. > So, what’s going on? As to why your post was discarded, unfortunately, the logs don't give more info. There are a couple of possibilities. If your post contained an attachment with Content=Type: application/subtype where sub-type doesn't contain 'signature' it would have been discarded by a header filter rule. Also it looks like you sent the message From: <ccsmith(a)mail2.cetsi.com>. If that is not an address on your <ccsmith(a)cetsi.com> account, it would have been discarded as a non-member post. > What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. I see nothing so far to indicate anything at lists.mailman3.org is broken in this respect. The only "unusual" thing is this is now a new thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, but presumably that is because your post was in reply to your earlier post which wasn't archived. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Mailman recovery test did not go as planned

by Mark Sapiro

On 8/5/22 09:38, bob B via Mailman-users wrote: > I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. > I need to perform a DR recovery test. > > I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). Does shutting down mailman-web also shut down Django qcluster? If not, this could be an issue. > While Mailman was stopped, I had our database team take a backup dump of the database. > I then restarted Mailman in docker. > I threw some more messages at a test list. > I validated that the new messages were delivered, and showed up in the archive. > I shut down Mailman again. > I had the database team restore the Mailman database from the backup. > I started Mailman > I logged into Mailman > I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. I would expect that too. > When went into the list archive, I get a spinning icon and no messages showed up. I don't offhand know what the issue would be unless Django qcluster was running the whole time. > I quit, restarted my browser, and logged in again, and the same thing. > I then sent a test message to the list and the message was delivered to the list. > Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Possibly one of the Django periodic jobs, maybe cache_cleanup or daily_cleanup would fix it without a message. > Is this normal? After a restore did the new message cause a refresh of archived messages etc? > Is there a way to do this without sending a message to a list after a restoration of the database? > > Are there better steps I should take when restoring the database? I don't know what better you could do as far as the save and restore are concerned as long as shutting down mailman-web stops qcluster. -- 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: MM3 not starting afte an upgrade

by Mark Sapiro

On 7/23/20 4:35 AM, Gelpi Andrea wrote: > Hi, > to day in a Debian system I upgraded some packages. > > After the MM3 doesn't start anymore. ... > MM3 on start up says: > > Jul 23 13:29:39 posta mailman3[2608]: Traceback (most recent call last): > Jul 23 13:29:39 posta mailman3[2608]: File "/usr/bin/mailman", line > 11, in <module> > Jul 23 13:29:39 posta mailman3[2608]: > load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ > Jul 23 13:29:39 posta mailman3[2608]: return self.main(*args, **kwargs) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/click/core.py", line 717, in main > Jul 23 13:29:39 posta mailman3[2608]: rv = self.invoke(ctx) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke > Jul 23 13:29:39 posta mailman3[2608]: return super().invoke(ctx) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke > Jul 23 13:29:39 posta mailman3[2608]: return > _process_result(sub_ctx.command.invoke(sub_ctx)) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke > Jul 23 13:29:39 posta mailman3[2608]: return > ctx.invoke(self.callback, **ctx.params) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke > Jul 23 13:29:39 posta mailman3[2608]: return callback(*args, **kwargs) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/click/decorators.py", line 17, in new_func > Jul 23 13:29:39 posta mailman3[2608]: return > f(get_current_context(), *args, **kwargs) > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line > 81, in start > Jul 23 13:29:39 posta mailman3[2608]: status, lock = master_state() > Jul 23 13:29:39 posta mailman3[2608]: File > "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 104, in > master_state > Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0) > Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1] > Operation not permitted I think you have a stale lock issue and the master is trying to determine if the process that set it still exists. Remove Mailman's var/locks/master.lck* -- 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: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/3/22 18:55, Philippe B wrote: > Yes, we understand that those logs are normal. And indeed we have a list called "mailman"... Could that be confusing the software somewhere?? I doubt it. Note that the log excerpt posted at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… only shows the handling of a message sent from snap_wl-bounces+mailman=caltech.edu(a)caltech.edu. The envelope sender is VERPed and indicates that this message was intentionally sent to mailman(a)caltech.edu. I.e., when the `snap_wl` list created this message it intended it to go to mailman(a)caltech.edu. > The thing is that we have a pretty convoluted setup for handling mailing lists messages, but it's always the same for all messages. That's why we don't understand why only a small fraction of all the moderation messages get misdelivered at random times for random lists. > > I think what Dan was getting at is: Are there any other logs that would show us how a message that: > > a) was accepted by Postfix on the Mailman server for local delivery to list-owner(a)lists.caltech.edu; > > b) was therefore piped into the Mailman software; But according to the header excerpt I quote at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… it isn't sent directly from Postfix to Mailman's LMTP runner. It gets there via `ec2-12-34-56-78.us-west-2.compute.amazonaws.com` I think that's where the issue occurs. It appears that isn't even on the Mailman host, the no Mailman logging is going to help. > c) came out of that processing as needing to be now delivered (remotely) to mailman(a)caltech.edu, rather than the actual address of the owner of the original list? > > Or maybe we can turn on more verbose logging or something? > PS: Not to confuse things (because it doesn't apply in my example), but what happens when a list has no owner and a message is sent to list-owner? Mail to list-owner is resent by Mailman to the list owners and moderators. If there are no owners or moderators the message goes to the configured site_owner https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/owner… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Mark Sapiro

On 08/09/2017 12:56 PM, cyp(a)trojina.si wrote: > Thanks for the quick and helpful reply. (However, please note that until now I was under the impression that there had been no response yet to my question, since my post appears to indicate having 0 comments at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2017/8/) Yes, I see that. It was apparently an issue with caching. I recently enabled memcached on the server for django and apparently there was an issue with that. I just did what @abompard suggested at <https://gitlab.com/mailman/hyperkitty/issues/131#note_30244378> and that seems to have fixed it, at least for the moment. > Yes, the one-liner did indeed help the "More ..." problem. :) > > As for the bar graph, it's showing a bar now, probably correct. But I have not seen anything about django cronjobs in the MM3 documentation, haven't set any up, can't find any in our (Ubuntu 16.04) system and haven't done anything to fix this in-between (although I have restarted mailman-core and mailman-suite a few times). Could you point me in the right direction? This is what I have in Mailman's crontab on lists.mailman3.org > @hourly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs hourly > @daily /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs daily > @weekly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs weekly > @monthly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs monthly > @yearly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs yearly > 0,15,30,45 * * * * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs quarter_hourly > * * * * * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs minutely > > # Send periodic digests. > # I like 03:30 so they go overnight, but since we're 'global' and on UTC, > # maybe 07:30 is good. > 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send I don't recall exactly where I saw that that was needed, but you can find it (except for the periodic digests bit) at <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>. Note that that suggests a system crontab with the web server user rather than the 'mailman' user's crontab. -- 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: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/18/22 11:28, gordon(a)dickens.com wrote: > Thanks Mark! > > Here is the Traceback from the error: > > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner > response = get_response(request) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view > return self.dispatch(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch > return handler(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/views/list.py", line 326, in get > primary_email = set_preferred(request.user, mm_user) > File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/utils.py", line 64, in set_preferred > primary_email = EmailAddress.objects.get_primary(user) > File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/managers.py", line 30, in get_primary > return self.get(user=user, primary=True) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/db/models/query.py", line 419, in get > raise self.model.MultipleObjectsReturned( > > Exception Type: MultipleObjectsReturned at /mailman3/lists/testing.dickens.com/ > Exception Value: get() returned more than one EmailAddress -- it returned 3!\ Thank you for this info. I've never seen this exact issue. What you have is a Django User with more than one primary email address. It may be you. Go to the Django web admin UI at https://host2.mailhub4u.com/admin/account/emailaddress/?q=gordon where you should see multiple email addresses for user `gordon`, three of which are primary. Go to each address and uncheck primary for all but one of them. If it's not you, see the Mult_primary script at https://gitlab.com/mailman/django-mailman3/-/issues/53#note_842641913 to find who, but this script would need to be modified for other than a postgresql database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

What should I do to tell Postfix to use my domain?? for example send emails using the email account mailing(a)labbrands.com Thank you El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: mail loops back to myself

by Mark Sapiro

On 6/8/25 16:04, Florian Sukup wrote: > > Postfix on its own is working fine. > > I set up mailman, created a site/domain (lists.yyy.com) My hostname is > host.xxx.com . My IP has a RDNS entry: reverse.rrr.com . Why is the RDNS to reverse.rrr.com and not host.xxx.com. It is important for mail delivery to have full circle DNS. I.e. the sending server should have an A record for its IP and revers DNS for that IP should point back to the sending server's name. I'm guessing that rrr.com is a hosting provider and you don't control the rDNS for that IP, but you should try to get them to change it for you. Without that change, delivery of your outbound mail, at least to large ISPs, will be problematic at best. > When I send an email to my mailing list mylist(a)lists.yyy.com I receive > an error email. The logfile says the following: > > ... > Jun 9 00:23:38 arvak postfix/smtpd[]: connect from host.xxx.com[m.y.i.p] > Jun 9 00:23:38 arvak postfix/relay/smtp[]: warning: host > reverse.rrr.com[178.251.71.190]:25 greeted me with my own hostname > host.xxx.com > Jun 9 00:23:38 arvak postfix/relay/smtp[]: warning: host > reverse.rrr.com[m.y.i.p]:25 replied to HELO/EHLO with my own hostname > host.xxx.com See above. > Jun 9 00:23:38 arvak postfix/relay/smtp[]: 094895FADB: > to=<mylist(a)lists.yyy.com>, relay=reverse.rrr.com[m.y.i.p]:25, > delay=0.06, delays=0.03/0.01/0.02/0, dsn=5.4.6, status=bounced (mail for > lists.yyy.com loops back to myself) What is the output from `postconf -n`? > Jun 9 00:23:38 arvak postfix/smtpd[114119]: disconnect from > host.xxx.com[m.y.i.p] ehlo=1 quit=1 commands=2 > ... > > The MX record of lists.yyy.com points to reverse.rrr.com. Not sure if > this is the best idea? reverse.rrr.com has no A or AAAA record. An MX MUST point to a domain that has an A or AAAA record. The MX should point to host.xxx.com. > Can anyone give me a hint where to search for this error? The output from `postconf -n` would help. Also, have you set up postfix per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… ? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: archives html user interface menu selection retention after refresh

by Mark Sapiro

On 6/28/23 10:38 PM, Ken Alker wrote: > I have just started studying the archives feature and I've noticed that > if I select "Most Active" in the top menu and then I refresh my browser, > the refreshed screen jumps back to Recent after the refresh. In fact, > if ANY of the five menu items across the top are selected and then a > browser refresh is performed, the result is that one is always taken > back to the Recent menu item. It was not apparent to me for a couple of > days that this was happening and I'd convinced myself there was some bug > in the Recent vs. Most Active lists because the Most Active list changed > entirely after I did a refresh, when, in fact, I was then viewing the > Recent list again. Confusing. This is the expected behavior. the various Recent, Most Active, ... tabs use # fragments to switch the view, but these don't change the URL that the browser went to (the one in the browser's address bar) so a refresh goes to that original URL which defaults to the `Recent` view. > Is there some way that whatever menu item was being viewed before a > refresh could be retained so that the same menu item is shown after a > refresh? Probably not without significant redesign of the web UI. > Thinking this through even further, I suppose a side-affect of this > request could be that visiting the same page much later (ie. not > immediately after a refresh) may result in the page NOT defaulting to > the Recent menu item any longer (unless once could clear the "last menu > item" memory when the viewer moves AWAY from or closes the page). I > don't have enough familiarly with the interface to suggest if this would > be a bad side-effect, or good, but would this, indeed become a > side-affect that would have to be thought through? It would depend on how the feature was designed, but this is probably moot as such a feature is unlikely to be implemented as it seems the potential benefit doesn't warrant the additional complexity. -- 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: LookupError: unknown encoding: _iso-2022-jp$esc

by Mark Sapiro

On 09/07/2018 08:30 AM, Thor Atle Rustad wrote: > This happens when I open a page of Held Messages containing an offending > message. I get Server Error (500) in Postorius. Here is the mailman.log: > > > Sep 07 15:25:39 2018 (32) REST request handler error: > Traceback (most recent call last): > File "/usr/local/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File > "/usr/local/lib/python3.6/site-packages/mailman/database/transaction.py", > line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", > line 214, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/site-packages/falcon/api.py", line 244, in > __call__ > responder(req, resp, **params) > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 160, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 159, in _make_collection > for resource in collection] > File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 159, in <listcomp> > for resource in collection] > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 150, in _resource_as_dict > resource = self._make_resource(request.id) > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 77, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", > line 54, in as_string > value = email.message.Message.as_string(self) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 243, in > _handle_text > msg.set_payload(payload, charset) > File "/usr/local/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > LookupError: unknown encoding: _iso-2022-jp$esc I think this should be fixed in Mailman core 3.2.0. It is related to Mailman core issues 256, 437 and 470 and merge requests 197, 322, 350 and 375. In particular, it looks like you are missing at least <https://gitlab.com/mailman/mailman/merge_requests/375>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:10 AM, Torge Riedel wrote: > > today I did this on my setup and got the following exception after > "systemctl restart mailman": > > # systemctl status mailman.service > mailman.service - GNU Mailing List Manager > Loaded: loaded (/opt/mailman/core/mailman.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Sun 2020-11-22 09:59:53 CET; > 46s ago > Process: 30520 ExecStop=/opt/mailman/core/bin/mailman.sh stop > (code=killed, signal=TERM) > Process: 30597 ExecStart=/opt/mailman/core/bin/mailman.sh start > (code=exited, status=1/FAILURE) > Main PID: 1223 (code=exited, status=0/SUCCESS) > > Nov 22 09:59:53 basis2 mailman.sh[30597]: File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/protocol.py", line > 220, in check_error > Nov 22 09:59:53 basis2 mailman.sh[30597]: > err.raise_mysql_exception(self._data) > Nov 22 09:59:53 basis2 mailman.sh[30597]: File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/err.py", > line 109, in raise_mysql_exception > Nov 22 09:59:53 basis2 mailman.sh[30597]: raise errorclass(errno, > errval) > Nov 22 09:59:53 basis2 mailman.sh[30597]: sqlalchemy.exc.InternalError: > (pymysql.err.InternalError) (1060, "Duplicate column name > 'archive_rendering_mode'") > Nov 22 09:59:53 basis2 mailman.sh[30597]: [SQL: ALTER TABLE mailinglist > ADD COLUMN archive_rendering_mode INTEGER] > Nov 22 09:59:53 basis2 mailman.sh[30597]: (Background on this error at: > http://sqlalche.me/e/2j85) > Nov 22 09:59:53 basis2 systemd[1]: mailman.service: Control process > exited, code=exited status=1 > Nov 22 09:59:53 basis2 systemd[1]: mailman.service: Failed with result > 'exit-code'. > Nov 22 09:59:53 basis2 systemd[1]: Failed to start GNU Mailing List > Manager. > > I checked the database and - yes - there is already such a column in the > DB. So I tried it the "hacker" way and just removed the column from the > DB and give "systemctl restart mailman" a second try. Now it worked and > the column is back. > > I don't know if this column was already there from 3.3.1. That column was added in 3.3.2 by <https://gitlab.com/mailman/mailman/-/merge_requests/644> It is the migration to add that column that failed in the above. It appears that somehow that migration was previously run and added the column, but the version_num entry in the alembic_version table was not updated to indicate that that migration had been run. -- 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: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Mark Sapiro

On 09/30/2018 11:42 PM, Thomas G wrote: > Hi, > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > install in Mailman3.2. > > I didn't found how migrate the archives. >>From : HyperKitty - Version: 1.1.1 - Python2.7 > To : HyperKitty - Version: 1.2.1 - Python3.5 As Abhilash said, you shouldn't need to migrate anything but the search index. > I exported a mbox from hyperkitty (web interface) and tried to re-import > it, without result. > """""""""""""""""""""""""""""""""""""""" > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > listedetests(a)hatlab.fr You can't import a gzipped mbox. You have to gunzip it. > Computing thread structure > Synchronizing properties with Mailman > Warming up cache > The full-text search index is not updated for this list. It will not be > updated by the 'minutely' incremental update job. To update the index > for this list, run the 'manage.py update_index_one_list > listedetests(a)hatlab.fr' command. > """""""""""""""""""""""""""""""""""""" > The database stay empty (and web interface): > """""""""""""""""""""""""""""""""""""" > mailmandbnameprod=# select * from hyperkitty_email; > id | message_id | message_id_hash | subject | content | date | timezone > | in_reply_to | archived_date | thread_depth | thread_order | > mailinglist_id | parent_id | sender_id | thread_id | sender_name > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > (0 rows) > """""""""""""""""""""""""""""""""""""" > > Any idea to do this importation ? Why is the database empty? It should be as it was with the prior HyperKitty. Also, it doesn't seem to be the issue here, but if you don't specify a --since option to hyperkitty_import, it won't import any messages older than the most recent message in the existing archive. i.e., if there are any messages in the existing archive, the default for --since is the date of the most recent such 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, 10 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 4/30/19 1:04 AM, Henrik Rasmussen wrote: > @Mark: I am really sorry for the delayed responses, but this is a very low frequency list. I have subscribed to the list using a non-Microsoft address to see the outcome. > > The mails does indeed contain 'X-Mailman' headers. > > X-Mailman-Rule-Hits:nonmember-moderation > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation It looks like the message hit the nonmember-moderation rule and was accepted. This can happen in a few ways: First we determine the senders. Assuming the config is default, these are the addresses in From:, the envelope sender, and addresses in Reply-To: and Sender: if any. The only address I can see in the message headers that hasn't been altered by Mailman is the From: and maybe Reply-To: which you have munged to [LISTNAME](a)senderdep.example.com. Anyway that unmunged address and possibly others from the original incoming message will be users of the list with role nonmember. Now each of those (possibly only the one) nonmember(s) is checked for a moderation action. Since the message does not appear to have been held or processed through rules beyond nonmember-moderation, we presumably found a moderation action of accept. This can happen in a few ways., If this list was originally imported from Mailman 2.1 by the 'mailman import21' command, there may be a legacy accept_these_nonmembers attribute for the list. If so, and if a nonmember sender address matches an address or pattern in the list's accept_these_nonmembers, the message will be accepted. Otherwise if the moderation_action for a nonmember sender address is accept the message will be accepted. You need to check the list's accept_these_nonmembers attribute and the non-member address's moderation action. If you have recent Postorius, you can see nonmembers and their options from the 'users' -> Non-members view. In any case, you can do something like mailman shell -l list.example.com Welcome to the GNU Mailman shell The variable 'm' is the list.example.com mailing list >>> m.accept_these_nonmembers returns a possibly empty list Then for the sender addresses >>> memb = m.nonmembers.get_member('sender address') >>> memb.moderation_action This may return <Action.accept: 3> in which case you may want >>> memb.moderation_action = m.default_nonmember_action -- 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: Message IDs

by Mark Sapiro

On 10/15/21 3:19 AM, Philip Colmer wrote: > > I'm not sure that the message ID identifies the author, does it? No, but it identifies the message, and while Mailman has made some cosmetic modifications to the headers, it is still the same message. > I've just done a quick test of sending myself an email and then replying to it. > > The original email has a message ID of > CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com > > In the reply, the following headers are present: > > References: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > In-Reply-To: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > Message-ID: <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> > > Would it be reasonable for Mailman 3 to use "References:" to keep the > original Message ID and then add a new Message ID? No, because the message from the list is not a reply to the incoming message. It is the incoming message. > I think that what Mailman 3 is doing is similar to forwarding the > email. If I forward an email, again the headers change: If you want Mailman to 'forward' the message, set DMARC mitigation action to wrap the message. >> The IETF has addressed the issue of non-identical but equivalent >> messages with the Resent-Message-ID field (and in general the whole >> suite of Resent-* fields. > > Mailman doesn't appear to be adding that header. Would that be an > acceptable solution instead of the one I suggested above? Mailman doesn't add the header, but even if it did, I doubt it would solve the problem with Gmail. > I appreciate your view that Google is broken. I'm just trying to find > an acceptable solution to the end-user perception of "I've sent an > email to the list but I haven't received a copy back". That is going > to be a big issue/headache for us. It's a long standing PITA with Google. See <https://wiki.list.org/x/4030680>. Your Gmail users can partially mitigate this by setting their Acknowledge posts option to Yes. Note also that Mailman core communicates with archivers to determine what goes in the Archived-At: header and this value is usually based on the Message-ID:. Changing the Message-ID: could possibly render that value incorrect. -- 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: django-allauth 0.59.0

by Jered Floyd

This is only required for the new "user sessions" app which doesn't appear to be exposed within Mailman. (I agree it should be added, though.) --Jered ----- On Dec 21, 2023, at 4:12 AM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/20/23 7:27 PM, Jered Floyd wrote: >> >> >> FYI, django-allauth 0.59.0 was released on December 12 and incorporates the >> patches to work properly with Mailman again. > > django-allauth 0.59.0 requires django.contrib.humanize in > INSTALLED_APPS. You may need to add this in your Django settings when > upgrading django-allauth. > > > -- > 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 jered(a)convivian.com

1 year, 7 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 11:00 AM, Seth Seeger wrote: > > I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: > > Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose > process(mlist, msg, msgdata, start_chain) > File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process > link.function(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), > File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ > self.set_payload(_text, _charset) > File "/usr/lib/python3.8/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 > > There are two owners listed, one of them is also listed as the moderator. This is redundant. Having the same user as both owner and moderator only results in possible duplicate notifications. There is no reason to have an owner also be a moderator. > "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Please do send me the shunted .pck. what is going on is this is an English language list which has character set `ascii` and the notice for some reason has non-ascii, possbbly the Subject: or the user's display name has non-ascii. But possibly the message itself is defective. In any case, I'd like to get the shunted message to see if there's something we should fix. -- 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: Mailman3 service on mailman-3.3.4 is not getting started

by Mark Sapiro

On 6/23/21 12:24 AM, Shashikanth Komandoor wrote: > Hi team, > > I am trying to install mailman 3.3.4, the currently available > latest version at > https://docs.mailman3.org/en/latest/install/virtualenv.html on RHEL 7.5. > > As part of the installation, I am not creating any user with the > name *mailman* and instead going with the *root* user only. Along with that > I am using the directory */var/lib/mailman* as the root directory. It is a very bad idea to run Mailman as root. If there were some vulnerability that would enable an exploit to run arbitrary code, you wouldn't want that code to run as root. ... > Now, the issue is while I am trying to start the service, it > is showing the below error and the status looks like as following: > > # systemctl start mailman3 > Job for mailman3.service failed because a configured resource limit was > exceeded. See "systemctl status mailman3.service" and "journalctl -xe" for > details. > > # systemctl status mailman3 > ● mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; disabled; vendor > preset: disabled) > Active: failed (Result: resources) since Wed 2021-06-23 12:51:27 IST; > 1min 7s ago > Process: 16277 ExecStart=/var/lib/mailman/venv/bin/mailman start > (code=exited, status=0/SUCCESS) > > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: os.execl(*execl_args) > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: File > "/usr/lib64/python3.6/os.py", line 527, in execl > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: execv(file, args) > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: TypeError: expected str, > bytes or os.PathLike object, not NoneType > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Starting Mailman's master > runner > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Generating MTA alias maps > Jun 23 12:51:27 psumm3.nic.in systemd[1]: PID file > /var/lib/mailman/var/master.pid not readable (yet?) after start. > Jun 23 12:51:27 psumm3.nic.in systemd[1]: Failed to start GNU Mailing List > Manager. > Jun 23 12:51:27 psumm3.nic.in systemd[1]: Unit mailman3.service entered > failed state. > Jun 23 12:51:27 psumm3.nic.in systemd[1]: mailman3.service failed. > > I can't understand where the issue might be. What's in 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, 1 month

[MM3-users] Re: DMARC Mitigation Wrap

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > > MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text. > > The From address of this message has been replaced with the list > address, while the From name has 'via list' appended. Please be > careful when using 'via list' addresses later for new emails, as they > will be sent to the whole list.\r\n -------------------------- > ----------------------------------------------------------------------\r\n > From: Allan Hansen <allan_hansen(a)icloud.com <mailto:allan_hansen@icloud.com>> > Subject: [Testlist] wrap with divider and BLANKLINE > > Which coding option am I missing? I have searched for one online. I assume you are entering your text in Postorius in the DMARC wrapped message text box. There are a number of things going on here. Postorius is wrapping and filling the text and stripping trailing whitespace. If you want more whitespace, I suggest following your text with one or more empty lines and a single dot as in The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list. ------------------------------------------------------------------- . In the above, the blank lines before and after the line of dashes will be preserved as will the final dot which should be unobtrusive enough. More importantly, the rendering of the received message is up to your mail client. Your's apparently begins the wrapped message immediately after the wrapper's text, but many will not do that. Unless you actually view the received message in every mail client used by your user's, you won't know what they actually see. -- 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: templates

by Mark Sapiro

On 5/5/23 17:04, Christian via Mailman-users wrote: >>From bounce.log > > May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list > degrowcali.lists.ccalternatives.org, bounce score = 5. > May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list > degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending > probe. > May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list > degrowcali.lists.ccalternatives.org, bounce score = 5. > May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list > degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending > probe. > May 05 08:11:01 2023 (765) Member vortexanthony(a)hotmail.com on list > degrowcali.lists.ccalternatives.org, bounce score = 1. > May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list > degrowcali.lists.ccalternatives.org, bounce score = 5. > May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list > degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending > probe. > May 05 08:15:01 2023 (765) Probe bounce received for member > juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. > May 05 08:15:01 2023 (765) Disabling delivery for juliankrauspolk(a)gmail.com > on list degrowcali.lists.ccalternatives.org by bounce > May 05 08:15:02 2023 (765) Probe bounce received for member > alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. > May 05 08:15:02 2023 (765) Disabling delivery for alaitz.aritza(a)gmail.com on > list degrowcali.lists.ccalternatives.org by bounce > May 05 08:15:02 2023 (765) Probe bounce received for member > baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. > May 05 08:15:02 2023 (765) Disabling delivery for baronchadg(a)gmail.com on > list degrowcali.lists.ccalternatives.org by bounce > May 05 08:17:02 2023 (765) Residual bounce received for member > juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. > May 05 08:17:02 2023 (765) Residual bounce received for member > alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. > May 05 08:17:02 2023 (765) Residual bounce received for member > baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. So some of your user's, but not 24, are bouncing. If your list's bounce processing settings have Notify owner on disable = Yes, the owner should receive a notice including the DSN. If Notify owner on bounce increment = Yes, the owner will also get notices when a user's score is incremented as for vortexanthony(a)hotmail.com above. This still doesn't answer the other users. Have you looked at the MTA logs? -- 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: import21 caused a few mails to be sent out

by Mark Sapiro

On 6/2/24 7:57 AM, Marc SCHAEFER wrote: > Hello, > > After importing a (big > 3000 subscribers) list with import21, I noticed the > following: > > 36 mails went out from LIST-NAME-bounces to subscribers, but they > apparently all bounced. > > Could those be subscribers that Mailman2 saw bouncing and added > the appropriate flag, and Mailman3 sent a probe after the import21? These are probably not probes. They are probably Bounce disable warnings. > I checked for one of the e-mail address and: > > Mailman2: > - that e-mail has the [X] R flag for "noncourriel" (no delivery) > > Mailman3: > - that e-mail is Delivery mode Regular, Bounces to 0 import21 will set an imported members delivery_status to the corresponding MM 2.1 delivery_status. If an imported member's 2.1 delivery status is nomail with reason unknown, by_user, by_moderator or by bounces (in French these are ?, U, A, R respectively), the MM 3 delivery_status will be set accordingly. This is not Delivery Mode, it is Delivery status which is not shown on the membership list, but only by clicking the user's email in the membership list. > NB: in MM2 and MM3, all users are in Hold for moderation, that's > normal. > > In addition, there are a few mails in /var/lib/mailman/messages > for example that same user: one file, showing a bounce from a remote > server. > > So my questions: > > 1) is this behaviour to "probe" already disabled addresses normal, and > not "port over" the "don't deliver"? No, if a MM 2.1 user's delivery was disabled, it will be imported as such. > 2) why are those messages held in messages/ ? Bounce DSNs are saved in the message store (/var/lib/mailman/messages) so they can be attached to admin notifications. > 3) should I then, before running import21, clean the MM2 installation > of all those users with [X] R flag? If yes, is there > a simple command? That should not be necessary. MM 2.1 users with nomail "R" (in French) should be imported with delivery_status = DeliveryStatus.by_bounces and they should not be sent mail except for the periodic Bounce disable warnings which is probably what you are seeing. -- 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: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 12:21 PM, Mark Sapiro wrote: > On 10/29/20 8:51 AM, Brian Carpenter wrote: >> On 10/29/20 11:33 AM, Mark Sapiro wrote: >>> 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. >>> >> Do you think this is a bug with Mailman core or my system? > > If the current policy is moderate and the user has a prior request > waiting confirmation and a new request is rejected because of the prior > request waiting confirmation, I think that is a bug in core, but I don't > know if that is the case or not. I think it is a bug in Mailman 3 core. I am seeing the same behavior on my Postorius server. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: slow restart time for mailmanweb

by David Newman

On 12/28/21 1:20 PM, Mark Sapiro wrote: > It looks to me like the timeout is in stopping, not starting. What > happens if you separately > > systemctl stop mailmanweb > > and > > systemctl start mailmanweb Confirmed: root@myhost:/etc/mailman3# time systemctl stop mailmanweb real 1m30.239s user 0m0.010s sys 0m0.004s root@myhost:/etc/mailman3# time systemctl start mailmanweb real 0m0.012s user 0m0.011s sys 0m0.001s On 12/28/21 3:01 PM, Mark Sapiro wrote: > Is your /etc/systemd/system/mailmanweb.service the recommended one at > https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… Yes, modulo the use of MariaDB instead of PostgreSQL. > If so, try adding > > KillSignal=SIGQUIT > > to the Service section and see if that fixes it. root@myhost:/etc/mailman3# time systemctl restart mailmanweb real 0m1.026s user 0m0.008s sys 0m0.004s My limited understanding of SIGQUIT is that it dumps core, but 'find / -type f -name '*.core' did not return any core dumps from this event. Still unsure why the service hung on stop, but thanks! dn

3 years, 7 months

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Perry Kollmorgen

Thanks Mark, I will give it a shot. — Perry > > On Nov 28, 2024 at 9:12 AM, <Mark Sapiro (mailto:mark@msapiro.net)> wrote: > > > > On 11/26/24 9:30 PM, Perry Kollmorgen wrote: > > For the code for moderators it currently only adds them: > > mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) > > Would I need to add something similar which sets a delivery_status for the moderator added ? I think something like this ``` mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) moderator = mailing_list._get_membership(moderator.email, 'moderator') prefs = moderator.preferences prefs['delivery_status'] = 'by_moderator' prefs.save() ``` -- 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 pcjkollmorgen(a)hotmail.com > >

8 months

[MM3-users] Re: Mailman Header Behavior

by Samir Faci

Perfect, Thanks. Is there a way to set this as a default for all new lists being created? Still working on the new styles, I imagine that can be set there during the selection of the list type. -- Samir Faci On Fri, May 15, 2020 at 9:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/20 9:31 AM, Samir Faci wrote: > > > > Is there a way to force mailman to ensure that the list name shows up in > > the from field? > > In Postorius Settings -> DMARC Mitigations set DMARC mitigation action > to Replace From with list address and set DMARC Mitigate unconditionally > to Yes. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 2 months

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

by Mark Sapiro

On 11/17/23 00:51, Odhiambo Washington wrote: > I am scratching my head bald trying to figure out how to bring in this > other MM3 site and list into my existing server, especially with regard to > the DB backend. > > The list - let's call it users(a)domainX.name was using MySQL backend and > had a separate DB for Mailman core and Mailman web. > I believe combining these into one isn't a problem. But getting to merge > this DB into my current one is what I am not sure about. This is https://gitlab.com/mailman/postorius/-/issues/13 which is a real need, but doesn't yet exist. I think the easiest thing for the archives is to forget the Mailman web DB and just export the archive as a mbox from the other site (if it's large, exporting the entire archive will time out so you have to do it in pieces). Then you can use hyperkitty_import to import it. For the list data, it's probably easiest to just create the list manually and go through the settings in Postorius and make them match, although you could dump the mailinglist table entry where list_id = 'users(a)domainx.name' and load that, but you'd need to edit the id field in the dump to match the id on your server. That leaves the members. Doing this with a DB dump/load would be very complex because while the member table has a list_id field which is the id of the list's entry in the mailinglist table and can be used to select the relevant members, these records also link to entries in the address, preferences and user tables and matching them would be an issue. I think a custom script would be required. If I were doing this, I would make a separate database on my server with a copy of the data from the other server and then try to make a script that would extract data from the other database and add it to mine. Alternatively you could just dump the members from the other servers with the `mailman members` command perhaps separately for regular and the different digest types and then add them with the `mailman addmembers` command. This wouldn't get all their attributes, but it could work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Disable Sign-up per domain

by Mark Sapiro

On 7/31/25 17:54, Mark wrote: > > Thank you Mark. It's so close. After wrangling your solution a bit it's > working a treat on my test server (wrangled solution below) . > > When I add it to the production server (same OS, MM installation, etc) > I'm getting a "Bad gateway" error page and the log reports ... > > ... > raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. That error will occur when settings.py contains SITE_ID = 0 and the host in the http request is not one of the hosts in the django_site table in the database or in Sites in the Django admin web UI. Is that possibly the case here? In any case, if the change to /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py that you report below is the only thing that changed from a working installation, I don't see how that can affect this. Is there a complete traceback preceding the log snippet you report. If so, what is it? > I cannot for the life of me get my head around that. I suspect it's > something to do with what you said -- "whatever is proxying to Django > setting the appropriate HTTP_HOST header." -- which I don't understand. This is in the configuration of the web server. It should be configured to pass the host of the incoming request to the proxy target in the HTTP_HOST header. In nginx this is `proxy_set_header Host $host;`. In apache it is `ProxyPreserveHost On`, but again the change to user_adapter shouldn't affect this. > Any additional advice gratefully received. > > > ================================== > /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py > ================================== > COMMENT OUT THESE 2 LINES... > > # def is_open_for_signup(self, req): > # return False > > REPLACE WITH THE FOLLOWING... > > def is_open_for_signup(self, req): > if req.META['HTTP_HOST'] == 'lists.mydomain.com': I had if req.META.HTTP_HOST == 'lists.mydomain.com': which as you discovered is wrong. What you have is correct. > return False > else: > return True And here I had return super().is_open_for_signup(self, req) which should return the is_open_for_signup result from allauth.account.adapter.DefaultAccountAdapter but since that result is an unconditional True, what you have is OK too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 day, 11 hours

[MM3-users] Re: Member Issue Discovered

by Mark Dadgar

On Oct 20, 2020, at 9:13 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/20/20 8:53 PM, Mark Dadgar wrote: >> On Oct 20, 2020, at 8:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> Even in mailman 2.1, while a list admin could go to a user's options >>> page for the list and change things, the "change globally" check boxes >>> only worked for the user, not for the list admin. >> >> That was by design!? >> >> As an admin, that was so irritating. > > Yes, it was by design. Do you really think that list owners should be > able to enable or disable mail delivery, set digest format, user's > password, etc. for a user's subscription on lists that they don't own? Yeah, that makes sense for very large installations. Good point. IIRC, mm2 had the concept of a site-admin. It would be nice if it had worked for them, though. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

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

by Mark Sapiro

On 12/14/23 01:48, Helio Loureiro wrote: > > But it is failing to start displaying the domain name from the previous > machine. > > (venv) mailman@new-server ~ (v3.3.9)> mailman start > Starting Mailman's master runner > Generating MTA alias maps > Traceback (most recent call last): > File > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", > line 1969, in _exec_single_context > self.dialect.do_execute( > File > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", > line 922, in do_execute > cursor.execute(statement, parameters) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line > 153, in execute > result = self._query(query) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line > 322, in _query > conn.query(q) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 558, in query > self._affected_rows = self._read_query_result(unbuffered=unbuffered) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 822, in _read_query_result > result.read() > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 1200, in read > first_packet = self.connection._read_packet() > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 772, in _read_packet > packet.raise_for_error() > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/protocol.py", > line 221, in raise_for_error > err.raise_mysql_exception(self._data) > File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/err.py", > line 143, in raise_mysql_exception > raise errorclass(errno, errval) > pymysql.err.OperationalError: (1054, "Unknown column 'domain.alias_domain' > in 'field list'") The issue is your domains table and possibly others are not up to the current schema. This should be accomplished by Mailman core running all the necessary migrations in mailman/database/alembic/versions/. For some reason, alembic's MigrationContext thinks the migrations have been run, but they haven't. In the `mailman` database, the alembic_version table has the version_num of the putative current version. The migration that added alias_domain is dfe82cf73702_add_alias_domain.py. If there is no alias_domain column in the domain table, alembic_version.version_num should be a version older than 'dfe82cf73702'. I suggest querying the prior mailman database for the alembic_version.version_num value and setting that in the current database, assuming that that migration exists in mailman/database/alembic/versions/. This may be sufficient, but there may be other inconsistencies depending on exactly what you did. -- 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: Multiple domain problem

by Lars Bjørndal

Ah, so stupid error and so simple solution - thank you! Lars On Tue, Feb 14, 2023 at 12:42:16PM -0800, Mark Sapiro wrote: > On 2/14/23 12:08, Lars Bjørndal wrote: > > > > The domain that doesn't work: > > > > > > <VirtualHost *:80> > > ServerAdmin webmaster(a)list.punktskriftutvalget.no > > DocumentRoot /var/www/list.punktskriftutvalget/ > > ServerName list.punktskriftutvalget.no > > ErrorLog logs/list.punktskriftutvalget-error_log > > CustomLog logs/list.punktskriftutvalget-access_log common > > Redirect permanent / https://list.punktskriftutvalget.no > > </VirtualHost> > > Add a trailing slash > > Redirect permanent / https://list.punktskriftutvalget.no/ > > -- > 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 lars(a)lamasti.net

2 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I thought the mailman-suite would do it for me... it says: If you have absolutely no idea about Django, just clone/download this mailman-suite repo How do I install Django? in my 'env' virtualenv ??? Thanks Mark El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: hello， Discussion on how to subscribe to the mailing list

by Mark Sapiro

On 1/16/23 18:55, 朱超 wrote: > Hi, When I subscribe the email list in Subscription Policy is confirm, Some problems happen in here： > 1.Some mail mua reject send the confirm the message, because the length of recipient is too long. for exmaple: requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, and the mail mua reject to modify about this. The default English template says in part: Before you can start using GNU Mailman at this site, you must first confirm that this is your email address. You can do this by replying to this message. Or you should include the following line -- and only the following line -- in a message to $request_email: confirm $token I.e. It gives an alternative method if `reply` doesn't work. You can provide a custom version of this template with different wording if you think you can improve it. > 2.It is inconvenient for users to use. Many people will mistakenly think that after clicking the subscribe button, it will be successful, and they will not process the email. If you set Subscription Policy to Confirm, you are saying that the user must confirm that that is their email address. This requires sending an email requesting confirmation to that address. If you don't want that step, you can set Subscription Policy to Open, but then anyone can maliciously subscribe third parties to the list. > Regarding the discussion on the subscription method of the mailing list, should we consider optimizing the subscription method of the mailing list, for example: > 1. use the method of sending a verification code to subscribe by email，When you receive the verification code sent by the mailing list and fill it in again, you can subscribe successfully。 How is this different from the present method. If you want, you can make a custom template and include something like: Alternatively, you can confirm by going to the URL https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token We don't include that in the default template because Mailman core doesn't know if you even have a web UI or how to access it if you do. > 2. use the email to send a connection to confirm the subscription，People click the link to be redirected to a confirmation page to subscribe to the email。 See above. -- 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: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 12:15 AM, Peter Münster wrote: > > It seems, that mailman bounces the bounces, so that the list-owner never > sees them: > > --8<---------------cut here---------------start------------->8--- > postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] > postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] > postfix/cleanup[11841]: 879D6F12E8: message-id=<> > postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) > postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) > postfix/qmgr[10092]: 879D6F12E8: removed > --8<---------------cut here---------------end--------------->8--- There are a few things going on here. It appears that out04.smtpout.orange.fr has bounced a list post from the <test(a)my-domain.org> list and and sent a DSN back to Mailman at <test-bounces(a)my-domain.org>. It is this DSN that has no Message-ID:. Mailman's LMTP runner rejects such messages. The underlying issue is the orange.fr domain is sending DSNs without a Message-ID: header. > What could I do please, to get the bounces? I would like to use VERP to > identify wrong addresses... If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] section of your config), this log message > postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) would contain to=<test-bounces+user=example.com(a)my-domain.org> and you could identify the bouncing address (user(a)example.com in this case) that way. Beyond that, there are still other issues, the biggest of which is currently, Mailman is not processing bounces other than storing them in the database. See <https://gitlab.com/mailman/mailman/issues/343>. Also, the LMTP runner requires a Message-ID: at least in part because that is part of the algorithm for creating a unique ID for archiving. Given that messages to a -bounces address are handled differently and not archived, it would be possible to not require a Message-ID: for those messages, but arguing against that, if a recipient MTA can't create a DSN that has a Message-ID:, would you trust what else it does? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

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

by Mark Sapiro

On 5/13/21 11:28 AM, Ruth Ivimey-Cook wrote: > Mark, > > While the venv will to a degree isolate you, my experience of the > upgrade from 18 to 20 was that python3.6 was uninstalled and 3.8 > installed. In this scenario, the mailman3 installation is subsequently > broken because there is no python to run. Yes, I overlooked some aspects of virtualenv. Actually, the Python in the virtualenv is mostly symlinks to the Python it was built with, so whether it continues to work after a Python upgrade depends on what the symlinks are and how the Python upgrade installs. > It *is* possible to reinstall python3.6 after the dist upgrade is > complete, and I would presume that after doing so mailman3 would > probably resume ok. In my case I decided to continue using 3.8, which > meant, in essence, rebuilding my mailman3 install -- not fun given my > state of knowledge. > > I would therefore appreciate some guidance on performing the upgrade > from 3.6 to 3.8 with the minimum of fuss. > > [I am not sure, but it could be possible to install python3.8 while > using Ubuntu 18, so that the dist upgrade never breaks anything. Worth > exploring.] I haven't tested any of this, but I suspect if Python is for example, /usr/bin/python3.6 and /usr/lib/python3.6 the upgrade removes those and installs /usr/bin/python3.8 and /usr/lib/python3.8, that you could just create symlinks from /usr/bin/python3.6 and /usr/lib/python3.6 to /usr/bin/python3.8 and /usr/lib/python3.8 respectively and it would work. On the other hand, if the symlinks in the venv are to things like /usr/bin/python3 and /usr/lib/python3 which used to point to 3.6 versions and after upgrade point to 3.8 versions, it should just work. As far as installing Python3.8 on Ubuntu 18.04 goes, the machine I'm typing this on is Ubuntu 18.04 and has 6 different Python3 versions mark@msapiro:~$ /usr/bin/python3.5 --version Python 3.5.2 mark@msapiro:~$ /usr/bin/python3.6 --version Python 3.6.9 mark@msapiro:~$ /usr/local/bin/python3.6 --version Python 3.6.12 mark@msapiro:~$ /usr/local/bin/python3.7 --version Python 3.7.9 mark@msapiro:~$ /usr/local/bin/python3.8 --version Python 3.8.7 mark@msapiro:~$ /usr/local/bin/python3.9 --version Python 3.9.1 and /usr/bin/python3 is a symlink to /usr/bin/python3.6 and /usr/local/bin/python3 is a symlink to /usr/local/bin/python3.9, so take your pick... -- 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: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/23/24 23:36, vogt(a)spamcop.net wrote: > > I have tried anything I could think of but I cannot reproduce the issue using curl as user mailman (or any other for that matter) > > Going directly for localhost:8000, using some or all of the headers I can capture with tcpdump: > > ``` > $ curl -v -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… > ``` > > as well as going through the local httpd: > > ``` > $ curl -v --http1.1 -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' https://lists.example.org/mailman3/api/templates/list/community.lists.examp… > ``` > > Running tcpdump during those runs shows me it's sending the same headers as mailman does. Thus on http protocol level it's the same, but still the server returns immediately. > > What I have just noticed is that the Date header in the delayed response is the "late" time. I have even compared tcp headers from either capture. They look identical down to the frame sizes. > > The only difference the last times is that with curl, the server side sends the ACK for the request and milliseconds later a PSH,ACK with the response headers. When it comes internally from mailman it sends the ACK for the request and then 5 seconds later it sends the PSH,ACK with the response headers. I'm unable to explain what's going on. You could try one more thing in an attempt to duplicate this outside of Mailman. Invoke the same python3 that Mailman does - this may be in a venv or the system python3. If in a venv, you don't need to activate the venv, just run venv/bin/python. Then in response to Python's prompts do ``` >>> import requests >>> res = requests.get('https://lists.example.org/mailman3/api/templates/list/community.lists.examp…', timeout=5) ``` and see what that does? I think it should time out because this is exactly what Mailman core is doing tho get the template, and if it does, perhaps you can determine why from this simple example. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: list admin via email

by Mark Sapiro

On 10/28/21 9:33 AM, Christian Stalberg via Mailman-users wrote: > I'm unclear on how to approve via email a message sent to a list. > > As list owner you receive a 'requires approval' email. It then says: > > "If you reply to this message, keeping the Subject: header intact, Mailman > will discard the held message. Do this if the message is spam. If you > reply to this message and include an Approved: header with the list password > in it, the message will be approved for posting to the list. The Approved: > header can also appear in the first line of the body of the reply." > > Question: if I want to approve the message, where do I "...include an > Approved: header with the list password in it" ? First of all, the required password is the list's moderator password. If the list was imported from Mailman 2.1 and the list's moderator password was set there, it was imported. Otherwise, you must set one. You can't currently do this via postorius it has to be done via `mailman shell` or via the REST API. Via REST, something like ``` curl --user restadmin:restpass -X PATCH --data 'moderator_password=new_password' http://localhost:8001/3.1/lists/list.example.com/config ``` should do it. Via `mailman shell` you need to encrypt the password before setting it. e.g. ``` mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.config import config >>> m.moderator_password = config.password_context.encrypt('new_password').encode('utf-8') ``` That said, the message to which you refer has three MIME parts and what you quote is from the message/rfc822 part at the end and "reply to this message" means reply to the message in that part, not to the message you received. I.e you have to reply to the -request address with the appropriate `confirm <token>` in the Subject: Then if your MUA makes it easy, you can include the password as the value of an Approved: header in that reply. Otherwise, you can include ``` Approved: ... ``` as the first line of the plain text reply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Mailman 3.2.0 Hyperkitty fulltext index error

by Mark Sapiro

On 7/12/18 7:34 AM, Marvin Gülker wrote: > Hi, > > I've just upgraded to Mailman 3.2.0 (finally everything Python 3 now, > thanks!) and it appears to work. However, there's a repeating error > message in mailman-suite's logfile for Hyperkitty that looks like this: > > ERROR 2018-07-12 14:28:33,895 2742 hyperkitty.lib.utils Failed to update the fulltext index: ord() expected a character, but string of length 0 found > Traceback (most recent call last): > File "/home/mailman/env3/lib/python3.5/site-packages/hyperkitty/lib/utils.py", line 179, in run_with_lock > fn(*args, **kwargs) > File "/home/mailman/env3/lib/python3.5/site-packages/hyperkitty/search_indexes.py", line 115, in update_index > update_cmd.update_backend("hyperkitty", "default") > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/management/commands/update_index.py", line 276, in update_backend > last_max_pk=max_pk) > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/management/commands/update_index.py", line 97, in do_update > backend.update(index, current_qs, commit=commit) > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/backends/whoosh_backend.py", line 178, in update > self.setup() > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/backends/whoosh_backend.py", line 126, in setup > self.index = self.storage.open_index(schema=self.schema) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/filedb/filestore.py", line 176, in open_index > return indexclass(self, schema=schema, indexname=indexname) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 421, in __init__ > TOC.read(self.storage, self.indexname, schema=self._schema) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 632, in read > check_size("int", _INT_SIZE) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 626, in check_size > sz = stream.read_varint() > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/filedb/structfile.py", line 191, in read_varint > return read_varint(self.read) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/util/varints.py", line 102, in read_varint > b = ord(readfn(1)) > TypeError: ord() expected a character, but string of length 0 found > > The error repeats every minute, so I suppose it comes from the minutely > cronjob. This cronjob looks like this: This is due the the change from Python 2.7 to Python 3. The existing search index is not compatible with Python 3 whoosh. I fixed this by deleting all the files in the index directory which is defined as PATH in HAYSTACK_CONNECTIONS in your settings and running 'django_admin update_index', but just running 'django_admin rebuild_index' should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Error while running mailman-web compilemessages

by Prasanth Nair

Thanks Steve. On Wed, 20 Jul 2022 at 15:39, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/20/22 06:16, Prasanth Nair wrote: > > Hello, > > > > I'm in the process of installing a Mailman3 server. I get the following > > error messages when I run the command 'mailman-web compilemessages'. It > was > > working fine before and noticed this recently. Can someone suggest a > > solution to solve this issue, please? > > > This is a bug in the Arabic localization in django-extensions 3.2.0. See > https://github.com/django-extensions/django-extensions/issues/1744 > > If you aren't concerned about Arabic, just ignore those messages. > > > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years

[MM3-users] Re: mailman findmember runs very slow

by Wong, Wesley

Thanks for the fix, Mark. I tested the fix and query times are now under 2 s. wesley ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, July 13, 2024 4:36 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: mailman findmember runs very slow Wong, Wesley wrote: > Hi, I am noticing a performance issue with Mailman 3 when using the "mailman findmember" CLI command to search for email address or name. A fix has now been committed for the next release. See https://gitlab.com/mailman/mailman/-/merge_requests/1239<https://gitlab.com/mailman/mailman/-/merge_requests/1239> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to wesley.wong(a)anderson.ucla.edu

1 year

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

by Mark Sapiro

On 6/15/20 8:47 AM, rongxinliu(a)cs50.harvard.edu wrote: > > We tried deleting this mailing list and recreating a new one, but no luck. We also tried restarting mailman, and the issue persists. When looking at the mailman.log, messages sent to this problematic mailing list are accepted and archived successfully without a noticeable issue. > > In the smtp.log, also no errors are found except one line "Connection lost during _handle_client()", but this is true for all other mailing lists. Yes, that's normal. ... > However, the mailing list having issue will just stop at: > ....... > Jun 15 14:04:29 2020 (23) Connection lost during _handle_client() There are a couple of things. The post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… includes the log message: Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 This is strange as it says that Mailman is trying to connect to hostname `postfix`. Is this actually a legitimate host name on the Mailman server that Mailman can connect to? However, it doesn't seem that this is the issue as that name comes from the smtp_host setting in the [mta] section of the configuration and is global so if it were wrong, it would affect all lists. The fact that there is nothing after "Connection lost during _handle_client()" message means only that the message wasn't successfully delivered. A database issue seems unlikely. Set [logging.smtp] level: debug in mailman.cfg and see if the increased logging helps. It seems to me that the most likely issue is a list member whose address in an smtp RCPT TO command causes some issue with the MTA. Does the MTA actually see a connect and commands for the delivery attempt. I'm also confused by > The out-runner keeps creating new .pck and .bak files endlessly whenever an email gets sent to this mailing list. Mailman should create a .pck in the out queue. Then the out runner processes it and renames it as a .bak during processing for recovery purposes and when done processing removes the .bak. If in the process it encounters retryable errors for one or more recipients, it will remove the successful and perm failure recips from the metadata and queue the message in the retry queue. It should never be just requeueing the message in the out queue. -- 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: External MTA incoming mail: configuration

by Mark Sapiro

On 7/30/24 11:18, Roland Giesler via Mailman-users wrote: > > Now, lists.fast.za.net is the mailman server. The docs say that mailman > passes these on to the MTA. However, the MTA (postfix) on > box2.gtahardware.co.za has the following setting in it main.cf: The docs are badly worded. "but also will be passed to the MTA to identify the Mailman host." means passed manually in the MTA's configuration. > virtual_transport=lmtp:[127.0.0.1]:10025 You should not be using virtual_transport. You should be using transport_maps. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > If I reply to a signup confirmation email for example, the mail is > received and processed by box2.gtahardware.co.za, and it is not passed > on to the mailman server. It appears you have a situation where the MX for the Mailman domains is not the Mailman server. You need to configure the MTA on box2.gtahardware.co.za to relay Mailman's mail to the mailman server. You can to this by configuring that MTA to use transport_maps, etc as if it were the Mailman server. In order to get Mailman's generated files on the other server, you need to create a process to do that. When Mailman makes changes by adding or deleting lists or when it is started, it updates the postfix_lmtp and postfix_domains files and calls a command (normally postmap) to update the corresponding .db files. The command can be set by setting `postmap_command` in the `[postfix]` section in mailman.cfg. You can set this to a process which accepts a file name argument and then runs postmap on the file and rsyncs the file and it's .db to the other server. > So what is meant by "but also will be passed to the MTA to identify the > Mailman host" in the docs? As I said, that's badly worded it means 'passed manually to the MTA's config'. > If I change the config of the MTA (postfix) to be > "virtual_transport=lmtp:[lists.fast.za.net]:8024", I assume the incoming > mail will be forwarded, but how does postfix know that only the mailman > emails should be forwarded and not all the other mail that the server at > box2.gtahardware.co.za receives? Using transport_maps you can forward only list mail. -- 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: mailman import21 passwords

by Mark Sapiro

On 9/16/24 18:18, Sam Darwin via Mailman-users wrote: > >> inherently not secure > > The passwords were good enough for mailman2. If a mailman2 instance has been in production for 20 years and users aren't complaining about security, maybe it's not a show stopper There are regular complaints dating back at least to <https://bugs.launchpad.net/mailman/+bug/265179> about passwords mailed in the clear. > The point is to make the upgrade seamless. That means... being able to say that everyone gets to keep their user account and password. To be able to easily tell the users "Your account is still the same. Just log in. Change your password when you like." But is it "the same"? What about an import of two lists with members which are the same person, but with possibly separate email addresses and/or passwords? Do we really want to create multiple Django users, or let the user create one Django user with multiple addresses? > In the current context, passwords are associated with django accounts rather than mailman-core accounts. So this is about creating django users. > >> creating a django user is "expensive". "poor performance" > > I didn't follow what that means. What is expensive? What is poor performance? I pointed to <https://mail.python.org/archives/list/mailman-developers@python.org/thread/…> which discusses the performance issue as a reason for dropping the import of MM 2.1 passwords. > Creating new django accounts en masse would be a one-time operation. It doesn't matter if it's slow, or expensive, since it only happens once. While probably not typical, mail.python.org currently has (still) 209 MM 2.1 lists with 40261 unique member addresses. Creating 40261 Django users, even just one time would probably be painful. > And it would be optional. With the --django-accounts flag. Or another separate script. Then you can tell users "Your account is the same as before. A transparent upgrade. Just log in". I really don't understand why telling the user that she has an account and she can just log in with one of the N MM 2.1 passwords she had on the N MM 2.1 lists or get a reset email if she doesn't know or remember the password(s) is any easier for the user than telling her to go to ... and sign up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Message Personalization: embed User name in header/footer‏

by Asaf Ohayon

Thanks I edit the file mailman/core/var/templates/site/en/list:member:generic:footer.txt : _______________________________________________ Thanks $user_name $display_name mailing list $fqdn_listname https://mailman.sysbind.biz/lists/$fqdn_listname/ FOOTER All the variables are expanded correctly when i recieve the email, but $user_name remains unexpanded Is there any option to enable in order for $user_name to be available ? ‫בתאריך יום א׳, 6 במאי 2018 ב-17:27 מאת ‪Mark Sapiro‬‏ <‪mark(a)msapiro.net ‬‏>:‬ > On 5/6/18 7:16 AM, Asaf Ohayon wrote: > > Thanks, > > I understand those features are not available (yet) on Postorius > We're working on getting template editing in Postorius for release later > this month. > -- > 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/ -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

7 years, 2 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 1:28 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > <snip> > > However, those are from cron jobs and say nothing about the wsgi process > that runs the web UI and the hyperkitty api. > OK, I see uwsgi running in process table. PID USER TIME COMMAND 1 mail 0:13 uwsgi --ini uwsgi.ini 7 mail 1h11 uwsgi --ini uwsgi.ini There is only one uwsgi.ini file, and it is in the same directory as settings.py, settings_local.py and wsgi.py I'll see if I can find some logs for uwsgi that might provide some more insight. Thanks! -p > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

2 years, 8 months

[MM3-users] Re: urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Mark Sapiro

On 1/18/22 4:20 AM, Axel Rau wrote: > > While selecting a list in the browser, I’m getting: > - - - > Traceback (most recent call last): > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch > return handler(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get > 'hyperkitty' in archivers and # noqa: W504 > File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ > self[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ > return self._get(key) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get > return self.rest_data[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} The above seems to be from Django's log. What's in Mailman core's mailman.log? > Question: Am I missing aliases in my nginx.conf? > I just have: > - - - > location / { > uwsgi_pass unix:///tmp/uwsgi.sock; > include /usr/local/etc/nginx/uwsgi_params; > } > > location /static { > alias /usr/local/mailman3/static; > } > > location /static/favicon.ico { > alias /usr/local/mailman3/static/postorius/img/favicon.ico; > } > - - - I don't use uwsgi so I'm not sure, but I think the above is OK. This list's host uses gunicorn and has location / { proxy_pass http://127.0.0.1:8000/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } The only locations beyond what you have above are for /robots.txt and /favicon.ico -- 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 did this: (env) [mailman@localhost mailman-suite_project]$ pip install Django Requirement already satisfied: Django in /var/lib/mailman/env/lib/python3.6/site-packages Requirement already satisfied: pytz in /var/lib/mailman/env/lib/python3.6/site-packages (from Django) Does Django is already installed?? with python3.6 ??? El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Hyperkitty download mbox

by Mark Sapiro

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

4 years, 3 months

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

by Mark Sapiro

On 1/11/22 7:08 AM, Michal Soltys wrote: > Hi, > > I have noticed that any mail send with text/html, e.g. with following > headers: > > Content-Language: en-US-large > Content-Type: text/html; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > is slightly transformed by mailman3 - the body is put into its own part, > but all the international letters are replaced by question marks. The body being put in its own part is because of message decoration. In order to add the list's message header and/or footer the message is recast as multipart/mixed and the header and/or footer are added as separate MIME parts. See https://wiki.list.org/x/4030707 for an explanation of why this is done for non-plain text messages. > Having searched the list I tried: > > 1) adding following to mailman.cfg: > > [language.master] > description: English (USA) > charset: utf-8 > enabled: yes > > [language.en] > description: English (USA) utf8 > charset: utf-8 > enabled: yes I would have expected that to work. > 2) changing preferred language of a mailing list to something else via > shell, e.g.: > > m.preferred_language = 'pl' That should be m.preferred_language = getUtility(ILanguageManager).get('pl') > > 3) changed default_language to 'pl' in mailman.cfg I would have expected any of those things to work, but I can see that they don't. I'm looking into why. > 4) Ensured all relevant glibc locales are generated (not sure if that > matters though in this case) > > > None of this seems to have any positive result - all mails, whether > under 'pl' or 'en' setting still get all non-ascii chars replaced with > question marks (in html case, probably(?) in any case where it becomes > multipart). > > Any ideas what to do so html mails are passed without filtering out > their characters ? Do I have to recreate all mailing lists under new > [language.en/master] settings ? No, this is a bug. It has to do with message decoration (adding of headers and footers). You can probably avoid this issue by setting the list's filter_content and convert_html_to_plaintext to True. I am looking at why this occurs and fixing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Any good ideas on how to troubleshoot django allauth

by Mark Sapiro

David Krantz wrote: > > I found a solution that so far seems to work. The culprit was that the > machine had python-openssl and python3-openssl installed. After > removing them I have so far not seen any error. It turns out that unbeknown to me I had the same issue. I manage MM 3 installations at lists.mailman3.org and mail.python.org/mm3. I support django-allauth OAuth2 authentication using GitHub, GitLab, Google and Facebook on both. On lists.mailman3.org everything was working fine. On mail.python.org/mm3 all OAuth2 login attempts produced a 500 server error and a traceback in the mailman-web log similar to > ERROR 2017-04-23 18:51:39,501 base 3673 139978913507072 Internal Server Error: /mm3/accounts/google/login/callback/ > Traceback (most recent call last): > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.13-py2.7.egg/django/core/handlers/base.py", line 149, in get_response > response = self.process_exception_by_middleware(e, request) > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.13-py2.7.egg/django/core/handlers/base.py", line 147, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/django_allauth-0.27.0-py2.7.egg/allauth/socialaccount/providers/oauth2/views.py", line 62, in view > return self.dispatch(request, *args, **kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/django_allauth-0.27.0-py2.7.egg/allauth/socialaccount/providers/oauth2/views.py", line 120, in dispatch > access_token = client.get_access_token(request.GET['code']) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/django_allauth-0.27.0-py2.7.egg/allauth/socialaccount/providers/oauth2/client.py", line 74, in get_access_token > auth=auth) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/api.py", line 56, in request > return session.request(method=method, url=url, **kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/sessions.py", line 488, in request > resp = self.send(prep, **send_kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/sessions.py", line 609, in send > r = adapter.send(request, **kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/adapters.py", line 497, in send > raise SSLError(e, request=request) > SSLError: bad handshake: SysCallError(0, None) I only discovered this because I saw the ERROR entries in the log while looking for something else. In any case, it turned out that python-openssl was installed on mail.python.org and not on lists.mailman3.org. Removing it from mail.python.org allowed OAuth2 logins to work. We'll see if its removal broke something else that depended on it :( -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

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

by Mark Sapiro

On 9/21/20 10:49 AM, peterbw(a)gmail.com wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com > cc: listserv(a)lists.test.org; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com > cc: listserv(a)lists.test.org, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org, "Williams, Peter" <peters_real_address(a)example.com> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com cc: other_user(a)gmail.com; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com and other_user(a)gmail.com receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- 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: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 6:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 21:25, Odhiambo Washington wrote: > > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> See > >> > >> > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > >> for mitigation. > > > > > > What is the danger of replacing my settings.py with this one, seeing as > it > > differs in a number of ways with mine? > > > If your's works, don't do it. The danger is the differences might be > significant and break things. Also, that one is for HyperKitty only and > doesn't include Postorius settings. > So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Internal Server Error: /hyperkitty/list/my@lists.domain.eu/pop-threads

by Mark Sapiro

On 2/21/21 3:09 AM, Marco Marinello wrote: > Dear all, > > I've setup my own instance of Hyperkitty working as archiver of a Mailman 3 server. > It works fine but, sometimes, I get an email of a Django error: > > Internal Server Error: /hyperkitty/list/my(a)lists.domain.eu/pop-threads > > KeyError at /hyperkitty/list/my(a)lists.domain.eu/pop-threads > 'file' The above is not the issue. It results from Django trying to look up a log file in the LOGGING configuration. > Request Method: GET > Django Version: 2.2.12 > Python Executable: /usr/bin/python3 > Python Version: 3.7.3 > Traceback: > > File "/usr/local/lib/python3.7/dist-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/local/lib/python3.7/dist-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/local/lib/python3.7/dist-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/local/lib/python3.7/dist-packages/hyperkitty/lib/view_helpers.py" in inner > 129. if not is_mlist_authorized(request, mlist): > > File "/usr/local/lib/python3.7/dist-packages/hyperkitty/lib/view_helpers.py" in is_mlist_authorized > 146. if mlist.list_id in get_subscriptions(request.user): > > File "/usr/local/lib/python3.7/dist-packages/django_mailman3/lib/mailman.py" in get_subscriptions > 130. _get_value, 60, version=2) # 1 minute > > File "/usr/local/lib/python3.7/dist-packages/django/core/cache/backends/base.py" in get_or_set > 167. default = default() > > File "/usr/local/lib/python3.7/dist-packages/django_mailman3/lib/mailman.py" in _get_value > 122. for member in mm_user.subscriptions > > File "/usr/local/lib/python3.7/dist-packages/mailmanclient/restobjects/user.py" in subscriptions > 66. 'members/find', data={'subscriber': address}) > > File "/usr/local/lib/python3.7/dist-packages/mailmanclient/restbase/connection.py" in call > 112. error_msg, response, None) > > During handling of the above exception (HTTP Error 500: <html> > <head> > <title>Internal Server Error</title> > </head> > <body> > <h1><p>Internal Server Error</p></h1> > > </body> > </html> What's happening is HyperKitty is trying to determine if the request comes from a list member, and that throws an exception resulting in the 500. What's in Mailman core's mailman.log? Is Mailman core's REST API even accessible from this HyperKitty instance. If not, you can't support private archives and will probably have other issues? -- 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: Transaction failed: Duplicate header 'DKIM-Signature'

by Mark Sapiro

On 4/13/23 07:25, Mohsen Masoudfar wrote: > I am observing the following error message in the logs for one specific list: > > = = = > relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) > = = = This is non-compliant. Various parts of RFC6376, e.g. sections 5.6 and 6.1 clearly anticipate that a message can contain multiple DKIM-Signature: headers. > As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: Is email-smtp.us-east-1.amazonaws.com the outgoing MTA for Mailman. I.e the value reported by `mailman conf -k smtp_host` or perhaps smtp_host is a local MTA which is configured to relay via email-smtp.us-east-1.amazonaws.com? In what log is that message? Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. > > = = = > To distribute messages with valid DKIM signatures, I set > remove_dkim_headers: yes > in /etc/mailman3/mailman.cf > = = = > > Here are my questions: > 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. This setting will remove all DKIM headers from the message as Mailman receives it. Then, it depends on how and how many DKIM signatures are added to the outgoing mail. > 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? No, there is no such option. The fact that this happens for only one list is very strange. I would need more information to understand why. Do these messages get queued in Mailman's retry queue? If so, if you examine one such message with `mailman qfile`, what are the complete headers from that message. -- 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: One-click unsubscribe?

by Mark Sapiro

On 2/4/25 20:24, Jered Floyd wrote: > > I'm having a lot of problems with GMail delivery due to lack of "one-click unsubscribe" -- however that is quantified, which is not clear. See the footer of this message which contains To unsubscribe send an email to mailman-users-leave(a)mailman3.org This is produced by To unsubscribe send an email to ${short_listname}-leave@${domain} in the template which is also in the default template. This seems sufficient for Google, as I don't see mail bounced for this reason. You might try adding a link to Postorius. You can't really link to an immediate unsubscribe as that requires the user be logged in (and the user may not even have an account) and it also required POST data, but for Mailman >= 3.3.10, you could add To unsubscribe send an email to ${short_listname}-leave@${domain} or go to $mailinglist_url This requires the domain have a base_url set. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> and this is not yet exposed in Postorius. See https://gitlab.com/mailman/postorius/-/issues/594 > In particular, there is an issue with the fact that Google ignores dots in email addresses. So I have many (MANY!) subscribers who try to use the List-Unsubscribe header target, but because they are subscribed as "idiotsubscriber(a)gmail.com" rather than "idiot.subscriber(a)gmail.com" (which they have since changed their sender to) they get a reject that they are not subscribed. These people are also far too unobservant to read the footer of every message that reads "You are subscribed as idiotsubscriber(a)gmail.com". > > Is there any way to provide personalized List-Unsubscribe header links, or have Mailman ignore dots in gmail.com addresses... or... anything? I'm finding reported spam percentages in the Google Postmaster Dashboard exceeding 0.1%, which causes massive delivery blocking to GMail-based subscribers. The List-Unsubscribe: header is added in the handler pipeline by mailman/handlers/rfc_2369.py. At his point in the process the message is still generic so the header can't be personalized. The mailman/handlers/decorate.py handler can add personalized content so could modify the List-Unsubscribe: header to add the recipient's email address except at least at present this won't work because emails to listname-leave or listname-request with a leave or unsubscribe command currently only look at the sender of the email for the address to unsubscribe. -- 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: Installing mailman 3

by Rafael Mora

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them: [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 Should I run any command to activate the CACHE dir? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 11 months

[MM3-users] Re: mailman changeaddress: Address already exists; can't change

by Mark Sapiro

On 10/10/24 8:58 AM, joelbrownstein(a)computer.org wrote: > Hi, > > We migrated ~100 lists from mailman2 to mailman3 (very nice!) including > 6000 distinct email addresses ("subscribers"). > > I would like to run the mailman changeaddress command to do a global change of email for a member that moved. But they have other subscriptions using their new email, so both the old and new address are migrated to mailman3 as distinct "members", which prevents the mailman changeaddress from making the change with error: > > $ mailman changeaddress "EMAIL_1" "EMAIL_2" > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address "EMAIL_2" already exists; can't change. There is a major difference between MM 2.1 and MM 3 in this respect. In MM 2.1, a list member is an email address that bears no relation to any other member of this or any other list. In MM 3, there is a user which corresponds to a person which has one or more email addresses which can be members of lists with various roles. What happened here is importing the MM 2.1 lists created a user for EMAIL_1 and subscribed it to some lists an created a separate user for EMAIL_2 subscribed the other lists. You can't change EMAIL_1 to EMAIL_2 because EMAIL_2 is already a separate user. There are two ways to deal with this. You can use `mailman findmember EMAIL_1` to list all of EMAIL_1's memberships and edit that to make a shell script that will do `echo EMAIL_2|mailman addmembers -f - LISTNAME> to add EMAIL_2 to all of EMAIL_1's lists and then do `mailman delmambers -m EMAIL_1 --fromall` You could do direct database manipulation. First get the id and user_id of the address table entries for email = EMAIL_1 and EMAIL_2. If we call them aid_1, uid_1, aid_2 and uid_2, do ``` UPDATE member SET address_id = aid_2, user_id = uid_2 WHERE address_id = aid_1; ``` Caveat: I haven't done this. I think it should work, but no guarantees. Backup the database first in case of problems. After doing either of the above, there will still be a user with address = EMAIL_1, but that user should have no subscriptions. You can delete that user via Postorius and if desired the remaining user with address EMAIL_2 could add EMAIL_1 as another address. -- 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: Installing mailman 3

by Rafael Mora

I did not interrupt the running process... It's running, but I cannot see anything El vie., 21 jul. 2017 a las 16:08, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:00 PM, Rafael Mora wrote: > > Yes I did ran it in the env2 python2 virtualenv, it > > says: ERR_CONNECTION_REFUSED > > I stopped the firewalld service and it's still refused > > > After you ran 'manage.py runserver' did you leave that terminal window > open with that process running? If you control-C or interrupt it in any > way, it stops listening. > > > > I installed uwsgi, should I put the config inside mailman.cfg?? > > > Not yet. That's for production. I don't think you're there yet. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Postorius not HTML-decoding < to "<" characters

by Mark Sapiro

> > Does that mean the DB has data with mismatched tags in it? The database has exactly what list members receive by email. What we are talking about is how this is rendered in HyperKitty. > Interestingly, the quoted part of my message has < where my message > has proper less-than and greater-than for the Apache tags. > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > It's inconsistent with the archive rendering mode at lists.mailman3.org. Here's what's going on. In normal text, mistune disables HTML tags by converting `<` to the html entity `<`, but your browser renders the HTML entity `<` as `<` so you see what was written. The issue here is the text you quoted was originally in a markdown code block, i.e. preceded and followed by lines of three backticks. Code blocks are intended to be seen literally as written so they are wrapped in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. The problem is the tag disabling converts `<` to `<` but then the HTML escaping converts `<` to `&lt;` which your browser then renders as `<` rather than `<`. (aside, it will be interesting to see how that is rendered in the archive) If HyperKitty is set to render as plain text rather than markdown it doesn't interpret code blocks so this doesn't happen. There are other anomalies with the markdown rendering, e.g., as pointed out by Jeremy at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Those notwithstanding, we prefer markdown rendering for this list because often people post Python snippets or `mailman shell` interactions and enclosing those in markdown code blocks renders them much better. > I haven't currently got an instance that I can test on but will keep > this in mind when the time comes to migrate. > > Should the rendering at lists.mailman3.org get modified, please share > the procedure. > > > > Testing: less-than and greater-than around a tag: > > <Location /mailman/accounts/signup> > > Testing: less-than and greater-than around a tag in a quoted block: > > > <Location /mailman/accounts/signup> Both the above tests look fine 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

8 months, 3 weeks

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Mark Sapiro

On 10/31/18 5:57 AM, Thomas G wrote: > Hi, > > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… > > I changed "sender" for this; > # Sender > try: > from_str = header_to_unicode(message['From']) > from_name, from_email = parseaddr(from_str) > from_name = unidecode.unidecode(from_name).strip() What is unidecode? > except (UnicodeDecodeError, UnicodeEncodeError): > raise (ValueError("Non-ascii sender address", message)) > > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown(a)unknown.com" > else: > sender_address = "unknown(a)unknown.com" > print("Non-ascii sender addre -- Sender address replaced by ", > sender_address) > > I got this output (example): > |Non-ascii sender address -- Sender address replaced by > stephaneblipblopstlablipblopgmailcom > It's not really perfect, I'm working to do something better, but basically > it's works. The original code intends to provide some value for the email address where parseaddr returns a null address. You have an address, and you would do better to remove the non-ascii from the address than to try to make and address out of the sanitized real name. Your issue is parseaddr() returns an email address with non-ascii. I would suggest that instead of > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown(a)unknown.com" > else: > sender_address = "unknown(a)unknown.com" you do > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > sender_address = from_email.encode('ascii', errors='replace').decode("ascii").strip() > I think that there is a issue in the original code: > Because : "" raise ValueError("Non-ascii sender address", message) "" > > The second part will be never call: It will if there is no exception. > if not sender_address: > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown" > sender_address = "{}(a)example.com".format(sender_address) > else: > sender_address = "unknown(a)example.com" > > If you bypass : "" raise ValueError("Non-ascii sender address", message) > "", by a simple print(), you will get an error due to an unassigned > variable (sender_address). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: How to delete non-users

by Mark Sapiro

On 9/16/22 11:19, Allan Hansen wrote: > Hi all, > > This is a bit of an emergency: > > I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. > For individuals I have been able to delete their non-membership and they then could subscribe properly. I don't understand. the fact that an address is a non-member of a list should not impact subscribing that address as a member. > I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. What is actually happening when the non-member attempts to subscribe as a member? What do they do and what it the result? > I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). > > Can anyone help me find out how to > a. delete all non-members of all my lists If you have access to `mailman shell` you could do: ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> commit() ``` > b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) nonmembers are an integral part of Mailman 3's architecture. The basic idea is a nonmember has a moderation action and setting a nonmembers moderation replaces MM 2.1's adding that address to one of *_these_nonmembers (The legacy *_these_nonmembers attributes still exist, but only to support regexps). It would require extensive modification to not create nonmembers. However, I still don't understand why the presence of a nonmember record is an issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: 500 Internal Server Error on specific list pages

by Mark Sapiro

On 7/30/20 9:05 AM, Johnny Cison wrote: > The Mailman logs contain the following: > > Jul 30 10:32:11 2020 (26190) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, > in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ > (falcon/api.c:2872) > File "falcon/api.py", line 189, in falcon.api.API.__call__ > (falcon/api.c:2419) > File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 346, in > on_get > archiver_set = IListArchiverSet(self._mlist) > File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line > 135, in __call__ > adapter = self.__adapt__(obj) > File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line > 151, in __adapt__ > adapter = hook(self, obj) > File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, > in adapter_hook > return sitemanager.queryAdapter(object, interface, name, default) > File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line > 348, in queryAdapter > return self.adapters.queryAdapter(object, interface, name, default) > File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line > 353, in queryAdapter > return self.adapter_hook(provided, object, name, default) > File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line > 363, in adapter_hook > result = factory(object) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line > 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2793, > in one_or_none > "Multiple rows were found for one_or_none()") > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() This is a known issue <https://gitlab.com/mailman/mailman/-/issues/657>. There are two entries for the same `mailing_list_id` and `name` in the listarchiver table in the database. We don't know how this happens, but you need to delete one (either one) of the duplicates. Also see the recent thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. If you have any idea about how this might have occurred in your case, let us know. -- 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: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 9:23 AM, Mohsen Masoudfar wrote: > > 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. > After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" This is <https://gitlab.com/mailman/mailman/-/issues/417> fixed by <https://gitlab.com/mailman/mailman/-/merge_requests/329> in Mailman core 3.2.0. Either upgrade Mailman core or set it via `mailman shell` > 2- I checked the python files and found this file, where, it seems, the default value is defined: > /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 > > I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: > The message is being held because: The message is larger than the 40 KB maximum size Changing that file only affects the default setting for new lists. It doesn't affect any existing list. To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like $ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> m.max_message_size 40 >>> m.max_message_size = 0 >>> commit() > 3- I totally agree that the most important issue is the fact that the message vanished with the production list. > I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. > > 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ OK, but what if anything is in 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, 10 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 3:41 PM, David Newman wrote: > > There are 24 messages in the shunt queue, the most recent of which is a > digest from 0000 hours today. The test messages I sent later today are > not there. > > There are also 13 messages in the out queue. I can't read these as the > filenames appear to change on every invocation of ls. I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/* >> Are there errors and tracebacks in var/logs/mailman.log? Every message in the shunt queue should have an exception and traceback logged in mailman.log. > But the Postfix log doesn't show it being distributed to me or anyone else. Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log? > Oddly, neither of the two list owner emails (me and someone else) show > this message in the archive via the admin panel. However if I log in as > the list owner directly to the archives: > > https://lists.domain.tld/archives/ > > I can see today's test posts if logged in as the list member, but do not > see the posts if logged directly into the archive as the Django superuser. That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can. > The nondelivery of list mail is more serious than the archive problem, > though. Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why? I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory. I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with `mailman qfile` and unshunt (reprocess) them with `mailman unshunt`. -- 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 made a change for test purpose on the mailman.cfg file and I got this: (env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running? How do I solve this? El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server

by Mark Sapiro

On 11/28/24 12:01 AM, peterrflores(a)hotmail.com wrote: > > Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? This is how things work. See for example https://mail.python.org/mailman3/?all-lists - each of those lists has its own settings. There are also `unadvertised` lists on that server, e.g. https://mail.python.org/mailman3/lists/capi-sig.python.org/ > Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. Mailman core provides a REST API for list management. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - this interface is only protected by a user name and password, so it is normally only available via `localhost` as wider access is not very secure. Postorius uses this API via the python bindings described at https://docs.mailman3.org/projects/mailmanclient/en/latest/ > Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. A list can be anonymous id desired which means the sender of a post is not identified in any headers of the distributed email. HyperKitty archives can be private, i.e. accessible only to list members. The membership list can be restricted to only list owners/moderators or available to list members as well via list settings. There is currently no support for encrypted email. Full access to a list's settings and other info via Postorius is limited to logged in users who are either a `superuser` or an owner of the list. moderators have more limited access, list members may be allowed to see the membership. -- 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: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 17:24, Mark Sapiro wrote: > On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 16/9/21 16:40, Mark Sapiro wrote: >>> >>> Are you asking what the equivalent MM 3 scripts would be? >>> >> More or less: I'm asking for a general direction here. I think I >> cannot use tthe "withlist" method as before, inside a python script, >> and I'm not sure how to do it. > > > You can run scripts via withlist in Mailman 3 similarly to Mailman 2. > See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > First, thanks for the prompt response, Mark. Maybe I'm a little bit ofuscated, but I readed this doc many times when I was searching how to do it... but I cannot imagine how to do a shell or a python script, using the needed parameters, that sets hold on a member of a list. I'll try to do some tests tomorrow. As said, thanks.

3 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I put this config in mailman.cfg: To configure Core to use Postfix, add the following configuration to your mailman.cfg configuration, be sure to replace mail.example.com with your email domain: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 is this correct?? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.

by Mark Sapiro

On 10/30/19 2:08 AM, Henrik Rasmussen wrote: > > It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. That's probably correct, but not the exact reason. > However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. > > I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? To understand, you need a bit of background. The basic engine that manages lists, subscriptions, users, etc. is Mailman core. Core does not provide any web UI. It only provides a REST API for use by other components. It is possible to run Mailman core only without any web UI, but management would need to be done directly via the REST API and/or `mailman shell` which is not particularly convenient. Because Mailman would not be too useful without a web management UI and a web based archiver, we provide Postorius and HyperKitty for these functions. These are only one possibility. One could build an entirely different web UI or other application to communicate with core via its REST API, but few if any have done so. Postorius and HyperKitty are Django projects and run under Django. The account that you see (Postorius top right) is a Django account. Core knows nothing about this. Core knows about users and addresses in its own database which is entirely separate from Django's accounts. These user/address records in core is where the user's display_name is kept. So when a user/address is added to a list, if core already knows that user/address, it just links that to the list and doesn't update the display_name, but if it doesn't know the user/address, it creates it and uses the supplies display name. It appears there is a mechanism within Postorius to detect a change in the name associated with a Django user and update core, but this is separate from subscribing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

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

by Odhiambo Washington

On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 02:16, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 1:37 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Isn't this just `mailman members --role nonmember LISTSPEC`? > >> > > > > I didn't know that the option was right in front of me, but it seems > there > > is a problem: > > GNU Mailman 3.3.10 (Tom Sawyer), Mailman Core API Version 3.1 > ... ^^^^^^^^^^^^^^^^^^^^^^^^ > > AttributeError: 'NoneType' object has no attribute 'display_name' > > > I saw that too. Reported > https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > https://gitlab.com/mailman/mailman/-/merge_requests/1297 It isn't clear to me what I should do to mitigate the error. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

7 months, 1 week

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/26/19 7:00 AM, Alain Kohli wrote: > I have noticed that especially the var/messages directory has a rather > considerable size compared to the rest. What exactly is this for and > what would be the consequences if that was lost? When a message is held for moderator approval, a pickle of the message is stored in the var/messages directory and an entry pointing to it is made in the message table in the database. An entry is also made in the list's pending requests. These are required so the held message can be handled. There is an issue in that when these messages are handled these aren't removed. See <https://gitlab.com/mailman/mailman/issues/257>. Thus, most of what's in the var/messages directory is old, but there are also currently held messages there that would be lost. You could periodically remove older messages, but this would leave entries pointing to them in the message table in the database which could cause errors but probably not. The real solution is a fix for <https://gitlab.com/mailman/mailman/issues/257>. > And more generally, would not backing up var/ at all only result in the > loss of some short term data (e.g. messages that are held or currently > processed) or would long term data also be lost? Or in other words, what > exactly would be non-recoverable if that isn't backed up? That depends in part on what your backend database is. If it's SQLite, the database is probably in the var/data directory. If not, you need to be backing up the MySQL or postgreSQL mailman database. var/archives contains archived messages for the 'prototype' archiver and messages that are queued for hyperkitty. var/cache contains a cache of recently used templates. var/data may contain a SQLite database and may contain Postfix mappings. The Postfix mappings can be regenerated by the `mailman aliases` command. var/etc may contain your mailman.cfg if you don't point to a different one. var/lists contains accumulated messages for the next digest for your lists var/locks contains locks and should probably not be restored from a backup var/logs contains Mailman's logs. var/messages is discussed above. var/queue contains Mailman's current queues. Except for 'shunt' this is all things currently in process. var/templates may contain custom templates. Also, I didn't mention it before, but your Django settings.py and settings_local.py should also be backed up. -- 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: New Mailman 3 installation issues

by Mark Sapiro

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

4 years, 2 months

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

by Mark Sapiro

On 9/21/22 10:39, Dan Caballero wrote: > I figured out the correct import based on what was done previously. It worked. Why do you think you need to import anything? > ">>> from mailman.app.moderator import handle_message `handle_message` is not referenced in the following and doesn't need to be imported here. ``` >>>> 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) > ... > Bad request id: 1694, deleting > Bad request id: 2509, deleting > Bad request id: 2727, deleting > Bad request id: 3251, deleting > Bad request id: 3265, deleting > Bad request id: 3371, deleting > Bad request id: 4844, deleting > Bad request id: 6058, deleting > Bad request id: 6201, deleting > Bad request id: 6432, deleting > Bad request id: 6502, deleting >>>> commit ()" ``` I assume after doing this, you were able to access the held messages view for the list. Note that the only names referenced in the above and not defined there are `IListRequests` and `RequestType`, but these are among the many names implicitly imported by `mailman shell` in interactive mode. ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for name in dir(): ... print(name) ... ALL_TEMPLATES ALT_TEMPLATE_NAMES ALWAYS_REPLY AcceptEvent AcceptOwnerEvent Action AddressAlreadyLinkedError AddressError AddressNotLinkedError AddressVerificationEvent AlreadySubscribedError ArchivePolicy ArchiveRenderingMode BadDomainSpecificationError BounceContext ChainEvent ClobberDate ConfigurationUpdatedEvent ContinueProcessing DMARCMitigateAction DatabaseError DeliveryMode DeliveryStatus DigestFrequency DiscardEvent DiscardMessage DomainCreatedEvent DomainCreatingEvent DomainDeletedEvent DomainDeletingEvent DuplicateStyleError EmailError ExistingAddressError FilterAction FilterType HoldEvent IAPI IAcceptableAlias IAcceptableAliasSet IAddress IArchiver IAutoResponseRecord IAutoResponseSet IBan IBanManager IBounceEvent IBounceProcessor ICLISubCommand ICacheManager IChain IChainIterator IChainLink IConfiguration IContentFilter IDatabase IDatabaseFactory IDomain IDomainManager IEmailCommand IEmailResults IEmailValidator IHandler IHeaderMatch IHeaderMatchList ILanguage ILanguageManager IListArchiver IListArchiverSet IListManager IListRequests IMailTransportAgentAliases IMailTransportAgentDelivery IMailTransportAgentLifecycle IMailingList IMember IMembershipManager IMessage IMessageStore IMutableChain IOneLastDigest IPendable IPended IPendedKeyValue IPendings IPipeline IPlugin IPreferences IRoster IRule IRunner IStyle IStyleManager ISubscriptionManager ISubscriptionService ISwitchboard ITemplate ITemplateLoader ITemplateManager IUser IUserManager IWorkflowState IWorkflowStateManager InvalidConfigurationError InvalidEmailAddressError InvalidListNameError LinkAction ListAlreadyExistsError ListCreatedEvent ListCreatingEvent ListDeletedEvent ListDeletingEvent MailmanError MemberRole MembershipChangeEvent MembershipError MembershipIsBannedError MissingConfigurationFileError MissingPreferredAddressError MissingUserError NewsgroupModeration NoSuchListError NotAMemberError PasswordChangeEvent PendType Personalization RejectEvent RejectMessage ReplyToMunging RequestRecord RequestType Response ResponseAction RunnerCrashEvent RunnerInterrupt SomeRecipientsFailed SubscriptionConfirmationNeededEvent SubscriptionEvent SubscriptionInvitationNeededEvent SubscriptionMode SubscriptionPendingError SubscriptionPolicy TokenOwner TooManyMembersError UnrecognizedBounceDisposition UnsubscriptionConfirmationNeededEvent UnsubscriptionEvent UnverifiedAddressError __builtins__ abort commit config getUtility m >>> ``` -- 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: Counter-intuitive header filter processing

by Mark Sapiro

On 09/18/2018 01:04 PM, Jonas Meurer wrote: > > Maybe then the description for chain "accept" in postorius needs to be > adjusted. Currently it says "Accept immediately (bypass other rules)". > This gives the impression, that it will overrule the default action. Yes, I agree it's confusing. > A related followup question: what configuration is recommended for an > announcement list where only specific senders (e.g. sender(a)example.org) > should be allowed to post and mail from all (other) subscribers should > be rejected? > > The only way I see to achieve this currently is: > > * Set default action for member posts to "Default processing" > * Add a header filter to accept "sender(a)example.org" > * Add a header filter to reject ".*" > > In my eyes, that's very counter-intuitive and cumbersome to configure. > But maybe I just missed a more obvious and elegant solution to achieve > the same? The way to do that is to set the default action for member posts to Reject and set Member Options -> Administration options -> Moderation for the authorized posters to Accept or Default processing as desired. However, this allows anyone to post by spoofing an authorized address. To avoid that, leave everyone's Moderation setting at List default and post using "pre-approval" (see <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.ht…>. The downside of this is it requires the poster to send a cleartext password in a header or body line of the post. It will be removed from the post delivered to list members, but sending it in cleartext in an email may be an issue. We will eventually do something with PGP signatures instead, but that isn't here yet. > And one more comment: if I make the list an "anonymous list" (i.e. "hide > the sender of a message, replacing it with the list address"), then > header filters for the "from" header don't work any longer. That's kind > of unexpected as well. I would have expected mailman to process the > header filters at reading the incoming mail, not after rewriting headers > of the outgoing mail? Your expectation is correct. All the applicable rules are applied to the incoming message before any message alterations such as anonymizing are applied. Possibly you were confused because some other rule's action took precedence over your header rule. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: [ERROR] Error handling request List archivers

by Mark Sapiro

On 7/23/20 12:39 AM, Shashikanth Komandoor wrote: > Thank you Mark for guiding me to the benefit of putting the list and so I > have added the list. > > Along with the [archiver.hyperkitty], [mta] and [database], few lines of my > mailman.cfg look like below: > > > > [webservice] > workers = 4 > timeout = 900 > > The above block of webservice is added yesterday for testing or trail as I > am getting the above issue. > > And there is no line that is calling *gunicorn* in my mailman.cfg. As I tried to explain to you in an off-list reply: You can't configure Mailman's REST gunicorn workers directly in the [webservice] section of mailman.cfg. The only thing you can configure there is: configuration: /path/to/gunicorn.cfg That file, which is separate from your web server gunicorn.cfg, is where you put things like [gunicorn] timeout = 900 It also will not work to put a gunicorn section in mailman.cfg. It must be in a separate file pointed to by webservice.configuration. Increasing the number of workers won't help this issue. > Apart from that I tried to locate and see the content of the gunicorn.cfg > file 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. > graceful_timeout = 30 > > Please confirm the time I have to change is *graceful_timeout *in > *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I > have never used or never known about this *gunicorn* but still running the > service in production. First, the file you reference above is the default gunicorn configuration for the REST server. You don't want to edit this file because your changes will be overridden in an upgrade. You want to create your own gunicorn.cfg file and point to it by adding configuration: /path/to/your/gunicorn.cfg to the webservice section in your mailman.cfg. Your gonicorn.cfg does not need to contain the graceful_timeout = 30 setting as that is a gonicorn default, and that is not what you need to increase. What you need is [gunicorn] timeout = 900 (actually 900 seconds is probably way overkill. 90 seconds would probably be enough.) -- 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: Installing mailman 3

by Rafael Mora

Ok, I screwed the mailman install ..... I reinstalled mailman core. How do I do a Python2 virtualenv? Thanks El vie., 21 jul. 2017 a las 15:03, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:44 PM, Rafael Mora wrote: > > I did this: > > > > (env) [mailman@localhost mailman-suite_project]$ pip install Django > > Requirement already satisfied: Django in > > /var/lib/mailman/env/lib/python3.6/site-packages > > Requirement already satisfied: pytz in > > /var/lib/mailman/env/lib/python3.6/site-packages (from Django) > > > > > > Does Django is already installed?? with python3.6 ??? > > > Your 'env' vitrualenv is a Python 3 virtualenv. You need this for > Mailman core, but Django and mailman-suite are Python 2. They need to be > installed and run in a Python 2 virtualenv. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Thomas G

I tried all job, without result. (and they are correctly in the crontab) [image: image.png] If I try to find my list in the form, hyperkitty can find it: [image: image.png] Le mer. 3 oct. 2018 à 17:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/03/2018 02:30 AM, Thomas G wrote: > > > I have just a problem with statistics not available. > > > If cron is running all the periodic django jobs, this gets fixed > eventually. The one thing you may need to run manually is > > manage.py runjob thread_order_depth > > as that helps with some things and is a 'yearly' job. I think the > 'hourly' and 'daily' jobs fix most other issues. See > > manage.py runjob --list > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 9 months

[MM3-users] Re: member appears twice in list - how?

by Mark Sapiro

On 11/5/24 11:09, Jose Bernal via Mailman-users wrote: > I've got a list member showing up twice in a list (same email address). > Can't use the GUI to remove the member from this list (get a 503 error) > Screenshots attached, underlying database query reveals no duplicates. > Wondering how this is possible or where else I should be looking to resolve > this duplicate before I simply remove their entry from the members table > altogether. I'm not sure how this could have happened, I need more info for that, but to deal with this use `mailman shell` as in ``` $ 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 list(a)example.com mailing list >>> x = m.memberships('user(a)example.com') This should set x to a list of that users memberships You can then examine x[0] and x[1] to determine which to delete. e.g. >>> dir(x[0]) ['__abstract__', '__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__getstate__', '__gt__', '__hash__', '__implemented__', '__init__', '__init_subclass__', '__le__', '__lt__', '__mapper__', '__module__', '__ne__', '__new__', '__providedBy__', '__provides__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__table__', '__tablename__', '__weakref__', '_address', '_lookup', '_mailing_list', '_member_id', '_reset', '_sa_class_manager', '_sa_instance_state', '_sa_registry', '_user', 'acknowledge_posts', 'address', 'address_id', 'bounce_score', 'delivery_mode', 'delivery_status', 'display_name', 'id', 'last_bounce_received', 'last_warning_sent', 'list_id', 'mailing_list', 'member_id', 'metadata', 'moderation_action', 'preferences', 'preferences_id', 'preferred_language', 'receive_list_copy', 'receive_own_postings', 'registry', 'role', 'subscriber', 'subscription_mode', 'total_warnings_sent', 'unsubscribe', 'user', 'user_id'] This gives the list of attributes which can be examined with, e.g. >>> x[0].delivery_mode <DeliveryMode.regular: 1> You can then remove the one you don't want, e.g. >>> x[0].unsubscribe() >>> commit() ``` Just to be sure, you should ensure that x[0].member_id and x[1].member_id are different. These are the _member_id column in the member table in the database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 03:04, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > afaiu, this snippet allows me to purge outdated pending subscriptions. > > modifying it slightly, also allows me to just list the pending > subscriptions along with their tokens and print them out. That is correct. > is it still possible to just use these tokens to confirm the pending > subscription (even though it is long overdue)? Yes. > while investigating this a bit, i also noticed that it seems that with > mailman3 the only option to confirm a pending subscription is via email > ("leaving the subject intact") - at least that is the only option that > is listed in the confirmation mail. > > now i would like to massage this into what i think is a bit more > user-friendly. > first of all: most email confirmation systems allow me to either "reply > by email" or "click this link". > is there a way to do this for mailman3? that is: is there a (hidden) URL > that would accept the token in order to confirm a subscription? See https://gitlab.com/mailman/mailman/-/issues/901 You can add something like ``` Alternatively, you can confirm by going to the URL https://$domain/mailman3/lists/$list_id/confirm/?token=$token ``` to the list:user:action:subscribe template. Note that `$domain` may not be appropriate here because it is the email domain which may not be the web domain. > also: the confirmation mail says that the subject must be kept intact. > however, i noticed that the actual "From" address of the confirmation > mail already contains the token. The current template https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l… doesn't say that. > would it be enough if people just sent an email to this special > email-address (that contains the token), regardless of the subject? Yes. > i'm thinking of sending a rather personalized email that has a more > attractive subject than "confirm flkdsajfsalkjflsajfsoisjdl". The current mail has Subject: Your confirmation is needed to join the <fqdn_listname> mailing list > finally: what else is required to approve the confirmation? will the > sender's email-address be taken into account? (e.g. if they subscribed > "foo+mylist(a)example.com" but send the confirmation-reply from > "foo(a)example.com", will that still work? Yes. Only the token is required. -- 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: Reason for Shunting (SOLVED)

by Brian Carpenter

On 2/9/21 6:37 PM, Mark Sapiro wrote: > On 2/9/21 2:57 PM, Brian Carpenter wrote: >> On 2/9/21 5:25 PM, Mark Sapiro wrote: >>> On 2/9/21 2:03 PM, Brian Carpenter wrote: >>>> Is there a way to determine why a message keeps ending up in the shunt >>>> queue? >>>> >>> Look in mailman.log for the `SHUNTING` message and the traceback that >>> immediately preceeds it. >> >> Thanks Mark. The reason was: >> >> Feb 09 16:40:11 2021 (2614) Uncaught runner exception: Multiple rows >> were found for one_or_none() >> >> sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for >> one_or_none() >> >> Feb 09 16:40:11 2021 (2614) SHUNTING: >> 1612906811.2642436+cd8e97a66b6d0c2b73c2adde71a4914108c3e673 >> >> I have no idea what that means. > > See > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > and <https://gitlab.com/mailman/mailman/-/issues/657> > Thanks Mark, that fixed it. In my case the list had duplicate entries for all 4 archivers in the Mailman database. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples.

by David Partain

Hi Mark, Helpful, as always. Thank you. And do I feel silly. That was pretty darned obvious. In any case, it's fixed. Cheers, David ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 21, 2024 01:46 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples. On 3/20/24 13:23, David Partain via Mailman-users wrote: > raise ValueError("The ADMINS setting must be a list of 2-tuples.") > ValueError: The ADMINS setting must be a list of 2-tuples. > > Our ADMINS setting in /etc/mailman3/settings.py has > > ADMINS = ( > ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), > ) > > Can someone point me in a direction to correct this? 2-tuples, not triples. E.g. ADMINS = ( ('Mailman Suite Admin1', 'someone(a)our.domain'), ('Mailman Suite Admin2', 'someoneelse(a)our.domain'), ) -- 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: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

On 9/20/19 1:54 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> What other log entries relate to attempts to send to 172.19.199.2:8024? >> You may have to go back to when this first started to see them. > > Docker deleted it's log when restaring, as the container is deleted and removed, but the starte of the current log says: > ``` > Sep 18 13:28:57 postfix rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="20" x-info="http://www.rsyslog.com"] start > Sep 18 13:29:00 postfix postfix/postfix-script[94]: starting the Postfix mail system > Sep 18 13:29:00 postfix postfix/master[96]: daemon started -- version 2.10.1, configuration /etc/postfix > Sep 18 13:29:02 postfix postfix/smtpd[102]: connect from incoming.gateway.example.com[192.168.111.222] > Sep 18 13:29:04 postfix postfix/smtpd[102]: EFF017E9D65AE: client=incoming.gateway.example.com[192.168.111.222] > Sep 18 13:29:04 postfix postfix/cleanup[106]: EFF017E9D65AE: message-id=<2E40950170CA0A4A8D0F0C0CF1C0630601B8B9F412(a)P1KITMBX03WC02.unicph.domain> > Sep 18 13:29:04 postfix opendkim[19]: EFF017E9D65AE: incoming.gateway.example.com [192.168.111.222] not internal > Sep 18 13:29:04 postfix opendkim[19]: EFF017E9D65AE: not authenticated > Sep 18 13:29:04 postfix postfix/smtpd[102]: disconnect from incoming.gateway.example.com[192.168.111.222] > Sep 18 13:29:18 postfix postfix/qmgr[98]: 0E53F7E9D7D8D: from=<>, size=212010, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: C51DE7E9920B8: from=<>, size=212004, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: 2923A7E99B41F: from=<>, size=212040, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: D0A1E7E981E26: from=<quarantine(a)messaging.microsoft.com>, size=14542, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: 95FA77E9815A5: from=<>, size=211977, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: 208777E993635: from=<sender(a)example.com>, size=9826184, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: 757C27E9BD45C: from=<>, size=211997, nrcpt=1 (queue active) > Sep 18 13:29:18 postfix postfix/qmgr[98]: 738C87E9B94BE: from=<>, size=212141, nrcpt=1 (queue active) > [SLIP] > Sep 18 13:32:24 postfix postfix/anvil[103]: statistics: max cache size 1 at Sep 18 13:29:02 > Sep 18 13:43:48 postfix postfix/smtpd[992]: connect from gateway[172.19.199.1] > Sep 18 13:43:48 postfix postfix/smtpd[992]: 9E0D37E9D65AF: client=gateway[172.19.199.1] > Sep 18 13:43:48 postfix postfix/cleanup[996]: 9E0D37E9D65AF: message-id=<3e08121bcdf5b0ebeb779a26ab2fe6ef(a)mailing.einnews.com> > Sep 18 13:43:48 postfix opendkim[19]: 9E0D37E9D65AF: DKIM-Signature field added (s=default, d=sendergateway.example.com) > Sep 18 13:43:48 postfix postfix/smtpd[992]: disconnect from gateway[172.19.199.1] > Sep 18 13:43:48 postfix postfix/qmgr[98]: 9E0D37E9D65AF: from=<sender(a)example.com>, size=59393, nrcpt=1 (queue active) > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: mail for [172.19.199.2]:8024 is using up 7863 of 7863 active queue entries > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: you may need to reduce lmtp connect and helo timeouts > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: so that Postfix quickly skips unavailable hosts > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: you may need to increase the main.cf minimal_backoff_time and maximal_backoff_time > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: so that Postfix wastes less time on undeliverable mail > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: you may need to increase the master.cf lmtp process limit > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: please avoid flushing the whole queue when you have > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: lots of deferred mail, that is bad for performance > Sep 18 13:43:48 postfix postfix/qmgr[98]: warning: to turn off these warnings specify: qmgr_clog_warn_time = 0 So we see that Postfix is trying to send 9E0D37E9D65AF, but the subsequent log entries are only the "warning: mail for [172.19.199.2]:8024 is using up 7863 of 7863 active queue entries" ones. If this happens again, look in the log before restarting the container for connection refused, lost or timed out types of entries. You verified that Postfix could connect and receive the greeting from Mailman's LMTP runner, but that was after the queue was full. Maybe when it started and the queue filled up, this wasn't the case, but then if Postfix can connect, the queue should eventually drain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Migration failure (2.1.29 to 3.3.8 on Debian testing)

by Mark Sapiro

On 6/7/23 11:58, {16/7} wrote: > > I have both the mailman and mailman3-full packages installed on my machine and I'm following the migration guide located here: https://docs.mailman3.org/en/latest/migration.html Which is the source of at least one of your issues. The Debian packages are behind and are missing multiple bug fixes and enhancements. > Running the command { mailman import21 mylist(a)mysite.com /var/lib/mailman/lists/mylist/config.pck } completes once I create the list but states that it cannot convert the msg_footer and digest_footer mailing list attributes. (I might also point out that the { mailman create mylist(a)mysite.com } command isn't actually documented on that webpage.) import21 tries to make Mailman 3 compatible versions of your Mailman 2.1 msg_footer and digest_footer. It will put these in Mailman's var/templates/lists/<list-id>/<lc>/ directory as list:member:regular:footer.txt and list:member:digest:footer.txt respectively. You need to examine those files as they probably contain Mailman 2.1 style replacements that haven't been converted. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for the Mailman 3 replacements which are encoded as dollar strings, e.g. $listname gets replaced with the list's posting address. > I can't seem to find the manage.py script in my $PATH and after searching, I find it as part of the mailman3-web package. As you report in a followup, in the Debian package it's called mailman-web > Next, I changed the file's group back to list and decided to try running the manage.py script as the www-data user. This results in "/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured." and "System check identified some issues:" followed by a list of "Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'" warnings for a number of Django tables. Recent mailman installed following https://docs.mailman3.org/en/latest/install/virtualenv.html will include ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in Django's settings which will avoid that warning with Django>=3.2 > > My questions are: > > 1. How do I undo any damage (if any) my efforts may have caused? You probably didn't do any damage as the commands failed before doing anything. > 2. What's the correct way to run manage.py? I see from your follow up that you figured this out. -- 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: re-injecting emails that were not archived

by Mark Sapiro

On 6/25/23 11:47 AM, Ken Alker wrote: > > I noticed when I came onto the project last week that there were 140 > messages stuck in the "shunt" queue for the two lists hosted by this > server (I have no idea why and the old logs were not available and I > don't recall the results of "mailman qfile", assuming that had shed some > light on the reason why they were shunted). In any event, I unshunted > these messages and they flowed out to the subscriber's email addresses > successfully. What I was not expecting is that the system did not > inject any of these emails into the archive. AFAICT, the messages are > no longer anywhere on the system (but I could be mistaken). Here are my > questions: > > 1) Why would these emails not have been injected into the archive? The message may have been shunted from by the `out` runner, in which case unshunting would only cause them to be processed again by the 'out' runner. Archiving is a separate queue and process. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/archi… for an overview of the message handling process. The bottom line here is if a message was shunted by the 'out' runner only, it should have been archived at the original post time. Were these messages already archived? If not, depending on list settings there may be HyperKitty archiving iossues in which case they may by queued in Mailman's var/archives/hyperkitty/spool/. directory, but if they are, there would be errors in mailman.log from regular attempts to process them. Also they may be found in var/archives/prototype/<list>/new/ directory. > 2) Is there some way for me to re-inject these messages into the two > lists? The only place I (THINK I) have them is in my own personal IMAP > box since I'm a subscriber to the lists. You can inject them into the archive queue with `mailman inject`. See `mailman inject --help`. Before doing this, be sure it's necessary, i.e. they're not already archived, although HyperKitty won't accept a message whose Message-ID: is already in the archive. > 3) Can this be done without the emails being re-delivered to subscribers? As long as you inject them into the `archive` queue queue only, they won't be resent to the list members. -- 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: serving /static-content within /mailman3-web-Folder - change in recent mm release

by Stefan Bauer

thank you Mark, that did the trick :) Am Do., 29. Sept. 2022 um 18:33 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 9/29/22 06:50, Stefan Bauer wrote: > > Hi Folks, > > > > during our migration to latest MM we noticed, that nowadays, the static > > content is not served from within mailmans base directory, but from > outside. > > > > old MM3: > > > > domain.tld/mailman3/static/django-mailman3/js/main.js > > > > new MM3: > > > > domain.tld/static/django-mailman3/js/main.js > > > > Is there a chance to change it to the old behavior? > > > See the Django settings STATIC_ROOT and STATIC_URL. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

2 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, should I install the SASL authentication daemon saslauthd and start it? El mar., 25 jul. 2017 a las 15:40, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:19 PM, Rafael Mora wrote: > > What should I do to tell Postfix to use my domain?? for example send > emails > > using the email account mailing(a)labbrands.com > > > If what you're asking is how to configure Postfix to relay all outbound > mail via some other email server, that is a Postfix configuration question. > > If I thought I could give you a simple answer and that would be the end > of it, I'd try, but in your case every answer leads to another question, > so I suggest you start here to learn about configuring Postfix > <http://www.postfix.org/documentation.html>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Upgrade

by Darren Smith

And as usual, Mark to the rescue. Works like a charm...thank you! By the way, whose idea was it to use Rush songs for the release names? I whole-heartedly approve. -Darren On Mon, Apr 16, 2018 at 11:52 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/16/2018 10:26 AM, Darren Smith wrote: > > Nice...spoke too soon. > > > > Mailman info works, but when attempting to start mailman I'm now getting > > this: > ... > > RuntimeError: Click will abort further execution because Python 3 was > > configured to use ASCII as encoding for the environment. Consult > > http://click.pocoo.org/python3/for mitigation steps. > > > Are you starting Mailman from an init script. If so, add > > export LANG=en_US.UTF-8 > > to the script. See > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/ > install.html#running-mailman-3> > > > -- > 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, 3 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

The -C ...mailman.cfg fixed it. Thanks!!! On Sun, Nov 10, 2024 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/10/24 08:58, Stephen Daniel wrote: > > If I run > >>>> for mlist in getUtility(IListManager): > > ... print(mlist) > > ... > > <mailing list "testlist1(a)chapelwoodhoadev.org" at 0x7f83f593fba8> > > I get only one list. Permissions? Where are the other lists? > > > It should get all the lists. I don't know why it doesn't. Are you > running `mailman shell` with the correct configuration. Try running > ``` > mailman -C path/to/mailman.cfg shell > ``` > and see if that helps. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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 swd(a)pobox.com >

8 months, 3 weeks

[MM3-users] Re: Replies

by Mark Sapiro

On 3/17/22 20:47, Matthew R via Mailman-users wrote: > Hi everyone, we're going to be using a Mailman3 list for the purpose of > providing email support. So: > > * Anyone can post to the list > * Agents will reply to the poster to receive support, and the reply > must go back to the original poster (the client) and the mailing list for > other agents to see > * The poster's replies will be sent to the mailing list (so other > agents can see) as well as to the agent who initially replied to the initial > posting > > > > Is there any way to accomplish this? Right now, if the agent replies to the > client's email correctly but the client doesn't hit "Reply All" the email is > only sent to the agent that initially took the "case" and the other agents > aren't aware that there was a response. This is an intractable problem. Ideally, you would be able to configure the list to ensure all mail is sent with a Reply-To: that includes the original From: and the list address, but there is no list configuration that guarantees that. It wouldn't be difficult to patch mailman to do it for a particular list. You could almost get there if all the posts to the list included a Reply-To: In this case setting Reply goes to list to the list and First strip reply to to No, but you can't even hope that all incoming posts include a reply to. But, even if they don't, this may work. I.e., setting Reply goes to list to the list will set a Reply-To: with the list address in all delivered posts. The agent can do Reply-All: and hopefully, this goes to the From: and to the Reply-To. Then the client gets the reply with a Reply-To: to the list and hopefully, the client's reply goes back to the list. I say `hopefully` twice above because if there's a Reply-To; it is not a guarantee with all MUAs that Reply-All will include the From:, and at the client's end, even with a Reply-To: to the list, there's no guarantee the client's MUA will honor that. I say it's an intractable problem because what ever the list does, it relies on the user's MUA to do the right thing, and unfortunately, not all do. -- 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-web showing "An error occurred while processing your request."

by Mark Sapiro

On 2/8/23 08:34, C. Souza wrote: > I'm trying to manage 2 held messages in a specific list and I'm getting > this error below when I click on /held_messages. It never happened before. ... > ==> mailmanweb.log <== > ERROR 2023-02-08 16:01:30,149 1516 django.request Internal Server Error: > /mailman3/lists/mylist.domain.com/held_messages > Traceback (most recent call last): ... > File > "/opt/mailman/venv/lib64/python3.6/site-packages/django/utils/dateparse.py", > line 107, in parse_datetime > match = datetime_re.match(value) > TypeError: expected string or bytes-like object I'm not certain, but it looks like one of the held messages has a bad or possibly missing Date: header. Working around this is tricky. You can do the following in mailman shell. ``` $ 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 list.example.com mailing list >>> requests = IListRequests(m) >>> msgstor = getUtility(IMessageStore) >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if data['_request_type'] == 'held_message': ... print(f'request ID = {request.id}Message-ID = {key}\n ' ... f'message = {msgstor.get_message_by_id(key)}') ... This will print for each held message output like request ID = nnn Message-ID = <the message id> message = the message content You can then handle these messages with >>> from mailman.app.moderator import handle_message >>> handle_message(m, nnn, action) where nnn is the request ID and action is either Action.discard to discard the message or Action.accept to accept it. And finally >>> commit() ``` If you decide you want to edit the message content before accepting it, you could find the message in the file system. One of the headers in the displayed message is something like Message-ID-Hash: IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL the message is saved as a python pickle in the file system in Mailman's var/messages/ directory. This has subdirectories of the first two characters of the Message-ID-Hash value and those have subdirectories of the second two characters of the Message-ID-Hash value, so if the above were the actual Message-ID-Hash the pickle would be at var/messages/IW/L2/IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL. You would need to pickle the new message content and save that over the existing file. -- 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: Installing mailman 3

by Rafael Mora

Regarding this: # To be added to Django's settings.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password> What should I use for username and password? Should I keep the localhost on the host param? Thanks El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

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

by Mark Sapiro

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

4 years, 6 months

[MM3-users] Change to content filtering collapse alternatives - was: Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 2/1/25 03:08, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Not if we're collapsing alternatives. If we're collapsing a > > multipart/alternative part with text/plain and text/html > > alternatives to just the first alternative we don't keep the > > text/html part. > > I understand that's what we currently do. But I think that when the > MUA provides an empty plain text part and a non-null HTML part, that's > a mark of lazy MUA developers, not author intent. I think that it's > very likely that the author would prefer the reader get converted HTML > rather than a blank. I think this is a request to change the collapsing of alternatives to not collapse to the first alternative if it is empty and a subsequent alternative is not. I see your point in general if the poster composes an HTML message and the MUA makes a multipart/alternative message with an empty text/plain part, but are there actually MUAs that do that? All the ones I'm aware of either make an HTML only message or attempt to make a reasonable text/plain alternative. Even Yahoo mail which does a horrible job of making the text/plain part (i.e. links which are copy/pasted in the HTML are dropped from the plain text) does make one. That said, the effect on the OP's case, which may be more common, may be harmful depending on list and Mailman config. The original message from the OP (edited) is ``` Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" --000000000000da2dcc062cb38aa1 Content-Type: multipart/alternative; boundary="000000000000da2dcb062cb38aa0" --000000000000da2dcb062cb38aa0 Content-Type: text/plain; charset="UTF-8" --000000000000da2dcb062cb38aa0 Content-Type: text/html; charset="UTF-8" <div dir="auto"><img src="cid:ii_194a8d787554eb091f02" style="max-width: 100%; height: auto;"><br><br></div> --000000000000da2dcb062cb38aa0-- --000000000000da2dcc062cb38aa1 Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 Content-ID: <ii_194a8d787554eb091f02> X-Attachment-Id: ii_194a8d787554eb091f02 <base64 content> --000000000000da2dcc062cb38aa1-- ``` The HTML alternative only renders the jpg as an inline image. After current collapse alternatives this becomes ``` Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" --000000000000da2dcc062cb38aa1 Content-Type: text/plain; charset="UTF-8" --000000000000da2dcc062cb38aa1 Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 Content-ID: <ii_194a8d787554eb091f02> X-Attachment-Id: ii_194a8d787554eb091f02 <base64 content> --000000000000da2dcc062cb38aa1-- ``` which is an empty first part followed by the jpg part which is then further collapsed to just the jpg part ``` Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 <base64 content> ``` I.e. a single part message with content type image/jpeg. If instead we collapsed the alternatives to the HTML part the message becomes ``` Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" --000000000000da2dcc062cb38aa1 Content-Type: text/html; charset="UTF-8" <div dir="auto"><img src="cid:ii_194a8d787554eb091f02" style="max-width: 100%; height: auto;"><br><br></div> --000000000000da2dcc062cb38aa1 Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 Content-ID: <ii_194a8d787554eb091f02> X-Attachment-Id: ii_194a8d787554eb091f02 <base64 content> --000000000000da2dcc062cb38aa1-- ``` and what that html part looks like after conversion to plain text depends on the configured command. With the default lynx the content is unchanged, put the type is text/plain which will render as the text with the image attached. With links the plain text content is empty which results again in a message with empty first part and image/jpeg second part. In short, for this message at least, I see no real advantage to dropping the empty text/plain alternative vs. dropping the text/html alternative. Possibly there is a difference if we don't convert HTML to plain text in that some MUAs might render the jpeg inline as opposed to an attachment, but if we do convert with lynx the recipient sees a message with a body which is HTML tags rendered as text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Mailman3 not delivering list mail

by Mark Sapiro

On 10/1/20 11:18 AM, gordon(a)dickens.com wrote: > Hi Mark, > > I have errors like these in the mailman3 logs but they occurred earlier (that is prior to my attempting to post messages to the new mailman3 mailing list and which are not echoed to list members): > > > Oct 01 11:08:22 2020 (7895) Skipping and preserving unparseable message: 1601564901.8696995+c2b86623e2dcc8e9800b10ca2bcf8b82e8d8d662 > Oct 01 11:08:23 2020 (7895) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1601564902.28165 > 63+16bd684dfb18c6175f3e7b0b11312cb203dc9c89.pck' > Oct 01 11:08:23 2020 (7895) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 158, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1601564902.2816563+16bd684dfb18c6175f3e7b0b11312cb203dc9c89.pck' These relate to the messages in the `bad` queue. It seems there is/was andn issue with ownership and/or permissions on some directory or directories is the path `/var/lib/mailman3/queue/virgin`. Is mailman3, queue and virgin user and group `list` and searchable, readable and writable by `list`. Are all the runners running as user `list` ps -fwwA|grep runner > The above errors occurred prior to the time that I attempted to send to the mailman3 list. However, here is what I see in the logs immediately after I sent a message to the list and which was not then echoed to list members: > > > Oct 01 11:51:03 2020 (7888) ACCEPT: <f92eeaad-245c-124b-dd09-b31a6b3c5686(a)dickens.com> > Oct 01 11:51:07 2020 (7885) HyperKitty archived message <f92eeaad-245c-124b-dd09-b31a6b3c5686(a)dickens.com> to https://georgiajets.org > /mailman3/hyperkitty/list/members(a)georgiajets.org/message/NUOU6UQ6DSHSK2WKNVZFIN5AELK5EYBU/ > Oct 01 11:51:07 2020 (7891) Cannot connect to SMTP server localhost on port 25 This is delivery of the outgoing message which looks like it was successfully archived. These messages come from `/var/lib/mailman3/queue/out` and after the failure are put in `/var/lib/mailman3/queue/retry` and periodically are moved back to the `out` queue and tried again. > Please note the message about the SMTP server not being able to connect to local host on port 25. Please let me know what you think is wrong and how to fix it. Normally it means exactly what is says. Is your MTA (Postfix or ??) running? Can you `telnet localhost 25` successfully? Note that if the message actually says `local host` and not `localhost`, the setting for smtp_host in the [mta] section of mailman.cfg 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

4 years, 10 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

I am extremely *sorry* Mark. As I was put under pressure with a timeline, I have reminded you over anxiety. I should not have disturbed such a good helper. Sorry once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 9:24 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 6:27 PM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Any suggestions over my earlier email? I am waiting for your > > reply. > > > Be patient. I am a volunteer and I have a life outside of Mailman. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 9 months

[MM3-users] Upgrade

by Mark Sapiro

On 5/22/19 2:07 PM, David Krantz wrote: > Hi all, > > I am running a relatively old version of mailman 3, namely 3.2.0a1 > from late september 2017. This is installed using the old > mailman-bundler method. I use postfix and postgres. > > I really have two questions: > > First: What is the normal way to upgrade such a setup? I guess that I > just can get the updated versions of all packages through git, set up > new venv's to simplify a rollback, back up the database and then just > restarting with the new version hoping for the best. That's more or less correct. I did this on mailman3.org a little over a year ago. I suggest you see <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which describes much of what I did. you can also see <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=re…> for what I had with Mailman Bundler. The biggest hurdle is now Postorius and Hyperkitty are Python3 so you need Python3 versions of various dependencies. Here's roughly what I did. git clone everything from GitLab. As a developer, I've always been running off the heads. There are occasional glitches, but I can work around these. You can also install from PYPI if you want more stability. Everything is mailman, mailman-hyperkitty, mailmanclient, django-mailman3, hyperkitty and postorius. But, I'm getting ahead. Create a new python3.5+ virtualenv. Python3.5 is the minimum, but 3.6 or 3.7 would be even better. Activate that virtualenv and if you are using the branches from GitLab, in each branch directory, do python setup.py clean --all python setup.py install or just pip install everything. You also need to do the things indicated in the Preliminaries and Installation sections of <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. Also see the Migration section for scripts I use to update from GitLab and build 'everything' and the rest of the document too. Then once you have things set up, it's pretty much a matter of just updating the various scripts you use to run things to point to the new command files in, in my case, /opt/mailman/mm/bin/. One caveat to note is if you are using the Whoosh backend. The Python2 version is incompatible with Python3 so you need to remove the fulltext_index directory and run the django management rebuild_index command to recreate it. You should be able to just run rebuild_index or maybe clear_index followed by update_index without removing the old index first, but there are reports that this doesn't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Yes, and I made all the tests as discribed here: https://workaround.org/ispmail/buster/relaying-through-postfix/ including the swaks test mentioned before output of sudo netstat -lntup | grep ":25" tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20660/master tcp6 0 0 :::25 :::* LISTEN 20660/master output of sudo lsof -i :25 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 20660 root 13u IPv4 1474228 0t0 TCP *:smtp (LISTEN) master 20660 root 14u IPv6 1474229 0t0 TCP *:smtp (LISTEN) Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 7. April 2020 21:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 3:22 AM, Wolfgang Bock via Mailman-users wrote: > Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost > on port 25 > > I have no idea what to do for solving my problems. Can you successfully telnet localhost 25 from a shell on the server? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 3 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > How to find out the versions of the each and every component > of the mailman 3 like mailman core, mailmancilent, postorius, > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > after installation? cd to the directory in which you cloned the gitlab project for the component and do `git log` > If I am running an old mailmanclient or older version of any > other mailman component, please suggest how to upgrade either one or > multiple components based on the requirement. Is there any link that > would help me to upgrade ? > > I have used the > link https://docs.mailman3.org/en/latest/devsetup.html to install the > mailman 3 components. I expected that the procedure followed in this > link would install the latest versions of the mailman 3 components. > Please correct me if I am wrong. Is there any latest version > compatibility table ? If you installed each of mailman, mailmanclient, django-mailman3, postorius and hyperkitty according to instructions like $ cd ~/mailman $ git clone https://gitlab.com/mailman/mailmanclient.git Then set up mailmanclient: $ cd mailmanclient $ python setup.py develop $ cd .. from that document, you should have the latest version. If that is the case, `git log` in the mailmanclient directory should begin like commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, origin/master, origin/HEAD) Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master' Use GHCR for the CI image See merge request mailman/mailmanclient!130 commit 8670751caff689733751ef323ef521c4a3fa1237 Author: Abhilash Raj <raj.abhilash1(a)gmail.com> Date: Wed Oct 14 17:36:58 2020 -0700 Use GHCR for the CI image commit ff39dd8f03a820f442f2251553c444370df3b914 Merge: 80ebed4 76d44e1 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Fri Aug 7 19:35:05 2020 +0000 Merge branch 'invite' into 'master' Add support for inviting an email address to join a list. See merge request mailman/mailmanclient!129 or if you did this before Oct 15, maybe it starts with commit ff39dd8f03a820f442f2251553c444370df3b914 The particular commit you need for your issue is commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 Merge: c8dcb1e 28d1c3a Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Sat May 16 08:02:21 2020 +0000 Merge branch 'held-count' into 'master' Add a new get_held_count() API to get a count of held messages. See merge request mailman/mailmanclient!122 Note that unless you intend to do actual development of Mailman 3, you should be following <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather than <https://docs.mailman3.org/en/latest/devsetup.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

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

by Mark Sapiro

On 6/16/23 19:20, Mike Wertheim wrote: > I'm running an email list on mailman3. > > My users are getting inundated by messages saying that their subscriptions > have been disabled due to their bounce score exceeding the mailing list's > bounce_score_threshold. > > But there is nothing wrong with these users' email accounts. They are all > perfectly fine. Apparently the issue is somehow related to spam. Is spam being posted to your list? If so, you should ensure that Default action to take when a member posts to the list is set to Hold for moderation so that spammers can't subscribe to your list and post without the post being reviewed by a moderator. Then if the post is on topic, the moderator can set the user's moderation action to Default processing when accepting the post so subsequent posts won't be held. Also set `verp_probes: yes` in the [mta] section of mailman.cfg. Then when a user's score reaches threshhold, a probe message is sent and delivery is only disabled if the probe bounces which it probably won't if the issue is spam bounces. > Whenever I (as admin) get these emails, I just unsubscribe the user and > then re-subscribe them. But also, the user gets confused and emails me > about it, which unnecessarily takes up their time and mine. That should be unnecessary. Just click on the member in the members list and set the member's Delivery status to Enabled. However, this may not work because of https://gitlab.com/mailman/mailman/-/issues/1061 which is not fixed until the next release, but enabling verp_probes will avoid that issue. > The relevant list settings are currently... > bounce score threshold: 5 > bounce info stale after: 7d > bounce disabled warning interval: 7d > bounce disable warnings: 5 > > What's the best way to fix this? I'm considering reducing "bounce > info stale after" to "2d" and/or increasing "bounce disabled warning > interval" to "90d". Increasing "bounce disabled warning interval" or "bounce disable warnings" won't help because the user's delivery will still be disabled. It will just take longer for them to eventually be removed. Reducing "bounce info stale after" to "2d" might help as long as the list gets good posts more frequently than that, but the best way to deal with this is to enable verp_probes and then only consider other things if that doesn't 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: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 7:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 7:28 AM, Odhiambo Washington wrote: > > On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > >> core than the one reading that mailman.cfg and the one Postorius is > >> talking to. > >> > > > > How can I track the one it's talking to? > > > Try `/opt/mailman/mm/venv/bin/mailman info` > So this command's output pointed to /opt/mailman/var/etc/mailman.cfg instead of my file that is in /opt/mailman/mm/mailman.cfg According to the HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> I am following, mailman.cfg should be in /opt/mailman/mm/. Now I am wondering what I am missing again. Did something change? Should I place all my config files in /opt/mailman/var/etc/ instead of /opt/mailman/mm/ ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

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

by Stefan Bauer

Unfurtunately, this completely removes the reply-to: header and sets the list-address as a new and only reply-to. This way, a reply does not address the origin sender anymore :/ Am Mo., 22. Nov. 2021 um 19:17 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/22/21 6:27 AM, Stefan Bauer wrote: > > > > john receives following mail: > > > > from: iu-int@mydomain > > reply-to: mike@mydomain, iu-all@mydomain > > > > If john now hits reply in mailclient, mail goes to ALL instead of just > the > > from-address, as mailman extended the reply-to header. > > > > How can this be changed? > > > Set Settings -> Alter Messages -> First strip reply to to Yes on the > iu-int list. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 8 months

[MM3-users] Re: The doubled entries issue

by Mark Sapiro

On 11/13/23 10:06, Lars Bjørndal wrote: > > On Sun, Nov 12, 2023 at 08:07:59AM -0800, Mark Sapiro wrote: >> for info. However, that script cannot be run as is by `mailman shell --run`. >> It can be run by invoking `mailman shell` interactively and copying and >> pasting it, > > Yes, that worked, e.g. no error messages. >> or if your Mailman is installed in a venv it can be run with the >> venv active by `python ./fix-doubled-entries.py`. > > I have mailman installed in venv, but got the following when trying that: > > "python fix-doubled-entries.py" need the IListManager interface but can't find it. I see that that's actually expected. In order to run that script with the Python in the venv, you'd need to add ``` from mailman.core import initialize initialize.initialize() ``` to the script to properly set up the Zope components. >> However, that script will not fix your issue because you don't have multiple >> mhonarc entries for a list. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and as it says, Tell us more about the "duplicate entries" error, and if >> possible copy it exactly from where you found it originally, including any >> traceback. > > Here's the entries in the mailman.log file: > ... > Nov 11 09:18:47 2023 (1715) Uncaught runner exception: Multiple rows were found when one or none was required > Nov 11 09:18:47 2023 (1715) Traceback (most recent call last): > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/runners/outgoing.py", line 111, in _dispose > self._func(mlist, msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/mta/deliver.py", line 89, in deliver > refused = agent.deliver(mlist, msg, msgdata) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/mta/base.py", line 167, in deliver > callback(mlist, message_copy, msgdata_copy) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/mta/decorating.py", line 32, in decorate > decorator.process(mlist, msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/handlers/decorate.py", line 250, in process > process(mlist, msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/handlers/decorate.py", line 73, in process > for archiver in IListArchiverSet(mlist).archivers: > ^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/zope/component/_api.py", line 167, in adapter_hook > return sitemanager.queryAdapter(object, interface, name, default) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/zope/interface/registry.py", line 351, in queryAdapter > return self.adapters.queryAdapter(object, interface, name, default) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/database/transaction.py", line 106, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/model/mailinglist.py", line 653, in __init__ > ListArchiver.name == archiver_name).one_or_none() > ^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2769, in one_or_none > return self._iter().one_or_none() # type: ignore > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/engine/result.py", line 1813, in one_or_none > return self._only_one_row( > ^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/engine/result.py", line 816, in _only_one_row > raise exc.MultipleResultsFound( > sqlalchemy.exc.MultipleResultsFound: Multiple rows were found when one or none was required > Nov 11 09:18:47 2023 (1715) SHUNTING: 1699690727.810848+3b6f3baba5576f3d87d3ff392aba2715d4dda793 That does look like https://gitlab.com/mailman/mailman/-/issues/657, but your database query showed no duplicate mhonarc entries for a list. Possibly, it was a different archiver, or more likely considering > I don't know what fixed the problem, but when I did `mailman unshunt` the message went through. it was already fixed when you queried the database. > Will mailman notify when there's shunted messages? No. I run a daily cron that does `ls -lAR /opt/mailman/mm/var/queue/` which lists the shunt queue and the others. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: External MTA incoming mail: configuration

by Mark Sapiro

I see this reply is now moot as you have now configured list mail to go directly to the Mailman server, but ... On 8/5/24 03:44, Roland Giesler via Mailman-users wrote: > > In the logs of the MTA I see this however: warning: do not list domain > fast.za.net in BOTH virtual_mailbox_domains and relay_domains > > Mailman creates these entries, but postfix doesn't like it. I don't see > any mail delivered to the mailman yet. Is this the problem? Probably not. It is telling you that mail to the fast.za.net domain cannot both be delivered to local mailboxes (virtual_mailbox_domains) and relayed to foreign hosts (relay_domains) > In the MTA postfix main.cf: > > relay_domains = hash:/etc/mailman3/data/postfix_domains > > cat /etc/mailman3/data/postfix_domains > ... > > and also > > local_recipient_maps=$virtual_mailbox_maps, > hash:/etc/mailman3/data/postfix_lmtp > > cat /etc/mailman3/data/postfix_lmtp > ... How about transport_maps = hash:/etc/mailman3/data/postfix_lmtp > > Then there's: > virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf > > cat /etc/postfix/virtual-mailbox-domains.cf > dbpath=/home/user-data/mail/users.sqlite > query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 FROM > aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM auto_aliases WHERE > source LIKE '%%@%s' > > When I run that query in sqlite3, it returns no records, so I'm not sure > how this is supposed to work. %s to me means that first argument, so is > this used in python and then %s is the argument sent to this query? See https://www.postfix.org/sqlite_table.5.html `%%` is replaced with `%` which is a SQL wildcard matching anything and `%s` is replaced by the key postfix is looking for, i.e. the domain that it is asking about. So, that query becomes SELECT 1 FROM users WHERE email LIKE '%(a)fast.za.net' UNION SELECT 1 FROM aliases WHERE source LIKE '%(a)fast.za.net' UNION SELECT 1 FROM auto_aliases WHERE source LIKE '%(a)fast.za.net' I.e, it returns true if any user or alias or auto_alias has an address ending in '@fast.za.net' and if that's true the mail to any '@fast.za.net' address including list mail will be stored locally. If you really have local users on box2.gtahardware.co.za with addresses '@fast.za.net' and you want to relay list mail to lists '@fast.za.net', you need to see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: list footer questions

by Mark Sapiro

On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://wiki.list.org/x/4030707> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- 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: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/26/20 3:15 AM, Odhiambo Washington wrote: > There is still some confusion on my part about the directives in the file > so allow me to seek some clarifications. > > The following are the contents of a file I have created and placed in my > Apache Includes/ directory. > I was hoping that with it, I can now access http://lists.my.server/mm3 and > get the UI. > > <CUT> > > # Global section > WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 user=mailman3 \ > group=mailman3 > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > \ > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > WSGIRestrictSignal Off > > <VirtualHost *:80> > ServerName lists.my.server > ServerAdmin odhiambo(a)gmail.com > > # (I'm not sure that WSGIRestrictSignal Off is required, but it was in the > # provided example so I kept it. I also made changes to WSGIDaemonProcess > # based on my own mod_wsgi experience elsewhere.) > > ErrorLog /var/log/myserver-error.log > LogLevel debug > > # This goes in the VirtualHost block for the domain. > > # Mailman 3 stuff > Alias /static "/var/spool/mailman-web/static" *<----- Where is this > directory supposed to be and what/who creates it and with what permissions?* It is created/updated by the mailman-post-update script based on CONFDIR and STATIC_DIR. > <Directory "/var/spool/mailman-web/static"> With the settings in the sample, the above should be <Directory "/opt/mailman/mm/static"> and the alias Alias /static "/opt/mailman/mm/static" Clearly <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> doesn't match some other files. I'll review abd update that. > Require all granted > </Directory> > WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > <Directory "/opt/mailman/mm/"> > <Files wsgi.py> > Order deny,allow > Allow from all > Require all granted > </Files> > WSGIProcessGroup mailman-web > </Directory> > </VirtualHost> > > </CUT-HERE> > > I end up with an "Internal server error" and from the error log I see: > ... > [Sun Jul 26 12:04:44.093265 2020] [wsgi:error] [pid 6444] [remote > 197.232.81.246:53383] ModuleNotFoundError: No module named 'settings' Django is trying to import your settings.py file and can't find it. Is it at /opt/mailman/mm/settings.py and also local settings at /opt/mailman/mm/settings_local.py? -- 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: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Though you are for sure that the current versions as I am claiming the above one is perfectly without any issue, please also suggest what would be the best previous version which definitely does not have that issue because I even checked out the immediate previous version of mailmanclient but still I am getting the same error. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 11:20 PM, Shashikanth Komandoor wrote: > > Can I go back to any previous version which is felt as working fine ? > > Sure. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 9 months

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

Hi, Marik! I realized that I had two variables in settings.py where the domains is listed, and one of them had a preceding https. I've now followed the documentation for configuring Apache here: https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. I want both domains to start mailman3 when contacting example1.com/mailman3 and example2.com/mailman3. I have the sam configuration in both virtualhost section in Apache. For example1.com/mailman3, it works perfectly. For example2.com/mailman3 however, the browser (elinks), reports Host not found: example2.commailman3 e.g. without a slash after the domain name. What could cause this to happen? Thanks Lars On Fri, Feb 10, 2023 at 11:59:02AM -0800, Mark Sapiro wrote: > On 2/10/23 01:43, Lars Bjørndal wrote: > > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > > > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > > > > > If I connect to example2.com, the title is example2.com, without the > > > > preceding List index. And the body says Page not found. > > > > > > > > > What's in the browser's address bar for that page? > > > > It's https://example2.com/mailman3/lists/ > > And when you get the Page not found, is it a browser 404 error or a > Postorius error page? > > > > > > > What's in Postorius domains view? > > > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > > > Why are you going to http://localhost:8000/? You should be able to see the > domain's view at https://example1.com/mailman3/domains/ or > https://example1.com/mailman3/domains/ or by just clicking Domains in > Postorius top nav bar. > > > > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. > > > Again you should be able to go to https://example1.com/admin or > https://example2.com/admin. If these don't work, you need to add directives > in your web server to proxy them to http://localhost:8000/admin > > -- > 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 lars(a)lamasti.net

2 years, 5 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 06/17/2016 12:16 PM, Bill wrote: > Hi, > > I'm looking for some information on Mailman3 administration. I've found > that it's not yet packaged by any of the common Linux distros - Debian, > Ubuntu, Mint, RedHat, Centos, Fedora, Suse, Arch etc so I have some > concerns about the amount of upkeep that running Mailman3 will entail. > > I know that Mailman2 is available as a package on the above distros, but > we would really like to take advantage of the kludge-free, virtual > domains feature on Mailman3. > > I've been asked by a local non-profit provider to assist them in moving > their 200+ mailing lists from an outdated Sympa list server to > Debian8/Postfix/Mailman. One of their chief concerns is the amount of > extra administration, over and above normal list administration, that > Mailman3 will require in the form of manual updates and maintenance. > > We are in the evaluation and design stage right now, but could use any > pertinent advice about supportive distros, available packages, the > amount of extra administration involved or perhaps, in a worst case > scenario, alternate list managers supporting a virtual domains feature > similar to Mailman3. > > Thanks for your help, > > Bill McGrath > President, Vancouver Linux Users Group > https://vanlug.bc.ca I've copied this post and set Reply-To: to the Mailman 3 users list <mailman-users(a)mailman3.org>. Please join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/> before replying there. That said, we are working on packaging for a more turn-key installation, but we aren't there yet. I've installed a couple of instances including the one at lists.mailman3.org, and it does require extra work. Some of the work in my case is because I want to run all the Mailman pieces from the heads of their branches rather than what's in PyPI, but even without that, installation is significantly more work than installing a distro's package. I will be writing up my experiences, but that's not done yet either. I will say that once you have Mailman 3 installed and running, updating (which I do frequently, but which doesn't need to be done unless you want specific updates/fixes) is pretty easy. As far as alternatives are concerned There is an up to date Mailman 2.1 branch with better virtual domain support at <https://code.launchpad.net/~msapiro/mailman/vhost>, but I think in the long run, you'd be better off with Mailman 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, 1 month

[MM3-users] Re: Mailman 3 on Fedora - Core only ?

by Mark Sapiro

On 6/13/20 2:17 AM, Lars Bjørndal wrote: > I'm about to set up a new list, and want to try out Mailman3. > > The only component available in Fedora, is the Mailman core package. I find that strange as <https://lists.fedoraproject.org/> is Mailman 3 and the core developer who did most of the HyperKitty development works or did work for Fedora. > With the /usr/libexec/mailman3/mailman command, I was able to create a > list, and add a member throug the sub commands create and members. > > How can I read out the list configuration from here, and change > settings? Do I then need to install/use other components, or is there > other possibilities, e.g. using the shell command? You can do anything through `mailman shell`, but it can be cumbersome. You can also do most things via the REST API <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>, but that too is cumbersome if doing it, e.g., with `curl`. > If I get a message that needs moderation, can I do the decision from cli, > or how do I do that? You should be able to do it via a reply to LIST-confirm+<token>@example.com, but this currently doesn't work. See <https://gitlab.com/mailman/mailman/-/issues/169>. To do it in `mailman shell` is something like: $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.app.moderator import handle_message >>> from mailman.interfaces.action import Action >>> action = Action.discard # to discard >>> action = Action.reject # to reject >>> action = Action.accept # to accept immediately >>> action = Action.defer # to continue with subsequent tests >>> rq = IListRequests(m) >>> rq.held_requests <generator object ListRequests.held_requests at 0x7f5431dda048> >>> list(rq.held_requests) [] >>> # when you have requests this is a list of (id, type) tuples >>> # type is 1 for message, 2 for subscription and 3 for unsubscription >>> id = 'integer request id from above' >>> handle_message(m, id, action, comment='reason if rejecting') This is obviously not practical, but you could make a script to accept the token that you know and an action and maybe a comment to do the actual handling. -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/23/21 12:43 AM, Marco Marinello wrote: > Dear Mark, > > I upgraded the pypi packages as you suggested but the problem remains the same. > Tried also installing from git heads but always get > > ==> /opt/hyperkitty_django/hyperkitty.log <== > ERROR 2021-10-23 09:42:42,523 30765 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls > WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls > > ==> /var/log/mailman/mailman.log <== > Oct 23 07:42:42 2021 (30888) HyperKitty failure on http://127.0.0.1:8080/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key must be > sent over the Authorization HTTP header. > </p></body></html> (401) Those messages look correct for HyperKitty 1.3.5, if mailman-hyperkitty is not sending the key as expected. The particular condition causing those messages is there is no "Authorization" header in the headers of the request from mailman-hyperkitty and there is also no "key" parameter in the request as there would have been with mailman-hyperkitty 1.1.0 This would seem to say that both HyperKitty 1.3.5 and mailman-hyperkitty 1.2.0 are doing the right thing, but somehow the request headers are not getting through in the http request from mailman-hyperkitty to HyperKitty. What is your setting for base_url in mailman-hyperkitty.cfg? Is there some redirect or other situation going on in serving the request to HyperKitty that could cause headers to get lost? > For information, how does your release cycle work? I prefer installing from a source rather than pypi. Is the master normally stable? When a packages lands on pypi? We are a small, all volunteer project and we don't have a fixed release schedule. We make releases when we feel enough change has been accumulated to warrant on or when there is a serious issue to fix. The heads of the gitlab branches are generally usable. There was actually a situation briefly where the mailman-hyperkitty changes for this issue were merged before the HyperKitty changes. See https://gitlab.com/mailman/hyperkitty/-/merge_requests/354#note_693162778 but situations like this are rare. The servers at lists.mailman3.org and mail.python.org run the heads of the gitlab branches (I update them regularly) so you can generally be confident that they work. > I'll stick on 1.3.4 / 1.1.0 for the moment. There are several changes in HyperKitty 1.3.5. See https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

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

by Mark Sapiro

On 6/20/20 5:41 PM, Ruth Ivimey-Cook wrote: > >>> My reason for thinking, in my original post, that the wrong host >>> address is being used is that the ConnectionError above contains >>> 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only >>> present as >>> the listen address on the core web service and does not appear in >>> the >>> config for postorius. >> The ConnectionError above comes from requests.request (docs at >> <https://requests.readthedocs.io/en/master/>). Client only provides a >> URL in the call to request and the URL is the baseurl + the path and the >> baseurl is MAILMAN_REST_API_URL which you have as >> http://greyarea-post:8870. Entries above have >> http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? >> >> I suspect a DNS lookup issue. How does greyarea-web1 resolve >> greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS >> rather than relying on /etc/resolv.conf and/or /etc/hosts. > > No, ignore that... I edited the FQDN down to the hostname in the email > for simplicity, but even if it was in the log the hostname does map > properly (i.e. host greyarea-post and host greyarea.cam.ivimey.org > return the same thing). Is the above a typo. You are saying greyarea.cam.ivimey.org. Did you mean that or greyarea-post.cam.ivimey.org as in the http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 log messages? > In referring to the ConnectionError from: > > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > > if you reconstruct the url passed in it was presumably: > > "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk" I don't think so. I think it was http://greyarea-post:8870/3.1/domains/ch-bc.org.uk and requests.request couldn't resolve that to the correct IP. If you look at Mailman client <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/re…> you'll see it makes the URL from the baseurl passed to the instantiation of the Connection class which occurs at <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/cl…> which in turn is called from Postorius at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…> which makes the baseurl argument from '%s/3.1' % settings.MAILMAN_REST_API_URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: PermissionError: [Errno 1] Operation not permitted

by Mark Sapiro

On 6/21/21 2:28 PM, Sarah H wrote: > The system we are running mailman 3 on crashed, it filled the drive, and when it was restarted and the issue cleared I found that mailman3 will not start, it returns the following: > > Jun 21 14:12:29 mailman[513274]: Traceback (most recent call last): > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/bin/mailman", line 11, in <module> > Jun 21 14:12:29 mailman[513274]: load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 829, in __call__ > Jun 21 14:12:29 mailman[513274]: return self.main(*args, **kwargs) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 782, in main > Jun 21 14:12:29 mailman[513274]: rv = self.invoke(ctx) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke > Jun 21 14:12:29 mailman[513274]: return super().invoke(ctx) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke > Jun 21 14:12:29 mailman[513274]: return _process_result(sub_ctx.command.invoke(sub_ctx)) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1066, in invoke > Jun 21 14:12:29 mailman[513274]: return ctx.invoke(self.callback, **ctx.params) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 610, in invoke > Jun 21 14:12:29 mailman[513274]: return callback(*args, **kwargs) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/decorators.py", line 21, in new_func > Jun 21 14:12:29 mailman[513274]: return f(get_current_context(), *args, **kwargs) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/cli_control.py", line 91, in start > Jun 21 14:12:29 mailman[513274]: status, lock = master_state() > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/master.py", line 104, in master_state > Jun 21 14:12:29 mailman[513274]: os.kill(pid, 0) > Jun 21 14:12:29 mailman[513274]: PermissionError: [Errno 1] Operation not permitted > Jun 21 14:12:29 systemd[1]: mailman3.service: Control process exited, code=exited status=1 > Jun 21 14:12:29 systemd[1]: mailman3.service: Failed with result 'exit-code'. > > this is via starting as root with systemctl start mailman3, or as the user mailman using /opt/mailman/venv/bin/mailman start This is probably due to a stale lock. See https://gitlab.com/mailman/mailman/-/issues/913. Assuming mailman is not running, you need to remove Mailman's var/locks/* Similar issues can occur if `bin/mailman start` is run as the mailman user but has previously been run as root. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/3/22 4:01 PM, Michael Heseltine wrote: > Hi Mark, > I tried out "pip install mistune==2.0.0rc1" (as I got hyperkitty via pip) which worked and let me move forward a little further once more, but still I get an error from "mailman-post-update": > >> # /opt/mailman/mm/bin/mailman-post-update >> + '[' False == False ']' >> + mkdir -p /opt/mailman/mm/static >> + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 >> + /opt/mailman/mm/bin/django-admin compress >> Compressing... done >> Compressed 2 block(s) from 104 template(s) for 1 context(s). >> + /opt/mailman/mm/bin/django-admin compilemessages >> Traceback (most recent call last): >> File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> >> sys.exit(execute_from_command_line()) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line >> utility.execute() >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 413, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 354, in run_from_argv >> self.execute(*args, **cmd_options) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 398, in execute >> output = self.handle(*args, **options) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/commands/compilemessages.py", line 113, in handle >> self.compile_messages(locations) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/commands/compilemessages.py", line 130, in compile_messages >> self.stdout.write( >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 155, in write >> self._out.write(style_func(msg)) >> UnicodeEncodeError: 'latin-1' codec can't encode character '\u201c' in position 5: ordinal not in range(256) This looks like an issue with some message catalog which is declared as character set `latin-1` but contains a unicode left_double_quote character. Unfortunately, `django-admin compilemessages` compiles, at least in my test installation, 1583 message catalogs from 19 different projects, so finding the problem file is difficult and I don't know how to narrow it down. However, this is the next to last step in mailman-post-update and isn't important if your installation is English language only and the last step is optional and runs /opt/mailman/mm/bin/django-admin update_index to rebuild the search index for HyperKitty and you can just run that one step if you want. At this point, you probably have no archives so this should take almost no 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, 6 months

[MM3-users] Re: Mailman3 on python3.13 debian testing package

by Mark Sapiro

On 2/12/25 23:12, Thomas Krichel wrote: > > Feb 13 06:49:56 2025 (857955) Uncaught runner exception: 'pathlib._local.PosixPath' object does > not support the context manager protocol > Feb 13 06:49:56 2025 (857955) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 111, in _dispose > self._func(mlist, msg, msgdata) > ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 89, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 167, in deliver > callback(mlist, message_copy, msgdata_copy) > ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate > decorator.process(mlist, msg, msgdata) > ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 250, in process > process(mlist, msg, msgdata) > ~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 88, in process > header = decorate('list:member:regular:header', mlist, d) > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 212, in decorate > template = getUtility(ITemplateLoader).get(name, mlist, **extradict) > File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 211, in get > path, fp = find(default_uri, mlist, code) > ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/utilities/i18n.py", line 157, in find > for search_path in raw_search_order: > ^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/utilities/i18n.py", line 117, in search > templates_dir = str(resources.enter_context( > ~~~~~~~~~~~~~~~~~~~~~~~^ > files('mailman').joinpath('templates'))) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.13/contextlib.py", line 528, in enter_context > raise TypeError(f"'{cls.__module__}.{cls.__qualname__}' object does " > f"not support the context manager protocol") from None > TypeError: 'pathlib._local.PosixPath' object does not support the context manager protocol > Feb 13 06:49:56 2025 (857955) SHUNTING: 1739429396.7636604+dba2fc372ce4c206e3bb753c1162bc3b768b7528 > Feb 13 06:49:56 2025 (857955) SHUNTING: 1739429396.7636604+dba2fc372ce4c206e3bb753c1162bc3b768b7528 > > Then there are repeated messages that hyperkitty can't archive the > message. Lots of them. > > No email reaches the list. I did not notice, but now the listowner > has written to me. Because the messages are being shunted because of the above exception which is a Python 3.13 issue https://gitlab.com/mailman/mailman/-/issues/1190 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1309. Once you fix that issue by either downgrading Python or installing the changes from https://gitlab.com/mailman/mailman/-/merge_requests/1309 you can reprocess those messages with `mailman unshunt` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: messages go to shunt queue

by Danil Smirnov

Thanks Mark! The change provided has fixed the issue. Danil On Thu, Sep 10, 2020 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/10/20 6:43 AM, Danil Smirnov wrote: > > Hi guys, > > > > I've faced weird Core behaviour after the last upgrade of the docker > > images. All the messages sent to a list now go straight to shunt queue > with > > the following error in the logs: > > > > --- > > Sep 06 22:41:32 2020 (27) Traceback (most recent call last): > ... > > File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line > 217, > > in is_reject_or_quarantine > > for record in txt_rec.items[0].strings) > > KeyError: 0 > > Sep 06 22:41:32 2020 (27) SHUNTING: > > 1599432092.4326646+4cbb58a0dd5d9705946ca583835e63ec175536e3 > > > See <https://gitlab.com/mailman/mailman/-/issues/743>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 10 months

[MM3-users] Re: User display name entry field input ignored

by Christian

Okay. What if I want to change the name from "None" to "firstname lastname" ? How can that be accomplished please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, June 26, 2022 5:22 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: User display name entry field input ignored On 6/26/22 08:03, Christian via Mailman-users wrote: > Whether I try and add users using mass subscribe, or individually, it > seems the display name field entry is ignored. The default is then > "none" for the user. Please advise. Thank you! If the address you are mass subscribing is already known to mailman, i.e., is an existing user, it is that user that will be subscribed with that user's display name, even if it is None. If that address is not an existing user, the user will be subscribed with the display name you provide. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years

[MM3-users] Re: Re-send subscription response and file permission error in queue

by Mark Sapiro

On 9/8/20 10:56 PM, accounts-mailman(a)holbrook.no wrote: > A user sent subscription request to the `..-join@` address of a list. Email domain wasn't set up properly, so response got rejected. Now, if the user tries to send another request, no reponse comes back. In the log I find a python stack trace saying subscription already pending. > > ``` > Sep 08 10:32:44 2020 (19918) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/command.py", line 196, in _dispose > mlist, msg, msgdata, parts, results) > File "/usr/lib/python3/dist-packages/mailman/commands/eml_membership.py", line 104, in process > ISubscriptionManager(mlist).register(subscriber) > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register > list(workflow) > File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 227, in _step_sanity_checks > raise SubscriptionPendingError(self.mlist, self.address.email) > mailman.interfaces.subscriptions.SubscriptionPendingError > ``` I'll look at this when I get some time. I'm still catching up after being off line for 12 days. > Furthermore I am getting a permission denied error in the attempt of shunting the message, which I don't quite understand because the folder has user `list` group `list` and `700` mode: > > ``` > Sep 08 10:25:29 2020 (19918) SHUNTING: 1599553529.9889646+88be5afa0bf3111a83e68cc97ce2000723ad93fd > Sep 08 10:29:49 2020 (19918) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/command/1599553789.306307+6fee74af69263553b5ffd0e73cc095ab651bd855.pck' > Sep 08 10:29:49 2020 (19918) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/command/1599553789.306307+6fee74af69263553b5ffd0e73cc095ab651bd855.pck' > ``` > > How can I remove the pending subscription, or re-send the response email? In Postorius, pull down Subscription Requests and select Pending Confirmation and delete the request. > And what could be the cause of the permission error? Mailman can't read the /var/lib/mailman3/queue/command/1599553789.306307+6fee74af69263553b5ffd0e73cc095ab651bd855.pck file. This is strange since it wrote it, but check the modes and user/group of all the directories in the path and the file itself. Could it be a SELinux or apparmor 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, 10 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/3/22 08:01, Stephan Krinetzki wrote: > Hello all, > > we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? This shouldn't be an issue, at least with Mailman core 3.3.5, unless I don't understand. Note that there are 3 tables involved. The request (IListRequests), the pendings (IPended and IPendedKeyValue), and the held message (IMessageStore). > This is the mailman shell command we used: > > mailman shell -l listname(a)lists.example.com > <removed> > 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. > Die Variable 'm' ist die listname(a)lists.example.com Mailingliste > >>> msg_db = getUtility(IMessageStore) > >>> req_db = IListRequests(m) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 > 107758: 1 OK, you have requests. > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, 107758, Action.discard) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 OK, you discarded the message held with request id 107758. > >>> handle_message(m, 92927, Action.discard) > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: 'NoneType' object is not iterable > >>> There is no request with id 92927. Why do you think there should be? If by remove them from the database, you mean just from the messagestore, you can do (using your above) msg_db.delete_message('the_message_id') To delete a pending request for which there is no request id, e.g. the id 92927 above, you could do ``` pendings = getUtility(IPendings) for token, data in pendings.find(pend_type='held message'): if data and data['id'] == 92927: pendings.confirm(token, expunge=True) ``` Mailman core 3.3.5 has a lot of changes to address this issue. Also see https://gitlab.com/mailman/mailman/-/issues/946 -- 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: Apache Conf

by Thomas G

Same result with Alias "/static/" "/opt/mailman/static/" I have sometimes: [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] AH01102: error reading status line from remote server localhost:8000 [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js But it's not systematic. Alias seem to be ignored by the proxy. Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > What's in the apache error log? > > -- > 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/ >

6 years, 9 months

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Thomas Drillich

Hello Mark, Andrew, thank you for your hints, the hosts_override gives me the way to solve my problem. It was a problem of DNS + resolv.conf, 1. inside resolv.conf there is a domain search defined, - search example.com - 2. Inside the Domain example.com there exists a record "* in a 85.25.8.21", so the question localhost resolvs to localhost.example.com ... 85.25.8.21 After I added the localhost in a 127.0.0.1 into the domain, the exim transport delivers correctly. greetings Thomas Am 06.05.20 um 22:39 schrieb Mark Sapiro: > On 5/6/20 1:33 PM, Mark Sapiro wrote: >> I think you need to add >> >> hosts_override = true >> >> to your transport definition to tell exim to use `hosts = localhost` >> rather than the host part of the email address. >> > Please report back if this is the solution. If it is, we'll update the docs. > > > _______________________________________________ > 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/ -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

5 years, 2 months

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

by tokyoprogressive＠mailbox.org

Thank you to all for helping me find it. Sent from my iPhone > On Aug 31, 2018, at 1:12, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 08/30/2018 02:59 AM, Simon Hanna wrote: >> >> It is being archived. You can find it here >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> You can see it listed here >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2018/8/ >> >> Hyperkitty has a "little" problem with caching and cache-invalidation... > > > And various searches such as "forum" will also find it. It is unclear > why it doesn't appear in the "Recently active discussions" list on the > overview even though I've stopped and started qcluster, gunicorn (the > wsgi server for Django) and mailman. > > -- > 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/

6 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Is there a ´default´ admin account?? El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 06:07 PM, Rafael Mora wrote: > > I want to use Mailman to send emails to our customers. > > > So you need to create a list and add your customers as members. > > Please note that Mailman is not a substitute for a customer relations > management system. It can be used in that way, but a true CRM system has > advantages ove Mailman. Mailman is primarily designed to support > discussion lists such as this one. > > > > I´m getting this error when I click on sign up and log in: > > > > FilterError at /accounts/login/ > > /bin/sh: sassc: command not found > > > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Grandpré

Dear Mr. Sapiro, thank you very much for your request, that is OK for me. You are also welcome to make changes to the documentation. Furthermore, I would like to ask you to contact the colleagues who convert your Mailman3 software into Debian packages. I think that the Mailman3 software should install successfully even if you do not have the DBA password at hand. Best regards, Markus Grandpré On 03.11.22 17:17, Mark Sapiro wrote: > On 11/3/22 03:57, Markus Ludwig Grandpré wrote: >> >> thank you very much for your answers. Below this text you will find a >> brief documentation how I finally managed to install mailman3 and >> mailman3web packages under Debian 11 with a remote PostGreSQL server >> v10.22. > > > Thank you for providing this documentation. With your permission, I > would like to add this to the wiki at > https://wiki.list.org/DOC/5%20Downloading%20and%20installing%20Mailman. > Is that OK, if so may I also acknowledge you as the author? > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

2 years, 8 months

Search results for query "sapiro"