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

[MM3-users] Unable to ban users via mailman-shell

by Stephen J. Turnbull

Mihai Moldovan writes: > # mailman-wrapper shell > Welcome to the GNU Mailman shell > > >>> from mailman.testing.documentation import dump_json > >>> from mailman.interfaces.mailinglist import IMailingList > >>> from zope.component import getUtility > >>> list_manager = getUtility(IListManager) > >>> mlist = list_manager.get('x2go-commits(a)lists.x2go.org') > >>> bans = IBanManager(mlist) > >>> new_bans = ["really", "long", "list", "with", "addresses", "I'd", "like", > "to", "ban"] > >>> for new_ban in new_bans: > ... bans.ban(new_ban) > ... > >>> for ban in bans: > ... print('{0}: {1}'.format(ban.list_id,ban.email)) > ... > [long list of bans] > >>> exit() You appear to have missed this line from 'mailman shell's banner: Exit with ctrl+D does an implicit commit() but exit() does not. > I don't even see any calls to the REST API for each bans.ban() > call. Should I see those? No. Mailman core does not call the REST API for anything that I know of. It implements the API so that processes on a different node can access Mailman's resources, but the 'mailman' utility is intentionally restricted to the same node. > Or is bans.ban() directly modifying the database? Yes, but inside a transaction that must be committed. > If that is the case (I'm using sqlite3, nothing fancy), why > doesn't it stick? Do I have to commit changes somehow? Of course somebody has to commit the transaction, and Ctrl-D to exit will do that for you. But there also has to be a way to back out without committing, and we use the more verbose exit() (without preceding commit()) for that. You might think it should require more effort to do possibly destructive changes than to abort safely, but we've found by experience that the majority of usage of 'shell' and 'withlist' is quite simple, and reports of problems with undesired commits are just about nonexistent. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 week, 3 days

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

by ryan.anderson.4＠go.mnstate.edu

Hello, We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings. The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything. Any ideas on how we can prevent these characters from being changed?

3 years, 1 month

[MM3-users] Question to add "alias" address in list by group

by Stephen J. Turnbull

Pierre Malard via Mailman-users writes: > We must add some (a lot) alias address for members and I don’t find > any indications on doc to do that with « mailman » command. I have no idea what you mean by an "alias address" that can be added for many members simultaneously. There is no concept of "alias" in Mailman, and almost certainly no special command for this. The general way to add a lot of addresses for a single list is the mass add command in Postorius's users tab, or an equivalent script using mailmanclient. If you need to do this at the user level (rather than the subscription level), you will need to write a script for it, and also to update subscriptions if that is what you have in mind. Steve

2 years, 11 months

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

by Mark Sapiro

On 1/6/22 3:25 PM, gordon(a)dickens.com wrote: > > How do I uninstall the Debian version and then reinstall with the venv and web instructions so that all of my mailing lists and configuration data are preserved? I may elect to go that route if I can preserve all of my mailing list and data and you think that would be a quicker route to a solution. Is there a simple way to do this? It's probably not "simple", but here's how I would do it. First, follow https://docs.mailman3.org/en/latest/install/virtualenv.html to install Mailman in a virtualenv. You can use `list` as the Mailman user rather than `mailman` if you like. The doc uses Postgreql as the database manager, but you want to use whatever the current DBM is because you will want to use the existing database which is where all the list configuration, membership and archives are. One gotcha here is the instructions tell you to create /etc/mailman3/mailman.cfg and the Debian package already puts its mailman.cfg there. The Debian mailman.cfg may actually be appropriate although it puts things in different places, e.g. /var/lib/mailman3 instead of /opt/mailman/mm/var. The Debian package puts its Django settings in /etc/mailman3/mailman-web.py and the virtualenv doc puts them in /etc/mailman3/settings.py. You need to reconcile the differences keeping in mind that the recommended settings.py imports most settings from the mailman-web project and only contains things you want to change locally. The basic idea is you want the virtualenv install to use the existing databases and /var/lib/mailman3 stuff so you preserve all your existing list stuff. It probably involves several gotchas that might be difficult to resolve if you are less than intimate with the details of a Mailman installation. I actually spun up a small Ubuntu 20.04 droplet and installed the mailman3-full package to see what things looked like, but I destroyed it without examining the contents of some of the files or I might know more. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] How to separate bans for sending emails to lists and subscribing to them

by Nathan Dixon

Hi, Our requirements for using Mailman are that we can have non-members send an email to a list from any domain name, but only people who's email addresses match a list of specific domains should be able to actually subscribe to those lists. I can't seem to find any way of doing this. Any ideas? I have tried using the bans (global and on each list) but these appear to stop all subscriptions and emails being sent to or from a list if the address matches a ban. Having moderated list subscriptions seems to be the only workaround, but this wouldn't be great if we could automate it (we are currently using Listserv which does allow us to do this) Thank you, -- *Nathan Dixon* MEng Senior Software Architect

5 years, 10 months

[MM3-users] Re: Problems with New MM3 Installation

by mm3＠steele.com

I have found work around for the settings issue but continue to have an issue with archiving new messages. New messages are stuck here; mailman3/mm/var/archives/prototype/[listname]@[domain]/new I have added this to my mailman.cfg: [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /usr/local/mailman3/mailman-hyperkitty.cfg And created the "/usr/local/mailman3/mailman-hyperkitty.cfg” as such: base_url: http://localhost/archives/ api_key: [key that matches “MAILMAN_ARCHIVER_KEY” in my settings.py] Some documentation says that the url should be "http://localhost/hyperkitty/ but url generates a page not found error on my setup while the archives are available at the “archives” url. But, now that I think about it, "localhost" doesn't make sense here because I am virtual hosts and "localhost" will probably just connect to the first virtual host rather than the mailmanweb virtual host. Any advice on what do do here?

3 years, 11 months

[MM3-users] [Suspected Spam]Re: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Stephen J. Turnbull

Mark Sapiro writes: > Rob's reply in this thread was garbled due to > <https://gitlab.com/mailman/mailman/issues/616>. The text of the reply > is quoted below. > > On 7/27/19 12:54 AM, Rob Lister wrote: > > > > One thing that does occur to me is that my exim header fudge will > > probably cause the Message-ID header to move around from its original > > position, and if someone is doing hashing or actually validating (gpg > > signing?) the headers haven't been tampered with, then it might > > complain, since although the message-id hasn't changed, it might be in a > > different place in the headers. I don't think this is a problem. GPG or S/MIME signing with any software I know of only signs the message body (or a MIME part). DKIM message signing isn't going to care about the order of fields because DKIM canonicalizes the order (at least for the unique fields) according to the specification in the signature field, and that will be verified on the way in. Of course adding a Message-ID will likely break DKIM for the outgoing post, but Mailman as normally used breaks DKIM anyway. This can be partly mitigated by using ARC (authenticated received chain), which is supported by Google already, and possibly some of the other usual DMARC suspects (Yahoo!, AOL). > > Probably the more correct way to do it is only add a new header if it's > > missing, and if it's there, leave it alone. True, and I think this does it: headers_add = ${if def:h_message-id:{fail}{Message-ID: ... id generator code ...}} If you like that and test it, I would really appreciate feedback so we can update the documentation. One thing *I* would like to add to this recipe is logging. I'd be curious to see how frequently it happens outside of spam and junior high school hackers using netcat as their MUA. I don't see how to do this in Exim, though. Another is using a prefix other than "E" to indicate this isn't standard Exim behavior. Steve

5 years, 8 months

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

by Odhiambo Washington

On Mon, Jul 22, 2024 at 9:06 PM Christian via Mailman-users < mailman-users(a)mailman3.org> 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 > You upgraded Debian from Buster to what??? Bullseye or Bookworm? Why not just 'sudo systemctl start mailman'? > 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 ? > The lists are there since your DB is intact and your venv is intact as well. > > What am I doing wrong/what's going on here please? Thank you in advance. > I suspect your Python was upgraded to a version different than the one you use to create your virtualenv in the 1st place. If that is the case, you'll need to create a new virtualenv and migrate the data. > One more thing...I am running mailman core version GNU Mailman 3.3.5, Core > API Version 3.1, and Core Python Version 3.7.3. > Is there a reason you did not upgrade MM3 core and MM3 Web all this time? Anyway, check the version of Python used to build your virtualenv against the system version after you upgraded: # cat /opt/mailman/mm/venv/pyvenv.cfg home = /usr/local/bin include-system-site-packages = false version = 3.11.2 executable = /usr/local/bin/python3.11 command = /usr/local/bin/python -m venv /opt/mailman/mm/venv If older than the system version, you just need to build a new virtualenv and migrate the data. HTH. -- 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]

9 months

[MM3-users] Re: Compression error

by Mark Sapiro

On 8/16/19 7:18 PM, Andrew Bernard wrote: > I did a git pull today. Now I get the following error and the archives wont display: > > compressor.exceptions.OfflineGenerationError: You have offline compression enabled but key "b5ae52a1ebb585c556edceb45a148cb948b2a2673d133a340a90cd02fdd34828" is missing > from offline manifest. You may need to run "python manage.py compress". Here is the original content: > > Any clues? Did you do what it says, i.e. run "python manage.py compress" or however you spell your django admin command? It isn't always necessary, but I recommend that every time you do an update, you run all four of $DJANGO_CONTROL_SCRIPT collectstatic --clear --noinput --verbosity 0 $DJANGO_CONTROL_SCRIPT compress $DJANGO_CONTROL_SCRIPT compilemessages $DJANGO_CONTROL_SCRIPT migrate where $DJANGO_CONTROL_SCRIPT is the command to run django-admin or manage.py or however you spell it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

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

by SATOH Fumiyasu

On Sun, 09 Jun 2024 06:48:58 +0900, Mark Sapiro wrote: > ``` > #!/bin/bash > unset PYTHONSTARTUP > > exec /opt/mailman/venv/bin/mailman \ > -C "/etc/mailman3/mailman.cfg" \ > $@ > ``` You should use `"$@"` to preserver arguments. For examples: ``` $ sh -c 'for v in $@; do echo "[$v]"; done' sh a 'b *' 'c d' ... $ sh -c 'for v in "$@"; do echo "[$v]"; done' sh a 'b *' 'c d' ... ``` -- -- Name: SATOH Fumiyasu @ OSSTech Corp., Japan (fumiyas @ osstech co jp) -- Business: <https://www.OSSTech.co.jp/> -- Development: <https://GitHub.com/fumiyas/> <https://GitLab.com/fumiyas/> -- PGP Fingerprint: EE58 9CE7 A512 E5D8 1DAD 5627 6709 E8A8 C7DD 5305

10 months, 2 weeks

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

by Tibor Molnar

Hi there, I'm looking to find out if there is any way of deleting a user over API and what config needs to be done. Also if I can subscribe user/ users over API to lists. I'm aware that I can remove users in cli mailman shell, so I want to do the same thing over the web. 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? My current version is: Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Related conf in mailman.cfg: [webservice] hostname: localhost port: 8001 use_https: no admin_user: restadmin admin_pass: Thank you for your help

3 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/26/2017 02:06 AM, David Krantz wrote: > > I have of course activated password login as it was not possible to get the > provider based logins to work (might be but not worth the time for me right > now). Is there any way for an user to request a new password when it is > forgotten? > > I presume that the Persona login is removed now. I cannot hide it in my > version or at least I do not know how. All of this is fixed in the current GitLab branches. See the login page at <https://lists.mailman3.org/accounts/login/?next=/mailman3/lists/> for example. You really need to upgrade. Please see <https://wiki.list.org/x/17891998> for a discussion of how you can do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: 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 2:44 PM, Mark Sapiro wrote: > On 4/25/23 2:14 PM, Andrew Hodgson wrote: >> >> Why aren't we seeing the actual address here? ... > > I actually started with the preferred_address.email code above, but in > testing, I got the 'no_preferred_address' result with the one deleted > user so I, perhaps erroneously, went with the representation of the > user. I'll probably update the script again. I have updated the script again. It now displays: User: "Junk Mail" <junk_mail(a)example.com> deleted from Mailman -- 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: Member Issue Discovered

by Mark Sapiro

On 10/28/20 1:42 PM, Brian Carpenter wrote: > > This is a bug with Affinity which I have scheduled to be fixed. However > I am confused. Data is completely removed from Mailman 3 core when you > delete the account via Postorius but not when you unsubscribe from a list? Why do you keep bringing this up? The current design of Mailman core does not remove the user when the user unsubscribes from a list, even if it is their only subscription. We know you don't like this behavior, but there are reasons for it. On the other hand, when a user removes their account, the circumstance is different and we do remove the user's information in this case because that's what the user asked for. -- 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] Disable archives per list

by Bernd Wurst

Hello, we are about to migrate our Mailman 2 instance to Mailman 3. As we are hosting many (small) mailing lists for different customers, we get in trouble about future handling of mail archives. Mailman 2 just used mbox files per list and flat files for public archive, so archives do not matter apart from some storage. With hyperkitty, all messages for all lists are stored in on single database and I'm a little bit scared of a single database table with dozens of GB of data. Many of our users do not really need archiving, some customers also asked archiving to be disabled for legal reasons within their lists. Can I as the server admin disable archiving (or set other list options) in a way that the list admin can not change it via postorious? Can I have custom archiver settings per list or per domain (customer-specific hyperkitty)? regards, Bernd

4 years, 1 month

[MM3-users] Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by David Partain

>> Heck, I guess I >> could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to >> get rid of the emoji in the worst case... > > > You would need to do that, because once one of the `emoji` messages gets > into /var/lib/mailman3/archives/hyperkitty/spool, I think no further > messages are archived because mailman_hyperkitty tries to process the > queued messages first and throws the exception. Hi, In this regard, I have three questions: 1. Am I correct in assuming that I can just use my favorite editor (vi) to remove the offending characters from the file? 2. If I cannot find the offending character, is it safe to just remove the file so that subsequent archiving can proceed? 3. Can I do something to make hyperkitty go through the spool? Cheers, David

4 years, 1 month

[MM3-users] Outgoing messages fro Mailman fails DMARC

by Henrik Rasmussen

I have set up Postfix to DKIM sign outgoing mails from GNU Mailman 3.2.0a1 which validates nicely ("dkim=pass (signature was verified)"), but DMARC fails ("dmarc=fail action=none") on the recipient end, probably because the "header.from=gmail.com;" (or similar) which means that DKIM d= will not match. According to dmarc.org*) "Mailing lists usually do not take authorship of the emails they relay" so I should "consider to apply specific rules for emails coming from mailing lists". Also according to dmarc.org*) Mailman (Mailman 2 that is, and I presume Mailman 3 does too) "include features to interoperate with DMARC senders". I assume that the dmarc mitigations list settings in Mailman is for incoming messages, but how do I set Mailman to cope with this on outgoing messages? Note: I have more than one list domain in Mailman 3. *) https://dmarc.org/wiki/FAQ#Is_there_special_handling_required_to_receive_DM… /Henrik

7 years

[MM3-users] Re: easy way to delete old mails in hyperkitty?

by Mark Sapiro

On 4/8/19 1:38 AM, l.schimmer(a)cgv.tugraz.at wrote: > Hi! > > is thjere a easy way to delete old mails in hyperkitty? > > e.g. with a list and checkmarks, or via a cli command? > > We got several mailinglists and we did import them from mailman2.x into mailman 3.2. Now it is time to remove old posts before 2016. But I do not see a easy way to remove old posts in one go, just the "remove thread" button in each mail view. I don't think it would be difficult to create a cli command to do this, but nothing currently exists. You could create an issue for this at <https://gitlab.com/mailman/hyperkitty/issues> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

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

by Mark Sapiro

On 1/7/22 1:51 PM, David Newman wrote: > > However, there's no evidence test messages to the list are going out. > (Nondelivery was the reason I was mucking around in the admin panel in > the first place.) > > The Postfix log shows delivery to the list address. > > MM3's smtp.log shows the usual handshake. > > However, I do not then see messages going out to subscribers in the > Postfix log, and as one of those subscribers I do not receive a copy > even though my preferences are set to receive my own posts. Are the messages in Mailman's var/queue/shunt queue? Are there errors and tracebacks in var/logs/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Two trivial questons:

by Bill Oliver

First: Last night I got everything installed and, I think, working. Unfortunately, I forgot to write down the name and password of the superuser I created. I know what I put in as password, but I cant' remamber the name of the superuser. I know I could just create another superuser with "mailmanweb createsuperuser" but I was wondering if there was a "mailmanweb" command for *listing* superusers. If not, I'll just make another superuser... Second: I have the "example.com" error in the login screen. The instructions state that this is a problem with making SITE_ID=1. Okay, but I don't know what to change it to. I tried SITE_ID=2 on a lark and everything broke, and the instruction say not to do SITE_ID=0. Apparently it has to be an integer (I also tried putting in site name and got that error). So... where do I change it? Thanks! billo

6 months, 2 weeks

[MM3-users] Re: moving list from mm3 -> mm3

by Jens Günther

Thanks Mark for our answers, I already got a bit further. Am 09.12.23 um 00:27 schrieb Mark Sapiro: >> But it returns {"title": "405 Method Not Allowed"} and I don't know >> where to look in the docs, since it shows almost always a way through >> mailman shell. > You need a PUT command, not POST. Try the above with `-X PUT`. With the `-X PUT`-command, there is the following error: {"title": "400 Bad Request", "description": "Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, http_etag, join_address, last_post_at, leave_address, list_name, mail_host, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, usenet_watermark, volume"} -> I don't know why, since I tried it with the exact same example-list from where I got all these parameters (ex- and then import) ... do I still miss something? Or does it only work on "fresh" lists? > You can use Postorius -> Mass operations -> Mass subscribe to add the > members, but you can't do that for owners and moderators. Also you lose > information about the members such as Delivery status, Delivery mode and > other user settings. Is there another way to preserve these information about the members? (in general I don't think a lot of people put in effort to customize there memeberships ... and furthermore they would need to register, right?) >> ## registered users > > That is not the answer. Those are Mailman core users, not Django (web > login) users. You need to get the relevant entries from the auth_users > and account_emailaddress tables and add them to the new DB. Ok, that would be fine. Are there any more relations to other tables/columns that need to be set? (I just realised, that there are 2 different id in each table ... the one in auth_users is the user_id in account_emailaddress :-) scary). Do you have any suggestions on how to add them correctly? Thank you in advance for now and another big one in general to all of you on this list that try to help continouisly with all these problems. It's a great pleasure to be able to ask for help on a list like that. Thank you! Have a good rest of the year. Regards, Jens.

1 year, 3 months

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

by bob B

We had an issue where a program went rogue and sent out 30k email alerts to one of our lists, so now I have a few questions. When the issue happened I turned on emergency moderation and we have resolved the issue so.. 1. How do I easily delete 30k of held messages? It looks like the GUI only allows me to do 200 at a time? is there a way to flush all held messages easily? 2. When I enabled Emergency moderation, I expected it to stop notifying the admin on every held message, but it appears that is not the case? Also, does it reply to the sender of every held message when Emergency moderation is on? it seems like the steps are: turn on "Emergency moderation" turn OFF "Notify users of held messages" turn OFF "Admin immed notify"

2 years, 11 months

[MM3-users] Re: SOLVED was --- Re: Re: Debian 11 mailman3 installation question

by William Oliver

On Wed, 2022-10-12 at 15:50 +0900, Stephen J. Turnbull wrote: > > Thanks for the report. Glad to hear OS packaging is working on > *some* > platforms. > > From recent (painful) experience, I cannot recommend doing using the > OS packages on Ubuntu 20 LTS, unfortunately. > > Steve There were a couple of gotchas, but not too bad. Happily, the README.debian and a few web pages fleshed it out. The only thing is that the packages put a lot of stuff in places different than the manual installation tells you to do, so I had to keep poking around to find stuff. I was never able to install it on Ubuntu, either by package or by hand. I can't remember why, now, because it was some months ago -- but that's why I switched to Debian.

2 years, 6 months

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

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > On 21/06/2020 04:52, Mark Sapiro wrote: > > Change that to greyarea-post > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 I don't understand. I'm not in a position to test with Mailman itself right now, but the standalone gunicorn[1] does the right thing (takes an IP address and binds to the corresponding interface, or takes a domain name, resolves it to the IP address, and binds that to the corresponding interface). It does not substitute localhost. It could be a Mailman bug (Mailman 3 is usually configured with all components running on the same host, and that's how it's tested), but first, does greyarea-post resolve to a routable address on the relevant network when queried from that host? > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed hosts to get the right connectivity, too. I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? It's not clear to me why you think Mailman might want to be multihomed (which is different from the host wanting to be multihomed). I don't object to the work to make it so. But my paranoia says it's best if Mailman is cordoned off into the DMZ with webservers and other hazmat. By design, Mailman core doesn't need to talk to the Internet or to the secure internal network -- Internet functions are delegated to the MTA and the webapps, and local configuration is via shell access which in principle could be console. I'd rather not enable the complexity of a multihomed application unless there's an important use case. (I don't make the final decision, but I am listened to by Those Who Do.) Footnotes: [1] gunicorn is the Python module that manages web services for the REST interface.

4 years, 10 months

[MM3-users] Re: Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty

by Mark Sapiro

On 7/7/22 8:12 AM, tim(a)thecutts.org wrote: > Hi everyone, > > As we all know, mailman3 got dropped from Ubuntu 22. So I updated the operating system anyway, and decided to switch to a virtualenv setup, keeping the old Debian/Ubuntu database and log locations etc. > > With some lumps and bumps, this has gone OK; the web interface appears to be working, and I can use the mailman CLI to manipulate the lists. So far so good. > > However, there do seem to be two problems, which might be linked: > > 1. If I send a message to my test list, it does not get sent on to any members. I can see the lmtp delivery to mailman. But nothing comes out again. I can see the two test messages in the “shunt” directory Look in mailman.log. There will be exceptions and tracebacks associated with the shunted messages. What are these? > 2. Trying to look in the archives for my mailing lists does not work. On the web, I get "An error occurred while processing your request.”, and the log file seems to show a schema error in the hyper kitty table: > > ERROR 2022-07-07 13:18:41,634 116894 django.request Internal Server Error: /mailman3/archives/list/fairhaven-members(a)thecutts.org/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 86, in _execute > return self.cursor.execute(sql, params) > psycopg2.errors.UndefinedColumn: column hyperkitty_mailinglist.archive_rendering_mode does not exist > LINE 1: ...e_policy", "hyperkitty_mailinglist"."created_at", "hyperkitt... > ^ > > Do I need to run a database migration manually? If so, how? I’m not very familiar with Django, it seems a bit hideously complex to me. Yes. You need to run your Django admin command however you invoke it with the 'migrate' option. e.g. with your venv activated ``` django-admin migrate ``` or ``` python manage.py migrate ``` or ??? > Are these issues likely to be related, or do I have two things going on here? The shunted messages are not related to the Django migration issues. -- 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] Alter Messages: Reply to confusion

by paul＠arenson.org

This is one thing I am confused about. The explanations in the settings about No Munging, etc. are not completely clear. MY GOAL What I want to make sure, since this is a discussion list, is that most messages go to the mailing list, not to individuals. I plan to put something in one of the templates to remind people that a reply goes to the discussion list. If they do not want to send it to everyone, they should send to the original poster. 1) I understand there are plusses and minuses but I am not sure I understand the explanation given. If it IS preferable to use NO MUNGING, how do I make sure that this is easy to accomplish? 2) I can put something in the footer of every message to remind people, but first I need confirmation of what I should choose in this section. Thanks in advance.

