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

[MM3-users] Occasionally "The content of this message was lost."

by Frank Richter

Hello, occasionally we face the problem "The content of this message was lost." when handling a message on hold. We use the mailman3 packages on Debian 12: 3.3.8-2~deb12u2 GNU Mailman 3.3.8 (Tom Sawyer) Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] with postgresql, exim and Apache httpd on the same machine. To get closer to this problem we made 2 changes: /usr/lib/python3/dist-packages/mailman/app/moderator.py def _lost_message(mlist, subject, sender, message_id): # Create a substitute for a message not found in the message store. text = _("""\ The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. """) + # Don’t send an empty message to all members in case this event occurs. + # raise an exception instead: + raise Exception("_lost_message",subject, sender, message_id) /usr/lib/python3/dist-packages/mailman/runners/task.py def _evict_pendings(self): … messages = getUtility(IMessageStore) for msg in messages.messages: # msg can be None if file is already removed. if msg is not None: mid = msg.get('message-id') if mid not in mids: messages.delete_message(mid) # 2024-12-11 fri: Debug inserted + tlog.debug('Task runner deleted message %s', mid) count += 1 tlog.info('Task runner deleted %d orphaned messages', count) So let’s see what happens: A message sent to one list is set on hold: exim mainlog: 2025-01-28 14:10:23 1tclMF-00H6cW-1s <= user(a)s2024.tu-chemnitz.de H=vittal.hrz.tu-chemnitz.de (mail.tu-chemnitz.de) [2001:638:911:b01:134:109:133:32] P=esmtps X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no K S=9058 id=2f972b-6798d700-9f-5b841500@14907502 2025-01-28 14:10:23 1tclMF-00H6cW-1s => fsr-hsw(a)lists.tu-chemnitz.de R=lists_mailman T=mailman3_transport H=localhost [::1] C="250 Ok" 2025-01-28 14:10:23 1tclMF-00H6cW-1s Completed vette.log Jan 28 14:10:24 2025 (2602) HOLD: fsr-hsw(a)lists.tu-chemnitz.de post from user(a)s2024.tu-chemnitz.de held, message-id=<2f972b-6798d700-9f-5b841500@14907502>: The message is not from a list member A task runner deleted the message 5 seconds later: task.log Jan 28 14:10:29 2025 (2609) Task runner deleted message <2f972b-6798d700-9f-5b841500@14907502> Jan 28 14:10:29 2025 (2609) Task runner deleted 1 orphaned messages Later an owner/moderator want to do a moderation action: mailman.log: 2025-01-28 17:40:54 [FALCON] [ERROR] POST /3.1/lists/fsr-hsw(a)lists.tu-chemnitz.de/held/7544 => Traceback (most recent call last): File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 155, in on_post handle_message(self._mlist, request_id, **arguments) File "/usr/lib/python3/dist-packages/mailman/app/moderator.py", line 144, in handle_message msg = _lost_message(mlist, subject, sender, message_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/app/moderator.py", line 104, in _lost_message raise Exception("_lost_message",subject, sender, message_id) Exception: ('_lost_message', 'Re: [Fsr-hsw] ...', 'user(a)s2024.tu-chemnitz.de', '<2f972b-6798d700-9f-5b841500@14907502>') Do you have any suggestions what we can do to find the reason, why the task runner deletes the message? Or any other hints … Thanks and kind regards Frank -- Frank Richter, Chemnitz University of Technology, Germany

7 months, 2 weeks

[MM3-users] Re: How to get rid of footer (Mailman3)

by Mark Sapiro

On 2/11/20 11:31 PM, tarmokumar(a)gmail.com wrote: > Hi, I have read multiple posts in this forum that you should be able to get rid of the footer completely but I am unable to. > I have tried: > - adding the footer template to a list and not adding any "Data" to it. Result was a attachment with some "dfgdfgdfgdfg" text in it. Did you add this via Postorius. If so, it would seem to be a Postorius issue. > - adding/creating a blank "list:member:generic:footer" document to /var/templates/site/en, var/templates/lists/LIST.ID/en/ and var/templates/domains/DOMAIN/en/. Result is that the sent e-mail still has the original unsubscribe text in the footer (as an attachment) Did you name the file list:member:generic:footer.txt (with the .txt extension)? Putting a zero-length file of that name in any of those places should work. > - removing all the files from /mailman/src/mailman/templates/en, still no change If you restarted Mailman after doing this, this indicates something (Postorius?) may have set a URI for this template. What do you get from curl -urestadmin:restpass \ http://localhost:8001/3.1/lists/LIST.ID/uris -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Running customized version of Mailman 3

by tlhackque

On 28-Feb-20 16:46, Alan Kelm wrote: > Since 2005, our organization has been running a customized version of > Mailman 2 with extensions that meet our particular needs. The main > novelty is support for /fixed subscription lists/, in which the list > members are predetermined (corresponding to a "committee"). Fixed list > subscribers are not offered the opportunity to unsubscribe, nor can > others add themselves to the list. A further enhancement is /hybrid > lists/ which, for example, have both a fixed and opt-in part. (This is > implemented as a fixed list residing within an opt-in one in a way which > is transparent to users). Our customizations consist of code > adjustments (patches) to 23 files. > > We are considering moving to Mailman 3 and would like to do this in a > way which makes it possible to periodically upgrade our installation to > the newest Mailman version, without clobbering our customizations. > Thus, I do not think that installing via "pip" is the right approach for > us. While I'm relatively new to git and GitLab, they seem to be ideally > suited to this situation. If I understand the developer documentation > correctly, I start out by creating a "fork" and can later "fetch" > changes from the master branch and "rebase" to bring them into our branch. > > I would welcome comments on what we are doing. I also wonder whether > others might be interested in support for "fixed lists", if they are > done in a way which can be "contributed" back into Mailman. > > I extend our "thank you" to the developers of Mailman who have provided > the robust system which has served us well for 15 years and provides the > possibility to extend this into the future. > > -Alan > FWIW: When I had similar requirements (MM2), I found it most convenient to populate the "fixed" list with a distribution list name. The distribution list was sourced from an LDAP group. That allowed the distribution to be populated based on job title, reporting relationship, committee membership - whatever. On the Mailman side, it's only one member (the distribution list) that had special treatment. Opt-in would be moderator approval, as was unsubscribe. But the moderator only had to remember the one "can't unsubscribe" name. That, or a variant might work for you - and probably can be done modifying fewer files... In minimal form, if you don't want to rely on a human, it seems like the minimal implementation is a "can't unsubscribe" bit for users and an admin interface to set it. You could also cause that user to have a different "language" - e.g. en-ZZ; then adjust the templates for that "language" to remove references to "unsubscribe". That's not functionally necessary - but prettier.

5 years, 6 months

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

by Andy Matthews

I'm testing locally to try and support additional domains. I can add new mailing lists with a domain: announce-123(a)mydomain.com I can't add a new mailing list with an alternate domain: announce-123(a)testing.com Following the documentation for domains I'm able to successfully add the new domain (locally) with the following steps: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… 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> But then when I run a cURL command (from the mailman server) to add a list with that new domain I get an error: $ curl -k -u restadmin:restpass -X POST -H "Content-Type: application/json" --data '{"fqdn_listname": "new-list(a)testing.com"}' https://0.0.0.0:8001/3.1/lists {"title": "400 Bad Request", "description": "Domain does not exist: testing.com"} Am I doing something wrong, or missing a step? If not, how do I add support for additional domains such that I can provide mailing list support for that domain?

11 months

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

by Stephen J. Turnbull

Hitashi mancho via Mailman-users writes: > I have migrated around 300 mailing lists from Mailman 2 to Mailman > 3. In most of the mailing lists we have configured > "max_days_to_hold" to 2. It was working fine in Mailman 2. However, > it is not working in Mailman 3. This doesn't seem to be exposed in Postorius. It's not all that old in Mailman 3 (April 2020) so it's possible that it is not moved from Mailman 2 to Mailman 3 by the migration scripts. You can use "mailman withlist" to access that variable: Use "mailman withlist -l LIST(a)DOMAIN.TLD", then at the prompt: >>> m.max_days_to_hold to examine the value for LIST(a)DOMAIN.TLD. To do a mass change, something like for ml in `mailman lists`; do mailman withlist -l $ml -r fix_mdth done where you put in Mailman's bin directory the file 'fix_mdth.py' containing def fix_mdth(ml): ml.max_days_to_hold = 2 commit() Of course if there are list where you want a longer or indefinite hold you'll need to change those back, since this approach changes all of them. You can get more information with "mailman withlist --detail". -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 2 weeks

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/7/21 11:27 PM, Marcus Granath wrote: > It seems like the version used is: Postorius Version 1.1.2 Current Postorius is 1.3.4. If you can't upgrade, someone with shell access to the server can do this with `mailman shell` > What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". > > But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). > Or can I use some other API (then the web-page) to do that kind of operation? ;-) Just add the no-reply(a)abc.com address as a member and set its delivery status to disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Timeouts

by tlhackque

On 25-Apr-21 18:08, Mark Sapiro wrote: > On 4/25/21 2:20 PM, Andrew Hodgson wrote: >> Hi, >> >> Hyperkitty 1.3.4. >> >> I am trying to download a complete list mbox by going to all threads view >> and using the download option. I have tried a couple of tools (Gunzip and >> Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. >> >> Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… > Depending in the web server configuration, timeouts can occur when > downloading large archive mboxes. instead of downloading the entire mbox > with > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, > do it in pieces by adjusting start and end. e.g. > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > > Although, I don't think timing out is the issue, and I'm not sure what > is, but I think it has something to do with messages in the archive. If > I try to get the 3 pieces as above, the first piece with > start=2008-02-19&end=2012-12-31 works but the others don't and even the > smaller > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > fails the same way. > > If I try to get 2013 month by month, all work except December which > gives me an internal server error. What's the traceback from that error. > The described timeouts are something that hyperkitty ought to be able to avoid. For apache, the timeout is idle time between blocks of output. Hyperkitty can avoid this by generating the archive in segments (based on size, or elapsed time), flushing its output buffer, generating a multi-file archive, and/or using Transfer-Encoding: chunked (chunked doesn't work for http/2). It ought to be able to break the work into blocks of "n" messages & do something to generate output. Besides avoiding timeouts, working in segments allows the GUI to display meaningful progress (e.g. if you're loading with XMLHttpRequest, "onprogress") It really oughtn't be up to the user to break up the request. Until then: the apache directive is "TimeOut" (or "ProxyTimeout"), with a default value of 60 (seconds). It's a server config/virtual host parameter, so if you're running in an environment where you only have .htaccess, you need admin help or you're out of luck. Other webservers (especially those with accelerators) may have more granular timeouts.

4 years, 4 months

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

by Ryan McClung

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

7 years, 1 month

[MM3-users] Re: Updating from Ubuntu-20.04 LTE installation

by Abhilash Raj

On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote: > On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > > running MM 3.2.2 (and python 3.8.2). > > > > Do you have any advise, how to upgrade from there to your current > > version? I know this might be a bit dangerous, but with today's VMs the > > risk is much less than it used to be: > > > It shouldn't be difficult, but I can't give you details because I don't > know exactly how the Debian/Ubuntu package installs things. Also I don't > know whether "current version" refers to the 3.3.1 release or the head > of the https://gitlab.com/mailman/mailman master branch. > > > > Do you think it would be possible, just to replace the code and library > > parts, keeping the database and config files as is? > > > Yes. It should be fairly straightforward. You first need to find where > the Mailman Core package is. You should be able to just replace the > contents of the `mailman` package directory with ours. You may be able > to do this via pip > > pip install --upgrade mailman > > globally or within Mailman's virtualenv if it is installed in a virtualenv. This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages). A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in `/etc/mailman3/` and Mailman Core installed anywhere should just pick that up without any special work. Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume). > However, there are caveats. There are Debian patches at > <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` > patch replaces importlib_resources with importlib.resources because > importlib_resources is not available in Debian. Most of the patches > apply to tests, and for the actual working code, we fixed this > differently as of Mailman 3.3.1, so I don't think you need the Debian > patches. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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, 3 months

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

by Stephen J. Turnbull

tlhackque writes: > No. It's not an address. "local part" has to do with an address. in a > Message-ID, It's syntactically a local-part or other stuff. RFC 5322: 4.5.4. Obsolete Identification Fields The obsolete "In-Reply-To:" and "References:" fields differ from the current syntax in that they allow phrase (words or quoted strings) to appear. The obsolete forms of the left and right sides of msg-id allow interspersed CFWS, making them syntactically identical to local-part and domain, respectively. > It's in "id-left", which is a supposed to be something generated by the > host that makes the message unique within the namespace defined by > "id-right". Right, those are the *semantics recommended to implementers*, for the reasons which you summarize accurately. But a validating parser doesn't care about that. > Treat the whole thing as an opaque string. Nothing else is safe. s/else// and I'll agree with you. But safety is not an issue in threading (except for DoS if the procedure might be non-terminating; I suppose you could argue DoS if a user misses an out-of-order mail from their boss and gets fired :-). > Yes, but did you fix the References header to match? Of course I did. :-) That was long before I was a Mailman developer and started reading the RFCs, also of course. > Yes, but you brought up the news RFCs, IIRC in saying that they defined > threading. Actually you brought up the news RFCs. I was wondering why. I guess it was to argue (implicitly) that there's a bug in the 2822 (and 5322) spec, and that 5537's solution tends to muck things up? > My quote was verbatim. 5537 does say you must trim. The point is that > the news rfcs may have introduced References, but they have different > obstacles to reconstructing threading. I don't think that's right, because mail suffers from the same line length restriction, with no exception for References. Mail just has strictly more specification bugs. :-( > I haven't looked at that. Given the trimming in 3.4.4 of 5337, I don't > see how this can be produce the whole thread, unless you are guaranteed > to have the complete thread to fill the gaps. It can't because you aren't. But it seems unlikely that anybody is producing msg-ids longer than 74 characters, so 998/(74+1) - 1 = 12 is a long enough gap that you probably don't care that they're the same thread. At least not in any forum I participate in! It's true that an MUA that doesn't produce either References or In-Reply-To will necessarily break threading, and that "enough" missing messages can do so. But both are pretty uncommon in my experience. Even AppleMail gets those right AFAICT. ;-) > Plus, you can lose messages for strange reasons: The moderator > deleted one for inappropriate content. A message was copied to the > list and the poster. The response to the list is lost. But a > reply from the poster happens later. So the response in question > is never seen by the server, though the reference is. Life is hard > :-) > Sure, but Jamie's algorithm *will get that right*. What remains is a UI question: missing message placeholder, to display or not to display? > Heuristics are fine. Guaranteeing that the resulting algorithm > terminates is important. But real life doesn't get you to "enough > messages" 100% of the time. 100% isn't necessary. If the thread is sufficiently broken that Jamie's msd-id-based procedure doesn't work, his full algorithm falls back to your idea of collecting the singletons by subject and sorting. (He doesn't specify the ordering criteria, rather what objects (= subthreads of the same parent) are to be compared. Your suggestion of date seems most appropriate for the leftovers.) > > > See my other post. The left and right halves can, besides being atoms, > > > be non-folding quotes or literals. So you have to handle that. > > > > Of course, but that's just a SMOP. The harder problem is figuring out > > what to do about non-conforming input. > And, as I've noted: lost input. Lost input does not prevent thread reconstruction as long as (1) all messages have a Message-ID, (2) "enough" messages have a non-empty References containing "enough" msg-ids, (3) those References do not misorder the msg-ids or introduce msg-ids corresponding to messages not in the thread. It should be obvious why I don't want to define "enough" (except in terms like "enough means Jamie's algorithm can reconstruct the thread" ;-), but in particular losing *one* message will certainly not prevent reconstruction. > When they don't, trying to guess at the semantics of an opaque ID will > seem to work for a while. But it amounts to the halting problem. There > are lots of variants of "generate a globally unique ID with an '@' in > the middle". I may have created a new one today :-) The problem I'm trying to address with the "stripping" is incorrect copying of msg-ids by MUAs that try to parse them, as we saw here. Apparently the bug was in Mailman itself, so it's not required, I guess. > Yes. But if they're well-formed, the <> are there, so stripping them > only saves a couple of bytes. > > If they're not, all bets are off. <two<three(a)example.net> - stripping > the outer <>s doesn't help. > > <"two<three"@example.net> is a valid message-Id, > and distinct from <"twothree"@example.net. Sure. Is it likely? > <twothree(a)example.net> distinct from <"twothree"@example.net>? > (unnecessary quoting, or a distinct message-ID) If you treat it as > opaque, you don't care. Take the whole thing, <@> included, as given > and look for it in the other fields. The most you might do is remove > quotes (and escapes) and use the left and right parts as your key. Which is basically what my stripping and cleaning procedure would do. The question is "does it help or hurt, on net?" If there was a widely distributed MUA out there that doubled the delimiters, it would help. Since it was Mailman doing that, it's a bad idea. > You could also fingerprint the user agent (e.g. by the order of headers, > format of message-ID), and correct for its bugs. But I'm inclined to > report client bugs and get them fixed. Meantime, their messages are > unthreaded (but not lost). It's just not worth working around other > people's bugs - there are better uses for your time. That's not my experience. See Reply-To munging. Depends on the bug, of course, but all too often people think it's our job to help them deal with bad MUA design. > Yes. A message ID should exist. These days I think all MTAs will assign > one if the client doesn't. > What I tried to say was that there will be times where you can't figure > out where to put a message into the thread graph (or forest). Because it > references message that you can't find, or it doesn't have a references > or reply-to, or those fields are corrupt. None of those prevent you from threading that message. The only reasons you won't be able to thread a message at all are when no other available message references it (eg, if several MUAs in a row supply In-Reply-To but not References, and the middle messages are missing or their identification fields are corrupt), and when there are References that have conflicting opinions on where that message belongs. Of course if a message lacks References and In-Reply-To it will be identified as a thread root (unless some descendent manually corrects References ;-). Even then it could be grafted into the tree more or less correctly using your sort on subject and date procedure. > These are heuristics - you might come up with better ones. Yours are already implemented in Pipermail, I believe, I'm not sure about HyperKitty. I don't think Jamie's algorithm messed with [name] and [serial number] because they weren't common at that time, but he stripped Re: and its nonconforming variants, as well as "Fwd:". > At least with an orphans bucket, you don't end up with "invisible" > messages. Nothing I suggested produces invisible messages, just a different set of orphans or occasionally a misthreaded message that seems to be a duplicate if different msg-ids are munged to the same string. At least not in Jamie's algorithm. I don't know exactly what algorithms are used in Pipermail and HyperKitty. Interesting discussion, but I've reached the point of diminishing returns. I will be checking to see if any of your suggestions are improvements over what HyperKitty currently does.

6 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hi Abhilash, I started to setup Postfix (I don't know if that is the suggested and easy to use mail server) doing the steps on the website http://docs.mailman3.org/en/latest/config-core.html which tells: Postfix <http://www.postfix.org/>: To setup Postfix, add the following configuration to master.cf: # Support the default VERP delimiter.recipient_delimiter = +unknown_local_recipient_reject_code = 550owner_request_special = notransport_maps = hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = hash:/path-to-mailman/var/data/postfix_domains I added that config at the bottom of the master.cf file and did a 'postfix reload' and I got this error message: [root@localhost ~]# postfix reload /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad field count postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf! What do you suggest??? Thank you El jue., 20 jul. 2017 a las 14:09, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > 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 > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna <simon.hanna(a)serve-me.info> wrote: > On 03/31/2017 08:10 AM, David Krantz wrote: >> I think that would correspond to this line in urls.py >> >> url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), > Yes, that's the culprit. Replace it with the following: > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), > You can also update whatever guide you were using... Great, will try that! I don't know whether I can update the guide. It's the one referenced earlier in this thread named something like setup experience of mailman 3 in production. >> Then I of course have things to do on getting social logins to work. I >> currently get "DoesNotExist: SocialApp matching query does not exist." >> if trying to connect an account to google (which I started with). Not >> a showstopper as passwords do work. > Did you follow django-allauth's guide on setting them up? No, I haven't found that yet, I just followed the config examples as those seemed reasonable (although my knowledge of Django is quite limited so I am not a good judge of that of course). Will try that as well. Any particular known to work nice with the django setup used for mailman applications? // David

8 years, 5 months

[MM3-users] Re: clicking on a username when viewing a thread results in "Page not found"

by Mark Sapiro

On 6/26/23 9:26 PM, Ken Alker wrote: > Mark Sapiro wrote: >> This is a problem. That link goes to, e.g., >> https://example.com/archives/users/<user_id>/. What do you get if you >> strip the user_id and just go to what >> https://example.com/archives/users/ translates to on your system? >> You should get a page saying >> Not implemented >> >> This feature has not been implemented yet, sorry. >> >> If you get a 404, there is an issue with your web server configuration >> or maybe your top level urls.py. > > I get "Not implemented". I do not get a 404 error. That indicates there is some corruption somewhere. I need to research it to figure out where, but the issue is the <user_id> in https://example.com/archives/users/<user_id>/ doesn't exist. Are the crons - https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… running? If they are, the hyperkitty sync_mailman job should run daily and might fix this. You can also run `mailman_web mailman_sync` manually. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

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

by Mark Sapiro

On 4/23/25 9:25 AM, Stephen J. Turnbull wrote: > Alexander Inzinger-Zrock via Mailman-users writes: > > and then i just found out that my postfix_lmpt file was empty > > 1. What database are you using?[1] Is it running? If not, yes, that > file is going to be empty. > 2. Do you have any lists configured for your Mailman 3 instance? If > not, that file will be empty. > 3. Is Mailman running? (This probably isn't necessary, just > checking.) > 4. Is there a postfix_lmtp.db file in the same place? (Postfix will > not read the plaintext version, it must be a .db file.) If you haven't set `incoming` in the `mta` section of mailman.cfg to other than the default `mailman.mta.postfix.LMTP`, the `mailman aliases` command will at least write ``` # AUTOMATICALLY GENERATED BY MAILMAN ON {} # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. ``` to the postfix_lmtp file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: How to store additional information about lists?

by jonathan.mailing.lists＠gmail.com

Andreas Barth wrote: > I need to add custom attributes to the mailing lists: > "responsible department": Free text field who is responsible from an > organisational pov (not a person but an entity) > ... > Any hints how to do that best? Is it possible to store custom > attributes, or should that be stored elsewhere? It's possible to do something similar with Mailman 2 - see "Bob's Unofficial Mailman Tricks & Tips" at http://nleaudio.com/bnotes/mailman.htm - I've been using it for years. In my case it's like the Systers subscription page that Steve mentioned - something to help me decide whether to accept the subscription request, rather than something that I need to store in a database. When I looked at Mailman 3 last year I made a short custom subscription form which included a custom field, and a script to email it to me then send an email to the listname-subscribe email address. (I think I must have edited the MM3 confirmation link too because I've found a script that takes URL parameters, and sends a confirmation email to an address created from listname-confirm+ and the relevant token. I can't remember whether that was linked to having the custom field script.) Best wishes Jonathan

4 years, 3 months

[MM3-users] Re: Docker or virtualenv?

by Andrew Hodgson

Tim Cutts <tim(a)thecutts.org> wrote: >I’ve used docker on my setup. I have been wondering about this though, it causes me to need to run an AWS VM continuously to run my mailing lists, and that probably isn’t really necessary. I do sometimes wonder whether docker might be a better approach and run it under ECS, so I no longer have to >look after a VM. >Even better, MM3 is just a bunch of python functions at the end of the day, and it doesn’t *need* to be running continuously. Mailing lists are, more or less by definition, event driven. Has anyone considered whether it’s feasible to turn it into a bunch of Lambda functions with a serverless database behind >it? I actually moved from Docker to Virtualenv on my machine as I wanted to use the same larger VM to run a Cloudron instance which takes over Docker. Overall I have been more happier with the virtualenv approach as it allows me to customise the install more easier. I did look at running Mailman using Azure Container instances. The main thing here is we need to get the MTA integrated, and the MTA needs to send out emails from a static IP address with reverse DNS etc setup. This isn't easy to do on anything other than a VM. Thanks. Andrew.

2 years, 8 months

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

by justfixit＠marilynstrother.com

Very interestng! Upon restarting the system (down momentarily for taking a snapshot) and starting Mailman again, all of these missing [List] messages emerged from their timewarp and were delivered to the members / subscribers. Just before shutting down the system I discovered that the apache2 webserver had been off the air due to a module not being enabled yet. As of yet, I was unaware of any requirement for a web server to be online (beyond possibly gunicorn) in order for Mailman to run its lists. Does that speculation have a factual basis? Or do I risk starting a vicious rumor amongst the impatient readers who are not still here once we deduce this pair of observations were merely correlated in time, with no cause-and-effect relationship? Before this situation healed itself, the thought had crossed my mind to peek and see if anything was stuck in the queues: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… While that could have provided peace of mind that email messages were merely delayed instead of vanished, even in hindsight I do not see how that would have led to repairing the situation. In the absence of a hypothetical command: mailman status --verbose about which diagnostic tools or clues should I learn?

2 years, 3 months

[MM3-users] Re: Loops back to myself

by Stephen J. Turnbull

simonjwiles(a)gmail.com writes: > Grateful for any insight you can offer! Thanks! Have you asked Postfix channels? I don't think this is a Mailman problem, and they would recognize the issue faster than we do. The first thing I would do is grep /path/to/mailman/var/data/postfix_lmtp for the looping address. If it's not in there, then Mailman is not involved in the loop. I'm pretty sure that what's happening is the domain is recognized because it's in relay_domains, the transport maps are consulted, the address lookup fails, the transport defaults to relay_transport, which defaults to relay, which is in fact smptd, which recognizes a loop because the source and next-hop are both self. Voila! From the ADDRESS_CLASS_README: Valid recipient addresses for [relay_domains] are listed with the relay_recipient_maps parameter. The Postfix SMTP server rejects invalid recipients with "User unknown in relay recipient table". If this parameter value is empty, the Postfix SMTP server accepts all recipients for domains listed with the relay_domains parameter. [Ie, you're an MX for those domains.] I guess relay_recipient_maps = hash:/path/to/mailman/var/data/postfix_lmtp will fix this problem assuming the error message above is acceptable. I can't guarantee it won't cause other problems, though, depending on whether your host provides other services to those domains. Steve

1 year, 8 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!

by Marco Emilio Poleggi

Thanks, Mark. On 2025-09-01 19:40, Mark Sapiro wrote: > On 9/1/25 08:17, ^m'e via Mailman-users wrote: >> >> The same problem appeared today with my mariadb-based installation. @Mark, >> do you have a mysql version of your scripts? > > I'm not certain as I don't offhand have a way to test, but I think > > g/psycopg2/s//pymysql/ > > (i.e. just replace both occurrences of `psycopg2` with `pymysql`) will do it. > Yeah, it works! In my case, no uppercase addresses were found by the UC_fix script, whereas the Mult_primary did spot two accounts, both with 'staff status' in Django admin UI and with the same set of extra addresses. Most probably my fault, as I intended to use both accounts for administrative tasks and played to far with assigning the same sets of addresses, one of which was primary for one account. I guess that was causing the failure, right? -- ^m'e ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0xC366FCF67CDBD9F9.asc

2 weeks, 1 day

[MM3-users] Re: I don't get my posts with Gmail

by Stephen J. Turnbull

Allan Hansen writes: > I was pleased to see the advice below on how to get your own list > messages sent from a Google client, as my subscribers complain > about their messages going AWOL all the time. > Do those messages really show up in the spam folder without this > filter? (I don’t use Gmail). No. They don't show up *at all*. GMail puts a copy of the sent mail in the sent folder, not in the INBOX. Because it has not left the MUA, it has no trace header fields at all, only the fields required by RFC 822 plus any fields the user has populated. This makes it completely useless for debugging mail problems. It then discards the post returned from the mailing list. > If so, then the server is, indeed, sending the message to the mail > client, I'm not sure what you mean by the server. If you mean the Mailman list, yes, it is sending the message in the case in point. > and the mail client is doing the message ID linking locally, > discarding the incoming duplicate. "Mail client" is ambiguous here. There are a large number of roles involved, any of which may be implemented as a separate program (and the user is always a separate program ;-). 1. User == you. 2. Message user agent (MUA), which fetches messages from a message store (file, maildir, POP server, IMAP server), displays it to the user, and provides commands for the user to manipulate the message in various ways. 3. Message store, which keeps a database of messages received from the message delivery agent. 4. Message delivery agent (MDA), which accepts messages from the message transfer agent, and delivers them to applications such as message stores. 5. Message transfer agent (MTA), which accepts messages from the Internet, and delivers them to the MDA. Duplicate handling (which is a special case of filtering) can be implemented in any of those roles, but we can assume the user is not doing it. If she were, we'd just tell her to stop. > Would a change in mail client solve that? No, the issue is that users want to use a particular client, Gmail. Even if they're willing to change: > If so, then problem solved by a work-around. > If not, then how can the filter above work? If user-defined filters are implemented in the same program as deduplication, then they're just alternative targets for delivery, where deduplication uses the target /dev/null. If the user says "send those messages to a particular folder," that should override the program's defaults. What seems possible here is that Google implements message filters in the message store, and deduplication in the MDA. In that case the filter can't work. But you'd have to ask Google to be sure. Steve

4 years, 10 months

[MM3-users] Re: Join a Mailman 3 list?

by Mark Sapiro

On 6/8/25 20:18, Cathryn McGuire wrote: > Hi Mark, Stephen & Thomas, > > We've successfully merged our Mailman 2 list into Mailman 3. EMWD worked over the weekend to get it done for our members. We're pretty grateful. > > There are a few things we're trying to get our heads around, specifically to do with the Affinity Web UI. Most of it is pretty self explanatory, and I can see where it will be more aesthetically pleasing to manage, but a few things that aren't so intuitive. Affinity is a proprietary product of EMWD. At one point during the development of Affinity, when Brian C was still alive, I had access to a demo version, but no more. I don't know if there are any EMWD Mailman 3 users on this list, but I suspect your best resource for Affinity questions is EMWD. > Is anyone working with Mailman 3 and Affinity that could help us through the set up? For instance, when I log in as owner and go to change my password, it won't take a new one and asks me (with a pull down menu box) which account I want to change the password for, and it gives me a list of my emails, and also the other owner's email address. When I choose the email I'm logged in under, it says it's not the correct "credentials." > > Has anyone had this issue? Have you actually created an Affinity login? I believe initially, you have to sign up before you can sign in, even if you are the listowner. > Another thing is, and Stephen J. Turnbull prepared us for this, that the transferred membership are all "enabled" but not "registered." I understand we have to send a membership wide notification with a link to the Affinity log in page, and instructions going to the top right hand and clicking on the login icon, putting in their email address (the one in the system) and adding a password OR do they have to "create" a new sign in? If it works like our web UI, they have to create a new sign in. You do too. The process that imports a Mailman 2.1 list to a Mailman 3 list does not create web UI logins. > Thanks for any info you can give us about Affinity. (I see Brian Carpenter was beta testing it 4 years ago.) Cheers, Cathryn I was one of the people working with Brian back then to try out and give feedback on Affinity, but I've probably forgotten all I knew at that time. There may be current EMWD/Affinity users on this list, but as I said, your best support resource is probably EMWD. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: how do I bulk-remove users from ML in MM3?

by tlhackque

On 25-Oct-17 12:05, Simon Hanna wrote: > Postorius is currently using this to mass unsubscribe. > AFAIK there is an open issue in core to add such functionality Yes, see https://gitlab.com/mailman/mailman/issues/419 Yes, the current API has a number of scaling issues. Delete is bad, but other operations can require multiple API calls... (e.g. get state to conditionally create; create+patch; create user+create subscription, ...) https://gitlab.com/mailman/mailman/issues/367 (and others) Mass modify is also missing - https://gitlab.com/mailman/mailman/issues/241 notes one such case. > On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >> On 10/25/2017 07:35 AM, Barry Warsaw wrote: >>> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >> wrote: >>>> I just realized that "mailman members" only offers to "add members" >> via >>>> "-a filename" but I see no remove option. >>> It’s true, `mailman members` doesn’t currently have a —remove option. >> I found Rest API call for single user removal but I am questioning it's >> effectiveness given that I need to use this operation to potentially >> remove 1500 members >> >> -- >> Sr System and DevOps Engineer SoM IRT

