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

[MM3-users] Changing subscription address

by Stephen J. Turnbull

Allan Hansen writes: > Will I now have to tell her to do this for each list she is subscribed to: > > > Select ‘Mailman Settings’ in dialog pulldown. > Select one of the lists listed. > Click on ‘Manage Subscription.’ > In ‘Select Emai’, select the ‘Primary Address’ pulldown option > Click on ‘Change email used for subscription.’ Yes, that appears to be the case currently. > Someone on list some time ago advised me that it was possible to do > this easily globally. I think that what they are referring to is that if you 1. Create a user account. 2. Set and authenticate a primary email address. 3. Allow all subscriptions to inherit from 'primary email address' (rather than setting any address explicitly) *then* 4. Changing the primary email address will change the subscribed address to all the lists. Or they might have meant doing it with a script. But I didn't find a way in Postorius. > Please make this easy, as I get these requests all the time and > some, like this one, are on many lists. I don't have the Postorius knowledge to do this in a reasonable amount of time to help your user immediately, but how about this design: In the 'Mailman Settings' screen, List-based Preferences' tab, currently each list has an active link at the list's posting address (which links to a page with the same options carefully documented), a plain text display of the subscribed address, and a row of options. Suppose we 1. Add a popup menu of addresses and attach it to the displayed address for each subscription, 2. Add a 'select subscription' checkbox to each subscription. 3. Add an 'act on all selected subscriptions' fake subscription, whose checkbox has the effect of select or deselect all. I guess this should be at the top.[1] Does that seem like what you have in mind? Any other needs you want to mention? (Suggestions for feature design are welcome, but "I do this often and there's got to be a better way" is good too.) Regards, Steve Footnotes: [1] Notes to implementers: The 'act on all' row needs tristate options. It should be at the top. The "fake list" itself can be a link to a heavily documented page like the regular per subscription page but with a couple of notes on the special behavior of the selection checkbox and the tristate options. When we "subscribe by address" (mass subscribe, email subscribe) rather than via a logged-in user, we should create a user, give it that primary address, and subscribe by primary address rather by that address literally.

4 years, 1 month

[MM3-users] Re: Where to find disabled members?

by Bill Oliver

On Mon, 2024-11-04 at 22:36 -0800, Mark Sapiro wrote: > On 11/4/24 19:28, Bill Oliver wrote: > > > > a) See who is disabled, and > > b) un-disable them by hand > > > > or... do I just have to wait seven days for them to automatically > > get > > un-disabled? > > They do not get automatically re-enabled ever the user or you has to > manually re-enable delivery. > > For an individual user, in Postorius you can click the user in the > members list and see their delivery status and reset it. > > To deal with the whole list membership for a list, you can do > ``` > $ shell -l list(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list(a)example.com mailing list > >>> for member in m.members.members: > ... if member.delivery_status == DeliveryStatus.by_bounces: > ... member.preferences.delivery_status = > DeliveryStatus.enabled > ... > >>> commit() > >>> > ``` > If you just want to list them > ``` > >>> for member in m.members.members: > ... if member.delivery_status == DeliveryStatus.by_bounces: > ... print(member) > ... > >>>``` > Thank you. It worked like magic. Looks like I've got some learnin' to do with respect to the cli. I've never played with it beyond the commands indicated for installation. It looks like a great way to manage things. I much prefer a cli to gui for most of this kind of thing. billo

5 months, 2 weeks

[MM3-users] Re: Emergency Moderation

by Abhilash Raj

On Sun, May 24, 2020, at 7:27 AM, Stephen J. Turnbull wrote: > Brian Carpenter writes: > > > Can I add this through a mailman core update via pip? > > Eventually .... This depends on when Abhilash gets enough content and > a little bit of time to do a new release. FWIW, you can also install from Gitlab directly simply using pip: $ pip install git+https://gitlab.com/mailman/mailman@master You can use `@` to specify a git reference, like a branch name or tag name or a commit hash would also work. > > Getting meta: You've been asking for very recent features fairly > frequently. I understand that everybody feels better with released > code, but to be honest, we do not have a deep quality assurance > process. The test suite is voluminous and quite comprehensive, but > that's not the same as having a proper beta process, mandatory > reviewing, etc etc. It's not obvious to me that we can do a better QA > for you than you can do for yourself. Our QA process is basically mail.python.org (m.p.o) and lists.mailman3.org and couple of other server Mark runs for his personal stuff. We get notified about the major breaking changes pretty fast (m.p.o is pretty important to keep up) but some small changes do get piled up until I get to them. I have a decent number of errors from Sentry that I should look at, many of which are triggered by weird inputs. It needs a bit more work and balance between bugfixing and new features, which I haven't been very good at :( I can however do more rc and beta releases if there are people out there willing to get/test out new features faster. With the current releases, I am first time releasing some rc versions, but I think I might keep up the 1-2 week rc period for upcoming releases. > With that in mind, have you considered building your own from source, > on a branch from a moderately recent tag, and cherry-picking only > commits for features you really want right now? > > I admit I don't know how appropriate that is in our tree (I just build > from master all the time), but I think that Abhilash is probably > pretty careful to pull complete branches so that this should work. If > it looks to you like the patches are a little "ragged around the > edges", we can work on the process and try to make it more amenable to > such cherry-picking for people like you who need some of the most > recent commits ASAP, but don't want to accept the whole "bleeding edge". The one huge issue with "clean" cherry-picking is NEWS.rst in each repo. There is a little bit of manual intervention involved always to update the changelog. We could adopt a different more specialized tool like Blurb[1] that CPython uses, but I find it a little too cumbersome for a small project like us. It might just end up making contributing to Mailman a bit harder too (extra tool to install and create NEWS files vs adding a new line in NEWS.rst, pretty small change but things add up!). [1]: https://github.com/python/blurb_it > > This also would be useful for your Affinity etc development, I think. > (Of course maybe that's what you're talking about, but "emergency > moderation" is a pretty common need in production.) I am "trying" to do more frequent releases. There are a lot of bugfixes and REST API enhancements coming up in the next version of Core, including like Mark said, emergency flag being exposed. I **think** emergency was the last one pending to be exposed via API, I did a whole bunch of them in previous version but missed out on `emergency`. There are a bunch of un-used attributes of MailingList (like topics, expire_subscriptions_after etc) which don't *need* to be exposed and they get mixed with some other useful ones. If anyone finds something useful that isn't exposed, please open a ticket or even better submit a MR (it is really quite easy![2]). [2]: https://gitlab.com/mailman/mailman/-/merge_requests/643/diffs > > 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, 10 months

[MM3-users] Change config to create a new list with all archives off

by Stephen J. Turnbull

Tibor Molnar writes: > Can archiving be changed anywhere in mailman3 configs, so then all > new lists created do not archive by default? Unfortunately, no. Once we get last year's GSoC merged, there will be, but that's going to have to wait a few weeks as it's not really ready and I don't have time for a while. What you can do is create a style in Python and make that the default. In $SITE_PKGS/mailman/styles/default.py, append: -------------------------------- cut here -------------------------------- from mailman.interfaces.archiver import ArchivePolicy @public @implementer(IStyle) class ArchivesDefaultDisabledStyle(LegacyDefaultStyle): """The legacy default style with archiving disabled.""" name = 'archives-disabled' description = _('Ordinary discussion mailing list style,' ' with archiving disabled') def apply(self, mailing_list): super().apply(self, mailing_list) mlist.archive_policy = ArchivePolicy.never -------------------------------- cut here -------------------------------- In mailman.cfg find and modify or create: -------------------------------- cut here -------------------------------- [styles] default: archives-disabled -------------------------------- cut here -------------------------------- Untested, feel free to ask if it doesn't seem to work. This really should be implemented as a plug-in so default.py being overwritten in an upgrade won't be a problem, but the plug-in API is annoyingly complicated and the example plug-in over-engineered, and I couldn't get it to work (and in the project where I learned to do this I am not being paid enough to care ;-). The approach above was straightforward. Eventually I'll get around to doing the plug-in approach, and maybe in the meantime Mark or Abhilash will speak up. If Those Who Know don't show up soon, ask again in the medium term (but before you update Mailman and it gets overwritten :-). Steve

1 year, 10 months

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

by Stephen J. Turnbull

Odhiambo Washington writes: > The issue you're dealing with in that case is this change in > PostgreSQL-15 discussed in this blog: > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… Thank you for the reference! If you have a Mailman-only host, with a Mailman-only PostgreSQL, or The Cabal of equally responsible maintainers are the only people who work on the Postgres cluster, the two approaches are basically equivalent. My take is that the default "right thing" is to transfer ownership of the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON SCHEMA public TO fred" in the case that you don't want to give "sudo mailman" to Fred. Rationale: I believe there are a number of things that the 'postgres' user can do that other users cannot, and you probably don't want random contractors or new volunteers to have those privileges. On the principlee that 'postgres' should only do those things that only 'postgres' can do, you want to make the 'mailman' user the owner of the 'mailman' database (and 'mailmanweb' too if you go that route). Then if you have a user 'fred' who may be working on both mailman and non-mailman databases in a session, then instead of giving sudo mailman to Fred, 'mailman' can grant all on schema public in mailman to 'fred'. It's a really fine difference, and probably will matter to almost nobody running Mailman 3. I do think user 'mailman' owns the 'mailman' database is conceptually simpler than user 'postgres owns the 'mailman' database and 'mailman' has ALL privilege on the PUBLIC schema Right? Steve

1 year, 2 months

[MM3-users] Templates do not work

by Stephen J. Turnbull

Eggert Ehmke writes: > When I look into mailman/mm/var/templates the directory is empty. > Nevertheless, the templates I create in Postorius seem to be stored > (where?), That is expected when you create templates in Postorius, because they are stored in the RDBMS (eg, PostgreSQL). > they just do not work. My first guess would be that there's a language mismatch. You need to create a variant template for each language that is used. I'm not sure offhand how the system chooses the language for stored templates vs the language for templates used for messages (I suspect the used template is the one for the list's default language), but an incomplete set of variant templates and a mismatch between the language the variant template was created in and the default language of the list is what I would guess. Steve

2 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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 ????? Thank you 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

7 years, 9 months

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

by Stephen J. Turnbull

Lars Schimmer writes: > Intereting view for a software poackage taking a few years to get a > way to migrate from mailman2 to mailman3. Or in other words: if a > stable version is not useable/to old, the software is not > production ready. Not our problem though. It was the distro's choice to provide Mailman packages. We're happy that they're interested, and happy to do what we can to support their users when they come here. But it's up to them to judge whether their packages are useful to their users. >> For constantly evolving projects where you need to be current, >> [distribution packages are] more of a detriment. > Nope. Vote against this view. > You need a stable system to rely on and setup without hassle in a nonce. Then what are you doing here? That is not Mailman 3, as you can see from reading this list. Once working, Mailman 3 is quite stable as long as you understand the parameters (for example, what a shunted message is, and what configurations are available from Postorius and what requires shell access). But it is not yet hassle-free to set up (unless you use Brian's guide on an otherwise empty host ;-). Mailman 3 is still a work in progress, with a wide variety of requirements from our users that only we can address. And again in <428b33e6-189b-3a13-0bab-b5d77735d8ab(a)cgv.tugraz.at>: > So, why does someone not care about the debian package to fix that bugs? > It is possible, and is done by other packages every day. Not our problem. Ask the Debian maintainer, who is not a core Mailman developer. > Thats why I like to stay with 1 standard for all softeare packages > on one system. I do not want to run 20 software distributions with > 20 ways of doing it the right waay (tm). I doubt anyone disagrees, but yet again, not our problem. Our problem is that y'all choose 20 different software distributions and somebody among you wants to run Mailman on each one of them, embedded in an equally wide variety of network configurations. You really should be over on some Debian list with this thread. I understand your frustration, but we have no obligation and no intention to do anything about it. We're here to maintain Mailman itself and never said anything else. If the Debian maintainer has specific requests of us, I'm sure all of us would take a strong interest in that. But maintaining the Debian packaging itself is his/her chosen job, not ours. Steve

4 years, 1 month

[MM3-users] Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by Stephen J. Turnbull

skenny(a)scss.tcd.ie writes: > But deleting and then creating a new blank mailmandb database just > prior to importing ... it can't be the right thing to do. If you're using containers, then you're using a system that should be turnkey for the *Mailman* admin, who isn't necessarily the *database* admin. So the database is going to be already populated to some extent. That will cause conflicts when you import a database dump, because the dump expects a blank slate. AFAICS (I haven't done it, so this is just theory) this *is* the right thing to do: blank out the database so the import just works. Does the installation work when you do it this way? If not, what is the problem?

2 years, 9 months

[MM3-users] Mail configuration

by Stephen J. Turnbull

Darren Smith writes: > We have been told that "warming up" the IP is the way to go - that is, > cutting over just some of the traffic a little at a time. AIUI the IP that receiving ADs care about is the last hop IP, ie, the source of the SMTP connection. I haven't done this myself, so take this with a grain of salt, but I would (1) Document the new IP with an MX record for your domain, as well as A and AAAA records as appropriate. This means you'll have to configure it to MX for the whole domain, of course. You can keep the load down by giving it low priority. (2) Set up the MTA on the Mailman host to send occasional mail via the new host. If the MTA doesn't know how to do it itself, you could do something really hacky like restart the Mailman host's MTA with different configurations at say 8am (current outgoing MX) and 5pm (new outgoing MX). You could also do something even more hacky with the routing tables. I don't think this really has anything to do with Mailman itself, although it probably wouldn't be hard to add code to round-robin some outgoing mail to an MTA configured to MX via the new IP. > So what I am looking for is a way for all mail on our domain to be > sent to our current mailman installation, All mail, or just the list mail? > and based on some configuration (certain mailing lists?) I would not do this by mailing list. Some reputation systems work on tuples, ie, (target mailbox, source IP, source domain), so only the lists configured to go via new IP would "warmed up". It also seems likely that recipient domains with only a few subscribers on your lists would have unbalanced distribution across your lists, and so might be missed entirely. > certain emails being sent out to the list subscribers will first be > forwarded to the new server and be sent from the new IP address. > > Does that make sense? As a strategy, yes, but how difficult to implement reliably, I don't know. > Does anyone know a way that mailman/postfix can be configured to accomplish > this? > > Is there a different forum where I might be able to ask experts about this? 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.

7 years

[MM3-users] Re: Mailman 3 localization

by Alexander Klotz

> This is managed entirely through Launchpad/Ubuntu. Nothing has been > contributed back to upstream, and nobody has volunteered to do the > work of pulling those files into our source tree and maintaining them > as they are updated (there is a lot of churn in translations; keeping > them in synch with release code is quite labor intensive). > > I would assume you can drop the .po file(s) into > mailman/src/mailman/messages/ru/LC_MESSAGE/ and the build and install > process will do the right thing. We would like to contribute further german translations, since there are still some parts missing, e.g. in the postorious interface. Would https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate be the right place to do so, so that everybody could use our translations? If there are other areas in which you could use our help, please let us know. Regards, Alex

6 years, 9 months

[MM3-users] getting all registered users and their lists

by IOhannes m zmoelnig

hi, TL;DR is there a scriptable way to get all users that have registered in my mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? longer version: we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that this is not the newest version; at this point, please refrain from asking me to upgrade my Debian installation or even to switch to a venv installation of mailman3: i'll eventually do that but right now i've gt a problem to solve :-)) a few weeks ago, we invited a number of people to join a new mailinglist via a link that points to the subscription interface of the list, e.g. <https://lists.example.com/postorious/lists/foo.lists.example.com/> now of course a number of these people had problems with the webinterface, confusing the big "Subscribe" button at the bottom of the page with the much smaller "Sign Up" button in the header (in German this button reads "Registrieren" which has a meaning that is pretty similar to "Subscribe"). people that "Signed up" typically do not understand that they have not been subscribed to any mailinglist (yet), wondering why they do not get any emails. at least this is what we suspect from feedback we got. to fix the situtation, i would like to check which users had this problem (and eventually contact them to explain the problem). for this i would like to get a listing of all users that are not subscribed to any mailinglist. i would also like to query, when a given user has signed up (so i can reduce the number of false positives) how would i do that? ideally i would rather not work on an SQL level. gfdmfas IOhannes

3 years, 2 months

[MM3-users] Re: Installation Questions [Installation}

by Arte Chambers

For other things like the systemd service and the postfix and web server configs, you need to do them as root (via sudo). Does this mean i need to add the mailman user as a sudoer? On Sun, Nov 3, 2024, 8:07 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > > Hello everyone, > > > > I'm running Ubuntu 24.10 and following the Virtualenv instructions > > < > https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u… > >. > > When creating the mailman user per the instructions I find that the > mailman > > user doesn't have sufficient permissions to do things later in the > > installation such as creating files in /etc. What steps should I take to > > ensure that the mailman user has the correct permissions to install the > > Mailman app. > > > We should probably cover this in the docs, but for /etc/mailman3, you > should do > ``` > sudo mkdir /etc/mailman3 > sudo chown mailman:mailman /etc/mailman3 > sudo chmod 755 /etc/mailman3 > ``` > Then you can create all the subordinate files as the mailman user. For > other things like the systemd service and the postfix and web server > configs, you need to do them as root (via sudo). > > -- > 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 paul.m.robey(a)gmail.com >

5 months, 2 weeks

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

by Henrik Rasmussen

> The bottom line is at this point, <https://bugs.python.org/issue27321> > no longer affects Postorius, but it still affects message delivery. I > have opened <https://gitlab.com/mailman/mailman/issues/406> about > defending against that and also the UnicodeEncodeError you included in > your OP. Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command > is 'bin/show_qfiles'. I much be in the wrong place because when I do a 'docker exec -it mailman-core bash' and do a 'mailman --help' I don't see a 'queue' argument. The only bin/mailman I have inside the mailman-core container is /usr/local/bin/mailman, which is the same command.

7 years, 6 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/30/20 1:25 PM, john_warland(a)hotmail.com wrote: > I came across this same error and solved it doing some googling and came across this statement. > > in main.cf: > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > > change it to: > local_recipient_maps = > > It fixed the immediate issue but I do not know enough to say why. Hope someone can elaborate on this. Setting local_recipient_maps = disables all local recipient checks. If you don't want to do that, you need to specify whatever the current or default setting is in addition, e.g. local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/var/data/postfix_lmtp See <http://www.postfix.org/LOCAL_RECIPIENT_README.html> We need to update the docs for that setting. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Bill Oliver

On Mon, 2024-10-28 at 21:08 -0700, Mark Sapiro wrote: > [ > [snip] > es. See the last part of the section at > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… > > where it says in part `And, create the > /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: > ...` > > > I found a template here: > > > > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman- > > hyperkitty.cfg > > > > > > Do I need to copy and paste that in my installation? > > > It, or something as mentioned in the above doc needs to be at the > location defined in the `configuration:` setting in the > `[archiver.hyperkitty]` section of mailman.cfg > > -- Hah! If it were a snake it woulda bit me. I can't believe I scanned right over it. Thanks! billo

5 months, 3 weeks

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

by Torge Riedel

Am 10.02.19 um 06:20 schrieb worik: > How do I turn off the social logins? > > I looked in the admin manual but > > They are not working, but I absolutely do not want them for now. Maybe > one day, but my users will be allergic to even the hint.... > > Worik > +1 I do agree, same here on my side. I need to migrate from mailman2 to mailman3 and was wondering why social accounts are enabled by default and are difficult to disable. Lot's of my users are very "sensitive" to social media and don't want see them here. I propose something like an additional setting listing the enabled social accounts. And if the admin is setting this to an empty value in the settings_local.py everything is disabled, even if new ones are added later. Without the risk to break something import. Best regards Torge

6 years, 2 months

[MM3-users] Re: Verification Failed Error

by Stephen J. Turnbull

Abhilash Raj writes: > You probably have > > verify = sender > > somewhere in your exim.conf, which is causing this. No, that seems unlikely. This is in the default exim.conf. > You can either modify the > > DEFAULT_FROM_EMAIL > > in your settings_local.py so that it is a real address that Exim can verify, He's already modified that, since the default in settings.py is "postorius(a)localhost.local" (which is a bug: this should default to a mailbox, and the domain should be added automatically if only a mailbox is given). It seems likely that what needs to be done is to set up a mailbox for Postorius, which can be done in several ways. When does Postorius receive mail? I guess it *sends* mail for the mailbox owner confirmation dialogs on subscription or password reset, but that confirmation is normally done by a web transaction, right? If <postorius> rarely gets mail, the obvious thing to do would be to alias to site owner or postmaster. (It looks like Django doesn't know how to receive mail, so any facility for postorius to receive mail would have to be configured in the MTA.) If it's not that, then the problem likely has something to do with the containerization, and the MTA getting confused about which host is which. > or, you can remove verify = sender from your Exim configuration. Don't do this. If you set up a separate Exim router for "postorius" (to do something fancy like a autoreply bot or delivery to /dev/null ;-), you can put the no_verify option in the Requires stanza for it. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 4 months

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

by Mark Sapiro

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

5 years, 3 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > So it's even weirder – however, I'm really not sure if this is > > the address HyperKitty is checking for, as I have 3 attached to > > my account! How may I know which one it's trying to use? > > If you go to https://example.com/user-profile/ what Primary email > and Other emails do you see? Do you see all three? And if you go to > https://example.com/mailman3/users and click Manage for your > address, do you see all 3 under Addresses? Is it possible this is a weird new symptom of the "multiple entries for archiver" bug? -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 2 days

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

Brian Carpenter writes: > I reported a serious problem. Inability to change display name is an annoying problem that probably *will* affect quite a few users, and if they can't do it themselves, it will affect list admins and then site admins who are asked to do it for them. Nobody has said we won't work on that, but it's not like we've had 1000 reports in the several years that Mailman 3 has been in production use. Nor is it all that big a deal: the user retains control of the display name in each post (modulo the DMARC mitigation). As far as I know the stored display name is only used cosmetically (in the UIs for user configuration of Postorius and HyperKitty and in administrative mail to the user). > The reply was to bring up assumptions that should not be made such > as a list member is actually a registered user. I'm not sure what you think is going on here. Users (registered) are the locus of authentication in Mailman, and as such they are more or less equivalent to Mailman's raison d'être, namely giving (human) users control of their own subscriptions. The difference between Mailman 2 and Mailman 3 is that in the former a user *is* an address, in the latter a user *has* an address (and maybe several). The original "user == subscription" model of Mailman 2 is plausible, but it wasn't sustainable. The users and admins we hear from most are "heavy users": the users subscribe to dozens of lists, typically several on a single host. They *really* wanted a single user that could provide a dashboard with one authentication, convenient default settings for new subscriptions, and access to information about all subscriptions and the user profile in the dashboard. And that's why Mailman 3 has a model with users (the core concept corresponding to human beings), addresses, and subscriptions (memberships), where most addresses are backed by users. > As you said they [list members] are not [registered users]. I'm pretty sure I didn't say that, but if I did, it's *still false*. Users are the core concept. It's *possible* to have addresses (and maybe subscriptions?) without users, but the normal case is a user which has one or more addresses, which are subscribed to one or more lists. > Regardless of whether they are just a list member or a list member > that is also a registered user, there is NO MECHANISM in place > where you can change their associated display name Ie, you agree. The *issue as originally reported* is that the display name cannot be changed in Mailman's database. > AND their data is not entirely removed when a reasonable assumption > is being made that it has, It's not reasonable for Mailman 3, as Mark and I have explained. > such as list unsubscribing. If a user unsubscribes from a list, that unlinks *one* of the user's addresses from *one* list. Assuming that that has anything to do with existence of user data is unwarranted in Mailman 3, and it was extremely weak in Mailman 2 as well, since unsubscribing fron one list doesn't change the fact that the address may be subscribed to other lists on the same server, likely with the same metadata (really the password was the only important thing, but that confirms the principle). If you want to automatically delete any associated user any time a list is unsubscribed in Affinity, you *can* do that. I don't think it's a good idea, not at all, but you *could*. I deal with the case where the user has exactly *one* subscription below. But that is not the general case. > Sorry but I can't see how this behavior can be justified Then you need to cool down, and think about how this actually could work, not how somebody who makes incorrect assumptions would like it to work. > and also not being made a high priority to fix. Offer me 25,000 yen/hr and I'll do the display name change next week. Priorities differ. > Some may think that retaining data when there is a reasonable > assumption that it is being removed It's not a reasonable assumption in Mailman 3, though, as Mark and I have explained. > is immoral and not just a violation of GDPR. I don't disagree for reasonable assumptions. I'm well-aware of the ethical and legal issues here. We may want to add a facility so that users can delete themselves. But that's a *hard* problem if it's going to be "right to be forgotten" compatible because you can't keep backups -- we need to be sure that the user knows what they're doing (and if they've assumed that the data "should" be removed, we already know they don't know what they're doing!) I don't think we keep Bitcoin wallets in the Mailman metadata (yet ;-), so deleting your user won't bankrupt you. But you will lose all your *other subscriptions* and your default settings, etc. The latter is a PITA until we build up a nice suite of templates (and I don't think we have user templates yet anyway). And once we do add that feature, it probably makes sense to offer to do so (after explaining the consequences) if the user deletes their last subscription. But I just don't see this as a major issue, except maybe for corporate users under GDPR and friends. And I doubt *they* will even blink at my consulting rates. :-) > As I said in my reply to Mark, it is a big deal for list owners > (admins) because they are the ones that are going to be interacting > with Postorius/Affinity the most. Technical question: Why do you include Affinity? As far as I know, Mark is correct, you can both change display names and delete users with mailmanclient, and therefore with the REST API (mailmanclient is just a wrapper around the REST API, it has no superpowers). In Affinity, this behavior is under *your* exclusive control. I also don't agree with your claim about admins interacting most. Yes, they will interact more often, but in my experience most interactions are conducted by ordinary users, not admins. That may not be true for your hosted lists, since they're aimed at a very different population from my software devs and economics professors and university students, but there are large populations of users out here who are perfectly happy to manage their own subscriptions, thank you very much. In any case, there's very little difference between users and admins for this kind of feature, *except* the scope of resources they can view and modify. If Postorius gives the feature to users, it will be trivial to enable it listwide for list admins, and vice versa. But deleting users is an even harder problem with respect to list admins: what if the user is subscribed to a list on a different virtual host that the list admin can't know about and the user may not realize is the same Mailman user? *Probably* it's good enough to refuse to delete the user in that case, but it's not obvious to me that users who make wrong assumptions will see it that way. > Most list members, especially those migrating from MM2, will not be > registering with Postorius/Affinity. I'm not sure what you mean. If you mean "the migration script will register them", OK, but they're still registered and still subject to the user-address-member model. But Postorius is just a UI. Postorius does have its own database, which is often confusing, but the user-address-member model is in core. It's core where the important registrations for subscribers take place. You can have a user-less address in the database, but for the address's owner to do anything with it, such as subscribe to a list or set a list to vacation mode, they have to authenticate (that includes implicit authentication with the OTK used to confirm a new user), and to authenticate they have to have a registered user, not just an address. Most addresses will be associated with users.

4 years, 6 months

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 12:58 PM, Rafael Mora wrote: > > Does the rDNS PTR record should be placed in my Centos7 server? You can't do this. Hostgator or whoever manages the network (Telmex Colombia S.A. ?) has to do this. > I've created the DNS A record for lists.labbrands.com with the IP but I > don't know the port that it uses so I can make a port redirect to my local > ip address wich is 192.168.1.42, do you know the port????? You need to forward port 25 for SMTP mail delivery and if you want the web UI (Postorius and HyperKitty) accessible from the outside, port 80 for http and/or port 443 for https <https://www.iana.org/assignments/service-names-port-numbers/service-names-p…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/28/20 8:06 AM, brylon(a)oit.rutgers.edu wrote: > Yes, I've stopped/started Mailman (quite a few times). > > Is there a particular order to undo Hyperkitty and re-do? Or perhaps add some debug lines to a particular file to get at the root cause? I'm not certain, but I don't think your issue has anything to do with the installation of HyperKitty itself. From the OP, the issue occurs in REST upon a get of /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers which is probably coming from Postorius -> Settings -> Archiving. The actual error occurs in Core trying to process that request, and while it clearly has to do with archiving configuration, I don't think the installation of Hyperkitty is the issue. What happens if you set [archiver.hyperkitty] enable: no and restart Mailman? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: LDAP user email verification

by Tony Deshields

Abhilash Raj wrote: > On 9/15/23 02:54, Tony Deshields wrote: > > I'm running the docker-mailman setup with LDAP integrated. My users that authenticate against LDAP are still required to verify their email address however, I do not want this functionality. I was looking for guidance on possibly configuring it so my LDAP users do not have to verify their email address. > > AFAIK, there isn't any existing configuration that would allow you to do > this, but it really depends on how have you setup the LDAP authentication. > IMO, the auth backend used is the best place to Thanks for the response Abhilash. I am using openldap with django_auth_ldap backend that pulls users from LDAP and assigns permissions based on AD groups. I have configured LDAP based upon the example configuration found here: https://django-auth-ldap.readthedocs.io/en/latest/example.html. I will take a look at the backend, as you suggested, thanks.

1 year, 7 months

[MM3-users] Re: [MM3-users]Re: Is it possible to grant all users the ability to Create List

by tibor.molnar＠waltoninstitute.ie

Hi, I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: Superuser: Can do everything. AnonymousUser: Can view list index and info pages. Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how?

3 years, 9 months

[MM3-users] Post-installation documentation?

by David Newman

Is post-installation documentation available for a full Mailman3 installation on a new Debian 11 machine? I am looking for a high-level "do these steps next to get a list working" document rather than an API command reference. I followed the venv documentation and the installation went ok, but still have questions about what to do next, e.g.: - why do the venv docs and admin FAQ give different nginx configs for the reverse proxy? https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… - Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides /opt/mailman/mm/mailman-hyperkitty.cfg? - For Django (presumably in /etc/mailman3/settings.py, but the docs don't say), what values to use with Postfix to set up the email back end? I have a working test list, but am not altogether sure it's set up correctly. Thanks in advance for pointers to docs beyond the installation steps. dn

3 years, 5 months

[MM3-users] Re: Strange password problem

by Roland Miyamoto

Dear Stephen, Eggert and everybody. On 23/09/2023 13:02, Stephen J. Turnbull wrote: > What are you doing that requires admin privileges, but you want to > authenticate separately for each domain? I ask because we've always > envisioned creating a domain-level administrator role, but until now > we've had no demand for it. I could easily imagine a situation where I'd need an admin per domain: On my server I have lists @lists.domain1.tld @lists.domain2.tld @lists.domain3.tld that are associated with websites www.domain1.tld www.domain2.tld www.domain3.tld used by separate "customers"¹ of my server. The "customers" do not know each other and might want to create additional lists in *their* domain. Currently *I* create all lists for all my "customers", but with list-domain admins I could leave that job to the respective "customers". Right? Best wishes, Roland -- ¹) "customers" in quotes because they do not pay for my service.

1 year, 7 months

[MM3-users] Re: How to count the number of members in a list using Mailman client?

by Abhilash Raj

On Mon, Mar 18, 2019, at 2:38 AM, Alan So wrote: > I tried to do so using Mailman client but it is really slow for lists > with size > 1000. I use the following code snippet: > > my_list = client.get_list(listname) > > print ("number of members =", len(my_list.members)) > > Are there any other ways to do so in a much faster speed? Thanks. If you have too many members, the above can be slow. You can instead do: $ mylist.get_member_page(count=2).total_size This will basically return Paginated list of members, and a Page object has an attribute total_size, which will return the total count. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: Your Dashboard

by Mark Dadgar

On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: > everytime I receive a mail for moderation it says: > > At your convenience, visit your dashboard to approve or deny the > request. > > So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. > > I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. > > If it is already there, where do I find it? If not, do others also find such a dashboard helpful? This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: Is there a reason not to implement the config_list command ?

by Mark Sapiro

On 6/10/18 11:54 PM, Asaf Ohayon wrote: > > Is it meant to be implemented ? > and if so, how is it recommended to do > (for someone new to mailman 3 programming) It depends what you are looking for. The Mailman 2.1 config_list command can do quite a lot. It has both an output (config dump) mode and an input (config load/alter/etc) mode. It would be a simple matter to implement a mailman sub-command to dump a list's config if all you want are list attributes and their values. If you want all the commentary that config_list produces, that is more difficult because config_list basically gets all that from the Mailman 2.1 web UI and in Mailman 3, the web UI is decoupled from the core and the core really knows nothing about it or if it even exists. You would need to get it from the various interface definitions in mailman/interfaces/mailinglist.py. For the input mode if all you wanted to support was input containing lines of the form attribute=value that wouldn't be too difficult to do, but config_list can to much more because it makes the list object available to the input script so the input script can do anything at all to the list. So, as I said, it depends on what config_list functionality you are looking for. If what you want is a way to configure a list for a particular "style", Mailman 3 has a concept of List Style to be applied when the list is created. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. This, rather than config_list is intended to be the way to configure a particular list style. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: list footer questions

by kelly.close＠lrewater.com

I must be really close on this, and I hope it's ok that I'm jumping in on this thread. I am also using the mailman-full package on Ubuntu 18.04 (and have been successfully running a bunch of lists now for almost 2 years!). I think I'm doing what the docs say to do, in order to override specific list footers, but to no avail. Everything else about my system is working great - I just can't customize templates. So I have a template file here: /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list:member:regular:footer.txt I had to create everything below templates/ as that folder was empty on install. I made sure what I created had the same permissions as the templates folder. I'm not sure what else to do. Is there a configuration file somewhere perhaps the identifies the path of the templates folder and maybe I need to adjust it? I appreciate the help.

4 years, 10 months

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

by Mark Sapiro

On 7/10/24 12:27 PM, Danil Smirnov via Mailman-users wrote: > > I'm aware of the tools you mentioned and they were properly used. Your issue is almost certainly caused by unescaped `From ` lines in message bodies and preprocessing the mbox with the hyperkitty/contrib/cleanarch3 script should fix those. > Please let us focus on the question I asked - how do we delete messages of > a particular date if there are too many of them so using Hyperkitty UI > isn't an option? You can do ``` DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; ``` but as you note there are entries in the hyperkitty_thread table that need to be removed too. So, before doing the above, maybe something like ``` DELETE FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>); ``` but there are also possibly entries relating to these messages/threads in the hyperkitty_favorite, hyperkitty_tagging, hyperkitty_lastview and hyperkitty_vote tables. It seems unlikely that there would be such entries in your case, but if you are concerned about them, here in order are what you can do in the database. ``` DELETE FROM hyperkitty_favorite WHERE thread_id IN (SELECT id FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>)); DELETE FROM hyperkitty_tagging WHERE thread_id IN (SELECT id FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>)); DELETE FROM hyperkitty_lastview WHERE thread_id IN (SELECT id FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>)); DELETE FROM hyperkitty_vote WHERE email_id IN (SELECT id FROM hyperkitty_email WHERE archived_date = <your datetime>); DELETE FROM hyperkitty_thread WHERE id IN (SELECT thread_id FROM hyperkitty_email WHERE archived_date = <your datetime>); DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: problem with Python's stdlib email module

by Mark Sapiro

On 6/5/23 14:59, Peter Münster wrote: > On Mon, Jun 05 2023, Mark Sapiro wrote: > >> Basically, all over. > > Thanks. I would like to find out, which function is responsible for the > modification of the body, before filling a bug report. > Unfortunately I don't have any experience with Python, so any help is > highly appreciated. > My idea is to add "print(message)" at the places, that you mentioned. > Where would I find the output then? You don't want to use print statements. All those modules do logging to various logs so they pretty much all import logging. Then you add something like ``` dlog = logging.getLogger('mailman.debug') ``` near the beginning of the module and then add things like ``` dlog.info(msg.as_bytes()) ``` to write the message to debug.log. However, I would not proceed in that way. I would start by putting the raw problem message as it comes to mailman in a file and then use `mailman shell` do to things like ``` >>> import email >>> import smtplib >>> from mailman.email.message import Message >>> with open('path/to/message/file', 'rb') as fp: ... msg = email.message_from_binary_file(fp, Message) ... >>> ``` to create the message object, and then do something like ``` >>> conn = smtplib.SMTP() >>> conn.sendmail(from_addr, to_addrs, msg) ``` to send the message to to_address and see if it has the added lines. Or maybe just ``` >>> print(msg.as_bytes()) ``` to see if that has the added lines. It may be necessary to do things like ``` >>> msg['Message-ID-Hash'] = 'aaaaa' ``` to add a header to create 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, 10 months

[MM3-users] Re: How to stop minutely mails about readme_renderer

by Mark Sapiro

On 5/22/22 08:10, Stephen J. Turnbull wrote: > Axel Rau writes: > > > /usr/local/py_venv/mailman_33/lib/python3.9/site-packages/readme_renderer/markdown.py:44: > > UserWarning: Markdown renderers are not available. Install > > 'readme_renderer[md]' to enable Markdown rendering. > > warnings.warn(_EXTRA_WARNING) > > > > I installed cmarkgfm 0.8.0 in my venv, > > Why did you do that? Is it something in our documentation? It is required by readme_renderer. Can you activate your venv, run python and successfully ``` import cmarkgfm from cmarkgfm.cmark import Options as cmarkgfmOptions ``` If you can't do either, cmarkgfm is not properly installed in the venv. If you can do the first, but not the second, there is a compatibility issue between readme_renderer and cmarkgfm 0.8.0. Try ``` pip install cmarkgfm==0.6.0 ``` which works in my installations -- 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] Any possible way to reduce robot spam accounts?

by Stephen J. Turnbull

Franklin Weng writes: > I really have no idea how the robots find my system since I haven't > told anyone the ip or URL of my mailman instance.� And, they're > registering on the system, not the mailing list since I have only > one list for testing now and it wasn't assaulted by spam yet. The bots just check every domain on the internet for the /mailman3 and /postorius paths. > * just let users join from email (lists-join(a)lists.url) instead of > registering on the mailman instance?� or What I do is open up the firewall only to ips I have legit users at. You probably can't do that, but if you can, it's quite effective. You could restrict it to email-only subscription in one of the following ways, but the bots have known how to do that since the 90s, and the only control you have is to require moderator approval. Requiring address verification doesn't help much, the bots have been doing that almost as long. You can disable the administrative UI entirely, by removing the entries for mailman3 and postorius from the top-level urls.py. You can edit the template for the list information to remove the subscription form. > * use a scheme like CAPTCHA to reduce the successful opportunity of > robot registering? I think somebody has implemented CAPTCHA for Mailman 3. Search the archives of this list. But the bots also know how to solve CAPTCHAs, and for some CAPTCHAs they were faster and more accurate than humans. Unless your users expect instant membership, or you expect an awful lot of subscriptions, I would just let subscriptions accumulate for a day or two and then discard them all. You can also write a script to figure out the IPs and ban those hosts at the firewall. Steve

1 year, 9 months

[MM3-users] Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Abhilash Raj

On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: > Abhilash Raj: > > On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: > >> Hey Abhilash, > >> > >> Thanks a lot for your work on mailman3! > >> > >> Abhilash Raj: > >>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. > >>> > >>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that > >>> I can think of is non-member management in Postorius. > >>> > >>> New releases are available on PyPI[3][4]. > >> > >> For earlier releases, you provided GnuPG signature files to > >> cryptographically verify that the release files were not tampered with. > >> > >> I couldn't find such signature files for the two latest releases. Would > >> you mind adding them? When packaging for Debian, I prefer to check the > >> GnuPG signatures before uploading new releases. Also, the signature > >> files get uploaded to the Debian archive as well so they can be checked > >> by everybody. That way we can cryptographically proof that the Debian > >> package is based on the original tarball that got packaged and signed by > >> upstream. > > > > > > Ah, sorry about that. I completely forgot about that. > > > > I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. > > Thanks a lot, that would be awesome. I'll wait for it before doing the > Debian package uploads. If it is not possible to upload signatures, I'll bump up patch versions and push out new tarballs with signatures. > > Just to let you know: we're close to soft freeze in Debian, so in order > to get those uploads into the next stable release (Buster), they'll have > to be uploaded rather soon. Can you give a rough estimate on how long do we have before the freeze? > The same holds for other pending releases of Mailman3 components: Just > in case you plan to do new upstream releases anytime soon, it's still > possible to upload them to Debian in time for Buster. I'll see if we can get other releases out too. Core doesn't yet have any backwards incompatible changes, so I might end up bumping minor version and doing a new release. Not sure much has changed in other components, but I can do a release if there are enough changes. -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: Where do I find the check_hk_archive script

by Mark Sapiro

On 11/18/23 11:21, Lars Bjørndal wrote: > In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run > the check_hk_archive script found in hyperkitty/contrib. When trying > `git clone https://gitlab.com/mailman/hyperkity`I get: > > Username for 'https://gitlab.com': > > Is it possible to get the script without an account on gitlab? I've updated some project settings. You should now be able to `git clone https://gitlab.com/mailman/hyperkity` without a gitlab account. However, why are you wanting to do this. If you have HyperKitty installed, there should be a hyperkitty/contrib directory in your installation, e.g. /opt/mailman/venv/lib/python3.x/site-packages/hyperkitty/contrib/ containing the check_hk_import and cleanarch3 scripts. Even if you don't have that, you can download the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/chec… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

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

by John Covici

OK, thanks a lot -- if anyone here can help with proper config for those, that would be great. I do have a web server, but its apache rather than mginx and I am not sure how to properly translate. Also, doing a separate container for an mta which would just talk to mailman would get around the sendmail situation I have, although there may be a decent way to do that as well. I guess the hard part is to tie the multiple containers together. On Sat, 31 Jul 2021 17:56:15 -0400, Abhilash Raj wrote: > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > I have a couple of questions about the container, if its OK. > > Sure it is :) > > > > > 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? > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > 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? > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > 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 > > _______________________________________________ > > 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) > -- 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