5 years, 7 months

[MM3-users] Disabling the footer on a mailing list: Is this how?

by David Partain

Hi, I regularly get requests from users to disable footers since they use email clients that simply show an attached text file. Yes, I know that's broken. I never got this working with my old broken installation. Since we're now running a shiny new version of mailman3, I thought I'd give it a go again. From what I've read, I thought the following would do the trick: # sudo -u mailman -s /usr/bin/bash $ source /local/mailman/venv/bin/activate $ cd ~/var/templates/ $ mkdir -p lists/test-list.our.domain/en/ $ cp /dev/null "lists/test-list.our.wee.domain/en/list:member:regular:footer" However, sending mail to test-list(a)our.wee.domain<mailto:test-list@our.wee.domain> still includes the footer. What am I missing? Do I need to restart something? Did I misunderstand what I've read? With kind regards, David

1 year

[MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Mark Sapiro

On 7/18/24 7:58 AM, willie.castillo(a)caemilusa.com wrote: > Not sure what's going on here. This is the output of the "mailman3 info". What am I doing wrong? > > $ /usr/bin/mailman3 info > Traceback (most recent call last): ... > alembic.script.revision.ResolutionError: No such revision or branch '2156fc3f6f7d' The `mailman3` command is trying to run all the alembic migrations as part of initialization and is failing with this error. Thus, it never gets to the point of actually doing what you ask. What is the version_num in the alembic_version table in the database? I.e., ``` SELECT version_num FROM alembic_version; ``` and what does ``` ls /usr/lib/python3.9/site-packages/mailman/database/alembic/versions/ and grep -r 2156fc3f6f7d /usr/lib/python3.9/site-packages/mailman/database/alembic/versions/ ``` give? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Mark Sapiro

On 4/7/23 13:43, Odhiambo Washington wrote: > On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < > as2020+github(a)fam.tuwien.ac.at> wrote: >> >> I am running MM2 und 3 in parallel without problems, I do have a >> special MTA setup though (Sendmail). Can't speak for Postfix etc.. >> > > Your setup can handle list1(a)domain1.name via MM2 and MM3, simultaneously, > right? :-) It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` simultaneously on the same server, but what is the MTA going to do with incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to both MM2 and MM3, but I don't see any practical use case 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

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mark Sapiro

On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://django-allauth.readthedocs.io/en/latest/providers.html#openid -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: How can administrator sign people up to a list?

by worik

Sorry about the noise. Found it. It is on the page for the list, a ,menu option at the top of the page. Thanks Worik On 11/02/19 2:28 PM, worik wrote: > On 11/02/19 2:25 PM, Mike wrote: >> Sign into Postorius and go to "Mass Operations" - >> "Mass Subscribe". >> >> >> >> On 2/10/2019 7:13 PM, worik wrote: >>> As a list administrator, how do I add a group of email addresses to a >>> list? > > I cannot see that option. > > When I click on the Postorius logo I get to postorius/lists/?all-lists > > Worik > -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] Seeking help completing a useful installation

by Hugh Esco

I have more fully documented where I am at with this attempt to build a working installation of mm3 at this link: https://gitlab.com/mailman/django-mailman3/-/issues/73 My questions include: - the template for /etc/mailman3/mailman.cfg, defines vardir, but no DATA_DIR. See test failure #1 (closed) <http:///mailman/django-mailman3/-/issues/1>, above. Where does that want to be? Any issue with putting the mm3.db next to the mm3_web.db at /opt/mailman/mm/var/data? - there are two possible virtualenv's in my build: (a) /opt/mailman/venv/ and (b) /opt/mailman/.pyenv/. I say more about these below. Which do I want to use in this instance? I'm guessing the latter where the mailman3 libraries are published, but have doubts. The link above urges a dependency on python ^3.11, but bookworm provides only python 3.8, so I used pyenv to satisfy the requirement. It wanted to deploy to its own path, though perhaps there is some switch which would consolidate everything under /opt/mailman/venv/. I do not work with python enough to know. - attempts to run bin/mailman-web startapp mm3web fail to add any new processes to the process list. bin/mailman-web start fails with errors. What change of state to the server should I expect from running this command? How do I test for success? If startapp is the correct invocation, what argument does it want on a working installation? - having run the command in the previous point, I see nothing in the browser except for the apache starter page at the root path '/'. None of the paths defined in the apache2 configuration seem to offer any joy. I assume that uwsgi wants to proxy the requests to a running mailman-web service somehow, but that no such service is found. I see one hopeful line in the log at: /opt/mailman/mm/var/logs/mailman.log "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" - I assume that once I get apache2 wired to a running application through the uwsgi proxy, that I can proceed to create an admin user, use it to explore the web gui, and begin to consider how to migrate my legacy mm2.1 lists into the new installation. Any further help crossing the finish line would be appreciated. Thanks, -- Hugh

1 year, 1 month

[MM3-users] Re: Hyperkitty performance problem

by Stephen J. Turnbull

Stephen J. Turnbull writes: > This doesn't make any sense. That appears to be the listarchiver > table. As far as I can tell in a quick grep, the only place that is > mutated is in mailman/models/mailinglist.py:643 (line number is > current HEAD), which happens whenever the list checks for its active > archivers. It's initialized lazily for each list in that place. HOWEVER, if you DO manage to populate that table with thousands of duplicate entries, we do not check for unique entries when we fetch the list of archivers: @property @dbconnection def archivers(self, store): entries = store.query(ListArchiver).filter( ListArchiver.mailing_list == self._mailing_list) yield from entries which could explain archiving one message thousands of times. (You shouldn't be able to get there without passing through the constructor __init__ though, which should be checking. It apparently does check according to your report ... my head hurts.) Steve

2 months

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

by Mark Sapiro

On 4/4/25 08:10, via Mailman-users wrote: > I have a mailing list that, due to specific circumstances, has a requirement to allow messages from a user that sends messages with no subject. I've added the address to the "Accept these non-members" collection, but messages from that address still get held for moderation, due to the no-subect rule. Do not add the address to accept_these_nonmembers. Is the user a member? If so, go to the `Members` list, click on the user (search if necessary), scroll down to Administration options Moderation and set the dropdown to `Accept immediately (bypass other rules)` and click the Save changes button below that. If the user is not a member, do the same thing, but use the `Non-Members` list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 5 days

[MM3-users] Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 5:40 PM, Brian Carpenter wrote: > Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. Abhilash (@maxking) is one person and he has a $DayJob. We're all doing the best we can. > I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. This is not a Docker issue per se. It is a consequence of upgrading Mailman core to 3.3.1+ and processing many old, stale, previously unprocessed bounces. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. > > I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: > > ### > The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: > > [webservice] > configuration: /path/to/gunicorn.cfg > > and then in the gunicorn.cfg you can add > > [gunicorn] > timeout = 90 > graceful_timeout = 30 > ### > > I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. > > After restarting docker-mailman, I can't access Postorius due to the following error: > > ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Is Mailman core running? If not, whats in core's mailman.log as to why not? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Tracking from gravatar

by Abhilash Raj

On Mon, Feb 18, 2019, at 7:16 PM, worik wrote: > On 15/02/19 3:51 PM, Mark Sapiro wrote: > > You can disable them by setting > > > > GRAVATAR_SECURE_URL = '' > > > > in your local settings. See > > <https://github.com/twaddington/django-gravatar> > > Where do I make that setting? There is nothing like it in any of my files. This should go in your Django's settings.py (or settings_local.py) depending on how you installed Mailman. > Worik > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: Welcome Message

by brian＠emwd.com

Mark Sapiro wrote: > Can you do bin/mailman shell? > > That would be even better. bin/mailman shell -bash: bin/mailman: No such file or directory Apparently not. Again this is the Docker version. Would love to have the Docker maintainer help out here. > If you're installing via pip you must have Python 3. Your tracebacks show a Python 3 > library in /usr/lib/python3.6/ /usr/lib/python3.6 -bash: /usr/lib/python3.6: No such file or directory I am installing it via pip on a Ubuntu server which is a different server from this template problem. Sorry about the confusion. The one where I need the templates to work is on a Centos server that used Docker to install it. I simply do not know how to get a python3 prompt when it has been setup via Docker. I will be requesting some assistance for the Ubuntu server once I get this template issue resolved. Brian

6 years

[MM3-users] Re: Hyperkitty django.request forbidden

by Arpad Horvath

Unfortunately I don't remember the articles that I used when I migrated. But this setting (no MAILMAN_ARCHIVER_FROM setting directly) does not seem to work. Hyperkitty is clearly available from outside, but doesn't seem to be from inside (localhost). I don't know how can I make it available on localhost with nginx. Current nginx setting is quite long and I am not sure, what is sensitive there. The structure is this upstream mailman3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0; } server { listen 80; listen [::]:80; server_name lists.somewhere.xx; ... } server { listen 443; listen [::]:443; server_name lists.somewhere.xx; ... location / { uwsgi_pass mailman3; include /etc/nginx/uwsgi_params; } location /mailman3/static { alias /var/lib/mailman3/web/static; } location /mailman3/static/favicon.ico { alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; } access_log /var/log/nginx/mailman3/access.log combined; error_log /var/log/nginx/mailman3/error.log; } Can I reach hyperkitty through the socket then or what do I need to do?

1 month, 3 weeks

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

by Lars Schimmer

On 02/03/2021 19:20, Mark Dadgar wrote: >> As someone who is stuck using the ancient version of mailman3 in debian, I have to disagree. 99.9999% of the time I hit an issue, it turns out it was fixed years ago, but because I use the debian maintained version, I don't have those fixes. It's horrible. 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. > +100 > > I originally installed mailman3 via the ubuntu packages and I eventually replaced that setup (read: paid Brian to re-install mailman3 “correctly") for 2 key reasons: > > 1) The ubuntu (and presumably debian) packages are 1+ years out of date - Quanah is correct in that most of the bugs you hit have been fixed already but haven’t made it through the package maintainer process yet. Just being 1+ years old does not tell you a software is bad or not useable. Thats a nonce. Bugs shoudl be iron out with package fixes, if someone cares about. New versions are out, needs to be tested. > 2) The package installs are non-standard with respect to the way the mailman3 community tends to install them, which makes getting support here on this list much, much harder. You can see evidence of that periodically when someone asks a question and Mark’s response starts with “I’m not entirely sure how the <distro> package sets things up, but …”, which is no slight on Mark because he has his hands full with mm3 already and tracking every distro install layout is just not going to happen. It also means that the official mm3 docs don’t match what came out of your package. It’s just not good all the way around. Sure, every software has its own scheme, but sthats what standards are for. I still cannot switch easy between fedora, debian and other distros due to different standards on file path. It is a nightmare. 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). You are right, the dev of a software should mostly care about fixing bugs, implementing new features and getting along with the software. Implementing different ways of installing is just a side topic. But someone should care about howto get the (useful) software to the masses for using it. And that position should care about howto implement the software good into the running distributions worldwide. And for distributions with a very good way of using packages, it is a nightmare to work beside the package manager just because the package is rather not well maintained. >> Distribution packages tend to be useful for really basic things like libraries. For constantly evolving projects where you need to be current, they're more of a detriment. > > So much this. You do not need a bleeding edge software on production servers. You just need bug free, whihc is easy done with packages on distributions, if maintainers do it well enough. For a testing server bleeing edge maybe fine, but not in production. > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 1 month

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Mark Sapiro

On 4/17/25 10:20 AM, Mihai Moldovan wrote: > > Now... is there a way to import mbox files into the prototype archiver? > Looking around, I haven't found anything mentioning this. Since it's > just using the Maildir format, I guess I could find a tool that unpacks > messages from an mbox to a Maildir destination and get that done, but if > mailman has some command to do that, it would be even better. There is no Mailman command to do this, but a Python script is very simple. Something like ``` from mailbox import Maildir, mbox mb = mbox('path/to/mbox', create=False) md = Maildir('path/to/maildir', create=False) for msg in mb: md.add(msg) mb.close() md.close() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 days, 20 hours

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

by Stephen J. Turnbull

Andreas Barth writes: > * Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210217 09:54]: > > Right. So what you mean is "ok, we have group permissions, and maybe > > someday there will be a case for ACLs down to arbitrary subsets of the > > user population," but you don't have a concrete use case for arbitrary > > ACLs at the moment. > I definitly have a usecase for that, but: currently other priorities :) > (I had to do an ad-hoc takeover of lots of infrastructure in my spare > time within an volunteer organisation including mailing lists, so > getting wishlist itmes done is not my top priority at the moment.) > > Just from the top of my head, for example I want to differentiate > between private, member and public lists. So if a member logs in, they > see more lists than a non-member. This is currently not possible, not > too big a deal (all member lists are currently configured as private) > but of course would be nice. Also archiv access should be aligned with > these permissions. This would not be worth doing with generic ACLs from Postorius, unless the list had (many) fewer than 100 users. What I'd end up doing (and I bet you would too) is write a 15-line mailmancli script that extracted membership information and then created the ACLs. But you'd still have to modify the Django templates, I suspect, and perhaps database schema. Essentially the same 15 lines could be put into Mailman itself without ACLs, and checking ACL membership is not going to be much, if at all, faster than checking list membership. > Of course the appropriate split between private changes and public > changes is also something which might need some discussions. Not sure what you mean by private and public here, but if you mean which changes we should maintain and which changes you should maintain locally, I haven't seen anything in this thread that we wouldn't want to offer all Mailman 3 users. From Abhilash's and Mark's posts, I believe they feel that way too. It's just a question of whether a very general implementation is needed/worthwhile. Steve

4 years, 2 months

[MM3-users] Re: Mass unverified subscriptions end up as pending user confirmation instead.

by Mark Sapiro

On 2/25/20 2:34 PM, hansen(a)rc.org wrote: > After mass subscribing with these settings: > > Pre confirm: Yes, Pre approved: Yes, Pre Verified (sic): No > > the addresses appeared in the list's 'Pending user confirmation' list. They were pre-confirmed. > The addresses did not appear in the Django Admin's non-verified addresses list. They were not verified. It is actually pending verification, not confirmation. Postorius can't tell the difference. It only knows that it's waiting for some action either by a moderator (pending approval) or the user (pending confirmation or verification, but just called 'confirmation') This verification is for Mailman core to verify it's a valid address that the user wants to use with this mailman installation. Once this address is verified, it can be subscribed to other lists without further verification. This has nothing to do with Django verified addresses which are addresses associated with Django log-in that have been verified to Django. > Also why does Postorius lists just 'Pending Approval' and 'Pending Confirmation' but not 'Pending Verification'? As I said, it doesn't know the difference between 'Pending Confirmation' and 'Pending Verification'. You should note that the user you subscribed in this way received a 'verification' request like > Email Address Registration Confirmation > > Hello, this is the GNU Mailman server at example.com. > > We have received a registration request for the email address > > user(a)example.org > > Before you can start using GNU Mailman at this site, you must first confirm > that this is your email address. You can do this by replying to this message, > keeping the Subject header intact. > > If you do not wish to register this email address, simply disregard this > message. If you think you are being maliciously subscribed to the list, or > have any other questions, you may contact > > listname-owner(a)example.com and not a subscription confirmation request. Also, if any of the addresses had been already verified, they would have been subscribed immediately without confirmation or approval. -- 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: Cannot setup announce-only mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/1/20 9:53 AM, Abhilash Raj wrote: > > Mark, do you think we should make the actual announce-only style reflect > > these settings so folks don't have to manually set these after they create > > a announce-only list? > > > > I am not sure the reason behind these settings lacking for the current > > announce-only style. Are there situations where announce-only list would > > have different list setting? > > I think it was probably done as it is just as a start. I do think it > would be good to set more things appropriately for the announce-only > style, ultimately we may need to add templates for post rejection > notices and things like that. If this involves a fair amount of coding maybe it could be a suggested GSoC task? Steve

5 years, 2 months

[MM3-users] Re: remove non members from a list

by Mark Sapiro

On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to remove all non members from a list. I know I can do it via > Postorius, but it has to be done one at a time. (you can delete ALL > suscribers but not all non members...) > > Anyone has a python recipe to do this? $ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> for nonmember in m.members.nonmembers: ... nonmember.unsubscribe() ... >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

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

by bob B

Mark, Thanks for the Assistance but a little lost in the interpreter, and no luck googling. How do Iget back to the >>> prompt? I enter bash-5.0$ mailman shell -l maillistappha(a)XXXXX.org 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 maillistappha(a)XXXXX.org mailing list >>> from mailman.app.moderator import handle_message >>> requestdb = IListRequests(m) >>> for req in requestdb.held_requests: ... if req.request_type == RequestType.held_message: ... handle_message(m, req.id, Action.discard) ... ********* This is where I am stuck ********** I hit return it takes me to a new line with no characters? how do i get back up a level to the >>> prompt to enter commit()

2 years, 11 months

[MM3-users] Re: List creation error

by Brian Carpenter

Odhiambo Washington wrote: > On Wed, 6 Jan 2021 at 15:36, Andreas Barth aba(a)ayous.org wrote: > > > > Odhiambo Washington (odhiambo(a)gmail.com) [210106 12:12]:PS: I could probably have caused the error with some weird operation I > > did: > > Initially when postorius comes up, it has the domain - example.com > > http://example.com. I am not sure > > where it gets this. > > > > > > example.com is the default domain from django. Renaming that via the > > django (e.g. mailman3/admin/sites/site/1/change/ ) worked for me quite > > well (without touching anything in the database by hand). > > Hi Andi, > I could be missing something still... > > At what juncture during the installation do you do this renaming? > Where is this directory? On my setup, I have no such directory - but I > could be missing something in the install process, maybe.. > > root@debian10:/opt/mailman# pwd > /opt/mailmanroot@debian10:/opt/mailman# find . -type d -name sites > ./mm/venv/lib/python3.7/site-packages/jedi/third_party/django-stubs/django-stubs/contrib/sites > ./mm/venv/lib/python3.7/site-packages/django/contrib/sites > Do you find anything amiss with this HOWTO - > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ?? I > find > the guide rather straight and clear. That is my work in progress and thank you for the compliment. > It's the one I am following - almost to the letter - except for the fact > that I am using Apache+mod_wsgi+MySQL+Exim instead. > I have configs in place by the time I run 'mailman info' portion. But then > again, when I run this command, I don't like what it prints because I see > some reference to sqlite. Can you paste what the mailman info output is and the contents of your mailman.cfg file? > As it is, I believe my problem lies elsewhere, not possible to solve with > your rename option. To get rid of example.com, I log into Django, create a new site using the main list domain and note the site id. I then edit the settings_local.py file and change the SITE_ID setting to the new site id of the main list domain. You will need to restart mailman and qcluster I believe after making that change.

4 years, 3 months

[MM3-users] Re: Removing banned emails

by Mark Sapiro

On 08/02/2018 11:47 AM, Kaleb White wrote: > I am trying to remove a banned email with a special character via the rest api and it's not working. It's also not working via the UI. Any ideas? > http://localhost:8001/3.0/lists/example.com/bans/provisor#41@bankofamerica.… > <Response [404]> You can't do it from Postorius (This should be considered a bug in Postorius or perhaps mailman-client). You can do it via rest if you URL encode the request as http://localhost:8001/3.0/lists/example.com/bans/provisor%2341@bankofameric… The issue is whatever client is making the HTTP request is considering '#41(a)bankofamerica.com' to be a fragment identifier so it issues the request for the resource '3.0/lists/example.com/bans/provisor' and expects to find sub-resource identified by '41(a)bankofamerica.com' in the response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

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

by Mark Sapiro

On 12/26/21 6:05 PM, William Oliver wrote: > > So.. if I need to do it myself, can you point me to what file I need to > create/modify in the /opt/mailman/mm tree to set up the alias? Assuming you have Postorius working, just go to the Domains view, edit your domain and add an Alias Domain. Otherwise, you can do this in mailman shell, e.g. ``` $ 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. >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = x.example.com >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Stephen J Turnbull

2023-05-16 17:42 に peter(a)chubb.wattle.id.au さんは書きました: > 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) I can't help with this. I don't understand why that would happen, maybe Mark or Abhilash does. I would think that the address that would be shown is the address in the email's From field. > 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/ They shouldn't, necessarily. The user's active emails will be maintained by the user in Postorius, which what I believe appears in the Django admin screen. However, HyperKitty needs to know *more*: in general, it needs to know every address by which that user was identified in the archives. This is valuable to the users of the archives -- if they try to mail an author at a defunct address, they can return to the profile to find an active one. > How can I as administrator get rid of bogus addresses? Or do I > have to ask each user to do this? I believe Mark has a script for getting rid of garbage addresses that have no root in user-visible data, but these are not garbage in that sense: they do appear in the archives. However, since that script refers only to the database, it would probably work for HyperKitty's addresses too. But it might require code modifications, inasmuch as there would be database errors if either the Address object doesn't exist or the User link in the Address object is null. > and how can I ensure that the email address displayed in the > archive is the primary address, not some address that no longer > works? That's not necessarily your choice (I'm not speaking to your installation, I'm talking about design principles). Remember that users can associate specific addresses with specific lists, and you would be overriding that preference ex post. (I have no problem with you announcing a "real address only" rule in advance, of course.) Also, there may be a reason why that address is defunct: stalkers, termination of employment, etc. In those cases, the user may have a strong desire not to contacted about the post in question. If you are in a jurisdication that is under GDPR or other strong privacy legislation, there may be legal implications you should consider. In general you should consider whether possibly violating users' expectations in these ways are appropriate to your site. In general, Mailman 3's design philosophy is to give users fine control of their user profiles and addresses and of their subscriptions' configurations, while list owners get the traditional features for their list configurations: control over access and default profiles, etc. So I suspect there is no way to impose the restrictions you want without writing new code. I don't have a particular objection to such features as long as the policies are transparently documented (users don't have to use those sites), but I'm not available to work on them for some time. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

1 year, 11 months

[MM3-users] Re: Delete a single email or thread from hyperkitty archive

by Abhilash Raj

On Fri, Jun 21, 2019, at 2:07 PM, Mark Sapiro wrote: > On 6/21/19 6:54 AM, andrew.bernard(a)gmail.com wrote: > > How can one do this? Raw database access gets you involved in all the usual foreign key constraints. > > > In the HyperKitty thread view there is a link to "Delete this thread". > In the message view there is a link to "Delete this message". Do note that this option is only visible to "Superuser" in Django, i.e. Admin accounts. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Re: List enumeration problem

by Darren Smith

Simon, The thing is that there doesn't appear to be any corresponding entries in the front end logs. There isn't anyone hitting postorius for the lists that are being enumerated. About the three items you mentione: 1) I hope that this can be fixed soon! There are several pages on our mailman instance that we had to write a separate back-end API to query the data, because a single user hitting a single page in postorius was causing a denial of service. 2) What sort of stuff is synced between the front and backends? Any chance you can point me to somewhere in the code where this is happening? We may need to rewrite something to streamline this as well, but it would be nice to know where we need to go poking around. 3) We have some hyperkitty cron jobs set up, but at the moment they have been scaled back somewhat. I do know that when this enumeration is going on our hyperkitty jobs aren't being run. We (I work with Kaleb) are one of those very large Mailman instances you mention, so yep, we're seeing what you're talking about! I think in our case the most likely root cause is your #2 above, so any guidance you can shoot in our direction would be much appreciated. Thanks! -Darren On Fri, May 11, 2018 at 3:53 AM, Simon Hanna <simon.h4nn4(a)gmail.com> wrote: > This appears to be logs from the backend. Do you have corresponding > entries from the frontend? > > I have a couple of explanations for this: > 1. Normal operation: > Most rest calls don't support batch processing, so the frontend needs to > issue multiple calls. > > 2. Synchronization between frontend and backend. > Some stuff is synced between the two, it might be that... > > 3. Hyperkitty cron jobs > Hyperkitty has a couple of cronjobs to do maintenance on the database and > such. > > If you have logs from the frontend, we can know for sure what's causing > this. > 1 is a known issue and is going to get fixed eventually... > (especially since very large Mailman instances are popping up...) > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 11 months

