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

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

by Perry Kollmorgen

Thanks Mark, I will give it a shot. — Perry > > On Nov 28, 2024 at 9:12 AM, <Mark Sapiro (mailto:mark@msapiro.net)> wrote: > > > > On 11/26/24 9:30 PM, Perry Kollmorgen wrote: > > For the code for moderators it currently only adds them: > > mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) > > Would I need to add something similar which sets a delivery_status for the moderator added ? I think something like this ``` mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) moderator = mailing_list._get_membership(moderator.email, 'moderator') prefs = moderator.preferences prefs['delivery_status'] = 'by_moderator' prefs.save() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com > >

4 months, 3 weeks

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

by Mark Sapiro

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

1 year, 5 months

[MM3-users] Re: Mailman Header Behavior

by Samir Faci

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

4 years, 11 months

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

by Mark Sapiro

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

1 year, 4 months

[MM3-users] Re: Member Issue Discovered

by Mark Dadgar

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

4 years, 6 months

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

Ah, so stupid error and so simple solution - thank you! Lars On Tue, Feb 14, 2023 at 12:42:16PM -0800, Mark Sapiro wrote: > On 2/14/23 12:08, Lars Bjørndal wrote: > > > > The domain that doesn't work: > > > > > > <VirtualHost *:80> > > ServerAdmin webmaster(a)list.punktskriftutvalget.no > > DocumentRoot /var/www/list.punktskriftutvalget/ > > ServerName list.punktskriftutvalget.no > > ErrorLog logs/list.punktskriftutvalget-error_log > > CustomLog logs/list.punktskriftutvalget-access_log common > > Redirect permanent / https://list.punktskriftutvalget.no > > </VirtualHost> > > Add a trailing slash > > Redirect permanent / https://list.punktskriftutvalget.no/ > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

2 years, 2 months

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

by Mark Sapiro

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

2 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

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

7 years, 2 months

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

by Mark Sapiro

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

3 years, 11 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Mark Sapiro

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

5 months, 4 weeks

[MM3-users] Re: list admin via email

by Mark Sapiro

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

3 years, 5 months

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

by Mark Sapiro

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

6 years, 9 months

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

by Prasanth Nair

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

2 years, 9 months

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

by Mark Sapiro

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

4 years, 10 months

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

by Mark Sapiro

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

8 months, 3 weeks

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

by Wong, Wesley

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

9 months, 1 week

[MM3-users] Re: mailman import21 passwords

by Mark Sapiro

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

7 months, 1 week

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

by Asaf Ohayon

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

6 years, 11 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

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

2 years, 5 months

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

by Mark Sapiro

On 1/18/22 4:20 AM, Axel Rau wrote: > > While selecting a list in the browser, I’m getting: > - - - > Traceback (most recent call last): > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch > return handler(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get > 'hyperkitty' in archivers and # noqa: W504 > File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ > self[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ > return self._get(key) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get > return self.rest_data[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} The above seems to be from Django's log. What's in Mailman core's mailman.log? > Question: Am I missing aliases in my nginx.conf? > I just have: > - - - > location / { > uwsgi_pass unix:///tmp/uwsgi.sock; > include /usr/local/etc/nginx/uwsgi_params; > } > > location /static { > alias /usr/local/mailman3/static; > } > > location /static/favicon.ico { > alias /usr/local/mailman3/static/postorius/img/favicon.ico; > } > - - - I don't use uwsgi so I'm not sure, but I think the above is OK. This list's host uses gunicorn and has location / { proxy_pass http://127.0.0.1:8000/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } The only locations beyond what you have above are for /robots.txt and /favicon.ico -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Hyperkitty download mbox

by Mark Sapiro

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

3 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did this: (env) [mailman@localhost mailman-suite_project]$ pip install Django Requirement already satisfied: Django in /var/lib/mailman/env/lib/python3.6/site-packages Requirement already satisfied: pytz in /var/lib/mailman/env/lib/python3.6/site-packages (from Django) Does Django is already installed?? with python3.6 ??? El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

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

by Mark Sapiro

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

3 years, 3 months

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

by Mark Sapiro

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

8 years

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

by Mark Sapiro

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

4 years, 7 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

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

2 years, 2 months

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

by Mark Sapiro

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

4 years, 2 months

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mark Sapiro

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

2 years

[MM3-users] Re: One-click unsubscribe?

by Mark Sapiro

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

2 months, 2 weeks

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

by Mark Sapiro

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

6 months, 1 week

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

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

by Mark Sapiro

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

5 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

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

by Mark Sapiro

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

6 years, 5 months

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

by Mark Sapiro

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

2 years, 7 months

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

by Mark Sapiro

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

4 years, 8 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

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

4 years, 7 months

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

by Mark Sapiro

On 1/7/22 3:41 PM, David Newman wrote: > > There are 24 messages in the shunt queue, the most recent of which is a > digest from 0000 hours today. The test messages I sent later today are > not there. > > There are also 13 messages in the out queue. I can't read these as the > filenames appear to change on every invocation of ls. I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/* >> Are there errors and tracebacks in var/logs/mailman.log? Every message in the shunt queue should have an exception and traceback logged in mailman.log. > But the Postfix log doesn't show it being distributed to me or anyone else. Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log? > Oddly, neither of the two list owner emails (me and someone else) show > this message in the archive via the admin panel. However if I log in as > the list owner directly to the archives: > > https://lists.domain.tld/archives/ > > I can see today's test posts if logged in as the list member, but do not > see the posts if logged directly into the archive as the Django superuser. That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can. > The nondelivery of list mail is more serious than the archive problem, > though. Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why? I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory. I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with `mailman qfile` and unshunt (reprocess) them with `mailman unshunt`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Mark Sapiro

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

4 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I made a change for test purpose on the mailman.cfg file and I got this: (env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running? How do I solve this? El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

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

by Guillermo Hernandez (Oldno7)

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

3 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

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

by Mark Sapiro

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

5 years, 5 months

[MM3-users] Re: What to backup?

by Mark Sapiro

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

5 years, 10 months

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

by Mark Sapiro

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

3 years, 11 months

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

by Mark Sapiro

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

2 years, 7 months

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

by Odhiambo Washington

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

3 months, 4 weeks

[MM3-users] Re: Counter-intuitive header filter processing

by Mark Sapiro

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

6 years, 7 months

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

by Mark Sapiro

On 7/23/20 12:39 AM, Shashikanth Komandoor wrote: > Thank you Mark for guiding me to the benefit of putting the list and so I > have added the list. > > Along with the [archiver.hyperkitty], [mta] and [database], few lines of my > mailman.cfg look like below: > > > > [webservice] > workers = 4 > timeout = 900 > > The above block of webservice is added yesterday for testing or trail as I > am getting the above issue. > > And there is no line that is calling *gunicorn* in my mailman.cfg. As I tried to explain to you in an off-list reply: You can't configure Mailman's REST gunicorn workers directly in the [webservice] section of mailman.cfg. The only thing you can configure there is: configuration: /path/to/gunicorn.cfg That file, which is separate from your web server gunicorn.cfg, is where you put things like [gunicorn] timeout = 900 It also will not work to put a gunicorn section in mailman.cfg. It must be in a separate file pointed to by webservice.configuration. Increasing the number of workers won't help this issue. > Apart from that I tried to locate and see the content of the gunicorn.cfg > file as below : > > *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg > [gunicorn] > # All the options that can be put here are available at > # http://docs.gunicorn.org/en/stable/settings.html#settings > > # No of seconds to wait before killing the worker processes. > graceful_timeout = 30 > > Please confirm the time I have to change is *graceful_timeout *in > *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I > have never used or never known about this *gunicorn* but still running the > service in production. First, the file you reference above is the default gunicorn configuration for the REST server. You don't want to edit this file because your changes will be overridden in an upgrade. You want to create your own gunicorn.cfg file and point to it by adding configuration: /path/to/your/gunicorn.cfg to the webservice section in your mailman.cfg. Your gonicorn.cfg does not need to contain the graceful_timeout = 30 setting as that is a gonicorn default, and that is not what you need to increase. What you need is [gunicorn] timeout = 900 (actually 900 seconds is probably way overkill. 90 seconds would probably be enough.) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

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

by Mark Sapiro

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

5 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

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

by Thomas G

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

6 years, 6 months

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

by Mark Sapiro

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

3 years, 1 month

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

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

5 years, 7 months

[MM3-users] Re: Reason for Shunting (SOLVED)

by Brian Carpenter

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

4 years, 2 months

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

by David Partain

Hi Mark, Helpful, as always. Thank you. And do I feel silly. That was pretty darned obvious. In any case, it's fixed. Cheers, David ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 21, 2024 01:46 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples. On 3/20/24 13:23, David Partain via Mailman-users wrote: > raise ValueError("The ADMINS setting must be a list of 2-tuples.") > ValueError: The ADMINS setting must be a list of 2-tuples. > > Our ADMINS setting in /etc/mailman3/settings.py has > > ADMINS = ( > ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), > ) > > Can someone point me in a direction to correct this? 2-tuples, not triples. E.g. ADMINS = ( ('Mailman Suite Admin1', 'someone(a)our.domain'), ('Mailman Suite Admin2', 'someoneelse(a)our.domain'), ) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

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

by Mark Sapiro

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

1 year, 10 months

[MM3-users] Re: re-injecting emails that were not archived

by Mark Sapiro

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

1 year, 9 months

[MM3-users] Re: serving /static-content within /mailman3-web-Folder - change in recent mm release

by Stefan Bauer

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

2 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

[MM3-users] Re: Upgrade

by Darren Smith

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

7 years

[MM3-users] Re: Replies

by Mark Sapiro

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

3 years, 1 month

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

by Stephen Daniel

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

5 months, 1 week

[MM3-users] Re: Mailman-web showing "An error occurred while processing your request."

by Mark Sapiro

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

2 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

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

by Mark Sapiro

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

4 years, 2 months

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

by Mark Sapiro

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

2 months, 3 weeks

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

by Mark Sapiro

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

4 years, 6 months

[MM3-users] Upgrade

by Mark Sapiro

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

5 years, 11 months

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

by Shashikanth Komandoor

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

4 years, 5 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

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

5 years

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

by Mark Sapiro

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

4 years, 5 months

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

by Mark Sapiro

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

1 year, 10 months

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

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

2 years, 8 months

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

by Stefan Bauer

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

3 years, 5 months

[MM3-users] Re: The doubled entries issue

by Mark Sapiro

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

1 year, 5 months

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

by Mark Sapiro

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

8 months, 2 weeks

[MM3-users] Re: list footer questions

by Mark Sapiro

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

4 years, 11 months

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

by Mark Sapiro

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

4 years, 8 months

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

by Shashikanth Komandoor

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

4 years, 5 months

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

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

2 years, 2 months

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

by Mark Sapiro

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

8 years, 10 months

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

by Mark Sapiro

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

4 years, 10 months

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

by Mark Sapiro

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

3 years, 6 months

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

by Mark Sapiro

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

4 years, 10 months

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

by Mark Sapiro

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

3 years, 10 months

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

by Mark Sapiro

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

3 years, 3 months

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

by Mark Sapiro

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

2 months, 1 week

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

by Mark Sapiro

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

4 years, 7 months

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

by Danil Smirnov

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

4 years, 7 months

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

by Christian

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

2 years, 8 months

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

by Mark Sapiro

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

3 years, 2 months

[MM3-users] Re: Apache Conf

by Thomas G

Same result with Alias "/static/" "/opt/mailman/static/" I have sometimes: [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] AH01102: error reading status line from remote server localhost:8000 [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js But it's not systematic. Alias seem to be ignored by the proxy. Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > What's in the apache error log? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 6 months

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

by Thomas Drillich

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

4 years, 11 months

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

by tokyoprogressive＠mailbox.org

Thank you to all for helping me find it. Sent from my iPhone > On Aug 31, 2018, at 1:12, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 08/30/2018 02:59 AM, Simon Hanna wrote: >> >> It is being archived. You can find it here >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> You can see it listed here >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2018/8/ >> >> Hyperkitty has a "little" problem with caching and cache-invalidation... > > > And various searches such as "forum" will also find it. It is unclear > why it doesn't appear in the "Recently active discussions" list on the > overview even though I've stopped and started qcluster, gunicorn (the > wsgi server for Django) and mailman. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

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

by Markus Grandpré

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

2 years, 5 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 12/2/21 21:24, Mark Sapiro wrote: > On 2/12/21 12:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 11/2/21 20:15, Mark Sapiro wrote: >>> For the web UI you need to run the django management `compilemessages` >>> command. >> I tried to run this using the same command as I did for the >> "collectstatic" (that solved all my previous problems for the upgrade) >> and "migrate" runs but it shows me an error: >> >> su -m mailman3 -c "python3 manage.py compilemessages" >> CommandError: This script should be run from the Django Git checkout or >> your project or app tree, or with the settings module specified. > > The documentation is at, e.g., > https://docs.djangoproject.com/en/3.1/ref/django-admin/. Didn't find it. Thanks > If the manage.py in the directory in which you ran this is the correct > one for your Mailman Django project, Yes, it is. > I don't know why it didn't work. :( > > Is your Mailman installed in a virtualenv? No. It's system's wide. Thanks for your answer. > If so, was the virtualenv > activated? >

4 years, 2 months

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

by Mark Sapiro

On 12/8/21 6:05 PM, Philippe B wrote: > Update: After disabling the footer on a few lists (as described here a week ago), we started seeing "Cache content lost" in most (but not all) messages from those lists. > > In some cases, that phrase is an attachment to the "real" body of the message. In others, it's the opposite (which is more problematic for responding). That seems to depend on whether the poster sent in plain text. The difference between inline and attachment has to do with how footers are added. They are only added inline if the message after content filtering is a simple text/plain message. > One puzzling aspect is that it doesn't happen consistently. One hourly automated message will have it; but exactly the same message one hour later won't have it; but will have it again 3 hours later for example. > > Is that a known problem, or would it be possible to troubleshoot? Thanks. The issue may be a bug or a race condition. What is going on is the 'empty' footer you created in Postorius is retrieved from Postorius by a URL. In order to reduce the number of http transfers to retrieve such templates, they are cached in the local file system. Now, when we want a template that is accessed via a non-mailman: URI, we call the cache managers get() method at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/cache.py… to get it. This should return either None if there's no cached file or the contents of the file, but if there is an entry but no corresponding file, it returns 'Cache content lost'. This could occur if some asynchronous process expunged the entry between getting the entry and getting the file. A process that could do that is the task runner that evicts expired cache entries. Look in your mailman.log. There will be `ACCEPT: <message_id>` entries for each accepted message and there will be hourly `Task runner evicted expired cache entries` entries. Do the ACCEPTs for the affected messages occur at the same time as the evictions? One way to avoid this is to not use Postorius to set the template but rather, create an empty `templates/lists/<list_id>/en/list:member:regular:footer.txt` in mailman's var/ directory for each such list and delete the Postorius templates. Of course, this is just a work around and not a solution to the issue. A proper fix is probably to implement a lock on the get(), evict(), evict_expired() and clear() methods so they can't execute concurrently. -- 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: Installing mailman 3

by Rafael Mora

Nice! Up and running! How do I start using mailman? what are the steps?? REALLY thank you all for your patience and help! Really appreciated ! El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:43 PM, Rafael Mora wrote: > > YEEEES! At last!!! I can see the web UI. > > > > Now I´m getting this message in the web UI: > > > > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > > > > > > > Where do I configure the REST API ????? > > > So I guess you figured out that ALLOWED_HOSTS is a Django setting in > settings.py or wherever your Django settings are. > > Now you have to start Mailman Core. In your Python 3 'env' where you > installed Mailman Core, run 'bin/mailman start'. > > -- > 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, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, so how do I config Postfix to send emails via my domain? i.e. using the email account mailing(a)labbrands.com ?? Thanks El mar., 25 jul. 2017 a las 15:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:21 PM, Rafael Mora wrote: > > Regarding this: > > > > # To be added to Django's settings.py > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > EMAIL_HOST = 'localhost' > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = <username> > > EMAIL_HOST_PASSWORD = <password> > > > > > > > > What should I use for username and password? > > Should I keep the localhost on the host param? > > > If you want Django (i.e. Postorius, Hyperkitty and Django > admin/auth/etc.) to deliver via localhost, you don't need > EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. Those are only for > authentication to some other host. > > -- > 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, 8 months

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

by Guillermo Hernandez (Oldno7)

On 19/9/21 3:03, Mark Sapiro wrote: > On 9/18/21 2:52 PM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 18/9/21 22:59, Mark Sapiro wrote: >>> On 9/18/21 11:56 AM, Guillermo Hernandez (Oldno7) via Mailman-users >>> wrote: >>>> >>>> Just a one more silly question: >>>> >>>> Where do I can find the diferent values that memb.moderation_action >>>> can take? (I want to prepare the "unhold" script too) >>> >>> >>> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/act… >>> >> >> Thanks: It's perfect > > > One more thing. It isn't obvious, but generally you want Action.defer > rather than Action.accept. Action.defer will pass the moderation > check, but still continue to check other rules such as administrivia, > implicit-destination, max-recipients, max-size, no-subject and header > filters whereas Action.accept will accept the message unconditionally > and bypass those subsequent checks. Thanks for the tip. I definitely use defer instead of accept now. At least for the use of moderators in a "unhold" stance. --

3 years, 7 months

[MM3-users] Re: Read-Mostly list?

by Stephen Daniel

Thanks. On Sat, Jun 10, 2023 at 2:30 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/10/23 11:02, Stephen Daniel wrote: > > I wish to have a list that anyone can read. A few designated people can > > post without moderation, and all other users are moderated. > > > > Is this possible? I don't see a way in the list settings to create users > > who are not moderated when the default action is to moderate. > > > Once the user is added as a list member, the list owner or site admin > can go to that members settings for the list (click on the user in the > members list) and set the user's Moderation to Default Processing. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to swd(a)pobox.com >

1 year, 10 months

[MM3-users] Re: Open List

by Samir Faci

Awesome, Thank you. On Wed, May 13, 2020 at 12:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/13/20 12:22 PM, Samir Faci wrote: > > So, > > > > I found a setting to allow me to create an Open List. I assume this is > > still doable in MM3 though I can't find the equivalent option. > > > > https://mail.python.org/pipermail/mailman-users/2009-March/065479.html > > > Settings -> Message Acceptance -> Default action to take when a > non-member posts to the list. > > > > 2nd question is how do I create a new List Style. I'd like Open- > Archived > > and Open-NonArchived to be options when creating a new list. > > > See > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… > >. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thank you Samir Faci https://keybase.io/csgeek

4 years, 11 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 20:36, Mark wrote: > >> Did you delete and recreate the template after changing >> POSTORIUS_TEMPLATE_BASE_URL? If not, the template table still has the >> old URI. > > Yes. Every test is: delete template and users (via Postorius), make any > config changes, restart everything, then new template and new user (via > Postorius). OK >> What does `ps -fwwu mailman|grep runner` show? > > # ps -fwwu mailman|grep runner > mailman 375726 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=archive:0:1 > mailman 375727 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=bounces:0:1 > mailman 375728 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=command:0:1 > mailman 375729 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=in:0:1 > mailman 375730 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=lmtp:0:1 > mailman 375731 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=nntp:0:1 > mailman 375732 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=out:0:1 > mailman 375733 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=pipeline:0:1 > mailman 375734 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=rest:0:1 > mailman 375735 375716 0 02:00 ? 00:00:00 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=retry:0:1 > mailman 375736 375716 0 02:00 ? 00:00:00 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=task:0:1 > mailman 375737 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=virgin:0:1 > mailman 375738 375716 0 02:00 ? 00:00:01 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=digest:0:1 > mailman 375790 375734 0 02:00 ? 00:00:00 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=rest:0:1 > mailman 375791 375734 0 02:00 ? 00:00:00 > /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C > /etc/mailman3/mailman.cfg --runner=rest:0:1 So all the runners are running as user mailman. That's good. What exactly is the issue now. Is it retrievals timing out or an empty welcome message? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This my settings.py email config: #DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' # Change this when you have a real email backend # EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = '' EMAIL_HOST_PASSWORD = '' EMAIL_USE_TLS = False DEFAULT_FROM_EMAIL = 'Mailing <mailing(a)labbrands.com>' El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Maximum number of recipients error

by Abhilash Raj

On Mon, Mar 18, 2019, at 10:57 AM, Mark Sapiro wrote: > On 3/18/19 10:40 AM, brian(a)emwd.com wrote: > > I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: > > > > "An error occured: Unknown attribute: max_num_recipients" > > > > I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? > > > It works for me. It was added by > <https://gitlab.com/mailman/postorius/merge_requests/358>, but it > requires Mailman core >= 3.2.1. What's in the docker image you're using? > This may be an issue for <https://github.com/maxking/docker-mailman>. It is an issue for images repo. I haven't yet updated to the latest releases, sorry! > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

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

by "Jörg M. Schulz"

and: When I put the stanza >> [language.en] into the mailman.cfg, the service doesn’t restart: … PermissionError: [Errno 13] Permission denied: '//var/templates' somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? > Am 09.01.2019 um 20:50 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Mark Sapiro wrote: >> >> 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. > > > I forgot to mention that there is a potential downside to the above. Because of the way the Python email library treats UTF-8 message bodies, list messages with UTF-8 bodies are sent with the body base64 encoded. This may or may not be an issue depending on whether you look at raw messages or perhaps grep mailboxes looking for things. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 3 months

[Test] Re: setting up the mailman-users@mailman3.org list

by Mark Sapiro

> I think we are very close to going live with a > mailman-users(a)mailman3.org list. > > I am comfortable that between Postorius and mailman shell I can create > and configure the list. The HyperKitty issues that were blockers for me > have been fixed. > > The one remaining blocker that I see[1] is that Google login doesn't > work. This is reported here > https://gitlab.com/mailman/hyperkitty/issues/73 I have been playing with this. I gave up on Google OpenID and tried configuring Google OAuth2 and Twitter OAuth. I've actually got Google working, so bang on it some. I'm close with Twitter, the issue is it gets all the way back but something is missing when HyperKitty tries to get the user record. The last few lines of the traceback are: File "/usr/local/lib/python2.7/dist-packages/HyperKitty-1.0.4-py2.7.egg/hyperkitty/lib/mailman.py", line 155, in add_user_to_mailman mm_user = profile.get_mailman_user() File "/usr/local/lib/python2.7/dist-packages/HyperKitty-1.0.4-py2.7.egg/hyperkitty/models/profile.py", line 91, in get_mailman_user mm_user = mm_client.get_user(self.user.email) File "/usr/local/lib/python2.7/dist-packages/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 514, in get_user return User(self._connection, content['self_link'], content) KeyError: u'self_link'

9 years

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

by David Newman

On 11/26/21 10:21 AM, Mark Sapiro wrote: > On 11/26/21 9:49 AM, David Newman wrote: >> On 11/25/21 1:16 PM, Mark Sapiro wrote: >>> >>> What django admin command are you running? >> >> As the mailman user, with venv activated: >> >> (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com >> /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox > > > hyperkitty_import is not a command. it is a subcommand to the django > administration command. You need to run > ``` > mailman-web hyperkitty_import -l testlist(a)lists.domain.com > /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox Bingo. Thank you! When running the subsequent 'mailman-web update_index_one_list' command to index the imported archive, the command failed with a permissions error on '/opt/mailman/web/fulltext_index' because that directory didn't yet exist. Creating that directory and chown'ing it to mailman resolved that. I'm still getting an error from the list page when clicking archives, but I'll investigate further and open a new thread if needed. Let's close this already overly long thread here. Thanks *very* much for your patience in resolving the import issue. If nothing else this is good fodder for an eventual admin guide. dn