7 years, 10 months

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

by Mark Sapiro

On 6/16/23 22:14, Stephen J. Turnbull wrote: > > @Mark > I've been seeing an unusual number of disabled subscriptions on > python.org and mailman3.org lists recently. Maybe we should look into > this. If you haven't seen this O365 breakage, I can send you some > samples. I haven't noticed this. I do receive notices when delivery is disabled, and I generally look at the attached DSN, and I don't recall any that have this issue. We do have an issue with mailman-users(a)mailman3.org messages for five users in the outlook.com, msn.com and hotmail.es domains. These are all since the server was moved last month and are all for the reason 550 5.7.1 Unfortunately, messages from [165.227.190.41] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [VI1EUR05FT020.eop-eur05.prod.protection.outlook.com 2023-06-17T05:14:54.401Z 08DB6E025E06C828] with differences only in the bracketed part at the end. The same five addresses keep getting disabled because I keep re-enabling them, and I have contacted Microsoft about this, so far with no results. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Mark Sapiro

On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > Dear Mark, > > FYI, I observed this issue with the postfix that receives the > mails from the previous MTA and hands it over to the mailman. But I fixed > at postfix by upgrading it to the version postfix 3. > > But still Mailman is not able to understand Hindi (Indian local > language) in which language the display names of the email ids are there. > > So, now what to do at Mailman so that it can also understand > local languages or any work around or other alternate solutions for these > sort of cases. As noted in my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… the issue is a Mailman bug which is fixed in the next release. It has to do with the fact that the display names are RFC 2047 encoded and not the particular encoding. Actually, the fix at https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on https://gitlab.com/mailman/mailman/-/merge_requests/652 which was released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is attached. -- 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: Hacking attempts?

by Stephen J. Turnbull

Lists via Mailman-users writes: > No, we’re nothing to do with Fedora, we just run a few low volume > mailing lists for our members. I would disable the fedora auth application as described in my previous mail, then. I wouldn't worry too much about the possibility that there are users of the feature, if there are people with Fedora accounts, they are sophisticated users who know how to request it be reenabled. > Happy to send you example error emails, I received 1,987 in the > past 24 hours. They seem to come in waves, it’s particularly bad > right now, but it will die off to a lower level for a while, then > hit a peak again in a week or so. This is how it would behave if web crawlers are the problem. Do you have a robots.txt file? If so, is your Django site protected? https://developers.google.com/search/docs/advanced/robots/intro https://robotstxt.org/ Note that if you decide to adopt Tim's suggestion of fail2ban, you probably need a robots.txt file, if there's *anything* on your site that you want indexed, you don't want the crawlers banned. > Let me know how many examples you want and I will send them direct > to your email. OK, but first let's try the low hanging fruit. Steve

3 years, 2 months

[MM3-users] Re: Deleting A List

by Odhiambo Washington

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

1 year, 4 months

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

by Ron

On 2024-07-10 12:05, Danil Smirnov via Mailman-users wrote: > After importing from Mailman 2, thousands of badly compiled messages > from the past appeared with empty content on the same date (date of > import). > > Is there a safe way to delete them all? If we delete them from the > database - hyperkitty_email table - do we need to do some clean-up > of hyperkitty_thread table as well? Per https://docs.mailman3.org/en/latest/migration.html, there's a tool with mailman2 that can clean messages *prior* to import: > all mailboxes should be checked for defects before importing. Certain > defects such as missing Message-ID: headers or missing or unparseable > Date: headers will be corrected or ignored by the import process. The > one defect that will definitely cause problems is lines beginning > with From in message bodies. These will be seen as the start of a new > message. There is a Mailman 2 script at $prefix/bin/cleanarch. I'd try deleting the corrupt list, running `cleanarch` on the old list, and re-importing. If the new list has messages that are not in the old list (i.e. it's in live production), then I'm not sure of how to proceed. Note the linked page also mentions a tool called check_hk_import script in hyperkitty/contrib folder.

1 year, 2 months

[MM3-users] eccentric setup question

by Jeff Berry

Good morning all, we've got a somewhat eccentric setup for our mailman installation, and we're having difficulty getting some of the settings to work properly, so I'm hoping some one has some insight. Our server machine is hidden behind our firewall, with the actual machine name not availble via external DNS) and all the mail is being routed through an Exchange server. So mail to list(a)domain.com hits our exchange server, which sends it on to lists(a)listserver.domain.com The problem we're having is that if the mailman domain of the list is listserver.domain.com then spamfilters start to flag the mail since it looks like spoofing/malformed headers and so on. If the mailman domain is just domain.com then postfix rejects it with an unknown local recipient error. I though I might be able to just tweak the incoming mail headers in postfix via header_checks but that's not working, either because I've got the wrong check or it's the wrong approach, or both. postfix relay_domains might do it, I think, but if it maps listserver.domain.com to domain.com that would break the listserver domain mailing lists (I think). Is there a canonical way to do this and/or have I missed some obvious configuration option in either mailman or postfix? Kind regards, Jeff Berry jeff.berry(a)mrc-cbu.cam.ac.uk

2 years, 5 months

[MM3-users] Digest Formatting

by Stephen J. Turnbull

mailman(a)manygoodideas.com writes: > I'm wondering how other admins have customized their digests to > make them more useful. It sounds like you have the digest format set to "plain". If you set it to "MIME", many email clients will format the display in such a way that you can click on individual messages. This is also possible with the plain format, but in my experience fewer clients implement that, because it's more fragile and painstaking to do. That might help. In general, this problem is really hard to address because the capabilities of clients vary so greatly. Perhaps your subscribers would be better off with single-message mode rather than digest mode. I'm not really clear on why anybody subscribes in digest mode any more. Digests still make sense for individual collections of messages, eg, "Your Honor, here are all the emails in which the defendent libeled my client." But for an ongoing stream such as a mailing list, I would think you would be much better off to receive the individual messages and let your modern client do its own thing with grouping threads and folders, and threading and ordering posts. Obviously, people like their own ways of doing things, but that suggestion might be useful for some of your subscribers. I hate to ask you to ask your subscribers to learn how to use their clients, as that frequently doesn't go over well, and they'll probably ask you to teach them with a client you've never used yourself :-/. However, if that's an option, most email clients provide a way to "burst" the digest into individual messages, which will then be threaded in the normal way for that client. This provides the user with the "download all the recent messages periodically" benefits of the digest, as well as the threading capability of the client. Also, a *good* email client will provide a way to view a digest "as a folder", without bursting it into individual messages. The latter is closest to what your users want, I think. (I still think that for most of them switching to regular mode is best.) > Yahoo! Groups used to send out HTML digests that had the thread > titles nicely distinguished, live links to the thread, and links to > Reply to sender, Reply to All, etc. Dealing with HTML email requires the resources of a billion-dollar company, unfortunately. It's a real mess. (For us old-timers, our favorite Mailman options are "strip HTML parts" and "convert HTML to plain text." ;-) For a small organization like Mailman, it's a "throw up your hands in distress" size problem. On the other hand, if you use a MIME-format digest, it's quite easy (but unfortunately not universal) for the client to implement that formatting itself. So that's the route we had to take. Hope this helps. If it inspires more questions, please ask! Steve

4 years, 10 months

[MM3-users] Re: Mail configuration

by Mark Sapiro

On 03/27/2018 03:43 PM, Stephen J. Turnbull wrote: > > My feeling is that you want to ask on Postfix channels, since I don't > see a good reason to involve Mailman itself in what is really a task > for the MTA. Mailman was deliberately designed to not know anything > about outgoing mail except a host and port to send to. Which brings up the point I've been meaning to post for days but it keeps slipping off the back burner and falling on the floor. I can think of a couple of ways to hack the code in Mailman 2.1 to select a different outgoing MTA by list. It can also be done in Mailman 3 by having separate MTA configs per list, but I can't give you a recipe off hand. But, the way I would do this is what you are presumably doing anyway. That is have separate Mailman installations on the old and new server. Then you can move the lists incrementally and gradually. Then all you need is a transport map in Postfix on the old server to route mail to the new server for the already moved lists, and then finally update DNS after all the lists are moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

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

by Odhiambo Washington

On Mon, Nov 20, 2023 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/20/23 00:58, Odhiambo Washington wrote: > > > > What is the command to export the archive as a mbox from the DB? > > I can't figure out which option it is by looking at 'mailman-web -h'. > > Normally you do this on the old server via the HyperKitty web UI which > has download buttons which do things like > > > https://example.com/archives/list/list@example.com/export/list@example.com.… > > or for a partial archive > > > https://example.com/archives/list/list@example.com/export/list@example.com-… > > However, in your case I don't think you have the old installation working > any more so the above won't help. > I had a dump of the old installation actually - both databases. The above has actually helped and I obtained the archive. > > BTW, how will ' mailman addmembers' treat a file containing: > > ``` > > Firstname Lastname <email@address> > > Onlyname <email2@address> > > ``` > > Correctly. It will import email@address with display name = 'Firstname > Lastname' and email2@address with display name = 'Onlyname'. > Super! > > I have opted for the simple way to do this: > > 1. Create the site in Django Admin and create/configure the list in > > Postorius > > 2. Add the members from the file dump, with delivery set to regular. > > 3. Send the members an email informing them that they need to set their > > delivery preferences. > > > > I am stuck on the issue of exporting the archives to mbox file as already > > stated above. > > Perhaps you can export the mbox via the web UI on the old server or > maybe temporarily create a second mailman-web on your server with the > old mailman-web database and use that web UI. That's exactly how I did it and got the archives. > Otherwise, if you have a working mailman-web that can access this > database, you could try > something like > ``` > $ mailman-web shell > > >>> from hyperkitty.lib.compat import get_list_by_name > >>> mlist = get_list_by_name('list_name_only', 'list_domain') > >>> with open('output.mbox', 'wb') as fp: > ... for email in mlist.emails.order_by("archived_date").all(): > ... fp.write(email.as_bytes() + b'\n') > ... > >>> > ``` > I tested the above out of curiosity. It failed. There are 9 lists in the setup, but I am only interested in 1. ``` (venv) mailman@debian12:~$ mailman-web shell Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Type 'copyright', 'credits' or 'license' for more information IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help. In [1]: from hyperkitty.lib.compat import get_list_by_name In [2]: mlist = get_list_by_name('list_name_only', 'list_domain') --------------------------------------------------------------------------- Http404 Traceback (most recent call last) Cell In[2], line 1 ----> 1 mlist = get_list_by_name('list_name_only', 'list_domain') File ~/venv/lib/python3.11/site-packages/hyperkitty/lib/compat.py:37, in get_list_by_name(list_name, domain) 35 matching = list(MailingList.objects.filter(name__startswith=list_name+"@")) 36 if len(matching) == 0: # no candidate found ---> 37 raise Http404("No archived mailinglist by that name") 38 if len(matching) == 1: # only one candidate 39 return matching[0] Http404: No archived mailinglist by that name ``` Was I supposed to substitute something for the real listname of the list I wanted? Another thing - totally unrelated - that surprised me: While using the commented-out block below, I could not click and get anything beyond http://http://list.name/mailman3 as anything to do with /postorius/xxxxx gave "Page not found" error. However, with the second config block that uses the UNIX socket, I am able to access everything ``` #<IfModule mod_proxy.c> # ProxyPreserveHost On # ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3" # ProxyPass "/archives" "http://127.0.0.1:8010/archives" # ProxyPass "/accounts" "http://127.0.0.1:8010/accounts" # ProxyPass "/admin" "http://127.0.0.1:8010/admin" # ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile" # </IfModule> ProxyPassMatch ^/static/ ! ProxyPassMatch ^/favicon.ico ! ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ ``` Why is it that the UNIX socket option worked flawlessly while the other option failed??? -- 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]

1 year, 9 months

[MM3-users] Re: Using MySQL via unix socket

by Mark Sapiro

On 2/2/19 5:31 AM, Torge Riedel wrote: > > A call to > > mysql -umailman -p > > successfully uses the socket on the machine and logs in. Yet you haven't specified -S or --socket > I tried > > mysql+pymysql://mailman:mailmanpass@127.0.0.1/mailman3?charset=utf8&use_unicode=1&unix_socket=/var/run/mysqld/mysqld.sock > > > as the connection string but it says that mysql server is not available. > Which is the same if remove the "unix_socket" parameter. I have found > this parameter when searching the net, but I'm not sure if it is supported. I think it should be, but the actual connection is via the the sqlalchemy create_engine() function. It appears this should be passed to the pymysql Connection() function per <https://docs.sqlalchemy.org/en/rel_1_2/core/engines.html#custom-dbapi-args> What happens if in a Python 3 session, you do from pymysql import connect conn = connect('127.0.0.1', user='mailman', password='mailmanpass', database='mailman3', charset='utf8', use_unicode=1, unix_socket='/var/run/mysqld/mysqld.sock') As I understand it, that's what sqlalchemy should be doing with your database url. In my testing, the above works with or without the unix_socket= argument, so I suspect something else is wrong in your case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Held message notifications ending up in junk

by Tibor Molnar

Hi Steve, I will look in to DKIM, thanks for your suggestion. Tibor On 09/09/2022 03:01, Stephen J. Turnbull wrote: Tibor Molnar writes: > I wonder if anyone else if having this trouble that all the held > message notifications are landing in junk folder. It's reported occasionally. This is automated pattern recognition doing its thing: these notifications *do* present very similar content *repeatedly* and *are* sent by a bot, and the algorithms figure that out quickly. Make sure the site DKIM signs its outgoing mail and whitelist the site, or whitelist the bot's address. Steve -- [Walton icon] Tibor Molnar [website icon] <https://waltoninstitute.ie/> [linkedin icon] <https://www.linkedin.com/in/tibor-molnar-564293106> [twitter icon] <https://twitter.com/username> [facebook icon] <https://www.facebook.com/username> System Administrator tibor.molnar(a)waltoninstitute.ie<mailto:name.name@waltoninstitute.ie> | +353 (0)51 30 6145 Walton Institute, South East Technological University, West Campus, Carriganore, Waterford, Ireland, X91 P20H [walton logo]<https://waltoninstitute.ie/> [setu logo] <https://www.setu.ie/> [DORA logo] <https://sfdora.org/read/> ________________________________ This email is subject to the following disclaimer(s) available at SETU Disclaimer.<https://www.wit.ie/about_wit/documents_and_policies/email-disclaimer> T? an r?omhphost seo faoi r?ir an ts?anta/na s?anta seo leanas at? le f?il ag SETU S?anad<https://www.wit.ie/about_wit/documents_and_policies/email-disclaimer> [SETU]<https://www.setu.ie>

3 years

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

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 5:48, Mark Sapiro escribió: > On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I did it via pip and all seems to be working, but when I try to >> discard or accept any message via postorius it shows a Forbidden 403 >> error CSRF verification failed. >> >> In my settings.py I have commented out these variables: >> >> # Other security settings >> # SECURE_SSL_REDIRECT = True >> # If you set SECURE_SSL_REDIRECT to True, make sure the >> SECURE_REDIRECT_EXEMPT >> # contains at least this line: >> # SECURE_REDIRECT_EXEMPT = [ >> # "archives/api/mailman/.*", # Request from Mailman. >> # ] >> # SESSION_COOKIE_SECURE = True >> # SECURE_CONTENT_TYPE_NOSNIFF = True >> # SECURE_BROWSER_XSS_FILTER = True >> # CSRF_COOKIE_SECURE = True >> # CSRF_COOKIE_HTTPONLY = True >> # X_FRAME_OPTIONS = 'DENY' >> >> I've been messing with them whith no results. It's like it lacked >> some value in some template... > > > It's not an issue with the code per se or the templates. These updates > are all installed on mail.python.org and lists.mailman3.org and are > working fine. > > After upgrading did you run > > django-admin collectstatic --clear > django-admin compress > django admin migrate Since I made all the mailman3 enviroment wide server open (not using venv) I already executed the migration doing a su -m mailman3 -c "python3 manage.py collectstatic" su -m mailman3 -c "python3 manage.py migrate" Being mailman3 the user who runs all of mailman3 related stuff I had problems doing the migrate part, showing an error of lacking perms. I solved it running the migration under root (I know it could be trouble after, but...) After that the compress part showed errors... but the postorius web maintenance was working well except for the CSRF error verification. I will trace the compress errors and will try to find the problem later. With your point to the CSRF_TRUSTED_ORIGINS parameter, I can now do the accept or discard part of a receiving message to the lists (I put below the config that is working for me). All seems to be working now flawlessly. Thanks once again for your guidance. ############ SESSION_COOKIE_SECURE = True SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_BROWSER_XSS_FILTER = True CSRF_COOKIE_SECURE = True CSRF_COOKIE_HTTPONLY = True X_FRAME_OPTIONS = 'DENY' # CSRF_TRUSTED_ORIGINS = [ "https://*.mydomain-example.xxx", "https://mydomain-example", "https://mydomain", ] ############ > > If you have and it doesn't help, you probably need to add > CSRF_TRUSTED_ORIGINS to your settings.py. > > See > https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins > and note the differences between Django <4.0 and >=4.0. > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 10 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

Hi Simon, Thank you for your reply. I did not realize that docker created everything for you so I prefer that. So let me get back to my original problems. I ran into the following after doing the normal docker installation: 1. curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; Connection refused 2. I was told to run docker ps. Here is the output from that: ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 073ecf209106 maxking/mailman-web:0.1 "docker-entrypoint..." 3 days ago Up 3 days 8000/tcp, 8080/tcp mailman-web aef8f44a7136 maxking/mailman-core:0.1 "docker-entrypoint..." 3 days ago Up 3 days 8001/tcp, 8024/tcp mailman-core 398e3fc05e2c postgres:9.6-alpine "docker-entrypoint..." 3 days ago Restarting (1) 36 hours ago dockermailman_database_1 3. I was asked to look at the logs which I don't have any: cd /opt/mailman/web/logs -bash: cd: /opt/mailman/web/logs: No such file or directory 4. I was asked to do docker logs mailman-web. It is filled with the following entries: psql: could not translate host name "database" to address: Try again Postgres is unavailable - sleeping It is after the above when I got confused. So now I understand that the Docker installation creates the database and runs it. That is important to know. So if you can help me get through the above 4 issues, it would be very appreciated. Thanks! Brian

7 years, 5 months

[MM3-users] Re: Help understanding why some users don't receive emails

by Mark Sapiro

On 9/21/22 14:06, Stephen Daniel wrote: > > Looking at one user in particular, I see in /var/log/syslog that postfix is > sending the email. There is nothing in bounce.log. And does the postfix log indicate the mail is accepted by the users MX? I.e. a log message with `status=sent`. > They are the only user who uses that particular email domain (embarqmail.com > ). > > Is there anything I can do to debug why they do not get the emails? Or is > this up to them and their email provider? Assuming the message is accepted by the user's MX, the user can check a spam/bulk/junk folder and if the messages aren't there, complain to their ISP about messages being silently discarded. Your log entries showing the message successfully delivered to the MX can provide evidence. Other than that, you need to ensure that your outgoing messages are DKIM signed, and that your outgoing MTA server has full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. It can also possibly help for the server's domain to publish a DMARC policy even if that is `p=none` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

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

by Shashikanth Komandoor

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values in production environment from the past 4 months almost. As of now, we are having around 1327 lists created on this. When I am trying to do some operations like creating the lists, deleting the lists or accessing the lists through the GUI, I am getting the below error. If I am trying to do the operations through API or through mailman shell, still I am not able to connect to the API. Something went wrong Mailman REST API not available. Please start Mailman core. But my mailman core was working fine in the background. At the same time I was able to do other operations on a few other lists. By the time I am getting the above error, the mailman.log recorded the below messages. *[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)* *[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)* *[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042* My mailman.cfg configuration is as below. The timeout value is the default value. I did not set any customized value. *(venv3) [root@lsmgr mailman]# grep -v ^# /var/lib/mailman/mailman/var/etc/mailman.cfg* *[archiver.hyperkitty]* *class: mailman_hyperkitty.Archiver* *enable: yes* *configuration: /var/lib/mailman/mailman-hyperkitty/mailman-hyperkitty.cfg* *[mta]* *incoming: mailman.mta.postfix.LMTP* *outgoing: mailman.mta.deliver.deliver* *lmtp_host: 0.0.0.0* *lmtp_port: 8024* *smtp_host: localhost* *smtp_port: 25* *[webservice]* *workers: 10* *[database]* *class: mailman.database.postgresql.PostgreSQLDatabase* *url: postgres://<postgresdbuser>:<postgresdbpassword>@127.0.0.1/mailman <http://127.0.0.1/mailman>* Then as per the suggestion I got earlier I configured the [webservice] section in the above file as below. *[webservice]* *configuration: /var/lib/mailman/mailman/var/etc/gunicorn.cfg* * [root@lsmgr logs]# cat /var/lib/mailman/mailman/var/etc/gunicorn.cfg* *[gunicorn]* *workers = 10* *timeout = 90 * After the above configuration, I found many errors like below in mailman.log file: *sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'pended.id <http://pended.id>'"* *sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.* *sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status PGRES_TUPLES_OK and no message from the libpq* The above might be few of the errors. FYI, for the creation of each list, it is taking almost around 15 to 20 minutes. After multiple times of the above error messages, at some time, I am fortunately getting the list created or some other operation getting done. I found the same scenario when the workers are from default 2 to 10. I don't understand where exactly I need to focus to solve the issue. Please let me know if I have to share any other details for you to suggest to me. -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 years

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

by Ángel

On 2020-08-13 at 16:55 -0700, Abhilash Raj wrote: > > I understand you may have a legal requirement do do this, but these > > "one-click - no user confirmation" links are a bad idea because usera > > will reply to a list post or forward it and not remove the link and > > userb will receive usera's reply and click usera's unsubscribe link > > either maliciously or thinking it will unsubscribe userb. > > There is also the issue that these days some Mail clients will try to > create a preview of all the URLs if they can and it would inadvertently > GET the URL resulting in the un-subscription. It's not just mail clients, but also anti-spam solutions. So for some customers, when the email passes through the antivirus/anti-spam solution, it would automatically unsubscribe the user. Check also this piece: https://inboxplacement.com/2020/05/machine-clicks-in-email/ If you end up with such system, the very least, I would make such system to also email the user one last time saying "Per your instruction as requested by machine IP V.X.Y.Z, we have unsubscribed from foobar-list, you can subscribe again by XYZ, etc." (maybe bcc the responsible internal team) And you don't want to start trying to tell apart real vs synthetic clicks. Regards

5 years, 1 month

[MM3-users] Re: Question after upgrade to mm 3.2.3 and latest postorius

by David Krantz

Thank you for your quick reply! Comments below. On Sun, Aug 11, 2019 at 10:03 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > I would recommend that you bump up to 3.7 for the web part too, mostly because 3.5 is now has been in security maintenance state for a while. We will drop support for 3.5 after this next release (so you do have some time :), but I fear there *could* potentially be other dependent libraries who might have dropped 3.5 support. > > Even though we do run CI and we'd (hopefully) know when there is a dependent library seriously breaking, but since we don't pin down versions, newer releases can cause problems. > > The web-server plugin I assume is mod_wsgi? Good information. Of course it is mod_wsgi. > If you use a separate wsgi server than the one embedded in web-server, you can bump versions a bit more easily. gunicorn or uwsgi are recommended options. Do note that the new version of Mailman Core also uses gunicorn now. That might be simpler although I probably still will have to use apache as passthrough as there are other things on that server using port 443 (80) and yet another server running is not what I'd like even if wsgi is a server process anyway as I understand it. I'll consider that and change it. > 1. The index page with all lists is not sorted in any useful way > > although it is based on something as the order seems to be stable. > > Prior to the upgrade the lists were sorted in alphabetical order after > > list name which is a lot more usable for me as admin. If I click the > > link at the bottom with "click to view all lists" I get the old > > behaviour. > > This change was made so that you will see only the lists you are a member of either as a subscriber, moderator or owner. This is default when you are logged-in, but when logged-out, you will see the old view with all lists alphabetically sorted. That is very good. It still is strange that this view is not sorted. > Are you sure the migrations are there? I can see the following list on the latest git master of Postorius (all the ones after 0004_ are related to emailtemplate): I thought so, but it seems as if they are not. That said I have not used django for anything else. After setting up the django-admin-script and modifying a few paths I got it to work correctly. The run I had made did not work although it also failed silently. Had I been used to django I'd known that it should print "OK" and ticked boxes for performed migrations, but I just use django for mailman-things. So now it works. Great. Thanks! // David

6 years, 1 month

[MM3-users] Re: Struggling with log rotation in Docker context

by Danil Smirnov

Hi Stephen, My example assumes that there are folders (inside of /basedir) on a Docker host machine which are mounted to mailman containers. So we run logrotate on the host machine against those mapped folders. Hence, /etc/logrotate.d/mailman file is for the host machine as well. Danil On Fri, Sep 4, 2020 at 12:36 PM <skenny(a)scss.tcd.ie> wrote: > Hi Danil, > > Firstly, thank you so much for your reply, and I do apologize for taking > so long to respond to your message. > > I understand your approach, and it sounds reliable and sensible. I'm > still a bit confused by something though. In your example, you create the > file /etc/logrotate.d/mailman - I presume that it must live in, or be > available in the container - but which one? You've created a single file, > with entries for both the mailman-core and mailman-web logs. But the logs > of -core are not available in -web and vice-versa. Did you mean to do > separate > "cat <<EOF > /etc/logrotate.d/mailman" operations for each container? > > Thanks again > Stephen > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

5 years

[MM3-users] Re: Archiver Hyperkitty Not Found

by Mark Sapiro

On 3/3/23 15:16, pat(a)suwalski.net wrote: > Hello, > > I upgraded from Debian 10 to 11 today, and hyperkitty archiver stopped working. > >>From the mailman.log: > > AssertionError: Archiver not found: hyperkitty > > I followed along on a related thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > I don't see any resolution to that thread. The only thing that worked for me was removing the hyperkitty rows from the listarchiver table in the database. But of course, now I don't have working archiving. There is a resolution of sorts there: It was setting ``` [archiver.hyperkitty] enable: no ``` in mailman.cfg, restarting Mailman core and then setting it back to `enable: yes`. > Any ideas? How would I make the archiver available? This django stuff is infuriatingly difficult compared to other frameworks. Do you have ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg ``` in your mailman.cfg where `/opt/mailman/mm/mailman-hyperkitty.cfg` is the actual path to mailman-hyperkitty.cfg and do you have in that file ``` [general] base_url: http://example.com/hyperkitty/ api_key: key matching the MAILMAN_ARCHIVER_KEY set in Django's settings. ``` Actually, even if these latter settings were wrong, the error would be different. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/22/23 12:57, ceo(a)sartrack.nz wrote: > Postorius is running. > I just removed all mailing lists, and created new empty ones. > These now show in the Apache2 website, via the link to Postorius I assume. > Then I imported members from the old mailing list "Templist" into the new one. > Now the "templist" is no longer visible on the website! Did you do this import with `mailman import21`? If so, did you run it as the Mailman user and not as root? > It is here: > https://sartrack.nz/mailman3/ > Note that the existing list "Templist" is missing. https://sartrack.nz/mailman3/ is missing CSS. Apache doesn't know how to access /static/ or you never built it with the django admin collectstatic command. > Now I need to login as 'superuser' or whatever it is called, so I can manage all the lists. > Where do I set up my login and password for access via the web browser? You create a superuser with the django admin createsuperuser command. How you invoke the django admin command depends on how you installed Mailman. Please tell us how you installed Mailman so we don't have to guess about this and other things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Stephen J. Turnbull

Allan Hansen writes: > LookupError: unknown encoding: iso-8859-8-i > Finally, in the captured message source (the last which was Cc'd to me) I do see this: > > Content-Type: text/plain; charset="iso-8859-8-i" Yes, that's the problem. Python doesn't define a codec for that encoding. It's generally preferable that mail senders use UTF-8, as that is likely to be implemented correctly in almost all modern mail clients, while the ISO-8859/8 series are likely to be implemented only in mail clients that specifically support Hebrew. That said, if the users are unable or unwilling to use UTF-8, it would be possible to create a codec for "iso-8859-8-i", I don't know how to do that, and I doubt Mark does. You could ask on python-list(a)python.org, or file an RFE on Python's GitHub tracker. For Mailman's purpose, there's no need to handle bidi, just codepoint for codepoint translation from "iso-8859-8-i" to Python internal encoding. So I guess the encoder and decoder from "iso-8859-8" (which does exist) can be used. If it's just code-for-code, then we can figure out how to have it used only for Mailman. Steve

2 years, 2 months

[MM3-users] Re: Rerun emails in the queue/bad

by Mark Sapiro

On 11/20/18 8:20 AM, Kaleb White wrote: > How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks. There should be error messages in the 'mailman' log for each preserved file. These would be like 'Skipping and preserving unparseable message: ....psv' 'Unpickling .bak exception: <error msg> Preserving file: ....psv' '.bak file max count, preserving file: ....psv' The first of these indicates an error in retrieving the message from it's original queue. The others have to do with how message loss is avoided. When a .pck file in a queue is processed, it is read and renamed to a .bak. Then if processing is interrupted by a crash, upon restart the .bak file will be processed. The second error above indicates a problem in unpickling the .bak and the third says the same .bak has already been tried too many times. You may be able to examine the files by pointing 'mailman qfile' at them. If that fails, either 'cat' or 'strings' may produce something useful. If they appear to be good, you can reprocess them by renaming to .pck, moving to queue/shunt and running 'mailman unshunt'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

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

by Nelson Strother

Yes, Postfix is also running, but this system currently has a trivially small configuration (single domain, single digit number of lists). When the CPU is kept ~100% busy for (maybe once as few as a) dozen minutes to (usually 20 minutes, but rarely) an hour [1] during `mailman start`, essentially all of the CPU time is being consumed by the dozen or so mailman runner processes, so I do not think Postfix alias processing has much if anything to do with these delays. [1] wall clock time; as an arbitrary indicator of how many cycles VMWare is giving to this server, here is what 7-zip observes: x@localhost:~$ 7za b 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,1 CPU Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz (406F0),ASM,AES-NI) Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz (406F0) CPU Freq: - - - - - - - - - RAM size: 425 MB, # CPU hardware threads: 1 RAM usage: 219 MB, # Benchmark threads: 1 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2909 99 2861 2831 | 29117 99 2502 2486 23: 2370 88 2741 2415 | 28833 99 2512 2496 24: 1937 79 2622 2083 | 27937 98 2501 2453 ---------------------------------- | ------------------------------ Avr: 89 2741 2443 | 99 2505 2478 Tot: 94 2623 2461 x@localhost:~$ On 6/8/23 10:14, Stephen J. Turnbull wrote: > Nelson Strother writes: > > > I did not intend to imply that `mailman start` (predictably) > > consumes more time than `mailman restart`. Both are lengthy and > > variable; > > You did say something about "30min" I believe. I don't understand why > it would take anywhere near that long. For example, I'm working with > a site with ~20,000 lists, and it only takes a few seconds. > > Oh ... wait ... are you using Postfix as the MTA? The supplied > Postfix MTA interface rebuilds the list aliases database on every > (re)start, and that's an O(#lists^2) process the way Mailman does it. > Postfix doesn't actually use the file to route mail, it always goes to > lmtp:127.0.01 or something like that. So I configured Postfix to > probe for existence of the list in Mailman's database. > > I think Postfix has plugins for all Mailman-supported databases > (PostgreSQL, MySQL/MariaDB, SQLite3). I can provide the changes > needed for this for PostgreSQL right away, if you're a MySQL site I > can give you the PostgreSQL config to give you the idea, but I may be > sslow if you want advice about the MySQL config. It's pretty > straightforward, though. > > > I do not yet understand how to make use of these clues, but at > > least one can see an epitaph from each deceased process. > > I don't understand them either. The only thing I can think of is that > a runner may try to access Mailman core, timeout, and crash during the > long startup. > > At least the MTA reconfig would make the restart cycle a lot less > painful. Note: this is NOT a Mailman-supported config (or even > contrib quality) yet, but I'm pretty confident of the theory and it is > working well in QA testing. > > Regarding the "alpha" status of the config, one Mailman 3 instance can > support multiple domains, but the Postfix docs say not to hit the > database for the "domain exists" check. If you aren't going to add > additional Mailman domains, then this doesn't matter (the domain list > file produced by the stock Mailman postfix config will work), but if > you do add or remove domains, you either need to configure Postfix to > hit the database for the "domain exists" check too contrary to > Postfix's advice, or you'd need to manage the domain list file by > hand. > > In any case, you could use this config for debugging, and go back to > the tried and true aliases file approach for production. And as I > indicated I'm somewhat available on a best-effort basis for > trouble-shooting. > > > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-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/mess… > > This message sent tojustfixit(a)marilynstrother.com

2 years, 3 months

[MM3-users] Re: Migrating Mailman 3 lists

by Mark Dadgar

On Apr 27, 2020, at 8:58 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> I know how to migrate mailman 2 lists to a new mailman 3 server. However >> I do not know how to migrate a mailman 3 list from one mailman 3 server >> to another one. Are there any instructions or protocol on how to >> accomplish this? The Mailman 3 server I want to migrate *from* was setup >> using Docker. The Mailman 3 server I want to migrate these lists *to* >> was setup using a python virtual environment via pip. > > If you can backup and migrate the database, that should do all of the Web stuff (except search index & logs) and most of the Core data. You'd need to additionally move the `var/` directory if you want to digests/logs/pending emails. At some point I would like to redo my MM3 instance to correct 2 bad decisions I made when I installed it: 1) using sqlite3 in production, and 2) using the Ubuntu packages, which are way behind current stable (~1 year). I’ve seen mentioned that it’s not as simple as dumping the sqlite3 database and restoring it to, say, Postgres because some of the data types are different between them (which seems like an odd design choice). Anyone sorted this kind of migration out yet? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 4 months

[MM3-users] Renaming a server after building

by Philip Colmer

We're getting closer to migrating from Mailman 2 to Mailman 3. In preparation, I want to get new servers built ready to accept the migrated data from our old MM2 servers before we shut them down. So, the new servers will be something like "new-lists.example.com" to complement the existing "lists.example.com" servers. When we are ready to do the migration, we'll rename the MM2 servers to "old-lists" and rename the MM3 servers to "lists" and then migrate the data. Looking at the settings in the Django admin interface, I *thought* I had figure out how best to do this: - Under /admin/sites/site/, click on the existing domain name and change it to match the correct FQDN. - Under /admin/django_mailman3/maildomain/, click on the exist mail domain and change the mail domain to match the correct FQDN. However, although the above works, if I then go back to the *Mailman* interface and go to /mailman3/domains/, the web interface recreates a domain for the original domain name that was in place when the server was created, i.e. we end up with "lists" and "new-lists". We've tried deleting that "new-lists" domain, rebooting and trying again but "new-lists" keeps on being created again. What am I overlooking here? Is there a better/approved way to achieve what we want to achieve? Thanks. Philip

3 years, 9 months

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

by Steve Brown

Genius. Yes, the bodyhash_mismatch is in the DKIM stuff, and the message returned from MM3 has a footer attachment. Although I had modified the default to contain no content, it is still 129 bytes. Second, the reason why I saw different behavior from my posts and my wife's was that she wasn't a member. When I made her a member and sent another post from her address, the bounce+ address showed up in the nonmember list identically. So all of this has something to do with how our email host handles the outgoing mail. TMD uses Mailgun as a mail handler that provides deliverability services. I have a ticket in to them, but haven't heard back. Mailgun appears to modify the return path to a bounce+ address that MM3 sees as a nonmember sender, and then the recipient's email handler sees it as equivalent to another address that might be in the envelope. The header of a message sent from steve(a)stevebrown.us to my radg.us address shows: spf=pass (fr-int-smtpin1.hostinger.io: domain of "bounce+906d23.99dcd9c-administrator=radg.us(a)stevebrown.us" designates 143.55.232.17 as permitted sender) smtp.mailfrom="bounce+906d23.99dcd9c-administrator=radg.us(a)stevebrown.us"; I think I have bothered you enough for something that does not seem to create any real problems or threaten to do so. So reply only if something here stimulates another thought.

11 months, 4 weeks

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

by Mark Sapiro

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

5 years, 6 months

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

by Abhilash Raj

On Thu, Apr 9, 2020, at 3:25 AM, skenny(a)scss.tcd.ie wrote: > Thanks for that Abhilash. I've since figured out how to add and remove > nonmembers using the REST API. > > Regarding the web interface, I wonder could you comment on the > following: I've created a test list and I have added a large number - > 1,800 - of nonmembers to it. I find that if I try to delete a > nonmember via the web interface, it seems to hang, and then the > following message appears: > > Something went wrong > Mailman REST API not available. Please start Mailman core. > > The same operation succeeds on other lists, where the number of > nonmembers is not large. Do you think this could be an issue of scale? Could be, I am not sure which operation is it stuck at. Can you check logs to see where is it breaking? 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. Abhilash > > Thanks > Stephen > _______________________________________________ > 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, 5 months

[MM3-users] Re: Replace "visit your dashboard" with URL link, like in Mailman 2.

by Mark Sapiro

On 5/8/23 09:52, Mark London via Mailman-users wrote: > Has anybody attempted to change the format of the emails that are sent > to the owner of a mailing list, to include a URL, instead of stating > "visit your dashboard"? The former is the behavior of Mailman 2. Many users, e.g. Jens Günther whose replied to this thread, have made custom templates to do this. > Is there any reason why this can't be done? If nobody has tried to do > so yet, I'll give it a try myself, as I'm familiar with django. Thanks. See https://gitlab.com/mailman/mailman/-/issues/901 and https://gitlab.com/mailman/mailman/-/issues/1055 Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for some documentation of templates, but note that you don't need to set URI's via REST, You can place list specific templates in Mailman's var/templates/lists/<list-id>/<lc>/ directory, domain specific templates in var/templates/domains/<domain-name>/<lc>/ and sitewide templates in var/templates/domain/site/<lc>/ or you can create list and/or domain specific templates via Postorius but see https://gitlab.com/mailman/postorius/-/issues/366 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Thomas Möhle

Hey Mark, thanks for your reply!> In what way? Do list posts get delivered? What works and what doesn't? > What are the observable symptoms for things that don't work? Yes, mails are not delivered. You can send a mail to the mailinglist without getting a bounce, but you will not receive the mail back through mailman. In addition to that, I'm unable to edit mailing lists in the web interface. After clicking on a list, I'll get a 404. Plus, I noticed that mailman is constantly writing files to /var/lib/mailman3/queue/out/ but they seem to get deleted right away again. I'm getting alot of IO there though. > What do you get for example if you go in a web browser with hyperkitty > running to > > https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… I get a small gziped json file back. Key is "url", value is a link to a message. > And please don't post secret keys and change the value of api_key: in > mailman-hyperkitty.cfg and the corresponding value in > MAILMAN_ARCHIVER_KEY in your Django settings. I actually tried to redact the logs and config files, but I must have failed to save my edits on that one file. I'll change it right away.

4 years, 1 month

[MM3-users] Re: Anyone integrated Single Sign On like Azure SSO with Mailman3?

by Ryan Morash

Since mailman-suite is already using allauth, I was able to easily enable the Microsoft Graph provider: https://django-allauth.readthedocs.io/en/latest/providers.html#microsoft-gr… From: Gilles Filippini <gilles.filippini(a)free.fr> Date: Wednesday, July 29, 2020 at 1:11 PM To: Jacob Bargery <jbargery(a)smccme.edu>, mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Anyone integrated Single Sign On like Azure SSO with Mailman3? Hi, Jacob Bargery a écrit le 28/07/2020 à 22:28 : > We are looking at whether it is possible to integrate Azure Single Sign On with Mailman3 to streamline use for our users, has anyone had any luck with doing this? If so, how did you go about doing so? I did such a thing with LemonLDAP-ng and the OpenID Connect protocol. I just had to add the django module mozilla-django-oidc and a custom logout method. The mozilla-django-oidc documentation [1] was quite helpful. [1] https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fmozilla-django-oidc.rea… Best, _g. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

5 years, 1 month

[MM3-users] Re: mailman-suite scheduled tasks

by Eric Broens

Thanks Morris!Since I included it in the crontab of the mailman user I could leave out the user: @hourly /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings Clear skies!Eric On Saturday, December 5, 2020, 11:39:41 PM GMT+1, Morris Jones <mojo(a)whiteoaks.com> wrote: On 12/5/2020 2:12 PM, Eric Broens via Mailman-users wrote: > Hi, > The documentation https://docs.mailman3.org/en/latest/config-web.html includes a section on scheduled tasks that need to be included in cron. > "runjobs" seems to be available only from "manage.py". > Do these scheduled tasks need to be executed from the python virtual environment?If so, is there a way to do that directly from cron, or should I create a script for these tasks which can be called from by cron? Eric, here's an example from my mailman crontab. By calling the django-admin instance from the virtual env, it gets picked up automatically: @hourly mailman /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings (Hopefully the line wrap won't munge the line too badly.) Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.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/

4 years, 9 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Wed, Dec 14, 2022 at 8:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/22 08:15, Odhiambo Washington wrote: > > After upgrading MM3 and running all the post-update tasks and even > > re-indexing all the posts, I have ended up with a somehow "broken" > > hyperkitty. > > The archives display on a browser six, to say the least. > > The site is public, so I can share the link: > https://list.rc.org/archives/ > > > > What should I do in order to fix this? > > > > > Are you asking about the lack of style or the "No archived list yet."? > The lack of style is the main issue. > The former indicates an issue in your web browser with accessing the > `static` directory or an issue with the django admin collectstatic or > compress commands. > So I have tested this with Brave, Google Chrome, Firefox - all on MS Windows and I do clear the browser cache. > I don't know about the latter - could it be because all the archives are > private and I'm, not logged in? > Even when logged in, the situation is the same, unfortunately. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Social signup?

by Duane Raymond

HI Mark, On Sun, 12 Mar 2023 at 22:06, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/12/23 13:56, Duane Raymond wrote: > > Is there a way to enable social signup (vs just login for existing > users)? > > It isn't at all clear or documented, but a user without an account can > go to the login page and login via a social account button and this will > create an account connected to that social account and log the user in. > Thanks for clarifying. Once I implemented social login, the buttons for social login did appear fine on the login page, but not on the signup page. I noticed for this list as well, there are no social signup buttons. So if it works, how does this happen? 1. Is there something I am missing adding to my settings.py and settings_local.py files to make it appear on the Posterius/Hyperkitty signup (vs login) page? (I searched but couldn't find anything) 2. Do I manually add this code to the Posterius/Hyperkitty signup template? 3. If a user tries to login via the login page and isn't registered will it be counted as a signup? 4. something else :-) I'm trying to get my head around where this is working from / what I need to do to get social signup obvious on the signup page (or other route) Cheers, Duane