3 years, 8 months

[MM3-users] Re: Changing subscription address

by Stephen J. Turnbull

Abhilash Raj writes: > > There does need to be a way to revert each option to inherit, and > > there currently doesn't seem to be one. The 'Preferences' interface I > > described in the previous post doesn't provide it either. I will > > think about that. > > The implementation of this isn’t very difficult, but the UX of this is > something I don’t know how to implement in that page to be very > honest. Oh, I can play Liz Warren on that one! :-) "I have a plan for that." > We do already have ability to switch from an explicit address to Primary > Address subscription. I would imagine it would be more than just a > button, but more like a dropdown to choose an email or primary address > and switch all subscriptions to that. Allan's situation is that for some reason he has a lot of users (or at least suspects he does) who would be happy to have only one address that there's only one place to change, but for some reason that address is copied to (not inherited by) each of several subscriptions. We should address that, because I'm pretty sure his suspicion is correct. For example, until I changed one of them -- and got two emails about it for my discard pile :-) -- all of my python.org Mailman 3 subscriptions were explicit. I still have about 8 to go. :-) > This is how Core actually does work[1] if you subscribe via Email > and you already have a primary address. It will lookup a user using > the address and if the address is the primary address of the user, > it will subscribe the primary address. If you say so, I guess it's true. Nevertheless, both Allan and I have observed users with only one address, with that address subscribed literally each time to several (~10) lists. > However, if it isn’t the primary address, and this is a new address, it will > subscribe the address instead of user because the address isn’t > verified at this point and hence can’t be a primary address. We could > extend the subscription workflow to add an additional step to set this > address as primary and subscribe the primary address. Yes, please, I think. Users who don't want this for subscriptions to the primary address are going to be (rare) edge cases. If we need an additional attribute on the user to handle the case of an unverified primary address, I think that's an acceptable cost. Note that to "claim" this User as her own, she has to verify that address. And if she *can* verify that address, we can't stop her from doing so, we can just make it more annoying. > Postorius has the full ability to define its own workflow because > REST API provides full expression capability and doesn’t enforce > anything. Previous versions didn’t had support for subscribing as > Primary Address, but that has since changed and is the default one > in the dropdown. > > This is for authenticated subscription, the anonymous subscribe works > similar to email -join command. Mass-subscribe is probably working the > same way. All of these should unify all subscriptions-by-this-address to one User, in my opinion. > Like mentioned above, it should be possible to do what you suggest. I > am getting into the implementation details here, but the Subscription > workflow would need an additional flag that would verify an address > and use the flag to determine if it should subscribe the address or > addresses’s user if an address is provided to the workflow. I don't think so. Just do the lookup, if it succeeds and matches primary address, use inherit. If it doesn't succeed, create a User and use inherit. If it does succeed, and doesn't match, use the explicit address. It seems to me that this flag would be impractical for email subscriptions (email commands with parameters are generally beyond the kind of user this is most important for) or mass subscriptions (how does the list owner know what the user wants?) anyway. If somebody really wants all their subscriptions via primary address to be copies of the primary address rather than user, I'm sorry, but they'll have to deal with that. I can't imagine that it's the usual case, and there's an easy workaround: make your primary address something other than your usual subscription address! If you disagree with me about the relative burden, then maybe we shouldn't do this at all, but I'm pretty sure this is something we should either do for all subscriptions, or for none. > Primary Address is also an attribute of the Mailman User, so it > should be possible for an admin to set that for a user if the user > doesn’t have an account. When they sign up, they’d be able to > manage and update accordingly. True, but AIUI Allan has a *lot* of users and on average they're relatively needy compared to, say, my user population. The point of his request is to smooth workflows for admins with user populations where the admin *wants* to do many things for their users, or to have smooth user workflows when they teach their users to do it for themselves. That's why I'm focusing on the "I have one address and if it changes I want to change it once" case. I think it's both extremely common, and extremely annoying :-) to admins who have to deal with the current situation. Steve

4 years, 1 month

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

by peter＠chubb.wattle.id.au

Hi Folks, I notice that for people with multiple email addresses, the email address that appears as the 'FROM' address in the hyperkitty archive is not the primary address, nor is it the address that the email actually came from, but the address that was created first. (Hyperkitty version 1.3.7) When I click on that from address in the archive view, I see all the email addresses for the user -- these do not match up with the ones in the django admin screen from .../admin/account/emailaddress/ When I see 'User profile for Fred Frog' it shows obsolete addresses (not subscribed, not in the Django profile for the user). How can I as administrator get rid of bogus addresses? Or do I have to ask each user to do this? and how can I ensure that the email address displayed in the archive is the primary address, not some address that no longer works? Peter C

1 year, 11 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/20/20 6:54 AM, Brian Carpenter wrote: > > Respectively, I think you are asking the wrong question here. The real > question is why isn't a display_name being removed when a list > subscriber is unsubscribed. I'd like to understand the real requirement. It seems to me that this issue has come up because a list admin wanted to change the display name shown in the membership roster for a user. Since there is currently no UI to do this, the list admin tried to do it by unsubscribing and resubscribing the user. That didn't work which led to this "unsubscribing a user should remove the user's information" thread, but the real issue is the lack of a UI for changing display names. It seems if that UI existed and was available, the "unsubscribing a user should remove the user's information" issue would never have been raised. So perhaps what we should be talking about is UIs for changing user information, what they would look like and who should be able to change what. Note that I personally am a member of many lists, an admin of multiple lists and a site admin for multiple mailman installations. I am well aware of the frustrations of list admins who wind up just doing it because it's way easier than instruction some users as to how to do it themselves. However, I don't think that is necessarily sufficient reason to hand over control of global, non-list specific user information to the admin of one particular list that the user happens to be a member of. Even in mailman 2.1, while a list admin could go to a user's options page for the list and change things, the "change globally" check boxes only worked for the user, not for the list admin. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: hyperkitty_import performance boosting potential

by Mark Sapiro

On 7/8/24 11:59 AM, dlb-ml--- via Mailman-users wrote: > > I can throw all of the resources I need at it in order to make it faster, but I'm not sure if the import application is single-threaded only. Is there a way to enable a multi-threaded option? Can I safely run multiple commands at the same time using something like /usr/bin/parallel? If you're concerned about down time while doing the switch over, you could just do the hyperkitty_import processes while the MM 2.1 lists are still up, and then just import only the latest messages while the MM 2.1 lists are down. That said, in order to provide parallelism, you could split the mbox into pieces and run multiple hyperkitty_import processes concurrently. If you do this, be sure to specify --since on the commands to be sure you get all the older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: First time mailman installation

by Roland Giesler

On 2024/07/25 08:51, Odhiambo Washington wrote: > On Wed, Jul 24, 2024 at 12:23 AM roland--- via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > I have installed mailman3 on Ubuntu including postorius & > hyperkitty (from the packages). > > I have questions now which are not quite clear to me from the docs: > > > Hi Roland, > > Which guide did you use to install mailman3? I simply installed it from Ubuntu packages. > > 1. How do I specify my mail server details (which is my own server > running postfix, etc) > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… That is a guide that provides basic info, but there's not reference to secure protocols, so I suppose it's just a bit dated. I have a great, secure couple of server (running power-mail-in-box), so I don't want to venture into the manual mail-server setup territory, with all it's accompanying spam and security requirements. The mailings list should just use one (or more) or those servers. As I have written in another post I made, I have set the (apparently) appropriate parameters in the mailman.cfg, but I still get "relay access denied" from my external MTA, which mean that authentication is not even attempted, or am I mistaken? > 2. How do I create new lists from the postorius UI, or can I only > do that in the config files or the command line console for mailman3? > > > Once everything is up and running and you have the Postorius UI, you > can always use the Django Admin interface to manage stuff. > It's available at https://FQDN-FOR-YOUR-SITE/admin > <https://FQDN-FOR-YOUR-SITE/admin>. > How do you log in? You create a "superuser" account using CLI, then > use it. Now that depends on how you installed MM3. I figured that out already. Thank you. Roland

8 months, 4 weeks

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Andy Smith

On Fri, Jul 01, 2022 at 08:40:23AM +0000, Andy Smith wrote: > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 770203 www-data 20 0 4516756 3.4g 1.6g R 99.7 43.5 12:08.00 python3 /usr/share/mailman3-web/manage.py runjo+ This has been going for nearly 6 hours now at 100% CPU and I've no idea if it's ever going to finish. If I strace it, it is doing *something*, albeit very slowly. I can't see what it needs the 100% CPU for. Output from 10 minutes or so of: $ sudo strace --output='|tee strace.txt' -tp 770203 is at: http://sprunge.us/RCGLmv It's only 145k and doesn't seem to do much. An occasional open,seek,read,close… Any good way to find out what it's spending its CPU time on? "top" says it is 100% "user" so I think it's something the python code is doing, not anything inside the kernel. Thanks, Andy

2 years, 9 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Stephen J. Turnbull

Helio Loureiro writes: > Problem was the wrong link was getting a generic page from Django > instead of error. You can set DEBUG = True in settings.py, which will give you a much more informative error page, including a lot of information that you can't easily get from logs and configuration files. HOWEVER, this also gives all that information to anybody who can induce an error, which of course is not that hard to do. You may want to take the server offline by firewalling it off, do some experimenting with DEBUG = True, then set it back to DEBUG = False before bringing it back up. > > Of those three, the api_key on mailman-hypperkitty.cfg and > > MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a > > Django thing and has nothing to do with the others. See > > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key > > > > If you changed it, that's the issue. Have you changed that key?

1 year, 1 month

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

by Stefan Bauer

Thank you Mark and Steve, that helped me a lot to understand the whole process. We noticed that we can remove the MM-specific footer and that did the job. No more attachments in Outlook. *list:member:regular:footer* thanks to the new template system, this can be done via mm3- web interface. Thats great! :) Stefan Am Mi., 25. Jan. 2023 um 07:10 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > Collapse alterantives: YES > > Convert html to plaintext: NO > > These options probably delete any plaintext and leave HTML as it is. > > > Thunderbird is showing the mail "correct". Outlook does show the > > attachments as attachments. > > Note that they're not attachments as defined by MIME, they're labeled > "inline" in the Content-Disposition header. The obvious thing for the > MUA to do is to display non-HTML inline parts in order vertically, > then the HTML part(s), then more non-HTML inline parts, and so on. A > Sufficiently Smart MUA can probably make things a bit more attractive. > Outlook just doesn't bother at all. :-( > > If you must cater to Outlook, the obvious way to handle it is to > configure to delete HTML parts unless they are the only text part, and > in that case convert HTML to plain text. IIRC that's > > Collapse alternatives: YES > Convert html to plaintext: YES > > If you can legally do so, you can also configure the header and footer > to be completely empty (not even white space). But that second option > is only useful when you want to remove "ugly" attachment buttons, and > can't be used when the footer text is needed. > > Before you ask the obvious question: It would be possible to try to do > "reasonably user-friendly" handling in Mailman by editing the HTML > part instead of adding MIME parts, but I myself won't do this because > it almost certainly would result in mangled, at least partially > unreadable mail in some cases. In particular, if you need to have the > footer displayed for legal reasons, this could make it undisplayable > even by competent MUAs like Thunderbird. It would also probably be > ugly. I'm not willing to deal with the likely user complaints, nor do > I like the risks it would impose on list or site administrators under > some laws. > > This could be done as a plugin, and if somebody wants to contribute > one (and preferably offer support) I would probably support adding it > as a contrib feature (that is, if the code is of a certain minimal > quality). > > Steve > > >

2 years, 2 months

[MM3-users] Re: Sorry to repeat a question, but how do I permanently delete messages, again?

by William Oliver

Thanks!!! That's exactly what I needed. billo On Fri, 2022-07-08 at 15:12 +0100, Tim Cutts wrote: > It can be done in the GUI. See this historical thread: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > T > > > On 8 Jul 2022, at 13:48, William Oliver <billo(a)billoblog.com> > > wrote: > > > > > > I askled this question some months ago, but for the life of me > > cannot > > find the response (though there is one). I want to purge some > > specific emails from the list archives. A user posted what he > > thought > > was a personal message to the list, and is embarrased by it, so I > > told > > him I couldn't delete emails that were already downloaded onto > > client > > machines, but I can delete it so that new users won't be able to > > see > > it. > > > > But... I can't figure out how to do it. > > > > I asked this once before, some months ago, and as I remember there > > is a > > command line way of doing it, but not a GUI way. But i can't > > remember > > what it was. > > > > Thanks! > > > > billo > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 9 months

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 11/3/19 6:58 PM, Alan So wrote: > Are there any pointer of documentation that I can clear all _these_nonmembers settings by updating the databases directly or using mailman shell? I am not so familiar with mailman shell though. We expect list owners use moderation_action only for members and non-members. $ bin/mailman shell -l test.example.com Welcome to the GNU Mailman shell The variable 'm' is the test.example.com mailing list >>> m.accept_these_nonmembers = [] >>> m.hold_these_nonmembers = [] >>> m.reject_these_nonmembers = [] >>> m.discard_these_nonmembers = [] That will just blindly clear them all. If you want to see what you're clearing, you could do things like >>> if m.accept_these_nonmembers: ... m.accept_these_nonmembers ... m.accept_these_nonmembers = [] ... which if the list's accept_these_nonmembers is non-empty will display it and then set it empty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Anyone using Rspamd with Mailman 3?

by Torge Riedel

Am 22.09.21 um 11:20 schrieb Philip Colmer: > why don't you let Mailman3 do the DMARC mitigation? I do have DMARC mitigation activated in mailman3, so that all mails sent are coming from a unique mail for each list. Some list members have strict SPF setups forcing me to do that. Following the config, I use rspamd from http://rspamd.com/apt-stable/ rspamadm configdump arc *** Section arc *** sign_networks [ "127.2.4.7", ] use_domain = "recipient"; allow_envfrom_empty = true; allow_hdrfrom_multiple = false; allow_username_mismatch = true; sign_inbound = true; sign_local = false; symbol_sign = "ARC_SIGNED"; path = "/var/lib/rspamd/dkim/$selector.key"; try_fallback = true; use_redis = false; key_prefix = "ARC_KEYS"; allow_hdrfrom_mismatch = true; sign_authenticated = false; use_esld = true; selector = "2019"; *** End of section arc *** rspamadm configdump dkim_signing *** Section dkim_signing *** sign_authenticated = true; use_esld = true; selector = "2019"; try_fallback = true; use_domain = "header"; allow_hdrfrom_mismatch = false; symbol = "DKIM_SIGNED"; allow_username_mismatch = true; allow_envfrom_empty = true; allow_hdrfrom_multiple = false; key_prefix = "DKIM_KEYS"; use_redis = false; sign_local = true; sign_networks [ "127.2.4.7", ] path = "/var/lib/rspamd/dkim/$selector.key"; *** End of section dkim_signing ***

3 years, 7 months

[MM3-users] uncaught bounce messages

by David Bremner

I'm getting (many) uncaught bounce messages for one user. Other than forcibly unsubscribing them, is there anything I can do? I hesitate to post this message publically, but here is what I can see, somewhat anonymized The MIME structure looks like └┬╴multipart/mixed 7030 bytes ├─╴text/plain 442 bytes ├─╴message/delivery-status 176 bytes └─╴text/rfc822-headers 5301 bytes In /var/log/mailman3/bounce.log I see lines like Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> In the delivery-status part I see Final-Recipient: rfc822; fub(a)foo.bar Action: delayed Status: 4.0.0 The initial text/plain part looks like Hi! This is the MAILER-DAEMON, please DO NOT REPLY to this email. A message is delayed for more than 4 hours for the following list of recipients: fub(a)foo.bar: Network error on destination MXs Please note that this is only a temporary failure report. The message is kept in the queue for up to 7 days. You DO NOT NEED to re-send the message to these recipients. Below is a copy of the original message:

3 years, 6 months

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

by Mark Sapiro

On 7/8/22 9:16 AM, kisner(a)live.com wrote: > > 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. The issue is when you do ``` pip install psycopg2-binary<2.9 ``` your shell (sh, bash, zsh or whatever) interprets `<2.9` as an input redirection and probably says something like `2.9: No such file or directory`. You need to do something like ``` pip install psycopg2-binary\<2.9 ``` or ``` pip install 'psycopg2-binary<2.9' ``` I'll update the doc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

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