3 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

[MM3-users] Re: footer message

by Henrik Rasmussen

From lists imported by import21, the colon in the files are substituted with underscores. Instead of list:member:regular:footer.txt the file are called list_member_regular_footer.txt And I wonder why having a footer text makes the mail contain the original HTML message sent to the list as attachment both in .txt and .html and the footer-text from list_member_regular_footer.txt as inline message. 'collapse_alternatives': False, 'convert_html_to_plaintext': False, 'filter_content': False, 'include_rfc2369_headers': True, 'posting_pipeline': 'default-posting-pipeline', -- Henrik Rasmussen her(a)adm.ku.dk University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 1. september 2018 20:17 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: footer message On 09/01/2018 10:51 AM, Abhijith PA via Mailman-users wrote: > > If I understand correctly, temp@lists.example.com:member:regular:footer > file need to created for /temp mailinglist/ ? Not exactly. Assuming default settings and English the file would go in Mailman's var/ directory at var/templates/lists/temp.lists.example.com/en/list:member:regular:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 7 months

[MM3-users] Re: Change delivery_status in bulk

by Hitashi mancho

Thanks, Mark, for the reply. The mailman shell interaction worked for me. Thanks again for your help. On Fri, Apr 4, 2025 at 8:25 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/3/25 19:36, Hitashi mancho via Mailman-users wrote: > > > > Now, I am unable to locate any command or an API call through which I can > > change the delivery_status back to enabled for 1000+ users. > > > > Can you please guide me on how I can do this programmatically using cli > (I > > will write a bash script) or using an API call? > > > See the post at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a mailman shell interaction to do this. > > -- > 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 huhamails(a)gmail.com >

2 weeks, 5 days

[MM3-users] Re: installation choices for mm3

by Mark Sapiro

On 5/16/19 10:33 AM, John Griessen wrote: > I've been reading > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > > and see that a virtual is recommended, which is not something I have > done yet, and wonder > if just putting the mm3 on a different server is easier? I am the author of that document. I started with virtualenv because my first Mailman 3 installation used the now obsolete mailman-bundler and it installed things in virtualenvs. It is not at all necessary to use virtualenv. Note that the first paragraph of the "Installation" section in that document says: For these installs, I opted to install the entire Mailman suite in a virtualenv. The biggest motivation for this choice was the fact that there are already production lists on both servers and using a virtualenv allowed me to do a lot of the work in advance without interfering with the production install. Possibly influenced by these experiences, I am now using virtualenv for all installs. There are pros and cons to using a virtualenv. The big plus is it isolates your installation and avoids conflicts due to the installed software requiring versions of dependencies that are different from those that might be installed and required system wide. It also avoids the need to install as root although things like web server and MTA configuration still require root. The downside is a potentially larger footprint in the file system. > I have a server, mail1.cibolo.us that has postfix, postgresql, dovecot, > mm2, nsd on it. Another server has just web pages and nsd doing backup > DNS for mail1.cibolo.us DNS server. I could do a straight debian > install of mailman3-full on the 2nd server > and keep it simple, let debian setup a blank database installation, > right? Has anyone seen a good write up on how to do that on a debian > server step by step? I can't speak to the installation of the Debian package. It should be straightforward, but I don't really know. The one potential glitch is if you don't have an MTA on the Mailman server. This is doable. Mailman has it's own LMTP server to receive mail and can be configured to use a remote MTA to deliver mail. Mailman also generates transport mappings to control delivery of mail to Mailman and these get updated when lists are added or deleted. There is a configurable postmap_command which is invoked when the maps are updated to update the .db files. That can point to a shell script to rsync the files to the other server if needed. -- 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: Member Issue Discovered

by Apollinaris Schöll

If this has been implemented already then that’s good. I have not tested with latest. Does this also happen when a user unsubscribes or a list admin unsubscribes? > On Oct 28, 2020, at 1:29 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

On 4/1/23 12:44, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I get the same error as before: Did you post this traceback before? If so, I missed it. > root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c > "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r > lmtp" > Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector > Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector > Traceback (most recent call last): > File "/usr/local/bin/runner", line 33, in <module> > sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', > 'runner')()) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1128, in __call__ > return self.main(*args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1053, in main > rv = self.invoke(ctx) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1395, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 754, in invoke > return __callback(*args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/click/decorators.py", > line 26, in new_func > return f(get_current_context(), *args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", > line 184, in main > runner = make_runner(*runner_spec, once=once) > File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", > line 70, in make_runner > return runner_class(name, slice) > File > "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line > 295, in __init__ > self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, > port=port) > File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", > line 417, in __init__ > self._localhost = get_localhost() > File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", > line 66, in get_localhost > with makesock(AF_INET6, SOCK_STREAM) as sock: > File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ > _socket.socket.__init__(self, family, type, proto, fileno) > OSError: [Errno 43] Protocol not supported > The issue is in aiosmtpd which is trying to determine if it can use IPv6 "::1" for localhost. It does this before it checks if we've provided a hostname which we have. The issue is in aiosmtp/controller.py in the get_localhost() function, but it's even deeper than that in socket which is raising the Protocol not supported error. There is something strange on your server in that IPv6 seems to be only partially supported. I don't know for sure what the underlying issue is, but look at https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/controller.py#L49 Find aiosmtpd /controller.py in your venv/lib/python3.?/site-pacakages directory and change that return has_ipv6 line to return False to work around the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 11:00 AM, Mark Dadgar wrote: > On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >> everytime I receive a mail for moderation it says: >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. There's no overall dashboard per se. The message actually refers to whatever web UI you use to manage the list. The default template for this message is non-specific because it comes from Mailman core, and core doesn't know if you are using Postorius or some other web management system or non at all, and even if it were to assume Postorius, it doesn't know the URL. >> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >> >> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? As I said, there is no overall dashboard in Postorius, just the individual list management pages. > This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. I explained above why this is the case, but you can fix it. You do so by making a sitewide template for this message. In the case of this list, we have a template in Mailman's var/templates/site/en/ directory (the default directory for sitewide english templates. This template is named list:admin:action:post.txt and its content on this site is: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: $listname > From: $sender_email > Subject: $subject > > The message is being held because: > > $reasons > > At your convenience, visit > https://lists.mailman3.org/mailman3/lists/$list_id/held_messages Of course, in your case the <https://lists.mailman3.org/mailman3/> part of the URL will be different. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> for the other templates I also install. You can also put domain specific templates in var/templates/domains/$domain/$lc/ which override site templates for the domain and list specific templates in var/templates/lists/$list_id/$lc/ which override site and domain templates for the list, and you can also set list templates via Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Hyperkitty failure?

by Stephen Daniel

Thanks! The thread pointed to at the end of your email, specifically replacing the base URL with http://127.0.0.1:8000/archives did the trick. On Thu, Feb 24, 2022 at 1:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/24/22 09:24, Stephen Daniel wrote: > > > > In the log I see messages that look like this: > > > > Feb 24 11:43:44 2022 (28621) HyperKitty failure on > > https://lists.example.com/archives/api/mailman/archive: <html> > > <head><title>401 Authorization Required</title> > > > What are the exact versions of HyperKitty and mailman-hyperkitty > HyperKitty >=1.3.5 requires mailman-hyperkitty >=1.2.0. Earlier versions > of HyperKitty require earlier versions of mailman-hyperkitty. > > If you have HyperKitty >=1.3.5 and > mailman-hyperkitty >=1.2.0 there is a thread on this at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > See the last two posts in that thread. > > -- > 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, 1 month

[MM3-users] Re: why owner mails rerouted to list

by Mark Sapiro

On 10/22/19 2:20 AM, Tamas HOLCZER via Mailman-users wrote: > Hi All, > > we have moved to Mailman3 from Mailman2 recently, and have a quite > strange problem: > > Every message sent to owners is forwarded to the lists instead of the > owner's mail address. ... > We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian > Buster repo. As MTA we use exim4 (running on the same machine as > Mailman), and have Amavisd on a separate machine for spam filtering. This may be an exim configuration issue. You can stop the mail from being delivered to the list by ensuring the Postorius Settings - Message Acceptance -> Acceptable aliases is empty and Settings - Message Acceptance -> Require Explicit Destination is Yes. This will cause the messages to -owner, etc to be held. First ensure exim, particularly the router for list messages is configured as in <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim4-co…>. > From MYLIST-bounces(a)MYDOMAIN.COM Mon Oct 21 21:13:59 2019 > Return-path: <MYLIST-bounces(a)MYDOMAIN.COM> > Envelope-to: MYADDRESS(a)MYDOMAIN.COM > Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 > Received: from [SPAMFILTER] (helo=localhost) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 > X-Virus-Scanned: by amavis-dc > Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) > by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) > with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200 It seems the issue occurs here. The Received: header below is the receipt of the message from Mailman to MYLIST-owner. That header clearly says the envelope recipient is MYLIST-owner(a)MYDOMAIN.COM. Then the header above looks like the delivery of the message from the Mailman list to one or more list members. What we don't see is the intermediate step of LMTP delivery of the message to Mailman's LMTP server. That delivery must have had envelope recipient MYLIST(a)MYDOMAIN.COM rather than MYLIST-owner(a)MYDOMAIN.COM I think what's missing is `rcpt_include_affixes = true` in the exim transport for Mailman. > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7r-0007pR-JZ > for MYLIST-owner(a)MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 > From: MYLIST-owner(a)MYDOMAIN.COM > To: MYLIST-owner(a)MYDOMAIN.COM -- 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: messages stuck in the bad queue

