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

[MM3-users] How to approve moderated messages via email?

by Stephen J. Turnbull

Brian Carpenter writes: > What is the protocol to approve moderated messages via email? I > hope I asking the question correctly. Is this capability important to you or your clients? If so, what is the context? I ask because, as you know, email is rather insecure by default. Making it highly secure would require a lot of effort and sophistication for the moderator, eg, PGP signatures, but there might be intermediate levels that would be appropriate for many lists. For example, the Mailman 2 mechanism. I forget exactly what Mailman 2 does, but if the post to be approved were identified by a one-time key, then a spammer would have to have both the moderation password and the key (presumably by intercepting the moderation email) to approve their own spam. That's still a plausible scenario in principle[1] so I don't much like it (and I bet that's why Barry didn't implement it), but it would be straightforward to implement. Footnotes: [1] Ie, a moderator falls for a phish; then Ms. Cantor[2] probably got everything she needs to spoof approvals. It's questionable whether a spammer would go to the trouble of identifying a moderator, phishing them, reading their mail, and using the email approval to spam for profit, of course. But I can easily imagine it if somebody hates you. On the other hand, if they have your Gmail password, and you use your Gmail account to authenticate to Postorius, they can do it by web, so disallowing email approvals is no help. Security is hard .... Maybe we should implement 2FA for privileged roles. [2] Original "Green Card Lawyer".

5 years, 6 months

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

by Mark Sapiro

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

3 years, 2 months

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

by Simon Hanna

On 05/14/2016 07:11 AM, Mark Sapiro wrote: > On 5/13/16 5:05 PM, Simon Hanna wrote: >> On 05/12/2016 09:26 PM, Barry Warsaw wrote: >>> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >>> >>>> It is the intent that Postorius will eventually expose all these >>>> settings. We're not there yet. At present you could possibly do this by >>>> interacting with mailmanclient, although I'm not certain the settings are >>>> exposed there. >>> >>> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >>> core's REST API, on the member resource. It's the `delivery_mode` attribute >>> and it takes as legal values one of 'regular', 'plaintext_digests', >>> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >>> DeliveryMode enum). > >> They are exposed in mailmanclient and are used in postorius. They can be >> found in the users personal subscription settings >> https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > > You are correct. When I checked this before my initial reply, I never > pulled down the Delivery Mode list to see all the options. My bad. > > However, please correct me if I'm wrong, but there does not appear to be > a way in Postorius to set a list's mime_is_default_digest attribute. > You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.

10 years, 2 months

[MM3-users] Re: Whitelist non subscriber

by Mark Ziranski

Hi, thanks for your reply. Can I set the moderation_action on this member? I cannot figure out the API command. All posts of other members should be moderated. POST: http://localhost:8001/3.1/members role=nonmember list_id=something.localhost subscriber=someone@localhost moderation_action=accept Reply: Unexpected parameters: moderation_action Thanks. Gesendet: Donnerstag, 10. August 2017 um 22:05 Uhr Von: "Mark Sapiro" <mark(a)msapiro.net> An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Whitelist non subscriber On 08/10/2017 07:12 AM, Mark Ziranski wrote: > > I want to whitelist an email address on all lists to bypass moderation. > The email address is not a subscriber. On google I > found accept_these_nonmembers but I do not know how to use it. > Please show me some examples how to whitelist someone(a)example.org. Since this is a Mailman 3 list, I assume you are asking about MM 3. Mailman 3 defines the list attribute accept_these_nonmembers, but it is not currently implemented to actually have any effect, nor is it exposed in Postorius. At the present, I think you would have to create a user record with the address and add that user to all lists with role nonmember and moderation_action 'defer' to apply subsequent tests or 'accept' to unconditionally accept posts from that address. (In MM 2.1, accept_these_nonmembers is a list of addresses and regexps matching addresses whose posts are to be accepted, subject to subsequent tests, and is exposed in the web admin UI) -- 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 [1]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org / References 1. https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 11 months

[MM3-users] Re: Topics - Tags

by Stephen J. Turnbull

Mark writes: > >> In Mailman 2 there is an Admin web UI for "Topics". Is there > >> such a web UI that can be enabled in Mailman 3 so that the list > >> owners can create topics (tags) in their lists? Do you specifically want topics, that is, a way for users to select subsets of the list posts based on themes set by the administrator? There is (was?) an alternative specification implemented by the Systers, which they call "dynamic sublists". The dynamic sublist feature is controlled by the users (thus "dynamic"), using specially formatted email messages to tag threads as "sublists" and to subscribe to them or suppress them. This was implemented internally by the Systers so it has not been contributed back to the Mailman project, and it was integrated with other Systers-specific features, so it wasn't just a matter of a git merge, If that sounds as good as Mailman-2-style topics to you, I can add/emphasize it on our GSoC task list. (It was on our GSoC task list for several years (maybe still is, I need to check that since contributor applications are now open.) The Systers users are developers themselves, so using email commands isn't much of a burden. I don't think it would be impossible to add sublist control features to Postorius, but it's nontrivial, and might require a second project to implemnt after the initial port. I may add the Mailman-2-style topic feature as well, although in my opinion the dynamic sublist feature is a better match for Mailman's core audience (lists that support open source development organizations). Steve

2 years, 4 months

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

by Odhiambo Washington

On Mon, Nov 20, 2023 at 7:56 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > The idea is to (if possible) not change anything at all. I will be > > serving the list using the original domain. > > Fine. I just didn't want to assume anything. > > > I am hoping that should not be necessary. > > It's not. That's one of the major things that MM3 does that MM2 does > not: handle multiple domains properly. > > > I actually had thought it wouldn't be complex doing this until I > > sat down and said wait - there is a DB involved :) > > > 3. (If the DB engines are different) Dump both databases in text > > > format (ie, scripts of SQL commands). Check to see how they > > > differ. > > > > > > > The DB is MySQL. My running setup uses MariaDB. I am not getting what > you > > mean here by how they differ. > > You didn't say that before. I tend to assume PostgreSQL because > that's what I use. > > I don't know if MySQL and MariaDB have different features that have > different syntax, etc. That's what you're looking for. Any commands > that are *not SQL* used to configure the database engine itself (for > example the utf8mb4 parameter which MySQL has but PostgreSQL does not, > does MariaDB need it?) Also any non-standard SQL stuff (mostly around > varchar/text types I think). > I use the utf8mb4 character set as default, unless something wants a different one. MySQL and MariaDB are almost similar. I have encountered very few significant differences since I switched to MariaDB. > 4. Adapt the foreign database to its new environment with search and > > > replace. > > > > If going with what I have mentioned above, is this step still > > necessary? > > Isn't one installation using 'mailman' and 'mailmanweb' databases, > while the other only 'mailman'? You'll need to deal with that at > least I suppose. > This is true. However, I was hoping that I could merge the two foreign DBs into one. I am yet to test it though. > > > 5. (Optional if your name is "Daredevil") Create a new Mailman suite > > > install using your current configs, preferably in a new VM or set > > > of containers. > > > > I was thinking about this as one way of testing the situation, much > > as it is quite involving. > > Fred Brooks famously put it this way: "Build one to throw away. You > will anyway. The only question is whether you deliver the first > version to the customer." ;-) > I had to Google who he was :-) > Suppose I just do: > > 1. Create the new list on my server using the inherited domain and > > configure it appropriately, > > 2. Configure Django to handle the different domains (there is something > > that I am yet to understand here around SITE_ID when you have multiple > > sites!) > > You just add them in the Django admin page. Problems come in when you > delete the original example.com placeholder domain. I think you > probably need to add SITE_ID=0 to settings.py so the Django figures > out the site from the HTTP header rather than just assuming it's the > same Postorius site for all lists. > In my case, I did not delete the original example.com. I finally get to use SITE_ID=0. I suppose that it should be accompanied by FILTER_VHOST=True > > 3. Extract the users from the list and subscribe them afresh (I can > > shoot an email to let them know the ML had to be moved so they can > > set their preferences again) > > 4. Import the archives of the list > > I should more or less achieve the migration, no? > > I think that should work. > I am going to try this method. It looks safer for me. > > What about setting up on /opt/mailman2 a complete replica of the > > list? That'd be the real "Daredevil" :) > > This will also work, I'm sure. But we'd be embarrassed after going to > the trouble of making Mailman 3 handle multiple domains. Also you'd > need separate instances of Mailman running, with their own > /etc/mailman3-1 and /etc/mailman3-2, and more important you'd double > the RSS and VM requirements by running two instances. > I also will need to have extra macros, routers, and transports for Exim. This method is untenable as it complicates life. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 8 months

[MM3-users] Re: Mailman3 on FreeBSD

by Barry Warsaw

On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> wrote: > > The instructions say > > After this, create a configuration file at /etc/mailman.cfg for Mailman > Core. > > On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't > see any indication as to what I should put in this file and if it was in > /usr/local/etc/mailman.cfg then how would mailman find it? It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro? (Side note, you can always use `-C /usr/local/etc/mailman.cfg` or set the MAILMAN_CONFIG_FILE environment variable for alternative locations.) > I'm using a different system to install Mailman so it's difficult to paste > the error msgs, but it seems to be related to being unable to find the > module '_sqlite3' That’s a Python problem. What does the following do for you? % python3 Python 3.6.2 (default, Jul 27 2017, 18:13:18) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import _sqlite3 >>> _sqlite3 <module '_sqlite3' from '/usr/local/Cellar/python3/3.6.2/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload/_sqlite3.cpython-36m-darwin.so’> This is what you get from a Python 3.6 installed via homebrew on macOS. Maybe you need to install another package to provide SQLite on FreeBSD? -Barry

8 years, 11 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Odhiambo Washington

On Thu, Aug 8, 2024 at 10:34 AM IEM Network Operation Center (IOhannes m zmölnig) <noc(a)iem.at> wrote: > On 8/7/24 12:55, Odhiambo Washington via Mailman-users wrote: > > On Wed, Aug 7, 2024 at 1:05 PM IEM Network Operation Center (IOhannes m > > zmölnig) <noc(a)iem.at> wrote: > >> - ./data: empty > > > > With a Postfic MTA situation, that would have had some files. So you > don't > > use Postfix. > > > >> - ./lists: empty directories named after each list (i think these are > >> used by the MTA to determine whether it should hand over a mail to the > >> mm3-ltmp) > > > > True, at least according to Exim MTA. > > indeed, i'm using exim. > i guess these directories are named like they are for backwards > compatibility. > if the sysadmin is supposed to ever do something with them, it would be > nice if there was some (discoverable) documentation (like a README in > Mailman's var; or the yet-to-be-written mm3-to-mm3 migration guide; even > if those files/directories are mentioned in the Bible for installing > Mailman, i don't think this can be found by a normal administrator (it's > not reasonable to assume that one should look up each file/directory in > Mailman's var to see if it is needed). > If you read that Bible with a toothcomb, you will be led to the READMEs which are online. And I think the Developers wrote this summarized version of the 'Bible' with the focus of getting us up and running with MM3 in the easiest way and shortest time. The complete MM3 'Bible' <https://docs.mailman3.org/projects/mailman/en/latest/README.html>is as large as the real Bible itself and that is left for the curious to go read online: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… >> - ./locks: plenty of lock-files, most of them rather stale (as in: 3 > >> years old) > > > > So MM3 on that host hasn't been running or? > > it *is* running. > i do not know why it didn't cleanup. > > > > - ./messages: a couple of old messages (i think all of them have been > >> held for approval) > >> - ./queue: dirtree without files > >> - ./templates: more templates for the existing mailinglists, though they > >> don't seem to be used (are these the fallbacks when I remove a template > >> via the webinterface?) > >> > > > > Yes. > > so can i just ignore them? > I believe it is safe to ignore them. > > So out here we focus so much on the following as the Bible for installing > > and running MM3: > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > probably. > sorry for being obtuse. > > afaict, the documentation is written for people setting things up from > scratch, where the paths are mostly setup automatically, and you only > need to configure them manually for interoperability with other software > (e.g. when using postfix as the MTA, the docs tell the admin to ensure > that both mm3 and postfix communicate via the same paths). > I am not sure that is entirely correct. People have installed MM3 on paths other than what the docs say. Narrowing down on Postfix, I know that all it needs to be told is how to 'know the lists being created by MM3 in order to handle mail deliveries for MM3'. There are instances where people don't even run a local Postix instance. > i guess i'm confused because it is unclear to me, which of these paths > hold persistent data, and which are just for ephemeral things > (like sockets). > In the summarized Bible, there is a reference to https://docs.mailman3.org/en/latest/config-core.html#config-core, which tells you that! There are also other references to the things you are interested in. Just a little more curiosity and you find them. PS: I saw the point you raised about the "the yet-to-be-written mm3-to-mm3 migration guide". In one of my responses to your posts, I attempted to write part of the process off the top of my head. I think you are going finish writing it for us since you are on that path. You will be able to complete the portions that I left out. Your experience, if documented and discussed here (addressing the pitfalls on the way) will finally bring forth that document. Or a semblance of it. -- 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]

1 year, 11 months

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Mark Sapiro

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

7 years, 3 months

[MM3-users] Mailman archive issues (Hyperkitty)

by klillipuu＠gmail.com

Hello All! I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). I also mention, that hyperkitty is a pretty old version - 1.1.4. The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? Extra information: * I have also noticed some memory violation issues which has caused by uwsgi. * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Output from mailman.log: HyperKitty failure on http://localhost/hyperkitty/api/mailman/archive: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (504) Exception in the HyperKitty archiver: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (1808) Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html>

5 years, 2 months

[MM3-users] Re: Postfix-Fehler mit mailman-web

by Jens Günther

Am 28.08.23 um 10:21 schrieb Stephen J. Turnbull: > Jens Günther writes: > > > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: > > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host > > rejected: cannot find your hostname, [192.168.176.6]; > > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> > > There are a bunch of $myxxxx variables in Postfix, I think $myhosts > might be the right one. If you add the IP 192.168.176.6 to that > variable, it will be whitelisted and this problem should go away. > There may be better ways to handle this, but don't mess with > hostnames. Find the "right" way to permit that IP should do the job. Thank you, adding the IP/network under mynetworks, as Abhilash writes, the error is gone. (this is so dumb, somehow docker started with a different IP and I have to figure out why ... and there is another Django-error -> shall I open a new thread? "OSError: [Errno 99] Address not available") > > I mean the hostname for the core-container must be there, since > > mail is accepted :-D > > That's not the way this works. Postfix accepts the mail because it's > arrives at the physical host, then looks up routing for the mailbox > and discovers it should be delivered via LMTP to the core container's > IP. No hostname needed. Ok, probably a misunderstanding. I was saying, that mails from core are relayed correctly to the outside world ... that's because the mailman-network was was relayed, but as I wrote, the web-container somehow got a different IP now. Thanks again.

2 years, 11 months

[MM3-users] Re: How to remove a nonmember from a list

by skenny＠scss.tcd.ie

Abhilash Raj wrote: > Could be, I am not sure which operation is it stuck at. Can you check logs to see > where is it breaking? Sure. I'm doing all this under Docker; below is what I see in /opt/mailman-web-data/logs/mailmanweb.log when I try to delete a nonmember via the web interface. Thediagnostics appear 30 seconds after I click on 'delete': ERROR 2020-04-09 20:35:51,482 19 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 421, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 416, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 720, in urlopen method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] File "/usr/lib/python3.6/site-packages/urllib3/util/retry.py", line 400, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/lib/python3.6/site-packages/urllib3/packages/six.py", line 734, in reraise raise value.with_traceback(tb) File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 421, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 416, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 96, in call headers=headers) File "/usr/lib/python3.6/site-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 533, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 646, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", line 38, in wrapper return fn(*args, **kwargs) File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line 943, in remove_role roster = getattr(the_list, '{}s'.format(role)) File "/usr/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 86, in nonmembers response, content = self._connection.call(url, data) File "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 119, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie The file /opt/mailman-web-data/logs/uwsgi.log contains just one line: [pid: 19|app: 0|req: 82/96] 172.19.199.5 () {46 vars in 1233 bytes} [Thu Apr 9 20:35:20 2020] GET /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie => generated 5583 bytes in 31411 msecs (HTTP/1.0 503) 5 headers in 180 bytes (1 switches on core 0) > Can you try doing the same with the REST API, just to verify if it is the Core which > has the issue or it is the web frontend. Using the REST API, I can successfully remove a named nonmember from the list. But I see the same pause-then-fail behaviour when I try to simply list all the nonmembers. My snippet of code can happily produce a listing of the members, but it gets stuck trying to list nonmembers, and then 30 seconds later it crashes out with exactly the same error messages as when I tried to delete a user in the web interface (see above). My piece of code appears below (II invoke it like this: docker exec -it mailman-core bash -c 'python3 /opt/mailman/local/probe.py scss-sysadmins(a)lists.scss.tcd.ie'). from mailmanclient import Client from mailmanclient import MailingList import sys my_list = str(sys.argv[1]) client = Client('http://172.19.199.2:8001/3.0', 'restadmin', 'restpass') this_list = client.get_list(my_list) print("\n\nMembers:\n-------------------------------------------------") for i in this_list.members: print(i) print("\nNonmembers:\n-------------------------------------------------") for i in this_list.nonmembers: print(i) Thanks again Stephen

6 years, 3 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Eggert Ehmke