by Mark Sapiro

On 8/5/22 07:02, Kimmo L wrote: > > The only concern I've observed and I'm trying to solve right now is with memory. Not sure whats consumes the memory gradually, so that it will start consume also swap memory and eventually you can find"OSError: write error" entries in uwsgi-error.log or "django.request Internal Server Error: /hyperkitty/" in mailmanweb.log > Do i need to modify my uwsgi.ini configuration maybe ? > Server has 2CPU and 5GB RAM. We have seen reports of memory leaks, but no solutions. We do not see these issues on any of the production servers we manage. The server that hosts this lists has 4GB RAM and that seems fine for a server doing just Mailman. Our servers use gunicorn, not uwsgi, so this could be a uwsgi issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail

by Torge Riedel

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post: The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen. I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look? Best regards Torge

5 years, 3 months

[MM3-users] Re: Templates do not work

by Mark Sapiro

On 4/28/22 02:50, Eggert Ehmke wrote: > I created some templates in Postorius to get > personalized notifications when there are > moderator requests. The notifications I get seem to > be the standard texts. When I look into mailman/ > mm/var/templates > the directory is empty. Nevertheless, the templates I > create in Postorius seem to be stored (where?), they > just do not work. As Steve said the templates are stored in the database. I suspect the issue is and incorrect value for `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to construct the URI to retrieve the template. The URI is stored in the `template` table in the database. It is normally just `http(s)://host.name/` If this is the issue, after correcting the setting and restarting the web service, you will need to delete and re-enter the template in Postorius to correct the `template` table entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Installation Questions [Installation}

by Mark Sapiro

On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > Hello everyone, > > I'm running Ubuntu 24.10 and following the Virtualenv instructions > <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u…>. > When creating the mailman user per the instructions I find that the mailman > user doesn't have sufficient permissions to do things later in the > installation such as creating files in /etc. What steps should I take to > ensure that the mailman user has the correct permissions to install the > Mailman app. We should probably cover this in the docs, but for /etc/mailman3, you should do ``` sudo mkdir /etc/mailman3 sudo chown mailman:mailman /etc/mailman3 sudo chmod 755 /etc/mailman3 ``` Then you can create all the subordinate files as the mailman user. For other things like the systemd service and the postfix and web server configs, you need to do them as root (via sudo). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

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

by Brian Carpenter

Dear Mailman 3 Users, Since Mailman 3 includes a forum feature via Hyperkitty, I would like to know the following: - Has the forum feature (Hyperkitty) of MM3 been received well by your list members or is it mostly ignored? - Do you see an increase in the use of HK as a forum from your list members? - What kind of feedback have you received from your list members considering the forum function of MM3? Positive or negative? - 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? Thank you for anything you shared. I am very curious to know the state of Hyperkitty among the Mailman 3 user community. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

4 years, 9 months

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

by Mark Sapiro

On 7/14/20 6:51 AM, Brian Carpenter wrote: > Dear Mailman 3 Users, > > Since Mailman 3 includes a forum feature via Hyperkitty, I would like to > know the following: > > - Has the forum feature (Hyperkitty) of MM3 been received well by your > list members or is it mostly ignored? > > - Do you see an increase in the use of HK as a forum from your list > members? For this list, I don't know other than myself, and for myself I receive the list and read it by email. I will occasionally reply from HyperKitty if I have reson to reply to a post that I have deleted from my mail server. For mail.python.org, there are multiple list members (including Guido) on multiple lists who use HyperKitty exclusively in lieu of mail. For my bicycling club lists, very few users use HyperKitty for anything and most didn't use pipermail either even though we had htdig integration. Those few that do use it probably use it primarily for search. > - What kind of feedback have you received from your list members > considering the forum function of MM3? Positive or negative? They find warts, in part due to the still developmental markdown rendering <https://gitlab.com/mailman/hyperkitty/-/merge_requests/160> that's installed there and on this list too, but overall those that use it, like it and prefer the forum model to the email list model. > - 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? Yes and Yes. > Thank you for anything you shared. I am very curious to know the state > of Hyperkitty among the Mailman 3 user community. > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

[MM3-users] Regarding nested mailing lists in mailman 3

by Stephen J. Turnbull

Chandrakant Pandey via Mailman-users writes: > I want to know whether we can setup nested mailing lists in > mailman 3 which we used to do in mailman 2. like > ep2021@iitb.ac.in,ep2022@iitb.ac.in,ep2023@iitb.ac.in mailing lists > exist and we add all this mailing lists as member in > ep(a)iitb.ac.in. Whether this kind of nested mailing lists work ? It depends on what you mean by "work". As far as I know, Mailman 3 is fully compatible with Mailman 2 for such lists. It is definitely true that mail sent to ep@ will be delivered to all members of ep2021@, ep2022@, and ep2023@. I believe the features of Mailman 2 for improving administration of umbrella lists (like ep@) are all implemented in Mailman 3. (These features mostly have to do with things like how the -owner address is handled.) For completeness I guess I should mention there are differences having to do with password reminders since we don't send those any more. Steve

3 weeks, 1 day

[MM3-users] Regarding nested mailing lists in mailman 3

by Stephen J. Turnbull

Chandrakant Pandey via Mailman-users writes: > I want to know whether we can setup nested mailing lists in > mailman 3 which we used to do in mailman 2. like > ep2021@iitb.ac.in,ep2022@iitb.ac.in,ep2023@iitb.ac.in mailing lists > exist and we add all this mailing lists as member in > ep(a)iitb.ac.in. Whether this kind of nested mailing lists work ? It depends on what you mean by "work". As far as I know, Mailman 3 is fully compatible with Mailman 2 for such lists. It is definitely true that mail sent to ep@ will be delivered to all members of ep2021@, ep2022@, and ep2023@. I believe the features of Mailman 2 for improving administration of umbrella lists (like ep@) are all implemented in Mailman 3. (These features mostly have to do with things like how the -owner address is handled.) For completeness I guess I should mention there are differences having to do with password reminders since we don't send those any more. Steve

3 weeks, 1 day

[MM3-users] Re: Templates

by Barry Warsaw

On Sep 23, 2017, at 10:36, David Krantz <gazorg(a)gmail.com> wrote: > > 1. I do not know how to force a cache invalidation on a template. So > only way to change is to set a new name on the file and change the uri > there. Unpractical. No, restarts do not work. With Mark’s help you figured out how to use file templates, which is probably best for your use case. URL templates will be best when using a CMS or other system that allows you to upload templates into them. I can imagine Postorius one day supporting this feature. The way to do cache invalidation for the template you added to the database would be (let’s say for mailing list alpha(a)example.com) $ mailman shell -l alpha(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the alpha(a)example.com mailing list >>> getUtility(ITemplateManager).delete('list:member:generic:footer', m.list_id) More information is provided here: https://gitlab.com/mailman/mailman/blob/master/src/mailman/interfaces/templ… http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html Cheers, -Barry

7 years, 6 months

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

by Mark Dadgar

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

4 years, 9 months

[MM3-users] Re: How to configure a mailing list?

by Mark Sapiro

On 3/10/20 6:44 AM, Patrick Ben Koetter wrote: > Greetings, > > I do have mailman 3 installed via virtualenv and it is up an running. Now I'd > like to create a mailing list, but I can't find any instructions how I should > do this. > > Is there a resource online I missed? If not, can anyone on this list tell me > how to do it preferrably using a command line tool? There is a bin/mailman command in your venv. It needs to be run with a -C option pointing to your mailman.cfg. I use a wrapper like #!/bin/bash exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ Give the mailman command with no args for a list of sub-commands and ultimately mailman create --help for instructions on creating a list. See <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/commands…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Redundant and load balanced Mailman3

by Stephen J. Turnbull

Bottom line up front: 1. Mailman was designed in the context of a single host, and most installations do work that way; we at Mailman don't know a lot about multihost setups and performance yet. This can give you some pretty large installations (eg, mail.python.org is a single host, I believe). Maybe Mark will chime in on this point. 2. You might get better information from postmasters at the largest sites who may have experience with distributed setups. fedora.org might be a good candidate because their people put a ton of work into optimizing HyperKitty for their situation (that's why HyperKitty has all the options for redis caching etc). Pawel Grzywaczewski writes: > I'm a bit confused about dependency on local files? You mean files > that are created when an e-mail is processed? Yes. > So where is the problem with redundancy? If this host is gone there > will be another Mailman deployment able to deal with the load. Where does the file go if the host goes down? If it's local and the host goes down, you lose or delay mail -- that should not happen if your Mailman system is up. That's why Abhilash mentions NFS, which allows another "core" host to take over if a "core" host goes down -- but that's not necessarily a good solution either. (I'm not saying it's *bad*, just that NFS has known problems for *some* applications, and I don't know if Mailman is one.) And of course the NFS server becomes a SPOF (single point of failure). > What about having 3 VM where all components of Mailman are > installed. Those VMs connect to 1 database on a remote host. But they don't connect to 1 database. Each component has its own database, and HyperKitty and Postorius also connects indirectly to core's database via core. They *could* all connect to one database server, but that server becomes a SPOF. > A given VM handles a request HTTP or SMTP, and if there is a > problem (or very high load of SMTP) Mailman doesn't handle SMTP requests, I assume you mean LMTP. I don't think that LMTP handling is very strenuous (could be wrong). The aiosmtp module can handle quite high loads, spending most time waiting for the payload (during which it handles other connections), then it dumps a file to disk, also quite fast. As I understand it, the bottleneck is the database stuff. Mailman does a lot of database accesses to handle a post. > there are still 2 other VM that can do the job. So perhaps the > question is: can we plug 3 Mailman instances into 1 DB? Is Mailman > software developed taking into account that several Mailman > instance writes to the same database at the same time? I don't see why that would be an ACID problem -- the database takes care of that. I do think it would make the database bottleneck worse for performance. Note that we're currently seeing reports of long delays (enough to cause database connection timeouts, so on the order of minutes) in creating lists when there are already a lot of lists. If I had to put money on it, I would bet that there is some procedure iterating over incremental requests in Python that should be doing "one big request" to the database. But I don't know that that's true. I do know that there are some very big sites (such as fedora.org) that use Mailman 3. But they seem to have rather complex setups, with powerful databases and caches to speed up even that. Finally, Mailman 3 was originally designed and tested with a single host doing all the work in mind. The most obvious symptom is the lack of authentication on the REST API. (Of course you can simulate that model with an appropriate firewall and subnetting setup.)

4 years, 7 months

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

by Stephen J. Turnbull

朱超 writes: > Yes, You got it. It is too cumbersome to ask the user to write a > reply email for email confirmation. Surely clicking on "reply" then "send" is not cumbersome (unless there's a way to get rid of confirmation altogether). Your problem is that some of your subscribers can't do that. I have not previously heard of a MTA that refuses to *send* mail because the addressee's mailbox is too long. IIRC there's a limit of 256 characters on domains, but only the (long-obsolete) recommendation that lines in the message be 998 bytes or less restricts the length of the local-part. I don't really see a good reason to change this default because there are a number of configurations where there is no web service available. I suggest a partial remediation in the issue I just filed. (I think dealing with the rest of the issue is a Simple Matter of Programming, but the question of determining existence and status of an appropriate web service is more complex so I did address that.) > Why do you need to modify the mailman-core service， >I suggest we should modify the code of the postorius, We are not going to do that, because 1. Mailman provides no guarantee that any web service is present, and we're not going to make changes that require one. 2. Mailman provids no guarantee that the web service is Postorius even if there is one, and we are definitely not going to make creating compatible implementations more annoying than necessary. > Currently I have achieved it this way。 We encourage you to use your code. ;-) But using it exclusively to accomplish this change would go against several of our goals in term of separation of concerns. If we can do it in an alternative way that serves those goals, there's no point in complexifying Postorius in this way as well. Regards, Steve

2 years, 3 months

[MM3-users] Re: Newbie hyperkitty question

by David Newman

> On Jan 11, 2022, at 08:28, Stephen Daniel <swd(a)pobox.com> wrote: > > Mailman users -- > > I am setting up a new mailman3 installation, and this is my first > experience with the suite. All of the software is up and running, but I > cannot tell if hyperkitty is actually running. > > When I look at my test mailing list, two archive options are available, > hyperkitty and "prototype", and both are enabled. I can see that my email > is being archived, but I think "prototype" is what is doing the archiving. > I see that a test message will end up in > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > and nowhere else. This suggests that "prototype" is archiving, but > hyperkitty is not. > > So, this opens up a raft of questions on hyperkitty: > > - How do I tell if hyperkitty is actually running? Is hyperkitty enabled? In the Postorious admin panel for your list page, check under Settings/Archiving. Generically, the URL for Hyperkitty archives is something like this: https://lists.domain.tld/archives/list/listname@lists.domain.tld/ When I’m logged in (which I needed to be to check settings), I see archives at that location. Also, your mailmanweb database should have a bunch of ‘hyperkitty_*’ tables. I’m not ssh’d in to a MM3 server right now but IIRC the messages go into the hyperkitty_email table. dn > - Does hyperkitty have a web-UI for admins or users? How would I access > it? > - I can not find any documentation on hyperkitty, other than > installation instructions and change logs. Does documentation exist? > - How do I set policies on how long archives are kept? > - Assuming I want to back up my archives, what do I need to back up? > > Thanks for your help! > > -- Stephen Daniel > _______________________________________________ > 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, 3 months

[MM3-users] Re: Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 18/2/21 11:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I want to contribute making it via Weblate, since it is already done > via gitlab repository (thanks to Mark Sapiro for approving the merge > requests), making a revision and editing them if needed, but I cannot > see how to make it in a consistent way, as I cannot determine how to > edit each template in the Weblate UI. I've tried to access via the > file name (accessing via msgid as for your example) of the > template... but I cannot access them by this way, or I'm missing > something. >> >> Can you, please, point me in the right direction on how to do it? > > Forget this, I've just found how to do it. Selecting by "key/context" > and the name of the file seems to do the trick. Done. Now the Weblate translation of templates is consistent with the gitlab src repository.

4 years, 2 months

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

by Mark Sapiro

On 09/03/2018 06:13 PM, Paul Arenson wrote: > Hi again. I take it the lack of responses mean I should wait it out a little longer? It's of course up to you, but I recommend Mailman 3. There are still some rough edges, and there are a number of settings not yet exposed in Postorius, but we are working on it and it is quite usable today. > I was considering, as mentioned, Fed Forum (but not much help in setting up), Slack and Flock. Would all mean more work than I can afford. > > Which is why upgrading from Mailman 2 to 2 still seems like the best idea. > > We would then have the perfect upgrade to Mailman 2, where people could more easily find their topics (aided by a lot of nudging to be proactive in choosing the topic to post in and not doing thread hijacking). Do you mean Mailman 3? > I looked to see if there was anyone doing this sort of service. All I could find is someone doing their own hosting called https://mailman3.com/. mailman3.com is a Mailman 3 hosting service unaffiliated with the GNU Mailman project. > I would much prefer to upgrade my C-Panel installation of the lists, which by the way are here: > > https://gale-sig.org/mailman/listinfo/galemembers_gale-sig.org > https://gale-sig.org/mailman/listinfo/galeexec_gale-sig.org > > Any estimate on if/when I would be able to upgrade these c-panel forums (or possibly get someone to help me move them?) I suspect it will be some time before Cpanel offers Mailman 3. It is fairly straightforward to migrate an existing Mailman 2.1 list and it's archives to Mailman 3, but it requires access to the underlying Mailman 2 file system which you may not have in a hosted cPanel environment. See <http://docs.list.org/en/latest/migration.html> for more on migration. -- 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] Simple ubi8/mailman3 container image

by Jered Floyd

Abhilash maintains a very complete and well-documented container deployment for Mailman 3, but when I was setting up my environment a few months ago I wanted to build on top of RHEL 8 as well as use a database instance shared across multiple applications. So I ended up creating a bare-bones container image that suited my needs and was closer to just doing a simple local install, but keeping the isolation, reproducibility, and rollback benefits of running as a container. I've been meaning to polish it up and share in case it is useful to others, but finally recognizing that I likely won't get to that soon I've just put it on GitHub here: [ https://github.com/jeredfloyd/mailman-container | https://github.com/jeredfloyd/mailman-container ] Doing a "podman build" of this should result in a container image that is very much like the result of doing a venv install. This uses the Red Hat Universal Base Image (UBI), which can be freely redistributed, gets upstream security updates, and is eligible for support on a paid RHEL subscription. --Jered

1 year, 6 months

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

by Simon Hanna

On 9/18/18 6:30 PM, Dmitry Makovey wrote: > On 09/18/2018 09:22 AM, Abhilash Raj wrote: >>> 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. >> Ah, why not take a database dump? There are a few specific tables >> that you can dump to get everything? >> >> We don't have a way to do that because we do not actually do not >> handle auth ourselves, but instead delegate it to allauth library. >> You may have to dig into internals of that to be able to >> fetch/restore users/passwords. > Thanks for picking up the thread, Abhilash. > > Since we're trying to get solution that would allow us to dump/restore > members/users of specific mailing list etc. we need a bit more "precise" > method of extracting user info. We also suspect our DB could be corrupt > (we have multiple address entries per member, of which 1 would have > proper address and the rest are with empty fields, what's more the ones > referenced from other tables are mainly those with empty fields) thus > would like to dump "clean" objects and refresh DB rather than copy > corruption from DB to DB. You are in Django territory, so I would suggest using django to get the job done. You can write your own python scripts that do that for you, you could even use the django management commands https://docs.djangoproject.com/en/2.1/howto/custom-management-commands/ You should be able to retrieve users from django.contrib.auth.models import User users = User.objects.all() user = users[0] user.password = 'passwordHash' user.save() That should set the password properly. If you need further help, the django docs are quite good, but if you need anything I'm happy to help cheers, Simon

6 years, 7 months

[MM3-users] Re: changing adverstised status

by Johannes Winter

Am Wed, 22 Aug 2018 13:33:09 +0200 schrieb Simon Hanna <simon(a)hannaweb.eu>: > On 8/22/18 10:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change > > "show list on index page" via the settings, but the value isn't > > saved. Is there a way to set advertised = False to a specific list > > via the shell? > > What do you mean it isn't saved? Are you getting an error? Is it just > being overwritten to True? > > I use the rest api, using it you can do the following: > > ./manage.py mmclient > > lists = client.lists > > l = <choose your list> > > l.settings['advertised'] = False > > l.settings.save() Using the command line mailman tool the sequence is: $ mailman withlist -l <mailinglist> >>> m.advertised=False >>> commit() >>> quit()

6 years, 8 months

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

by Mark Sapiro

On 3/10/25 12:24 AM, Kyle Lahnakoski wrote: > > When I add a user (like myself) I get a welcome email from all- > request(a)mymaillist.org. When I respond, the mail arrives in the S3 > bucket, but I do not know how to give it to mailman3. The "inject" > command will not work because there is no "all-request" mailing list. > > > How do I feed these administrative mails to mailman3? You can use `inject` with something like ``` /opt/mailman/venv/bin/mailman inject -f <somefile> -q command all(a)mymaillist.org ``` but > I have tried netcat the email to the ?LMTP? port, but it fails: this is the better way. The issue is you are not using `nc` correctly. When you do $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr you are telling nc to take commands from the file /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send the file. -- 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] Docker mailman 3 and upgrading questions

by bob B

I am running mailman 3 in docker and trying to figure out -how to upgrade -can you back out. For example I installed docker with a git pull • git clone https://github.com/maxking/docker-mailman docker images shows REPOSITORY TAG IMAGE ID CREATED SIZE maxking/mailman-web 0.3 9ba9d3d7084d 4 months ago 487MB maxking/mailman-core 0.3 26c920c0094b 4 months ago 178MB **** database is hosted via external database I only installed it a few months ago, am I really on 0.3.0 , I assume I am on 3.0 from 2019 and that is what "git clone https://github.com/maxking/docker-mailman" gets???? looking at the release matrix "https://github.com/maxking/docker-mailman/releases?page=2" It looks like the latest releases are 0.4.1 for core & 0.4.2 for web, How do I upgrade, is it a "git pull" or "docker update" command? If something does not work, is there a way to back out? What version should I go to from 0.3? I am thinking it should be v0.3.12 cause that won't break anything? But how do I do that? The documentation at https://asynchronous.in/docker-mailman/. says

3 years, 2 months

[MM3-users] Do you struggle with message rejected. AUP#CDRBL while using mailman with your ISP email relay?

by Michael Richardson

I'm impressed by Philip Bondi's use of mailman[23] for home financial automation. ("Take off Eh!") ... It seems like a ticketing system would be a better system for such a use... maybe the IETF SML WG will further help with this.. (I find most Canadian financial institutions are so far behind the curve) I think that your email is hosted by hostedemail.com? I'm guessing that "eshop" is the mailbox you use for these common notices, and maybe you retrieve that into your mailman3 with fetchmail or something? Or does your ISP turn around and SMTP to you directly? Is it your MTA, their MTA, or mailman that is doing the rejection? My problem, on lists.sandelman.ca aka lists.tcpdump.org, is messages that appear to have been processed by my MTA (according to postfix logs), but which are never delivered, nor held. Lost somewhere in mailman3 queue. Sometimes they show up after a host reboot.

5 days, 17 hours

[MM3-users] Re: Where do I find the bounced messages?

by Mark Sapiro

On 12/20/22 02:29, Sörös Zoltán wrote: > Greetings, > I am running several lists under mailman3. I am getting notifications > about users being put on nomail because of their bounces - but I can > find no way to actually see the bounced messages. > > Do mailman3 store the received bounces? Where? They are stored in the message store in the database but only temporarily. > Is there any setting to forward these bounces to the list owner? There are two relevant settings. These are exposed in Postorius -> Settings -> Bounce Processing. They are: Notify owner on bounce increment - sends a notice to the owner including the DSN when a user's bounce score is incremented, but to a value less than the bounce threshold. Notify owner on disable - sends a notice to the owner including the DSN when a member's subscription is automatically disabled due to the bounce threshold being reached. -- 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: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Stephen, Thanks for your reply. Stephen J. Turnbull 於 2023/7/20 21:11 寫道: > Franklin Weng writes: > > > * just let users join from email (lists-join(a)lists.url) instead of > > registering on the mailman instance? or > > What I do is open up the firewall only to ips I have legit users at. > You probably can't do that, but if you can, it's quite effective. > > You could restrict it to email-only subscription in one of the > following ways, > > You can edit the template for the list information to remove the > subscription form. Could you please tell me how to do it? I thought of removing the register link from the web page (upper right corner of /mailman3/postorius/lists/ ) but I couldn't find any web page templates like that. I tried /var/lib/mailman3/web/static but I couldn't even find any keywords like "accounts" or "signup". I don't know how to deal with javascripts. Thanks, Franklin

1 year, 9 months

[MM3-users] Re: OperationalError: database is locked

by Simon Hanna

> OperationalError: database is locked > > Does this suggest I should switch from sqlite to postgres (https://stackoverflow.com/a/26864360)? I'm happy to do that, but how do I migrate the data between the databases (after installing postgres and creating the database)? I've found this doc (http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html#data…) but I don't think I understand this and I haven't used alembic: these instructions are just for when you modify the model within the same database, right? sqlite isn't really good with constant load on it. Assuming your database is not very big, you can just use the dumpdata and loaddata commands of django. Otherwise you'll either have to do it "manually" using database dumps or programatically by using two databases for django. All aproaches are mentioned in this stackoverflow question: https://stackoverflow.com/questions/3476606/django-what-are-the-best-practi… When it comes to low level stuff, anything you find for django will work for Hyperkitty. As for the doc link, this is Mailman core specific and not related to Hyperkitty

7 years, 3 months

[MM3-users] Re: Migrating archives from mailman2 to mailman3 with attachments

by Mark Sapiro

On 2/28/22 10:14, bob B via Mailman-users wrote: > So I see the process for migrating an archive from mailman2 to mailman3 > https://docs.mailman3.org/en/latest/migration.html.................. i.e python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > but does the migration handle attachments?? attachments are in > ..../archives/private/foo-list/attachments. You do not need those files. They were extracted from the messages in the foo-list.mbox file which is all you need. > I am migrating to a new server and my plan is to follow these steps but copy the config.pck. and .mbox files to the new server and import them, but then it looks like I need to copy the attachment directory? if so how do I import the attachments to mailman3? No. You do not need the attachments directory or any of the .html files. All this information is in the .mbox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

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

by John Covici

I am finding some missing documentation in the section on configuring mailman-web, it refers to a file https://asynchronous.in/docker-mailman/web/ which does not exist. On Sat, 31 Jul 2021 21:21:24 -0400, John Covici wrote: > > OK, thanks a lot -- if anyone here can help with proper config for > those, that would be great. I do have a web server, but its apache > rather than mginx and I am not sure how to properly translate. Also, > doing a separate container for an mta which would just talk to > mailman would get around the sendmail situation I have, although > there may be a decent way to do that as well. I guess the hard part > is to tie the multiple containers together. > > > On Sat, 31 Jul 2021 17:56:15 -0400, > Abhilash Raj wrote: > > > > > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > > I have a couple of questions about the container, if its OK. > > > > Sure it is :) > > > > > > > > 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? > > > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > > > 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? > > > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > > > > 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 > > > _______________________________________________ > > > 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) > > > > -- > 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 > _______________________________________________ > 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

3 years, 8 months

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

by Paul Arenson

Hi again. I take it the lack of responses mean I should wait it out a little longer? I was considering, as mentioned, Fed Forum (but not much help in setting up), Slack and Flock. Would all mean more work than I can afford. Which is why upgrading from Mailman 2 to 2 still seems like the best idea. We would then have the perfect upgrade to Mailman 2, where people could more easily find their topics (aided by a lot of nudging to be proactive in choosing the topic to post in and not doing thread hijacking). I looked to see if there was anyone doing this sort of service. All I could find is someone doing their own hosting called https://mailman3.com/. I would much prefer to upgrade my C-Panel installation of the lists, which by the way are here: https://gale-sig.org/mailman/listinfo/galemembers_gale-sig.org https://gale-sig.org/mailman/listinfo/galeexec_gale-sig.org Any estimate on if/when I would be able to upgrade these c-panel forums (or possibly get someone to help me move them?) Thanks paul in Fukuoka, Japan

6 years, 7 months

[MM3-users] Re: user mail not accepted

by Stephen J. Turnbull

Christian Stalberg via Mailman-users writes: > My apologies. I did not confirm that what I did already sent you was the > message received by the user. The mailing list address is > ssan(a)lists.naturalintelligence.us and it seems as though this became an > alias for this single user christian(a)sewagesludgeactionnetwork.com > . Not exactly. What happened is this: % host lists.naturalintelligence.us lists.naturalintelligence.us has address 45.33.28.111 lists.naturalintelligence.us mail is handled by 10 box.ecovillage.cc. % host box.ecovillage.cc. box.ecovillage.cc has address 45.79.28.18 box.ecovillage.cc mail is handled by 10 box.ecovillage.cc. 'lists' and 'box' are different systems, it appears, because they have different IP addresses (45.33.28.111 vs. 45.79.28.18). Because of the MX record described by "lists.naturalintelligence.us mail is handled by 10 box.ecovillage.cc.", the mail sent to the list at 'lists' is going to 'box', not 'lists'. I guess that Mailman is installed on 'lists', not 'box', so Mailman never sees the post. My guess is that what you want to do is to change the MX for 'lists' to itself in the DNS, and you probably also need to do something about the webserver if you want 'lists' to offer Mailman services, since currently it presents the same page as 'naturalintelligence.us' which presents the same page as 'www.communityseekers.org'. Why that message is eventually delivered to 'christian' at ssan, I don't know, but this appears to have nothing to do with Mailman itself. We would need to see the configuration for the MTA (appears to be Postfix) on 'box' to figure this out. There seems to be a whole complex of domains involved here. We're happy to help you with Mailman even if that involves the DNS, MTA, and webserver configurations for Mailman services, but fixing up the DNS, mail service, and webserver configurations for a hosting service is really above our pay grade. You may want to hire a consultant for this, because the configuration seems suboptimal to me, but I don't know what you're trying to do. Regards, Steve

3 years, 11 months

[MM3-users] Re: Digest Formatting

by Apollinaris Schöll

> > In general, this problem is really hard to address because the > capabilities of clients vary so greatly. > Have tested many clients and its a total mess. For text only emails its not too bad but attachments break things in strange ways. The only ones working correct are outlook and Mail on iOS. Though display is not the most convenient. They both enable reply to original message and thats a great improvement compared to MM2 > 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 :-/. yes, yes, yes full ack. Thats what I am doing. But its extremely hard to convince users to change what they have done for a long time. > 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. Can you list clients that can do that? I’d like to have options to recommend if users insist on digest.

4 years, 5 months

[MM3-users] Re: Do you struggle with message rejected. AUP#CDRBL while using mailman with your ISP email relay?

by Odhiambo Washington

On Wed, Apr 16, 2025 at 4:17 PM Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > Hello to all: > > mailman3 is phenomenal upgrade from mailman2. Very nice. Thank you to > the team. > > In our family, we use mailman to provide redundancy on important financial > emails. In this manner, emails from banks, government, ecommerce or other > important providers are distributed to multiple family members. And we can > ask family members if they paid the credit card bill, received their > delivery, saw their tax liability or refund notification, etc. Does anyone > else use mailman for such a purpose? > > Do you struggle with "message rejected. AUP#CDRBL" while using mailman > with your ISP email relay? > AUP == Acceptable Use Policy. I am sure you signed some dotted lines about that, or clicked Accept/Yes somewhere and so something that is happening is violation the AUP. CDRBL sounds like the IP of your ISP relay server is in some blacklists. You could use https://mxtoolbox.com/ to lookup the IP/Hostname that you use for relay. For example, when receiving email from a Bank or the Government of Canada > on a mailman2 list, sometimes my ISP would not relay the email and I would > get message rejected. AUP#CDRBL > And what does your ISP Tech Support say is the problem? I also think the problem is referenced somewhere in your MTA logs. While, this is most likely going OT, I will try and narrow down on the mailman bits. Assuming: 1. That the sender address of the Bank or the Government of Canada is _allowed_ to send emails to some_mailman_list_address 2. That your family are all subscribed to to the mailing list for the purpose of receiving the emails from the senders in (1) above, It should be easy to configure the mailing list to send out the posts by rewriting the sender to be the list address. You can do the same with Mailman3 under List settings -> DMARC Mitigations On mailman2, I mitigated by stripping headers, wrapping message and DKIM > signing. Here is a mailman2 message that is stripped, wrapped and signed. https://freeimage.host/i/30O5EXe > > Do you have this problem with your ISP with certain senders? What are > your mitigation strategies on mailman3? > In my case, I don't, because of List settings -> DMARC Mitigations -> DMARC mitigation action = Replace From: with list address. Below that is the option DMARC Mitigate unconditionally, which I have also enabled. Curiously: If you DKIM sign your emails, does your ISP also co-sign them? Is your ISP relay server published in your domain's SPF records as an allowed sender for your domain? -- 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 week

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 1/30/23 10:32, Jeremy Stanley wrote: > > I'm not having any luck finding an API or CLI which I > can use to create sites and domains rather than manually doing it in > the Django admin WebUI. Does such a thing exist, or an I going to > need to resort to directly performing database inserts (which I'd > rather avoid since it could break if the schema changes). It appears > there's a foreign key relationship involved, which could make DB > manipulation like this even more fragile. Domains can be created via Postorius or via the Mailman Core REST API that postorius uses or implicitly by the `mailman create` command when creating a list in a new domain. However, none of this can create a new site. You can do this through the Django admin site at sites/site/add/. See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you can use to do this programmatically. -- 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: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 5:40 PM, Paul Arenson wrote: > >> Assuming MUA means a mail application. And if that mail application has no reply list function then the setting doesn't work. MUA means Mail User Agent which is another name for mail application, YES. > Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) > >> It is the presence of the >> List-Post: header in the message that allows the MUA to offer/process >> the "reply-list" function. > > Ok, I asked how to make it ANNOUNCE ONLY and you said to use "allow_list_posts is False" which is the same as "Include the list post header". Not exactly. You asked what settings were different between discussion style and announce only style. What I answered was that the only setting that differed as set by the style was what Postorius calls "Include the list post header". What I didn't say explicitly was that this is not sufficient to prevent posting to the list. > So does this mean that for a subset of users I cannot make it ANNOUNCE ONLY? And is it some other setting (send to moderator) that prevents it from being a DISCUSSION list? What exactly do you want? You found some info on configuring an announce only list and I referred you to a FAQ on that subject. Both of these do not directly address Mailman 3, but they do give useful information. I am going to stop guessing at what you want to accomplish, so tell me what you want to happen when someone sends a post to the list either from HyperKitty or by email. What should happen to the message? What if anything should be sent to the user? Should this behavior be the same for all users or just a subset. If a subset, how do you identify that subset and what should happen when others attempt to post? -- 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: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 2:36 PM, robert.kydd(a)gmail.com wrote: > Hi Mark, my apologies it is version 2.1.26 This list is really for Mailman 3. The list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>. > 1. Do I find Mailman's file system using cPanel ? In cPanel Mailman, Mailman's file system is at /usr/local/cpanel/3rdparty/mailman. > 2. Your quote: > with the various UPPERCASE things replaced appropriately and then > 'compile' it via > ... > msgfmt -o messages/en/LC_MESSAGES/mailman.mo > messages/en/LC_MESSAGES/mailman.po > > Does the compiling happen when I use mailman or do I have to have a compiler for this to happen ? The compiler is msgfmt. There may be a msgfmt installed with cPanel, but in any case, there is a Mailman version so you should be able to do cd /usr/local/cpanel/3rdparty/mailman bin/msgfmt.py -o messages/en/LC_MESSAGES/mailman.mo \ messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: MM3 to MM3 migration

