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

[MM3-users] Re: To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues

by Mark Sapiro

On 6/8/24 12:17 PM, Keith Christian wrote: ------------------------------------------------------------------------> Below in line B-6, systemd thinks mailman isn't running, but with the > "/opt/mailman3/venv/bin/mailman" commands, line B-2 says it is. > I could be misinterpreting the systemd output, however. Python not > happy about some directories. All of the systemctl status mailman3.service reports through E 24 are reporting the same failure from Jun 08 09:35:57. The "PermissionError: [Errno 13] Permission denied: '//var/templates'" is what it says. It is trying to create the absolute path /var/templates and user mailman3 doesn't have permission to create a templates/ directory in /var. I'm not sure why this is. It should be trying /opt/mailman3/mm/var/templates. What does ``` /opt/mailman3/venv/bin/mailman info ``` show for config file? Is it correct? Even if it is, you might create /opt/mailman/bin/mailman with appropriate permissions and content ``` #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/venv/bin/mailman \ -C "/etc/mailman3/mailman.cfg" \ $@ ``` or whatever the correct path to mailman.cfg is and use /opt/mailman/bin/mailman in the Exec* entries in your mailman3.service file or you could just add `-C "/etc/mailman3/mailman.cfg"` to the commands. -- 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: email command join - problem

by Mark Sapiro

On 5/27/21 7:43 AM, sky.x--- via Mailman-users wrote: > Hi All > > Im using Mailman core 3.3.4 on Ubuntu 20.04 with python 3.8 anf have this problem with email command join. > > When send command to ml-request@ > > join address=some.email(a)domain.com > > Response is: > Confirmation email sent to 3dsome.email(a)domain.com > > It add characters 3d to email and realy sent confirmation to it. There is apparently a bug in command processing. The issue here is your join command is getting quoted-printable encoded by your MUA so it looks like ``` join address=3dsome.email(a)domain.com ``` where the `=3d` is the quoted-printable encoding of `=`. We need to ensure that commands, are properly decoded. > Also help command for join return me > join [digest=<no|mime|plain>] [address=user(a)example.com] > > But digest doesnt work as after command > > join digest=no address=some.email(a)domain.com > > i get > > join bad argument: digest=no I think this is the same issue. I also think this is fixed by the fix for https://gitlab.com/mailman/mailman/-/issues/859 at https://gitlab.com/mailman/mailman/-/merge_requests/822. This fix decodes the message body including commands in the message body. Commands in the message Subject: were already properly decoded in Mailman core 3.3.4 except possibly if the Subject: contained non-ascii. -- 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 3 stops delivering to a domain after too many bounces

by Mark Sapiro

On 7/12/22 12:34 AM, Julian Kippels wrote: > Hi, > > We have recently upgraded from Mailman 2 to Mailman 3. Since then I > have observed many user reports that mails to mailing lists don't reach > all members. My suspicion is that there are too many "dead" members on > those lists. This was not a problem on Mailman 2, but has become a > problem on Mailman 3. It seems to me that for example Mailman 3 sends > mails to the first 5 existing member addresses from domain A, then > encounters several (20 or so seems to be the threshold) "dead" member > addresses from domain A that generate a bounce and then does not even > attempt to reach the remaining 800 member adresses from domain A and > only sends to members on domain B and domain C. > > Is there a way to globaly ignore bounces and send out mails to all > members of a list, no matter what? Mailman's outgoing runner should not be quitting because of bounces at SMTP time. It seems like there may by some issue causing Mailman's outgoing runner to die. What's in Mailman's var/queue/shunt/ and Mailman's var/logs/mailman.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Mark Sapiro