Hello Mark, thank you. I did change that entries, and now my mailman runs fine on Debian Bookworm. I did a complete reinstall of the venv directory to have a clean start. Maybe this was not needed. What's missing in the documentation: -the directiories web/logs have to be created manually with the ownership mailman. -The debian package pkg-config must be installed. -the package psycopg2-binary can/must be installed without version restriction on Bookworm Maybe this info helps some other people. Cheers, Eggert Am Montag, 26. Juni 2023, 22:22:37 CEST schrieb Mark Sapiro: > On 6/26/23 12:35 PM, Ken Alker wrote: > > I'm brand new to this, so take this with a grain of sale, but, I had a > > similar problem a few days ago, however, mine was "flufl.i18n>=3.2". > > Perhaps the same thing is happening with flufl.lock (but that didn't bite > > me). > > > > I solved my problem by following this: > > <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately > > modifying > > "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires. > > txt" per that thread (see > > <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by > > Thomas Ward section called "The WORKAROUND"). Maybe you need to do the > > same thing, but for flufl.lock. > Yes, the same issue now affects flufl.lock as well as flufl.i18n. You > will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 1 month

[MM3-users] Re: Mass subscribe bug - if you delete and re-add users it does not use updated info

by Abhilash Raj

On Thu, Sep 5, 2019, at 3:22 AM, roger(a)reasonal.com wrote: > Hi all -- think this is a bug. I had added some users as a mass > subscribe. Some were Name Surname <name(a)foo.bar> format, some were just > email addresses. I wanted to update the member list with complete name > & email addresses. I unsubscribed the partials, and re-added them as > full versions. However the updated member list keeps showing the > partial address only. > > This bug also works the other way. I added "Bob Smith <bob(a)bob.com>", > checked it was there in list. Unsubscribed the address, and then > re-added as "bob(a)bob.com" -- now in the members list it appears as the > full "Bob Smith <bob(a)bob.com>. This behavior happens because Mailman will remember all the "users" once it has seen it. It usually doesn't update the user's name (add or remove) it once it knows about it. Addition might be something we *could* do, but I don't think it makes sense to remove the user's name. Note that the user you add and subscribe has the ultimate control over their name. "Subscription" or "Unsubscription" process merely links or unlinks them with the MailngList. The link is what is called a "Member". > _______________________________________________ > 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, 10 months

[MM3-users] Re: Problem with database change sqlite -> mysql

by Stephen J. Turnbull

moritz both writes: > > "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/query.py", > > line 435, in get > > raise self.model.DoesNotExist( > > hyperkitty.models.email.DoesNotExist: Problem installing fixture > > '/home/daneben/mailman-suite/datadump.json': Email matching query does > > not exist. I assume you're using "python manage.py dumpdata > datadump.json" to dump and "python manage.py loaddata > datadump.json" to load the data? Are you using the right python binary, ie the one Django uses? I guess it's possible that some data is not in the database, but retrieved from Mailman core's on the fly, in which case you need Mailman core running. That said, this is entirely handled by Django, I think, and you might be better off asking on Django channels. I'll give you a couple of wild guesses, but unless somebody else knows more about Django than I do, it's probably fastest to ask on Django channels. I did a quick search for "datadump.json" and brought up these references, but none seem to refer to Mailman: https://stackoverflow.com/questions/4371375/db-error-when-running-python-ma… https://www.reddit.com/r/learnpython/comments/8jkre9/deserializationerror_w… https://www.rockandnull.com/django-dumpdata/ Here's a tutorial on SQLite to MySQL migration in Django: https://newbedev.com/what-s-the-best-way-to-migrate-a-django-db-from-sqlite… These are tutorials on SQLite to PostgreSQL migration in Django: https://www.solution-hub.com/Blog_description/37/ https://dev.to/thepylot/how-to-migrate-data-from-sqlite-to-postgresql-in-dj… https://gist.github.com/sirodoht/f598d14e9644e2d3909629a41e3522ad https://simpleit.rocks/python/django/migrate-django-sqlite-to-postgresql/ Perhaps one of those references will help. Steve

4 years

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

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

3 years, 10 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/24/23 07:20, Stephen J. Turnbull wrote: > > The only thing I can think of at the moment that might move the > discussion forward is if Mark knows how to run his test in your Docker > environment to see if it also produces > Content-Type: text/plain; charset="US-ASCII" > Content-Transfer-Encoding: 7bit Assuming there is not something like ``` [language.en] charset: utf-8 ``` in your mailman.cfg overriding the default us-ascii charset for English, if you send a message From: yourself to list-confirm-xxxxxxx(a)example.com with Subject: Re: Your confirmation is needed to join the list(a)example.com mailing list (replacing list and example.com with the actual list and domain), you should receive a response like (some headers removed) ``` Subject: The results of your email commands From: list-bounces(a)example.com To: mark(a)example.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: <169556563227.2592.7908020161516725770(a)example.com> Date: Sun, 24 Sep 2023 07:27:12 -0700 Precedence: bulk X-Mailman-Version: 3.3.9b1 List-Id: A test list <list.example.com> List-Help: <mailto:list-request@example.com?subject=help> List-Owner: <mailto:list-owner@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> The results of your email command are provided below. - Original message details: From: Mark Sapiro <mark(a)example.com> Subject: Re: Your confirmation is needed to join the list.example.com mailing list. Date: Sun, 24 Sep 2023 07:27:10 -0700 Message-ID: <20230924142710.GA23819(a)example.com> - Results: Confirmation token did not match - Done. ``` What do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Held messages not delivered after approval

by Stephen J. Turnbull

Stephan Krinetzki writes: > And then there is a logrotate: > And yes, this restarts mailman at midnight. Maybe i should optimize > the logrotate. Not sure what you mean by "optimize". Because of the bug I mentioned earlier, in older versions of Mailman 3 the master process would fail to close some of logfiles. After rotation, the master process would continue writing to the still-open file handle, defeating the purpose of logrotate. Unless that bug has been fixed in your version, you should leave the restart stanza in the logrotate for configuring mailman. That the shunt queue is collecting digests seems weird. It's not surprising that the message object in the queue file is empty, that's by design. It seems like the digest process is happening at the same time as the restart. This shouldn't be a problem, but it might clarify things if you make sure the periodic digest delivery is offset from the midnight restart in the /etc/cron.d/mailman3 file. Eg # cron time is UTC, put stuff on desks at start of day JST # core sends mail 22 5 * * * mailman /opt/mailman3/.v/bin/mailman notify 22 6 * * * mailman /opt/mailman3/.v/bin/mailman digests --periodic (note 22:00 UTC is 07:00 JST). My only other comment on your mail is that I see that you do have multiple out slices. So that explains the case of the .pck.bak (in process) file being younger than a .pck file (waiting in queue). It's not unusual in your configuration. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year

[MM3-users] Re: Python 3.13 compatibility

by Washington Odhiambo

On Sun, Mar 29, 2026 at 6:11 PM Thomas Krichel <krichel(a)openlib.org> wrote: > Mark Sapiro writes > > > If you do that and it results in a working system, you can then patch > > mailman/utilities/i18n.py as follows > > Thank you. This works, and I can successfully import a first > list configuration. > > > However there are other incompatibilities between the released Mailman > > versions and Python 3.13. > > Hmm https://docs.mailman3.org/en/latest/install/virtualenv.html > states "3.13 is recommended as it is the latest version of Python > with which Mailman is tested." > > > At the moment, until updated packages are > > released, in a Python 3.13 environment it is best to install all of > mailman, > > django-mailman3, postorius, hyperkitty and mailman-web from the heads of > the > > gitlab branches. > > I would love to see a command line for that. When I go to the gitlab > page, https://gitlab.com/mailman/, I see a bunch of project that > don't immediately correspond to pip package names. > pip install git+https://gitlab.com/mailman/mailman@master pip install git+https://gitlab.com/mailman/mailmanclient@master pip install git+https://gitlab.com/mailman/mailman-hyperkitty@master pip install git+https://gitlab.com/mailman/hyperkitty@master pip install git+https://gitlab.com/mailman/django-mailman3@master pip install git+https://gitlab.com/mailman/postorius@master pip install git+https://gitlab.com/mailman/mailman-web@master -- 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]

4 months

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

by Mark Sapiro

On 6/13/25 01:59, Florian Sukup wrote: > > > On 6/13/25 01:58, Mark Sapiro wrote: > >> but I'm at a loss to understand the issue, unless your >> /etc/postfix/master.cf is missing an uncommented entry for lmtp like >> ``` >> lmtp unix - - y - - lmtp >> ``` >> > > I found it there, here is my master.cf: I realized after the fact that that probably wasn't the issue because it probably would have logged an error. > mailman unix - n n - - pipe > flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Is the last line a problem? It seems to be from mailman2. It's a Debian thing for an unsupported MM 2.1 process to deliver mail to Mailman. It doesn't do any harm if it's not referenced in main.cf. > Is there a possibility to debug in more detail? To find out when and > where it takes the wrong turn? I'm unable to see where this is going wrong. I think it is a Postfix issue, not a Mailman issue per se, and while we make a best effort to help with Postfix-Mailman integration issues we are not the primary support resource for Postfix which is the postfix-users(a)postfix.org mailing list. See https://www.postfix.org/lists.html for info on subscribing and posting. Also, since you are dealing with Debian packages, the primary support resource is Debian. See https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Abhilash Raj

Excerpts from Simon Liebold via Mailman-users's message of May 29, 2017 2:16 pm: > Am 28.05.2017 um 22:24 schrieb Mark Sapiro: >> 'Delete this message' is in the 'message' view. "Delete this thread" is >> in the 'thread' view. > > Now found the message view. Thanks. > >> HyperKitty requires Django<1.11. The comment in the requirements in >> setup.py implies this is only a django-haystack requirement >> >> "Django>=1.8", >> # Don't upgrade to 1.11 until django-haystack supports it: >> # https://github.com/django-haystack/django-haystack/pull/1499 >> "Django<1.11", >> >> but since it works for me with Django 1.10, you might want to try that. > > OK, I was still running an RC version. Silly me. > >> In particular, this looks like Django 1.11 bug >> <https://code.djangoproject.com/ticket/27975>. > > Which was closed in the release version that I initially upgraded to > (1.11.1). > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > You may have to do `python manage.py makemigrations` after adding a new INSTALLED_APPLICATIONS and before running `python manage.py migrate` Hope that helps! -- thanks, Abhilash Raj

9 years, 2 months

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

by gordon＠dickens.com

Hello Mark and everyone else, I made significant progress in that I got the web interface working. The file permissions were wrong for the /var/log/mailman3/web directory in that the web directory needs to be writable by www-data (the apache user), Also, the aliases in the Apache configuration needed to be changed to the following: Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /static/ /var/lib/mailman3/web/static/ Once I fixed these issues then I was able to successfully access the web interface and login. Now, I am able to access the web interface and I am able to navigate to all of the main links on the top of the main page including: Postorius. Lists, Domains, Bans, System Information, Users and Archives. My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: "Server error An error occurred while processing your request." Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" This email and my logs now complain about: "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ get() returned more than one EmailAddress -- it returned 3!" Also, I get the same errors after I create a new mailing list as well. I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! Thanks, Gordon

4 years, 5 months

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Ibiam Chihurumnaya

Stephen J. Turnbull wrote: > Please don't reply to unrelated threads when reporting a new issue. > It's not just the subject being wrong (Django has nothing to do with > delivery, this is a problem with viewing archives, I believe). > Continuing a thread with an unrelated issue creates an apparent > context which is at best temporarily confusing, and could interfere > with solving the problem in worst case. You're right, I'll open a different thread for this. > Ibiam Chihurumnaya via Mailman-users writes: > > ERROR 2026-02-12 14:15:11,250 1985547 django.request Internal Server Error: /archives/list/soas(a)lists.sugarlabs.org/thread/CVAUPR7L6AYTNZXIWHQ263A6ZJUROTRC/ > > This is in HyperKitty, viewing a thread or a thread index. > > 233904 File "/opt/mailman/venv/lib/python3.10/site-packages/mistune/list_parser.py", line 178, in _parse_list_item > > 233905 block.parse(child, rules) > > 233906 File "/opt/mailman/venv/lib/python3.10/site-packages/mistune/block_parser.py", line 458, in parse > > 233907 end_pos2 = self.parse_method(m, state) > > 233908 File "/opt/mailman/venv/lib/python3.10/site-packages/mistune/core.py", line 214, in parse_method > > 233909 assert lastgroup > > 233910 AssertionError > > I'm pretty sure this is a known bug in mistune. It's pretty much > identical to the head of the thread ending the message below. (I > don't think there's anything interesting in the followups to the > thread, it's a different problem.) > See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... Thank you! > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan

5 months, 3 weeks

[MM3-users] Re: Receiving Email from ListName-bounce@Domain for Unsubcribe

by Marin Sok

Hi Mark, I changed it and it works as expect now. Thanks a lot for your help guide me on this. [cid:1c0306de-6190-48ad-a8f3-b67ffd1a48a3] Thanks, Marin <http:\\probonoweek.lalawlibrary.org> [http://www.lalawlibrary.org/sigimages/logo-sig.png] Marin Sok IT Director P 213.785.2556 | F 213.680.1727 http://www.lalawlibrary.org/<http://www.lalawlibrary.org/> | MSok(a)lalawlibrary.org Access to Information = Access to Justice <http://probonoweek.lalawlibrary.org/> Follow us: [http://www.lalawlibrary.org/sigimages/facebook.png] <http://facebook.com/LALAWLIBRARY> [http://www.lalawlibrary.org/sigimages/twitter.png] <http://twitter.com/LALAWLIBRARY> [cid:SocialLink_Instagram_32x32_dc37fa34-8ab4-41db-9940-9cb519436518.png] <https://www.instagram.com/lalawlibrary> ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, February 16, 2026 2:44 PM To: Marin Sok <MSok(a)lalawlibrary.org>; Stephen J. Turnbull <steve(a)turnbull.jp> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Receiving Email from ListName-bounce@Domain for Unsubcribe [You don't often get email from mark(a)msapiro.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] On 2/16/26 13:55, Marin Sok via Mailman-users wrote: > > Should I try to modify the code in file notifications.py in line 137. You could change that line from address, mlist.bounces_address, to address, mlist.owner_address, if you feel it's important. I will probably do something about https://gitlab.com/mailman/mailman/-/issues/1260<https://gitlab.com/mailman/mailman/-/issues/1260> so it will be fixed for the next release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Content-Type: image/png Name: SocialLink_Instagram_32x32_dc37fa34-8ab4-41db-9940-9cb519436518.png Replaced multipart/alternative part with first alternative.

5 months, 2 weeks

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

by Mark Sapiro

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

4 years, 6 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

Hi Rafael, On Wed, Jul 19, 2017, at 01:49 PM, Rafael Mora wrote: > Hello, > > What are the suggested steps in order to install the web UI ?? I haven't read through this entire thread but I understand that you are having problems with multiple configuration files for Core and setting up the Web UI. The installation guide at docs.mailman3.org should now have a "Pre-Installation Guide" and another new section called "Configuring Mailman 3". Please make sure than you read both of them along with the "Installation Guide" They have more information about how to setup Mailman 3 after you have installed them so that it becomes function. Also, your original question's answer can be found there. It has instructions about how to setup your Django project, which is the what the Web frontend for Mailman 3 is based on. > > Thanks > > El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< > kylerichardson2(a)gmail.com>) escribió: > > > There must be another config file being picked up. Have a look at the > > mailman.cfg search order explained here [1]. > > > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' > > to be sure. You'll want to delete any in the search path and then rerun > > 'mailman info'. > > > > [1] > > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > > > -Kyle > > > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

9 years

[MM3-users] Re: Mailman 3 localization

by Alexander Klotz

> I wanted to set it up, but the requirement is to use a free hosted > solution. (So transifex and crowdin are a no-go, they would be great to > get translations, especially crowdin looks very active in that regard) > I tried out zanata.org but it's extremely slow... > The other option at the time was pootle > (http://pootle.translatehouse.org) which doesn't offer hosting but some > folks at gnu had a customized instance set up, but they discontinued the > service. > > I searched for a translation service for a private project and found > weblate.org . They offer hosting (hosted.weblate.org) for open source > projects and it looks like a couple of people are using it. You need to > contact them if you want to set it up for an open-source project though > and I didn't want to invest in it without knowing what the end-result > would be... > > Since I'm also mainly interested in German translations for my own > installation, I opted to just use plain .po files and filed merge > requests against the repositories. Postorius has translations (not > perfect, but a start for the moderators that use my instance) included > by now but my merge request for core is still outstanding > https://gitlab.com/mailman/mailman/merge_requests/400/ > Since I don't use Hyperkitty, I didn't translate that. > Thanks for the reply, Simon! We were thinking of using plain .po-files too, however, we couldn't find the matching "src" folder in our installation, do you have any more details where it or the .po-files may also be located? Regards, Alex

8 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I think you have to open a new issue to modify the website for the mailman-suite git clone, it should be: git clone https://gitlab.com/mailman/mailman-suite.git El vie., 21 jul. 2017 a las 14:07, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Installing mailman-suite for web ui. I did this: > > (env) [mailman@localhost ~]$ git clone > https://gitlab.com/mailman/mailman-suite/ > Cloning into 'mailman-suite'... > error: RPC failed; result=22, HTTP code = 404 > fatal: The remote end hung up unexpectedly > > > but it returned an error, what should I do?? > > Thanks > > > > > > > > El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 10:29 AM, Rafael Mora wrote: >> > Can we modify the docs? >> > >> > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) >> > escribió: >> >> >> >> However, that said, the doc is wrong. The lines should be added to >> >> main.cf, not master.cf. See >> >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. >> >> >> That's what the above issue and associated MR are for. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- Atentamente / Best Regards Ing. Rafael Mora

9 years

[MM3-users] Re: Apple Mail encoding again

by tlhackque

On 21-Apr-22 13:09, Mark Sapiro wrote: > On 4/21/22 04:53, tlhackque via Mailman-users wrote: >> >> Note that MailMan is encapsulating a multipart/signed message in a >> multipart/mixed in order to append it's footer, and reports that it >> removed the signature part of the multipart/signed. This makes the >> signed message format invalid. So at least, MM3 needs to handle >> signed messages better: either include the signature or remove the >> signature headers (an unwrapping exercise to convert the message to >> unsigned)... Note that this can be recursive where a signed message >> contains a message/rfc822 part that contains a signed message, that.... > > This was an issue with Mailman's content filtering for the > mailmanusers(a)mailman3.org list. Pass types was: > > multipart > message/rfc822 > text > application/pgp-signature > > So the application/x-pkcs7-signature part was removed. I have just > updated Pass types to: > > multipart > message/rfc822 > text > application/pgp-signature > application/x-pkcs7-signature > > to not remove application/x-pkcs7-signature parts going forward. > That's what I expected to be behind the behavior. Thanks for fixing it on this list. But as I noted, it would be better if the application/*signature parts were automagically passed when a multipart/signed is present. Ideally those that correspond to the multipart/signed, but it's probably less work to allow them anywhere. I've seen variations of this misconfiguration on a number of lists, all of whose administrators had to learn by experience. Seems like a good case for Mailman becoming smart enough to do the right thing...

4 years, 3 months

[MM3-users] Re: Reset bounce count in MM3

by iMark

On 2026-03-09 05:03, Mark Sapiro wrote: > It's much easier to 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 >>>> mbr = m.members.get_member('user(a)example.com') >>>> mbr.bounce_score = 0 >>>> commit() > ``` > But what is the point of doing this? If the member is bouncing, the > score will continue to increment, and if not the bounces will become > stale and a future bounce will set the score to 1. ================================================ From time to time Microsoft will spit the dummy and start blocking mail from the lists. This will last a day or two, but in the meantime bounce counts get cranked up which can send some lists over the edge and start disabling/removing subscribers. In a bash script I can query the the database like so: UPDATE MEMBER SET bounce_score = 3 FROM address WHERE address.id = member.address_id AND email LIKE'%hotmail.com' AND member.bounce_score >= 4 AND member.list_id = '<LISTID>' The idea is that the script can be croned hourly for a couple of days on multiple lists to wind down the bounce_counts (preventing disable/remove) while the Microsoft issue gets resolved. > You mentioned reset_bounce.py, but that doesn't reset scores. It sets > delivery enabled for users whose delivery is disabled by bounce, ... Ahh, I see. Thank you for setting me straight on that.

4 months, 3 weeks

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Stephen J. Turnbull

M. Ede via Mailman-users writes: > The triggering rule states: > > SPOOFED_UNAUTH (50) and is determined as follows: > > (1) !MAILCOW_AUTH & > (2) !MAILCOW_WHITE & > (3) !RSPAMD_HOST & > (4) !SIEVE_HOST & > (5) MAILCOW_DOMAIN_HEADER_FROM & > (6) !WHITELISTED_FWD_HOST & > (7) -g+:policies (50) > > This means that nothing is checked here with signatures (DKIM, ARC, > SPF), etc. > > (1) mailman and mailcow are integrated via a Docker network, meaning > mailman is not logged in as SMTP user. > In my case, this should always be TRUE (the sender is "not authorized"). > (2), (3), (4), (6) Exception IPs that are allowed to send emails for > various reasons. > (5) This is FALSE for a non-anonymized list (which is why I don't have a > problem with non-anonymized lists). > For an anonymized list, this is TRUE. This analysis is correct. > As a solution, I now entered the delivering IP in (6) (this can be done > via the Mailcow UI as a forwarding host). This will work for you. The only thing I might do different: I've set up a system where the MTA and Mailman are on different VMs, both visible from a large number of "internal" hosts, and the MTA visible from the public Internet. In that case I used SMTP AUTH both incoming and outgoing (paranoia, justified in the case of that client), but in your case with all the relevant nodes running in containers on a single host I don't think that even gives any extra security. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

10 months, 2 weeks

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

by Bryan Loniewski

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? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:15 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 7:35 PM, Bryan Loniewski wrote: > $ /opt/mailman/mm/bin/mailman version > GNU Mailman 3.3.2 (Tom Sawyer) > > So, I'm running > 3.2. Any other advice on debugging the truncated data? The traceback indicates sqlalchemy is unpickling data whose type is PickleType. The only mailinglist columns which are PickleType are the legacy *these_nonmembers and topics. You could try invoking mysql on Mailman's database and doing SELECT list_name, accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, discard_these_nonmembers, topics FROM mailinglist; and look for the longest values to possibly identify the problem list and attribute. -- 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years

[MM3-users] Re: restricting public lists per virtual domain

by Stephen J. Turnbull

David Newman writes: > Awhile back Stephen Turnbull suggested a terminology guide that > included an MM3-specific definition of FQDNs. I think that Mailman should use the usual definitions, but sometimes we have more restrictive implementations. For example, although we store the case sensitive form of email addresses, some checks for equality of email addresses are case insensitive even though local parts can be case sensitive at some hosts. That can be surprising, although frequently it's what users expect. It's going to be hard to document all of these, but even listing some of them will probably help users diagnose issues for themselves, or suggest improvements. > > Also in an MM3 context, I think it would be useful to distinguish > between mail hosts and web hosts and domains (all in the general > Internet sense) and mail domains and sites (in the > MM3/Django/Postorious/Hyperkitty sense). Yes, this is really complicated. Web hosts aren't too bad, although often www.example.com will be a CNAME for example.com and configurations like that, but Internet mail is quite a mess, what with CNAME, MX, and PTR at least being involved, and if you are doing signatures, all the stuff for SPF, DKIM, DMARC, ARC and more, not to forget that if you're actually sending and receiving mail you need to worry about distinctions among SMTP, LMTP, and SUBMIT, and all of the SSL/TLS versions. *sigh* > Not sure I fully understand these distinctions yet, but I can take a > crack at it. Just list them under "this stuff is really weird, watch out for dragons lest you be toasted from behind". :-) Steve

4 years, 7 months

[MM3-users] Re: Social signup?

by Duane Raymond

Wow - thanks for the redirection on where to patch it and the first-cut code. I'll look into this in 2 weeks when I am able to focus on it. Cheers, Duane On Wed, 15 Mar 2023 at 16:18, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/23 05:08, Duane Raymond wrote: > > > > I'll jump over to the developers list when I start this (I'm about to > > travel for a week to run an annual event in Oxford - so the far removed > > from programming)...but which chatGPT suggested so far was > > > > 1. Extending postorius/signups.html with a loop to get the configured > > social login providers PLUS adding a csrf_token field to the form > > 2. Modifying postorius/views.py (which doesn't seem to exist but > there > > is a postorius/views folder) - so perhaps this is views/urls.py > > > This is not what you want to do for this. The changes need to be in > django-mailman3, not postorius. I have attached a patch which might work > for you. I think it is good, but some of the wording is stuff that may > not be appropriate. See what you think. > > -- > 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 duane(a)fairsay.com >

3 years, 4 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 4:54 PM, Mark Sapiro wrote: > On 1/14/22 11:56 AM, David Newman wrote: >> >> I created a pending subscription request on a test list. Here is the >> text I'm using in a file called 'list:admin:action:subscribe.txt' >> (minus the rows of hypens): >> >> ---------- >> >> >> As list administrator, your authorization is required for a mailing >> list subscription request approval: >> >> For: $member >> List: $listname >> >> At your convenience, visit: >> >> https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ > > This looks like a Mailman 2.1 URL. Are you sure you don't want something > like > > https://${domain}/mailman3/lists/${short_listname}.${domain}/ Yes. The server redirects MM3-style requests to MM2.1 URLs. I need to determine why, but that may be a different issue than the templates one. There's nothing obvious in this vhost's nginx config that would generate the redirect. Will check, if I can't resolve this I'll open a different thread. > >> >> to approve or deny the request. >> >> ---------- >> >> Instead the message that goes out at midnight daily reads like this: > > > That's a different message. It is sent from the `mailman notify` command > run by cron. It's built from the list:admin:notice:pending template. OK, wrong template then. > >> >> On successive nights I have placed copies of the >> 'list:admin:action:subscribe.txt' file above in these locations: >> >> mm/var/templates/lists/test.lists.domain.tld/en > > I hope you mean > > /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en Yes > >> /opt/mailman/mm/var/templates/site/en > > > Either of those should work. The lists one will take priority over the > site one for that list. > > >> and then in Postorius, with the same contents as above. > > If you set a template in Postorius, it takes priority. If you later > decide you want to use one in /opt/mailman/mm/var/templates/ you have to > delete the postorius one. > > >> The file versions are owned by the mailman user, and have 0644 >> permissions. Not sure this is necessary but I've restarted the >> mailman3 and mailmanweb services each time after a change. >> >> There is no sign of trouble in the MM3 or web logs. The only thing I >> see is in the Postfix log, where the shorter and less helpful message >> goes out each night. I don't see anything in the template docs about >> this. >> >> Questions: >> >> 1. What to do to get the custom message working? > > > It should work. I suspect you need to go to the list's Settings -> > Automatic Responses and set `Admin immed notify` to Yes. It's enabled. I think this triggers notifications only for new subscription requests, not pending ones. > > >> 2. Is there a way to trigger a subscribe reminder for one list only? > > > If by subscribe reminder you mean the `list:admin:action:subscribe.txt` > message, yes that's the above list setting. If you mean the one sent > from the `mailman notify` command, see `mailman notify --help` for the > options. You can specify one or more lists (default is all lists) via > options and put them in your cron. > > >> Asking because there are other lists on this server with other >> requests pending, and I don't want to bother other moderators with >> multiple reminders per day. Not a big deal, but it would be nice to >> test this with one list rather than waiting up to 24 hours after each >> change. > > > You can test `mailman notify` at any time by running it by hand. Thanks. This still isn't working as intended. I took these steps: 1. Created the file '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' with these contents (minus the hyphens top and bottom): ---------- The $listname list has $count moderation requests waiting. $data At your convenience, visit: https://${domain}/mailman3/lists/${short_listname}.${domain}/ to approve or deny the request. ---------- 2. Restarted the mailman3 and mailmanweb services 3. As the mailman user, ran the command 'mailman notify -l test.lists.domain.tld -v' This generated an email message but its contents were the same as in my previous post: ---------- The test(a)lists.domain.tld list has 1 moderation requests waiting. Held Subscriptions: User: letmein(a)domain.tld Please attend to this at your earliest convenience. ---------- What I'm trying to do here is replicate a feature from MM2.1, where pending notifications had URLs embedded in the message. That's not available out of the box in MM3, and if there's a place for feature requests I'd be glad to ask that this be made the default. For now, though, I'm looking to get this customization working. Thanks. dn

4 years, 6 months

[MM3-users] Re: Urgent help needed...

by Simon Hanna

On 05/24/2018 06:21 PM, Darren Smith wrote: > Hello, > > This morning our Mailman 3/Hyperkitty/Postorius installation has become > unresponsive. When looking at the machine, postgres is pegging all 4 CPUs > on the machine. > > We did some digging in postgres, and here is the query that is causing > problems: > > "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE > hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY > hyperkitty_email.date ASC LIMIT 1;" > > We have found that it doesn't matter what mailinglist_id is being used. > > We have also found that this might be an issue with the LIMIT 1 - our > investigation is showing that using LIMIT 1 in postgres makes things > execute very differently than if you use a limit 2 or more, and that this > is probably what is going on. > > Basically, every time this gets called, it pegs an entire CPU for 20-30 > seconds. It appears to be called a LOT. > > So our users are getting 504 gateway timeouts right now. > > What has changed: > > We have been in the process of importing our 40 million archived emails > from our old mailman 2 archives. > > Questions: > > 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, > postorius, django - basically anything that might be calling this code, but > we can't find it. Does anyone know what generates this query? It looks like the query is to get the date from the last email for a mailinglist. AFAIK Hyperkitty checks this when new emails get it (maybe even during import) It could also relate to the "active" state of mailinglists...

8 years, 2 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 08:14, Eggert Ehmke via Mailman-users wrote: > I edited this file: > venv/lib/python3.9/site-packages/mailman/commands/cli_members.py > > The content at line 107ff is: > #patch of Mark Sapiro > # if email_only: > if email_only or not address.display_name: > print(address.original_email, file=outfp) > else: > # print(formataddr((address.display_name, address.original_email)), file=outfp) > print(f'{address.display_name} <{address.original_email}>', file=outfp) > > This file is actually executed when I call mailman members. I verified this by uncommenting the first (old) print line. Now each address is printed twice (as expected), with the utf8 code in both lines in case of umlauts. In that case the address.display_name value is the RFC 2047 encoded name. One way this can happen is if the subscribe was via email prior to Mailman 3.3.3. See https://gitlab.com/mailman/mailman/-/issues/802. You could try something like this to fix these. ``` 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. >>> um = getUtility(IUserManager) >>> from email.header import decode_header, make_header >>> for address in um.addresses: ... decoded = str(make_header(decode_header(address.display_name))) ... if decoded != address.display_name: ... address.display_name = decoded ... print(f'Fixed {decoded}') ... >>> # while you're at it do users too. >>> for user in um.users: ... decoded = str(make_header(decode_header(user.display_name))) ... if decoded != user.display_name: ... user.display_name = decoded ... print(f'Fixed {decoded}') ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

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

by Danil Smirnov

Hi Abhilash, Docker builds are failing for the last few days so we don't have this update in the images: https://circleci.com/gh/maxking/docker-mailman/tree/master Could you look at the issue please? Best regards, Danil Smirnov вс, 24 мар. 2019 г. в 07:59, Abhilash Raj <maxking(a)asynchronous.in>: > Hello Everyone, > > Mailman Core 3.2.2 is released and available on PyPI[1]. > > This is a regular bugfix release and I had to do that to fix a version > constraint > which pulled in a pre-release of a dependency (falcon) when installed via > pip > and caused the default install to break. > > There are few other changes included in this release, including a big > refactor > of error reporting in Core's REST API. All the error responses are now > correctly > formatted as JSON with more information about the error. For example, > invalid > inputs for Enum data types return the valid options. Other error message > are > now generated from the input validtor and will be more informative. > > REST API also accepts input as JSON formatted body, alongside the > x-www-form-urlencoded. > > A full list of changes are available here: > > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 > > This release supports Python 3.5-3.7. > > Thanks very much to all the contributors involved in this release. > > > [1]: https://pypi.org/project/mailman/ > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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/ >

7 years, 4 months

[MM3-users] Re: Server 500 error for just one list, just one page

by Mark Sapiro

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

6 years, 1 month

[MM3-users] mailmanweb/django?: too many postgresql DB connections

by api＠egartech.com

Hello, I'm migrating from mailman 2.1 to the latest version (3.3.9) on Almalinux 9 (python 3.19, postgresql 13.16). Have followed the instructions here https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install to perform a clean install on a new VM. Everything seems to be working (well, I just created one list and doing some basic tests). What I have noticed is hundreds of PGsql connections from mailmanweb. Once mailmanweb service is started there are new non-stop DB connections requests (from Django I guess), here is just 1 second from PGsql log: 2024-10-10 12:15:37.112 EDT [3217] DEBUG: forked new backend, pid=3747 socket=10 2024-10-10 12:15:37.113 EDT [3217] DEBUG: server process (PID 3746) exited with exit code 0 2024-10-10 12:15:37.318 EDT [3217] DEBUG: forked new backend, pid=3748 socket=10 2024-10-10 12:15:37.318 EDT [3217] DEBUG: server process (PID 3747) exited with exit code 0 2024-10-10 12:15:37.523 EDT [3217] DEBUG: forked new backend, pid=3749 socket=10 2024-10-10 12:15:37.524 EDT [3217] DEBUG: server process (PID 3748) exited with exit code 0 2024-10-10 12:15:37.728 EDT [3217] DEBUG: forked new backend, pid=3750 socket=10 2024-10-10 12:15:37.729 EDT [3217] DEBUG: server process (PID 3749) exited with exit code 0 2024-10-10 12:15:37.934 EDT [3217] DEBUG: forked new backend, pid=3751 socket=10 2024-10-10 12:15:37.935 EDT [3217] DEBUG: server process (PID 3750) exited with exit code 0 Few minutes later there are around 300 dead (TIME_WAIT) connections to port 5432 like these: tcp 0 0 127.0.0.1:33728 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40392 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:50860 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40254 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40218 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40110 127.0.0.1:5432 TIME_WAIT I'm totally unfamiliar with Django so not sure where even to look, but that doesn't looks right to me. Thanks

1 year, 9 months

[MM3-users] Re: captcha for subscription and account registration forms

by Stephen J. Turnbull

Johannes Rohr via Mailman-users writes: > Last time I tried, [captchas worked well], but maybe that was > before AI became ubiquitous. What we saw was that 2005-level machine learning technology was producing character recognition good enough to beat the distorted character CAPTCHAs in a small number of tries. This was readily available to the most persistent spammers, so CAPTCHAs were not very successful at reducing such attacks to tolerable levels. > Is there another approach that you would recommend? Not my expertise, unfortunately. I would talk to people who work on these problems. At a hunch, maybe the Django people, especially the ones who work on allauth would have ideas. Also you could look for captcha projects (especially on PyPI, where you would find the most easily integrated products) and talk to their developers. Since you seem quite concerned, it wouldn't hurt to try it. It's not hard, and the instructions for the django-simple-captcha package seem straightforward. It can be installed from PyPI using pip. That would pull in all the Python dependencies. You might need to install imaging libraries in the OS, although I think they're usually available. The patch referenced earlier would probably show which files to edit, and where, to add the captchas to the right forms. Even if you don't program Python yourself, anybody with a little experience should be able to do it. Just make sure you make backups of any file you change, and a list of them, so you can revert easily. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months

[MM3-users] Re: Authenticating against Hyperkitty's DB

by Abhilash Raj

On Thu, Jul 25, 2019, at 12:36 PM, Marvin Gülker wrote: > Hi, > > inspired by the question about LDAP, I want to ask a related > question. We're currently thinking about adding a wiki to our small OSS > project, and requiring users to have multiple accounts for the same > project is nonsense. We don't have LDAP set up yet, but we do have a > running Mailman 3 installation, including Hyperkitty. Thus I thought > about whether it's possible to just write some glue script that > authenticates against the user information in Hyperkitty's database. > Creating an account for Hyperkitty would then be sufficient to get > access to the wiki. > > Could someone give me a hint where and in what format Hyperkitty stores > the user information into its database? So, Hyperkitty itself doesn't concern with authentication and it is handled by django-allauth, which itself hooks into the higher level authentication API provided by Django. Django allows for pluggable Authentication backends, that it can use to authenticate requests. You can read more about it here[1]. We use Django-allauth as an authentication backend. You can use the higher level `django.contrib.auth.authenticate()` [2] function with right values in a Python script running in the same virtualenv to authenticate the user to your wiki. [1]: https://docs.djangoproject.com/en/2.2/topics/auth/default/ [2]: https://docs.djangoproject.com/en/2.2/topics/auth/default/#django.contrib.a… > > Marvin > > -- > Blog: https://mg.guelker.eu > _______________________________________________ > 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)

7 years

[MM3-users] Re: Change Member's Address

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > Stephen: I will be collecting the information requested. However, > the address "xxxxxxxx" is the superuser that lets me log in. "uuuu" > is/are the address of the superuser I can't confirm. Usually there's only one superuser account. There's no reason not to have more than one. Caveat, I've always used SQL UPDATE to toggle the superuser and staff bits on an existing account. But I would imagine using createsuperuser to make the additional superuser accounts would work as well. I do not understand how you created two instances of the "uuuu" address and linked user accounts. Maybe there's some kind of race condition > It does not appear that "uuuu" is in the address table. That's definitely possible. It's probably just because it's never been used to attempt to post or be a member (including owner or moderator) of a list. Mailman core manages that table. I don't think Postorius updates it except as a side effect of creating list members, which is does through a proxy object which manages a core User object accessed via the REST API. > As for the unexplained addresses in there, mailman2 does not use > mysql, does it? No, Mailman 2 does not use SQL. But if you ever tried to migrate the list, the mailman2 addresses and subscriptions would be in Mailman 3's MySQL database until explicitly deleted or the database dropped, even if you deleted the original Mailman 3 installation and reinstalled. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 2 weeks

[MM3-users] Re: Migrate from mysql to postgresql

by Bjoern Franke

Hi, >> >> I tried to convert it with pgloader, but some identifiers had to be cut off: >> _address_id); >> 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner >> idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e >> wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac >> gekrzt > > > > I suspect the issue is due to the way Mailman supports different > databases via SQLAlchemy. The bottom line is the table and column > specifications are based on the Mailman database models, but are > database specific. Now with the via pgloader converted db I get: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context context) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 450, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) FEHLER: Operator existiert nicht: character = uuid LINE 4: WHERE "user"._user_id = 'd254e5dc-188a-48de-8b99-3cbe81155c1... ^ HINT: Kein Operator stimmt mit dem angegebenen Namen und den Argumenttypen überein. Sie müssen möglicherweise ausdrückliche Typumwandlungen hinzufügen. [SQL: 'SELECT count(*) AS count_1 \nFROM (SELECT "user".password AS user_password, "user".id AS user_id, "user".display_name AS user_display_name, "user"._user_id AS user__user_id, "user"._created_on AS user__created_on, "user".is_server_owner AS user_is_server_owner, "user"._preferred_address_id AS user__preferred_address_id, "user".preferences_id AS user_preferences_id \nFROM "user" \nWHERE "user"._user_id = %(_user_id_1)s) AS anon_1'] [parameters: {'_user_id_1': UUID('d254e5dc-188a-48de-8b99-3cbe81155c11')}] Jun 14 12:30:43 2018 (22147) 127.0.0.1 - - "GET /3.0/users/279578694160539064315719588335836290065/addresses HTTP/1.1" 500 59 root@srv20 /etc/mailman3 # > If I were doing this, I would dump the data from MySQL, but rather than > using the CREATE TABLE queries from the dump, I would let Mailman create > a new PostgreSQL database and then just load the existing tables from > the MySQL dump. Unfortunately that did not work due to some missing indexes. Regards Bjoern