by Mark Sapiro

On 1/31/23 13:34, David Newman wrote: > > Is this really as simple as building the new server, creating the same > lists on the new server, and rsync’ing the archives from the old server? > If not, how to do the migration? If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff. To do only selected lists is much more difficult and there are no scripts that I am aware of. HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported. -- 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: moving list from mm3 -> mm3

by Stephen J. Turnbull

Jens Günther writes: > -> I just don't see, how this would be easier :-D Read through it, > but still don't know how to batch export and reimport config and/or > users. If you were expecting a single command, that would be available via the command line interface "mailman". There is no such thing yet. What I meant by "easier" is that you can experiment with it and maintain state in the Python interpreter rather than having to store intermediate results in files and figure out how to read them back in. And you have all Python facilities (classes, lists, dicts) to organize data rather than needing to mess with text editing of JSON or trying to script things in exactly the right order (eg, to deal with read-only attributes). Once you have an object, you can use the pickle module to save it (that's how Mailman 2 kept its configs, after all). > -> maybe it's again a dumb question, but how would I start it? The easy way to experiment is mailman shell This starts a Python 3 interpreter with many of the base mailman classes and functions already imported. It's actually an alias for "mailman withlist", but I usually use "mailman shell" with no arguments and "mailman withlist -l $LIST" when I know what list I want to work with. Once you know what you want to do, for list-oriented tasks you can use "mailman withlist -l $LIST -r $YOUR_SCRIPT" to do it repeatedly. You'll need to be more "creative" with users and other non-list objects to write usable scripts, importing mailmanclient and any relevant core modules. See mailman/src/mailman/commands for many examples (including the source code for mailman shell and mailman withlist in the file cli_withlist.py. The "mailman" command line utility itself is in mailman/src/mailman/bin/mailman.py, but you don't need to look at that, it doesn't do much interesting for your purpose. And you can probably ignore all the @click decorators, they are used to get rid of boilerplate for managing command line arguments. mailman shell and mailman withlist keep a history, I think it's configured in mailman.cfg or schema.cfg. > -> it it's easier, is there an easy way to export and import > config? (or members?) I don't understand what you're trying to do, so I can't say. The usual use case is backing up a whole site either as a disaster recovery tool, or in order to move the site to a new host. For that an SQL database dump, and an archive of /etc/mailman3 and any changes you've made to templates or source files, is the way to go. If you just want lists of addresses and the like, "mailman withlist" will do that for you. But you seem to want self-contained pieces of the whole object- oriented database, and that's going to be harder because you need to maintain structure. There's no way around that. Steve

1 year, 3 months

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

by Barry Warsaw

Hi David, On Mar 25, 2017, at 08:22 PM, David Krantz wrote: >Still annoying to hear that the mailman_bundle is deprecated. Yes, I'm sorry you went down a dead end with mailman-bundler. I'm trying to purge the world of it so others won't get led astray. I've clobbered the README in the GitLab repo and we may at some point just archive and delete the whole project, but I'm not quite ready to do that yet. The only other place that I'm aware of that still mentions bundler is on the PyPI page, and I don't have permission atm to delete that package. We'll do that asap. Where did you find out about the bundler? I'd like to make sure we steer people to the current best recommendations: http://docs.mailman3.org/en/latest/ That includes a link to the setting up guide. We do need a better overall story for setting up all the components. I suspect we may not get to that before Pycon, and it will be one of the things we concentrate on for the sprint. Cheers, -Barry

8 years

[MM3-users] Re: Patch/kludge suggestion and a question on adding accepted addresses

by Mark Sapiro

On 04/24/2017 07:07 AM, David Krantz wrote: > On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: >> On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>> I have another question: In the old mailman you could add accepted >>> senders without adding them to the list. Is that possible in Mailman >>> 3/Postorius? >> >> You do this by creating a "nonmember" subscription for the sender, and then >> setting that member's moderation_action to Action.accept. > > Okay. I see no way of doing that in my instance of Postorius but in > this case it is okay to do it in the command prompt. Yes. There are still quite a few things that aren't yet exposed in Postorius and probably some not yet exposed in the rest API. In these cases you have to resort to mailman shell (aka mailman withlist). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

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

by Stephen J. Turnbull

bob B via Mailman-users writes: > Thanks, but how would make backup mbox files in mailman3 with > Hyperkitty? You don't do it with HyperKitty (I'm pretty sure you can export mboxes from HyperKitty, but I don't think it would be timely, you have to do it by hand). The sample archiver (which you can enable in mailman.cfg IIRC, haven't done it in a while) would make the mbox files directly from the core at the same time that they are sent to HyperKitty. It's possible to have both HyperKitty and the sample archiver enabled at the same time. > I thought all the messages were stored in the database and there > were no mbox files anymore. That's true in HyperKitty. The sample archiver is a separate facility that's part of core. All it does is append to an mbox on the core's host. It has no facility for display to users. It's basically a developer demo for how you attach an archiver to Mailman core, but it's also a possible backup approach for a very careful admin like you. > I would assume I would just be able to restore the database True, but how frequently do you back up the database? The "also store to mbox" approach I described loses no messages even if your database gets trashed (unless the mbox also gets trashed in the the disaster, but if I understand your setup correctly, the mbox would be on the core's host, while the database server and storage is on a different host, so trashing both would be a really bad situation, hopefully very unlikely). > and reinstall/rebuild mailman and then run maybe a script to make > sure the archives are rebuilt? If the database restore is successful, there's no rebuilding to do. The database is the archive. You just need to reattach it to HyperKitty. > and then I would be good to go. Yes, modulo the period between most recent database backup and disaster. Regards, Steve

2 years, 8 months

[MM3-users] Re: SMTPNotSupportedError when requesting new password

by Eggert Ehmke

Thanks, you are right. I removed the email and password from settings.py, and it works now. Am Mittwoch, 21. Dezember 2022, 14:13:31 CET schrieb Odhiambo Washington: > On Wed, Dec 21, 2022 at 4:04 PM Eggert Ehmke via Mailman-users < > mailman-users(a)mailman3.org> wrote: > > > > I get this error when a user tries to use the "forgot password" function > > in hyperkitty. > > Obviously the exception is thrown when the send_mail function is called > > in > > > > > > > > /opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py > > > > > > > > > > In settings.py I have: > > > > > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > EMAIL_HOST = 'localhost' > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = 'valid email' > > EMAIL_HOST_PASSWORD = 'valid password' > > > > > > > > What can I do to debug further? > > > > > > > Is it necessary to have the authentication details when communicating with > localhost? > Most MTAs do not require ASMTP on port 25 because that port is meant for > MTA-to-MTA communication usually. > If you must use authentication, please configure it on a different port > (like 587) and ensure you only advertise for ASMTP on that port. > For now, just comment out the EMAIL_HOST_USER and EMAIL_HOST_PASSWORD > and restart whatever needs to be restarted > and all shall be okay. > I suspect that you do not advertise AUTH to localhost, and neither do you > (or should you) enforce auth on port 25. > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > _______________________________________________ > 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 > /JLVOTE7IB4T2JPB7FM2Y2GEVFR3T73EE/ > > This message sent to eggert(a)eehmke.de

2 years, 4 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/5/24 10:30, Odhiambo Washington via Mailman-users wrote: > > Actually, what I mean is that CF is proxying requests to the host named > m3-lists.kictanet.or.ke. > I do not have any configuration other than DNS proxying at CF. ``` dig a mm3-lists.kictanet.or.ke ... mm3-lists.kictanet.or.ke. 300 IN A 172.67.167.73 mm3-lists.kictanet.or.ke. 300 IN A 104.21.11.217 ``` Both of those are cloudflare IPs, and why 2? > So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP who > you talk to and it in turn talks to the host directly. And how is that configured? > So the IP address you see in the logs is CF's IP address, not yours, not > mine and CF are doing some caching. That's why > they are requesting for expired files. Why is cloudfare trying to access /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css locally if all it is doing is proxying the request to the actual mailman server? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Deactivate list without deleting it?

by Colin Watson

On Tue, Jan 16, 2018 at 10:59:28AM +0900, Stephen J. Turnbull wrote: > Colin Watson writes: > > > Ideally, I'd like mailing lists to have a "deactivated" state in > > addition to full deletion. In this state, the list would appear > > nonexistent for most purposes: incoming email would be rejected, > > Postorius would deny its existence, etc. > > [...] > > > Has there been any discussion of this in the past, or any advice as to > > implementation strategy? > > I don't recall anybody discussing this. Your use case is your use > case, but I think if we were going to implement this I'd probably want > "partial" deactivation where the archives remain available but no mail > is delivered, can't subscribe, etc. I'm also not sure I'd want > Postorius to deny it ever existed. That seems rather unfriendly > (again, I don't understand your use case, so that is not a comment on > your requirements). I possibly should have explained our situation in a little more detail. The way we have things set up with Mailman 2.1 is that any team in Launchpad (teams are basically just a collection of people, with varying policies on who can join them etc.) can have a mailing list if its administrators want one, and they enable it in the Launchpad web UI. If you want to subscribe to one of these lists, you join the team in question and you press the "Subscribe to mailing list" button. Launchpad runs the show and tells Mailman exactly what to do. So in fact we have all of Mailman's user interface disabled except for the list archives, and Postorius wouldn't come into it in our case - I probably shouldn't have confused things by bringing it up hypothetically. We'd probably want to do roughly the same kind of thing with Mailman 3, at least to start with, though we may well want to make some of HyperKitty's advanced features work with single-sign-on integration. I haven't looked into that in any detail yet. I can definitely see that both "preserve archives" vs. "hide archives" are potentially useful things to do. > It seems to me that dump, delete, and restore may be the best approach > for the HyperKitty side because HyperKitty maintains all that state. > Of course this could be done inside the database. Also, perhaps you > can (ab)use the ArchivePolicy enum by adding an "inactive" element, > but core has no way to enforce those on the archiver (which can be a > third party host like mail-archive.com) and I'm not sure HyperKitty > ever consults core about that once the archive is created. I'd been thinking more of a new enum in HyperKitty for the visibility state, since it does seem like quite an archiver-specific thing. (Dump/delete/restore would of course be possible, but it's somewhat cumbersome to do externally and it seems like an odd way to go about things internally given the ability to change the DB schema.) I agree that not all archiver implementations can support this. > I'm not sure what you mean about IArchiver; as far as I can see that > interface is sort of half-duplex: it provides the information core > needs *about* the archiver to do core's side of archiving, not for > core to communicate *with* the archiver. In fact all of the concrete > code is callbacks provided by the archiver, and once a message is > archived the core forgets about it. So this isn't "just" an > extension; it's a fundamental redesign of IArchiver. Well, IArchiver.archive_message sends a message from core to the archiver. I'd been thinking of something like IArchiver.set_list_visibility(mlist, visibility) which would send a message from core to the archiver to instruct it to show/hide the archives. It doesn't seem too out of line, though I'm not wedded to it either. I suppose that one alternative could be that we handle this in a Launchpad-specific add-on to HyperKitty, since at a minimum we'll need some of our own code there to deal with sign-in for private lists. So the same bit of custom code that determines whether a list's archives are private could hide them from everyone except their owner, or even deny their existence entirely. It sounds like maybe we'd be better off pursuing that? > I'm not sure that's not a good thing, but we do need to think about > it. ISTM we're gradually converging back on the monolithic approach > to MLM, with the distribution, administration, and archiving quite > tightly interwoven, and I'm not sure I like that. OTOH, we do get a > lot of requests for ever more bundling. Given our requirements, the decreased coupling in Mailman 3 is a very good thing, and I'm definitely not looking for more bundling. I hope I've clarified that above. Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

7 years, 3 months

[MM3-users] HTML email sent to lists migrated from Mailman 2.1

by Stephen J. Turnbull

Nate Coraor writes: > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. Did the host change? How about MTA and malmail checkers? Is it possible that something else is doing the stripping? Lynx is not used in stripping. Do you have the HTML-to-text conversion option on? If so I can imagine that lack of Lynx would fall back to stripping (but that would be a bug, of course, and we'd want to fix it). Is there anything in the logs? It would help if you attached full configurations from a Mailman 2 list and the Mailman 3 list it migrated to. Obfuscate names and IP addresses as appropriate. > I'm trying to get a new list to behave the same way so I can figure > out what's going on without spamming a production list, but have > been unsuccessful: despite setting nearly all the list options the > same as the old lists, new lists pass HTML portions and attachments > just fine. How about spamming the "mailman" (ie, administrator's) list? I think Mailman 3 still has that? Since your hypothesis is that it has something to do with the conversion, one route would be to create a test list in a Mailman 2.1 installation and migrate it. Also, it should be possible to copy an existing production configuration, change the name of the config object, and use withlist to fix up the internal names. But that would have to be done very carefully. > Are there are really old options that can't be accessed via mailing > list objects obtained with `withlist` on the command line? I don't think so. There's no reason to hide them, and they wouldn't be recognized by Mailman 3 anyway. -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years

[MM3-users] Re: Imported Digest Settings

by Mark Sapiro

On 2/16/21 4:08 PM, Brian Carpenter wrote: > On 2/16/21 6:13 PM, Mark Sapiro wrote: >> On 2/16/21 2:28 PM, Brian Carpenter wrote: >>> The beginning of my OP stated I was using Mailman 3.3.3. >> Then please get me a copy of the complete raw digest message so I can >> try to find the underlying issue. >> > Not sure how to do that. Do you mean have the list member forward their > garbled digest message to me? Is that what you need? Oops. Sorry for the prior content free reply. Yes the list member needs to forward the garbled digest to you to resend to me or to me directly, but if it's forwarded, it must be forwarded as an attachment, not inline, because inline forwarding will lose the headers I need to see. Alternatively, the list member can view the message source (how to do that depends on the MUA), select it in its entirety, copy and paste it into a message to you or me -- 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: auto-away notices as bounces

by Andreas Barth

* Stephen J. Turnbull (stephenjturnbull(a)gmail.com) [210824 19:31]: > First of all, until recently Mailman 3 wasn't doing any bounce > processing at all. Depending on your version, it's possible that > Mailman had nothing to do with it. Well, the mail adress got disabled, and the user got warning mails ("Your subscription for list mailing list has been disabled"). As none of the list owners did that, I don't think there is any other explanation. Please note that individualsation was enabled, so all mails are sent out with per-subscriber mail envelope address, which then makes bounce detection quite straight-forward. > Now, are these going to the bounce address, or to the list? If > they're going to the bounce address, I doubt they're being recognized > as standard delivery status notifications. They are sent to the bounce address (more specifically list-bounces+user=domain@listdomain where user@domain is subscribed to the list). > I think they're probably > still counted as bounces if sent to a LIST-bounces address, but they > should also be sent to the list owner as "unrecognized bounces". I didn't get them as list owner, so no. (I however have duplicates of the unprocessed mails, so I can check what was actually sent to the -bounce-adress). I only became aware of the fact after I got a complaint that the account had been disabled. > This > decision isn't something Mailman should be doing because it depends on > context and guessing what the subscriber wants. Really, this is an > owner problem, not a Mailman problem. What should I do different as owner? The user was set to disabled without any manual intervention from me as list owner. > It's not obvious what *we* should do. My proposal would be to ignore messages sent to the bounce address with the 'Auto-Submitted: auto-replied (vacation)' header. I'm thinking about doing that change on the MTA level, but I believe it would be more appropriate at the mailman level. > If Mailman continues sending > posts to the user, it can fill his or her mailbox with mail that is in > many cases available in archives. Not a good idea. I would say, that's up to the user. > In fact, > typically the reason vacationers get unsubscribed is because their > mailboxes fill up, and they generate real bounces. This would be a real bounce, and of course should be handled as such. > Or a moderator got > tired of vacation messages to the list, and nuked the subscription. There was no vacation message at the list, and also no was sent to the moderators or the list address. > Are you sure one of those is not what happened here? "Reasonably sure" I would say. Also, as written above, the user received the "Your subscription for list mailing list has been disabled" mail which specifies : Your subscription has been disabled on the $mailinglist mailing list because it has received a number of bounces indicating that there may be a problem delivering messages to $address. You may want to check with your mail administrator for more help. > I don't understand how the user managed to get automatically > unsubscribed unless you have aggressive bounce settings on the mailing > list(s) or they were gone for quite a while. What should happen is > after the first few bounces they will be disabled, and then checks for > reactivation will be sent once a day or so. Sorry, I meant "disabled". A contributing fact was for sure that the users mail setup sent out the vacation mail on any incoming mail, not only the first, and also on mails with precendence list. I adressed that already to the user (because I believe it's a bug), but of course, IMHO this should be adressed at both sides. (Especially as the mail provider is gmx, this is *the* largest webmail provider in Germany, so both the probability of fixes is rather low, and the probability of happening with users users is not too low.) Thanks for your help Andi

3 years, 7 months

[MM3-users] Re: Hyperkitty

by Onyeibo

Hi Mark, On Mon, 30 Jan 2023 12:24:24 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:58, Onyeibo wrote: > >> 2. Your MM3 log files - do they say anything? > >> > > Nothing! No new errors. It is very strange and frustrating > > > Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/? > YES! A lot of them > Do messages received from the list have an Archived-At: header:? > No > Do messages received from the list have a List-Archive: header:? > No > If the first answer is yes, the mailman_hyperkitty archive_message > method is failing. > > If the second answer is no, the mailman_hyperkitty permalink method > is failing. > > If the second answer is no, the mailman_hyperkitty list_url method is > failing. > That means they are all failing. Wow > All of these failures log errors to the mailman.archiver log which by > default is written to mailman.log. The log doesn't have entries pointing to failures above > > If by chance there is an Archived-At: header, what is it? > The mails don't have that header. I suspect I may have to investigate SELinux.

2 years, 2 months

[MM3-users] Re: configure Mysql and postfix on mailman3

by Mark Sapiro

On 02/20/2018 10:01 AM, Abhilash Raj wrote: > > One _hack_ that I can think of is that when using maps for postfix, Core calls the "postmap" command to generate the maps from the files that it generates. You can potentially provide a script that updates the MySQL database with the same configuration instead of generating maps and specify that script in configuration to be called by Core instead of "postmap". More information on how to do this. On mail.python.org we want to do some manipulations to the various maps, so we have a script to do this. The first step is in your mailman.cfg file, add an [mta] section if there isn't one and in that section add configuration: /path/to/your/postfix.cfg That file is a copy of mailman/config/postfix.cfg except you change the line postmap_command: /usr/sbin/postmap to postmap_command: /path/to/your/script While you could just edit mailman/config/postfix.cfg directly, this is not advisable as your edits will be lost in an upgrade. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Installation Questions [Installation}

by Odhiambo Washington

On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > Hi, > > On 04.11.24 02:06, Mark Sapiro wrote: > > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > > We should probably cover this in the docs, but for /etc/mailman3, you > > should do > > ``` > > sudo mkdir /etc/mailman3 > > sudo chown mailman:mailman /etc/mailman3 > > sudo chmod 755 /etc/mailman3 > > ``` > > Then you can create all the subordinate files as the mailman user. For > > other things like the systemd service and the postfix and web server > > configs, you need to do them as root (via sudo). > > is it really necessary that the mailman user can write that directory? > For most services, directories and files in /etc/ may be readable for > the service but usually not writable as you don't want the service > itself change it's core configuration. > > On your server it looks like this: > > # ls -la /etc/mailman3 > total 28 > drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > > and it works just fine. > True, but making the mailman user own the files makes life easier when you operate from the virtualenv - you do not have to exit the virtualenv to edit the files in /etc/mailman3, and then re-enter the virtualenv. You do not have to give the mailman user sudoer rights. That's the whole point about the below: ``` sudo mkdir /etc/mailman3 sudo chown mailman:mailman /etc/mailman3 sudo chmod 755 /etc/mailman3 ``` -- 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]

5 months, 2 weeks

[MM3-users] funding MM3 development

by John Griessen

On 3/18/20 11:10 AM, Quanah Gibson-Mount wrote: >> We are working on these >> things as we can. We would love to have your help in fixing these. In >> the mean time, there are really only 2 or 3 core developers working on >> this and we are all volunteers, so it takes time. > > I fully understand and would love to contribute. The problem being that I already am doing this for multiple other projects where > we're facing the same issue -- Lots of people use the software and there are the occasional contributions, but few people who are > willing to be core members to really help drive the projects, and I can only drive so many and do my paying job. : Maybe this non-profit foundation could help MM3? It's helping pcb-rnd now... It seems like well documented to do lists are what they like to fund --> "I am announcing a great news that is going to change pcb-rnd development, advancing it to the next level: with the help of NLnet, through the NGI0 PET fund, main pcb-rnd feature development is fully covered for a long time financially."

5 years, 1 month

[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 Odhiambo Washington

On Tue, Apr 25, 2023 at 12:21 PM Mark London via Mailman-users < mailman-users(a)mailman3.org> wrote: > I added some email addresses manually to a mailing list and then removed > them. But now I can't find how to totally remove them from mailman3. > They show up in the Users list. > You can delete them from the command line: su - mailman for m in `cat file_containing_the_addresses_one-per_line`; do \ mailman delmembers -m $m -l listane@domain; \ done When I go to the Django interface, I don't see them listed in any > selection. I thought they would show up under Emails in Hyperkitty, > but they are not there. > Does your SITE_ID in the Django interface (it's shown under Domains) match the SITE_ID in settings? -- 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, 11 months

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

by John Covici

On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote: > > > > > On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > > > On Sat, 13 Mar 2021 14:46:55 -0500, > > Mark Sapiro wrote: > >> > >> On 3/13/21 11:14 AM, John Covici wrote: > >>> > >>> Now one thing came up while trying to create the database, I got a > >>> traceback complaining about a revision error because gentoo had a > >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I > >>> upgrade mailman, am I going to have to do something to the database as > >>> well and why should the database have some kind of reference to the > >>> mailman version? > >> > >> > >> I don't know why this is an issue. You shouldn't need to do anything > >> with the database when you upgrade. Please post the full traceback and > >> error message. > > > > Sorry I can't reproduce it, after dropping and recreating the database > > the error went away, but it was in alembic and it was talking about an > > invalid revision and gave a long hex string. > > > > > My guess is that you updated the database (perhaps, by invoking the mailman > command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > up and sees a new revision for the database migration added from 3.3.3 but > can’t find the same migration in its source (because it is 3.3.2). That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at. -- 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: Mailman3 OOM and high CPU usage

by Prasanth Nair

Hi Stephen, Thank you for the quick reply. I found the issue and fixed it. The flood of .mbox.gz archive export requests from web crawlers overloaded uWSGI workers, leading to instability. Kind regards, Prasanth On Sat, 5 Apr 2025 at 19:52, Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Prasanth Nair writes: > > > Our Mailman3 server crashes with OOM and high CPU usage. As soon as we > > start the mailmanweb service (uwsgi process), the system crashes. It was > > working fine, but this issue started recently. We haven't changed any > > recently. > > > > Any idea how to fix this? > > You're not giving us anything to work with, except "get more memory > for the server". > > > or any suggestions? > > By "system crashes" do you the Mailman system, or does it take the OS > with it? > > By "no changes" do you mean no change to Mailman, or do you mean > *nobody* has touched *anything* on the system recently (no new > applications, no upgrades of existing applications or system daemons, > etc)? > > Tell us system resource limits. Limited CPU should not cause a crash, > and I'm not aware of reports that CPU was a limiting factor in a > Mailman problem. But a Mailman 3 system needs at least 2GB of memory > to function properly unless you're really crafty about configuring it, > and 4GB to be really comfortable. Do you have swap enabled? If not, > 2GB-4GB of swap should get you past the crash, although if there > really is that much memory pressure performance will probably be > terrible. > > Check mailman.log, mailmanweb.log, error.log (usually in > .../mailman/var/logs). I don't know what you're looking for, so start > by looking at many pages of logs when mailman was working normally. > Then look at the recent ones when it started crashing, and just report > "anything that looks different". > > Check memory usage and CPU load just before starting mailmanweb. > > Steve > >

2 weeks, 3 days

[MM3-users] Re: Mailman/Django-allauth integration with Yahoo

by Mark Sapiro

On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Python is updated

by Odhiambo Washington

Your symlimks don't make sense to me. And BTW why do you need symlimks in the first place? Your new virtualenv should be purely a Python3.11 instance. I don't see such an error in my staging environment which is identical to yours. Did you do a fresh install then migrate the data as I proposed earlier? On Thu, Apr 27, 2023, 22:19 Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi, Mark! > > You wrote: > > > On 4/27/23 11:42 AM, Lars Bjørndal wrote: > > > After I've installed the venv and packages again, I get the following > error when running the mailman command from within the venv: > > > > > > SystemError: initialization of _psycopg raised unreported exception > > > > > > How do I fix that? > > > > The first issue arises because the venv/bin/ directory contains only > > symlinks to a system python3, and either they broke upon the upgrade or > they > > pointed to what is now Python 3.11 and there was some incompatibility > > between that python and modules in the venv. > > I have some symlinks: > > python -> /usr/bin/python > python3 -> python > python3.11 -> python > > > > Did you install psycopg2-binary as discussed at > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… > > Yes, I did. > > > Is the error logged in var/logs/mailman.log? If so, what's the traceback? > > No. But the traceback is: > > Traceback (most recent call last): > File "/opt/mailman3/venv/bin/mailman", line 8, in <module> > sys.exit(main()) > ^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1130, in __call__ > return self.main(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1054, in main > with self.make_context(prog_name, args, **extra) as ctx: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 920, in make_context > self.parse_args(ctx, args) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1613, in parse_args > rest = super().parse_args(ctx, args) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1378, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 2360, in handle_parse_result > value = self.process_value(ctx, value) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 2322, in process_value > value = self.callback(ctx, self, value) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/bin/mailman.py", > line 95, in initialize_config > initialize(value) > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/core/initialize.py", > line 229, in initialize > initialize_2(propagate_logs=propagate_logs) > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/core/initialize.py", > line 187, in initialize_2 > config.db = getUtility(IDatabaseFactory, utility_name).create() > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/database/factory.py", > line 57, in create > database.initialize() > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/database/base.py", > line 117, in initialize > self.engine = create_engine( > ^^^^^^^^^^^^^^ > File "<string>", line 2, in create_engine > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", > line 283, in warned > return fn(*args, **kwargs) # type: ignore[no-any-return] > ^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", > line 601, in create_engine > dbapi = dbapi_meth(**dbapi_args) > ^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > line 669, in import_dbapi > import psycopg2 > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", > line 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception > > Do I need to upgrade the database? If so, how do I do that? > > Thanks, Lars > _______________________________________________ > 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 odhiambo(a)gmail.com >

1 year, 11 months

[MM3-users] Re: Internal Server Error on installing Mailman 3 using PIP

by Mark Sapiro

On 10/28/20 11:04 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As you have suggested in my earlier issue, I have implemented > the latest stable version of mailman 3 through the URL > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > . > > But after the installation through the above URL, when I > tried running the command *elinks http://localhost:8000/postorius/lists > <http://localhost:8000/postorius/lists>* or *elinks > http://localhost:8000/admin <http://localhost:8000/admin>*, I got the error > as *Internal Server Error*. > > I don't find any specific log in mailman.log or in > mailmansuite.log. > > Is there any way to solve this issue ? > You need to hire a consultant who understands Mailman 3 installation to help you with this. The help you need is beyond the scope of this list. I am not available as a paid consultant. I do not do that work. See <https://wiki.list.org/x/4489296> for a partial list of people who do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Mailman do not honor non-members moderation setting sometimes

by Mark Sapiro

On 6/16/20 1:28 AM, Alan So wrote: > Some of our users reported that their list do not honor the nonmembers moderation setting sometimes. We were not able to repeat the issue consistently earlier. Luckily, we found the following way to repeat the issue: > > 1) Create a new list with user(a)example.com as owner. (Ordinary disussion mailing list style) > 2) Change the list Settings -> Message Acceptance -> Default action to take when a non-member posts to the list: Discard > 3) Add a non-member user(a)example.com and change the moderation setting to Hold for Moderation > 4) Send an email to the list using user(a)example.com. > > The message is discarded instead of being held. The above can also be repeated with the list setting Default action to take when a non-member posts to the list: Accept immediately. The message sent from user(a)example.com is accepted instead of being held. So, it looks like that the non-members moderation setting is ignored for this case. > > Further study indicate that the issue did not happen if the owner is set to user(a)example.com *after* adding the non-member. It looks like that we can avoid the issue during list creation. However, the issue can also be triggered through other ways such as adding the non-member as member and remove. There are also ways to resolve the issue by removing all corresponding member, non-member, owner setting and add them back in the following order: non-member, owner. However, it does not always work and so I do not go into the detail at this moment to complicate the issue. This is a known issue. See <https://gitlab.com/mailman/mailman/-/issues/659#note_270261964>. When the same user/address has both non-member and owner roles, setting moderation for the non-member in Postorius actually sets moderation for the owner which is meaningless because the owner role is never checked for moderation. Since the reference above is obscure, I have created https://gitlab.com/mailman/postorius/-/issues/436 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Enforcing SSO and subscription options

by Stephen J. Turnbull

via Mailman-users writes: > Thank you for the reply. Ultimately, I ended up digging deeper > into the allauth docs, per your suggestion, and I went a little bit > further with the "SOCIALACCOUNT_ONLY" option. It turns out that > the errors I were seeing were related to the sign up button > referencing a view that didn't exist. You have to do this, I suspect (I am unsure that removing the reference from urls.py would protect you from A Sufficiently Smart Miscreant, and if it did you'd still get the error, so why not remmove the code and remove all doubt!) > I solved this in an admittedly ugly way, by removing the sign up > button from the postorius and hyperkitty templates. You do not have to do it this way. There is a search path for templates, and you can remove those buttons from copies stored in a directory earlier in the path. I use /etc/mailman3/templates/..., but they can go anywhere convenient that won't be overwritten by an upgrade. The worst that could happen is the copies get removed, and then you get the error, which you fix.

2 months

[MM3-users] Re: Mailman 3 Installation

by Mark Dadgar

On Jan 16, 2021, at 7:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: >> I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? > > You can use sqlite, but if you don't already have a mysql/mariadb > database on the server, we recommend postgresql for performance and > robustness. I personally have had issues with mysql and use postgresql > on one production server that uses mysql for other applications. I’ll word this a little more strongly: do not use sqlite for a production server. Do not "just start with sqlite to get it running and then I’ll migrate it to something else down the road.” There is currently no validated way to migrate a mailman3 instance from sqlite to something else, and by “no validated way” what I actually mean is “no one has managed to get this to work, me included.” Put in the extra effort to start with posgresql or mysql/mariadb up front. You’ll regret it if you don’t. Ask me how I know. 😁 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 3 months

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

by Jörg Schulz

the "requirements.txt with "~=" compatible" bit sounds reasonable. By the way, the current rolling release of your docker image sports the 0.58.2 version and seems to work just fine. Am 2. November 2023 um 09:24 schrieb "Abhilash Raj" <maxking(a)asynchronous.in <mailto:maxking@asynchronous.in?to=%22Abhilash%20Raj%22%20%3Cmaxking%40asynchronous.in%3E>>: (...) I agree, but past few days I've been thinking if we should do _something_ about it so that after a while 'pip install' doesn't just start failing for folks forcing us to do another release to pin to a version that we support. In the past, we've had to do that a couple of times for various packages and maybe it doesn't make sense for to pin to a very specific version, but maybe we can provide a requirements.txt with "~=" compatible release requirements so it doesn't stop newer bugfix/security releases from being installed. There will still be issues with packages that don't follow semver or unknown bugs (which was the case IIUC in allauth) that creep up, but it can still prevent us from intentional compat changes made by bumping major version. Thoughts? (...)

1 year, 5 months

[MM3-users] Re: An archive/read-only list on a full setup?

by Mark Sapiro

On 4/11/23 09:36, Andreas Schamanek wrote: > > I have a working full installation of mailman3, postorius and hyperkitty > (on Debian 11). Now I wanted to host the archive of a remote list, and I > am wondering how to do this properly. > > After I found no documentation and no posting I simply created a list in > mailman3 with only 1 dummy member. The list address is subscribed to the > actual remote list. So, messages arrive and are archived. But that's not > optimal because hyperkitty thinks it's a normal list where it should be > read-only and do not allow subscriptions etc. > > What's the proper way to set up a hyperkitty-only list? There really isn't one as HyperKitty is intended to archive Mailman lists, however, it is possible to have a list in HyperKitty without a corresponding Mailman list. Thus, in your case you could just remove the Mailman 3 list you created and leave the HyperKitty list. Then you have an issue with posts, so you can keep sending the posts to be archived to the prior list address, but arrange for the incoming MTA to pipe mail to that address to a process. That process would do the following. Add a Unix From_ line at the beginning of the message and write the result to a temp file. Invoke a command like django-admin hyperkitty_import --no-sync-mailman --since 1990-01-01 \ -l list(a)example.com /path/to/the/tempfile where list(a)example.com is the actual HyperKitty list. This will archive the message. The addition of a Unix From_ line is to make the message file look like a mbox. Since there is no Mailman list, attempts to post or reply directly from HyperKitty will fail, although such attempts using email software will probably succeed in archiving the mail, and mail directly to that list address will be archived, but such messages won't go to the remote list. This may not be any better than what you're currently doing. -- 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: Welcome message template errors

by Mark Sapiro

On 4/23/24 17:51, Mark wrote: > > > >> On 2024-04-24 03:58, Mark Sapiro wrote: >> >>> What do you get if you do >>> ``` >>> sudo -u mailman curl >>> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… >>> ``` >>> with the template set in Postorius? >> > > ******************* > >> The welcome message is returned. >> >> root@hel:~# sudo -u mailman curl >> https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… >> Test Welcome message for new subscribers.root@hel:~# > > ******************* > > Making progress... > > I edited settings file again, replacing the domain name with the IP > address () > > POSTORIUS_TEMPLATE_BASE_URL = 'http://12.34.56.78' (no SSL) That should be no different than `http://host_name` where host_name's DNS A record is 12.34.56.78. > The URI in the template table now has this. > > http://12.34.56.78/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/list… And if you go there in a browser, 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

1 year

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

by John Covici

On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote: > > On 3/13/21 11:14 AM, John Covici wrote: > > > > Now one thing came up while trying to create the database, I got a > > traceback complaining about a revision error because gentoo had a > > slightly different version (3.3.2) instead of 3.3.3 using pip. When I > > upgrade mailman, am I going to have to do something to the database as > > well and why should the database have some kind of reference to the > > mailman version? > > > I don't know why this is an issue. You shouldn't need to do anything > with the database when you upgrade. Please post the full traceback and > error message. Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string. -- 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: Can't deliver mails in queue

by Nathanael Schneider

>> I then created a completely new List which did not exists in mm2.1, >> subscribed two addresses and sent myself an EMail. That one worked as >> intended. I then deleted the whole broken list and created it cleanly, >> added the same two people, sent an email and nothing. > > This seems strange. If I understand, you are essentially saying the two > lists are the same. I.e., you created a completely new List which did > not exists in mm2.1, and that one worked. Then you deleted the whole > broken list and created it cleanly ... What was different between this > cleanly created list and the completely new List? They were in fact not identical, as I changed some stuff in hopes to get it up and running again quickly. I now changed the completely new List to be identical with the cleanly created one (as far as postorius shows me) and it still works just fine. >> May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> >> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net >> May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> >> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net > > The fact that these are the only messages says that the attempt to send > that message via smtp raised no exception as exceptions would have been > logged, yet you say there's nothing in the maillog so there was no > connect to Postfix. What are your settings for smtp_host: and > smtp_port: in the [mta] section of mailman.cfg? I set nothing explicitly as the default options fit my needs, so localhost:25 it is to my knowledge. Postfix itself was configured by Plesk and the config for mailman3 was manually added as prescribed. A manual telnet on localhost 25 gives me the expected 220 message from postfix. >> I have no clue what to do with this. I then turned the debug module >> loglevel to debug. Also nothing useful. Just an endless list of >> >> [...] >> May 19 18:17:29 2021 (7209) [outgoing] <function deliver at >> 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> >> May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop >> May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 >> May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: >> 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd >> May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic >> May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction >> May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit >> May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 >> May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop >> May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: >> 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e >> May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile >> May 19 18:17:29 2021 (7209) [outgoing] <function deliver at >> 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> >> [...] >> >> Which also tells me nothing I can understand. > It says the message in queue entry > 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled > but gets requeued as > 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which > presumably is handled and requeued again ... Ok. Then I just need to figure out why it gets requeued. That also explains why the out-queue folder keeps creating a single message with different filenames over and over. But the logs keep silent about the reason.. >> I have no clue what's >> going wrong. (I've turned on debugging both on the original member list >> and the reduced member list. Both hang on the first delivery they do). >> If I restart mailman, the message gets correctly shunted as it is >> interrupted mid-delivery. My maillogs don't register any activity beside >> the listpost. Any ideas what I need to do to figure out what's not >> working here or where the culprit could be? Not sure if it is related to >> the mailinglist being in mailman2.1 before. > > I have no real understanding of why this isn't working. I don't think > it's likely that it has to do with the mailing list being imported from > MM 2.1, but I suppose it could be. > > How did you create and import the list? When you say you deleted the > whole broken list and created it cleanly, what did you actually do? My steps where basically what the migration guide told me to do. First, I created the new list in postorius, I then copied the config.pck over to the mailman directory, chowned it to mailman and imported it in the venv using mailman import21 list(a)example.com config.pck Does import21 expect anything besides the config.pck? Maybe it couldn't find the required files and botched something? I recreated the list by deleting it in postorius and creating it anew. It could be that there is some configuration that does not get cleaned properly? If it helps, I've also made a document containing all the specific steps I used for my server as I've tested the setup process first before rolling it out (not the migration though) on a different server to get it done without a hitch. -- Nathanael Schneider

3 years, 11 months

[MM3-users] Trying to set up mailman3 on my mail server

by Shawn Heisey

I'm having a lot of trouble with trying to set up mailman3 on my mail server. It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2. The problem I am trying to troubleshoot first is how this can be happening: Oct 14 11:27:26 2021 (2341) ACCEPT: <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on port 25 From the shell, I can "telnet localhost 25" successfully, even as the "list" user. Apparmor is disabled. The UFW firewall is enabled, which allows all traffic on the loopback interface. I disabled ipv6 at the kernel level, but had the same problem with ipv6 enabled, so I don't think ipv6 is related at all. I do not see any connections in the postfix log that correspond to the mailman connection error. From a fresh install of mailman, I created two mailing lists. Once upon a time I had those lists active on a Debian 6 machine running mailman 2.1.13 ... I copied the mailing list config from that machine over and used the "import21" facility to import the configuration into the new mailman3 install. That worked without error and I can see the lists and their members with the "mailman" command. I found instructions for integration with postfix, and added the required three config lines to the postfix config. When I try to send a message to the list, I get what I pasted above in the mailman log. I think that means the postfix integration is working, and is forwarding to mailman. I'm hoping somebody can give me some pointers, and if more information is needed for troubleshooting, let me know what is needed. I'm also having trouble with the web UI ... I thought I had found what to do with Apache, but it's having problems and I do not know what to do so it works. The UI is not super important right now, I'd like to get the lists working first. I first tried to get help on the IRC channel, but that appears to be a dead end. I did give it several hours. Thanks, Shawn

3 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 14:09, Simon HANNA (<simon.hanna(a)serve-me.info>) escribió: > > > On August 3, 2017 8:50:41 PM GMT+02:00, Rafael Mora < > rafael.mora.guti(a)gmail.com> wrote: > >El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) > >escribió: > > > >> On 08/03/2017 10:42 AM, Rafael Mora wrote: > >> > > >> > I've found the MX records on my cpanel but how do I redirect the > >emails > >> > going to my list to my private server? > >> > >> > >> You have to configure the MTA that is the MX for the domain to relay > >the > >> mail to the Mailman server. > >> > > > >Our domain is: LABBRANDS.COM We have that domain config in a Hosgator > >hosting. The emails sent to labbrands.com go to our hosting, so how do > >I > >tell cpanel in hostgator hosting that the mails sent to the list ( > >mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private > >server (we have static public IP address) ?? > > > You can't redirect one email address using DNS! > If you don't want to host an entire domain on your own server, I suggest > using a subdomain (lists.example.con) instead. > Should I configure my private Centos7 server with subdomain lists.labbrands.com? Doing so how do I redirect the email to the private Centos where postfix and MM3 are installed? > You could probably also redirect one email in cpanel to the subdomain, but > I'm not sure how mailman and clients like emails with different domains... > In theory postfix can send emails using any domain. You just have to make > sure spf, dkim and PTR records are properly set. Otherwise you'll most > likely get issues with rejected mail... > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: What to backup?

by Alain Kohli

Thank you, that's perfect! For anyone that might stumble upon this, I had to make two minor adjustments to automate it. import os msg_ids = {} lm = getUtility(IListManager) ms = getUtility(IMessageStore) for mlistin lm.mailing_lists: requestdb = IListRequests(mlist) for rqin requestdb.held_requests: key, msgdata = requestdb.get_request(rq.id) if msgdata['_request_type'] !='held_message': continue msg = ms.get_message_by_id(key) msg_ids[(msg['Message-ID-Hash'])] =True for root, dirs, filesin os.walk('/docker/var/messages'): for filein files: if not msg_ids.get(file, False): msg = ms.get_message_by_hash(file) # It happened to me that msg was 'None' if msg: ms.delete_message(msg['Message-ID']) # I couldn't run it with '--run' and if you pipe it into 'mailman shell' # I needed this or the loop above wouldn't execute. pass On 5/27/19 6:22 AM, Mark Sapiro wrote: > On 5/26/19 3:07 PM, Mark Sapiro wrote: >> You could modify the above to write the list to a file and then wrap the >> whole thing in a shell script which would make the list and then do >> something like >> >> for f in `find var/messages -type f`;do >> n=`cut -d / -f5 <<<$f` >> for keep in `cat list` ;do >> k=0 >> if [ $n == $keep ] ;then >> k=1 >> break >> fi >> done >> if [ $k -eq 0 ]; then >> rm $f >> fi >> done > Actually, I thought about it a bit more, and I decided that arcane shell > script was a bit obscure and it would be easier to just do it in Python. > Plus, you can properly delete the message that way. > > A complete script for `mailman shell` is like > > import os > msg_ids = {} > lm = getUtility(IListManager) > ms = getUtility(IMessageStore) > for mlist in lm.mailing_lists: > requestdb = IListRequests(mlist) > for rq in requestdb.held_requests: > key, msgdata = requestdb.get_request(rq.id) > if msgdata['_request_type'] != 'held_message': > continue > msg = ms.get_message_by_id(key) > msg_ids[(msg['Message-ID-Hash'])] = True > > for root, dirs, files in os.walk('path/to/var/messages'): > for file in files: > if not msg_ids.get(file, False): > msg = ms.get_message_by_hash(file) > ms.delete_message(msg['Message-ID']) > >

5 years, 10 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 14:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:15 PM, Rafael Mora wrote: > > > > Should I configure my private Centos7 server with subdomain > > lists.labbrands.com? > > Doing so how do I redirect the email to the private Centos where postfix > > and MM3 are installed? > > > Create a DNS A record for lists.labbrands.com with the IP of the Mailman > server. You will also want a rDNS PTR record pointing from the IP to > lists.labbrands.com. > Does the rDNS PTR record should be placed in my Centos7 server? I've created the DNS A record for lists.labbrands.com with the IP but I don't know the port that it uses so I can make a port redirect to my local ip address wich is 192.168.1.42, do you know the port????? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

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

by Hagen Bauer

Hi, same thing here. A lot of usergroups "accept" social media but in regards to data privacy like to avoid it. Although technical not true people might believe that Facebook & Co have access to the data in a local mailman install. I would like to disable it to but havent yet the time to dive into it. +1 for site wide disabling Regards Hagen On 12.02.19 17:11, Stephen J. Turnbull wrote: > Note: I've changed the order of sentences from Torge's post to fit my > responses. > > Torge Riedel writes: > > > I do agree, same here on my side. Lot's of my users are very > > "sensitive" to social media and don't want see them here. > > This is the first I've heard of this. Obviously it's fairly > widespread; *please* speak up if anyone have similar issues that we > haven't addressed. AFAIK all of the currently active Mailman > developers believe that social auth is a GoodThang[tm], so we're > unlikely to DTRT as you see it without your help. > > > I need to migrate from mailman2 to mailman3 and was wondering why > > social accounts are enabled by default > > By default Mailman 3 is social media: you have a profile, you can be > searched in the indicies of the archives, and so on. The large auth > providers provide more secure authentication, and a lot of convenience > for users who have such accounts already. They also take some > administrative burden off the list and site managers when people lose > their passwords and forget what their subscription address is, and > similar scenarios. Clearly, these are not universally-valued > features, but I think that they justify the current defaults. > > > and are difficult to disable. > > They're easy enough to disable (easy to recognize and just add a hash > character in front), since you have to edit settings_local.py to > install anyway. If you're using a packaged version and the package > configuration utility doesn't handle it, there's nothing we can do > about it. The distro will have to deal with that. > > It should be better documented, I imagine (haven't checked yet). > > > I propose something like an additional setting listing the enabled > > social accounts. > > Do you mean in the Postorius administration interface? If so, do you > want it by-site, by-domain, or by-list? ("You" is everybody who wants > to disable social auth, not just Torge!) > > If you mean in settings_local.py, I suggested something similar > earlier. It's not obvious it would be easy to do (sometimes these > things are order-dependent, though that's bad practice). > > > And if the admin is setting this to an empty value in the > > settings_local.py everything is disabled > > Because the settings are a Python module, this is the way > settings_local.py works anyway. That's why Mark suggested editing > INSTALLED_APPS. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 2 months

[MM3-users] Re: Mailman3 Setup

by Odhiambo Washington

On Sat, Jun 11, 2022 at 4:03 PM George R. Kasica <gkasica(a)netwrx1.com> wrote: > Mark: > > These all reference the virtual environment setup, which is fine if I need > to go with that. I’ve already installed the components etc. As a “standard > installation. Do you know of a good doc that would help me set up in a > non-container environment – just the native OS – Ubuntu 20.04 LTS. If I > need to go with a virtual environment, do I need to uninstall what I have > out there and what’s the best way to get all the added bits out? > The virtual environment is self-contained. It really does not require much of what is installed in the OS, bar for the web server engine, IIRC. So yes, you will need to uninstall what you already installed (so as to have a clean system) and the best way to get all the added bits out is to follow the HOWTO that you used, in reverse order :-) You can also look at https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 and maybe do the 'apt remove blah' that you had installed. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] how to administrate mailman3 in CLI ?

by Stephen J. Turnbull

Hi testeur via Mailman-users writes: > I have installed mailman3 and i want to administrate it with rest > api, Do you really mean REST API, or do you mean CLI? > i tryied with curl to manage it, i can see if there is a pending > message with : > > curl --user restadmin:restpass > http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m > json.tool| This is a lot easier using "mailman shell" if you want to use CLI, or a Python program using mailmanclient if you really want to use the REST API for some reason. This is explained here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… but it's likely to be pretty rough going for you because it's really oriented to programmers studying to be Mailman developers, not for admins. > but� how to delete all held messages ? is it possible in one time ? No, you need to fetch the list and then loop over the messages. > And how to select a specific message to discard /accept / defer ? > > do i have to use a POST ? This is all explained here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Steve

1 year, 7 months

[MM3-users] Re: Where to find disabled members?

by Mark Sapiro

On 11/4/24 19:28, Bill Oliver wrote: > > a) See who is disabled, and > b) un-disable them by hand > > or... do I just have to wait seven days for them to automatically get > un-disabled? They do not get automatically re-enabled ever the user or you has to manually re-enable delivery. For an individual user, in Postorius you can click the user in the members list and see their delivery status and reset it. To deal with the whole list membership for a list, you can do ``` $ shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` If you just want to list them ``` >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

ok, thanks Mark, I'm getting an error doing: (env) [mailman@localhost mailman-suite_project]$ python2 manage.py migrate Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management What do you suggest?? El vie., 21 jul. 2017 a las 14:31, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:07 PM, Rafael Mora wrote: > > Installing mailman-suite for web ui. I did this: > > > > (env) [mailman@localhost ~]$ git clone > > https://gitlab.com/mailman/mailman-suite/ > > Cloning into 'mailman-suite'... > > error: RPC failed; result=22, HTTP code = 404 > > fatal: The remote end hung up unexpectedly > > > > > > but it returned an error, what should I do?? > > > It's another case of incorrect docs. It should be > > git clone https://gitlab.com/mailman/mailman-suite.git > > See <https://gitlab.com/mailman/mailman-suite-doc/issues/15>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

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

by Mark Sapiro

On 3/9/21 1:59 AM, Per Jessen wrote: > All, > > I am trying to figure why a particular outbound message was bounced, so > I'm looking for the text of the NDR that was sent - where do I find > that ? Mailman 2.1 would include the NDR in the notice to the admins when delivery was disabled or bounce score's incremented if those notices were requested. Mailman 3 has no such capability. If you have access to the server, this patch ``` > diff --git a/src/mailman/runners/lmtp.py b/src/mailman/runners/lmtp.py > index 6a0bdcf5e..eca474089 100644 > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -217,6 +217,8 @@ class LMTPHandler: > slog.debug('%s subaddress: %s, queue: %s', > message_id, canonical_subaddress, queue) > status.append('250 Ok') > + if queue == 'bounces': > + config.switchboards['bad'].enqueue(msg, msgdata) > except Exception: > slog.exception('Queue detection: %s', msg['message-id']) > config.db.abort() ``` will add all received bounces as queue files to var/queue/bad/ where they can be examined with `mailman qfile`. -- 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] problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

Hi. I am having a great deal of difficulty installing mailman3 using gentoo and sendmail. Also, I want to upgrade my old mailman2 data to mailman3. What I have done so far is to install the mailman3 packages from my repository and got this: django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman version 3.3.2 (apparently the core), postorius version 1.3.3 and hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. Now trying to read your documentation, it seems it wants me to reinstall some packages using pip in the home directory of the mailman user in a python virtual environment, that was the first thing. But I would like to avoid multiple package managers wherever possible -- gentoo is already a lot of maintainance without dealing with pip's maintainance. The binaries also seem to be different from my gentoo packages. So, how do I proceed with getting mailman3 up and working, configuring the database, configs, etc and I guess after doing that upgrading mailman2 and getting sendmail to interface properly with mailman3? Thanks in advance for any suggestions. -- 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: spanish localization

by Mark Sapiro

On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > very significant date for me (it is my wedding anniversary) and I'm 90% > sure that I dedicated time to Weblate after that date... With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical. If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>. > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, after > updating to the latest releases, are still in Englanish (more English than > Spanish). > > This is not a fight, we want to help, but do not know how. And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files. -- 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] Problems getting MM3 to work

by Alain D D Williams

I have been using mailman2 for some 15 years ... decided that it is time to upgrade to MM3. I have to admit that I am finding it very hard to do so. My target is a Rocky Linux machine (AKA CentOS/RedHat). I am doing a test install in a virtual Debian 10 machine - the idea is learn how it hangs together before reimplement on Rocky (where I tie things down with SELinux). For me the biggest problem is the poor documentation - for someone who is new at MM3 and is not a Python programmer. After a few false starts I am doing a virtualenv installation as described: https://docs.mailman3.org/en/latest/install/virtualenv.html (Changes: I am using mariadb not postgresql, apache not nginx) I am trying to set up the WSGI server. It thinks that my domain is example.com ... when I 'grep -r example.com /opt/mailman' I see 11338 lines - far too many to look through. Could someone please tell me what/where I configure to enter my test domain. Thanks in advance. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 11 months

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

by Per Jessen

Mark Sapiro wrote: >> diff --git a/src/mailman/runners/lmtp.py >> b/src/mailman/runners/lmtp.py index 6a0bdcf5e..eca474089 100644 >> --- a/src/mailman/runners/lmtp.py >> +++ b/src/mailman/runners/lmtp.py >> @@ -217,6 +217,8 @@ class LMTPHandler: >> slog.debug('%s subaddress: %s, queue: %s', >> message_id, canonical_subaddress, >> queue) >> status.append('250 Ok') >> + if queue == 'bounces': >> + config.switchboards['bad'].enqueue(msg, >> msgdata) >> except Exception: >> slog.exception('Queue detection: %s', >> msg['message-id']) config.db.abort() > ``` > will add all received bounces as queue files to var/queue/bad/ where > they can be examined with `mailman qfile`. Thanks. Yep, I'm getting NDRs kept now. "mailman qfile" seems to be a bit slow, 2-3 seconds per go. To look for a specific address that bounced, is there any mailman tool for grepping through a collection of bounces? (I have +1200 after a few days). I'm trying with this: find /var/spool/mailman/bad -type f -name \*pck |\ while read m do (mailman qfile $m | grep -q ad.dr@ess) && echo $m done Is there a better way? -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