by Mark Sapiro

On 6/24/23 9:54 PM, Ken Alker wrote: > I am working on a mail server that was migrated from mailman V2 to > mailman V3 in February. I just noticed that there are over 1000 > messages in the bad queue. All of the messages in the bad queue are > dated 2/2/23 and all have a timestamp within a one-hour window of each > other. > > I used mailman qfile to inspect five random emails in the bad queue and > so far they are all "successfully subscribed" emails, This is a bit strange. See below. > but I presume > there are no guarantees there aren't others mixed in there that might be > legitimate emails (ie. I just unshunted 140 emails in the shunt queue > and they were all good emails and all got processed). Presumably these were shunted due to some issue that was subsequently fixed. > I figure that the easiest way to inspect these 1000 emails is just to > have them re-delivered. I tried moving one from the bad queue to the > shunt queue and I ran "mailman unshunt" but nothing happened. What does nothing happened mean? "mailman unshunt" should move the message to the original queue which was stored in the 'whichq' attribute in the msgdata when the message was shunted. Since this wasn't a shunted message, there's no 'whichq' attribute so it goes to the 'in' queue. I.e., "mailman unshunt" would have moved the message from the 'shunt' queue to the 'in' queue. If the message wound up back in the shunt queue, there should be messages in mailman.log indicating why. > Is there a way to reprocess the bad queue? You could just move the messages to the 'in' queue. > Also, what exactly is the bad queue? If Mailman's content filtering is enabled and Filter Action is Preserve, messages which have no remaining content after content filtering are put in the 'bad' queue. These are the only messages put there. When this happens there should a log message like <message-id> preserved in file base <queue_file> It is unclear to me how these 1000+ messages wound up in the 'bad' queue. If you have logs from Feb 2, they might help. My guess is there was some MTA misrouting that caused these list welcome messages (from some mass subscribe?) to be rerouted to the list posting address combined with some bad content filtering settings that removed all the content, but that seems pretty far fetched. -- 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: List in list, mutiple reply-to addresses

by Stefan Bauer

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 Am Mi., 24. Nov. 2021 um 21:53 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/24/21 2:05 AM, Stefan Bauer wrote: > > That is already set. No change. > > This completely removes the reply-to: header and sets the iu-all > > list-address as new and only reply-to. > > > What are your current settings on both the mother and daughter lists for > Anonymous list, First strip reply to, Reply goes to list and under DMARC > Mitigations for DMARC mitigation action and DMARC Mitigate unconditionally? > > > -- > 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, 4 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/27/20 9:52 PM, joseverde(a)gmail.com wrote: > The settings match the Django settings, yes. As far as the rest runner, the following shows on that command: > > root 25868 25475 0 21:50 pts/0 00:00:00 grep --color=auto runner=rest So the rest runner is not running as all you see is your grep command. On 7/27/20 10:34 PM, joseverde(a)gmail.com wrote: > On 7/27/20 10:34 PM, joseverde(a)gmail.com wrote: >> And one last infopoint for tonight, I checked on a whim to see if mailman3 was still running, it wasn't since the last time I checked. (the command mailman status, on the other hand, shows it is up and running. The following error was shown when starting to start: >> >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 88, in process >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: status, lock = master_state() >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 133, in master_state >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: hostname, pid, tempfile = lock.details >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 145, in details >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: with open(self._lockfile) as fp: >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/master.lck' >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Control process exited, code=exited status=1 >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Failed with result 'exit-code'. >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: Failed to start Mailman3 server. >> It appears there is a permissions issue in trying to read the locks. Does your systemd script set the user to the Mailman user, and does the Mailman user have read/write permission on Mailman's var/locks/? Also, is any of Mailman core running? Try ps -fwwA|egrep 'master|runner' If a master is running, try service mailman stop If that doesn't stop it, send it a sigterm or, only if necessary, a sigkill. Then if there are an runners left, sigterm them. Finally if there's anything in var/locks, remove it. Then try to start Mailman. Note that if you've previously started Mailman as root, there may be locks and or other files owned by root that are now inaccessible to mailman. You may need to `chown -R mailman` in Mailman's var directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Does this have anything to do with the problem?: (env) [mailman@localhost logs]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project/logs (env) [mailman@localhost logs]$ tail -f mailmansuite.log File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 204, in hunks precompiled, value = self.precompile(value, **options) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 265, in precompile return True, filter.input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 196, in input raise FilterError(err) FilterError: /bin/sh: sassc: command not found Thanks El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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 El sáb., 22 jul. 2017 a las 22:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/22/2017 05:29 PM, Rafael Mora wrote: > > > > How can I config Mailman/Postfix to send the confirmation email for the > > superuser I created this morning??? > > > What is in Postfix's logs relevant to the attempt to send the mail > (probably /var/log/mail.log)? > > What is the output from 'postconf -n' > > -- > 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, 9 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Mark Sapiro

On 09/14/2018 03:07 AM, Paul Arenson wrote: > Recently I asked my server administrator (large educational organization with many accounts for various sub groups). > > I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. > > He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: > > "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." The initial step is to install a working Mailman 3 on the server. This can be done in a couple of ways. See <http://docs.list.org/en/latest/prodsetup.html> for more detail. It is not clear to me because I don't know much at all about cPanel whether MM 3 can be installed outside of cPanel on the same server or not, and if it has to be installed within cPanel, how that would be affected by cPanel updates if it can even be done at all. > I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. The info at <http://docs.list.org/en/latest/migration.html> covers migration of Mailman 2.1 lists to Mailman 3. The big hurdle is the installation of Mailman 3 which is not covered in that doc. As far as how to migrate from a 'custom' install to an eventual cPanel Mailman 3, that would depend at least in part on the database manager (SQLite, MySQL or PostgreSQL) used. I.e. if your custom install used SQLite and cPanel's used only MySQL, you would have a database migration issue. Some of these questions would be better directed to cPanel itself. Only they can tell you what their Mailman 3 timeline might be or if they even have one. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/12/22 11:45, David Newman wrote: > > To rule out the smtp module, I sent a PGP-signed message using a > different MUA (Thunderbird, in my case). Mailman3 accepted this post > without complaint, and I reported back to list users that this appears > to be an Apple Mail encoding issue. > > Normally, that'd be the end of it. But this is a list for a bunch of > Internet graybeards, including one of the authors of the SMTP protocols > and the subscriber is a former IETF chair. He's grumbling that if this > really were an Apple Mail issue, wouldn't it be far more widespread? Maybe, but who knows. The issue is with at least macOS 12.0.1, Mail.app Version 15.0 (3693.20.0.1.32), and GPG Mail 6.0, Build 2023. That combination at least produces multipart/signed messages with multipart/* parts containing a Content-Transfer-Encoding: header. The Python 3 email library considers this to be a InvalidMultipartContentTransferEncodingDefect() message defect. I had a long exchange with Barry Warsaw about this. an excerpt is It's definitely an Apple Mail issue. Both the message you sent and the original message part have the same defect: InvalidMultipartContentTransferEncodingDefect() Also, My Thunderbird MUA wouldn't display the message content at all. Interesting though that your original message was also signed and sent by Apple Mail and didn't have the defect. It's structure was multipart/signed multipart/alternative text/plain text/html application/pgp-signature and none of the multipart parts have Content-Transfer-Encoding. The follow up you sent with the original message was multipart/signed multipart/mixed * text/plain message/rfc822 (the attached message) * multipart/signed * text/plain application/pgp-signature text/plain (an empty plain text part) text/plain (a quote of my message to you) application/pgp-signature All the asterisked parts have a Content-Transfer-Encoding header which is the defect. It seems to be related to the presence of the empty text/plain part following the signature. > I don't think it would be, because (a) Mailman2 is still far more > pervasive than Mailman3 and (b) the combination of PGP signing and Apple > Mail on MacOS and Mailman3 is still pretty unusual. > > Has anyone else hit this encoding issue, other than the post above? And > did Mailman2 silently accept this because it was less strict about > checking for bad encoding? To my knowledge it's only been hit by Barry and the poster of the original report Mailman 2.1 is has the Python 2 email package which doesn't report InvalidMultipartContentTransferEncodingDefect(). I reported it in November at https://feedbackassistant.apple.com/feedback/9768496 which is open with no reply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: mm3 installation question

by Mark Sapiro

On 3/6/24 1:33 AM, Odhiambo Washington wrote: > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Odhiambo Washington writes: >> >> > The odd thing is that the HOWTO that he followed never involves the >> > manipulation of any urls.py at all - it's not even mentioned at any >> > point. So obviously the issue is caused by something else and I >> > suspect something within Apache needs to be re-evaluated in the >> > guide. The HOWTO installs mailman-web which contains a urls.py. >> >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" >> URI paths. It is quite unclear to me how this works at all with >> either the >> >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> >> version of urls.py or the reverse order version >> >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), This is an issue with Django. I'm not sure of the exact mechanism, but consider the first of the above two sets. If you go to the mailman3/ URL that gets redirected to the postorius/ URL. I.e. two paths that ultimately reference the same thing wind up considering the second path as the canonical path and redirecting the first path to the second. I was not initially aware of this when I added the postorius/ and hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of making either set of paths work, and I added those paths after the mailman3/ and archives/ paths, and this version got released as mailman-web 0.0.8. That caused the recommended Apache config to fail because now the mailman3/ and archives/ paths were redirected to the postorius/ and hyperkitty/ URLs which are not in the recommended Apache config. I have since reordered the paths in mailman_web/urls.py, but that version isn't yet released. Thus the issue. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for some background. > My thinking then is that the documentation at > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > needs to be fixed by adding the missing bits, What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will 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, 1 month

[MM3-users] Re: MIME Digests with posts and index inline likewise Plain Text Digests

by Mark Sapiro

On 1/18/19 5:11 AM, Henrik Rasmussen wrote: > Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. > > Would it be possible for Mailman to send both posts and index inline in the MIME digest? The format of the MIME digest is specified by RFC 2046 which defines the multipart/digest format in section 5.1.5. This defines the MIME digest as a multipart/digest message part containing the individual messages as message/rfc822 sub-parts. It also says (after spelling corrections - ErrataID: 510): Note: Though it is possible to specify a Content-Type value for a body part in a digest which is other than "message/rfc822", such as a "text/plain" part containing a description of the material in the digest, actually doing so is undesirable. The "multipart/digest" Content-Type is intended to be used to send collections of messages. If a "text/plain" part is needed, it should be included as a separate part of a "multipart/mixed" message. The MIME format digest Mailman produces has the structure multipart/mixed text/plain the "masthead" text/plain (only if a digest header) the digest header text/plain the table of contents multipart/digest message/rfc822 the first message message/rfc822 the next message ... message/rfc822 the last message text/plain (only if a digest footer) the digest footer The only change that could be made while keeping the digest compliant would be to combine the masthead, digest header if any and table of contents in a single text/plain part. While this might solve the the issue of the table of contents being an "attachment" in some MUA's rendering, it won't address the larger issue of the messages being rendered as attachments. As you note, Gmail's web mail does an OK job of rendering the MIME digest as do other mainstream MUAs such as Thunderbird. The real solution is for those people who insist on using non-compliant MUAs to subscribe to the plain format digest. The whole point here is if you want a digest which has everything in line, that's what the plain text digest is. If you want a digest which maintains the original structure of the messages without flattening them to plain text, the messages have to be separate message/rfc822 parts. -- 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: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' I have checked if there is already a subscription with that email address, but that's not the case. Best Regards,Eric On Thursday, January 14, 2021, 08:43:54 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/9/21 5:39 AM, Eric Broens via Mailman-users wrote: > For one of our mailinglists we also have a problem with accepting a subscription request. > When Clicking "Accept", we get a 404 Not found error. > See the attached screenshot. > Is there a way to solve this? Content filtering removed your screenshot so we can't see it. What is the URL that gives the 404? How does this compare to the URL of the held message view? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 3 months

[MM3-users] Re: New install - The Message have no valid senders

by Mark Sapiro

On 3/30/22 04:30, kenneth.karlsson(a)eco.cept.org wrote: > > The command: > EHLO contoso.com > mail from: <xxx(a)xxx.com> > rcpt to: <mhtest(a)list.cept.org> > DATA > This is a test message > . Some headers in the message might be nice. > Accepted by Postfix: > Mar 29 11:17:17 lits01a postfix/smtpd[4088]: B86DD6A04B9: client=unknown[192.168.200.157] > Mar 29 11:17:30 lits01a postfix/cleanup[4091]: B86DD6A04B9: message-id=<> In my case, Postfix adds a Message-ID: header and logs it here. > Mar 29 11:17:30 lits01a postfix/qmgr[3952]: B86DD6A04B9: from=<xxx(a)xxx.com>, size=200, nrcpt=1 (queue active) > Mar 29 11:17:30 lits01a postfix/lmtp[4109]: B86DD6A04B9: to=<mhtest(a)list.cept.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=24, delays=24/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 29 11:17:30 lits01a postfix/qmgr[3952]: B86DD6A04B9: removed > > MM receives it: > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) handling connection > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'LHLO list.cept.org' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'MAIL FROM:<xxx(a)xxx.com>' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) sender: xxx(a)xxx.com > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'RCPT TO:<mhtest(a)list.cept.org>' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) recip: mhtest(a)list.cept.org > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'DATA' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'QUIT' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) connection lost > Mar 29 11:17:30 2022 (3940) Connection lost during _handle_client() These log messages come from aiosmtpd which is used by mailman/runners/lmtp.py to implement Mailman's LMTP server. Clearly, aiosmtpd sees the envelope sender as xxx(a)xxx.com, but > But MM3 discards it: > Mar 29 10:08:03 2022 (1767) DISCARD: <164854848338.1768.3954079936807939297@lits01a>; ['The message has no valid senders'] This is because Mailman's NoSenders rule gets an empty response from the messages `sender` method. This means there is no address in any of the messages From:, Reply-To: or Sender: headers which is expected, but it also says that the message's get_unixfrom() method didn't return an address as this is checked between From: and Reply-To:. I tried a similar test, but in my case, Postfix (3.4.13) added Message-Id:, Date: and From: headers, so that wasn't definitive, but I then added logging to the LMTP runner at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… to log the unixfrom and the message and the message did have a unixfrom as added by the LMTP runner, so even without the Postfix added header, it had a sender. -- 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: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Michael Sage