2 years, 6 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Florian Fuchs

On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote: >Hello Mailman 3 users and developers! > >It's been a long slog but I think we are finally ready to begin the release >process for Mailman 3.1. I am pretty happy about the state of the Core, and >Florian is going to do some more integration testing with HyperKitty and >Postorius. We still have a few issues and a merge proposal or two to address, I did some manual integration testing today (core+mailmanclient+postorius) which looked fine so far. I didn't get to test HyperKitty and the bundler though, so any help testing those would be very much appreciated. I will have some more time tomorrow. I did all of my testing locally, which has some limitations. So I started setting up a more realistic environment on one of my dev machines. But I'm not done yet. Will report back when I'm done... ;-) >but I am planning to spin a beta of Core this weekend to facilitate testing. I think it's OK to put out a separate beta of the core, because the version pulled from pypi will still be 3.0 if I'm not terribly mistaken. For the real 3.1 we should probably do a coordinated release of all components, once everything's tested a little more thoroughly. Cheers Florian

8 years, 9 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 5/17/18 3:35 AM, Henrik Rasmussen wrote: > > I am also concerned that new lists are created with a subscription policy "Confirm" as default, rather than at least "Moderate", which can cause people to be subscribed by others against there will. I'm confused. Confirm sends a confirmation request to the subscribed address which must be acted upon by the user before she is added to the list. Moderate just means approval by an owner/moderator which, it seems to me is more susceptible to a 3rd party subscribe succeeding - i.e., subscription requires membership in some organization. A subscribes B who is a member of the organization but doesn't want to be on the list. The moderator verifies that B is an organization member and approves the subscription. Granted, it may be possible for some brain-dead vacation responder to confirm a subscription request, but that's a separate issue. > Also, regardless of this setting, administrators can subscribe people without their knowledge. Granted that this can be abused, but not allowing admins to directly add members will probably create more problems than it solves. -- 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: Mailserver Log entries following through mailman?

by Mark Sapiro

On 11/10/23 12:39, Andreas Barth wrote: > > is there some way to find an ID to follow an email through mailman? In > the exim logfile there is only something like C="250 Ok" (whereas in > mails sent to another exim there is something like C="250 OK id=…"). > (What I sometimes need to do is to follow an mail whether it is sent > through mailman and to where.) Every message should have a unique Message-ID: header. According to my reading of https://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html Exim should create a => log entry with an id= field containing the Message-ID when the message is received for delivery to Mailman and another similar entry when the message is received from Mailman for delivery to one or more list members. Mailman itself logs ACCEPT:, HOLD:, DISCARD:, REJECT: and OWNER: entries in mailman.log for those events (OWNER: indicates a message to list owners). All these entries contain the Message-ID. Mailman's smtp.log contains 'post to' and 'smtp to' entries with Message-IDs for all outgoing messages. > Or should I raise an issue as whishlist request? What exactly would you wish for that Mailman can do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3

by Shashikanth Komandoor