4 years, 1 month

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 21:32 -0800, Mark Sapiro wrote: > > > Have you added an Alias Domain for your domain? > > After doing that did you run `mailman aliases` or restart mailman to > (re)generate the files. > > postfix_domains postfix_lmtp postfix_vmap > postfix_domains.db postfix_lmtp.db postfix_vmap.db > > > -- > First, thanks for your patience. Two steps forward and one step back, here. I have the interface running and I can create a list which *does* send messages to my test recipients. To answer your question, yes, I did all that, and that generates postfix_domains and postfix_lmtp, but not postfix_vmap. Here's what I got: $more postfix_domains # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-26 22:29:27 # # 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. libertyfp.org libertyfp.org $more postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-26 22:29:27 # # 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. # Aliases which are visible only in the @libertyfp.org domain. testlist(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-join(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-leave(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-owner(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-request(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-subscribe(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-unsubscribe(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 But no postfix_vmap. However, let me ask another question first: When running mailman3, do I need to set up a completely different virtual domain for it to run in? My "real" domain name is libertyfp.org, and I'm trying to make mailman work on that domain, e.g. "testlist(a)libertyfp.org." I'm starting to get the idea that I need to stick a completely different domain in there for the mailinglist. Which I can do -- I've got another two or three domain names to play with. Is it a problem to run the mailinglist on the same domain that the machine sits on for its regular business? A lot of the errors I'm getting seem to be from trying to do regular mail *and* the mailinglist on the same domain. Now that I've installed all this stuff a couple of times, I can easily re-install for a second virtual domain, if that's what I should be doing. But, on to what's not working now... Unfortunately, I seem to have completely screwed the pooch on getting postfix/dovecot to play nicely with respect to *receiving* mail. First, adding "virtual_alias_domains" (and putting libertyfp.org in it) and commenting out "virtual_mailbox_domains" resulted in postfix ignoring all my virtual mailboxes. Mail still worked, but mail is now being sent to /home/<user>/Maildir instead of /home/vmail/libertyfp/<user>/Maildir -- which means that dovecot, which looks in the virtual mailboxes, is now unaware of new mail. I suppose I could link /home/<user>/Maildir to /home/vmail/libertyfp.org/<user>/Maildir, but I suspect there will be problems and it's not a real fix. But.. .a problem for another day. Except... the same thing is happening with the mailinglist. In mailman3: I set up a test list (testlist(a)libertyfp.org) and added two test users (one local and one on a different domain). They added just fine, and both received the welcome message. However, when I replied, both messages bounced with the error that "testlist(a)libertyfp.org" was "user unknown in virtual alias table." No problem, I thought. So I added: testlist(a)libertyfp.org testlist to /etc/postfix/virtual, and testlist libertyfp.org/testlist/Maildir to /etc/postfix/virtual-mailbox, and I added testlist as a user: $ adduser -m testlist So, now mail from my list members goes to /home/testlist/Maildir, but not to the mailinglist. I also have managed to get another *different* warning, and the "there ain't no vmap, newbie" error as well: Dec 26 17:33:11 libertyfp systemd[1]: certbot.service: Consumed 1.041s CPU time. Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: error: unsupported dictionary type: #hash Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: connect from billoblog.com[162.144.108.19] Dec 26 17:33:16 libertyfp postfix/trivial-rewrite[46479]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and relay_domains Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap lookup error for "fplist(a)libertyfp.org" Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: NOQUEUE: reject: RCPT from billoblog.com[162.144.108.19]: 451 4.3.0 <fplist(a)libertyfp.org>: Temporary lookup failure; from=<billo(a)billoblog.com> to=<fplist(a)libertyfp.org> proto=ESMTP helo=<billoblog.com> That "you can't have both virtual_alias_domains" and "relay_domains" seems like it should be a clue. But I don't' know what for. Adding virtual_alias_domains really changed things... Anyway, here's the part of the /etc/postfix/main.cf that I think is likely important. Note that I comments out "virtual_mailbox_domains". myorigin = localhost mydestination = localhost, localhost.$mydomain alias_maps = /etc/aliases (which, by the way, just contains "postmaster: root") home_mailbox= Maildir # add to the end (add ssl support) smtpd_use_tls = yes smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_cert_file = /etc/letsencrypt/live/libertyfp.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/libertyfp.org/privkey.pem smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache # add to the end (add virtual users) # if specify multiple domains, specify comma or space separated #virtual_mailbox_domains = libertyfp.org virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 # mailman3 changes owner_request_special = no always_add_missing_headers = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 virtual_alias_domains = hash:/etc/postfix/domains virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap #hash:/etc/postfix/virtual Here's the postfix maps: /etc/postfix/domains: libertyfp.org # /etc/postfix/virtual: fp145(a)libertyfp.org fp145 mailman(a)libertyfp.org mailman testlist(a)libertyfp.org testlist /etc/postfix/virtual-mailbox: mailman libertyfp.org/mailadmin/Maildir/ fp145@localhost libertyfp.org/fp145/Maildir/ testlist libertyfp.org/testlist/Maildir