Thanks for your tip about digging deeper into the logs! Turns out it was a postfix issue (the hash files hadn't been created), which was causing it to loop and crash out. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: 12 June 2019 17:56 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup On 6/12/19 9:53 AM, Michael Sage wrote: >> This seems like something I've seen reported before, but I can't find it now. > >> Is anything logged in the various Mailman, Django, Apache logs? > > Nothing at the time in the Mailman, Mailman web or apache (error or > access) logs, I can't find any Django logs I am afraid. I only have > standard logging, happy to turn any debugging logging that you think > might help The Django log is most likely the one named mailman_web. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 10 months

[MM3-users] Re: list owner creation

by Christian Stalberg

Via Postorius. I added the user back using the same page. Thank you! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, February 21, 2021 4:29 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list owner creation On 2/21/21 4:15 PM, Brian Carpenter wrote: > On 2/21/21 6:50 PM, Christian Stalberg via Mailman-users wrote: >> If one inadvertently deleted a list owner account, how could one >> either create a new account and make them a list owner -or- make an >> existing account a list owner? Thanks! > > Are you talking about deleting the account via the Django admin > interface or via Postorius? > Yes, the answer depends on what you did and what tools you have available. For example, if you deleted the owner via the Delete button on the page at <https://example.com/mailman3/lists/list.example.com>/members/owner/>, you can add it back on the same page. You need to tell us what you did. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 2 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Mark, Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow. Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image. The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error... Now answering your questions: ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > do you have django-q in INSTALLED_APPS in your Django settings and what > is set for Q_CLUSTER? > I've checked settings.py inside the container and I haven't found any of the mentioned configurations there. Does the manage.py that's being run here point to the right settings.py? > No clue. Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image? https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Danil > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 1 month

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

by Mark Sapiro

On 12/10/19 5:35 AM, Marvin Gülker wrote: > Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull: > >> I would guess this is in the shunt queue. If there's only one file >> there, you can just delete it. The issue in this case is not a shunted message. it is a message held for moderation. The message itself is in Mailman's var/messages/ directory. It is pointed to by an entry in the database 'message' table. The var/messages/ directory contains two levels of subdirectories and the message files. The file name is the message-id hash. The first subdirectory is the first two characters of the name and the second subdirectory is the next two characters of the name. E.g. a message with message-id hash = UPZXRAAO6Q7HDDJR7LH5NAYTIX57C32X will be stored as a pickle in the file var/messages/UP/ZX/UPZXRAAO6Q7HDDJR7LH5NAYTIX57C32X. The underlying issue here is probably <https://bugs.python.org/issue32330>, but that knowledge doesn't help us. We need to get rid of the offending message in the message store. The first step is in mailman shell. Note the paths /opt/mailman/mm/bin/ and /opt/mailman/mm/var/ will need to be adjusted. /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell >>> import os >>> import pickle >>> for root, dirs, files in os.walk('/opt/mailman/mm/var/messages'): ... for fn in files: ... print(fn) ... with open(os.path.join(root, fn), 'rb') as fp: ... msg = pickle.load(fp) ... print(msg['Message-ID-Hash']) ... This should print the file name and Message-ID-Hash (two lines the same) for each message in the messages directory until it prints only one line followed by the UnicodeEncodeError exception. That list line is the file name/Message-ID-Hash of the offending message. Then you need to run the query DELETE FROM message WHERE message_id_hash = xxx; against the mailman database where xxx is the hash value you found above. > I confess that I haven't visited the held messages page for a very long > time (because I didn't have a reason to; I received no notifications of > held messages). Only after I received the notification that my > errorneous message was being held, I visited it, and I was faced with > the 500 error. If Mailman failed to notify me of held messages > previously, they might have been in hold status already and one of them > might be the cause. As of Mailman core 3.3.0 there is a 'mailman notify' command designed to be run periodically by cron to notify owners/moderators of prnding requests. -- 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: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 14:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:15 PM, Rafael Mora wrote: > > > > Should I configure my private Centos7 server with subdomain > > lists.labbrands.com? > > Doing so how do I redirect the email to the private Centos where postfix > > and MM3 are installed? > > > Create a DNS A record for lists.labbrands.com with the IP of the Mailman > server. You will also want a rDNS PTR record pointing from the IP to > lists.labbrands.com. > Does the rDNS PTR record should be placed in my Centos7 server? I've created the DNS A record for lists.labbrands.com with the IP but I don't know the port that it uses so I can make a port redirect to my local ip address wich is 192.168.1.42, do you know the port????? > > -- > 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, 8 months

[MM3-users] Re: Mailman will not restart

by Christian

Yes, thank you Mark & Peter. I did that and also eliminated locks that were appearing and it is now working. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, March 8, 2023 3:10 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman will not restart On 3/8/23 12:34, peter(a)chubb.wattle.id.au wrote: >>>>>> "Christian" == Christian via Mailman-users <mailman-users(a)mailman3.org> writes: > > Christian> , line 36, in <module> Mar 08 20:17:45 > Christian> zarathustra.ccalternatives.org mailman[31893]: from > Christian> typing_extensions import Concatenate as Concatenate # 3.10 > > You probably need to update the typing_extensions package. inside your > venv. Yes, but why? Something upgraded sqlalchemy > 2.0 but didn't install all its dependencies. The latest versions of sqlalchemy require typing-extensions but sqlalchemy<2.0 didn't require that. So in the venv, `pip install typing-extensions` will probably solve this. -- 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/ 2SXACQYNAHYSUYY4G33PQQDJKKAIBZZM/ This message sent to csa(a)web-analysts.net

2 years, 1 month

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

by Mark Sapiro

To follow up, I received the traceback and the dump of the shunted message off-list. The traceback is ``` Jul 07 21:36:47 2020 (26815) Uncaught runner exception: sequence item 0: expected str instance, Header found Jul 07 21:36:47 2020 (26815) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues) TypeError: sequence item 0: expected str instance, Header found Jul 07 21:36:47 2020 (26815) SHUNTING: 1594138007.5613732+1a5932f41fb4cfcd18c9b0b0ac6f999c84408577 ``` This was apparently caused by an invalid RFC 2047 encoded To: header which encoded the entire header including the address as one base64, unknown-8bit character set encoded word. However, despite trying with several different Python versions, I was unable to recreate the TypeError, so the reason for this exception remains unknown.

4 years, 9 months

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

by Mark Sapiro

On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- 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: moving list from mm3 -> mm3

by Mark Sapiro

On 12/8/23 08:01, Jens Günther wrote: > > This is a nice collection of the configuration of a certain list. Does > anybody know how I would get this data back to the newly created list in > the second working mm3-instance? Shouldn't it be possible via POST > command? I thought of something like: > > curl -u restadmin:restpass -d @short.domain -H "Content-Type: > application/json" localhost:8001/3.1/lists/&short.&domain/config > > But it returns {"title": "405 Method Not Allowed"} and I don't know > where to look in the docs, since it shows almost always a way through > mailman shell. You need a PUT command, not POST. Try the above with `-X PUT`. > ## Members, moderators, owners > > To export all members I normally run within mm-core-container as user > mailman the following command: > > mailman members &short.&domain > &short.txt > > To fill them back in, it can be done in Postorius (or is there a way > through API?). You can use Postorius -> Mass operations -> Mass subscribe to add the members, but you can't do that for owners and moderators. Also you lose information about the members such as Delivery status, Delivery mode and other user settings. > What I would love to know is how to get out Owners of the corresponding > lists and reimport them in the new one (which will be the same at the > end :-D but different instance). You can use the --role option with `mailman members` to get owners and moderators, but short of a custom script, you have to add them manually. > ## registered users > > This part is somehow tricky, since I have no clue how to do it. Some of > the mailinglist-admins don't want to bother their list-owners again with > registering newly on the other system. Is there a way to export all > users (I think I found them in the DB in the table auth_users, somehow > in combination with account_emailaddress) and get them over to the new > instance (actually I just need part of them, but that's another question > that I might solve lateron on my own). > > Maybe the answer is already here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > -> but can somebody help to get this working (import/export)? That is not the answer. Those are Mailman core users, not Django (web login) users. You need to get the relevant entries from the auth_users and account_emailaddress tables and add them to the new DB. -- 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: Enable delivery

by Mark Sapiro

On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… Also see the various tabs at https://www.example.com/mailman3/accounts/subscriptions/ > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

ok, thanks Mark, I'm getting an error doing: (env) [mailman@localhost mailman-suite_project]$ python2 manage.py migrate Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management What do you suggest?? El vie., 21 jul. 2017 a las 14:31, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:07 PM, Rafael Mora wrote: > > Installing mailman-suite for web ui. I did this: > > > > (env) [mailman@localhost ~]$ git clone > > https://gitlab.com/mailman/mailman-suite/ > > Cloning into 'mailman-suite'... > > error: RPC failed; result=22, HTTP code = 404 > > fatal: The remote end hung up unexpectedly > > > > > > but it returned an error, what should I do?? > > > It's another case of incorrect docs. It should be > > git clone https://gitlab.com/mailman/mailman-suite.git > > See <https://gitlab.com/mailman/mailman-suite-doc/issues/15>. > > -- > 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, 9 months

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

by Mark Sapiro

On 6/20/20 1:37 PM, Ruth Ivimey-Cook wrote: > Thanks Mark, Ignore bracketed numbers below ([1], [2], etc.) They come from conversion of the HTML only post to plain text. > On 20/06/2020 03:53, Mark Sapiro wrote: > > 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? > > greyarea-post is the mailman-core and exim server. > > greyarea-web1 is the postorius and hyperkitty server. > > On greyarea-web1, in django-settings.py, > > MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = XXXX > > and both the above-named hosts are also included in ALLOWED_HOSTS along > with localhost. > > On greyarea-post, in mailman.cfg: > > [webservice] > admin_pass: XXXXX > admin_user: restadmin > api_version: 3.1 > hostname: 0.0.0.0 > port: 8870 > use_https: no > > The password and username are as on web1. That all looks good. > Do you see REST requests from the Postorius machine in core's > mailman.log and access.log? > > Yes, there are lots of requests of the form: > > [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 > HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" > > I made a new list using the core CLI, and as a result of navigating > directly to the list archive page I get to see: > > [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk > HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" > > ... but in neither case do I get a complete screen on the browser or > 'follow-up' requests. > > I don't have a file access.log on the greyarea-post. Yes, that's actually a gunicorn log so would only be on greyarea-web1, but the mailman.log tells us the requests are getting to the core REST API, so we don't need that info. > On the greyarea-web1 I have mailmansuite.log with the last few lines: > > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba > se.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co > nnection.py", line 124, in call > 'Could not connect to Mailman API: ', repr(e)) > mailmanclient.restbase.connection.MailmanConnectionError: ('Could > not connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > ERROR 2020-06-03 01:02:06,115 29002 django.request Service > Unavailable: /postorius/lists/ OK. This is telling us that mailmanclient (the REST API Python bindings that Postorius uses to access core) is having trouble establishing a connestion to the core REST server, but it clearly gets there some of the time based on the mailman.log entries. > the uwsgi-error_*.log contains many lines of the form: > > api: url is > [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > api: url is > [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > > My reason for thinking, in my original post, that the wrong host > address is being used is that the ConnectionError above contains > 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as > the listen address on the core web service and does not appear in the > config for postorius. The ConnectionError above comes from requests.request (docs at <https://requests.readthedocs.io/en/master/>). Client only provides a URL in the call to request and the URL is the baseurl + the path and the baseurl is MAILMAN_REST_API_URL which you have as http://greyarea-post:8870. Entries above have http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? I suspect a DNS lookup issue. How does greyarea-web1 resolve greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS rather than relying on /etc/resolv.conf and/or /etc/hosts. -- 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: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 17:06, Mark Sapiro wrote: > On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > The smtp.log I refer to is Mailman's smtp.log which is in Mailman's > var/logs/ directory. There are no entries in the /var/log/mailman3/smtp.log that get created when I try to log in (and authenticate) in Postorius. Jul 28 15:30:18 2024 (516) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 28 15:30:18 2024 (516) Peer: ('192.168.161.103', 54464) Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) handling connection Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) EOF received Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) Connection lost during _handle_client() Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) connection lost Jul 28 15:50:22 2024 (1059) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 28 15:50:22 2024 (1059) Peer: ('192.168.161.103', 34814) Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) handling connection Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) EOF received Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) Connection lost during _handle_client() The recent attempts I made where after 18:00.

8 months, 3 weeks

[MM3-users] Re: Messages disappearing into hole??

by Mark Sapiro

On 8/30/20 6:15 AM, Ruth Ivimey-Cook wrote: > > I looked around the interface and decided to set up the sender as a > non-member, as that appeared to permit them to be "special" and outside > of the normal access rules for the list. Before I did that I could send > a message from this sender and that would be sent to me as list owner > for moderation, so both incoming (from my mailserver) and outgoing (to > it) can be completed. > > However, with a non-member who is auto-accepted the message is passed > from my mailserver to mailman and then disappears. I cannot find > anything in the logs to indicate what happened next. I have tried > setting the default non-member policy to both 'hold' and 'default' with > no change in that behaviour. The logs for the mailserver show the > message being sent to mailman; mailman's "smtp.log" shows an LMTP > message being received ok, and then nothing. > > Any ideas how to find out what is going on? I can share config if that > helps but not sure what would be useful. First, this is a bad way to configure an announce list because anyone can post by spoofing the authorized posting address. The better way is to set a list moderator password and post using an Approved: <password> header or pseudo header. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> for details. As far as the disappearing message is concerned, it's hard to say. What is the non-member's moderation action? Unless it is 'list default' setting the list's default non-member policy has no effect. Also, if the non-member's address or a pattern matching it is in accept_these_nonmembers, that takes precedence over whatever the non-member's moderation action is. One guess about the disappearing message is content filtering may be removing all the message. What is the setting for Filter Action? > As a side-issue, at one point I added a regex matching the sender > address to the acceptable members list, but find that I cannot now > delete it (using postorius): If I delete the field and Save, it returns > on page refresh. There is an issue with Postorius. You can't empty these settings. If you clear the box or or have it contain only whitespace, Postorius won't change the prior setting. In order to remove the only entry in Postorius, you have to replace it with a bogus entry or you can remove it with `mailman shell`. I've just filed <https://gitlab.com/mailman/postorius/-/issues/444> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: archiving problem & updates

by Mark Sapiro

On 2/19/21 7:19 AM, Christian Stalberg via Mailman-users wrote: > I see two messages waiting to be archived. Below is excerpt from the > logfile: > > Feb 10 13:40:49 2021 (974) held message approved, message-id: > <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A(a)mail.gmail.com> > [10/Feb/2021:13:40:49 +0000] "POST > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.1" > [10/Feb/2021:13:40:49 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > [10/Feb/2021:13:40:49 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > [10/Feb/2021:13:40:50 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU > Mailman REST client v3.3.1" > [10/Feb/2021:13:40:50 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > Feb 10 13:40:55 2021 (846) HyperKitty failure on > https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M > </html>^M > (413) > Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M > </html>^M > Feb 10 13:40:55 2021 (846) Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ > _.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ > _.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M The issue is that one of the messages in var/archives/hyperkitty/spool/ is throwing this exception and that effectively stops archiving of new messages. I'm not sure what causes Request Entity Too Large, but I suspect it is a very large message body. You can examine the messages in var/archives/hyperkitty/spool/ with Mailman's `bin/mailman qfile` command, but I suspect the problem is caused by the largest of the files. You can just move it aside, and that should allow archiving to resume. -- 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: Another interesting error...

by Mark Sapiro

On 04/23/2018 01:31 PM, Darren Smith wrote: > So it appears that there was a message sent to one of our mailing lists > that was put into the held message queue. However, when attempting to go to > the message to do the moderation, the web page returns and Error 500. > > Looking in the mailman log, I found this: > > Apr 23 14:21:02 2018 (17878) REST request handler error: > Traceback (most recent call last): > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line 137, > in run > self.result = application(self.environ, self.start_response) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/transac > tion.py", line 50, in wrapper > rtn = function(*args, **kws) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/wsgiapp.py" > , line 214, in __call__ > return super().__call__(environ, start_response) > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", > line 227 , in __call__ > responder(req, resp, **params) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera > tion.py", line 167, in on_get > resource = self._make_collection(request) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" > , line 159, in _make_collection > for resource in collection] > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" > , line 159, in <listcomp> > for resource in collection] > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera > tion.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera > tion.py", line 100, in _make_resource > make_header(decode_header(resource['subject']))) > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in > make_he ader > h.append(s, charset) > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in > append > s = s.decode(input_charset, errors) > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > illegal multibyte sequence > > It LOOKS as if there might be a character in the email somewhere - possibly > in the subject or sender fields? - that is somehow unexpected. It appears that the Subject: header is RFC 2047 encoded and there is an encoded word with charset gb2312 that contains an invalid encoding. The message is apparently defective, but this kind of defect shouldn't cause a 500 error. I can't tell for sure from the traceback if this is Postorius or some other application accessing the REST api. Is it Postorius or something else? > I am attempting to find the held message - can someone point me where I can > go to see the message so that I can see what might be causing the problem? It's in Mailman's database in the 'message' table. -- 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: Editing "automatic responses" tab i Postorius does not work

by David Krantz

But this one is already exposed. But I cannot change it anyway as the tab requires URIs for the different templates to allow saving. I do not use those URIs as I have configured the defaults as I like them. I tried once and it failed so I decided to set the defaults instead. cheers. // David On Sun, May 21, 2017 at 3:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/21/17 5:22 AM, David Krantz wrote: >> >> I am trying to change e.g. the value of "notify admin on membership >> changes" through postorius. > > > There are still many settings not yet exposed in Postorius. We are > painfully aware of this and will probably be working on some of this at > the PyCon sprints starting tomorrow. > > Until we get more of these addressed, you will need to use tools like > "mailman withlist" to set these things. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 11 months

[MM3-users] so many instances of mailman.cfg

by Christian Stalberg

Question: I've five copies of mailman.cfg on my box. How can I tell which one is actually being used please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, November 26, 2021 11:06 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 11/26/21 9:39 AM, Christian Stalberg via Mailman-users wrote: > After the first time where users were unsubscribed automatically, I > added back one at a time all the subscribers who were unsubscribed. > Now they have all been unsubscribed again automatically. They are > valid working email addresses. How can I stop this behavior from occurring please? Do you have the bounce processing notifications `Notify owner on disable` and `Notify owner on removal` set to `Yes`. If not, set them. Then, what's in the notices you receive? You might also consider setting `verp_probes: yes` in the `[mta]` section of mailman.cfg. This will avoid some issues with users being disabled/unsubscribed due to list posts being rejected as spam. -- 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, 4 months

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/23/20 6:32 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As I already said, your suggestion worked well on one list. > > But when I tried to implement the same trick on another list, I > found the below error messages in the mailman.log. > > >> * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno >> 2] No such file or directory: >> '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* >> >> >> *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* >> * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* >> * f = open(self._path, 'rb+')* >> *FileNotFoundError: [Errno 2] No such file or directory: >> '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* >> *During handling of the above exception, another exception occurred:* >> *Traceback (most recent call last):* >> * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, >> in _one_iteration* >> * self._process_one_file(msg, msgdata)* >> * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, >> in _process_one_file* >> * keepqueued = self._dispose(mlist, msg, msgdata)* >> * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line >> 37, in _dispose* >> * process(mlist, msg, msgdata, pipeline)* >> * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, >> in process* >> * handler.process(mlist, msg, msgdata)* >> * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line >> 47, in process* >> * with Mailbox(mailbox_path, create=True) as mbox:* >> * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* >> * _mboxMMDF.__init__(self, path, factory, create)* >> * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* >> * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such >> file or directory: >> '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* >> >> I ran in both the ways you suggested i.e. through "mailman shell" > and "mailman remove". But no luck. > > Could you please suggest me at this point ? Mailman is trying to add a message to the digest of the press.dpr-pb.lsmgr.nic.in list, but the /var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/ directory doesn't exist, presumably because the list has been removed. The question is why is Mailman trying to write to this list's digest.mmdf? Did the above result from unshunting something from before the list was removed? -- 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: slow restart time for mailmanweb

by David Newman

On 12/28/21 7:52 PM, Mark Sapiro wrote: > On 12/28/21 3:51 PM, David Newman wrote: >> On 12/28/21 1:20 PM, Mark Sapiro wrote: >> >> > If so, try adding >> > >> > KillSignal=SIGQUIT >> > >> > to the Service section and see if that fixes it. >> >> root@myhost:/etc/mailman3# time systemctl restart mailmanweb >> >> real 0m1.026s >> user 0m0.008s >> sys 0m0.004s >> >> My limited understanding of SIGQUIT is that it dumps core, but 'find / >> -type f -name '*.core' did not return any core dumps from this event. > > > Actually, SIGINT is probably better, SIGINT does fine: root@myhost:/etc/systemd/system# time systemctl restart mailmanweb real 0m1.024s user 0m0.009s sys 0m0.006s > but they should be equivalent. See > https://uwsgi-docs.readthedocs.io/en/latest/Management.html#signals-for-con… > and > https://uwsgi-docs.readthedocs.io/en/latest/Management.html#stopping-the-se… > > > I'll update the doc. Thank you! > >> Still unsure why the service hung on stop, but thanks! > > It hung on stop because systemd wasn't told how to stop uwsgi so it sent > a SIGTERM which doesn't stop it. Got it. Again, many thanks. dn

3 years, 3 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

On 10/24/23 18:53, Mark Sapiro wrote: > On October 24, 2023 3:47:10 PM PDT, Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 10/24/23 18:29, Mark Sapiro wrote: >>> What if you try this with `mailman-web shell`? >>> >> Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. > > I was confused. I should have said ` mailman shell`, not `mailman-web shell`. Insert "circular problem" here. When I DO NOT have the module loaded in the configuration, `mailman shell` works. Since that was functional, I went into the shell and executed this: > from mailman_customizations.hooks import MailmanCustomizations This worked fine, but obviously importing the class doesn't necessarily *activate* the class. So something is up with how I'm *supposed* to activate the plugin in the config, and we know that it's visible to Mailman in its shell, but it can't autoload it. So, again, not sure where to look next for debugging. Thomas

1 year, 5 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:13 PM, Paul Arenson wrote: > Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used: > > The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) > > 1) So, for both subscribers vi postorius only and hyperkitty users: > email to discuss-leave(a)list.tokyoprogressive.org (or > discuss-unsubscribe(a)list.tokyoprogressive.org) Yes, but you seem to have some confusion about how things work. Mailman 3 consists of several pieces. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/introduction.html…>. As it says there, Postorius and HyperKitty are separate, web based applications for list management and archiving respectively. Both of these are Django projects - Django is a Python web framework. What you refer to as hyperkitty users are actually Django Users. When you create and account and/or log in at Postorius or HyperKitty, you are creating/logging in to a Django account. When you are logged in, Django, and thus Postorius and HyperKitty know who you are. If you aren't logged in, they don't. > 2) Only for hyperkitty users, you can login, go to > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > and click the big red unsubscribe button. You need to be logged in for this so Postorius knows who to unsubscribe. > 3) Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/ and click the Delete > Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/delete This deletes your Django account, but does not affect your list memberships. > (Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?) That's right. The important thing is Postorius itself knows nothing about lists or list settings or list members. It gets and/or sets this information by communicating with Mailman core. You saw an example of this when you changed an archive from public to private. Postorius told Core to make it private and Postorius would then tell you it was private because it would get that information from Core. But, it required a daily cron job to propagate that setting to HyperKitty, so HyperKitty didn't get the memo until later. I hope this helps rather than adding confusion. -- 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: Apache+mod_wsgi issue