Stephen, Thank you for your response. I am sorry for getting confused between two lists mailman-users and mailman-developers. Developers may be busy and my question may be basic but still there is a space for more politeness at your end to advice me. Apart from that, you have given a lot much of useful information which is really and honestly helpful for me to the maximum extent. Now I shall take the help of members of mailman-users only. @mailman-users@mailman3.org <mailman-users(a)mailman3.org>, Team, I have installed Mailman Version 3.3 and running in production. Our development team developed another application which requires the access of the REST API and do changes over the MM3 DB automatically without manual intervention. That application would be connecting to REST API over http or https protocol To achieve this I have enabled the REST API to run at all the IP addresses of my MM3 Server by editing the mailman/src/mailman/config/schema.cfg file. I was able to run few commands like creation of domains, lists, list configuration changes for testing using the CURL (GET, POST, PATCH, DELTE) and got succeeded. But for every operation I need to write a different URL for CURL command to work. Out of many operations I require, addition of members to a list and removal of members from a list are most important tasks. So, I request herewith, from the URL https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html, I could see many URLs but they are executed at python prompt (>>>) only. I require URLs usable at the CURL command. Is there any way I could generate the URLs or any where documented regarding the URLs usable with CURL for the addition and removal of subscribers ? On Sat, Apr 25, 2020 at 8:04 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Shashi, > > This whole thread is off-topic for the developers list. This list is > for development of Mailman, not for teaching people to use it. Read > the whole recommended documentation before you ask busy developers to > tutor you in very basic things. There's a mailman-users(a)mailman3.org > list for users to help each other. All of the Mailman developers who > might be willing to answer your questions are there as well, but there > are also many experienced users, some of whom have experimented with > the REST API who will also help. Please reply there for further > help. (Reply-To is set.) > > That said, there are plenty of URLs in the API documentation. Here's > a hint: search for "dump_json". That function takes an URL. You may > want https: instead of http: in your URLs, and you may need to change > the port from 9001, depending on the configuration of your REST > server. Try it with simple GET requests for information first, such > as for domains or lists. You can also do these requests with an > ordinary web browser, though I don't know what it will do with the > JSON-formatted reply. > > If you don't have domains and lists configured, I suppose the > informational requests will come back as empty JSON objects. It > should be safe to make them. You can either use Postorius to > bootstrap a few example domains, lists, and users, or (the hard way) > figure out how to POST appropriate requests. I don't recommend trying > to update the backend DBMS by hand; the schema is quite complicated. > I don't know how to use curl to update Mailman's databases. That > requires a POST request which I have never done with curl. The POST > request needs to be valid JSON. > > The more I think about this, the less I think your idea of using curl > is worthwhile, because formatting JSON requests by hand is going to be > a real annoyance and a great way to mess up your database with > spurious information. You're really going to want programmatic > support for this. But that's already all available in Python in the > Mailman system. > > It's up to you, but I feel a responsibility to warn you that using > curl is not going to be simpler than learning enough Python to do > these things. > > Regards, > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 4 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/16/23 18:55, 朱超 wrote: > > Hi, When I subscribe the email list in Subscription Policy is > > confirm, Some problems happen in here： > > 1.Some mail mua reject send the confirm the message, because the > > length of recipient is too long. for exmaple: > > requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, > > and the mail mua reject to modify about this. > > The default English template says in part: > > Before you can start using GNU Mailman at this site, you must first > confirm that this is your email address. You can do this by replying to > this message. > > Or you should include the following line -- and only the following > line -- in a message to $request_email: > > confirm $token > > I.e. It gives an alternative method if `reply` doesn't work. You can > provide a custom version of this template with different wording if you > think you can improve it. The problem is the reply address, though. Changing the template to suggest only the "confirm $token" in body method doesn't help people who hit R expecting that should work, especially since many "user fiendly" (misspelling intentional) MUAs don't display the address. Avoiding that requires code changes, I guess? > > 2.It is inconvenient for users to use. Many people will > > mistakenly think that after clicking the subscribe button, it > > will be successful, and they will not process the email. > step, you can set Subscription Policy to Open, but then anyone can > maliciously subscribe third parties to the list. *Please* do not do this if your server is exposed to the Internet. There are bots that search for such servers, and sell lists of them to people who want to DOS mailboxes. You may find yourself banned across the Internet. The only real alternative to confirmation is approval by moderators. I believe Mailman 3 offers that alternative as Mailman 2 did, can't check at the moment. > > Regarding the discussion on the subscription method of the > > mailing list, should we consider optimizing the subscription > > method of the mailing list, for example: > > 1. use the method of sending a verification code to subscribe by > > email，When you receive the verification code sent by the > > mailing list and fill it in again, you can subscribe > > successfully。 > > How is this different from the present method. Just wording. I think they are thinking of the "invite" option that was provided in Mailman 2 mass subscribe (again, I think Mailman 3 retains it but I never ever used it so I don't recall for sure). But it doesn't make sense for a user-initiated interaction. > If you want, you can make > a custom template and include something like: > > Alternatively, you can confirm by going to the URL > > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token If I understand the OP's PoV correctly, I think I would change the list information page to say "Send a personal invitation to join the list to [email address here]. If you aren't a subscriber, you can invite yourself." And change the word "confirm" in the confirmation template to "subscribe". > We don't include that in the default template because Mailman core > doesn't know if you even have a web UI or how to access it if you > do. We should fix that, at least if the web interface is Postorius (wishlist, assigned to me): https://gitlab.com/mailman/mailman/-/issues/1055 @mark https://gitlab.com/mailman/mailman/-/issues/901 Maybe we can close this? I'm not sure why it was left open since there's no action proposed for Mailman improvement. > > 2. use the email to send a connection to confirm the > > subscription，People click the link to be redirected to a > > confirmation page to subscribe to the email。 > > See above. Indeed, AFAICS almost everything the OP is suggesting amounts to an identical procedure as far as the Mailman server is concerned, it's just described to the subscriber differently. The one exception is the suggestion to eliminate the confirmation step, and while that is supported, it's quite likely to cause problems for third parties and eventually for the Mailman site unless you have an alternative ground source of truth such as an employee database. Steve

2 years, 8 months

[MM3-users] Re: Display the last post time for a list or all lists.

by Mark Sapiro

Mark Sapiro wrote: > It wouldn't be difficult to do, but at the moment, it wouldn't provide anything useful because of <https://gitlab.com/mailman/mailman/issues/453>. The issue is now fixed in the branch head at least. The script corresponding to https://www.msapiro.net/scripts/last_post.py would be almost identical except for changing real_name to display_name, last_post_time to last_post_at and fixing the print for Python 3. Also changing the string interpolation to format(), it becomes: --------------------------------------------------- import time def last_post(mlist): print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) --------------------------------------------------- The only issue with the script is for a list which has had no posts since #453 was fixed, mlist.last_post_at is None and time.ctime(None) is the current date and time. That too could easily be fixed like: --------------------------------------------------- import time def last_post(mlist): if mlist.last_post_at: print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) else: print('{}: No posts'.format(mlist.display_name)) --------------------------------------------------- The trickier part is the Mailman 3 mailman withlist command has no option to run for all lists, so you'd need to run it something like #!/bin/sh for list in `mailman lists -q`; do mailman withlist -r last_post -l $list done -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Can creating too many Django accounts crash Mailman3 server?

by Abhilash Raj

On Tue, Sep 15, 2020, at 12:09 AM, Stephen J. Turnbull wrote: > Mohsen Masoudfar writes: > > > It seems anybody can go to the site: > > https://LISTSERVNAME/mailman3/postorius/lists/ > > and click on the [Sign up] on the top-right corner and create an > > account. > > Yes. > > > This can easily be automated, even though the next step, confirming > > the email address, being ignored. I believe it can be used as a > > target for a DOS attack by creating so many accounts, that > > eventually causes an 'out of space' error. > > > > Is this a justified concern? > > "Justified" depends on who you think the attacker is. Theoretically > it's a real possibility, but the space used by an unverified account > is not large. I suspect there are always much more painful DoS > attacks to worry about. > > > Is there a way to manage this feature in a secure way? > > In some sense, I don't think there is. The point of the feature is to > allow anybody to sign up without authentication beyond having a usable > email address. Either you allow the DoS attack or anything you do is > likely to deny service to legitimate users. > > Brian's approach (cron job purging unverified users) is generally good > hygiene, but I don't think it would do much against an deliberate > attack. And it shouldn't be hard to automate the confirmation > process. I guess you could handle that by purging accounts with no > subscriptions or other roles on any lists, but that might annoy a few > legitimate users. > > Probably the best you could do for an open server would be to throttle > user creation to say 1 per minute (adjustable to the scale of your > site). > > I don't know if there is currently a way to require admin approval for > account creation (as opposed to list subscription). Perhaps we should > add that if we don't have it. I checked django-allauth, it doesn't have a feature like that. We could implement something on-top of that to optionally allow for admin approval but some other details would need to be figured out and would be a sizeable task involving a new view for account approvals. We potentially also would have to modify the models used in django-allauth to add the flag for "approved", which I am not sure would be an easy task to figure out. Perhaps, it might be easier to make a feature request and implement it in django-allauth though. > > Steve > _______________________________________________ > 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)

4 years, 11 months

[MM3-users] Re: Running mailman shell commands in a script

by Eggert Ehmke

Thanks, that works for me. Am Dienstag, 14. September 2021, 20:31:59 CEST schrieb Abhilash Raj: > On Tue, Sep 14, 2021, at 4:57 AM, Eggert Ehmke via Mailman-users wrote: > > Hello, I understand that the mailman shell is basically interactive. I > > need to run some actions as adding and deleting users in a Linux shell > > script, or even from another python program. How does that work? > > Check out mailman members, addmembers, delmembers, syncmembers > commands[1] and see if they do what you are expecting the Mailman2 commands > to do or you need something more. > > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d > ocs/commands.html > > If you are using another Python program, then you can rely on > mailmanclient[2] python package for operations on lists and memberships > using Mailman's REST API. > > [1]: https://pypi.org/project/mailmanclient/ > > > In fact, I miss the commands that were in the bin directory of the old > > mailman2 installation. Wouldn't it be nice to add them again to mailman3? > > > > Cheers, Eggert > > > > > > _______________________________________________ > > 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

[MM3-users] Re: Mailman runners missing - nothing in logs

by Mark Sapiro

On 1/18/20 6:13 AM, Torge Riedel wrote: > > So now back to good. I checked all the logs prior to restarting the > service in directory /opt/mailman/var/log, but I do not see any errors. > And the master was still running, I would expect that the master will > start / restart a runner in case it died? What's in /opt/mailman/var/log/mailman.log? There should be entries like Jan 18 13:51:11 2020 (11700) xxxx runner started. for each runner every time it starts and like Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. Jan 18 13:47:31 2020 (10096) xxxx runner exiting. for each runner every time it stops, but with perhaps a reason other than `caught SIGTERM` That should at least tell you when they stopped. Also, if they stopped for some reason. The master will only restart runners that exit if they exit because of SIGUSR1 or some internal error and even then, only the configured max_restarts number of times. Do you have a logrotate script for the logs in /opt/mailman/var/log, and if so, does it have a postrotate script that signals Mailman to reopen logs other than by a `mailman reopen` command, perhaps by signaling the master with other than SIGHUP? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

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

by Zaheer Abbas

Thanks, Mark & Odhiambo for providing options for the solution. I will try the 'postorius header filters' hacky way as it's more suitable to my requirement, however, if it didn't work as expected, then filtration through exim filter is also an acceptable option. Thanks again for the quick response. On Thu, Mar 30, 2023 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 11:07, Odhiambo Washington wrote: > > So the MTA option that doesn't involve any regex is better than no? > > Partly it's a matter of taste and possibly a matter of necessity. I.e. a > list admin can do this with header filters and may not have access to > the MTA config. > > Also, it's not clear to me that doing this in Postfix is less > complicated than understanding a regex. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to zaheer.psg(a)gmail.com >

2 years, 5 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/02/2016 08:07 AM, Barry Warsaw wrote: > Hello Mailman 3 users and developers! > > It's been a long slog but I think we are finally ready to begin the release > process for Mailman 3.1. I am pretty happy about the state of the Core, and > Florian is going to do some more integration testing with HyperKitty and > Postorius. We still have a few issues and a merge proposal or two to address, > but I am planning to spin a beta of Core this weekend to facilitate testing. Barry, I understand you need to feel comfortable about everything going into the core and this takes time and energy to review all the MRs, but I think it is pretty important to get the DMARC mitigations into the core. If there's anything I can do to help with this, let me know. I will rebase my branch again and possibly make one minor tweak, but I think it should be OK. I can also work on Postorius. Also in this vein I have a question. Should the DMARC settings be added to the Alter Messages tab in the List Settings view or would it be better to have a separate DMARC Mitigations tab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

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

by Mark Sapiro

On 7/8/21 1:03 PM, Mark Sapiro wrote: > On 7/8/21 8:35 AM, Sarah H wrote: >> >> When trying to add a new thread via the hyperkitty interface I can see >> the email go through the maillog, I get the email with the entered >> content and everything else works, it just doesn't add a new thread to >> the archive. > > What if anything is in Mailman's var/archives/hyperkitty/spool/ directory? > > Do you have something like > ``` > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > ``` > in your mailman.cfg? Do you then have > ``` > [general] > base_url: ... > api_key: ... > ``` > in the mailman-hyperkitty.cfg file and is base_url set to a url tha > accesses hyperkitty and is api_key set to the same value as the > MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but > not in mailman-hyperkitty.cfg, i.e., > ``` > api_key: xxx > MAILMAN_ARCHIVER_KEY = 'xxx' > ``` > I see that these settings are not covered in the virtualenv installation guide at https://docs.mailman3.org/en/latest/install/virtualenv.html. This is now https://gitlab.com/mailman/mailman-suite-doc/-/issues/32 and we'll fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: installing a new instance of mm3

by Christian Stalberg

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

3 years, 10 months

[MM3-users] Re: List of "site admin" commands in Mailman 3.1 docker-mailman

by Abhilash Raj

Hi Henrik, On Mon, Jul 17, 2017, at 07:55 AM, Henrik Rasmussen wrote: > I am new to all of Python, Django, Docker, Docker-compose and everything > else used by docker-mailman. I have managed to get a webinterface of > Mailman 3.1, I installed using Docker and Docker-Compose from > github.com/maxking/docker-mailman, but my config is still bogues > (probably just my Apache-config). > > I'm quite confused about Mailman 3 documentation regarding those commands > the site admin would do in Mailman 2 like list_members, config_list -o > etc.)., and I have been trying to figure out what documentation regards > the development of Mailman 3, what regards the final version 3.1 and what > I am supposed to do regarding Docker. > > > 1) Should I enter the container using "docker exec -it mailman-web > bash" and run "python" in order to get a python prompt, and from there > run commands like those documented at > mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html > ?. Just to add to what Barry mentioned, the in docker command above, you should enter the `mailman-core` container instead of the `mailman-web` container if you are looking for the command line options of Mailman Core. so it should be something like: $ docker exec -it mailman-core bash -- thanks, Abhilash Raj

8 years, 2 months

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Andrew Hodgson

bin/mailman import21 I saw this in the image, do you have any idea about what may be missing from this? I may shelve this project again for the time being if we can't do the migration, but good to know I can get a production like Docker instance running relatively painlessly. Andrew. -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: 01 September 2017 16:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman3 Docker question and importing lists from MM2 On 09/01/2017 07:09 AM, Andrew Hodgson wrote: > > I had a question regarding the parameter: SERVE_FROM_DOMAIN. > > I want to use multiple domains, what is the best way to specify multiple domains in this environment variable? I don't know the answer to this. > Furthermore, is there a recommended way to get data from MM2 (list configs and archives) into MM3? There are two things. For importing list configs there is bin/mailman import21 but it is not up to date and probably doesn't work. For importing archives there is django-admin hyperkitty_import [--settings=if.needed] which works well using the MM 2.1 LISTNAME.mbox/LISTNAME.mbox file as input. -- 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

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

by Abhilash Raj

On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > 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. Yes, you are correct. Mass Subscription current just subscribes each address one-by-one and thus times-out. I have created an issue for this https://gitlab.com/mailman/postorius/issues/264. > > Some quick overview of our infrastructure: The TCP endpoints are: > browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes- > ingress -> nginx in mailman -> mailman I would very much appreciate if you'd share you configuration and/or a blog post on your setup. I have been trying to set Mailman use Kubernetes for a time, but haven't had time to do it. > 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? Which MTA are you using? What do you see in mailman's logs and MTA's logs? I haven't seen this kind of problem before with Mailman 3. This very list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > 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/> > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 4 months

[MM3-users] Re: Mailman3 on virtual domains

by Mark Sapiro

On 10/7/23 09:25, Lars Bjørndal wrote: > [Mark] > > [...] > >> See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? It has been in postorius since 1.2.0. > I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? If your Postorius is >=1.2.0, there should be 3 fields on the Edit domain page - Description, Alias Domain and Web Host. The whole page looks something like: Edit domain example.com Description Alias Domain Normally empty. Used only for unusual Postfix configs. Web Host The domain from which you want the web UI to be served from. This can be same or different from the Mail Host. You can edit the list of available web hosts here. You can also set an alias_domain in `mailman shell`. E.g., ``` >>> domain = getUtility(IDomainManager).get('example.com') >>> domain.alias_domain = 'x.example.com' >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

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

by Allan Hansen

Hi Stephen, Thank you for your response. I have let my users/moderators know how few resources are available for developing Mailman - that it’s not a system supported by hundreds of highly paid developers, testers, security experts, product managers, etc., and that the software is public-domain code. My own involvement in this is similar to yours. A note to flush bounces to people upgrading may be a good idea. And yes, the disabled accounts were mostly on busy lists, but not all. I should also mention that a heck of a lot of them were sbcglobal.net users, which was interesting. AT&T apparently is not doing a good job for their clients (and they do have armies of staff who could). Maybe your users have better service providers than mine. As for looking at subscription options, I have an authenticated (verified) Django account that I use for testing (non-owner but moderator). When I log in to that account (or as list owner with my usual account), the only field that is filled out in the ‘Subscription options’ dialog is the ‘Select Email’ pulldown menu. So yes, I think that there is an issue here. I agree with you that to provide access to this information for people who don’t have verified Django accounts does not make sense. But those who have set up accounts should, and the moderators and owners definitely should. If not being able to see these settings is specific to my installation, I would appreciate getting it fixed. If needed I can provide screen shots to prove authentication and issue. Once a setting is modified, it becomes visible then and afterwards! I thought about contacting you all at the time, but figured that I needed to get this done promptly (based on the reactions from my users/moderators, which were very prompt). :-) Finally, about the ‘Change Address’ feature: It’s really not complicated, Stephen, or rather, it should not be. People all the time move from one provider (like sbcglobal, hopefully) to another (like gmail). When they do, they generally want all instances of their old address strings everywhere necessary in Mailman/Postorius to be replaced with the new address, so they can use that instead. This is how the ‘Apply Globally’ address change worked in MM2 and that was more than good enough. If there are other use cases where they need to retain the old address for whatever reason, they would not use this feature, but add the new address to their account and then manage the old in some other way. Of the thousands of subscribers I have, maybe a handful are interested in maintaining more than one subscription address. All the rest simply use one address and when they get a new email address they want to use that instead for all their subscriptions everywhere and never see the old one again (other than in the archives, of course). Period. It’s really that simple in 99.9 % of the cases. Please don’t hold this up for the 0.1%. Yours, Allan

4 years, 7 months

[MM3-users] Long-shot cry for help

by David Partain

Hi, I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... 2. There's this one curious cron job... * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings (yes, I know python2.7 is a problem... see the last paragraph below). These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? ----------------------------------- Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Cheers, David

4 years, 3 months

[MM3-users] Re: Subscription Request asking for Confirmation instead of Moderation

by Henry Hartley

> -----Original Message----- > From: Stephen J. Turnbull <steve(a)turnbull.jp> > Sent: Thursday, August 28, 2025 12:27 > > Henry Hartley via Mailman-users writes: > > >>> 1. Are there particular headers that are causing the email > >>> to go to the Confirmation page instead of the Approval page? Or >>> are > there particular headers we can add that will help with this? > > No. That's entirely determined by the list's configuration. You cannot change > that behavior via a user's subscription request whether by email or web. IIRC, > the only overrides are either through the REST API, "mailman shell", or the > "mass subscribe" page on the web. (I guess it's possible that the moderator can > "pre confirm" at approval time, do you see such an option when you approve? > I've never managed a "moderate" list so I don't know without groveling through > the code.) > > Do you really only have one list? Is it possible that the misbehaving list is not > configured as you expect (ie, the list subscription policy is "confirm" or "confirm > then moderate")? Unlikely, but if you haven't checked since the problem > started, please confirm. I have 50 lists and they all have the "Subscription Policy" set to Moderate. If I send an email (e.g. from my gmail account) to the LIST-join address, it goes into the Subscriptions Pending Approval list, as it should. But, when sent from Drupal it goes to the Subscriptions Pending User Confirmation list. That's the weirdness that I'm trying to untangle. Nevertheless, I will have one of our testers subscribe through Drupal to a list and confirm that the issue happens every time. > Are you sure that the members have not been approved by some moderator? I > forget exactly how this works, but unless you use mass subscribe with the "pre > confirm" option set, the user will have to confirm before they can receive mail. The issue was reported by the moderator, who saw the email address in the wrong place. If the Subscription Policy is set to 'Confirm then Moderate' then ;First subscribers have to confirm, then a moderator needs to authorize.' Since it's set to 'Moderate' (only), then 'Moderators will have to authorize each subscription manually.' > > > > 2. Is there any way for us to move an address from the > > > > Confirmation Pending page to confirmed on the backend > > > > (preferably through the web interface, but on the server > > > itself, if > necessary)? > > Not that I know of, but what you can do is mass subscribe those addresses. I > think that you'll still end up with them waiting for confirmation as described > above. You can confirm them by accessing the database directly, but that's > more fraught than I want to deal with at bedtime :-). Until we figure this out, I've instructed the moderator to copy the address from the User Confirmation list and Mass Subscribe them and then remove them from the Confirmation List. It works but the moderators don't like it. > > Authentication-Results: spf=fail (sender IP is 192.168.0.0) > > smtp.mailfrom=SCHOOL.edu; dkim=none (message not signed) > > header.d=none;dmarc=fail action=oreject > > header.from=SCHOOL.edu;compauth=fail reason=000 > > This requires some care. DMARC is failing, and necessarily will fail. > If SCHOOL.edu has a p=reject policy, this mail should not get to Mailman at all. I'm pretty sure the outgoing mail from mailman is getting the right headers for DMARC but it definitely bears testing. > If the Drupal host is the Mailman host, then you could use the PHP script to talk > to the REST API instead of using email. Cutting out the long list of middlemen, so > to speak. (It would also be possible if they're different hosts, but the security > precautions I would recommend are quite a bit more severe.) Yes, Drupal and Mailman are on the same host. We definitely could rewrite our code to use the REST API, and in the long run, that would be good. But we brought this code over from government servers that were using Mailman2 and since it basically worked (except for this odd issue) we put that at a lower priority. But maybe we need to do that sooner rather than later. -- Henry Hartley

2 weeks, 6 days

[MM3-users] Re: Mailman 3 localization

by Simon Hanna

On 07/03/2018 10:21 AM, Stephen J. Turnbull wrote: > Simon Hanna writes: > > > > 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? > > I don't think that is the right place to do it, because I'm sure > Ubuntu lags our releases by quite a bit. Obviously on Launchpad you > should translate for their releases. > > > I wanted to set it up, but the requirement is to use a free hosted > > solution. > > If by "free" you mean we can't afford to pay for a service, that's > probably not true. If by "free" you mean the services you mention > operate on non-free software, yes, RMS would indeed give us bat-guano > about that, but it's not a 100% requirement. We did use Jira for some > services for several years. So the main issue would be how long > Abhilash is willing to put up with rms-guano. Yeah I meant the second definition :-) When I brought it up Barry said it had to be this way and that we don't want to self host it.

7 years, 2 months

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

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. On 4/26/19 6:32 PM, Abhilash Raj wrote: > On Fri, Apr 26, 2019, at 8:14 AM, Alain Kohli wrote: >> Hi >> >> I have hyperkitty running and noticed that the process 'python manage.py >> runjobs minutely' is running for over 70h now and is constantly using >> 100% of a CPU core. That can hardly be intended, but I don't know why >> it's doing that. As far as I could see, this job mainly updates the >> search index. Running 'python manage.py rebuild_index' only takes about >> an hour, though, so I don't see why this would take so much longer. The >> text search is not working in the first place, so that might be >> connected as well. I'm currently running the v1.2.2. > Do you see any errors in the logs? > >> Regards, >> Alain >> _______________________________________________ >> 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: Postorius claims 2 messages held when there are none - out of sync

by Ken Alker

--On Monday, June 26, 2023 8:24 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 12:01 AM, Ken Alker wrote: >> When I view a list via Postorius the "Held Messages" menu item has an >> inverse-red-"2" next to it, as if there are two held messages. There >> are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the >> held messages should be in "pipeline" subdirectory). When I click on >> "Held Messages" I get "Something went wrong" followed by "HTTP Error >> 500: {"title": "500 Internal Server Error"}". How do I fix this? > > The held messages are not in any queue. They are stored in Mailman's > var/messages/ hierarchy. They can be examined with `mailman qfile` Is the var/messages hierarchy also where all the archived emails are stored for future viewing via the web interface? > Also, there is a long thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be > relevant. I have never used the mailman shell before, but based on the referenced thread I learned to do this (note that the thread also taught me how to rewrite it to narrow down to just the list with issues so I didn't delete held messages in other lists, if my case): for verification: venv) mailman@speedy:~/web/logs$ mailman shell -l sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list >>> requests = IListRequests(m) >>> first = True >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(m.list_id) ... print (f"""\ ... Sender: {data['_mod_sender']} ... Subject: {data['_mod_subject']} ... Date: {data['_mod_hold_date']} ... Reason: {data['_mod_reason']} ... """) ... and then to delete the two messages: (venv) mailman@speedy:~/web/logs$ mailman shell -l sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list >>> requests = IListRequests(m) >>> first = True >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(m.list_id) ... print(f'request id: {request.id}, deleting') ... requests.delete_request(request.id) ... sbarc-list.lists.netlojix.com request id: 27, deleting request id: 28, deleting >>> The result of this, however, was that the web interface still claimed I had two held messages. I wasn't sure if there was some cron-type "sweeper" process I had to wait to auto-run or if I had to manually do something to create an update. I then realized that the sample script had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered the script (but it didn't spit out that it deleted anything this time) and got an error when I did the commit. So, I figured the messages HAD been delete and the commit wasn't really necessary. When I went back to the web interface, the number of held messages was at 0 and I no longer get the original error when clicking on "Held messages", so my issue is solved. But this does leave me with some educational questions: 1) Did I affect something somehow with my "commit", or was there a job that cleaned things up (if so, what job)? 2) Is the "commit" even necessary (I saw it in someone else's script in the thread)? 3) Is there a way to save a script and then execute it via shell rather than typing it in every time (it appears from the examples that people are typing them in every time, which is super tedious; I didn't paste for fear of doing something damaging, but maybe that would work)? 4) Are the request.id's of the messages dynamic/changing, or are they fixed for life? I thought I'd delete based on exact request.id without looping but I was afraid maybe they were changing over time and that this wouldn't be a good idea. Might be nice to know for the future. Thanks for the guidance! Ken

2 years, 2 months

[MM3-users] Re: hyperkitty_import Unicode Errors

by kdhall＠binghamton.edu

Stephen J Turnbull wrote: > On 2023-05-07 07:39 Mark Sapiro writes: > > On 5/6/23 11:27, Dave Hall via Mailman-users wrote: > > > django.db.utils.OperationalError: (1366, "Incorrect string value: > > '\xE1\x90\xA7\x0A\x0AO...' for column > > mailman3web.hyperkitty_email.content at row 1") > > Is there a known cause for this? > > Almost always nonconforming user clients. You write "frequently", but > I'm > guessing it's maybe 1% or 2% of all the messages, right? I suspect it's > a > particular author or institution using such a client. > > Is it fixed in some release more recent than 0+20180916? > > This is almost surely not something we can fix. Based on the error, > it's in third > party code (Django) that we import. It's possible we could provide a > more explanatory message, but the only thing we can sensibly do is hold > the > message for an admin to edit it by hand. As long as the text in > question and the > Content-Type header aren't too sensitive, we can help with identifying > charset > (often UTF-8 as Mark suggests but why someone would be encoding FINAL > MIDDLE DOT is a mystery to me). > > I'm not sure what's going on here. My first thought is the database is > > MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database > > column charset definition is utf8 and not utf8mb4, but > > '\xE1\x90\xA7\x0A\x0A' is the 3-byte UTF-8 encoding for CANADIAN > > SYLLABICS FINAL MIDDLE DOT ('\xE1\x90\xA7') followed by two > > newlines. so I'm not sure what the issue is. > > I'm guessing home-made client, possibly Asian or a spammer, which > provides no > content-type header. Even today I see raw 8-bit encoded text without an > encoding > spec from legitimate Japanese and Chinese sources, and of course with > spammers > all bets are off -- they might even do it deliberately to crash filters. I have located an email with a similar error in a V2.1 .mbox file. The post was by a faculty member in my organization using Thunderbird 60.2.1 on a Mac - OSX 10.13. The list was used to correspond with students taking a programming course. The message body is multi-part MIME with two sections: This is a multi-part message in MIME format. --------------4BAB6CD38F4927471D366565 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit and --------------4BAB6CD38F4927471D366565 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit The hexadecimal sting \\xEF\\xBB\\xBF\\xEF\\xBB\\xBF appears one place in each section. I'm not sure exactly what this means. I did check my MariaDB (as Mark hinted) and found that it set for utf8 rather than utf8mb4. I'd be willing to change this, but would I also have to do something to update the Mailman databases since those tables are already created? Thanks. -Dave

2 years, 4 months

[MM3-users] Re: Postfix SMTP REJECT non-subscribers

by Odhiambo Washington

On Wed, Jul 10, 2024 at 3:48 PM Matthew Blissett via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi, > > > With Mailman 2, I have configuration and scripts to reject non-members > from posting to lists _during the SMTP connection_. This is better than > bouncing (no backscatter), better than discarding messages (the user > finds out) and better than moderation (spammy messages aren't forwarded > to external email systems). > > > The configuration and scripts are described here: > https://code.launchpad.net/~jimpop/mailman/check_subscriber > > > Is anything like this built-in to Mailman 3? I cannot find it in Gitlab. > MM2 stored the subscribers' addresses in the /PATH/TO/mailman/lists/LISTNAME/config.pck. MM3 has the subscribers' addresses stored in your favorite DB backend (PostgreSQL, MySQL.Sqlite). So you'll need to do an SQL lookup for the subscribers. I am wondering why you should waste those CPU cycles instead of just having MM3 do its work: So, when "Default action to take when a non-member posts to the list = Discard", how does the user find out? I suppose it's an MH370 kind situation :( -- 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, 2 months

[MM3-users] Re: Importing users and mas settings "Moderation Action"

by Mark Sapiro

On 5/19/22 06:17, bob B via Mailman-users wrote: > I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? Correct. > But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? Yes. > I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? That's correct, and that was also the case in Mailman 2.1 . > is there a way to change all their user's "Moderation Action" for a list in bulk? You could do it with `mailman shell`, but not in Postorius. > So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user? If you are a list owner whose only access is via Postorius, that's correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: MASS mailing list import - 900 ezmlm lists to Mailman

by turnbull

Couple of points: 2023-04-20 07:37 に grant(a)horizonsunlimited.com さんは書きました: > I'm looking to have some time for me. Time to get out and ride my > motorcycles more. :) Mark takes a month off every year to ride his bicycle into the wilds. We definitely encourage our admins to ride more! > 3: Batch script to mass convert - not me! I suspect I COULD - but the > time involved is no way worth it to me. As long as you have access to the (*nix) host, I suspect we'd be happy to write the script. The problem is the ezmlm list config database. > Hosting the lists is a thought, but again, trying to reduce costs, and > since my server already HAS mailman 2, that seems unnecessary. > I did get a couple of DM's re hosting a list, one even suggested they > can do the conversion, so will check out if they will do the conversion > for a reasonable fee. I understand that your users are unlikely to be massive donors, but maybe you could spend the time saved on administration on applying for grants. I wouldn't be surprised if the telephone operators at an organization like the Gates Foundation have authority to grant a $9.98/month hosting service. :-) Good luck on finding a good deal, and let us know if we can help.

2 years, 4 months

[MM3-users] Re: converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Lucio Chiappetti

Dear Mark, thanks for your interest. On Fri, 11 Feb 2022, Mark Sapiro wrote: > This may actually be a bug. I'll have to think about that. I've filed > https://gitlab.com/mailman/mailman/-/issues/978 on this. > This is https://gitlab.com/mailman/mailman/-/issues/794 (still open) Given the time needed to solve the issues (I will anyhow notify the site administrators, hopting they would update mailman when/if resolved), this means we have to find a workaround. > And those non-members all have there moderation action set to Defer > which means their posts will be accepted but the additional checks such > as too big, etc. will still be applied. not sure what you mean by "defer". The non-member options I see are called List default -- follow the list's default member action. Hold -- This holds the message for approval by the list moderators. Reject -- this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. Discard -- this simply discards the message, with no notice sent to the post's author. Accept -- accepts any postings without any further checks. Default Processing -- run additional checks and accept the message. > If they are nonmembers, you can accept the post and set moderation > action in one operation in Postorius, but the regexps in > hold_these_nonmembers will still take precedence. OK, I've found where to do it, it requires to select the held message and scroll to the bottom then set Moderation from a menu. But if hold_these_nonmembers takes priority this will be uselesws in the current setting. > I'm not sure what you are looking at here. Imported nonmembers should > all have moderation action set according to which *_these_nonmembers > they came from. Imported members should have their moderation action set > to Defer if they were unmoderated and if they were moderated, it should > be set based on the 2.1 list's member_moderation_action. I go to the non-member list, select non-member options and at the bottom see an item Administration options Moderation. The possible values are those I pasted above. The actual value for most of the imported non-members is "Default processing" while it is "List default" for thoase automatically added afresh, It is "Discard" for a number of imported non-members with spam-looking addresses (I guess they were in some other *_not_members part of the standard 2.1 antispam ... I can't recall me doing something on those) Side question: is there a way to operate IN BULK on non-members ? Like it is for members (I exported them to CSV). >> - if so, how can we do it automatically for all 189 entries ? >> - or move back the 189 addresses to accept_these_nonmembers ? > Yes, move them back. I am not so concerned of these 189 (or better of the 189 minus the discard ones which should stay) ... anyhow moving them back will be uncomfortable if there is not a bulk operation tool. I am more concerned of the new cases automatically added. Our member list includes 1043 addresses. Of these less than 20 use an external address (say gmail), so they post "from home" and will pass. 194 addresses are of the form name.surname(a)inaf.it (these are likely to be recently hired staff, who have and use onlyu the organization-wide address). All the rest (so still more than 800, can't really ask all of them to re-register (*)) are of the form username(a)institute.inaf.it (and it won't be easy also to bulk-delete and bulk-resubscribe because of the inhomogeneous mapping of username to name.surname. Of these about 800 some are lurkers and are no problem. Some are frequent posters and remember to post from username(a)institute.inaf.it and are no problem. Other may post from an alternate address (maybe even the old address exists as a receiving-only alias), and in this case with the current arrangement they will bo on hold every time. I guess we should wait for the solution of issue 794 (*) by the way do you confirm that if one is subscribed to a list with an address (be it bulk subscription, import or new fast subscription), this person CANNOT change their settings (or address) unless one does a "sign in" to a (Postorius) account ? > It is because all the legacy *_these_nonmember actions are applied > before nonmember moderation checks, so if an address matches a regex in > hold_these_nonmembers, the post will be held regardless of the > nonmember's moderation action. > Addresses still work, and accept_these_nonmembers takes precedence over > hold_these_nonmembers just as in MM 2.1. This was not my impression when I ran a thorough test of 12 cases. Except the obvious case of the subscriber posting from the subscription address, all messages went on hold. Whatever the non-member moderation would be (even if set to reject ! ... but that makes sense if *_these_nonmembers prevail on non-member options), and even if the address was set explicitly in accept_these_nonmembers (should I delete it from the non-member list ?) What is the actual order (or flow chart) of choices ? *_these_nonmembers in the order listed in the page (within each in the order of occurrence of regexp's) then non-member options ? If I have Name.Surname(a)inaf.it in accept_these_nonmembers, then hold_these_nonmembers set to ^.+@.+\.it ^.+@.+\.tng\.iac\.es what do you foresee ? And for different regexps, will processing terminate at the first non-matching one, will they be ANDed or ORed, or what ? I am reluctant to accept inconditionally ^.+\..+(a)inaf\.it (they may be falsified, only the check on their presence in the other list (issue 794) I guess I should remove the ^.+@.+\.it regexp AND AT THE SAME TIME change the Default action to take when a non-member posts to the list to Hold instead of Discard. This way we'll have to check spam (instead of having it auto-discarded), but if people with alternate addresses post, once they are entered in the Non-member list they can be authorized to pass for the future ... .. would it work ? -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html

3 years, 7 months

[MM3-users] very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

Hi all: I need to provide the list moderators a way to change the moderation flag for users from whichever it is (normally "list default processing") to "hold for moderation" and viceversa (to "list default" or to "accept") I understand that it could be done via console script (That's the way I did on mailman2: I made two commands using "withlist", one to hold, moderar.py, and other one to accept, desmoderar.py. I show you below) But I think I'm not the only one that could use as an improvement a way to do this on postorius/web. Before to trying implementing them on mailman3, I beg you to tell me if they could do that on mailman3. Thanks in advance. ****************** (moderar.py) #! /usr/local/bin/python # # script via withlist para moderar a pelo # """moderar un miembro. Save as bin/moderar.py Run via bin/withlist -r moderar <listname> <member> """ from Mailman import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() ****************** (desmoderar.py) #! /usr/local/bin/python # # script via withlist para desmoderar un miembro # """desmoderar un miembro. Save as bin/desmoderar.py Run via bin/withlist -r desmoderar <listname> <member> """ from Mailman import mm_cfg def desmoderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, False) mlist.Save() mlist.Unlock() --

4 years

[MM3-users] Re: Docker, Mailman 3, templates and list user accounts

by Abhilash Raj

Hi, On Mon, Aug 7, 2017, at 06:06 AM, Henrik Rasmussen wrote: > I used Docker to installed Mailman 3. > > The top header of the web interface says "Example.Com" while linking to > the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a > post[1], Mark Sapiro referred to the template system in Mailman 3 by > pointing out that "a custom template can be put in > var/templates/site/en/welcome.txt or > var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> > or > var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> > where var is Mailman's configured var_dir". I believe this refers to the > mail templates. Yes, these are email templates. > > 1) Where do I change the similar template system, for the web > interface, without breaking a laver upgrade? I am not sure if you can do that for now without tinkering with the source code. > 2) How do I change the site name in the top of the web interface on > Mailman 3 to my subside and ? When you deploy the web interface, the domain it is being served from is used at the top of the web interface. It is defined by SITE_ID in the settings.py file for Django (or settings_local.py if you are using the container images). The default value is set to 1 and points to example.com. In the newer versions of Container Images, the SERVE_FROM_DOMAIN environment variable's value will replace the `example.com` domain and you will be able to see that instead of example.com. For now, you should just login into the admin interface at /admin/ and just create a new Site model. And then use the id of that Site in your Django's settings.py. Each domain that you add gets their own id and depending on which domain you are serving from, you can set the SITE_ID in the settings. Mailman 3 supports multiple domains at the same time. > [1] > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > The Mailman command in Mailman Core doesn't seem to have a command for > listing the accounts users have created by using Sign up in the web > interface, so I believe that accounts may be created in the webinterface. The Core and and Web frontend handle users separately. Ideally, a user shouldn't have to worry about the Core ever and only interact with the Web Interface. > Is there similar commands for the web interface like the mailman commands > for the Mailman core? You can interact with the Django shell to get almost any internal data structure. But you can go to the admin interface at /admin/ and you will find the list of users there along with a whole lot of other information. > > Regards, Henrik Rasmussen > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 1 month

[MM3-users] Re: Some doc updates from Fedora install experience

by tlhackque＠yahoo.com

A number of the Python module installs generate "PEP 440" warnings, which I ignored. There are warnings on some components - and then a failure to build HyperKity looking for redhat-hardened-cc1. Add redhat-rpm-config to the dnf install to get that. setup for hyperkitty - cd hyperkitty, not mailman-hyperkitty under "setup a mail server", it says: You will also have to add some settings to your django configuration. The setup instructions are provided in django’s email documentation. OK: What file do I put them in? Perhaps this is mailman-suite/mailman-suite_project/settings.py? That file is a mix of stuff that an admin would want to change, and application configs for developers. Perhaps that can't be helped - but could the admin settings come first? What's a SITE_ID ? There's no comment. It would be nice to have a list of what settings (there are a zillion of them) need to be changed to get going. Several are authentication items (passwords, usernames, urls). A cross reference that says across the whole project, where do you need to put them would be a big help. E.g., pick your REST api url, and put it in the following files: ... Out of time for now. Seems like sorting this out will take more work. BTW, I've replicated this on a Fedora 23 system with Python 3.4... (VM in notebook PC for the waiting room :-)

8 years, 2 months

[MM3-users] Footer question...

by David Partain

Hi, Background: I have a painful mailman3 installation based on ubuntu 18.04 packages, a mistake I regret but have to live with until I can finish a fresh install of the latest. Currently running on mailman 3.1.1-9 and python-django-mailman3 version 1.1.0-4 (if that matters). I migrated > 1200 lists from an old mailman2 installation. That brought along all of the footers (naturally), and now I'm trying to get rid of them but failing miserably. I've spent a fair bit of time reading archives of this list, but I'm still stuck. Here's what's configured... In /etc/mailman3/mailman.cfg: -------------------------------------------------------------------------------------------------------------------------- var_dir: /var/lib/mailman3 # Root directory for site-specific template override files. template_dir: $var_dir/templates -------------------------------------------------------------------------------------------------------------------------- In that directory, list-specific directories like: /var/lib/mailman3/templates/lists/list.mydomain/ and, as an example, en/list_member_digest_footer.txt For the migrated lists, that might have: ------------------------------------------------------------------------------------------------------------------------- _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} ------------------------------------------------------------------------------------------------------------------------ Based on what I've read elsewhere, my first attempt was to create an empty file doing 'cp /dev/null list_member_digest_footer.txt' to replace the one installed in migration. That had no effect. As a shot-in-the-dark, I did 'cp /dev/null list:member:regular:footer.txt' to see if that might have some effect. Nope. I suppose some decision is made earlier in the process to tack on the footer, so these files I'm manipulating have zero effect. Anyone have suggestions of what I can do? Thanks in advance. David

4 years, 1 month

[MM3-users] Re: Blocked by Hotmail

by Mark Sapiro

On 1/22/21 4:11 PM, Tom @ Gather wrote: > I am getting rejections from Hotmail > > Jan 18 14:42:22 mail postfix/smtp[6571]: 046713F914: to=< > helen_maryd(a)hotmail.com>, > relay=hotmail-com.olc.protection.outlook.com[104.47.58.161]:25, > delay=0.14, delays=0.06/0.03/0.04/0.01, dsn=5.7.1, status=bounced (host > hotmail-com.olc.protection.outlook.com[104.47.58.161] said: 550 5.7.1 > Unfortunately, messages from [167.99.151.239] weren't sent. Please contact > your Internet service provider since part of their network is on our block > list (S3140). You can also refer your provider to > http://mail.live.com/mail/troubleshooting.aspx#errors. [ > BN8NAM11FT014.eop-nam11.prod.protection.outlook.com] (in reply to MAIL FROM > command)) > > I have submitted a ticket to > https://support.microsoft.com/en-us/supportrequestform/8ad563e3-288e-2a61-8… > > Not sure why they are blocking me. Not on any other blacklists per > mxtoolbox... > > Anyone else experienced this? How to resolve? Yes, I've had this block at times. All the affected servers subscribe to SNDS and JMRP and never receive any bad reports. The process is to submit the form as you have done. This may result in mitigation without further action on your part, but if they reply to the ticket with Not qualified for mitigation (IP address) Our investigation has determined that the above IP(s) do not qualify for mitigation. The next step is to reply to that with an explanation of what you do. Here's a copy of such a reply: ------------------------------------------------------------ Beginning around 14:43 -0500 on Dec 31, mail from mail.python.org (IP 188.166.95.178) to various hotmail.com, outlook.com. live.com, etc. addresses is being blocked. A typical response to such mail is Jan 4 19:11:49 mail postfix/smtp[14283]: 4D8tGD3YZSzpFbf: to=<marksapiro(a)hotmail.com>, relay=hotmail-com.olc.protection.outlook.com[104.47.17.161]:25, delay=0.69, delays=0.55/0.01/0.11/0.03, dsn=5.7.1, status=bounced (host hotmail-com.olc.protection.outlook.com[104.47.17.161] said: 550 5.7.1 Unfortunately, messages from [188.166.95.178] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [VI1EUR05FT004.eop-eur05.prod.protection.outlook.com] (in reply to MAIL FROM command)) This mail is virtually all messages to confirmed opt-in subscribers of various python.org email lists. We do not send spam and we have various filters in place to block spam from reaching these lists. We publish SPF and DMARC records for our domain and DKIM sign our outgoing mail. We subscribe to your Junk Email Reporting Program (JMRP) and Smart Network Data Services (SNDS) and see no reports or unusual complaint rates. Our IP 188.166.95.178 is not found on any blacklists checked at <https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a188.166.95.178&run=…> Please stop blocking our mail. ------------------------------------------------------------ This usually works. If not, you just have to persist. > My mail server is on Digital Ocean if that makes any difference. It may. All of my recent blocks have been DigitalOcean servers including mail.python.org, but I think I've had this in the past from non- DigitalOcean servers. -- 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: Subscribe to a list on a Mailman3 server without account registration

by Mark Sapiro

On 6/6/23 01:07, c.buhtz(a)posteo.jp wrote: > Hello, > I might miss something here but I'm confused about a difference between Mailman2 and 3. > > On MM2 I just subscribed a mailinglist via my EMail address. I didn't need to create an account on the MM2 server first. > But it seems on MM3 it is otherwise. For example I use MM3 on python.org. It seems I have to register first before subscribing to a mailing list. > https://mail.python.org/mailman3/lists/twisted-web.python.org/ You can subscribe without creating an account. You do need an account if you want to manage your subscription via the web UI or to visit private archives, but not to just be a list member or visit public archives. The issue with the https://mail.python.org/mailman3/lists/ lists is that the anonymous subscribe form which looks like: ----------------------------------------- You can also subscribe without creating an account. If you wish to do so, please use the form below. Your email address __________ Your name (optional) __________ ----------------------------------------- has been removed from list info page because it was being abused by people attempting to subscribe third parties. You can still subscribe without creating an account by emailing twisted-web-subscribe(a)python.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Problems with signed messages from Apple Mail

by Mark Sapiro

On 11/12/21 6:06 AM, Rainer Herbst wrote: > Dear all, > > after upgrading his Mac to MacOS 12.0.1 Monterey, one of our users can > not send send signed messages to lists using Apple Mail v. 15.0 > (3693.20.0.1.32). > > mailman3 denys the delivery of the mail with error message: > host 172.19.0.4[172.19.0.4] said: 501 Message has defects > (in reply to end of DATA command) > > I.e. mailman does not process the message, but rejects it already in the > incoming smtp session. Is that a known issue? Incoming SMTP is relaying the message via LMTP to Mailman's LMTP runner which in turn parses the message using Python's email.message_from_bytes() method and the resultant message has defects. Rejecting such a message outright as we do may be too harsh, but it is hard to say without seeing the message and what Python's email package thinks the defects are. This could be a bug in Apple Mail or in the Python email module. If you wish to see the details, you could do the following in `mailman shell` ``` import email from mailman.email.message import Message content = b"""\ (paste the raw message here) """ msg = email.message_from_bytes(content, Message) msg.defects ``` This will show you what the defects are. -- 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: Installing mailman 3

by Rafael Mora

Why isn't it sending emails? What do you think? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' > > > This looks good to me. > > > What should I use in user and password?? Does Django use postfix to send > the email??? > > > I think you don't need a password and username as long as your postfix is > configured to relay local emails without authentication (which it is by > default if you installed from distro packages and if you haven't changed > the settings). > > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) > escribió: > > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > _______________________________________________ > > > Mailman-users mailing list > > > mailman-users(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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 > > > -- > thanks, > Abhilash Raj > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: templates

by Mark Sapiro

On 5/5/23 15:27, Christian via Mailman-users wrote: > Okay I sent a test message this morning and subscribers are reporting they > did not receive it. The smtp.log shows 'smtp to > degrowcali(a)lists.ccalternatives.org for 25 recips, completed in > 3276.275292634964 seconds' (see below) > I alone received it however and it is listed in the archive. Below is the > excerpt from smtp.log. Two of my 5 lists are exhibiting this behavior, while > 2 other lists are working normally. Please advise. Thank you. That message says Mailman delivered the message for 25 recipients to the outgoing MTA. If only one recipient received it, you first need to check the outgoing MTA's logs to see whether the message was delivered to the recipient's mail servers or not. Those logs should indicate that either the message was delivered to each recipient's first hop mail server or not. If not, there should be a reason why in the logs. If the message was delivered, it could have been rejected by an MTA further down stream in which case a DSN message should be returned, but possibly not for days, or it could have been delivered to the user's spam/bulk/junk/promo/whatever folder or silently discarded. Do your list's do bounce processing? If so, what's in Mailman's bounce.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Deleting moderation requests in database

by Joachim Schrod

OK; so I have an old mailman instance where I can't confirm unsubscribe moderation requests. mailman3 core is still sending me daily notices about that moderation requests; I want to get rid of them. (By now, I unsubscribed this test subscriber, so these messages are garbage anyhow.) First: I assume that all information about moderation is in the database mailman3. If that's not the case, please tell me. Second: I tried to determine what DB records are involved in a moderation, so I can delete them. I found the following records: -- workflowstate: records about pending confirmations; with a token as primary key. -- pended: records that references that key, with an id. -- pendedkeyvalue: records with additional information about the request, referenced by the id of table record `pended'. In addition, there is a record in table `member' for that mailing list, with an UUID in `_member_id' that isn't stored in any other record in the database elsewhere. (This is a test mailing list that currently has *no* members; thus this record might be relevant.) Where is this `_member_id' UUID used? My question is: Which records do I have to delete to get rid of the daily pending unsubscribe moderation notices? 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

9 months, 2 weeks

[MM3-users] clean up spambot generated accounts

by Johannes Rohr

Dear all, I'm trying to find a way to clean up hundreds of spambot generated accounts on my system. I was pointed to this script that should be capable of doing the task: https://www.msapiro.net/scripts/clean_users.py However, it seems outdated. First, the path to the interpreter is not what I find on my mailman3 installation. It says: #! /opt/mailman/mm/venv/bin/python However, the python command is located in /opt/mailman/venv/bin/python instead, no "mm" After fixing this, the script still throws an error: (venv) mailman@ida:~$ clean_users.py Traceback (most recent call last): File "/usr/local/bin/clean_users.py", line 55, in <module> django.setup() File "/opt/mailman/venv/lib/python3.10/site-packages/django/__init__.py", line 19, in setup configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 102, in __getattr__ self._setup(name) File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 89, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 217, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' Can somebody explain to me, why this module is not found and what I can do to fix it, if anything? Thanks a lot in advance! Johannes

6 months, 3 weeks

[MM3-users] How can i suppress sending moderation mail to all owners?

by Stephen J. Turnbull

Markus Grandpré writes: > How can I configure the list settings the way that emails intended > for moderators are delivered only to them, and not to the > owners/administrators of the list? If the owners are few and well-trusted, you could make them superusers. There are a lot of reasons why that is unattractive, of course. I think (without looking at the code) that the change you want is about 4 lines in two files if it's a global configuration. It becomes somewhat more complex if a list configuration. (Plus documentation, of course.) Both forms seem quite simple. I would definitely be willing to review a merge request if submitted. It would also be a suitable "easy"/"beginner" task (eg, to qualify for GSoC) in the tracker. I'm a little reluctant to do it myself, because the pain point a couple of my large clients had is different, and more complex. Some of their owners wanted to delegate owner-only capabilities like mass (un)subscribe to their moderators, but were uncomfortable with making them owners. So I would prefer to look into that code when I have time to do the more complex task, and the "who gets moderator mail" patch could ride along "for free". -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month

[MM3-users] Re: more about spanish translations

by Guillermo Hernandez (Oldno7)

On 19/2/21 18:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 19/2/21 18:26, Mark Sapiro wrote: >> On 2/19/21 5:09 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> I would like to translate it all, but as said, I cannot find where >>> to do >>> it. I wonder if it's comes from another package as allauth or something >>> like this. >> >> Yes, it does come from allauth, specifically >> allauth/templates/account/email/email_confirmation_message.txt. >> >> The Spanish allauth message catalog is at >> <https://github.com/pennersr/django-allauth/tree/master/allauth/locale/es/LC…>. >> >> I suppose you could submit a pull request to update it. >> >> Or you could just update your local file in your installation. >> > I will do both: first translate locally. Test it, and then see if I > can share it with the rest of the people (and then I will not have to > worry to maintain it when next upgrades come) I went first with the translation in github and the pull request. Let's see if it's approved and then how to upgrade locally. > > Thanks a lot, as always, Mark. > _______________________________________________ > 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: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:13 AM, mm3(a)steele.com wrote: > I have found work around for the settings issue but continue to have an issue with archiving new messages. New messages are stuck here; > > mailman3/mm/var/archives/prototype/[listname]@[domain]/new They aren't `stuck` there. That is where they are archived by the prototype archiver. This is separate from HyperKitty. > I have added this to my mailman.cfg: > > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /usr/local/mailman3/mailman-hyperkitty.cfg > > And created the "/usr/local/mailman3/mailman-hyperkitty.cfg” as such: > > base_url: http://localhost/archives/ > api_key: [key that matches “MAILMAN_ARCHIVER_KEY” in my settings.py] > > Some documentation says that the url should be "http://localhost/hyperkitty/ but url generates a page not found error on my setup while the archives are available at the “archives” url. > > But, now that I think about it, "localhost" doesn't make sense here because I am virtual hosts and "localhost" will probably just connect to the first virtual host rather than the mailmanweb virtual host. > > Any advice on what do do here? Set base_url: in /usr/local/mailman3/mailman-hyperkitty.cfg to a url that will reliably access HyperKitty, probably the same base URL that a user with a web browser would use. -- 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: hooking up mailman and sendmail

by John Covici

On Sun, 14 Mar 2021 14:05:33 -0400, OK, thanks a lot. Mark Sapiro wrote: > > On 3/14/21 7:56 AM, John Covici wrote: > > That post does not answer my question, it applies only to mailman2 and > > is a big mess. I was hoping to use lmtp, which sendmail will use and > > mailman seems to have some facilities to use it as well. > > > What that post describes is for Mailman 2.1, how to hijack Mailman's > generated aliases for Postfix and apply them to sendmail. The hope is > that someone who understands how to configure sendmail can take those > ideas and apply them to the Postfix transport and domain mappings > generated in var/data/postfix_lmtp and var/data/postfix_domains to > generate what is needed for sendmail. > > Hopefully, once people figure out how to do this, they will inform us of > the solution and we can update the docs. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ > -- 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

4 years, 6 months

[MM3-users] Re: Mailman 3 deployment: ok to use same database instance for core, web, and hyperkitty tables?

by Andrew Hodgson

Stephen J. Turnbull wrote: >s.dobrau(a)ucl.ac.uk writes: > > We are currently working on a migration plan for Mailman -> Mailman > 3. We have around over 3000 mailing lists with a total of 50K > members >Medium-size. I guess a 2-CPU/4GB Linode or similar should handle the Mailman load (including Postorius and HyperKitty), you might want more memory and maybe more CPUs if you're running the RDBMS on the same host. In the 23k lists/50k users/100k inbound messages/day migration described below, >we ended up reconfiguring the VMs 3 times before declaring the system stable. IMO the 2 x 8CPU/16GB final setup was way overpowered for the need, but we didn't try to calibrate finer than that. Yep, I have helped a migration with around 150 lists but not as much archived data, and ended up with a 2 CPU with 8GB machine. I think we could have gone lower, but found we needed the larger VM to help us import the archives. I used a managed PostGreSQL instance from Amazon for the database. > > Our plan is to have core+web (instance 1) and Hyperkitty (instance > 2). With the archives on the FS local to the Hyperkitty. >The archives are in the database as BLOBs. There's no reason to have a separate instance for HyperKitty. It's not obvious to me that you need more than that 2x4 Linode for both Mailman and RDBMS, but if you're going to split it's Mailman vs RDMBS, not Mailman vs HyperKitty. I would agree. I think the issue here is there are several ways of splitting out Mailman people get bogged down in whether they should run separate parts on different instances. In my view I have always ran Mailman, Postorius and Hyperkitty on the same host and I think it works better that way. For example, if you run Mailman and the web components on different hosts, you need to make sure the Mailman REST interface is secured, whereas if its on the same host then the REST interface can just listen on localhost. The Dockerised instances do use separate containers for Mailman Core and the web components, but that is the only real time I have seen the components split. > > And all 3 tables (core, web, Hyperkitty) pointing to the same > database on a remote SQL (mysql-enterprise) instance. Using class > mailman.database.mysql.MySQLDatabase (and whatever necessary on the > Django/Hyperkitty instance). >Make sure your MySQL database(s) for Mailman are configured with the utf8mb4 option for 4 byte UTF-8 support, or it will choke on emojis and the like. I don't think there are any other gotchas for MySQL. Are there any performance benchmarks for running MySQL vs PostGreSQL? I tend to fall back to PostGreSQL because it seems to be what is used in a lot of places, I have never recommended going with MySQL for a Mailman instance. >Note there are a lot more than 3 tables in Mailman's databases. The "traditional" configuration is a "mailman" database for core and a "mailmanweb" database for Django and the archives, but Mark says that as the tables are disjoint across Mailman, Django, and the archives there's no reason not to use a >single "mailman" database for all of them. I believe that's how this list's host is configured. Yep, the original installation guide created one database for Mailman and the tables for all components are in the same database, this was how my larger install was done. Later revisions of the guide have us split the core vs web components to different databases, I don't think there is any performance hit either way by doing that. >Importing list configurations, users, and subscriptions into Mailman 3 is pretty fast, as long as you're not using the stock Postfix support.[2] The problem is that generating the Postfix alias files for the lists seems to be noticably linear in number of lists, which means it's quadratic for the mass import. IIRC with >5000 lists you'd be looking at >1m/list just to keep regenerating Postfix's alias database, ie 5000 minutes. I found two solutions, both of which required patching Mailman. I hope to get both into the next release. >I think we got it down to <5s/list, for 5000 lists that's < 1hr. That is very interesting I had a similar issue with the Postfix alias generation in my larger setup but didn't have time to identify the root cause. In the end I used Exim sending all mails for the list domain to Mailman which is the setup I use elsewhere and it doesn't rely on the alias file generation. >Importing archives is ... yeeech. The client decided they didn't want a ton of archives anyway (you know corporations, if it's not required by law, shred it after 6 months). I don't recall the size estimate accurately but we kept 6 months X 4500 lists, maybe 100GB out of 2.3TB of mboxes. That took 24 hours to >import into HyperKitty, without doing the full-text indexing. I do know the original conservative estimate was 20 days to import the whole 2,3 TB. The full-text indexing took more than a week if I remember correctly. Yes, I had the same problem with the archives. I did import all the archives, in our case it took us several months to get the archives in so as not to stress load on the box. Full text indexing really caused an issue for me, I ended up disabling it for the time we were importing archives then generated a clean index once the archives were imported. This wasn't a good user experience and I would probably plan this out better next time. >It's also quite possible to migrate incrementally, a few lists at a time. Mailman 2 and Mailman 3 can coexist happily on the same host. >Mark can advise on that, I think. Its worth noting this is more difficult to do now on Debian/Ubuntu installs as Python2 has been removed. This was something I ran into myself when trying to co-exist both installs on the same box. Andrew.

1 year, 10 months

[MM3-users] Re: Header and footer templates in MM3

by Mark Sapiro

On 1/19/20 1:15 AM, Gila Halpern wrote: > I read the earlier message from Peter Mueller about message decoration, and > where the templates are in the file system. However, when I edit the > header and footer templates in Postorius, those templates do not appear in > the location specified. Should I be looking somewhere else? The templates created in Postorius are created in the postorius_emailtemplate table in Mailman's database and referenced via URLs like 'https://example.com/mailman3/api/templates/list/<list-id>/<template-name>'. I.e., they are not stored in the file system. > (I intend to > write a program to rotate though several headers/footers, so I need to know > where to have it write to.) If Postorius has set a template for a list, it has set the URI for that template and list to one similar to that above and that URI ultimately references the template in the database. You have choices. You can set the templates in Postorius and your program can do database queries to rotate the template text, or you can set the template URIs via Mailman's TemplateManager to file system paths or not set them and use the default paths (deleting them in Postorius will leave them unset). See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Mark Sapiro

On 8/7/21 4:35 AM, Thomas Möhle via Mailman-users wrote: > Hey, > > I have set up mailman3 with mailman3-web on my mailserver and after > upgrading to Ubuntu 21.04 my setup stopped working. In what way? Do list posts get delivered? What works and what doesn't? What are the observable symptoms for things that don't work? > I can see repeating > log entries of mailman trying to reach something within hyperkitty and > getting an error. The same constant repeating cycle of log entries is > visible in my log files. It appears from your logs that Mailman core's attempts to reach the hyperkitty api may be failing. Mailman core uses the mailman_hyperkitty module to communicate with the hyperkitty api to get the url at which a message will be stored and to deliver a message to hyperkitty. This may not be working. There are probably unarchived messages in Mailman's var/archives/hyperkitty/spool/ directory. What do you get for example if you go in a web browser with hyperkitty running to https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… And please don't post secret keys and change the value of api_key: in mailman-hyperkitty.cfg and the corresponding value in MAILMAN_ARCHIVER_KEY in your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Alter Messages: Reply to confusion

by tokyoprogressive＠mailbox.org

> > This is something which is specific to Emails. There is a header called "Reply-To" which is used by email clients to send replies. That is the "default" address a reply will go to when you hit "reply button" in you email client. > > The setting you are talking about can alter the "Reply-To" header in the emails, for whatever reason they might have to do so. Ideally, you don't want to change the settings since it can break things for some of your users who use emails. > Ok, so testing this, I left it as no munging and “reply to@ automatically became the list, which is what I want. The list settings are different for THIS list I guess since your name appears when I hit Reply, but I want it to go to the list so others can benefit and therefore I use REPLY TO ALL. I wonder what setting in this list that was? By the way, I see that my email address in my messages in my list is fully visible. If I want to make it hard for email harvesters, what setting do I use? Thank you again, Abilash Raj. Paul >> _______________________________________________ >> 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

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

by Abhilash Raj

On Tue, Apr 7, 2020, at 3:38 AM, skenny(a)scss.tcd.ie wrote: > Hi, I've been banging my head against the proverbial wall for more than > a day trying to remove nonmembers from a list (I am a Mailman3 and > Python novice so that might account for something, but anyway ...) > According to > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, it should be possible to do: > > MailingList.remove_role('nonmember', 'email_address(a)example.com') > > However I can't get this to work. I think I have manage to track down > all the required imports. This is what I see: > TypeError: remove_role() missing 1 required positional argument: > 'address' Do you have a web interface? Then it should have a way to remove members. If you don't please use the REST API insteadto find a member[1] and delete the membership resource to remove the non-member[2]. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.h… [2]: https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.h… > More digging in the docs seems to indicate that a third parameter is > required - "self". At this point though I am way out of my depth, and > would appreciate any guidance. "self" is basically a placeholder for the object itself and when you call the method, you need to pass an initialized class. -- thanks, Abhilash Raj (maxking)

5 years, 5 months

[MM3-users] Re: Trouble Installing Mailman3

by Mark Sapiro

On 6/5/25 08:40, Henry Hartley via Mailman-users wrote: > > The other thing I had to do that was different to the instructions was to use pip to install setuptools. I got to a point where I had an error message that said "ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0" but when I ran "apt install python3-setuptools" it reported that it was "already the newest version (68.1.2-2ubuntu1.2)". However, running pip install setuptools (on a whim) installed version 80.9.0. After that "pip install mailman" worked. Perhaps I should have known this. I feel that making sure setuptools is properly installed might be something to add to the installation instructions. It depends how you create the venv. `virtualenv venv` will create the venv with `pip`, `setuptools` and `wheel` installed, but our install doc says do `python3 -m venv venv` and that only installs `pip` in the venv. I'll update the doc. > The next step in the instructions has me create /etc/mailman3/mailman.cfg. The first thing in that file is shown as: > > [paths.here] > var_dir: /opt/mailman/mm/var > > Looking in /opt/mailman, there is no mm directory. Should that have been created, or is that something I need to create myself? You need to create it. I'll update the doc for that too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: trying to clean up the "held messages" mess

by Mark Sapiro

On 5/28/21 12:37 AM, Bjoern Franke wrote: > Hi, > > I migrated a Mailman3 installation on Debian10 yesterday evening from > Debian packages to PIP (thanks to [1]). > > I think some bugs which existed before are now cleaned out, but mailman > still threw exceptions when trying to get the "held messages". What exceptions? Note that there is a lot of cleanup in the as yet unreleased core 3.3.5. You might consider installing that. To do so, in your virtualenv as the Mailman user do ``` pip install --upgrade git+https://gitlab.com/mailman/mailman ``` > The amount of held messages is now reduced, but e.g. a list with 120 > held messages before has till 59 held messages. And now I'm confused: > where are they? The held message entries are in the _request table with `request_type` = 1. For those entries, `key` is the message-id and `data_hash` is the `token` in the pended table and the `id` in the pended table is the `pended_id` of the related entries in the pendedkeyvalue table. The message itself is stored in the file system and is pointed to by the entry in the message table with the corresponding message-id. The exceptions you see are because entries are missing from the pended, pendedkeyvalue and/or message tables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't 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/

4 years, 9 months

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

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

2 months, 3 weeks

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

by Mark Sapiro

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

6 years, 7 months

[MM3-users] Better documentation for Mailman Core's config options

by Abhilash Raj

Hey All, For the past few days, I've been trying to improve the documentation style for Mailman Core's config options. Internally, Mailman has all configurations defined in an ini formatted `schema.cfg` file, which serves as a schema for our `zope.configuration` library. We had that file simply embedded in the sphinx documentation previously as a wall of text. I ended up writing a Sphinx (our documentation generator) plugin which parses the config file and presents the same documentation with more bells and whistles so it is easier to lookup and link sections and config options.[1] The process of doing that was fun and I learnt how to write a simple sphinx plugin, so yay! It treats the comments above each config option in the ini file as it's doc and basically generates ReST text that it passes to Sphinx to parse and convert to the markup format that you see in browser. You can look at it in the source repo[2] . Do note that not all sections are documented yet, I am still figuring out what would be a good way to document template sections like `[plugins.master]` and other similar sections of that kind. [1]: https://gnu-mailman--667.org.readthedocs.build/projects/mailman/en/667/src/… ((URL is for the PR, the main doc seems like is serving the cached version from an older build). [2]: https://gitlab.com/mailman/mailman/-/blob/master/_ext/configplugin.py -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Template Ignored?

by Stephen Daniel

That pulls a 404 error. Thanks for the hint. I will investigate. On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 08:04, Stephen Daniel wrote: > > Mailman3 people -- > > > > I created a new list, and used postorius to create a template for " > > list:user:notice:welcome". I then used the mass subscription feature to > > add myself to the list, having checked "pre-confirmed", "pre-approved", > and > > "pre-verified". > > > > I received a welcome message that appears to be the default welcome > > message. It certainly wasn't what I put into my template. > > > > Any suggestions on how I get mailman to use my template? Things I might > be > > doing wrong? > > > What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a > full URL by appending > `/api/templates/list/list.example.com/list:user:notice:welcome` > <http://list.example.com/list:user:notice:welcome> to that > where `list.example.com` is the actual list_id of your list, and go to > that URL, 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 > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 7 months

[MM3-users] Re: Mailman shell tutorial

by Andrew Bernard

Thanks Mark, The omission of the code to make the examples work seems to need correction. Perhaps I can submit an update to the project. Had me scratching my head for a long time. Obviously I knew there were imports etc missing, but what to put? I have this going, and it is great. But I recall seeing something called mmclient or similar which has simple commands like show user, show lists, and so on. Is that still available? Now knowing how mailman shell works, anybody could write their own commands, but I don't want to reinvent wheels. Andrew > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, 11 June 2019 1:26 PM > To: mailman-users(a)mailman3.org > > Perhaps you saw the `command('mailman shell --details')` line in the docs at > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/s > hell.html#getting-detailed-help> > in any case, that requires two things to precede it. The first is part of the > doctest infrastructure and is not evident in the docs. that step is > > from mailman.testing.documentation import cli > > The second step is in the docs and is > > command = cli('mailman.commands.cli_withlist.shell') > > If you do those two steps within `mailman shell`, then the step > > command('mailman shell --details') > > will work, but as I said, this is just the same as doing `mailman shell --details` > at a command prompt.

6 years, 3 months

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

by Mark Sapiro

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

2 years

[MM3-users] Re: Handling of Mail from non-subscribers

by Mark Sapiro

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

5 years, 4 months

[MM3-users] Re: Archives with encoding characters

by Mark Sapiro

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

5 years, 6 months

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

by kisner＠live.com

Mark Sapiro wrote: > On 7/8/22 8:28 AM, kisner(a)live.com wrote: > > I tried to follow that guide ( https://docs.mailman3.org/en/latest/install/virtualenv.html ), but I couldn't get it to work. I'd have to try it again to see where it broke. One thing that I got past was I had to change: > > (venv)$ pip install wheel mailman psycopg2-binary<2.9 > > to > > (venv)$ pip install wheel mailman psycopg2-binary==2.8.6 > > and that got me past that part, > > I don't understand why that would make a difference since the latest > psycopg2-binary<2.9 is 2.8.6 > > but hyperkitty/mailman-web pip install has components that failed to install. I'm not sure why, someone smarter than me could probably have figured it out, but as written it wasn't working for me. > > If you do try again, post the specific issues/error messages and we will > try to help. Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros.

3 years, 2 months

[MM3-users] Re: Member Issue Discovered

by Jörg Schulz

So, the issue seems to be, like in the following scenario We imagine a list server for the domains fruiteaters and meateaters. We have two listadmins, anna (fruit) and carl (meat). They don't share anything. We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. While he can do so using two different email addresses, he cannot do so using wormy wonder <hunger(a)eatall.com> fritz the cat <hunger(a)eatall.com> as from: addresses because all requests will be matched to the one email address. Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. Not optimal for some rare conditions - that's the way it seems to be???

4 years, 10 months

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

by Mark Sapiro

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

2 years, 7 months

[MM3-users] Re: Rootkit issues

by Kyriakos Terzopoulos

Hi Peter, The rootkit had already been removed up to that point. The user of the Blitz process was the mailman user. Taking steps to secure the server more now. On Tue, 17 Oct 2023, 22:23 , <peter(a)chubb.wattle.id.au> wrote: > > > Some more info on the issue after running RKhunter: > > [09:47:54] Warning: Network TCP port 47018 is being used by > > /tmp/.X291-unix/.rsync/c/blitz64. Possible rootkit: Possible Universal > > Rootkit (URK) component > > You need to remove the rootkit. Someone has hacked into your system. > This has nothing to do with Mailman3 as such. > > If you do a > ps axfu | grep blitz64 > > you should be able to find which uid is being used (first column of > output). You'll then be able to find the bits of the rootkit by > looking at that user's processes and open files, and delete them. > > And then you can fix that user's permissions/password so it's less > likely to be compromised again, or delete the user entirely if the > user isn't being used for anything else. > > > -- Peter C > _______________________________________________ > 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 kyriakos.terzopoulos(a)gmail.com >

1 year, 11 months

[MM3-users] question about recommended postfix configuration

by Marc Sluiter

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert. This is recommended: transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost. My first change then was to use “relay_recipient_maps” instead of “local_recipient_maps”, because the domains were also added to the relay configuration "relay_domains". That worked. But then I noticed warnings by postfix about having the same domain in “virtual_mailbox_domains” and “relay_domains”. Made sense again because I used the same domain in my “normal” mail setup (with “virtual_mailbox_domains”) and in mailman. So finally I ended up with adding the mailman files to “virtual_mailbox_domains” and “virtual_mailbox_maps” instead of “relay_domains” and “local_recipient_maps”. Do my findings and changes make sense to you? Or do I miss something important? Good thing is that at least “transport_maps” worked for whatever configuration I used :) Thanks and greetings, Marc

7 years, 11 months

[MM3-users] Re: Importing archive from mm21

by Mark Sapiro

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

1 year, 9 months

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

by Mark Sapiro

On 11/4/21 1:02 AM, Simon Coggins wrote: > > All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914 and this was a fix for that. Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

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

by tokyoprogressive＠mailbox.org

Thank you Mark. I will need to find time tomorrow to create two totally new email accounts that I can use in tests so I do not inadvertently sign up again with the same address. Also will double check my settings. Best regards Paul Sent from my iPhone > On Sep 17, 2019, at 14:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/16/19 9:22 PM, Paul Arenson wrote: >> In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? >> >> 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… >> >> 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" >> >> 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org > > > You have to approve it or the user has to confirm her email address? > Maybe you have to approve it because the lists Subscription Policy is > Moderate. > >> 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? > > > No. They will be a member, they just will not have a Django account that > they can log in to. > > >> 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: >> >> "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. >> To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" > > > Because when you create a Django account, you have to confirm your email > address. > > >> 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! >> To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by >> sending a message to....... I then get a notice: >> >> "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" > > > What is Message Acceptance -> Default action to take when a member posts > to the list ? > > You get the notice or the user gets the notice? > > >> 7) While if they send FROM THE interface it goes through. >> >> 8) What I am confused about. >> >> Signing up for an account should make them a member, right? Subscribing should make them a non member, no? > > Signing up for an account is just signing up for a Django account. You > can sign up for an account and log in and then subscribe to the list. > > Subscribing makes one a member whether or not you subscribe from a > logged in account or subscribe without creating an account. > > >> But here it seems that both make them a non member. > > If an address which is not a member posts to the list, that address > becomes a non-member. This is the only way other than being explicitly > added by an admin that an address becomes a non-member. > > >> And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. > > > If by sending from the interface, you mean posting via hyperkitty, the > user must have an account and be logged in to do that. > > Your "same person" may have multiple entities within Mailman, possibly > subtly different email addresses, one of which is a member and one of > which isn't. > > > -- > 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

[MM3-users] Re: Django logins for new subscribers

by Abhilash Raj

On Fri, Jan 12, 2018, at 8:41 AM, Alex McLean wrote: > Hi all, > > I'm moving our groups to mailman3 (http://we.lurk.org) Enjoying it so far! > > I've mass-subscribed people via postorius. However the subscribers don't > have django (postorius/hyperkitty) logins. It seems they only exist on > the mailman side, not the django side. > > If they go through the process of creating an account in postorius, they > can configure their mailing list subscriptions, but this is a bit > fiddly. > > Is this expected behaviour? It would be great if they could be sent a > temporary link to set a password and go. Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well. So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins. It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a `get_or_create()` on each one of them (simplest of all approaches, you can ofcourse better ways to do the same). -- Abhilash Raj maxking(a)asynchronous.in

7 years, 8 months

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

by Mark Sapiro

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

5 years, 3 months

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

by Mark Sapiro

On 11/25/21 11:00 PM, Stefan Bauer wrote: > Mother: > Anonymous list: No > First strip reply to: No > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > > > > Daughter: > Anonymous list: No > First strip reply to: Yes > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > Because of DMARC mitigation, you can't do what you want. With the settings you have the mother list puts the original From: in Reply-To: and it's own address in From:. Then regardless of what the daughter does with the incoming Reply-To:, it will add the incoming From: to Reply-To: so the Reply-To: of a message from the daughter will always contain the address of the mother. The best you can do, unless you are willing to set DMARC mitigation action: to No DMARC mitigations is what you started with which is First strip reply to: No on the daughter which will at least put the original From: to the mother in Reply-To: from the daughter along with the mother's address, but you can't remove the mother's address from the daughter's Reply-To: because DMARC mitigation will always put it there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

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

by Mark Sapiro

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

3 years, 4 months

[MM3-users] Re: copies of sent "admin" messages

by Stephen J. Turnbull

David Bremner writes: > As far as I can tell, people (bots? mindless corporate firewalls?) > are complaining about the initial confirmation email. So I think an > additional approval step won't really help. Then you can go to approval only, or subscription by admin only. That's probably not what you want, but on the off chance it's better than the current situation I mention them. I'm not sure what you plan to do with these messages if you get them. Do you think the content is likely to reveal anything about the problem agents that are conducting this apparent attack? You could try adding [logging.subscribe] level: debug or [logging.smtp] level: debug to 'mailman.cfg' get more output in the logs. Note that the latter will be *very* verbose and fill up the 'smtp' log very quickly. This will not get the content of the messages. With Mailman 2 there was a neat dodge: you move the 'mailman' executable wrapper aside and put another executable in its place. I guess you could stick an lmtp server such as Postfix's smtpd on localhost:8024, configure mailman to listen on 8025, and have the smtpd dupe it for you (ie, deliver both to a file and to localhost:8025. Maybe you want to put an instance of a filter like procmail in there so it only looks at -subscribe mailboxes. I don't really know what to say beyond that.

1 year, 9 months

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

by Abhilash Raj

On Thu, May 13, 2021, at 7:18 AM, Torge Riedel wrote: > Am 03.02.21 um 02:59 schrieb Abhilash Raj: > > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Dear MM3 releasers, > > after successful update to latest versions I realized that Mailman Core > change log links are stable (I requested this some time ago and it was > changed - thanks for that), but Postorius and Hyperkitty change logs do > not have stable header ids. > > Can this be changed too? > > It makes it easier for me (and hopefully for others) when communicating > changes to the users. At the moment they see the upcoming changes for > Postorius first, which always introduces confusion for some of them. > The stable headers are sometimes missed when creating a new NEWS section. There isn't an automation that I've found to add a new section in the news.rst file yet which will do that for me. So I just forget sometimes :-) Adding headers is a trivial thing though. If you find one missing on any project please feel free to submit a MR to fix that. It can be done after the release has been made too. See this[1] that Mark just made to fix it for Postorius. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/636/diffs -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

Thanks to all who responded for your feedback. Unfortunately, the firewall blocking outbound traffic isn't something I can do anything about. Servers in our "web zone" must have specific rules allowing outbound access. That's fine for Red Hat or Ubuntu repositories but this is the first machine where we are trying to install using pip, so getting the right rule in place took some experimentation and adjustment. I did eventually get the install to work with the firewall opened for me and with a --proxy option added to the command (although I'm not 100% sure --proxy was needed). The other thing I had to do that was different to the instructions was to use pip to install setuptools. I got to a point where I had an error message that said "ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0" but when I ran "apt install python3-setuptools" it reported that it was "already the newest version (68.1.2-2ubuntu1.2)". However, running pip install setuptools (on a whim) installed version 80.9.0. After that "pip install mailman" worked. Perhaps I should have known this. I feel that making sure setuptools is properly installed might be something to add to the installation instructions. The next step in the instructions has me create /etc/mailman3/mailman.cfg. The first thing in that file is shown as: [paths.here] var_dir: /opt/mailman/mm/var Looking in /opt/mailman, there is no mm directory. Should that have been created, or is that something I need to create myself? -- Henry Hartley Westat RB 2151 -----Original Message----- From: Gerald Vogt <vogt(a)spamcop.net> Sent: Tuesday, June 3, 2025 12:29 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Trouble Installing Mailman3 CAUTION: External Email * On 03.06.25 17:22, Henry Hartley via Mailman-users wrote: > I'm having problems installing mailman3 following the instructions on https://secure-web.cisco.com/1lGZ6VhIpDXnBDYduOpQfdrz5vzmVmUu1Ox4qpxrEdA3f2… Everything goes well until I get to the Installing Mailman Core<https://secure-web.cisco.com/1XnIv9oM-wXrdCe9VFieDJykhtB-NNf5h-UB4ysN7pvWtA…> 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://secure-web.cisco.com/149I_kjrnLhuIpr1APuB8udvv8jCJuk0lqcI_esQ- > dqwmKVpgaw1Y6LT5_dF8kBkxoIp3E5cH7c8E3NU5TFqaenv2yCcBV0jBYVDBuHgpqP9oRU > OfJ6XZruLMDf2pqH2ydyrnAxjJ_ZTs59eeLe69Iy0jFuoA5d_XpSiBVdVvGKbBN13EkyH2 > HNcgmruVikAcwrT6sN52QPqQIesisnHaK6MvxqVRbMuHjoY3vpvMzLsJaSrN6_XOSx3oGf > DZgAOV/https%3A%2F%2Fpypi.org%2Fsimple%2Fwheel%2F%3A 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 There is no self-signed certificate in the chain, when I check it. I guess, there is a proxy somewhere which has a different certificate. Run $ openssl s_client -connect pypi.org:443 -showcerts to check what certificate is presented. It should be something like: Connecting to 2a04:4e42::223 CONNECTED(00000003) depth=2 OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign verify return:1 depth=1 C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 verify return:1 depth=0 CN=pypi.org verify return:1 --- Certificate chain 0 s:CN=pypi.org i:C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Feb 24 04:28:22 2025 GMT; NotAfter: Mar 28 04:28:21 2026 GMT ... 1 s:C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 i:OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Oct 16 03:08:04 2024 GMT; NotAfter: Oct 16 00:00:00 2026 GMT ... Server certificate subject=CN=pypi.org issuer=C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 ... > When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: Never ever do that. Find out what is happening. Either something bad is interfering with your network traffic. Or there is a proxy and the chain is different. In the latter case, you will see lots of issue until you have configured your system correctly for the proxy in place... But never ever simply turn off security and try to install something through broken security. It defies the whole purpose of security and certificates if you simply turn it off or try to ignore it. -Gerald _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://secure-web.cisco.com/18iP3uSUcjHSqrMHO0qp7xLDZfU6UEQCIjFnQjNhiuLqlv… Archived at: https://secure-web.cisco.com/14EbakuFKJzXm1e5mfHMqLgTjYS9LSvDFEBHhhf-pvIniT… This message sent to henryhartley(a)westat.com * Please use caution when responding and/or clicking on links as this email originated from outside of Westat.

3 months, 1 week

[MM3-users] Re: Installing mailman 3

by Kyle Richardson

You shouldn't need to wipe all of the other directories. If you're following Simon's steps, the only one being used will be /var/lib/mailman. I would also double check that you don't have an instance of mailman3 running. The presence of the /run/lock/mailman file has me thinking you do. You can check with: # ps -elf | grep -i mailman If it returns results, you have an instance running and should stop or kill it. You can use the sledgehammer approach with: # kill -9 <pid_of_mailman_process> -Kyle On Thu, Jul 13, 2017 at 11:19 AM, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: > Dear Kyle, > > I did what you suggested and this is what I got: > [root@localhost ~]# rpm -qa | grep -i mailman > [root@localhost ~]# rm -rf /var/lib/mailman > [root@localhost ~]# find / -name mailman > /run/lock/mailman > /etc/selinux/targeted/active/modules/100/mailman > /etc/selinux/targeted/tmp/modules/100/mailman > /root/mailman > /root/mailman/src/mailman > /root/mailman/venv/bin/mailman > /root/dev/mailman > /root/dev/mailman/venv3/bin/mailman > /root/dev/mailman/mailman > /root/dev/mailman/mailman/src/mailman > /var/log/mailman > /var/spool/mailman > /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman > /mailman > /mailman/mailman > /mailman/mailman/src/mailman > /mailman/mailman/build/lib/mailman > > How do I wipe all other mailman directories? using rm -rf??? > > I don't think I can start with a brand new centos 7 for the moment. > > Thank you > [excessive, redundant quoting removed by moderator]

8 years, 2 months

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

by Mark Sapiro

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

10 months

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Odhiambo Washington

On Tue, 28 Jul 2020 at 07:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 6:48 AM, Odhiambo Washington wrote: > > > So now I have tried to see if there is such option from django-admin, > but: > > > > (venv) [root@gw /opt/mailman/mm]# django-admin --help > > > You must run /opt/mailman/mm/bin/django-admin. If you run these commands > in your venv, you run the ones in /opt/mailman/mm/venv/bin which dont > have all the pointers to configuration and settings. It's OK to run > /opt/mailman/mm/bin/* with your venv active, but if you just give the > command name, you get the wring one. > So, I should run /opt/mailman/mm/bin/django-admin with a valid argument, right? Like /opt/mailman/mm/bin/django-admin createsuperuser ... How do I get all the available arguments for django-admin? That is what I was attempting to do by passing --help to it. > You also must have the empty /opt/mailman/mm/__init__py so that imports > of /opt/mailman/mm*.py modules will work as I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > This is quite clear now. Thank you. It wasn't clear at what point in the installation process this file needs to be created. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

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

4 years, 3 months

[MM3-users] DKIM header not added to subscribe/unsubscribe notification email

by Stephen J. Turnbull

Philip Colmer writes: > Everything seems to be working fine *except* when the system sends a > notification email to the list owners of someone subscribing or > unsubscribing. *Those* emails do not have the DKIM header added and are > getting trapped by anti-spam systems as a result. My guess is that the address Mailman uses for From in those messages is not in OpenDKIM's SigningTable. This is probably the $LIST-owner@$LISTDOMAIN address. You should also add the mailman@$LISTDOMAIN address. > I cannot see anything in the configuration for OpenDKIM or Postfix > that might allow just those messages to go out unsigned. Neither can we, although for a different reason. ;-) Please don't hesitate to send full configuration files to us on the grounds of absolute size or bandwidth. Such reports are relatively rare, they're not actually that big, and almost everybody on our lists are admins who know that it could be them tomorrow. Unfortunately at present I don't think you can send it as attachments. If you're worried about system security, you can either redact sensitive information such as passwords, domain names, mailboxes, and IP addresses, or you can send it to one of the developers directly (me, at the moment; Mark, when he gets back in a few weeks -- I believe Mark prefers a zipfile if there are multiple files, and I know I do) if you're willing to trust us. Steve

3 years

[MM3-users] Re: Moving existing lists to a new domain

by Mark Sapiro

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

11 months, 4 weeks

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

by Onyeibo Oku

On Wed, 14 Oct 2020 08:53:23 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman \ > -C "/opt/mailman/mm/mailman.cfg" \ > $@ > Greetings Mark, I gave up on setting up mailman using option #2 while following https://docs.mailman3.org/en/latest/install/install.html (there are lots of unknowns on that route. Certainly, the packagers are considering a lot of things that are not immediately apparent to users). Perhaps, we will see elaborate guides/docs soon. 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'. OUTPUT: Error: [Errno 13] Permission denied: '/opt/mailman/venv' This is expected. Which makes me wonder ... hmm, how did you do it? (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. (2) Should the setup proceed with 'root'? (why do I get the feeling that this is not the design?) (3) How about using an already existing local user? What are the implications? Regards Onyeibo

4 years, 11 months

[MM3-users] Re: Posting replies vs starting a thread via email

by paul＠arenson.org

Ugnius wrote: > Hi, Paul. For configuration, I would recommend to create separate list with own > addresses only, and to play a little. Thanks, but I am on hosted and cannot afford to create other lists. Just wanted to see what others did, or what Mailman 2 or 3 recommends. I am using https://www.emwd.com/mailman-3-shared-list-hosting/. I am not expert. I started to use DMARK option in > mailman version 2. Because I started to get issues with the Yahoo members. Yahoo stopped > to deliver messages from the list, when "reply to" was list address. DMARK made change in > "From:" Messages started to come for example from: "Paul via list" list(a)example.com. You should use setup good to your case, 1) Ah, I remember when we had that issue with a group I was hosting on Mailman 2. So maybe that is what I did. I guess to avoid problems with Yahoo and Gmail etc., it would be ok to use DMARC option. 2) It there a place where I can read about all the options? 3) then the latter part of my question had to do with DMARC MITIGATIONS. I do not understand the difference between selecting DMARC in ALTER MESSAGES and the choices available in DMARC MITIGATIONS. an you advice what settings to use or recommend a place where I can read about these? I currently have REPLACE FROM: with list and YES OR NO I have NO. Thanks!!!

6 years

[MM3-users] Re: Installing Mailman3 on Debian Bullseye

by Franklin Weng

Hi Charlie, charlie derr 於 2023/8/26 19:43 寫道: > On 8/26/23 04:59, Franklin Weng wrote: >> Hi, >> >> >> After several times attempts I finally successfully build a (reliable >> enough) mailman3 instance on Debian. >> >> I had a blog article describing how I did it. Maybe there were >> something you find it ridiculous, but they are all what I found >> important and may not be shown in the current documents. >> >> >> https://blogs.slat.org/node/1012 >> >> >> Hope this helps. >> >> >> Franklin > > > Thank you Franklin. And also of course, thank you to all the folks who > work on and support mailman, as it's really wonderfully robust and > excellent software. > > TL;DR: we're interested in whether anyone has run into problems with > mailman3 on debian bookworm. > > Franklin, I'm curious as to why (at this point, with debian bookworm > having been available for several months as the current stable > platform) you wanted to do this. I'm asking specifically because the > team I'm a part of has worked with mailman for many years (but not yet > engaged with mailman3) as our main listserv answer for our users. We > do have a need to spin up a new mailman instance soon, and we were > planning on doing this with mailman3 on debian bookworm. If your > choice to stick with bullseye was because of problems with trying to > get things configured successfully on bookworm, we would definitely > like to know any specific details which have created issues. > > thanks so much in advance for any additional info, > ~c The problem was reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041681 AND here: https://gitlab.com/mailman/django-mailman3/-/issues/68 Not sure which it should belong to. There are screenshots in the bug report, but some users said they couldn't open our Nextcloud instance. If you have problems opening the screenshots too you can give me a private mail I'll send pictures to you. And - honestly I ran a mm3 instance on Debian Buster (10) a few years ago, and when I tried to upgrade my Buster to Bullseye the mm3 was totally broken. Fortunately I made a VM snapshot before upgrading so I reverted it back. However that instance was unstable too - it would run out of memory about every two weeks, so I had to setup a cron to reboot the VM every week. I have no idea what happened. It was pretty frustrated. Then we moved all our services to another server hosts and I decided to rebuild the mm3 instances. I tried to build-remove-rebuild several times, including building it on Bullseye but got a lot of database locked errors, then tried it on Bookworm and got a broken django admin page, and finally set up a pretty stable instance on Bullseye which has run for about 6 weeks without any problem. So I decided to share the progress and what I found. Hope it helps. Franklin

2 years

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

by Abhilash Raj

On Sat, Jul 25, 2020, at 2:17 PM, Mark Sapiro wrote: > On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > > > Finally, I have adapted your init script to get some rudimentary one that I > > could use on FreeBSD. > > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > > have "live" MLs on this server, using mailman-2.1.34. > > I am not sure if they can co-exist. I suppose they could, but what might be > > the security implication, if any?? > > I manage more than one server that supports both Mailman 2.1 and Mailman > 3 running as user `mailman`. I'm not aware of any security issues. > > > > This is what the init script looks like (rudimentary!!): > > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > > ### BEGIN INIT INFO > > # Provides: GNU Mailman > > # Short-Description: Mailman3 Service > > # Description: service control for Mailman3 > > ### END INIT INFO > > > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > > DESC="GNU Mailman service" > > DAEMON=/opt/mailman/mm/bin/mailman > > NAME=mailman > > USER=mailman3 > > GROUP=mailman3 > > > > # Needed by click > > export LANG=en_US.UTF-8 > > > > # Exit if the package is not installed > > [ -x "$DAEMON" ] || exit 0 > > > > # Load the VERBOSE setting and other rcS variables > > #. /lib/init/vars.sh > > > > # Define LSB log_* functions. > > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > > # and status_of_proc is working. > > #. /lib/lsb/init-functions > > > > case "$1" in > > start) > > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > > # use --force to remove a stale lock. > > /usr/local/bin/sudo -u $USER $DAEMON start --force > > T don't recommend using --force in init scripts. It *shouldn't* matter > because even with --force the master shouldn't break the lock if the pip > that set it still exists, but I prefer not to use it. > > > > ;; > > stop) > > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > > /usr/local/bin/sudo -u $USER $DAEMON stop > > ;; > > status) > > /usr/local/bin/sudo -u $USER $DAEMON status > > ;; > > reopen) > > /usr/local/bin/sudo -u $USER $DAEMON reopen > > ;; > > restart) > > log_daemon_msg "Restarting $DESC" "$NAME" > > /usr/local/bin/sudo -u $USER $DAEMON restart > > ;; > > *) > > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > > exit 3 > > ;; > > esac > > > > It does start mailman3 for sure, but also complains after a few seconds > > with the message: > > > > (venv) [root@gw /usr/local/etc/rc.d]# > > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > > DeprecatedWarning: Call to deprecated function __init__(...). API class may > > be removed in a future release, use falcon.App instead.* > > * **kws)* > > > Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 > and 3.0.0a1 and I don't see this warning, but it is only a deprecation > warning. It doesn't mean it won't work. I have seen this during development and there is an issue open for this[1]. [1]: https://gitlab.com/mailman/mailman/-/issues/733 > > > > But: > > > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman > ... > > It seems Mailman core and the rest runner and its workers are all running. > > > > > > Assuming that I am using mod_wsgi with Apache, and that I have configured > > apache right using > > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > .. > > should I be able to access the MM3 web UI?? > > Yes, I think so. > > > > At that point, I am feeling somewhat confused as to what to try next. > > > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > > Jul 25 22:53:16 2020 (40670) Master started > > Jul 25 22:53:18 2020 (42036) bounces runner started. > > Jul 25 22:53:18 2020 (45205) out runner started. > > Jul 25 22:53:19 2020 (41191) archive runner started. > > Jul 25 22:53:19 2020 (46670) retry runner started. > > Jul 25 22:53:19 2020 (44567) nntp runner started. > > Jul 25 22:53:19 2020 (43069) in runner started. > > Jul 25 22:53:19 2020 (46960) virgin runner started. > > Jul 25 22:53:20 2020 (45720) pipeline runner started. > > Jul 25 22:53:20 2020 (47326) digest runner started. > > Jul 25 22:53:20 2020 (43755) lmtp runner started. > > Jul 25 22:53:20 2020 (45922) rest runner started. > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > > http://127.0.0.1:8001 (45922) > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > > Jul 25 22:53:21 2020 (42743) command runner started. > > > The above is all fine, but it is just Mailman core. > > > > How do I access the web UI for MM3 now? > > > The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which > is at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. > Do you have that? > > If you installed the Apache config literally, the location for Mailman 3 > is defined by > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > and the URL would be http(s)://your.server/mm3 - have you tried that? > > -- > 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, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I installed whoosh, ran the server and got this: DisallowedHost at / Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Request Method: GET Request URL: http://192.168.1.42:8000/ Django Version: 1.11.3 Exception Type: DisallowedHost Exception Value: Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/django/http/request.py in get_host, line 113 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 Python Path: ['/var/lib/mailman/env2/lib/python2.7/site-packages/django_q', '/var/lib/mailman/mailman-suite/mailman-suite_project', '/var/lib/mailman/env2/lib64/python27.zip', '/var/lib/mailman/env2/lib64/python2.7', '/var/lib/mailman/env2/lib64/python2.7/plat-linux2', '/var/lib/mailman/env2/lib64/python2.7/lib-tk', '/var/lib/mailman/env2/lib64/python2.7/lib-old', '/var/lib/mailman/env2/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7', '/var/lib/mailman/env2/lib/python2.7/site-packages'] Server time: Fri, 21 Jul 2017 23:35:16 +0000 Where's the ALLOWED_HOSTS file???? El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:27 PM, Rafael Mora wrote: > > > > it says it needs whoosh > > > > How do I install that? on env2 with python2 or env with python3 ??? > > > In env2 do 'pip install whoosh' > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

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