8 years, 1 month

[MM3-users] Re: update_index

by Darren Smith

Holy cow I think that's exactly what the problem is. I will give that a try and let you know what happens! On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/03/2018 09:02 AM, Darren Smith wrote: > > Hello, > > > > If I'm reading the docs correctly, when we run manage.py update_index, it > > should be an incremental index of new emails that have been added since > the > > last time update_index was run - can anyone confirm that this is the > > expected behavior? Or is there another command line option that I am > > missing? > > > There are two ways to run update_index. > > Hyperkitty's update_index is incremental and is run by > > manage.py runjob update_index > > Running > > manage.py update_index > > runs haystack's update_index which with no options does a full update. Run > > manage.py update_index --help > > to see the options. The incremental 'manage.py runjob update_index' > should be run every minute by 'manage.py runjobs minutely' assuming cron > is running the periodic Django jobs, so running either update_index job > manually shouldn't be necessary > > > ... > > So...can anyone help with how to get the update_index to do only emails > > added since the last time the update_index was run? > > > manage.py runjob update_index > > -- > 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/ >

8 years, 4 months

[MM3-users] Re: spf/dkim/dmarc

by Stephen Turnbull

Christian writes: > 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record This says it's parsing your mail session and using the MAIL FROM. > 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with > 550-5.7.26 the ip: [192.46.218.224]. At least Google is seeing the mail arrive from the expected IP address. > To best protect our users from spam and > 550-5.7.26 phishing, the message has been blocked. > Could the hard fail policy be implicated in the gmail rejection? It certainly could. However I would expect the DSN to say "because of the hard fail specification we are rejecting your email" in that case. This looks like a Gmail policy to me. > Other than readdressing my server, is there anything else I can do? I don't think readdressing is going to help unless you're referring to the PTR issue mentioned below. I see the same SPF record you have described before: lists.ccalternatives.org descriptive text "v=spf1 a mx ip4=192.46.218.224 -all" so I'm not sure what is going on with Odhiambo's lookup. However, there is an error (the '=' after ipv4 should be ':'), and it has some other problems: 1. the 'mx' mechanism is a no-op because lists.ccalternatives.org has no MX record. 2. the PTR for 192.46.218.224 points to mail.ccalternatives.org, not to lists.ccalternatives.org. Neither should cause an SPF check to fail but they make the check more expensive. I would simplify your TXT record to "v=spf1 ip4:192.46.218.224 -all" because the 'a' mechanism isn't working and the 'mx' mechanism is a no-op. That's really all you need. Steve

3 years, 2 months

[MM3-users] Re: Ready to try installation: use "normal" install or docker.

by Abhilash Raj

On Tue, Aug 1, 2017, at 09:50 AM, Tom Browder wrote: > On Tue, Aug 1, 2017 at 12:28 Abhilash Raj <raj.abhilash1(a)gmail.com> wrote:>> Hi Tom, > .... >> On Tue, Aug 1, 2017, at 07:54 AM, Tom Browder wrote: >> > I'm leaning toward installing using the docker method but I would>> > appreciate any recent thoughts about which method to choose. >> >> It really depends on what way you want to go, container images will be>> much less hassle to use right now, mostly because all the dependencies>> are bundled in and the moving parts are already configured to work with>> each other. > > Abhilash, thanks for the response. > > My goal is to use the installation in production immediately (production meaning using some interested friends as testers before opening lists to "real" subscribers).> > If I understand properly, the docker way will be a good path to do that and it should make my volunteer maintenance life easier in the future, too.> > Does that sound reasonable? While other non-developers would be able to tell you more about how easy it is to administer these container images, I think I have made them easy easy as possible to deploy without having to worry about inner workings. Unless ofcourse you want something more customized, it should work Ok for you. I am planning to release some new bugfixes and enhancements very soon, maybe today or tomorrow depending on when can I get some time. That release should be a significant improvement over the current one with ease-to-use factor. -- thanks, Abhilash Raj

9 years

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Abhilash Raj

On Thu, Oct 26, 2017, at 11:23 AM, Andrew Hodder wrote: > I have an odd one, my Hyperkitty is functionally working fine (archived > several lists without issue, can login/out), however I must have done > something wrong during it's setup as it's layout is completely broken > (and > it keeps throwing Example.com up in the top-left corner). You need to change SITE_ID in your Django's configuration to point to your domain name you want to be show there. Default is set to `example.com` which corresponds to SITE_ID=1 in the Django's configuraiton. How to find the SITE_ID of your domain? This is rather no-so-nice right now, you will basically have to go to the admin console (/admin/) and login as admin. Then you visit `/admin/django_mailman3/maildomain/` and you should see your domain there. Clicking on it will how your it's id in URL bar, like /admin/django_mailman3/maildomain/2 or something. I understand this is rather difficult thing to do, there is an issue open to make this information visible in the UI. Ideally, SITE_ID is sequential, so if you have only one domain, it is most probably 2. > > See attached. > > I'd run into a similar issue with Postorious when I first set it up, but > I > can't recall what fixed it. Any ideas to what needs correcting? Thanks. > > > > Sincerely, > > Andrew Hodder > Systems Administrator > Support Operations, Afilias > E-mail: drew(a)afilias.info > Phone: +1 416.673.4164 > Fax: +1 416.646.1541 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 9 months

[MM3-users] Re: Moderation Action Changed After Import

by Mark Sapiro

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

5 years, 5 months

[MM3-users] How to delete non-users

by Allan Hansen

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 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. 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 b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) Any help with this is appreciated. Yours, Allan I'm still at Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] My system used to be kept up to date by EMWD, but since Brian died have not been able to get it updated, and I'm too scared (from my attempts at installing MM3) to attempt it myself. If the above can only be solved via an update, I'd appreciate a referral.

3 years, 10 months

[MM3-users] Re: Moderated unsub requests are not provided by mailman3 service

by Joachim Schrod

Mark Sapiro writes: > On 11/29/24 4:47 PM, Joachim Schrod wrote: > > > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > > both on Debian 11 (bullseye). > > > > I know that this is out of date; thus a definitive info "this is fixed > > by now" is quite OK for me. (Debian upgrade is planned as the next > > action after getting Mailman3 to work for that use case.) > > Yes, this is fixed. Thanks for the information that it's fixed in Postorius 1.3.6; that information is a great help, it means that I don't need to spend more time on debugging resolved issues. I tried to gather data if an update to Debian 12 (bookworm) would help. But packages.debian.org is not helpful at all, for me. I know that this is beyond the realm of this mailing list, but perhaps someone here has that information and can supply it: Debian 12 (bookworm) package mailman3-web has the version "0+20200530-2.1". This is supposed to be from some source package mailman-suite that is a salsa project that I don't grok at 1st and 2nd sight. Can anybody please provide me with information what versions of mailman3 core and mailman3-web are in this package; i.e., in Debian 12 (bookworm)? Sorry, but I'm not versed enough to understand the information about Debian packages that my search delivers. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

1 year, 8 months

[MM3-users] Strange behaviour when SSL (https) is activated

by Stephen J. Turnbull

François TOURDE writes: > But if I activate SSL on the web server, I'm unable to login. I go to > the /admin, prompted for the user/pass, and got a Firefox error page > saying "Échec de la connexion sécurisée". According to Google Translate, this means "Secure connection failed", which seems to be a webserver problem, not a Mailman problem. Recent Firefox is very picky: it wants a proper certificate (although free certificates such as CertBot will do), and it won't accept SSL or TLS versions less than 1.2. Make sure that your webserver is properly configured to use TLS >= v1.2, and has a properly configured certificate. > [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) > Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) > OSError: write error > [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 > bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => > generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes > (1 switches on core 1) This suggests that you're seeing a variant on the "redirect from HTTP to HTTPS loses POST data" problem. The description of the problem is different and I have no idea what your configuration is, but if the advice (not the problem description) looks familiar the following post may be of help: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Any hint appreciated ;) More information about your webserver and Django configurations would be useful.

4 years, 7 months

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

by Paul Arenson

Well more to report. CPanel says: "Thanks so much for reaching out. I know the mailman upgrade is definitely something many people are looking forward to, but it’s not something we’re able to support at this time. As uncomfortable as it is, the only current option would be to install MM3 and see what breaks. Since we have a minimum requirement for our consideration of their software (being able to migrate people in place), we haven’t done any testing, so it’s not possible for us to say what would or wouldn’t work. Unfortunately you will have to make the best call for your customers, but without our testing I have to advise against trying a manual install of Mailman." There is still the possibility of Discourse (suggested by a member of this forum). But it would require a hosted account somewhere as to host it oneself, you need VPS and something called Docker. I tried a free version of it on Disroot a while ago and it seemed ok, but the Disroot collective was very slow responding, plus you had to see other people's conversations. So while I wait for Mailman 3 on CPanel, this might be another solution. Thanks. PS... I am 66 and have lived outside the US since the age of 27. The language has begun to pass me by. The CPanel rep's use of REACHING OUT is a case in point. When I was in the US, you reached out to someone in trouble, Since I am in trouble, I do to feel I am reaching out to CPanel. I guess that is the nature of language change though.

7 years, 10 months

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

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210216 16:24]: > But if the admin should respect the DBS (disabled by subscriber) > setting, DBS|DBA (disabled by admin) is logically equivalent to DBS. > Are there use cases where the admin does not want to repect the > subscriber's choice, and enables it anyway? What are they? To support a user saying "I have disabled myself and can't re-enable it, can you help me please". So basically when acting on-behalf of the user. > > Or while importing from another server, and there are people who > > have receiving mails disabled, this is the state that could be used > > for it. > > Why wouldn't they get the exact state from the original server? Or do > you mean from a non-Mailman server? For example, however there are no more imports from yahoogroups (that's why I started using mm3). > This is possible. If it occurs less than once in a million years, > it's "too unimportant" to even think about.[2] Have you actually done > this, or know anybody who has? I'm happy to have forgotten much of my past experience, and for "my" archives I hope to be soon able to switch from subscriber-only to authorized-user-only, so doesn't matter too much for me anymore. Otherwise, I think the good thing of this discussion is that we have now clearly written up the current state machine. Otherwise, I just wrote up my favourite but if it stays the current way, well, that's ok of course as well. :) Thanks for your answers and time. Andi

5 years, 5 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 8/4/25 00:21, Krinetzki, Stephan wrote: >> >> And for every one of those shunted messages there should be an exception with traceback logged in mailman.log. Those tracebacks should be helpful. > > If there were any. Maybe the "debug" level should be "info". But for which logs? The standard logging levels from lowest to highest are debug info warning error critical Whatever level is set for a log results in all messages of that level or higher being logged. I.e. if the log's level is debug, all messages for that log of any level should be logged. For every shunted message, a message like `SHUNTING: <file name without the .pck extention>` preceded by the exception and traceback is logged to error.log with level error. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/runner.py… > Maybe the restart at night after the lograte maybe the issue. As I said before, blindly restarting Mailman is a bad idea. On servers that I maintain, I always verify that all queues are empty before stopping or restarting Mailman. If necessary, I'll kill the incoming runner and wait for the out queue to empty and then stop mailman. If you want to do this daily, you could automate that., e.g. ``` if queues empty: restart Mailman else: when in queue is empty, sigterm incoming runner when out queue is empty, stop Mailman when Mailman stopped, start Mailman ``` The stop/start is needed because a simple restart at that point won't start the sigtermed incoming runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

[MM3-users] Customizing Postorios web templates

by Stephen J. Turnbull

Stefan Bethke writes: > I have two list servers that I would like customize the web pages > for, specifically I need to add some legal information to the > footer, and I might want to apply some light branding to the > site. I can't find any hints on how to do that, maybe I'm looking > in the wrong place? Postorius is a Django application. There are copious docs on djangoproject.com. We really don't want to duplicate the upstream project's documentation, especially since our downstream (ie, OS distros) are likely to have various different versions of Django installed in their packages. The basic procedure is to add a local template path (I use /etc/mailman3/templates) early in Django's template path in /etc/mailman3/settings.py. Then copy any templates you want to modify to the right place in that local template hierarchy and modify them there. > If Postorious does not currently allow that outright, It does, there's no need to vendor Postorius. > If so, would there be interest in adding a feature to define some > blocks that can be overridden more easily, Don't think this approach is better than overriding base.html if you want sitewide legal and branding. It would be more appealing if it were list-specific. It might be slightly more convenient, but you still need to create the local template hierarchy. On the other hand, it would increase the documentation burden. And for obvious reasons we don't want to make it too easy to replace our own branding. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months, 1 week

[MM3-users] Re: 12/24 hour clock ?

by Per Jessen

Mark Sapiro wrote: > On 11/28/20 7:18 AM, Per Jessen wrote: >> Hi all >> >> at openSUSE we have recently migrated to mailman3, and we seem to be >> having a couple of teething issues: >> >> a) hyperkitty and postorius both seem to insist on using a 12 hour >> clock format, no matter what the user has set. Is there a way of >> changing it system-wide ? > > > This is a Django setting. Try > > TIME_FORMAT = 'H' > > in settings_local.py. See > https://docs.djangoproject.com/en/3.1/ref/settings/#time-format and >https://docs.djangoproject.com/en/3.1/ref/templates/builtins/#std:templatef… Thanks, will have a look. >> b) overriding the default set of footers - despite having set the >> template "list:member:regular:footer" to empty for a specific list, I >> am still getting the default footers attached. > > > How did you set the template to empty? I edited it in list settings under Templates, at first really just leaving it empty, then actually writing "empty" :-) > it works for me in Postorius from the HEAD of the gitlab branch and > should work with any Postorius >= 1.3.0 > > Note that when you set a template in Postorius, it sets the URI in > Mailman core for that template to > https://<HOST>/<PATH>/api/templates/list/<LIST-ID>/<TEMPLATE-NAME> > where the https://<HOST>/<PATH> part is the Django setting for > POSTORIUS_TEMPLATE_BASE_URL. Is that URI accessible from the Mailman > core host machine? I'll have to check, I only do the list admin, I don't maintain the installation. -- Per Jessen, Zürich (2.2°C) Member, openSUSE Heroes

5 years, 8 months

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

by Mark Sapiro

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

4 years, 6 months

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

by Mark Sapiro

On 4/7/25 02:30, MegaBrutal via Mailman-users wrote: > On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > >> so it is saying there is only one choice for sender which I think means >> there is only one address associated with your login. That still doesn't >> explain why it thinks you're not a list member. >> > > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries > you recommend to run to get to see what's happening under the hood? Not offhand. What is the exact email address that you are logging on to the web UI with. Does it match exactly with the address of a list member or are there mixed-case differences? You might try an interaction like this: ``` mailman-web shell Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_mailman3.lib.mailman import get_mailman_client >>> client = get_mailman_client() >>> list_id = 'test.example.com' # your actual list_id >>> rest_list = client.get_list(list_id) >>> email = 'user(a)example.com' # your actual email >>> member = rest_list.get_member(email) >>> member This should print something like <Member 'user(a)example.com' on 'test.example.com' with role 'member'> ``` This is exactly what HyperKitty is doing except in your case rest_list.get_member(email) is throwing a ValueError exception instead of returning the member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

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

by Mark Sapiro

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

5 years, 8 months

[MM3-users] Re: Mailman 3 localization

by Simon Hanna

> We would like to contribute further german translations, since there > are still some parts missing, e.g. in the postorious interface. Would > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > be the right place to do so, so that everybody could use our > translations? > > If there are other areas in which you could use our help, please let > us know. > > Regards, > Alex I wanted to set it up, but the requirement is to use a free hosted solution. (So transifex and crowdin are a no-go, they would be great to get translations, especially crowdin looks very active in that regard) I tried out zanata.org but it's extremely slow... The other option at the time was pootle (http://pootle.translatehouse.org) which doesn't offer hosting but some folks at gnu had a customized instance set up, but they discontinued the service. I searched for a translation service for a private project and found weblate.org . They offer hosting (hosted.weblate.org) for open source projects and it looks like a couple of people are using it. You need to contact them if you want to set it up for an open-source project though and I didn't want to invest in it without knowing what the end-result would be... Since I'm also mainly interested in German translations for my own installation, I opted to just use plain .po files and filed merge requests against the repositories. Postorius has translations (not perfect, but a start for the moderators that use my instance) included by now but my merge request for core is still outstanding https://gitlab.com/mailman/mailman/merge_requests/400/ Since I don't use Hyperkitty, I didn't translate that. cheers, Simon

8 years, 1 month

[MM3-users] New problem on new installation of Mailman

by Brian Carpenter

I am just about done with installing Mailman 3 on a new Debian 10 server and when I go to run ./mailman-post-update, I am running into the following error: ./mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 10, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 377, in execute django.setup() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/registry.py", line 91, in populate app_config = AppConfig.create(entry) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/config.py", line 90, in create module = import_module(entry) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/__init__.py", line 11, in <module> from haystack.utils import loading File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/utils/__init__.py", line 9, in <module> from django.utils import six ImportError: cannot import name 'six' from 'django.utils' (/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/__init__.py) I assume it has something to do with Haystack. Suggestions for a fix? Thanks, Brian

6 years, 1 month

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