3 years, 3 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

Ok thank you Abhilash, I'll check the MX records. El mié., 2 ago. 2017 a las 13:07, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi, > > On Wed, Aug 2, 2017, at 10:57 AM, Rafael Mora wrote: > > Hello, > > > > I created a test list called: testlist1(a)labbrands.com > > > > How do I do in order to redirect the incoming emails to that direction to > > my server with MM3 ?? > > You typically need to change the DNS records for you domain to redirect > emails to your server. Particularly, MX Records are which relate to > Emails. > > I am not sure about how to do that with cPanel, but I think their > docs/support might help with DNS settings. > > > > > Thanks > > -- > > > > 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

7 years, 8 months

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

by Stephen J. Turnbull

kontakt(a)michaelbakonyi.de writes: > I have the same usecase as Krešimir and tried the example of > Mark. So in mailman.cfg I set hostname to > "https://lists.mydomain.org" and then fire this command I don't recall this, and unfortunately Mark is on vacation and completely offline until mid-September, except for maybe a couple days next week. > curl -urestadmin:mypw --referer https://lists.mydomain.org --request POST -H 'Content-Type: application/json' --data-binary '{"list_id": "thelist.lists.mydomain.org", "subscriber": "user(a)example.net", "display_name": "Joe User", "pre_verified": true, "pre_confirmed": true, "pre_approved": true}' https://lists.mydomain.org/mailman3/postorius/lists/thelist.lists.mydomain.… > > But then I get a CSRF-warning. Do I now have to get the token and > put it in my POST or is there an easier way to do this? As far as *I* know there's no way to avoid the CSRF warning. If that means you can't get the response data you need, you will have to do the CSRF two-step. With luck maybe Mark will see this in a few days but I think he's going to be busy preparing the 2d half of his trip. Regards, Steve

2 years, 7 months

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

by Stephen J. Turnbull

antoine.depoisier--- via Mailman-users writes: > First, my nodes are all an instance of mailman-core only. > I have an existing MTA that handle all email, and sent them to a > proxy, that dispatch all email between the existing pods. Then, > email are transferred to the MTA and MTA send them. So you are distributing mailman core across multiple nodes? And "proxy" = "load balancer" (such as HAProxy)? That is probably subject to a number of problems, unless you do things that I'm not sure how to do. For example, when a user account is disabled by bounces, every so often Mailman will send a "hey, are you alive again?" message to the user. If enough of those bounce, the user gets unsubscribed. The problem is that that status is recorded in the PostgreSQL database that all Mailman instances have access to, and I think they'll probably all send those messages. At best there's a race condition where more than one might send the message. Under some conditions moderators may get daily messages about bounces. I suspect they would get one from each Mailman instance. I think digests will be broken unless you share the lists subfolder, because each Mailman instance will accumulate only the messages it processes, so chances are good on an active list that digest subscribers will get multiple partial digests when they should get only one. As I'll describe below, Mailman tends to spawn a lot of processes, many of which don't have much work to do. Now you're dividing very little work across multiple nodes, which seems very wasteful. You haven't said where your MTA lives. If it's Postfix, it needs to share the $data_dir folder with a Mailman instance that is responsible for list creation. Every time you restart Mailman it recreates the files in that folder, so if it's shared among Mailman instances there will be delays due to file locking. So unless you have an insane amount of list traffic to process (say, a G7 national government ;-), I wonder if the multi-instance approach is necessary. Mailman is not implemented to be operated that way -- you're asking for trouble. The design is such that I imagine it can be done with careful tuning, but current default configuration didn't consider such a use case. You don't need to answer, you know your use case and I don't, but you may save yourself a lot of trouble by just running with a little more resources on a single node. Mailman uses a lot of memory just to get started (about 2GB unless you're really aggressive and do unsupported tuning of which runners are started and what modules are loaded), but then it easily scales without increasing resources except CPU to some extent. For example I've worked on a system that processes hundreds of thousands of incoming posts a day on a single Linode (2vCPU, 16GB) running core, Postorius, HyperKitty, Xapian, and nginx (PostgreSQL got its own VM for some reason). CPU usage on that system never gets above 25%, active memory usage generally 20-25% and there's usually a substantial amount free despite Linux's strategy of aggressively caching files, load average normally around 2.5 and never more than 5. The only tuning we did there was to bump the out queue's slices to 8 and in queue to 2, but all running on that same Linode (which pushes Mailman's memory usage to over 2GB). Running "ls -R queue" gives all empty subfolders about 2/3 of the time. > For the folder queue, I'm not sure if I should share this folder > between all pods, because one instance of mailman core mean one > worker if I'm right, No, one instance of Mailman core means a minimum of 15 processes (one master and 14 runners) in the default configuration. About half of those have nothing to do most of the time. You can probably whittle that 15 down to 11 with some care at a cost of a certain amount of functionality. Most runners have their own queues as subfolders of 'queue'. Each queue consists of message files with times derived from the timestamp of creation and a hash. Each runner processes its queue in order of the timestamps. When its task is complete, it passes the message to the next runner in sequence by moving the file into the appropriate subfolder (with the same filename). By the nature of email, each message is independent of all the others. So we can process them in parallel, as long as there is a way to assign one and only one runner to each message in a queue. The way we do that is to take the top N bits of the hash component of the filename, which we call a slice. Thus each queue has 1 or 2 or 4 or 8, etc slices. To configure multiple slices for the out runner (usually the bottleneck because it's the one that talks almost directly to the network[1]), add [runner.out] instances: 4 to your mailman.cfg and restart. That's what I recommend you do. Footnotes: [1] At least Postfix optimizes relaying by opening a connection to the remote smtpd while still talking to Mailman, and only queues the file on disk if the remote connection fails.

2 months, 2 weeks

[MM3-users] Re: Edit archived email? Is it possible?

by Stephen J. Turnbull

Prasanth Nair writes: > As you know, we can edit the individual messages using the message_id_hash. > Is there any possibility that we can edit the original message > which then updates all of the threads it has (for example, if someone > already replied to the original message)? Or do we need to edit each > message manually? What do you mean by "update threads"? If you mean, "make the same edit to quoted material in later posts in the same thread", you have to do that manually. Because of the variety of quoting styles, the fact that well-trained users will trim or edit much of the content, and the fact that some MUAs will refill paragraphs, you'd have to check every message anyway to ensure that the desired edit was actually made. It's not something that can be done automatically. If it's something that cause security exposure or legal liability for the host, don't forget to edit all alternative parts, by the way. Eg, the message has both text/plain and text/html alternatives, and you don't strip the HTML, the text you want to change will be duplicated in both parts. If that's not what you meant, please explain in more detail. Steve

3 years, 6 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Élodie BOSSIER

Thank you for your response Mark, With Mailman 2.1, the lists were split on their webpage respectively. How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? My domain table SQL have this result : id, mail_host, description, alias_domain 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr mailinglist table SQL : id, list_name, mail_host, list_id, ... 1, bar, ml.franceserv.fr, bar.ml.franceserv.fr, ... 2, viticreation, ml.viticreation.fr, viticreation.ml.viticreation.fr, ... Can I do something ? A patch somewhere ? Shall I wait issues are solved and how long approximatively please ? Which don't reassure me is I can see old discussions about FILTER_VHOST there are 2 years. I can retrieve my own old question there are 2 years when I tried to migrate from Mailman 2 to Mailman 3 : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and in 2020 you told me it was working for you at this date. It's don't reassure me to retrieve a problem I got there are 2 years. I could set in production my Mailman 3 but the problem is my customers won't understand why they can see the lists of others domains name ... and not sure about the security ... Thank you again. Le 18/02/2022 à 00:33, Mark Sapiro a écrit : > There are issues with FILTER_VHOST due to the fact that mailing lists > do not have a web host attribute. This means when you go to HyperKitty > or Postorius when FILTER_VHOST is True, we look up the domain record > for the web host you are visiting and show you all the lists whose > mail host matches the mail host for the web host domain. This has > nothing to do with alias domains. > > What that means is if all your domains records have a unique mail > host, FILTER_VHOST will work as you expect, but if multiple domains > have the same mail host FILTER_VHOST will show you the lists for the > current web host plus all those with a matching mail host. > > I.e. if in your case, the ml.franceserv.fr domain and the > ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't > separate them. If they have different mail hosts FILTER_VHOST will > separate them. >

3 years, 2 months

[MM3-users] auto-away notices as bounces

by Stephen J. Turnbull

Andreas Barth writes: > Looking into details, his mail provider sent out lots of auto aways > notices marked with > Auto-Submitted: auto-replied (vacation) > > Should we not exclude these as being counted as bounce? First of all, until recently Mailman 3 wasn't doing any bounce processing at all. Depending on your version, it's possible that Mailman had nothing to do with it. Now, are these going to the bounce address, or to the list? If they're going to the bounce address, I doubt they're being recognized as standard delivery status notifications. I think they're probably still counted as bounces if sent to a LIST-bounces address, but they should also be sent to the list owner as "unrecognized bounces". This decision isn't something Mailman should be doing because it depends on context and guessing what the subscriber wants. Really, this is an owner problem, not a Mailman problem. On the other hand, if they are going to the list itself, I don't think we treat those as bounces at all. It's not obvious what *we* should do. If Mailman continues sending posts to the user, it can fill his or her mailbox with mail that is in many cases available in archives. Not a good idea. In fact, typically the reason vacationers get unsubscribed is because their mailboxes fill up, and they generate real bounces. Or a moderator got tired of vacation messages to the list, and nuked the subscription. Are you sure one of those is not what happened here? I don't understand how the user managed to get automatically unsubscribed unless you have aggressive bounce settings on the mailing list(s) or they were gone for quite a while. What should happen is after the first few bounces they will be disabled, and then checks for reactivation will be sent once a day or so. It should take at least two weeks, and often longer, to unsubscribe a user. If you live where people habitually take month-long vacations, you should change your settings to account for that. Finally, if the user doesn't want to get unsubscribed while they're on vacation, they can set themselves to no-mail. They should also be able to resubscribe themselves; deleting a subscription for excessive bouncing doesn't delete the user's login account. Steve

3 years, 7 months

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

by Henrik Rasmussen

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 ?. 2) Where do I define the what was previously known as the site admin user and site admin e-mail? On another note: Is it a setting in the mailman-users(a)mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."? Thanks Henrik Rasmussen

7 years, 9 months

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

by Mark Sapiro

On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. > > 1) How do I set another default for Digest Size Threshold for new lists. It's hard coded in mailman/styles/base.py. It should be a config setting, but I think it's not. > 2) How do I change the default for existing lists Postorius -> Settings -> Digest > When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. No. digest_volume_frequency only controls how often the digest volume number increments (and issue number resets). In order to send periodic digests, you need to run 'mailman digests --periodic' via cron. > How do I change this setting, both on a single list and the default for new lists? The only setting is the lists digest_send_periodic which again is hard coded (to True) in mailman/styles/base.py. For existing lists, it is exposed in REST, but not yet in Postorius. -- 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] upgraded Django & flufl.lock now do not receive own postings

by Christian

I just upgraded Django from version 3.0.11 to 3.2.15 receiving this confirmation > Successfully installed Django-3.2.15 asgiref-3.5.2 I also upgraded flufl.lock from version 7.0 to 7.1 > Successfully installed flufl.lock-7.1 Then I restarted mailman, qcluster & gunicorn Now for some reason I'm not receiving my own postings to the list whereas before I was. 'Receive own postings' is still set to yes. Thank you! -----Original Message----- From: David Newman <dnewman(a)networktest.com> Sent: Friday, July 8, 2022 11:29 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14 On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? Yes > > So I would guess you can remove them. Probably you have the relevant > Ubuntu packages cached somewhere, and they're probably available from > Ubuntu if you really wanted them. This system runs Debian 11, with everything installed in a venv. I'm unclear on the relationship between the usual apt* tools and pip, and just do everything Mailman-related using pip. On 7/8/22 7:47 AM, Mark Sapiro wrote: > When pip is doing an upgrade of the xyz package, it renames the existing > package as ~yz and then ultimately deletes the old ~yz package after > successfully installing the new xyz. In this case, the upgrade was > aborted because of the Django<3.1 constraint in mailman-web and > apparently pip then installed Django<3.1 and left the ~jango* > directories behind. Ahhh, that explains it. Thanks for your replies. I've deleted the ~ directories and so far have not noticed any adverse effects. dn _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 7 months

[MM3-users] Re: mass remove pending confirmation

by Mark Sapiro