[MM3-users] Re: ham-confirm+3ee85b006eeb5897ca6f53b093cb063672f6a784@example.com

by Jörg Klein

Here the second try. The email will be deliverd. But I can not confirm the mail. How to configure the email-address xxx-owner(a)example.com or ham-confirm+c56ac3f61561fc11239897d602956f62b3ca5670(a)example.com? Email Address Registration Confirmation Hello, this is the GNU Mailman server at example.com. We have received a registration request for the email address user(a)example.com Before you can start using GNU Mailman at this site, you must first confirm that this is your email address. You can do this by replying to this message. Or you should include the following line -- and only the following line -- in a message to ham-request(a)example.com: confirm c56ac3f61561fc11239897d602956f62b3ca5670 Note that simply sending a `reply' to this message should work from most mail readers. If you do not wish to register this email address, simply disregard this message. If you think you are being maliciously subscribed to the list, or have any other questions, you may contact ham-owner(a)example.com

4 years, 2 months

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

by Mark Sapiro

On 7/7/22 3:09 PM, David Newman wrote: > > I *think* the command runs if I escape the hyphen: > > root@somehost:/opt/mailman/venv/lib/python3.9/site-packages# grep -r > '\-jango' /opt/mailman/venv/lib/python3.9/site-packages/ > > But then that doesn't return anything. Yes, escaping the hyphen is the correct thing to do. You could also try something like ``` grep -r '.-jango' /opt/mailman/venv/lib/python3.9/site-packages/ ``` but that will also return nothing. See https://stackoverflow.com/questions/67613777/pip-ignoring-invalid-distribut… https://stackoverflow.com/questions/68880743/why-do-i-get-this-when-using-p… and perhaps other hits from https://www.google.com/search?q=pip+warning+ignoring+invalid+distribution Look for ``` ls -la /opt/mailman/venv/lib/python3.9/site-packages/~jango* ``` i.e. `~jango` rather than `-jango` -- 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: Turn off social logins?

by Jonas Meurer

Hi Stephen, thanks for your follow-up and the discussion about ID providers. Stephen J. Turnbull: > 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. As the Mailman3 Debian Maintainers, we decided to disable social auth in the mailman3-web Debian package alltogether. That's because in general, we try to avoid "calling home" features in software when it's possible. Usually, these "call home" features are abused to track users behaviour. With Mailman3, it's not directly calling home. But still, adding so-called "social" authenticators to the mailman3 django application will expose users to the risk of clicking on those ID provider buttons. > > 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. Personally, I consider it a major privacy issue if one central instance (e.g. Facebook) is able to track on which platforms and services you authenticate. And to be honstes, I'm a bit irritated that those tracking features from big corporates like Facebook and Google, whose main business model is to aggregate as as much private data points as possible about as much users as possible are enabled by default in Mailman3 upstream. Besides the privacy concerns raised above, on problem with central authentication services is that they also create new single points of entry/failure. If your Facebook account gets hacked, you now loose control over all other services/platforms, that you used the Facebook authenticator service for. > > 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!) I agree with Torge that those social auth providers should be disabled per default. IMHO, A sane default would be to list them in the settings.py but have them commented out. Cheers jonas

6 years, 2 months

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Mark Sapiro writes: > This apparently confuses the Python email package so that the > get_payload() method returns a list of strings rather than a list of > message objects. Yes, I got that far too. I'm guessing that in the absence of a Content-Type, which then *should* default to text/plain, the email package goes ahead and detects the MIME headers anyway (although I don't think it should do that) and breaks the message into MIME parts. I would think we'd raise an Exception here. If there's a reason for the email package to do that detection (*shrug*, it seems to work), then the dispatching in _handle_text should be done on the Python type rather than the MIME Content-Type. I forget exactly how the code is structured, the relevant dispatching may be in _dispatch or in _dispatch_meth. Steve

2 years, 7 months

[MM3-users] Re: 2 postfix instances and 1 mailman instance possible?

by Mark Sapiro

On 9/29/22 06:55, charlie derr wrote: > Greetings, > > We will be (temporarily) splitting our single postfix instance and > running two separate instances on our email server. > > Can we configure mailman to listen to one of them and send to the other? > > If so, please do direct us towards how we would go about configuring > mailman to do this. > > versions: > > mailman: 2.1.15-30.el7_9.2 The list for Mailman 2.1 questions is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/> That said, to set the outgoing MTA, set SMTPHOST and SMTPPORT in mm_cfg.py to the desired values. For the incoming MTA, configure that Postfix to deliver to Mailman. See https://www.list.org/mailman-install/mail-server.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/4/21 12:52 PM, Duane Raymond wrote: > > Virtual Domains: > So based on the Postfix virtual domain documentation and the Mailman3 specific "Unusual Postfix configuration' section, I added the following to my postfix main.cf file: > virtual_alias_domains = emaillistA.com emaillistB.com > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > and removed those domains from the 'mydestination' setting. You probably do not have a configuration that is a "Unusual Postfix configuration" Putting Mailman aside, is there some reason why emaillistA.com and emaillistB.com need to be virtual_alias_domains? If these domains are only for mail lists, they do not need to be virtual_alias_domains? > I then created the postfix_vmap file and added to it: > emaillistA.com DOMAIN > # > emaillistB.com DOMAIN You don't create these files. Mailman creates them in its var/data directory when you run `mailman aliases` or just start mailman core. > ...then ran postmap with the path and reloaded postfix. Mailman also runs the appropriate postmap commands. You should have one of two setups in Postfix depending on whether emaillistA.com and emaillistB.com need to be virtual_alias_domains or not. If they are only for list mail, they should not be virtual_alias_domains in Postfix and their domain definitions in Mailman should not have an alias domain. In that case, in Postfix you want transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp local_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains and you want Mailman to generate those files. Also see the note in <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> about adding hash:/path-to-mailman/var/data/postfix_lmtp to local_recipient_maps rather than replacing it. If emaillistA.com and emaillistB.com do need to be virtual_alias_domains, you configure them in postfix according to the normal postfix configurationfor virtual_alias_domains and virtual_alias_maps. Then each of these domains needs a corresponding, otherwise unused alias domain defined in Mailman and what you need in Postfix is transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap Where again if you have existing settings for these things, add the mailman files rather that replacing the existing with them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

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

by Mark Sapiro

On 11/2/21 9:30 AM, bob B wrote: > So just want to make sure I have the latest information after searching this list and googling or have I missed something? It appears there is no way in mailman3 to delete archives. There has been discussion on implementing this, but it has not been developed? is that correct? I'm not sure when it first appeared, but current Hyperkitty has Delete Archive button on the list overview page, but it is only available to Django superusers, not to list owners. > I saw references to: >>>> from hyperkitty.models import MailingList >>>> ml = MailingList.objects.get(name="test2(a)freeculture.org") >>>> ml.delete() > > > But how do I run this? I believe it is run in mailman-core (I am in a docker environment but that should not matter). I can get into the mailman shell, but that command does not work It is run in a Django management shell, not mailman shell. > ************** Question 2 > > What about pruning archives? I use to run a script for mailman2 to prune archives of messages older than X days for a list, Is that possible in mailman3 There are a few ways to do this. You can export the archive for a list as an mbox and edit the mbox to delete the messages you want to prune. Then delete the archive for this list and finally run hyperkitty_import to import the pruned mbox. Alternatively, in a django management shell, you could try something like ``` import datetime from hyperkitty.models import Email for msg in Email.objects.filter(mailinglist_id=X): if msg.date < datetime.datetime(Y, M, D, tzinfo=datetime.timezone.utc): msg.delete() ``` where X is the id of the mailing list you want to prune, or if you wanted to do all lists, just use Email.objects.all() instead of filtering on mailinglist_id. And, Y, M and D are integer Year, Month and Day for the cutoff. Note that something like ``` from hyperkitty.models import MailingList for ml in MailingList.objects.all(): print('{}: {}'.format(ml.name, ml.id)) ``` will print all the list names and their ids. -- 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: Stability issues

by Mark Sapiro

On 09/07/2018 06:53 AM, schultmc(a)cinlug.org wrote: > We're currently piloting Mailman3 to replace a failing Ecartis installation. We've had to push back our go live date several times due to stability issues with our Mailman 3 installation. We currently have Mailman core 3.2.0 running on Red Hat Enterprise Linux 7.5 with 2 vCPUs, 8GB RAM and 25GB swap space. Occasionally, we see mailman become unresponsive both via the REST API and the web UI. We haven't seen anything glaring in the logs but would be happy to check further. I know Mailman 3 powers many large lists and would appreciate any performance, stability and tuning information that can be provided. When it is unresponsive what is the state of the 'rest' runner and is it listening on localhost:8001? What do you do to 'fix' it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Problem with perms on /etc/mailman3/mailman.cfg while following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Philip Bondi

Hello to all: Trying to install mailman3 for the first time on Debian 12 virtual machine. I tried to search for relevant and related posts, but could not find any. I'm following along the documentation and I get stuck after this step https://docs.list.org/en/latest/install/virtualenv.html#setup-mailman-user I'm finding that there's a problem while trying to edit /etc/mailman3/mailman.cfg The instructions https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… do not say what to do with existing file. root@shackleton12:~# ls -alF /etc/mailman3/mailman.cfg -rw-r--r-- 1 root list 11119 Mar 20 11:45 /etc/mailman3/mailman.cfg Should we move the /etc/mailman3/mailman.cfg out of the way and create new file as user and group mailman:mailman ?

4 weeks, 2 days

[MM3-users] Excluding archives from a mailman3web database backup

by Andy Smith

Hi, In doing regular database dumps for backup purposes I note that by far the largest quantity of data is HyperKitty's archives. We already keep external archives using the prototype archiver (and some rotation of Maildirs), because we see value in having a simple archive outside of HyperKitty. So, I'd rather not be backing up this data twice. In event of disaster I'd like to be able to do a maildir2mbox on what prototype has written and re-import the resulting mbox file. Is that a realistic proposal? i.e. does a typical maildir2mbox conversion script generate something that "manage.py hyperkitty_import" would be happy with when run on prototype's maildir? If so, is it safe to just exclude every table starting with "hyperkitty_" from the database backup of mailman3web? Dumping only the schema for these, I mean, so that an import would restore empty tables. Thanks, Andy

2 years, 10 months

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

by Henrik Rasmussen

Henrik Rasmussen wrote: > Abhilash Raj wrote: > > On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro > > wrote: > > each other, but Postfix is trying to deliver > > mail via lmtp to > > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > > listening on port 8024. Either that is not the case or that port is not > > exposed to Postfix on IP 172.19.199.2. > > Right, that is what I was wondering, you verify that by using telnet > > on the specified IP and Port (172.19.199.2:8024). > > Yes, the postfix container listens on 172.19.199.2:8024 > [root@postfix /]# nc -v 172.19.199.2 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.19.199.2:8024. > 220 mailman-core GNU Mailman LMTP runner 2.0 > > > docker-compose ps lists all the running containers, > > do you see all > > the containers running? > > That also seem to be okay > [root@lstapp01pl ~]# docker ps > CONTAINER ID IMAGE COMMAND CREATED > STATUS PORTS > NAMES > bddc80799b8c maxking/mailman-web:0.2 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 8000/tcp, 8080/tcp > mailman-web > be098b18aeca maxking/mailman-core:0.2 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 8001/tcp, 8024/tcp > mailman-core > c47fd8ccf19d postgres:9.6 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 5432/tcp > mailman_database_1 > 699264501acd mailman3-mime_htmlizer "container-entrypoint" 16 hours ago > Up 16 hours 8080/tcp > postmime > 90f381a74709 mailman3-postfix:v1.1 "./entrypoint.sh" 16 hours ago > Up 16 hours 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, > 0.0.0.0:26->25/tcp postfix > > And netstat in the mailman-core container shows: > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 172.19.199.2:8024 0.0.0.0:* LISTEN` > > > You mentioned that Mailman is not receiving enough > > emails, do you get > > any emails from Mailman? I am trying to see if this is a perf problem > > or if Mailman's LMTP isn't reachable at all. > > Mailman do send out mails like when someone signs up for an account. > Thanks to both. And the runner is running: `Sep 19 06:55:06 2019 (36) b'220 mailman-core GNU Mailman LMTP runner 2.0`

5 years, 7 months

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

by Mark Sapiro

On 11/1/19 2:30 AM, Alan So wrote: > Double check the list that have issue: > > On mailman 2, > accept_these_nonmembers is empty > discard_these_nonmembers is empty > hold_these_nonmembers have a few email addresses > > The list was imported to mailman 3 a few months ago. > > On mailman 3, > accept_these_nonmembers is empty > hold_these_nonmembers is empty > discard_these_nonmembers have a few email addresses which is the same as those in hold_these_nonmembers on mailman 2. > > Therefore the import21 seem not importing the lists correctly. See <https://gitlab.com/mailman/mailman/issues/588>. import21 should convert addresses in MM 2.1 *_these_nonmembers to MM 3 nonmembers with appropriate moderation_action and keep only regexp patterns in MM 3 *_these_nonmembers. Prior to core 3.3.0 this was not working. -- 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: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/25/21 2:20 PM, Andrew Hodgson wrote: >> Hi, >> >> Hyperkitty 1.3.4. >> >> I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. [...] >Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, >do it in pieces by adjusting start and end. e.g. [...] >Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [2021-04-26 08:53:12 +0000] [28181] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters I do still have the original mbox files for the imported lists which were on Mailman 2.1. The other thing is when downloading these mbox files I noticed they aren't the raw messages as we had in Mailman 2.1 but modified with headers stripped and email addresses modified. Is there any way to get the raw mbox back as in the option we had in Mailman 2.1? Thanks. Andrew.

3 years, 11 months

[MM3-users] Re: Your Dashboard

by Allan Hansen

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

5 years, 2 months

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

by Stephen J. Turnbull

joseverde(a)gmail.com writes: > Okay, so I got the webservice of Mailman3 up and running, It would help to know how you did that. Did you wipe the server and start over? Did you just purge Mailman3 and its configuration files? Something else? > but when I go to mailman3/postorius/lists/, I get the following error: > > Something went wrong > Mailman REST API not available. Please start Mailman core. > > When I logged in to the admin user, it threw a server 500 error, > but I could refresh and see myself logged in. The admin user is a Django concept. There isn't really one for Mailman core; it assumes you have direct access to the REST API. If you do have access to the REST API, you're the admin. So this doesn't prove anything about what core is doing or if it's running. > If I try to go to lists or mailman settings, however, I get the > error above. The webservice is two front ends, Postorius for administration and HyperKitty for list traffic archives. You mention only Postorius. Is HyperKitty running? The problem here could be several different things. Mailman core, Postorius, and HyperKitty are separate processes, communicating over TCP sockets. If Postorius says core isn't running, that just means it was unable to open a socket to connect to core. Core might be running but listening on a different port than the one Postorius expects, or it might not be running, and there are probably arcane reasons it could fail even if it's running and they have the same port configured. You can can check whether Mailman core is running in several ways, depending on what Ubuntu 18.04 uses to control daemons. If it's systemd, then "systemctl status mailman" (or maybe "... mailman3") should do the trick. If core is not running, you need to start it, and figure out how to get that to happen automatically since it didn't happen this time. If core is running, most likely either the webservice(s) or the core are misconfigured as to the port where core is providing the REST API. But we'll cross that bridge when we get to it, as there are a number of configuration files involved.

4 years, 8 months

[MM3-users] Re: How to promote non-members to members?

by Mark Sapiro

On 3/15/22 11:16, Quanah Gibson-Mount wrote: > Hello, > > We have a constant issue with confirmation emails for subscribers > getting lost and then the subscriber contacting us because their posts > to the list never show up. Is there a way I can, as an administrator, > do the confirmation on their behalf or in some other way promote them to > being a member from non-member? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… If they don't have an outstanding subscription waiting user confirmation, you can just mass subscribe them. If they do and your Postorius and Mailman core is reasonably up to date, you can find the pending request at Subscription requests -> Pending Confirmation, delete it and then mass subscribe them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Messages not going to held queue

by Stephen J. Turnbull

Mail Person writes: > Not sure why, but messages set to be held for moderation There are quite a few settings that can result in moderation holds. Which are you talking about, and exactly what is the setting? > appearing to be discarded. Have you checked the other logs? A discard should show up in the 'vette' log. If there's no notice there, the message should be stuck in some queue, my first guess is shunt, but it could be anywhere. > smtp.log shows the message is going through but it doesn't get to > the moderation queue. How do you know? Do you mean moderators don't get email that the message is held, or have you checked in Postorius and it tells you no messages are available for moderation? I believe that if the message is waiting for moderation it should be in the 'pipeline' queue. Steve

2 years, 7 months

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

by Morris Jones

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

4 years, 4 months

[MM3-users] Re: "Private archives" aren't private

by Mark Sapiro

On 06/04/2017 07:47 AM, Simon Liebold via Mailman-users wrote: > OK, no problem there: > > <QuerySet [(u'simsimmer(a)lists.simonliebold.de', 2L)]> >> >> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Just to be sure, if you are just repeating the MailingList.objects.all().values_list('name', 'archive_policy') command, you won't be seeing the current value. You have to do either abort() or commit() to flush the previously retrieved data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

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

by Mark Sapiro

https://gitlab.com/mailman/mailman/-/issues/967 is now fixed. This is the patch to fix it. See https://gitlab.com/mailman/mailman/-/merge_requests/946 ``` diff --git a/src/mailman/handlers/decorate.py b/src/mailman/handlers/decorate.py index ec0ba8ed385e529b2b4c959e41d7d8985cc783e5..53ea861de13c76d1571c3664ec8358bf9c97b4e0 100644 --- a/src/mailman/handlers/decorate.py +++ b/src/mailman/handlers/decorate.py @@ -18,13 +18,13 @@ """Decorate a message by sticking the header and footer around it.""" import re +import copy import logging from email.mime.text import MIMEText from email.utils import formataddr from mailman.archiving.mailarchive import MailArchive from mailman.core.i18n import _ -from mailman.email.message import Message from mailman.interfaces.handler import IHandler from mailman.interfaces.mailinglist import IListArchiverSet from mailman.interfaces.template import ITemplateLoader @@ -176,26 +176,12 @@ def process(mlist, msg, msgdata): # Because of the way Message objects are passed around to process(), we # need to play tricks with the outer message -- i.e. the outer one must # remain the same instance. So we're going to create a clone of the outer - # message, with all the header chrome intact, then copy the payload to it. - # This will give us a clone of the original message, and it will form the - # basis of the interior, wrapped Message. - inner = Message() - # Which headers to copy? Let's just do the Content-* headers - for h, v in msg.items(): - if h.lower().startswith('content-'): - inner[h] = v - inner.set_payload(msg.get_payload()) - # For completeness - inner.set_unixfrom(msg.get_unixfrom()) - inner.preamble = msg.preamble - inner.epilogue = msg.epilogue - # Don't copy get_charset, as this might be None, even if - # get_content_charset isn't. However, do make sure there is a default - # content-type, even if the original message was not MIME. - inner.set_default_type(msg.get_default_type()) - # BAW: HACK ALERT. - if hasattr(msg, '__version__'): - inner.__version__ = msg.__version__ + # message, with all the header chrome intact, then delete unwanted headers. + inner = copy.deepcopy(msg) + # Which headers to keep? Let's just do the Content-* headers + for h, v in inner.items(): + if not h.lower().startswith('content-'): + del inner[h] # Now, play games with the outer message to make it contain three # subparts: the header (if any), the wrapped message, and the footer (if # any). ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Andrew Hodder

I assume you mean from the command line, since mass remove can be done from the postorius interface for the list. Checking the 'mailman members -h', I don't see any options for mass removal (strange since add has a function). This might be a consequence of the way members are now tied to ownership in lists (changed from MM2>MM3). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Wed, Oct 25, 2017 at 3:08 AM, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > > I just realized that "mailman members" only offers to "add members" via > "-a filename" but I see no remove option. > > -- > Sr System and DevOps Engineer SoM IRT > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

7 years, 5 months

[MM3-users] Help with some 'withlist' configuration changes

by David Partain