by Mark Sapiro

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

5 years, 2 months

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

by Odhiambo Washington

On Thu, Mar 30, 2023 at 6:55 PM Zaheer Abbas <zaheer.psg(a)gmail.com> wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. > > I believe it was previously available in mailman2 > via Accept_these_nonmembers attribute. > > But I cannot find this attribute anywhere on postorius. > > I am using mailman 3.2.2 > > Any help would be really appreciated. > > Best regards, > I would do this at the MTA level with either a router or a filter (milter in Postfix lingo): IF $sender_address_domain IS NOT "example.com" AND $recipient is "listname@domain" THEN send-to-dev-null. Exim (MTA) has a filter plugin to do this. I don't know about Postfix and Sendmail (as I am not willing to read on your behalf). It is easier that way. I don't remember is Mailman3 has the logic to deal with that, but maybe it does. If you did not manage to find it, then my solution is plausible, no? Filter at the MTA level. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Does mailman2 regular_exclude_list equal mailman3 receive_list_copy ?

by Stephen J. Turnbull

Did you ever get an answer to this? I was short of round tuits so left this in the inbox, but maybe you already have the answers. sunil soprey writes: > Do you plan to reintroduce the de-duplication feature so that if a > mail list subscriber is on multiple email lists that are cc'd/bcc'd > they only get the message one time? Yes, it's desirable. However, the question is actually quite complex because a 'User' may have many 'Address' entries. Here, does "subscriber" mean 'User' or 'Address'? I can see it going both ways. Some users have many addresses, all except one are pure forwarding, and they only want to read the email once. Other users have separate addresses for separate roles, and they want to have that message for context in each role even if they have read it before. Hashing this out means it will take us some time to get it into a release. (That's IMO, I defer to Abhilash as project leader and Mark as having more experience if their opinions differ.) Of course we could implement "de-dup" with the subscriber = 'Address' interpretation immediately, which provides substantial relief for many users, and later add a User config option for "Also de-dup equivalent addresses" for some definition of "equivalence" (I can think of two implementations already, that's what I do, complexify things ;-). > Are you aware of solutions feature outside of Mailman3 core? Say > filtering in postfix-mta? (might complicate tracking of dups in > postfix) I'm sure there are no such. It's much simpler to implement in Mailman core because you don't need to deal with transporting Mailman to filter and filter to MTA, and more reliable to implement in core because Mailman knows a lot more about both subscriptions and messages than you could deduce from the message itself. It's not impossible, of course, but I think it would be hard to implement well. > For "mailman core", could we filter in outbound send of mailman? > Example - could the processing pipeline be modified to > track/discard duplicate msgs? I'm not sure what you mean by modifying the processing pipeline, but the basic idea is pretty clear. At some point the list name has to be expanded into a list of addresses. This is done by a specific handler in the pipeline, and the filtering will be done at that time. There are a number of possible implementations. We'd start by looking up all of each subscription's list affiliations when we look up the subscription configuration. In some cases we could create addressee lists for all the relevant mailing lists at that time, then send the message to the outgoing pipeline of each list to be decorated appropriately, but I'm not sure whether it's worth trying to do that. We'd also have to keep a record of lists of addresses (or Users) wanting de-duplication identified by Message-ID for some period of time in case the sender's MTA sent the message multiple times rather than providing multiple recipients in one transaction. Steve

5 years, 2 months

[MM3-users] [Spam] Installation Help on Ubuntu 18

by Stephen J. Turnbull

joseverde(a)gmail.com writes: > Hi folks, I spent many hours last night trying to get Mailman 3 up > and running. I am using Ubuntu on a Digital Ocean LAMP droplet (so > PHP, Apache, Sql, and Postfix are already installed). The LAMP > stack works as I have a successful installation of YOURLS going > on. So, I tried to use this guide > (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) That's not our guide, we don't support it, and at least I don't recognize the author offhand, can't speak for the rest of the team. Now that our NO WARRANTY notice is out of the way, I will say that guide is written in very good style, with great attention to detail and appropriate warnings about delicate parts of the procedure. If you end up succeeding with it, I'll add a link to it to our docs. > to install the Mailman3 package and got to the configuration screen > (the one with all the DOS-esque GUI). That's Ubuntu's UI, not ours. Your questions so far are all really Ubuntu questions, not Mailman questions. We'll do what we can to answer, but I don't think any of the core developers use Ubuntu packages to manage their Mailman installations. You are likely to get more help, more accurate help, and faster help in Ubuntu (or perhaps Debian) channels. > I ran it but it kept saying the DB wasn't installed. Mailman can use any of several database backends (at least SQLite3, PostgreSQL, and MySQL). It seems possible that Ubuntu Mailman is configured for one, and the preinstalled one is another. Which SQL implementation was preinstalled, and which one are Mailman and Django configured to use? > 1. Does that guide actually work? Ask the author, not us. Internal evidence (quality of presentation, dates, the NOTE at the top) strongly suggests it works for somebody. > Did I just foul up the database part? Not clear what got fouled up or where in the process, but clearly getting database installation and configuration right is necessary to proceed. > 2. Is there a better way to install mailman3 with some nice > step-by-step directions to follow? Don't know. We provide docker containers, but I don't know if those are compatible with Digital Ocean's droplets. Our docs are at mailman.readthedocs.io, but they're not step-by-step the way the guide you reference is because they're distribution- agnostic, and generally oriented toward a build from source. > 3. Is there a way to completely wipe my previous installs without > wiping the server? ( I didn't back up...silly I know ). Just wipe the server and create a backup image. Multiple, if you have the space for one every time you successfully install and configure a subsystem. You will save yourself a lot of time. dpkg --purge will wipe out the Mailman stuff, but if your config process touched anything else (the database, the MTA config) rerunning the process is not guaranteed to do the right thing. It probably will do the right thing, but why not be sure you have a reset to known state? Steve