On 5/22/23 13:46, Jens Günther wrote: > > Since we migrate some lists from mailman2 to 3, there are a lot of new > users/subscribers and an admin made the mistake to not checkbox the 3. > option that the users don't need to verify their address. Are these newly added users since the migration? If you migrate a list with the `mailman import21` the users of the MM 2.1 list will be imported and there won't be confirmations. > Now we have a long list of pending confirmations in different lists. Is > there an easy way in the shell to mass remove these pending > mailaddresses so that we don't have to do that one by one? That would be > awsome. Do you want to remove them or confirm them. If you just remove them, the user's addresses will still be unconfirmed. If you just want to remove them so you can redo the mass subscribes, you could do something like the following in `mailman shell` ``` >>> pendings = getUtility(IPendings) >>> for token, data in pendings.find( token_owner=TokenOwner.subscriber, pend_type='subscription'): ... pendings.confirm(token, expunge=True) ... >>> 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: ARC

by brian＠emwd.com

Marvin Gülker wrote: > > I don't have that problem anymore since I pay for my SMTP relay > provider. For me, the issue is solved. Before my personal mail (I'm not > talking about mailing lists, just simple direct e-mail) was pretty much > always sorted into the recipient's spam folder or directly rejected at > the SMTP level (this was the case with both Microsoft and AOL; GMail > usually filed my e-mail als spam). I looked up the reasons they gave in > the SMTP reject; it was always bad reputation of IPs. Tools like > mail-tester on the other hand say my e-mail and IP was fine, and > delivery to small providers always went nicely. My mail server has never > sent a single spam e-mail. I run it since years, and I am very sure that > this never has happened. This mail server only hosts my and my family's > e-mail. Did you keep an eye on the reputation on the IP addresses you were sending from? Sometimes an IP address just doesn't send enough volume of mail to build one up. I do agree some providers do ignore the IP reputation of an IP address. For instance we had one that actually had a 100% reputation from SenderScore and it ran into a block with Microsoft. However the server had only been online for a few months and we placed a client there that increased the volume to Microsoft users. We did get that fixed. The key to Microsoft is to sign up for their Hotmail Feedback Loop. They also provide a nice interface (SNDS) that shows you what they think of your IP addresses so you can mitigate any potential delivery issues ahead of time. > Thus, I say they were rejecting my e-mail for no reason. Might be a > hyperbole, but from my point of view, there was no reason. Again, the > problem is now past with my workaround, so there is no need to > investigate any further. I've given up on it. I don't believe you can > have a VPS that directly delivers e-mail to the large providers > successfully. The workaround with the SMTP relay provider still allows > me to self-host, which fulfills my needs. I disagree. We are a list hosting provider (Mailman 2 and 3) that has about a dozen of VPS servers that are categorized as high volume senders and we see great delivery rates. Our clients all use their own domain or sub-domains as for their list as well. The key for us has been to keep our clients' lists clean by enforcing reasonable bounce settings and screening new clients to make sure we don't mistakenly take on a spammer. We do work hard to maintain our IP reputations. Yahoo is the worst. They ignore everything, are hard to get a hold of, says they want you to join their feedback loop but don't actually respond to your attempts at doing so, etc. However once the IP address "warms up" (Yahoo's language, not ours) delivery rates are as good as the others. The majority reason why messages ends up in Spam folders has nothing to do with the mail server at all. It is because the content of the message comes across as spammy, i.e. a message that contains several URLs, using exclamation points, etc. Brian

5 years, 8 months

[MM3-users] Using REST api to subscribe member

by Brian Carpenter

I have a development server that only has Mailman core installed on it. I used a virtual environment to do the installation but I did not install Postorius or Hyperkitty as I am currently working on developing a custom u.i. for Mailman 3. My programmer said the following: "I have a problem with mailman on development server ... I was trying to add member to a list using REST api, but to no avail. After I tried all possible and impossible things, I finally looked at the logs. Error I found in log file is: IsADirectoryError: [Errno 21] Is a directory: '/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/templates' I guess mailman was looking for a template for welcome mail, and failed for some reason. I also guess this has something to do with locale or language settings I tried googling, but couldn't find anything" The log that gave the error was /opt/mailman/mm/logs/mailman.log My programmer tried it on another server that has both Postorius and Hyperkitty working and the api call worked, i.e. added the member to the list and sent out a welcome email. So what else do I need to install to be able to use the api to add members to a list using a non-postorius interface? Any assistance would be appreciated. Thanks, Brian

5 years, 1 month

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

by Odhiambo Washington

On Sun, Jan 28, 2024 at 11:26 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > The issue you're dealing with in that case is this change in > > PostgreSQL-15 discussed in this blog: > > > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… > > Thank you for the reference! > > If you have a Mailman-only host, with a Mailman-only PostgreSQL, or > The Cabal of equally responsible maintainers are the only people who > work on the Postgres cluster, the two approaches are basically > equivalent. > > My take is that the default "right thing" is to transfer ownership of > the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON > SCHEMA public TO fred" in the case that you don't want to give "sudo > mailman" to Fred. > > Rationale: I believe there are a number of things that the 'postgres' > user can do that other users cannot, and you probably don't want > random contractors or new volunteers to have those privileges. On the > principlee that 'postgres' should only do those things that only > 'postgres' can do, you want to make the 'mailman' user the owner of > the 'mailman' database (and 'mailmanweb' too if you go that route). > Then if you have a user 'fred' who may be working on both mailman and > non-mailman databases in a session, then instead of giving sudo > mailman to Fred, 'mailman' can grant all on schema public in mailman > to 'fred'. > > It's a really fine difference, and probably will matter to almost > nobody running Mailman 3. I do think > > user 'mailman' owns the 'mailman' database > > is conceptually simpler than > > user 'postgres owns the 'mailman' database and 'mailman' has ALL > privilege on the PUBLIC schema > > Right? > Right! That makes more sense. -- 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: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/19/2018 03:22 AM, Henrik Rasmussen wrote: > > Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. If DMARC Mitigate unconditionally is No, DMARC mitigation action will only be applied if the original From: domain publishes a DMARC policy of quarantine or reject. If the action is not being applied in this case, there is some issue in looking up the DMARC policy for the domain. Possibly, dnspython is not available or there is some other issue with this. In any case, errors should be logged in Mailman's log. > Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? You need to do this with list styles. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. At present, Postorius doesn't allow specifying a style when creating a list, so you may need to modify mailman/src/mailman/styles/base.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Adding / manipulating users

by Mark Sapiro

On 11/18/19 6:15 AM, Seth Seeger wrote: > > My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. You are correct that there is no existing command line tool or Postorius way to do this. If you have facility with Python, you can look at the mailman import21 command which is actually processed by mailman/utilities/importer.py. It shouldn't be too difficult to adapt the part that imports the list members to use your data and create a script to do what you want. Alternatively, you could create a script that would post the appropriate transactions to add a member and set moderation and delivery status to Mailman's REST API and use that to process your members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

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

by Mark Sapiro

On 1/18/22 10:53 AM, Stephen Daniel wrote: > 2nd follow-up. Apologies for spamming this list. > > I went wandering through the code as suggested by the traceback. I > discovered that thee "as_boolean" routine is expecting a string argument > but getting a boolean argument. > > So, If I send the booleans as strings, with values "true" or "false", all > is well. > This is not what the API documentation suggests I should do. Can someone > either fix the documentation or the code? Those snippets in the documentation are doctests. That code is actually executed by unit testing and passes. In all those snippets, dump_json is passing the second argument as `data` to mailman.testing.documentation.dump_json() which in turn calls mailman.testing.documentation.call_http() which calls mailman.testing.helpers.call_api() which ultimately calls requests.request() with the same `data` argument. So basically, the issue is the difference between how requests.request() handles that `data` dictionary in creating the POST data and whatever you are doing. Possibly we could add some caveat to <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> or possibly elsewhere. Do you have a suggestion as to what? -- 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: Social signup?

by Mark Sapiro

On 3/12/23 14:32, Duane Raymond wrote: > > 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. The buttons do not appear on the sign-up page. They probably should, but they don't. > 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) You aren't missing anything. > 2. Do I manually add this code to the Posterius/Hyperkitty signup > template? No > 3. If a user tries to login via the login page and isn't registered will > it be counted as a signup? Yes, that's how it works. > 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) I just created https://gitlab.com/mailman/django-mailman3/-/issues/67 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Abhilash Raj: > On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: >> Abhilash Raj: >>> On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >>>> Hey Abhilash, >>>> >>>> Thanks a lot for your work on mailman3! >>>> >>>> Abhilash Raj: >>>>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>>>> >>>>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>>>> I can think of is non-member management in Postorius. >>>>> >>>>> New releases are available on PyPI[3][4]. >>>> >>>> For earlier releases, you provided GnuPG signature files to >>>> cryptographically verify that the release files were not tampered with. >>>> >>>> I couldn't find such signature files for the two latest releases. Would >>>> you mind adding them? When packaging for Debian, I prefer to check the >>>> GnuPG signatures before uploading new releases. Also, the signature >>>> files get uploaded to the Debian archive as well so they can be checked >>>> by everybody. That way we can cryptographically proof that the Debian >>>> package is based on the original tarball that got packaged and signed by >>>> upstream. >>> >>> >>> Ah, sorry about that. I completely forgot about that. >>> >>> I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. >> >> Thanks a lot, that would be awesome. I'll wait for it before doing the >> Debian package uploads. > > If it is not possible to upload signatures, I'll bump up patch versions > and push out new tarballs with signatures. Perfect, thanks a lot! >> Just to let you know: we're close to soft freeze in Debian, so in order >> to get those uploads into the next stable release (Buster), they'll have >> to be uploaded rather soon. > > Can you give a rough estimate on how long do we have before the freeze? See https://release.debian.org/buster/freeze_policy.html. For getting new releases into Buster, the full-freeze (2019-03-12) is relevant. Since packages per default take five days to transition from Unstable to Testing, 2019-03-06 would be the last day to upload. But given that we're all busy with other things and stuff, we better not calculate that tightly ;) >> The same holds for other pending releases of Mailman3 components: Just >> in case you plan to do new upstream releases anytime soon, it's still >> possible to upload them to Debian in time for Buster. > > I'll see if we can get other releases out too. Core doesn't yet have any backwards > incompatible changes, so I might end up bumping minor version and doing a > new release. Not sure much has changed in other components, but I can do > a release if there are enough changes. Sure, that would be awesome. Ideally after my recent merge requests got accepted ;) Cheers jonas

6 years, 2 months

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

by Mark Sapiro

On 11/11/22 16:36, Caballero, Danny (Dan) wrote: > Thanks for some clarification. > > I cleared out 2800 held messages via Python shell "mailman -l" option and it took about 28 hours. Anything done via Mailman shell is a connection from Mailman core to the database, correct? That's correct. > Although I can't replicate that many messages via Postorius/DJango, I do see similar slowness there as well at a message per minute or more of processing. > > I recreated the above Mailman shell clean up via Docker container running MariaDB and noticed similar processing time for discarding held messages. That leads me to conclude that the issue isn't network related or specific to AWS RDS. I'm assuming the docker container installation also had all the lists/users? It seems this must be related to a large number of lists/users and we must be doing a number of queries that doesn't scale well. This seems excessive. We'll have to look at the processing to see what we're doing. There have been some recent improvements in scaling. What Mailman core version is this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

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

by Allan Hansen

Much appreciated, Mark. We'll go with (a.), as it's a one-liner as I expected, and it does not require me to change the policy. I'll just need to make some adjustments to the template contents. Yours, Allan On 3/28/23, 11:29, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/NNMWW4PW55H4OLA3NTAKZLRNIEV2HHUA/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years

[MM3-users] Re: Django site - how to create programmatically - new install

by Clark Boylan

On Fri, Sep 30, 2022, at 10:12 AM, daniel.botting(a)codethink.co.uk wrote: > Hi all, > > I've mainly setup mailman3 to replace our mailman 2.1 install using > Ansible, a point I could do with some assistance on is setting the fqdn > used programmatically. I've been doing alot of reading before creating > this thread. > > To create a domain I currently navigate to: > https://serverfqdn.com/postorius/domains/ and click 'Add Domain'. > > I believe this is setting the name of the Django site, please accept my > apologies if I'm wrong and the SITE_ID=1 is then used, I am only > planning to use one domain only. I'm using Postgres and when I check > the contents of the Django_mailman3_maildomain table as below > afterwards: > > mailman3web=# TABLE django_mailman3_maildomain; > id | mail_domain | site_id > ----+--------------------------------------+--------- > 1 | mailman3-test2.guest.codethink.co.uk | 1 > > Many thanks You can create domains via the REST API: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… The documentation shows the use of helper functions, but you should be able to interact with the API using any HTTP client. We're doing this with Ansible and it looks like: https://paste.opendev.org/show/byAG1wqXVHgKVsJ28Eb9/ > > Daniel

2 years, 6 months

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Stephen J. Turnbull

Peter Münster writes: > If the "final fallback" as mentioned in > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > worked, that would be a good feature. Only one template in > templates/site/en and everything works as expected, independently of any > language settings. But that's not the way it works. If I understand correctly, you're referring to the overriding site-specific templates, but in fact there is always the fallback of the builtin template. I don't see how this can work any other way. The Mailman project is fortunate to have a team of translators handling all the default templates. They need to stay for many, if not the great majority, of sites. For example, on my site, I have to support English, Japanese, and Chinese. I can do the first two myself, but except for trivial cases like "suppress footer with empty template file", I definitely want to fall back to the default Chinese even if I've added site-specific or clarifying wording to the English and Japanese. If you think this kind of use case is really important (and I can imagine many other similar use cases, I just think they're too rare to justify even more complexity in the I18N algorithm), you could file an issue, requesting an "LC_ALL-like" override pseudo-language, such that if that template is set, all languages use it. Note, I've already figured out how to do this. I think it would do less good (save you a few "cp <template file> ../fr" copies) than harm (confuse people reading the docs who don't have a use case). All you need to do is convince at least one of the active core (me, Mark, Abhilash) that it's a good idea and I'll implement. For reference, from src/mailman/utilities/i18n.py: The <language> path component is variable, and described below. * The list-specific language directory $template_dir/lists/<mlist.list_id>/<language> $template_dir/lists/<mlist.fqdn_listname>/<language> (deprecated) * The domain-specific language directory $template_dir/domains/<mlist.mail_host>/<language> * The site-wide language directory $template_dir/site/<language> -------------------------------- HERE -------------------------------- * The template directory within the mailman source tree <source_dir>/templates/<language> ---------------------------------------------------------------------- The <language> path component is calculated as follows, in this order: * The `language` parameter if given * `mlist.preferred_language` if given * The server's default language * English ('en')

2 years, 7 months

[MM3-users] GNU Mailman has been accepted in Summer of Code!

by Stephen J. Turnbull

Just to let everyone know. [Cc'd to Mailman 3 Users, but please direct followups to the Mailman Developers list only!] GSoC "who we are" page is here: https://summerofcode.withgoogle.com/organizations/4903353420611584/ Ideas page is here: https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021 Student applications open on March 30, and continue until April 13 18:00 UTC. Comments, ideas, etc welcome on Mailman Developers (preferred) or directly to me or Abhilash. Please do NOT edit the ideas page on the wiki without discussing with me, Abhilash, or Mark, as Google has strict rules about what ideas are relevant to their program. If you have been active in GSoC and do understand the rules, the discussion will be "pro forma", but at least we do want to know what we might be asked about as potential mentors. We can add more mentors, definitely, you're welcome. If you can reliably spend about 5 hours per week on it for the summer, we'll sign you up as a regular mentor. If you'd like to interact regularly with students, but can't promise 5 hours a week, we can negotiate a semi-formal status (but you won't get the privileges of a full mentor, like the T-shirt). Otherwise, we'll try to keep discussions on the list, everybody welcome. Regards, Steve

4 years, 1 month

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

by Mark Sapiro

On 1/6/22 6:28 PM, Stephen J. Turnbull wrote: > Michael Heseltine writes: > > > > Do you have all of these apache modules enabled, proxy.conf, > > > proxy_http.load and proxy.load, in particular proxy_http.load? > > > > Well, mostly: > > > > > # a2enmod proxy_http.load > > > Considering dependency proxy for proxy_http: > > > Module proxy already enabled > > > Module proxy_http already enabled > > > # a2enmod proxy.load > > > Module proxy already enabled > > > # a2enmod proxy.conf > > > ERROR: Module proxy.conf does not exist! > > In my Debian configuration that module is needed because it contains > the necessary directives to enable proxying. Actually though, I think that's enabled as part of proxy. > The bottom line, though, is that that error message has to do with the > internal configuration of Apache, and as far as I can see it has > nothing to do with Mailman itself. However, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I now suspect the real issue is there's no wsgi server listening on port 8000. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Mark Sapiro

On 6/7/23 21:30, Nelson Strother wrote: > > Interestingly if I use `systemctl start mailman` thus far the results are: > - the wall clock duration is shorter than when `mailman start` is issued > from the command line, and > -- either that all of the runners remain present once they are started, > -- or I can see in syslog a traceback from each missing runner process > starting from .../mailman/.local/bin/runner and ending with > "flufl.lock._lockfile.NotLockedError: Already unlocked". > > I do not yet understand how to make use of these clues, but at least one > can see an epitaph from each deceased process. The NotLockedError is most likely because a lock has been set with a lifetime and its lifetime has passed and some other process has broken the lock before the original process tries to unlock it. This probably has something to do with the long times to do start/restart. However, the only lock that should be involved is the master lock set by the master watcher, so I don't really understand what might be happening. What is the full traceback from these errors? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Re-enable member after bouce processed disable

by Mark Sapiro

On 1/5/22 12:48 AM, Henrik Rasmussen wrote: > > It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces. > > Using the `mailman members` command it is possible to list such members, however how do I enable them using either the `mailman shell` command (available) og the mailmanclient (needs first to be installed in the docker container)? There is a `mailman shell` session in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… that will re-enable all bounce disabled members on all lists. To do just a single list do something like ``` $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print("Re-enabled delivery for bouncing member {} on list {}" ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: import21: A string literal cannot contain NUL (0x00) characters.

by Simon Hanna

On 02/12/2018 09:02 AM, Henrik Rasmussen wrote: > It seems that this issue is still unsolved. Is there any estimated date for a fix? https://gitlab.com/mailman/hyperkitty/issues/155 . > > Thanks. > > Henrik I commented on the issue, here is my comment for the lazy: That's actually an issue with the Postgresql backend. They don't allow storing null characters in strings. More information can be found in this bug report https://code.djangoproject.com/ticket/28201 and this discussion https://groups.google.com/forum/#!topic/django-developers/D1gvXYCezEc/discu… TLDR: Saving such values is currently not supported, it's highly unlikely you want to store the null character in the first place, so you should clean your inputs (in this case the file) to strip them out. I'm not sure Hyperkitty should actually do anything about that. Checking all inputs to strip null characters doesn't sound like a practical idea. If you import the values in any other way (loaddata for instace) you'd still run into this issue and there's nothing we can do about that. So I guess the sane thing to do, is to say that your input file has errors that you should fix. But then again, I don't really have anything to say. It's up to @maxking and @abompard to decide that.

7 years, 2 months

[MM3-users] Re: File Attachments

by Abhilash Raj

On Mon, Jan 7, 2019, at 11:27 PM, Stephen J. Turnbull wrote: > brian(a)emwd.com writes: > > > Thanks Mark. I went ahead and [submitted an RFE to implement file > > attachments in Hyperkitty posting]. > > This one is not GSoC'able by itself, right, Abhilash? But it seems a > little bigger than a minimal "can you submit a PR" test. Anybody know > if there are some other "buttons" we should put into the "post from > HyperKitty" UI that we could bundle up as a GSoC task? It is definitely bigger than "can you submit a PR" test. Not sure if there are more things that needs to be added to the Hyperkitty UI yet, I would love to get some feedback from users who actually use the web ui. > Maybe this weekend I'll go through the tracker and start tagging in > preparation for a GSoC application. Of course we'll decide later if > we have enough mentors etc, but I think this is worth doing anyway > (updating the "easy" bugs, etc) even if we don't apply for GSoC this > year. I do want us to apply this year, will send out an email and see how many mentors do we have available and then decide if we should be applying separately or under PSF. -- thanks, Abhilash Raj (maxking)

6 years, 3 months

[MM3-users] API web hook for subscribe and remove user

by Stephen J. Turnbull

Tibor Molnar writes: > I'm also aware that mailman3 is already query API on localhost and > that's how it's generating the output for system information but if > I was going to configure it for remote where else other than > mailman.cfg do I need to configure this? You don't want to mess with mailman.cfg. Instead you should reverse proxy it, the same way that you do for Postorius. Note that you don't have to open up the whole REST API, you can restrict to very specific endpoints. For example for nginx, the basic scheme is location /REST-API/domains { proxy_pass http://127.0.0.1:8001/3.1/domains; } That particular configuration allows access to domains but not lists. Still,I recommend strong authentication on those locations. ... There are probably ways to get at pretty much everything once you have access to anything. For example, if you can get to a specific list, you can get its subscriber roster, and I think there's a way to pick a specific user, so then you can get their addresses and other subscriptions .... I haven't tried to do that, but I see no good reason to suppose pretty arbitrary path traversal is impossible. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for the REST API endpoints. Steve

3 months

[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 Mark Sapiro

On 4/25/23 3:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py That script will only delete Django users and optionally the Mailman user corresponding to the deleted Django user. I think the OP wants to delete Mailman users that are not members of any lists even if there is no corresponding Django user. That script won't do that. Mailman Users can be deleted from the Postorius Users view, but it's a one at a time process, and there's no indication that the User has memberships unless you first go to `Manage` to check. I will modify the script to enable deleting Mailman users with no memberships even if they aren't Django users and post here when it's done. -- 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: Solved Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > 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...) It would be much better to identify the problem files/directories and adjust their ownership. It is possible that running stuff as root in the past left things owned by root causing the issue. > > 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. Do you have `COMPRESS_ENABLED = True` in your settings? If that's not the issue, it may be in the settings for COMPRESS_PRECOMPILERS -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

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

by Stephen J. Turnbull

Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

3 years, 3 months

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

by Stephen J. Turnbull

Mark writes: > as I kept getting an error when starting:� > > #django-admin shell > >>> from hyperkitty.models.mailinglist import MailingList > ... > django.core.exceptions.ImproperlyConfigured ... This suggests to me that you have multiple versions of Python and/or Django installed. This is an advantage of using a venv -- once activated, you are much more likely to get a well-defined, consistent set of utilities and libraries. By the way, does that # prompt mean you are logged in as root while you're working with Mailman? That is inadvisable, as if you change anything there is a chance that root will be the owner of the file, and the list user will not be able to work with it. Also, if you have mailman-web installed, I recommend using that rather than django-admin or python3 manage.py. Each Django application may have its own copy of django-admin (not usually, but I've seen it happen) and definitely will have its own copy of manage.py. mailman-web knows how to work with both HyperKitty and Postorius without getting confused about that. > 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? If all you're doing is querying the database, it doesn't really matter how you do this. If you get the right copies of python3, django-admin, and manage-py it's all just going to work. It doesn't matter which utility you start with, it all ends up going through the same Django modules in the end. The process of search index construction is both CPU and wall-clock time intensive. For this reason, the cron jobs that do regular index updating (I think once an hour?) are separate from the utility that constructs the index in the first place when you have existing archives (either migrated from another MLM such as Mailman 2, or if you're upgrading to better archive software). Is it possible that you have most of a bunch of migrated archives indexed because the migration process did it, but that the periodic update process (like cron jobs, but actually run by the Django queue task manager IIRC) is not running, so no new posts are being archived? That fits the symptoms you described so far (that I recall). Steve

1 year, 6 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > We're really working on getting a consistent, workable installation > story and even getting some packaged solutions. I know we're not yet > there, but we're here to help when people run into problems. The site now works, but not the / url for the site. I get this error in the mailman-web.log (with a very long stacktrace before it) NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. 'hyperkitty.views.index.index' is not a valid view function or pattern name. I think that would correspond to this line in urls.py url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), but this corresponds exactly to what the example config says and I know of no other name for hyperkitty. Probably it is dependent upon understanding the url dispatching in Django but that takes some time to read up on. The interesting thing is that /archives works so it is just this redirect that has problems. I can probably get apache to do the redirect instead but that is not the most elegant solution. 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. cheers // David

8 years

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

by Dmitry Makovey

On 09/18/2018 09:22 AM, Abhilash Raj wrote: >> 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. > > Ah, why not take a database dump? There are a few specific tables > that you can dump to get everything? > > We don't have a way to do that because we do not actually do not > handle auth ourselves, but instead delegate it to allauth library. > You may have to dig into internals of that to be able to > fetch/restore users/passwords. Thanks for picking up the thread, Abhilash. Since we're trying to get solution that would allow us to dump/restore members/users of specific mailing list etc. we need a bit more "precise" method of extracting user info. We also suspect our DB could be corrupt (we have multiple address entries per member, of which 1 would have proper address and the rest are with empty fields, what's more the ones referenced from other tables are mainly those with empty fields) thus would like to dump "clean" objects and refresh DB rather than copy corruption from DB to DB. -- Sr System and DevOps Engineer SoM IRT

6 years, 7 months

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

by Abhilash Raj

On 10/30/23 20:58, Stephen J. Turnbull wrote: > Jered Floyd writes: > > > I've noticed the django-allauth ecosystem seems to be somewhat > > prone to breaking changes. I'm sure this discussion has happened > > before, but it may be worth pinning "known good" dependency > > versions for django-mailman > > That's a double-edged sword, of course, because you will not get > security upgrades etc either. I agree, but past few days I've been thinking if we should do _something_ about it so that after a while 'pip install' doesn't just start failing for folks forcing us to do another release to pin to a version that we support. In the past, we've had to do that a couple of times for various packages and maybe it doesn't make sense for to pin to a very specific version, but maybe we can provide a requirements.txt with "~=" compatible release requirements so it doesn't stop newer bugfix/security releases from being installed. There will still be issues with packages that don't follow semver or unknown bugs (which was the case IIUC in allauth) that creep up, but it can still prevent us from intentional compat changes made by bumping major version. Thoughts? -- thanks, Abhilash Raj (maxking)

1 year, 5 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, I checked the database; nothing there. Note that there are only 3x entries and only one is list:member:regular:header (my test), so just nothing of interest. The URL works and produces the proper template information. I finally did a find/grep in the mailman tree and found a match for this errant string. It is under the cache folder. This corresponds to the cache_dir value. I could wipe the file out, but what is the proper way of doing so and should they be cleaned out via a schedule? These don’t appear to be web related, as far as I can tell. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Friday, February 7, 2025 at 10:37 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/7/25 10:08, Lieuallen, Thomas Otis via Mailman-users wrote: > > I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. What do you get from the following database queries? SELECT * FROM template WHERE name = 'list:member:regular:header'; SELECT * FROM postorius_emailtemplate WHERE name = 'list:member:regular:header'; Depending on your installation, these tables may be in separate databases, i.e., template table in mailman db and postorius_emailtemplate in mailmanweb db. And what do you get if you go to the uri in the result(s) from the first query? The context in the first results and maybe the second results should also be a clue. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

2 months, 2 weeks

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

by Jens Günther

Thank you for your questions. I hope I can give you the needed answers on what we try to do :-) - We do have a Wordpress-Site for our association set up. - There we put a html-Snippet for the visitors to be able to subscribe for a mailing list (newsletter). - This snippet has been with Mailman2 (2.1.23): <form method="POST" action="https://$domain/mailman/subscribe/$short_listname"> <input name="email" value="" type="text"><br> <input name="email-button" value="Subscribe" type="submit"> </form> We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): <form method="POST" action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> <input name="email" value="" type="text"><br> <input name="email-button" value="Anmelden" type="submit"> </form> When I now enter a mailaddress, the quoted error occurs. Checking another answer directly to me, there seems to be another hint :-) > I believe you are attempting to use the MM Core API via http GET/POST, rather than via Postorius? That you have tried and get the CSRF error reported? > > Typically this is because you need to add a token to the request to indicate to the MM Core that your request isn't a forgery. Typically this token is requested from Core and then presented with subsequent requests. Have you tried this? > Therefor it is needed to send also a token!? Or use another URL, not postorius in order to subscribe!? How can I submit such a token? Still wondering if there is something sorresponding to this documentation!? If not, I'm also willing to write some lateron, if somebody could lead me the way on how to achieve this :-) https://wiki.list.org/DOC/4.33%20How%20do%20I%20put%20a%20subscribe%20form%… Thanks already a lot! Am 21.06.21 um 17:23 schrieb Stephen J. Turnbull: > Jens Günther writes: > > > (forbidden 403 - CSRF-verification failed. Request aborted.) > > I think you need to tell us more about what you're trying to do (the > obvious way to implement a "website subscribe form" is "run Postorius" > which should just work), the configuration you now have, and exactly > what actions you take in the browser to get this response. > > It would also be helpful to tell us what operating system(s) you're > using and their versions, and the versions of Mailman 2 and 3. > > Steve >

3 years, 10 months

[MM3-users] Re: list admin via email

by Mark Sapiro

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

3 years, 5 months

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Mark Dadgar

On Jul 1, 2022, at 6:50 AM, Andy Smith <andy(a)strugglers.net> wrote: > > On Fri, Jul 01, 2022 at 08:40:23AM +0000, Andy Smith wrote: >> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >> 770203 www-data 20 0 4516756 3.4g 1.6g R 99.7 43.5 12:08.00 python3 /usr/share/mailman3-web/manage.py runjo+ > > This has been going for nearly 6 hours now at 100% CPU and I've no > idea if it's ever going to finish. If I strace it, it is doing > *something*, albeit very slowly. I can't see what it needs the 100% > CPU for. > > Output from 10 minutes or so of: > > $ sudo strace --output='|tee strace.txt' -tp 770203 > > is at: > > http://sprunge.us/RCGLmv > > It's only 145k and doesn't seem to do much. An occasional > open,seek,read,close… > > Any good way to find out what it's spending its CPU time on? "top" > says it is 100% "user" so I think it's something the python code is > doing, not anything inside the kernel. What indexer are you using? If it’s whoosh, this is wholly expected. Switch to xapian. You’ll thank me. There’s good implementation details in this list archive. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 years, 9 months

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

by Roland Giesler

On 2024/08/05 12:44, Roland Giesler via Mailman-users wrote: > > I do now have the lmtp runner on port 8024. > > # netstat -tunap | grep 8024 > tcp 0 0 192.168.161.103:8024 0.0.0.0:* LISTEN > 46730/python3 > > In mailman.cfg I set it to listen on the LAN address instead of > 172.0.0.1, since I'm expecting mails from my external MTA server. > > In the logs of the MTA I see this however: warning: do not list domain > fast.za.net in BOTH virtual_mailbox_domains and relay_domains > > Mailman creates these entries, but postfix doesn't like it. I don't > see any mail delivered to the mailman yet. Is this the problem? > > I have come to the conclusion that without substantially hacking power-mail-in-a-box to provide the ability to facility forwarding incoming emails to a list (or other) server, mailman3 cannot be used with it as external MTA. So I have removed my changes and have done "dpkg-reconfigure postfix" on the mailman3 machine to start with a functional postfix server. Thanks to all that assisted me in this quest. I may revisit this at some future date, since I think Power-MiaB is a excellent service to use for an internet mail server and provides a whole lot of advantages to a mailing list server, but for now, Postfix properly configured manually will have to do.

8 months, 2 weeks

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

by Mark Sapiro

On 12/27/19 6:54 AM, brunol(a)agro.uba.ar wrote: >> What do you mean by constantly appearing? Do you mean endlessly > repeating or that they just repeat a number of times equal to the number > of expected recipients of the post? > > Sorry, I meant endlessly repeating. > > This is a piece from debug after sending an email to the list from a recipient that does not need moderation: > > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de264a8> > Dec 27 11:41:10 2019 (11468) [BounceRunner] starting oneloop > Dec 27 11:41:10 2019 (11468) [BounceRunner] ending oneloop: 0 > Dec 27 11:41:10 2019 (11473) Cannot connect to SMTP server 127.0.0.1 on port 25 This message is logged only once, but the issue occurs every time. deliver is getting a socket.error exception on its attempt to connect to the MTA. Thus, sending of this message fails and the message is requeued and the process repeats. Is an MTA listening on 127.0.0.1 on port 25? The only question is if we can't send this mail, how can we send the 'held for moderation' notices?. These are sent the same way. > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.0510046+6fe6039c1b0b65672aade3bfced1aca2fe8afa16 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26e10> > Dec 27 11:41:10 2019 (11470) [IncomingRunner] starting oneloop > Dec 27 11:41:10 2019 (11470) [IncomingRunner] ending oneloop: 0 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26f28> > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.6512213+13fe7854257bb1a494f797f480cb10733bd440ac > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3dd44390> > Dec 27 11:41:10 2019 (11469) [CommandRunner] starting oneloop > Dec 27 11:41:10 2019 (11469) [CommandRunner] ending oneloop: 0 > > This is endlessly repeating with different filebase > _______________________________________________ > 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/ > -- 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: Memory footprint

by Barry Warsaw

On Apr 10, 2017, at 11:25 PM, David Krantz wrote: >Now running mailman 3 I am a bit surprised that the memory footprint >is so large. I count to 13 processes These correspond to the runners, most of which are long running processes that sleep for a while, then wake up and dequeue messages for handling. We model the REST API and LMTP servers as runners as well, but they are technically different since both listen on ports for connections. There's also a master process that controls the runner subprocesses. This architecture is some of the oldest and most stable bits of Mailman, and while the details have changed, the essential nature of these processes are largely inherited from Mailman 2. Given the technology at the time, it was the best way of doing things. It's probably still the most generic way of doing it, since they don't rely on much more than standard POSIX semantics, so they run on just about any POSIX-compatible system right out of the box. I can imagine different ways of doing it. For example, systemd socket activation on OSes that support that for the REST and LMTP servers. And maybe use inotify in the master watcher to spawn queue processing runners on demand. These would all be interesting things to explore, although they may not be universally appropriate (i.e. not all *nix systems supported by Mailman run systemd, nor support inotify). Cheers, -Barry

8 years

[MM3-users] Re: Pck files stuck in out queue

by Mark Sapiro

On 2/7/25 10:08, Lieuallen, Thomas Otis via Mailman-users wrote: > > I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. What do you get from the following database queries? SELECT * FROM template WHERE name = 'list:member:regular:header'; SELECT * FROM postorius_emailtemplate WHERE name = 'list:member:regular:header'; Depending on your installation, these tables may be in separate databases, i.e., template table in mailman db and postorius_emailtemplate in mailmanweb db. And what do you get if you go to the uri in the result(s) from the first query? The context in the first results and maybe the second results should also be a clue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 2 weeks

[MM3-users] New MM3 plugin: mailman_sieve

by Дилян Палаузов

Hello, I have published a new Mailman 3 plugin at https://mail.aegee.org/cgit/mailman_sieve/tree/ . It generates for each mailing list a Sieve script. When the Sieve script is evaluated during the SMTP dialog, it would reject some emails, which otherwise would be bounced by Mailman. Less bounces means less backscatters and better IP reputation. For the record, I do the evaluation of the Sieve scripts during the SMTP dialog with https://mail.aegee.org/cgit/aegee-milter . Since the latter is not documented yet, you cannot use it. The mailman_sieve plugin is not useful, unless you have software to evaluate the Sieve Scripts during the SMTP dialog. This is a very first version, which does what it is supposed to do. Some optimizations are possible, like not including the subscriber addresses in the Sieve scripts for announce-only mailing lists. I am not good at writing setuptools configuration. Neither do I understand the mailman system very good right now, creating possibly shorter scripts. But the plugin is there to keep by IP reputation good! See https://mail.aegee.org/cgit/mailman_sieve/tree/README.md . My reading of the mm3 source code is that there is no event triggered, when the mailing list configuration changes, like adding a new moderator, or switching the announce-only status. In the lack of such event triggers, the Sieve scripts are not updated. When the code improves, the plugin could be published in PyPi or in mailman/contrib . Greetings Дилян

3 years, 1 month

[MM3-users] Re: Problems after update to mailman 3.3.7

by Guillermo Hernandez (Oldno7)

El 6/12/22 a las 16:34, Danil Smirnov escribió: > On Tue, Dec 6, 2022 at 5:12 PM Guillermo Hernandez (Oldno7) via > Mailman-users<mailman-users(a)mailman3.org> wrote: > >> Too late for that... Doy you know what components could I downgrade to >> avoid this? SQLAlchemy? Which versions of which packages could I >> downgrade to work prpoerly? >> > I suppose you can downgrade the mailman package to version 3.3.6 which > should also downgrade SQLAlchemy to the 1.3.x version. > (However I haven't tested this path by myself, so please do a backup first.) I was doing that myself when I received your message. Yes, it worked. This morning (I'm in Spain) I tried to do that, but all the fuss in my head didn't help much. Now it's working again in 3.3.6 and the lists beyond the 10th are reachable. Thanks a lot for your help. > > Danil > _______________________________________________ > 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 toguillermo(a)querysoft.es > -- ___________________________________________ 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, 4 months

[MM3-users] rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid

by Stephen J. Turnbull

Kyriakos Terzopoulos writes: > Some research showed me that I needed a rDNS entry in my > server. I'm on a Hetzner cloud VM so I used the Hetzner console to > change the rDNS entry from: > > static.XXX.XXX.XXX.XXX.clients.your-server.de Don't do that. Aside from inducing the 127.0.0.1 problem you experience, some recipients insist on a reverse lookup that "round-trips", so that if you look up the HELO name, and then look up the IP returned, you get the HELO name back. > Oct 24 14:17:47 2023 (3759611) > <169814622178.3759638.4589434779084932533@localhost> *response exception: > (550, b'Helo name contains an IP address (HELO was [127.0.0.1]) and not is > valid'*, 'testlist-bounces+myusername=myproject.eu(a)myproject.eu') I don't understand why you get the loopback IP address in HELO. Maybe somebody else can explain. > The weird thing is that when I do a mailman-web sendtestemail this > email is sent successfully. That's not entirely surprising. When you send mail via a Mailman list a lot of processing gets done and it passess through three separate processes that are basically doing Internet mail: the incoming MTA, Mailman, and the outgoing MTA. mailman-web sendtestemail there's only one Internet-capable agent, which is the outgoing MTA. Steve

1 year, 5 months

[MM3-users] Re: Mailman 3 localization

by Daniel

FYI: I did translate some strings a while ago. Have a look https://gitlab.com/dadosch/mailman3-german-translation-foo The reason I didn't made a PR or similar was, that I didn't know where :D Liebe Grüße, Daniel Am 02.07.2018 um 10:50 schrieb Alexander Klotz: > >> This is managed entirely through Launchpad/Ubuntu. Nothing has been >> contributed back to upstream, and nobody has volunteered to do the >> work of pulling those files into our source tree and maintaining them >> as they are updated (there is a lot of churn in translations; keeping >> them in synch with release code is quite labor intensive). >> >> I would assume you can drop the .po file(s) into >> mailman/src/mailman/messages/ru/LC_MESSAGE/ and the build and install >> process will do the right thing. > > > We would like to contribute further german translations, since there are > still some parts missing, e.g. in the postorious interface. Would > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > be the right place to do so, so that everybody could use our translations? > > If there are other areas in which you could use our help, please let us > know. > > Regards, > Alex > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 9 months

[MM3-users] Re: There are currently no mailing lists!?

by Mark Sapiro

On 7/22/24 11:05, Christian via Mailman-users wrote: > I recently upgraded Debian 10 'buster' and when I logged in to Postorius in > the browser I got the ' Mailman REST API not available. Please start Mailman > core' message. So I started it up from the command line doing 'sudo -u > mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded > > Starting Mailman's master runner > Generating MTA alias maps > mailman@lists: > > Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists' > in my browser I get the message ' There are currently no mailing lists.' > Meanwhile their archives exist. Are the lists actually gone or ? I suspect the lists are not gone. I suspect mailman core is not using the correct database. I also note you started mailman core with sudo -u mailman /opt/mailman/mm/venv/bin/mailman start -f Are you using the Debian packages or did you install Mailman following https://docs.mailman3.org/en/latest/install/virtualenv.html Assuming the latter, what do the following show? sudo -u mailman /opt/mailman/mm/venv/bin/mailman lists sudo -u mailman /opt/mailman/mm/venv/bin/mailman info In particular does `mailman info` report the correct path to mailman.cfg and the appropriate database? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Now I do have a running instance, too. Seems my error was to do all of the installation via ansible from the start and I wouldn't seen many things failing: - missing wheel - missing gcc The link to the virtualenv user guide seems to be broken. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 2 months