Hi, Firstly, a repeat that I have a relatively broken (and soon to be fixed, I hope) installation of mailman3 based on Ubuntu 18.04 distrib packages (3.1.1-9) that stumbles along by me dealing with a bunch of things by hand that I hope'll go away once I'm up to the current version. In this set-up, I get a fair number of items shunted. Since I have this wonky version where stuff isn't always exposed in the web interface, I have to fix these things by hand. An example is that something gets shunted because of too many recipients, where I do: sudo -u list mailman withlist somemailmanlist m.max_num_recipients = 0 commit() sudo -u list mailman unshunt I've managed to find a number of these, such as m.max_message_size, m.require_explicit_destination, and m.administrivia. My questions are undoubtedly foolish, but here goes: 1. Is there any way to print the entire 'm' structure? If so, I'd perhaps be able to figure out the answers to my other questions. 2. Is there a way for me to correct the following shunt-ing issues with 'withlist'? I've been unable to figure out how... a. 'moderation_reasons': [ 'Message has no subject'] / 'rule_hits': ['no-subject'] b. Some things get caught as 'rule_hits': ['nonmember-moderation']. However, if I look in the (web-based) config, it shows that non-members should be accepted but the messages are shunted nonetheless. I don't know what to look for in 'm' or how I might clear these messages. 3. I have no idea what these are telling me to do about digest messages. Suggestions? This is the entire info I get from 'mailman qfile': ------------------------------------------------------snip snip---------------------------------------------- [----- start pickle -----] <----- start object 1 -----> <----- start object 2 -----> { '_parsemsg': False, 'digest_number': 457, 'digest_path': '/var/lib/mailman3/lists/somelist/digest.31.457.mmdf', 'lang': 'en', 'listid': 'somelistid', 'version': 3, 'volume': 31, 'whichq': 'digest'} [----- end pickle -----] ------------------------------------------------------snip snip---------------------------------------------- 4. I have some that have 'rule_hits': [] (it's empty) but are shunted nonetheless. I can't see anything weird other than one of the messages has a utf-8 subject. Any ideas? 5. Some messages that were sent to -request addresses (e.g., subscribe messages, confirm, approve messages) are being shunted. What should I do with these? Thanks for your patience. Cheers, David

3 years, 10 months

[MM3-users] Re: more about spanish translations

by Guillermo Hernandez (Oldno7)

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

4 years, 2 months

[MM3-users] Re: Template Ignored?

by Mark Sapiro

On 2/17/22 08:04, Stephen Daniel wrote: > Mailman3 people -- > > I created a new list, and used postorius to create a template for " > list:user:notice:welcome". I then used the mass subscription feature to > add myself to the list, having checked "pre-confirmed", "pre-approved", and > "pre-verified". > > I received a welcome message that appears to be the default welcome > message. It certainly wasn't what I put into my template. > > Any suggestions on how I get mailman to use my template? Things I might be > doing wrong? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a full URL by appending `/api/templates/list/list.example.com/list:user:notice:welcome` to that where `list.example.com` is the actual list_id of your list, and go to that URL, what do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Verification links to localhost

by Lars Bjørndal

[Mark] > On 2/4/23 22:50, Lars Bjørndal wrote: > > The verification link I get back when trying to add an account, referes > > to localhost, e.g. > > > > To confirm this is correct, go to https://localhost:8000/accounts/confirm-email/Mw:1... > > > > Where do I change that? > > > This message comes from Django allauth and is probably using what it thinks > is the host that is doing the add. This is based on your web server > configuration which I would need to see to be more specific. I suspect you > are proxying requests to https://localhost:8000/ and you are missing a > directive to pass the host. For Apache I think you want > ``` > ProxyPreserveHost On > ``` > and for nginx > ``` > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > ``` Thank you very much. I'm using Apache, and `ProxyPreserveHost On` works perfectly. Lars

2 years, 2 months

[MM3-users] Messages not picking up header or footer template

by benjamin＠tougshire.com

Hi I can't figure out how to get headers or footers on my messages Example: I create a footer in Postorius. The name in the form is '[list:member:regular:footer] - The footer for a regular (non-digest) message.' The data is 'Test Footer' I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… I can do a wget on that uri and download a copy of the footer, and it looks right But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message So what am I doing wrong? Thank you Ben

2 years, 1 month

[MM3-users] Re: join via webform

by Mark Sapiro

On 6/19/19 4:50 AM, mailman3(a)malevil.cc wrote: > Is there a simple possibility to join a mailinglist besider writing a mail to list-join(a)example.com? I know you can register and then join a list, but thats only possible for public lists It is also possible for unadvertised lists. You can go to `lists/list@domain` and subscribe even though the list is not advertised. > and I would like to have such a very simple webform for a specific list where you just enter your email address and then get the confirmation mail. I guess there was something like this with mailman2 You can do this by having your web form do the subscription via the REST API. See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html> and <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Moderation of posts via email is not working in mailman 3

by Shashikanth Komandoor

Hi Team, In mailman 2, few of my users used to approve the held messages through the mail by writing Approved: header and the password of the list in the first line of the reply mail to the "confirm" attachment in the mail notification of the held messages. But after I started migrating my distribution lists from mailman 2 to mailman 3, my users are complaining that they could not approve the posts or the held messages through the mail as they usually do while they were browsing their lists in mailman 2. Is there any bug or limitation in mailman 3 or if I am doing any wrong at the server side? Please suggest. -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

4 years, 9 months

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

by Abhilash Raj

On Tue, Sep 18, 2018, at 9:30 AM, 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. I was looking at the allauth docs and wasn't able to find any public API (http or python) to export/import users. So, I'd say the best way would be use a combination of Mailman's API and Django API in a python script to filter the members/users you want to export and import. You can ask here for help if you need any with writing the script, but there are good docs for Django's API and for mailmanclient too. > > -- > Sr System and DevOps Engineer SoM IRT > > _______________________________________________ > 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/ > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Mark Sapiro

On 2/5/20 9:55 AM, Shashikanth Komandoor wrote: > > With the above script I am able to set the value of max_days_to_hold as > required but how to check manually and make my held messages discarded > automatically which are after the specified period configured for > max_days_to_hold. > > If I am able to do it manually I can be confident to take in to production > so that the held messages after a specific period would not be appeared > under "held messages" tab. I'm really not sure what you are looking to do, but I can tell you that while the max_days_to_hold list attribute exists and can be set, the actual discarding of held messages older than max_days_to_hold is not implemented. Thus the setting currently does nothing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Mark Sapiro

On 2/26/21 11:03 AM, Morris Jones wrote: > On 2/26/2021 10:55 AM, Mark Sapiro wrote: >> Brian is correct. Essentially, you would need to run database queries to >> get all the relevant data from the database and then add it to the >> database of the new instance. A tool could be created to do the export >> and import, but it doesn't currently exist unless some user has >> developed one and not reported it. > > Would it be unreasonable to do a database dump on the old instance and a > restore on the new one? The question is transferring a `list`. I took that to mean transferring one of multiple lists to another installation which may also have other lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: MM3 generates long lines?

by Mark Sapiro

On 6/23/21 7:10 AM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [210623 15:34]: >> We would need to see the email itself in order to begin to >> understand if this is a Mailman issue or some issue withe the mail >> as received by Mailman. >> >> Assuming the prototype archiver is enabled, you should be able to >> find the messages in Mailman's var/archives/prototype/LIST/new/ >> directory. > > One question, in order to ease debugging, can I forcefully activate > the prototype archiver from the global configuration, or do I need to > do that on a per-list basis? You need [archiver.prototype] enable: yes in mailman.cfg. I'm not sure if that's enough for existing lists. You may need to activate the archiver per list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: EMWD Mailing Lists Down

by Jared＠emwd.com

Hey Allan and Sherry, Thank you all for starting this thread. I am a system administrator for EMWD. We are working through these issues, and we are short staffed at the moment, especially with Mailman specific issues. We will answer all tickets, but there may be some delays. We do respond to support tickets only at this time. If you were used to working through email or other ways with Brian, right now we are still sorting out that system. Sherry, Marshall responded to your ticket through the EMWD support ticket system today. Thank you for the info and we'll follow up there. Allan, the reason why we can't support your ticket at this time is that you aren't a hosting customer, and had a labor-only relationship with Brian. We do want to continue working together, but have to work with customers who are on our servers at this time. Sincerely, Jared Jared(a)emwd.com EMWD Systems Administrator

3 years, 3 months

[MM3-users] Re: Mailman3 on virtual domains

by Lars Bjørndal

[Mark] [...] > > Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? > > It has been in postorius since 1.2.0. Mine is 1.3.8. > > > I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? > > If your Postorius is >=1.2.0, there should be 3 fields on the Edit domain > page - Description, Alias Domain and Web Host. The whole page looks > something like: [...] Thanks, got it. I was confused becasue there are two Edit buttons on the prior page, one right above SITE_ID number and another (the button I had to use) inbetween Templates and Delete. Thanks a lot for your assistance! Lars

1 year, 6 months

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

by Lieuallen, Thomas Otis

I’m still wondering about mailman’s cache (cache_dir setting). I have 2x cache files under it that are 3-4 days old. These are mailman cache files, not mailman-web. # pwd /opt/mailman/mm # find cache -type f -ls 38627053 4 -rw-rw---- 1 mailman mailman 13 Feb 6 16:42 cache/26/26/2626c32ded811be4e9631d2215f32d88522b67142bf0eea502362d2b15c4743e 118392 4 -rw-rw---- 1 mailman mailman 11 Feb 7 09:42 cache/98/14/9814e4457e2489e2ec77d19ce982d3643fac3ad849c9861a9198eebf53f1fcde I haven’t figured out how to work with these cache files. I found some mention that a runner would clean up cache files after a week (default) and that one could use ‘cache_life’ to change that default. So, I set the following and restarted mailman. The cache files hadn’t been removed after > 4 hours, so I unset it and restarted again. Cache_life: 1d Without further information or direction, I’m tempted to just remove those cache files and move on with life. Thank you Tom Lieuallen From: Lieuallen, Thomas Otis via Mailman-users <mailman-users(a)mailman3.org> Date: Friday, February 7, 2025 at 1:43 PM 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.] 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://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://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 _______________________________________________ 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, 1 week

[MM3-users] Re: Installing mailman 3

by Rafael Mora

How do I tell mailman to connecto to postfix? Is mailman able to use the smtp I use for our emails service with hostgator? Instead of using postfix?? Thanks El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Hacking attempts?

by Dave McGuire

On 7/15/22 01:21, Stephen J. Turnbull wrote: > > We're getting hit with this BS all the time too. This is what > > happens when we can no longer spank our children. > > I don't think it's all script kiddies, though. I actually look at > this stuff rather than automating with fail2ban. I used to look at them, for over a year, until I got fed up with it. It was taking way too much time away from the work I was supposed to be doing. I figured that I probably wouldn't be able to find the delinquent little twats that were doing it and break their fingers, so I finally bit the bullet and dealt with fail2ban's awful configuration system. Now I just check it every week or two and see the number of blocked IP addresses steadily growing, and smile. > Among other things > there are attackers who have access to /16s and I'm not interested in > whack-a-mole *sigh*. I also follow some of the usual suspects on > Twitter (eg, @briankrebs) and I've seen at least two brand-new CVEs > show up on my site in the same week. Right now I see over a hundred individual IP addresses in 114.119.137/24 in my list, yes. > > For fail2ban, here's my jail.local entry: > > Thanks! I'm sure this will be helpful to several users. I hope so. If I can spare anyone else the pain of spending two solid hours with fail2ban's configuration-system-of-questionable-judgment, I'll count that as a win. > > I don't know if this is optimal, but it works, and it's catching > > these little idiots left and right, a few dozen per day. My platform is > > Solaris (SmartOS). > > My site is small, but I only see 0-10 (weighted to the low end) a day. > You might want to sort the blocklist and ban a few netblocks if you > haven't done that already. In one case (sorry, I forget the domain) I > ended up searching out a domain's netblocks and banning all 3 of them. Thanks, that's a good idea. Maybe I'll write a little script to do it. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 years, 9 months

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

by Mark Sapiro

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

3 years, 9 months

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

by Mark Sapiro

On 11/29/21 8:13 PM, Philippe B wrote: > I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. > > We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. > > Could someone share the instructions for doing that? Thanks. In Postorius go to the Templates tab for the list, click New Template, then in the Name dropdown select [list:member:regular:footer], leave the Data box empty and Save. Do the same for [list:member:digest:footer] if you want to eliminate that one too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

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

by Simon Hanna

Postorius is currently using this to mass unsubscribe. AFAIK there is an open issue in core to add such functionality On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/25/2017 07:35 AM, Barry Warsaw wrote: >> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >wrote: >>> >>> I just realized that "mailman members" only offers to "add members" >via >>> "-a filename" but I see no remove option. >> >> It’s true, `mailman members` doesn’t currently have a —remove option. > >I found Rest API call for single user removal but I am questioning it's >effectiveness given that I need to use this operation to potentially >remove 1500 members > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

7 years, 5 months

[MM3-users] How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Shashikanth Komandoor

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 in production environment from the past 3 months almost. I am currently automating a few things using the CURL commands but only postorius related as of now. Now I have a requirement. I need to create a lot many users and their mapping email ids through Site Administration almost daily. But it is becoming to do the same through Graphical Interface. So, I just want to know the CURL commands that can be used to create the user accounts and email ids mapped to user accounts. Please do the needful. -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

4 years, 8 months

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

by Mark Sapiro

On 5/13/21 7:25 AM, Torge Riedel wrote: > > today I upgraded one of two servers from Ubuntu 18.04 to 20.04 and - > besides some minor config updates - postfix & dovecot worked well > afterwards. > > So I am very optimistic that the upgrade of the second server from 18.04 > to 20.04 will also work fine. But the second server is running MM3 > (installed in venv) and I saw that on upgrade Python 3.8 is installed. > > Is there anything I have to take care of? Anything to do / change in venv? The venv will still run whatever Python it was built with. That's what virtualenvs are for - to isolate the software therein from external changes. You shouldn't need to do anything in the venv for Mailman to continue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/21/22 05:10, chris(a)mehl.one wrote: > Hi, > > I am running Mailman3 on Debian 11 with Apache and MariaDB. Single installation. > > When I edit a footer from the WebUI templates, it doesn't show in the messages. How is Mailman installed? If from the Debian packages, this may be a Debian issue, and you should contact Debian for assistance. > Could it be an issue with the related DB? If so - what do I need to change? I can't say without more info. Is the default footer added to messages? What do you get from the db query ``` SELECT * from template WHERE name = 'list:member:regular:footer'; ``` Assuming that returns a row with context of the list id, what is the uri and can you retrieve it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 11/4/20 12:04 PM, Stephen J. Turnbull wrote: > Brian Carpenter writes: > > > If you mean if they don't have a Django user account, they can't > > unsubscribe? > > The Django user account is more or less a proxy for the underlying > Mailman User object, which is what we're concerned with here because > that's where the data you want deleted is stored. > > > I think that is true if they are wanting to unsubscribe via > > the web interface. But sending an email to > > listname-unsubscribe@listdomain allows them to unsubscribe without such > > user authentication. Isn't that correct? > > They don't need a Django password or social auth, but they'll still > have to do the OTK dance. I don't see a reason to distinguish the > methods of authentication. They all reduce to the OTK dance to prove > ownership of a mailbox, then optional *delegation* to a password in > Django or social auth via Gmail etc. Please speak in simple terms. I am pretty sure my questions were straightforward but I have a sneaky suspicion you convoluted the issue with these replies. I feel like my questions were not answered. > > I understand that your users don't understand this or care to. Thing > is, some of *our* users care about the features that this architecture > enables. I think everyone should care that data should be removed when there is an expectation that it is being removed. > > > My intent in our changes is to give the list owner and member > > exactly what they expect: when they explicitly remove a > > subscription and/or user profile, that they expect their data to be > > totally removed. > > That's fine, and you're welcome to implement that in Affinity. In > fact, as I understand it, you have already done so. *I'm* not saying > *nobody* should implement that. > > I'm saying that *Mailman* shouldn't, because a lot of subscribers to > Mailman lists won't like it. The whole point of Mailman 3 is to cater > to users who want powerful control over their subscriptions. For > Mailman (Postorius), prompting the user "If you delete this > subscription, you will have no subscriptions linked to this account. > Would you like to delete the account as well?" (as I have proposed > three times now) is the right way to go. This can be implemented via > email with a second OTK. Since the account is a django account, I don't see why unsubscribing from a list has anything to do with that account except removing the user's prefer settings for a list that they are no longer subscribed to. For me I made this issue about those list members who unsubscribe from a single list AND does not have a django user account. This discussion has expanded to all kinds of scenarios. Those who are the power users are not in play here. I am sure they intend to to keep their subscriptions active and their django account open. I am talking about those who want to leave a list or wants to remove their django user account permanently. > > > I can easily picture a scenario where an older list has a number of > > list members move to on to other things in life > > And I can picture a scenario where they take a summer break and > reactivate a decade later. I would be *pissed off* if my data got > deleted in that scenario. (Yes, I've done that in the five year > variant, if not the full decade.) Why would you be mad? Am I missing something here? The data that is being kept are a few fields of data (email address, username, password, real-name, and some list preferences). Why would anyone expect to have such inactive accounts kept perpetually? Regardless, I am not talking about removing accounts/subscriptions without a user's permission. I am talking about when a user either does it themselves or asks a List Owner to do so. > > > and even abandon their email accounts totally. > > Which is a totally different scenario. I deny your "imperative" in > the former case; inactivity from the point of view of a list owner is > (usually) not abandonment. I question it in the latter, because > "abandon" is an inference drawn from lack of activity or bounces, > either of which could be inadvertant (respectively the "summer break" > scenario, and separation from an employer). I worded that poorly. But remember if an email address that no longer exists (because a list member never unsubscribed from a list and closed their email provider account anyways) is removed due to bounces (as it should), that user data still exists. I think that is not good and such a scenario happens a lot. > > > In those cases it is imperative that those list addresses are > > removed either via bounce processing or list owner intervention and > > that no legacy data on such members remain. > > But how do you propose to identify "legacy data"? In Mailman 3, > members are *people*, not addresses. Do you really want it to be the > case that if Albert signs up with albert(a)example.com, and later gets > fired by example.com, then all his subscriptions get bounce-cancelled, > and his User profile gets irreversibly trashed? Or some large email > provider hosting lots of posters decides to suddenly implement some > spam protection that causes a ton of bounces (as DMARC p=reject did in > 2014) and hundreds of users have their accounts trashed? It worked for Mailman 2 right? What happened in those cases? They just got resubscribed again. As you said, unsubscribing doesn't impact a django account anyways. So I don't understand your point here. Again I am talking about the scenario where a user is requesting to be removed or does the removal themselves and expects their data to be removed. > You just can't know without asking Albert what he wants done in his > case and you can be quite sure you're doing the wrong thing in the > DMARC-like case. In either case, resubscribing is a click per list if > his data is retained (and Albert needs an OTK confirmation of another > address). It's an annoying session of duplicating his configuration > (including passwords and social auth links) if not, and probably some > months of discovering that a configuration that built up over years > wasn't accurately reproduced for some lists. Apples and oranges here. For public lists and a user who does not have a Affinity/Django account, it is just a click per list. For those who have a django/Affinity account, well there account should still be there since they never asked for it to be removed or did not remove it themselves. Personally I think I am going to implement some sort of backup generation tool for an Affinity account holder where they can download their profile/list settings in a json or equivalent format before account deletion. Then if they wish to create their account, they can rebuild their profile from that backup. > > List owners, of course, can do what they want with their lists. If > they want to add automation for their subscribers that simplify the > lives of people who have simple needs, that's not something Mailman > can, should, or will try to stop. That's *why* I support efforts like > Affinity, Empathy, and Harmony. > > Steve I personally intend to get into the "power-user" market. That is the #1 reason for creating my UIs. I have that flexibility. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Possible bug in Mailman 3.1 (Docker-mailman 0.1)

by Abhilash Raj

On Mon, 14 Aug 2017 10:47:58 +0000 Henrik Rasmussen <her(a)adm.ku.dk> wrote: > Mailman 3.1, docker-mailman 0.1 > > While I was trying to automate distribution of the files > in /opt/mailman/core/var/data/postfix_domains I found what I think must be a > bug. > > Adding a new mail list (or deleting one) _does_ update the Postfix > files /opt/mailman/core/var/data/ ,but adding a new mail domain does not. > This is OK. Yes, there is no point in adding a new domain if there is no list associated with it. > > But deleting a mail domain that have lists associated to it > * does not issue a warning other than "Are you sure you want to permanently > delete this domain?" which is not different from deleting mail domains > without lists associated to it. OK, we can have a list of mailing lists that are associated with the domain in the confirmation screen and customize it say "There are mailing lists associated with this mail domain, are you sure you want to delete this? Note: Deleting the mail domain will also delete the mailing lists associated with it" What do you think? > * the associated lists disappears both from the web interface Lists view and > from the output of the "docker exec -it mailman-core mailman lists" command Yes, because the lists are deleted when a domain is deleted. > * the files in /opt/mailman/core/var/data/ is not updated even the lists is > being deleted. > > 1. Deleting a mail domain with associated lists should issue a warning that > it has lists associated to it. > 2. The files in /opt/mailman/core/var/data/ > should be updated according to the deleted lists / domains. https://gitlab.com/mailman/mailman/issues/388 Yes, this looks like a bug in Core where the transport maps are updated when a list is deleted, but it isn't if the list is deleted as a result of domain being deleted. >3. Actually I > think it should be impossible to accidentally delete a mail domain with lists > associated to it. Ok, what do you mean by "accidentally deleted" here? There is already a confirmation step when deleting a domain or list, what else do you suggest should be there? -- thanks, Abhilash Raj

7 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Is this the problem?????: # When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. if DEBUG == True: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') Shouldn't DEBUG be FALSE?? 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: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 11:48, Wikinaut wrote: > > I was "_forced_" :-) to install that in one of the very first steps of the documentation. https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… > > What I suggest is: > > I will (try to help) to fix the documentation, so that it also can work for mysql. > Please, I am willing to help. It seems to me that adding a sentence following "This will install latest release of Mailman Core, and Python bindings for Postgresql database." such as "If you are using a different database manager, do not install psycopg2-binary." would suffice. What do you think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

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

by Mark Sapiro

On 5/31/23 06:17, justfixit(a)marilynstrother.com wrote: > Very interestng! Upon restarting the system (down momentarily for taking a snapshot) and starting Mailman again, all of these missing [List] messages emerged from their timewarp and were delivered to the members / subscribers. Just before shutting down the system I discovered that the apache2 webserver had been off the air due to a module not being enabled yet. > As of yet, I was unaware of any requirement for a web server to be online (beyond possibly gunicorn) in order for Mailman to run its lists. Does that speculation have a factual basis? Or do I risk starting a vicious rumor amongst the impatient readers who are not still here once we deduce this pair of observations were merely correlated in time, with no cause-and-effect relationship? > Before this situation healed itself, the thought had crossed my mind to peek and see if anything was stuck in the queues: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > While that could have provided peace of mind that email messages were merely delayed instead of vanished, even in hindsight I do not see how that would have led to repairing the situation. I suspect if you had looked, you would have found the messages in Mailman's `pipeline` queue, and they were not being processed because the `pipeline` runner wasn't running, although it is possible that the issue was with the `in` runner/queue. It wasn't the `out` runner/queue if welcome messages were being delivered. The fact that the web server wasn't running is just a coincidence. It has nothing to do with Mailman core's processing of messages with the one exception that Mailman core needs to communicate with HyperKitty's API via mailman_hyperkitty, but this only affects archiving to HyperKitty and the addition of an Archived-At: header to messages. > In the absence of a hypothetical command: > mailman status --verbose > about which diagnostic tools or clues should I learn? Logs are possibly the most useful. You might find something in mailman.log about the death of whatever runner had died. Looking at queues is also useful. -- 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: Installing mailman 3