5 years, 1 month

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

by Odhiambo Washington

On Tue, 28 Jul 2020 at 06:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 4:29 AM, Odhiambo Washington wrote: > > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Is there an empty /opt/mailman/mm/__init__.py file? > >> > > > > No. > > > There has to be one. Create it and then Django will be able to import > your settings. > > See the first line after > > Create directories: > ... > and files: > > at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69 > > > I don't know why I didn't see that initially :-) > > Yes. However, that also means the /opt/mailman should be owned by > mailman3, > > right? So I wasn't quite mistaken. > > > It doesn't matter what user actually `owns` this directory and its > subordinates as long as the Mailman user, mailman3 in your case, can > read and write there. Of course, making everything owned by the Mailman > user is the easiest way to ensure this. > True. > > Note also that any commands in /opt/mailman/mm/bin need to be run as the > Mailman user and not root. Running them as root can create things owned > by root the can't be read by the Mailman user. > So, now I remember why I had to chown -R mailman3 /opt/mailman Then now it seems like I have been doing things incorrectly, because I have been doing a lot of operations as root by simply: cd /opt/mailman/mm virtualenv venv source venv/bin/activate Looks like the correct way is to start with su - mailman3 > > PS: There is the issue with qcluster, which doesn't seem to have been > > documented in details from your "experience". > > I see the configuration file and the init script, but not how to install > > it, or whether the procedure already installed it. > > > qcluster is part of Django. If you have this > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > or similar uncommented in your Django settings, and also 'django_q' in > your INSTALLED_APPS, it's there and all you need to do is run > > /opt/mailman/mm/bin/django-admin qcluster > > to run it, but it should be run as a service via init or ?? > I have run it from supervisord. It has forked 30 processes and refuses to kill them when I stop supervisord. I will look for options around it. Answering my own question I asked earlier, I have found "django-admin help --commands" to answer it. PS: Did you by any chance find time to look into the issue about wsgi.py that you had mentioned - the one that has me stuck using it?? Thanks again. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

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

by Odhiambo Washington

On Tue, Nov 12, 2024 at 11:52 AM Markus Grandpré < markus.grandpre(a)uni-konstanz.de> wrote: > Dear Mr Odhiambo, > > thank you very much for your reply. > > In mailman.log I see: > > Nov 12 09:46:02 2024 (698086) ACCEPT: > <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de HTTP/1.1" > 200 486 "-" "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de/config > HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/users/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU > Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner > HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/addresses/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 436 "-" > "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/ > import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator > HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" > Nov 12 09:46:03 2024 (698083) HyperKitty archived message > <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> to > > https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_te… Is that ALL you have from mailman.log for today,? I was expecting more - like some task runners being logged. In smtp.log I found: > > Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO > mailman-app-test.kim.uni-konstanz.de' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL > FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: > markus.grandpre(a)uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT > TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: > Import_mm3_testliste(a)mailman-test.uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost > during _handle_client() > > I have no idea why there is a "connection lost". What do you think? That 'connection lost' is normal. So there seems to be communication from mailman to your MTA. What do you see in your MTA (Postfix?) logs when you send an email to the list? > How can I increase the log level? > Actually, you do not need to, but mailman.cfg complete documentation is here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… -- 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]

10 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:36 -0800, Mark Sapiro wrote: > > Why do you say the .mo files are old. The timestamps are all Feb 3 > 02:47 which is when the package was built for PyPI. Because my brain goes faster than my fingers and I say the reverse of what I mean. I meant .mo files, all .po where properly dated, and I reversed the meaning of my thoughs while typing. Thanks for brining my confussion to my (and everybody's) attention, and my appologies for the noise. > When things are changed on weblate, we get automatically generated > merge requests to update our source. We don't always merge them > immediately, but we certainly do merge all the outstanding ones > before making a release. I'm 95% certain that I edited messages after Nov 7th in the Spanish translation of both mailman, postorius and hyperkitty, but the .po file is dated Nov 7h. Actually, I did a review of outstanding strings when Abhilash annonced the RC for the current version. That is why I was bit surprised. But then, it may be me and my faint memory. And, of course, I'm very grateful and happy with all the work that is being done on Mailman3. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 7 months

[MM3-users] Log rotation

by Darren Smith

Hey everyone, So I have a question about log rotation... Our mailman.log has grown to over 5 gigs. It's time to add this to log rotation. We added what we thought might work to the /etc/logrotate.d/mailman script, but when we ran it with a -f, we learned that the -f flag doesn't keep old logs. That in itself is fine - a normal scheduled log rotation won't have that problem. My problem is that doing the rotation caused the mailman not to be able to write to the log anymore. It appears that it no longer has a handle to the file. To overcome this with, say, nginx, there is a command in logrotate that you can add that restarts the service. I have found, however, that restarting the mailman service can be VERY problematic. There is so much going on that it takes a very long time to stop, and I have seen several instances where the service never shuts down cleanly - even after 3-4 minutes. The service thinks it is shut down, but there are several threads that haven't yet completed. If they are killed, then you have to go clean up the master.lck files etc. It seems like a bad way of doing things and a good way to somehow corrupt data. Anyway - after rambling... 1) Has anyone come up with a good log rotation strategy that doesn't necessitate a restart of the service? 2) Has anyone seen problems stopping and restarting the service? Is there a way to help with this problem? Thanks, Darren

7 years, 5 months

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

by Stephen J. Turnbull

Simon Handfield via Mailman-users writes: > I have been working through other threads that indicate the same > symptom (500 error when loading held_messages for a list). You want threads that deal with Unicode: > Error reported in log with debug enabled: > > Traceback (most recent call last): And that last call is:: > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) It appears that the message is improperly constructed, and either a Content-Type field has a omitted or inappropriate charset parameter, or perhaps the Content-Type field is omitted entirely (ASCII is the default charset). This is frequently a problem created by spam messages. The message should be in the shunt queue. You can examine it with the command "mailman qfile /path/to/message_file.pck". Unfortunately it's not clear from the backtrace where in the message this is: it's at the beginning of a part ("position 8-9") or maybe line, but the part could be late in the message. If it's spam, you can just delete the file (and do whatever else you do about spam, of course). If it's not spam, it would help if you can guess what language and charset are being used in the message, and we can go from there. If this is unclear, feel free to ask more.

5 years

[MM3-users] Re: Strange password problem

by Eggert Ehmke

Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > On 9/22/23 09:50, Eggert Ehmke via Mailman-users wrote: > > -I try to log in as admin > > -rejected because of wrong password (password is stored in browser) > > -used forgotten password function, using my email address > > -reset password to the stored value from browser > > -login works now. Works also when logged out/in again > > -however, the next day this behaviour repeats. > > So apparently the issue is that although you reset your login password > to a known value, it doesn't stick and reverts overnight to some other > value. Yes that it looks like. > Is this the Debian package or installed following > https://docs.mailman3.org/en/latest/install/virtualenv.html or something > else. Yes it is a virtualenv installation following that guide. > All I can think of is some cron may be resetting the password. If that's > it, it's probably a Debian thing. Can you see if there's any cron > running the Django admin changepassword command? Will try to find that. > If you set the password with the Django admin changepassword command, > does it stick? Never tried that, how do I do that? > Can you create another superuser with the Django admin createsuperuser > command and does that user's password stick? Will try that. So I can create another superuser? Does it need a separate email address? I guess yes Thank you for your ideas.

1 year, 11 months

[MM3-users] Re: Advice on migrating to Mailman 3

by Mark Sapiro

On 2/13/20 2:02 PM, Christoph Groth wrote: > > The only problem is that our list runs on Mailman 2. We would like to > move to Mailman 3, but this does not seem to be that simple. Perhaps > someone here would be so kind to give us advice? I think it's pretty simple, but I've been a Mailman developer for 15 years ;) > The number of (shared) hosters who offer Mailman 3 seems to be very > limited [3]. Would it be a good idea to book a virtual private server > (VPS) somewhere, that runs, say, Debian, and simply install Mailman > 3 through the distribution’s package system? I’m already running > a small personal box with nginx on it, and this is very little work, but > running Mailman would require sending out up to a few thousand email > messages per day (our list has a few hundred subscribers). Is this > something that one is commonly allowed to do on a VPS system? Most VPS > offers that I see are silent about mail. This list is on a VPS hosted by RackSpace. mail.python.org which hosts hundreds of lists is a VPS hosted by DigitalOcean, and my bicycling club's web site, email and mailing lists are on a VPS also hosted by DigitalOcean. These servers all run some version of Ubuntu, but because we are developers, they do not use the Debian/Ubuntu packages. They are all installed from the heads of the GitLab branches and kept pretty much up to date with those. All three servers use Postfix as an MTA. We have no issues with mail volume per se. What you will see with a new VPS is your IP being blocked by various ISPs. It takes a bit of communication and patience to work through these blocks, but once you develop a good reputation, they tend to go away. > If we setup such a system, can we assume that it will silently operate > without causing much administration work most of the time (like my nginx > server)? Or is maintaining a Mailman 3 server a significant burden ([2] [2], or [3]? > seems to imply that)? If yes, are you aware of organizations that > propose Mailman 3 hosting for open source projects? Python.org seems to > host some lists for third party projects, but otherwise I haven’t seen > much. I don't think a Mailman 3 installation needs an undue amount of baby sitting. I do run daily reports that list the contents of mailman's queues (normally empty, but messages in the shunt queue need investigation) and grep a couple of logs for errors. mail.python.org hosts lists for Python related open source projects. Kwant seems to be eligible. Ask postmaster(a)python.org specifying the desired list name and name and email address of the initial list owner(s). However, we don't normally import lists or archives from elsewhere. > [1] https://kwant-project.org/ > [2] https://mailman-mail5.webfaction.com/listinfo/kwant-discuss > [3] > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

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

by Mark Sapiro

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

1 year, 11 months

[MM3-users] Re: Question about adding addresses using the REST API

by Stephen Daniel

TL;DR: Listening to the advice, I will create and manage user/address pairs. I am in the process of porting a web site that is used to manage a small organization. The web site maintains a directory of users of that organization, and also allows them to subscribe/unsubscribe to a small set of interest-group mailing lists for that organization. The users are not tech savvy, and are not expecting or expected to manage their subscriptions through Postorius, nor do they have access (normally) to the archives. Indeed, the URL to Postorious will normally be turned off at the reverse proxy server that sits in front of both Postorious and the organization's website. The one-source-of-truth is the website's database. The website code has callouts for "subscribe <address> to <list>" and "unsubscribe <address> from <list>". I am trying to minimize the amount of code I write to implement the web site's callouts, to initialize the mailing lists when I port the organization to this new implementation, and make it relatively easy to keep the website's database and mailman3's database in sync. The impression I had from the docs was that unlinked addresses were a first class object. Since my website callouts only deal with addresses, this seemed a good mapping. However, I understand from this email thread that unlinked addresses are not the way to go, so I'll map <address> in the website database to <user>/<address> in mailman3. Thanks for the advice and feedback! -- Stephen Daniel On Sat, Jan 15, 2022 at 2:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/15/22 10:03 AM, Stephen Daniel wrote: > > > > The only way I've found to create a standalone address (not linked to any > > user) is to create a user with that address, unlink the address, then > > delete the user. > > > > Is there a more straightforward way to just create an address with no > user? > > > The more straightforward way is via the IUserManager create_address > method. This method is not exposed directly in REST, so you can't do it > via REST. > > My question is why do you want to? > > Granted when an unknown nonmember address posts to a list we create a > standalone address record, but maybe we should be creating a user too. > We don't because it's tricky. Suppose User A with address A posts to a > list from nonmember address B. We create the standalone address B record > as a nonmember, but now user A can add address B as another address. If > we also created User B, this would not be possible. > > But again, what is your use case for creating standalone addresses? > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 8 months

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

by Stephen J. Turnbull

Shashikanth Komandoor writes: > I am currently running Mailman 3 with version 3.3.1 and in > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version > with default values in production environment from the past 4 months > almost. As of now, we are having around 1327 lists created on this. Aren't you the crew that modified Mailman to interface with SMS or something like that? If so, don't worry, it doesn't invalidate your warranty, but it seems possible that it has something to do with this: > After the above configuration, I found many errors like below in > mailman.log file: > > *sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for > column 'pended.id <http://pended.id>'"* > > *sqlalchemy.exc.ResourceClosedError: This result object does not return > rows. It has been closed automatically.* > > *sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status > PGRES_TUPLES_OK and no message from the libpq* Whether you have that modified Mailman or not, the messages above suggest that there may have been a change in the schema of the database that one side (presumably SQLAlchemy) knows about but have not been propagated to the other (PostgreSQL). Have you perhaps done an upgrade but not run the database migration script? About the REST API not available error: > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > But my mailman core was working fine in the background. At > the same time I was able to do other operations on a few other lists. > > By the time I am getting the above error, the mailman.log > recorded the below messages. > > *[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)* > > *[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)* > > *[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042* Something is taking too long, the worker is timing out. That's probably why you get the REST API not available message. Do the sqlalchemy errors correlate with the timeouts? I suspect the exit and reboot of the worker is normal but I haven't looked at this part of the code. > My mailman.cfg configuration is as below. The timeout > value is the default value. I did not set any customized value. Thanks for sending it; sometimes it speeds up debugging. But in this case you say that other lists are working, so site configuration doesn't seem to be the problem. Is this particular list special in some way? List configuration is different? > The above might be few of the errors. FYI, for the creation of each list, > it is taking almost around 15 to 20 minutes. After multiple times of the > above error messages, at some time, I am fortunately getting the list > created or some other operation getting done. This is quite strange. I don't see why this would suddenly start working after many minutes. Does PostgreSQL have any logs with "interesting" (or scary) messages in them? Maybe somebody else has some ideas, but this is as far as I can go.