On 1/2/23 03:54, Onyeibo Oku wrote: > > I pulled the plugs on uwsgi and installed Gunicorn. Gunicorn gave more > mileage but something is still not right. When I visit the mailmanweb > home with a browser, I see the following: > > "Server Error. An error occurred while processing your request." > > Mailmanweb and mailman3 services are running. I perused the log file > at /opt/mailman/web/logs/mailmanweb.log and found the following: > > > raise MailmanConnectionError( > mailmanclient.restbase.connection.MailmanConnectionError: ('Could not > connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', > port=8001): Max retries exceeded with url: > /3.1/lists?advertised=true&count=0&page=1 (Caused by > NewConnectionError(\'<urllib3.connection.HTTPConnection object at > 0x7f7f4b128c40>: Failed to establish a new connection: [Errno 111] > 0x7f7f4b128c40>Connection refused\'))"))') Postorius is unable to connect to Mailman core's REST API. Are your settings for accessing Mailman's REST API correct? E.g., does MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' match $ mailman info ... REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Note the 3.1/ in REST root url is not included in MAILMAN_REST_API_URL. What do you get from, e.g. curl -urestadmin:restpass http://localhost:8001/3.1/lists It should return JSON with information about your lists. -- 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: redirecting -bounces replies

by Mark Sapiro

On 6/25/25 10:53, Hirayama, Pat wrote: > Thanks, Mark. > > I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. > > The current postfix_vmap has entries like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 This looks very strange. It should be something like ``` list-bounces(a)lists.domain.info list-bounces(a)alias.domain ``` where alias.domain is the configured alias domain for the mail host lists.domain.info. > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. > > If I do: > > list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 > > Then it goes to the gmail address, and no bounce processing happens. The issue here is the value `lmtp:[mailman-core]:24` is completely wrong. It should be an email address with a syntactically valid domain name. The domain name isn't a real domain. It is only a name exposed to Postorius in the postfix_vmap and postfix_lmtp files. What do you have configured for the alias domain for the lists.domain.info domain? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… If you have this properly configured, adding user(a)gmail.com in either order in postfix_vmap should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[MM3-users] Re: Turn off social logins?

by Mark Sapiro

On 2/14/19 11:10 PM, Stephen J. Turnbull wrote: > Torge Riedel writes: > > > - there is a way to do this now via settings_local.py, but feels > > a little bit risky if default configuration changes on update of > > mailman > > This should not be true. If it is, we need to fix that. Will check. It is more or less true. The issue is that unlike mm_cfg.py and Defaults.py in Mailman 2.1, the recommended way to set up Django in Mailman 3 is to point Django at settings.py for the default config, and the last thing in settings.py is try: from settings_local import * except ImportError: pass Thus,the only way settings_local.py can change something like INSTALLED_APPS is to redefine INSTALLED_APPS in it's entirety which leads to the possibility of INSTALLED_APPS changing in settings.py and those changes not being picked up in settings_local.py. The way around this is to remove the import of settings_local from settings.py and then put from settings import * at the beginning of settings_local.py and then point Django at settings_local rather than settings. Then you can do things like try: INSTALLED_APPS.remove('allauth.socialaccount.providers.google') except ValueError: pass in settings_local.py except there are still issues because, e.g., INSTALLED_APPS is defined as a tuple (immutable) and not a list in settings.py. -- 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: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. -- 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: Handling of (un)subscribe mails for already (un)subscribed users

by Mark Sapiro

On 12/10/20 2:04 PM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [201210 22:51]: >> On 12/10/20 11:51 AM, Andreas Barth wrote: >>> Hi, >>> >>> I noticed that a mail to -subscribe for an already subscribed user >>> doesn't get any response (about line 225 in >>> mailman/src/mailman/app/subscriptions.py). Same but different for >>> unsubscribe for users not on the list. >> >> >> I tested and I see this, so there is a bug, but I don't know what the >> issue is. > > Ok, if you consider this a bug it makes sense to fix it upstream and > not just locally. > > > >> The code you point to should raise AlreadySubscribedError and >> <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> >> should catch it and report, but this doesn't seem to be happening.. > > Actually I don't see where it should send the mail in the code you > refered to, but I'm pretty new to mm3-code and the involved coding > guidelines. Ther code pointed to adds the error to `results` and returns ContinueProcessing.yes. The return is to mailman/runners/command.py which is ultimately responsible for returning `results` to the user in a `results of your email commands` message. The issue is the code at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/subscripti…> appears to not be executed as in my test at least, the workflow continued. > I would tend to add something along > msg = UserNotification( > self.mlist.owner_address, self.mlist.owner_address, > subject, text, self.mlist.preferred_language) > msg.send(self.mlist) > (with appropriate subject, ...) before > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/subscripti… > but of course that could be the wrong approach (but as > subscriptions.py is sending out mail at other places, that's my first > idea). Aside from the fact that this wouldn't work if that code isn't executed, sending that message at that point would not be appropriate if the subscription request originated from something other than an email command. I.e., if it's a web subscribe, the error should be reported in the web response, not in an email to the user who may not even be the one originating the request. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mark Sapiro

On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 5:32 PM, Peter Adebahr via Mailman-users wrote: > > May 09 01:22:38 2020 (1235) SHUNTING: 1588980158.3151...... > > But immediately before I find the "module 'time' has no attribute > 'clock'" which I remember from a thread a couple of days ago, though I > cannot remember a solution when mm3 has not been installed from source > but via apt-get. > > My core is V 3.2.2, core python 3.8.2, by the way. That is exactly the issue. Mailman 3.2.2 is not compatible with Python 3.8. This is a Debian/Ubuntu packaging bug. What has happened is the post encountered the exception shown in the Traceback that preceded the SHUNTING message and the message that triggered the exception was placed in the shunt queue. The thread you remember is <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> The fix is to patch your Mailman installation with the changes at <https://gitlab.com/mailman/mailman/-/merge_requests/552/diffs?commit_id=ea0…>. Or, at the very least change x = random.random() + right_now % 1.0 + time.clock() % 1.0 to x = random.random() + right_now % 1.0 + time.process_time() % 1.0 in mailman/utilities/uid.py. After doing that and restarting Mailman core you can do `mailman unshunt` to reprocess the message or if you prefer, `mailman unshunt --discard` (or just remove it from the shunt queue) to discard 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, 2 months

[MM3-users] Re: Moderation not working?

by Mark Sapiro

On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: > > Hi Folks, > Running a shiny new instance of mailman3, as per the Debian package > (version 3.2.2) but the moderation doesn't seem to work. WE got > hit by a heap of spammers overnight, even though the 'hold for > moderation' bit is set for non-members (and now for members too). If the action for member posts was accept ot default processing at the time, perhaps the spam spoofed a member address in one of From:, Reply-To:, Sender: or the envelope sender, > Emails seem just to get straight through. Even now with both member and non-member actions set to hold? > Any advice on how to debug this? Would upgrading to a later version > using pip help? An upgrade probably won't help. This should work in your version. For one of the mail's, check all 4 addresses, From:, Reply-To:, Sender: and the envelope sender (available in the MTA logs). Note that Reply-To: and/or Sender: may have been modified by the list. Then see if any of those addresses matches a member or a non-member and what the specific moderation action is for that address. Also check the list's accept_these_nonmembers which is probably not exposed in your version of Postorius but which you can see via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Header Filter madness

by Brian Carpenter

On 1/13/21 3:05 PM, Mark Sapiro wrote: > On 1/12/21 9:57 PM, Mark Sapiro wrote: >> On 1/11/21 6:14 PM, Brian Carpenter wrote: >>> On 1/11/21 8:48 PM, Mark Sapiro wrote: >>>> On January 11, 2021 5:50:04 PM MST, Brian Carpenter >>>> <brian_carpenter(a)emwd.com> wrote: >>>>> I have a client whose header filters seemed to have stop working. No >>>>> matter what I try, it seems none of their header filters are being >>>>> applied. Other lists on the same server that use header filters, are >>>>> working fine. This particular header is the subject header. I can >>>>> duplicate their problem but only with their list. If I create the exact >>>>> same header on a test list using the exact same subject line, the >>>>> header >>>>> filter does its job (moderate). Just not with this one list. >> >> What's in the X-Mailman-Rule-* headers of the post that should be but >> isn't held? >> >> Are there other header filter rules besides the one that doesn't work? > Also, on your test list, did you copy/paste the regexp or retype it. If > the latter, there is possibly trailing whitespace that breaks it. Thanks Mark. I am currently waiting for feedback from my client. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

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

by Mark Sapiro

On 1/16/21 9:46 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > Unfortunately the provided options didn't work out either: > > 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 ************* mailing list >>>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm > workflow.restore() > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore > raise LookupError(self.token) > LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b It appears that although the token was in the pended table, it wasn't in the workflowstate table. I have no clue how this happened. > I noticed that the mail address was also listed as a non-member. > After deleting it there, I could not accept the subscription either. > Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. > > I'll monitor if such cases will happen again. Hopefully it won't happen again, but at least you have a workaround. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Mailman3 is wrongly display name a list member

by Mark Sapiro

On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> 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, 6 months

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

by Mark Sapiro

On 5/29/24 9:48 AM, Marc SCHAEFER wrote: > > May I just modify those files, and is there any way to see, in the web GUI, > where those files are referenced? Yes, you may modify them. The search algorithm for templates is described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… however, this is only for templates which have no entry or a mailman:/// entry in the template table in the database. Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > In the database itself, the template table is empty (as seen in the GUI) and I > did not see the text "web_page_url" in a dump of the database, so I have some > issues to understand how this is used by Mailman (except direct file access > to /var/lib/mailman3/templates?) It is by direct access following the search algorithm. If you are looking at templates in Postorius, these can be created and will place the template in the postorius_emailtemplate table in the database and an entry in the templates table with a URI beginning with the POSTORIUS_TEMPLATE_BASE_URL setting to retrieve the template via the Postorius API. The Postorius template UI should show the current value for a template not yet set in Postorius, but it doesn't. See https://gitlab.com/mailman/postorius/-/issues/366. -- 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: 500 error on Held Messages page

by Mark Sapiro

On 9/20/22 19:54, Dan Caballero wrote: > I'm getting an unexpected error when I try to clear all the held messages. Any ideas what could be wrong here? > ``` > (mailmanve) mailman@11f52637274a:/var/www/mailman-www$ mailman shell -l jewishlife(a)caltech.edu > 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 jewishlife(a)caltech.edu mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > Traceback (most recent call last): > File "<console>", line 3, in <module> > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: cannot unpack non-iterable NoneType object ``` There is a corrupt request with a request id that doesn't exist. Try something like: ``` >>> from mailman.interfaces. >>> 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) ... ``` -- 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: Archives with encoding characters

by Mark Sapiro

On 3/4/20 8:55 AM, Seth Seeger wrote: > Hello everyone, > > I have a few (but not all) members complaining that their digests are full of coded characters. Two examples below were forwarded to me: > >> What I ended up doing was creating 2 "practice lines" in the centre of=20 >> our big teaching circle (I always teach new figures in a big circle) -=20 >> which each had 3 people set up in a line with generous space between,=20 >> and first=C2=A0 I walked through one of those lines myself starting first= >> =20 > > and > >> Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= >> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= >> eft > > What is the cause? Is there anything I can do about it? The cause is a quoted-printable encoded message body not being decoded. This may or may not be a Mailman bug, but if as Mark Dadgar suggests, it only happens with some MUAs, the issue might be in the MUA. To understand more we'd need to see the actual raw digest message from the list, or maybe just a raw incoming message that winds up like that in the digest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/14/23 2:09 AM, Alex Schuilenburg via Mailman-users wrote: > > I am migrating from mailman 3.2.1 & mailman3-web 0+20180916-8 on Debian Buster to mailman 3.3.8 & mailman3-web 0+20200530-2.1 on Debian bookworm, have mailman3 and mailman3-web configured (and running on bookworm) from the initial install. But when I use the mailman3-web 0+20180916-8 database (after stopping mailman3 and mailman3-web) on bookworm, unfortunately migrate fails: ... > But the migrate fails at the first operation: > # mailman-web migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > Applying contenttypes.0001_initial...Traceback (most recent call last): ... > MySQLdb._exceptions.OperationalError: (1050, "Table 'django_content_type' already exists") You are attempting to apply migrations that have already been applied. Apparently the django_migrations table is inconsistent with the state of the database. > Indeed the table django_content_type already exists on 0+20180916-8 . Apart from fields changes, there are an additional 4 tables in mailman3-web 0+20200530-2.1 > > I managed to import the mailman 3.2.1 database to the mailman 3.3.8 database, and all lists, subscriptions and settings looks fine. > > So how can I upgrade my existing mailman3-web database? This appears to be a Debian package issue. I suggest you ask Debian. -- 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: [Mailman-Developers] Re: Help on Gitlab

by Mark Sapiro

Plese keep the thread on the list. On 3/8/24 6:36 AM, Daniel Azubuine wrote: > Sir, I get this error > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python: can't > open file '/home/daniel/Documents/repos/mailman/mailman/setup.py': > [Errno 2] No such file or directory > ERROR: invocation failed (exit code 2)/ > _______________________________________________ summary > ________________________________________________ > ERROR: qa: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python > /home/daniel/Documents/repos/mailman/mailman/setup.py --name (exited > with code 2) > when i run tox -e qa. What is your tox version (tox --version)? You shouldn't need this, but adding ``` skipdist = True ``` in the [tox] section of tox.ini may help. > I also get this when i run tox -e py310-diffcov > ------------- > src/mailman/interfaces/listmanager.py (75.0%): Missing lines 37 > ------------- > Total: 4 lines > Missing: 1 line > Coverage: 75% > ------------- > > ERROR: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/py310-diffcov/bin/diff-cover coverage.xml --fail-under=100 --compare-branch origin/master (exited with code 1) This is expected output in this case. Line 37 in your src/mailman/interfaces/listmanager.py is not covered by any tests. Modifying the test_cannot_create_a_list_twice test in src/mailman/model/tests/test_listmanager.py to use assertRaisesRegex rather than assertRaises may help. See <https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertRai…>. -- 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: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 01:22 PM, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> > >> You need to forward port 25 for SMTP mail delivery and if you want the > >> web UI (Postorius and HyperKitty) accessible from the outside, port 80 > >> for http and/or port 443 for https > >> < > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>> . > >> > > > > I mean for incoming mail redirected from my hostgator hosting, because > when > > I suscribe an email address MM3 sends a confirmation email, so I have to > > reply to be suscribed to the list. > > > As I said, for mail delivery you need to forward port 25 to the Mailman > server. > Ok so I'll redirect in my zentyal firewall the port 25 to my local centos7 with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > -- > 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: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/23/23 02:54, Jana Berger wrote: > > I have multiple control messages, all received from my instance which > all contain the "Content-Transfer-Encoding: base64" marker, their > contents is plain text (Content-Type: text/plain; charset="utf-8"), but > they are still encoded using base64. It seems you are saying these messages are valid. I.e. they specify "Content-Transfer-Encoding: base64" and the body is in fact base64 encoded. This is as they should be. > Of course that is not proof, but an indication that it is either done by > the mail server itself or widely across MUAs. As you say, this suggests that some MTA in the path to your user or the user's MUA is responsible for decoding the base64 encoded body but leaving the "Content-Transfer-Encoding: base64" header as is. > Global "Preferred language" is "English (USA)", which is not overridden > by the list in question. I have not changed the default encoding. Is > there a surefire way to detect this? > > My mailman.cfg has no section pertaining to encoding, and all related > files also do not mention encoding. The Subject: and body of these messages should be ascii, not utf-8 unless you have something like ``` [language.en] charset: utf-8 ``` in your mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Single Click Unsubscribe

by Mark Sapiro

On 1/25/24 15:21, olebra(a)samfundet.no wrote: > > To me, "subscribed messages" in the above means the policy applies to > everyone sending over 5k emails daily, whether for marketing or not. > > All the best, > Ole > > [0]: https://support.google.com/a/answer/81126 > _______________________________________________ > 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… You can always put something like the above "To unsubscribe ..." line in the lists footer as we do. Gmail's web UI renders that as a mailto: link. Further, at least in some cases, Gmail's web UI recognizes the List-Unsubscribe header in the message and provides it's own Unsubscribe buttons in the web UI. Granted, these aren't truly "one click" as they require confirmation, but that can be avoided by setting a list's unsubscribe_policy to `open`. Also granted that Gmail is the 900 pound gorilla here, but unsubscribe links that don't require confirmation are a bad idea. Even if the link contains some kind of encrypted data to ensure it can't be spoofed, there is still a danger if I forward list mail to a 3rd party and they click my unsubscribe link. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Scheduled tasks

by Mark Sapiro

On 6/7/18 9:59 AM, Darren Smith wrote: > All, > > I am looking more through the documentation of the Mailman Suite here: > > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf > > In section 3.2.5 it talks about the scheduled tasks that need to be run to > do "specific routine functions" in hyperkitty. > > I installed through the easy install script found here: > > https://github.com/iomarmochtar/mailman3_ei/ > > However, I can't find anything in THAT documentation that talks about these > cron jobs, and in fact the Mailman Suite isn't installed through that > script. That is a third party project. If you have issues with it, you should take them up with @iomarmochtar. > Can someone point me to any other documentation about the tasks that need > to be run on a continual basis? The section 3.2.5 you refer to tells you what needs to be set up in cron. For a list of the jobs tat are run, use django-admin runjobs --list . Our hyperkitty installation seems to be > bogging down more and more, and I am hoping that it will be as simple as > just running some jobs that haven't been on our radar. what do you mean by 'bogging down'? If you aren't doing so, setting up qcluster as in section 3.2.3 may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

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

by Mark Sapiro

On 7/29/20 9:55 PM, Johnny Cison wrote: > I have a new Mailman 3 server set up and am having a strange issue with > just one particular list. > > Accessing the list's Info page URL or it's Archiving Settings page URL > returns a 500 Internal Server Error, but its other pages work correctly. > Also, the Info and Archiving pages on the other lists are working correctly. > > When I access the info page for the problem list, I get these errors in the > log: > > Traceback (most recent call last): > File > "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", line > 41, in inner > response = get_response(request) ...> line 103, in call > raise HTTPError(url, response.status, content, response, None) > HTTPError: HTTP Error 500: A server error occurred. Please contact the > administrator. > > > When I access the Archiving page in Settings, I get these: > > Traceback (most recent call last): > File > "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", line > 41, in inner ... > line 103, in call > raise HTTPError(url, response.status, content, response, None) > HTTPError: HTTP Error 500: A server error occurred. Please contact the > administrator. These messages are from Django's log. 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

5 years

[MM3-users] Re: postfix malformed address with confirm replies

by Mark Sapiro

On 2/26/21 3:34 PM, Stephen Willey Mats Mats wrote: > > I’m getting bounces back from postfix (553 5.1.3 Error: malformed address) for my confirm replies. ... > I’m pretty sure I have all of the mailman settings in postix: > " > # Support the default VERP delimiter. > recipient_delimiter = + Yes, this is the relevant one and is correct. ... >> The mail system >> >> <matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>: >> host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address >> (in reply to RCPT TO command) >> Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal >> X-Postfix-Queue-ID: E144B8BC3C5 >> X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com >> Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST) >> >> Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >> Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >> Action: failed >> Status: 5.1.3 >> Remote-MTA: dns; 172.19.199.2 >> Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address I have no idea why Postfix is saying `matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu` is a malformed address, but this is a Postfix issue, not Mailman. Can you successfully post to `matsmats-mm3-test1 @mm3.aca-aws.s.uw.edu` how about a `help` command to `matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu` -- 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: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Mark Sapiro

On 3/13/21 7:08 PM, John Covici wrote: > On Sat, 13 Mar 2021 16:22:59 -0500, > Abhilash Raj wrote: >> >> My guess is that you updated the database (perhaps, by invoking the mailman >> command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes >> up and sees a new revision for the database migration added from 3.3.3 but >> can’t find the same migration in its source (because it is 3.3.2). > > That is sort of what happened, except in the opposite direction, it > was from 3.3.3 to 3.3.2. My question is therefore, do I have to > update this alembic_version when I upgrade mailman to a newer version? > That is what I was getting at. Abhilash's conjecture is that the error was due to a Mailman version accessing a database that had been previously accessed by a newer version so that the version_num in the alembic_version table didn't exist in mailman/database/alembic/versions/. This normally would not occur on an upgrade of Mailman, but if you went from a gentoo Mailman core to a version obtained by pip, it's possible that the gentoo Mailman had an alembic version that wasn't known to the pip Mailman even though the pip Mailman was newer. -- 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: sending messages in response to posts from non-members

by Mark Sapiro

On 2/26/22 04:26, David Bremner wrote: > > I'd like to turn off the "bounce messages" sent by mailman to > non-members. My reasoning is that most such posts are spammers, and > often use forged return-paths / From's, so I end of sending steady > stream of backscatter to amazon.com etc... > > Is this configurable (without postorius) somehow? What exactly do you want? Do you want to discard without notice any nonmember posts or do you want to hold them but not send a notice of the hold to the poster? For the former, you want to set the list's default_nonmember_action to discard. For the latter you want to set the list's respond_to_post_requests to False. To make either of these settings the default for new lists, you'd need to patch mailman/styles/base.py. To set them for all lists you could do the following in `mailman shell` ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager).mailing_lists: ... # Pick the appropriate one of the following. ... mlist.default_nonmember_action = Action.discard ... mlist.respond_to_post_requests = False ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Mark Sapiro

On 1/17/23 23:45, Stefan Bauer wrote: > Dear Users & Developers, > > we're running MM3 on Ubuntu 22 and used the venv-installation method. > Last week we updated via¹ to > > Mailman Core-Version GNU Mailman 3.3.8 (Tom Sawyer) > Mailman Core API-Version 3.1 > Mailman Core Python-Version 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC > 11.3.0] > > and now mailman attaches mime-attachments to email as text-files. That > breaks many mails in our environment. > > For example: Now we have attachments like > > smime.p7s + ATT000001.txt as well as what looks like MM footers > "mailing list --- test@domain ... To unsubscripbe send an email to ..." > > How can we get the "old" processing back? I doubt this has anything to do with the upgrade per se. It has to do with MIME multipart (in this case, signed) messages and how MM headers/footers are added. The MM 2.1 FAQ article at <https://wiki.list.org/x/4030707> has some info on this. In order to say more, I would need to see the list's settings for Filter types, Filter extensions, Pass types, Pass extensions, Collapse alternatives and Convert html to plaintext and the complete MIME structure of the incoming 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, 6 months

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

by Mark Sapiro

On 1/24/22 15:06, Mark Sapiro wrote: > On 1/18/22 06:24, Stephan Krinetzki wrote: >> Hello, >> >> We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is >> installed in a venv and deployed using Apache and uwsgi. This works >> quite well so far, only withheld messages cause us a problem: If we >> try to approve them via Postorius, the message is delivered to the >> list immediately, but the success message in Postorius takes a long >> time - on average the process hangs for three minutes until the >> message is no longer displayed. We have already adjusted the timeout >> in gunicorn.cfg, but this does not improve the situation. Are there >> any tips on how we can speed up the REST API? Or is it even a >> configuration error? > > > There are two steps in handling the POST for a held message. The first > step is accepting, rejecting or discarding the message. This is > happening immediately. > > The second step is handling the poster's moderation action based on the > choice from the Set member moderation dropdown in the view of the held > message. This is processed by the code at > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…>. > If no selection has been made, the default value POSTed for > moderation_choice is `no-action` and that code is skipped. If it is one > of the choices `Hold for moderation`, `Reject (with notification)`, > `Discard (no notification)`, `Accept immediately (bypass other rules)` > or `Default processing` that is processed. So presumably a selection has > been made and processing is stuck on getting the member or setting the > member's moderation action. > > Possibly the logs of your database manager will have information. > Some additional info. By gunicorn.cfg, do you mean the file at mailman/config/gunicorn.cfg? If you are using gunicorn as a wsgi server, that is separate from the gunicorn serving the REST API and its config doesn't affect the REST API. The relevant config is mailman/config/gunicorn.cfg?. Also, I doubt the issue is with the REST API per se, but rather it is in Mailman core's processing of the particular endpoint and if that is slow, it is most likely some kind of database issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/19/21 1:26 PM, Sarah H wrote: > I think you've just hit the nail on the head as far as my biggest issue with this project. The documentation lays out an install method that should be roughly followable for anyone (though it needs a bit of fine tuning here and there) and then the rest of the configuration guide and documentation assumes that you have installed the software in a completely different way and doesn't work the same as the guide laid out. Because virtually all that documentation was written by different people and long before the https://docs.mailman3.org/en/latest/install/virtualenv.html was added. > The documentation should be uniform, if you want users to install it one way then write the guide and documentation so that's the "default". Sure present alternatives or notes "if you've installed via git, your commands will look like this xxx" but ultimately the biggest issue I've had with getting this deployed is inconsistent or lacking documentation. I'm not trying to make excuses. I know the docs need improvement, but we are a very small, all volunteer project doing the best we can. If you feel you can offer improvements to the documentation, we'd love to have your help. You are more than welcome to submit merge requests to update the docs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Importing archive from mm21

by Mark Sapiro

On 11/27/23 13:01, Lars Bjørndal wrote: > I imported an archive from a list created in September 2013 with the > following command: > > mailman-web hyperkitty_import -l annonsering(a)hodr.no --since 2013-09-01 <mbox file> If it's a new list with no current archive, I typically don't use --since. If there might be messages in the archive, I normally use something like `--since 1970-01-01` just to be sure I get everything. > No errors reported. And this should have imported all messages with Date: header dates >= 2013-09-01 plus any without Date: headers. > I then did > > mailman-web update_index_one_list annonsering(a)hodr.no > > No, when I go to https://hodr.no/archives/list/annonsering@hodr.no/, I > cannot choose mails earlier than January 2023. > > What's the problem, do you think? The messages are there. I went to https://hodr.no/archives/list/annonsering@hodr.no/ and only saw messages from 2023, but then I went to https://hodr.no/archives/list/annonsering@hodr.no/latest?count=200&page=2 and started seeing all the messages even at https://hodr.no/archives/list/annonsering@hodr.no/. What do you see now? I also note your pages seem to be missing the styling as the references to the styles, etc at https://hodr.no/static/* all return 404. Is the issue fixed for you now? I don't understand what caused the 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: Another interesting error...

by Mark Sapiro

On 04/23/2018 02:59 PM, Darren Smith wrote: > Well, using the mailman shell we were able to find the request that was > causing the problem - it was apparently a spam message that had some > chinese characters in it. I am trying to duplicate this issue in a test environment. I can create a message with an invalid RFC 2047 encoded subject, i.e., Subject: =?gb2312?Q?=ff=fe=de=21=a2?= and send it to a list where it gets held, but I don't get a 500 in postorius and I see the held message with a raw (not decoded) header. I think there were some recent changes that affect this. I'll look some more. > We used the shell to delete the held request... > > And postorius is still giving me an error 500. > > If I'm not mistaken the held messages are kept in .pck files - do you know > if when postorius asks for held messages through the API, does mailman go > to the database or to the .pck? I would actually suspect the latter, or > removing the request should have fixed the problem. They were held in .pck files in Mailman 2.1, but not in Mailman 3. They should just be in the database and deleting them via mailman shell should delete them as long as you quit the shell or commit(). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: mass subscribers disablement!?

by Mark Sapiro

On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote: > I added the additional hosts to ALLOWED HOSTS in settings_local.py and > mailman is distributing mail to subscribers again. However, I then received > many emails of valid users subscriptions being disabled. What would cause > that? Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users(a)mailman3.org/threa… > Can subscriber management be done via command line? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… for description of the available mailman subcommands. If you are interested in re-enabling delivery for members whose delivery is disabled by bounce, you can do this fairly easily in an interactive `mailman shell` session. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… Something like the following session: ``` $ 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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print("Re-enabled delivery for bouncing member {} on list {}" ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() ``` -- 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: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Mark Sapiro

On 5/7/23 10:51, Volkmar Grote wrote: > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: >> >> >> Page not found (404) >> >> Request Method: GET >> Request URL: >> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >> >> ... > > Nginx, /etc/nginx/conf.d/me.domain.de.conf >> server { >> listen 80; >> listen [::]:80; >> >> server_name me.domain.de; >> ... >> location /static/ { >> alias /opt/mailman/mm/static/; >> } > > Again, many thanks in advance for any clue The above in nginx is correct, but you aren't getting the static files via nginx. You need to go to a URL like http://me.domain.de/postorius/lists/. Going to http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi server and doesn't involve nginx at all. You need to go to port 80 where nginx is listening and nginx then proxys requests to 127.0.0.1:8000. Do you also have location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } in /etc/nginx/conf.d/me.domain.de.conf. You need that. -- 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: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 12:39 PM, Mohsen Masoudfar wrote: > Hi Mark, > > Thanks again for the nice Python script. There is an issue with outlook.com. They add a '^M' (carriage Return) before msgid!! > Here is part of the log that shows that. This is not in every log, though. I updated the get_log_data function (please see below), I believe it is not the smartest solution, but it seems to be working for me. Does the script with your change produce a different result than the original? This has nothing to do with outlook.com per se. It only has to do with the length of the log message. Further, I do not think there are actually newlines in these log messages. I think that is just an artifact of how you are viewing the log. > Mar 14 12:53:21 2021 (11701) > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds I suspect if you do ``` grep namprd20.prod.outlook.com /path/to/var/logs/smtp.log ``` The result will be lines like ``` > Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds ``` whereas if they are really split, the result would be ``` > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds ``` -- 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: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 1:02 AM, Simon Coggins wrote: > > All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914 and this was a fix for that. Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. -- 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: No emails distributed after mail received for a new list following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Mark Sapiro

On March 26, 2025 3:28:27 AM GMT+07:00, Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > >My list is named ebill. An email was received for the DL, but not distributed. Can you advise how to troubleshoot from here? > >Mar 25 15:23:04 shackleton12 postfix/smtpd[247708]: connect from smtprelay0015.hostedemail.com[216.40.44.15] >Mar 25 15:23:04 shackleton12 postfix/smtpd[247708]: Anonymous TLS connection established from smtprelay0015.hostedemail.com[216.40.44.15]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256 >Mar 25 15:23:04 shackleton12 postfix/smtpd[247708]: 3CD47189B: client=smtprelay0015.hostedemail.com[216.40.44.15] >Mar 25 15:23:04 shackleton12 postfix/cleanup[247722]: 3CD47189B: message-id=<a7aee014-f200-4bd4-bbc4-bc9f37abb6df(a)systemdatabase.com> >Mar 25 15:23:04 shackleton12 postfix/qmgr[241822]: 3CD47189B: from=<pjbondi(a)systemdatabase.com>, size=3238, nrcpt=1 (queue active) >Mar 25 15:23:04 shackleton12 postfix/smtpd[247708]: disconnect from smtprelay0015.hostedemail.com[216.40.44.15] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 >Mar 25 15:23:04 shackleton12 postfix/lmtp[247723]: 3CD47189B: to=<ebill(a)systemdatabase.ca>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.29, delays=0.06/0.03/0.02/0.19, dsn=2.0.0, status=sent (250 Ok) >Mar 25 15:23:04 shackleton12 postfix/qmgr[241822]: 3CD47189B: removed The above says the message was successfully delivered to Mailman's LMTP runner. Is it queued in one of Mailman's queue/* queued? Check mailman.log for info. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 months, 1 week

[MM3-users] Re: disable body transcoding

by Mark Sapiro

On 9/22/21 9:02 AM, Markus Schaaf wrote: > Hi, > > I have disabled all message modifications and filtering from within the > webUI, and created empty header and footer template files. Still, some > list messages get their body encoding changed to base64, breaking DKIM. > What can I do to prevent this? (I'm a newbie to mailman3, so please give > somewhat complete commands. I have read other threads with similar > questions, but did not understand some shortened configuration commands.) This is probably due to the message body charset being utf-8. The Python email library used by Mailman encodes utf-8 message bodies as base64. There are no configuration settings in Mailman to avoid this. Calling email.charset.add_charset('utf-8') at some point in Mailman's processing might avoid this. E.g. ``` --- a/src/mailman/handlers/validate_authenticity.py +++ b/src/mailman/handlers/validate_authenticity.py @@ -23,6 +23,7 @@ import logging from authheaders import authenticate_message from authres import AuthenticationResultsHeader, SyntaxError from dns.resolver import Timeout +from email.charset import add_charset from itertools import chain from mailman.config import config from mailman.core.i18n import _ @@ -121,5 +122,7 @@ class ValidateAuthenticity: def process(self, mlist, msg, msgdata): """See `IHandler`.""" + # Try to avoid base64 encoding of utf-8. + add_charset('utf-8') if config.arc_enabled: authenticate(msg, msgdata) ``` Note this is just a guess and could be a disaster so test it before trying it in production. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Mailing Lists

by Mark Sapiro

On 12/23/21 3:09 PM, John McDonald via Mailman-users wrote: > I am responsible for the mailing list of a local church. Recently the church was moved to using Mailman for this. When a simple message is created and sent to the mailing list most email addresses received it correctly but those with an Outlook or Hotmail account received attachments and not the message. There are three attachments and one of them has to be opened to view the message. > > Am I missing some setting? First question. Is this Mailman 2.1 or Mailman 3? This list is for Mailman 3. The corresponding list for Mailman 2.1 is https://mail.python.org/mailman3/lists/mailman-users.python.org/ That said, your issue is because the list is adding a message footer (or possibly header or both) to the delivered message. This is discussed in the FAQ at https://wiki.list.org/x/4030707 That FAQ says there are Mailman configuration things you can do. Exactly what you do depends on the requirements of your list and whether this is Mailman 2.1 or Mailman 3. If you don't require that HTML or other non plain text parts be delivered, you can adjust content filtering to remove them and create a simple plain text message which won't have this problem. Or you can ensure that no message header/footer is added. How you do these things depends on your Mailman version. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/16/25 15:14, via Mailman-users wrote: > "Does your empty list:member:generic:footer.txt work to not add any footer to list messages? If so, I can't think of any reason why your list:user:notice:welcome.txt wouldn't be used." > > Sorry, I am not sure how to chekc this. > Can I use a mailman command? > Where does that footer get added if it was not empty? > > Thanks. > > Frances > _______________________________________________ > 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 mark(a)msapiro.net In the above message received from the list, the footer (which is custom) is everything from the horizontal line below your name to the end of the message (and will be added again below my sig). A default footer for this list would be just ``` _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org ``` If the message is a single text/plain part, the footer is added to the body inline. If it is a MIME multipart message, the footer is attached as a separate MIME part. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: Remove login from list subscription page

by Mark Sapiro

On 3/1/22 12:23, bob B via Mailman-users wrote: > Is there any way to easily remove the login button for the List subscription page? 99% of our list do not use archiving, and log-in just confuses users so We would like for them just to be able to sign up to be on the list. You would need to patch postorius/templates/postorius/lists/summary.html Something like this would do what I think you want. ``` --- a/src/postorius/templates/postorius/lists/summary.html +++ b/src/postorius/templates/postorius/lists/summary.html @@ -101,20 +101,9 @@ {% endif %} {% else %} <div> - <h2>{% trans 'Subscription / Unsubscription' %}</h2> - <p>{% blocktrans %} - To subscribe or unsubscribe from this list, please log in first. - If you have not previously logged in, you may need to set up an account - with the appropriate email address. - {% endblocktrans %}</p> - <p><a href="{% url LOGIN_URL %}?next={{ next|default:request.path|urlencode }}" class="btn btn-primary">{% trans 'Log In' %}</a></p> - </div> - <hr /> - <div> - <p> + <h2>{% trans 'Subscription' %}</h2> {% blocktrans %} - You can also subscribe without creating an account. - If you wish to do so, please use the form below. + To subscribe to this list, please use the form below. {% endblocktrans%} </p> <form action="{% url 'list_anonymous_subscribe' list.list_id %}" ``` -- 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: Migration from old server to new server failed

by Helio Loureiro

Hi, This is running on the latest mailman3. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 25 Feb 2024 at 02:52, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/23/24 09:28, Mark Sapiro wrote: > > On 2/22/24 21:51, Stephen J. Turnbull wrote: > >> If I'm correct, I think you'll > >> find the offending message in $var_dir/archive/hyperkitty or some > >> subdirectory, it's a regular queuefile, and you can read it with the > >> showqfile utility to see if it's spam. Otherwise you need to edit the > >> [] out of the message ID. > > > > The directory is $var_dir/archive/hyperkitty/spool/ and the command to > > view the queue entry is `mailman qfile path/to/file`. > > > BTW, the issue with bogus [] delimited Message-IDs is "fixed" (actually > worked around) in Mailman 3.3.9 by > https://gitlab.com/mailman/mailman/-/merge_requests/1099/ > > -- > 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 helio(a)loureiro.eng.br >

1 year, 5 months

[MM3-users] Re: Problem creating list members using REST API

by Mark Sapiro

On 1/18/22 2:11 PM, Stephen Daniel wrote: > The REST API documentation is a bit informal. As someone who is not > familiar with mailman, and who doesn't know python, they are a bit of a > slog. Agreed. I guess we sort of assume that people dealing directly with the REST API are familiar with both. > It might be worth seeing if the code can be enhanced to allow the boolean > values to be sent in using JSON booleans as well as JSON strings. I think here we only have to deal with the REST API because other uses of as_boolean are all on strings that come from config files. We can't modify as_boolean directly, as it is part of a third party dependency and is intended to be used with config files, not JSON objects, but I think something like this will do it. ``` --- a/src/mailman/rest/helpers.py +++ b/src/mailman/rest/helpers.py @@ -249,6 +249,8 @@ class GetterSetter: """ if self.decoder is None: return value + if self.decoder is as_boolean and isinstance(value, bool): + return value return self.decoder(value) ``` Perhaps you could try to test that. I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. It would help me in fixing this if you could provide a small piece of your code that throws the error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

On 8/5/22 14:03, summersan(a)nclack.k12.or.us wrote: > > Previously, there were `34775` files in the `/opt/mailman/mm/var/queue/bounces` directory, ranging from June 7 to August 4. For background, there's typically a time in the summer where many user accounts are purposely disabled (generally near July-August, I think). From the bounce file dates, I wonder if this bounce-related issue has been happening for longer than I first realized. The issue is that sometimes the bounce runner dies. This can be from an OOM error or some other reason, but I have observed it even on systems I admin. The master SHOULD restart it, but it doesn't. See https://gitlab.com/mailman/mailman/-/issues/898. Anyway, it appears your bounce runner died sometime on or before June 7 (if you have syslog from then it might have a clue), and you didn't stop and start Mailman core until August 4 when the bounce runner started again and began chugging through it's queue. I.e., I think everything in your installation is OK and the excessive load was just due to processing the 34775 queued bounces that should have been processed gradually over the previous 2 months. Although 500 bounces per day seems like a lot, but if you have a lot of lists, and bouncing users aren't being disabled because bounce runner isn't running, this may be normal. -- 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: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/26/20 12:33 AM, Alan So wrote: > Thanks. Just filed an issue: > https://gitlab.com/mailman/mailman/-/issues/725 Thank you for your "well formed" issue. I have started to work on this, but I have run into a snag. The patch at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> doesn't work. The problem is msg.get_all(header, []) does not parse the header and return a list of addresses. It just returns a list, the items of which are the raw values if the header instances in msg. I.e., if there is only one Cc: header, msg.get_all('cc', []) returns a list of one string which is the raw value of that header. If there were two Cc: headers in the message it would return a list of two strings with the two raw values. Thus, we would need to parse the strings returned into the individual email addresses. The simple minded way to do that is addrs = [] for hdr in msg.get_all(header, []): for addr in hdr.split(','): addrs.append(parseaddr(re.sub('[\r\n]', '', addr))) but that will fail if the header contains a quoted display name containing a comma such as "last, first" <user(a)example.com> So, I need to go back to using getaddresses, but do the unfolding first. Watch the issue for the final fix. -- 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: List in list, mutiple reply-to addresses

by Mark Sapiro

On 11/25/21 11:00 PM, Stefan Bauer wrote: > Mother: > Anonymous list: No > First strip reply to: No > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > > > > Daughter: > Anonymous list: No > First strip reply to: Yes > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > Because of DMARC mitigation, you can't do what you want. With the settings you have the mother list puts the original From: in Reply-To: and it's own address in From:. Then regardless of what the daughter does with the incoming Reply-To:, it will add the incoming From: to Reply-To: so the Reply-To: of a message from the daughter will always contain the address of the mother. The best you can do, unless you are willing to set DMARC mitigation action: to No DMARC mitigations is what you started with which is First strip reply to: No on the daughter which will at least put the original From: to the mother in Reply-To: from the daughter along with the mother's address, but you can't remove the mother's address from the daughter's Reply-To: because DMARC mitigation will always put it 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, 8 months

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

by Mark Sapiro

On 4/28/22 10:59, bob B via Mailman-users wrote: > We had an issue where a program went rogue and sent out 30k email alerts to one of our lists, so now I have a few questions. > > When the issue happened I turned on emergency moderation and we have resolved the issue so.. > > 1. How do I easily delete 30k of held messages? It looks like the GUI only allows me to do 200 at a time? is there a way to flush all held messages easily? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the thread containing it. > 2. When I enabled Emergency moderation, I expected it to stop notifying the admin on every held message, but it appears that is not the case? Also, does it reply to the sender of every held message when Emergency moderation is on? > > it seems like the steps are: > turn on "Emergency moderation" > turn OFF "Notify users of held messages" > turn OFF "Admin immed notify" MM 2.1 didn't notify the admins of emergency holds. This is not the case in MM 3. It probably should be, but isn't. Senders are or aren't notified per "Notify users of held messages". So the steps above are correct. -- 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: using SSH/TLS with external MTA

by Mark Sapiro

On 7/24/24 06:35, Roland Giesler via Mailman-users wrote: > I have managed thus far to get things working on my new install, but I > need to use a secure logon to send mail from an external MTA. I have > set up: > > /etc/mailman/mailman.cfg: > > smtp_host: box2.gtahardware.co.za > smtp_port: 465 > smtp_user: roland(a)giesler.za.net > smtp_pass: <hidden> > smtp_secure_mode: smtps > smtp_verify_cert: no > smtp_verify_hostname: no This looks OK, but > I'll get a cert installed later, for now just want to get it going. The `no` values for smtp_verify_cert and smtp_verify_hostname may be part of your issue. ... > "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line > 125, in _send > self.connection.sendmail(from_email, recipients, > message.as_bytes(linesep='\r\n')) > File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail > raise SMTPRecipientsRefused(senderrs) > smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, b'4.7.1 > <roland(a)giesler.za.net>: Relay access denied')} > > However, the mailserver is in daily use and accept logon all the time. I > believe I'm missing something that should be installed to make SMTPS > (SSL) work, but what? It is the mail server at box2.gtahardware.co.za that is refusing to relay this message. I think this issue needs to be resolved in that MTA's configuration. -- 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: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/27/25 12:36, Kim Sunggun via Mailman-users wrote: > script: > #!/usr/bin/env python3 > import smtplib > > host = 'localhost' > port = 25 > connection = smtplib.SMTP(host=host, port=port) > connection.ehlo() > connection.quit() > > result: > Traceback (most recent call last): > File "/opt/mailman/./testone.py", line 7, in <module> > connection = smtplib.SMTP(host=host, port=port) > File "/usr/lib64/python3.9/smtplib.py", line 255, in __init__ > (code, msg) = self.connect(host, port) > File "/usr/lib64/python3.9/smtplib.py", line 341, in connect > self.sock = self._get_socket(host, port, self.timeout) > File "/usr/lib64/python3.9/smtplib.py", line 312, in _get_socket > return socket.create_connection((host, port), timeout, > File "/usr/lib64/python3.9/socket.py", line 856, in create_connection > raise err > File "/usr/lib64/python3.9/socket.py", line 844, in create_connection > sock.connect(sa) > ConnectionRefusedError: [Errno 111] Connection refused So you are doing the same thing Django allauth is doing with the same result. Do you even have an MTA listening on localhost, port 25? You need to figure out what settings you need to be able to connect to your outgoing MTA and set EMAIL_HOST EMAIL_PORT and maybe some of EMAIL_HOST_USER EMAIL_HOST_PASSWORD EMAIL_USE_TLS EMAIL_USE_SSL EMAIL_SSL_CERTFILE EMAIL_SSL_KEYFILE appropriately so you can connect to the MTA. If outgoing mail from Mailman works, look in the [mta] section in mailman.cfg for the appropriate settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/15/19 3:45 AM, Wolfgang Bock via Mailman-users wrote: > > That doesn't solve the problem. I changed that in mailman-web.py > (MAILMAN_REST_API_URL = https://localhost:8001) and after that in > mailman.cfg (use_https: yes). But got the same errormessage on postorius > website. You posted this log excerpt: Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type The first 3 GETs are a normal sequence of GETs from Postorius when you go to the Mailing Lists view. That should be followed by a GET like "GET /3.1/domains/domain.tld HTTP/1.1" where domain.tld is a configured domain. Do you have any domains configured?/0.9'? I'm not sure what the issue is. You have an older version of mailmanclient < 3.2.3a1 which uses httplib2 rather than requests. https://pypi.org/project/httplib2/ says: HTTP and HTTPS HTTPS support is only available if the socket module was compiled with SSL support. but I don't think this can be the issue because the first 3 GETs work. You might try upgrading mailmanclient to 3.3.0. I don't know if that will help, but it may. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

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

by Mark Sapiro

On 6/30/20 7:03 AM, Brian Carpenter wrote: > On 6/30/20 9:56 AM, tom(a)gather.coop wrote: >> I have a Mailman 3 server up and running but I'm terrified to migrate >> to it from my existing Mailman 2 provider for fear that services like >> Gmail will randomly start blacklisting my IP with little I can do >> about it. I have SPF records set up so I'm hoping I'll be Ok but I'd >> like to have a backup plan. ... > There is no reason to be afraid if you are sending out legitimate > communications. SPF records will help. You will also need to enable > DMARC mitigation on your lists and Mailman 3 does that very well as > Mailman 2 did. It also helps if you sign your outbound mail with DKIM. > With those 3 things in place, you should have no problem sending mail. > Keep in mind AT&T will probably block you if the IP address you are > using is new. That is standard practice for them. It's easy to get that > block remove. Same goes for Comcast using their Vader RBL. You also need to ensure you have full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. That together with SPF and DKIM signing of outbound mail is virtually essential for deliverability. -- 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: Mailman stops processing....... where to start looking for root cause?

by Mark Sapiro

On 3/29/24 12:34, bob B via Mailman-users wrote: > Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. ... > So where can I look to try to determine a cause? > If it happens again, what and where can I cook to troubleshoot before restarting the service? One of the runners has died, most likely the `out` runner, but possibly another. The missing messages are stuck in a queue. Do ``` ls -laR /opt/mailman/core/var/queue ``` to see in which queue the messages are. The runner that processes that queue is gone or possibly stuck. Do ``` ps -fwwu mailman|grep runner= ``` when things are working to get a list of what runners should be there. Do it again when things aren't working to see what's missing. There also should be something in mailman.log about why the runner died, but if it was killed for some external reason, there may not be anything. Look in `syslog` for something like an out of memory (OOM) or other issue that caused the runner to die. -- 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: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/14/24 21:40, adam.heathcote(a)utas.edu.au wrote: > Hi Mark, > > Sorry about the delay in replying. > > You're correct, I am clicking on the list in the Mailing List view. > > Navigating to the list URL directly while not logged in produces the same error and even produces the error when a different user is logged in. Now it's my turn to apologize. I've been traveling. In your original post you wrote "I've tried removing it and reimporting it to no avail." What exactly does this mean. You removed the list how? Then you reran the import21. Was the list broken at that point, or only after removing the old owners and adding yourself? What if you try the following steps in order and try to view the list in Postorius after each step. - remove the list with `mailman remove list(a)example.com` and recreate it with `mailman create list(a)example.com` - run `mailman import21 list(a)example.com path/to/config.pck` - in Postorius, add yourself as owner. - in Postorius, delete one of the other owners. - repeat the deletion and viewing the list for the other unwanted owners one at a time. If the view throws the error at some point, after which step? -- 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: Customise Postorius templates?

by Mark Sapiro

On 2/1/22 09:47, Duane Raymond wrote: > Hi, > > I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying > venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html > to > var/templates/lists/summary.html > > As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. The var/templates directory has a specific structure and is only for custom list specific, domain specific and sitewide templates used for notifications from Mailman core. It has nothing to do with Postorius or HyperKitty templates. > Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!) I don't know about a `best` way, but the way I do this is to keep all local mods as patches to the base and apply those patches as part of the upgrade process. -- 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: Problem replying via Hyperkitty

by Mark Sapiro

On 6/30/22 10:07 AM, Jeff wrote: > Hello Everyone, > > A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: > > [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) This looks like the post of the reply to HyperKitty. What does the user see in response to that? There should be a brief alert popup indicating the message was sent. > A couple of basic questions: > > 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? To the list. > 2) what log files could I check to see what — if anything — happens to these emails? Mailman's var/logs/mailman.log, The MTA logs and the Django logs. > 3) Are there any settings that need to be set to make this work? There shouldn't be as long as the list and archiving work. Note, a user can select 'Use email software' when replying which should open a composition dialog in their email client to post a reply yto 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 years, 1 month

[MM3-users] Re: No e-mail distribution after import of archive

by Mark Sapiro

On 11/12/24 00:52, Markus Grandpré wrote: > > In smtp.log I found: > > Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO > mailman-app-test.kim.uni-konstanz.de' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL > FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: > markus.grandpre(a)uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT > TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: > Import_mm3_testliste(a)mailman-test.uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost > during _handle_client() > > I have no idea why there is a "connection lost". What do you think? How > can I increase the log level? This is delivery of the message to Mailman. `connection lost` is normal and not a problem. This has nothing to do with your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Which folder should I share between pods with kubernetees persistentVolumeClaim ?

by Mark Sapiro

On 2/6/25 02:37, antoine.depoisier--- via Mailman-users wrote: > > There are all the folders in mailman > archives cache data etc lists locks logs master.pid messages queue templates Here's my opinion. archives - If the prototype archiver is enabled for a list, its posts are archived here in maildir format. This should be shared for consistency, but if you don't care about this, you can put `enable: no` in the [archiver.prototype] section of mailman.cfg to disable it. cache - you're already sharing data - doesn't need to be shared unless it contains a sqlite mailman.db that's actually used. etc - doesn't need to be shared. lists - should be shared as it contains the mailboxes (digest.mmdf) for accumulating messages for a list's digest locks - should be shared master.pid - must not be shared as it contains the pip of the master process running on that node. messages - you're already sharing which you should. queue - this is tricky. If it isn't shared once a message gets queued in virgin/ or in/ on a node, only that node's runners will process it through its queues. This may have an impact on load balancing. templates - doesn't need to be shared, but should be synced between nodes. -- 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: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/2/21 12:48 AM, klillipuu(a)gmail.com wrote: > Hello All! > > I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. > So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). > I also mention, that hyperkitty is a pretty old version - 1.1.4. > The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. > Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? It would be good to upgrade. Current HyperKitty/Postorius/Django is Python3 which will remove your dependency on Python 2.7. Also, there have been many performance improvements in more recent versions which may solve your issue. Your gateway timeout issue is a uwsgi time limit. You can increase that in your uwsgi configuration. > Extra information: > * I have also noticed some memory violation issues which has caused by uwsgi. > * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Are these coincident with the gateway timeouts or do they occur at different times? -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/14/24 08:42, jkoral(a)luc.edu wrote: > joetest(a)listservnew.luc.edu is the list, but in postfix_lmtp, it is showing up as joetest(a)luc.edu. Where can I change that? I tried changing the domain and site, but it still has not changed. The list has a mail_host attribute which is set when the list is created. Presumably, you created the list as `joetest(a)luc.edu`. You have to change the mail_host attribute of the list, but it may be easier to just delete it and create a new joetest(a)listservnew.luc.edu list. Then you can ignore everything below. To change the mail_host for the list you can do a database query or use `mailman shell`. The database query is ``` UPDATE mailinglist SET mail_host = 'listservnew.luc.edu' where list_name = 'joetest'; ``` The `mailman shell interaction is ``` $ mailman shell -l joetest(a)luc.edu 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 >>> m.mail_host = 'listservnew.luc.edu' >>> commit() ``` If you do either of the above to change the mail host, you probably need to do `mailman aliases` to regenerate the files for Postfix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 15:49, Christian via Mailman-users wrote: > Mail.log > > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from > box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: > client=box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: > header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; > from=<christian(a)naturalintelligence.us> > to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP > helo=<box.ecovillage.cc> > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: > message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: > from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from > box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: > to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces(a)lists.ccalternatives.org? Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read? -- 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: Moving existing lists to a new domain

by Mark Sapiro

On 9/18/24 10:13, Jeremy Stanley wrote: > > Since all the lists for the given domain will be moving to the same > unused new domain on the existing server, and can move at the same > time, I suppose this could be done through (offline if necessary) > backend database update queries. Yes. For the mailing list, the only changes needed are to the mailinglist table; A query like ``` UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = 'old_domain'; ``` would do, but this leaves the question of list_id. According to RFC 2919, section 4, the list_id should not change, but this is problematic in that if it isn't changed, a Postorius URL like https://example.com/mailman3/lists/list_name@new.domain will retrieve the list, but https://example.com/mailman3/lists/list_name.new.domain will not work. It would need to be https://example.com/mailman3/lists/list_name.old.domain so to reduce confusion, it may be better to update the list_id values A query like the following after the above should do it ``` UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE mail_host = 'new_domain'; ``` For HyperKitty, similar changes need to be made to the hyperkitty_mailinglist table. The `name` column entries need to be changed from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column entries need to be changed from `listname.old.domain` to `listname.new.domain` -- 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: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/28/20 10:20 AM, Shashikanth Komandoor wrote: > > I tried for the command to know if any entry in the "address" table for > which 'id' is not an integer. > > But unfortunately, I could not get any command or idea how to find that. > > But out of my extra talent, I tried the below commands which, I thought, > may print the records which contain a non integer id value. ... > select id,email from address where id NOT BETWEEN 1 AND 84203; > id | email > ----+-------(0 rows) > mailman=# select id,email from address where id NOT BETWEEN 1 AND 84202; > id | emai> -------+-----------------------------> 84203 | user(a)exampl.com > > *1 and 84203 are the minimum and maximum values of the id:* > > Please see the above outputs and suggest if anything possible or please let > me know the command what should I run to find a non integer id value. > The above looks qood to determine if there is a non-integer value. > I also doubt this error as if my REST API is contacting postgresql in a > delayed manner. If possible, can you say what optimal setting I can do at > Postgresql so that faster responses would be given to REST API. I'm out of ideas. -- 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: Docker-Setup: example.com in test mails

by Mark Sapiro

On 3/28/22 00:04, Bjoern Franke via Mailman-users wrote: > > Thanks for your reply. It seems the probes were triggered by some > rejected example.com mails and I have no idea where the example.com > mails are coming from. I think what you are seeing must be some kind of spam. If not if you could post the complete raw message of one of these probes or probe bounces, I'll look further. > Some users also reported they got some "unsubscribed due to bounces" > messages but the bounce.log contained only entries for them 7 days ago. And were they unsubscribed? In general, unsubscription does not occur until some time after bounces are recorded. At some point, bounce score reaches threshold and a probe is sent. The probe may not bounce for days if the bounce is some downstream timeout. When the probe bounce is received, the user's delivery is disabled by bounce. This starts a process where the user is sent a warning at intervals until a limit is reached and the user is finally removed. The default settings are: bounce_you_are_disabled_warnings = 3 bounce_you_are_disabled_warnings_interval = timedelta(days=7) which means the user is sent 3 warnings, one immediately, one after 7 days and one after 14 days until finally being unsubscribed after 21 days. An entry 7 days ago could be a bounce of a warning message. -- 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 3, postfix domains, and postgresql cannot authenticate user

by Mark Sapiro

On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > --------------------------------------------------------------------------- > First issue:Postfix v3.5.8 on RHEL 8. > The below is from journalctl -xe: > --------------------------------------------------------------------------- > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > directory > > I manually created the var_dir: /opt/mailman3/mm/var directory > specified in the mailman.cfg file. > How do I find out how to populate the postfix_domains.db files, and > the postfix_lmtp.db file? The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. > --------------------------------------------------------------------------- > Second issue: Postgresql authentication. > PostgreSQL v10.23. > --------------------------------------------------------------------------- > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > same complex password in the mailman3 config file: > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 I don't think you should have two /mailman3 at the end the form is `postgresql://user:password@host:port/database_name` The default port is 5432. -- 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: Dropdown problem in postorius due to bootstrap

by Mark Sapiro

On 7/9/24 1:18 PM, Greg Newby wrote: > (My first post) > > As has been observed, the Ubuntu 24.04 LTS packaging for native Mailman3 > can be challenging. I've been solving all kinds of issues, and I'm writing > here about something I've so far been unable to solve. Are you using the Debian/Ubuntu packages? If so, this may be a Debian issue. See https://wiki.list.org/x/12812344 ... > I've dug deeply into this. The relevant <script> is bootstrap.min.js. > Postorius (via django) is using version 5.3.1 via package libjs-bootstrap5: > > ** This is what django is using: > /usr/share/bootstrap-html/js/bootstrap.bundle.min.js -- version 5.3.1, > linked to: > /usr/share/javascript/bootstrap5/js/bootstrap.bundle.min.js > > /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js The Gnu Mailman project's postorius ships with postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js version 5.1.3 ... > By temporarily replacing > /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js > I have tried moving back to 4.6.1 (from libjs-bootstrap4). I have also > retrieved the latest 5.3.1 from the CDN, which is slightly different but > doesn't change the error: > https://cdn.jsdelivr.net/npm/bootstrap@5.3.1/dist/js/bootstrap.bundle.min.js Try using the ones from https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/static/pos… -- 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: Moderation of posts via email is not working in mailman 3

by Shashikanth Komandoor

Thank you Mark Sapiro for your response. After going through the discussion at the link you provided, I understood as of now, it is not possible to moderate the posts through the mails in Mailman 3. But since the user is getting the "confirm" attachment to the mail, the users are getting confused. Is there any work around to achieve this? or Is there any way to remove that "confirm" attachment so that users would not get an idea of confirming via email? <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 Tue, Jun 30, 2020 at 2:46 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/29/20 12:24 AM, Shashikanth Komandoor wrote: > > > > Is there any bug or limitation in mailman 3 or if I am doing > > any wrong at the server side? Please suggest. > > > > This is a known issue in Mailman 3. See > <https://gitlab.com/mailman/mailman/-/issues/169>. > > -- > 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, 1 month

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

by Mark Sapiro

On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: > I'm trying to set up mailman3 on two hosts, one of which runs core + > exim, the other runs postorius (&possibly hyperkitty). > > I have I think got core set up correctly, and postorius is sort of > usable, but anything in the web ui that talks to core ends up with a > white screen. > > I think what is happening is a postorius URL ends up with the core (or > perhaps no) hostname, and as there's nothing there to answer it fails. What are your Django settings for MAILMAN_REST_API_URL, MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with the [webservice] settings for hostname, port, use_https, admin_user and admin_pass in mailman.cfg in core and is the port open to the outside on the core machine? > I've checked the settings and I don't think I have misconfigured > postorius. Is it possible that the bad url is being passed from core to > postorius in some way and reused without changing the host? > > In the config at present, both hosts are visible to the browser, and > each host can communicate with the other. > > Any ideas on how to pin down the problem better? Do you see REST requests from the Postorius machine in core's mailman.log and access.log? -- 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: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:21 AM, Nate Coraor wrote: > > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. I'm trying to get a new > list to behave the same way so I can figure out what's going on without > spamming a production list, but have been unsuccessful: despite setting > nearly all the list options the same as the old lists, new lists pass HTML > portions and attachments just fine. > > I've verified the settings using mailing list objects directly with > `mailman withlist` on the command line and the only differences are things > that I can't imagine would be related like admin_notify_mchanges, > advertised, and archive_policy. Are there are really old options that can't > be accessed via mailing list objects obtained with `withlist` on the > command line? No, there aren't "hidden settings" The relevant settings are filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext These are exactly analogous to the MM 2.1 settings filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext and should behave the same way. Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist. -- 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: MM3 templates

by Mark Sapiro

On 2/15/23 08:09, Odhiambo Washington wrote: > > [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > total 48 > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. > -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt This template is used in a domain context. It will never be accessed here. It needs to be in /opt/mailman/mm/var/templates/site/en/ or /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ > -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt > -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt > -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt > -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt The generic footer is used for both regular messages and digests if there isn't a specific regular or digest footer. In this case, you have both so the generic footer won't ever be used. > -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt > -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt > -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt > -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt > -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt Are the other templates such as list:member:regular:footer.txt used? -- 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: Problems getting started with postorius

by Mark Sapiro

On 11/13/24 16:46, Alain D D Williams wrote: > > I eventually tracked it down. The problem was that I had signed in with an > account "addw@localhost". That, for some reason, failed validation above. > I hacked the database and changed to "addw(a)localhost.localdomain" and creating > the new domain worked. > > I could send email to addw@localhost - so at the MTA level it is correct. > > So please can the initial account creation do the same validation as does > adding a new domain. Mailman doesn't allow local, unqualified addresses, see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/validate… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/emai… On the other hand, Account creation/validation is done by django-allauth over which we have no control. > I have looked but cannot find any documentation on postorius than > https://docs.mailman3.org/projects/postorius/en/latest/ > which is not helpful for a user or system admin. Can you point me to something > better. Unfortunately, there is not user/list owner documentation for Postorius. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I did it via pip and all seems to be working, but when I try to discard > or accept any message via postorius it shows a Forbidden 403 error CSRF > verification failed. > > In my settings.py I have commented out these variables: > > # Other security settings > # SECURE_SSL_REDIRECT = True > # If you set SECURE_SSL_REDIRECT to True, make sure the > SECURE_REDIRECT_EXEMPT > # contains at least this line: > # SECURE_REDIRECT_EXEMPT = [ > # "archives/api/mailman/.*", # Request from Mailman. > # ] > # SESSION_COOKIE_SECURE = True > # SECURE_CONTENT_TYPE_NOSNIFF = True > # SECURE_BROWSER_XSS_FILTER = True > # CSRF_COOKIE_SECURE = True > # CSRF_COOKIE_HTTPONLY = True > # X_FRAME_OPTIONS = 'DENY' > > I've been messing with them whith no results. It's like it lacked some > value in some template... It's not an issue with the code per se or the templates. These updates are all installed on mail.python.org and lists.mailman3.org and are working fine. After upgrading did you run django-admin collectstatic --clear django-admin compress django admin migrate If you have and it doesn't help, you probably need to add CSRF_TRUSTED_ORIGINS to your settings.py. See https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins and note the differences between Django <4.0 and >=4.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 10:12, andrea.janna.unipd(a)gmail.com wrote: > >>From the database debug log I guess that mailman gatenews abruptly terminates the database connections. > For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry. > > 70759 Connect mailman3web@localhost on mailman3web using Socket > 70759 Query SET sql_mode='STRICT_TRANS_TABLES' > ... > 240131 18:54:34 70759 Quit > > There is a "Quit" at the end. > While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end. You could try the following in `mailman shell` ``` $ 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).mailing_lists: ... print(mlist.fqdn_listname) ... (here should be a list of your mailing lists) >>> ``` Does this produce the expected list of mailing lists and does it produce the error in the database debug log? If it does produce the expected list of mailing lists and the error in the database debug log, I'd say this is some issue between SQLAlchemy and MariaDB, but it seems harmless. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users]New Mailman 3 users list

by Mark Sapiro

I'm happy to announce a new list for Mailman 3 users and others interested in Mailman 3. This list is running on a new Mailman 3 installation at lists.mailman3.org. The list's posting address is <mailman-users(a)mailman3.org>. The list's info page is <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> and its archives are at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/>. The top level Postorius page is <https://lists.mailman3.org/mailman3/> and the HyperKitty archiver is at <https://lists.mailman3.org/archives/>. You can subscribe by email by sending a blank message to <mailman-users-join(a)mailman3.org> and responding to the resulting confirmation request. You can also subscribe by going to the info page at <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>, logging in and subscribing. Log in offers three options. There are Google and Facebook OAuth2 login links on the log in page to log in with a Google or Facebook account, and there is a 'Login by email' link to login via Persona with any address you register and confirm with Persona. This is a new installation of Mailman 3 so there are still kinks to work out, and any issues can be discussed on the list or reported to the trackers at <https://gitlab.com/mailman/postorius/issues>, <https://gitlab.com/mailman/hyperkitty/issues> or <https://gitlab.com/mailman/mailman/issues> as appropriate. Enjoy! -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Mark Sapiro

On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- 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: Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)

by Mark Sapiro

On 3/8/24 11:29 AM, Wikinaut wrote: > Is there a possibility to > > > - to discard the present mail ; and > - accept this sender (non-member) for further mails ? > > The reason: > - Member has sent from their office mail (= not yet known address) - mail 1 on hold and > - sent successfully mail 2 (copy of mail 1) from the known address > > So I want to discard the mail #1 (because the copy mail #2 was sent already) but I want to add his office address as member or to the whitelist. > > Can this be done in one step? It would be nice, at least. This was answered in the message to which you replied, found at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. To reiterate, go to the held messages view. Click the subject of the message, pull down the `--- Set member moderation ---` dropdown and select `Default processing` or if you really want to bypass additional checks, `Accept immediately (bypass other rules)`, and click the `Discard` button. It doesn't matter that the address wasn't known beforehand. The post itself created a non-member record for the sender, and the above will set that non-member's moderation action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Hyperkitty tracebacks: possible DB corruption?

by Mark Sapiro

On 3/12/24 11:12 PM, peter--- via Mailman-users wrote: > FOr the other issue, I changed > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/thread… > > From: ``` > if request.user.is_authenticated: > last_view_obj, created = LastView.objects.get_or_create( > thread=thread, user=request.user) > if not created: > last_view = last_view_obj.view_date > last_view_obj.save() # update timestamp ``` > to: ``` > if request.user.is_authenticated: > try: > last_view_obj, created = LastView.objects.get_or_create( > thread=thread, user=request.user) > except LastView.MultipleObjectsReturned: > last_view_duplicate, last_view_obj = LastView.objects.filter( > thread=thread, user=request.user).order_by("view_date").all() > last_view_duplicate.delete() > created = False > > if not created: > last_view = last_view_obj.view_date > last_view_obj.save() # update timestamp ``` > > and that seems to have fixed it. Wrapping the last_view_obj, created = LastView.objects.get_or_create() in a try, except seems appropriate, but your code in the except clause assumes there will be exactly 2 objects returned. Something like ``` except LastView.MultipleObjectsReturned: last_view_objects = LastView.objects.filter( thread=thread, user=request.user).order_by("view_date").all() last_view_obj = last_view_objects[-1] for object in last_view_objects[:-1]: object.delete() ``` might be better. > I've been thinking though that it'd be better to fix duplicates in the > LastView class rather than on every get() or get_or_create() call. That might be good, but these exceptions are rare. I'm not sure how they even occur, so catching them on the get() or get_or_create() calls seems OK. -- 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: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 1:59 PM, Quanah Gibson-Mount wrote: > >> Click on the subject in the held messages list. At the bottom of the >> dialog that opens, there is a drop down to set the user's moderation. >> Normally, you would set it to 'default processing'. > > I do not see any such option. After clicking on the header the only > options available at the bottom are: > > Accept, Reject, Discard, Show Source, Show Header > > There are zero drop downs anywhere. This was implemented by <https://gitlab.com/mailman/postorius/-/merge_requests/397> and released in Postorius 1.3.0. >> This was not "removed". It just hasn't been implemented in MM 3 yet. > > So in terms of available functionality that was present in MM2, it was > removed. It may need to be re-implemented, but this was a core feature > that was present in the prior version that is no longer available. Yes, we are aware of many things that are not yet exposed/implemented in Postorius and elsewhere. There are currently 580 open issues at <https://gitlab.com/groups/mailman/-/issues>. We are working on these things as we can. We would love to have your help in fixing these. In the mean time, there are really only 2 or 3 core developers working on this and we are all volunteers, so it takes time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Sapiro

On 5/18/21 4:06 PM, Mark Dadgar wrote: > I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. > > Any ideas what’s going on here? ... > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login > emailaddress = EmailAddress.objects.get_for_user(user, email) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user > ret = self.get(user=user, email__iexact=email) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get > raise self.model.MultipleObjectsReturned( > > Exception Type: MultipleObjectsReturned at /accounts/login/ > Exception Value: get() returned more than one EmailAddress -- it returned 2! > Request information: > USER: AnonymousUser Go to the Django admin users page - something like http(s)://example.com/admin/auth/user/ - and search for the email address. This search is case-insensitive and I'm guessing it will find two users differing in case. In any event, django allauth is trying to find this user and is finding multiple EmailAddress.objects for this address or username. -- 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: Hyperkitty

by Mark Sapiro

On 1/30/23 13:17, Onyeibo wrote: > > The mails don't have that header. I suspect I may have to investigate > SELinux. I think it's unlikely a SELinux issue unless you mean it's an issue writing the log, but if there are any entries at all in mailman.log, that should be OK. what does `mailman conf -s archiver.hyperkitty -k configuration` show? The default is `/etc/mailman3/mailman-hyperkitty.cfg`. Whatever it is, what's in that file. It should be something like ``` [general] base_url: http://127.0.0.1:8000/archives/ api_key: some_key ``` some_key needs to match ``` MAILMAN_ARCHIVER_KEY = 'some_key' ``` in /etc/mailman3/settings.py and the base_url setting needs to access hyperkitty. It could be as above or it could be the URL that accesses HyperKitty externally as in ``` base_url: http:://example.com/archives/ ``` Is all of that correct? To verify base_url, you can do ``` curl http://127.0.0.1:8000/archives/api/ ``` where the initial part of that is the base_url setting. That should return the html for a page of documentation. Look at https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperki…. This is Mailman Core's interface to the archiver. If any of the methods there fail to connect to HyperKitty or get an appropriate response, they all log errors. In particular, the archive_message() method at line 171 is saving the message in the spool queue. Immediately before that at lines 164 and 167 it is writing log messages. You should be seeing them. -- 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: troubleshooting hyperkitty

by Mark Sapiro

On 12/9/20 5:01 PM, Morris Jones wrote: > > did that as well ... > > base_url: https://mailman.whiteoaks.com/hyperkitty/ > > (Though the configuration comment on this suggests it should not be > publicly accessible, I don't see any alternative endpoint that's private.) The comments in mailman-hyperkitty/mailman-hyperkitty.cfg say in part # ... It does not need to be publicly available, in fact it's # better if it is not. but they add # However, if your Mailman installation is accessed via HTTPS, the URL needs # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty) > I added both my public IP address and my domain name to > MAILMAN_ARCHIVER_FROM. > > So this part is all set, it would seem ... > > [archive.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg > > [logging.archiver] > path: /opt/mailman/var/logs/archiver.log api_key What is api_key? Is your setting for api_key somehow garbled. Note it needs to be set in the general section of mailman-hyperkitty.cfg and not in mailman.cfg > My archiver log continues empty > > The API keys match in settings_local.py MAILMAN_ARCHIVER_FROM and > mailman-hyperkitty.cfg The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not MAILMAN_ARCHIVER_FROM, a typo in your mail or ?? Anyway, in settings_local.py the key is a python string and must be quoted, but the api_key setting in mailman-hyperkitty.cfg is not quoted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

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

by Mark Sapiro

On 10/17/20 10:39 AM, Torge Riedel wrote: > > The message is being held because: > > Header "Yes" matched a header rule > > At your convenience, visit your dashboard to approve or deny the > request. > > I think this is wrong, it should read 'Header "x-spam" matched a header > rule'. Cause the header rule is configured for header "x-spam" and > pattern "Yes". The message is defined as 'Header "{}" matched a header rule' where {} is replaced with the value of the matching header. I agree it would be better if it were something like 'Header value "{}" matched a header rule for {}:' with {}s replaced with the header value and name. That would make it in your case 'Header value "Yes" matched a header rule for x-spam:' > I haven't found a bug report for this yet on gitlab. If someone of the > developers confirm this is wrong, I will file a bug on gitlab for it. Please do file a bug. It won't be fixed until after the upcoming 3.3.2 final release because we not making i18n changes between the candidate and final releases. Also, if you don't like my suggestion, feel free to suggest something else. -- 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: Upgrade to 3.3.2 fails

by Mark Sapiro

On 12/26/20 11:28 AM, Joel Lord wrote: > innodb_page_size of 16384 is the default, so that is what I'm working > with as well. The row size limit is half the page size minus some > overhead, so it comes out to 8126 and I bet that is yours as well. > > Yes, I am utf8mb4 at the database and table levels, and I bet you are > right. Just to confirm, between 3.2.1 and 3.2.2 the column archive_rendering_mode was added to the mailinglist table. This column is type - integer (4 bytes), but could be enough to push the row over the limit. As far as utf8mb4 vs. utf8 is concerned. There will be issues with the hyperkitty_email table subject and content columns in particular and maybe others if email messages contain 4-byte utf-8 unicodes. However, as I read the MySQL docs, for columns like VARCHAR(255) and VARCHAR(510), the difference affects only the number of characters that can be stored in the column and not the actual column width. I.e., a VARCHAR(255) column is actually up to 256 bytes wide (1 byte for length and up to 255 butes of data) and can thus hold up to 85 3-byte utf-8 encodings or up to 63 4-byte utf-8 encodings, but since any string normally contains only a few if any (probably none in the case of the mailinglist table) the actual limit is much closer to 85. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Archive search failing on one list

by Mark Sapiro

On 10/9/23 22:50, Mark wrote: > > I'm still on this problem of one list's archive-search not returning > any results. I created a new list today and it also has the same > problem. > > In short, the older lists all seem fine -- their search results are up- > to-date so that tells me the cron is okay. It's just these 2 newer > lists that have the problem. > > It's taken me while to get my head around the Django admin command you > have suggested, as I kept getting an error when starting: Steve has addressed your issues with multiple Django admin commands, some of which apparently don't reference the correct settings. > The format of my final line is different to yours ... > > Mine: <MailingList: <MailingList thepost(a)example.com>> > > Yours: <MailingList listname(a)domain.com (listname.domain.com)> > > Does this (missing list_id) give any clue as to why the archive-search > isn't working, or is just that starting with "# python3 manage.py > shell" is the wrong thing to do? It is not a clue as to the problem. The format of that `representation` changed in HyperKitty 1.3.5. What is your version? What happens if you do, with the appropriate Django admin and list name, ``` python3 manage.py update_index_one_list thepost(a)example.com ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Pre-approved howto

by Mark Sapiro

On 7/5/18 6:14 AM, thor.rustad(a)gmail.com wrote: > I have tried to understand the concept of pre-approved messages, but I'm spending way too much trying to figure it out. Help! There is a list attribute, moderator_password, which is not currently exposed in Postorius and therefore must be set via 'mailman shell'. Here's a sample session. > $ mailman shell -l junk(a)msapiro.net > Welcome to the GNU Mailman shell > The variable 'm' is the junk(a)msapiro.net mailing list >>>> m.moderator_password >>>> from mailman.config import config >>>> m.moderator_password = config.password_context.encrypt('xxx123').encode('us-ascii') >>>> m.moderator_password > b'$6$rounds=656000$SKMqTlPybIZSBjYB$wCga5qALCv8oobp4cDql2iKEg8T6qIgk8XEKYbkk9QXENeFQDHZ1M4AtmqfureYQDB5g.Az.nZPrWAr9N9g1N0' >>>> commit() That will set the list's moderator_password to the encrypted value of 'xxx123'. Then, if a post to the list contains Approved: xxx123 either as a header in the message (recommended if possible) or as the first non-blank line in the first text/plain part of the message, the post will be 'pre-approved'. The header can actually be any of Approve:, Approved:, X-Approve: or X-Approved: and if it is not a header, but is found in the first text/plain part of the message, it will be removed from that part and a best effort will be made to remove it from other text/* body parts in case it is also in an alternative part. -- 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: Removing the footer from mails

by Mark Sapiro

On 10/21/2017 01:46 PM, Peter Mueller wrote: > Hi, > > mailman2 had the configuration variable "msg_footer" to edit/remove the > footer. How can I get rid of the footer in mailman3? The doc is at <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/decorate.…>, but it's a bit complex. First, the message footer template name is 'list:member:regular:footer' and the digest footer template name is 'list:member:digest:footer' and if you want the same template for both, the name 'list:member:generic:footer' will do. The easiest way to set these is to create a template for the desired language (probably 'en') or an empty file if you want no footer. Then, there is a 'var' directory in the Mailman installation which contains sub directories named 'archives', 'cache' 'data', 'etc', 'ext', 'lists', 'locks', 'logs', 'messages', 'queue' and 'templates'. You can put list specific templates in var/templates/lists/LIST.ID/en/, domain specific templates in var/templates/domains/DOMAIN/en/ and sitewide templates in var/templates/site/en/. For example if you put an empty file at var/templates/site/en/list:member:generic:footer and a non-empty file at var/templates/lists/list.example.com/en/list:member:regular:footer, all messages and digests will have no footer except for regular deliveries from the list.example.com list which will use it's template. list overrides domain overrides site overrides default. -- 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: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, > > Mailman settings page giving me below error. > > Server error > An error occurred while processing your request. > > Error logs: > > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306, in user_subscriptions > mm_user = MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in get_or_create_from_django > return self.get(address=user.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in get > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET /users/user(a)example.com (or whatever the user's address is). It appears that that user doesn't exist in core. -- 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: # comment allowed in a template file?

by Mark Sapiro

On 7/27/20 5:15 AM, skenny(a)scss.tcd.ie wrote: > > The effect of the template files not being readable by user "mailman" was interesting. Hundreds of lines like the following got written to mailman-core's var/log/smtp.log file at the rate of 4 per second: > > Jul 23 17:09:54 2020 (25) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fdf9e7b5f28> > > (the hex number was different each time). That's a `debug` level log message written for every delivery. It has nothing to do with the unreadable templates except that the unreadable template causes looping in an attempt to send the message. Did you perhaps set [logging.smtp] level: debug in an effort to diagnose the template issue? > Having excessively restrictive permissions on the template files is a silly - but easy enough - mistake to make. If it were possible to add it to Mailman 3, a more descriptive logging message could point others who make it in the right direction, perhaps. I spent a long time trying to figure out why messages weren't getting sent out from Mailman core, and in the end it was luck in form of a colleague's suggestion about file permissions that got me out of the rut. There is clearly a bug in that an unreadable template should just be skipped and the fact logged. I have reported <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

5 years

[MM3-users] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/30/21 6:23 AM, Lucia Moreno wrote: > Hi Mark, > > We are facing the same issue. My postgres database is growing too fast and > I would need to do some creaning of old archives dated from 2001 and keep > only the last, lets say... 5 years. > > Could you please help us with the development of such a script? I have no > experience in python. The attached script is a rough idea. It assumes your Mailman is installed in a virtualenv at /opt/mailman/mm/venv and the django settings module is /opt/mailman/mm/settings.py. The pruned messages will be in a mbox at /opt/mailman/pruned.mbox. The age of messages to prune is defined by the days=365*5 argument in CUTOFF = datetime.datetime.today() - datetime.timedelta(days=365*5) All these things may need adjustment for your purpose. There is also a commented bit showing how you could do just one list. It's probably good to do just one list at a time since it's not clear how useful the pruned.mbox will be if it contains messages from multiple lists. I.e., run it for one list and move the pruned.mbox aside before doing the next list. Note that I've tested that this works, but it's possible that it will leave HyperKitty in a bad state. Backup your database before running this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Archive download - unexpected end of file

by Mark Sapiro

On 3/1/25 13:58, Mark wrote: > > I have a MM3 list to whose archive I recently added an mbox file of > older emails. > > Viewing/searching the archive (Hyperkitty) is working fine. > > Downloading archives "for the month" or "last 30 days" delivers the > expected ".mbox.gz" file and those are fine. > > However, when I download the "Entire archive" and attempt to gunzip that > ".mbox.gz" file I get the error: " ... unexpected end of file". The process creating the zip for download times out. You can increase the timeout. If your wsgi server is Gunicorn, see https://docs.gunicorn.org/en/stable/settings.html#timeout - for uwsgi see https://uwsgi-docs-additions.readthedocs.io/en/latest/Options.html#harakiri However, it's probably easier to get it in pieces. You can prpbably get chunks bigger than a month. Look at the URL for a month, e.g. for Jun, 2005 it will be something like https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2025-02.mbox.gz?start=2025-01-01&end=2025-02-01 The <fqdn-listname>-2025-02.mbox.gz can be any arbitrary file name. The start and end parameters determine what's included. E.g. for all of 2024 https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2024.mbox.gz?start=2024-01-01&end=2025-01-01 Note that the end date is the first date not included, i.e. the day after the last date included. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: Questions regarding message acceptance

by Mark Sapiro

On 7/28/20 6:35 AM, Pawel Grzywaczewski wrote: > Hello, > > I have few questions regarding usage of Mailman3: > > 1) We have list1 and list2 with members. Can we specify that all members of list1 can post messages to list2? This is a Mailman 2.1 feature that does not currently exist in Mailman 3. > 2) In explanation of “Accept these non-members” it’s written: “While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing”. > > I noticed that if someone posts to a list then he is added automatically to non-members. Which means that next time he will be able to post. > My understanding is that it’s better to use the feature “Accept these non-members”. Am I correct? You are mistaken. When a non-member attempts to post to a list she is automatically added to non-members with a moderation action of list default, which means that this and subsequent posts will be handled according to the list's "Default action to take when a non-member posts to the list" If you want to accept a non-member's posts you need to set that non-member's moderation action to "Default Processing" to still apply other tests that might hold the message or to "Accept" if you want to accept anything from that non-member. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 9/30/24 14:44, jkoral(a)luc.edu wrote: > That makes sense. Are there instructions on how to do this? It depends on the MTA. For Postfix you probably have a set of aliases for each of the form: mailman: "|/path/to/mail/mailman post mailman" mailman-admin: "|/path/to/mail/mailman admin mailman" mailman-bounces: "|/path/to/mail/mailman bounces mailman" mailman-confirm: "|/path/to/mail/mailman confirm mailman" mailman-join: "|/path/to/mail/mailman join mailman" mailman-leave: "|/path/to/mail/mailman leave mailman" mailman-owner: "|/path/to/mail/mailman owner mailman" mailman-request: "|/path/to/mail/mailman request mailman" mailman-subscribe: "|/path/to/mail/mailman subscribe mailman" mailman-unsubscribe: "|/path/to/mail/mailman unsubscribe mailman" You could change these, preferably in a separate aliases file so Mailman's genaliases won't overwrite them, to mailman: mailman@new_server mailman-admin: mailman-admin@new-server mailman-bounces: mailman-bounces@new-server mailman-confirm: mailman-confirm@new-server mailman-join: mailman-join@new-server mailman-leave: mailman-leave@new-server mailman-owner: mailman-owner@new-server mailman-request: mailman-request@new-server mailman-subscribe: mailman-subscribe@new-server mailman-unsubscribe: mailman-unsubscribe@new-server For exim, you would need to add another Mailman router ahead of the existing one which would match only the migrated lists and specify an smtp transport which relays to the new server. > Then once we are done migrating to the new server, then we can just change the DNS, correct? Yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users] Re: How to process emails with Mailman3?

by Kyle Lahnakoski

Thank you for this answer. In both the inject case and the netcat case I must know the recipient. My complex setup looses that metadata; leaving me with only the message. I guess I will be parsing the message to find that recipient. Thanks again On 2025-03-09 10:50 p.m., Mark Sapiro wrote: > Mark Sapiro wrote: >> The issue is you are not using nc correctly. >> When you do >> >> $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr >> >> you are telling nc to take commands from the file >> /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send >> the file. > Actually, what I said is not correct. The issue is you are just sending the data rather than engaging in an LMTP dialog. > > You need to send LMTP commands so you might prepend the message with > ``` > LHLO mymaillist.org > MAIL FROM: <sender(a)example.com> > RCPT TO: <all-request(a)mymaillist.org> > DATA > ``` > and append to the message > ``` > . > QUIT > ``` > > -- > 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 kyle(a)lahnakoski.com >

4 months, 3 weeks

[MM3-users] Re: Attack on Mailman Server?

by Mark Sapiro

On 3/9/23 11:34, Eggert Ehmke via Mailman-users wrote: > I had some attacks on my wordpress homepage today, I added some IPs to the > blacklist of my firewall. At the same time, I got several reports like this: > > Internal Server Error: /accounts/signup/ > > TemplateDoesNotExist at /accounts/signup/ > 429.html I suspect that's a coincidence. > Request Method: OPTIONS > Request URL: https://lists.eehmke.de/accounts/signup/ > Django Version: 3.2.16 > Python Executable: /opt/mailman/venv/bin/uwsgi > Python Version: 3.9.2 > Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/ > python3.9', '/usr/lib/python3.9/lib-dynload', '/opt/mailman/venv/lib/ > python3.9/site-packages'] > Server time: Thu, 09 Mar 2023 13:09:34 +0100 > > So it seems there were attempts to register new users but this caused this > internal error. Where can I send the complete error message? I would look in the web server logs to see what the actual accesses were. I'm guessing you'll find that some bot or script kiddies did a GET of /accounts/signup/429.html. You could also look for more detail in whatever log Django writes. This is defined in Django's settings as LOGGING['handlers']['file']['filename'] and is often Mailman's var/logs/mailmansuite.log. If you followed https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it is /opt/mailman/web/logs/mailmanweb.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

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

by Mark Sapiro

On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I'm NOT blaming any of the parts involved... Sure, most probably is my > fault. But the last upgrade shows that the process that fail is involved > with mailman upgrade. The last server was working smoothly and it has > higher traffic than the first I tried. It cannot be that I missed that > something was not working for weeks (since the last upgrade of the OS) It depends on what you did. Mailman's lmtp runner would only encounter this issue at startup, so unless you restarted Mailman or rebooted the server, lmtp runner would have continued without issue even if there was an underlying OS problem. Also, I don't think the problem is with Mailman per se. The underlying issue is in the Python library socket module. Try the following in a Python 3 shell ``` $ python3 Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() ``` This is essentially what aiosmtpd does and I expect that `sock = makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] Protocol not supported` exception. -- 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: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 20:53, Bryan Fields wrote: > mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; > ERROR: update or delete on table "hyperkitty_thread" violates foreign > key constraint > "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table > "hyperkitty_email" > DETAIL: Key (id)=(35670) is still referenced from table > "hyperkitty_email". > mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; > ERROR: update or delete on table "hyperkitty_email" violates foreign > key constraint > "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table > "hyperkitty_thread" > DETAIL: Key (id)=(150555) is still referenced from table > "hyperkitty_thread". Well, that's a catch 22, you can't delete the email because it's referenced by the thread and you can't delete the thread because it's referenced by the email. You could always update those entries to remove the references, but deleting and reimporting is probably better. > I'll attempt to clean this up tomorrow an clean it up/re-import. > > Is there a quick/easy way to drop the entire archive from the db or must I > delete the entire list? If you can get to https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/ as a Django staff user or superuser, there is a Delete Archive button to delete the entire archive. Even if you can't get there, you may be able to get to the confirmation page at https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/del… -- 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: exim4 + mailman3 lmtp failure

by Mark Sapiro

On 5/6/20 12:52 PM, Thomas Drillich wrote: > lines from exim4/mainlog > 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu > 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT > 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) It's not clear to me from the log what is happening. It all happens within a fraction of a second, so there don't seem to be any time outs involved. It seems the first two entries are the delivery of the message from th(a)drillich.com to exim for seebruecke(a)listen.td3.eu. I'm guessing here because I don't know that much about exim, but it looks like exim is trying to connect to listen.td3.eu rather than localhost to deliver the message and most likely, port 8024 is not open to the outside which is correct. 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. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/19/22 21:23, Stephen J. Turnbull wrote: > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > doesn't replicate that success. > > systemd doesn't know anything about venv. If it's possible to source > (not call as a command!) the venv bin/activate script via systemd, > that should fix it. If not, we'll have to figure out what it is that > the venv provides that the current systemd config does not. I would > guess that after sourcing the venv's bin/activate Our suggested systemd script at https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… has ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop /opt/mailman/venv/bin/mailman should work whether or not a venv is active. Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman is quite different from mine which is just ``` #!/opt/mailman/venv/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' __requires__ = 'mailman==3.3.5' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() ) ``` What is yours? and can you start mailman as the mailman user with ``` /opt/mailman/venv/bin/mailman start ``` without activating the venv? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: How to remove a message with an invalid Message-Id?

by Mark Sapiro

On 6/14/23 15:12, McGuire, Tommy M. (MSFC-IS61)[EAST2] via Mailman-users wrote: > I have a fun problem: apparently a message sent to a mailing list has an invalid Message-Id (I think), which is causing the message parse to fail while attempting to archive the message. Unfortunately, the message seems to be trapped somewhere and resulting in error logging every few minutes. Is there any way to find and remove the message? > > Literally, the only thing I've been able to find out about it is that the Message-Id contains the text "[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>". This is https://gitlab.com/mailman/mailman/-/issues/1065 which is fixed for the next release by https://gitlab.com/mailman/mailman/-/merge_requests/1099 You will find the message queued at Mailman's var/archives/hyperkitty/spool/ directory. You can examine the pickled message object with `mailman qfile` and you can simply remove the file. If you want to "fix" it and archive it, A `mailman shell` interaction like this will do it ``` >>> import pickle >>> with open('/path/to/.pck/file', 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Message-ID', '<83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com>') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` -- 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: Moving mm3 -> mm3 to different host

by Mark Sapiro

On 10/19/23 02:38, Axel Rau wrote: > Hi all, > > There are lots of threads for mm2 -> mm3 moves, but only one > thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining > the steps, but I can't find it again. > > I have created a working mm3 installation on the new host with both > mailman and mail-web dbs imported. > hyperkitty archive seems to in the db. > > What are the next steps to complete the transfer? > > - rsyncing messages, lists and templates to new host You may want to add archives/prototype to that. Also note that the contents of the messages/ directory should correspond to the entries in the message table in the mailman db. > - Setting up DNS CNAMES to the new server > - Adapting exim to accept mails to the aliased domain > > - Can I keep the old listname, with the old domain name? As long as mail to the list at that domain gets delivered to the new server. Note that in DNS if the domain has an MX record it must point to a domain with and A record and if there is no MX record, there must be an A record. CNAMEs won't do for mail delivery. > -What else has to be done ? I think that's it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: AttributeError: ,> 'ReopenableFileHandler' object has no attribute '_stream'

by Mark Sapiro

On 11/19/21 9:43 PM, David Newman wrote: > ((reposting with correct subject line -- sorry!)) Actually, the original Subject was probably closer to the problem. > Greetings. I am attempting a complete Mailman 3 installation on a Debian > 10 system that already runs Mailman 2, following this documentation: > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > Even following this guide, I'd had a lot of issues with permissions, > where directories and files were owned by list rather than mailman. > After correcting those issues, I then got to the point of checking > mailman3's status, and systemctl shows this error: > > Nov 19 20:09:57 [REDACTED] mailman[1463]: Error in atexit._run_exitfuncs: > Nov 19 20:09:57 [REDACTED] mailman[1463]: Traceback (most recent call > last): > Nov 19 20:09:57 [REDACTED] mailman[1463]: File > "/usr/lib/python3.7/logging/__init__.py", line 2038, in shutdown > Nov 19 20:09:57 [REDACTED] mailman[1463]: h.flush() > Nov 19 20:09:57 [REDACTED] mailman[1463]: File > "/opt/mailman/venv/lib/python3.7/site-packages/mailman/core/logging.py", > line 67, in flush > Nov 19 20:09:57 [REDACTED] mailman[1463]: if self._stream: > Nov 19 20:09:57 [REDACTED] mailman[1463]: AttributeError: > 'ReopenableFileHandler' object has no attribute '_stream' These generally stem from permissions errors preventing opening the log file. > There is an October 2019 thread on this error [1] but I think it's in a > different context, where the OP already had mailman3 running, and was > trying to migrate Mailman 2 lists. > > Also, regarding those permissions issues above, it matters which > "layout" value is in /etc/mailman3/mailman.cfg. I'd tried "dev" because > I saw a post from Mark Sapiro recommending that, I don't know in what context I recommended that. In my installs I use `layout: here` and in [paths.here] I specify an absolute path for var_dir. > but then mailman3 > wanted me to create a bunch of directories under /etc, even though > $var_dir was set to /var/lib/mailman3. Things seem to go better, except > for the confusion between lists/mailman ownership, when I set layout to > "debian", which was the default. It seems you may be using the Debian packages as our source has no `debian` layout. I.e., if you are installing with pip in a virtualenv, there would be no `debian` layout. If you are using Debian packages the Mailman user is `list` not `mailman`. > Thanks in advance for clues on addressing the ReopenableFileHandler > error above. Fix the underlying permissions error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: "Approved:" header from mailman2 times

by Mark Sapiro

On 04/09/2018 03:59 PM, Abhilash Raj wrote: > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: >> Hi, >> >> is there any equivalent to "Approved" header that was present in MM2 in >> MM3 land? Google is not very helpful in that. > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. I don't think it is broken, but it requires setting the moderator_password attribute for the list which can be set visa REST but I think not by mailmanclient. > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > Agreed. This is a shared password. and would be sent in plain text as a header or body line. It would be nice though to have some feature to enable, for example, spoof proof posting to a one-way (announce only) list. One thought on how to do this would be to have a list attribute that says posts from 'authenticated' owners and moderators can be auto approved and authentication could be by PGP signing the post. This would require Mailman to have the ability to verify a PGP signature from an owner or moderator which is not currently the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

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

by Mark Sapiro

On 5/22/23 12:42, ceo(a)sartrack.nz wrote: > I found the problem with Exim4. > The Exim4 config file should contain this: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > and NOT > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > Somewhere the documentation is wrong. The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} Where did you see MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > But I now have the next problem: > I send an email to a new mailing list called templist(a)sartrack.nz (I imported my old list members). > in /var/log/mailman3 I get an error regarding this; > The (final) error states: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/lists/templist.sartrack.nz/digest.mmdf' > > The file digest.mmdf does not exist there at all. Because Mailman was trying to create it and couldn't. I suspect you ran `mailman create` as root and the /var/lib/mailman3/lists/templist.sartrack.nz/ got created with user:group as root:root rather than the mailman user and group. Recent Mailman versions won't run the `mailman` command as root without a --run-as-root option for this reason. How are you installing Mailman? > The mailing server does not send out any emails for "templist" This is a separate issue from the above error, but it might also be a permissions error. What other errors do you see in /var/log/mailman3/mailman.log? -- 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: Installing mailman 3

by Mark Sapiro

On 07/23/2017 08:16 AM, Rafael Mora wrote: > This is the content of my /var/log: > > > [root@localhost log]# pwd > /var/log > [root@localhost log]# ls > anaconda grubby messages-20170716 spooler-20170710 > audit grubby_prune_debug messages-20170723 spooler-20170716 > boot.log httpd mysqld.log spooler-20170723 > btmp lastlog php-fpm tallylog > btmp-20170701 letsencrypt ppp tuned > chrony maillog rhsm wtmp > cron maillog-20170702 samba xferlog > cron-20170702 maillog-20170710 secure xferlog-20170702 > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > cron-20170723 mailman secure-20170716 xferlog-20170723 > dmesg messages secure-20170723 yum.log > dmesg.old messages-20170702 spooler > firewalld messages-20170710 spooler-20170702 Your current postfix log is /var/log/maillog. The files like /var/log/maillog-20170702, etc are older versions rotated by logrotate. On 07/23/2017 08:14 AM, Rafael Mora wrote: > content of the file maillog-20170723 (I didn't find mail.log in /var/log): > > [root@localhost log]# cat maillog-20170723 You want to be looking at /var/log/maillog for current messages. ... > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Is this where these files are? You should have at least postfix_domains, postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the /var/lib/mailman/var/data/ directory. It this the case? > output command 'postconf -n': > ... > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp This is missing a / transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: configuring moderators per list

by Mark Sapiro

On 11/06/2017 02:33 PM, Dmitry Makovey wrote: > We're trying to configure moderator per list and so far we were only > able to add "superuser" accounts that can handle "Held messages", > "Members", "Banned addresses" etc. You can add ordinary users as Moderator or Owner of a list. I'm not sure what is and isn't currently working, but Moderators and Owners get notices of things like held messages and subscriptions and can approve or deny them. I think only Owners, not Moderators, should be able to change various list settings. Have you tried these things? Is it not working? > Is there a way to create special account per-list to manage some of the > aspects of particular ML without giving them all the permissions that > Superuser comes along with? An Owner of one list should not be able to do things to other lists. If you're looking for more granularity in permissions on a single list, Owners can do anything, and Moderators should only be able to deal with held requests, but there's no granularity beyond that. > In MM2 there was a ML password that moderator/list admin would use to > login to perform operations. > > Current setup allows list admins to add/delete existing lists which is > not desired. This was a site option in MM 2.1. I'm not sure about MM 3 -- 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: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:33 PM, Andrew Bernard wrote: > Hi Mark, > > Thanks for your great help. But despite decades of UNIX experience, my area > is not Django (yet). The nub of my question is that I thought you have to > have a manage.py file for Django to be able to set up the various affairs, > such as making the database migrations and so on. It is that that is > eluding me. Apologies for this hopelessly newbie question. The equivalent of manage.py in what I suggested is /opt/mailman/bin/django-admin. > I was impressed with your method of installation in the page referenced, > and I have foolwed that closely. But I am puzzled about the build script. > If I run as user mailman, not root, it wanted to install under /usr. which > of course results in permission denied. I had to modify the script to say > this: > > python setup.py install --prefix /opt/mailman/mm/venv If you want to install in the virtualenv, you should just activate the virtualenv and it should work. Perhaps the issue is that the build script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> assumes the virtualenv is at /opt/mailman/mm/venv. You need to insure that the '. ../mm/venv/bin/activate' line is actually pointing to your 'venv/bin/activate' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Bounce processing

by Mark Sapiro

On 4/23/20 2:27 PM, Andrew Hodgson wrote: > > When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. The message the user is sent in built from the list:user:notice:warning template. The next release of Postorius will offer that template as one you can edit, but the current release doesn't. You can make an edited template in the var/templates/ directory. The logged-in user can go to her settings pages in Postorius at accounts/subscriptions/ to set delivery status. The generic template can't be that specific because Mailman Core doesn't even know if you have Postorius. > I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. The bounce recognition for Mailman 3 is essentially the same as Mailman 2.1. If you post one of these complete bounce messages, we'll investigate why it isn't recognized. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by Mark Sapiro

On 1/26/22 14:34, gordon(a)dickens.com wrote: > > However, mailman3-web (or mailman-web) is not working, I think because of a permissions issue. The installation instructions specify that mailman3-web (or mailman-web) run as user=mailman and group=mailman. However, the debian installation specifies the data files as user=www-data and group=www-data which is what apache runs as. For instance, I have my static files stored in the /var/lib/mailman3/web/static directory and the previous Debian mailman3 version set all the ownerships and groups to www-data for /var/lib/mailman3/web, /var/lib/mailman3/web/static along with all of the directories and files in the static subdirectory. So, > when I run "mailman-web collectstatic" it bombs on the following permissions error: > > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/web/static/hyperkitty/js/hyperkitty-common.js' > > So, my question is as follows. Should I continue to run mailman3-web as user mailman and change the ownership of the /var/lib/mailman3/web directory to mailman or should I leave the permissions of the /var/lib/mailman3/web directory alone and have mailman3-web run as user and group www-data? As David later said, owner and group of all Mailman's files and directories should be `mailman` and what ever the wsgi interface is (uwsgi, gunicorn, mod_wsgi) should run the wsgi process as user:group mailman:mailman -- 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: Removing all moderatortors (and owners) from a list in one go

by Mark Sapiro

On 8/12/24 04:07, Henrik Rasmussen wrote: > > Isn't there an easier way? And why not like https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… ? The next release of Mailman core will include a `mailman admins` command for adding and removing list owners and moderators. You could back port it simply by downloading and installing https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_a… The documentation is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… but I suspect this isn't what you want anyway because it does owners and moderators separately and you need to provide their email addresses. You could modify the script at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… to remove all owners and moderators from a list. E.g., ``` import os import sys from mailman.core import initialize from mailman.database.transaction import transaction from mailman.interfaces.listmanager import IListManager from zope.component import getUtility os.environ['MAILMAN_CONFIG_FILE'] = '/path/to/mailman.cfg' initialize.initialize() def delete_admins(list_id): mlist = getUtility(IListManager).get(list_id) if not mlist: print(f'No such list {list_id}', file = sys.stderr) sys.exit(1) with transaction(): for admin in mlist.administrators.members: admin.unsubscribe() if __name__ == '__main__': delete_admins(sys.argv[1]) ``` Running this with an argument of the list-id or list posting address will remove all owners and moderators from a list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

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

by Mark Sapiro

On 1/23/24 12:30, Thomas Schachtner via Mailman-users wrote: > > > Mark Sapiro wrote: >> >> Why do you think Mailman needs the contents of the postfix >> configuration file.. I don't think so. > I thought so, as mailman does not start if there's not > /etc/postfix/main.cf file is there. > > The following messages are logged: > Jan 23 21:20:35 mailman mailman3[491404]: RuntimeError: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not > permitted > Jan 23 21:20:35 mailman mailman3[491404]: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation > not permitted Mailman itself is not looking for Postfix main.cf, but when Pustfix is the MTA, it invokes the postmap command to create the .db files for postfix_lmtp and postfix_domains. Apparently postmap fails if there is not a Postfix main.cf. You can avoid this by using regexp tables instead of hash tables. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. >>> This seemed to work pretty fine, as all files and directories seemed >>> to be available, but when starting mailman 3, the following error >>> message was shown: >>> FileExistsError: A race condition might have happened. >>> /var/lib/mailman3 actually exists and is not a directory. >>> >>> Any idea why this message is shown? >> >> Possibly because the uid and gid of /var/lib/mailman3 on the postfix >> machine do not map to the appropriate Mailman uid and gid on the >> mailman machine. > You refer to the uid and gid of the "list" user? They are both 38 (uid > and gid) on both machines. > Then that isn't the reason. I don't know then why Mailman would complain that /var/lib/mailman3 actually exists and is not a directory. This message comes from mailman.utilities.filesystem.makedirs(). The code is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/file…>. makedirs() calls first_inexistent_directory() which checks if the directory exists with os.path.isdir() which apparently says it isn't a directory which makes no sense unless there is an actual race condition and you are creating the /var/lib/mailman3 directory on the mailman machine at the same time as you are starting mailman. BTW, you say you are doing sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 on the mailman machine. Presumably on the mailman machine /var/lib/mailman3 has lots of content. How does that 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, 6 months

[MM3-users] Re: Custom Archiver

by Mark Sapiro

On 4/1/23 09:39, pknowles(a)tpnsolutions.com wrote: > I'm playing around with installing Mailman Core, and want to have messages on a "per-list" basis sent to a special "archiver" address which I intend to make archives available at via a custom built "read-only" IMAP client. > > How would I go about having messages sent to this external address, short of adding the address as a subscriber? See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/archiving/prot… for an example of an archiver that implements Mailman's IArchiver interface. You could make something similar with an archive_message() method that sends the message to your IMAP server, or possibly you could just implement your IMAP client to serve messages from the existing var/archives/prototype/ hierarchy. Messages for lists with the prototype archiver enabled are stored there in maildir format by list name. To enable the prototype archiver, you may need to put [archiver.prototype] enable: yes in your mailman.cfg. To make your own archiver, create a python module, say my_archive.py, that defines a My_Archive class implementing the IArchiver interface. Put that module somewhere where mailman can import it and put something like [archiver.my_archiver] class: import.path.my_archive.My_Archive enable: yes where import.path.my_archive.My_Archive is the actual path that is imported. For example if Mailman is installed in a venv, you could put my_archiver.py in the venv's site-packages directory and then the class would be just class: my_archive.My_Archive -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Mark Sapiro

On 1/16/23 07:58, jaboyib556--- via Mailman-users wrote: > > However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? I have had some contact, but not much. As far as I know, they are still in business and offering list hosting including Mailman 3 lists with Affinity and Empathy. They no longer offer support for installation and maintenance of Mailman on other people's servers. When we first were developing Mailman 3, we designed it in a modular fashion with a REST API for the core engine so that users who were so inclined could develop their own web UIs for archiving and list management. We also recognized that we needed to develop our own to make a complete package. Thus, we developed HyperKitty and Postorius for that, but we have always hoped that the community would develop others (hopefully open source and Python based). As far as I know, it was only EMWD that did this and for business reasons, kept it proprietary. -- 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: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/27/21 1:36 PM, William Oliver wrote: > > When I send a message to the list from *any* of these three, the > mailman3 accepts it and attempts to broadcast it out. It is delivered > sucessfully to the local email address, but it looks like there's a > relaying problem with external addresses. > > In the syslog snippet below, note that the fp145(a)libertyfp.org mail is > delivered, but the mail to the recipients at billoblog.com get an > "Access denied" ...> > Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: NOQUEUE: reject: RCPT > from mail.libertyfp.org[2.56.57.28]: 554 5.7.1 <billo(a)billoblog.com>: > Recipient address rejected: Access denied; > from=<testlist-bounces+billo=billoblog.com(a)libertyfp.org> > to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> > > Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: disconnect from > mail.libertyfp.org[2.56.57.28] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 > quit=1 commands=7/8 It appears that the MX for billoblog.com is not accepting mail from your server. Can you send non-mailman mail from this server to this address? If not, you need to contact billoblog.com to fin wht they are blocking your mail. > I tried changing the smtp port in mailman.cfg to 587, but that didn't > change anything. because the issue is not in delivery from Mailman to Postfix. It is in delivery from Postfix to billoblog.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: CPU usage when idle

by Mark Sapiro

On 5/28/25 08:27, roughnecks via Mailman-users wrote: > > It's the manage.py qcluster whatever is called. I have shut down MM for > the time being, because I'm not fully motivated to have it running, so I > can't be more accurate right now. I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend. Settings that control this are typically ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` and possibly a setting like `'workers': 2,` (default is the CPU count of the system but see <https://django-q2.readthedocs.io/en/master/configure.html#f1>). ``` CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION': '127.0.0.1:11211', } } ``` although the default if not set is ``` CACHES = { "default": { "BACKEND": "django.core.cache.backends.locmem.LocMemCache", } } ``` It is the `'orm': 'default'` setting that says to use Django's CACHES. See <https://django-q2.readthedocs.io/en/master/brokers.html#django-orm>. You can get info about what qcluster is doing with `manage.py qinfo` and monitor things with `manage.py qmemory` and `manage.py qmonitor`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

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

by Mark Sapiro

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

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

by Mark Sapiro

On 11/8/21 8:28 PM, dancab(a)caltech.edu wrote: >> In either case, the bounce message (fake DSN) should have contained a >> message body like >> Mail to user(a)example.com failed at outgoing SMTP >> with the actual user's address. These fake DSNs are sent in the case >> where the outgoing MTA refuses a message from Mailman so there is no >> actual failure DSN. > > Thanks. I think I'm missing how I can configure Mailman so that the actual user's address is used. I think you are missing the point. This is a pseudo DSN. If it were a real DSN it would be something like From: mailer-daemon@somewhere To: listname-bounces@listdomain However, there is no real DSN because Mailman has gotten a reject in it's attempt to deliver to the outgoing MTA so it creates it's own pseudo DSN for the failure. Another way of looking at this is if you configured Mailman to deliver to a local MTA and configured that MTA to relay to your remote MTA, your local MTA would accept the message and then receive the 5xx status upon delivery to the Remote MTA and would then send an appropriate DSN back to the list-bounces address. Since you are skipping the local MTA part, Mailman gets the 5xx status upon delivery to the remote MTA and creates it's own DSN for itself. -- 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: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/5/25 13:00, megabrutal--- via Mailman-users wrote: > Hi Everyone, > > I've recently installed Mailman3 and still testing it. I tried to reply to a topic on my own list while also being a superuser from HyperKitty, but I got this error message: > > "This list is moderated, please subscribe to it before posting." Is your login a member of the list? > Then why I even see the archive of the private list? What might be wrong? You can see the private archive because you are logged in as a superuser. > One thing that might confuse the system is that I added a secondary e-mail to my account. I thought it would allow me to post from any of my addresses, but it seems like it's not the case, looks like I can only subscribe with one of the addresses. How did you add that email? When you find yourself at https://example.com/mailman3/users and click Manage, do you see the expected addresses? > It also looks like HyperKitty has trouble matching up the addresses, as it lists 4 participants for the conversation, while 2 of them is my account, the other 2 is my test address. In reality, it should list 2 posters. This is normal. Hyperkitty lists participants by address whether or not the addresses are linked to the same user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 06:24, Jens Günther wrote: > > I find those changes, but: in the merge request there is mentioned a > /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po > > -> but I don't find a mailman-de.po ... is it maybe that? That file was for a test only. The German message catalog is at mailman/messages/de/LC_MESSAGES/. That directory should contain a mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be created. The source distribution contains a generate_mo.sh script to generate these for all languages, but you can do the German one by changing to the mailman/messages/de/LC_MESSAGES/ directory in the running installation and doing msgfmt mailman.po -o mailman.mo >> Please be more specific than `all types of system mails`. Which >> specific message subjects are not translated. > > It's exactly as mentioned in issue 993 the welcome and goodbye-messages > that I don't see translated. > > But also other examples: > - bounce-mail for the user that moderator approval is necessary (there > the text is in german, but the reason is in english) > - approval-mail for moderator (also text is in german, but subject and > reason in english) I'll look into these. If you don't have the mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the reason, but there may be a bug. -- 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: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 2:27 PM, Ken Alker wrote: > --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> The 404s are addresses im HyperKitty's sender table for whih there is no >> corresponding Mailman user. There are multiple possible reasons for this. > > And that is OK, right? Sure. It only means that there are messages in the archive that are From: addresses that aren't currently Mailman users. >> If the behavior has stopped it's probably because the periodic Django >> jobs are not being run - this is bad. > > I see this in the logs from just after midnight: > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > Followed by a huge amount of HTML (strange). This is all from one post. The first is normal it just says that Mailman's var/public_suffix_list.dat doesn't exist, but it should be retrieved from https://publicsuffix.org/list/public_suffix_list.dat and then saved at var/public_suffix_list.dat so it doesn't need to be retrieved from the web again until the saved copy is older that the configured dmarc.cache_lifetime (default = 7 days, so that message) after which time the message will be 'Cached copy of public suffix list is out of date' The second is acceptance of the post. The third is a failure in archiving the message. Th HTML should contain an error message with a traceback which should help determine the problem. > Is there a way to kick it into re-running whatever it does at midnight > so I can test this again after putting the public suffix list back? I > assume I can just execute "mailman-web runjobs daily", but will this > mess things up, or is it OK to run it mid-day without stopping anything > first? Midnight is a coincidence in this case. the above are all due to the post with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> The cached var/public_suffix_list.dat should now be there with a timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) > Is the last (third) log line excerpt simply a result of the first, or do > I have something else messed up? The third is not because of the first. It is because of some issue with archiving that post. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/3/23 00:31, Onyeibo Oku wrote: > > (1) Mailman refuses to resolve to a preferred subdomain. If the > server's domain is "website.tld", I'd like mailman's homepage to be > at "list.website.tld". Mailman insists that I add "website.tld" to > the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an > ALLOWED HOST (same VPS/IP address nonetheless). The result is that > the homepage ends up at "https://website.tld/mailman3/lists" when the > desired url is "https://lists.website.tld/mailman3/lists". This is a > conflict because the main domain is intended for another service. How > do I approach this? This is all configured in your web server. It needs to proxy requests for lists.website.tld to gunicorn and depending on the web server, may need more. E.g. see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for nginx. > (2) See the traceback below: > ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server > Error: /mailman3/lists/ Traceback (most recent call last): ... > "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", > line 650, in get raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. > > It seems a migration is missing. How should I approach this? Set SITE_ID = 0 in your Django settings. Also see 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

2 years, 6 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/25/25 01:02, Alexander Inzinger-Zrock via Mailman-users wrote: >>>> 3.1 parameter for default lookup table type >>> 3.2 pointing to command ''postmap'' >>> Both entries must be present or Mailman will error out before creating >> the postfix_lmtp file. There should be a template (actually, you can >> probably use it "as is") in site-packages/mailman/mta/postfix.cfg (or >> maybe in config/postfix.cfg). >> This file can be located anywhere, but I recommend putting it where >> mailman.cfg is (usually /etc/mailman3), and pointing to it in the >> [mta] section of mailman.cfg with the full path. > > + this file seems to be missing in my setting > + also the postmap command seemed to be unavailable for the user ''mailman''. > + [X] placed file in same dir as mailman.cfg (/etc/mailman3/) > + [X] replaced old config and pointed to it in mailman.cfg with full path: > #+begin_src txt /etc/mailman3/mailman.cfg > #configuration: python:mailman.config.postfix > configuration: /etc/mailman3/postfix.cfg > #+end_src > command ''mailman conf'' will show the new configuration path for > [mta] but no results for search term 'postmap_command' nor 'transport_file_type'. What does `mailman info` show for config file:? What does `mailman conf -s mta` show for [mta] configuration: [mta] incoming: mailman.mta.postfix.LMTP What's in /etc/mailman3/postfix.cfg? -- 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: looking for more detailed traceback for shunted message

by Mark Sapiro

On 4/27/23 1:23 PM, bob B via Mailman-users wrote: > Had a message get shunted in > /opt/mailman/core/var/queue/shunt/. *** but that is the location in the docker environment, which we are running. > > The mailman log shows: > > Apr 26 13:09:56 2023 (31) ACCEPT: 2e0e82a5-0924-1777-bed8-34862417fe7e@[Redacted] > Apr 26 13:09:56 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:09:56 2023 (35) Traceback (most recent call last): > Apr 26 13:09:56 2023 (35) SHUNTING: 1682514596.7976818+6067e5ddeb70e4aad97977071b5ed00c41999057 > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:16 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:10:16 2023 (35) Traceback (most recent call last): > Apr 26 13:10:16 2023 (35) SHUNTING: 1682514616.5346222+7292ba8b651bc1bd76a9098733a39090e092add2 > > > > Is there anyway to get more info, Is there a more detailed traceback somewhere? I have never seen anything like this. There should be a complete Traceback in between the `Traceback (most recent call last):` line and the `SHUNTING: ...` line. However, I'm pretty sure the issue is a defective email which has non-ascii bytes in an explicit or implicit ascii part. You can see the raw message by pointing `mailman qfile` at the shunted .pck file(s) -- 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: Timeouts

by Mark Sapiro

On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: > The described timeouts are something that hyperkitty ought to be able to > avoid. For apache, the timeout is idle time between blocks of output. > Hyperkitty can avoid this by generating the archive in segments (based > on size, or elapsed time), flushing its output buffer, generating a > multi-file archive, and/or using Transfer-Encoding: chunked (chunked > doesn't work for http/2). It ought to be able to break the work into > blocks of "n" messages & do something to generate output. Besides > avoiding timeouts, working in segments allows the GUI to display > meaningful progress (e.g. if you're loading with XMLHttpRequest, > "onprogress") It really oughtn't be up to the user to break up the > request. It is not the web server that times out. I'm not sure about uwsgi because I don't use it, but the timeouts I see are on servers that use gunicorn as the WSGI interface to Django and the timeout is in a gunicorn worker. This is controlled by the timeout setting in the gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> Note that even 300 seconds is not enough to download the entire <https://mail.python.org/archives/list/python-dev@python.org/> archive. It may be possible to get HyperKitty to chunk the output to avoid this, but it doesn't currently do that. Care to submit an MR? -- 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: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Mark Sapiro

On 5/25/24 10:00 AM, schaefer(a)alphanet.ch wrote: > > How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database. As far as the comment/display name in From: is concerned, what specific emails are you talking about? I don't know where `example.com` would come from unless you mean email from Django in which case look at your setting for ADMINS in your Django settings. > Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. The `mailman import21` command will properly import the Mailman 2.1 from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. If you have some customization in this area, that probably won't be handled. -- 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: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg)

by Mark Sapiro

On 1/2/19 4:20 PM, kelly.close(a)lrewater.com wrote: > Happy New Year! > > What isn't working yet are the archives, specifically the messages sent to lists showing up at .../mailman3/hyperkitty. I'm at a loss and I'm hoping maybe the folks on this list can help me bring it home. > > Messages are distributed to subscribers as they should be - subscribers can send from their emails or from the web site. People can subscribe, etc. It's all working great. Just no archives. Presumably the list is known to HyperKitty since you appear to be able to post from there. > I'm not sure what to try next or what info to provide here for help - can anyone suggest where I can look to see why archives aren't getting created, or let me know what information would be essential for me to post to get help on this? I'm using PostgreSQL for the database, Postfix for mail and Apache2 for the web server. The first place to look is Mailman's mailman.log. Are there errors there with tracebacks? Are there messages there like <timestamp> 2018 (9606) HyperKitty archived message <message-ID> to <archive_URL> Also is there an Archived-At: header in received posts? If either or both of those, what happens if you go to the URLs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > Folks, > > For my own purposes I have created some patches which apply to the > current mailman pip package. I'm only responding here to the issue of how to suggest patches. If you hope that they could be incorporated into the distribution, posting them to this list is not very effective. It is too easy for list posts to get lost, buried or forgotten. The best thing to do is to create an issue or issues at <https://gitlab.com/mailman/mailman/-/issues> (each issue should address only one thing). Then you can either attach the suggested patch to the issue or better, create a merge request with the patch to fix the issue. Ideally, the merge request would also contain relevant additions to unit tests. The first advantage is open issues do not get lost. They are always there in the tracker. The second is that all of the above is work that needs to be done in order to actually get the patch into the master branch, and the more of it you do, the less of it needs to be done by someone else who may not be as motivated as you are. Granted, this may seem like a burden for you. After all, you fixed your problem so why bother, but open source works best if we all contribute what we can to improve the product. -- 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: Welcome message issue

by Mark Sapiro

On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of 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 months, 1 week

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 9:33 AM, "Jörg M. Schulz" wrote: > But, also in mailman log. > Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) > Jan 09 12:24:06 2019 (17491) 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/digest.py", line 324, in _dispose > mime = mime_digest.finish() > File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish > footer = MIMEText(footer_text.encode(self._charset), > so the footers may not contain special characters. > Will review this one. in the above, self._charset is the character set of the lists preferred_language. The footer can't contain characters not in the character set of the list's preferred_language. For English (en) this is us-ascii. For German (de) it is iso-8859-1. These are artifacts from Mailman 2.1 You can change this for English by putting [language.en] charset: utf-8 in your mailman.cfg. This works because us-ascii is a proper subset of utf-8. For other languages, a change like this might require recoding of templates and/or a message catalog, but since we don't currently ship any non-English templates or message catalogs, that is moot at the moment. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Unable to configure mailman . Please give any information

by Mark Sapiro

On 3/13/19 11:47 PM, pradeep Kumar xplorer wrote: > Subject: [Fwd: Please list the variables i need to modify in the configure.in] > From: "Pradeep Kumar Xplorer" pradeepkumarxplorer(a)pradeepkumarxplorer.com > Date: Mon, March 11, 2019 4:04 am > To: mailman-users(a)mailman3.org > Priority: High > Read Receipt: Requested [ Send Read Receipt Now ] > Options: View Full Header | Print | Download this as a file > ---------------------------- Original Message ---------------------------- > Subject: Please list the variables i need to modify in the configure.in > From: "Pradeep Kumar Xplorer" > pradeepkumarxplorer(a)pradeepkumarxplorer.com > Date: Thu, March 7, 2019 6:36 am > To: mailman-users(a)python.org It appears you originally posted this to mailman-users(a)python.org where it would have been rejected as a post from a non-subscriber. That was probably the correct place for this as is it a Mailman 2.1 question and this list is for Mailman 3. > before running the configure script > I changed > AC_PREFIX_DEFAULT(/home1/explodi4/public_html/MAILMAN) > and it still says /home/mailman does not exist. > > Pradeep Kumar Xplorer > http://www.dhyanayoga.info > http://www.pradeepkumarxplorer.com/2016/CyberCrime/index.php You should not need to touch either configure.in or configure. Start with an unmodified configure and run `./configure --help` to see the options. It appears you may be running configure with '--prefix=/home/mailman' and that directory doesn't exist. See <https://www.list.org/mailman-install/node3.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Ann: Mailman Core 3.3.5 is out

by Mark Sapiro

On 9/29/21 9:59 AM, Brett Delmage via Mailman-users wrote: > On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > >> Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I >> would have >> to bypass the Debian installer. Or will there be Debian packages >> available? >> Same question for Postorius 1.3.6 Since Mailman 3.3.4 has been out for over six months and the latest Mailman 3 in even Debian sid is still 3.3.3, I would expect a long wait before these latest releases are available in Debian/Ubuntu. > I am excited to see 3.3.5 with its many updates available. Thanks to all > the contributors. > > I would like to know this too, as I was just about to install parallel > to the Debian package(s). I expect there are many of us. > > Going forward, what is the best way to maintain a stable version of > 3.3.5 with security and defect fixes only, exluding new features? Is > picking and applying individual checkins on gitlab the only way? I would suggest abandoning the Debian packages and installing as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. You should be able to keep all your existing configuration files and the database. You could even keep `list` as the Mailman user if desired. Once you have done this, upgrading via pip from PyPI or even from GitLab is very simple. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

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

by Mark Sapiro

On 12/22/21 9:22 PM, David Newman wrote: > > On my system that file lives here: > > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py It appears that you have installed following https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… and in that case, this is the file. > But the error persists after this addition and restarting MM3 and > mailmanweb and nginx: > > url(r'^mailman/', include('postorius.urls')), > > There is this 404 error in uwsgi.log: > > [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed > Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 > bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on > core 0) However, that's not the issue. You originally reported and I didn't look closely enough: > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. That URL is from a Mailman 2.1 installation. Are you still running Mailman 2.1? If so, you need to support Mailman 2.1's CGIs. In Apache, this would be something like ScriptAlias /mailman/ /parh/to/mailman/cgi-bin/ but nginx doesn't do that. You would need something like location /mailman/ { proxy_pass <something that can serve Mailman 2.1's CGIs.> } The something could be apache or ?? -- 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: Messages Showing Up as "Forwarded"

by Mark Sapiro

On 7/21/22 14:08, Mail Person wrote: > Sorry if this is an easy question, but I've got mailman3 up and running and all my test messages show up with forwarding language around them rather than just the message, see below: > > ---------- Forwarded message ---------- > From: Person <person(a)gmail.com> > To: all(a)domain.com > Cc: > Bcc: > Date: Thu, 21 Jul 2022 13:56:22 -0700 > Subject: Hello Members > This is a wonderful test > > > > ---------- Forwarded message ---------- > From: Person <person(a)gmail.com> > To: all(a)domain.com > Cc: > Bcc: > Date: Thu, 21 Jul 2022 13:56:22 -0700 > Subject: Hello Members > _______________________________________________ > Mailing list footer Are you looking at a MIME format digest or individual messages? If you are looking at a MIME format digest, this is expected depending on your mail program. You might prefer Plain Text Digests. If you are looking at individual messages, you probably have in your list's Settings -> DMARC Mitigations, DMARC mitigation action = "Wrap the message in an outer message From: the list" and DMARC Mitigate unconditionally = Yes. If you set DMARC mitigation action = "Replace From: with list address", the From: will be replaced, but the message won't be an attachment, and if you set DMARC Mitigate unconditionally = No, the selected action will be applied only to messages whose From: domain publishes a DMARC policy of reject or quarantine. -- 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: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/22/23 09:32, Stephen J. Turnbull wrote: > > To diagnose, we really need to see that in context of the raw message > as received by the user. It was posted. The issue is the message declares Content-Transfer-Encoding: base64 but the body is not base64 encoded so the MUA tries to base64 decode it and even though that's invalid, produces the garbled output. > The only other thing I can think of is it might have something to do > with your internationalization settings. What is the default language > of the list? (This is available in Postorius.) Have you changed the > default encoding for English on your site? (I think you need to look > in mailman.cfg for this.) What is the default language of the site? I note that the message also declares Content-Type: text/plain; charset="utf-8" and Python's email package will base64 encode utf-8 message bodies. I also note that the messages Subject: is RFC 2047 encoded as utf-8. These tell me that the user's preferred_language if set or the list's preferred_language is not English or the charset for English is changed to utf-8. I tried to duplicate this in a test installation with the charset for English set to utf-8, but I get a similar response but with Subject: =?utf-8?q?The_results_of_your_email_commands?= and Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -- 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: postfix virtual domain and mailman 3

by Mark Sapiro

On 12/25/19 1:53 PM, work(a)andrefincato.info wrote: > > question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. > > is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so > > ``` > virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap > ``` I think the above should work for you. As far as `dump_json` is not an available module goes, the docs reference a lot of helper functions that are described at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/docs/documentati…>. These need to be imported. I.e., for dump_json ``` from mailman.testing.documentation import dump_json ``` But, if you are just trying to set an alias_domain for the domain and you have Postorius, you can do that via Postorius. If not Postorius you can use `mailman shell`, For example ``` $ mailman shell Welcome to the GNU Mailman shell >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = 'x.example.com' >>> ``` Then you need to do `mailman aliases` to create/update the maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

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

by Mark Sapiro

On 3/16/21 11:34 AM, Per Jessen wrote: > > I'm trying with this: > > find /var/spool/mailman/bad -type f -name \*pck |\ > while read m > do > (mailman qfile $m | grep -q ad.dr@ess) && echo $m > done > > Is there a better way? Yes, as you've noticed there is a significant startup cost every time you invoke the `mailman` command. to invoke it only once first see ``` mailman shell --details ``` (that refers to `mailman withlist` which is just another way to spell `mailman shell`). You will want to create a script similar to the following: import pickle from os import listdir def findaddr(address): for fname in listdir('/var/spool/mailman/bad'): if not fname.endswith('.pck'): continue with open(fname, 'rb') as fp: msg = pickle.load(fp) if address in msg.as_string(): print(fname) That's your script. Save it as findaddr.py where `mailman shell` can import it and run ``` mailman shell -r findaddr.py -- ad.dr@ess ``` This should print the names of any pickles that contain 'ad.dr@ess' Note however that this may not be necessary. If all you want is the names of the .pck files that mention 'ad.dr@ess', ``` grep ad.dr@ess /var/spool/mailman/bad/*.pck ``` should actually work reporting things like Binary file /var/spool/mailman/bad/*.pck matches with the actual file name, not *. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

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

by Mark Sapiro

On 5/12/16 3:46 PM, deu8yz2mpq(a)snkmail.com wrote: > My quibble is that the multipart/digest encapsulation level is > gone. > > Barry Warsaw wrote at 15:16 -0400 on May 12, 2016: > > The MIME format of MIME digests should roughly be: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > But mm 2 had: > > multipart/mixed > text/plain (the digest heading) > text/plain (the TOC) > multipart/digest <--- this is the part that's gone in mm3 > message/rfc822 > message-1 > message/rfc822 > message-2 > ... > text/plain (footer) > > So was that removal intentional, a bug or ?? I'm sorry. I missed the point of your OP. I think it's a bug. The doctest at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, the part just after "The MIME digest has lots of good stuff, all contained in the multipart." is clearly missing the multipart/digest part. It appears that this got lost in the refactoring of the MM2 code for MM3. Please file an issue at <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me (msapiro), but it any case, I'll work on fixing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 9:57 PM, Paul Arenson wrote: > Success. I first tried to send a sample here but it was over 40k so it is being held for moderation. Then I realized my own list is set to hold all messages now, including my own, so I sent it and I got a message telling me it was held for moderation. I could see the message and it looked perfect (have to look in mail client, not hyperkitty). > > Sent it out and it looks fine on both my computer and on my iPhone. > > > Hyperkitty archive is without the html view but it looks ok and the images show up as attachments. I have now accepted your held message. This list's content filtering collapses alternatives so what you see from the list and in HyperKitty is the plain text alternative that your MUA (Mac mail) created, but all the URLs seem to work as links even though displayed as truncated in the Hyperkitty view. Also this list will filter out images. HyperKitty will only display plain text parts in the message and thread views. Other parts such as html and images that pass the list's content filtering will appear as attachment links in HyperKitty. Anyway, it appears your issue is resolved by setting Filter content and Collapse alternatives to No. I'm glad it's working for you. -- 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: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/11/22 13:32, gordon(a)dickens.com wrote: > Hi Mark, > > I think that I found a hint as to the cause of my problems. > > I changed the apache2 LogLevel to debug and the following was then generated in /var/log/apache2/ssl_error_log: > > [Fri Feb 11 15:40:18.325675 2022] [core:debug] [pid 3982011] core.c(5280): (95)Operation not supported: [remote /var/lib/mailman3/web/static/uwsgi.sock:12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY) > > Apparently, there appears to be a problem with uwsgi.sock. > > My uwsgi.ini file has the following: > > uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock > > Also, my apache.conf for mailman3 has the followig: > > ProxyPass /mailman3 unix:/var/lib/mailman3/web/static/uwsgi.sock|uwsgi://localhost > > So do you see a problem in my configuration files that would cause the Operation Not Supported error with the uwsgi.sock file. I don't use uWSGI and have no experience with it at all, however here are some things to consider: For Apache to support uwsgi protocol you may need ``` a2enmod mod_proxy_uwsgi ``` However, I would suggest you use http rather than a unix socket. In your uwsgi.ini file instead of ``` uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock ``` which requires Apache support for uwsgi protocol, put ``` http-socket = 0.0.0.0:8000 ``` which will tell uwsgi to listen on TCP port 8000 and in Apache, use ``` ProxyPass /mailman3 http://127.0.0.1:8000 ``` -- 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: Changing default message limit (max_message_size)

by Mark Sapiro

On 5/24/19 7:05 AM, roger(a)reasonal.com wrote: > > $ bin/mailman shell -l list(a)example.com // Welcome to the GNU Mailman shell // The variable 'm' is the list(a)example.com // mailing list m.max_message_size = nn // commit() > > Unfortunately this does not work in the containerised mailman. > > So I get the container ID and run: > docker exec 3373d426996d /usr/local/bin/mailman shell -i test-list(a)iotcouncil.org.za > > (in the post by Mark it says "-l" but I get "unrecognized argument" -- I assume it should be -i for "interactive"? It should be -l or --listspec followed by the list posting address or list ID. I can't explain why you get "unrecognized argument". > Either way, it fires up the mailman shell and then throws me straight out back to the command line: > > Welcome to the GNU Mailman shell > The variable 'm' is the test-list(a)iotcouncil.org.za mailing list > >>> > [root@listman ~]# The above indicates there was a recognized '-l test-list(a)iotcouncil.org.za' argument because it knew to instantiate the list and assign it to 'm'. > So that doesn't help... I really can't help with Docker, but there is some issue that causes the command to exit as soon as it asks for input. It is waiting for interactive input and gets an end of file. Maybe @maxking can help with this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: mailman2 import not working

by Mark Sapiro

On 7/29/20 10:16 AM, Abhijith PA via Mailman-users wrote: > > When I restarted mailman. I got, > > Jul 29 16:58:21 2020 (14473) SHUNTING: > 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d > >> I think Mailman's var/ directory in the Debian package is >> /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? >> Is there a .pck file either in shunt/ or in out/? > > There is many .pck files in /var/lib/mailman3/queue/shunt and > /var/lib/mailman3/queue/out. And a lot of .psv files in > /var/lib/mailman3/queue/bad The .pck and (presumably one) .bak files in queue/out are messages waiting to be processed by out runner, the .bak is the one currently being processed. It appears your out queue is backlogged, but that is a separate issue and may just be transient. For every message in queue/shunt there should be a SHUNTING message and also an exception with Traceback logged in mailman.log. It is these Tracebacks we need to see to know what the issue might be. (If they're all the same exception, we only need one.) The .psv files in queue/bad are unparseable messages. There should be a "Skipping and preserving unparseable message:" entry in mailman.log for each of these. The messages can be seen with `mailman qfile` pointing to the .psv file. If they look like legitimate messages, it is possible a permissions issue that caused them to be unparseable. -- 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: new list not working

by Mark Sapiro

On 3/9/23 13:26, Christian via Mailman-users wrote: > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client() > What else is in the smtp.log? There should be messages like <timestamp> (<pid>) <message-id> smtp to redlatinleg(a)lists.ccalternatives.org for nn recips, completed in n.nnn seconds <timestamp> (<pid>) <message-id> post to redlatinleg(a)lists.ccalternatives.org from christian(a)naturalintelligence.us nnn bytes If there aren't, try setting [logging.smtp] level: debug in mailman.cfg, restarting Mailman core and see what you then get in smtp.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: How to fix lists with characters errors?

by Mark Sapiro

On 3/23/24 11:56, Helio Loureiro wrote: > Hi, > it is python 3.10. Problem is... some mailing lists were created long ago, > with python2 something. Most probably 2.5. And the tables on mysql were > set to latin1. This has nothing to do with the data or the charsets/collation in the database. The issue is the locale setting in your python is causing stdout output from the `mailman members` command to be encoded as `latin1` and at least some user's display name contains a `\u0142` (i.e. `ł` character. > That I know. Question now is how to fix this. Any suggestion? What is > the table? I probably can run some script for these specific lists that > have the failure, import data as latim-1, and update back to the table as > utf-8. That's not the issue. The issue is the Python in your venv has sys.stdout.encoding set to latin1, probably for locale reasons. You ca apply this patch ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -17,6 +17,7 @@ """The 'members' subcommand.""" +import sys import click from mailman.core.i18n import _ @@ -30,6 +31,9 @@ from zope.component import getUtility from zope.interface import implementer +sys.stdout.reconfigure(encoding='utf-8') + + def display_members(ctx, mlist, role, regular, digest, nomail, outfp, email_only, count_only): # Which type of digest recipients should we display? ``` to mailman/commands/cli_members.py to fix the 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, 4 months

[MM3-users] Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/22/23 03:42, thomas--- via Mailman-users wrote: > Hello, > very new to mailman3, I used to manage mailman2 on a Debian 10 server. > The server has been upgraded to Debian 11 and mailman2 disappear… > > I try fresh install of mailman3, prerequisite to data migration, but without success. > If some can help, I would be really greatful. > > <VirtualHost *:80> > ServerName newsletter.mydomain.tld > > Alias /static /var/lib/mailman3/web/static > Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > > DocumentRoot /var/lib/mailman3/web/static > <Directory "/var/lib/mailman3/web/static"> > Require all granted You can probably fix the below error by adding options +Indexes here, but see below. > And now I have a 404 answer when consulting my http page. > > When trying to access `/static` sub-path, I get `Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found`. It is unclear to me what is doing a GET of /static/admin/ and why. GETs should by of actual files, e.g., things like /static/admin/css/base.css > I am a bit lost with that. So are we. Questions about the Debian package are better asked of Debian. See https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… We can provide much better help and support if you install via the resources mentioned in the 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

2 years, 4 months

[MM3-users] Re: Rejecting held emails

by Mark Sapiro

On 04/26/2018 08:43 AM, Darren Smith wrote: > > We recently had a phishing message make it through our spam filters and > arrive at a mailing list. The good news is that since it was not from a > list member it was in the held message queue. > > I was able to find the message in the var/messages directory by searching > for a keyword in the subject. However, after rejecting the message from > Postorius, the message doesn't seem to be removed from the var/messages > directory. Do you mean Reject and not Discard? Phishing/Spam should never be "rejected" for backscatter reasons. Reject should only be used for somehow inappropriate posts from known people. > Is this expected behavior? I know that infosec people won't be too happy > about a phishing email sitting around on our disk. (Infosec guys are > notoriously paranoid. :) ) > > Is there some sort of cleanup process that would remove these messages? If > not, does this pose an issue where over time disk usage will creep up? This > could be a pretty significant problem if that is the case. It's not the behavior I would "expect", but it is the way it currently works, and yes, all your concerns are valid. This is <https://gitlab.com/mailman/mailman/issues/257> which I just edited to note that in addition to not removing the pending db entry, the message isn't removed either. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

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

by Mark Sapiro

On 10/14/19 7:03 PM, Paul Arenson wrote: > > MAILMAN 2 > What I got from the Mailman 2 Wiki is "How to restrict the list so only authorized persons can post (moderation). If there is an option like that in Mailman 3 I want that. There is, but you can't do it the best way. See below. > SUMMARY > I want to be able to reply personally to the user if necessary without his or her message going to the list. So something like moderation. > > So let me take a guess: > > Default action to take when a non-member posts to the list AND > Default action to take when a member posts to the list > > should be set to HOLD FOR MODERATION? That will work and is probably what you want anyway. Your own posts will also be held, but you can just accept them. Alternatively, you could set your own Moderation setting to Accept or Default Processing so your posts won't be held, but don't do that as it allows anyone to post by spoofing your address in From:, Sender: or Reply-To: or the envelope sender. The best way to post without the post being held is pre-approval with an Approved: <password> header, where <password> is the list's moderator_password, but you can't set that in postorius so it won't work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Confusing mailman user model

by Mark Sapiro

On 7/19/20 8:10 AM, Gilles Filippini wrote: > Hi, > > I'm trying to understand the Mailman user model, and I'm confused about > the respective roles of tables 'auth_user' and 'user'. auth_user is a Django auth table. These are the users listed in the Django admin web UI. user is Mailman core's users. > Both have an 'id' column referred to as 'user_id' when used as a foreign > key. But there seems to be no relation at all between them as they use > different ids for the same user. Right, they are unrelated. > Our mailman server was migrated from mailman2 to mailman3 about 1.5 year > ago, and there is an inconsistency I'd like to fix: > 2 of our users have a registered Mailman account with their respective > email addresses in table 'auth_user', but these very same addresses in > the 'address' table are linked to another old admin account in the > 'user' table. Their Mailman account is the 'old' one. the auth_user account is a Django account > > Then if add one of these addresses as a domain owner, it it the old > admin address which is selected instead. How could I fix that? That's because domain owner in a Mailman thing and involvs the Mailman user. You could delete the Django users via the Django admin UI and then re-register them via Postorius. That *might* work. -- 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: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 2/24/22 18:21, chucka(a)blackforest-co.com wrote: > I have this working: > > #!/bin/bash > H="http://lists.mysite.org/admin.cgi/newsletter-mysite.org/members" > case $1 in > 'add') curl "$H/add?subscribees=$2&adminpw=verysecret" ;; > 'del') curl "$H/del?subscribees=$2&adminpw=verysecret" ;; > esac > > and scan the return for "Successfully [Un]subscribed" Since the above is MM 2.1 I'm assuming you are asking how to do the above in MM 3 via REST. Here are some examples: To add a single user curl -urestadmin:restpass \ --request POST \ -H 'Content-Type: application/json' \ --data-binary '{"list_id": "list.example.com", "subscriber": "user(a)example.net", "display_name": "Joe User", "pre_verified": true, "pre_confirmed": true, "pre_approved": true}' \ http://localhost:8001/3.1/members Response is empty or a JSON object describing the error. To delete a single user: curl -urestadmin:restpass \ --request DELETE \ http://localhost:8001/3.1/lists/list.example.com/member/user@example.net Response as above To delete a list of users: curl -urestadmin:restpass \ --request DELETE \ -H 'Content-Type: application/json' \ --data-binary '{"emails": ["user(a)example.net","other(a)example.org"]}' \ http://localhost:8001/3.1/lists/list.example.com/roster/member Response is a JSON object similar to {"user(a)example.net": true, "other(a)example.org": false, "http_etag": "\"...\""} where success or failure is indicated by a true or false value for each address or a JSON object describing the error 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, 5 months

[MM3-users] Re: Null sender?

by Mark Sapiro

On 6/28/20 6:58 AM, tom(a)gather.coop wrote: > Does Mailman generally send email with a null sender? > > This is what I see in the log: > > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <> > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT' > > Notice the empty MAIL FROM. > > Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject. > > Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail. It isn't Mailman doing this. It is the MTA at mail.example.coop that is reporting the bounce of some message from the techque(a)example.org list. The log messages you see are Mailman's receipt of the bounce DSN. Bounce DSNs are always sent with a null envelope sender so if they are undeliverable, it doesn't result in another bounce. See <https://www.rfc-editor.org/rfc/rfc3461.html#section-6.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, 1 month

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/25/24 23:07, Mark wrote: > > So, the template is all good, it can be accessed by Lynx, but the part > of the Mailman suite that sends out the custom Welcome message cannot > access it and spits out the error. > > Where are the custom templates stored? Is there a permissions issue > perhaps? A grep for the text of my Welcome message turns up zero results. They are stored in the postorius_emailtemplate table in the mailmanweb database. And yes, I think there is some permissions issue, but it is not simple. It probably involves apparmor or some other security manager. If it were simple, the mailman shell test I suggested at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… would fail. > By the way, in Lynx when the template's URI uses the public ip adress -- > ie. > > http://my-public-ip-address/mailman3/api/templates/list/mytestlist.mydomain… > > ... it returns a "404 page not found" in Lynx. Which is probably why that setting sent the welcome with empty content. > Given that this is pretty much an out-of-the-box installation (venv > installation as per the docs) and everything else works perfectly I'm > thinking surely others have encountered this. Or is it just me? I just did a test on my development system and I see the same timeout error, so it's not just you. I'll work on this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

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

by Mark Sapiro

On 12/28/21 1:28 PM, William Oliver wrote: > > If I just stop the thing and then start it, it goes fast. Here's that > log: > > Dec 28 16:27:22 emergenus systemd[1]: Stopping GNU Mailing List > Manager... > Dec 28 16:27:24 emergenus mailman[23408]: Shutting down Mailman's > master runner > Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Succeeded. > Dec 28 16:27:27 emergenus systemd[1]: Stopped GNU Mailing List Manager. > Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Consumed > 42.834s CPU time. > Dec 28 16:27:27 emergenus systemd[1]: Starting GNU Mailing List > Manager... > Dec 28 16:27:29 emergenus kernel: [ 8076.868797] [UFW BLOCK] IN=eth0 > OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.108 > DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=58971 PROTO=TCP > SPT=44610 DPT=21987 WINDOW=1024 RES=0x00 SYN URGP=0 > Dec 28 16:27:29 emergenus mailman[23433]: Starting Mailman's master > runner > Dec 28 16:27:29 emergenus mailman[23433]: Generating MTA alias maps These log entries are from restarting mailman, not mailmanweb. > Dec 28 16:27:30 emergenus systemd[1]: mailman3.service: Can't open PID > file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not > permitted > > I don't know what's up with the pid thing -- it moves right on in about > 1 second. It's a race condition. systemd (systemctl start) is trying to read /opt/mailman/mm/var/master.pid before the master has created it. That's why it says (yet?). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

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

by Mark Sapiro

On 7/12/24 3:34 PM, 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. On average, it takes about 15 - 20 seconds to run a query which is very slow IMHO. When searching through web administrator interface for Users, it takes only 1 -2 seconds. Is there a reason for such a discrepancy between the two interfaces? Is there any tuning to the CLI that could help with the performance issue? Here is the setup information regarding the VM hosting the Mailman 3 server: This is actually https://gitlab.com/mailman/mailman/-/issues/1095 The basic loop is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_f… and the time consuming part is https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_f… On mail.python.org which has about 75,000 users ``` for user in getUtility(IUserManager).users: continue ``` takes a few seconds, but ``` for user in getUtility(IUserManager).users: emails = [address.email for address in user.addresses] continue ``` takes almost 3 minutes which is about the time that `findmembers` takes in total. I've tried changing this to ``` for user in getUtility(IUserManager).users: if len(user.addresses) == 1: emails = [user.addresses[0].emails] else: emails = [address.email for address in user.addresses] continue ``` but it doesn't help. Just referencing user.addresses in the loop as in ``` for user in getUtility(IUserManager).users: x = user.addresses continue ``` takes 3 minutes. -- 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: Creating and placing custom templates

by Mark Sapiro

On 5/2/19 12:45 PM, kelly.close(a)lrewater.com wrote: > > Here's what I'm doing: > > I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ What is the setting, if any, for 'layout' in your mailman.cfg? If, for example, you have layout: fhs The default var_dir in that layout is /var/lib/mailman, not /var/lib/mailman3, although that could be changed in a [paths.fhs] section. > In that folder I created the following folders and made sure they were properly owned (by list:list) > /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ > > Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". Yes, you do need the .txt extension. If this doesn't work, it's possible you have a different URI for the template. Try bin/mailman shell Welcome to the GNU Mailman shell'list:member:regular:footer', >>> tm = getUtility(ITemplateManager) >>> tm.raw('list:member:regular:footer', 'f2p2-test.udfcd-lists.org') This should return something like 'mailman:///$listname/$language/list:member:regular:footer.txt' Does it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

When I go to https://.../admin/ I get a Django Administration screen and in the upper right hand corner I see WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:55 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 5:11 PM, Mark Sapiro wrote: > On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: >> Is this anything to be concerned about? It seems like an attempted >> break-in as I have no user named alekos.pantazis. > > > First, this is a Django user, not a Mailman user.... > The error you see seems to say that > django_mailman3/templates/django_mailman3/profile/profile.py contains > {% load gravatar %} at line 3 but there is no > django_mailman3/templatetags/d_gravatar.py file. The above should say `contains {% > load d_gravatar %} at line 3` Regarding attempted breakin. It's not that. Just someone signing up or logging in at your web UI and visiting their user profile. If you go to your Django admin UI (https://.../admin/) you should see that user. The error seems to be something broken in your installation. Can you visit your user-profile? -- 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, 9 months

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

by Mark Sapiro

On 3/22/22 07:46, ryan.anderson.4--- via Mailman-users wrote: > Hello, > > We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings. You can accept HTML and not convert it if in Postorius -> Settings -> Alter Messages, assuming Filter content is yes, ensure Pass types includes `text/html` or maybe `text` to include all text maintypes and both Collapse alternatives and Convert html to plaintext are set to No. > The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . They probably aren't ` and -, but rather things like Unicode Left Single Quote and En Dash. > We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything. When you say you changed the character set to UTF-8, what did you do? If you set ``` [language.en] charset: utf-8 ``` in mailman.cfg and restart mailman core, that should allow those characters without replacing them. -- 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 migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Mark Sapiro

On 3/3/25 07:52, Stefan Bauer via Mailman-users wrote: > > trying to update mailman3 to lastest version, we fail during > > mailman-web migrate with: > > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, > django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > Applying account.0006_emailaddress_lower...Traceback (most recent call > last): > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", > line 89, in _execute > return self.cursor.execute(sql, params) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", > line 328, in execute > return super().execute(query, params) > sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang and replace psycopg2 with sqlite3. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… > We found a workaround to fake the migration with > > migrate --fake You should fix the issue with the DB and run the migrations. > Could this be some duplicate users with same mail-address? This is not related to Mailman users. It is Django users. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 4 weeks

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Mark Sapiro

On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: > We use a multi-hop SMTP system to go from the inside of our network out > to the Internet at the domain test.lists.example.com. > > The setup is this way for ingress: > > {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 Connector) > -> Mailman for delivery to listserv > > Egress is this: > > Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET > > -- > > When a message is sent an invalid list (we'll call it > invalid(a)test.lists.example.com) we end up with a nasty side effect in > the system. The "no such recipient" response gets sent to the smtpproxy > machine and then *it gets redelivered back to Mailman* as a redelivery > as if it isn't accepting a permanent-failure condition code. I don't understand why this is happening. Whatever MTA is seeing the "no such recipient" status and creating the response DSN should be sending it to the envelope sender of the original message so it should not be sent to the invalid mailman address. Is one of the MTAs in the delivery chain to Mailman rewriting the envelope sender? What are the MTA log messages from all the MTAs whos logs you have access to? -- 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: Subject Munging

by Mark Sapiro

On 7/5/24 08:34, Sam Darwin via Mailman-users wrote: > Hi, > > We have a user who is proposing that reply messages from a mailing list should be in the following format: > > Re: [MM3-users] Ubuntu 24.04 upgrade notes > > and not > > [MM3-users] Re: Ubuntu 24.04 upgrade notes > > Their reason... is that mailman2, and other lists, used to do it that way. > > I myself am agnostic about the difference, and probably prefer to keep things the way mailman3 recommends. > > The questions are: > 1. What could be explained to the user to convince them the new method is preferable. This is to support prefixes that contain %d for the message number. Suppose the prefix is [List #%d] and a post to the list has prefixed subject [List #501] A Subject. With old style, a reply a few posts later might have subject Re: [List #504] A Subject. But it is not a reply to [List #504], it is message [List #504] replying to `A Subject.` so the appropriate subject is [List #504] Re: A Subject. > 2. Can this be customized with a Setting? (Not that we will end up modifying it. Just curious). In mailman 2.1 this was called OLD_STYLE_PREFIXING and prefixes without %d could optionally do it the old way or the new way , but prefixes with %d always did it the new way. For Mailman 3 we always do it the new way even if the prefix does not contain %d. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Howto: Mass import of nonmembers in several lists?

by Mark Sapiro

On 1/10/22 4:00 AM, Paul Paulchen wrote: > > So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. > I thought so, because the import21 command did this as well when we migrated to mailman3. You could script it with `mailman shell`. If you really want this, I'll help. > I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. > But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! You can't without modifying the code. > Hope I explained my case properly. I appreciate your responds! Thanks in advance. My question is why do you want to add these nonmembers. The only thing gained by adding a nonmember is the ability to set the nonmember's moderation action to other than the default, and you can handle that with the legacy * these non-members settings which take priority over the nonmember's moderation action anyway. Note that if a nonmember posts to a list, she will automatically be added to the list as a nonmember with default moderation action if she isn't one of the list's nonmembers already. -- 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: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > Thank you Mark. > > What you have said is right.. > > I found a list with two "hyperkitty" records in the listarchiver in the > database. I had removed the list and recreated it and now I found it is > working fine. The recreated list is having only one record. OK, but that's not a reasonable way to fix this in general. You can just remove the `extra` record using a direct database query which is probably the least disruptive way to fix this. > After searching the links you provided I found there is just a work around > but not the precaution to be taken for not getting the duplicate record. > > Can you say what might be the reason for this duplication? If I need to > provide any details, please let me know. As noted in the threads I referenced, we don't know the cause. Yours is the first report of this issue with the `hyperkitty` archiver. In all the other reports, the duplicate archiver has been `mhonarc`. If it happens again and you know the exact sequence of events that led to it, i.e. what was done with the list between the last time it worked and when it stopped working, that might give us clues, but currently we are at a total loss to understand how this happens. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

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

by Mark Sapiro

On 6/17/23 17:02, Mike Wertheim wrote: > I set `remove_dkim_headers: yes` in the [mta] section of mailman.cfg. > > I'm seeing a bunch of these errors in the logs: > 2023-06-17 18:57:11 1qAbMA-005Y7W-HP ** mike.wertheim(a)gmail.com > <mailto:mike.wertheim@gmail.com> R=dnslookup_single_domain > T=remote_smtp_single_domain H=alt2.gmail-smtp-in.l.google.com > <http://alt2.gmail-smtp-in.l.google.com> [172.253.62.26]: SMTP error > from remote mail server after end of data: 550-5.7.26 Unauthenticated > email from gmail.com <http://gmail.com> is not accepted due to > domain's\n550-5.7.26 DMARC policy. Please contact the administrator of > gmail.com <http://gmail.com> domain\n550-5.7.26 if this was a legitimate > mail. Please visit\n550-5.7.26 > https://support.google.com/mail/answer/2451690 > <https://support.google.com/mail/answer/2451690> to learn about the\n550 > 5.7.26 DMARC initiative. > w13-20020a05622a190d00b003fde5babbf5si1170418qtc.14 - gsmtp Your issue is mail From: the gmail.com domain to the list and sent to gmail users is being bounced because it fails DMARC. I.e. Gmail applies a DMARC policy of p=reject to mail From: gmail.com even though it's published DMARC policy is p=none. You need to apply DMARC mitigations to this mail. Unfortunately, this requires setting DMARC Mitigate unconditionally to Yes. Mailman 2.1 has a feature to apply DMARC mitigation to messages From: specific domains regardless of any domain specific DMARC Policy. Unfortunately this hasn't been implemented in Mailman 3 yet. I just filed https://gitlab.com/mailman/mailman/-/issues/1084 for that. -- 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: How to keep virtualenv install secure?

by Mark Sapiro

On 11/7/24 01:31, Lichtinger, Bernhard wrote: > Hi, > > I am looking for some advice: If we use the virtualenv install method, how does one keep track of security updates for all the installed dependencies? > > I can think of: > - Upgrade regularly all installed packages inside the virtualenv. This might break mailman3 if there are incompatible updates. You can do in the venv ``` pip install --upgrade --upgrade-strategy eager mailman psycopg2-binary mailman-web mailman-hyperkitty ``` I'm not sure if this will update dependencies if there are no updates to the named package, but in any case, incompatibilities should be avoided because if a newer version of a dependency in incompatible, the dependency should be pinned to a compatible version in the project's requirements. > - Try to track all dependencies and check if there are security updates published. This might be impossible to achieve. It shouldn't be too difficult to script this. ``` Get the output from `pip freeze` in the venv for each line split it on `==` into PACKAGE and VERSION get https://pypi.org/rss/project/PACKAGE/releases.xml find the first <title>VERSION</title> and compare that VERSION to the VERSION from `pip freeze` ``` This won't tell you if the newer version is a security update, but it will tell you which packages have newer versions. > - Security updates are so rare, we do not need to bother. ;) For the Mailman dependencies, this is probably true. -- 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: Approve an email

by Mark Sapiro

On 12/26/22 12:08, Lars Bjørndal wrote: > Hi, list! > > I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and > postorius-1.3.6-2.fc36.noarch installed. with the command > > sudo -u mailman mailman3 create <listname> > > I was able to create a list. > > I'm not able to find out how to setup and configure the postorius > package. There's no mailman-web command. See <https://docs.mailman3.org/projects/postorius/en/latest/>. I don't know how you invoke the Django management command in the postorius-1.3.6-2.fc36.noarch package. It could be manage.py or django-admin or something else. > Hyperkitty will not installed du to a dependency conflict, but I dont > need archiving for the list. > > Here comes my quesitons: > > - What's the easiest way to approve an email sent to the list? Approving held messages via email requires Mailman core >= 3.3.5. See <https://gitlab.com/mailman/mailman/-/issues/169> Thus, the easiest way is via Postorius. > - How can I configure the list to accept messages also from non members? Set the list's default_nonmember_action to Action.defer. This can be done via Postorius, mailman shell or the REST API. > - How can I setup postorius to work on Fedora? I have django-admin, but > I'm not sure where to go. See the Postorius docs at https://docs.mailman3.org/projects/postorius/en/latest/setup.html#installat… to get started. (replace `python manage.py` with `django-admin`) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 10:37, Eggert Ehmke via Mailman-users wrote: > Hello Steve, > I really would appreciate to get some help on the withlist command. I really like to program python, but this interface is not at all intuitive. I also find it strange to do administrative tasks in a programming language. In this special case, I believe it should be possible to work on the display names in Postorius in the member settings. You can update user display names in Postorius via the Users tab at the top of the page, but it would be a tedious, one at a time process, and I don't think you can modify address display names in Postorius and those are the ones `mailman members` displays. I just posted a mailman shell (aka withlist) interaction at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Try that. > I also find it strange to do administrative tasks in a programming language. Understood, but there are a couple of things at work here. One is that this particular task is a one-off the correct the result of a bug, but perhaps more significantly, mailman developers (at least me) are comfortable with `withlist` (it's been around since MM 2.1) and if I can do it that way, it reduces the motivation to make something more friendly for the normal admin. Unfortunately doing things easily that way requires a lot of specialized knowledge of Mailman internals, so most admins need help with it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Mailman3 Docker persmission denied

by Mark Sapiro

On 1/6/25 13:09, Commander456 wrote: > Hello everyone, > > I recently installed the mailman-core Docker image (Version 0.5) and tried to create a list using the mailman commands inside the container. I used the --notify argument but doesn't receive any mail (I'm the list owner), However, inside the mailman.log I get the following error: > > Jan 06 20:54:25 2025 (156) Uncaught runner exception: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' > Jan 06 20:54:25 2025 (156) Traceback (most recent call last): > File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 164, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/site-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > ^^^^^^^^^^^^^^^^^^^^ > PermissionError: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' > Jan 06 20:54:25 2025 (156) Skipping and preserving unparseable message: 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8 Did you run `mailman create` as user `mailman`? Also did the command print a `Created mailing list:` message? In any case, it looks like the list was created and the command generated the notification which was queued in the virgin queue as 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck, but then virgin runner was unable to read it, but if there was no `Failed to unlink/preserve backup file:` message in the log the file should have been moved to /opt/mailman/var/queue/bad/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.psv. What is ownership and permissions of that file, and what is the user running the various runners? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Mailman3 Setup

by Mark Sapiro

On 6/11/22 06:02, George R. Kasica wrote: > Mark: > > These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. I virtualenv is not a "container", at least in the sense of a Docker container. It is just a way of isolating an environment from various OS things and vice versa. You do not need to install in a virtualenv. You can follow the procedure for installing in a virtualenv and just omit the bits about creating and activating the virtualenv However, if you do not install in a virtualenv, you are vulnerable to OS package updates breaking things. For example, installation of Mailman core installs SQLAlchemy <1.4 because Mailman core is not currently compatible with SQLAlchemy >=1.4. If an OS package upgrade installs SQLAlchemy >=1.4, that will break your Mailman installation. > If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? You actually don't need to remove anything because whatever is installed in the virtualenv will be what's used when the virtualenv is active. However, any Mailman specific stuff installed systemwide will not be used and is just wasted space and could be uninstalled. -- 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: Mailman issues after re-boot

by Mark Sapiro

On 9/16/23 5:29 AM, Paul Rubin wrote: > *I need to know what to remove, how to correctly update, etc., That said > the two scripts appear to be very similar:* > > mail:/opt/mailman # head /usr/bin/mailman > > #!/usr/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' > __requires__ = 'mailman==3.3.4' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( This is no good because it uses the system Python and won't have the venv's site-packages in its path. > mail:/opt/mailman # head /opt/mailman/venv/bin/mailman > #!/opt/mailman/venv/bin/python3 > # -*- coding: utf-8 -*- > import re > import sys > from mailman.bin.mailman import main > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) > sys.exit(main()) > mail:/opt/mailman # This one is good because it uses the venv python3 and thus uses site-packages from the venv. > *Given the two years since the last reboot I also tried following * > https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was > running the latest* > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web Thin may be part of the issue. The above may not upgrade dependencies as needed. You may need the `--upgrade-strategy eager` option. -- 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: Welcome Message

by Mark Sapiro

On 11/6/19 9:18 AM, josh(a)caluette.com wrote: > I just setup a new Mailman 3 server using maxking/docker-mailman from GitHub. I got everything working just right including changing the footer template for messages. However, when trying to set anything in a Welcome template, I am encountering these same errors. > > I have confirmed that the mailman-core container is able to download the template via curl using the http://mailman-web:8000/ api URL and gets the correct text, but anytime I try to mass subscribe, it fails with the errors that Brian had provided and I get an HTTP 500 error. > > If I remove the Welcome template, then I can do mass subscribe just fine. > > Here are the logs: > > Nov 06 17:10:13 2019 (29) deque: > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 384, in _make_request > six.raise_from(e, None) > File "<string>", line 2, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 380, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1331, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 297, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 258, in _read_status > line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") > File "/usr/lib/python3.6/socket.py", line 586, in readinto > return self._sock.recv_into(b) > socket.timeout: timed out Have you set POSTORIUS_TEMPLATE_BASE_URL appropriately in your 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, 8 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/27/21 3:48 PM, Ruth Ivimey-Cook wrote: > > It is also possible to Alter existing databases and tables, but with one > catch: the maximum table row length is reduced, so some tables will need > to be adjusted (e.g. converting varchar(255) to varchar(230)). This is misleading. The maximum row length depends on the actual data stored in the row. The sum of the various column size limits for VARCHAR and other columns can well exceed the maximum row size as long as the sum of the lengths of the actual data stored in the row does not. The significant issue is all these limits are bytes, not characters, so in the worst case, a VARCHAR(255) column can only store 85 3-byte utf8 encoded unicodes or 63 4-byte utf8mb4 encoded unicodes, but this too is misleading an most strings contain single byte encodings with some 2 or 3 byte encodings and maybe at most one or two 4-byte encodings. Furthermore, the problem issues are essentially limited to emojis and possibly other 4-byte encoded symbols in email subject headers and bodies. Bodies are a TEXT field and the data are stored separately and do not affect the row size and subjects are defined with a maximum length of 512 bytes which should be sufficient. None of the data stored in rows is at all likely to exceed the maximum row length, even with a lot of 4-byte encodings. -- 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: Mailman notify generating emails for request that aren't visible.

by Mark Sapiro

On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ… although they may not be counted in the Subscription requests count badge. -- 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 recovery test did not go as planned

by Mark Sapiro

On 8/9/22 07:19, Stephen J. Turnbull wrote: > > You don't do it with HyperKitty (I'm pretty sure you can export mboxes > from HyperKitty, but I don't think it would be timely, you have to do > it by hand). The sample archiver (which you can enable in mailman.cfg > IIRC, haven't done it in a while) would make the mbox files directly > from the core at the same time that they are sent to HyperKitty. It's > possible to have both HyperKitty and the sample archiver enabled at > the same time. The `sample archiver` is actually called the prototype archiver and it is typically enabled by default. The messages are stored in maildir format in Mailman's var/archives/prototype/ directory in sub-directories with names of the list posting addresses. You would need to convert maildir to mbox format to import to hyperkitty. A simple script to do this is ``` #!/usr/bin/python3 """Run this with the list posting address as it's argument.""" import os import sys from mailbox import mbox, Maildir MDIR = '/path/to/mailman/var/archives/prototype/' MBOX = '/path/to/output_directory' if len(sys.argv) != 2: print(f'Usage: {sys.argv[0]} list_posting_address', file=sys.stderr) sys.exit(1) mdir = Maildir(os.path.join(MDIR, sys.argv[1]), create=False) mlbox = mbox(os.path.join(MBOX, sys.argv[1]), create=True) for msg in mdir: mlbox.add(msg) mdir.close() mlbox.close() ``` -- 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: Time Zone Problem In Postorius

by Mark Sapiro

On 1/12/22 7:34 PM, Alan So wrote: > I notice that the template was updated to add the code. However, I still observe an issue. > > If the correct hold date is: 2022-01-13 10:16 GMT+8 or 2022-01-13 02:16 GMT > If I select my time zone as Asia/Hong_Kong, it is displayed as Jan. 13, 2022, 2:16 a.m. > If I select time zone as GMT, it is displayed as Jan. 12, 2022, 6:16 p.m. > > There is a shift of -8 hours when displaying the time in Postorius. I cannot find the detail of the held message from database tables yet. Not sure how the hold date was stored at this moment. As you note later, the hold time is stored in UTC. It should be rendered in Postorius held message view in the timezone that you have set in your user-profile. The timezone conversion is in Django. It is defined in the template as ``` {{ msg.hold_date|datetime_parse|localtime|date:"DATETIME_FORMAT"}} ``` where msg.hold_date is the time in UTC. I think the issue is that while msg.hold_date in in UTC, it is a naive datetime.datetime object (see https://docs.djangoproject.com/en/4.0/topics/i18n/timezones/#interpretation…) so if your Django setting for TIME_ZONE is Asia/Hong_Kong it is interpreted as UTC +0800 so that subtracts 8 hours and then conversion to your profile timezone if Asia/Hong_Kong adds 8 hours back. I think if you set `TIME_ZONE = 'UTC'` you will get the behavior you expect. -- 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: Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails

by Mark Sapiro

On 10/12/24 1:44 AM, francesd919--- via Mailman-users wrote: > Hi everyone, > > I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. > These emails mentioned that the subscription was disabled due to bounce score. > Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > I have some questions: > > 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? > 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. > 3. What could have cuased functioning emails to bounce and therefore being disabled? The answer to all those is you upgraded from a Mailman core version prior to 3.3.1. Prior to that, bounces were recorded in the database but not processed. when you upgraded, they all got processed at once. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… which includes a `mailman shell` interaction to re-enable all the subscriptions disabled by bounce. -- 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: redirecting -bounces replies

by Mark Sapiro

On 10/31/24 16:17, Hirayama, Pat wrote: > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Then for example if your list domain is example.com and its alias domain is x.example.com, you could modify one line in the postfix_vmap file for the `listname` mappings from ``` listname-bounces(a)example.com listname-bounces(a)x.example.com ``` to ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` and then run postmap on the file. The problem is any time you create or delete a list or run `mailman aliases` or run `mailman start` with the --generate-alias-file option, the file is regenerated and you will have to edit it again. To avoid that issue, you can create a separate vmap file containing only the ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: Cannot locate manage.py

by Mark Sapiro

On 1/21/20 4:08 PM, Frank van den Heuvel wrote: > Hello, > > While following https://docs.mailman3.org/en/latest/migration.html, I > want to execute: > > python manage.py hyperkitty_import -l foo-list(a)example.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > Of course edited with values for my list. But I already get stuck in not > being able to locate "manage.py". > > When I run "locate manage.py", I get: > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl > > /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py > /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py > > Which one is the right one? Probably none of those. I'm not that familiar with the file layout in the Debian package if that's what you installed, but I would expect to find it in /opt/mailman/mm/venv/bin/ and I'd expect to find the files django_admin and django_admin.py. Both of those will run the Django management interface, but they won't work because they won't access your settings. I put the following executable in /opt/mailman/mm/bin #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ This assumes my settings.py file is /opt/mailman/mm/settings.py. If yours is elsewhere you may need to adjust PYTHONPATH and/or DJANGO_SETTINGS_MODULE. For example, on another server with the settings at /opt/mailman/mm/mailman_web/production.py I have export DJANGO_SETTINGS_MODULE=mailman_web.production -- 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: Edit archived email? Is it possible?

by Mark Sapiro

On 9/28/21 6:02 AM, Prasanth Nair wrote: > Hello, > > Does anyone know how to edit an archived email in Mailman3? It is possible > in Mailman2 ( > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M…) > Is there any option similar to this in Mailman3? In some sense the process is the same but possibly even simpler in Mailman 3. You need to modify the underlying data which requires appropriate access to the server. In Mailman 3, the data are in the hyperkitty_email table in Mailman's database. You can get the Message-ID hash from the URL to the archived message, e.g. for the message to which I'm replying, the URL is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have access, you can do database queries like ``` SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; ``` and ``` UPDATE hyperkitty_email SET content = '<new content>' WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; UPDATE hyperkitty_email SET subject = '<new subject>' WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; ``` If the message has attachments, they are in the hyperkitty_attachment table and can be referenced by `email_id` which is the corresponding `id` from the hyperkitty_email entry. You can also do similar things via `django-admin shell`. E.g. ``` $ django-admin shell Python ... (InteractiveConsole) >>> from hyperkitty.models.email import Email >>> x = Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >>> print(x[0].content) ``` but this requires some knowledge of HyperKitty's models and Django's ORM. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

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

by Mark Sapiro

On 2/8/22 17:57, Philippe B wrote: > Thanks. I'm getting: > > >>> owner.delivery_status > <DeliveryStatus.by_moderator: 4> > > for the 2 lists with that odd behavior (as opposed to `<DeliveryStatus.enabled: 1>` for several other lists I checked). > > What does that 4 mean? It means that owner's delivery was disabled by moderator action[1]. You want to set it enabled as I indicated in my prior post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. That is why the owners don't get notices, and you need to set their delivery status enabled so they will. Note that this only affects notices. It doesn't affect list posts assuming they are list members. That is controlled by the member's delivery status And because there are no eligible owner or moderator recipients the notices go to the configured site_owner. [1] The disabled by moderator status can occur in the following way for a list imported from Mailman 2.1. If the address in MM 2.1 is both an owner or moderator and also a list member, and the list member's delivery was disabled in MM 2.1, both the imported member and owner/moderator will have delivery disabled. This is really a bug in import21 as in Mailman 2.1, owner/moderator delivery couldn't be disabled, it shouldn't be imported as disabled. I have just created https://gitlab.com/mailman/mailman/-/issues/977 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Mailman 3 bounce handling and DKIM mitigation

by Mark Sapiro

On 09/05/2017 01:14 PM, David Krantz wrote: > > I have a question on bounce handling. I get the impression that > bounces are just lost and neither handled nor forwarded to the list > admin. Is this a known problem? I am running mailman from git, but > about version 3.1 and use postfix. Bounce processing in Mailman 3 is currently not done. See <https://gitlab.com/mailman/mailman/issues/343>. > I find lots of things in the > bounceevents table. Is there any way to find out more on these events? > I probably can configure postfix to send listname-bounce@domain to an > admin adress. Or for that matter hack mailman to send it to the > correct admin. Your ideas are possible. Until it's fixed, you could just make postfix forward the listname-bounces address to listname-owner. I think this will then get the LMTP runner to send them to the owner. > Also the DKIM mitigation does not seem to detect DKIM domains. If I > force the mitigation for all mails it works but that of course has > annoying consequences although mostly cosmetic. This has caused quite > a number of bounces for my lists (as well as being temporarily banned > by at least Microsoft). I assume you mean DMARC mitigation. It should work for From: domains that publish DMARC policy 'reject' or 'quarantine' without setting DMARC Mitigate unconditionally. What if anything do you see in mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 08:33, William Oliver wrote: > > So... I run a small mailinglist using mailman3 that has been workiing > great for a couple of months. Last week, all my users from gmail got > kicked off because gmail decided that the list messages were > "unsolicited email". I didn't find out about it until the users hit > their mailman3 bounce limit. I *thought* would be seeing all the > bounce messages, but apparently not. I didn't see any config settings > for "see all the bounce messages" so i thought to myself, "Self, well > maybe that's because my mailinglist username doesn't have a mailbox in > /home/listname". Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, you will see settings like `Notify owner on bounce increment`, ` Notify owner on disable` and `Notify owner on removal` under `Bounce Processing`. Presumable you did get the notification of removal, so delivery to the owner works. Are the increment and disable (or maybe just disable if your versions are older) notices set to Yes? > So, I decided to try that. I created /home/listname/Maildir/* and > logged in as fplist to see if it would put mail there. In order to log > in as listname, I gave the user listname a password. Can't you just reverse those steps. I.e. remove /home/listname/ and remove the listname user? -- 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: How to promote non-members to members?

by Mark Sapiro

On 3/17/22 10:19, Quanah Gibson-Mount wrote: > > So then I ran your code to confirm it, and it blows up with an error: ``` >>>> for token, data in pendings.find(pend_type='subscription'): > ... if data['token_owner'] != 'subscriber': > ... continue > ... if data['email'] != 'xxxxxxxx(a)xxxxx.org': > ... continue > ... sub_mgr.confirm(token) > ... > Traceback (most recent call last): > File "<console>", line 6, in <module> > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 545, in confirm > workflow.restore() > File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line > 149, in restore > setattr(self, attr, data[attr]) > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 119, in address_key > assert self.address is not None > AssertionError ``` This says that there is no Address object with the email xxxxxxxx(a)xxxxx.org What do you get in `mailman shell` for ``` >>> um = getUtility(IUserManager) >>> um.get_address('xxxxxxxx(a)xxxxx.org') >>> um.get_user('xxxxxxxx(a)xxxxx.org') ``` These should return an Address and a User respectively. If they don't, did you perhaps run some process to delete the user? If the user is gone, you should be able to replace ``` ... sub_mgr.confirm(token) ``` in the above with ``` ... wfm = getUtility(IWorkflowStateManager) ... pendings.confirm(token, expunge=True) ... wfm.discard(token) ``` to clear the pending subscription and workflow and then be able to mass subscribe the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 1:37 AM, "Jörg M. Schulz" wrote: > > Normal, non-digest messages are sent correctly. Administrative messages as well. > > Using GNU Mailman 3.2.0 (La Villa Strangiato) > > Where could I look for errors / stuck queues? > > /var/lib/mailman3/lists > /var/lib/mailman3/lists/mailman.unswolke.de > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.3.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.2.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.2.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.6.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.4.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.1.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.1.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.3.mmdf When a digest is to be sent by 'mailman digests', the digest.mmdf file is renamed to digest.x.y.mmdf (x and y are the volume and issue numbers) and an entry placed in queue/digests to send that digest. The digest runner then picks up that entry, prepares the digest, queues it in queue/virgin to be sent to the recipients if any and removes the digest.x.y.mmdf file. Since the digest.x.y.mmdf files are not removed, either the digest runner is not running at all in which case there will still be entries in queue/digests or it is encountering an error in processing in which case there should be messages with tracebacks in Mailman's error log and probably messages in queue/shunt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

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

by Mark Sapiro

On 4/11/19 10:02 AM, brian(a)emwd.com wrote: > I followed Kelly's guide and ran into some issues but were able to resolve most of them. It seems I have one out standing issue: Hyperkitty. When I post to a list, I am getting the following in the /var/log/mailman3/mailman.log: > > Apr 11 14:01:15 2019 (1334) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF/$ > <html><head> > <title>503 Service Unavailable</title> > </head><body> > <h1>Service Unavailable</h1> > <p>The server is temporarily unable to service your > request due to maintenance downtime or capacity > problems. Please try again later.</p> > <hr> > <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> > </body></html> > (503) ... > Everything else works fine. Postfix is receiving and delivery mail to Mailman3. List members are receiving the posts. I can access the list on Hyperkitty just no archived messages. What URL do you use to access HyperKitty. The problem URL above, http://localhost/mailman3/hyperkitty/api/mailman/archive is based on the base_url setting in mailman-hyperkitty.cfg which in your case is http://localhost/mailman3/hyperkitty/, byt the web server listening on localhost:80 is returning the Service Unavailable. It probably doesn't like the IP or name 'localhost'. Set base_url in mailman-hyperkitty.cfg to use an acceptable host name instead of localhost or adjust your apache config to accept localhost. -- 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: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/11/22 09:37, Stanisław Findeisen via Mailman-users wrote: > Dear Experts > > What is the best way to go about reconciling GNU Mailman3-made message modifications (like message footers or subject prefixes) with sender-made DKIM signatures? I am aware of the "DMARC mitigations" tab in the list settings, not bad, but it looks that "replace From: with list address" doesn't help (of course), whereas wrapping the message in an outer message often looks ugly. Is there a better way?... > > BTW I would like to point out that broken DKIM signature can be a problem even with an easy DMARC policy; for example ProtonMail will display this flashy red warning: https://protonmail.com/support/knowledge-base/email-has-failed-its-domains-… in its webmail. (I guess nothing can be done about it except "DMARC Mitigate unconditionally"). ProtonMail is broken - see https://www.rfc-editor.org/rfc/rfc6376.html#section-6.1 That said, BCP recommends removing the signatures that the MLM will break https://www.rfc-editor.org/rfc/rfc6377.html#section-5.7 Mailman implements this with the mailman.cfg setting ``` [mta] remove_dkim_headers: yes ``` Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your valid DKIM signature and no prior Authentication-Results:. ARC <https://www.rfc-editor.org/rfc/rfc8617.html> is intended to address this while preserving prior authentication results and is supported by Mailman, but is not accepted by all receivers. -- 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: Moderate mails from owner

by Mark Sapiro

On 5/7/19 1:54 AM, Henrik Rasmussen wrote: > Do I have to make a commit or something? Even m.accept_these_nonmembers.remove removes the member from the list, it is right back when I return to the Mailman shell: > >> bash-4.3# mailman shell -l [LISTNAME].lists.example.com >> Welcome to the GNU Mailman shell >> The variable 'm' is the [LISTNAME].lists.example.com mailing list >>>>> m.accept_these_nonmembers >> ['listadmin(a)senderdep.example.com'] >>>>> m.accept_these_nonmembers.remove('listadmin(a)senderdep.example.com') >>>>> m.accept_these_nonmembers >> [] >> quit() There are potentially two issues here. First, the entire interaction is in the context of a database transaction and quit() exits without committing the transaction. abort() will also abandon the changes but not exit. commit() will commit the changes and not exit, and control-D will implicitly commit and exit. Thus, you need to exit with control-D or commit() before quit(). However, there is another potential issue and that is the one described at <https://stackoverflow.com/questions/37310770/sqlalchemy-committing-pickle-t…>. What this says is the way the *_these_nonmembers attributes are defined in the SQLAlchemy data model results in changes due to mutating the list (which .remove() does) aren't recognized. See <https://gitlab.com/mailman/mailman/merge_requests/505>. I think in your case, if you just do m.accept_these_nonmembers = [] commit() and then look at m.accept_these_nonmembers again which will show you what's in the database, you'll see that you have what you want. -- 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: HyperKitty async tasks runner: systemd qcluster service fails eventually

by Mark Sapiro

On 12/4/19 6:15 AM, actionmystique(a)gmail.com wrote: > Ubuntu 20.04 > mailman3 3.2.2-1 > python3-django-hyperkitty 1.3.0-1ubuntu1 > > According to [Hyperkitty Asynchronous tasks paragraph](https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks), we can start a qcluster systemd service file: ... > [Service] > ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings > User=<user> > Group=<group> > Restart=always Did you replace <django_project_path>, <user> and <group> with appropriate values? ... > Starting it works fine: ... > However, the service fails after a few seconds: > ``` > # systemctl status qcluster > ● qcluster.service - HyperKitty async tasks runner > Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Wed 2019-12-04 15:09:48 CET; 1min 1s ago > Process: 1055961 ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings (code=exited, status=1/FAILURE) > Main PID: 1055961 (code=exited, status=1/FAILURE) It appears you haven't replaced <django_project_path> with the actual path to the directory containing your Django settings.py file Also, <user> and <group> should be those of the Mailman user, probably 'list' in Debian/Ubuntu packages. ... > Also, another doc paragraph [Running the task queue (required)](http://docs.mailman3.org/en/latest/config-web.html#running-the-t…) talks about another required command "python manage.py qcluster"; so which one is it? They should be the same thing. Usually manage.py is just configured to run the django-admin command for the particular project. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

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

by Mark Sapiro

On 5/19/20 4:09 AM, Alan So wrote: > It is exactly the file I used to test (listname and list server munged). I can send you the full header personally if you want. I did a similar test. I used this message exactly ``` From: mark(a)msapiro.net To: list(a)example.com CC: "ABC DEF (XYZ)" <ktso(a)cuhk.edu.hk> Subject: testing please ignore Message-ID: <sfhifdgdfdsjHHIHIo987sd(a)98vD9FVhdv.8shy65FGvsd> Hello ``` and I posted it to the list via `mailman inject`, and the message I received back from the list with some headers removed was: ``` From: mark(a)msapiro.net To: list(a)example.com Message-ID: <sfhifdgdfdsjHHIHIo987sd(a)98vD9FVhdv.8shy65FGvsd> Message-ID-Hash: NUQVMF52CDRIRH4RXEM2VV7MU3HYXASG X-Message-ID-Hash: NUQVMF52CDRIRH4RXEM2VV7MU3HYXASG Date: Tue, 19 May 2020 17:24:34 -0700 CC: "ABC DEF (XYZ)" <ktso(a)cuhk.edu.hk> X-Mailman-Version: 3.3.2b1 Precedence: list Subject: [List] testing please ignore List-Id: <list.example.com> Archived-At: <https://msapiro.net/archives/list/list@example.com/message/NUQVMF52CDRIRH4R…> List-Archive: <https://msapiro.net/archives/list/list@example.com/> List-Help: <mailto:list-request@example.com?subject=help> List-Post: <mailto:list@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello _______________________________________________ List mailing list -- list(a)example.com To unsubscribe send an email to list-leave(a)example.com ``` Note that the Folded CC: header in the received message is exactly the same as in the original message. Are you looking at the raw message received from the list or some MUA's rendering of 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, 2 months

[MM3-users] Re: Problem updating mailman

by Mark Sapiro

On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't remember consciously > installing that because it was never in the guide I followed (which is your > own writeup). > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /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 > CommandError: An error occurred during rendering > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > */bin/sh: sass: not found* You can't just uninstall rubygem-sass. You have to replace it. Here's one recipe for Ubuntu cd /usr/local/lib # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the # appropriate version. wget https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5… sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz sudo chmod -R o-w dart-sass sudo ln -s dart-sass/sass /usr/local/bin/sass rm dart-sass-1.32.5-linux-x64.tar.gz Then you should see the command sass --version prints 1.32.5 Then, because dart-sass doesn't recognize the short form -t option for --style, you have to edit your settings(_local).py and change COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) to COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass --style compressed {infile} {outfile}'), ('text/x-sass', 'sass --style compressed {infile} {outfile}'), ) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Mark Sapiro

On 4/13/22 10:04, bob B via Mailman-users wrote: > > So to confirm my assumptions/findings: > Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent > Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... Correct. > So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? > > If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? To send digests periodically regardless of size, you need to run `mailman digests --periodic` on the schedule you want. This will send the accumulated digest if any for every list that is configured to Send Digest Periodically. Normally, this is run daily via cron. If you want a different schedule for different lists you need to run `mailman digests --list list(a)example.com --periodic` per list on its own schedule. -- 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: possible backscatter attack using Mailman3 servers

by Mark Sapiro

On 1/3/25 16:18, David Newman wrote: > Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing > about 20-30 entries per day in the Postfix queue where it appears a > Gmail user signs up for a mailing list that requires confirmation, and > Gmail responds that the user is too busy to handle requests. > > There are no publicly advertised email lists on this server, and I don't > ever see anything in the Mailman logs indicating the user ever tried > signing up. This is an attack mail bombing the user. The requests that result in the can come via web or email. Mailman's logging of subscribes has been missing most events through Mailman 3.3.10. See https://gitlab.com/mailman/mailman/-/issues/1143 which will be fixed in 3.3.11, but subscribes waiting user confirmation still won't be logged. However, the message with subject "Please Confirm Your Email Address" comes from Django allauth so it isn't actually Mailman sending it but rather Django allauth as a result of a request to sign up for a Django account at https://mail.example3.com/accounts/signup/. You can probably find that request in your web server logs, and you may find the user and/or email in the Django admin UI. Since django-mailman3 1.3.6, you can disable these signups by putting ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in your Django settings, but then your users won't be able to sign up for web accounts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 4 weeks

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 10/02/2017 05:25 AM, Henrik Rasmussen wrote: >> The bottom line is at this point, <https://bugs.python.org/issue27321> >> no longer affects Postorius, but it still affects message delivery. I >> have opened <https://gitlab.com/mailman/mailman/issues/406> about >> defending against that and also the UnicodeEncodeError you included in >> your OP. > > Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? There is no user or list admin workaround, but the defense is a fairly simple patch. See the MR at <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit at <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. The commit changes 7 files, but only two are needed. The rests are tests or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't necessary. The only changes you need are those to mailman/email/message.py and mailman/mta/connection.py. >> No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command >> is 'bin/show_qfiles'. > > I much be in the wrong place because when I do a 'docker exec -it mailman-core bash' and do a 'mailman --help' I don't see a 'queue' argument. The only bin/mailman I have inside the mailman-core container is /usr/local/bin/mailman, which is the same command. My bad. The name is 'qfile', not 'queue'. Sorry about that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Archive import fails: "IndexError: list index out of range"

by Mark Sapiro

On 1/7/23 23:04, Stephen J. Turnbull wrote: > Johannes Rohr writes: > > > IndexError: list index out of range > > That isn't the problem, it's the earlier failure, I think: > > > File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, > > in get_msg_id > > token, value = get_dot_atom_text(value) > > File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, > > in get_dot_atom_text > > raise errors.HeaderParseError("expected atom at a start of " > > email.errors.HeaderParseError: expected atom at a start of dot-atom-text > > but found '@localhost>' > > It appears that HyperKitty is trying to find a domain name (the common > use for "dot_atom_text" in mail headers in a Message-ID), but is > finding "@localhost>" instead. Actually, this occurs after the message has been converted to an email.message with policy=policy.default. Getting the Message-ID attempts to parse it and in this case, the dot_atom_text it's looking for is the 'local part' which doesn't exist. I.e. <xxx@localhost> would be OK, but <@localhost> is not. > First I would try the check_hk_import script which is provided with > HyperKitty. HyperKitty's contrib/check_hk_import script didn't find this issue. The GitLab branch was updated yesterday, but that update is not yet released. An up to date script which does find this issue is at <https://www.msapiro.net/scripts/check_hk_import>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 7/5/22 12:32 PM, Kimmo L wrote: > Hello! > My plan is to install fresh Mailman3 host, which means that i need to migrate/transfer my existing mailman mailing lists + hyperkitty archives to new host. > Unfortunately i didnt find any good documentation about this. > I tried myself to export and import mailmanweb/mailman databases (from old PostgreSQL to new PostgreSQL) and recreate indexes(mailman-web update_index). Now i can see and search hyperkitty archives, but if try to open one of the mailing list, i get error - HTTP Error 500: {"title": "500 Internal Server Error"} > So im pretty sure, that I'm gonna have to transport some more stuff over, which I have no idea. Maybe existing users and user rights. Dumping the databases from the old serverr and loading them on the new server should work. There should be an exception and traceback logged in Mailman core's mailman.log or possibly in the Django (mailmanweb) log. What is logged? > If its not a big trouble, can someone kindly share, what exactly should i need to export/import and what would be the right steps/commands/moves. I thing just dumping and loading the databases and copying mailman.cfg and the Django settings should do it. Are the domains the same on the new server? If not there may be issues with that. I'd need to see the exception and traceback to say 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

[MM3-users] Re: Postfix problem with imported Mailman2 list

by Mark Sapiro

On 3/2/23 13:16, mailman3(a)outofoptions.net wrote: > I installed and tested Mailman3. I imported a Mailman2 list. All looks good but I get this error. > > Recipient address rejected: User unknown in virtual alias table; from=<hit(a)options.org> to=<atm(a)alist.net> > > The aliases seem to show up find in the GUI for the control panel software I use. Postfix virual file has a mapping of atm to atm(a)alist.net . > > It seems mailman at least sees the connection. From the smtp.log under mailman: Presumably there are LHLO, MAIL FROM, and RCPT TO entries before these next ones. > `Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) recip: atm(a)alist.net > Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) Data: b'DATA' > Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) Data: b'QUIT' > Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) connection lost > Mar 02 10:14:13 2023 (1242405) Connection lost during _handle_client() The connection lost entries are normal in the log. This all looks like Mailman's receiving of the message via LMTP from Postfix. This is inconsistent with Postfix reporting Recipient address rejected: User unknown in virtual alias table which would have occurred before any attempt to relay the message via LMTP. In order to understand more about this, I'd need to see at least the output from `postconf -n`. I'm just guessing here, but https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… may be applicable in your case. -- 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: Hyperkitty Replies showing up as new posts

by Mark Sapiro

On 3/5/25 8:55 PM, Arte Chambers via Mailman-users wrote: > Hello, my Hyperkitty is creating a new post for each reply in a thread. I > would expect that new posts to a list would show up in the archive and once > you click on that thread you would see all replies. However in my > Hyperkitty each reply to a thread shows up as its own post usually with the > subject line saying RE: Original Message. How can I set up Hyperkitty to > behave more like the lists.mailman3.org archives where replies to topics > are filed under their respective threads? HyperKitty's threading is based solely on In-Reply-To: headers. It does not attempt to thread based on References: or Subject: matching. Usually this works, but it can fail if for example A posts to a list. B replies off list to A and A replies on list to B's off list reply. In this case, the In-Reply-To: of A's reply is the Message-ID: of B's reply which isn't on the archive, so A's reply starts a new thread, but this is unusual, and HyperKitty has a "Reattach this thread" feature that a list owner or superuser can use to attach one thread to another. However, if this non-threading occurs regularly, It may be that the replyer's MUA is not setting In-Reply-To:. I've seen some phone clients do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin

by Mark Sapiro

On 8/8/19 10:14 PM, Stephen J. Turnbull wrote: > maztec(a)gmail.com writes: > > > Issue: Postfix LMTP does not pass messages onto MM3:LMTP. > > I don't understand why this is a Mailman problem. Seems like Postfix > user lists would be a better venue to get expert help with this. > Among other things, our most responsive Postfix guy is out of cell > coverage for now. I have a window of availability - and it's longer than I thought because my second of three back-country trips has been canceled :( > I would post this To: the relevant Postfix list, Cc: this list, and > set Reply-To and Mail-Followups-To to the Postfix list to get > everybody who can contribute on the same page. I don't have much to add to what Steve has said except our recommended config includes transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp in Postfix main.cf. This should contain (per your log message) things like ListName-confirm(a)ListServer.TLD lmtp:[127.0.0.1]:8024 to tell Postfix to deliver that address via lmtp to port 8024 on the local host. Dovecot should not be involved. There is something in your config that trumps this and delivers via lmtp to Dovecot for mailman3:[127.0.0.1]:8024. Does your transport_maps look like the above or perhaps like ListName-confirm(a)ListServer.TLD mailman3:[127.0.0.1]:8024 If so, I don't know where mailman3 instead of lmtp: comes from. Also, even if it is lmtp: I don't know that Dovecot can deliver via lmtp. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: starting gunicorn per mailman.log yet gunicorn not installed

by Mark Sapiro

On 6/26/23 1:15 AM, Odhiambo Washington wrote: > On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Yes, it makes sense. Mailman 3 core is basically an application which >> manages a webserver that provides the REST API, a database of domains, >> users, and lists, an LMTP server for incoming posts and an SMTP client >> for outgoing distribution. Mailman uses gunicorn to provide the >> webserver. >> >> Installation of gunicorn is handled as a package dependency, so you >> probably wouldn't notice unless you were watching the installation >> process very carefully. >> > > It doesn't make sense, IMHO, because as the OP says, > 1. his ExecStart is: > ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and > not* > ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf > mailman_web.wsgi:application. > > 2. He has not knowingly created any gunicorn.conf > > Why would Gunicorn be Exec-ing itself? :-) As Steve says, Mailman core uses Gunicorn to manage it's REST API. This has nothing to do with whatever WSGI server (uWSGI, Gunicorn, Apache mod_wsgi, ...) is used to support the Django applications (django-mailman3, hyperkitty and postorius). I.e., there is always a Gunicorn instance configured and started by Mailman core, regardless of whatever WSGI server supports Django or even if one isn't running Django at all. -- 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: Unable to update templates

by Mark Sapiro

On 5/27/25 18:54, Mark wrote: > > However when I update the template, the databases are updated correctly > but the Welcome message is still sent with the old template content. > > mailman.templates > mailmanweb.postorius_emailtemplate > > Additionally, if I delete the template and create a new one the old > content still gets sent. > > I cannot find where this content is written or is being cached. The content is stored in the mailmanweb.postorius_emailtemplate table. As far as Mailman core and Postorius are concerned, that's the only place. I'm guessing, but my guess is it's cached in your wsgi server. I.e., upon initial creation an entry is made in the mailman.template table with a uri like https://example.com/mailman3/api/templates/list/list.example.com/list:user:… and when Mailman core wants the template, it gets that uri which I'm guessing is then cached in the wsgi server. Then, if the content is changed, the GET returns the old cached value instead of getting the new value from Postorius. If the template is deleted, the mailman.template table entry is deleted and at that point Mailman core will get the template from the file system following it's normal search rules, but if the template is recreated in Postorius, a new table entry is made with the same uri which may still get a cached template from the wsgi server. If this is correct, restarting mailman-web or whatever controls the wsgi server should fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[MM3-users] Re: Hyperkitty import from mailman2

by Mark Sapiro

> > Now I wanted to try import from mailman2 mbox, so i did: > > python2 manage.py hyperkitty_import --settings settings --ignore-mtime > -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > > It shows that it have sucessfully imported all emails and I can see them > from database (sqlite3), but I cannot see them from GUI (hyperkitty). > Only thing I can see is this inactive "test" list. > > I have tried that I create list before importing, still same result. I have done this several times for several different lists and it has always worked with no problems. I have always created the list first. I do not use any of the options other than -l. My settings location is built in to the django admin script I run. So what I run is equivalent to python2 manage.py hyperkitty_import --settings .. -l .. mbox Do you have cron set up to run the periodic django tasks as in @hourly python2 manage.py runjobs --settings settings hourly @daily python2 manage.py runjobs --settings settings daily @weekly python2 manage.py runjobs --settings settings weekly @monthly python2 manage.py runjobs --settings settings monthly @yearly python2 manage.py runjobs --settings settings yearly 0,15,30,45 * * * * python2 manage.py runjobs --settings settings quarter_hourly * * * * * python2 manage.py runjobs --settings settings minutely If not, did you run python2 manage.py update_index --settings settings after the hyperkitty_import? I'm actually not sure any of this will help since it should only affect the search index, not the message display. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/18/20 3:33 PM, Mark Dadgar wrote: > > Any thoughts on how to salvage ~20 years of list archives? The archives shouldn't be an issue. I don't think they are involved in the corruption, but anyway, hopefully you still have the archive mbox you imported. Then for the messages since then, you should be able to get a mbox from hyperkitty with something like https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… with the obvious substitutions and appropriate start and end dates. The list is trickier. If you are going to start over with a clean install, and if you have a config.pck that you imported from MM 2.1, I suggest the following: Use the `mailman members` command to get a list of all members. Then depending on how much work you want to do, also get separate lists of plaintext and mime digest members and members with delivery disabled. Then on the new install, import the config.pck with `mailman import21` and import the archive mboxes with hyperkitty_import. Run `mailman members --sync` with the full current membership list, and record the [ADD]s. Then you can match the [ADD]s against the plain and mime digest members and those with delivery disabled and set their options. That's a lot to do, but it should get you close. On the other hand, if you can wait, we might be able to figure out how to fix this, and it's even possible the underlying issue isn't database corruption. -- 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: Moderator Approval Subscription template

by Mark Sapiro

On 2/8/21 5:55 PM, Brian Carpenter wrote: > Hey all, > > I am seeing a strange issue with the Moderator Approval Subscription > template. > > 1. First problem is that this template by default does not include a URL > to the list admin page of said mailing list. Mailman 2's notifications did. Mailman 2 was monolithic. Mailman 3 is Modular. Core, which sends this notice, doesn't know if you even have a web admin UI, much less how to access it. It has been suggested that we add a config setting for the web base URL and if that is set, include URLs in these messages and we may eventually do that, but in the mean time > 2. Problem 1 can be solved by editing the template and adding the List > Owner (admin) url to moderate the subscription. This is what you need to do. > However in the case of > long URLs, the URL is getting cut-off in Thunderbird. Not sure about > other email clients. That is an issue because the expanded template is filled and wrapped at column 70 with mailman.utilities.string.wrap(). However, you can avoid wrapping the URL by preceding it in the template with a space. Something like > Your authorization is required for a mailing list subscription request > approval: > > For: $member > List: $listname > > Visit > > https://list.redeacted.org/admin/list/oligodendroglioma.list.redacted.org > > to act on this request. Lines beginning with spaces aren't wrapped. -- 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: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/17/22 15:15, Élodie BOSSIER via Mailman-users wrote: > Hello, > > My mailman3 installation is now functional, but the config "FILTER_VHOST > = True" doesn't work fine when I define "alias_domain" for the 2 > domains. I need to define that because I need to get "postfix_vmap" file. > > As you can see, list from others domains are visible on this URL : > https://ml.franceserv.fr/postorius/lists/ > > I would like https://ml.franceserv.fr/postorius/lists/ and > https://ml.viticreation.fr/postorius/lists/ with their own lists. There are issues with FILTER_VHOST due to the fact that mailing lists do not have a web host attribute. This means when you go to HyperKitty or Postorius when FILTER_VHOST is True, we look up the domain record for the web host you are visiting and show you all the lists whose mail host matches the mail host for the web host domain. This has nothing to do with alias domains. What that means is if all your domains records have a unique mail host, FILTER_VHOST will work as you expect, but if multiple domains have the same mail host FILTER_VHOST will show you the lists for the current web host plus all those with a matching mail host. I.e. if in your case, the ml.franceserv.fr domain and the ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't separate them. If they have different mail hosts FILTER_VHOST will separate them. -- 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: Mailman issues after re-boot

by Mark Sapiro

On 10/4/23 05:09, paulrubin37(a)gmail.com wrote: > Ok first I tried the force reinstall, that changed nothing. > > (venv) mailman@mail:~> pip install --force-reinstall psycopg2-binary\<2.9 > Collecting psycopg2-binary<2.9 > Using cached psycopg2_binary-2.8.6-cp311-cp311-linux_x86_64.whl You are forcing the version to be <2.9 which is why your venvs have 2.8.6. Note you are installing a cached version. That may be why it's broken. You could try ``` pip install --no-cache-dir --force-reinstall psycopg2-binary\<2.9 ``` or as I note below, if your Django is >=3.1 ``` pip install --no-cache-dir -U psycopg2-binary ``` ... > Here is what is in the file that is failing, If I read this right I need to check every single sub import. > > 50 > 51 from psycopg2._psycopg import ( # noqa > 52 BINARY, NUMBER, STRING, DATETIME, ROWID, > 53 > 54 Binary, Date, Time, Timestamp, > 55 DateFromTicks, TimeFromTicks, TimestampFromTicks, > 56 > 57 Error, Warning, DataError, DatabaseError, ProgrammingError, IntegrityError, > 58 InterfaceError, InternalError, NotSupportedError, OperationalError, > 59 > 60 _connect, apilevel, threadsafety, paramstyle, > 61 __version__, __libpq_version__, > 62 ) > 63 This is way too much detail. This psycopg2-binary is broken. You can't successfully import psycopg2 from it. You need to get a working psycopg2 installed rather than trying to fix your broken one. What is your Django version? The only reason for pinning psycopg2-binary<2.9 is for Django<3.1. See https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…. If your Django is >=3.1 try in your venv ``` pip install -U psycopg2-binary ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Search results for query "sapiro"