[MM3-users] ARC

by Stephen J. Turnbull

David Krantz writes: > It might be that no support really is needed in mailman so that just > milters in sendmail, postfix etc. might do the trick. MTA features are the way to go in principle. First, Mailman can't check SPF because it doesn't have access to the connection. Second, the MTA needs access to private keys for signing DKIM and so on. Mailman 3 is definitely insecure against attacks from localhost. Third, MTAs need to access DNS; Mailman shouldn't need to (this is necessary for all of the various protocols to get public keys). I don't know how big the problem really is from experience, but I can say that the representatives of the big sites at IETF worry a lot about the burden of these checks on the DNS. Finally, in some domains there are multiple Mailman administrators behind one MTA, and the Mailman admins can't manipulate DNS or access private keys. There have been a couple of ARC modules contributed; there's a lot of code to review, and probably still some configuration magic to be added to the core given that I don't think it should default on. Maybe the thing to do is release an add-on for the people who have access to the configuration files of their installation (the actual configuration interface is adding a rule to the chains to check ARC stuff, and a handler to the pipeline to do the signing). Steve

6 years, 7 months

[MM3-users] Re: MM3 to MM3 migration

by David Newman

On 1/31/23 2:01 PM, Mark Sapiro wrote: > On 1/31/23 13:34, David Newman wrote: >> >> Is this really as simple as building the new server, creating the >> same lists on the new server, and rsync’ing the archives from the old >> server? If not, how to do the migration? > > > If you want to mirror the entire installation, you can dump the > databases off the old server and import them to the new server. > Depending on the installation, everything may be in one database or > there may be separate ones for mailman core and mailman web. This is a > little tricky because some of the tables have to do with Django stuff. > > To do only selected lists is much more difficult and there are no > scripts that I am aware of. > > HyperKitty can dump a list's archive as a mbox which could then be > used as input to hyperkitty_import on the new server to move archives, > but there are no similar scripts to dump list settings, users, > memberships, etc. in a format that can be imported. Thanks for this. Would I need to create the lists first on the new server before restoring databases and running hyperkitty_import? Also, I'm unclear about there not being scripts for settings, users, etc. –– isn't that stuff in the mailman database? Thanks! dn

2 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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? 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

7 years, 8 months

[MM3-users] Re: Docker mailman 3 and upgrading questions

by Abhilash Raj

> On Feb 1, 2022, at 12:26 PM, bob B via Mailman-users <mailman-users(a)mailman3.org> wrote: > > I am running mailman 3 in docker and trying to figure out > -how to upgrade “tags” are the versions, you pull down container images at a version and re-create the containers using those. > -can you back out. > > For example > I installed docker with a git pull > • git clone https://github.com/maxking/docker-mailman The only real thing that this gets you is the docker-compose.yaml file, everything else in the repo is only ever useful if you want to re-build the image. Assuming that your local copy of `docker-compose.yaml` has your settings and password, you want to keep a copy of it before you do a `git pull` and delete changes in it. > > docker images shows > REPOSITORY TAG IMAGE ID CREATED SIZE > maxking/mailman-web 0.3 9ba9d3d7084d 4 months ago 487MB > maxking/mailman-core 0.3 26c920c0094b 4 months ago 178MB > **** database is hosted via external database > > I only installed it a few months ago, am I really on 0.3.0 , I assume I am on 3.0 from 2019 and that is what "git clone https://github.com/maxking/docker-mailman" gets???? Whatever is the “TAG” in the above row is the real version, that’s what you get. Tags can be moving though, so 0.3 represents the 0.3.x at the point of docker pull. All you get from “git clone …” is the “docker-compose.yaml” file, which specifies the version of the container images to pull. Currently, the main branch says 0.4[1]. When you pulled, the value there was probably 0.3. [1]: https://github.com/maxking/docker-mailman/blob/main/docker-compose.yaml#L27 For a fully re-producible copy, keep a copy of the “IMAGE ID” and you should be able to re-create the old setup and back-out from upgrade. Just put the respective image id for core and web images in the docker-compose.yaml under `”image” section. > > looking at the release matrix "https://github.com/maxking/docker-mailman/releases?page=2" It looks like the latest releases are 0.4.1 for core & 0.4.2 for web, > > How do I upgrade, is it a "git pull" or "docker update" command? Here are steps: - Copy the docker-compose.yaml to safe place, that’s the only thing you really need from the git repo. - Bump the “image” to the version you want to upgrade to, for both Core and Web. Note that 0.4.2 release notes mentions only changes in web, but both images are tagged with 0.4.2 during the release. If you are jumping to 0.4.x release, make sure you also follow[2]. [2]: https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release - Run the following commands wherever you have other changes ready: - docker-compose -f docker-compose.yaml down. # Shuts down the current instance. - docker-compose -f doker-compose.yaml rm # Deletes the containers with name mailman-core and mailman-web. - docker-compose up -d # Starts the new container with the new container image. > If something does not work, is there a way to back out? Local state on disk isn’t wiped, but do make sure to backup the database because new releases will try to install the database schema changes, which you’ll need to revert to back out. > > What version should I go to from 0.3? I am thinking it should be v0.3.12 cause that won't break anything? But how do I do that? 0.3.12 would be safe to try before jumping to 0.4.x. Same steps, except the link pointing to upgrade notes for 0.4.x -- thanks, Abhilash Raj (maxking)

3 years, 2 months

[MM3-users] shunt vs. bounce [was: File in mailman3/queue/bounces/]

by Stephen J. Turnbull

Just a note on the difference. The problem itself was fixed. Andreas Barth writes: > Any hint how to get rid of [this file]? 'mailman unshunt' doesn't > do it, it's in queue/bounces and not queue/shunt. A *shunted* post is an *undistributed* post that raised an exception that Mailman doesn't know how to handle usefully, so instead of continuing normal processing it stuffs it into the "dead-end" shunt queue, which is processed by hand, not by Mailman. 'mailman unshunt' tells Mailman that it is "fixed" and ready to continue processing, and moves it back into the normal pipeline to be processed and sent. A *bounced* post has been *sent* already, and the problem is at the receiver, not with the post as Mailman got it. Since it has been sent already, unshunt would do the wrong thing. Also, the bounce runner will do the right thing once it's restarted. In fact, for "stuck files" in any queue except shunt, the first answer is "restart the corresponding runner". It is the presence of a file in the queue directory that triggers processing. If it stays stuck, then I guess you call Ghostbusters (us). I should add this as a FAQ or the docs as "What is shunt?" but it's not obvious to me which is better, and if the docs, where. Comments welcome.

3 years, 4 months

[MM3-users] Trying basic install of mailman3 in docker, but how do you set allowed hosts?

by bob B

I am starting small, My goal is just to get mailman3 running in docker and test the website access via curl from the host, then I will move on from there In the docker instructions it says SERVE_FROM_DOMAIN: The domain name from which Django will be served. To be added to ALLOWED_HOSTS in django settings. Default value is not set. This also replaces Django's default example.com SITE and becomes the default SITE (with SITE_ID=1). But where do I set the ALLOWED_HOSTS I added this to the yaml file - ALLOWED_HOSTS=127.0.0.1 under environments mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - ALLOWED_HOSTS=127.0.0.1 - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - SECRET_KEY=333blah-blah-secret - HYPERKITTY_API_KEY=333someapikey ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: But when I try: [docker-mailman]# curl 127.0.0.1:8000 <h1>Bad Request (400)</h1>[root@bmimailmandr1 docker-mailman]# [root@bmimailmandr1 docker-mailman]# I see this in the logs [docker-mailman]# cat /opt/mailman/web/logs/mailmanweb.log WARNING 2021-07-08 17:40:46,979 1642 django.request Bad Request: / ERROR 2021-07-08 19:20:58,416 1641 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: /

3 years, 9 months

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

by Mark Sapiro

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

2 years, 7 months

[MM3-users] Mailman 3.1 beta coming soon

by Barry Warsaw

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. Here is the Core's 3.1 milestone page: https://gitlab.com/mailman/mailman/milestones/2 If your favorite issue or merge request isn't on that list, please do get in touch. Otherwise it will be deferred to 3.2. I'm also not entirely promising I'll get to all of these; I really want to release 3.1 in 2016 so if we run out of time, it will get deferred. Here's the project-wide list of 3.1 issues: https://gitlab.com/groups/mailman/issues?scope=all&state=opened&utf8=%E2%9C… and merge requests: https://gitlab.com/groups/mailman/merge_requests?scope=all&state=opened&utf… Except that HyperKitty isn't on this list. Please do test whatever you can and let us know how it goes. Cheers, -Barry _______________________________________________ Mailman-Developers mailing list Mailman-Developers(a)python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/mark%40msapiro.n… Security Policy: http://wiki.list.org/x/QIA9

8 years, 4 months

[MM3-users] Re: Changing subscription address

by Stephen J. Turnbull

Thank you for your comments, Allan! Allan Hansen writes: > On 3/15/21, 21:28 , "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >>In the 'Mailman Settings' screen, List-based Preferences' tab, >You may mean the 'Subscriptions' tab. I did mean the 'List-Based Preferences' tab. The 'Subscriptions' tab is non-functional. It's in some sense aesthetically more pleasing than 'List-Based Preferences', but you have to do extra, unnecessary work to get anything done from the 'Subscriptions' tab. It may make sense to just get rid of the current 'Subscriptions' tab and rename 'List-based Preferences' to 'Subscriptions'. The only functionality of 'Subscriptions' over 'List-based Preferences' is that it lists you once for each role and address (member, non-member, moderator, owner) that you have for that list. This is possibly more confusing than helpful for non-owners. Moderators get informed of their role every time they need to do something. And it's possible to be both a member and a non-member of a list, which is pretty confusing. > Under 'User profile for <name>', under the 'E-mail Addresses', add > button to ensure that 'Primary E-mail' is used for all lists. If you define "ensure" strictly, this would be a fair amount of work because it would require overriding the normal "cascade" of preferences, and incidentally a way to turn off that override. I'd rather not make the implementation so complicated. There does need to be a way to revert each option to inherit, and there currently doesn't seem to be one. The 'Preferences' interface I described in the previous post doesn't provide it either. I will think about that. It should be normally unnecessary to use the 'Preferences' interface, because the default subscription should be "use primary address". For people using the current versions of Mailman 3, who are already have a bunch of subscriptions with the same *explicit* address, I think it is good enough. But if there's demand for a "revert all to use primary address" button, that would be easy enough to add. Here's why I think such a button would be unnecessary in future versions of Mailman. What should happen if you subscribe by an address not already known to Mailman without creating an account in Postorius is 1. Mailman registers the address. 2. Mailman creates a User object to "own" that address, and makes that address the primary address for the User. 3. Mailman creates a subscription which links the User (not the address) to the mailing list so that the primary address is used. For addresses already known to Mailman, Mailman should look up the User registered to that address, and if the subscription address is the primary address, set "use primary address" for the subscription. In this scheme, as far as I can see, your user doesn't need to do anything with the account until she wants to change the address. At that point she needs to activate the account: - visit her personal options page in Postorius - request a password reset (she doesn't have one yet, so she can't log in) - click the special link - set a password or link a social media account, and - finally change the address. Note that this is the bare minimum of work for her. She has to prove she can read mail at that address. Anything less, and *anybody* can change her subscriptions. We could omit requiring a new password, but it's not a lot of work once you've got to this point, while the "request, wait for email, click link, do work" dance is pretty annoying. Why make someone do it again next time? This is problematic if she's already lost access to the old address, of course, but in that case you're probably going to have to intervene anyway. I don't think Postorius requires her to do anything else, but if she wants to she can update her profile at that point. I have to check the code, and probably also ask Barry and the other folks who designed the current subscription mechanism in case there's some fatal flaw in the scheme above. But I think that should do what almost all "one address" users want, and it's probably what the majority of people who have multiple addresses and use different ones for different purposes want most of the time, too. Note to self of possible problems: (1) The primary address is where you would send administrative mail to the account holder and that might not be an appropriate address for the default subscription. (2) This is a pretty radical change from the current situation, so it might need to be an option for the list or domain owner. > And, indeed, new subscriptions should default to 'Use Primary.' I agree. I'm astonished that there are situations where they don't, to be quite honest. That's the whole point of having accounts in the first place -- having *one* source of information about the user rather than spreading it out over a bunch of lists. > Is that possible now? It is already the default for someone who subscribes by logging in to Postorius. I assume that it is *not* the default for someone who subscribes by email or mass subscription, otherwise you wouldn't have the problem. > Does a member have to have an account for me to set it up thus for > them? Yes. The primary address is an attribute of the account. Subscriptions can't know anything about a primary address unless there is an account. However, it should be possible to make this default for an account that hasn't been activated yet, such as in a mass subscription. Regards, Steve

4 years, 1 month

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 07:52, Jeremy Stanley wrote: > > Thanks, I'm still doing my best to wrap my brain around how Django > uses database migrations to create sites (seems like a very strange > use of a migration, I'm only accustomed to seeing them applied for > database schema updates). I don't think it does. There are a couple of migrations at django/contrib/sites/migrations, but these are only the initial creation of the model and an update to make the domain field unique. Why do you think it creates sites in this way. > Once I work out how to script site > creation, I'm still not completely finding the explanations I need > for how to map them to domains in Mailman though. > > The Mailman documentation about domains says "Domains are how > Mailman interacts with email host names and web host names" but > doesn't actually go on to say (that I can find anywhere) how it > actually associates them. Mailman core doesn't associate domains with Django sites. Mailman core knows nothing about a web UI. The association between Mailman core domains and Django sites is via Postorius. It doesn't exist in Mailman core. When Postorius sees a new domain from core, it assigns it a web_host based on the current web host accessing Postorius. > I can see in the API docs that a POST to > the domains endpoint will create a new domain with a specific > mail_host FQDN, but there's some association somewhere of that to a > web host (Django site), right? No. The only association is if Postorius is creating the domain in core, vs something else creating it via the REST API, Postorius will assign it a web_host in it's own Domain model, and that web host must be an existing Django site, which is only created via Django. > How is that set or manipulated > through the API? Or is that something which has to be set directly > in Django's data structures instead? Yes, A new site has to be created in Django. Even Postorius doesn't do that. > To recap, on creation of a mailing list server I want to populate it > automatically with multiple lists on different domains and have > dynamic SITE_ID=0 domain guessing performed so that the correct site > name and list filtering is performed depending on which domain name > is used in a URL the client requests. I believe I need to have the > automation perform the following steps: > > 1. Instantiate the Mailman installation and run initial migrations > with SITE_ID=1 in order to avoid the problem mentioned in the docs > about not using SITE_ID=0 until the tables have been populated, then > switch the settings.py to use SITE_ID=0 once done. > > 2. Create the individual sites I need in Django (Mailman web hosts) > by creating and applying database migrations. No. You create the sites via Django, but not by creating and applying database migrations. > 3. Create the individual domains I need in Mailman (Mailman mail > hosts) through its REST API. > > 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond > to what web hosts. Neither Mailman nor Django. It's Postorius which maintains the relationship between Django sites which it calls web_hosts and domains. > As I said, I'm still trying to understand how to make step 2 happen > (Django has a steep learning curve for me), but beyond that I'm > unsure how to do step 4 at all. I can do all of this through the > WebUI of course, and have confirmed that it works as expected when I > do, I'm just trying to work out the automation so that our other > sysadmins don't have to perform these steps by hand the next time we > need to rebuild the server. Step 2. $ django_admin shell ``` >>> from django.contrib.sites.models import Site >>> new_site = Site(id=5, domain='5.example.com', name='display_name') >>> new_site.save() ``` Of course the values are up to you and you can omit the id= to have Django assign the first available.. Once you've done step 2, you need to create a domain in Postorius. Look at the code behind Postorius add new domain. Or you can create the domain in core via REST, but you then have to modify it in Postorius to associate the correct site. -- 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: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Sun, Aug 1, 2021, at 1:52 PM, John Covici wrote: > I am finding some missing documentation in the section on configuring > mailman-web, it refers to a file > https://asynchronous.in/docker-mailman/web/ which does not exist. Try https://asynchronous.in/docker-mailman/web.html Can you point me where you saw the original URL so I can update it? > > > On Sat, 31 Jul 2021 21:21:24 -0400, > John Covici wrote: > > > > OK, thanks a lot -- if anyone here can help with proper config for > > those, that would be great. I do have a web server, but its apache > > rather than mginx and I am not sure how to properly translate. Also, > > doing a separate container for an mta which would just talk to > > mailman would get around the sendmail situation I have, although > > there may be a decent way to do that as well. I guess the hard part > > is to tie the multiple containers together. > > > > > > On Sat, 31 Jul 2021 17:56:15 -0400, > > Abhilash Raj wrote: > > > > > > > > > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > > > I have a couple of questions about the container, if its OK. > > > > > > Sure it is :) > > > > > > > > > > > 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? > > > > > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > > > > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > > > > > 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? > > > > > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > > > > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > > > > > > > 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 > > > > _______________________________________________ > > > > 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) > > > > > > > -- > > 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 > > _______________________________________________ > > 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 > -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users] Re: Templates do not work

by Eggert Ehmke

It seems my apache vhost settings are messed up. To access the postorius page, I have to use URLs like this: https://lists.[1]tld_/mailman3/mailman3/lists/_ That does not look right, and maybe is the cause of my problem. There are very few guides to set up apache virtual hosts with mailman virtualenv installation. Any hint? Am Donnerstag, 28. April 2022, 19:02:42 CEST schrieb Mark Sapiro: > On 4/28/22 02:50, Eggert Ehmke wrote: > > I created some templates in Postorius to get > > personalized notifications when there are > > moderator requests. The notifications I get seem to > > be the standard texts. When I look into mailman/ > > mm/var/templates > > the directory is empty. Nevertheless, the templates I > > create in Postorius seem to be stored (where?), they > > just do not work. > > As Steve said the templates are stored in the database. > > I suspect the issue is and incorrect value for > `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to > construct the URI to retrieve the template. The URI is stored in the > `template` table in the database. It is normally just `http(s)://host.name/` > > If this is the issue, after correcting the setting and restarting the > web service, you will need to delete and re-enter the template in > Postorius to correct the `template` table entry. -------- [1] https://lists.ftv-spandau.de/mailman3/mailman3/lists/

2 years, 11 months

[MM3-users] Re: Member Issue Discovered

by Apollinaris Schöll

> On Oct 27, 2020, at 11:07 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > But it's not just the architecture. Even the requirements are > controversial. I'm on record that it might be a good idea to remove > the User (ie, the profile of PII in the database) when the last > subscription is deleted, but should that be automatic unless > inhibited, should it be an option offered but default to "keep", > should it be an operation done only on specific request? In any of > those options, since this is a major deletion of presumed unneeded but > in some cases valuable data, we should provide a convenient but > cautious UI. Should there be a temporary backup of the data in case > the user changes their mind? Is that GDPR conformant? Maybe the user > could download their profile for later upload? Maybe that could be > portable across Mailman 3 sites, with some kind of semi-automated > merge UI? > Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” This is not true and needs to be done. This is the promise here. Otherwise it should say “some data is removed but if you really want to remove all data you need to track down the person who can do that by removing you from the db" As a subscriber to several MM2 lists, forums, social networks, …. My expectation is to have the option to delete all my personal user data if I wish to do so. As a admin for a MM3 list I need to have the option to delete the data I have created. I can subscribe someone. Subscribe is also creating a record in a db. If I unsubscribe someone I want to be able to delete that record in the db. Once a user create an account and/or has other active subscriptions I don’t expect to have this power. User or some other list admin has taken responsibility to (co)own this record. > How about the user's archived posts? How about quotations of the user > in *other's* archived posts? Just designing this is not easy, but > because it might involve changes in the architecture, we do need to > design in advance. This is not the kind of change where "move fast, > lose user data, and break everything" makes sense. User created these posts and released them to be sent to all other subscribers. If the list is public then that means to everyone on the internet who happens to find the archives. Archives could be copied and mirrored and there is no way to erase history. Having an UI to delete archived posts is good to have. But it’s unreasonable for a user to expect that they can go back in time and undo what they did. If a admin is really concerned they need to have every user to sign a contract. Even turning off archives will not prevent other subscribers to keep old posts and repost/reply/archive in some other ways. It’s same for any forum or social networks like Facebook, google, next-door, twitter …. They send out emails with data provided by others. While a user can delete their account the emails are no longer under control of the platform. > > I'm not saying we can't do it, but we also have our priorities, and > limitations. Also, I don't think we can, let alone should, do that > design ourselves. Even if it's not reasonable for you to contribute > code or money, we do need to know the community's requirements, and > because it's often pretty fuzzy stuff, I think it's reasonable to ask > *why* a feature is needed -- we may be able to negotiate a change > that's easier to code or less fragile in operation if we know what the > underlying need is. So members of this list can help a lot by (1) > answering the questions I asked above, (2) coming up with more > questions (and answering them), and (3) turning the whole thread into > concise requests for enhancement on the tracker. > Fully agree, as a developer it’s impossible to know how product will be used. Offering a UI to control settings as much as possible to a user/admin is important > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

[MM3-users] Re: Mailman automatic accept notification

by Stephen J. Turnbull

Dear Tambet Paide, We understand what is happening. We do not know why it is happening because (1) with proper configuration of Mailman and the MTA this should not happen and (2) you are the only site reporting this problem. First, your expectation is *incorrect* for the purposes for which Mailman is intended (discussion and announcement lists). The DSN should *not* go to the original sender. It is not the original sender's "fault" that a deleted mailbox is subscribed to the list, nor can they do anything about that, except to stop sending mail to the list. Only the list owner (or site administrator) can unsubscribe or set no-mail on that mailbox. Therefore the DSN is forwarded to the list owner's address. I can imagine applications of bulk mailing software where you might want non-list-owner senders informed about delivery failures, but we do not support them with Mailman, and this particular feature will not change because it's the right thing for *all* existing Mailman users (except possibly you). If you want to use Mailman and have an application where the DSN *should* go to the original sender, we will be happy to discuss it and treat it as a request for enhancement, to provide it as an option. But I can't imagine a situation where the DSN should go *only* to the original sender where that sender can't be the list owner. All the situations I can think of can be handled with the existing software and an auxiliary list for "senders with need to know about DSNs". If your list is in fact a traditional discussion or announcement list, then the fact that a Delivery Status Notification (DSN) appears to be delivered through the mailing list to subscribers indicates that there is a problem with your Mailman configuration or your MTA configuration. Without precise and accurate information about your configurations we *cannot* help you. I suspect that your list owner is set to the mailing list posting address. If you do that, delivery of DSNs to all subscribers is exactly the effect that you *should* get, because the list owner is the agency that is expected to deal with problems with the list, and therefore *must* get these notifications. Regards, Tambet P via Mailman-users writes: > The link does not work correctly here is the correct link: https://ibb.co/NY15mDt > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

4 years, 4 months

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

The main point here is not "poor Mailman developers", it's that we need input from users (subscribers too, although list owners are probably most important) about how to design these features. Unfortunately I don't have time or energy to fix the tone which is a little self-pitying, so please read with that main point in mind -- I'm posting because I really want to know what people need, and want. And the bit about "re-using Mailman 2 scripts" too. I'm not sure how practical it is given the architecture changes, but we'll definitely take a look at requests. Alex Schuilenburg via Mailman-users writes: > Yes, this is social media territory, but with the EU/UK DPA (data > protection act) and record fines being issued, Sure. It's also a pretty big ask of the Mailman developers. As you are now aware, the architecture of the application is not well-suited to this. If you're worried about paying fines, maybe a contribution of a fraction of the average fine would be good insurance? :-) But it's not just the architecture. Even the requirements are controversial. I'm on record that it might be a good idea to remove the User (ie, the profile of PII in the database) when the last subscription is deleted, but should that be automatic unless inhibited, should it be an option offered but default to "keep", should it be an operation done only on specific request? In any of those options, since this is a major deletion of presumed unneeded but in some cases valuable data, we should provide a convenient but cautious UI. Should there be a temporary backup of the data in case the user changes their mind? Is that GDPR conformant? Maybe the user could download their profile for later upload? Maybe that could be portable across Mailman 3 sites, with some kind of semi-automated merge UI? How about the user's archived posts? How about quotations of the user in *other's* archived posts? Just designing this is not easy, but because it might involve changes in the architecture, we do need to design in advance. This is not the kind of change where "move fast, lose user data, and break everything" makes sense. I'm not saying we can't do it, but we also have our priorities, and limitations. Also, I don't think we can, let alone should, do that design ourselves. Even if it's not reasonable for you to contribute code or money, we do need to know the community's requirements, and because it's often pretty fuzzy stuff, I think it's reasonable to ask *why* a feature is needed -- we may be able to negotiate a change that's easier to code or less fragile in operation if we know what the underlying need is. So members of this list can help a lot by (1) answering the questions I asked above, (2) coming up with more questions (and answering them), and (3) turning the whole thread into concise requests for enhancement on the tracker. > Yes, it would be nice to re-use some of those old mm2 scripts built > up over the years on mm3. Feel free to post the scripts you want to reuse on the tracker, in request-for-enhancement issues. Without an accurate idea of what you want to do, specifically the data the scripts want to access, we'd have to reproduce the whole Mailman 2 API/UI. Some of that would be extremely tedious, such as anything that manipulates list config pickles -- they don't exist any more. But other things might be fairly easy.

4 years, 5 months

[MM3-users] Re: Upgrade-path from Ubuntu18LTS to recent mailman release

by Stefan Bauer

Thank you all for your time. I managed to do a fresh installation. The MM documentation is very good. As i only use sqlite, i will give it a try to just copy the database files. Stefan Am Do., 5. Mai 2022 um 11:11 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > thanks alot. That looks promising. Can we just copy the current > > mailman3-database and take the configurations or is there a specific > > migration path we have to follow? > > Much of the documentation on mailman.readthedocs.io discusses > migrations and upgrades. You should read those for general hints. > > The distro Mailman to venv Mailman case is more discussed here on the > mailing list than in those documents. I don't have pointers to those > threads or the time to look offhand, maybe over the next few weeks as > I work on our GSoC project. If you do find any, and would post them > here, I'll make sure they get into the docs. > > The main thing is to backup Mailman configs (probably in /etc/mailman > or /etc/mailman3) and the backend database (core, Postorius, possibly > HyperKitty depending on configuration, and the django-mailman auth > stuff) before trying to migrate. (For the backend database I would > just dump the RDBMS unless non-Mailman content is really huge.) The > nature of the virtualenv install is such that it *will not* overwrite > any of the distro files at all (as long as you put it in /usr/local or > /opt). However, you want to preserve the configs and database and > reuse them, so those *must* be backed up. > > > We are currently running 3.1.1-9 (Ubuntu 18). > > Ubuntu 18 is probably old enough that you need to be careful about > MySQL and its derivatives. The specific problems are (1) you need to > specify the right UTF-8 variant for the coding system, and (2) more > recent versions of Mailman tend to make certain records overflow. > > If you're using PostgreSQL these caveats *do not* apply. If you're > using sqlite3 (I doubt it, but just for completeness) you should > change to PostgreSQL or MySQL. If you're using something else (same > caveat), I can't really say. Probably somebody out there is using > Oracle or whatever, but we don't know about that. :-) > > Steve > >

2 years, 11 months

[MM3-users] Fwd: HOWTO: Mailman 3 Equivalent of "Accept: @all"

by Abhilash Raj

Please use the mailman-users(a)mailman3.org list for questions related to Mailman 3 usage. Abhilash ----- Original message ----- From: "hmills(a)t-online.de" <hmills(a)t-online.de> To: "mailman-users-owner(a)mailman3.org" <mailman-users-owner(a)mailman3.org> Subject: HOWTO: Mailman 3 Equivalent of "Accept: @all" Date: Tuesday, July 21, 2020 9:31 AM Greetings, I have a question concerning usage of mailman3 (not an installation issue). Previously we used mailman2 & changed to mailman3 some months ago. "We" being a sports club located in Northern Germany. I guess I'm the "List Administrator" & "Moderator" - a colleague is the "Site Administrator". We use a number of maillists - one for "all" members and further ones e.g. for "instructors", "juniors" and so on. With mailman 2 it was possible to add "Accept: @all" in the configuration of the smaller maillists such as "instructors" thus enabling any club member to mail to the "instructors" but mails amongst the "instructors" remained just with themselves. Up to now we cannot do this with mailman3 which means I have to frequently approve mails (with the associated delay). I'm told (but not "how to do it") that with the recent update to mailman3 which our Site Administrator has installed it should be possible to do the "Accept: @all" mechanism - or similar. Could some kind soul please simply explain how I can achieve this? Best Wishes Howard -- thanks, Abhilash Raj (maxking)

4 years, 9 months

[MM3-users] Re: Scheduled tasks

by Mark Sapiro

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

6 years, 10 months

[MM3-users] Re: Mailing Lists

by Mark Sapiro

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

3 years, 4 months

Search results for query "dO"