5 years

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by John Covici

I have a couple of questions about the container, if its OK. First, it says to run you create the directory /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the git clone. What directory should the git clone be in? A couple of more questions -- is there a way to install the web server and the mta in the container, this way I could make the whole thing be independent of my host configs? On Fri, 30 Jul 2021 16:04:48 -0400, bob B wrote: > > is this the info you need for the container version > > [root@..... docker-mailman]# docker ps > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > for smtp host > ------------ > cat /opt/mailman/web/settings_local.py > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > ALLOWED_HOSTS = ['*'] > DEBUG = True > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'smtp.example.com' > EMAIL_PORT = 25 > --------------------------- > cat /opt/mailman/core/mailman-extra.cfg > # mailman-extra.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > # mailman-core hostname or IP from the Postfix server > lmtp_host: localhost > lmtp_port: 8024 > # Postfix server's hostname or IP from mailman-core > smtp_host: smtp.example.com > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: my_real_email_is_in_the_file.com > __________________________________ > > My docker most machine /etc/postfix/main.cf has > > transport_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = > regexp:/opt/mailman/core/var/data/postfix_domains > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > ------------------------------ > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > _______________________________________________ > 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/ > -- 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

4 years, 1 month

[MM3-users] Re: Run a mailman program outside of mailman shell

by Odhiambo Washington

On Tue, Jul 23, 2024 at 11:18 PM Greg Newby <gbnewby(a)petascale.org> wrote: > Hi again folks. I have hundreds of lists to convert from MM2.1 to MM3, and > intend to write a Python program do this this rather than running commands > in mailman shell (and rather than running 'command()' functions in mailman > shell, if possible). > > However, when I write a simple Python program to run the types of commands > found in the Mailman docs, such as these > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > >, > I get errors. This is a venv installation, following these instructions > <https://docs.mailman3.org/en/latest/install/virtualenv.html>. The > Mailman3 > installation is working fine and I have a handful of lists in production > that I set up manually. > Okay. Not to go against your favorite method, but looks to me that you're killing a feal with a hammer! I had some 10 lists to migrate from MM2 to MM3 and I simply did the migrations using bash a shell command line. for l in list1 list2 list3 ...listN; do blah blah; done ...as documented here: https://docs.mailman3.org/en/latest/migration.html -- 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, 1 month

[MM3-users] Re: The Use of Hyperkitty as a Forum and Archiver

by Allan Hansen

I can echo Mark’s responses exactly, as well as the sentiment that it’s WAY WAY WAY better. One additional item of praise: The ability to post/respond to messages from within HK(I guess what you refer to as the ‘forum’ feature) is way cool. While I’m at it here are also some small and not so small gripes: a. The link for visit ’the archives’ is embedded in a sentence. It should be an icon like ’Unsubscribe’. While we’re on that page, the same goes for ‘your list options page.’ b. On entering HK, when listing ‘Recent’, etc, the author is not listed. c. Why is ‘Manage subscription’ an option on this page? The ‘Manage this list’ in the header already has this link. And it appears in the list of options on which threads to show. ????? d. When listing ’Threads by month’ and ‘All threads’, the left panel is taken over. e. When I log in as admin, I get a ‘Delete’ button on this page as well. There is no mention of what it does. Does it delete the list, the archive or the shown threads (I assume the list, but why is this button here???). f. The activity summary here is irrelevant to most users and should be just an optional display. g. Sometimes the lists are listed by Postorius and at other times (at login) by HK. The displays by Postorius are much better and cleaner. The listings by HK use too much real estate for the ‘Activity in the past 30 days’ graphs, which really are just fluff. The difference in presentation between Postorius and HK is confusing and confounding. Thank you for the reminder, Brian. I’ll send out a note to my lists’ members to remind them of this very improved tool. Yours, Allan Hansen hansen(a)rc.org > On Jul 14, 2020, at 8:48 , Mark Dadgar <mark(a)pdc-racing.net> wrote: > > On Jul 14, 2020, at 6:51 AM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >> - Has the forum feature (Hyperkitty) of MM3 been received well by your list members or is it mostly ignored? > > Pretty sure no one even knows its there, even though I told them when we migrated to MM3 originally. > >> >> - Do you see an increase in the use of HK as a forum from your list members? > > No. > >> - What kind of feedback have you received from your list members considering the forum function of MM3? Positive or negative? > > None. > >> - Do you think HK is received well by your list members as an archiver and do you think it provides a better user experience for viewing/searching archives vs Pipermail of MM2? >> > > WAY WAY WAY better experience than Pipermail. The single most common feedback about the archives under MM2 was “the archives are broken - search can’t find anything.” htdig was not a great indexer. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > _______________________________________________ > 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, 2 months

[MM3-users] Using it with the "smtp2go" email relay service that has special deliverability rules

by golden_rock＠hotmail.com

Hi, Smtp2Go relay service enforces a few rules for deliverability: The From: address domain has to be verified in smtp2go The sender envelope address also has to be verified in smtp2go So emails sent by mailman don't get relayed because mailman sets From: to be the original sender of the message, and it means anyone that wants to send to the list would have to approve themselves with smtp2go first, which is not workable. To make it work, I would have to have something like: Sender: bounce-address(a)lists.mailman3.org - untouched From: original.sender@gmail.com@lists.mailman3.org - change #1 having the From address to be From the list Reply-To: original.sender(a)gmail.com - change #2 - if someone replies Then smtp2go will send the email. I looked in the settings and I didn't find a readily available option to do that. I'm new to customizing mailman3 , but have been using it in production for a little more than 1 year. I've seen other software do the solution proposed above, namely DIvi contact forms set the "From" to be something @website.com and the Reply-To: as the form submitter. I am told that the standards is moving away from forging the DATA From: that doesn't have a predictable domain, and instead put the variable email address in Reply-To, for things like contact forms or automated sending. Can someone guide me on where I could start looking?

2 years, 7 months

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

by Stephen J. Turnbull

Helio Loureiro writes: > Well... not that good. Now it is mailman3-web that doesn't work. > > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > System check identified no issues (0 silenced). > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate > Traceback (most recent call last): [omitted] > LookupError: No installed app with label 'migrate'. > > Any idea why migrate isn't working and saying it is installed? Management commands aren't applications, so they wouldn't be valid arguments to "mailman-web check" in any case. Try "mailman-web check postorius" or "mailman-web check hyperkitty" to see how the application argument works. You should get the report "System check identified no issues (0 silenced)." as above. Then try "mailman-web migrate -h". If that returns help output, the migrate command is installed and can be run (the help string is part of the migrate module, not part of mailman-web itself). Why do you think "mailman-web migrate" isn't working? Most likely "migrate" is working as designed, but it is doing nothing because something about the way you transported the database originally caused mailman-web to think its database schema is up-to-date even though it is not (as happened with the mailman database). Unfortunately this database is managed by Django, not by Alembic, and I don't know offhand how to discover and tell Django the actual schema version and then ask it to run any new migrations. Steve

1 year, 9 months

[MM3-users] Mailman3 Docker persmission denied

by Commander456

Hello everyone, I recently installed the mailman-core Docker image (Version 0.5) and tried to create a list using the mailman commands inside the container. I used the --notify argument but doesn't receive any mail (I'm the list owner), However, inside the mailman.log I get the following error: Jan 06 20:54:25 2025 (156) Uncaught runner exception: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' Jan 06 20:54:25 2025 (156) Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 164, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: ^^^^^^^^^^^^^^^^^^^^ PermissionError: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' Jan 06 20:54:25 2025 (156) Skipping and preserving unparseable message: 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8 These are my file permissions: mailman-core:/opt/mailman/var/queue# ls -l total 48 drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 archive drwxrwx--- 2 mailman nogroup 4096 Jan 6 20:54 bad drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 bounces drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 command drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 digest drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 in drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 nntp drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 out drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 pipeline drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 retry drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 shunt drwxrwx--- 2 mailman nogroup 4096 Jan 6 20:54 virgin mailman-core:/opt/mailman/var/queue/virgin# ls -l total 0 Do you have any idea what I'm doing wrong? Thank you

8 months, 1 week

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

by Stephen J. Turnbull

Dave Hall via Mailman-users writes: > I have seen this with several open source projects lately. There's no big > picture, just 'hundreds' of cross-linked little bits of disjointed > information that almost seem like documentation for individual > modules. It is documentation for hundreds of individual modules. That's, like, the point of open source software. ;-) > So, a challenge for us all: When writing and reviewing your documentation, > imagine that you're explaining your whole project face-to-face to your > grandmother, or to anybody who never learned to program. From experience I > promise that it's easy once you get the hang of it. I agree in principle, and for greenfield projects I agree that many/most developers can get the hang of it and it's easy (fsvo "easy") once you do. But in decades-old open source development projects at Mailman 3 scale (which isn't even all that big), most of is not our job. For example, the HAYSTACK_CONNECTION variable that incited this thread is buried deep in a Django extension that's distributed independently of Django. The best we can do with modules like that is cookbook explanations (I'm pretty sure there is at least one and likely two or more in the official docs on list.org or readthedocs). If the cookbook recipe doesn't work, I doubt anybody here can write anything deeper off the top of their head.

2 years, 7 months

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:01, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:39 AM, Odhiambo Washington wrote: > > Hi, > > > > In my quest to create a superuser, I followed another HOWTO - > > https://docs.mailman3.org/en/latest/devsetup.html > > > > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# > > python manage.py migrate > > Traceback (most recent call last): > > manage.py migrate (or django-admin migrate) is part if the > mailman-post-update script. It doesn't work here because when you run it > this way, it doesn't get your settings.py. > I have taken note of that. Thank you. > ModuleNotFoundError: No module named '_sqlite3' > > And it's looking for sqlite3 because that's the default database. > > *<==============================================================* > > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# > pip > > install pysqlite3 > > You don't need this. You need to run django-admin with the correct > settings. > Thanks for clarifying. > So I figured out that I need to put my own settings_local.py into the > > directory and let the command rely on MySQL as the database backend since > > by default, it uses sqlite3 backend. > > > > But the question then is WHY is this not documented on the above page??? > > > Because that's not relevant to what you are doing. You are trying to > install Mailman for production, not development. > Okay. That is true. > > How can I delete the superuser after creating it?? > > > The only django-admin or manage.py you should run is > /opt/mailman/mm/bin/djhango-admin. You can run `django-admin > createsuperuser` to create a superuser. If you want to delete one, you > need to go to the Django admin web UI - should be > http://your.server/admin - login as a superuser and go to the Users page > and delete it. You should probably do this as a different superuser > The reason I asked for how to delete superuser came from the fact that from the above confusion, I needed to create a superuser. So now I have tried to see if there is such option from django-admin, but: (venv) [root@gw /opt/mailman/mm]# django-admin --help Type 'django-admin help <subcommand>' for help on a specific subcommand. Available subcommands: [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate runserver sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver *Note that only Django core commands are listed as settings are not properly configured (error: 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.).* (venv) [root@gw /opt/mailman/mm]# So is something wrong with my settings???? I do not see the command to create the superuser listed. My settings_local.py has got only the bits from settings.py that I have customized. Thank you for your patience. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Mark Sapiro

On 8/3/25 00:09, Odhiambo Washington via Mailman-users wrote: > I wonder what this means and whether it's fatal. > > How do I fix it? > > ``` > ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) ... > *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() > returned more than one EmailAddress -- it returned 2!* It appears you created a new list, and that list' owner email address has two Django user records with emails differing only in case. See https://www.msapiro.net/scripts/UC_fix for a script to fix this or you can just go to the Django web UI and delete the mixed case user. > I suspect it's something to do with my action yesterday while attempting to > reply to a thread from HyperKitty. Possibly, if hyperkitty was looking at a mixed case email address that it didn't recognize as a list member and subscribed it. > The superuser account uses my address - odhiambo at gmail dot com.I am also > the listowner for most lists. > I tried unsuccessfully to create an account on Postorious using the same > email address. > I kept getting sent links to verify the account, over and over. > Finally, I was able to verify the account, but cannot login with it. This too is probably because there are two accounts with email addresses differing only in case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Trying to configure a list (hosted)

by Abhilash Raj

On Sat, Aug 31, 2019, at 7:05 PM, paul(a)arenson.org wrote: > Thank you for the very quick response, Abhilash Raj. Being non > technical (and therefore opting for hosted Mailman 3), I can partly > understand your kind response. > > 1) I can understand that I cannot disable the different ways to sign up. > > 2) I am still struggling to understand the difference between the two > web choices as shown here. > > WAY # 1 TO GET AN ACCOUNT > https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… > > VS > > WAY # 2 YOU CAN GET AN ACCOUNT WITHOUT SIGNING UP > at the bottom of > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > (I was under the impression making only WAY #1 allows one to post, but > are you saying that the bottom option also allows one to post, but only > by email?) That's right. Mailman is a mailing list manager and is primarily based around discussions using Emails. You can subscribe to mailing lists and send email to the list address, which then gets distributed to all the members. All the emails sent to the mailing lists are also archived usually in an archiver. The official archiver, a.k.a the one supported by us, also additionally supports posting to the mailing list via the Web interface. If anyone wants to use the web ui to post, they need to have an account and need to verify that they own the email address they are signing up with. Then, anything they post is sent as an email, on their behalf, to the mailing list and that's how you can get 2 ways to post. You don't need any account on the web interface if all you want is to post through email. > If I am confused, I know my users will also be confused. I think I > understand I can qualify their subscription in the ways you suggest: > "Confirm where all users would have to confirm their subscription using > an email sent to them. Optionally, you can also enable moderation where > each subscription needs explicit approval too." > > So to put it simply: > > 1) I want to make it a discussion list. Not available to people who are > not signed up? It is slightly confusing, but let's separate sign-up into two terms and let me know if that is still confusing, "sign up to web interface", "subscribe to mailing list". - sign up to web interface: This is optional. This allows you, as an administrator to operate the mailing list and it's configuration. A user can sign up to the web interface and manage all the subscriptions they have, and also subscribe to mailing lists. - subscribe to mailing list: This is a user participating in a Mailing List. For this, they don't necessarily need to sign up via web interface as there are other ways to subscribe to a mailing list, like anonymous subscribe (which is your #2 above). Once they are subscribed, they are called "subscribers". Users will always have to "subscribe" before they can participate on a mailing list. There is currently no way to mandate "sign up on the web interface" for all "subscribers". > > 2) This is dependent on all having access to the archives so they can > see what they are responding to If the archives are set to be private, only the "subscribers" can view the archives. > > 3) What settings do I make to insure that all who sign up via WAY #1 > can see the archives and post. You have to set the archives to be private and that's all. You can do that from: List -> Settings -> Archiving Options on that page should be self-explanatory > > 4) What settings do I make to insure that all who sign up via way #2 > can do the same? They will receive emails and will be able to reply to them. If they want to post via the web interface, they will have to create an account and sign up, same as #1. > > Last, in my account settings what is the difference between a member > and a non member? "non-members" are people Mailman remembers who interacted with a MailingList in past. For example, I can ask an list owner to let my post through, without actually subscribing(because I don't want to get all the emails, just send a single email) by allowing me to be a "non-member" who is allowed to post. > > Thanks and sorry I was not clear the first time. > _______________________________________________ > 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

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

by Rubén Rivero Capriles

Hi! sorry for updating one last piece of info provided by Thomas Woerner of firewalld. He seems interested in our issue of python 2 / python 3: Thomas Woerner <notifications(a)github.com> 4:12 (hace 3 horas) para t-woerner/fire., mí, Author Do you want to use python2 or python3? In the firewalld repo there is a firewalld.spec file. With this it is simply to generate packages for Fedora and also RHEL >= 7. For RHEL-7 it is still using python2, for Fedora >= 23 python3. TO build a package with it you can simple do the following in the root directory of the firewalld source tree: ./autogen.sh make test-rpm Or you can use rpmbuild -ta firewalld-0.4.2.tar.gz with a release from https://fedorahosted.org/released/firewalld/ or https://github.com/t-woerner/firewalld/releases I am still stuck with awstats. Have been able to watch them through lynx linux browser, but stats are not being generated. I enrolled in a local linux academy where I will take an apache course and maybe they''ll be of help. However I don't like software that does not provide support themselves, especially if good folks such as mailman or firewalld team are around. Is there any alternative statistics generation package for apache that you could recommend and I would be able to use without so many installation issues Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)

9 years, 3 months

[MM3-users] Re: bypassing rules on an individual basis

by dlb-ml＠anl.gov

Stephen J. Turnbull wrote: > via Mailman-users writes: > > I have a mailing list that, due to specific circumstances, has a > > requirement to allow messages from a user that sends messages with > > no subject. > > Do you mean "any user who sends a message with no subject", or are > there specific users who do this? If there is one such user (or a > handful), and you trust that user not to abuse the privilege, you can > directly pre-approve that user from Users menu in the list > configuration (see Mark's post for details). This also works if there > is no Subject field at all! > If you don't know who might post with no subject (or there are > annoyingly many, especially if some are less than clueful), you could > use the header match: The address in question is from an automated process, so there's no immediate expectation that it will be abused, so I'm utilizing the recommendation that Mark provided. I'll see if that works as expected. And, out of curiosity, why is the "accept_these_nonmembers" collection not applicable here? Is its use deprecated or is there a very particular use case for it? """ While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing. """ I should have paid more attention to this part. Thanks!

5 months, 1 week

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

by Ryan McClung

Scratch that. Ran with the corrected script and getting the following: [root@mailman3(stg) archives]# mailman lists No matching mailing lists found Any thoughts? On Tue, Jul 31, 2018 at 9:35 AM Ryan McClung <rmcclung(a)afilias.info> wrote: > Hey there, > > Im going to breakdown my response into sections: > > 1) Yes, there is only one install of mailman on the box. > > 2) I created the list using the script below > > 3) My method of importing it is by copying the lists to > /opt/mailman/old/lists and running these commands (within lists) > > MYDIR="/opt/mailman/old/lists" > DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` > for DIR in $DIRS; do mailman import21 "${DIR}"@afilias.info > "${DIR}"/config.pck; done > > However, if you look at the above you can see where I am going wrong. What > it should actually be doing is: > > > MYDIR="/opt/mailman/old/lists" > DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ > afilias.info "${DIR}"/config.pck; done > > Sorry for wasting your time on this one. Coffee is on me. > > > On Mon, Jul 30, 2018 at 6:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/30/2018 07:37 AM, Ryan McClung wrote: >> > GNU Mailman 3.2.0 (La Villa Strangiato) >> > Python 3.6.5 (default, Apr 10 2018, 17:08:37) >> > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] >> > config file: /opt/mailman/var/etc/mailman.cfg >> > db url: sqlite:////opt/mailman/var/data/mailman.db >> > devmode: DISABLED >> > REST root url: http://localhost:8001/3.1/ >> > >> > Shortly after I run an import on a bunch of lists they all disappear. >> > [root@mailman3(stg) mailman]# mailman lists >> > No matching mailing lists found >> > >> > I have 30+ lists. >> >> >> Does the 'mailman lists' command invoke the identical 'mailman' file as >> the 'mailman import21' command that did the imports. And how did you >> create the lists before importing them? >> >> We have done several imports of 2.1 lists to >> <https://mail.python.org/mm3/mailman3/> and have never seen an issue >> like this. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

7 years, 1 month

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 18:53, Bryan Fields wrote: > On 7/26/24 4:01 PM, Mark Sapiro wrote: > >> If this returns just the one message_id, I would then >> >> DELETE FROM hyperkitty_thread WHERE id = 35670; >> DELETE FROM hyperkitty_email WHERE id = 150555; > > It's giving an error due to a fk constraint on another table. I'm not > familiar with the db structure enough to be certain how to clean/fix it. Yes, you need to do these first. DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; DELETE FROM hyperkitty_vote WHERE email_id = 150555; Not all those will exist, but then you should be able to DELETE FROM hyperkitty_thread WHERE id = 35670; DELETE FROM hyperkitty_email WHERE id = 150555; > I'm actually thinking I need to fix the archive mbox, then delete them and > re-import them once they are cleaned. Actually, that would be safest. Fix the mbox, delete the entire archive and re-run the import. >> Also, FYI, assuming those messages with very old Date: headers had >> reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script >> would fix them, except you have to get the script from >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… >> or https://www.msapiro.net/scripts/cleanarch3 because the script in the >> latest release has a bug. > > I tried the dry run option on your script and it gave a bunch of output > for bad > dates. This was absent on the one shipping with the source. What's > interesting > is that pipermail seems to have no issue with this, detecting the date > correctly. If I recall correctly, pipermail checks date skew and 'fixes' the dates in the archive, but they remain off in the mbox. > https://mailman.nanog.org/pipermail/nanog/2000-January/137630.html > One other thing, I did notice a number of archives not showing up in > sequence > due to missing "In-Reply-To:" headers from the source. The first > message in > this is one like this, and pipermail in mmm2 seems to handle this by > referencing > the subject, > https://mailman.nanog.org/pipermail/nanog/2002-April/151325.html, > where as in hyperkitty it's an orphaned thread. Yes, HyperKitty does not do threading by subject matching. It only threads based on In-Reply-To: and absent In-Reply-To:, only the last entry in References: if any. > Is the archive tool in pipermail's import more robust in this manner? > I'd argue > it's common to have missing In-Reply-To: headers where the subject and time > would need to be used to infer the likely thread. I'll agree this is a > major > violation of the relevant RFC's to be missing this, but many MUA's (M$) are > famous for doing just this. Yes, it's arguably a defect in HyperKitty to not implement Jamie Zawinski's threading algorithm <https://www.jwz.org/doc/threading.html>, but it doesn't. -- 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: configuring moderators per list

by Mark Sapiro

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

7 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Should Sign Up ?? Log In?? El vie., 21 jul. 2017 a las 18:56, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Nice! Up and running! > > How do I start using mailman? what are the steps?? > > REALLY thank you all for your patience and help! Really appreciated ! > > El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 04:43 PM, Rafael Mora wrote: >> > YEEEES! At last!!! I can see the web UI. >> > >> > Now I´m getting this message in the web UI: >> > >> > Something went wrong >> > Mailman REST API not available. Please start Mailman core. >> > >> > >> > >> > Where do I configure the REST API ????? >> >> >> So I guess you figured out that ALLOWED_HOSTS is a Django setting in >> settings.py or wherever your Django settings are. >> >> Now you have to start Mailman Core. In your Python 3 'env' where you >> installed Mailman Core, run 'bin/mailman start'. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

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

by Brian Carpenter

Make sure you have a SPF record setup for the sending domain. Also if this is a new IP address then ISPs such as Gmail and Yahoo recommend you "warm" up the IP address until its reputation is built up. However none of this has anything to do with Mailman 3. Just a FYI. Have a great day! Brian Carpenter EMWD.com brian(a)emwd.com -----Original Message----- From: worik <root(a)worik.org> Sent: Monday, February 11, 2019 5:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Gmail emails bouncing - anybody seen this problem? 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 -- 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) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 7 months

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021, at 9:21 PM, Stephen J. Turnbull wrote: > Victoriano Giralt writes: > > > I've visited Weblate, all Spanish strings are translated. Spanish > > is 100% translated, but, none of them have been "approved", > > whatever that is. It seems that a reviewer needs to approve the > > translation in order for them to be incorporated or released or > > whatever. I was sure I had reviewed everything between November 7th > > and the day Abhilash announced the release candidate and asked for > > translation review, but nothing has made it to the released > > version. > > > > Maybe there's something in the translation flow that we are doing wrong. > > I'm starting to miss the good old days when Mailman 2 translators just > > downloaded the .po files and returned them :-) > > Probably all it needs is for someone other than the submitter to check > a box. I doubt there is an assigned reviewer/owner, just any > translator registered for that language. That's the way Debian used > to work, anyway, and it seems like a good way for open source to work. > > @Abhilash, you set up Weblate, right? Do you know anything about this? https://docs.weblate.org/en/latest/workflows.html This is the documentation from Weblate about the whole workflow. There is a Project level setting which mandates that a Reviewer review and approve all the translated strings, but that is turned off for GNU Mailman project. -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Disabling the version disclosure.

by ninad＠iitb.ac.in

Steve from another mailman list suggested the below solutions. 1st method suggested worked. This is just for this group's information. Thank Steve for the solution. --------------------------------------- Suggested solution ------------------------------------------------------- It helps to explain why you don't want to change the HTML code, because there are several ways to do this, with different implications both for the page's appearance and for future maintenance. The visually cleanest way to do this is to copy the files site-packages/postorius/templates/postorius/base.html site-packages/hyperkitty/templates/hyperkitty/base.html to /etc/mailman3/templates/postorius/base.html /etc/mailman3/templates/hyperkitty/base.html search for '_VERSION' and delete or edit the version stanzas near the end of those files, add TEMPLATES[0]['DIRS'].append('/etc/mailman3/templates') somewhere in /etc/mailman3/settings.py, and restart mailman-web (typically as root, using 'systemctl restart mailmanweb'). Alternatively and less visually appealing you can clear the version variable itself with a file 'site-packages/version_hack.py' containing the lines def suppress_version(request): return {"HYPERKITTY_VERSION": "Wouldn't you like to know?", "POSTORIUS_VERSION": "Wouldn't you like to know?"} ... you probably want to change the strings to empty strings ... and add the lines TEMPLATES[0]['OPTIONS']['context_processors'].append( 'version_hack.suppress_version' ) somewhere in /etc/mailman3/settings.py, and restart mailman-web. The former method of overriding the templates is a supported API, and very unlikely to be obsoleted any time soon. The latter method of patching the variables is something of a hack, and also leaves the tags like "Postorius version" visible in the page. Steve ----------------------------------------------------------------------------------------

5 months, 3 weeks

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Eggert Ehmke

/ I saw output like:/ <User "Real Name1" (250400693957149667060114911620088407125) at 0x7f9435096640> deleted from Mailman <User "Real Name2" (52978839424924170731978420609240089133) at 0x7f9435096760> deleted from Mailman So your users had no real names configured? Cheers, Eggert Am Dienstag, 25. April 2023, 23:14:27 CEST schrieb Andrew Hodgson: > Mark Sapiro wrote: > >The script at https://www.msapiro.net/scripts/clean_users.py has been > >updated. As before, it has settings to control whether Django users are > >deleted if there is a corresponding Mailman user with no memberships or > >only if there is no corresponding Mailman user, and whether or not Mailman > >users with no >memberships are deleted. > Thanks, I ran this script and it did delete a load of Mailman users, I got > output similar to this: <User "" (47600399411039288509336192576257642185) > at 0x7fb17a6a35e0> deleted from Mailman > > Why aren't we seeing the actual address here? > > Thanks. > Andrew. > _______________________________________________ > 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 > /BTJUT6FGNGK5ARADPD6VW37VMHQG2GWJ/ > > This message sent to eggert(a)eehmke.de ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 4 months

[MM3-users] Re: MM3 occasionally chokes (?)

by Abhilash Raj

On Mon, Mar 18, 2019, at 9:46 AM, Dmitry Makovey wrote: > Thanks for fast response Abhilash! > > See inline for responses: > > On 3/18/19 9:24 AM, Abhilash Raj wrote: > > On Mon, Mar 18, 2019, at 9:14 AM, Dmitry Makovey wrote: > >> In the last couple of month we've observed some odd behavior from MM3 > >> (namely the core) where it seems like email that is about to be sent to > >> a large-ish mailing list (10K users) has been processed yet never gets > >> sent out until we restart the core. > > > > This is indeed weird, I don't think 10k is too much, but it also depends > > on your MTA. How fast do they allow sending emails and if there is any > > rate limiting. > > I'm using Mailu.io for MTA. We're controlling it so there's not much > throttling as I've whitelisted mailman to send anything over LMTP. Mailman sends out email using SMTP and receives it from MTA using LMTP. > > > I wouldn't necessarily consider this a performance problem in Core, > > since it is still just processing only one email. All it needs to do is > > send them all out, which is where the problem should be. > > inferred assumption is that mailman-core loses LMTP connection with > Mailu stack. but then upon restart of service it regains it? Mailman acts as am SMTP client sending out emails via MTA. AFAIK, Mailman 3 recycles SMTP connections after certain number of emails are sent out. You can configure how many emails are sent-out per-connection and when should each connection be recycled. You can also disable the recycling altogether and always keep a connection open to the MTA. See [1] here for detailed docs. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht… Again, copying from the docs, these are some extra MTA related settings that you may want to change: --- # Ceiling on the number of recipients that can be specified in a single SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. max_recipients: 500 # Ceiling on the number of SMTP sessions to perform on a single socket # connection. Some MTAs have limits. Set this to 0 to do as many as we like # (i.e. your MTA has no limits). Set this to some number great than 0 and # Mailman will close the SMTP connection and re-open it after this number of # consecutive sessions. max_sessions_per_connection: 0 # Maximum number of simultaneous subthreads that will be used for SMTP # delivery. After the recipients list is chunked according to max_recipients, # each chunk is handed off to the SMTP server by a separate such thread. If # your Python interpreter was not built for threads, this feature is disabled. # You can explicitly disable it in all cases by setting max_delivery_threads # to 0. max_delivery_threads: 0 --- max_sessions_per_connection is by default set to 0, so that shouldn't be causing any problems. For a list of 10k members with `max_delivery_threads` set to to default(500), Mailman could be sequentially sending out emails in 20 (10k/500) connections, which could be causing the delay that you see. You could increase the threads or if your MTA can handle it, set the max_delivery_threads to 20 and see if that helps? > > > I'd imagine debug logging on outgoing runner should give some more > > pointers on what is going on. > > > > You can configure the smtp runner to log extra information (copied from > > docs)[1] > > > > [1]: > > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > awesome - I'll give it a go. thanks for the pointer. > > > I'd also recommend looking into MTA logs for anything un-usual. > > we briefly did , but nothing stood out. > > >> troubleshooting/digging before I just restart the core (which by the way > >> takes about 45min to fully start... which is another puzzle to solve at > > > > How do you measure that it takes 45 mins to start? > > normally it's "docker ps" command output along with "docker top" so once > I see all the sub-processes kicked off I'm assuming core is started and > from that point it's anywhere between 35 and 45min before I can get any > *response* from core (i.e. mailman-web complains, REST commands fail, etc.) Maybe we should discuss this in another thread? REST Runner (and other runners) shouldn't be taking this long to boot up. > > > What database backend are you using? > > Postgres. The whole setup is docker-setup (0.1.7 version of containers > at this point). > > > -- > Sr System and DevOps Engineer SoM IRT > > > Attachments: > * signature.asc -- thanks, Abhilash Raj (maxking)

6 years, 5 months

[MM3-users] Re: Hyperkitty import from mailman2

by Simon Hanna

On 12/22/2017 03:39 PM, Sten Aus wrote: > Hi > > I have installed mailman3 - it looks very great! > > Now I wanted to try import from mailman2 mbox, so i did: > > python2 manage.py hyperkitty_import --settings settings --ignore-mtime > -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > > It shows that it have sucessfully imported all emails and I can see > them from database (sqlite3), but I cannot see them from GUI > (hyperkitty). Only thing I can see is this inactive "test" list. > How did you try to access them using Hyperkitty? Can you try doing that while logged in as a django superuser? Could you try using a permalink for a message? If you can access the files from the database you should be able to construct the urls using the list name and the message_id_hash of a message. You should try this using DEBUG=True in the settings.py. The URL would be similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… Another option would be to check if you can access the data using a python shell. `python manage.py shell` to open a python shell preconfigured for Hyperkitty and then input the following two lines: from hyperkitty.models.email import Email Email.objects.all() This should print out all the messages that are stored in the database. (You can limit them by appending "[10:]", or any other python slice) What do you see in the UI? Is it somewhat similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ?

7 years, 8 months

[MM3-users] Re: Hyperkitty performance problem

by Stephen J. Turnbull