Hi. I have fixed my RO database issue. Thank You for help, Abhilash. It was 100% my stupid fault. I had issues with "django-admin". If I ran manage.py it works correct, if I run django-admin - it not: only basic commands. I did not find way how to give correct environment. Then I found on some notes, that manage.py does exactly the same what django-admin does. So I made work around : I had created /usr/local/bin/django-admin to my project file manage.py and it started to work. Later I installed mailman from 0 under another user, and I forgot about that sym link. So why because database was Read Only. It had simply leaking write privileges to database file. Understandable, because owner was another user... > On 6 Sep 2019, at 00:20, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:49 PM, Ugnius wrote: >> >> Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. >> Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple >> writable. > > I think your problem about locked database might be solved. Like I mentioned, it is possible that those two running server could be stepping over each other toes. > > After removing the "runserver" process, I think you shouldn't fall into anymore of those locking issues. > > FWIW, it is also highly recommended to not use sqlite for any production use cases. Either postgres or mysql is preferred. > >> SQLite version 3.16.2 2017-01-06 16:32:41 >> Enter ".help" for usage hints. >> >> BR >> Ugnius >> >>> On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >>>> >>>> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? >>> >>> No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. >>> >>> The doc mentions that it is "development" server[1][2]. >>> >>> [1]: # Run the Django's "development" server at localhost:8000 >>> [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project >>> >>> Perhaps it should be more descriptive about what does it mean. >>> >>>> >>>>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> >>>>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>>>> >>>>> You only need one of those, since they both do the exact same thing. Please remove >>>>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>>>> >>>>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>>>> May mailman processes are next: >>>>>> >>>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>>>> >>>>>> Looks like there are no double. Nothing more is running. >>>>>> >>>>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> >>>>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>>>> >>>>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>>>> $ sudo pip3 install mailman >>>>>>> $ sudo pip3 install postorius >>>>>>> $ sudo pip3 install hyperkitty >>>>>>> $ sudo pip3 install mailman-hyperkitty >>>>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>>>> >>>>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>>> >>>>>>> >>>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>>> > Hi. All the project installation is under the same user / path and >>>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>>> > I have found work around - it is possible to change list as private in >>>>>>> > "admin" page. >>>>>>> > I started to get issues with runjobs after I have created couple of >>>>>>> > new lists with "no archive" option. >>>>>>> >>>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>>> >>>>>>> > >>>>>>> > If as owner user from project home I run: >>>>>>> > >>>>>>> > django-admin mailman_sync >>>>>>> > >>>>>>> > Traceback (most recent call last): >>>>>>> > File >>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>>> > line 84, in _execute >>>>>>> > return self.cursor.execute(sql, params) >>>>>>> > File >>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>>> > line 383, in execute >>>>>>> > return Database.Cursor.execute(self, query, params) >>>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>>> > >>>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>>> > END TRACEBACK >>>>>>> > >>>>>>> > I did not find information how to fix this. It was worked without errors >>>>>>> > before. >>>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>>> > to work. >>>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>>> > again. >>>>>>> > I did not check other jobs, but I think what is related to database, >>>>>>> > will get errors. >>>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>>> > >>>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>>> > I have returned this database file back, postorius started to work >>>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>>> > only". >>>>>>> > Please help me how to fix this issue. >>>>>>> > _______________________________________________ >>>>>>> > Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>>>> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>>>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>>>> > >>>>>>> >>>>>>> -- >>>>>>> thanks, >>>>>>> Abhilash Raj (maxking) >>>>>> >>>>>> -- >>>>>> thanks, >>>>>> Abhilash Raj (maxking) >>>>>> >>>>>> >>>>> >>>>> -- >>>>> thanks, >>>>> Abhilash Raj (maxking) >>>>> >>>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years, 10 months

[MM3-users] Fwd: Incoming command emails (i.e. listname-leave) routed to list itself

by Abhilash Raj

Hi Mark, Excerpts from Mark Lindsay's message of April 20, 2017 5:37 pm: <snip> Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.o > rg > >> `? >> > > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through > it. > > Yes, I had the exact same problem very recently and was able to fix it. The updated documentation[1] should fix your problem. The basic gist of the problem is that the exim configuration on the older documentation is missing a critical part. Exim4 by default strips off any prefixes/suffixes when delivering mail to the mailman, which causes mailman to post all the messages to mailing list instead of processing them as commands. `rcpt_include_affixes = true` Adding the above line to the transport fixes that problem. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mt a.html#exim4-configuration thanks, Abhilash

9 years, 3 months

[MM3-users] Re: Why is it so difficult to setup Mailman3?

by Peter Chubb

>>>>> "Thomas" == Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> writes: Thomas> On 2026-04-08 10:28, alain williams wrote: >> On Wed, Apr 08, 2026 at 11:07:42PM +0900, Stephen J. Turnbull >> wrote: >> >>> To the best of my knowledge, the recommended installation >>> documents at >>> https://docs.mailman3.org/en/latest/install/virtualenv.html are >>> complete and straightforward for "typical" one-domain >>> installations. >> No they are not. I struggled, part of the reason is that I am not >> imbued in the python mindset and the documentation is written >> assuming that background. So I used the Debian package and a lot >> of work was needed on top of that. There are still problems: it is >> a resource hog and parts crash - generating large numbers of >> incomprehensible emails (I have talked about here, no real help). Thomas> The Debian package is inherently old and inefficient I'm using it with Nginx, Postgresql and exim4; on sid it's at Mailman3 3.3.10 with postorious 1.3.13; it has been stable for me since the upgrade before last (before that, there was a memory leak somewhere). I did find configuring it initially a pain; the way Django works was (still is) a mystery to me; plus a couple of the upgrades have been rocky and broken things (which I expect when working with the unstable distribution) The README in /usr/share/doc/mailman3/README.Debian was enough to get me going. And sudo -u list /usr/bin/mailman <args> gets you the CLI so you can do the things in the official docs. Peter C

3 months, 3 weeks

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: > > I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. The doc mentions that it is "development" server[1][2]. [1]: # Run the Django's "development" server at localhost:8000 [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project Perhaps it should be more descriptive about what does it mean. > > On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> >> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >> >> You only need one of those, since they both do the exact same thing. Please remove >> whatever is running the "python manage.py runserver" part and only use uwsgi. >> >> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>> May mailman processes are next: >>> >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>> >>> Looks like there are no double. Nothing more is running. >>> >>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> __ >>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> >>>>>> >>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>> > Hi. All the project installation is under the same user / path and >>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>> > I have found work around - it is possible to change list as private in >>>>>> > "admin" page. >>>>>> > I started to get issues with runjobs after I have created couple of >>>>>> > new lists with "no archive" option. >>>>>> >>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>> >>>>>> > >>>>>> > If as owner user from project home I run: >>>>>> > >>>>>> > django-admin mailman_sync >>>>>> > >>>>>> > Traceback (most recent call last): >>>>>> > File >>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>> > line 84, in _execute >>>>>> > return self.cursor.execute(sql, params) >>>>>> > File >>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>> > line 383, in execute >>>>>> > return Database.Cursor.execute(self, query, params) >>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>> > >>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>> > END TRACEBACK >>>>>> > >>>>>> > I did not find information how to fix this. It was worked without errors >>>>>> > before. >>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>> > to work. >>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>> > again. >>>>>> > I did not check other jobs, but I think what is related to database, >>>>>> > will get errors. >>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>> > >>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>> > I have returned this database file back, postorius started to work >>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>> > only". >>>>>> > Please help me how to fix this issue. >>>>>> > _______________________________________________ >>>>>> > Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>>> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>>> > >>>>>> >>>>>> -- >>>>>> thanks, >>>>>> Abhilash Raj (maxking) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Mark Sapiro

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

5 years, 9 months

[MM3-users] Re: Upgrading packages

by Mark Sapiro

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

3 years, 9 months

[MM3-users] Time Stand Still

by Barry Warsaw

Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation. I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps. I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken. Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org. It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals. My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced. And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader. If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient. This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate. Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention. -Barry https://www.wefearchange.org/

8 years, 8 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace From: with list address and DMARC Mitigate unconditionally to > Yes. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 6 months

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

by Mark Sapiro

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

2 years, 7 months

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

by Roland Giesler

On 2024/07/28 15:42, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>>> >>>> The server runs power-mailinabox, which uses Postfix indeed. All my >>>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>>> on port 465. Actually, this message is sent via that server too. >>>> So it's clear to me that MM3 is not authenticating for some reason. >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log The /etc/mailman3/mailman3-web.py file contains inter alia these lines: # Set default domain for email addresses. EMAILNAME = 'fast.za.net' # If you enable internal authentication, this is the address that the 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/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) # 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@{}'.format(EMAILNAME) fast.za.net was giesler.za.net before, so I changed it.

2 years

[MM3-users] Mailman 3 install questions: HAYSTACK_CONNECTIONS

by heller＠deepsoft.com

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

2 years

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Stephen J. Turnbull

Sebastian Hagedorn writes: > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with Alembic, > as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? No. What is being discussed in the thread is changing the backend RDBMS, behind the SQL schema. Alembic operates in front of the SQL schema, managing the relationship between Python objects and the SQL schema. As the "Migration" section states, Alembic is used to handle changes in the model (ie, the Python objects), so that they are reflected in the SQL used to access the backend. Users don't need to use it unless they customize the Python objects (ie, patch Mailman themselves). If *we* change the model between versions, Alembic will automatically be invoked to update the SQL, but the user doesn't need to do anything about it. The potential issues Mark refers to involve differences in the way the different backend implementations handle SQL (this includes issues like default encodings for strings). These should be few because all the supported backends support standard SQL, but we can't guarantee there will be none. Differences in implementation also mean that you can't use the more efficient and compact dump formats that most implementations provide, because they are implementation- dependent. You need to use the textual format that is actually SQL programs that individually create each table, insert each record, create any needed indices, and so on.

8 years

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

by Mark Sapiro

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

6 years, 2 months

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

by Mark Sapiro

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

5 years, 8 months

[MM3-users] Re: what process creates webui tables (mailmanweb db)?

by Mark Sapiro

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

3 years, 10 months

[MM3-users] Out there plugin idea for tech cost sponsorship

by Steven Clift EDem

After spending 20 years running a non-profit that hosted email lists for local communities as my day job, that's now all volunteer as I run a startup. Figuring out how to raise money to cover server costs without selling out our members with targeted social media advertising, was a continuous challenge. Anyway, today I am still involved in efforts to route around digital ad behemoths, but I a trying to help small businesses and shop for good brands gain new customers. So here is the question - do you think a Mailman add-on/plugin/module/whatever you'd call it that allowed list admins to reward their new subscribers to email lists with custom themed "for good" discounts would be of interest to many??? Normally, we (GoodCarts) reward people post-checkout with discounts in reciprocity powered circles of online stores. Stores essentially grow together by sharing customers instead of bidding against each other. The way I could see working with email list providers is basically adding an affiliate marketing style commission where purchases with post-subscription rewards would go to the partner based on results. When we go from hundreds of brand members to thousands and add in a "buy local" or brands by theme/values/impact, in theory my non-profits local online community forums could mission align by offering discounts to locally owned businesses. Our view is that exclusive discounts as rewards post transaction (purchase, email list subscription, volunteer sign-up, event registration, online petition signature, etc.) is far better than plastering ads everywhere. Anyway, I'd be curious if you think idea might have legs with Mailman list hosts/admins??? Nothing urgent, just a Saturday morning think different idea. Steven Clift

3 years, 6 months

[MM3-users] Re: Held messages not delivered after approval

by Stephen J. Turnbull

Krinetzki, Stephan writes: > Now in the mailman.log I see the HOLD messages and the approved > messages. The smtp.log logs just the incoming Mail, which seems to > be fine. By that you mean the incoming mail is fine? Or smtp.log is fine? smtp.log should include two (or more) lines for each successful post, like Jan 02 16:09:17 2025 (42985) <43007@turnbull> smtp to list-1(a)turnbull.jp for 1 recips, completed in 0.6027507781982422 seconds Jan 02 16:09:17 2025 (42985) <43007@turnbull> post to list-1(a)turnbull.jp from list-1-owner(a)turnbull.jp, 992 bytes, 1 failures Jan 02 16:09:17 2025 (42985) <43007@turnbull> delivery to list-1-owner(a)turnbull.jp failed with code 550, b'5.1.1 <list-1-owner(a)turnbull.jp>: Recipient address rejected: User unknown in local recipient table' (That last line shows an example of a failure report.) > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 Postfix for some reason doesn't know about the alias "localhost" (it has something to do with trusting the DNS and not reading the /etc/hosts file). 127.0.0.1 works. I don't understand how any lists' posts get delivered at all with that. If it's postfix it's possible that the connection pool is exhausted intermittently (but that wouldn't explain why it's consistently impossible to post to a subset of lists). You can specify that connections from the loopback interfaces are less restricted. That might help. > Even after changing the smtp_host in mailman.cfg this error appears > randomly. Note that > Sadly the mail does not get delivered. :-( -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

11 months, 4 weeks

[MM3-users] Re: Reg Archive Inactive Status

by Nirmal J

Yes I have it. I am also sharing that also settings_local.py -----Original Message----- From: Stephen <steve(a)turnbull.jp> To: Nirmal <nirmal(a)iitm.ac.in> Cc: mailman-users <mailman-users(a)mailman3.org> Date: Friday, 26 September 2025 3:09 PM IST Subject: [MM3-users] Re: Reg Archive Inactive Status Nirmal J via Mailman-users writes: > Hereby I am sharing the full settings.py file. Are you sure this is the settings.py being used by your installation? It appears to be the distribution file, unchanged. > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')# Application definition If this is from the installed settings.py, it isn't going to work, since you specified a routable domain (I think, although "list1.iitm.ac.in" is not in the public DNS), which will have a routable address, not localhost. What IP does your DNS report for "list1.iitm.ac.in"? > HOSTNAME = 'localhost.local' That isn't what you told Mailman via hyperkitty.cfg. I'm not sure it matters, but I think you should make sure all the config files agree on the name of the host. > # 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@{}'.format(HOSTNAME) This can be problematic, at least if you enable error messages by email. > try: > from settings_local import * > except ImportError: > pass Do you have a "settings_local.py" file? -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

10 months, 1 week

[MM3-users] Re: Creating users via RestAPI / User-Management - a bunch of questions

by Mark Sapiro

On 6/20/25 06:39, Christian Schneider wrote: > Dear Mark and companions, > > somehow I can not cope with the user management... > (I am running a venv-installation, latest stable versions) > > I read this manual: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > and played with the RestAPI calls... > > I know about the fine grained differences between user and member, admin/owner, superuser... > and about the two user databases in PostgreSQL and Django-Framework. I'm not sure what distinction you are making between PostgreSQL and Django-Framework. There are two separate and distinct users, Django users and Mailman core users. Information about both is in the PostgreSQL database. Django users are in the `auth_user` table and Mailman core users are in the `user` table, both in the public schema, although if you split the data into a `mailman` database and a `mailmanweb` database the `auth_user` table is in `mailmanweb` and the `user` table is in `mailman`. > What I stumble upon is the RestAPI calls to create a "working" user (with the ability to login via WebUI). > When I follow the manual (from the url above) I create a user (including password) that appears in the PostgreSQL database. > (And this user is visible on the User-URL (https://example.com/mailman3/users)) > Even when I (via WebUI) set the user as "approved" this user is not able to log in... > I assume this restriction is in accordance to the fact that there is not equivalent Django user. > (There was a mail in the archive of the MM3 user group...stating that one has to use the Django RestAPI to create the appropriate user) The above is correct. The Mailman REST API only deals with Mailman core. Mailman core knows nothing about Django. > When I create the user using the WebUI (https://example.com/accounts/signup/?next=/mailman3/lists/) > the new user is created in the right (complete) way...appearing in the PostgreSQL database and as a user in Django. > How is this sync between the two databases realized? I'm still looking into that, but it isn't the creation of the Django user per se that creates the Mailman user. The process has multiple steps. 1) Sign-up for an account. This creates the Django user and sends an address confirmation email. 2) Click the link in the confirmation email. This takes you to a page with a `Confirm` button to confirm the email address. 3) Click the confirm button. It is not until step 3) that the Mailman user and address records are created. > (The Django user also has the correct status (no staff status / no superuser status / just active status) how is this realized?) Presumably by the sign-up process not setting staff status and superuser status. > As I am not very familiar with python programming (I know Perl/Java/C++ and have an (maybe outdated) concept of OOP), > is there a quick way to implement this kind of sync by copying the register logic from mailman's python action script for registering? I think it must be django-mailman3 that's doing this, but I haven't been able to see how so far. django-mailman3 does override the template for the /accounts/confirm-email page, but this is only to include styling. > Other questions: > Will there be a create_admin_user-script that is callable via CLI (like createsuperuser or create_list)? > (This script ought create a user in PostgreSQL and as Django user) No plans. There are `mailman addmembers` and `mailman admins` commands to add members or admins to a list. Adding an owner or moderator to a list via `mailman admins` will also create a Mailman user for that person if there isn't one already, but it won't create a Django user. > How will a social account provider (like oidc) linkage (in Django) fit in this concept? > Will oidc-accounts be copied to the Django's user database (or PostgreSQL db) or is it an on-the-fly check against the oidc-provider? (I assume second option) > What are the status-flags (staff status/superuser status/active status) of the linked oidc-accounts? (Can I specify the status flags?) I don't offhand know the answers to that, but I think logging in via a social account provider creates a Django user.. > A conceptual thought: > When "user1" (with email user1(a)example.com) is known to django via oidc linkage > and I create "user1" (also with email user1(a)example.com) via RestAPI calls > (following the url https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > do I have a "complete" user then? > I mean a user who is able to login and who can be assigned to a list as admin (e.g.) > (In this case I would not have to care about the Django user database... ;-)) If the user can log in to the web UI with an associated email address, if that address is an admin of a list, the logged in user can admin 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, 1 month

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

by Christian Stalberg

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? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. > Is there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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, 8 months

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

by Simon Coggins

On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: I wound up taking a different approach. I check for other references to the message in the message store and only delete the message if there are none. The fix is at https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs> Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 8 months

[MM3-users] Re: Healthchecks and Django

by Philip Colmer

On Tue, 4 Jan 2022 at 09:36, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > Philip Colmer writes: > > > For the MM3 servers, we're probing "/mailman3/lists/". > > You could create a path in urls.py called "250" that does nothing but > respond with a 250 status (and maybe a hello-world page). The issue > with /mailman3/lists/ is that it queries core for the lists (which, if > successful, proves that core is up as a side effect). > > > Is there another URL we could use to check the health of a MM3 server > > What does this mean to you? Our Mailman 3 suite consists of three > applications, core, Postorius, and HyperKitty, which might or might > not be installed, and if installed might or might not be running on > the same host. Core in turn depends on the MTA and starts a bunch of > qrunners. Any of the above might fall over on its own. (I don't > think there's any way to check on the health of a particular qrunner > from the net, though.) > That's a very good point. It would be nice if, at some point, an actual healthcheck endpoint could be included that returned some information about the state of the different applications as a JSON blob. It is increasingly useful to try and spot application problems before users do :) > > > Or, if not, is there a way of stopping Django from sending out the > > emails? > > There probably is, but I don't know it. Mark might, but if not asking > on a Django list would be a better place. > > Thank you. Regards Philip

4 years, 6 months

[MM3-users] Re: Dealing with recipients' servers spam filtering

by Gilles Filippini

Brian Carpenter a écrit le 12/02/2021 à 17:33 : > On 2/12/21 10:59 AM, Gilles Filippini wrote: >> It says: host mx1.free.fr[212.27.48.7] said: 550 spam detected >> (in reply to end of DATA command) I don't have any SPF record setup. >> DMARC mitigation is configured to 'Replace From: with list address' >> and 'DMARC mitigate unconditionally' set to 'No'. > > Well make sure you set up SPF records for your list domains. They do > help in mail delivery. I personally set DMARC mitigate unconditionally > to yes for my lists. Unfortunately the 550 spam detected message is too > generalized to be helpful. If you have more informative information from > your logs then please share them. Writing down what I've learned so far, in case it may help others: 1- The lists server DNS record (lists.example.com) should be of 'A' type (no 'ALIAS' or 'CNAME') 2- The SPF record should be set for the very same DNS name; e.g. lists.example.com (not just example.com) 3- This record seems to work for my server: lists.example.com. IN TXT "v=spf1 ip4:123.123.123.123 -all" Where the IP address is the same as the one registered for the 'A' record. How to check the SPF record: 1- Create a dummy mailing list and register your email address and check-auth(a)verifier.port25.com. 2- Send an email to this list. You should receive a report from auth-results(a)verifier.port25.com Here is what I've received for my server: ========================================================== Summary of Results ========================================================== SPF check: pass "iprev" check: pass DKIM check: none Let's see it this is enough to mitigate the problem with Hotmail addresses. Best, _g.

5 years, 5 months

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

by Abhilash Raj

> On Nov 2, 2021, at 12:51 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/2/21 11:50 AM, bob B wrote: >> So I am teaching myself to fish, and see that it is actually django-admin, so that is in >> mailman-web? (in docker) >> But i get this: >> $ docker exec -it mailman-web /bin/bash >> bash-5.0# django-admin shell >> Python 3.8.10 (default, May 6 2021, 06:30:44) >> [GCC 9.3.0] on linux >> Type "help", "copyright", "credits" or "license" for more information. >> (InteractiveConsole) >>>>> from hyperkitty.models import MailingList >> Traceback (most recent call last): > ... >> raise ImproperlyConfigured( >> django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. > > > Do what it says. I.e. run > > DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell DJANGO_SETTINGS_MODULE expects a Python import path, instead of a filesystem path. The docker has documentation on running management commands, which in this case is “shell” [1] $ docker exec -it mailman-web python3 manage.py shell [1]: https://asynchronous.in/docker-mailman/web/#django-management-commands I know there are plethora of ways to run Django management commands, but this is the easiest one for docker. django-admin will work too, but you have to be in the right working directory for the import path to work and it get weird. I’ve always disliked how Django management commands work unfortunately and in trying to “fix” that with “mailman-web” (which isn’t adopted by container images), i feel I might have re-invented a third option. -- thanks, Abhilash Raj (maxking)

4 years, 9 months

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

by Mark Sapiro

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

6 years

[MM3-users] Re: changing adverstised status

by Mark Stuart

I can confirm the issue is happening to me as well postorius 1.2.1 / Django 2.0.7. If you're logged in and go to the list setting page, check the radio button for 'Show list on index page' to 'No' and click save at the bottom, it reverts back to 'Yes'. Then it still shows up on the index page. I haven't tried the mmclient method to see if that works. -- Mark (stuieordie) On Wed, Aug 22, 2018 at 1:30 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Aug 22, 2018, at 1:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change "show > > list on index page" via the settings, but the value isn't saved. Is > > there a way to set advertised = False to a specific list via the shell? > > Could be related to > https://gitlab.com/mailman/postorius/merge_requests/352 > > The behavior of some of our boolean fields changed with newer releases of > Django, but it has been fixed in master branch. > > > > > Thanks & Regards, > > Alex > > > > (Kulturserver editorial staff) > > _______________________________________________ > > 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) > _______________________________________________ > 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/ >

7 years, 11 months

[MM3-users] Re: Weekend releases

by Abhilash Raj

On Tue, Dec 10, 2019, at 8:27 AM, Mark Sapiro wrote: > On 12/10/19 2:58 AM, Paul Arenson wrote: > > Thank you. The setup I am using now has Hyperkitty 1.3.0 and I just wanted to confirm. Somewhere I thought I read there is a facility in the Hyperkitty archive interface to format text. Probably I misunderstood, but if there is such a facility, I am not seeing it. Maybe I am looking for something like Tiny Ice and thus can't find it. > > > Markdown rendering of message bodies in Hyperkitty is > <https://gitlab.com/mailman/hyperkitty/merge_requests/160>. This is > installed on <https://lists.mailman3.org/mailman3/> and > <https://mail.python.org/mailman3> but is not yet released. > To add more, if you look at the merge request, there are some pieces missing before it can be merged. Especially, a mechanism to opt-out on a per-list basis from this. While markdown is pretty nice to look at when you are dealing with certain mailing lists which communicates in plain text, it can be horrible to look at if the users aren't aware about markdown and/or the special markdown syntax. In practice, there is only so much we can do to render a random email as HTML using markdown syntax. Maybe I can get to it this holiday season and it can go out for interested folks in the next Hyperkitty release :) > -- > 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, 7 months

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

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

3 years, 11 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 03:25:41 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > On 13/3/21 8:53, John Covici wrote: > >> We recommend installing Mailman and the web components in a virtualenv, > >> but it is not a requirement. We also suggest that postgresql is a better > >> choice than MariaDB. > >> > > I sort of am installing from source, gentoo installs from source. No > > one on the gentoo users mailing list seems to be able to help me, > > except to tell me to use a different mailing list mechanism called > > mlmmj. > > > From the perspective of someone who was in the same place (but > installing in a FreeBSD S.O.), I would recommend you to follow > the "virtualenv" guide but without executing the "env" > commands. It will produce a system wide mailman3 installation but > it will work (as it is for me since a few moths ago) > > I writed down a step by step path of my installation and it could > be of your interest (maybe you have to locate and install some > packages by different name, but I think it will be not much > difference). It could provide you a overall view of all the > processes implied. > > I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 Thanks, by the env commands you mean the creation and activation commands? I will certainly look at your thread. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 4 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Mark Sapiro

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

5 years, 4 months