by Rafael Mora

I did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > 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: clicking on a username when viewing a thread results in "Page not found"

by Ken Alker

Mark Sapiro wrote: > On 6/26/23 12:20 AM, Ken Alker wrote: > > If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? > This is a problem. That link goes to, e.g., > https://example.com/archives/users/<user_id>/. What do you get if you > strip the user_id and just go to what > https://example.com/archives/users/ translates to on your system? > You should get a page saying > Not implemented > > This feature has not been implemented yet, sorry. > > If you get a 404, there is an issue with your web server configuration > or maybe your top level urls.py. I get "Not implemented". I do not get a 404 error.

1 year, 9 months

[MM3-users] virtual_alias_domains

by Johannes Rohr

Dear all, I have to set up mailman3 in an environment where postfix uses virtual alias domains. This is described in https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… I don't understand, though, what I need to do to have mailman generate $PREFIX/var/data/postfix_vmap I have tried to follow the instructions at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… with the purpose of setting an alias domain. However, things go sideways quickly: >>> from mailman.interfaces.domain import IDomainManager >>> from zope.component import getUtility >>> manager = getUtility(IDomainManager) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/mailman/venv/lib/python3.8/site-packages/zope/component/_api.py", line 165, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.domain.IDomainManager>, '') >>> So, something is missing. But, being a complete python layman, I do not know what and how I fix it. Can someone give me a headsup? That would be greatly appreciated! Johannes

2 years, 3 months

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

by Guillermo Hernandez (Oldno7)

On 18/9/21 17:22, Danil Smirnov wrote: > I think you've missed one good option to do this - by sending an HTTP(s) request to your Mailman Core. You can do it from console via curl or even from a custom web page via Javascript (if your API is exposed to the public). Sound very interesting. Tomorrow I'll take a thorough look at this Thanks a lot > The request would be quite simple - check docs at > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > You can also retrieve a list of mailing lists (e.g. for a nice UI select element) using GET /lists request: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Best regards, > Danil > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 7 months

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

by Jens Günther

Thanks Mark for the tests and your thoughts on this matter. Am 23.05.23 um 17:19 schrieb Mark Sapiro: > > That file was for a test only. The German message catalog is at > mailman/messages/de/LC_MESSAGES/. That directory should contain a > mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be > created. The source distribution contains a generate_mo.sh script to > generate these for all languages, but you can do the German one by > changing to the mailman/messages/de/LC_MESSAGES/ directory in the > running installation and doing > > msgfmt mailman.po -o mailman.mo I just checked the mailman/messages/de/LC_MESSAGES directory and there was only a mailman.po. I tried to create the mo-file with the command you provided, unfortunately it doesn't work in the running docker-container (obviously the gettext-package is missing ... and can't install it with apt, but this is another docker-related problem, shall I open another thread?). I did create on OS-level the mo-file, restarted the container and now the welcome- and goodbye-subject is indeed in German, coolio! 2 thoughts on this for me is: - Shall I create all the mo-files (the other folders also only contain the po)? If so, how would it be possible? - How can I make it persistent? (probably it should be included in the repo!? also another thread or an issue regarding maxxking's repo!?) > > I just tested, and the notice to the moderator of a held message is in > the list's preferred language including the Subject: and the moderation > reason, and the notice to the user sending a held message is in the > User's preferred language for that list including the Subject: and the > moderation reason. > > I suspect your issue is you don't have the compiled mailman.mo German > message catalog. The text is in German because it comes from templates > and you presumably do have German language templates. > Exactly. What I was wondering: for the welcome-messages I did not have explicit templates for those lists/domains/site that I wrote in German, it has to be from the predefined templates, which are stored elsewhere the in the mo-files!? (actually I don't get this point exactly but wouldn't bother, if the above works). Thanks again!

1 year, 10 months

[MM3-users] upgraded Django & flufl.lock now do not receive own postings

by Stephen J. Turnbull

Christian via Mailman-users writes: > 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. Is anybody receiving posts? Are you looking at your settings as a list subscriber, or for the address, or for your User? The first one in that list will decide what setting is applied. Most likely all of your settings are set in the User (called "global" in Postorius), but you should check to make sure. How about "receive list copies"? If you're Cc'd on the post as well as being a member of the list, setting that to "no" would prevent you from receiving the message via the list. The three levels of setting applies here too. Otherwise, we need to see logs, please. Also check your spam folder and local filters. Steve

2 years, 7 months

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

by Abhilash Raj

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)

3 years, 8 months

[MM3-users] Re: Changing posting address

by Mark Sapiro

On 11/7/18 10:59 PM, Johannes Winter wrote: > Dear list, > > I'd like to change the sending address of a mailinglist, but when I try > to set it via mmclient with > > ./manage.py mmclient > lists=client.lists > l=lists[listnumber] > l.settings['posting_address']='new name' > > > I get `ValueError: value is read-only`. > > Is it possible to change this value, or should I use another setting > for this objective? You can't change the list's posting_address. You have to change the list_name which you can't do via mmclient, but you can do via 'mailman shell'. If you want to change the posting_address without changing the list name, you can alias the desired posting address to the list_name@domain address in the MTA and add the desired posting address to the list's acceptable_aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Help! List traffic shunted to gmail/yahoo spam folders

by Mark Sapiro

On 7/10/21 2:42 PM, Matt Wilbur EFS via Mailman-users wrote: > Hello, > > I've been through DKIM hell and back. Now I'm to the point where when I > "show original" mail with gmail it says SPF, DKIM and DMARC all pass, > but it's still going to the spam folders. Does your list domain publish a DMARC record? If not publishing a DMARC record with policy of none may help, but it seems you are probably doing that. Beyond that, it is probably filtering based on something in the message content and the recipient ISPs will never tell you what because they consider that kind of information proprietary. Setting up feedback loops with gmail and yahoo also may help, but there's really not much else you can do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Apache

by Stephen J. Turnbull

Lars Bjørndal writes: > I have already Apache installed and running for mailman2 and other > resources. How do I serve mailman3 from Apache for the respective > domains? I don't understand what you're asking. Do you mean Mailman 3 serves a different domain from Mailman 2's domain? Are you planning to migrate lists from Mailman 2 to Mailman 3 for multiple domains? The main difference between Mailman 2 and Mailman 3 is that Mailman 2 uses CGIs to serve the archives and the administrative pages, but Mailman 3 uses the WSGI protocol, so you need to install additional software to manage that. There are two options: uwsgi which is a separate compiled binary, and gunicorn, which is a pure Python implementation in a separate executable. For what it's worth, the Mailman devs all use gunicorn (including on the python.org mailing lists). Then you configure access to Postorius and HyperKitty using a ProxyPass to the WSGI service for Mailman 3 rather than invoking CGI binaries directly as in Mailman 2.

2 years, 3 months

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

by Mark Sapiro

On 7/28/20 1:07 PM, joseverde(a)gmail.com wrote: > [Does your systemd script set the user to the Mailman user, and does the > Mailman user have read/write permission on Mailman's var/locks/?] > > How do I check for that? ls -la /path/to/mailman/var/locks > Also, what's the difference between the mailman command and the systemctl mailman3? Are they the same processes? Presumably your mailman3.service actually uses the `mailman start` command to start Mailman. The `mailman` command is a shell with many subcommands for various purposes including starting and stopping Mailman. > Oh and does the /3.1 matter at the end of the Rest url for Django? Do not put the 3.1 at the end of your MAILMAN_REST_API_URL. Postorius adds it. See <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 16:41 schrieb Brian Carpenter: > On 8/27/20 10:33 AM, Sebastian Hagedorn wrote: >> In case it matters, I'm trying to moderate the list using the "root" >> account. Discarding works, but when I try to either accept or reject a >> message, there is a timeout. > > Is there an error message displaying in Postorius or do you receive an > Apache timeout error? Neither. The browser times out. >When you say root account, do you mean the Django > superuser account? I guess? It's the one I created using "python manage.py createsuperuser". > Also have you made sure all of the permissions are > owned by the mailman user in /opt/mailman? Right now everything is running as root (except for Apache). I realized too late that I should've used a mailman user. Could that be the reason for the issue?

4 years, 7 months

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

by Dan Caballero

Thanks for the quick reply. We have over 2000 lists but a relative few receive large amounts of spam or unusual amounts of messages which aren't intended to be delivered to list members. We've been using Mailman for decades so there's been a lot of creative applications for the system which do not correlate to a standard discussion list or listserv. I'm currently removing 2800 messages from one such list via Python shell and it's been going for 16 hours now. It's only half done. I had previously increased timeout settings so that Postorius would not cause a browser timeout. That helps the vast majority of our list owners/moderators do what they need for small batches of messages. I'll try replicating this latest issue in my test environment where logging is easier to inspect. I'll follow up with my findings and more questions. Thank you!

2 years, 5 months

[MM3-users] Re: DMARC DNS settings for MM3?

by Mark Sapiro

On 1/30/22 20:25, Jay Hamilton-Roth wrote: > Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). > > Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. > > Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). > > MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: > > v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com > > -or- > > v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com > > -or something else- Have you seen https://wiki.list.org/DEV/DMARC ? Nothing you publish as a DMARC policy or SPF will affect the DMARC actions of recipient domains for list mail unless you set DMARC mitigations for your lists to make the mail be From: your domain. As long as you leave the From: intact, it is the DMARC policy of the From: domain that counts, and if you make any transformation at all to the message (content filtering, subject prefixing, munging Reply-To:, etc) you will break the From: domain's DKIM signature and DMARC will fail at the receiving MTA. As far as recommendations go, what we do for this list for example is we set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to No. We publish SPF "v=spf1 mx a ~all" We publish DMARC "v=DMARC1\; p=none" and we DKIM sign all our outgoing mail. Our Python.org lists are similar except we publish DMARC "v=DMARC1\; p=none\; pct=100\; rua=mailto:rxxx@dmarc.postmarkapp.com\; sp=none\; aspf=r\;" because we've signed up with postmarkapp.com for their free reporting service. We do publish a DMARC policy and DKIM sign outgoing mail because we believe this helps mail delivery, but without DMARC mitigation action = Replace From with list address or Wrap the message ... it won't stop recipients from treating list mail as failing DMARC. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/26/23 10:12 PM, Ken Alker wrote: > --On Monday, June 26, 2023 5:03 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> Your urls.py file probably contains in its urlpatterns list >> ``` >> re_path(r'^mailman3/', include('postorius.urls')), >> re_path(r'^archives/', include('hyperkitty.urls')), >> ``` >> The simplest fix is to add >> ``` >> re_path(r'^postorius/', include('postorius.urls')), >> re_path(r'^hyperkitty/', include('hyperkitty.urls')), >> ``` >> to that list. > > I see many ursl.py files all over the system, but none that appear to be > where I'd expect them to be for processing by any executables. Is this > a file I should have copied over and edited, or created from scratch and > somehow missed? I don't see anything about it in the instructions at > <https://docs.mailman3.org/en/latest/install/virtualenv.html> (although > I do see a post from last July from someone stating it got missed in the > instructions back then). In your case, it is the one in /opt/mailman/venv/lib/python3.x/site-packages/mailman_web/, but it is not a good idea to change that as changes will be overwritten when mailman_web is updated. It's OK to not change it. Just do the following. >> Another way to fix this is in your mailman-hyperkitty.cfg, you have >> ``` >> base_url: https://lists.netlojix.com/hyperkitty >> ``` >> Change that to >> ``` >> base_url: https://lists.netlojix.com/archives >> ``` > > Done, and restarted both services, but I'm not seeing a difference when > I go to <https://lists.netlojix.com/hyperkitty/api/> (I was getting a > "Page not found", and still get that). That's because going to the 'hyperkitty' url won't work, but nothing should be doing that so it's OK if it doesn't work. Fixing mailman-hyperkitty.cfg will tell mailman-hyperkitty to use the 'archives' url, so now it should be working. The next post after you fixed it should archive OK and all the messages in /opt/mailman/mm/var/archives/hyperkitty/spool/ should also be archived and the files removed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Mailman3 not delivering list mail

by Gordon Dickens

Hello, I have a fresh mailman3 installation that I recently upgraded from mailman2 on a debian system.Â In any event, I imported some test lists and tested my installation thoroughly and everything seemed to be working fine.Â Then, today, I imported a important live working mailing list from mailman2 and everything appeared to go well both with the import of the list addresses and the archives.Â However, when I sent out the first post on Mailman3 the post was not echoed to the list members.Â Then, I subsequently discovered that the queue had lots of mail undelivered in /var/lib/mailman3/queue/bad. It appears that my mailman3 installation has stopped delivering list mail and that all of the list mail is stuck in /var/lib/mailman3/queue/bad. How do I resolve this situation?Â Can I just remove the files with "rm *" in the /var/lib/mailman3/queue/bad directory?Â Please let me know what I should do to get things working again. Thanks, Gordon

4 years, 6 months

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

by Thomas Schachtner