Tobias Diekershoff writes: > On 22.11.24 07:59, Tobias Diekershoff wrote: > > so far we could not find the reason behind the performance > > problem. Since you're already running two allegedly identical systems, have you tried hitting the experimental one with the "do what the developers recommend" hammer? That is, blow away the Debian packages in favor of a vanilla installation from source in a virtual environment (and without --system-site-packages!)? It's impossible to be sure what's going on in a Debian package environment because not only Mailman, but any of the scores of packages that Mailman 3 depends on may have been patched or reconfigured by Debian. > To rule out virtualization problems Do you mean a VM, which should not cause a problem, or a container, which is known to be tricky to configure? (Note, I've not heard of it causing the kinds of problems you describe.) > in our setup, we tried to migrate MM3 to a bare metal server in the > data center. After importing the database for MM3 and Hyperkitty to > the new postgresql server MM3 wcomplained about > > MultipleResultsFound: Multiple rows were found when one or none > > was required [in the listarchiver table] I've seen that in a migration from a Mailman 2 site to Mailman 3. Once I removed the duplicate rows in the archiver table, it stopped. I don't know why it happened, but it was a small number of lists (4 or 5 out of 20k), and at most one extra per (list, archiver) pair. I suspect it carried over from the Mailman 2 instance. I no longer have access to that system to confirm, sadly. > However the duplicates are added back to the listarchiver table for > all archivers (mhonarc, hyperkitty, mail-archive and prototype) > even though only hyperkitty is activated. By "duplicates are added back" do you mean something like this: mailman=> select * from listarchiver; id | mailing_list_id | name | _is_enabled ----+-----------------+--------------+------------- 1 | 1 | mhonarc | f 2 | 1 | mail-archive | f 3 | 1 | prototype | t 4 | 1 | hyperkitty | t 5 | 2 | mhonarc | f 6 | 2 | mail-archive | f 7 | 2 | prototype | t 8 | 2 | hyperkitty | t where each list has one of each archiver whether or not that archiver is active? This is correct behavior, as long as the archiving/*.py and mailman_hyperkitty.py files are importable by Mailman core. Or by "duplicates are added back" do you mean this? mailman=> select * from listarchiver; id | mailing_list_id | name | _is_enabled ----+-----------------+--------------+------------- 1 | 1 | mhonarc | f 2 | 1 | mhonarc | f 3 | 1 | mail-archive | f 4 | 1 | mail-archive | f 5 | 1 | prototype | t 6 | 1 | prototype | t 7 | 1 | hyperkitty | t 8 | 1 | hyperkitty | t 9 | 2 | mhonarc | f 10 | 2 | mhonarc | f 11 | 2 | mail-archive | f 12 | 2 | mail-archive | f 13 | 2 | prototype | t 14 | 2 | prototype | t 15 | 2 | hyperkitty | t 16 | 2 | hyperkitty | t (don't take the id -> (list_id, archiver) mapping too seriously). In the multiple instances of an archiver per list case, which are enabled? > We tried to add a constrain on the table to only allow one entry > per list and archiver, but that caused the runner to fail and the > message to be shunt. > > > Uncaught runner exception: (raised as a result of Query-invoked > > autoflush; consider using a session.no_autoflush block if this > > flush is occurring prematurely) (psycopg2.errors.UniqueViolation) > > duplicate key value violates unique constraint "workaround" > > DETAIL: Key (mailing_list_id, name)=(98, mhonarc) already > > exists. This doesn't make any sense. That appears to be the listarchiver table. As far as I can tell in a quick grep, the only place that is mutated is in mailman/models/mailinglist.py:643 (line number is current HEAD), which happens whenever the list checks for its active archivers. It's initialized lazily for each list in that place. @public @implementer(IListArchiverSet) class ListArchiverSet: @dbconnection def __init__(self, store, mailing_list): self._mailing_list = mailing_list system_archivers = {} for archiver in config.archivers: system_archivers[archiver.name] = archiver # Add any system enabled archivers which aren't already associated # with the mailing list. for archiver_name in system_archivers: exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() if exists is None: store.add(ListArchiver(mailing_list, archiver_name, system_archivers[archiver_name])) As you can see, the .add is protected by "if exists". That code has not changed since v3.3.8, which is what is in Bookworm according to "apt list mailman3". If that is so in your installation, I'm pretty sure the problem is somewhere between the SQLAlchemy API and the RDBMS, not in Mailman itself. And if that's true, that might explain the weirdness in archiving as well. What version of PostgreSQL are you using? of SQLAlchemy? Are both the original system with performance problems and the new one accessing the same PostgreSQL server, or is there are separate PostgreSQL instance for each? Steve

6 months, 4 weeks

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

by Mark Sapiro

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

2 years, 3 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > That combination at least produces multipart/signed messages with > multipart/* parts containing a Content-Transfer-Encoding: header. > > The Python 3 email library considers this to be a > InvalidMultipartContentTransferEncodingDefect() message defect. Merely containing C-T-E is not an error per RFC 2045, although it seems to consider it a stupid thing to do. If present, it may be "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening that restriction been published since? (I don't know why it would, though.) Even with a non-cleartext C-T-E, it seems reasonable for Mailman to treat it as application/octet-stream and pass it through, unless the list is configured to do something like strip application/octet-stream or that requires decoding like spam-filtering (Postel principle, although one could argue it shouldn't be sent on on the same principle -- ah, the joys of being an e-mail Mediator). That would be especially true it if were quoted-printable, since any relevant MIME headers would (presumably) be pure ASCII and therefore unencoded. > multipart/signed > multipart/mixed * > text/plain > message/rfc822 (the attached message) * > multipart/signed * > text/plain > application/pgp-signature > text/plain (an empty plain text part) > text/plain (a quote of my message to you) > application/pgp-signature It's true that Apple Mail is horked if it produces that structure with C-T-E in the indicated places (but we already knew that :-( ). Steve

3 years, 5 months

[MM3-users] Re: redirecting -bounces replies

by Nelson Strother

If you are using Postfix with mysql you could use an entry in the virtual_aliases table by doing something like: MariaDB [mailserver]> REPLACE INTO mailserver.virtual_aliases (id,domain_id,source,destination) VALUES ('N', '1', 'ListNameHere-bounces(a)example.org', 'person(a)example.org'); Query OK, 1 row affected (0.010 sec) where the value 'N' is one larger than the largest id entry already present in said table .... Cheers, Nelson On 10/31/24 19:17, Hirayama, Pat wrote: > Greetings, > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. > > I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location. > > Thanks! > > -p > > > > Pat Hirayama > Pronouns: he/him/his > Systems Engineer > IT | Systems Engineering - Infrastructure > Fred Hutch Cancer Center > O 206.667.4856 > > phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org> > > > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-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/mess… > > This message sent tojustfixit(a)marilynstrother.com

10 months, 2 weeks

[MM3-users] Re: Verification links to localhost

by Odhiambo Washington

On Sun, Feb 5, 2023 at 2:16 PM Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi! > > You wrote: > > > On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <[1]lars(a)lamasti.net> > wrote: > > > > Hi, and than you for your quick reply! > > > > You wrote: > > > > > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1][2] > lars(a)lamasti.net> > > wrote: > > > > > > The verification link I get back when trying to add an account, > > referes > > > to localhost, e.g. > > > > > > To confirm this is correct, go to [2][3] > https://localhost:8000/ > > accounts/ > > > confirm-email/Mw:1... > > > > > > Where do I change that? > > > > > > > > > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings? > > > > I don't have this variable anywhere in /etc/mailman3. However, I > found it > > here: > > > > ./venv/lib/python3.10/site-packages/mailman_web/settings/ > > mailman.py:POSTORIUS_TEMPLATE_BASE_URL = '[4]http://localhost:8000' > > > > In which config file should that variable be set, and how do I set > it so > > that mailman can works for multiple domains? > > > > > > Because it is still too early in your quest to get to run Mailman3, I'd > advise > > that you take your time to follow this guide: > > [5]https://docs.mailman3.org/en/latest/install/virtualenv.html# > > > It is the official installation guide. > > Yes, I've followed it, maybe with some errors. > > > There is a step where it tells you to create a file named settings.py, > in a > > particular path. You really need that step. > > Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't > have the variable in question. > Oh, in that case, it does not appear in settings.py. I have followed that guide, but I always login to the /admin UI to create a site (and a mail domain tied to a site) before I create my lists. Perhaps that's why I haven't encountered the problem you are seeing. > > > Regarding your question about multiple domains, that is already well > taken care > > of when you create a list either via Postorius or the cli: > > (venv) [mailman@gw /opt/mailman]$mailman create [6]list1(a)domain1.name > > (venv) [mailman@gw /opt/mailman]$mailman create [7] > another-lis(a)domain2.name > > > > Mailman will know how to handle this in conjunction with your MTA. > > That's right. But, still, when I set the SITE_ID = 0, I get an server > error when trying to connect. I also get mail from Django that states the > error. I'm not sure how to fix it. > How many sites did you create already? IIRC, this SITE_ID = 0 should be accompanied with FILTER_VHOST = True -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Stephen J. Turnbull

bob B writes: > Anyone have any ideas? First, what docker configuration are you using? One supplied by the Mailman project? If not, you need to tell us more about what's going on. If so, are there any containers other than those running the Mailman suite (Mailman 3 core, Postorius, HyperKitty)? In mydestination you have mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com I do not understand the "localhost.$mydomain" entry. I guess that's a Postfix-ism, but I can't find any documentation about it. You could try taking it out (this is a very random suggestion). You say you have no /etc/postfix-mailman.cfg. Where are you looking for it? That file will only exist in the container, not in the host OS. (If it were in the host OS, it would be located somewhere like /opt/mailman/core/postfix-mailman.cfg.) Try `find /opt/mailman/core -name postfix-mailman.cfg`, although "automatically" might mean it's generated in the container when it starts. Abhilash would know, but he doesn't seem to be available. I really don't think it's the issue because I assume "bmimailmandr1" is the Docker container running Mailman core. If so Postfix is connecting to the configured LMTP port on localhost which is what it's supposed to do from the configuration. Since the container's Postfix appears to be connecting to the right place but the connection is refused, that Mailman core may not be running. For more help you'll have to wait for Abhilash. Steve

4 years, 1 month

[MM3-users] Re: Timeouts

by Mark Sapiro

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

4 years, 4 months

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

by Nelson Strother

As you had suggested, the `in` runner/queue was missing in action. Given your insight about the limitations of `mailman restart`, I looked back at the log from the time of the preceding `mailman start`, and found that there was NOT a line such as: in runner started. in that instance! Watching the logs on each subsequent `mailman start`, the good news is that the `in` runner/queue has been started each time; the bad news is that slightly more than half of the time one or two runners are NOT shown as starting. The other runners/queues sometimes missing in action per the log file have been `retry`, `task`, `nntp`, `archive`, and `pipeline`. No errors are being recorded in the mailman log files. This is GNU Mailman 3.3.8 via `pip install mailman` on Debian 5.10.179-1 (2023-05-12) running on a shared system where VMware gives this server enough cycles that `mailman start` and `mailman stop` each consume from 20 minutes to an hour of wall clock time, so I do not issue those commands recreationally, attempting to keep the system available for users. What should I do to help understand the cause for these failures? Would not it be helpful for this limitation of restart to be included in: mailman restart --help with a suggestion to use `mailman stop` and `mailman start` instead? On 6/1/23 11:16, Mark Sapiro wrote: > When you issued a restart and the logs show runners restarting, did > all the runners restart or was one or more missing.

2 years, 3 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Stephen J. Turnbull

M.Ede via Mailman-users writes: > Mark Sapiro wrote: > > > The following patch will remove the header. > > Thanks for the hint, I removed authentication-results header as > well as arc-authentication-results with your patch, but rspamd > still results in SPOOFED_UNAUTH. I don't think Mark was suggesting that would help with the SPOOFED_UNAUTH problem. I read his mail as saying that it needs to be fixed because it breaks anonymous_list. I don't think that rspamd is paying attention to any of the smtp.*from information because the one that matters is the one in the SMTP MAIL FROM command, which only appears in the message header by accident. (It could be some kind of machine learning thing, but I doubt that would get dinged for 50 points.) If you're still having issues 1. Does your problem resemble any of those in the links Mark sent? 2. Where is rspamd running? On your host or at Mailcow? 3. Who is sender(a)t-online.de, is it a placeholder for a random user, or is it an address associated with your Mailcow account? 4. Are my.mailserv.er and lists.list.domain the same host? If not, what is their relationship? 5. Where are you running the ARC and DKIM processors? 6. Do you have Mailman set to strip DKIM signatures? (I find it hard to believe that a major ESP like t-online doesn't sign outgoing email.) 7. What is the list address? Specifically, is it @lists.list.domain, or is it @list.domain? You need a DKIM public key record in DNS for the exact domain of the list as it is added to From. 8. Do you have a non-permissive DMARC policy for lists.list.domain? 9. How do you send list mail to Mailcow? (a) Regular SMTP directly to the Mailcow MX (b) Regular SMTP indirectly via a different host that is not authorized in SPF to send mail for your list domain (c) Authenticated SMTP (usually SASL on port 587)? Something is definitely odd about your ARC installation. It should not be possible for ARC verification to fail within the administrative domain that applied the ARC headers, because in theory the ARC signature and seal are performed on the *outgoing* message at the administrative boundary. Also, in the example in your third post[1] the server names in the ARC headers doesn't match: ARC-Message-Signature: i=1; d=lists.serv.er; ARC-Authentication-Results: i=1; mailserv.er; ARC-Seal: i=1; s=dkim; d=lists.serv.er; Maybe that's just a typo, but if not that could be the problem, I'm pretty sure those are expected to match. I think the missing DKIM signature may be important. One interpretation of "SPOOFED_UNAUTH" is "I think it's spoofed because I can't authenticate it". In question 9 above, if you send mail via (a) SPF *could* authenticate it, and via (c) that's pretty good authentication, but DKIM is best and Mailcow may insist on it. [1] <175750349214.87167.13924287800652306747(a)mail.mailman3.org> Aaargh, gmx.de has a non-permissive DMARC policy -- hope you're not deleting dupes because that almost always means you don't get the list version. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 days, 14 hours

[MM3-users] Re: Mailman installation results in KeyError: 'env_py'

by Marvin Gülker

Hi, Am 22. October 2017 um 11:47 Uhr -0700 schrieb Abhilash Raj <maxking(a)asynchronous.in>: > As Simon mentioned, try using DEBUG=False, if you don't already have > that. With DEBUG=True, you should see emails printed in a `emails` > directory under `mailman-suite_project` directory. Bingo! Man, I was not seeing the forest for the trees. I should have peeked inside that emails folder. And yes, changing the DEBUG flag resolves the problem and emails now go out as they should. My bad! Thank you! > > That being said, the enormous number of configuration files to consider > > and dozens of cross-references to other pages in the docs make the > > installation guide hard to follow; it also lacks logical structure in my > > opinion, when it refers to parts of the configuration which are later > > explained. For someone like me who never programmed a Django application > > (Ruby dev) this is all pretty cryptic. Especially, that some parts of > > information are on <http://docs.list.org/en/latest/index.html> whereas > > other parts are scattered over readthedocs.io makes it very > > complicated. > > There are only two primary configuration files (there are a few more for > finer configurations ;-): Mh, mailman.cfg, settings.py, and hyperkitty.py are three. But I agree, I exaggerated. > All the settings mentioned in the documentation go to either of these > files, except, when configuring web server and mail server. Please open > an issue[2] if it is not clear where a particular configuration snippet > goes and we will fix it. I'll open an issue later; for now off the top of my head so I won't forget I came over these problems with the docs: * The linked installation guide for Sass (<http://sass-lang.com/install>) does not include any C/C++ implementation you speak of. * The mailman-suite's settings.py includes a handler for Less, which is not mentioned in any documentation. * It's officially suggested to use the "fhs" filesystem path layout. It's not documented that you need to create the exact directories and change permissions accordingly; even worse, if one uses this layout, Mailman tries to write into /sbin, which only the package manager is allowed to do. Thus, don't recommend that layout in <http://docs.list.org/en/latest/config-core.html>. * This page: <http://docs.list.org/en/latest/config-core.html> does not mention that the "postfix_lmtp" and "postfix_domains" files are *generated* by Mailman. I spend quite some time looking for these files before I found in the Mailman Core docs that they're generated and it was not an error in my installation. * This page: <http://docs.list.org/en/latest/config-core.html> configures the LMTP server and the REST API server for the same TCP port (8024). This clashes. * This page: <http://docs.list.org/en/latest/config-web.html> should mention the thing with the DEBUG variable we've successfully worked through in this thread. * There's no mention of how to create the initial superuser on <http://docs.list.org/en/latest/>, it is hidden down in <https://postorius.readthedocs.io/en/latest/setup.html>, where however there's no mention of the mailman-suite, but some kind of "example_project". It was unclear to me whether this now applied to me or not. * <http://docs.list.org/en/latest> contains quite some pip install commands (duplicated from the postorius/hyperkitty/core docs), but it's missing "$ pip3 install mailman-hyperkitty", which is only mentioned in <http://hyperkitty.readthedocs.io/en/latest/install.html> in the text body (but not as a command block). * This page: <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> uses "configuration: python:mailman.config.postfix" in the introductory text without explanation, but down in the Postfix-specific block the directive is missing with no explanation. I opted to include it, but I don't know whether that's now correct or not. The overall problem I had with the docs is that they can't be followed top-down. One has to refer to the subproject docs if something is unclear, then searching in them until one finds what one was looking for (even if one doesn't know what one is looking for, as with the superuser creation command). I totally appreciate the detailed subproject-docs approach, but you should follow it consequently then. That is, do not duplicate some information from the subproject docs in the mailman-suite docs. It creates the impression as if the mailman-suite docs are complete, which they aren't. Instead, the mailman-suite docs should use explicit references, for example: 1. Do this... 2. Now follow the procedure outlined in [Postorius Installation link] 3. Do something else... 4. Follow the procudedure in [Hyperkitty installation link] That way, the Mailman installation guide would be less of a puzzle. It however might just be me. I apologise if I sound silly. Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 10 months

[MM3-users] Docker Support Sucks

by Brian Carpenter

Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: ### The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: [webservice] configuration: /path/to/gunicorn.cfg and then in the gunicorn.cfg you can add [gunicorn] timeout = 90 graceful_timeout = 30 ### I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. After restarting docker-mailman, I can't access Postorius due to the following error: ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 160, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 84, in create_connection raise err File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 677, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 392, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib/python3.6/http/client.py", line 974, in send self.connect() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 187, in connect conn = self._new_conn() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 172, in _new_conn self, "Failed to establish a new connection: %s" % e urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f96340a2e10>: Failed to establish a new con$ 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 725, in urlopen Commenting out "configuration: /opt/mailman/gunicorn.cfg" brings Postorius back up. I am really frustrated here. All I want to do is export a 3000 member list and I can't. Updating Mailman 3 using new Docker images shouldn't break a stable installation either. Please help. Brian

5 years, 1 month

[MM3-users] Re: Dump/restore users (with passwords) via API

by Dmitry Makovey

On 09/17/2018 12:39 PM, Abhilash Raj wrote: > On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: >> We are trying to dump/restore users using API calls and it seems >> that API allows us to dump password hashes (a good thing), but then >> API does not allow to insert users back using saved password hashes >> - only cleartext passwords. > > I'd say that is intentional. You don't want people to be setting up > hashes as passwords. > >> Aside from create_user is there any other way to create >> users/change their password? > > Not that I know of, not using the API atleast. You could potentially > use the low level API that inserts records in the database or use SQL > to dump and restore that data. > > What do you use the Core's user/password for? Currently, the user > passwords are basically just a carry-over from Mailman2 and there > shouldn't be any use for it. I have been considering removing that > completely have Postorius do all the authentication/authorization. > > Email based authentication should rely on more reliable identities > like email signatures, intead of having to send cleartext passwords > over email. I think I am asking about the username/password auth for postorious and how to dump/restore it. At present we have no tools for dump/restoring users so that's what we're trying to build. -- Sr System and DevOps Engineer SoM IRT

6 years, 11 months

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by tlhackque

On 11-Jul-17 12:54, Jason Glazer wrote: > I run several MailMan 2.1 mailing lists and some subscribers are > frustrated by the way pipermail deals with JPEGs that are embedded in > the messages and also with how attachments are handled. Does hyperkitty > in Mailman 3.1 do better on these issues. > > Assuming this message gets archived, I am going to try embedding a > small picture right here: > > Hopefully that shows up in the archive. I won't add an attachment > because the list may not allow it but I'm curious how those are > handled. > > Thanks > > Jason > -- > Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair > Admin for onebuilding.org building performance mailing lists > I know that this particular list is setup to strip HTML and only distribute text/plain. I haven't gotten to HyperKitty configuration yet (a lot of plumbing yet to do for my environment), but I too am interested in having HTML mail archived & viewable as an HTML MUA would show it. I pretty much gave up on the 2.1 archiver for the HTML lists. Instead, I subscribed a mailbox to the lists, and served it to the community read-only with IMAP. Dovecot handles private 'seen' flags for shared mailboxes, so this let people use their favorite e-mail client to browse the archive. I'm hoping that I won't have to reconstruct this for my new environment...but it's an option.

8 years, 2 months

[MM3-users] Re: The doubled entries issue

by Stephen J. Turnbull

Lars Bjørndal writes: > select * from listarchiver where name = 'mhonarc'; > > and get: > > id | mailing_list_id | name | _is_enabled > ----+-----------------+---------+------------- > 1 | 2 | mhonarc | f > 9 | 4 | mhonarc | f > 13 | 5 | mhonarc | f > 17 | 6 | mhonarc | f > 21 | 8 | mhonarc | f > 25 | 9 | mhonarc | f > 29 | 10 | mhonarc | f > 33 | 7 | mhonarc | f > 37 | 11 | mhonarc | f > 41 | 12 | mhonarc | f > 45 | 13 | mhonarc | f > 49 | 14 | mhonarc | f > 53 | 16 | mhonarc | f > (13 rows) > > mailman=# > > So which lines should I remove, and how do I do that? None of them? You have one entry per mailing list, which is as it should be. Also, your preceding message doesn't complain about the database, it complains > raise ComponentLookupError(interface, name) > zope.interface.interfaces.ComponentLookupError: > (<InterfaceClass mailman.interfaces.listmanager.IListManager>, '') That says that "python scriptname.py" need the IListManager interface but can't find it. You didn't provide enough information to explain why that might be, so I'm not going to guess. Tell us more about the "duplicate entries" error, and if possible copy it exactly from where you found it originally, including any traceback. Also tell us more about your installation. Is it a distro installation? If so, which one, what version of Mailman? Is it a venv installation? If so, did you activate the venv before invoking "python scriptname.py"? If you didn't, try that and run scriptname again. Steve

1 year, 10 months

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

by Stephen J. Turnbull

Odhiambo Washington writes: > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * I think just putting these as close to the top as possible, and including a comment (or two) saying that this is importing defaults that can be overridden by any assignment made later in the file is about as far as we can go for explaining. If you don't know how Python imports work, just ask about the specific case. There's quite a bit of potential complexity hiding in those '.'s; much more complicated than the '/'s in a file system path. Trying to explain the ins and outs of the Python import system is way beyond the scope of Mailman docs. > [At first instance, it is not obvious that mailman_web.settings.base > and mailman_web.settings.mailman are actually paths in Python - > which magically translates to mailman_web/settings/base.py and > mailman_web/settings/mailman.py] You shouldn't have to know that, it doesn't help with the bigger problem of finding mailman_web, and any simple explanation might turn out not to be true in your installation. This is why I prefer flat files for end-user configuration, even if they get pretty big. I understand why developers do stuff like this, but it's not "naive user"-friendly. > For example, my mind all along has been tuned to having a settings_local.py > for overriding the settings.py. Yes, and that is a better system unless our intent is to *hide* settings from the user, in my opinion. I don't see why you chose to deviate from it. Either way you have to integrate settings you have changed with settings the developers have changed. It's easier if you stick with the system you're most familiar with. > However, with this particular documentation, it would appear that > everything is intended to just go into /etc/mailman3/settings.py. > > Is it possible to modify the documentation Which documentation? We can modify our own, but that's a pretty big task because we have several different systems for managing config files over the last five or ten years. We shouldn't mandate any particular organization because they all still work, and people who use older setups shouldn't have to do without our docs. And we can't do anything about out-of-date mirrors or HOWTOs by random admins on the web. > and that those settings are in what file(s) ? But we don't know where those files are. If you use a venv install, they're almost certainly in $MAILMAN_HOME/venv/lib/python3.N/site-packages/mailman_web/settings/, but otherwise the mailman_web/settings part could be anywhere on Python's search path. And on modern systems unless you have a dedicated host with everything installed at once, you're likely to have 3 or more Pythons installed (Python 2.7, and two or more Python 3s). So tools like find and grep -l are often more confusing than enlightening. I think if you get confused, the most efficient solution is to just ask. If Mark or I or whoever directs you to check out the defaults, and you can't find them, ask again. Steve

2 years, 7 months

[MM3-users] Re: Office365 posts shunted (authres.core.SyntaxError)

by Stephen J. Turnbull

brylon(a)oit.rutgers.edu writes: > Thanks for the response. You are correct in the fact that I've > enabled/configured the ARC module, however, I don't think Mailman > is adding that (malformed) header considering I'm now HOLDing the > test email(s) sent to our postfix inbound MX servers *before* they > are LMTP'd to the Mailman server and its already there when I > postcat it. OK, thanks for that clarification. I feel better (but will still check it! just a bit less urgently ;-) What do you still need from us? I guess the easiest thing for us would be to catch the Exception in our ARC module, and ignore nonconforming Authentication-Results, so that there will be no ARC signature from Mailman on those posts. Will that do? (Note that "ignore and/or delete" is the RFC recommendation. I'd need more than "it would be nice" as a reason to try to parse non-conforming A-R. Mark's experience with parsing *conforming* (non)delivery notifications is quite a deterrent to that.) > At the same time I also can't fathom that Office365 has this wrong > (still?) and no one has noticed/complained? I guess I would say, how would we know if there were complaints? ARC is a very recent addition to Mailman, so you wouldn't necessarily see it here yet, and Office365 doesn't have a public bug database AFAIK. ;-) Microsoft (and other > 1G$ corporations) have a long history of "embrace, extend, and drive conformant implementations out of business".

5 years

[MM3-users] User account issue after importing data from Mailman 2.x server

by dgoldsmith＠sans.org

We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. I just started looking at a user and a list in both the Postorius and Django admin web UIs and found: - in Postorius: - list exists, has 20K plus subscribed members and has 3 list owners - user exists and is subscribed to this list - in Django: - in HyperKitty section - in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators) - in the Emails page, there are 149K plus entries - in the Profiles page, there are 147 entries - in the Accounts->Email addresses page, there are only 155 entries - in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Thanks, David Goldsmith

10 months, 3 weeks

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Stephen J. Turnbull

Michael Bakonyi writes: > allright, thx a lot for your quick answer! After fiddling around > some more time, I guess I had some misunderstandings regarding the > REST-API. I guess if we reach the API correctly, we will not be > confronted with the CSRF-Error. We will continue to try but > nevertheless: What would be a cleaner approach to reach the API > from an external IP? I didn't found any examples in the web so far. If you mean the core REST API, you won't find any useful examples on the Internet. Anything you do find should be considered a form of self-harm and/or an insider threat. Access to the REST API is not securely authenticated, and therefore should never be exposed to the Internet. This API is expected to be contained either to localhost, or to a subnet behind a firewall that prohibits access to that port except from the host(s) serving HyperKitty and/or Postorius. If that's what you're trying to do, I would suggest a secure tunnel (not a generic VPN, but a specific tunnel to the API port). If you're talking about the Django administrative API to Postorius, you'll probably get a better answer faster from Django channels. Mark may know but he won't be available until mid-September most likely. As I wrote earlier, as far as I know you need to access the Postorius port, provide credentials, get the CSRF token, and then access Django. Regards, Steve

3 years

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by William Oliver

On Tue, 2021-12-28 at 20:05 -0800, Mark Sapiro wrote: > On 12/28/21 5:58 PM, William Oliver wrote: > > On Tue, 2021-12-28 at 17:50 -0800, Mark Sapiro wrote: > > > The recommended uwsgi.ini includes > > > > > > pythonpath = /etc/mailman3/ > > > > > > according to > > > https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… > > > > > > this should work. Did you have that? If you did and it doesn't > > > work, > > > perhaps adding > > > > > > env = PYTHONPATH=/etc/mailman3 > > > > > > > Yes, I had the first, and does not work. The second entry works. > > > I updated the doc to use > > env = PYTHONPATH=/etc/mailman3 > > I don't know enough about uwsgi to know for sure, but the issue may > be > that setting pythonpath in a running python process doesn't work - > it's > too late as the path is already set in python's initialization. > You might add that it may be necessary to do it in .bashrc for linux folk -- I got it to work but as I've demonstrated, I can sometimes make mistakes and leave detritus around. I may not have successfully cleared my previous setting. That being said, I think it works. I am, I am afraid not a details-oriented guy, which is a bit of a drawback for someone doing system admin...

3 years, 8 months

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

by Mark Sapiro

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

5 years, 11 months

[MM3-users] Re: Syncing Real Name between user account and membership

by Abhilash Raj

On Sat, Dec 19, 2020, at 10:42 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > a user was mass-subscribed (with a wrong name) and now registered > > and changed his name via the web interface but the list entry is > > not changed. > > I don't recall the design discussion, but I'm pretty sure that this > distinction was intentional. The idea was that people might want to > have different display names associated with different addresses (eg, > you probably don't want your User display name associated with an > address you use on anonymized lists). I'm not sure that option has > any merit in practice. > > @ Abhilash: > > Since Postorius doesn't provide a way to manage address-specific > display names, we should probably have Postorius propagate display > name changes. I believe that is normally what the user wants. > > What does everybody think? +1, I've been thinking the same. I am just wondering if Core's API should do this (probably not by default, but with a bool parameter that P can use every time), or should we iterate over all addresses and PATCH the display names in them (would be slower, with multiple API requests). I am leaning towards the first option. What do you think? > _______________________________________________ > 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)

4 years, 8 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > That said, the effect on the OP's case, which may be more common, may be > harmful depending on list and Mailman config. > > The original message from the OP (edited) is > ``` > Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" Ouch, that's a mess. First, unless you elided it, it's missing the required type parameter. Despite being required, it's basically an optimization and in most cases will not be much of one. So that's not really a big deal. Second, the Content-IDs are malformed. They are supposed to have the form of message IDs. Also not a big deal, they're close enough for government work. The big problem is I have no idea what the semantics of multipart/related text/plain image/jpeg should be. Throwing away the image data seems like it would be the right thing to do according to RFC 2387, which delegates rendering of the entire multipart/related entity to the root entity. But if that were the desired result of the author of the original message, it's straightforward to achieve by inverting the related and alternative parts. And (at least for image content) I would think that would be a rare intention. I don't see an obvious way to resolve this without checking what popular MUAs do with the various possibilities. So as long as your patch does the expected thing, it's the minimal solution. Steve

7 months, 2 weeks

[MM3-users] Re: Moderation action "None" is misleading

by Stephen J. Turnbull

Markus Grandpré writes: > Hopefully we won't have to wait too long with Debian Debian has traditionally been quite slow to update Mailman, and they're following tradition. Both the testing and unstable distributions are still on Mailman 3.3.8. Regarding your specific issue of Kein/None, testing has the same version of mailman-web (dated 2020-05-30), while unstable has a much newer version of mailman-web (dated 2024-03-12). That should resolve that issue, but you will have to wait a full Debian development cycle at least. Our standard recommendation is to do a source installation in a Python virtual environment, point the new installation at your $SQLDB, review the content of /etc/mailman3 (I think Debian puts mailman3 configs there and that's what we recommend), test the new installation, and if that works, remove the Debian installation after preserving the /etc/logrotate.d/mailman*, /etc/cron.d/mailman*, and /usr/lib/systemd/system/mailman*.service files which are probably generally appropriate for Mailman 3 installed in a Debian system. There is also a containerized distribution of Mailman 3 suite, but I don't know how straightforward it is to port over a Debian packaged system to that environment. It may sound pretty fearsome, but you can hire people to do the installation and testing (maybe for as little as a pizza and a mug of beer ;-). After that you will get a more reliable system and better support (really, almost all the Reply Guys here run up-to-date systems of that kind, so we're much more familiar with it than with distro installations). Steve

7 months, 1 week

Search results for query "dO"