by Mark Sapiro

On 12/24/22 00:00, Odhiambo Washington wrote: > > These are my files: > 1. urls.py > <CUT > > from django.conf.urls import include > from django.urls import re_path > from django.contrib import admin > from django.urls import reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > re_path(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > re_path(r'', include('django_mailman3.urls')), > re_path(r'^accounts/', include('allauth.urls')), > # Django admin > re_path(r'^admin/', admin.site.urls), > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ] > </CUT> You don't need all of those. ^postorius/ and ^mailman3/ are two different ways to access Postorius, and ^hyperkitty/ and ^archives/ are two different ways to access HypereKitty. You only need one of each, but having both is OK. > 2. apache.conf > <CUT> > ... > Alias /static "/opt/mailman/mm/static" > <Directory "/opt/mailman/mm/static"> > Require all granted > </Directory> > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > WSGIScriptAlias / /opt/mailman/mm/wsgi.py This will send every http request to mod_wsgi except for requests to /static. This is OK if there are no other web sites on this server and the only http requests are for Django related things. ... > I have tested with creating all those commented out aliases and that ended > up still giving me /mailman3/mailman3/* which I did not > like, although everything appeared to work. > I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" > and now when I type https://mm3-lists.kictanet.or.ke I end > up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course something > has appended "/mailman3" > So this has resulted in all URLs having /mailman3/ appended, except for the > /archives link. How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > Now my question is about what could be adding the /mailman3. Is it possible > that I installed something out of the ordinary? It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time (I now use gunicorn on all the sites I manage), but when I did I think I had WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py and all the URLs were like https://example.com/mm3/mailman3/..., https://example.com/mm3/archives/..., etc. -- 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: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Johannes Rohr

Am 24.01.2023 um 01:26 schrieb Mark Sapiro: > On 1/23/23 14:00, Johannes Rohr wrote: >> >> Am 23.01.23 um 21:08 schrieb Mark Sapiro: >>> e.g. >>> ``` >>> HAYSTACK_CONNECTIONS['default']['PATH'] = >>> '/opt/mailman/mm/var/fulltext_index' >> >> Thanks! Indeed. Including this line helps. It makes the error go >> away. So I guess the instructions should be amended. >> >> After that, for some reason, I have to re-index all lists, because >> initially, empty results were returned for any query, only after >> re-indexing to I get results. > > Did you adjust the path to point to your existing fulltext_index? yes, I did. > If not and if you had, I don't thing you would have needed to reindex. That's precisely, why I was surprised. > > The question is what changed so that the relative "fulltext_index" no > longer pointed to where the actual directory was. I don't think that anything had changed, I just don't think I never checked whether the fulltext search actually works and so I spotted this error rather late in the game. Thanks, Johannes > >

2 years, 2 months

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

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

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

by Odhiambo Washington

On Fri, Dec 30, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/29/22 23:17, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> The default without the since= option is to import only those messages > >> from the mbox which are newer than the newest message in the existing > >> archive which is exactly what you want. > >> > > > > So I ended up using this and I can see the list metrics indicating that > the > > last post was on 29Dec22, but > > I don't seem to be able to see those posts in the archives. > > > If Postorius list metrics show the last post was 29 Dec, that was a post > to the MM3 list and if it was archived, then running hyperkitty_import > without a since= option will not import any messages older than that. > Is there a way to delete the whole archive and re-import afresh? I checked the django-admin options for hyperkitty and did not see any such option. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/27/23 23:53, Odhiambo Washington wrote: > > I have reread what you wrote now and I'm beginning to get the hang of this > method. > My observation is that it can only be _obvious_ to someone very familiar > with Python config > to decipher that *additional* settings *that can be augmented or overridden > in /etc/mailman3/settings.py* can be obtained from: > /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed > these two lines in > the sample settings given in /etc/mailman3/settings.py: > > from mailman_web.settings.base import *from > mailman_web.settings.mailman import * This is how it was always done in Mailman 2.1 and how it should have been done in Mailman 3's Django web UI from the start, but wasn't. MM 2.1 had mm_cfg.py which had ``` from Defaults import * ################################################## # Put YOUR site-specific settings below this line. ``` > [At first instance, it is not obvious that mailman_web.settings.base and > mailman_web.settings.mailman are > actually paths in Python - which magically translates to > mailman_web/settings/base.py and mailman_web/settings/mailman.py] This is very basic Python. > Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. > > For example, my mind all along has been tuned to having a settings_local.py > for overriding the settings.py. > However, with this particular documentation, it would appear that > everything is intended to just go into /etc/mailman3/settings.py. In that method you had the defaults in settings.py which at the end imported settings_local.py. This method has defaults in /PATH-TO/mailman_web/settings/{base|mailman}.py and those are imported at the beginning of settings.py which then has overrides. This is preferable because it allows things in settings.py like ``` HAYSTACK_CONNECTIONS['default']['PATH'] = 'some path' ``` to just override that one thing rather than having to redefine all of HAYSTACK_CONNECTIONS or import it from settings in settings_local.py. > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, > that those two "import *" _DO establish a base set of settings that can be > augmented or overridden in /etc/mailman3/settings.py_ > and that those settings are in what file(s) ? Again, this is very basic Python, but if you submit a merge request to update https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, we'll certainly consider 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, 2 months

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 10 months

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

by Odhiambo Washington

On Tue, Jan 31, 2023 at 9:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:43, Mark Sapiro wrote: > > > > add another section header > > > > Regular Expression Tables > > ------------------------- > > > > and change that text to > > > > Regular Expression tables are less efficient than hash tables, but they > > remove the additional dependency of having ``postmap`` command available > > to Mailman. If you want to use ``regexp`` or Regular Expression tables, > > then add the following to Postfix's ``main.cf`` file > > > This is now done. > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > That is now quite clear, but I still have one question and this is cosmetic (because Postfix isn't my MTA of choice. You can ignore it if it feels like spoon-feeding a Postfix admin. In the section: ``` https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… ``` .. the Postfix admin had to figure out whether they are using hash or regex tables and modify accordingly, right? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 2 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Jered Floyd

Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home from another episode of turkey overconsumption. I confess that I am not a python expert - once I create a new list, what’s the easiest way to inspect the object state? --Jered > On Nov 25, 2023, at 18:28, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/25/23 8:01 AM, Jered Floyd wrote: > >> This suggests that new lists in 3.3.9 may be getting mlist.dmarc_addresses set to None rather than an empty list (which seems to be expected). > > > How did you create this list? > > I have tried and when I create a new list it has mlist.dmarc_addresses set to an empty list. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

1 year, 4 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Thu, Dec 29, 2022 at 3:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 11:37, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 21:46, Odhiambo Washington wrote: > >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >>>> > >>>> I see from another post that you've decided against using Twitter, but > >>>> to answer the question, Twitter does not require adding anything to > >>>> SOCIALACCOUNT_PROVIDERS. > >>>> > >>> > >>> I tried it and ended up with: > >>> > >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server > Error: > >>> /accounts/twitter/login/ > >>> Traceback (most recent call last): > >> ... > >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > >>> query does not exist. > >> > >> > >> Do you have > >> > >> 'allauth.socialaccount.providers.twitter', > >> > >> in INSTALLED_APPS? > >> > > > > Here is what I have in settings_local.py: > > > > INSTALLED_APPS = ( > > 'hyperkitty', > > 'postorius', > > 'django_mailman3', > > # Uncomment the next line to enable the admin: > > 'django.contrib.admin', > > # Uncomment the next line to enable admin documentation: > > 'django.contrib.admindocs', > > 'django.contrib.auth', > > 'django.contrib.contenttypes', > > 'django.contrib.sessions', > > 'django.contrib.sites', > > 'django.contrib.messages', > > 'django.contrib.staticfiles', > > 'rest_framework', > > 'django_gravatar', > > 'compressor', > > 'haystack', > > 'django_extensions', > > 'django_q', > > 'allauth', > > 'allauth.account', > > 'allauth.socialaccount', > > #'django_mailman3.lib.auth.fedora', > > #'allauth.socialaccount.providers.openid', > > 'allauth.socialaccount.providers.github', > > #'allauth.socialaccount.providers.gitlab', > > 'allauth.socialaccount.providers.google', > > 'allauth.socialaccount.providers.facebook', > > 'allauth.socialaccount.providers.twitter', > > #'allauth.socialaccount.providers.stackexchange', > > ) > > > Did you add an app at https://site.name/admin/socialaccount/socialapp/ > with twitter as a provider? See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… Exactly, and I have entered all the credentials from the "OAuth 2.0 Client ID and Client Secret" of the twitter developer portal. https://webmail.kictanet.or.ke/~wash/twitter-oauth.png I have checked my settings_local.py several times trying to find out why the entry is ignored. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 11 months

[MM3-users] Re: Apple Mail encoding again

by David Newman

On 4/14/22 10:45 AM, Mark Sapiro wrote: > On 4/14/22 10:18, David Newman wrote: >> On 4/14/22 9:50 AM, Mark Sapiro wrote: >>> >>> It could accept a defective message or one with specific defects, but >>> this is problematic for further processing. For example, at least one >>> MUA, Thunderbird, renders such a message with an empty body. >> >> That's not my experience. Mailman 3 accepted without complaint a >> PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to >> list subscribers with the message body intact. > > > Yes, and that's what we expect, but MM 3 does not accept the defective > message, and T-bird does not render the body of such a message. I.e., if > such a message composed by Apple Mail 15 is sent via a non-Mailman > channel to a T-bird user, the user can't read it. Sorry, I misspoke. The Apple Mail sender used S/MIME signing, not PGP signing. In Thunderbird, I was able to read an S/MIME-signed message the user sent directly to me complaining about the 501 bounce. Thunderbird said the signature was invalid due to the use of an untrusted CA, but I could read the message body. dn

3 years

[MM3-users] Re: Permission denied for /list:member:digest:header.txt

by Eric Broens

Thanks again Mark, from the bash_history that seems to be the case, while I intended to run it as mailman user.It looks like only the ownership of the subdirectories and files in /var/lib/mailman3/templates are incorrect.Those in /var/lib/mailman3/lists and other directories are correct. I can't find back if I have changed the ownership of these manually. Is it sufficient to change the ownership manually, or is there another change required too? Best Regards,Eric On Monday, December 14, 2020, 01:59:06 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/14/20 3:19 AM, Eric Broens via Mailman-users wrote: > Thanks Andi, > I understand that it is a Unix permissions issue.The question is, what process created these files and directories? Mailman runs with its own user. Since these files and directories were created automatically, I expected that these would have been created with the correct permissions. You ran the hyperkitty_import job for these lists as root. It needs to be run as the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

[MM3-users] Re: Migration from 2.1 to 3

by Ryan Morash

I figured it out. It was a stupid mistake on my part, running the ‘mailman create’ commands as root… chown’ing the /var/lib/mailman3/lists directories to lists:lists solved the issues. From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, January 8, 2020 at 1:20 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Migration from 2.1 to 3 On 1/8/20 6:38 AM, Ryan Morash wrote: > I'm running into the same issue, but after some troubleshooting I think the issue isn't with the import21 command. I'm running into the same issue when I create a list using 'mailman create' without importing anything. New lists created through Postorius work fine. Can you please post the `mailman create` command options you are using to create the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

5 years, 3 months

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/25/23 1:31 PM, Ken Alker wrote: > > I moved the .psv file from the bad queue into the shunt queue. I then > ran "mailman unshunt" (as user 'mailman' while in the virtual > environment). I tailed mailman.log during this process and no logs were > spit out. The date stamp on the .psv file never changed (maybe it does > not when being moved between queues?) and, AFAICT, the file never moved > from the shunt queue. I waited maybe five minutes, tops. I forgot that the extension in the `bad` queue is `.psv` (for preserve). You have to rename it to `.pck`. >>> Is there a way to reprocess the bad queue? >> >> You could just move the messages to the 'in' queue. Changing .psv to .pck in the process. this can be done, e.g., by ``` for file in `ls var/queue/bad/*.psv;do mv /var/queue/bad/$file /var/queue/in/${file/psv/pck};done ``` > I just now tried moving the same message into the 'in' queue but, again, > nothing happened. I left it in there for five minutes. Do I have to > run a program to get it to act on the 'in' queue (I presume that there > is a "runner" that is always looking and taking care of this already as > I presume this is the queue where all 'normal' traffic is handled). Again, you need to change the extension to .pck. > Here are the (obfusacted) results of "mailman qfile > /opt/mailman/mm/var/queue/shunt/1675389793.6945386+2aeaf0015558c9d8380c96142c3fa9d03a8142bc.psv" (the message I was experimenting with): > > [----- start pickle -----] > <----- start object 1 -----> > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Subject: THE-list subscription notification > From: email(a)obfuscated.com > To: the-list-owner(a)lists.obfuscated.com > Message-ID: <167538979369.2390432.521344217673230839(a)obfuscated.net> > Date: Thu, 02 Feb 2023 18:03:13 -0800 > Precedence: bulk > > user(a)domain.tld has been successfully subscribed to THE-list. > > <----- start object 2 -----> > { '_parsemsg': False, > 'envsender': 'email(a)obfuscated.com', > 'listid': 'the-list.obfusacted.com', > 'nodecorate': True, > 'recipients': {'person(a)domain.tld'}, > 'reduced_list_headers': True, > 'version': 3} > [----- end pickle -----] I was assuming these were list welcome messages which they aren't. They are owner notifications, so they were sent to the -owner address and processed through the owner-pipeline, but unless the Debian package changed the default-owner-pipeline, it doesn't contain mime-delete so how they ended up in the `bad` queue is still a mystery. However, what would be the point of resending these at this time? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

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

by Ryan McClung

That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db? On Tue, Jul 31, 2018, 4:22 PM Mark Sapiro, <mark(a)msapiro.net> wrote: > On 07/31/2018 12:39 PM, Ryan McClung wrote: > > I do see the output of the script and it shows the mailing lists being > > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > > > Also, to that end, the output of lists changes depending on which > directory > > I am in which makes 0 sense. > > > That is the problem. Either your mailman.cfg does not specify a fixed > directory for var_dir or the mailman command(s) you run do not specify a > fixed mailman.cfg. > > If you look, you will probably see a var/ directory is every directory > in which you ran a 'mailman' command and they will all have different > databases, etc. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 8 months

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

by Shashikanth Komandoor

Thank you Mark for your response. All the mentioned versions of all the components are taken from my currently running system only in which I am facing the issue. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 10:54 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 12:46 AM, Shashikanth Komandoor wrote: > > > > *### Mailmanclient Version ###* > > > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > > *Merge: ff39dd8 8670751* > > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in > >>* > > *Date: Thu Oct 15 01:09:32 2020 +0000* > > > This mailmanclient is up to date and does define the get_requests_count > mailing list attribute, so this version must not be whats running in > your mailman installation. Did you install it? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 5 months

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 7/14/20 3:54 AM, Brian Carpenter wrote: > On 7/14/20 6:49 AM, Gilles Filippini wrote: >> Mailman Core logs: >> [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) >> [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) >> [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 > > I am pretty sure that timeout is related to gunicorn. If it is, then > increasing the worker out timeout setting for gunicorn should work. You > tend to get such errors when doing an export of a large membership > roster. This is the first time I have seen it related to a held message. It seems weird that a gunicorn worker would run for more that the default 30 seconds because of a 23MB message, but I think Brian is correct. > I have this in my setup: > > mailman.cfg: > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > gunicorn.cfg: > > [gunicorn] > workers = 4 > timeout = 900 > > You will need to restart gunicorn after adjusting the timeout setting. It's confusing, but after adjusting that setting, you need to restart Mailman core, not gunicorn. If you are running a gunicorn service, that is what is providing WSGI support for Django (Postorius and/or HyperKitty). You may be using gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is not the gunicorn we are considering here. Regardless of what you use to provide WSGI support for Django, Mailman core uses gunicorn to support the REST API, and that is the gunicorn affected by the settings in the gunicorn.cfg pointed to by [webservice] configuration: /opt/mailman/mm/gunicorn.cfg If, with the above configuration, you do `ps -fwwA|grep runner=rest` you will see something like: mailman 20582 20561 0 01:21 ? 00:00:16 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20722 20582 0 01:21 ? 00:01:19 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20725 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20726 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20727 20582 0 01:21 ? 00:01:50 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 The first of these, pid 20582, is Mailman's actual REST runner. The other 4 with parent pid 20582 are the 4 gunicorn worker processes forked from the REST runner. It's the REST runner or Mailman core that needs to be restarted to pick up that change. -- 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: Domain Issue with MM3

by Mark Sapiro

On 10/23/19 12:53 PM, Liebeskind Uri (luri) wrote: > > I have setup this mailing list test(a)digital.lists.zhaw.ch but subscribing failed. How did you create the list and the digital.lists.zhaw.ch domain in Mailman? > * Subscribing via the Mass Import Form failed with a Server Error message in the browser. Log messages may help here. I can't tell you where to find them in your installation, but your Django settings or local settings will define LOGGING['handlers']['file']['filename'] which is where your Django logs are. and your various Mailman logs are generally in Mailman's var/logs/ directory. You may find a traceback from this error in the Django log or in Mailman's error.log or access.log. > * Subscribing via e-mail test-join(a)digital.lists.zhaw.ch<mailto:test-join@digital.lists.zhaw.ch> because no response came from MM3. This is Postfix. See below. > The mail to join has been delivered properly to MM3 but MM3 has swallowed the mail w/o response or error message. There also has not been any pending subscription. MM3 did respond. See below. > 2019-10-23T19:51:33.678705+02:00 svma-s-01321 postfix/smtpd[98348]: connect from srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.692258+02:00 svma-s-01321 postfix/smtpd[98348]: A8EFC3FA6A: client=srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.693192+02:00 svma-s-01321 postfix/cleanup[98351]: A8EFC3FA6A: message-id=<eb90deb6-58af-a873-3382-c27ce6d05031(a)anydomain.org> > > 2019-10-23T19:51:33.704102+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: from=<name(a)anydomain.org>, size=5329, nrcpt=1 (queue active) > > 2019-10-23T19:51:33.704864+02:00 svma-s-01321 postfix/smtpd[98348]: disconnect from srv-mail-013.zhaw.ch[160.85.104.123] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > > 2019-10-23T19:51:33.763670+02:00 svma-s-01321 postfix/lmtp[98352]: A8EFC3FA6A: to=<test-join(a)digital.lists.zhaw.ch>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.08, delays=0.02/0.01/0/0.05, dsn=2.0.0, status=sent (250 Ok) Per the above the message was delivered to Mailman. > 2019-10-23T19:51:33.764485+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: removed > > 2019-10-23T19:52:29.278529+02:00 svma-s-01321 postfix/smtpd[98348]: table hash:/var/lib/mailman3/data/postfix_lmtp(0,lock|fold_fix|utf8_request) has changed -- restarting Why all these table changes/restarts? > 2019-10-23T19:52:29.286154+02:00 svma-s-01321 postfix/smtpd[98558]: connect from localhost[127.0.0.1] Mailman has connected to Postfix. > 2019-10-23T19:52:29.288612+02:00 svma-s-01321 postfix/cleanup[98351]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.292655+02:00 svma-s-01321 postfix/smtpd[98558]: 476AD3FA6A: client=localhost[127.0.0.1] > > 2019-10-23T19:52:29.293671+02:00 svma-s-01321 postfix/cleanup[98559]: 476AD3FA6A: message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> And delivered its response, message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> to Postfix. > 2019-10-23T19:52:29.296393+02:00 svma-s-01321 postfix/qmgr[90603]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.298231+02:00 svma-s-01321 postfix/smtpd[98558]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4 So the message was delivered to Postfix with the four commands ehlo, mail, rcpt and data. This is normal. What did Postfix do with the message? -- 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: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Fri, May 3, 2024 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > Mark Sapiro wrote: > > > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = > 13; > > delete from hyperkitty_mailinglist where id = 13; > > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > > 'list.lists.nog.ke' where id = 2; > > Or instead of that you could just go to the new list(a)lists.nog.ke > archive in HyperKitty and delete it and then just do the > ``` > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; > ``` > I went with this approach and worked super! Thank you. So, seeing as deleting a list retains its archives, if I want to delete a list together with its archives, do I first delete the archives, then follow with the list? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 2 weeks

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

by Helio Loureiro

Hi, I forgot to mention that, but there is no mailman-web on ubuntu packages on 18.04. So I can't find a way to run it. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 10:19, Jered Floyd wrote: > > > > Did you run the upgrade steps? > > > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > > > For schema upgrades you will at least need to do "mailman-web migrate", > but please read the entire section as 3.1.1 to 3.3.9 is a big step. > > > These are all important and necessary steps, but "mailman-web migrate" > updates schemas for the mailman-web database. It does not update the > alembic migrations for the mailman database. > > -- > 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, 4 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote: > > I looked at Django Admin and Postorius and I see all my MLs in both. What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database. > What I am sure about is that I did NOT create my MLs using Django admin UI. > I either created them using the CLI or Postorius. > Having said that, I did run two tests: > 1. Create a ML in Postorius and check whether it appears in Django admin - > The list was visible in Django Admin Because the list you created had the hyperkitty archiver enabled. > 2. Create a ML in Django admin and check whether it appears in Postorius - > The list was NOT visible in Postrorius Because it's only in HyperKitty. > 3. Create a ML in CLI and check if it appears in both Django admin and > Postorius - List is visible in Postorius, but not in Django admin Becayse this list did not have the hyperkitty archiver enabled. > ``` > MariaDB [mailmansuite]> select list_name, list_id from mailinglist where > list_name like 'ulf%'; > +-----------+-------------------------------+ > | list_name | list_id | > +-----------+-------------------------------+ > | ulftest2 | ulftest2.lists.kictanet.or.ke | > | ulftest3 | ulftest3.lists.kictanet.or.ke | > +-----------+-------------------------------+ > ``` These are only Mailman lists. > The list that I created using Django admin is NOT listed here! Because it's only in HyperKitty. > ``` > MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist > where list_id like 'ulf%'; > +-------------------------------+-------------------------------+ > | list_id | name | > +-------------------------------+-------------------------------+ > | ulftest1(a)lists.kictanet.or.ke | ulftest1(a)lists.kictanet.or.ke | > | ulftest2.lists.kictanet.or.ke | ulftest2(a)lists.kictanet.or.ke | > +-------------------------------+-------------------------------+ > ``` > The list I created using Django admin and the one I created using > Postorius are both listed, but the one I created from CLI is not listed. Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the `new_lists_from_mailman` job runs even though hyperkitty is enabled. > So there must be some logic behind this. However, I don't know what it is. The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty. Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the `new_lists_from_mailman` job runs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 12:26 PM, Mark Sapiro wrote: > On 7/7/22 11:10 AM, David Newman wrote: >> On 7/7/22 10:25 AM, Mark Sapiro wrote: >> >> pip install -U mailman postorius django-mailman3 hyperkitty >> mailman-web uwsgi >> >> and it downgraded Django back to 3.0.14. > > > Because mailman-web 0.0.5 has in its setup.cfg > ``` > install_requires = > Django<3.1 > ``` > try > ``` > pip install -U git+https://gitlab.com/mailman/mailman-web.git > ``` > to get the latest mailman-web whose Django requirement is > ``` > install_requires = > django >=2.2, !=3.0, <4 That seemed to work OK, thanks. mailman-web is now on a dev version of 0.0.6 and Django is now on 3.2.14. However, pip now throws a warning when looking at package info: (venv) mailman@somehost:/home/dnewman$ pip show mailman-web WARNING: Ignoring invalid distribution -jango (/opt/mailman/venv/lib/python3.9/site-packages) Name: mailman-web Version: 0.0.6.dev9+gc606169 Summary: Mailman 3 Web interface. Home-page: https://gitlab.com/mailman/mailman-web Author: Mailman Developers Author-email: mailman-developers(a)python.org License: GPLv3 Location: /opt/mailman/venv/lib/python3.9/site-packages Requires: django, hyperkitty, postorius, whoosh Required-by: How to correct that so the command runs clean with no warnings or errors? This is on a host running Debian 11 with mailman3 and friends installed in a venv. Thanks. dn

2 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I read the doc and it says that when the DEBUG var is set to False we should do these commands: django-admin collectstatic --pythonpath example_project --settings settings django-admin compress --pythonpath example_project --settings settings I did the first one and got this: (env2) [mailman@localhost mailman-suite]$ pwd /var/lib/mailman/mailman-suite (env2) [mailman@localhost mailman-suite]$ django-admin collectstatic --pythonpath mailman-suite_project --settings settings You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/var/lib/mailman/mailman-suite/mailman-suite_project/static', 345 unmodified. why it did not copy the files??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

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

by Mark Sapiro

On 7/9/22 9:51 AM, Andy Smith wrote: > > Over in Exim's mainlog I then see that delivered out to list > members. One of them rejects it at SMTP time, which I think causes > this: > > Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces(a)mailman.bitfolk.com>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces(a)mailman.bitfolk.com > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost > Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client() The SMTP rejection should not cause that. An SMTP recipient reject is processed internally and does not result in anything sent via SMTP to the list-bounces address. > …and I think that bounce message somehow incremented the bounce > score for andy(a)bitfolk.com even though that address was only present > in the original post's Cc: and body. If the original post was the message delivered to users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or another recognizer parsed those addresses from the message body. > Is there a good way to further debug this? Maybe by being able to > see the full content of the DSNs that Mailman generates? As I posted previously, the DSN that Mailman generates is defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…, but this message is not sent anywhere. It is only saved for possible inclusion in an admin notification or a probe message. If you send me the post as received from the list, I can run it through flufl.bounce and see what that produces. You might also be able to find the fake dsn and/or the message received via SMTP to users-bounces(a)mailman.bitfolk.com in Mailman's var/messages/ directory, although these are pickles and need to be examined with `mailman qfile`. > I think I've seen this before in the last couple of weeks so I'm > sure it'll crop up again soon. I've seen it mention about bounce > score for users-leave before, but I only really paid attention today > when it also listed my own address. users-leave probably is parsed out of the message footer. -- 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: Database read only error on mailman_sync job

by Ugnius

Thank You, Mark for guideline. I accidentally posted here. I wanted to start new thread and just replaced subject of messages. Message was sent to this thread anyway. The reason of this issue was very simple. I creadet symlink in /usr/local/bin/django-admin to /project/home/manage.py, because I was unable to set original django-admin file to work as it should to work. Later I decided to run mailman project under other user and forgot about that symbolic link. So it was normal, that previous user had no privileges on database file. Thank You for helping. > On 12 Sep 2019, at 21:50, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/1/19 1:02 AM, Ugnius S wrote: >> >> I guess that issue is hyperkitty database, but I even do not know the name >> and location of that database. > > See the DATABASES definition in your Django settings. The default is a > sqlite3 database named mailmansuite.db in the same directory as the > Django settings. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 7 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/20/22 11:40 PM, Josef Dietl wrote: > Dear all, > > > > Sorry for coming back to a topic that seems to be done for 18 months now. > > I'm staring at this issue for a few days now (on and off). But I still get > these messages: > > > > Jan 19 22:43:27 2022 (149439) HyperKitty failure on > https://lists.[...]/hyperkitty/api/mailman/urls: > <html><title>Forbidden</title><body> > > <h1>Access is forbidden</h1><p>Please check the IP addresses > > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > > </p></body></html> (403) > > > > . and consequently, nothing ends up in the archive. > > > > I have checked (among others): > - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP > address, different orders, '*'. OK. > (Asterisk makes a difference, see at the bottom) ??? I didn't see what. > - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in > mailman-hyperkitty.cfg (except for the quotes). According to the editor's > color coding, the quotes are "right", too. I have removed special characters > to circumvent diverging treatment in different environments > > - I guess it doesn't matter, but wget --user restadmin --password [.] > http://localhost:8001/3.1/lists works, too. That is Mailman core's REST API which is not the issue here. > - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter > > > > I'm running a fresh package installation from Debian Bullseye with > certificates from Certbot with nginx, so Certbot may have messed with my > nginx config, but even that seems to be OK: Yes, Certbot has inserted > http->https redirection, but I'd expect that a https base_url and > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. It should. Note that your primary resource for help with issue with Debian packages should be Debian. > Mailman info says ... > To provide all possible information, I'm also adding the nginx log that > seems to correspond to that request (no other requests at that time, give or > take five minutes): Yes, everything yields 403 response codes. > > > > [.] - - [19/Jan/2022:22:43:27 +0000] "GET > /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] > HTTP/1.1" 403 175 "-" "python-requests/2.25.1" The issue here is accessing the hyperkitty API. The base URL for these accesses is configured in mailman-hyperkitty.cfg. From what I see here, that is something like `http(s)://host.example.com/hyperkitty/` If you append `api/` to that base URL and go there in a web browser do you get a page of documentation of the HyperKitty API? If so, then figure out why it works from a web browser and not when Mailman core does it. If you get the 403, figure out why. This is probably an nginx issue. -- 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: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Thank you for your help. I have traced the versions of different components of mailman 3. I am downloading through GIT LAB because I need to modify the code according to my organization's requirements like to add SMS notifications when a mail is waiting for pending approval and so. With your help, I have found out the commits I am using in my environment. I got them using the way you suggested "git log". That may be helpful for you to help dummies like me. *### Mailman Core Version ###* *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* *Merge: 98cf97b 0bca998* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Thu Oct 15 14:02:36 2020 -0700* * Merge branch 'template' into 'master'* * Clarify the posting instruction in the list welcome message.* * See merge request mailman/mailman!723* *### django-mailman3 Version ###* *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* *Merge: ea2b33a c091e43* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:40:51 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/django-mailman3!108* *### Hyperkitty Version ###* *commit 36f43466763c2686cf4d69c982ea64b956c30939* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Mon Oct 5 04:54:44 2020 +0000* * Use GH registry to pull CI image.* *### Mailmanclient Version ###* *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* *Merge: ff39dd8 8670751* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 01:09:32 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/mailmanclient!130* *### Mailman Hyperkitty Version ###* *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* *Merge: 35ff801 04deff5* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Fri Jun 19 18:15:57 2020 +0000* * Merge branch 'fix_25' into 'master'* * Add a test for the presence of surrogates in the stringified message.* * Closes #25* * See merge request mailman/mailman-hyperkitty!7* *### Mailman-suite Version ###* *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* *Merge: 74e7927 4463b31* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Sat May 30 00:32:40 2020 +0000* * Merge branch 'doc_mb4' into 'master'* * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* * See merge request mailman/mailman-suite!8* *### Postorius Version ###* *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* *Merge: 61242d2 321310c* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:43:14 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use the GHCR registry for CI image.* * See merge request mailman/postorius!549* I have removed only mailmanclient and re-cloned it from gitlab and ran the python setup.py develop command. But still the same error. Is there anything else I can do to get rid of that error. Thanks in advance. <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, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > > > How to find out the versions of the each and every component > > of the mailman 3 like mailman core, mailmancilent, postorius, > > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > > after installation? > > > cd to the directory in which you cloned the gitlab project for the > component and do `git log` > > > > If I am running an old mailmanclient or older version of any > > other mailman component, please suggest how to upgrade either one or > > multiple components based on the requirement. Is there any link that > > would help me to upgrade ? > > > > I have used the > > link https://docs.mailman3.org/en/latest/devsetup.html to install the > > mailman 3 components. I expected that the procedure followed in this > > link would install the latest versions of the mailman 3 components. > > Please correct me if I am wrong. Is there any latest version > > compatibility table ? > > > If you installed each of mailman, mailmanclient, django-mailman3, > postorius and hyperkitty according to instructions like > > $ cd ~/mailman > $ git clone https://gitlab.com/mailman/mailmanclient.git > > Then set up mailmanclient: > > $ cd mailmanclient > $ python setup.py develop > $ cd .. > > from that document, you should have the latest version. If that is the > case, `git log` in the mailmanclient directory should begin like > > commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, > origin/master, origin/HEAD) > Merge: ff39dd8 8670751 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Thu Oct 15 01:09:32 2020 +0000 > > Merge branch 'fix-ci' into 'master' > > Use GHCR for the CI image > > See merge request mailman/mailmanclient!130 > > commit 8670751caff689733751ef323ef521c4a3fa1237 > Author: Abhilash Raj <raj.abhilash1(a)gmail.com> > Date: Wed Oct 14 17:36:58 2020 -0700 > > Use GHCR for the CI image > > commit ff39dd8f03a820f442f2251553c444370df3b914 > Merge: 80ebed4 76d44e1 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Fri Aug 7 19:35:05 2020 +0000 > > Merge branch 'invite' into 'master' > > Add support for inviting an email address to join a list. > > See merge request mailman/mailmanclient!129 > > or if you did this before Oct 15, maybe it starts with > commit ff39dd8f03a820f442f2251553c444370df3b914 > > The particular commit you need for your issue is > > commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 > Merge: c8dcb1e 28d1c3a > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Sat May 16 08:02:21 2020 +0000 > > Merge branch 'held-count' into 'master' > > Add a new get_held_count() API to get a count of held messages. > > See merge request mailman/mailmanclient!122 > > > > Note that unless you intend to do actual development of Mailman 3, you > should be following > <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather > than <https://docs.mailman3.org/en/latest/devsetup.html>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 5 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/22/23 14:48, ceo(a)sartrack.nz wrote: > Thanks; > There has never been a 'Mailman' user. I do have a www-data user (all Apache2 data' and there is a 'list' user. So what I refer to as the Mailman user (a generic term) is `list` in your case. > I may have run the import fuction as root, but I then used chown() to set the directory tree /var/lib/mailman3/* to user 'list'. OK > So I upgraded Debian 10 to Debian 11. > This also upgraded Apache2 I assume, but I kept the original (single) config file. > > I then installed the whole Mailman3 package with 'apt'. I may also have installed additional missing bits afterwards, as I think it was not complete. I initially tried to use MariaDB but the installation failed completly because it never asked for the MariaDB root password, and as a result of that everyting else failed too. > Then I un-installed 5 times, and then I finally went for the 'default' database system. > > I then edited the file with the recommended settings for Mailman3: > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > So clearly Apache2 manages to access the data supplied by Postorius because it sees the lists (at least the empty ones). > -What user should the whole system running under: 'list'? of 'www-data'? > - Is there anything else I should tell Apache2? All the web based stuff is a Django application. Django is run by uWSGI which probably runs as www-data, but Django only accesses hyperkitty, postorius and django-mailman3 and other Django related tables in the database. It doesn't need access to file system files other than things like wsgi.py, urls.py, settings.py and settings_local.py and only read access to these. All the mailman3 file system stuff has to be read/write/searchable by `list`. > Now I tried to use "django-admin createsuperuser". This also fails because of this error: > ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) > And I cannot find where this 'force_text' is called from. It must be removed as it is too old. It seems your Django installation is broken. Do cd /usr/local/lib/python3.9/dist-packages/django grep -r force_text to find where force_text is called, or maybe add def force_text(s, encoding='utf-8', strings_only=False, errors='strict'): return force_str(s, encoding, strings_only, errors) to /usr/local/lib/python3.9/dist-packages/django/utils/encoding.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Installing Mailman for the first time

by Jim Berg, Jr.

I am not so sure what I am doing. Is there someone who does this for a fee? Jim Berg > On Mar 24, 2023, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/24/23 16:43, comprepair_jimberg--- via Mailman-users wrote: >> I am running Debian 11 Server and wanting to install Mailman 3 >> Will this work for what I am trying to do? >> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > > Yes, but <https://docs.mailman3.org/en/latest/install/virtualenv.html> is our current recommendation. > >> If not is there a shorter list of steps to accomplish what I am trying to do? > > The above may not be shorter. There are a lot of steps no matter how you do it. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to comprepair_jimberg(a)icloud.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years

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

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > When held mails are released in Mailman (maybe also mails which are not held) they are sometimes not sent nor archived, as mentioned in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > One of my list admins reported that he released two mails on Sep 25 07:20:48 2017 UTC, and only the first was sent to the members. In the mailman.log I found the following from that particular release: > ... I will look at the above as time permits, but ... > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 This one at least is a known issue. See <https://gitlab.com/mailman/mailman/issues/256>. As noted there, the underlying cause is <https://bugs.python.org/issue27321>, a bug in the Python email library (not yet fixed as of Python 3.6.2, but there are references to patches in the bug report). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 8:58 AM, Quanah Gibson-Mount wrote: > Now that we are on mailman3, I'm finding things that were really useful > in mailman2 are completely missing in mailman3, which seems odd, since > they in particular affect the ability of list moderators to do their job > well. > > a) When a post was made to a moderated list in mailman2, I would get an > email that included a LINK to the held email. Now I just get a canned > email saying I need to go to the dashboard, blah blah. Why was this > link removed? It was extremely useful and now I have to jump through > extra hoops. The message comes from Mailman core. Mailman core does not know what web management UI you are using or the URI to access it. You need to change the template for the message to include the URL. E.g. on this iist, in var/templates/sitr/en/list\:admin\:action\:post.txt we have As list administrator, your authorization is requested for the following mailing list posting: List: $listname From: $sender_email Subject: $subject The message is being held because: $reasons At your convenience, visit https://lists.mailman3.org/mailman3/lists/$list_id/held_messages to approve or deny the request. > b) When a post is made to a moderated list in mailman2, when I went to > the page to approve/deny/discard, there was additionally an option to > remove the moderated flag from the user for all future emails. This > option no longer exists. This was EXTREMELY useful, as we force all new > members of the list to be moderated for a time while we evaluate the > quality of their postings. Now I have to go manually track down the > user and their settings. Unnecessary extra hoops to jump through 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'. > c) When a post is made to a moderated list, one of the options when > selecting REJECT was it allowed me to set a custom message when > rejecting the email. This was extremely useful. For example today, > someone emailed our bug tracking list directly instead of filing a bug. > In the past, I would have added a note to them about what they should do > (in this case, I would have told them to send their email to our > community technical discussion list). Now I can no longer do that, I > can only reject it or discard it. Why was this removed? This was not "removed". It just hasn't been implemented in MM 3 yet. See, e.g., <https://gitlab.com/mailman/postorius/-/issues/368> and <https://gitlab.com/mailman/postorius/-/issues/368>. -- 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: how should I implement multiple domains for receiving emails to a list

by Mark Sapiro

On 4/15/25 16:51, Philip Bondi wrote: > > I have two domains: systemdatabase.ca, systemdatabase.homelinux.com > > All my lists should be on both domains. So h(a)systemdatabase.ca is the same list as h(a)systemdatabase.homelinux.com. I found this was the mailman2 behaviour on my old CentOS 7 installation and I am accustomed to it. While Mailman 2.1 had some support for multiple domains, list names had to be globally unique because a given list name referred to that one list regardless of domain. Mailman 3 is different in that the domain is part of the list name so h(a)systemdatabase.ca and h(a)systemdatabase.homelinux.com are different lists. > I edited /opt/mailman/venv_mm/var/data/postfix_lmtp directly. Duplicated and edited all the lines. And compiled with postmap /opt/mailman/venv_mm/var/data/postfix_lmtp > > I sent a test email. This appears to work. > > Is this the best method to achieve this goal? What would you recommend? If all you want is for mail to h(a)systemdatabase.ca or h(a)systemdatabase.homelinux.com to wind up at the same list, what you've done is OK, but whatever fqdn name your list is created as, it needs the other fqdn name added to it's Acceptable aliases setting, at least if Require Explicit Destination is Yes. The other issue is every time you start Mailman core it will implicitly run `mailman aliases` and overwrite your changes. I have a similar situation on one of the servers I support. The lists are all in a domain I'll call example.com, but we also want to allow mail to <list>@otherexample.com to reach the <list>@example.com list. We use this patch to add all those names. ``` --- a/src/mailman/mta/postfix.py +++ b/src/mailman/mta/postfix.py @@ -261,5 +261,10 @@ class LMTP: '{}@{}'.format(alias, mlist.true_mail_host)) line = VMAPTMPL.format(true_addr, width, addr) print(line, file=fp) + if mlist.true_mail_host == 'example.com': + true_addr = self._decorate( + '{}@{}'.format(alias, 'otherexample.com')) + line = VMAPTMPL.format(true_addr, width, addr) + print(line, file=fp) print(file=fp) return True ``` However, this only works because example.com has an alias domain. If that weren't the case, we would need something like this instead. ``` --- a/src/mailman/mta/aliases.py +++ b/src/mailman/mta/aliases.py @@ -43,9 +43,14 @@ class MailTransportAgentAliases: """See `IMailTransportAgentAliases`.""" # Always return yield mlist.posting_address + if mlist.mail_host == 'example.com': + yield '{}(a)otherexample.com'.format(mlist.list_name) for destination in sorted(SUBDESTINATIONS): yield '{}-{}@{}'.format( mlist.list_name, destination, mlist.mail_host) + if mlist.mail_host == 'example.com': + yield '{}-{}@{}'.format( + mlist.list_name, destination, 'otherexample.com') def destinations(self, mlist): """See `IMailTransportAgentAliases`.""" ``` Do not use both those patches. If your list domain has an alias domain, use only the first one and if not, only the second. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 1 day

[MM3-users] Re: MM3 & postfix ... (mail loops back to myself)

by Abhilash Raj

On Thu, Jan 18, 2018, at 2:39 PM, Mark Sapiro wrote: > On 01/18/2018 02:25 PM, Dmitry Makovey wrote: > > > > transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > > local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > > relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains > > The initial implementation of Mailman's regexp maps for Postfix was > broken. This was fixed by > <https://gitlab.com/mailman/mailman/merge_requests/323>. The bottom line > is if /opt/mailman/core/var/data/postfix_lmtp contains entries like > Also, MR 323 was backported to Core's 3.1 release. So if you are running the newer images with 3.1.1 release, you should ideally have the fix. > /^foo-bounces(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > /^foo-confirm(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > > these entries (only the -confirm and -bounces, not the others) need to be > > /^foo-bounces(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > /^foo-confirm(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > > because Postfix recipient_delimiter = + is not effective for regexp tables. > > -- > 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/ > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 3 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/25/22 07:54, denis.bitouze(a)univ-littoral.fr wrote: > > > Mark Sapiro wrote: > > The difference between Reject and Discard is Reject notifies the > > sender of the rejection whereas Discard just discards the message > > without notification. > > IMHO, even in English, “Reject” and “Discard” are not > > self-explanatory. > > They seem so to me, but in any case, if you look at Postorius -> > Settings -> Message Acceptance -> Default action to take when a > (non-)member posts to the list, they are described there in much more > detail. OK: not easy to figure out. A tooltip on the corresponding buttons would be helpful. > > BTW, no clue about an automatic banishment of emails from discarded > > messages? > > In the pop-up dialog from clicking the subject of a held post you can > set the sender's moderation status when discarding the post. Sorry but I can only see: - “--- Set member moderation ---” (non selectable, I guess) - “Hold for moderation” - “Reject (with notification)” - “Discard (no notification)” - “Accept immediately (bypass other rules)” - “Default processing” and cannot see how I can at the same time “Discard (no notification)” and “Banish the email of the post's sender”.

2 years, 9 months

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

On 1/6/20 11:16 PM, hansen(a)rc.org wrote: > Mark Sapiro wrote: > >> What's the setting for base_url in mailman-hyperkitty.cfg? > > It's > base_url: https://<OLDHOSTNAME>/archives > > I suppose it should be changed to > base_url: https://<NEWHOSTNAME>/archives That's part of it, but see below. > But: > What if we decided to have more than one domain, as the UI indicates is kosher? Again, see below. >> Are there any errors in var/logs/mailman.log? > > Yep. Lots. They all are of this nature: > > Exception in "hyperkitty" archiver > Traceback: > ... > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 430, in _match_hostname > match_hostname(cert, asserted_hostname) > File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname > % (hostname, dnsnames[0])) > ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHOSTNAME'",) OK. So the real issue is you are trying to access HyperKitty via an https URL and the certificate presented by the web server doesn't allow the domain in the URL. The domain in the URL doesn't really matter as long as it resolves to the HyperKitty host, but if it's an https URL the host's certificate must include that domain. It looks like in your case, the certificate is for 'NEWHOSTNAME', so setting base_url: https://<NEWHOSTNAME>/archives should be enough >> qcluster is not what you need to restart. You need to restart whatever >> is supporting the wsgi interface to Django. This may be uwsgi or >> gunicorn or ??. Whatever it is, that's what needs to be restarted. > > Beats me, Mark. Brian, do you know? Brian has answered: systemctl restart gunicorn >> If you do ps ax|grep runner=, what do you see? If you don't see at >> least three processes with --runner=rest:0:1, stop Mailman and start >> Mailman. > > Yep. I did not get the whole string before. With your options I see three > of these rest:0:1 processes. So I guess the REST stuff is running anyway. OK >> If so, what's >> in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as filename in the file handler in the LOGGING >> definition in settings(_local).py. > >> hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log >> return Site.objects.get_current(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", >> line 60, in get_current >> return self._get_site_by_request(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", >> line 45, in _get_site_by_request >> SITE_CACHE[domain] = self.get(domain__iexact=domain) >> File "/opt/mailman/mm/venv/lib/python3.7/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.7/site-packages/django/db/models/query.py", line >> 408, in get >> self.model._meta.object_name >> django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. > >> This is because of the domain change. In settings(_local).py you have a >> setting for SITE_ID. Possibly, setting that in settings_local.py to a >> value one greater that the current setting will do. > > Trying setting it to 1 (it was 0 before). OK. You can just shotgun trying numbers until one works, or >> To be certain of the >> correct value, you need to look at the django_site table in mailman's >> database. That table has 3 columns, id, domain and name. The id for the >> row of your domain is what needs to be set as SITE_ID. > > You lost me here. No idea how to access the Mailman database. > Brian, do you know? It depends on the database engine. In the database section in your mailman.cfg there is a class: definition which will mention sqlite, mysql or postgresql. The tools for interacting with these are sqlite3, mysql and psql respectively. >> Stop Mailman and then start it. > > No idea here, either. I looked online and found this: > > $ from mailman.commands.cli_control import Stop > But it complained: > from: too many arguments That's a Python statement, not a shell command. You would do systemctl stop mailman systemctl start mailman alternatively, you could do /path/to/bin/mailman stop /path/to/bin/mailman start but that appears to not be the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by Mark Sapiro

On 1/7/22 11:06 AM, David Newman wrote: > > 1. In Users/Members, moderation action for the newly resubscribed users > shows as "None". Is there a method, either in the UI or the command > line, to change this to "Default processing" for all users? I assume you don't want to set `Default action to take when a member posts to the list` to Default Processing because you want new member posts to be held. This is a good practice. To set all members to default processing in mailman shell ``` $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.interfaces.action import Action >>> for mbr in m.members.members: ... mbr.moderation_action = Action.defer ... >>> commit() >>> ``` > 2. Although Delivery Mode shows as "Regular" for all users in > Users/Members list, clicking on a member's name shows all options such > as delivery status, delivery mode, etc., as undefined. They show as undefined, but if you look at your own settings by selecting `Mailman settings` from the dropdown under your username at the upper right in Postorius, you will see you have Global Mailman preferences, Address-based preferences and List-based preferences. If a list based preference is unset for a list, it falls back to the address based preference for the address and if that's unset, to the global preference. When you as an admin look at a user, you only see the user's list based preferences. > Similar question: How to set subscriber options for all members in one go? Per the above, you only need to set the user's preferences if they don't have address based preferences and the preference differs from the global (default) preferences. However, if you want to set the member's list preferences, you could add to the beginning of the above: ``` >>> from mailman.interfaces.member import DeliveryMode, DeliveryStatus >>> english = getUtility(ILanguageManager).get('en') ``` and to the `for` loop in the above: ``` ... mbr.preferences.acknowledge_posts = False ... mbr.preferences.delivery_mode = DeliveryMode.regular ... mbr.preferences.delivery_status = DeliveryStatus.enabled ... mbr.preferences.hide_address = False ... mbr.preferences.preferred_language = english ... mbr.preferences.receive_list_copy = False ... mbr.preferences.receive_own_postings = True ``` Or whatever you think these settings should be. > 3. As a subscriber to this list, I received email notification that I'd > been unsubscribed. Where is the control for enabling/disabling > subscription notifications? Settings -> Automatic Responses > Settings/Member Policy/Un-subscription Policy is set to Confirm, but I > don't think that's relevant here since I unsubscribed users as the > Django superuser. 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: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

ok Thank you Mark for your valuable time. I will try this method and let you know the status. Thanks once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/20 12:08 AM, Shashikanth Komandoor wrote: > > I tried this way but in this method I don't find any files to edit for my > > customizations like > > 1. Removal of social accounts, > > 2. Addition of SMS integration and so. > > > > If I can do my required customizations through pip installation I am fine > > with that. > > If you follow the instructions for installing in a virtualenv, in say > /opt/mailman/venv, all the component files will be in > /opt/mailman/venv/lib/python3.x/site-packages > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 5 months

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

by Mark Sapiro

On 9/18/23 8:36 AM, bryan.kartzman(a)yu.edu wrote: > > I'd like to say it worked flawlessly (and it did allow the archives to be displayed, which wasn't happening before, but I'm getting the following two errors (or maybe KeyError 1365 and 1366 are the same error?) every minute: > > 11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1365 : Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker > res = f(*task["args"], **task["kwargs"]) > File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.nodes[msgid]["obj"] > File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ > return self._nodes[n] > KeyError: 1365 > > 11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1366 : Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker > res = f(*task["args"], **task["kwargs"]) > File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.nodes[msgid]["obj"] > File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ > return self._nodes[n] > KeyError: 1366 > > Is this an error only in the archives or might I also have a problem with other timestamp fields in the database? If its just the archives, is there a simple way to fix it? If no simple way to fix the archives, is there an easy way to erase all list archives? If no easy way to erase all list archives, would deleting all the lists and recreating them remove the archives? The above errors have nothing to do with timestamps. There are entries in the hyperkitty_thread table with starting_email_id = 1365 and 1366, i.e., `SELECT * FROM hyperkitty_thread WHERE starting_email_id in (1365, 1366);`, but there are no entries in the hyperkitty_email table with id = 1365 or 1366. You could look at the thread_id for those entries in the hyperkitty_thread table and see if there are entries in the hyperkitty_email table with message_id_hash = those thread_id values. if those entries exist, you can fix this by altering the starting_email_id of those entries to the respective id values for those messages from the hyperkitty_email table. If those messages don't exist in the hyperkitty_email table, you could just delete the offending entries from the hyperkitty_thread table. As far as deleting archives is concerned, a Django superuser should have a `Delete Archive` button on the top level Hyperkitty view for the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: hyperkitty failed to create a thread

by Danil Smirnov

Thank you very much for the quick fix, Mark and Abhilash! Abhilash, could you include the fix into the "latest" version of mailman-web container please? Btw I wasn't able to find a changelog of Mailman docker images anywhere and 'Releases' page in Github is quite outdated too... Is there any other place I should check? Danil вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > What could be a reason of HyperKitty failing to create a thread from > > chained emails? > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > "Openvpn and Network mapping" discussion displayed as five threads > instead > > of only one... > > > > Any ideas how to improve HyperKitty ability to detect threaded messages? > > > Thanks for the report. > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > will fix this. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 2 months

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Zaheer Abbas

Thanks, Mark & Odhiambo for providing options for the solution. I will try the 'postorius header filters' hacky way as it's more suitable to my requirement, however, if it didn't work as expected, then filtration through exim filter is also an acceptable option. Thanks again for the quick response. On Thu, Mar 30, 2023 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 11:07, Odhiambo Washington wrote: > > So the MTA option that doesn't involve any regex is better than no? > > Partly it's a matter of taste and possibly a matter of necessity. I.e. a > list admin can do this with header filters and may not have access to > the MTA config. > > Also, it's not clear to me that doing this in Postfix is less > complicated than understanding a regex. > > -- > 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 zaheer.psg(a)gmail.com >

2 years

[MM3-users] Re: MM3 in virtualenv - FreeBSD-11

by Mark Sapiro

On 1/11/19 6:51 AM, Odhiambo Washington wrote: > > Now that I look at it, I think you should clarify that if one is not > interested in using PostgreSQL (which is what `pip install psycopg2-binary` > is for), > then there should be some different binary they need to install, no? And > which one is it? I have added a note to the comment at https://wiki.list.org/DOC/Mailman%203%20installation%20experience which says: """Also, please note the first paragraph of the introduction. This is documentation of my decisions and experiences. It is not a how-to and does not replace the documentation at http://docs.list.org/""" In particular, documentation of the requirements for different databases is at <https://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>. > Under your "*Recommended Configuration*", I have followed each step, > getting the files and editing them to suite my needs, until I got to where > you refer to: > /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file but > with DEBUG = False) > I tried to get this file using `git clone > https://gitlab.com/mailman/mailman_suite.git` and realized that > authentication is required in order to get it. Because you should be getting <https://gitlab.com/mailman/mailman-suite.git> (hyphen, not underscore) which works without authentication. Or you could just go to <https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/…> and copy it from there. > What is the reason you did not include a copy like for the rest?? Because it's available on GitLab. > I have created the executables - all of them. > I have created the templates and did `find . -type f -exec sed -i.BAK 's/ > mailman3.org/mydomain.name/g' {} \;` > Maybe you should state explicitly that once one gets these templates, they > need to change the url to match theirs. You said it, but it doesn't come out > forcefully :0 I added "Of course, if you use these you need to edit the URLs for your site." > In your "MTA" section, I suppose you need to be a little more generic as > well and accommodate Exim users. > First I suggest you clearly state that one needs to edit /opt/mailman/mm/ > mailman.cf to ensure that the values under [mta] match what is required. > Maybe there is a different file to edit for MTA settings??? Again, I'm documenting MY experience, not trying to replace the official documentation. I refer to <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix> because I use Postfix. That same page also has Exim documentation. > So far ..... > > Next, I will be looking into "Running Things".... which is where I believe > things will get thicker .... Perhaps when you're done you will write u your experiences with FreeBSD and Exim. -- 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: installing a new instance of mm3

by Christian Stalberg

mailman.log is showing this: ERROR 2021-10-18 22:19:12,385 616 django.security.DisallowedHost Invalid HTTP_HOST header: 'subdomain.domain.tld'. You may need to add 'subdomain.domain.tld' to ALLOWED_HOSTS. ERROR 2021-10-18 23:01:15,318 616 django.security.DisallowedHost Invalid HTTP_HOST header: '192.168.0.1'. You may need to add '192.168.0.1' to ALLOWED_HOSTS. Where do those entries go? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 11:44 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: installing a new instance of mm3 On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm > getting nowhere with diagnostics and troubleshooting (which was easier > with mailman 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 6 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Mark Sapiro

On 8/27/20 5:44 PM, Simon Handfield via Mailman-users wrote: > > Traceback (most recent call last): > File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) > File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text > msg.set_payload(payload, charset) > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) > > I'm sorry if this is a query that's answered already but I have not been able to find matching thread that seems to relate to my error. Sorry for not answering earlier and for not being able to devote more time to this now as I'm going away within the hour, but this looks as if the message is somehow defective. Basically, the message can't be flattened by its as_string() method because of unicode issues. This can occur because of non-ascii characters is the message headers or in body parts explicitly or implicitly declared as ascii. We have had workarounds for this for some time, but I don't think they are in 3.1.1, See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/message.…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

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

by Mark Sapiro

On 12/10/22 01:13, Odhiambo Washington wrote: > On Thu, Dec 8, 2022 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> In the DATABASES['default'] definition, you need to set `'OPTIONS': >> {'charset': 'utf8mb4'}` >> > > I added that: > > [database] > class: mailman.database.mysql.MySQLDatabase > url: mysql+pymysql://mailman_user:XXXXXXXXX@localhost > /mailmansuite?charset=utf8mb4&use_unicode=1 The above is for Mailman core. It doesn't affect HyperKitty. For that you need to look at the DATABASES definition in /etc/mailman3/settings.py <https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail…> and ensure that in addition to the other settings under `default {` you have ``` 'OPTIONS': {'charset': 'utf8mb4'}, ``` ... >> You might also need to modify the tables, particularly hyperkitty_email >> with something like >> ``` >> ALTER TABLE hyperkitty_email >> DEFAULT CHARACTER SET utf8mb4, >> MODIFY subject varchar(512) >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, >> MODIFY content >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; >> > > > So I removed my list, dropped the database, and proceeded as follows: > > create database mailmansuite CHARACTER SET utf8mb4 COLLATE > utf8mb4_0900_ai_ci; > ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4; > ALTER TABLE hyperkitty_email MODIFY subject varchar(512) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY content longtext CHARACTER SET utf8mb4 > COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY sender_name varchar(255) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY in_reply_to varchar(255) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > > I did all those (although looks overzealous) just to be on the safe side. I > have seen people putting emojis in their names. None of that should be necessary. `mailman-web migrate` should create the database and tables as needed. > After that, I did the mailman-web migrate, created the list, imported the > config from MM2 and then proceeded to import the archives. > However, the errors still are there, and several messages were not imported Do you have the OPTIONS setting in your DATABASES definition in settings.py? ... > Warming up cache > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> > sys.exit(execute_from_command_line()) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 402, in run_from_argv > self.execute(*args, **cmd_options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 448, in execute > output = self.handle(*args, **options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", > line 411, in handle > call_command("hyperkitty_warm_up_cache", list_address) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 198, in call_command > return command.execute(*args, **defaults) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 448, in execute > output = self.handle(*args, **options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", > line 53, in handle > self.warm_up_mlist(mlist, options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", > line 61, in warm_up_mlist > for thread in mlist.recent_threads: > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 162, in recent_threads > return self.cached_values["recent_threads"]() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/common.py", > line 58, in __call__ > return self.get_or_set(*args, **kwargs) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 317, in get_or_set > return [Thread.objects.get(pk=pk) for pk in thread_ids] > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 317, in <listcomp> > return [Thread.objects.get(pk=pk) for pk in thread_ids] > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", > line 85, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", > line 650, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does > not exist. > (venv) [mailman@gw ~/mm]$ I have no idea what would cause this in a newly created database with no archives before running hyperkitty_import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

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

by Mark Sapiro

On 1/29/22 05:48, Jacob Sievert via Mailman-users wrote: > Hello, > > we seem to have the same problem right now. > > We are still on python3.6 and postgresql 12.9 > > I looked at our Table pendedkeyvalue and we have roughly 35k rows in > that table, > is that normal or shouldn't those get cleaned up after a while? Yes they should. This is https://gitlab.com/mailman/mailman/-/issues/257 fixed in Mailman core 3.3.5. Also in Mailman 3.3.5 is a new Task runner that runs periodic tasks, one of which is to remove orphaned pendings. This may also be the issue for the OP in this thread if that pendedkeyvalue table is also large. Here is a `mailman shell` script that will clean that up. ``` # Prior to Mailman 3.3.5, some tokens for user confirmations were pended with # too long a lifetime. This script removes those pendings based on when they # were pended and the configured pending_request_life rather than their # expiration. # Also prior to Mailman 3.3.5, pended held_message tokens for email handling # of the message were not removed when the message was handled via REST. This # script removes those pendings too. # This is run with # mailman shell -r delete_orphans_expireds # after saving it as # /opt/mailman/mm/venv/bin/delete_orphans_expireds.py from datetime import datetime from lazr.config import as_timedelta from mailman.config import config from mailman.database.transaction import transactional from mailman.interfaces.pending import IPendings from zope.component import getUtility pendings = getUtility(IPendings) def is_request(id): if config.db.store.execute( 'SELECT * FROM _request WHERE id = {};'.format(id)).rowcount > 0: return True return False then = datetime.now() - as_timedelta(config.mailman.pending_request_life) thenm = datetime.now() - as_timedelta(config.mailman.moderator_request_life) def fromisoformat(x): if hasattr(datetime, 'fromisoformat'): return datetime.fromisoformat(x) try: return datetime.strptime(x, '%Y-%m-%dT%H:%M:%S.%f') except ValueError: return datetime.strptime(x, '%Y-%m-%dT%H:%M:%S') @transactional def delete_orphans_expireds(): count = 0 for token, data in pendings.find(pend_type='held message'): if data and not is_request(data['id']): result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} orphaned pended held messages') count = 0 for token, data in pendings.find(pend_type='data'): if data and data['_mod_hold_date']: when = data['_mod_hold_date'] if isinstance(when, str): when = fromisoformat(when) if when < thenm: result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} expired held messages') pends = list(pendings.find(pend_type='subscription')) pends += list(pendings.find(pend_type='unsubscription')) count = 0 for token, values in pends: if values and values['token_owner'] == 'subscriber': when = values['when'] if isinstance(when, str): when = fromisoformat(when) if when < then: result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} expired (un)subscription confirmations') ``` The above says to save the script at /opt/mailman/mm/venv/bin/delete_orphans_expireds.py but that path may need to be adjusted based in where Mailman's bin/ directory is in your installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Search results for query "sapiro"