Mark Sapiro wrote: > On 1/22/24 13:05, Thomas Schachtner via Mailman-users wrote: >> Hi there, >> >> But that's not the full deal. Postfix needs access to some hashed >> configuration files containing the transport maps and the domains of >> the mailman installation, and mailman needs the contents of the >> postfix configuration file. > > Why do you think Mailman needs the contents of the postfix > configuration file.. I don't think so. I thought so, as mailman does not start if there's not /etc/postfix/main.cf file is there. The following messages are logged: Jan 23 21:20:35 mailman mailman3[491404]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Jan 23 21:20:35 mailman mailman3[491404]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted If /etc/postfix/main.cf is there, mailman is starting perfectly fine. But in another anwer I learned that mailman might not need the contents of that file but rather change it (although I did not see any changes). > >> As a quick and dirty solution, I've established a process which >> periodically copies the /var/lib/mailman3 directory from the mailman >> box to the postfix box using rsync. > > It appears you are using the Debian/Ubuntu package or at least have > configured `layout: fhs` in the `[mailman]` section of mailman.cfg. > This is OK, but in any case, all Postfix needs is > /var/lib/mailman3/data/*. Thanks for this information. I already thought so, but I was not sure. Yes, I am using the Debian package. I also found the line with 'layout', but it reads 'layout: debian'. They write: "You should not change this variable" > >> But I would like to have a more professional solution, like a >> directly shared directory between both. >> I did not yet find any suggestions on how to achieve this. Are there >> any best practices recommendations? >> I already tried sharing the directories using sshfs, but that did not >> work. >> >> I connected the remote directory >> postfix.example.com:/var/lib/mailman3 to my local directory >> /var/lib/mailman3 using >> >> sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 > > > I would suggest the opposite. I.e. on the postfix machine > ``` > sshfs user@mailman_machine:/var/lib/mailman3/data /var/lib/mailman3/data > ``` There are two reasons why I would like to do it the other way around: (1) I would like to make all changes on the mailman3 box and change as little as possible on the postfix server and (2) mailman is running on a system which does not have a fixed IP address. Mounting the file system from there can become complicated, as the IP address can change on a daily basis... >> This seemed to work pretty fine, as all files and directories seemed >> to be available, but when starting mailman 3, the following error >> message was shown: >> FileExistsError: A race condition might have happened. >> /var/lib/mailman3 actually exists and is not a directory. >> >> Any idea why this message is shown? > > Possibly because the uid and gid of /var/lib/mailman3 on the postfix > machine do not map to the appropriate Mailman uid and gid on the > mailman machine. You refer to the uid and gid of the "list" user? They are both 38 (uid and gid) on both machines. > >> So, is it a bad idea to use sshfs? > > > If you do it the other way, it might work. > I try to work around the changing IP address challenge then. Thanks! Tom

1 year, 3 months

[MM3-users] Re: New domain cannot set set host

by Alain D D Williams

On Wed, Nov 27, 2024 at 12:42:41PM -0800, Mark Sapiro wrote: > On 11/27/24 12:18 PM, Alain D D Williams wrote: > > > > But it is not in table mailman3web.django_site > > > > Please how do I do this ? > > Add the domain as a site in the Django web admin UI. I did not see this y/day and created the entry in table django_site using SQL. This might be the cause of the other problems that we have been talking about. I must admit to finding django daunting -- something that I know nothing about; I ran "mailman-web --help" and was non the wiser. I found the following which did not help either: https://docs.mailman3.org/en/latest/django-primer.html -- 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. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

4 months, 3 weeks

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

by Odhiambo Washington

On Thu, Dec 26, 2024 at 1:27 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On December 25, 2024 2:01:27 PM PST, Odhiambo Washington via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > members --role nonmember LISTSPEC | wc -l > > 13 > > What do you get if you do > ``` > mailman shell -l LISTSPEC > ... > >>> len(list(m.nonmembers.members)) > (venv) mailman@eu:~$ mailman shell -l LISTSPEC 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 LISTSPEC mailing list In [1]: len(list(m.nonmembers.members)) Out[1]: 873 In [2]: -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 months, 4 weeks

[MM3-users] Re: Mailman 3 Installation Assistance

by Simon Hanna

On 04/04/2018 03:31 PM, brian(a)emwd.com wrote: > Ok I am trying this again. I am not sure why my last questions were not answered. Please let me know if I am doing something wrong in asking them. Here they are again: > > "Please explain "You'd have to manually change the docker-compose.yaml file to use > the on-host database though." Even though I run docker-compose-mysql -d I still need > to update the docker-compose.yaml file? See that is confusing for me. Again it is probably > due to my inexperience in using docker." > > I think that is a legitimate question. There are two files being referenced here. If docker-compose-mysql.yaml has the correct setup then why do I need to manually change the docker-compose.yaml? It seems both files perform the same function except one references a Postgre DB and the other a MySQL DB. > The docker-compose files run a database inside a docker container as well. The difference between the "normal" and mysql version is the database being used. If you wish to run Mailman using docker with a database on the local host (not in a container) you will need to update the docker configurations to reflect that. The stuff you would need to change is: * remove the database container from the compose file * update the credentials to be able to connect to the database running on the host DATABASE_URL and DATABASE_TYPE. Note that each one of them exists twice! There is no easy way to get the private IP address of the docker host in the compose-file. So you'll have to patch that in somehow. Here is an issue with pointers on how to do that https://github.com/docker/compose/issues/4092 As for your other issue: You don't need to setup anything yourself if you want to use docker for everything. It autocreates everything for you. You should change the credentials though before running it... You are having trouble finding information because you want to partially use docker but leave the database on the host. If you want to tinker with how Mailman is supposed to be deployed using docker we can't start to document every possible thing you might want to change. If you have specific issues with how to run them after reading https://asynchronous.in/docker-mailman/ please mention mention what part needs fixing/explanation

7 years

[MM3-users] Re: Hyperkitty CPU usage

by Abhilash Raj

On Fri, Apr 26, 2019, at 8:14 AM, Alain Kohli wrote: > Hi > > I have hyperkitty running and noticed that the process 'python manage.py > runjobs minutely' is running for over 70h now and is constantly using > 100% of a CPU core. That can hardly be intended, but I don't know why > it's doing that. As far as I could see, this job mainly updates the > search index. Running 'python manage.py rebuild_index' only takes about > an hour, though, so I don't see why this would take so much longer. The > text search is not working in the first place, so that might be > connected as well. I'm currently running the v1.2.2. Do you see any errors in the logs? > > Regards, > Alain > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 11 months

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

by Dmitry Makovey

Thanks for fast response Abhilash! See inline for responses: On 3/18/19 9:24 AM, Abhilash Raj wrote: > On Mon, Mar 18, 2019, at 9:14 AM, Dmitry Makovey wrote: >> In the last couple of month we've observed some odd behavior from MM3 >> (namely the core) where it seems like email that is about to be sent to >> a large-ish mailing list (10K users) has been processed yet never gets >> sent out until we restart the core. > > This is indeed weird, I don't think 10k is too much, but it also depends > on your MTA. How fast do they allow sending emails and if there is any > rate limiting. I'm using Mailu.io for MTA. We're controlling it so there's not much throttling as I've whitelisted mailman to send anything over LMTP. > I wouldn't necessarily consider this a performance problem in Core, > since it is still just processing only one email. All it needs to do is > send them all out, which is where the problem should be. inferred assumption is that mailman-core loses LMTP connection with Mailu stack. but then upon restart of service it regains it? > I'd imagine debug logging on outgoing runner should give some more > pointers on what is going on. > > You can configure the smtp runner to log extra information (copied from > docs)[1] > > [1]: > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html awesome - I'll give it a go. thanks for the pointer. > I'd also recommend looking into MTA logs for anything un-usual. we briefly did , but nothing stood out. >> troubleshooting/digging before I just restart the core (which by the way >> takes about 45min to fully start... which is another puzzle to solve at > > How do you measure that it takes 45 mins to start? normally it's "docker ps" command output along with "docker top" so once I see all the sub-processes kicked off I'm assuming core is started and from that point it's anywhere between 35 and 45min before I can get any *response* from core (i.e. mailman-web complains, REST commands fail, etc.) > What database backend are you using? Postgres. The whole setup is docker-setup (0.1.7 version of containers at this point). -- Sr System and DevOps Engineer SoM IRT

6 years, 1 month

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

by Quanah Gibson-Mount

--On Friday, March 13, 2020 9:41 AM -0700 Abhilash Raj <maxking(a)asynchronous.in> wrote: > dump_json is a documentation helper method which doesn't do much except > calling the URL and dumping the returned json in a pretty-printed fashion. > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/documentation.h > tml The point is more that the documentation at this URL: <https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/usermanager…> makes repeated use of the dump_list function, and while it shows you a variety of bits to import, it doesn't include the bits necessary to make use of dump_list, so if one is going off the documentation, all they get is errors. But really, the documentation needs to be updated further to point out the the Django ADMIN INTERFACE as the best way to do user management, and not the python shell. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 1 month

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/16/21 9:59 PM, Mark Dadgar wrote: >> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >> >> Error messages below. >> >> rebuild_index fails with the same error. >> >> This is with django version 3.0.12. > > > django.utils.six was removed in Django 3.0. See > <https://pypi.org/project/django-utils-six/> for a work around > replacement. I.e. in your venv do > > pip install django-utils-six OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. I really appreciate the support of this community in general and you in particular, Mark. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 2 months

[MM3-users] Re: Python 3.9 support

by Mark Sapiro

On 2/24/22 14:01, dancab(a)caltech.edu wrote: > > Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Because Mailman's "out" runner (/opt/mailmanve/lib/python3.9/site-packages/mailman/runners/outgoing.py from the above traceback) is what hit the exception and died. The master watcher should restart it, but see https://gitlab.com/mailman/mailman/-/issues/898 > Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Something like ``` ps --ppid=`cat /opt/mailman/mm/var/master.pid|tr -d '\n'`|wc -l ``` will report the number of child processes of the master. You could test that against the expected number and do something. Note that `mailman restart` probably won't start a runner that died - you need to do `mailman stop;mailman start` to be sure. -- 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: Changing subscription address

by Stephen J. Turnbull

Andreas Barth writes: > To make it more complex (perhaps?), I'd like to switch django to use > the single sign on-system, which means: mail adresses and user > accounts are managed elsewhere, and djano / mailman / whatever > component consumes accounts (and verified mail adresse) from the > central account store. Django *is* our single-sign-on system, and Mailman core *is* our central account store. That's why it's possible to mix and match Mailman core with other UI applications. This has been proved in practice by at least one commercial service. That is, we don't do *any* authentication in Mailman core. And because authenticating general Internet connections is *hard*, we want to keep it that way![1] ;-) The single exception is the mail address verification dance, which is an extremely simple protocol with a well-known threat model that nobody can do anything about (somebody who can read your mail).[2] So we delegate authentication and credentials management to Django, which already knows how to do passwords, OAuth and friends, and probably multifactor, too. That's *all* that the Django account functionality does for Postorius.[3] All the other user and admin information that Postorius exposes are ultimately backed by queries to Mailman core's REST API, not by Django's internal database. This subthread is 100% about how to initialize the Mailman core user record in a way more consistent with user expectations. The other, closely related subthread is about presenting tables of subscriber data for multiple subscriptions, instead of requiring people to visit per-subscription pages. There's no need to change the division of labor between core and Postorius to implement either. Steve Footnotes: [1] We probably can't, in the long run. People definitely want Mailman systems distributed across multiple hosts, and there are limits to how well that can work with all the hosts behind a firewall. That implies authenticating connections to the REST API endpoints. [2] Technically, in theory we could encrypt the verification email in case there's a miscreant-in-the-middle who can read plain text, but then we've got a key distribution problem and a user education problem. Encryption is like regexps but worse: whenever you have a problem and you adopt encryption as the answer, now you have *three* problems! :-P [3] I'm not sure about HyperKitty. Mailman core doesn't know or care about web preferences, so I suppose HyperKitty has to store them somewhere.

4 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

What should I do to tell Postfix to use my domain?? for example send emails using the email account mailing(a)labbrands.com Thank you El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Virtual alias + shell

by alopez＠ac.upc.edu

Hello, I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? The code I use in the shell is: mailman shell from mailman.interfaces.domain import IDomainManager from zope.component import getUtility manager = getUtility(IDomainManager) from operator import attrgetter def show_domains(*, with_owners=False): if len(manager) == 0: print('no domains') return for domain in sorted(manager, key=attrgetter('mail_host')): print(domain) owners = sorted(owner.addresses[0].email for owner in domain.owners) for owner in owners: print('- owner:', owner) manager.add('example.edu',alias_domain='x.example.edu') show_domains(with_owners=True) exit() Thanks in advance Albert

1 year, 10 months

[MM3-users] Re: Configuring ARC with multiple domains in Mailman3

by Lance A. Brown

I found a solution by arranging for outbound mail to go through a dedicated service which handles the ARC sealing and such-like for me. It's working nicely! I was even able to turn off the DMARC munging on my test list without problems. --[Lance] Stephen J. Turnbull wrote on 2/5/2025 7:54 AM: > It shouldn't be. It should be configured in your MTAs. Mailman can't > do SPF, and it can't make the decision to distribute or not based on > ARC validation without a preexisting ARC-Authentication-Results field > from your host. Neither of those is fatal, but implementing in the > MTA is preferable. > > ARC was originally added as a proof of concept. But I have to admit > setting it up in Mailman is easier than doing it in the MTA, it's not > as easy as throwing a switch in Postfix or Amavis (although it should > be!)

2 months, 2 weeks

[MM3-users] Re: Run 'manage.py makemigrations' to make new migrations

by Victoriano Giralt

On mié, 2022-06-29 at 10:17 +0530, Abhilash Raj wrote: > > > On Wed, Jun 29, 2022, at 2:21 AM, > christopher.claus(a)tgcamberg1848.de wrote: > > Hello together, > > > > at startup of my docker-container with mailman 0.4.3 i got some > > warnings to apply some data-model-migrations. I´m very unfamilar > > with python and django and be not sure how to handle it. Are these > > warnings from mailman and should i migrate the data-model (and > > how)? Or should i ignore these message for keeping mailman in a > > safe state? The warnings can be "safely" ignored. See below. > This might have something to do with the newer Django versions being > pulled in during the build. Given that they are warnings, I don't > think they will affect data. But regardless, can you open an issue on > Github to track this? We want to make sure that either we downgrade > Django or make sure affected components are updated to properly > support new versions of Django. > > I can take a look a bit later to see what's this new W402 check that > was added. The version of Django that introduced this (W402) warning is not so "new". It was introduced in Django 3.2. The "id" field that is the default primary key for those objects that do not have a explicit one defined (usually most objects) has changed from AutoField (32 bit integer in most setups) to BigAutoField (64 bit integer). That means that the number of possible objects has dramatically increased. What's the problem: if you do not explicitly define the type for the auto fields (in settings.py, for example, as DEFAULT_AUTO_FIELD), BigAutoField will be used, and that migh overflow your database columns for the id fields if you have big enough number of objects of a given Class. This is basically why a migration is needed, to change the type of the "id" columns to be able to accept 64 bit integers. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

2 years, 9 months

[MM3-users] Re: Outgoing messages fro Mailman fails DMARC

by Henrik Rasmussen

> On 04/10/2018 06:53 PM, Mark Sapiro wrote: > > I'm not sure I understand what you are saying. Mailman's (both 2 and 3) > DMARC mitigations allow modifying the outgoing message in some or all > cases so the From: domain is the list's domain so the message won't be > dealt with by the recipient MTA according to the original From: domain's > DMARC policy. > > See <https://wiki.list.org/DEV/DMARC>;. Also, > <https://wiki.list.org/x/17891458> may be of interest. 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. Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? Henrik Rasmussen

7 years

[MM3-users] Re: Reduction of spam - FROM_LOCAL_HEX

by Odhiambo Washington

On Tue, Oct 31, 2023 at 11:56 AM Kyriakos Terzopoulos < kyriakos.terzopoulos(a)gmail.com> wrote: > Hi, > > After fixing all issues with mailman I want to reduce the chance for email > being marked as spam, especially from Gmail. I have added SPF and DKIM > records and I am now using dkimvalidator to debug the emails being sent. > Here is what I'm getting from spam evaluation: > > *0.3 FROM_LOCAL_HEX From: localpart has long hexadecimal sequence* > > My guess is that the From address is very large, for example: > > mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu > > Is there any way to mitigate this problem? > Since mailman is doing what it is supposed to, and doing it correctly, I am not understanding what you want. Is Gmail classifying that email as spam? -- 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, 5 months

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

by Mark Sapiro

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

4 years, 8 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 6:30 PM, maszap(a)tin.it wrote: > Hi, > > you say I have to delete these lines? > > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_gid_maps = static:5000 > virtual_mailbox_base = /var/vmail > virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_mailbox_domains.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > virtual_transport = lmtp:unix:private/dovecot-lmtp > virtual_uid_maps = static:5000 I say you have to understand what you want Postfix to do and configure it appropriately. I am not a primary resource for Postfix support in general. I will help you to the extent that I can, but you might be better off posting to a Postfix list. I would need much more information in order to know how your Postfix should be configured, and in any case, I don't have time to do any more today. -- 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: My list has been switched from public to private archives, but they are still visible

by Enrique Terrazas

Thank you Abhilash, I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Regards, Enrique On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: I am having a very similar issue. Here is what I have found: There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings Archiving and they are: Public archives Private archives Do not archive this list This is interface of Mailman to set the archives. In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists Mailing List object(x) > Archive policy: never private public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. Enrique On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: Can anyone help with this? I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now) This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core. I have made a change which should fix this problem and the process would become synchronous. You can run `python manage.py runjobs --daily` command to force sync that information. https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… Am I misunderstanding what a private archive is? Not really, your expectation is right. Is something wrong with my setup (which is hosted)? Thank you. _______________________________________________ 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 7 months

[MM3-users] Re: Docker Installation of Mailman -- The Hyperkitty Chronicles

by Abhilash Raj

On Sat, Dec 22, 2018, at 6:08 AM, brian(a)emwd.com wrote: > Using Maxking's docker project to install mailman3, I have a fairly > functional mailman3 installation. However Hyperkitty is not archiving > or showing list participants like: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This is my page: > > https://mailman3.emwd.com/hyperkitty/list/testlist@mailman3.emwd.com/ > > The docker documents really don't say much about getting HK up and running. You don't need to do anything to make HK work. What do you see in the logs? Check /opt/mailman/web/logs/ for Mailman-Web logs and /opt/mailman/core/var/logs for the logs of Core. There must be some errors showing up, causing emails to not be archived. > Brian > _______________________________________________ > 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, 4 months

[MM3-users] Problem with languages

by Jens Günther

Hey, I set up Mailman3 from the Debian-packages and got it working. But for some reason I do have a mixed setup in languages now. Some strings are in English, some are in German. The settings I changed are: in mailman.cfg [mailman] default_language: de in mailman-web.py LANGUAGE_CODE = 'de-DE' TIME_ZONE = 'Europe/Berlin' Nothing changed after restarting services. I then came across this post: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -> but actually I do not find any of the files, ... - no mailman.po / .mo - no generate_mo.sh - no languages folders in /usr/lib/python3/dist-packages/mailman/messages - when searching with locate (after updatedb) no LC_MESSAGES/mailman or anything stated in the post Actually it would be fantastic to be able to choose language for the web interface / lists like on this here, but this is additional :-) just to have it in one language, this time German would be cool. I also would translate, but it seems finished: https://hosted.weblate.org/projects/gnu-mailman/mailman/ Thank you for help, regards, Jens.

4 years, 1 month

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

by Odhiambo Washington

On Sat, Nov 18, 2023 at 1:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/23 00:51, Odhiambo Washington wrote: > > > I am scratching my head bald trying to figure out how to bring in this > > other MM3 site and list into my existing server, especially with regard > to > > the DB backend. > > > > The list - let's call it users(a)domainX.name was using MySQL backend and > > had a separate DB for Mailman core and Mailman web. > > I believe combining these into one isn't a problem. But getting to merge > > this DB into my current one is what I am not sure about. > > This is https://gitlab.com/mailman/postorius/-/issues/13 which is a real > need, but doesn't yet exist. > > I think the easiest thing for the archives is to forget the Mailman web > DB and just export the archive as a mbox from the other site (if it's > large, exporting the entire archive will time out so you have to do it > in pieces). Then you can use hyperkitty_import to import it. > What is the command to export the archive as a mbox from the DB? I can't figure out which option it is by looking at 'mailman-web -h'. > For the list data, it's probably easiest to just create the list > manually and go through the settings in Postorius and make them match, I want to go with the above. although you could dump the mailinglist table entry where list_id = > 'users(a)domainx.name' and load that, but you'd need to edit the id field > in the dump to match the id on your server. Not going with that. > That leaves the members. Given that I have a dump of the two DBs (mailman and mailman-web) I just created one DB and imported them. I have been able to dump the members into a text file. Now importing is not a problem. BTW, how will ' mailman addmembers' treat a file containing: ``` Firstname Lastname <email@address> Onlyname <email2@address> ``` ? > Doing this with a DB dump/load would be very complex because while the > member table has a list_id field which is the id of the list's entry in > the mailinglist table and can be used to select the relevant members, > these records also link to entries in the address, preferences and user > tables and matching them would be an issue. > I am also not taking that path. I think a custom script would be required. If I were doing this, I would > make a separate database on my server with a copy of the data from the > other server and then try to make a script that would extract data from > the other database and add it to mine. Alternatively you could just dump the members from the other servers > with the `mailman members` command perhaps separately for regular and > the different digest types and then add them with the `mailman > addmembers` command. This wouldn't get all their attributes, but it > could work. > I have opted for the simple way to do this: 1. Create the site in Django Admin and create/configure the list in Postorius 2. Add the members from the file dump, with delivery set to regular. 3. Send the members an email informing them that they need to set their delivery preferences. I am stuck on the issue of exporting the archives to mbox file as already stated above. -- 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, 5 months

[MM3-users] Re: LMTP on unix socket

by Mark Sapiro

On 10/20/19 3:55 PM, Hristo Venev via Mailman-users wrote: > How do I configure mailman to use a unix socket for lmtp connections? > Setting > > [mta] > incoming: mailman.mta.null.NullMTA > lmtp_host: /path/to/socket > > does not work. Mailman still tries to create a TCP socket. You can't do this. Mail Delivery is to Mailman's lmtp runner which uses the LMTP class in aiosmtpd <https://aiosmtpd.readthedocs.io/en/latest/> to create an LMTP server which listens for tcp connection on lmtp_host:lmtp_port. You would have to modify mailman/runners/lmtp.py to listen on a unix socket. The docs imply the aiosmtpd.controller.Controller class has a make_socket() method which "allows subclasses to customize the creation of the socket before binding" which I suppose could be used to create a unix socket, but mailman/runners/lmtp.py currently doesn't make use of that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Something wrong in Django admin interfaces

by Franklin Weng

Hi, Since both Mark and Danil kindly told me that my wish to disable web anonymous account registering requires new version of mailman and django-mailman, I found that newest Debian bookwarm (12) has * mailman 3.3.8-1 (including mailman3-full and mailman3-web 20200530-2.1) * python3-django-mailman3 : 1.3.9-1 * python3-mailman-hyperkitty : 1.2.1 So I re-installed mailman3 (and took notes so that I could write a blog). After installing that, I found that it has problems in django admin page. When I clicked any features like users, Mail domains, Failed tasks... anyone, no matter New or Change, the web page was covered by the first page. All the configuration fields/labels are covered by the first page. Please see the screenshot: https://nextcloud.slat.org/index.php/s/e5KKEEbqDK6DpiN https://nextcloud.slat.org/index.php/s/nLgMRQ9ACyxCwoc It was not able to do the administration tasks. I looked at django-mailman issues https://gitlab.com/mailman/django-mailman3/-/issues but didn't find anything useful. Does anyone have similar issues? What can I do to solve this? Thanks, Franklin

1 year, 9 months

[MM3-users] GNU Mailman condemns reinstatement of RMS

by Abhilash Raj

To the Mailman community, The GNU Mailman Steering Committee condemns the reinstatement of Richard M. Stallman (RMS) to the Board of the Free Software Foundation (FSF), and has taken the following actions: 1. On behalf of the GNU Mailman project, signed the letter on GitHub[1] calling for the removal of the entire FSF Board, as well as RMS himself. 2. Started exploring ways to move our financial assets, for decades managed by the FSF, to new management. The management fees are small, but this is an important symbolic protest. 3. Started exploring how to leave the GNU Project. On the one hand, if we leave but GNU wants to maintain a "GNU Mailman" project, we cannot stop them, confusing users. On the other hand, RMS is leader of the GNU Project, and has intervened in Mailman affairs on many occasions. We should forestall this in the future. We wish to explain our actions to the community. Although free exchange of software among users is a practice that goes back to days of the earliest general purpose computers, RMS was the first to propose a complete free software distribution, and is the acknowledged founder of the Free Software movement. Even leaders of the Berkeley Software Distribution (BSD) acknowledge this. We all owe him a debt for this. Nevertheless, the movement has matured and thrived, spawning the competitive open source movement, with whose philosophy Mailman is more closely aligned. While we acknowledge our debt to RMS, we don't need him any longer. And unfortunately, he has become both a symbol and a source of the toxicity in tech communities. The FSF Board did the right thing by accepting RMS's resignation. They did the wrong thing by reinstating him. RMS has a long history of abusive behavior and toxic political positions. A small part of it is described in the open letter on GitHub[1] and its references[2], and several members of the Steering Committee have observed it directly. All of us have heard stories directly from those who were abused or observed it directly. His political positions are public, for example his support of pedophiles. He claims that he in no way supports abusive relationships with children, yet refuses to acknowledge that children are generally in no position to provide consent, an evasive and highly toxic position. There is no question: RMS is toxic. We came for mailing list management, but we stayed for the community. We have a right to protect our community by dissociating it from toxic influences. We do not want our project associated with such a person, nor to provide economic resources to organizations that promote him to leadership positions. We are taking these actions to protect our community, both the narrow community of Mailman developers and users, and the broader open source community, from his toxic behavior and from the reputational damage that will come from helping to enable him. While we have no information suggesting that other members of the FSF Board are similarly toxic as individuals, as a group they enabled RMS for decades, and now have taken an explicit step in enabling him again. If they want to regain their position of respect and acceptance in our community, they must acknowledge their error, and we don't see -- given their reinstatement of RMS himself -- how they can do so convincingly while maintaining their positions on the Board. They must resign, and a new Board composed, to demonstrate their sincerity. What they do is up to them, of course, but if they do not take radical steps, we will continue to consider association with the FSF a threat to our community. For the Mailman community, Abhilash Raj (project leader) Mark Sapiro Stephen J. Turnbull Aurélien Bompard Terri Oda Barry Warsaw John Viega (founder) [1] Text and signatures: https://rms-open-letter.github.io [2] Appendix to the letter: https://rms-open-letter.github.io/appendix Related statements: https://rms-open-letter.github.io/statements

4 years

[MM3-users] Re: Verification links to localhost

by Lars Bjørndal

Hi! You wrote: > On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <[1]lars(a)lamasti.net> wrote: > > Hi, and than you for your quick reply! > > You wrote: > > > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1][2]lars(a)lamasti.net> > wrote: > > > > The verification link I get back when trying to add an account, > referes > > to localhost, e.g. > > > > To confirm this is correct, go to [2][3]https://localhost:8000/ > accounts/ > > confirm-email/Mw:1... > > > > Where do I change that? > > > > > > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings? > > I don't have this variable anywhere in /etc/mailman3. However, I found it > here: > > ./venv/lib/python3.10/site-packages/mailman_web/settings/ > mailman.py:POSTORIUS_TEMPLATE_BASE_URL = '[4]http://localhost:8000' > > In which config file should that variable be set, and how do I set it so > that mailman can works for multiple domains? > > > Because it is still too early in your quest to get to run Mailman3, I'd advise > that you take your time to follow this guide: > [5]https://docs.mailman3.org/en/latest/install/virtualenv.html# > It is the official installation guide. Yes, I've followed it, maybe with some errors. > There is a step where it tells you to create a file named settings.py, in a > particular path. You really need that step. Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't have the variable in question. > Regarding your question about multiple domains, that is already well taken care > of when you create a list either via Postorius or the cli: > (venv) [mailman@gw /opt/mailman]$mailman create [6]list1(a)domain1.name > (venv) [mailman@gw /opt/mailman]$mailman create [7]another-lis(a)domain2.name > > Mailman will know how to handle this in conjunction with your MTA. That's right. But, still, when I set the SITE_ID = 0, I get an server error when trying to connect. I also get mail from Django that states the error. I'm not sure how to fix it. Thanks, Lars [...] > References: > > [1] mailto:lars@lamasti.net > [2] mailto:lars@lamasti.net > [3] https://localhost:8000/accounts/ > [4] http://localhost:8000/ > [5] https://docs.mailman3.org/en/latest/install/virtualenv.html# > [6] mailto:list1@domain1.name > [7] mailto:another-lis@domain2.name

2 years, 2 months

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

by Mark Sapiro

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

1 year, 5 months

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

by Ryan McClung

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

6 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/19/20 9:04 PM, Mark Sapiro wrote: > I suppose it could be considered a bug, but what's happening is your > initial subscribe created a user and and address and set the user's > preferred address to the created address. It also set the display_name > of the address and it subscribed the user to the list or possibly the > address to the list depending on what actually did the subscribe. > > When the user/address was unsubscribed, it is removed from the list's > membership and the list was removed from the user's memberships, but the > user and address still existed. > > Then when you resubscribed, the existing user/address was made a member > of the list, but not updated so the "new" display_name was ignored. I > think this is also the case if the original address had no display_name. > > You could say this is a bug and the display_name associated with this > new subscription should replace the prior one, but what if that address > was subscribed to other lists and didn't want the display_name changed > on those lists. > > Ideally (perhaps) there could be multiple address records with the same > email address and different display_names, but address records are keyed > by email address, so this can't be. > > One workaround would be for a user who wanted to have an address with > different display_names for different lists to have multiple addresses > likeaddress+list1@example.com,address+list2@example.com, etc. > > Is this really an issue that should be fixed or just a curiosity? No. No. No. No one set their preferred address here at all. The first incident was an imported list member who was not a registered user. They wanted their real name changed to something else. The list owner tried to figured out how to do that, found no way to do it, figured out it was just easier to unsubscribe them, and resubscribed them to the list using a different name. The old name showed up again. This is a bug and please fix it soon. This has nothing to do with being subscribed to other lists. I can probably come up with a workaround using Affinity (one of the benefits of moving away from Postorius) but I can't imagine this not being a serious issue as Mailman 3/Postorius is more widely adopted. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Fwd: Seeking help completing a useful installation

by Hugh Esco

Trying this again. ---------- Forwarded message --------- From: Hugh Esco <hresco3(a)gmail.com> Date: Mon, Mar 11, 2024 at 10:30 PM Subject: Seeking help completing a useful installation To: <mailman-users(a)mailman3.org> I have more fully documented where I am at with this attempt to build a working installation of mm3 at this link: https://gitlab.com/mailman/django-mailman3/-/issues/73 My questions include: - the template for /etc/mailman3/mailman.cfg, defines vardir, but no DATA_DIR. See test failure #1 (closed) <http:///mailman/django-mailman3/-/issues/1>, above. Where does that want to be? Any issue with putting the mm3.db next to the mm3_web.db at /opt/mailman/mm/var/data? - there are two possible virtualenv's in my build: (a) /opt/mailman/venv/ and (b) /opt/mailman/.pyenv/. I say more about these below. Which do I want to use in this instance? I'm guessing the latter where the mailman3 libraries are published, but have doubts. The link above urges a dependency on python ^3.11, but bookworm provides only python 3.8, so I used pyenv to satisfy the requirement. It wanted to deploy to its own path, though perhaps there is some switch which would consolidate everything under /opt/mailman/venv/. I do not work with python enough to know. - attempts to run bin/mailman-web startapp mm3web fail to add any new processes to the process list. bin/mailman-web start fails with errors. What change of state to the server should I expect from running this command? How do I test for success? If startapp is the correct invocation, what argument does it want on a working installation? - having run the command in the previous point, I see nothing in the browser except for the apache starter page at the root path '/'. None of the paths defined in the apache2 configuration seem to offer any joy. I assume that uwsgi wants to proxy the requests to a running mailman-web service somehow, but that no such service is found. I see one hopeful line in the log at: /opt/mailman/mm/var/logs/mailman.log "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" - I assume that once I get apache2 wired to a running application through the uwsgi proxy, that I can proceed to create an admin user, use it to explore the web gui, and begin to consider how to migrate my legacy mm2.1 lists into the new installation. Any further help crossing the finish line would be appreciated. Thanks, -- Hugh

1 year

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

by Mark Sapiro

On 12/20/19 7:26 AM, brunol(a)agro.uba.ar wrote: > Hi, > > I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) > Following the 2.1 to 3 docs: > - Create a new list > - Use the import21 command > The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. Are you saying that when a post is sent to the list, it is held for moderation, and when you approve it, it is not delivered? Or are the moderation messages from some other lists? Are there any non-digest members with delivery enabled? Is the MTA (which MTA) delivering the message to Mailman's REST runner? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Dadgar

On May 8, 2020, at 3:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > We tend to do this differently. For example, on mail.python.org which > currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends > about 135,000 individual messages per day from the two Mailman > instances, we define in /etc/postfix/master.cf > > 127.0.0.1:8026 > inet n - - - - smtpd > -o smtpd_authorized_xforward_hosts=127.0.0.0/8 > -o mynetworks=127.0.0.0/8 > -o smtpd_recipient_restrictions=permit_mynetworks,reject > -o smtpd_client_restrictions= > -o smtpd_helo_restrictions= > -o smtpd_sender_restrictions= > -o smtpd_data_restrictions= > -o receive_override_options=no_unknown_recipient_checks > -o smtpd_milters=inet:127.0.0.1:8891 > > Then port 8026 only accepts locally generated mail and only does dkim > signing (milter on port 8891) and essentially no other checks. > > Then in the [mta] section in mailman.cfg we only need > > smtp_port: 8026 Yep - I used to do something similar back when I was running dspam with mm2.1. This is a slightly more complicated to set up, but cleaner. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 11 months

[MM3-users] # comment allowed in a template file?

by skenny＠scss.tcd.ie

I've found that dropping files in to the templates directory is a simple and convenient way to make certain things happen. E.g. I can set a default footer for all posts by putting the desired content in a file called var/templates/site/en/list:member:generic:footer.txt. I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: # This file is managed by Puppet. Is it ok to do this? I may not have searched the docs enough, but I couldn't find anything relating to comments. One other observation in case it's any use: Initially, I created the template files with owner set to "root". This resulted in postings to lists getting stuck in mailman-core. It's vital that these files are owned by user "mailman". Once I changed the owner of the file to the latter, everything worked. Stephen

4 years, 9 months

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

by Stephen J. Turnbull

Shashi, This whole thread is off-topic for the developers list. This list is for development of Mailman, not for teaching people to use it. Read the whole recommended documentation before you ask busy developers to tutor you in very basic things. There's a mailman-users(a)mailman3.org list for users to help each other. All of the Mailman developers who might be willing to answer your questions are there as well, but there are also many experienced users, some of whom have experimented with the REST API who will also help. Please reply there for further help. (Reply-To is set.) That said, there are plenty of URLs in the API documentation. Here's a hint: search for "dump_json". That function takes an URL. You may want https: instead of http: in your URLs, and you may need to change the port from 9001, depending on the configuration of your REST server. Try it with simple GET requests for information first, such as for domains or lists. You can also do these requests with an ordinary web browser, though I don't know what it will do with the JSON-formatted reply. If you don't have domains and lists configured, I suppose the informational requests will come back as empty JSON objects. It should be safe to make them. You can either use Postorius to bootstrap a few example domains, lists, and users, or (the hard way) figure out how to POST appropriate requests. I don't recommend trying to update the backend DBMS by hand; the schema is quite complicated. I don't know how to use curl to update Mailman's databases. That requires a POST request which I have never done with curl. The POST request needs to be valid JSON. The more I think about this, the less I think your idea of using curl is worthwhile, because formatting JSON requests by hand is going to be a real annoyance and a great way to mess up your database with spurious information. You're really going to want programmatic support for this. But that's already all available in Python in the Mailman system. It's up to you, but I feel a responsibility to warn you that using curl is not going to be simpler than learning enough Python to do these things. Regards,

4 years, 11 months

[MM3-users] Re: Best guide for installing from pypi

by Duane Raymond

Thanks Jacob and Abhilash, I've had enough of trying to do it myself so I've asked Brian (I'd previously asked him but he only does it on vanilla machines and I wanted to use an existing setup). I'll learn from his work once it is running and see what I can do without a migration deadline looming over me ;-) Cheers, Duane On Wed, 24 Feb 2021 at 04:02, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi, > > > On Tue, Feb 23, 2021, at 10:00 AM, duane(a)fairsay.com wrote: > > Hi. > > > > I've got a partial mailman3 install done and, based on the > > documentation, am not sure how to complete it! (this is my first time) > > > > I've installed mailman3 (3.3.3) on a Debian 10 server using python3.7, > > mysql, postfix, apache, etc. and have run the install using pip3 > > install mailman. The "mailman info" command works, version shows > > "3.3.3 (Tom Sawyer)" the databases creates, tables, all exist, etc. So > > it seems the necessary services are running. I'm running froxlor on the > > server to configure the non-mailman services (apache, ssl, postfix, > > etc). I had also tried apt install mailman-full but it was an older > > version, so using the pypi route ensured I was on the latest version. > > I don't know anything about Froxlor, so I won't be able to help with > any issues caused due to that unfortunately. > > > > > Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html, > > what I can't figure out is: > > 1) There is no /opt/mailman/ user - the user installed seems to be > > "list" > > The user recommended to create is "mailman" with "/opt/mailman" > as the home directory for the user. Debian systems use the "list" > user to run Mailman. You can simply substitute the user from > mailman to list, the name itself doesn't make a lot of different, just > make sure you do change the name in systemd config files and > sudo commands that you use. > > > 2) Is a virtual environment needed for a production environment? > > It is recommended by Linux distros that you don't install from pip > directly into the system's site-packages. This can *potentially* > have side effects and break other systems that rely on Python > packages installed on your system, some which you might not > even be aware of that relies on Python (like, Yum package manager > does in RHEL systems). > > Hence, if you aren't use the system packages to install Mailman, > it is recommended that you use an isolated Python virtualenv. > > > 3) if django is setup properly or the webservice is working > > 4) I've tried to connect to some web interface > > (posterious/hyperkitty/some mailman3 web frontend) via lynx to > > localhost:8001 on the local machine - but it has a 404 error > > 8001 is Mailman Core's API endpoint. To test Web Frontend, > you want to reach out to: https://<mydomain>/ after configuring > your Nginx to reverse-proxy the uwsgi. > > Uwsgi runs a custom protocol, also called uwsgi, which Nginx > understands and is able to reverse proxy. You can't use Lynx > to test that. However, if you do want to test your service > locally, you can add this line the uwsgi.init[1] after the > "uwsgi-socket" line: > > http-socket = 0.0.0.0:8080 > > This will make uwsgi also accept HTTP connections on Port > 8080 that you can use to test. > > > [1]: > https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… > >

4 years, 1 month

[MM3-users] Re: Strange error in uwsgi-error.log

by brian＠emwd.com

Derek Lambert wrote: > Brian, > > When I was seeing this, new lists weren't showing in HyperKitty. > > I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from > functioning. I had to drop the constraint to get the lists in. None of them have a > description now. > > Was this working for you in the past? If so, did you do any updates recently? > > Derek Lambert Hi Derek, Actually you are right. None of my new lists are showing in http://mailmam3domain/hyperkitty/. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install. How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched. Brian

6 years, 2 months

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

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

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

by Mark Sapiro

On 6/30/21 9:23 PM, Mark Sapiro wrote: > On 6/30/21 6:23 AM, Lucia Moreno wrote: >> Hi Mark, >> >> We are facing the same issue. My postgres database is growing too fast >> and >> I would need to do some creaning of old archives dated from 2001 and keep >> only the last, lets say... 5 years. >> >> Could you please help us with the development of such a script? I have no >> experience in python. > > The attached script is a rough idea. Another way to do this that might actually be preferable is to download the entire archive from HyperKitty as a mbox, then split the mbox into what you want to keep and what you don't, delete the list from HyperKitty and then run hyperkitty_import to import only the messages you want to keep. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Help needed to create filters that were working in Mailman 2.

by Mark Sapiro

On 6/20/23 11:04 PM, mrl(a)psfc.mit.edu wrote: > How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? > > I could do this using the anti-spam filters in mailman 2, as there was a Accept option. > > But there is no Accept option in Mailman 3 (that I can find). > > I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. The default action for "Default antispam action" is "hold" but you can change that to "accept" by setting ``` jump_chain: accept ``` in the [antispam] section of mailman.cfg, however current Postorius offers "Accept immediately (bypass other rules)" as a choice for the Header Filters action. Does yours not? What is your Postorius version? -- 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: Change config to create a new list with all archives off

by Danil Smirnov

Hi Steve, I tried to use your approach today: On Fri, Jun 2, 2023 at 8:30 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > ... 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 -------------------------------- > I used it with a different source list - it's PrivateDefaultStyle. When I try to create a new list using the new custom style I get an error: 2024-04-21 12:16:08 [FALCON] [ERROR] POST /3.1/lists => Traceback (most recent call last): File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3.11/site-packages/mailman/rest/lists.py", line 321, in on_post mlist = create_list(**validator(request)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/mailman/app/lifecycle.py", line 100, in create_list style.apply(mlist) File "/usr/lib/python3.11/site-packages/mailman/styles/default.py", line 107, in apply super().apply(self, mailing_list) TypeError: PrivateDefaultStyle.apply() takes 2 positional arguments but 3 were given > Untested, feel free to ask if it doesn't seem to work. > Could you check what's the issue, please? Danil Smirnov 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 > Sincerely, Danil Smirnov

1 year

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

by Mark Sapiro

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. > I still don't get it. What if I just suscribe the members and then send the > email to the suscribers the thing is that the email has to be received by > mailman in order to resend it to the list suscribers right? If all you want to do is send mail that you generate, you can use mailman inject to deliver the mail to Mailman on the local machine. The drawback of not being able to receive mail from the outside is Mailman won't receive bounce DSNs from remote servers. -- 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] [Older bug, but still unsolved] When deleting one or more threads in an archive, django send error mails (based upon "Thread matching query does not exist")

by Wikinaut

I installed the venv version to scrutizine whether this old bug is still present (yes it is). How to reproduce: Delete one thread in via the archive - thread - view page. Remark: Thread is deleted as wanted. However, django complains via several (here: two) error mails: 1st mail: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/test(a)example.com/top-threads Internal Server Error: /archives/list/test(a)example.com/top-threads DoesNotExist at /archives/list/test(a)example.com/top-threads Thread matching query does not exist. ... 2nd mail: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/test(a)example.com/posted-to Internal Server Error: /archives/list/test(a)example.com/posted-to DoesNotExist at /archives/list/test(a)example.com/posted-to Thread matching query does not exist. ... I wish to fix this problem, how can I help, what can I do? Do you need the full error stack?

1 year, 6 months

[MM3-users] Re: Mail configuration

by a.matveev＠lan-project.ru

> I'm not sure if this is the correct forum for this question, but I'm pretty > sure if there is expertise on how to do what I want to do, it can be found > here. > > Overview of what I am looking to do: > > Due to the impending shutdown (in the next 6 months) of the data center > where our mailman server lives, we are being forced to move the > installation. We are going to be moving it to a different location. > > Here is our problem... > > Moving things is not really a problem in and of itself - I'm confident that > I can get things set up correctly elsewhere. However, our email server > sends somewhere around 100,000 emails per day, and if you cut over from one > IP address to another IP address, my understanding is that most ISPs will > start to ban you, because they are not used to that sort of volume coming > from an unknown IP. I know it would be better if we could keep the IP > address, but again, due to circumstances beyond my control, this is not > going to be a possibility. > > 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. So what I am > looking for is a way for all mail on our domain to be sent to our current > mailman installation, and based on some configuration (certain mailing > lists?) 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? > > 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? > > Thanks, > > -Darren Hi Darren Your current IP(s) is used for correct PTR lookups, when remote mail server is decide to receive or reject your mail. So when you change your IP for outgoing mail server (or mailman, if mta on the same host such as postfix ), you must update those records in DNS. This takes some time. If you know your new IP, you may add new PTR for it and when it start resolves, just switch working services.

7 years

[MM3-users] Re: configuration to send to recipients in a spread out manner to avoid being considered spam

by Odhiambo Washington

On Sun, Nov 19, 2023 at 3:25 PM testeur via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi, > > I s there a mean to configure the list for that emails be sent to > recipients in a spread out manner to avoid being considered spam ? cause > AOL, YAHOO seems to consider emails sent to recipients as spam or an > "Excessively high volume of emails". there's just 40 (aol, yahoo) emails > suscribed to the list. > > thx. > I believe this is doable within your MTA - Postfix or Exim. In Exim, we do something like this: https://lists.exim.org/lurker/message/20080818.185617.b5534450.en.html Hopefully, it gives you a clue on what you can do for your MTA. -- 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, 5 months

[MM3-users] Re: configuration to send to recipients in a spread out manner to avoid being considered spam

by testeur

Then i ve to watch more on postfix options. very thanks ! On 19/11/2023 13:39, Odhiambo Washington wrote: > On Sun, Nov 19, 2023 at 3:25 PM testeur via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Hi, >> >> I s there a mean to configure the list for that emails be sent to >> recipients in a spread out manner to avoid being considered spam ? cause >> AOL, YAHOO seems to consider emails sent to recipients as spam or an >> "Excessively high volume of emails". there's just 40 (aol, yahoo) emails >> suscribed to the list. >> >> thx. >> > I believe this is doable within your MTA - Postfix or Exim. > > In Exim, we do something like this: > https://lists.exim.org/lurker/message/20080818.185617.b5534450.en.html > Hopefully, it gives you a clue on what you can do for your MTA. > >

1 year, 5 months

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

by Odhiambo Washington

On Mon, Aug 5, 2024 at 9:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > 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? > Yes, those are Cloudflare IPs and I don't know why 2! All I know is that in DNS, I created an A record for the hostname and chose the "proxy" option in the cloudflare DNS management interface. > > 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? > You add the domain - kictanet.or.ke to CF's control panel. They give you TWO name servers. You substitute the NSes your registrar gave to your domain for those two. Subsequently you create A|CNAME|MX\TXT records on the CF's control panel. You decide whether an A or CNAME record you create is proxy-ed or not. If you proxy the record, no one will ever get to know its real IP, but if you don't proxy, then the dig tool above will tell you the real IP address. > 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? > I don't know. However, those IPs you see in the Nginx logs, none belong to me! I have two possible IPs - one domiciled in KE and another domiciled in the US (when I use VPN). -- 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]

8 months, 2 weeks

[MM3-users] Re: Managing users

by Abhilash Raj

On Fri, Mar 1, 2019, at 12:42 PM, worik wrote: > Is there a interface for managing users? > > I can use the data base directly to query `auth_user` etcetera, but > Postorious? What are you actually trying to do? "managing users" doesn't tell me how to help you out. In general, it is not a good idea to change the internal database without using any of the public apis, unless you are just trying to read things. If you are talking about web interface, then you can go to the admin console `/admin` on your installation and there should a list of users and Email addresses there. > Worik > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

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

by Mark Sapiro

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

3 years, 3 months

[MM3-users] Deactivate list without deleting it?

by Stephen J. Turnbull

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). So to get it into the distribution we'd need to make these things optional. (Perhaps if these options proliferate much, they could be incorporated into list "styles" so that instead of setting all the options manually, the primary use cases could be served by "intuitively" named styles.) 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'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. 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.

7 years, 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 London

Andrew - The script had: DELETE_MAILMAN_USER = False When I set it to True, it got rid of the orphaned email addresses. Thanks! - Mark On 4/25/2023 6: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 > > I have it running in a cronjob. Thread discussing the script can be found here: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. > > Thanks. > Andrew.

1 year, 11 months

[MM3-users] Re: Disabled by bounce

by Jan Eden

On 2023-02-20 19:03, Stephen J. Turnbull wrote: > Jan Eden via Mailman-users writes: > > > To distribute messages with valid DKIM signatures, I set > > > > remove_dkim_headers: yes > > > > in /etc/mailman3/mailman.cf > > That should be "mailman.cfg" for a standard installation, and it may > not be in "/etc/mailman3" in a shared hosting situation. > > Do you have evidence that removing DKIM headers helps you get mail > delivered? (Not adding your own, IMO you should do that regardless of > whether you strip existing ones, but removing originals.) The DKIM > spec says that you shouldn't, and that consumers should treat invalid > signatures no differently from missing signatures. I haven't run into > a "public" host that treats an invalid signature as a problem in quite > a while. Right – removing the invalid DKIM signature is just a matter of taste. I tested message distribution with and without signature removal, and two major mail providers did not handle the messages differently. - Jan

2 years, 2 months

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

by Stephen J. Turnbull

Jeremy Stanley writes: > On 2023-09-09 01:21:32 +0900 (+0900), Stephen J. Turnbull wrote: > [...] > > We could easily have an option to not attach the messages to the > > notifications, just a list of most useful headers, or simply a > > statement of how many if you really want to be minimal. > > A number of our lists would probably make use of that if it were an > option, though sadly my dance card is too full to code the feature > any time soon. Turns out there's already an RFE in the GitLab tracker: https://gitlab.com/mailman/mailman/-/issues/670 I added "easy" and "beginner-friendly" to the issue. I'm not so sure if that's true of the follow-on RFE (the change to Postorius, which I did not yet create ;-), but we can cross that bridge when a volunteer shows up. :-) Do you know if the whole spammy mail is needed to trigger the overly sensitive sites, or if just From: and Subject: can do it?

1 year, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 8 months

[MM3-users] Re: Problem with missing MySQLDatabase

by Peter Sørensen

Hi Mark, Unfortunately I answered on ³auto response not sent² instead of this - sorry. In the meantime I found one problem. The comment I¹ve put at the end of line ## MOD .. This is not the way to do it in Python. I normally use Perl and not a Python as script language. Deleteing the #Š Made this problem disappear but instead below problem showed up. /etc/mailman3# mailman aliases Traceback (most recent call last): File /usr/bin/mailman, line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File /usr/lib/python3/dist-packages/mailman/bin/mailman.py, line 94, in main initialize(config_path) File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line 189, in initialize initialize_2(propagate_logs=propagate_logs) File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line 160, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File /usr/lib/python3/dist-packages/mailman/database/factory.py, line 54, in create database.initialize() File /usr/lib/python3/dist-packages/mailman/database/base.py, line 106, in initialize self.engine = create_engine(url, isolation_level='READ UNCOMMITTED') File /usr/lib/python3/dist-packages/sqlalchemy/engine/__init__.py, line 387, in create_engine return strategy.create(*args, **kwargs) File /usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py, line 80, in create dbapi = dialect_cls.dbapi(**dbapi_args) File /usr/lib/python3/dist-packages/sqlalchemy/dialects/mysql/pymysql.py, line 62, in dbapi return __import__('pymysql') ModuleNotFoundError: No module named Œpymysql' I have installed pymysql with: pip install pymysql When I do this once more I get pip install pymysql Requirement already satisfied: pymysql in /usr/local/lib/python2.7/dist-packages Requirement already satisfied: cryptography in /usr/lib/python2.7/dist-packages (from pymysql) So the problem has probably to do with this installed in python2.7 and not python3. How do I solve that ? Best regards Peter Sørensen University of Southern Denmark Den 19/10/18 19:13 skrev "Mark Sapiro" <mark(a)msapiro.net>: >On 10/19/18 3:44 AM, Peter Sørensen wrote: >> Hi, >> >> I have looked into installing this before without success but found >> The Debian package Mailman3-full >> >> I installed this succesfully along with the mailman-suite. >> I have configured varios setting but are stuck when trying to generate >>aliases >> For mailman with: >> >> mailman aliases >> Traceback (most recent call last): >> File /usr/bin/mailman, line 11, in <module> >> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() >> File /usr/lib/python3/dist-packages/mailman/bin/mailman.py, line 94, >>in main >> initialize(config_path) >> File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line >>189, in initialize >> initialize_2(propagate_logs=propagate_logs) >> File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line >>160, in initialize_2 >> config.db = getUtility(IDatabaseFactory, utility_name).create() >> File /usr/lib/python3/dist-packages/mailman/database/factory.py, line >>52, in create >> database = call_name(database_class) >> File /usr/lib/python3/dist-packages/mailman/utilities/modules.py, >>line 67, in call_name >> named_callable = find_name(dotted_name) >> File /usr/lib/python3/dist-packages/mailman/utilities/modules.py, >>line 50, in find_name >> __import__(package_path) >> ModuleNotFoundError: No module named >>'mailman.database.mysql.MySQLDatabase\t\t\t#MOD(inserted ) 02'; >>'mailman.database.mysql' is not a package >> >> I can see from the message that I¹m missing a module but I can¹t figure >>out. how to get >> This installed. The mudule is referenced in the mailman.cfg as >> class: mailman.database.mysql.MySQLDatabase > > >The module mailman.database.mysql is part of mailman core. In your case, >it should be /usr/lib/python3/dist-packages/mailman/database/mysql.py. >If that file exists, I don't know what the problem might be. If not, >there is something wrong with your installation. In any case, this is a >Debian issue. You need to take it up with Debian. > >-- >Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >San Francisco Bay Area, California better use your sense - B. Dylan >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 6 months

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

by Terri Oda

On 2016-12-12 12:29 AM, Stephen J. Turnbull wrote: > Barry Warsaw writes: > > > >I can also work on Postorius. Also in this vein I have a question. > > >Should the DMARC settings be added to the Alter Messages tab in the List > > >Settings view or would it be better to have a separate DMARC Mitigations > > >tab. > > > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > > Terri have final say I think. > > I would find it more natural to have "Posting Policy" (which would > include posting filters on size and list membership, as well as > message alterations such as removing .exe files and enforcing plain > text by removing or rendering HTML parts), and "Malware Mitigation", > which would include IP, domain, and mailbox filters as well as DMARC. > I think DMARC mitigation is probably too special to deserve its own > tab. Alter messages tab works for me, but DMARC is kind of a big enough deal (as far as mail delivery goes) and sufficiently different that I agree with Mark that it's not unreasonable to give it a separate tab. I'd be willing to start it on its own and move it if we're getting too cluttered later, as long as we document it in the release notes when we do. Florian, what do you think? > Probably this is way too much reorganization to do at this point, but > I'd like to keep this point in mind. We are already getting reports > that configuration options are hard to find just because it's > different from Mailman 2. I suspect that the REST API is sufficiently > flexible and regular that we'll be tempted to proliferate options, so > let's try to keep them organized. We also get reports that mailman 2.1 options are hard to find -- I think I personally help someone find something at least once a month (on irc, in person, or by email) for the past decade. :) I imagine Mark has answered a lot more of those than I have. The big thing I want is good documentation here. There's never going to be an organization that works for everyone, but an easily searchable document with all the options would make a big difference. I only got to that level with the user docs not the list admin docs in 2.1

8 years, 4 months

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

by Mark Sapiro

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

6 years, 5 months

[MM3-users] Re: Gmail/Fetchmail in Mailman3?

by Mark Sapiro

On 06/23/2018 02:48 PM, Bill Christensen wrote: > > Our Mailman2 setup uses Fetchmail to retrieve list mail from our > accounts on Gmail. > > Is there a similar setup for Mailman3? Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail? If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3. If Fetchmail is piping it to a command like "| /path/to/mail/mailman post listname" that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP server (which it calls a runner). Mail is normally delivered to an MTA which is configured to relay the mail via LMTP to the localhost port that Mailman is listening on. So Fetchmail can eithr deliver to the MTA and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port. -- 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: Cannot setup announce-only mailing list

by Mark Sapiro

On 2/1/20 9:53 AM, Abhilash Raj wrote: > > > On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: >> >> In short, you need to set this up manually using things like moderation >> settings and custom templates for the welcome message. > > Mark, do you think we should make the actual announce-only style reflect > these settings so folks don't have to manually set these after they create > a announce-only list? > > I am not sure the reason behind these settings lacking for the current > announce-only style. Are there situations where announce-only list would > have different list setting? I think it was probably done as it is just as a start. I do think it would be good to set more things appropriately for the announce-only style, ultimately we may need to add templates for post rejection notices and things like that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

by Stephen J. Turnbull

Peter Münster writes: > On Wed, Aug 31 2022, Stephen J. Turnbull wrote: > > > Do you really mean "en"? > > Yes. Since this is the only file under the templates-directory, it > should be used according to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > > Or do I misunderstand something? No, I was just making sure because Mark's message that you quoted mentioned "de", and you have an umlaut in your name. Come to think of it, I'm not even sure Mark was replying to you, but for what it's worth that was my thought process. :-) I'm not very familiar with Django's handling of such files, but my understanding is that many files are collected from various places using manage.py's collectstatic command. I don't remember whether these templates are among them. That's the only thing I can think of offhand. If that's not it, I'll try to get back to this on Saturday. Steve

2 years, 7 months

[MM3-users] Re: Problem with perms on /etc/mailman3/mailman.cfg while following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Mark Sapiro

On March 25, 2025 1:20:22 AM GMT+07:00, Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > >The instructions https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… do not say what to do with existing file. > >root@shackleton12:~# ls -alF /etc/mailman3/mailman.cfg >-rw-r--r-- 1 root list 11119 Mar 20 11:45 /etc/mailman3/mailman.cfg > >Should we move the /etc/mailman3/mailman.cfg out of the way and create new file as user and group mailman:mailman ? How did that file get there? It looks like at some point you installed the Debian package. If you are following <https://docs.list.org/en/latest/install/virtualenv.html you shouldn't install the Debian package. In any case, just remove the file. Probably it's best to remove the Debian package completely and start over. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 weeks, 2 days

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

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: > hansen(a)rc.org writes: > > b. The ability of members to change their addresses for all lists > > they are subscribed to. > > What exactly do you want here? I can think of a number of ways to > implement that, depending on whether the old address is to be > deactivated from the lists, unsubscribed from the lists, or deleted > from the Mailman and/or Postorius Users. There may be other > variables to consider, as well; I haven't thought about this. AFAICS > this is not a trivial feature, and I'd really like to hear from people > who want "something like" this about exactly what they want and their > use cases. Or we'll release an insufficiently designed feature that > causes somebody hundreds of problems.... I thought user could do that if they have an web account, and multiple mail addresses are associated with the account? Or does my memory serve me wrong there? Andi

4 years, 2 months

[MM3-users] Bounce handling after upgrade

by David Krantz

Hi, I am in the process of configuring a new mailman3 server based on my old one. This includes upgrading to the latest version of mailman and installing a database upgrade. To my surprise mailman core started by sending tens of mails and blocking the corresponding users for very old bounces. What is worse is that this happens every time I start mailman core. Now I have blocked (almost) all outgoing mail in postfix using a transport map which discards it but this is a temporary testing measure of course. When I deploy this server into production, I do not want these recipients to be blocked as the old problems have been solved since very long. My plan is to reload the database from a newer backup anyway... Would it be enough to empty the bounce table (bounceevent) or is there anything else driving this behaviour? Or is there a better way to do this via the mailman shell? For me a "delete from bounceevent" seems a lot simpler than anything via the shell but there may be dependencies in the database. Cheers // David

4 years, 9 months

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

by David Partain

Hi Mark & all, Thanks for the response. Just picking up where we are at the moment to provide a bit more info, in case you have ideas. Thanks, Stephen T. as well for the idea of turning on DEBUG. We might resort to that in the end. This is what our system is running right now: Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] As previously noted, we moved this off of an old Ubuntu package-based installation that has delivered mail reliably but many other things haven't worked well, so we're happy to be on something that might improve that situation. Right now, archiving is not working on the new installation, both building the archive on the new installation after the move and for new messages. uwsgi-error.log is getting blasted with constant errors along the lines of what follows. I suspect that these errors are why archiving isn't working, but I obviously don't know that: Message: BadSignature('Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match') Arguments: ('Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher task = SignedPackage.loads(task[1]) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads return signing.loads( File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign result = super(TimestampSigner, self).unsign(value) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign raise BadSignature(\'Signature "%s" does not match\' % sig) django.core.signing.BadSignature: Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match',) What we have in our config files on the old installation and new installation are (the quotes are exactly as they are in the files): Old installation: mailman-web.py SECRET_KEY = 'somerandomstringiaintputtinginmail' MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' mailman-hyperkitty.cfg api_key: somerandomstringiaintputtinginmail New installation: settings.py SECRET_KEY = 'somerandomstringiaintputtinginmail' MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' mailman-hyperkitty.cfg api_key: somerandomstringiaintputtinginmail All of that says that the value is the same for all three (whether I should have done so or not...) and those settings were carried along to the new installation as well. Django is a big scary beast as I've not had to manage django apps before. Would it make sense that the error above is because what I _think_ django believes is the SECRET_KEY (in the config files above) is in fact not what django believes? Maybe it was set during installation (which I didn't do)? I don't believe anyone has purposefully changed it. I suppose I could do something like https://medium.com/django-unleashed/securing-django-applications-best-pract… to reset the secret key, but I'm not doing that on Friday afternoon :) If anyone has other thoughts, please holler. Wishing you all a good weekend from lighter-by-the-day Sweden. Cheers, David -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net<mailto:Mark%20Sapiro%20%3cmark@msapiro.net%3e>> To: mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> Subject: [MM3-users] Re: Badsignature on uwsgi-error.log Date: Wed, 20 Mar 2024 18:12:20 -0700 On 3/20/24 14:25, Helio Loureiro wrote: Hi, I keep receiving a lot of errors like this: --- Logging error --- Traceback (most recent call last): ... "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign raise BadSignature('Signature "%s" does not match' % sig) django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match ... The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY on setting.py are the same. 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. If you know what it was previously, you could set the previous value in SECRET_KEY_FALLBACKS, see https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks

1 year, 1 month

[MM3-users] Re: Mailman 3 Installation

by Mark Dadgar

On Jan 17, 2021, at 11:01 AM, Andreas Barth <aba(a)ayous.org> wrote: > > * Mark Dadgar (mark(a)pdc-racing.net) [210117 19:59]: >> 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.” > > I need to disagree to the last part of the sentence because I did it, > but my strong recommendation based on expirence is: save the effort, > start directly with postgresql. It's not much more work, and migrating > is .. well, just don't try or do it. 😁 Did you document it anywhere? I could not find evidence of a successful migration when I looked 6 months ago, including in this list’s archives. That would be great information for the community, if only as a cautionary tale. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 3 months

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

by Mark Sapiro

On 1/23/23 22:50, Stefan Bauer wrote: > Dear Mark, > > thank you for your time. > > Here are the lists settings and an example mail attached. > > Filter content: NO > Filter types: EMPTY > Pass types: EMPTY > Pass extensions: EMPTY > Collapse alterantives: YES > Convert html to plaintext: NO > > Thunderbird is showing the mail "correct". Outlook does show the > attachments as attachments. So Filter content is NO so Mailman isn't doing any content filtering. All it is doing is adding headers and footers if any, and if the original message is other than a single text/plain part, these will be added as separate MIME text/plain parts. For a discussion on why this is done, see https://wiki.list.org/x/4030707 which is written for MM 2.1, but which applies at least generally to MM 3. -- 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: bulk deletion of messages from Hyperkitty

by Timour Bakeev

Hi Mark! Mark Sapiro wrote: > 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. Could you take a look at my MR for this script? Right now I have to use a locally modified version of it, as the one in contrib/ doesn't work out of the box. > > 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>; Thanks a lot for this detailed walk-through, it is very helpful and I'm going to use it to clean up my migrated archives. With best regards, Timur Bakeev.

9 months, 1 week

[MM3-users] rest api runner not running

by Christine

Hi, I have been using mailman for about ten years, now I want to move the lists to another server, I have installed mailman3 there, most of it seems to be running, but the "rest api runner" is not. Nothing is listening on port 8001. What have I missed? What do I do to start the restapi runner? I checked the logs, I don't see anything suspicious. this is what systemctl status says: root@lists:~# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; 6min ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 173111 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM) Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation timed out. Terminating. Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result 'timeout'. Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server. There is nothing in mailman.log, nor in smtp.log dagdag Christine -- dagdag is just a two character rotation of byebye

4 years

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

by Mark Sapiro

On 7/30/21 10:47 AM, bob B wrote: > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? I'm not sure what the actual command would be do run the django-admin interface in the docker image, but from below, it looks like it's `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. This command tries to send the mail via SMTP to localhost port 25. > How can I make sure my containers can send and receive mail? The MTA should be listening on port 25 and that need to be visible in the mailman-web container. See <https://asynchronous.in/docker-mailman/#setting-up-your-mta> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

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

by Stephen J. Turnbull

Peter Münster writes: > On Thu, Sep 07 2023, Stephen J. Turnbull wrote: > > and then have a "reproduce defects" flag for the reassemble > > functions. > > Yes, that sounds good. Are you ready to do that? And if yes, what > recompense would you like to receive please? I could do it, but I don't really want to. The problem is even if it were done, it's a very fragile feature because it depends on collecting particular behaviors that can change at any time. So I'm unsure (50-50 at best) that it would get into Python, and then I don't know if it would get into Mailman because it's not obvious anybody would want the responsibility of continuous maintenance in order to take account of all the idiosyncrasies of homebrew mail clients of various companies. The current DMARC behavior of changing From and Reply-To is much more robust, and I just don't think there's that big a constituency for making life easy for disruptive actors like Google. Steve

1 year, 7 months

[MM3-users] Congrats on the instructions for installation on ubuntu, what about migration?

by Bill Oliver

So I went ahead and tried to install mailman3 on ubuntu 24.04 using the virtual environment approach. It worked like a charm. There were a very few glitches, all from me not reading the instructions closely (e.g. not replacing MY_SERVER with my server name, Doh). The whole thing, from start to finish was about two hours. I appreciate all y'alls efforts in this. The reason I'm doing this is that I'm having to migrate from a server that's going to be defunct soon. I've been running a mailman3 mailing list on that for a few years. Is there a tutorial/instructions on migrating data from an old system to a new one? It's actually not the end of the world if I don't get all the old emails transferred, but I'd like to get the email addresses of the participants moved over easily... I believe that I set it up in 2020, but did not do any version upgrades since then... Thanks! billo

6 months, 2 weeks

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

by Mark Sapiro

On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: > > But I am trying to delete a list on an urgent basis. Because of which I am > getting the above said errors. I tried to delete > through the interface, through curl command and through "mailman shell" but > nothing led me to a > positive result. Is there any work around to delete the list ? What have you tried in Mailman shell? This should do it. $ 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 >>> getUtility(IListManager).delete(m) >>> commit() So should just $ mailman remove list.example.com What happens if you do those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: subscribing to any list is not possible

by Stephen J. Turnbull

r.woithe(a)callassoftware.com writes: > to try patch is good idea, but why my files are more different than > the patch file lines? You have a different version from the version the patch was created on. > Should i rather copie the whole file? No. The patches are generally very local changes which are easy to understand. If you copy a whole file, you are likely to run into internal API changes, such as new functions or additional arguments. These changes typically do cross file boundaries. > Example: > in cli_members.py: > def add_members(mlist, infp): but into the patch file it is -> def add_members(mlist, add_infp): > but this line is not a patch line and should be the same or not? That depends on whether the patch lines use "infp". If they do, you almost certainly need to change them too. I didn't make the patch so I can't help you with the details, but I did want to warn against trying to copy files when patches don't match. Steve

4 years, 3 months

[MM3-users] Re: spanish localization

by Stephen J. Turnbull

Victoriano Giralt writes: > I've visited Weblate, all Spanish strings are translated. Spanish > is 100% translated, but, none of them have been "approved", > whatever that is. It seems that a reviewer needs to approve the > translation in order for them to be incorporated or released or > whatever. I was sure I had reviewed everything between November 7th > and the day Abhilash announced the release candidate and asked for > translation review, but nothing has made it to the released > version. > > Maybe there's something in the translation flow that we are doing wrong. > I'm starting to miss the good old days when Mailman 2 translators just > downloaded the .po files and returned them :-) Probably all it needs is for someone other than the submitter to check a box. I doubt there is an assigned reviewer/owner, just any translator registered for that language. That's the way Debian used to work, anyway, and it seems like a good way for open source to work. @Abhilash, you set up Weblate, right? Do you know anything about this?

4 years, 2 months

[MM3-users] Re: Strange password problem

by Mark Sapiro

On 9/22/23 11:39, Eggert Ehmke via Mailman-users wrote: > Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > >> If you set the password with the Django admin changepassword command, >> does it stick? > > Never tried that, how do I do that? In our recommended install, the Django anmin command is `mailman-web` so with your venv active, ``` $ mailman-web changepassword ``` will prompt you for a new password for the current user. If you want to change another user's password, specify that user's username as in ``` $ mailman-web changepassword user ``` >> Can you create another superuser with the Django admin createsuperuser >> command and does that user's password stick? > > Will try that. So I can create another superuser? Does it need a separate > email address? I guess yes ``` $ mailman-web createsuperuser ``` It will prompt for a username, email address and password. The username and email address need to be unique. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Why is a mailing list not sending the moderator subscribe or post notifications?

by Mark London

Hi - I migrated from mailman 2 to mailman 3. All but one list is working correctly. That list is not sending the moderator any emails. It appears to configured exactly like the other lists. I.e. subscription requests and moderated users posts don't generate any emails to the moderator (me). I tried changing moderator email addresses, and everything else I could think of, but nothing worked. What can I do to debug this problem? This list is much larger than any of my other lists. And has a huge archive. I doubt that is a factor, but I’ll mention it anyway. Also, how do I run the command to remind me of awaiting moderation requests, so that I can run it hourly? In case this can’t be fixed quickly. As an aside, I had some mailman 2 lists that had no moderators. I could swear that for them, that the owners would get moderated requests. Am I hallucinating? I can't check the old server any longer. Thanks. – Mark

1 year, 10 months

[MM3-users] Re: update_index

by Mark Sapiro

On 04/03/2018 09:59 AM, Darren Smith wrote: > OK - next issue...here's the warning that I'm receiving when I run that: > > /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date > received a naive datetime (2018-04-03 07:51:25) while time zone support is > active. > RuntimeWarning) That warning comes from dateutil.parsedate, and I think it's just a warning and shouldn't affect processing. > I'm not sure that anything else occurred. The indexing took 2 seconds, and > there have been tens of thousands of emails imported since the last index. > Thoughts? I'm unsure about what happens when 'runjob update_index' runs after an import. I.e. it adds messages added since the last run, but is this based on when the message was added or on some date in the added message, so if the added messages are old, do they get indexed by 'runjob update_index'. You could easily check by doing some searches that should find them and see if they're found. -- 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: Dealing with recipients' servers spam filtering

by Gilles Filippini

Brian Carpenter a écrit le 12/02/2021 à 15:10 : > On 2/12/21 8:41 AM, Gilles Filippini wrote: >> I run a mailman3 instance with mainly private lists for which I know >> and trust every single member. Some of them have Hotmail email >> addresses, and the messages they send though our lists are rejected as >> being spam by most of the recipients' mail servers, while these are >> legitimate emails. >> >> I'd welcome any pointer to best practices / howtos regarding mailman3 >> / exim4 configuration to mitigate this problem. > > What does the non-delivery long entries say are the reasons for the > rejections? It says: host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command) > Do you have a SPF record setup for your list domain? Do you > have DMARC mitigation enabled for your list? I don't have any SPF record setup. DMARC mitigation is configured to 'Replace From: with list address' and 'DMARC mitigate unconditionally' set to 'No'. Thanks, _g.

4 years, 2 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Mark Sapiro

On 6/24/23 9:44 PM, Ken Alker wrote: > How did you join the split thread? using HyperKitty's "Reattach this thread". > The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too? That was my mistake. There were two choices. I could open the reply thread containing only https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and reattach it to the original message thread now containing several messages or vice versa. I did the latter, i.e. with the result you see with the reply out of sequence at the top. Had I done the former the reply would have been out of sequence at the bottom. This would have been better, but it's now too late to change it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Can "Pre Verified" set to yes by default?

by Stephen J. Turnbull

Hi Alan, It occurred to me that Django template widgets are very flexible. It may be possible to customize the template to accomplish this task. In that case, the customized template would be kept in a place that doesn't get overwritten in an upgrade, reducing the maintenance cost (unless either Postorius or Django changes the template in a way that seems unlikely to me). I'll try to take a look at that over the holiday break -- that has the advantage that I just document how we did it for you, and tell any future requests to RTFM and DIY. ;-) Alan So writes: > I can say that it is not purely a technical issue in an > organization that whether system admin should maintain a few minor > changes that are not in the main branch. Sure, we understand that. I'd be interested to hear from business users and university users if they would like this particular default to be configurable. It's very easy to do as a one-off, if there is substantial demand we *can* do it, and later say to people who want similar changes that it's on them to demonstrate they have enough demand on their side for another one-off, just as was done for this one. > Due to massive customization made to previous Mailman 2 > installation by some student helpers which made it very difficult > to be upgraded nearly 20 years ago, we tend not to repeat this > pattern when we upgrade to Mailman 3 a few years ago. I agree, you need to be disciplined about what changes you are willing to develop and maintain. This one seemed to me to be over that bar, especially since you can put it in and not suffer too greatly if it gets reverted in a upgrade and the maintainers don't notice. > After all, it is just one of the many suggestions that you > received. I respect the decision of the core team. If the core > team consider that this feature is low priority, it is fine not to > implement it. Unless I see a lot of demand, I think as a one-off I don't want to implement it in list_forms.py, but rather let occasional admins do it on their sites if they want it that bad. But GSoC is coming up again; maybe a student would be willing to take on a generic "pwn all the defaults" project next summer. Steve

2 years, 4 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

Do you have something like this[1] in your settings.py file? [1]: https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… `EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'` `This is a dummy email backend which will basically only print the email to stdout, which seems to happen in your uwsgi-error.log. If you do, please comment it out and see if that solves your issue.` `Abhilash` On Sat, Mar 28, 2020, at 5:38 PM, Ralph Seichter wrote: > * Mark Sapiro: > > > What is the complete log message from uwsgi-error.log? > > I'll attach a typical log file to this message. It shows startup > messages followed by a recorded confirmation email. User name and > domain are obfuscated, but other than that the log is unchanged. > > -Ralph > > > _______________________________________________ > 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/ > > > *Attachments:* > * uwsgi-error.log -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: List mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 05:31, itservice--- via Mailman-users wrote: > How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net > I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. > unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. Unfortunately, there are some ESPs that will silently discard mail without giving any clue as to the reason. I think this is wrong, but there's nothing we can do about it. > At web.de they go to the SPAM folder. Is your mail server properly configured with a fixed IP and full circle DNS? Is it on any block lists (check at http://mxtoolbox.com/blacklists.aspx)? Are you DKIM signing your outgoing mail? Are you applying DMARC mitigations to your list mail? All these things are important. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Database running VERY hot

by Darren Smith

Hello all, We had an old installation of Mailman 2.1 across three servers with over 32,000 mailing lists on them. Due to circumstances beyond my control, we had to shut them down and quickly set up Mailman 3 on a new server. We have Mailman3 set up on a single server this time, as we were having problems with a 3-server setup and Hyperkitty and archives. Long story short, it is up and running, and our users are starting to come back. However, we do not have very many users hitting Postorius and Hyperkitty yet, and we are seeing a distressing number of 504 gateway timeouts. We noticed that there is a significant number of queries to the API whenever hitting Postorius's front page to load the mailing lists, and then on every load. It looks as if it makes a single call to the API to get information about a single list, and does this 10 times - once for each list - to render the page. This gets much worse when users set the view to 200 per page, as they are inclined to do with 32,000 mailing lists... What we've done, actually, is to override the front page and point the users to a different set of static pages where we have all of our lists categorized and searchable, and when they find the list they are looking for, we have a link back to postorius. It has taken a lot of the stress off of the server. However, I still see where the database at times can run VERY hot. We have set up this server to run with PostgreSQL. When I do a ps aux | grep postgres, I find a lot of processes that have been spawned to take care of mailman - a dozen or so. However, one of the threads is taking up about 85% of the load, another thread about 14%, and little dribbles here and there from the rest of the threads. Here are the questions: 1) Has anyone run into problems like these? I would think that maybe this is an issue having so many mailing lists, but honestly there aren't that many people using the system yet. It is going to ramp up as the users realize that we are live again, but we aren't getting that much traffic. 2) Is there any configuration that I can set, especially with regards to the database, so that it can be used more efficiently and not throttle through one or two threads? Please let me know what further information I can provide. Thanks in advance for any help or advice! Silas

7 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

7 years, 9 months

[MM3-users] Re: Selective mailing

by Stephen J. Turnbull

chucka(a)blackforest-co.com writes: > I like the controls that MM uses. What I have and need: a member > database [name, address, email, date dues paid, etc]. So I can do > this 2 ways: > 1) select name, email from members where xyz > file. Login to MM > empty member list - which is kind of painful then load file and > send the email. Then repeat for NOT xyz or This is an interesting idea, although it's more CRM than traditional MLM (and we have historically encouraged people to use CRM applications for CRM). We are currently accepting applications for GSoC interns. If you could provide a little bit more explicit requirements, perhaps it would make a good GSoC project. I'm not sure this is as easy as Abhilash's "try the API", so if we could get a student to flesh it out it make be useful for a lot of admins who need more realtime list administration flexibility -- I can think of applications for myself -- and don't want to go full-on CRM or just would rather do it with Mailman. Steve

6 years, 1 month

Search results for query "dO"