[MM3-users] Trouble Installing Mailman3

by Henry Hartley

I'm having problems installing mailman3 following the instructions on https://docs.mailman3.org/en/latest/install/virtualenv.html Everything goes well until I get to the Installing Mailman Core<https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> step, which has me do the following in my venv environment: (venv)$ pip install wheel mailman psycopg2-binary Ubuntu 24.04.02 LTS Python 3.12.3 pip version 24.0 First, I was getting problems because my company firewall was blocking outbound traffic. I got that taken care of. Next, I was seeing certificate errors, saying there was a self-signed certificate: WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))': /simple/wheel/ Could not fetch URL https://pypi.org/simple/wheel/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/wheel/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))) - skipping When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) ERROR: No matching distribution found for wheel The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I've rerun the apt install of python3-dev and python3-venv to make sure those are present and up to date. Any help you can provide will be greatly appreciated. -- Henry Hartley Westat

1 year, 2 months

[MM3-users] Re: Lookup Table Questions

by Mark Sapiro

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

4 years, 7 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

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

10 years, 2 months

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

by Mark Sapiro

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

7 years, 4 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Thu, Oct 26, 2017, at 06:39 PM, Mark Sapiro wrote: > On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > > > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. > > > This usually means that postfic is trying to deliver to an address and > the message already has a Delivered-To: header with that address. > > What are the headers of the "looping" message in the report? What are > the Postfix log messages related to that message? > > > > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > > > https://github.com/maxking/docker-mailman > > > I have essentially no knowledge of the docker container images, so I > can't be much help with issues specific to them. The Postfix integration in container images is basically just using regex instead of hash maps and everything else is same. I do remember atleast one other person facing a similar issue where Postfix wouldn't accept listname+token@domain addresses with our regex. I am thinking this is the same issue. > > -- > 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/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 9 months

[MM3-users] User management page [was: Changing subscription address]

by Stephen J. Turnbull

Core implementation details, so I beinging this here from Mailman Users @ mailman3.org. Abhilash Raj writes: > I have started working on designing a User management page[2] in > Core which should make it easy for superuser to manage several > things about a User, including the ones that don’t have an account > in Postorius to manage their own. I don't understand this design with a "page in Core". I was thinking about this kind of problem, and tentatively came to the conclusion that any reference to something that can be resolved to a User should generate a Django account for that User in Postorius or HyperKitty. Authorization to use that account would still require authentication via the usual email verification dance, or some level of admin privilege. The thing is that emails that have not been added to a User are unique. They will be the only Address attached to User created to manage them until authenticated, and transitively the only address attached to an automatically-created Django account (since those are 1-1 with core Users if they exist AFAIK). What's missing here is the ability to merge core Users and their corresponding Django accounts. Doing this with nothing more than the usual email verification dance is not *obviously* provably secure to me, so we need to be careful, but I think it probably will turn out to be as secure as you can get. It seems to me that User merging is the most pressing problem of this kind. (At least, it affects me on a couple of list hosts, as well as on GitHub and GitLab.) > [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 I'll take a look tomorrow or early next week. Steve

5 years, 4 months

[MM3-users] Re: Deleting default "example.com" domain breaks everything

by Abhilash Raj

On Fri, Jul 16, 2021, at 12:12 PM, Mark Sapiro wrote: > On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > > Hello. I'm new with v3 of mailman. > > Installed via aptitude on deb10. > > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > > I then deleted example.com, and everything broke. > > The only site I had was still using example.com. > > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? > > > Try setting `SITE = 0` in your Django settings file. If that doesn't > work, try successively 1, 2, etc. One of these should work. Usually, example.com is always 1 and then it increases sequentially. So, if this is the first one you created, I'd try using 2. > > Also going back to your prior thread, you had > > > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser > > Aside from the python/python3 issue, you should run any Mailman and > Django management commands as the Mailman user (probably `list` in your > case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 > and https://gitlab.com/mailman/mailman/-/issues/776. > > > -- > 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)

5 years

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

by Jacob Sievert

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? with regards Jacob On 2022-01-28 15:57, Stephan Krinetzki wrote: > Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> > mailmancore/API ->database >> > that seems to have an issue and only with this one >> > DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX >> > query. However, like you, I have no idea as to what you could do further >> > to debug this. >> > I have an idea, but it seems so obvious that presumably it's already >> been tried: log in to the database as mailman with pgsql and try >> deleting something. If that works immediately, try with mailmanclient >> and the mailman command line utility. >> Steve > > Well, we didn't try this. Since we don't know what the query for > deleting a held message in the database needs to look like, we left > that out for now. If someone can help me there, it would be great. > > Over the mailman shell it hangs as long as on the web ui (using > mailman shell -l list@host and iterating over the held messages). So > it is the communication Mailman API <-> Database. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 6 months

[MM3-users] Re: Query on how to change moderator message to non-members

by Mark Sapiro

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

8 years

[MM3-users] Re: Modify approval email

by Odhiambo Washington

On Fri, Sep 15, 2023 at 5:33 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > pau.baiges(a)csuc.cat writes: > > > Is there a way to modify the email that is sent by default to list > > owners when a non-list member sends email to the list? > > Yes. As list owner (or site admin) in Postorius go to Templates, and > click on "New Template". Select list:admin:action:post from the > drop-down menu to the right of "Name". Copy the current message > (site-packages/mailman/templates/en/list:admin:action:post.txt is the > original, but do not edit this -- it will be overwritten on upgrades) > to the text box and edit to taste. Unfortunately there is no "web > site" variable but typically that is the same for all lists, so adding > > https://your.host.here/mailman3/lists/$list_id/held_messages > > in some appropriate place probably does what you want. > > There is no way to indicate that this is a link because these messages > are plain text. However, most mail clients will turn a URL into a > link. If your moderators are not so lucky, try wrapping it with > > <URL:https://your.host.here/mailman3/lists/$list_id/held_messages> > > or even the usual HTML: > > <a href="https://your.host.here/mailman3/lists/$list_id/held_messages"> > Moderation Page > </a> > > One of those may help. > Also, you can take a look at this documentation: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 10 months

[MM3-users] Re: Hyperkitty not receaving messages / empty archive [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/urls

by Mark Sapiro

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

1 year, 6 months

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

by Mark Sapiro

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

8 years, 10 months

[MM3-users] Re: Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4

by Jered Floyd

The weird client version was, of course, my fault... I had followed the instructions here in my settings.py: https://adamj.eu/tech/2020/02/04/how-to-use-pymysql-with-django/ This fix was incorporated into PyMySQL some time ago and is no longer necessary. The requirement for MariaDB remains real. --Jered ----- On Apr 3, 2024, at 7:36 PM, Jered Floyd jered(a)convivian.com wrote: > A heads-up for anyone else on RHEL 8, because the error is mystifying. > > django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django > 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for > MariaDB 10.3. > > For some reason I haven't yet been able to identify, this causes pyMySQL > integrations to fail with the mysterious error: > django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is > required; you have 1.4.6. > > (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while > Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is > coming from as it appears... nowhere.) > > Bypassing that error check gives the more informative: > django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found > 10.3.39). > > Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past > LTS, so I would recommend that Mailman systems be migrated to RHEL 9. > > --Jered > _______________________________________________ > 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

2 years, 4 months

[MM3-users] Re: Mailman3 upgrades

by Caballero, Danny (Dan)

Thank you! Yes, it was my fault. I have some customization in base.html. I'll need to track those changes across updates. Thank you! ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Tuesday, October 19, 2021 8:02 PM To: Caballero, Danny (Dan) <dancab(a)caltech.edu>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Mailman3 upgrades dancab(a)caltech.edu writes: > "Loading failed for the <script> with source > “https://mailman3.caltech.edu/static/hyperkitty/libs/jquery/jquery-1.10.1.min.js” > > Sure enough, I do not have that script. In fairly freshly updated sources, I have references to one or the other of > -rw-r--r-- 1 gunicorn root 117370 Oct 19 14:55 jquery-ui-1.10.3.custom.js > -rw-r--r-- 1 gunicorn root 58173 Oct 19 14:55 jquery-ui-1.10.3.custom.min.js in hyperkitty/hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bunudle.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js hyperkitty/hyperkitty/templates/hyperkitty/base.html The last file also refers to hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css My guess is all the files you listed are from a recent installation or upgrade, but somehow base.html didn't get upgraded. Based on the principle "always blame the user" ;-), I'd start by checking if our version is shadowed by your local version? Anyway, I bet the version number is wrong in base.html and if you fix that everything else will fall in line. If not, check if popper and boostrap are either older versions or perhaps shadowed by older versions somewhere. A word to the wise: grep(1)ing the .min.js.map files is not advised. They're huge and all one line it seems. Better to use an editor's search function.

4 years, 9 months

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

by gordon＠dickens.com

Hello everybody, I successfully resolved the owner:group issue and I am no longer getting the permission errors. Basically, I had to set the ownership:group to mailman:www-data and make the group permissions rw for everything to work successfully with Apache and Mailman3. As I mentioned earlier, I have mailman (core) now working, however, I cannot seem to get the web interface to work. I believe that I have gotten rid of all of the permissions issues and the mailman3-web service starts and stops without error. However, when I use a browser to go to the web interface, I get File Not Found errors in the browser window and my Apache2 logs say: 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: 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> By the way, this is the Apache configuration file that the Debian package installed with my initial installation. Does anybody see any problems in my Apache configuration file that could be causing my problems? Do you see or suspect any other issues? Thanks, Gordon

4 years, 5 months

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

by Mark Sapiro

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

3 years, 10 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

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

3 years, 2 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

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

3 years, 2 months

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

by Mark Sapiro

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

4 years, 2 months

[MM3-users] Re: pending subscriptions lost?

by Mark Sapiro

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

4 years, 4 months

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

by Mark Sapiro

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

1 year, 8 months

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

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

6 years, 3 months

[MM3-users] Re: HyperKitty and duplicate emails across maillists

by Stephen J. Turnbull

Derek Lambert writes: > For new messages does mailman generate unique message IDs for each > recipient? Mailman in principle doesn't generate message IDs at all. That's the job of originating clients or their MTAs. Mailman is what is called an "intermediary": it may do useful transformations on a message (such as adding RFC 2369 header fields and the List-Id field, as well as headers, footers, and subject decorations, removing banned media types, and even changing the format of text parts (such as removing HTML parts from multipart/alternative messages, or translating HTML to plain text by formatting with a browser such as Lynx), but in some sense the content of the message remains faithful to the author's intent. In such cases, the message is considered to be the same for the purposes of assigning Message-Id, so Mailman doesn't touch it. In the case that Mailman receives a message that has no Message-Id, it may be a good idea to generate one. (I don't think this is implemented. It has its problems as well as its benefits.) Otherwise, no, Mailman leaves the existing Message-Id alone. > E.x. if multiple lists (children) are members of another list > (parent), will the children lists all be able to archive the same > message sent by parent? Yes. I'm not sure whether the message body is stored multiple times or only once[1], but the primary key for archived message is effectively the list id plus the message-id. Steve Footnotes: [1] Probably multiple times, once for each list that has archiving turned on. Ensuring that any relevant decorations (headers, footers, Subject tags) are consistent would require pretty fragile analysis of the messages and complicated storage and indicies.

6 years, 10 months

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

by Paul Arenson

Hi The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. As well, links were weird. LINKS ===== Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). URL === So while I typed https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... It came out double as https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") The embedded one did not come out embedded buy showed the text like this: Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? (Even the web archive shows this problem though): https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See the top item Homeless man drowns in river during Typhoon and what I mean. IMAGE No image appears though one was added inline. And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). So are there guidelines one whether/how to attach an image so that it makes it? Thanks

6 years, 9 months

[MM3-users] Re: equivalent mailman 3 commands from 2.0

by Mark Sapiro

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

4 years, 9 months

[MM3-users] Re: Strange URL in error message

by waps＠tantalus.jena.thur.de

Hi Mark, thanks for your patience. But now I get a little spinning wheel on the archive site, 3 "Error 500" in the Browser console and /var/log/mailman3/web/mailman-web.log shows repeatedly the error: ERROR 2024-07-18 08:34:38,261 1760 django.request Internal Server Error: /mailman3/hyperkitty/list/latex-team(a)latex-project.org/posted-to Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 304, in overview_posted_to for thread in mlist.recent_threads: ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 162, in recent_threads return self.cached_values["recent_threads"]() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py", line 58, in __call__ return self.get_or_set(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 317, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 317, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. Since the archive is still quite empty and we have only one mailing lis, it would not be a big loss if it could resettet. But how I can do the, without resettinh the member data? Could it be that the Sqlite interface is not as stable as one the the "real databases"?

2 years

[MM3-users] Re: toward improving correctness when running on single core system ...

by Ruth Ivimey-Cook

One of the simpler ways of experimenting with mailman on a restricted system is using an SBC - something like a Raspberry Pi 2 or 3, or a Beaglebone, or similar. Both have limited memory and CPU, and are relatively slow systems. I would avoid a Pi 4 because it's too powerful in this context! Logging errors always changes the behaviour, but you can do much by noting things to internal variables and then after the event printing those (e.g. set a variable to count the number of times a try-lock operation found the lock held), and perhaps then doing the logging to a memory filesystem (Linux: tmpfs) which will have much lower latency. Normally a linux /tmp is using tmpfs. A multicore system will have different behaviour to a single core, but the kernel will almost always be preemptive (force timeslice). So one option might be to experiment with a fast-tick (e.g. 1000Hz or higher) kernel such that the timeslices are shorter. (It used to be the case Linux ran on 100Hz - I know most kernels are now "tick-less", meaning there is no persistent timer interrupt marking time, but there will be a unit of timeslice). A final option: if the problem is (as it appears to be) one of starvation, then perhaps the system is better run (on that hardware) with fewer worker processes. That is, cut the 13 workers down to e.g. 8. That said, starvation is something that can normally be designed out of systems though I know far to little about the architecture here to say if that is the case here. HTH, Ruth On 19/06/2023 18:51, Stephen Daniel wrote: > I'm currently running the entire mailman3 stack, including postgres and > postfix, plus my production web server, all on a GCP e2-small instance. > e2-small is two virtual CPUs running on a single physical core, restricted > to consuming at most 50% of the CPU cycles on that core. The system has 2 > GB of memory, 10GB of disk space. > > The entire stack runs well, albeit slowly, on this configuration, for which > I pay about $13/month. The entire stack is shut down every night so I can > take a snapshot while the applications are down. Once the snapshot is > complete, the stack is restarted. I have no startup issues in this > configuration. > > It is hard to imagine a more limited pool of resources, yet everything > works. > > On Mon, Jun 19, 2023 at 12:38 PM Nelson Strother < > justfixit(a)marilynstrother.com> wrote: > >> [My apologies for the mangled formatting of the diffs in [2] and [3] >> above. at least as shown on the web view of this list. Will happily >> repost or resend by direct email if anyone expresses interest.] >> >> > Presumably there's also a chance for the runner to detect and log the >> expired lock before it dies. >> >> This may require some cleverness, as the delays introduced by recording >> a log message e.g. "I'm the nntp runner holding the lock, and it has not >> expired yet." are likely to change the results of the lock competition, >> maybe even allowing all runner processes to continue as intended. It is >> unclear to me whether a process would ever have an opportunity to record >> a log message e.g. "I'm the nntp runner holding the lock which has >> expired, but I am not dead yet." before it dies. If such an opportunity >> exists, it should extend the lock's lifetime via e.g >> Lock.refresh(timedelta(seconds=10)). >> >> As I attempted to summarize at the end of [3] above, each time I tried >> shorter sleep intervals (1, 10, 15 seconds) within >> .../flufl/lock/_lockfile.py the original problem remains, namely one or >> more locks are broken and runner processes die. >> >> On 6/19/23 03:00, Stephen J. Turnbull wrote: >>> > The best "performance" I have yet obtained on this single core >>> > system is [by] [3] [which waits 20s before trying to obtain the >>> > lock]. >>> >>> Is 20s necessary? There are a lot of runners, you may be able to cut >>> the startup time by 2-3 minutes if you can cut that to 5s or less. >>> That would still be 100x longer than the naive #cores * seconds >>> estimate, but perhaps significant. >> _______________________________________________ >> 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 >> > _______________________________________________ > 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 ruth(a)ivimey.org -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 1 month

[MM3-users] All list messages shunted due to mailman core database lock

by Ryan Curtin

Hi there, I have been trying to debug a git commit development list for a project I maintain: http://lists.mlpack.org/mailman3/hyperkitty/list/mlpack-git@lists.mlpack.or… The list is run on mailman3 as provided by Debian. Messages are successfully received---you can see all the test messages in the archives I just linked to if you want to click on it. However, no messages are actually relayed to subscribers. I spent a while digging into logs and found that every message sent to the list results in an error like this in /var/log/mailman3/mailman.log: ``` Oct 02 17:01:26 2023 (2957556) Uncaught runner exception: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?] [parameters: ('2023-10-02 21:01:21.702224', 99565, 2)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Oct 02 17:01:26 2023 (2957556) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3/dist-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/acknowledge.py", line 46, in process member = mlist.members.get_member(sender) File "/usr/lib/python3/dist-packages/mailman/model/roster.py", line 120, in get_member memberships = self._get_all_memberships(email) 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/roster.py", line 116, in _get_all_memberships return members_a.union(members_u).all() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3373, in all return list(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3534, in __iter__ self.session._autoflush() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1633, in _autoflush util.raise_(e, with_traceback=sys.exc_info()[2]) File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1622, in _autoflush self.flush() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2540, in flush self._flush(objects) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2682, in _flush transaction.rollback(_capture_exception=True) File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ compat.raise_( File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2642, in _flush flush_context.execute() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/unitofwork.py", line 422, in execute rec.execute(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/unitofwork.py", line 586, in execute persistence.save_obj( File "/usr/lib/python3/dist-packages/sqlalchemy/orm/persistence.py", line 230, in save_obj _emit_update_statements( File "/usr/lib/python3/dist-packages/sqlalchemy/orm/persistence.py", line 994, in _emit_update_statements c = cached_connections[connection].execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1011, in execute return meth(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement ret = self._execute_context( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context self._handle_dbapi_exception( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception util.raise_( File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.OperationalError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?] [parameters: ('2023-10-02 21:01:21.702224', 99565, 2)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Oct 02 17:01:26 2023 (2957556) SHUNTING: 1696280486.719109+114cb2cc738a61874a5eed7e3f66a3ac111f5b90 ``` I have tried a handful of things: * Restart mailman3 and mailman3-web systemd services. * Ensure that there are no stale locks in /var/lib/mailman3/locks/ when mailman3 core is stopped. * Move the database in /var/lib/mailman3/data/mailman.db out of the way and replace it with a copy, in case some process is holding it open. * Unshunt all the messages with `sudo /usr/bin/mailman3 unshunt` (didn't realize this would drop all the shunted messages, but not a big deal). Most threads I have read appear to be related to the Django interface encountering a locked database, but this looks different---it seems mailman core is having the problem, not anything having to do with mailman3-web or Django. Does anyone have any thoughts on things I can do to fix this error? I am not a mailman3 expert (and to be perfectly honest I don't want to be one, I just want to post things to the list :)). One extra caveat: rebooting the machine I am using is not a realistic option. Thanks in advance for any help. Ryan -- Ryan Curtin | "Not like this... not like this." ryan(a)ratml.org | - Switch

2 years, 10 months

[MM3-users] Re: Auth question

by Mark Sapiro

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

9 years, 4 months

[MM3-users] Re: Invalid confirm text

by Mark Sapiro

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

5 years, 11 months

[MM3-users] Xapian error on RHEL9 - module 'xapian' has no attribute 'QueryParser'

by Stephen J. Turnbull

l.reilly(a)ucl.ac.uk writes: > I first tried to install it using Method 1 > (https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian) > however, xapian_wheel_builder.sh seems to just exit right as it > starts "preparing xapian wheel...". I suppose this probably includes an invocation of "python -m build ...". Try editing the xapian_wheel_builder.sh script to add the "-v" option after "build" to try to get more information about what it did and (I hope) why it didn't. Not sure if multiple "-v" gives more information. I believe you could also use the distutils build instead of wheel, and ask pip to install that into the venv. (I could be wrong, one of the motivations for wheels was handling installation of binary Python modules and auxiliary DSOs better.) > I ended up installing Xapian 1.4.29 from source and symlinking > xapian in the venv as per Method 2. Method 2 is Debian-specific (it depends on Xapian and python-xapian both being packaged). What exactly did you do? > Has anyone else encountered this before? I've done the python-xapian build and install for an Ubuntu host with no problem. I used the Ubuntu Xapian package and installed python-xapian directly into the site-packages directory in the venv, though. I did need to work out a g++ version compatibility problem. I assume you're building the Python bindings in the same tree and at the same time as the main application? If so, you shouldn't have a problem with library version mismatches. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

11 months, 1 week

[MM3-users] Re: Please help - Held message is crashing mailman.

by Alex King

Thanks for your help Mark, it's ideal having the pointer to the issue in gitlab. I'll raise a bug with Ubuntu because this makes mailman3 in their LTS version unusable for me. Perhaps they can backport a fix for their version in LTS, otherwise they may have a backport or PPA source where I can get a 3.2 version, or just pin some packages from cosmic or disco. I think documenting this will be useful to people who hit the issue in future (Bionic/18.04 is supported until 2023, and likely the most used until 20.04 is released). Thanks, Alex On 7/04/19 4:29 AM, Mark Sapiro wrote: > On 4/5/19 10:27 PM, Alex King via Mailman-users wrote: >> Hi, >> >> I've used mailman a lot in the past, and decided to install mailman3 in >> a recent install. I'm unimpressed so far, it seems buggy. >> >> Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, >> mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. >> >> After a few messages, I now can't go to the "Held Messages" in >> postorius, I get a 500 error. >> >> I tried to interact on the command line, but could not work out how. >> Reading >> https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html >> and >> https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, >> I tried: >> >> # mailman shell >> Welcome to the GNU Mailman shell >> >>>>> command = cli('mailman.commands.cli_withlist.shell') >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> NameError: name 'cli' is not defined >> >> I did a lot of reading of the manual and googled, but I have no idea >> where the cli object is supposed to come from.....? The documentation >> is confusing. > > The line > > command = cli('mailman.commands.cli_withlist.shell') > > in > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > is dependent upon some behind the scenes setup to make the doctests > work. Granted this is confusing, but basically all that does is set > things up for the doctests to run the 'mailman shell' command. It is not > intended to be run from within 'mailman shell'. > > >> Anyway, after some trial and error, i found: >> >> # mailman shell >> Welcome to the GNU Mailman shell >>>>> list_manager = getUtility(IListManager) >>>>> m=list_manager.get("committee(a)[redacted].org") >>>>> from mailman.interfaces.requests import IListRequests >>>>> requests = IListRequests(m) >>>>> [x for x in requests.held_requests][0].id >> 8 >>>>> requests.get_request(8) >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> 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/requests.py", line >> 120, in get_request >> result.data_hash, expunge=False) >> 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/pending.py", line >> 138, in confirm >> value = json.loads(keyvalue.value) >> File "/usr/lib/python3.6/json/__init__.py", line 354, in loads >> return _default_decoder.decode(s) >> File "/usr/lib/python3.6/json/decoder.py", line 339, in decode >> obj, end = self.raw_decode(s, idx=_w(s, 0).end()) >> File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode >> obj, end = self.scan_once(s, idx) >> json.decoder.JSONDecodeError: Unterminated string starting at: line 1 >> column 1 (char 0) >> >> It seems something was written out to disk that can't be read in for >> some reason (assuming a json object on disk?) > > This is <https://gitlab.com/mailman/mailman/issues/385> which should be > fixed by <https://gitlab.com/mailman/mailman/merge_requests/333>. The > fix in in Mailman core version 3.2.0 > > >> How do I debug this further? How do I find the json being decoded? Any >> help would be appreciated. (I found mailman2 just worked, I was happy >> with that.) > > The issue is in storing a pickled representation of the json encoding of > 'rule_misses'. This gets very long if you have lots of header filters, > and with at least the mysql backend gets truncated in the database which > causes the Unterminated string error. > > I'm not sure what your options are for upgrading. The current Debian > packages are all >= 3.2.0 [1], but Ubuntu doesn't get 3.2.0 until cosmic > (18.10) [2]. > > [1] https://packages.debian.org/search?keywords=mailman3 > [2] https://packages.ubuntu.com/search?keywords=mailman3 > >> (My colleague posted a bug about this I believe but I don't have the >> link to that.) > > I haven't seen it. > >

7 years, 3 months

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

by Mark Sapiro

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

8 years

[MM3-users] Re: mailman import21 passwords

by Sam Darwin

> There is no guarantee that any Mailman Core installation into which a MM 2.1 list is imported actually also supports Django users for Postorius and/or HyperKitty. There is no guarantee that a mailman-core installation also includes Postorius and/or HyperKitty. However we can imagine that the vast majority do utilize all those components. If you've installed mailman3, you are probably installing Postorius and HyperKitty. To account for the fact that it's not 100% guaranteed, the import script could require a flag such as --django-accounts. Or it could even be another script entirely. So, the step wouldn't be automatic, but at least it would be an option. > 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. 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." 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? 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. 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".

1 year, 10 months

[MM3-users] Re: Why is it VERPing every message?

by Stephen J. Turnbull

Paul Tomblin via Mailman-users writes: > Right now it appears to be obeying the destination_recipient_limit > (5) in my postfix configuration, but it's not obeying the > destination_concurrency_limit (1), Is that a typo? In <https://www.postfix.org/postconf.5.html> I didn't finad a mention of 'destination_concurrency_limit', rather a family of "default_destination_concurrency_limit" and "$TRANSPORT_destination_concurrency_limit" variables for $TRANSPORT = "smtp", "lmtp", "local", etc. (Similarly for "*_destination_recipient_limit".) Also note that "*_destination_recipient_limit = 1" changes the meaning of the corresponding "*_destination_concurrency_limit" from "per domain" to "per recipient". From what you write above this isn't an issue in your configuration, but remember that "1" is special here. > and hitting their servers with a bunch of connections at the same > time. My research into postfix configuration continues. > I wonder if I should set max_recipients to 0 in Mailman, and let > Postfix decide how many recipients, if things would be a bit > happier? This is more likely to give you full control over a mail flow than having Mailman decide. In general it's better to configure limits as close to the agents you *don't* control as possible so downstream agents in your system don't mess with it. For example, if you have a set of messages to a site that all have temporarily failed, Postfix will likely batch them up for retry. Mailman can't do anything about that. Also, probably more important from your point of view, is that Postfix can deal with draconian limitations at one recipient domain and be more performant at sane domains. Mailman can't. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month, 1 week

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

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

9 years, 4 months

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

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

7 years, 9 months

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

by Stephen J. Turnbull

Johannes Rohr writes: > IndexError: list index out of range That isn't the problem, it's the earlier failure, I think: > File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, > in get_msg_id > token, value = get_dot_atom_text(value) > File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, > in get_dot_atom_text > raise errors.HeaderParseError("expected atom at a start of " > email.errors.HeaderParseError: expected atom at a start of dot-atom-text > but found '@localhost>' It appears that HyperKitty is trying to find a domain name (the common use for "dot_atom_text" in mail headers in a Message-ID), but is finding "@localhost>" instead. First I would try the check_hk_import script which is provided with HyperKitty. (You may also want to use the Mailman 2.1 cleanarch script to check for unescaped 'From ' lines, or the script at https://www.msapiro.net/scripts/cleanarch2 which can do that and check for unparseable Date: headers as well.) If that fails to identify the problem, try grep -iE '^(Message-ID|In-Reply-To).*@localhost>' problem_mbox_file | wc -l to see how how often that string appears, then grep -iE '^(Message-ID|In-Reply-To).*@localhost>' problem_mbox_file | head -15 to see if you can identify the problem text.[1] The problem character before the "@" is probably "<", "@", or ".", but maybe it's one of these: ()<>[]:;@\,." (note the double quote is a disallowed character). Other ASCII punctuation are allowed in message IDs. Once we know how the message id(s) is (are) malformed, we can discuss how to deal with them. Steve Footnotes: [1] In theory we should also check References but those usually have multiple continuations, which is annoying to deal with in grep.

3 years, 6 months

[MM3-users] [Solved] PAM error (was Re: Re: OK, so I backed out completely and re-installed....)

by Bill Oliver

On Wed, 2024-10-16 at 12:19 -0700, Mark Sapiro wrote: > On 10/16/24 10:26, Bill Oliver wrote: > > > > 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" > > forensic pathologists to discuss cases. > > > Does the forensicpath.us domain have an alias_domain configured in > mailman causing mailman to create > /opt/mailman/mm/var/data/postfix_vmap > and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. Yes, I created a "lists.forensicpath.us" early on. > > > > In my previous attempt, I added > > > > hash:/opt/mailman/mm/var/data/postfix_lmtp > > > > to both virtual_mailbox_maps and virtual_alias_maps, but I haven't > > done that yet here. I thought I'd ask and make sure I should. > > > > Should that be my next step? > > You should add hash:/opt/mailman/mm/var/data/postfix_vmap to > virtual_alias_maps only. Done. I started getting the disappearing mail problem again, though none of the references to errors from the changes I made originally. After spending a few hours going over debug files, I noticed that I kept getting a pam error. The mails were getting rejected over authentication errors. It turns out it was all a permissions problem with /sbin/unix_chkpwd. Apparently the sticky bit was not set correctly on installation. Here's a discussion of the problem: https://unix.stackexchange.com/questions/422411/pam-authentication-failure-… I still don't understand why this was a problem with mailman and not with "regular" mail, but doing the "chmod u+s /sbin/unix_chkpwd" resulted in things magically working just like it's supposed to. Thanks for the help! billo

1 year, 9 months

[MM3-users] seems solved (was: Re: error changed after restart)

by Guillermo Hernandez (Oldno7)

On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 7/2/21 19:04, Abhilash Raj wrote: Well... I did reinstall all mailman relationed apps with a pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient Restarted thee apache24 server... Aaaaaand closed de admin session and reopened it... (just for a "what if" sensation). I can not tell what have been the solution here, but now I can access the administrative pages and attend de pending subscriptions and discard retained messages. Thanks Abhilash and Mark for your support. >> >> On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >>> On 6/2/21 21:19, Abhilash Raj wrote: >>>> >>>> On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via >>>> Mailman-users <mailman-users(a)mailman3.org> wrote: >>>>> On 6/2/21 18:08, Abhilash Raj wrote: >>>>> >>>>> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) >>>>> via >>>>> Mailman-users wrote: >>>>> >>>>> I restarted de server and the error changed. Now the log >>>>> shows "KeyError: 'subscription_mode'": >>>>> >>>>> Did you also restart Mailman Core after the upgrade? >>>>> >>>>> Yes, indeed: I stopped mailman core and all the processes related. >>>>> Did the upgrades. Started all again. Find the errors in the web user >>>>> interface. Stopped all again. Looked for errors in the log. Restarted >>>>> the complete server. Found the second error that this second mail is >>>>> about to. It happens when, in the main page that shows all the lists >>>>> you click to see one of them. It seems to me that it has been >>>>> database structure changes in django that the upgrade is not aware... >>>>> but it's a very long shot from my side. >>>> `subscription_mode` was added in Mailman Core 3.3.2 and it is actually >>>> a derived atrribute and not stored in Database. Mailman's API >>>> should be >>>> returning this attribute for each Member, but for some reason it seems >>>> to me like it isn't doing that even though do have Mailman 3.3.3 >>>> running >>>> like you said. >>>> If you have Curl installed, can you send me the output of: >>>> $ curl -u <user>:<pass> >>>> http://localhost:8001/3.1/members?count=5&page=1 >>> This is the output you asked for (it's the same you can see when you >>> try >>> to interact with one list): >>> >>> /usr/local/mailman3 # curl -u XXXXXX:XXXXXX >>> http://localhost:8001/3.1/members?count=5&page=1 >>> /usr/local/mailman3 # <html> >>> <head> >>> <title>Internal Server Error</title> >>> </head> >>> <body> >>> <h1><p>Internal Server Error</p></h1> >>> >>> </body> >>> </html> >>> >>> No log entry has been produced... >> This is weird, if you have working Core, then there should be *some* >> json returned >> from the above command. Do you have the Gunicorn running? > I have the uwsgi approach running... >> What is the >> output of `ps -ef | grep mailman`? > > none > > but if I do an ps ax | grep mailman it shows > > /usr/local/mailman3 # ps ax | grep mailman > 26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master > --force -C /usr/local/mailman3/var/et > 26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > 50481 2 S+J 0:00.00 grep mailman > 26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > 26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > >> Are you able to run `mailman members` command to list the members of >> a list? > > Yes. All the commands are working as expected. > >> Also, how did you actually install Mailman? > > Using pip. Here is a detailled post of how I did put all together: > > https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 > > Thanks for your support > >> >> Abhilash. >> >>> TIA. >>> >>> >>> >>> >>>> It should ideally return an output that looks something like shown >>>> here[1]. You >>>> can put the username/password of Core's API server in the above >>>> command. >>>> [1]: >>>> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… >>>> >>>> >>>> Abhilash >>>>> I'm using sqlite as django database and mysql for mailman. >>>>> >>>>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >>>>> Server Error: >>>>> /mailman3/mailman3/lists/name_and_domain.of.the.list >>>>> Traceback (most recent call last): File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 119, in __getattr__ return self._get(name) File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 86, in _get raise KeyError(key) KeyError: >>>>> 'subscription_mode' During handling of the above exception, >>>>> another exception occurred: Traceback (most recent call >>>>> last): File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >>>>> line 34, in inner response = get_response(request) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>>> >>>>> line 115, in _get_response response = >>>>> self.process_exception_by_middleware(e, request) File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>>> >>>>> line 113, in _get_response response = >>>>> wrapped_callback(request, *callback_args, **callback_kwargs) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>>> >>>>> line 71, in view return self.dispatch(request, *args, >>>>> **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >>>>> line 74, in dispatch return super(MailingListView, >>>>> self).dispatch(request, *args, **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>>> >>>>> line 97, in dispatch return handler(request, *args, >>>>> **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >>>>> line 295, in get member.subscription_mode == File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 124, in __getattr__ self.__class__.__name__, name)) >>>>> AttributeError: 'Member' object has no attribute >>>>> 'subscription_mode' *********************** some info about >>>>> the installed versions via pip list: pip list | grep django >>>>> django-allauth 0.44.0 >>>>> django-appconf 1.0.4 >>>>> django-compressor 2.4 >>>>> django-extensions 3.1.0 >>>>> django-gravatar2 1.4.4 >>>>> django-haystack 3.0 >>>>> django-mailman3 1.3.5 >>>>> django-picklefield 3.0.1 >>>>> django-q 1.3.4 >>>>> djangorestframework 3.12.2 pip list | grep mailman >>>>> django-mailman3 1.3.5 >>>>> mailman 3.3.3 >>>>> mailman-hyperkitty 1.1.0 >>>>> mailmanclient 3.3.2 pip list | grep >>>>> postorius >>>>> postorius 1.3.4 On 6/2/21 11:12, >>>>> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >>>>> >>>>> I've just upgrade mailman 3 installation following Mr. >>>>> Sapiro advice: did a pip install --upgrade >>>>> django-mailman3 hyperkitty mailman mailmanclient >>>>> mailman-hyperkitty postorius I did a "python3 manage.py >>>>> migrate" after, too. And all seemed to run well. All the >>>>> lists showed in postorius via web, but when I try to >>>>> accesss into one of them the browser shows an error. In >>>>> the log you can see: *-*-*-*-*-*-* Traceback (most >>>>> recent >>>>> call last): File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 119, in __getattr__ return self._get(name) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 86, in _get raise KeyError(key) KeyError: >>>>> 'get_requests_count' .. (And after all the traceback >>>>> lines) AttributeError: 'MailingList' object has no >>>>> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >>>>> seem to be distributing messeages well.. but I cannot >>>>> acces via web administration (django/postorius) Can >>>>> anyone point me in the right direction to solve this, >>>>> please? _______________________________________________ >>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send >>>>> an email to mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Mailman-users >>>>> mailing list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an >>>>> email to mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>>>> >>>>> _______________________________________________ Mailman-users mailing >>>>> list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >>>>> mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>> >>> _______________________________________________ >>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

5 years, 5 months

[MM3-users] Re: Question about message bounce stats

by Ruth Ivimey-Cook

Stephen, Thanks for your comments. I kinda-thought that was the state of affairs but am glad there is at least some work on it in the pipeline. If Abhilash has a starting point, and there is acceptance from others to integrate something of this sort, then I could possibly help make it happen. Ruth On 30/08/2021 16:46, Stephen J. Turnbull wrote: > Ruth Ivimey-Cook writes: > > > Does Mailman3 keep such stats, and if so is there any way to get > > access to them, even if only API? I would think it useful to do so > > (and yes, for individual outgoing messages at least for a period). > > In released versions, it currently does not, as far as I know. This > kind of thing should be available from your MTA, of course, and I > think there was a visceral opposition to keeping track of people's > behavior that way from the early days. So those are our excuses. > > However, it's something that comes up occasionally on the list as well > as as a GSoC proposal, and I think there's some code on a branch for > this that Abhilash has been threatening to release. And of course > HyperKitty now publishes stats on posting behavior. So there's really > no reason to oppose it, now it's just a matter of time to implement. > > Abhilash's participation has been kind of spotty recently (and > apologetic about it, he's not going anywhere), but hopefully he'll > pick up the thread shortly and at least confirm or deny what I wrote > here. > > Steve -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 11 months

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

by Roland Giesler

On 2024/07/29 22:45, Odhiambo Washington via Mailman-users wrote: > On Mon, Jul 29, 2024 at 10:09 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/29 16:26, Roland Giesler via Mailman-users wrote: >>> However, the response URL doesn't not respond when I click it. It >>> opens in a browser, but the processes times out. I'm now checking why >>> that is. >> I found out why. Firefox and Brave (Chromium) have a bug in their https >> redirect functionality, so one cannot disable https redirection on any >> site at this stage. Since I don't have the https certificates in place, >> I had to use Edge to be able to visit >> >> http://192.168.161.103/accounts/confirm-email/Mg:1sYQR2:xt3_639JwJ78GW9Xhrp… >> >> Account verified. >> > The actual issue is that the verification email URL is sent with HTTPS://...... > You cannot blame a browser for NOT respecting the HTTPS and redirecting it > to HTTP. > So one has to know that their site is not secured with SSSL certs, and so > change httpS:: to http:// > I don't think Edge is the only one that does that. On my tests, I use VMs > and Brave/Chrome/Firefox to access the link. I just change HTTPs to HTTP > manually. > It's a situational awareness type of thing. My browsers do not respect it when I change https to http. I have an issue open with Firefox on this. They change the URL back to https, so the address cannot be loaded. I have since added Let'sEncrypt certificates to the nginx config, so now https is being accepted. > >

2 years

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

by Mark Sapiro

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

1 year, 9 months

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

by Mark Sapiro

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

1 year, 5 months

[MM3-users] Re: deployment recommendation(?)

by Marc SCHAEFER

Hello, On Thu, Jul 18, 2024 at 09:05:28AM -0000, noc(a)iem.at wrote: > (my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). Which is no longer supported (unless you subscribed to ELTS) -- for more than two weeks now. I upgraded from Mailman2 (buster) to Mailman3 (bookworm). I took the opportunity to isolate mailman in its own container, so I really imported the lists & archives. PostgreSQL is also in another container now. The main mail server also. So far I have not seen any issue that I could not fix easily, in part with the help of this list, which is very efficient. > what are the drawbacks, limitations, advantages and benefits of the various deployment methods? Some of the enhancements (e.g. password forgotten mail only sent to actual account holders) will not be backported: only real security fixes will. I might apply some of those by hands, using diversions, as I was doing for Mailman2. I will also implement a IPS using mailman's log, looks useful since, opposite to some Perl web apps I run, it does not seem there are any built-in counters in Python/Django (e.g. max number of logins per minute, hour, day; max number of e-mails to an e-mail address per minute/hour/day, etc). Maybe I just don't know enough of Django though. It's handy eg. when people mass-create accounts, etc. The main issue I had is the enormous amount of resources (disk, database, memory) that Mailman3 uses over Mailman2 (about 10x more RAM, and the mailmanweb DB backup, zstd compressed, is 2 GBytes, where the archives were AFAIR 500M in Mailman2). With some tweaking, I could reduce the 8 GB memory footprint to 2 GB. But as you already run Mailman3 it should not be new.

2 years

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Hi Mark, Thanks for taking the time to reply. Mark Sapiro wrote: > On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > > However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. > > Am I missing something with the expected functionality? > > A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? > Actually, it is good practice to set that to Hold for moderation for > all lists or at least all those that don't require moderator approval > for subscription to prevent a spammer from subscribing and spamming the > list. Then, upon approving a member's post you can also set the member's > moderation action to default processing and upon discarding a spammers > post, you can also set the spammer's moderation action to Discard. I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. I'm happy to do more testing, provide other information/logs as desired if that would help? cheers, Mark

1 year, 8 months

[MM3-users] Re: Cannot setup announce-only mailing list

by Abhilash Raj

On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: > On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > > > Of course, I want to keep this mailing list "read only" for members, and > > I want only selected people to post to that mailing list. > > > > Any idea on how to achieve that? > > > There is only one difference between the `Discussion` and `Announce` > list styles, and that is for an `Announce` list, the `allow_list_posts` > attribute is set to `False`. In turn, all that does is cause the > List-Post: header to be set to NO rather than the list posting address. > > There is a discussion at <https://wiki.list.org/x/4030685> of how to set > up an announce list for Mailman 2.1. Most of this translates > straightforwardly to Mailman 3, although not all the relevant settings > are exposed in Postorius. > > In short, you need to set this up manually using things like moderation > settings and custom templates for the welcome message. Mark, do you think we should make the actual announce-only style reflect these settings so folks don't have to manually set these after they create a announce-only list? I am not sure the reason behind these settings lacking for the current announce-only style. Are there situations where announce-only list would have different list setting? > > -- > 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, 6 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Mark, I tried doing this. I unsubscribed myself from a list, set the policy as you suggest and re-applied. I got no confirmation messages but as moderator I got the moderate message. I then tried a bogus email and saw that a message was sent to that and no moderator message to me. Would the server skip the verification message because I'm a moderator/admin? Yours, Allan On 3/28/23, 08:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 01:49, Allan Hansen wrote: > > There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. > > Our Subscription Policy is currently: 'Moderate' for all lists. If you set the subscription policy to 'Confirm, then moderate' the user will receive a confirmation request based on the list:user:action:subscribe template whether or not the address is verified. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@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 <mailto:mailman-users@mailman3.org>/message/ORDAIBK4JUICZADYPEPWDVV2WP5EXWEB/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

3 years, 4 months

[MM3-users] Re: Error message from monthly cronjob

by Danil Smirnov

Check this: https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… BR, Danil Smirnov On Tue, Dec 5, 2023 at 1:40 PM Johannes Rohr <johannes(a)rohr.org> wrote: > Dear all, > > Mailman3 on my system is installed in virtualenv. Each month I get the > following error message. This error does not seem to have a serious > impact on the functioning of mailman, still, what does it mean and how > do I get rid of it? > > Thanks for any hints! > > Johannes > > > > -------- Weitergeleitete Nachricht -------- > Betreff: Cron <mailman@*** /opt/mailman/venv/bin/mailman-web > runjobs > monthly > Datum: Fri, 1 Dec 2023 05:56:40 +0100 (CET) > Von: Cron Daemon <root(a)mail.rooot.de> > An: mailman@*** > > > > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.10/site-packages/django_extensions/management/commands/runjobs.py", > > line 40, in runjobs > job().execute() > File > "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/jobs/update_and_clean_index.py", > > line 37, in execute > run_with_lock(update_index, remove=True) > File > "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", > line 177, in run_with_lock > with lock: > File > "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", > line 470, in __exit__ > self.unlock() > File > "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", > line 420, in unlock > raise NotLockedError('Already unlocked') > flufl.lock._lockfile.NotLockedError: Already unlocked > _______________________________________________ > 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 danil(a)smirnov.la >

2 years, 7 months

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

by Stephen J. Turnbull

Thomas Schachtner via Mailman-users writes: > I just saw that mailman does not start (systemctl start > mailman3.service) on my debian installation if the postfix > configuration file is not there, so I thought it might be needed by > mailman3. Mark explained this. > But maybe [the Mailman won't start issue] is not a mailman issue > but a debian-only issue... It's that Mailman 3 recreates the postmapped database files at startup. It will happen on any stock Mailman 3 + Postfix installation if postmap can't find main.cf. > Nevertheless, I just put the file on the mailman box and > everything is fine. It does not seem to be changed when starting > mailman, so maybe that's safe... At startup, Mailman reads the postfix-lmtp and postfix domains files, and (re-)creates the .db files using Postfix's postmap utility. When creating a domain or list, it adds an entry to the appropriate file, and then compiles it with postmap. Otherwise Mailman does not touch or even read those files. > I'll definitely have a look at the callout approach (currently, I > have no clue what that might be...), but I also see that exposing > LMTP to the Internet is dangerous... Exposing anything to the Internet is dangerous. Since LMTP is (usually) cleartext and unauthenticated (I'm pretty sure both Postfix and Mailman can do authenticated TLS), yes, it's riskier than say ssh. That's why I suggest firewalls and TLS connections, and then you're basically as secure as ssh. Or you can avoid exposing LMTP by having Postfix on the Mailman host, and use virtual alias or mailbox hosts with virtual_transport = lmtp:[127.0.0.1]:8024 to catch the Mailman traffic. Steve

2 years, 6 months

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

by Mark Sapiro

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

7 years, 1 month

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

by Mark Sapiro

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

6 years

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 2:21 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > > On 11/22/22 13:40, Hirayama, Pat wrote: > > > > There is only one uwsgi.ini file, and it is in the same directory as settings.py, > settings_local.py and wsgi.py > > > What is the content of that file? uwsgi.ini: [uwsgi] uwsgi-socket = :8000 chdir = /opt/mailman/mailman-suite/mailman-suite_project wsgi-file = /opt/mailman/mailman-suite/mailman-suite_project/wsgi.py harakiri = 60 master = true process = 4 threads = 4 uid = mail gid = mail attach-daemon = ./manage.py qcluster The referenced wsgi.py looks pretty vanilla: """ import os # import sys # import site # For some unknown reason, sometimes mod_wsgi fails to set the python paths to # the virtualenv, with the 'python-path' option. You can do it here too. # # # Remember original sys.path. # prev_sys_path = list(sys.path) # # Add here, for the settings module # site.addsitedir(os.path.abspath(os.path.dirname(__file__))) # # Add the virtualenv # venv = os.path.join(os.path.abspath(os.path.dirname(__file__)), # '..', 'lib', 'python2.6', 'site-packages') # site.addsitedir(venv) # # Reorder sys.path so new directories at the front. # new_sys_path = [] # for item in list(sys.path): # if item not in prev_sys_path: # new_sys_path.append(item) # sys.path.remove(item) # sys.path[:0] = new_sys_path from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") application = get_wsgi_application() > > -- > 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 Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

3 years, 8 months

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

by Mark Sapiro

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

3 years, 6 months

[MM3-users] Re: Apache shows No Lists

by ceo＠sartrack.nz

Thanks; There has never been a 'Mailman' user. I do have a www-data user (all Apache2 data' and there is a 'list' user. 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'. 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? 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.

3 years, 2 months

[MM3-users] Re: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

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

1 year, 5 months

[MM3-users] Re: list footer questions

by Mark Sapiro

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

6 years, 1 month

[MM3-users] Re: mailman3 not working for mailman21 lists

by Stephen J. Turnbull

Diana von Bidder writes: > I have several entries in /var/lib/mailman3/queue/shunt/ with Aug 21 > timestamps, Evidence! Preserve it! You can look at those using "mailman qfile <file>", where the specification for <file> needs to be a regular path. the 'qfile' command does not assume a prefix of /var/lib/mailman3/queue/, unfortunately. Look for non-ASCII characters in headers, very long lines, a line with no indentation that doesn't match the "name: content" pattern that header follow (indented lines are considered to be "logically" part of the previous line so that's not a problem), and empty lines in the header. (There is always an empty line between the message header and the message body, but an empty line in the middle of the header will often cause problems.) Check the size of the files; probably all these messages were short test messages and it won't matter but in real life you might have a huge attachment which I think would be printed out. Start with the short ones. :-) > and several entries in /var/lib/mailman3/queue/shunt/ with > current timestamp (i.e. everytime I ls -l there is a new timestamp with > the current time). I'm not sure what's going on with that. The point of the shunt queue is that Mailman doesn't know what to do and it's putting the messages there to wait for human intervention. So timestamps shouldn't be changing. > My output looks exactly the same. Good! If you want you can send me one of those entries in shunt (assuming you're satisfied with my assurance of privacy of any identifying information such as IP addresses, domain names, and mailbox names). Steve

3 years, 11 months

[MM3-users] Re: Enable delivery

by Mark Sapiro

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

1 year, 7 months

[MM3-users] HyperKitty archiver <h1>Server Error (500</h1>

by Daniel Erlendson

Hello all, I'm getting the following in the logs in our MM server: Nov 01 14:00:17 2021 (26843) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <h1>Server Error (500)</h1> (500) Nov 01 14:00:17 2021 (26843) Exception in the HyperKitty archiver: <h1>Server Error (500)</h1> Nov 01 14:00:17 2021 (26843) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <h1>Server Error (500)</h1> which is mirrored in the mailman-web.log with this 21:57:07 [Q] INFO Enqueued 1962530 21:57:08 [Q] INFO Process-1:36 processing [sender_mailman_id] 21:57:08 [Q] INFO Processed [sender_mailman_id] ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): plus a bunch of python errors and this: ValueError: A string literal cannot contain NUL (0x00) characters. ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): We are on v3.1 on Ubuntu 18.04. I do have a project beginning to move to Ubuntu 20.04 eventually. For now, I'm struggling to find the resolution to this error. I've looked at the site here, did a rebuild on the whoosh index, I've found and tested the suggestions to add a localhost non-https in apache for HyperKitty, I've edited HyperKitty to be https rather than HTTP, none of these settings / changes seem to resolve the issue. Oddly for all intents and purposes, the server appears to run fine, the archive might be a bit slow but it doesn't seem to have issues other than the constant errors coming into the admin emails. Happy to post any configs or detail anything, appreciate any replies. Respectfully,

4 years, 9 months

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 12/02/19 11:25 AM, worik wrote: > Friends > > On a fresh install (docker) on a fresh VPS I am getting all Mailman > messages to Gmail addresses bouncing telling me I am sending too many > messages. Has anybody else have this problem? > > I am getting the following error in mail.log: "Our system has detected > an unusual rate of 550-5.7.1 unsolicited mail originating from your IP > address. To protect our 550-5.7.1 users from spam, mail sent from your > IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 > 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" > > I have been to the URL mentioned and exhausted my options there. > > Worik > Well. Golly. I complained to Google, and heard nothing back. But with no changes on my end they have stopped bouncing my emails. Now they are just marked as spam. I can live with that. Very frustrated with google's levels of service. What a pain! Thank you Brian Carpenter, who may well have been right about "warming up the IP". What ever that might mean. I have not read that RFC, but I have a lot to learn. Thank you Mark Sapiro, for your patience. Thank you every body for the obviously hard work creating this system. I have a long way to go until I know how to use it properly, but I am no longer stopped at the google cliff. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) I have a lot of onion pie, that explains the aroma

7 years, 5 months

[MM3-users] Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Christian Schneider

Dear mailman community, with the help of you I was able to set up a new mailman3 environment (a big THANK YOU!!! :-)): OS: Ubuntu 24.04-LTS mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] Method: Python Virtual Environment Installation My configuration files are placed in the following directory: /etc/mailman3 - gunicorn.py - mailman.cfg - settings.py The environment is up and running: A list for testing is set up and mails are transfered (and archived) using the test-list - successfully... :-) Looking at the thread overview of the list (in Hyperkitty archives) I realized that the shown date format is unusual (for Germany), like: Do Mai 22, 3:57 nachm. (meaning: Thu May 22, 3:57 p.m.) I would prefer a format like: 22-05-2025 15:57:24 So I tried to reconfigure this setting in settings.py according to this URL: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the format did not change. (After changing settings.py I initiated a restart of mailman3 and mailmanweb) I also set USE_L10N to False as suggested in Django-Docs: https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO… My /etc/mailman3/settings.py is parsed - as far as I can say because changing USE_I18N to false (in /etc/mailman3/settings.py) switches date to English as this is my locales-setting on Ubuntu... Nevertheless the format stays the same (in this case: Thu May 22, 3:57 p.m.) How can I adjust the date format (in the discussion boxes) at the thread overview page (url: https://my-domain.de/archives/list/test-list@lists.my-domain.de/)? Any hint is appreciated! Thank you very much and kind regards Christian

1 year, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I tested with python3 and got this: (env) [mailman@localhost mailman-suite_project]$ python3 manage.py migrate Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line utility.execute() File "/var/lib/mailman/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 337, in execute django.setup() File "/var/lib/mailman/env/lib/python3.6/site-packages/django/__init__.py", line 27, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/apps/registry.py", line 85, in populate app_config = AppConfig.create(entry) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/apps/config.py", line 94, in create module = import_module(entry) File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 978, in _gcd_import File "<frozen importlib._bootstrap>", line 961, in _find_and_load File "<frozen importlib._bootstrap>", line 948, in _find_and_load_unlocked ModuleNotFoundError: No module named 'hyperkitty' Why does it say that hyperkitty is not installed? 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

9 years

[MM3-users] Re: Mailman3 on FreeBSD

by John Poltorak

I'm making progress, albeit slowly. Any progress I make I will post on the FreeBSD forums... https://forums.freebsd.org/threads/61050/ On Sun, Aug 13, 2017 at 7:14 PM, Barry Warsaw <barry(a)list.org> wrote: > Thanks for the reference John, > > > On Aug 13, 2017, at 06:52, John Poltorak <karotlopj(a)gmail.com> wrote: > > > > Regarding location of mailman.cfg...FreeBSD adopt a strict directory > > hierachy > > > > https://www.freebsd.org/cgi/man.cgi?hier(7) > > > > Anything installed outside the base OS belongs in /usr/local > > I looked over that page. Does this mean that even if you were to install > Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want > mailman.cfg in /usr/local/etc instead of /etc? That would differ from most > Linux distributions where package manager installed packages would have > their configuration files in /etc, and where “third party” packages would > have them in /usr/local/etc. > > > I guess that issue is something for the FreeBSD porters of Mailman3… > > I think so. I think for now I don’t want to support > /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion > if there are some more generic use cases. OTOH, the internal function that > calculates the search paths could be refactored to make it easy for > distributions to carry small deltas to add that as a search path (it really > wouldn’t be that hard to do now, but it’s a little icky). Of course, you > can’t add a configuration file to find a configuration file. :) > > Cheers, > -Barry > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

8 years, 11 months

[MM3-users] FILTER_VHOST for 3.2.1 not working after install

by Élodie BOSSIER

Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french.

6 years, 6 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Thu, Apr 11, 2024 at 11:00 PM Ron / BCLUG <admin(a)bclug.ca> wrote: > Mark Sapiro wrote on 2024-04-10 14:09: > > > I suspect you are not starting the services with your venv active. > > What's in your mailman3.service and mailman3-web.service files? > > Thanks for the pointer! > > I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` > somehow. > > > I changed that to match the docs, did the `systemctl daemon-reload`, > etc. but still had similar problems. > > > I went through all my config files carefully, I wiped the static folder > completely and rebuilt it, and I finally have the last piece of the > puzzle in place and my web interface is working! > > I'm not sure which change actually fixed the issue though. > > > (When looking at "Available lists" my header has "example.com" in the > top-left corner?!?) > See also this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… But read it as "example.com", not example.org :-) I think I need to backup what I have and do a clean re-install so I have > a better grasp of what's going on with all these components. > Way to go! Before I got MM3 working on the sites that I manage, it took me lots of installs and wipes until I could figure out what's going on. I was literally being hand-held by the good developers. -- 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]

2 years, 3 months

[MM3-users] Re: Archive not working - Reg.

by Stephen J. Turnbull

Nirmal J via Mailman-users writes: > While I am opening mailman.log.1 It is displaying this. Everything up to this ACCEPT is irrelevant: > Oct 28 15:46:33 2025 (678430) ACCEPT: <176164659325.678449.14176354478536014912(a)list1.iitm.ac.in> Looks like the Mailman configuration is correct, at least up to the point of contacting the HyperKitty archiving code: > Oct 28 15:46:34 2025 (678434) Exception in "hyperkitty" archiver But your TLS is misconfigured (probably not configured at all?): > ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992) (Haven't we been here before?) The most likely problem is that you did not configure the base_url in mailman-hyperkitty.cfg. If your SSL configuration is correct, then changing that line to something like base_url: https://list1.iitm.ac.in/archives/ should do the trick (be careful, pretty sure it will be similar but the host part must match the SSL certificate used by the host). In the most common installation, Mailman and HyperKitty are on the same host. If so, there's no point in using SSL. At least I cannot think of a scenario where an adversary can tap a local connection but doesn't have a dozen other ways to steal the same information. So if that is the case, an alternative to fixing the SSL configuration is to have a virtual host listening on port 80 that doesn't accept any requests except those reverse proxied to HyperKitty. Or even just going directly to http://localhost:8000/archive should work. (This has the possible disadvantage that accesses to HyperKitty from Mailman won't be logged by your webserver, but they will still normally be logged by HyperKitty itself I think.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months

[MM3-users] Re: user self registration

by Stephen J. Turnbull

Christian Stalberg via Mailman-users writes: > Something strange is now going on. Now when a user tries to > subscribe themself and they get the ' Please check your inbox for > further instructions' no such email arrives in their mailbox. Please check your mail server and Mailman logs to see whether mail is being sent. The most relevant Mailman log is smtp.log (or possibly virgin.log, but almost nobody uses the latter any more). Also check that all the runners are running. > Relatedly, if I as an admin try adding someone to a list via the > Mass Subscribe, they are not added to the list, but they do appear > in the listing of all Users. I don't see how the setting ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ could have either of the effects above. It effectively sets a flag that is used internally by Django, but nowhere in the mailmanweb code. That is all it does. But once Django hands off the subscription request to the Postorius code, Django is no longer involved. So I am quite sure that the ACCOUNT_ADAPTER change did not cause either issue. I seem to recall that you have tried a number of things to disable the sign-in. Please review all changes made in the last couple of months to mailman.cfg, settings.py, and your mail server to see if any of those have been left in place, or whether apparently unrelated changes were made. Also, are you sure these problems started immediately after making the change to ACCOUNT_ADAPTER? If you can determine when these issues started accurately, it may help in localizing the issue to a particular change or set of changes. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 3 weeks

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Mark Sapiro

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

4 years, 2 months

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

by antoine.depoisier＠ikmail.com

I use mailman with kubernetees, and I have four pods. I currently use persistentVolumeClaim for two folders in the mailman configuration "cache" and "messages". I share these folders, as mailman needs to be consistent for these two folders, but I'm wondering if I should share other folders as well, like locks and such. There are all the folders in mailman archives cache data etc lists locks logs master.pid messages queue templates I ask this question because I often have a problem when creating a mailing list. I think I have a problem with the locks, but I'm not sure if the problem is due to the fact that the locks folder is not shared. If you want more details, here's the trace I sometimes get, when someone tries to create a mailing list: File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3.12/site-packages/mailman/rest/lists.py", line 322, in on_post mlist = create_list(**validator(request)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 102, in create_list call_name(config.mta.incoming).create(mlist) File "/usr/lib/python3.12/site-packages/mailman/mta/postfix.py", line 96, in create self.regenerate() File "/usr/lib/python3.12/site-packages/mailman/mta/postfix.py", line 106, in regenerate with Lock(lock_file): ^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/flufl/lock/_lockfile.py", line 467, in __exit__ self.unlock() File "/usr/lib/python3.12/site-packages/flufl/lock/_lockfile.py", line 417, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked When I check the lock folder, I have these two files, and I'm wondering if I should delete these two files : -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck|mailman-core-deployment-5f59557b66-bkkf4|16|4268829230172994873 Do you have any answer for me ?

1 year, 5 months

[MM3-users] Re: Importing mbox files into archive defect with lines with From

by Mark Sapiro

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

7 years, 1 month

[MM3-users] Performance of member listing [was: How to remove a nonmember...]

by Stephen J. Turnbull

skenny(a)scss.tcd.ie writes: > Actually, I came across another thread where you suggested > increasing the "graceful_timeout" in gunicorn.cfg. In fact this > didn't work for me, but I followed your reference to the > documentation Which documentation? An exact reference would be nice, but I'm not even sure if you're talking about Mailman or gunicorn docs here -- whatever you have off the top of your head would help! I'd like to find a place to put this in the Mailman docs. > and tried increasing just "timeout" instead - and that worked! > > It's pretty slow, but I can now get all my (very long) mailing list > members via the REST API, which is great. Do you mind saying just how long your very long list is (ie, the number of subscribers)? It's useful to us to have some idea of the scales at which people are operating (and having performance issues :-/ ). (The biggest list I run in Mailman 3 is 17, so I'm not much help with that.) I'm not happy about your "pretty slow" remark. We've had Mailman 2 lists get seriously big (seven digits worth of subscribers, I think). If we can improve the performance of listing, or help you to improve it by using a different API, it would be good for you, and help with scaling Mailman 3. I forget the context, but let me confirm: you're using the REST interface to get the member list, right? The main point: I'm wondering if you might not get better performance by getting using the paginated interface, and assembling the list at the receiving end instead of trying to get it all at once. Steve

6 years, 3 months

[MM3-users] Re: integrate subscribe form in Website -> CSRF-token

by Mark Sapiro

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

5 years, 1 month

[MM3-users] Single Click Unsubscribe

by Stephen J. Turnbull

J D writes: > However, Google has recently announced that they will be enforcing > one-click unsubscribe for bulk senders: > https://techcrunch.com/2023/10/03/gmail-to-enforce-harsher-rules-in-2024-to… > > Thoughts? One-click unsubscribe for bulk senders of *commercial* email. For those of you who are using Mailman to send bulk commercial email, I guess you have to worry whether they're going to apply this to your advertising and product announcement lists only, in which case I guess you end up with a higher than current unsubscribe rate (but if you're smart you'll figure out how to use that expression of disinterest to advantage! ;-) Or if they are going to apply it to user discussion forums as well, in which case you have to think about the issue of user-on-user mischief (eg, redact OTKs or whole footers in quoted material). I'm not sure if we should be in the business of providing those features (they're kinda getting into content and business model), but I'd at least consider adding them to contrib, dunno about the other devs tho. For one thing, we already provide the OTK infrastructure for email verification. The rest is a nothingburger too. It looks like they're just saying they're going to enforce best practices, like publishing SPF and DKIM policies and signing your outgoing mail with valid keys. Mailman users should already be doing those things, because a lot of sites already bounce or discard unsigned email without valid signatures. It's the rules that Google does not announce, especially when they have publicly announced the opposite, that are a big threat. Personally I think the company has long since gone over to the Dark Side of the Force, and I'm rooting for the FTC. Steve

2 years, 9 months

[MM3-users] Slow performance when listing members on Postorius

by Alan So

We are about to upgrade to Mailman core 3.3.9 and Postorius 1.3.10. We notice that for setup with large number of members, the performance is much slower when listing members on web (Postorius). Further troubleshooting show that there are quite a number of API calls which do not appear in Mailman core 3.3.5 and Postorius 1.3.6 when we list members. [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/33a6266d0a04472c8d5d6c78869a964c/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/7a18b7cb90a34ac98881a3f01b5488d1/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/61c6c3e2aaf443babd3bd191519b0424/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/8dd681165b8c436fac6793cae1ed2c27/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" Further tests showing that each database query using "_member_id" in table member can take as much as 0.3 to 0.5 seconds for some large installations. The default 25 members per page mean that it will take at least 7.5 to 12.5 seconds. Changing to 200 members per page will take even longer time. We wonder whether "_member_id" should be indexed just like most other id in the database mailman_core in order to solve the issue. Or are there any other workarounds? +----------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | _member_id | char(32) | YES | | NULL | | | role | int(11) | YES | MUL | NULL | | | list_id | varchar(255) | YES | MUL | NULL | | | moderation_action | int(11) | YES | | NULL | | | address_id | int(11) | YES | MUL | NULL | | | preferences_id | int(11) | YES | MUL | NULL | | | user_id | int(11) | YES | MUL | NULL | | | bounce_score | int(11) | YES | | NULL | | | last_bounce_received | datetime | YES | | NULL | | | last_warning_sent | datetime | YES | | NULL | | | total_warnings_sent | int(11) | YES | | NULL | | +----------------------+--------------+------+-----+---------+----------------+

2 years, 3 months

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 30 Jun 2020, at 8:22, Florian Schulze wrote: > On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > >> On 6/29/20 1:38 AM, Florian Schulze wrote: >>> Hi! >>> >>> After upgrading to HyperKitty 1.3.x I get the following error for >>> qcluster: >>> >>> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >>> 300, >>> in pusher >>> task = SignedPackage.loads(task[1]) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 31, >>> in loads >>> serializer=PickleSerializer) >>> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >>> line >>> 38, in loads >>> return serializer().loads(data) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 44, >>> in loads >>> return pickle.loads(data) >>> AttributeError: Can't get attribute 'process_task_result' on <module >>> 'hyperkitty.tasks' from >>> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >>> >>> How do I recover from that? It seems like there are still persisted >>> tasks in the qcluster queue using the old code from 1.2.x with the >>> old >>> locking implementation. >> >> Have you stopped ans started qcluster since upgrading? > > Yes > >> Are you running the Django periodic jobs? > > They were disabled because of the errors (someone else did the > upgrade). I have enabled them again and will watch it and report back. The cronjobs seem to work fine, no errors so far. The queue doesn't seem to change at all. In "qmonitor" there is nothing listed and the statusline remains the same at ORM default Queued 303(118) Success 100 Failures 0 Regards, Florian Schulze

6 years, 1 month

[MM3-users] Re: digest summary heavily cluttered with hrml code

by Mark Sapiro

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

5 years, 9 months

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

by Onyeibo Oku

On Wed, 19 Oct 2022 23:38:05 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Judging from the traceback, Onyeibo Oku's > /opt/mailman/venv/bin/mailman is quite different from mine which is > just ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: > 'mailman==3.3.5','console_scripts','mailman' __requires__ = > 'mailman==3.3.5' import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', > 'mailman')() ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv? > True mine is different: **************** /opt/mailman/venv/bin/mailman ************ #!/opt/mailman/venv/bin/python # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' import re import sys # for compatibility with easy_install; see #2198 __requires__ = 'mailman==3.3.5' try: from importlib.metadata import distribution except ImportError: try: from importlib_metadata import distribution except ImportError: from pkg_resources import load_entry_point def importlib_load_entry_point(spec, group, name): dist_name, _, _ = spec.partition('==') matches = ( entry_point for entry_point in distribution(dist_name).entry_points if entry_point.group == group and entry_point.name == name ) return next(matches).load() globals().setdefault('load_entry_point', importlib_load_entry_point) if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit(load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')()) *************** end of /opt/mailman/venv/bin/mailman *********** I have tried setting environment path (PYTHONPATH) by specifying either "Environment" or "EnvironmentFile" in /etc/systemd/system/mailmain3.service. None works. I had: EnvironmentFile=/opt/mailman/.systemd_vars where the contents of .systemd_vars are: PYTHONPATH=/usr/lib64/python310.zip:/usr/lib64/python3.10:/usr/lib64/python3.10/lib-dynload:/usr/lib64/python3.10/site-packages:/usr/lib/python3.10/site-packages:/opt/mailman/venv/lib64/python3.10/site-packages:/opt/mailman/venv/lib/python3.10/site-packages At this point, I am frustrated. Is there something else I can do to get mailman3 on this server? from a frustrated Onyeibo

3 years, 9 months

[MM3-users] Re: MTA setup

by Mark Sapiro

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

1 year, 7 months

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

by Ruth Ivimey-Cook

On 21/06/2020 04:52, Mark Sapiro wrote: > On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: >> ... the Body of reply, with the JSON text: >> >> { >> "start": 0, >> "total_size": 1, >> "entries": [ >> { >> "alias_domain": null, >> "description": null, >> "mail_host": "ch-bc.org.uk", >> "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", >> "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" >> } >> ], >> "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" >> } > > All these self_link references are generated from self.api.path_t which > is a reference to (in the case of 3.1) > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… > which gets the host portion from config.webservice.hostname, i.e. the > value of hostname in the webservice section of mailman.cfg, and actually > <sigh>, looking back at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > that's exactly where you said you set it to 0.0.0.0. > > Change that to greyarea-post Problem is, if I do that (which I did in the beginning), the core rest service listens on localhost / 127.0.0.1 (it obviously recognises that as the , and so cannot be connected to by anything. That is why I set it to 0.0.0.0 to begin with, and what the documentation implies (fairly strongly) that this parameter is about. IMO, the hostname parameter needs to be split up into a "what address should the rest of the world use to address me" and separately "what address(es) should I listen on". Multiple listen addresses enable multihomed hosts to get the right connectivity, too. Would that be hard? Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

6 years, 1 month

[MM3-users] OIDC (was: username)

by Jörg Schulz

The most recent version of Django-allauth has some nice changes, it's now straightforward to include oidc. Just include SOCIALACCOUNT_EMAIL_AUTHENTICATION=True ## This allows existing users to login MAILMAN_WEB_SOCIAL_AUTH = [ "allauth.socialaccount.providers.openid_connect"] in settings.py and use the Django admin to configure the socialauth.... While it is _possible_ to add things like ---- SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "mm3", "name": "TheNameThat shows up in the button", "client_id": "configuredID", "secret": "yourOIDCproviderGivesItToYou", "settings": { "server_url": "https://keycloak.wherever.com/realms/yourRealm/.well-known/openid-configura…", "token_auth_method": "client_secret_basic", }, } ] } } ---- I think it's preferable to do that within the Django Admin Gui. Does anybody dare to include this info in the documentation, or are we afraid the next django_allauth breaks things again (this time: Keycloak has been replaced by openid_connect)? -------- Weitergeleitete Nachricht -------- Betreff: Re: [MM3-users] Re: username Datum: Wed, 13 Sep 2023 07:34:35 +0000 Von: info(a)joergschulz.de An: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Hi, probably you are looking for https://django-allauth.readthedocs.io/en/latest/index.html and https://github.com/lokeish/django-all-auth-and-keycloak-integration but https://github.com/pennersr/django-allauth/commit/ab704687f438c06fd23e72bce… will be helpful once implemented. Am 12. September 2023 um 05:54 schrieb "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp <mailto:turnbull.stephen.fw@u.tsukuba.ac.jp?to=%22Stephen%20J.%20Turnbull%22%20%3Cturnbull.stephen.fw%40u.tsukuba.ac.jp%3E>>: bryan.kartzman(a)yu.edu writes: > Just to let you know, there is a maintained SAML2 plugin available > on github (https://github.com/grafana/django-saml2-auth) that I was > able to install and get to work with AZURE SSO. There are multiple ways to solve this problem. My employer wanted a host-wide solution so they chose Shibboleth. Some day I'll go out and collect the ones I can find and document them (in summary form: source site, recency of stable version, recency of maintenance, etc). Steve

2 years, 9 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Michael.Sanderson＠ubc.ca

Mark, thanks for your response. It is perhaps non-fatal, but we do have a different number of templates processed. This is from a successful run with django-allauth==0.57.0. Note the different count of templates from the “failed” processing and this one. (venv) [mailman@rubytears ~]$ mailman-web compress Compressing... done Compressed 2 block(s) from 124 template(s) for 1 context(s). Is this compression of web content that will served to clients? Compressed data would be preferred over non-compressed to decrease data volume, but non-compressed will be served if compressed isn’t available? Michael Sanderson > On Nov 7, 2023, at 7:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > [CAUTION: Non-UBC Email] > > On 11/7/23 16:26, Michael.Sanderson(a)ubc.ca wrote: >> Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get >> (venv) $ mailman-web compress >> Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html >> done >> Compressed 2 block(s) from 78 template(s) for 1 context(s). > > > I don't think this is fatal, but I have reported it at https://github.com/pennersr/django-allauth/issues/3513 > > -- > 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 michael.sanderson(a)ubc.ca

2 years, 8 months

[MM3-users] Re: Hyperkitty CPU usage

by Abhilash Raj

On Sat, Apr 27, 2019, at 9:40 AM, Alain Kohli wrote: > I have run "python manage.py rebuild_index" before, doesn't that do > clear_index as well? Apart from that, I run hyperkitty in a docker > container and didn't know fulltext_index should be persistent, so that > got deleted after every version update for sure. Which images are you using and how are you deploying them? You should persist fulltext_index, yes, and possibly logs if you need them for debugging later. Can you paste the entire error traceback? > > > On 4/26/19 10:18 PM, Mark Sapiro wrote: > > On 4/26/19 11:14 AM, Alain Kohli wrote: > >> I see loads of "A string literal cannot contain NUL (0x00) characters." > >> messages, but I haven't found missing messages in the archives yet. Not > >> sure how that could be related, though. Apart from that I don't see > >> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to > >> run and finish normally. > > > > Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 > > version? The Haystack/Whoosh search engine databases are not compatible > > between the two and "A string literal cannot contain NUL (0x00) > > characters." is the symptom. > > > > You need to run 'python manage.py clear_index' or just remove all the > > files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in > > your settings file (normally 'fulltext_index' in the same directory that > > contains your settings.py. > > > _______________________________________________ > 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)

7 years, 3 months

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

by {16/7}

Hi Odhiambo, thank you for responding. Let me first say that I am familiar with Python virtualenv, and while it may be the recommended **generic** installation procedure, there is no denying that Linux distros will offer software using their own packaging mechanisms. It would seem that moving this conversation over to the Debian community would be the best move to take then, if I continue to have issues and their packaging is to . It turns out that I left the "-l" in the hyperkitty_import command. So I re-ran it with the "-l" included. I got the same warnings about primary keys but on first glance it appears to have successfully imported the entire set of archives. Something interesting to note: if I examine the mailman-web script, it attempts to run that same python script as the user www-data. This is just as I was doing (lucky guess!), but using su instead of sudo. It seems like I've managed to complete the full process of migrating my list documented on that webpage (apart from rmlist'ing the old list). FWIW, Here's the output: $ sudo -H -u www-data /usr/share/mailman3-web/manage.py hyperkitty_import -l mylist(a)mysite.com /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox ... warnings ... Importing from mbox file /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox to mylist(a)mysite.com Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list mylist(a)mysite.com'. And here's the result of rebuilding the index. $ sudo -H -u www-data /usr/share/mailman3-web/manage.py update_index_one_list mylist(a)mysite.com ... very similar warnings ... Indexing 1497 emails

3 years, 1 month

[MM3-users] Re: Finding a user to delete them

by Allan Hansen

You log on to the member’s account using the admin password. Then one of the options is to list all the accounts. I think that the site admin (in own account) and a member (ditto) should be able to do this easily in the Postorious interface. I had expected that. Yours, Allan Hansen hansen(a)rc.org > On Mar 13, 2020, at 11:26 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 3/13/20 1:02 PM, Allan Hansen wrote: >> The Django Admin Interface is better, but it also does not give a full picture of a member, as it does not show the lists that member is a member of. >> MM2 had that feature, which was very useful. When I heard of MM3 supporting ‘users’ as opposed to ’subscribers’, I was expecting an interface that was >> ‘user’ centered, both at the user level and at the admin level. As a site admin I don’t have a way to get a comprehensive view of a user account (attached email addresses, subscribed lists, etc.). > > Hi Allan, > > What feature in MM2 allowed the function to see what lists a member was subscribed to? For some reason my mind is coming up empty. > > Your above comments is something we will be considering seriously as we continue to develop Affinity. > > -- > Please let me know if you need further assistance. > > Thank you for your business. We appreciate our clients. > Brian Carpenter > EMWD.com > > -- > EMWD's Knowledgebase: > https://clientarea.emwd.com/index.php/knowledgebase > > EMWD's Community Forums > http://discourse.emwd.com/ > > _______________________________________________ > 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, 4 months

[MM3-users] Re: Bottom line of message footer

by Mark Sapiro

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

5 years, 5 months

[MM3-users] Re: new list not working

by Christian

Mail.log Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: client=box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; from=<christian(a)naturalintelligence.us> to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP helo=<box.ecovillage.cc> Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 2:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 14:32, Christian via Mailman-users wrote: > When I ran > > mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org > > I did receive a list of subscribers for the new list I created, not > just the owner or moderator. > > Upon closer examination, another of my longtime working lists is also > not working. Similar behavior as the new list I created in that I see > the message has been archived, but not distributed to the subscribers. What do your MTA logs show? -- 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/ EOYMZXS4WPQGLDLVVWOGC67WY576665F/ This message sent to csa(a)web-analysts.net

3 years, 4 months

[MM3-users] help with startup scripts

by Piet Barber

Hello, I'm trying to get mailman3 working on Ubuntu. I'm following these instructions: https://docs.list.org/en/latest/install/virtualenv.html#setup-virtualenv I've gotten to the point where I can successfully su - to the mailman3 user, and manually start the mailman3 process with the startup command. However, when I follow the systemctl startup scripts as per the instructions at the URL above, it get stuck in the startup ... forever Starting from the command line works great! (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman start Starting Mailman's master runner Generating MTA alias maps (venv) mailman@arcus:~$ (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman status GNU Mailman is running (master pid: 47815) But when I try to start it from systemctl, it just hangs forever... root@arcus:/etc/nginx# systemctl start mailman3 If I background it, and check it out from systemctl status, I get that It's stuck in the startup mode. root@arcus:/etc/nginx# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: activating (start) since Wed 2025-08-13 23:12:05 UTC; 29s ago Process: 49024 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Tasks: 17 (limit: 4605) Memory: 878.0M (peak: 878.5M) CPU: 11.030s I've tried this with and without the forking entry in the systemctl configuration. No matter what I do, it's stuck in the ... Active: activating (start) since Wed 2025-08-13 23:13:37 UTC; 27s ago What am I missing? root@arcus:/etc/nginx# cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=syslog.target network.target postgresql.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid User=mailman Group=mailman Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop Restart=on-failure RestartSec=15 [Install] WantedBy=multi-user.target root@arcus:/# -- Piet Barber http://www.pietbarber.com/ http://blog.pietbarber.com/

11 months, 3 weeks

[MM3-users] Re: URL-lines in templates get folded

by Frank Steinberg

> Am 18.10.2022 um 18:37 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 10/18/22 06:52, Frank Steinberg wrote: >> Hi, >> I’ve added links to some templates to give owners and moderators >> shortcuts to the postorius UI for moderation tasks, e.g., I’ve added >> https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> >> Unfortunately those lines seem to exceed a certain limit and get >> folded, so that they appear as, e.g. >> https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> >> messages >> (or similar) and are not directly useful. > > How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? I am using the docker containers and have been putting files into the directory mapped to var/templates/site/. > Also are those lines of the form > > https://... <https://...> I am sorry, my Mail program changed the encoding here. In fact the template files just contain the plain URL. No blanks no angle brackets. Just one URL containing the $list_id variable. > what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. > > Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? The folding appears in the raw message sent by Mailman and put into the users INBOX. I thought there could be a kind of filter in Mailmans mailout processing that cares for line breaks in order to not exceed approx. 75 chars per line? I will do some more testing tomorrow (european time).

3 years, 9 months

[MM3-users] External MTA incoming mail: configuration

by Roland Giesler

I have mailman set up to send mail via an external MTA, which is supported by mailman and described in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Specifically it says: |lmtp_host|and|lmtp_port|are parameters which are used by Mailman, but also will be passed to the MTA to identify the Mailman host. The “same host” case is special; some MTAs (including Postfix) do not recognize “localhost”, and need the numerical IP address. If they are on different hosts,|lmtp_host|should be set to the domain name or IP address of the Mailman host.|lmtp_port|is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using it. However, there is a practical problem with LMTP (to receive incoming email) which is as follows: The setup in mailman.cfg: lmtp_host: lists.fast.za.net lmtp_port: 8024 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: virtual_transport=lmtp:[127.0.0.1]:10025 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. So what is meant by "but also will be passed to the MTA to identify the Mailman host" in the docs? 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? This is quite fuzzt to me at this stage. Could someone help me with some clarity please?

2 years

[MM3-users] Re: Google auth issue redirect_uri_mismatch

by Abhilash Raj

On Sun, Sep 8, 2019, at 2:12 PM, Ugnius S wrote: > Hi. > New question about configuration, maybe somebody has experience and know > what I should change it. I have tried to implement Google authorisation. > I have created Google credentials keys and successfully added using Django > admin page. > I use UWSGI proxy for apache setup like "ProxyPass / http://127.0.0.1:8002", > UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects to > internal) What happens when I try Google auth... > If I set Authorised redirect URIs: > http://lists.example.com/accounts/google/login/callback/ , Google gives me > error 400 Error: redirect_uri_mismatch and requests for: > http://127.0.0.1:8002/accounts/google/login/callback/ > If I set that requested address to Google, then Google authorises me, > but and after authorisation redirects to > http://127.0.0.1:8002/accounts/google....../.... (very long line) Of > course this internal address does not open, but... > If I just manually replace part of address just: http://127.0.0.1:8002 > replace to https://lists.example.com/.../...(long line) this makes me get > in as authorised user to the page. > How to make django to send external request to Google? Because > Google should not point back to internal address... This seems simple, but > I do not find what I should change in the configuration: Apache or Django > or uwsgi.ini I hope anybody of You have experience and made it to run. You need to set this in nginx under your location directive, where you setup your proxy_pass or uwsgi_pass proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; Something similar should exist for Apache. > > Kind regards > Ugnius > _______________________________________________ > 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, 10 months

[MM3-users] Re: message duplication and an NNTP related error

by Laurens Kils-Hütten

Am Tue, Feb 24, 2026 at 01:16:45PM -0800 schrieb Mark Sapiro: > On 2/24/26 09:23, Laurens Kils-Hütten wrote: > > > > I've used the debian packages: > > > > apt install mailman3-full mailman3-web > > Then this may be a Debian issue and should be reported there in any case. > See <https://wiki.list.org/x/12812344>. I will, once I convinced it's really a bug. Right now I'm thinking it's a misconfiguration on inn2's side. From scrutinising the message headers this is what happens: mailman sends the message to the newsserver where it get's injected properly receiving an Injection-Information: header field. Then however this new message is sent back to mailman. Now there's a duplicate with identical message ID. Mailman then sends it back to inn2 which refuses to take it and the python nntp client throws an error, thus preventing an endless loop. Why inn2 even sends the message back to mailman I can't tell right now. These are the relevant snippets from my inn2 setup: # this is from /etc/news/news2mail.cf # no surprises, and it basically works. News from the grenzland.test # group is forwarded to the proper list address test-grenzland-club test(a)grenzland.club # this is in /etc/news/newsfeeds news2mail!:!*:Ac,Tc,Wn*:/usr/lib/news/bin/news2mail test-grenzland-club/grenzland.club:!*,grenzland.test:Ap,Tm:news2mail! # this last line should do two things: forward messages from the # test(a)grenzland.club list to the grenzland.test newsgroup, # AND don't send any messages back which have grenzland.club # in their Path header. This last bit seems to fail however, # and I fail to spot the error. I'll ask about this in the inn2 places I known of. Cheers, lkh -- Laurens Kils-Hütten https://lkh.sdf-eu.org

5 months, 1 week

[MM3-users] Mailman not able to process "big" requests

by Jonas Felber

Hi, We migrated from mailman2 to mailman3 a week ago. Since then we are unable to send messages the our students through the mailing list. Here are some symptoms: 1. I go to mass subscribe and subscribe 400 emails 2. I click subscribe, the browser (in my case safari) tries to load the page for a few seconds 3. The request times out 4. Once the service becomes responsible again, I see that only part of my emails got subscribed (~50 in this case). For me this really looks like the emails are sent on the "web-thread" that gets killed once the request times out. Looking at this https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p… <https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p…> seems to confirm my suspicions. Some quick overview of our infrastructure: The TCP endpoints are: browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes-ingress -> nginx in mailman -> mailman We mitigated the issue by giving it more CPU power and increasing the timeouts in one of the nginx endpoints. We also have a problem with sending out emails to "large" (>50) groups, as they seem to not getting sent out at all. Do you have any idea what the problem here could be? We would be really glad if you can help us getting our mailman up and running, as I currently have to send emails out by "hand". I will happily provide you with more details about our configuration, just let me know what you need. Kind regards, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch <mailto:jonas.felber@vis.ethz.ch>> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch <https://www.vis.ethz.ch/>

8 years, 3 months

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Mark Sapiro

On 2/15/21 2:38 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 13/2/21 20:00, Mark Sapiro wrote: >> Also note that the translations on weblate only affect strings in the >> core code. The Mailman core templates are not currently translated in >> weblate and there are currently no Spanish language templates. One would >> need to create Spanish translations of all the templates in >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> >> and submit a merge request to add them to a mailman/templates/es/ >> directory. > > I downladed the templates and I'm beginning the translation process, but > I have a question. What language map has to be used? In my S.O. it's > ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before > having to do a remapping of the files after... They should be encoded as UTF-8. > It comes to my attention that three files have 0 bytes. The 0-byte files can either be left out of templates/es or put in as empty files. They are things for templates which are empty by default. Also, help.txt is unused and doesn't need to be translated. At one time it was intended to be the template for the response to the email `help` command, but it is not used for that purpose. Finally, although I said previously that the translated templates should be submitted as a merge request, that can still be done, but is not necessary. They can be translated in weblate. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and <https://gitlab.com/mailman/mailman/-/issues/825>. -- 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: Set domain inactive / archive import from other domain.

by Johannes Winter

Am Sat, 15 Sep 2018 09:31:53 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 09/15/2018 07:15 AM, Johannes Winter wrote: > > > > we've migrated a list from another domain and would like to keep the > > archives. Hyperkitty doesn't recognize the emails in the mbox > > archive during import due to the other domain name. > > > I don't understand the problem. I just ran a test where I imported a > mbox containing 3 messages which were not even list posts and in > which I had changed all the domain names to 'example.com'. I.e., in > the mbox I imported, the headers containing domain names looked like > > From root(a)example.com Sun Aug 26 09:12:06 2018 > Return-Path: <root(a)example.com> > Delivered-To: root(a)example.com > Received: by example.com (Postfix, from userid 0) > From: Anacron <root(a)example.com> > To: root(a)example.com > Message-Id: <20180826161158.F154D34010C(a)example.com> > X-msapiro-MailScanner-From: root(a)example.com > > and the 3 messages were all added to the archive. > > Why do you think the domain name is an issue? Perhaps the issue is > there is already one or more messages in the archive and the messages > you are importing are older. If you don't specify --since to > hyperkitty_import it won't import messages older than the newest > message in the existing archive. Thanks a lot for your excellent and fast support! That was the problem. Maybe it would be wise to include that into the help of the hyperkitty_import command? Although this command successfully imported 3/4 of the huge (1.7GB) mbox, it stumbled upon an error after some minutes: https://gitlab.com/mailman/hyperkitty/issues/200 -- Johannes Winter matrix: @yova:matrix.allmende.io

7 years, 10 months

[MM3-users] Re: [Mailman-Users] mailman 3 and freeipa

by Abhilash Raj

On Mon, Mar 18, 2019, at 12:16 AM, Stephen J. Turnbull wrote: > Crossposting and redirecting replies to mailman-users(a)mailman3.org. > > Steven Jones writes: > > > I cant find anything on this so far but can Mailman3's webui use > > freeipa as the authentication mechanism? > > Hi Steve, > > I don't have a complete answer offhand (and right now I'm just > reducing my inbox so a single google search is as much as I can do), > but searching for "freeipa django" indicates that there are > "connectors" for Django and FreeIPA. The nicest option would be a > plugin for Django's socialauth application. > > If that doesn't seem to exist, perhaps you can just add a FreeIPA > application to the Django configuration. You would need to add it to > both Postorius and HyperKitty configurations. Here is a list of all the providers Django-allauth(and hence us) support[1]. You can definitely add more providers and if Django-allauth isn't ready to merge that, you could create a completely separate python package that providers that functionality. If you need examples, here is a custom provider we have in our source code to authenticate using Fedora's auth management system[2]. [1]: https://django-allauth.readthedocs.io/en/latest/providers.html [2]: https://gitlab.com/mailman/django-mailman3/tree/master/django_mailman3/lib/… > > Steve > > > -- > Associate Professor Division of Policy and Planning Science > http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information > Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba > Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN > _______________________________________________ > 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)

7 years, 4 months

[MM3-users] Re: list footer questions

by Kelly Close

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

6 years, 1 month

[MM3-users] Re: Emails about moderation are sent to list owners, want them sent to moderators instead

by Mark Sapiro

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

4 years, 1 month

[MM3-users] Re: SPF check fails for lists subdomain

by Odhiambo Washington

On Thu, Jan 5, 2023 at 10:56 AM Jan Eden via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > I was misreading your DNS and now I am as puzzled as you about the > failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? > > - Jan > Might you be willing to use proven tools instead of trying so hard to understand the myth? I use https://easydmarc.com/tools#spf-tools It allows me to generate, lookup, test SPF, DKIM, DMARC, etc. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 6 months

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

by Stephen Turnbull

Sorry about breaking the thread, institution system "upgrade" to O365 broke my world so I'm cutting and pasting into Outlook. comprepair_jimberg--- via Mailman-users writes: > Can you setup Mailman3 for me? I have done apt install > mailman3-full but I have no clue whaat I am doing. You should seriously consider either going for a managed host or hiring somebody. Unfortunately, you're asking a bit much for volunteer help. The problem is that Debian uses the FHS layout with the system Python,while we core devs recommend and use a self-contained "virtual environment" with an /opt-style layout. Debian also applies patches that may or may not be backports from more recent versions. We just don't know what's going to go wrong on a distro install. Mailman also has dependencies on several system components (webserver, mailserver, WSGI implementation, SQL database, text indexer) which each come in multiple flavors, but the range of combinations we're familiar with is limited and may not even include the Debian default list. Once you have a working Mailman installation we'll be happy to help you tune it, though. (And you don't need core devs for that anyway, other Mailman site admins who hang out here can often help as well as well as we can.) We are much more likely to have knowledge and experience to help with a virtual environment install as described in https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Here's an alternative, "from the ground up" step by step description of a specific combination of components: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I think it should work just fine for Debian 11 as well. The author of "Mailman3 On Debian10" was a hosting and mailing list service provider, and used this recipe for all his hosts. Regards, Steve

3 years, 4 months

[MM3-users] Re: spf/dkim/dmarc

by Christian

Using https://www.spf-record.com/ I have checked my SPF records which are reported as 'SPF check passed'. My DKIM also passes various test suites. Yet, Google is still rejecting mailman messages to any and all gmail users. I have even filled out their short form for delisting at https://support.google.com/mail/contact/bulk_send_new all to no avail. Example of block logfile message: May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: to=<billb6951(a)gmail.com>, relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: [192.46.218.224]. To best protect our users from spam and 550-5.7.26 phishing, the message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - gsmtp (in reply to end of DATA command)) Could the hard fail policy be implicated in the gmail rejection? Other than readdressing my server, is there anything else I can do? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, May 17, 2023 11:50 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: spf/dkim/dmarc On 5/17/23 07:20, Odhiambo Washington wrote: > > You can only have 1 SPF record. For a domain. But as Jeremy Stanley noted, mail.ccalternatives.org and lists.ccalternatives.org are different domains and it is fine for each to have its own spf record. -- 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/ WAUVS6WWYOYQBJGIDP3HK6L3NHM4RGHF/ This message sent to csa(a)web-analysts.net

3 years, 2 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by David Newman

On Jan 25, 2022, at 06:56, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: >> Or is there a better MLM for simple use cases? I used Majordomo >> back in the 90s and was happy to get onto Mailman from >> that. Something similar to Mailman 2.1 in features/functionality. > > It's been years since we had an answer to that question. Mark might > have more to say, but the last time we were challenged on this, the > rival was Sympa, and the conclusion I came to was that the use cases > are different. I prototyped Sympa and mlmmj along with MM3, and found the latter was the closest match to MM2’s feature set. It also provided some features not available with the others, at least not available by default. > > Depending on your Linux distro, and your attitude to risk, Python 2 > plus Mailman 2 in a container, VM, or even a dedicated host in the DMZ > or outside the firewall might be a reasonable solution. Yes, this is possible. The IETF, the body that defines Internet technical standards, is still on MM2. I’m with them; given my druthers I’d run MM2 forever because it Just Works. Then again, I put a high priority on keeping the base OS and applications patched against current security vulnerabilities. That’s getting harder to do with MM2. Debian and FreeBSD have deprecated Python 2. MM2 still has maintenance releases but no new development. MM2 also has some archaic design decisions such as sending user passwords in plaintext email. Like it or not, MM3 and related components are current, and currently maintained. I wasn’t crazy about the learning curve to get MM3 working, but I pressed on because it will provide a platform I can keep running much farther into the future. dn

4 years, 6 months

[MM3-users] Re: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Hi Mark, As you have mentioned about implementation of "Auto discard after max_days_to_hold" in a next release. How do I install that release? I have installed mailman3 using pip in virtual environment and whenever I try to upgrade the release using pip install -U, it gives package already compiled and up to date. My Mailman version is as follows. Mailman version: GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.9 Rocky Linux 9.5 Regards, Hitachi. On Thu, May 1, 2025 at 12:51 PM Hitashi mancho <huhamails(a)gmail.com> wrote: > Thank you so much, Mark and Stephen, for the quick action and response. > Waiting for the next release. > > On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 4/28/25 10:55, Mark Sapiro wrote: >> > >> > `mailman import21` will import the setting, but per the above comment, >> > it doesn't yet work. The setting exists and is exposed in REST, but it >> > appears it is not actually implemented. >> >> >> This is now implemented for the next release. See >> https://gitlab.com/mailman/mailman/-/issues/1215 and >> https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman >> core and https://gitlab.com/mailman/postorius/-/issues/628 and >> https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. >> >> -- >> 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 >> >

10 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Guillermo Hernandez (Oldno7)

On 15/5/21 0:29, Odhiambo Washington wrote: > > > On Sat, May 15, 2021 at 1:08 AM Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org>> wrote: > > > On 14/5/21 23:52, Odhiambo Washington wrote: > >> Which OS are you using? > > FreeBSD. > > > > > As Mark pointed, you probably have installed the textproc/sassc > port (or > package). I'ts an equivalent for sass. Do the config as advised. > > I have mailman3 installed and running smoothly in a pair of 12.2 > RELEASE > FBSD servers. > > There is a thread about this installations that can help: > https://forums.freebsd.org/threads/mailman-3.61050/post-488128 > <https://forums.freebsd.org/threads/mailman-3.61050/post-488128> > > > > I will look into this. I know FreeBSD has a mailam3 port, The mailman3 port runs, but aaaaaall the other apps needed, just no. Following the FreeBSD ports route ended in a failure. In the previous post on the link I explained all the failed tries. > but I have mailman2 in production and the port installs to > /usr/local/mailman I had mailman2 indeed. And migrated to mailman3 all my lists (17 in one server, 2 in other). One of them with more than 8000 suscribers. I know it's not much, but in that thread you can find example config files than you can compare. They are working. > so I have to be careful - install mailman3 in /opt, then plan on > hosing mailan2 and moving mailman3 to it's place after migration. > It's not simple. Yes, I know. I did. Best luck. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 2 months

[MM3-users] Re: Hyperkitty

by Odhiambo Washington

On Mon, Jan 30, 2023 at 10:58 PM Onyeibo <onyeibo(a)schemefusion.com> wrote: > On Mon, 30 Jan 2023 16:01:16 +0300 > Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > So an array?? > > > These are defaults. I have also added my IPs. Nothing is happening. > > > > > Perhaps I did something wrong here. Any documentation on this? > > > > > > > https://mailman-web.readthedocs.io/en/latest/settings.ht > > > > > > My instance is not archiving. > > > > Things to check: > > 1. Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!) > > the same as api_key in mailman-hyperkitty.cf (unquoted here!)? > > I have double-checked this. Yes ... I got it right > > > 2. Your MM3 log files - do they say anything? > > > Nothing! No new errors. It is very strange and frustrating > Simply put: Mailman3 uses the following components for archiving: Archiver: responsible for storing messages and metadata, such as message header information, in the archive database. Archiver API: provides an interface for accessing the archived messages. Archiver REST API: allows access to the archives through a RESTful interface. To configure Mailman3 archiving, you can: Choose an archive backend, such as the built-in HyperKitty backend, or a third-party archive backend. Set up the archive backend, including database connection details and other required configurations. Configure Mailman3 to use the chosen archive backend. This typically involves updating the Mailman3 configuration file and specifying the backend's configuration information. You can find more information about Mailman3 archiving and its configuration in the Mailman3 documentation. Now you need to go over the archiver configuration/enablement with a toothcomb :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 6 months

[MM3-users] Re: Subscription confirmation email

by Mark Sapiro

On 3/14/26 07:19, Eric Broens via Mailman-users wrote: > While doing some tests I subscribed to a mailinglist by sending an email to > <list>-join@<domain> > > Mailman correctly emailed the confirmation request, and the mail was > accepted by my ISP. > > For some reason the confirmation mail did not arrive in my mailbox nor in my > spam folder, it seems to have been silently dropped. This is a problem, but we can't help with that. Only your ISP knows why it dropped it. > A day later, I again sent a subscription request to <list>-join@<domain>, > and I received a mail from <list>-bounces@<domain> with subject "The results > of your email commands" saying that I have a pending subscription for that > mailinglist. > > However, no confirmation link is included, nor instructions to visit the > website to confirm the subscription. > > Am I missing something in the configuration? No. The original request is pending and needs to be confirmed or discarded or time out. If you are a list admin you can go to Subscription requests -> Pending Confirmation and discard the pending request. The time out is configured as pending_request_life with a default of 3 days. > I would expect that a confirmation request is mailed again to the > subscriber. Most subscribers don't use the web interface to manage their > subscriptions. I see your concern. Currently the frustrated subscriber whose original confirmation request is lost has to contact the list owner and may not even understand that need. You could submit an RFE at <https://gitlab.com/mailman/mailman/-/issues/new> to request that the pending request response include the confirmation link. -- 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: Things I miss about mailman2

by Quanah Gibson-Mount

Hi Mark, --On Tuesday, March 17, 2020 1:43 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > 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. Ok great, thank you!. >> 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'. I do not see any such option. After clicking on the header the only options available at the bottom are: Accept, Reject, Discard, Show Source, Show Header There are zero drop downs anywhere. > This was not "removed". It just hasn't been implemented in MM 3 yet. So in terms of available functionality that was present in MM2, it was removed. It may need to be re-implemented, but this was a core feature that was present in the prior version that is no longer available. --Quasnah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 years, 4 months

[MM3-users] Re: disabled users

by Mark Sapiro

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

2 years, 9 months

Search results for query "dO"