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

[MM3-users] Re: Remove login from list subscription page

by Mark Sapiro

On 3/1/22 12:23, bob B via Mailman-users wrote: > Is there any way to easily remove the login button for the List subscription page? 99% of our list do not use archiving, and log-in just confuses users so We would like for them just to be able to sign up to be on the list. You would need to patch postorius/templates/postorius/lists/summary.html Something like this would do what I think you want. ``` --- a/src/postorius/templates/postorius/lists/summary.html +++ b/src/postorius/templates/postorius/lists/summary.html @@ -101,20 +101,9 @@ {% endif %} {% else %} <div> - <h2>{% trans 'Subscription / Unsubscription' %}</h2> - <p>{% blocktrans %} - To subscribe or unsubscribe from this list, please log in first. - If you have not previously logged in, you may need to set up an account - with the appropriate email address. - {% endblocktrans %}</p> - <p><a href="{% url LOGIN_URL %}?next={{ next|default:request.path|urlencode }}" class="btn btn-primary">{% trans 'Log In' %}</a></p> - </div> - <hr /> - <div> - <p> + <h2>{% trans 'Subscription' %}</h2> {% blocktrans %} - You can also subscribe without creating an account. - If you wish to do so, please use the form below. + To subscribe to this list, please use the form below. {% endblocktrans%} </p> <form action="{% url 'list_anonymous_subscribe' list.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 years, 1 month

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

by Mark

> > The issue you're dealing with in that case is this change in > > PostgreSQL-15 discussed in this blog: > > > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… ********************** > If you have a Mailman-only host, with a Mailman-only PostgreSQL, or > The Cabal of equally responsible maintainers are the only people who > work on the Postgres cluster, the two approaches are basically > equivalent. > > My take is that the default "right thing" is to transfer ownership of > the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON > SCHEMA public TO fred" in the case that you don't want to give "sudo > mailman" to Fred. > > Rationale: I believe there are a number of things that the 'postgres' > user can do that other users cannot, and you probably don't want > random contractors or new volunteers to have those privileges. On the > principlee that 'postgres' should only do those things that only > 'postgres' can do, you want to make the 'mailman' user the owner of > the 'mailman' database (and 'mailmanweb' too if you go that route). > Then if you have a user 'fred' who may be working on both mailman and > non-mailman databases in a session, then instead of giving sudo > mailman to Fred, 'mailman' can grant all on schema public in mailman > to 'fred'. > > It's a really fine difference, and probably will matter to almost > nobody running Mailman 3. I do think > > user 'mailman' owns the 'mailman' database > > is conceptually simpler than > > user 'postgres owns the 'mailman' database and 'mailman' has ALL > privilege on the PUBLIC schema > > Right? ************************* === From the blog === ...almost any privilege escalation attack on a PostgreSQL database requires the attacker to create malicious objects. ... The public schema is the perfect vector for such a privilege escalation attack. ... In version 15, only the database owner can create objects in the public schema. === The user mailman has its plain text password written into the mailman.cfg file. If that is a potential weakness, would making mailman NOT the owner reduce vulnerability by a degree (in that objects could not be created in the public schema by using mailman's credentials)? Of course I would have a whole world of other problems if those credentials were misused, so I guess it's a bit theoretical anyhow.

1 year, 2 months

[MM3-users] MHonArc archiver setup/config?

by Stephen J. Turnbull

Bryan Fields writes: > I've had a request to setup this for a mm3 list. It looks like it's supported > from the config files, From the comments in the implementation files, I would say that no consideration has been given to private archives. I don't know how MHonArc handles that, so if it's a concern I can only warn you to be careful. > but I'm at a loss for exactly how to go about this. > Has anyone setup this with mm3 and can provide an overview? I haven't set it up. However, what I would do is 1. Copy .../mailman/config/mhonarc.cfg to /etc/mailman3 (or wherever you keep mailman.cfg). 2. Edit base_url and command in /etc/mailman3/mhonarc.cfg. base_url may already be appropriate for your system, but the "/path/to/archive" part of command will need to be adjusted. $hostname, $listname, and $fqdn_listname are variables supplied by Mailman at runtime. I don't know enough about MHonArc to say if the usage of $listname (just the local part of the posting address) and $fqdn_listname (posting address including domain) is appropriate. I would think you'd want to use the same variable in both places, so be careful. 3. Create any directories in "/path/to/archive" that MHonArc won't, and make sure they have appropriate ownership and search ("x") permissions all the way down. 4. Check that your webserver is configured to serve MHonArc at the location specified in base_url. 5. Add the stanza [archiver.mhonarc] enable: yes configuration: /etc/mailman3/mhonarc.cfg to /etc/mailman3/mailman.cfg 6. (Recommended) Mailman is perfectly happy to supply several archivers at the same time so add [archiver.prototype] enable: yes to mailman.cfg. This drops all the posts into a maildir somewhere under $var_dir as a backup in case the MHonArc archiving doesn't work, and nothing else -- it's not a usable archive for browsing. I guess there's probably a way to import them back into MHonArc, but if not presumably you can script it usng some variant of the command in mhonarc.cfg. Once the MHonArc configuration is doing the right thing you can disable it and delete the maildir contents. (Don't just "rm -rf $var_dir/archive", though -- Mailman uses that to queue messages being archived. I think archiver.prototype uses $var_dir/archive/prototype as its maildir.) 7. Restart Mailman. I don't think you need to do anything for Postorius, it will fetch the base_url from Mailman to populate the archive links. And that should do it on the Mailman side (except for the caveat about private archives). Steve

3 months

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

by Mark Sapiro

On 2/27/25 12:36, Kim Sunggun via Mailman-users wrote: > script: > #!/usr/bin/env python3 > import smtplib > > host = 'localhost' > port = 25 > connection = smtplib.SMTP(host=host, port=port) > connection.ehlo() > connection.quit() > > result: > Traceback (most recent call last): > File "/opt/mailman/./testone.py", line 7, in <module> > connection = smtplib.SMTP(host=host, port=port) > File "/usr/lib64/python3.9/smtplib.py", line 255, in __init__ > (code, msg) = self.connect(host, port) > File "/usr/lib64/python3.9/smtplib.py", line 341, in connect > self.sock = self._get_socket(host, port, self.timeout) > File "/usr/lib64/python3.9/smtplib.py", line 312, in _get_socket > return socket.create_connection((host, port), timeout, > File "/usr/lib64/python3.9/socket.py", line 856, in create_connection > raise err > File "/usr/lib64/python3.9/socket.py", line 844, in create_connection > sock.connect(sa) > ConnectionRefusedError: [Errno 111] Connection refused So you are doing the same thing Django allauth is doing with the same result. Do you even have an MTA listening on localhost, port 25? You need to figure out what settings you need to be able to connect to your outgoing MTA and set EMAIL_HOST EMAIL_PORT and maybe some of EMAIL_HOST_USER EMAIL_HOST_PASSWORD EMAIL_USE_TLS EMAIL_USE_SSL EMAIL_SSL_CERTFILE EMAIL_SSL_KEYFILE appropriately so you can connect to the MTA. If outgoing mail from Mailman works, look in the [mta] section in mailman.cfg for the appropriate settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Mark Sapiro

On 3/29/24 12:34, bob B via Mailman-users wrote: > Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. ... > So where can I look to try to determine a cause? > If it happens again, what and where can I cook to troubleshoot before restarting the service? One of the runners has died, most likely the `out` runner, but possibly another. The missing messages are stuck in a queue. Do ``` ls -laR /opt/mailman/core/var/queue ``` to see in which queue the messages are. The runner that processes that queue is gone or possibly stuck. Do ``` ps -fwwu mailman|grep runner= ``` when things are working to get a list of what runners should be there. Do it again when things aren't working to see what's missing. There also should be something in mailman.log about why the runner died, but if it was killed for some external reason, there may not be anything. Look in `syslog` for something like an out of memory (OOM) or other issue that caused the runner to die. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Replies

by Mark Sapiro

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

3 years, 1 month

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/14/24 08:42, jkoral(a)luc.edu wrote: > joetest(a)listservnew.luc.edu is the list, but in postfix_lmtp, it is showing up as joetest(a)luc.edu. Where can I change that? I tried changing the domain and site, but it still has not changed. The list has a mail_host attribute which is set when the list is created. Presumably, you created the list as `joetest(a)luc.edu`. You have to change the mail_host attribute of the list, but it may be easier to just delete it and create a new joetest(a)listservnew.luc.edu list. Then you can ignore everything below. To change the mail_host for the list you can do a database query or use `mailman shell`. The database query is ``` UPDATE mailinglist SET mail_host = 'listservnew.luc.edu' where list_name = 'joetest'; ``` The `mailman shell interaction is ``` $ mailman shell -l joetest(a)luc.edu Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> m.mail_host = 'listservnew.luc.edu' >>> commit() ``` If you do either of the above to change the mail host, you probably need to do `mailman aliases` to regenerate the files for Postfix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

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

by Rafael Mora

El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:58 PM, Rafael Mora wrote: > > > > Does the rDNS PTR record should be placed in my Centos7 server? > > You can't do this. Hostgator or whoever manages the network (Telmex > Colombia S.A. ?) has to do this. > > > > I've created the DNS A record for lists.labbrands.com with the IP but I > > don't know the port that it uses so I can make a port redirect to my > local > > ip address wich is 192.168.1.42, do you know the port????? > > > You need to forward port 25 for SMTP mail delivery and if you want the > web UI (Postorius and HyperKitty) accessible from the outside, port 80 > for http and/or port 443 for https > < > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >. > I mean for incoming mail redirected from my hostgator hosting, because when I suscribe an email address MM3 sends a confirmation email, so I have to reply to be suscribed to the list. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] mailman3 digest sending questions and also adding docker to the mix

by bob B

So I have been down the digest rabbit hole. So to confirm my assumptions/findings: Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? My use case is, that I have a list admin who set a size threshold, but regardless of that, they also want their list digest sent out daily, they thought it was the "Digest Volume Frequency" setting but that is not correct. However in their testing they are not getting daily digest, they are getting digests only when the threshold is reached, BUT they have "Send Digest Periodically" set to "yes" and "Enable Digests" is set to "yes"

3 years

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

by Tim Cutts

Yup. I noticed that when I went through this two days ago. I hadn’t got around to mentioning it yet. :-) > On 8 Jul 2022, at 18:01, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/8/22 9:16 AM, kisner(a)live.com wrote: >> Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros. > > > The issue is when you do > ``` > pip install psycopg2-binary<2.9 > ``` > your shell (sh, bash, zsh or whatever) interprets `<2.9` as an input redirection and probably says something like `2.9: No such file or directory`. You need to do something like > ``` > pip install psycopg2-binary\<2.9 > ``` > or > ``` > pip install 'psycopg2-binary<2.9' > ``` > I'll update the doc. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 9 months

[MM3-users] Re: Mailman 3 stops delivering to a domain after too many bounces

by Stephen J. Turnbull

Julian Kippels writes: > Additionally if the MTA would reject connections from IPs that > generate too many errors, then why is Mailman 3 still able to > deliver to domain B and C when domain A has already failed? Because *Mailman* doesn't doesn't handle bounces by domain, only by address. It will send to your MTA every address on the list that is enabled, regardless of whether transmission to other addresses at that domain failed. The *MTA* handles domain-level lossage such as DNS and network outage. Mailman is blissfully unaware of that until the individual addresses start bouncing (which by default in most MTAs takes a week or two of retries), but it doesn't care if they're all from the same domain, it handles each one individually without affecting other addresses at that domain. > Currently I am trying to write a script to check if mail aliasses are > alive and remove users if that check should fail. This isn't straightforward, as most site now disable the SMTP verify command. IIRC you need to open a connection, do the HELO, MAIL FROM, RCPT TO dance, check for error (if so, record as a bounce), and then close the connection before issuing the DATA command. > I plan to run this as a cron job for every list every night. I find it hard to imagine that's useful. I'm not sure why you would have accumulated large numbers of dead addresses on Mailman 2 lists unless you had bounce processing disabled. Nevertheless, if you do hav dozens per list, running the script once a month should be enough unless you have really mammoth lists (> 10,000 subscriptions), or your subscribers are changing addresses as frequently as spammers do. > I don't think that this is a good option, but I don't see anything > better right now. What version of Mailman 3 are you running? I don't recall the version offhand, but bounce processing was fully implemented only about two or three years ago. Recent versions of Mailman 3 will automatically disable, and eventually remove, subscriptions that bounce "often enough" (ie, the number of bounces and interval until various purges of old bounce information are configurable). If you want to purge a large number of "dead" addresses quickly, just set the disable and delete levels very low, then set them back to default. That should do the trick. Note that some distros provide rather old versions of Mailman 3, where bounce processing did not work. Steve

2 years, 9 months

[MM3-users] Re: list of subscribers

by Peter Münster

On Mon, Feb 05 2018, Simon Hanna wrote: >> from django.contrib.auth.models import User >> user = User.objects.get(email='address(a)of.user') >> print(user.first_name) >> print(user.last_name) >> >> So, I'll try to make some loop over a list with email addresses, that I >> can get on the web interface. > > These are names that are saved in Postorius' (django) database and have > nothing to do with mailman. I know, but for my use case, it's just what I want, and it seems to work. > Displaying the names stored in django probably won't happen. > Matching the names in django with the members in lists > would require lots of code Really? I don't know Python, but wouldn't it be possible (just as an option) to do something like this: user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name If there is no Django account associated to the email address, the columns would just be empty. I think, that my use case is perhaps not so special: whenever you manage a sports club, you'll need lists like - members(a)my-club.com - board(a)my-club.com - team-1(a)my-club.com - team-2(a)my-club.com - and so on Whenever there is a new member, the administrator will do the sign up with create_user(...) and subscribe him to the right lists. And the members (or the moderators) should be able to check the subscriber list sometimes. -- Peter

7 years, 2 months

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

by John Covici

It was in https://asynchronous.in/docker-mailman On Sun, 01 Aug 2021 16:55:11 -0400, Abhilash Raj wrote: > > > > On Sun, Aug 1, 2021, at 1:52 PM, John Covici wrote: > > I am finding some missing documentation in the section on configuring > > mailman-web, it refers to a file > > https://asynchronous.in/docker-mailman/web/ which does not exist. > > Try https://asynchronous.in/docker-mailman/web.html > > Can you point me where you saw the original URL so I can update it? > > > > > > > > On Sat, 31 Jul 2021 21:21:24 -0400, > > John Covici wrote: > > > > > > OK, thanks a lot -- if anyone here can help with proper config for > > > those, that would be great. I do have a web server, but its apache > > > rather than mginx and I am not sure how to properly translate. Also, > > > doing a separate container for an mta which would just talk to > > > mailman would get around the sendmail situation I have, although > > > there may be a decent way to do that as well. I guess the hard part > > > is to tie the multiple containers together. > > > > > > > > > On Sat, 31 Jul 2021 17:56:15 -0400, > > > Abhilash Raj wrote: > > > > > > > > > > > > > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > > > > I have a couple of questions about the container, if its OK. > > > > > > > > Sure it is :) > > > > > > > > > > > > > > First, it says to run you create the directory > > > > > /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the > > > > > git clone. What directory should the git clone be in? > > > > > > > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > > > > > > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > > > > > > > A couple of more questions -- is there a way to install the web server > > > > > and the mta in the container, this way I could make the whole thing > > > > > be independent of my host configs? > > > > > > > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > > > > > > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > > > > > > > > > > On Fri, 30 Jul 2021 16:04:48 -0400, > > > > > bob B wrote: > > > > > > > > > > > > is this the info you need for the container version > > > > > > > > > > > > [root@..... docker-mailman]# docker ps > > > > > > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > > > > > > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > > > > > > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > > > > > > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > > > > > > > > > > > > > > > > for smtp host > > > > > > ------------ > > > > > > cat /opt/mailman/web/settings_local.py > > > > > > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > > > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > > > ALLOWED_HOSTS = ['*'] > > > > > > DEBUG = True > > > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > > > > > EMAIL_HOST = 'smtp.example.com' > > > > > > EMAIL_PORT = 25 > > > > > > --------------------------- > > > > > > cat /opt/mailman/core/mailman-extra.cfg > > > > > > # mailman-extra.cfg > > > > > > > > > > > > [mta] > > > > > > incoming: mailman.mta.postfix.LMTP > > > > > > outgoing: mailman.mta.deliver.deliver > > > > > > # mailman-core hostname or IP from the Postfix server > > > > > > lmtp_host: localhost > > > > > > lmtp_port: 8024 > > > > > > # Postfix server's hostname or IP from mailman-core > > > > > > smtp_host: smtp.example.com > > > > > > smtp_port: 25 > > > > > > configuration: /etc/postfix-mailman.cfg > > > > > > [mailman] > > > > > > # This address is the "site owner" address. Certain messages which must be > > > > > > # delivered to a human, but which can't be delivered to a list owner (e.g. a > > > > > > # bounce from a list owner), will be sent to this address. It should point to > > > > > > # a human. > > > > > > site_owner: my_real_email_is_in_the_file.com > > > > > > __________________________________ > > > > > > > > > > > > My docker most machine /etc/postfix/main.cf has > > > > > > > > > > > > transport_maps = > > > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > > > local_recipient_maps = > > > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > > > relay_domains = > > > > > > regexp:/opt/mailman/core/var/data/postfix_domains > > > > > > > > > > > > > > > > > > # Support the default VERP delimiter. > > > > > > recipient_delimiter = + > > > > > > unknown_local_recipient_reject_code = 550 > > > > > > owner_request_special = no > > > > > > > > > > > > ------------------------------ > > > > > > > > > > > > > > > > > > > > > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > > > > > > > > > > > > > > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > > > > > > _______________________________________________ > > > > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > > > > > > > -- > > > > > Your life is like a penny. You're going to lose it. The question is: > > > > > How do > > > > > you spend it? > > > > > > > > > > John Covici wb2una > > > > > covici(a)ccs.covici.com > > > > > _______________________________________________ > > > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > > > > > > > > -- > > > > thanks, > > > > Abhilash Raj (maxking) > > > > > > > > > > -- > > > Your life is like a penny. You're going to lose it. The question is: > > > How do > > > you spend it? > > > > > > John Covici wb2una > > > covici(a)ccs.covici.com > > > _______________________________________________ > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > > Your life is like a penny. You're going to lose it. The question is: > > How do > > you spend it? > > > > John Covici wb2una > > covici(a)ccs.covici.com > > > > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

3 years, 8 months

[MM3-users] Re: Emergency Moderation

by Allan Hansen

In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ My own current top-of-the-list issues: A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. Otherwise things appear to be running smoothly (I’m currently knocking very hard on an actual piece of wood - not my head). :-) Yours, Allan Hansen hansen(a)rc.org > On May 24, 2020, at 7:27 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Brian Carpenter writes: > >> Can I add this through a mailman core update via pip? > > Eventually .... This depends on when Abhilash gets enough content and > a little bit of time to do a new release. > > Getting meta: You've been asking for very recent features fairly > frequently. I understand that everybody feels better with released > code, but to be honest, we do not have a deep quality assurance > process. The test suite is voluminous and quite comprehensive, but > that's not the same as having a proper beta process, mandatory > reviewing, etc etc. It's not obvious to me that we can do a better QA > for you than you can do for yourself. > > With that in mind, have you considered building your own from source, > on a branch from a moderately recent tag, and cherry-picking only > commits for features you really want right now? > > I admit I don't know how appropriate that is in our tree (I just build > from master all the time), but I think that Abhilash is probably > pretty careful to pull complete branches so that this should work. If > it looks to you like the patches are a little "ragged around the > edges", we can work on the process and try to make it more amenable to > such cherry-picking for people like you who need some of the most > recent commits ASAP, but don't want to accept the whole "bleeding edge". > > This also would be useful for your Affinity etc development, I think. > (Of course maybe that's what you're talking about, but "emergency > moderation" is a pretty common need in production.) > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 10 months

[MM3-users] How to Increase outgoing mail volume for Mailman 3

by Brian Carpenter

Hello everyone, We had a new client come on board that brought a list that had the largest out-going mail volume that I have ever dealt with. So I did what any sane server administrator would do that is running Mailman 3: I ran to Mark Sapiro for help! Here is what the Sage of all things Mailman counseled me to do: 1. Disabled VERP delivery. VERP can help improve mail delivery by delivering 1 message per SMTP transaction (I think I got that right). Using VERP is counter-productive as it can seriously delay outgoing mail delivery for a high-volume list. So you can use something like the following in the MTA section of your mailman.cfg: [mta] verp_confirmations: no verp_personalized_deliveries: no verp_delivery_interval: 0 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. This action was the game changer. It allows Mailman to handle 4 incoming messages at a time instead of 1. My client's incoming list volume was high enough where it was overwhelming the single outgoing runner. Here is what I added to the mailman.cfg file: [runner.out] instances: 4 Doing this step immediately solved the backlog in var/queue/out. 3. If you start up with a new server for a list that is high volume then keep an eye out for Proofpoint and Vade Security as they will block your new IP address quicker than Mark Sapiro can say "This is a bug. See <some Gitlab.com url>" Mark, thank you! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

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

by Bill Christensen

On 6/23/18 5:01 PM, Mark Sapiro wrote: > 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? the general syntax we're using is: poll imap.gmail.com protocol IMAP username "<list address>" there with password "<password>" is "mailman" here nofetchall keep ssl sslcertck sslcertpath /path/to/share/ssl/certs mda "/path/to/mail/mailman post <listname>" set daemon 900 > > 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. I think that's what the above is doing. Right? > > 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. > -- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108 Dance like nobody's watching. Encrypt like everyone is. --Adrián Lamo

6 years, 10 months

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

by Stephen J. Turnbull

Jonas Meurer writes: > But in my eyes, software developers, package maintainers and system > administrators all should do their best to protect their users from > privacy and/or security threats. Me too. Passwords are a well-known vulnerability, providing a large attack surface. I'd rather not burden Mailman providers with protecting their users' credentials, other things being equal. They're not, so we have to decide (individually and as a project) which vulnerabilities are more frightening, and how much configurability to provide, and how. > Probably we have a different opinion on whether providing usage of > authentication providers which earn their money by collecting > users' data exposes users to privacy threats. We do not. We differ on the importance of those vulnerabilities to the users. > I have a different opinion on this. You're correct that most users know > next to nothing about protecting themselves against all kinds of threats > on the internet. But to me this shows even more, that we as those who > build the tools have a responsibility to protect our users against > shooting themselves in their foot. See my reply to Worik on this. > But that doesn't mean that we as independent and free software > developers have to agree on the dangerous interfaces and standards > those corporates develop (for their business!). Sure. This is a valuable service which for most users reveals very little information: the domain and IP that the user wants to authenticate to. If I were the type to visit porn or RWNJ sites, I wouldn't use GMail as my auth provider, and I'd probably use Tor as my ISP. I have no problem with using Gmail as my auth provider to Google Summer of Code (!) and Github. Why do you think it's a problem to allow users to make the choice? As I mentioned to Worik, I wouldn't mind allowing customization of the interface, with a warning displayed about social auth. I do not see any argument for preventing them from making the choice. > My irritation was mainly about what I wrote above: that the privacy > concerns against authentication providers from big corporates seem > to be of low priority when deciding about defaults in Mailman3 > upstream. Then you misunderstand. We explicitly made the decision to emphasize social auth *in part* because *as authentication* is far more secure than (1) passwords and (2) most mom and pop sites. I'll grant that the "coolness" and user demand factors matter, too. And the privacy implications generally seem minor with a few exceptions (see the mentions of "DV" in my message to Worik). > To be honest, I've never evaluated the privacy implications of > OpenID. From a first glance, it looks *way* better. AFAICS (first glance in several years), OpenID is no better: the on- the-wire information is provided in basically the same way, and it looks like the content is arbitrary. The FAPI (financial information) and HEART (health information) protocols look especially tasty to big data users/privacy invaders The question is what do the providers provide (account identifier, real name, address, gender orientation, where you buy your illegal drugs ...) and what the client asks for (Mailman asks if user credentials are valid). > But for sure, Github, Google, Facebook, Stackexchange and Twitter > all rely on collecting users data for their business model. So it's > probably not a good idea to share with them the information which > platforms and services you authenticate against, *if* you care > about privacy. I'm far more worried about the video cameras that are everywhere nowadays, hacks of government databases, people who record "private" conversations in person and otherwise, and which of my passwords are going to show up on haveibeenpwned.com next week. Steve

6 years, 2 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > Folks, > > For my own purposes I have created some patches which apply to the > current mailman pip package. I'm only responding here to the issue of how to suggest patches. If you hope that they could be incorporated into the distribution, posting them to this list is not very effective. It is too easy for list posts to get lost, buried or forgotten. The best thing to do is to create an issue or issues at <https://gitlab.com/mailman/mailman/-/issues> (each issue should address only one thing). Then you can either attach the suggested patch to the issue or better, create a merge request with the patch to fix the issue. Ideally, the merge request would also contain relevant additions to unit tests. The first advantage is open issues do not get lost. They are always there in the tracker. The second is that all of the above is work that needs to be done in order to actually get the patch into the master branch, and the more of it you do, the less of it needs to be done by someone else who may not be as motivated as you are. Granted, this may seem like a burden for you. After all, you fixed your problem so why bother, but open source works best if we all contribute what we can to improve the product. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

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

by Kyriakos Terzopoulos

Hi Stephen, all, The issue is resolved. I had in my /etc/hosts this: 127.0.0.1 hestia.myserver.com which I removed. No more mail being marked as spam. However I face a (hopefully) new problem now. When I mass subscribe the users, they get an initial invitation email. However after replying I get this in the exim logs, the subsequent mails do not arrive and the users are not verified at all: 2023-10-25 13:36:41 1qvbFh-001kcb-Ig <= myname(a)myproject.eu H=localhost ( webmail.myproject.eu) [127.0.0.1] P=esmtpa A=dovecot_login: myname(a)myproject.eu S=1726 id=32091a0e12cc23fa988380639a4c44a6@ myproject .eu 2023-10-25 13:36:41 1qvbFh-001kcb-Ig == partners(a)myproject.eu < partners-confirm+6df62cd0f805b2b66b21a43a42ec8ee77487e8ad(a)myproject.eu> R=mailman3_router T=mailman3_transport defer (-54): retry time not reached for any host for ' myproject.eu' Can you kindly provide your feedback on this? *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Tue, 24 Oct 2023 at 15:36, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Kyriakos Terzopoulos writes: > > > Some research showed me that I needed a rDNS entry in my > > server. I'm on a Hetzner cloud VM so I used the Hetzner console to > > change the rDNS entry from: > > > > static.XXX.XXX.XXX.XXX.clients.your-server.de > > Don't do that. Aside from inducing the 127.0.0.1 problem you > experience, some recipients insist on a reverse lookup that > "round-trips", so that if you look up the HELO name, and then look up > the IP returned, you get the HELO name back. > > > Oct 24 14:17:47 2023 (3759611) > > <169814622178.3759638.4589434779084932533@localhost> *response > exception: > > (550, b'Helo name contains an IP address (HELO was [127.0.0.1]) and not > is > > valid'*, 'testlist-bounces+myusername=myproject.eu(a)myproject.eu') > > I don't understand why you get the loopback IP address in HELO. Maybe > somebody else can explain. > > > The weird thing is that when I do a mailman-web sendtestemail this > > email is sent successfully. > > That's not entirely surprising. When you send mail via a Mailman list > a lot of processing gets done and it passess through three separate > processes that are basically doing Internet mail: the incoming MTA, > Mailman, and the outgoing MTA. mailman-web sendtestemail there's only > one Internet-capable agent, which is the outgoing MTA. > > Steve > >

1 year, 5 months

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

by Mark Sapiro

On 3/16/21 11:34 AM, Per Jessen wrote: > > I'm trying with this: > > find /var/spool/mailman/bad -type f -name \*pck |\ > while read m > do > (mailman qfile $m | grep -q ad.dr@ess) && echo $m > done > > Is there a better way? Yes, as you've noticed there is a significant startup cost every time you invoke the `mailman` command. to invoke it only once first see ``` mailman shell --details ``` (that refers to `mailman withlist` which is just another way to spell `mailman shell`). You will want to create a script similar to the following: import pickle from os import listdir def findaddr(address): for fname in listdir('/var/spool/mailman/bad'): if not fname.endswith('.pck'): continue with open(fname, 'rb') as fp: msg = pickle.load(fp) if address in msg.as_string(): print(fname) That's your script. Save it as findaddr.py where `mailman shell` can import it and run ``` mailman shell -r findaddr.py -- ad.dr@ess ``` This should print the names of any pickles that contain 'ad.dr@ess' Note however that this may not be necessary. If all you want is the names of the .pck files that mention 'ad.dr@ess', ``` grep ad.dr@ess /var/spool/mailman/bad/*.pck ``` should actually work reporting things like Binary file /var/spool/mailman/bad/*.pck matches with the actual file name, 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, 1 month

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

by Stephen J. Turnbull

Henrik Rasmussen writes: > What I meant was, that the list admin may be able to set the list > to Open or Moderate, making it possible to subscribe others, and I > was told by our GDPR folks that we have to make the subscribers > re-confirm, so I was just trying to figure out a way to do it. I > don't know very much about GDPR yet. I think Mark misinterpreted "re-confirm". I assume you mean forcing the *existing* subscribers to perform some action to confirm that they still want to be subscribers. This is not currently a feature of Mailman 2 or Mailman 3. We only can require confirmation at initial subscription, except by something like unsubscribing or no-mail'ing everybody as Mark suggested. > I agree, I wouldn't remove [the mass subscription feature] either, > but I just have to be concerned about the possibility that someone > may have been subscribed against their will. I think you would hear about that. Re-confirmation in light of new rights for subscribers and responsibilities for providers seems reasonable to me, but I think it's reasonable to assume list admins are not malevolent. In light of GDPR, we may need to develop ways to enforce site policy about subscription confirmation and ability of users to unsubscribe themselves at will. > Is there a way to resend a confirmation request to either those who > haven't been requested to confirm or alternately to all > subscribers? It seems to me that what most organizations are doing is not to force reconfirmation, but rather informing their users of 1. their GDPR rights 2. what PII is present in the relevant databases 3. how to terminate the relationship if desired In the case of Mailman, you might also want to 4. require SSL to access the website 5. advise the users to change their passwords if you had been allowing access via HTTP or sending password reminders For stock Mailman 2, this is not a big deal (I don't think any of the subscriber configuration information is PII except display name and address), but for Mailman 3 I believe there's some profile information in HyperKitty that might be considered PII, and Mailman 3 will be easier to extend using plugins etc to potentially incorporate even more. Mark Sapiro writes: > Or, post to the list that everyone will need to resubscribe and > then remove everyone. Note that this means that people who resubscribe late will miss mail. That may or may not be a big deal. Steve

6 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I want to use Mailman to send emails to our customers. I´m getting this error when I click on sign up and log in: FilterError at /accounts/login/ /bin/sh: sassc: command not found Request Method: GET Request URL: http://192.168.1.42:8000/accounts/login/?next=/postorius/lists/ Django Version: 1.11.3 Exception Type: FilterError Exception Value: /bin/sh: sassc: command not found Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py in input, line 196 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 What's missing??? El vie., 21 jul. 2017 a las 19:57, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:57 PM, Rafael Mora wrote: > > Should Sign Up ?? Log In?? > > > Yes. > > > > El vie., 21 jul. 2017 a las 18:56, Rafael Mora (< > rafael.mora.guti(a)gmail.com>) > > escribió: > > > >> Nice! Up and running! > >> > >> How do I start using mailman? what are the steps?? > > > What do you want to do with Mailman? This is the key question. > > There is some list subscriber documentation at > <http://docs.list.org/en/latest/userguide.html>. > > You can create domains and lists via Postorius or via the core's > bin/mailman commands ('bin/mailman --help' for a list). > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

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

by brian＠emwd.com

Abhilash Raj wrote: > 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. This is what I found but sporadic: ERROR 2018-12-22 13:54:07,233 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:07,252 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:07,686 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:07,721 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:08,447 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. > There must be some errors showing up, causing emails to not be archived. I am not seeing any other errors. 1. Do I need mailman-hyperkitty.cfg setup in the /opt/mailman/core directory? 2. What ownership/group does the file structure need to be in the /opt/mailman directory? I am wondering if the hyperkitty issue has something to do with permissions? It seems HK should work out of the box with your docker setup if I read your documentation correctly. Is that correct? At this moment I am dead in the water. Is there anyway to try to test the archiving and see if the logs shows an error using the tail -f command? Brian

6 years, 4 months

[MM3-users] Re: No recent activity discussions and activity overview shown. Only a spinning wheel.

by Stephen J. Turnbull

Freerk Bosscha via Mailman-users writes: > I have recently setup a fresh mailman3 installation on my debian12 > box. If this is a Debian package, you should report to them. Debian maintainers make the patches they think are wise, and often go well beyond conformance to Debian policy on file locations and the like. Also, while MySQL is a supported backend database, and the main problem I know of seems to be addressed with the "?charset=utf8mb4&use_unicode=1" parameters in the db url, I believe the developers mostly run PostgreSQL. So if there is a database communication issue, the Debian developers may be more aware of it. > In my opinion this should be ok and the qcluster is running I don't know what you meant by "looks like an AJAX problem" -- if you have specific knowledge of such problems, please enlighten us, but otherwise it is very unhelpful to guess. Also, what do you mean by "the archive files are getting the archived messages"? If you know what you're doing you may be able to find archived messages in your RDBMS, but in principle HyperKitty just stores them as blobs in the RDMBS -- HyperKitty doesn't see them as files. Now, what Sam is pointing out suggests that qcluster is not talking to qinfo, and therefore it may not be talking to HyperKitty. Since queues are implemented as files on disk, it's likely that qinfo is counting them using filesytem utilities, while it's talking to qcluster over a socket. Anyway, I don't think the "clusters 0, workers 0" report is good news. Also, I believe the "successful" queue is a measure of backlog. I've seen backlogs of that size on a site with thousands of archived lists and hundreds of thousands of posts per day, but I don't think it's normal for typical scales. I have seen it take many minutes for the recent activity to show up in HyperKitty on that huge site. I don't recall what the problem was, maybe something to do with a backlog in the full-text indexer (Xapian on that site). Unfortunately I don't recall how that was resolved, and don't have access to that system any more. In general, IIRC, qcluster is a red herring for the activity display. It's used to manage the incoming queue from Mailman core for the archive but I don't think it's relevant to fetching data. HyperKitty fetches that directly from the database. I would guess that the issue has to do with communication between HyperKitty and the database. Steve

2 months, 3 weeks

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

by Mark Sapiro

On 3/22/22 07:46, ryan.anderson.4--- via Mailman-users wrote: > 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. You can accept HTML and not convert it if in Postorius -> Settings -> Alter Messages, assuming Filter content is yes, ensure Pass types includes `text/html` or maybe `text` to include all text maintypes and both Collapse alternatives and Convert html to plaintext are set to No. > The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . They probably aren't ` and -, but rather things like Unicode Left Single Quote and En Dash. > 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. When you say you changed the character set to UTF-8, what did you do? If you set ``` [language.en] charset: utf-8 ``` in mailman.cfg and restart mailman core, that should allow those characters without replacing 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] Re: Strange password problem

by Eggert Ehmke

Hello Roland, That's exactly my situation. Am Samstag, 23. September 2023, 18:57:24 CEST schrieb Roland Miyamoto via Mailman-users: > Dear Stephen, Eggert and everybody. > > On 23/09/2023 13:02, Stephen J. Turnbull wrote: > > > What are you doing that requires admin privileges, but you want to > > authenticate separately for each domain? I ask because we've always > > envisioned creating a domain-level administrator role, but until now > > we've had no demand for it. > > > I could easily imagine a situation > where I'd need an admin per domain: > > On my server I have lists > > @lists.domain1.tld > @lists.domain2.tld > @lists.domain3.tld > > that are associated with websites > > www.domain1.tld > www.domain2.tld > www.domain3.tld > > used by separate "customers"¹ of my server. > The "customers" do not know each other > and might want to create additional lists in *their* domain. > > Currently *I* create all lists for all my "customers", > but with list-domain admins I could leave that job > to the respective "customers". > > Right? > > Best wishes, Roland > > -- > > ¹) "customers" in quotes because they do not pay for my service. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message > /L2SGU5ADFEMKRLPVDMTTEGJ52GE2JBSS/ > > This message sent to eggert(a)eehmke.de

1 year, 7 months

[MM3-users] Re: installation choices for mm3

by Mark Sapiro

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

5 years, 11 months

[MM3-users] Re: Subject Munging

by Mark Sapiro

On 7/5/24 08:34, Sam Darwin via Mailman-users wrote: > Hi, > > We have a user who is proposing that reply messages from a mailing list should be in the following format: > > Re: [MM3-users] Ubuntu 24.04 upgrade notes > > and not > > [MM3-users] Re: Ubuntu 24.04 upgrade notes > > Their reason... is that mailman2, and other lists, used to do it that way. > > I myself am agnostic about the difference, and probably prefer to keep things the way mailman3 recommends. > > The questions are: > 1. What could be explained to the user to convince them the new method is preferable. This is to support prefixes that contain %d for the message number. Suppose the prefix is [List #%d] and a post to the list has prefixed subject [List #501] A Subject. With old style, a reply a few posts later might have subject Re: [List #504] A Subject. But it is not a reply to [List #504], it is message [List #504] replying to `A Subject.` so the appropriate subject is [List #504] Re: A Subject. > 2. Can this be customized with a Setting? (Not that we will end up modifying it. Just curious). In mailman 2.1 this was called OLD_STYLE_PREFIXING and prefixes without %d could optionally do it the old way or the new way , but prefixes with %d always did it the new way. For Mailman 3 we always do it the new way even if the prefix does not contain %d. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

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

by tim＠thecutts.org

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 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. Are these issues likely to be related, or do I have two things going on here? Regards Tim

2 years, 9 months

[MM3-users] Re: Your Dashboard

by Mark Sapiro

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

5 years, 2 months

[MM3-users] Re: Scheduled tasks

by Darren Smith

So I don't know how in the world we missed the qcluster and running that. Pretend I'm a python novice (that would be correct) - can you tell me what the ramifications of not running this? I have attempted to start the queues running, but it caused the entire machine to be consumed processing things. So I'm going to have to do this later at night again when our customers won't be as inconvenienced. This is one of those times that I wish that I had been able to understand everything deeper before we had to switch to the new system. Live and learn I guess. -Darren On Thu, Jun 7, 2018 at 9:57 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > I will take up any problems with the installation with the creator. > However, I was able to find and run some of the scripts this afternoon, and > I'm running some of the longer-running ones tonight while the usage is > lower. > > As for bogging down - I mean attempting to click on an email can take a > LONG time to render, and we frequently get 504 gateway timeouts (the calls > to hyperkitty are timing out). I am trying hard to figure out why this is > happening and to try to tune the system. I still suspect that there are > some inefficiencies with how the database is being used, or how the > database is doing things. > > I will take a look at qcluster, that was interesting info and hopefully it > can help me out. > > Thanks for your response, > > -Darren > > On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/7/18 9:59 AM, Darren Smith wrote: >> > All, >> > >> > I am looking more through the documentation of the Mailman Suite here: >> > >> > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf >> > >> > In section 3.2.5 it talks about the scheduled tasks that need to be run >> to >> > do "specific routine functions" in hyperkitty. >> > >> > I installed through the easy install script found here: >> > >> > https://github.com/iomarmochtar/mailman3_ei/ >> > >> > However, I can't find anything in THAT documentation that talks about >> these >> > cron jobs, and in fact the Mailman Suite isn't installed through that >> > script. >> >> >> That is a third party project. If you have issues with it, you should >> take them up with @iomarmochtar. >> >> >> > Can someone point me to any other documentation about the tasks that >> need >> > to be run on a continual basis? >> >> >> The section 3.2.5 you refer to tells you what needs to be set up in >> cron. For a list of the jobs tat are run, use >> >> django-admin runjobs --list >> >> >> . Our hyperkitty installation seems to be >> > bogging down more and more, and I am hoping that it will be as simple as >> > just running some jobs that haven't been on our radar. >> >> >> what do you mean by 'bogging down'? If you aren't doing so, setting up >> qcluster as in section 3.2.3 may help. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> 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, 10 months

[MM3-users] Re: Hyperkitty message threading

by Stephen J. Turnbull

andrew.bernard(a)gmail.com writes: > So the issue is, how do I stop my users from this practice of > replying and changing the subject? This is frequently called "thread hijacking." But be thankful that they at least change the Subject! My worry is more people who start in on a completely new subject without doing it, and then complain that they get ignored because they're off-topic for the thread. > I suppose there is no way except education. That's right. If you had the resources of a major AI lab, you could probably train up a classifier to do the job fairly well, but in practice it's a matter for human judgment. Eg, I know that I frequently change the Subject: several posts after others have, eh, "evolved" the subject into a completely different thing :-), so it's useful to have proper threading across the subject change.[1] One practice I found effective was to impose moderation on people who just couldn't practice proper netiquette, then reduce moderation frequency to once a week. ;-) A week is probably overkill. :-þ (I happened to be in a period of frequent travel for two weeks and at the beginning of that period there was this jerk.... He learned.) Once-a-day moderation is sufficiently frustrating for most people to be an effective re-education tool. Steve Footnotes: [1] There was a day and age *sigh* when educated people would *frequently* change the subject to reflect the subject of the *message* rather than the subject of the *thread*. That's gone the way of traditional inlined replies are going, though.

5 years, 9 months

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

by Mark Sapiro

On 8/9/22 07:19, Stephen J. Turnbull wrote: > > You don't do it with HyperKitty (I'm pretty sure you can export mboxes > from HyperKitty, but I don't think it would be timely, you have to do > it by hand). The sample archiver (which you can enable in mailman.cfg > IIRC, haven't done it in a while) would make the mbox files directly > from the core at the same time that they are sent to HyperKitty. It's > possible to have both HyperKitty and the sample archiver enabled at > the same time. The `sample archiver` is actually called the prototype archiver and it is typically enabled by default. The messages are stored in maildir format in Mailman's var/archives/prototype/ directory in sub-directories with names of the list posting addresses. You would need to convert maildir to mbox format to import to hyperkitty. A simple script to do this is ``` #!/usr/bin/python3 """Run this with the list posting address as it's argument.""" import os import sys from mailbox import mbox, Maildir MDIR = '/path/to/mailman/var/archives/prototype/' MBOX = '/path/to/output_directory' if len(sys.argv) != 2: print(f'Usage: {sys.argv[0]} list_posting_address', file=sys.stderr) sys.exit(1) mdir = Maildir(os.path.join(MDIR, sys.argv[1]), create=False) mlbox = mbox(os.path.join(MBOX, sys.argv[1]), create=True) for msg in mdir: mlbox.add(msg) mdir.close() mlbox.close() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

On 10/31/24 16:17, Hirayama, Pat wrote: > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Then for example if your list domain is example.com and its alias domain is x.example.com, you could modify one line in the postfix_vmap file for the `listname` mappings from ``` listname-bounces(a)example.com listname-bounces(a)x.example.com ``` to ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` and then run postmap on the file. The problem is any time you create or delete a list or run `mailman aliases` or run `mailman start` with the --generate-alias-file option, the file is regenerated and you will have to edit it again. To avoid that issue, you can create a separate vmap file containing only the ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

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

by Terri Oda

I don't *think* we have a checkbox for this, but I've definitely seen this behaviour in Mailman 2 and had trouble with Mailman getting blocked as a result, so I think this would be a very nice feature request. Terri On January 16, 2020 10:49:38 a.m. PST, Torge Riedel <torgeriedel(a)gmx.de> wrote: >Hi, > >we migrated successfully to mailman3 so far. I have some questions >regarding handling of SPAM mails in mailman, here is the first, second >comes in a separate post: > > >The list moderator currently receives a copy of the original mail in >the info mail he gets for moderation. This is bad in case it was a SPAM >mail, cause we have seen that such an info mail is detected also as >SPAM. That might rise problems cause other mail servers might block the >info mail as SPAM and if this happens too often blocking the whole >server. I fear. At least I see that my rspamd starts learning the info >mail as SPAM. I don't want that to happen. > >I searched mailman web interface for a setting to disable adding a copy >to the info mail. But have not found it. Is it missing or where do I >have to look? > > >Best regards >Torge >_______________________________________________ >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, 3 months

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

by Henrik Rasmussen

Mark Sapiro wrote: > I'm confused. Confirm sends a confirmation request to the subscribed > address which must be acted upon by the user before she is added to the > list. Moderate just means approval by an owner/moderator Oh sorry, you're right, I mixed up those two. > which, it seems > to me is more susceptible to a 3rd party subscribe succeeding - i.e., > subscription requires membership in some organization. A subscribes B > who is a member of the organization but doesn't want to be on the list. > The moderator verifies that B is an organization member and approves the > subscription. What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. > Granted that this can be abused, but not allowing admins to directly add > members will probably create more problems than it solves. I agree, I wouldn't remove it either, but I just have to be concerned about the possibility that someone may have been subscribed against their will. Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Henrik Rasmussen

6 years, 11 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Mark Sapiro

On 4/13/22 10:04, bob B via Mailman-users wrote: > > So to confirm my assumptions/findings: > Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent > Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... Correct. > So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? > > If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? To send digests periodically regardless of size, you need to run `mailman digests --periodic` on the schedule you want. This will send the accumulated digest if any for every list that is configured to Send Digest Periodically. Normally, this is run daily via cron. If you want a different schedule for different lists you need to run `mailman digests --list list(a)example.com --periodic` per list on its own schedule. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Mark Sapiro

On 10/02/2017 05:25 AM, Henrik Rasmussen wrote: >> The bottom line is at this point, <https://bugs.python.org/issue27321> >> no longer affects Postorius, but it still affects message delivery. I >> have opened <https://gitlab.com/mailman/mailman/issues/406> about >> defending against that and also the UnicodeEncodeError you included in >> your OP. > > Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? There is no user or list admin workaround, but the defense is a fairly simple patch. See the MR at <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit at <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. The commit changes 7 files, but only two are needed. The rests are tests or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't necessary. The only changes you need are those to mailman/email/message.py and mailman/mta/connection.py. >> No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command >> is 'bin/show_qfiles'. > > I much be in the wrong place because when I do a 'docker exec -it mailman-core bash' and do a 'mailman --help' I don't see a 'queue' argument. The only bin/mailman I have inside the mailman-core container is /usr/local/bin/mailman, which is the same command. My bad. The name is 'qfile', not 'queue'. Sorry about that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] One-click unsubscribe?

by Stephen J. Turnbull

Jered Floyd writes: > Is there any way to provide personalized List-Unsubscribe header > links, Google should do it in their implementation -- they know which of dozens of equivalent addresses the post was sent to, and it's quite likely to be available in the header of the delivered post (and if not it's easy to add). For Mailman, not without adding a new feature. The current approach takes the sender of the "unsubscribe" message as the address to unsubscribe. While this is not currently hard to spoof, it does cut down on mere mischief. If spoofing becomes a problem, it would be sraightforward to check for From alignment, which should make spoofing very hard, as the overwhelming majority of users use providers who DKIM sign and check the login. An URL which specifies the address to unsubscribe would need to be authenticated in a different way, requiring a different command for a MAILTO URL, or a different scheme such as HTTPS. > or have Mailman ignore dots in gmail.com addresses... I think we already canonicalize addresses to lowercase, and I'm unaware of problems with that, as apparently essentially all providers ignore case. Theoretically we could do that, but ... catering to Google breakage?! I'll do it for money, maybe somebody else will volunteer. If we're talking about a new feature, I think the most straightforward approach is to use RFC 8058[1] "one click" URLs. I believe it is already implemented by Gmail and Yahoo, I don't know about Outlook or the open source MUAs. This would require a substantial (but straightforward[2]) addition of code, and of course personalized delivery (I don't know if anyone balks at that any more, though). > or... anything? I'm finding reported spam percentages > in the Google Postmaster Dashboard exceeding 0.1%, which causes > massive delivery blocking to GMail-based subscribers. That's obnoxious. If they can get reported spam rates down to 0,1%, almost certainly 90% of reports are subscriber malfeasance or incompetence! > While I would gladly ban everyone who uses gmail, that sadly > accounts for about half of the Internet today and would be > incredibly unproductive. Aw, c'mon, be a hero! (^^) Gmail has gotten so enshittified, but it just doesn't seem to matter, does it. Footnotes: [1] https://datatracker.ietf.org/doc/html/rfc8058 [2] That is, we'd need to add a new location in Postorius and code to accept POST access to it, encrypt/decrypt functionality to handle an opaque token (to prevent automated denial of service by folks without access to the person's email) or a table of one-time tokens with expiration (same purpose, and expiring so the database doesn't grow infinitely). What we wouldn't need to do is to change any exsting code.

2 months, 2 weeks

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

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 8., K, 4:06): > On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > > > So it's even weirder – however, I'm really not sure if this is the > address > > HyperKitty is checking for, as I have 3 attached to my account! > > How may I know which one it's trying to use? > > If you go to https://example.com/user-profile/ what Primary email and > Other emails do you see? Do you see all three? And if you go to > https://example.com/mailman3/users and click Manage for your address, do > you see all 3 under Addresses? Now I see a difference here! User-profile shows my GMail address as primary and my own-domain address as secondary. The third address is not present, because I actually wanted to get rid of it, and it seems I succeeded in that. Mailman3/users shows me with the address I wanted to get rid of. If I click Manage, I see all 3 addresses, with (for some reason) only the GMail one being verified (strange because I'm sure I verified the other as well). And here's something interesting: it shows me as a member with my GMail address under subscriptions, but shows me with my megabrutal.com domain under ownerships. This might be the cause? Maybe HyperKitty wants to use my owner identity, which is not subscribed? Btw, is the owner not automatically considered as someone who can post to the list, they also need to be subscribed?

2 weeks, 1 day

[MM3-users] Lost in default style creation

by kenneth.karlsson＠eco.cept.org

Hi all I have installed a brandnew server - ubuntu 21.10, mailman3 version 3.3.3 (Tom Sawyer) I want to set some default settings to all new lists, as we are creating them through API from another system, i do this (snipped straight from the shell) : >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> from zope.interface import implementer >>> from mailman.interfaces.styles import IStyle >>> @implementer(IStyle) ... class EcoStyle: ... name = 'ECOstyle' ... description = 'ECO mailing list style.' ... def apply(self, ml): ... ml.dmarc_mitigate_action = 'munge_from' ... ml.dmarc_mitigate_unconditionally = 'True' ... ml.send_welcome_message = 'True' ... ml.subject_prefix = '' ... ml.subscription_policy = 'moderate' ... ml.max_message_size = '0' ... >>> manager.register(EcoStyle()) >>> commit() No error all seem good, i then do this to confirm the style is there: >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... ECOstyle legacy-announce legacy-default private-default It shows me its there, then i proceed to quit() and go back in to the shell, and do this: >>> quit() ecoadmin@list01:/etc/mailman3$ sudo mailman shell Welcome to the GNU Mailman shell >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> and now my newly created style is gone again ? What am i missing here ? Kind regards Kenneth Karlsson

2 years, 10 months

[MM3-users] Re: Scheduled tasks

by Darren Smith

I will take up any problems with the installation with the creator. However, I was able to find and run some of the scripts this afternoon, and I'm running some of the longer-running ones tonight while the usage is lower. As for bogging down - I mean attempting to click on an email can take a LONG time to render, and we frequently get 504 gateway timeouts (the calls to hyperkitty are timing out). I am trying hard to figure out why this is happening and to try to tune the system. I still suspect that there are some inefficiencies with how the database is being used, or how the database is doing things. I will take a look at qcluster, that was interesting info and hopefully it can help me out. Thanks for your response, -Darren On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/7/18 9:59 AM, Darren Smith wrote: > > All, > > > > I am looking more through the documentation of the Mailman Suite here: > > > > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf > > > > In section 3.2.5 it talks about the scheduled tasks that need to be run > to > > do "specific routine functions" in hyperkitty. > > > > I installed through the easy install script found here: > > > > https://github.com/iomarmochtar/mailman3_ei/ > > > > However, I can't find anything in THAT documentation that talks about > these > > cron jobs, and in fact the Mailman Suite isn't installed through that > > script. > > > That is a third party project. If you have issues with it, you should > take them up with @iomarmochtar. > > > > Can someone point me to any other documentation about the tasks that need > > to be run on a continual basis? > > > The section 3.2.5 you refer to tells you what needs to be set up in > cron. For a list of the jobs tat are run, use > > django-admin runjobs --list > > > . Our hyperkitty installation seems to be > > bogging down more and more, and I am hoping that it will be as simple as > > just running some jobs that haven't been on our radar. > > > what do you mean by 'bogging down'? If you aren't doing so, setting up > qcluster as in section 3.2.3 may help. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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, 10 months

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

by Guillermo Hernandez (Oldno7)

On 18/2/21 9:13, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 14/2/21 2:42, Abhilash Raj wrote: >> You can actually translate the templates in Weblate too. That is >> actually the whole >> reason to go with monolingual template format in Mailman Core. >> >> Mailman uses the template file's name as the msgid for translations >> and all in-tree >> templates are copied into English's .po file when we re-generate them. >> >> For example in here: >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… >> >> >> The english .po file is considered as reference in Weblate and used >> for source string. > > I want to contribute making it via Weblate, since it is already done > via gitlab repository (thanks to Mark Sapiro for approving the merge > requests), making a revision and editing them if needed, but I cannot > see how to make it in a consistent way, as I cannot determine how to > edit each template in the Weblate UI. I've tried to access via the > file name (accessing via msgid as for your example) of the > template... but I cannot access them by this way, or I'm missing > something. > > Can you, please, point me in the right direction on how to do it? Forget this, I've just found how to do it. Selecting by "key/context" and the name of the file seems to do the trick. Movin' on Sorry for the noise.

4 years, 2 months

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

by Mark Sapiro

On 11/28/24 10:19 AM, Alain D D Williams wrote: > 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. It's not likely that this is the cause. > 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 Yes, Django can be daunting. It is certainly possible to implement alternatives to Postorius and HyperKitty that use some lighter weight, non-Django framework, and it was always our hope that someone would do this and contribute it. A few years ago, EMWD did implement alternatives using PHP, but at least in part due to the untimely death of EMWD's principal, those remain proprietary. That said, if you follow the installation doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you shouldn't need much Django knowledge beyond that and https://docs.mailman3.org/en/latest/django-primer.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

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

by tlhackque

I am one who uses Mailman to support a closed community. Social logins are NOT a good thing there. Besides encouraging spam signups (social media accounts are easy to get - just ask the spammers), they tie your site to the privacy and other policies of the providers. This includes that when they authenticate, they also track users and sites. Monetizing the data. Many people find this objectionable. And not auditable. When I tried to use MM3, turning off social logins was one of the first things I tried to configure. It wasn't easy. First I commented out too much, then too little. The resulting errors were opaque. I hope things have improved - at present I keep an eye on MM3, but it's not usable for me at this time. So I may be somewhat behind the times. The admin interface could use an authentication control panel - per site, and per-list. Click to enable/disable the social (password, 2-factor, and other plugin) providers. On the whole, MM3 is far to painful to set up - editing hierarchies of config files assumes a technical person runs the list. Frequently, people who want lists aren't. [X} login with Google [x] login with passwords [x] login with GitHub is comprehensible - the implications may not be, but better to explain policies than how to edit a config file written in a foreign language. There's a big difference between "installing" (that can assume some technical knowledge) and "configuring" (that should not). The former has to do with where you put files, how updates and time-driven events are enabled. The latter is how one expresses one's site policies/preferences. Package managers and MaxKing's containers are "good enough" for installing. "configuring" by config files and extensive wiki searches is not. The persistent echos of issues I raised and appear on the list from others are in the same vein. Cut and paste is not scalable for bulk subscribing thousands of users. Neither is API performance. Or "resent confirmation codes". or... I recognize that replacing a mature technology is hard. MM3 has a lot of potential. It's just not there, for me, yet. On 12-Feb-19 11:11, Stephen J. Turnbull wrote: > Note: I've changed the order of sentences from Torge's post to fit my > responses. > > Torge Riedel writes: > > > I do agree, same here on my side. Lot's of my users are very > > "sensitive" to social media and don't want see them here. > > This is the first I've heard of this. Obviously it's fairly > widespread; *please* speak up if anyone have similar issues that we > haven't addressed. AFAIK all of the currently active Mailman > developers believe that social auth is a GoodThang[tm], so we're > unlikely to DTRT as you see it without your help. > > > I need to migrate from mailman2 to mailman3 and was wondering why > > social accounts are enabled by default > > By default Mailman 3 is social media: you have a profile, you can be > searched in the indicies of the archives, and so on. The large auth > providers provide more secure authentication, and a lot of convenience > for users who have such accounts already. They also take some > administrative burden off the list and site managers when people lose > their passwords and forget what their subscription address is, and > similar scenarios. Clearly, these are not universally-valued > features, but I think that they justify the current defaults. > > > and are difficult to disable. > > They're easy enough to disable (easy to recognize and just add a hash > character in front), since you have to edit settings_local.py to > install anyway. If you're using a packaged version and the package > configuration utility doesn't handle it, there's nothing we can do > about it. The distro will have to deal with that. > > It should be better documented, I imagine (haven't checked yet). > > > I propose something like an additional setting listing the enabled > > social accounts. > > Do you mean in the Postorius administration interface? If so, do you > want it by-site, by-domain, or by-list? ("You" is everybody who wants > to disable social auth, not just Torge!) > > If you mean in settings_local.py, I suggested something similar > earlier. It's not obvious it would be easy to do (sometimes these > things are order-dependent, though that's bad practice). > > > And if the admin is setting this to an empty value in the > > settings_local.py everything is disabled > > Because the settings are a Python module, this is the way > settings_local.py works anyway. That's why Mark suggested editing > INSTALLED_APPS. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- This communication may not represent my employer's views, if any, on the matters discussed.

6 years, 2 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Odhiambo Washington

On Fri, May 24, 2024 at 11:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > > > Is nntp common enough these days to be a useful default runner? > > > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > > resources (yet another Python interpreter running) for a fairly edge > > case of mailing list <--> nntp transits. > > > You raise an interesting point. By default, the runner runs, but if > there are no lists gating to usenet, its queue is always empty and it > mostly sleeps between waking, finding its queue empty and going back to > sleep. A more significant use of resources is every (default) 5 minutes > spawning `mailman gatenews` which goes through a startup process and > then looks at every list figuring out there's nothing to do. > > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I last heard of usenet in the late 90's. Do they still exist, even? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months, 4 weeks

[MM3-users] Re: Mailman import of 2000 lists

by Abhilash Raj

> On Oct 19, 2021, at 7:37 PM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Bryan Loniewski writes: > >> We have noticed similar slowness when importing/creating/deleting >> lists. We have ~2600 lists and the bottleneck does seem to be the >> MTA alias code that reads from backend (sorts by domain and then >> list names?) and subsequently writes the (lmtp,vmap,etc) files. > > Is there a GitLab issue for this? If not, will somebody file one for > us? I'd do it but I don't really understand the issue and diagnosis > except for S-L-O-W, that part I get. I didn’t find any issue, so I created one https://gitlab.com/mailman/mailman/-/issues/953 My understanding of the issue is that Mailman tries to create the LMTP files whenever a new list is created and in their setup, the LMTP files are on a remote volume. So the latency to write to LMTP file is significant. And when 2600 of those happen, it takes a lot of time. I don’t think we can do anything about the MySQL latency though, since we have to create the lists. Although, these lists are separate rows in database, so it should be possible to do multiple imports in parallel by invoking the commands simultaneously. We should be able to fix this by adding a flag that skips creation of LMTP files after creation/import of a list. Once the imports are complete, a single run of "mailman aliases” command should generate everything. Hyperkitty has a similar mechanism to avoid indexing emails when bulk importing emails from mboxes. -- thanks, Abhilash Raj (maxking)

3 years, 6 months

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/XXXXX/login/

by Stephen J. Turnbull

Odhiambo Washington writes: > Where XXXXX from the subject implies github|fedora|openid|gitlab, etc, I > edited my settings.py and removed those references to socialaccount auth > providers, except google: It's clear enough: Internal Server Error: /mailman3/accounts/gitlab/login/ DoesNotExist at /accounts/gitlab/login/ SocialApp matching query does not exist. Mailman is doing the right thing here: it assumes the remote user knows what they're doing, tries the auth provider, and discovers it doesn't exist, so it reports an error. Mailman is not responsible for the query; some third party is. You're dealing with the Internet -- we can't help you with what third parties do. The one possible link to Mailman is that somehow mailman-web is offering social auth using those providers to users. When you log out of Postorius/ HyperKitty, then try to log back in, does the application offer login through any social auth other than Google? If so, that may be the problem, but I don't know how that can happen: the social auth offered is based on querying the providers installed by settings.py. And the person initiating the login would presumably be your user, who I would imagine would complain if they were trying to use social auth and it failed for them. Perhaps it's a user's browser cache. If mailman-web doesn't offer social auth, it's something else. The reverse DNS lookup says it's coming from REMOTE_ADDR = '185.191.171.20' which is "20.bl.bot.semrush.com", where semrush is an SEO company. The "bot" part is suggestive of an automated attack, but who knows. Steve

3 years, 6 months

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

by Stephen J. Turnbull

Philip Bondi writes: > [E]mails from banks, government, ecommerce or other important > providers are distributed to multiple family members. This an interesting application, but very likely to have delivery issues because most financial institutions participate in the DMARC protocol to control use of their domains in email. I would guess that government and ecommerce do as well, but my personal experience them is using the web or bespoke apps. Since you're stripping the From header field, you shouldn't have DMARC issues, but many providers are more aggressive than the DMARC standard recommends. > Do you struggle with "message rejected. AUP#CDRBL" while using > mailman with your ISP email relay? The code "AUP#CDRBL" is specific to your ISP. USers of other sites won't know what that means. You should check the rejection or the ISP's pages for a page explaining the code. Also, there are numerical codes like "503" and "5.7.1" (it will probably start with 5 because that's the code for "this message cannot be delivered"). The standardized codes are not at all specific about why the ISP doesn't like your mail, but some ISPs also add more specific reasons in a comment field immediately after the numerical code. "AUP" very likely stands for "Acceptable Use Policy", which is standard terminology for your side of the agreement with the ISP. I don't know what "CDRBL" means. "RBL" is a common acronym for "realtime block list" which is a system where the source domain or IP is looked up and checked against a list of spam or phishing sources. That seems unlikely, though, because normally these are based on the IP address of the most recent connection---which would be yours. > On mailman2, I mitigated by stripping headers, wrapping message and > DKIM signing. Here is a mailman2 message that is stripped, wrapped > and signed. If that works, all of those features are at least as well supported by Mailman 3 as by Mailman 2. I don't see why you'd have more problems with Mailman 3 than Mailman 2 if you use them same settings, The only additional possibility that you haven't mentioned (but may already be using) is to set the list to anonymous. > https://freeimage.host/i/30O5EXe This is almost useless, it just confirms what you said in the text. If that's not working, we will need to see the raw email to help you, including the entire header and maybe the body. If you're not comfortable sending to the list (and for this data, maybe you should be uncomfortable), you can send to me and Mark at our personal addresses. Steve

1 week

[MM3-users] Re: Changing subscription address

by Abhilash Raj

> On Mar 20, 2021, at 4:36 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Abhilash Raj writes: > >>> There does need to be a way to revert each option to inherit, and >>> there currently doesn't seem to be one. The 'Preferences' interface I >>> described in the previous post doesn't provide it either. I will >>> think about that. >> >> The implementation of this isn’t very difficult, but the UX of this is >> something I don’t know how to implement in that page to be very >> honest. > > Oh, I can play Liz Warren on that one! :-) "I have a plan for that." > >> We do already have ability to switch from an explicit address to Primary >> Address subscription. I would imagine it would be more than just a >> button, but more like a dropdown to choose an email or primary address >> and switch all subscriptions to that. > > Allan's situation is that for some reason he has a lot of users (or at > least suspects he does) who would be happy to have only one address > that there's only one place to change, but for some reason that > address is copied to (not inherited by) each of several subscriptions. This is a common situation actually, given that Postorius until recently only allowed subscribing individual addresses. Also, any subscriptions imported from Mailman 2.1 are also subscribed as address. > > We should address that, because I'm pretty sure his suspicion is > correct. For example, until I changed one of them -- and got two > emails about it for my discard pile :-) -- all of my python.org > Mailman 3 subscriptions were explicit. I still have about 8 to > go. :-) +1 >> This is how Core actually does work[1] if you subscribe via Email >> and you already have a primary address. It will lookup a user using >> the address and if the address is the primary address of the user, >> it will subscribe the primary address. > > If you say so, I guess it's true. Nevertheless, both Allan and I have > observed users with only one address, with that address subscribed > literally each time to several (~10) lists. Well a couple of stars have to align for it to work unfortunately. I realized that Core will use the primary address if you *already* have one set during email -join command processing. Add to that you can’t set an address as primary using just email commands, you end up with what you are seeing. Also, like I mentioned above, imported subscriptions are always address based. Another thing I thought I should clarify is that when I said subscribed via Primary Address in this or previous emails, I really meant that the User was subscribed and subscription inherits whatever the primary address of the user is. As opposed to explicit address itself (which could also be the email address currently set as primary address). > >> However, if it isn’t the primary address, and this is a new address, it will >> subscribe the address instead of user because the address isn’t >> verified at this point and hence can’t be a primary address. We could >> extend the subscription workflow to add an additional step to set this >> address as primary and subscribe the primary address. > > Yes, please, I think. Users who don't want this for subscriptions to > the primary address are going to be (rare) edge cases. If we need an > additional attribute on the user to handle the case of an unverified > primary address, I think that's an acceptable cost. Note that to > "claim" this User as her own, she has to verify that address. And if > she *can* verify that address, we can't stop her from doing so, we can > just make it more annoying. We don’t necessarily need the flag on user to set an unverified primary address, we might be able to get away without that. We could set the address as primary *after* we verify it. We always verify addresses regardless of the choice of the subscription mode (user or address). > >> Postorius has the full ability to define its own workflow because >> REST API provides full expression capability and doesn’t enforce >> anything. Previous versions didn’t had support for subscribing as >> Primary Address, but that has since changed and is the default one >> in the dropdown. >> >> This is for authenticated subscription, the anonymous subscribe works >> similar to email -join command. Mass-subscribe is probably working the >> same way. > > All of these should unify all subscriptions-by-this-address to one > User, in my opinion. +1 > >> Like mentioned above, it should be possible to do what you suggest. I >> am getting into the implementation details here, but the Subscription >> workflow would need an additional flag that would verify an address >> and use the flag to determine if it should subscribe the address or >> addresses’s user if an address is provided to the workflow. > > I don't think so. Just do the lookup, if it succeeds and matches > primary address, use inherit. If it doesn't succeed, create a User > and use inherit. If it does succeed, and doesn't match, use the > explicit address. Right now, P is explicit about it. You can choose if you want Primary Address or one of the explicit addresses added to your account. The primary address is the pre-selected choice, so if you go and just click on subscribe button, you get the primary address being subscribed. If you choose the explicit address then we subscribe the explicit address. Is that something you think needs modifying? The email join command does the first part you suggested, (if the lookup succeed and matches primary address, use inherit) but doesn’t do the second part (it will create a user, add the address to it and then use the address to subscribe). We can and should fix that. > It seems to me that this flag would be impractical for email > subscriptions (email commands with parameters are generally beyond the > kind of user this is most important for) or mass subscriptions (how > does the list owner know what the user wants?) anyway. If somebody > really wants all their subscriptions via primary address to be copies > of the primary address rather than user, I'm sorry, but they'll have > to deal with that. I can't imagine that it's the usual case, and > there's an easy workaround: make your primary address something other > than your usual subscription address! The flag I was talking was not really a user visible one but just thinking code flow. It might have to be a flag in API though to differentiate between the “verify this address and subscribe it” vs “verify this address, set it to primary and subscribe the User” cases. I agree that in situations where we just have an address to subscribe and no user exists, we create a user, add the address and verify and set it to primary and then use inherit. This should apply to, mass subscribe, anonymous subscribe and -join command. > If you disagree with me about the relative burden, then maybe we > shouldn't do this at all, but I'm pretty sure this is something we > should either do for all subscriptions, or for none. No, I think it shouldn’t be a big burden. > >> Primary Address is also an attribute of the Mailman User, so it >> should be possible for an admin to set that for a user if the user >> doesn’t have an account. When they sign up, they’d be able to >> manage and update accordingly. > > True, but AIUI Allan has a *lot* of users and on average they're > relatively needy compared to, say, my user population. The point of > his request is to smooth workflows for admins with user populations > where the admin *wants* to do many things for their users, or to have > smooth user workflows when they teach their users to do it for > themselves. That's why I'm focusing on the "I have one address and if > it changes I want to change it once" case. Makes sense. -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Python is updated

by Lars Bjørndal

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

1 year, 11 months

[MM3-users] Re: List creation error

by Odhiambo Washington

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... 1. At what juncture during the installation do you do this renaming? 2. 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. 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. As it is, I believe my problem lies elsewhere, not possible to solve with your rename option. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 3 months

[MM3-users] Re: Member Issue Discovered

by Apollinaris Schöll

There might be a handful of these. But the bigger problem is a user can’t be removed entirely. User can delete account and unsubscribe from all lists. But the email and user name is still kept in the db. Just tested with Affinity List admin can’t do it either. I am admin for a list. Users got subscribed with bulk import during transition from MM2 to MM3. So in a sense I am responsible for adding these to a db. BUT there is no way for me to remove them. Only mailman admin with access to the db can do it manually. I think the correct action is to remove all records if a email is unsubscribed from all lists and that user has not registered for an account. If a user has registered for an account all information including display name must be removed from that particular list subscription. It should not matter if a user unsubscribes or a list admin unsubscribes. There shouldn’t be any data kept. > On Oct 21, 2020, at 1:43 AM, Jörg Schulz <info(a)joergschulz.de> wrote: > > So, the issue seems to be, like in the following scenario > > We imagine a list server for the domains fruiteaters and meateaters. > We have two listadmins, anna (fruit) and carl (meat). They don't share anything. > We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com > > He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. > While he can do so using two different email addresses, he cannot do so using > > wormy wonder <hunger(a)eatall.com> > fritz the cat <hunger(a)eatall.com> > > as from: addresses because all requests will be matched to the one email address. > > Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. > > So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. > > So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. > > Not optimal for some rare conditions - that's the way it seems to be??? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 6 months

[MM3-users] Re: Changing subscription address

by Stephen J. Turnbull

Abhilash Raj writes: > Well a couple of stars have to align for it to work unfortunately. I'm not going to wait for the stars; I have backward-incompatible surgery in mind. > Add to that you can’t set an address as primary using just email > commands, you end up with what you are seeing. Right. The idea is that the first time an address is used, a User will be created and that address will be primary for that User. When the person wants to claim that address, they go to Postorius, create a Postorius account, do the address verification dance and set credentials, which links the Postorius account to the User via the Address. This is why the ability to merge Users becomes an urgent need: people who subscribe via email are going to end up with multiple Users. > We don’t necessarily need the flag on user to set an unverified primary > address, we might be able to get away without that. We could set the > address as primary *after* we verify it. We always verify addresses > regardless of the choice of the subscription mode (user or address). I'm not clear what you're saying. In general admins can't read your mail, so they can't verify you on a mass subscribe or an import. > Right now, P is explicit about it. You can choose if you want Primary > Address or one of the explicit addresses added to your account. The > primary address is the pre-selected choice, so if you go and just click > on subscribe button, you get the primary address being subscribed. If > you choose the explicit address then we subscribe the explicit address. > > Is that something you think needs modifying? No. The option to set a subscription to the literal primary address should still be available. I don't see a good reason to complicate the UI logic by comparing primary to literal addresses just to remove that one. I just want the primary address to be populated automatically, and inherit-from-primary be the default subscription address when the subscription address matches primary, *unless* the subscriber explicitly chooses that literal address in Postorius. This is backward-incompatible, but I think it will be overwhelmingly popular with new users and old. > The email join command does the first part you suggested, (if the lookup > succeed and matches primary address, use inherit) but doesn’t do the > second part (it will create a user, add the address to it and then use the > address to subscribe). We can and should fix that. I think that's all we need to do going forward. We do need a better UI for setting options (including address) for a selection of subscriptions, but that's an independent task. Thanks for looking at this, Abhilash! Steve

4 years, 1 month

[MM3-users] Re: "held for moderation" - alias domain details sought

by Mark Sapiro

On 11/1/24 11:14, Jeremy Stanley wrote: > On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: >> Hi friends. I've viewed this old thread: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> and documentation here: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… >> (and the Postfix docs it links to). Those documents don't seem to guide my >> situation, or maybe I just need a more specific example. The alias domain discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has nothing to do with what you are doing. >> The problem is that when messages are delivered to the alias domain, they >> are held for moderation. I.e., mail to the alias domain like >> testlist(a)domain.tld is held for moderation, but mail from the same >> subscribed, non-moderated user to testlist(a)lists.domain.tld is posted >> immediately without moderation. > [...] > > I manage a similar setup (though with Exim instead of Postfix), and > when migrating from Mailman v2 to v3 kept the same basic settings > which seemed to work: notably, under Message Acceptance I set the > alias addresses for the list in the Acceptable aliases field. If > memory serves, not doing that caused messages addressed to those > aliases to be unconditionally held for moderation. This is the correct solution. Just add `testlist(a)domain.tld` to the acceptable aliases setting of the `testlist(a)lists.domain.tld` list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Hiding an ML from a site

by Odhiambo Washington

On Thu, Feb 8, 2024 at 1:21 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On February 7, 2024 1:34:32 PM PST, Odhiambo Washington < > odhiambo(a)gmail.com> wrote: > > >What should I do then? Edit some file? Apply some patch? > >It's pretty easy for me to create a DNS record for the same server (IP) > for > >use with the web host that I'd like to hide. > > > In the Domains view in postorius, you need separate mail hosts. Then you > need to change the domain of one of the lists to the 'new' mail host. This > implies changing its address which may not be acceptable. > Looking at Postorius, they do have different mail hosts. See the screenshot at: https://imgur.com/a/GsiiEjP Or, you can just live with it as is. > The problem with this is that those who go to the site have been trying to subscribe to the other ML. Note, I have been without power at my house for almost 3 days now, so I > don't have access to all my usual resources. > In Kenya, the blackouts can last equally long at times - and there is nothing we can do about it because the power distributor is a monopoly. Sorry for all the loss you've incurred from the foods getting spoilt in the fridge :-( -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

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

by Mark Sapiro

On 1/25/21 11:42 PM, David Partain via Mailman-users wrote: > Hi Gordon (and Mark)! > > I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: > > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.mysql', > 'NAME': 'mailman3web', > 'USER': 'mailman3web', > 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', > 'HOST': 'localhost', > 'PORT': '', > 'OPTIONS': { > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > 'charset': 'utf8mb4', > }, > } > } > > and restarted stuff, but I cannot tell that it has changed anything. That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. If this is the case, it would have been retried and produced the same error with each new post, and after you made the above change, it would have been archived and the errors stopped. > Do I need to do something with the database itself (which is somewhat outside my comfort zone...) to make this work? Are you saying you are still seeing these errors? If so, it may be a different error. What is the exact error message? We don't need all the Django stuff, just the part equivalent to > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\xF0\x9F\xA4\xA3\xF0\x9F...' for > column mailman3web.hyperkitty_email.content at row 1") from the OP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

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

by Guillermo Hernandez (Oldno7)

On 17/9/21 19:58, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 17/9/21 17:24, Mark Sapiro wrote: >> On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> On 16/9/21 16:40, Mark Sapiro wrote: >>>> >>>> Are you asking what the equivalent MM 3 scripts would be? >>>> >>> More or less: I'm asking for a general direction here. I think I >>> cannot use tthe "withlist" method as before, inside a python script, >>> and I'm not sure how to do it. >> >> >> You can run scripts via withlist in Mailman 3 similarly to Mailman 2. >> See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… >> >> > First, thanks for the prompt response, Mark. > > Maybe I'm a little bit ofuscated, but I readed this doc many times > when I was searching how to do it... but I cannot imagine how to do a > shell or a python script, using the needed parameters, that sets hold > on a member of a list. > > I'll try to do some tests tomorrow. I've followed the indications of a mailman -C /usr/local/mailman3/var/etc/mailman.cfg shell --details I've been trying to "translate" the python script that I made for mailman2 to new mailman3, but obviously, I'm missing something. It seems that mailman cannot locate the "module" needed. The script is named "moderar.py": *-*-*-*-*-*-*-*-*-* (begin of /usr/local/mailman3/moderar.py) /usr/local/mailman3 # cat moderar.py #! /usr/local/bin/python3 # # script via withlist para moderar a pelo en mailman3 # import os import sys sys.path.insert(0, '/usr/local/mailman3') os.environ['PYTHONPATH'] = '/usr/local/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' os.environ['MAILMAN_CONFIG_FILE'] = '/usr/local/mailman3/var/etc/mailman.cfg' import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() *-*-*-*-*-*-*-*-*-* (end of /usr/local/mailman3/moderar.py) When I execute a mailman withlist -r moderar -l list_to_use(a)mydomain.com address(a)moderate.com The system returns: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.7/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'moderar' I've done a ln -s /usr/local/mailman3/moderar.py /usr/local/lib/python3.7/site-packages/mailman/bin/moderar.py But with the same result. And I'm not sure if I'm doing well importing "mm_cfg" in the script. My enviroment is open wide installation of mailman, python, etc. in a FreeBSD 12.2-RELEASE-p10 Mailman Core Version GNU Mailman 3.3.4 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius version: 1.3.5 If someone can give a hint it will be much appreciated.

3 years, 7 months

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

by Mark Sapiro

On 10/18/20 5:46 AM, Allan Hansen wrote: > I was pleased to see the advice below on how to get your own list messages sent from a Google client, as my subscribers complain about their messages going AWOL all the time. > Alas, it has the following note at the bottom: > > "I have tested this and while it seems to work, it doesn't. What the filter does is put a copy of the sent message in your inbox as it is sent so it appears that you received the list post, but the message in your inbox is the same message that's in your sent folder. It's not the message received from the list.” > > Do those messages really show up in the spam folder without this filter? (I don’t use Gmail). No, they do not. > If so, then the server is, indeed, sending the message to the mail client, and the mail client is doing the message ID linking locally, discarding the incoming duplicate. > Would a change in mail client solve that? This is a Google thing. It does not depend on the client. I.e., it is the same regardless of whether your client is Gmail's web mail or a Gmail phone app or some other imap or pop3 client accessing gmail. The message is sent from the list server to the recipient's gmail/googlemail MTA and that MTA determines the Message-ID is a dup of one in the sent folder and discards it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Newbie hyperkitty question

by Stephen Daniel

Thanks. So yes, I'm clearly running hyperkitty. Good to know. What is the archiver named "prototype" that is selected in the list options page? See screenshot below: [image: image.png] Would also like to know how I control archiving policy -- specifically how long archived entries are saved. On Tue, Jan 11, 2022 at 11:51 AM David Newman <dnewman(a)networktest.com> wrote: > > On Jan 11, 2022, at 08:28, Stephen Daniel <swd(a)pobox.com> wrote: > > > > Mailman users -- > > > > I am setting up a new mailman3 installation, and this is my first > > experience with the suite. All of the software is up and running, but I > > cannot tell if hyperkitty is actually running. > > > > When I look at my test mailing list, two archive options are available, > > hyperkitty and "prototype", and both are enabled. I can see that my > email > > is being archived, but I think "prototype" is what is doing the > archiving. > > I see that a test message will end up in > > > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > > and nowhere else. This suggests that "prototype" is archiving, but > > hyperkitty is not. > > > > So, this opens up a raft of questions on hyperkitty: > > > > - How do I tell if hyperkitty is actually running? > > Is hyperkitty enabled? In the Postorious admin panel for your list page, > check under Settings/Archiving. > > Generically, the URL for Hyperkitty archives is something like this: > > https://lists.domain.tld/archives/list/listname@lists.domain.tld/ > > When I’m logged in (which I needed to be to check settings), I see > archives at that location. > > Also, your mailmanweb database should have a bunch of ‘hyperkitty_*’ > tables. I’m not ssh’d in to a MM3 server right now but IIRC the messages go > into the hyperkitty_email table. > > dn > > > > > - Does hyperkitty have a web-UI for admins or users? How would I > access > > it? > > - I can not find any documentation on hyperkitty, other than > > installation instructions and change logs. Does documentation exist? > > - How do I set policies on how long archives are kept? > > - Assuming I want to back up my archives, what do I need to back up? > > > > Thanks for your help! > > > > -- Stephen Daniel > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Replaced multipart/alternative part with first alternative.

3 years, 3 months

[MM3-users] Re: Topics? First bug...

by tlhackque

Thanks - comments inline. On 20-Jun-17 23:48, Barry Warsaw wrote: > On Jun 20, 2017, at 11:18 AM, tlhackque via Mailman-users wrote: > >> I'd like to deploy a new project on Mailman 3, which I prototyped on >> 2.1). Unfortunately, it's organized as one mailing list with ~ 120 >> topics. (The project follows another source, and it's much easier to >> spin up (or down) a new topic than to instantiate & manage a new list.) >> I see that the latest Mailman 3 release (Congrats!) doesn't support >> topics yet. >> >> Where is that on your todo list? > It's not. We've discussed topics quite a bit and unfortunately, I don't think > it's something we've seen enough traction on to want to support in Mailman 3. > We think something along the lines of "dlists" (dynamic sublists, as > originally implemented for Mailman 2 by Systers) as a better overall feature > for supporting sub-conversations in parent lists. > > That said, I think topics could be a good candidate for a plugin, and the work > being done for GSoC this year will greatly improve the plugin architecture. > So while topics may not be a built-in feature, it could be an interesting > third party add-on. That's disappointing; I was expecting feature parity. Topics are a good fit for my use case - which is a bunch of announce-only lists on related topics. E.g. Project foo news, meeting agendas, meeting minutes, x several dozen projects. I suppose I can map these to virtual e-mail addresses for Mailman's benefit (I have a process between the MTA and Mailman), but I'm not sure how that will play out with list creation via the API & the user interface. Perhaps creating a list isn't as heavyweight in V3 as it is in V2... In V2, all I have to do to spin up a topic is use config_list to extract the the configuration, add the topic name, regexp & description, and then push it back, which is easy to do on the discovery path. Creating a list requires updating the MTA (aliases) & establishing the list's admin controls, templates, separate directories, user registrations, etc... Creating a new list also doesn't provide the 'unless you do something, you get everything' default of V2's topics.... But I'll keep an open mind. Many of the other changes you've made seem, at first blush, to be helpful. Once I get V3 to where I can experiment, I guess I have more work to do... Hoping for maybe a 3rd party plugin to appear doesn't constitute a plan on my end :-) And I don't want to switch UIs on my users soon after initial deployment. I don't mean to sound negative - I'm excited about trying to make this work. Just trying to share a perspective from outside your usual suspects :-) I seem to be about 1/3 of the way to getting MM3 up -- I finally got the core running in developer mode on Fedora. I'll post my "new user" notes on the process... they're not refined, but you only do something for the first time once :-) Hopefully they'll be helpful. >> First bug: Looking at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/. >> >> If I set "results per page" to a large number & switch months, results >> per page reverts to the default (10). >> >> It should stick with whatever I select... >> >> It also would be nice to have an account preference for this, so it >> doesn't have to be set on each visit. > The best place to capture this is on the HyperKitty tracker: > > https://gitlab.com/mailman/hyperkitty/issues Done, Issue #138 Thanks again for all the good work. > Cheers, > -Barry > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 10 months

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

by Mark Sapiro

On 04/10/2018 02:18 AM, Henrik Rasmussen wrote: > 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. Right. DMARC deals with the From: domain. For DMARC to pass, either a valid DKIM sig or SPF with domain 'aligned' with the From: domain must be true. I.e., your DKIM sig and/or SPF won't do if the From: domain is not your domain. > 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? 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. -- 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] 421 - Too many sessions from source IP

by Stephen J. Turnbull

hansen(a)rc.org writes: > The link gives just this: > > 421 - [too many sessions from <source IP>] The sending IP address > has exceeded the five maximum concurrent connection limit. > Configure your sending server to establish no more than five > concurrent connections. > > 1. Is that a legitimate excuse to refuse passing on emails or is > cox.net too stingy? Very stingy (Postfix default is 50) but possibly legit. From http://www.postfix.org/postconf.5.html (edited for brevity): smtpd_client_connection_count_limit (default: 50) WARNING: The purpose of this feature is to limit abuse. It must not be used to regulate legitimate mail traffic. Note the warning. Cox may have had trouble with their MXes getting DoS'ed, either intentionally or by poorly configured remote MTAs. Modern MTAs all can do connection caching, which means they can stream multiple messages over one connection. Permitting many simultaneous connections might be (a) a courtesy to legacy and unconfigured modern systems that don't cache, or (b) an optimization that might be appropriate among a collection of mutually trusting MTAs in a cloud "mail cannon" service. > 2. Is that a setting we need to change in Mailman somewhere? > Or should this be handled in some Postfix setting? I see Torge already suggested smtp_destination_concurrency_limit, thanks Torge! That is the obvious setting, but there are some other possibilities which I'll mention here, as the Postfix default is 20, so this may affect other mail traffic adversely. I think you should prefer MTA setting. IIRC, Mailman 3 doesn't have any self-throttling capability anymore, but relies on the MTA to tell it when to stop. Even if it does, it is very likely to be more efficient all around to have the MTA do the throttling. What should happen (unless you're a very high-volume server talking to an MTA you own) is that Mailman jams as many messages as possible into the MTA's queue, and the MTA takes care of throttling. This is more efficient, because the MTA can do a (very :-) limited amount of negotiation with its remote peer, which Mailman cannot do. Check the configuration of the following options in your Postfix configuration (documentation at postconf.5.html URL above): smtp_connection_cache_destinations (default: empty) smtp_connection_cache_on_demand (default: yes) Note: this default presumably means that, unless somebody told it NOT to, your Postfix "should" try to cache the connection when Mailman sends a ton to cox.net. If it's yes, try putting cox.net in smtp_connection_cache_destinations (see documentation for correct syntax). smtp_connection_cache_time_limit (default: 2s) smtp_connection_reuse_count_limit (default: 0) smtp_destination_concurrency_limit (default: $default_destination_concurrency_limit) smtp_destination_recipient_limit (default: $default_destination_recipient_limit) Hope this helps, and feel free to ask more questions. Note I probably can't help more with Postfix (my host is Exim), but Mark and I believe Abhilash are quite familiar with production Postfix installations. I can't promise their availability; the Postfix channels may be more prompt and helpful.

5 years

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

by Alan So

Stephen J. Turnbull wrote: > The problem isn't writing the code, I doubt it would be difficult to > come up with boilerplate to allow sitewide configuration of all the > defaults for all actions. The problem is thinking about the admin's > user interface for this. Sure, we could put some kind of mechanism in > settings.py, but how do we document all the configurable defaults? > How do admins discover them except by asking on mailman-users? And > changing that much code would probably be pretty tedious. :-) Thanks for exchanging the idea about adding codes for configuration or making customization. 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. 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. Therefore, we are now very cautious to accept request that need to change the codes. We do not want to give an impression to our business users that codes of an open-source software can be changed at no/low cost and without any maintenance cost. I understand that coding is tedious and users often demand a lot of different things especially about the UI. It is one of the reasons why there are a lot of commercial product of opensource backend and closed source frontend. I really appreciate all of these development effort in the mailman project which focused in the (admin) frontend a lot, which usually create great unique differences in a commercial product. 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. > I don't understand what that's suppposed to mean. If you do it, > you're changing a default, that's all. There's no real design here. > It's just a question of the greatest good for the greatest number, > which is an empirical question. You have a different answer for your The supposed to here mean that you may try to solve the issue in some other ways. You may not add the options to change the default. I am not sure but maybe make them be settings of list or prompt an alert that a lot of email will be sent to confirm/verify. I believe that you probably read a lot more of opinion from others than me and so I think the core team can judge what should or should not be done after consolidating the opinions.

2 years, 4 months

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

by Mark Sapiro

On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > running MM 3.2.2 (and python 3.8.2). > > Do you have any advise, how to upgrade from there to your current > version? I know this might be a bit dangerous, but with today's VMs the > risk is much less than it used to be: It shouldn't be difficult, but I can't give you details because I don't know exactly how the Debian/Ubuntu package installs things. Also I don't know whether "current version" refers to the 3.3.1 release or the head of the https://gitlab.com/mailman/mailman master branch. > Do you think it would be possible, just to replace the code and library > parts, keeping the database and config files as is? Yes. It should be fairly straightforward. You first need to find where the Mailman Core package is. You should be able to just replace the contents of the `mailman` package directory with ours. You may be able to do this via pip pip install --upgrade mailman globally or within Mailman's virtualenv if it is installed in a virtualenv. However, there are caveats. There are Debian patches at <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` patch replaces importlib_resources with importlib.resources because importlib_resources is not available in Debian. Most of the patches apply to tests, and for the actual working code, we fixed this differently as of Mailman 3.3.1, so I don't think you need the Debian patches. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Rolling releases for Container Images and Funding Campaign for Mailman

by Abhilash Raj

On Sun, Nov 12, 2017, at 08:06 AM, Simon Hanna wrote: > > >>> These images are built using git-heads *only* if they are passing our > >>> test suite and are re-generated weekly. You should be aware that while > >>> all these components are tested with their individual test suites, their > >>> combination might sometimes not be stable. This will get you > >>> updates/bug-fixes much faster :) > >> This contradicts what you said in my merge request for Postorius > >> https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 > >> > >> You either use released versions, or make sure that the master branches > >> are always compatible. You can't have both with the current development > >> model. > > Not exactly, I still believe all our git-heads should be compatible with > > released (i.e. stable) versions of dependencies, regardless of the fact > > that we maintain those dependencies. > > > > Also, there is at least one test per-project which tests with git-heads > > of dependencies we maintain, so that we know if we make any incompatible > > changes. > > > > I am not sure what in the current development model prevents us > > to do both? > > > > The story for container images is different than testing with git-heads. > > We need better integration testing for the entire suite to be stable in > > conjunction, rather than independently. In fact, containers might be the > > perfect way to actually do the integration testing. > Scenario: Core changes something about rest that is backwards > incompatible. The change is commited to master. Since your containers > use the master branches, all future builds will fail until mailmanclient > and postorius/hyperkitty. Yes, that is a totally possible scenario. But, given that kind of testing we currently do, this scenario can happen not only to git-heads but also releases. That is what I am trying to build using container images. The fact that I *announced* and *released* these rolling images for public use, is only because people asked for it before. These images come with a fair amount of warning that, right now, they can break! > If you want to always have Postorius (and others) compatible with the > latest release of master, development for Postorius will be a Pain, > because you can't use the master branch of mailman for testing and quick > changes. Also your containers and all integration tests that can be done > with them will always fail. It would most definitely be a pain if we were to break REST API frequently, but that is quite rare. Given that in future API will be consumed by not just us, it is important to keep this assumption true. Another wishful project I have is to be able to "map" the REST API and monitor for changes; it'd also help us with lemme (the authenticating/authorization proxy for Core). And yes, container images will fail, and that's the point! I want them to fail so that releases don't :) Rolling images are meant to bring a faster feedback-loop from users who are OK with rare occasional breaking and want to help test the software, something like public-beta releases. > Until you fix Postorius and the other clients... So why not just have > the master branches always compatible and make life easier for > developers. Incompatible changes are released only with major version upgrades, so it is not going to happen with everyone, unless they choose to use the git-heads and get themselves into it. > I don't see a good reason why you want to do it the other way round... > > Any bug in core that affects Postorius will also just remain there until > you release a new version of core. > > If you really really want to have it your way, there have to be more > frequent releases. Yes, we definitely don't want to say "use new beta-quality container images or stone age stable release". Going forward, we will have more frequent releases too :) > >>> - Improve the container images to work with new micro-services > >>> architecture, > >>> to achieve scaling and redundancy in services. > >> The current bottleneck is the rest api from core. IMO bulk actions, > >> filtering and sorting should be added there before trying to have > >> multiple postorius/hyperkitty instances serving the same core... > > I didn't say they will be served from the same core ;-) > > > > Yes, the Core's API can be further improved to be more efficient. But > > that > > doesn't prevent us from scaling. I understand there are issues around > > multiple > > instances of containers, but I have ideas to get around most of them. > I just don't want that people that have issues with big installations > get the answer: > We know of that issue, please deploy Mailman on X containers/machines as > a workaround Containers are just an easy way to scale, given that we already have them, it'd be fun to see if I can make multiple instances run in parallel. Given that _most_ parts store their data in a data store (database, redis etc), it shouldn't be too difficult. There will be quirks with logging, queues in Core and hence held message views in Postorius, but apart from that, I think everything else can be served using any random instance of Core/Postorius/Hyperkitty. We can most definitely run multiple instances of Hyperkitty, which I feel will be more used than any other part of UI. If we partition the data smartly, we could do the same with Core. Again, these are just theories and needs much more testing and some changes in components themselves! This would most definitely increase the availability and auto-scaling. Making Core's API more efficient would definitely be a good thing and we do intend to do that in future. But, this would still be relevant if we had an efficient REST API, it's not a band-aid to the actual problem :) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 5 months

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

by Mark Sapiro

On 6/21/20 9:38 AM, Ruth Ivimey-Cook wrote: > > > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 (it obviously recognises that > as the , and so cannot be connected to by anything. That is why I set it > to 0.0.0.0 to begin with, and what the documentation implies (fairly > strongly) that this parameter is about. What documentation? I do understand what you are saying and I see the issue. I don't understand why it works for this poster <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> but maybe that's specific to Docker containers. > 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. Try something like this and let us know if it works? If so, we can do something like add a config setting for this. > --- a/src/mailman/rest/gunicorn.py > +++ b/src/mailman/rest/gunicorn.py > @@ -53,7 +53,7 @@ def make_gunicorn_server(): > # We load some options from config.webservice, while other extended options > # for gunicorn can be defined in configuration: section. We also load up > # some logging options since gunicorn sets up it's own loggers. > - host = config.webservice.hostname > + host = '0.0.0.0' > port = int(config.webservice.port) > log_path = os.path.join(config.LOG_DIR, config.logging.http['path']) > options = { -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

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

by paul＠arenson.org

Thank you for the very quick response, Abhilash Raj. Being non technical (and therefore opting for hosted Mailman 3), I can partly understand your kind response. 1) I can understand that I cannot disable the different ways to sign up. 2) I am still struggling to understand the difference between the two web choices as shown here. WAY # 1 TO GET AN ACCOUNT https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… VS WAY # 2 YOU CAN GET AN ACCOUNT WITHOUT SIGNING UP at the bottom of https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… (I was under the impression making only WAY #1 allows one to post, but are you saying that the bottom option also allows one to post, but only by email?) If I am confused, I know my users will also be confused. I think I understand I can qualify their subscription in the ways you suggest: "Confirm where all users would have to confirm their subscription using an email sent to them. Optionally, you can also enable moderation where each subscription needs explicit approval too." So to put it simply: 1) I want to make it a discussion list. Not available to people who are not signed up? 2) This is dependent on all having access to the archives so they can see what they are responding to 3) What settings do I make to insure that all who sign up via WAY #1 can see the archives and post. 4) What settings do I make to insure that all who sign up via way #2 can do the same? Last, in my account settings what is the difference between a member and a non member? Thanks and sorry I was not clear the first time.

5 years, 7 months

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

by Stephen J. Turnbull

Steven Clift EDem writes: > Figuring out how to raise money to cover server costs without selling out > our members with targeted social media advertising, was a continuous > challenge. I understand why you object to the kinds of advertising you might see via Google, Amazon, or Facebook, but targeted advertising is the way to go if you want to minimize annoyance and still get revenue. You just want to target something different (don't ask me for specifics, you know your business, but basically you want advertisements your customers / clients / members find informative and useful rather than targeting revenue from advertising). > So here is the question - do you think a Mailman > add-on/plugin/module/whatever you'd call it that allowed list admins to > reward their new subscribers to email lists with custom themed "for good" > discounts would be of interest to many??? Mailman 3 allows you to provide custom templates for both Postorius (how new subscribers sign up by web) and for various emails. It would be easy to provide custom templates for each list for your purpose, for example if all users get the same "coupon code", or get a random code. There isn't really an opportunity for a "plug in" here, though, because presumably you really want carefully designed templates for *your* business (or NPO), and probably with some attention paid to the group your business is affiliated with. Once you have the template, and maybe a little custom code, you're done, nothing left for the "plug in" to do. If you're thinking of something more dynamic, eg, checking profiles of existing Mailman users who sign up for new subscriptions, again, I don't see an opportunity for plugins, because Mailman's current profiles are not going to support personalized rewards. So you'll need to design your own database for that, and unless there's a standard database for that (ie, with the kinds of market share that PostgreSQL and MySQL have with Mailman systems), that's all going to be custom code that nobody else uses. > Normally, we (GoodCarts) reward people post-checkout with discounts in > reciprocity powered circles of online stores. As I understand that, you (GoodCarts) are providing the user database services at least to the extent of ordering and billing records. So you'll be eating your own dogfood here, but probably similar services do their own thing, so your code would be unlikely to be of use to them, right? > The way I could see working with email list providers is basically adding > an affiliate marketing style commission where purchases with > post-subscription rewards would go to the partner based on results. I think Mailman provides a good platform for that kind of thing, but it's going to require a ton of additional APIs to do well. > Our view is that exclusive discounts as rewards post transaction (purchase, > email list subscription, volunteer sign-up, event registration, online > petition signature, etc.) is far better than plastering ads > everywhere. If there's a dominant database application for keeping track of these things, a plug-in architecture might work. But if not, every such business is going to need to make its own extensive customizations, and it's really going to be more of a direct-mail application than a mailing list manager, which is fundamentally for mass mailings, maybe with a bit of personalization of mailings. Stock Mailman only does direct mail for the email verification dance and subscription welcome messages. You could easily use the latter for this one event of subscription. But Mailman doesn't know anything about "volunteer signups" or "event registration", etc, and teaching it to do that part is likely to be painful and make maintenance of the software difficult. My recommendation would be to use a separate application to manage the rewards system, and add only a couple of additional rules or handlers to trigger rewards (by messaging the rewards manager) on specific events that Mailman tracks anyway. Steve

2 years, 3 months

[MM3-users] Re: template head/footer questions.

by Mark Sapiro

On 4/8/22 11:04, bob B via Mailman-users wrote: > I migrated from mailman 2 to mailman3 and had head/footer questions. > > In the mailman 3 GUI see the templates section, so where do those files get edited/stored? in the postorius_emailtemplate table in the database. > I added a footer to a list via the GUI, but I do not see it in: > /var/templates/lists/[listNAME]/en Because when you set a template in Postorius it makes an entry in the template table in the database with a URI pointing to its own API to retrieve the template. > I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. > > Bottom line, > > I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? That's up to you. The default search path for templates in the absence of a template table entry (or even with one with a mailman:/// URI) includes the var/templates/lists/list_id directory. is this directory leftover from migrating from mailman 2 to 3? No I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option. Again, it's up to you. If you have Postorius and want list admins to be able to create, modify, break, etc. templates without involving you, then Postorius is a good option, but it isn't in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Ken Alker

--On Sunday, June 25, 2023 2:47 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 1:31 PM, Ken Alker wrote: >> >> I moved the .psv file from the bad queue into the shunt queue. I then >> ran "mailman unshunt" (as user 'mailman' while in the virtual >> environment). I tailed mailman.log during this process and no logs >> were spit out. The date stamp on the .psv file never changed (maybe >> it does not when being moved between queues?) and, AFAICT, the file >> never moved from the shunt queue. I waited maybe five minutes, tops. > > > I forgot that the extension in the `bad` queue is `.psv` (for preserve). > You have to rename it to `.pck`. Ah! I noticed the file extension difference but only for a fleeting moment, and I convinced myself during that moment that I must have looked at the original one (.pck) incorrectly (even though I knew it stood for "pickle"... and so the vaguely-noted discrepancy never made it to the stop of the stack... but it eventually may have, but I still wouldn't have know how that would affect the queued file. That solves that issue. >>>> Is there a way to reprocess the bad queue? >>> >>> You could just move the messages to the 'in' queue. > > > Changing .psv to .pck in the process. this can be done, e.g., by > ``` > for file in `ls var/queue/bad/*.psv;do mv /var/queue/bad/$file > /var/queue/in/${file/psv/pck};done > ``` I moved one message by hand, and, wow.. the runner just gobbles it up... fast! >> I just now tried moving the same message into the 'in' queue but, again, >> nothing happened. I left it in there for five minutes. Do I have to >> run a program to get it to act on the 'in' queue (I presume that there >> is a "runner" that is always looking and taking care of this already as >> I presume this is the queue where all 'normal' traffic is handled). > > > Again, you need to change the extension to .pck. > > >> Here are the (obfusacted) results of "mailman qfile >> /opt/mailman/mm/var/queue/shunt/1675389793.6945386+2aeaf0015558c9d8380c9 >> 6142c3fa9d03a8142bc.psv" (the message I was experimenting with): >> >> [----- start pickle -----] >> <----- start object 1 -----> >> MIME-Version: 1.0 >> Content-Type: text/plain; charset="us-ascii" >> Content-Transfer-Encoding: 7bit >> Subject: THE-list subscription notification >> From: email(a)obfuscated.com >> To: the-list-owner(a)lists.obfuscated.com >> Message-ID: <167538979369.2390432.521344217673230839(a)obfuscated.net> >> Date: Thu, 02 Feb 2023 18:03:13 -0800 >> Precedence: bulk >> >> user(a)domain.tld has been successfully subscribed to THE-list. >> >> <----- start object 2 -----> >> { '_parsemsg': False, >> 'envsender': 'email(a)obfuscated.com', >> 'listid': 'the-list.obfusacted.com', >> 'nodecorate': True, >> 'recipients': {'person(a)domain.tld'}, >> 'reduced_list_headers': True, >> 'version': 3} >> [----- end pickle -----] > > > I was assuming these were list welcome messages which they aren't. They > are owner notifications, so they were sent to the -owner address and > processed through the owner-pipeline, but unless the Debian package > changed the default-owner-pipeline, it doesn't contain mime-delete so how > they ended up in the `bad` queue is still a mystery. > > However, what would be the point of resending these at this time? Because I didn't know if they were ALL subscribe notices or if there were other people's emails mixed in. I felt, at the time, that it would be easier to requeue them and then be able to manipulate the results in my email client (ie. sort by subject) than to try to do it at the Unix level. That said, since there is more than one queue I'd have to move them into, the sorting process would require manipulating/viewing the messages at the Unix level first anyway and if I have to do that I might as well just inspect them all at the Unix level and skip the re-injection, as you noted. Also, after countless hours of learning over the past two days, I'm more qualified to do that now. So, I modified your suggested script thusly: for file in `ls var/queue/bad/*.psv` do mailman qfile $file >>results done and then compared the number of times "subscription notification" appeared in the results file (grep subscription\ notification results | wc) to the total numbers of "bad" messages (ls var/queue/bad | wc) and they matched (1142 of each). And just for fun and as a second check, I did a "grep subscription results | sort | uniq" and ended up with three lines of output; one for each mailing list import, and nothing more. It's things like that that really make me appreciate and enjoy the Unix shell. Thanks for the wisdom and for a slice of your time; I'm learning a lot and I appreciate the help. Ken Alker KA6KEN

1 year, 9 months

[MM3-users] Re: Bounces

by David Krantz

Thank you for the tip. In the end I changed mailman/runners/bounce.py instead by moving the maybe_forward line so that it is always run. Smaller change (just removing one indention level) and preserves the handling. Might break something else, but I do not think so. diff --git a/src/mailman/runners/bounce.py b/src/mailman/runners/bounce.py index 57b259f..e772765 100644 --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -86,6 +86,6 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False Cheers // David On Sun, Nov 5, 2017 at 10:39 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/05/2017 01:29 PM, Mark Sapiro wrote: >> >> The bottom line is we aren't doing anything with bounces other than >> storing them. We need to fix that, and we will (It's targeted for 3.2). >> If you could help with code, that would be great. > > > As an interim work around, if you wanted to send ALL bounces to the list > owner instead of what little we currently do, at about line 65 in > mailman/runners/rest.py, you'll see > > SUBADDRESS_NAMES = dict( > admin='bounces', > bounces='bounces', > confirm='confirm', > ... > > If you change the > > bounces='bounces', > > line to > > bounces='owner', > > that will cause all bounces to be just sent to the list owner(s). > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 5 months

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

by Paul Arenson

And the to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) "I understand it's not totally explicit, but it says 'To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address.’ To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say?" I had to test to find out that there is not a lot I would change. Let me just preface it by sharing my experience. As a person with learning disabilities (following instructions is the hardest), I found the procedures dating when using a few pretend signups. This brings me back to a job I had in the 80s and 90s. When I was working on user manual for Seiko watches, the engineers wrote the manuals in Japanese-Engllish based on what the watches could do. But I put myself in the place of the user, who often did not know why they needed that function. And so I had to translate into an English explanation started from the point of view of what they might want to do with the watch. In the case of Mailman 3 much depends on the individual list and its settings, so my conclusion is it is mostly on me. With just a suggestion that you have a SIGN UP blue button to make things less confusing and not necessitating multiple clicking. The main obstacle I found was I had my list settings as NO to "Choose whether to include this list on the list of all lists". Changing this to "Yes" made it a little easier. Here are my two tests and conclusion. 2) TEST 1 ________ Sign up first... https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… ...you will find that if I have said NO on "Choose whether to include this list on the list of all lists” you will find it hard to go back to the subscribe page. Unless you backspace. Or paste the address again. Not ideal QUESTIONS: Am I missing something? By not having my discussion listed, people cannot find it to subscribe. Or is NOT LISTED better where I add people manually to subscribe and then tell them to sign up? 3) TEST 2 ________ One solution is I could put the list back on the host’s list of lists back and tell people to click on Discuss. That is what I did for now. Then it is rather smooth. I could tell my users (especially ones from previous company’s mailing list who want to interact with the hyperkitty site) to CLICK LOGIN CLICK SIGNIN then follow all these steps: Verify Confirm Get taken to sign in page Click Discuss Subscribe Click Archives Or I could leave it as it is and tell people to backspace until they find the signup page and then subscribe. Or tell them to copy and paste https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… or https://list.tokyoprogressive.org/accounts/signup/ in the same browser window and then subscribe. CONCLUSION and SUGGESTION—> WHY NOT HAVE A SEPARATE BLUE BUTTON TO SIGN UP TO AVOID THE CONFUSING clicking twice? IS THIS THE ANSWER?— Tell my users as follows on a WORDPRESS PAGE as follows: - - - - - - - - - - - - Greetings. If you have never signed up before, follow instructions A. If you are coming from the previous dadamail list, follow instructions B INSTRUCTIONS A Steps 1-3 to get on the mailing list and be able to post from your email account. Continue to steps 4 and 5 if you want to see the archives and post from that page. (Note to Mark: I have turned the archives off by default to make it more of a no brainer to want to sign up) INSTRUCTIONS B You are already registered, you will continue to get messages and be able to send to the list. If you want to keep using the same email address you are all set and do not need to do anything. If you want to keep using the same address, but also be able to access the archives, follow steps 4 and 5 only. If you want to register a new address, follow steps 1-5 below. 1) Go here https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… Add your email address at the BOTTOM of the page. Name is optional. 2) Then wait for email to reply to come. 3) That’s it. You can stop here. However, you can sign up to the archives which makes this list more of a forum to see at a glance old conversations. And you can also post from it. To do so, continue to steps 4 and 5, 4) Right on the same page, you can sign up and sign in by clicking log in and then sign up and then follow the same procedure as above. (Mark, SEE SUGGESTION FOR A BLUE SIGN UP BUTTON). 5) Once you have signed up, you can log in to access the archives and web posting. - - - - - - - - - - - - Hope the above long winded post was clear. Feel like I am sseing the lite.

5 years, 7 months

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

by Paul Arenson

> It's of course up to you, but I recommend Mailman 3. There are still > some rough edges, and there are a number of settings not yet exposed in > Postorius, but we are working on it and it is quite usable today. Thank you, Mark. My thoughts now. I have used nothing but MM for ages so will wait…. And it would require less convincing for the two groups I host > > Which is why upgrading from Mailman 2 to 2 still seems like the best idea. > Do you mean Mailman 3? OOPS!! yes. > I suspect it will be some time before Cpanel offers Mailman 3. It is > fairly straightforward to migrate an existing Mailman 2.1 list and it's > archives to Mailman 3, but it requires access to the underlying Mailman > 2 file system which you may not have in a hosted cPanel environment. > > See <http://docs.list.org/en/latest/migration.html> for more on migration. Thanks. I had a look just now. I suspect we won’t worry about broken URL links. Most people check archives to try to keep track of a conversation. With difficultly now, but much easier in MAILMAN 3. And going forward, they might just be motivated to post from the archives!!!! (As I am now doing!!!) The rest of the upgrade procedures are pretty much lost on me (not having done this kind of thing before), so either I wait or pay someone who might be willing to do it. (Assuming there is a someone and assuming it can be done in my CPanel environment) Also, this particular account is hosted by an educational NPO, so they may have restrictions. I will ask them if it is possible. Thanks! Paul

6 years, 7 months

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

by Derek Lambert

Brian, I'd presume it's from something recent since you only started seeing it after updating. Do you recall what the prior version was? To drop the constraint on postgres I did: alter table hyperkitty_mailinglist alter column description drop not null; That's pretty standard SQL so I'd imagine it'd work on other platforms. After dropping it the error message is no longer logged, but none of the maillists have descriptions in HK. To add the constraint back after the bug is fixed: alter table hyperkitty_mailinglist alter column description set not null; Derek On 2/6/19, 4:23 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__mailmam3domain_hyperkit…. 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 _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

6 years, 2 months

[MM3-users] Re: Create a mailman-web admin user

by Roland Giesler

On 2024/07/30 17:10, Odhiambo Washington via Mailman-users wrote: > On Tue, Jul 30, 2024 at 4:55 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/30 15:48, Roland Giesler via Mailman-users wrote: >>> However, which user in the mailman user mentioned? >>> >>> I tried to do this as root, but login in as an admin doesn't give me >>> any option to create new lists in postorius. What am I missing / >>> doing wrong? >>> >> I seem to have solved the riddle. The "mailman-web createsuperuser" >> command suggest the the mailman user is www-data, which I accepted. That >> worked and I can now create a new list from Postorius. >> > Actually, it wasn't a riddle. > You looked at documentation meant for the virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html>installation > method while your installation seems to be done from your OS package > distribution. > The OS package installation is fraught with pain. The virtualenv method is > the officially recommended. I use Linux LXC containers mostly in Proxmox, so adding another layer by using docker or something else to mean seems like another layer of complication. The documentation is obviously good enough for people that know how already, but need to look up a detail here or, but for a first time mailman user it is a bit of a nightmare. Once I have chewed my way through all the traps and tunnels, I intend to do something about this. I can't contribute to code here, but I can make it easier for the next person coming along. > > >

8 months, 3 weeks

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

by Mark Sapiro

On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. This format vs. plain text digests was a user option in Mailman 2. > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius. If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool. > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

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

by Andy Smith

Hi Mark, On Sat, Jul 09, 2022 at 12:05:32PM -0700, Mark Sapiro wrote: > If the original post was the message delivered to > users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or > another recognizer parsed those addresses from the message body. For now I've configured a copy of all mails to -bounces addresses, so if/when it happens again I can inspect the actual email that triggered it. In case anyone else ever wants to do that, this is one way to do it on Exim: # This goes in your "routers" section. # Add a router, before every other router that you would want to # tap messages for. traffic_tap: unseen no_expn no_verify transport = local_copy_outgoing driver = accept # "mm_domains" is a list of domain names for mailman, e.g. # "lists.example.com"; it's set as part of the usual Mailman install on # Debian. domains = +mm_domains # Only do this for bounce addresses. So between this and the above, this # router will only happen for *-bounces*@your-mailman. local_part_suffix = -bounces : -bounces+* # This goes in your "transports" section. # Add a transport for taking a local copy. Mail to Mailman is "outgoing" as it # is delivered by LMTP over a socket. But the name is not important. local_copy_outgoing: driver = appendfile # Simply store it all in a maildir. If you're expecting a lot of # messages then you'll want a directory structure by date and/or # recipient or something. directory = /var/mail/archive/.outgoing/ delivery_date_add envelope_to_add return_path_add # If not on Debian then your exim probably runs as a different user/.group. group = Debian-exim user = Debian-exim mode = 0660 maildir_format = true create_directory = true Cheers, Andy

2 years, 9 months

[MM3-users] Re: Auth question

by Simon Hanna

On 03/31/2017 08:10 AM, David Krantz wrote: > On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> We're really working on getting a consistent, workable installation >> story and even getting some packaged solutions. I know we're not yet >> there, but we're here to help when people run into problems. > The site now works, but not the / url for the site. I get this error > in the mailman-web.log (with a very long stacktrace before it) > > NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. > 'hyperkitty.views.index.index' is not a valid view function or pattern > name. > > I think that would correspond to this line in urls.py > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), Yes, that's the culprit. Replace it with the following: url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), You can also update whatever guide you were using... > but this corresponds exactly to what the example config says and I > know of no other name for hyperkitty. Probably it is dependent upon > understanding the url dispatching in Django but that takes some time > to read up on. The interesting thing is that /archives works so it is > just this redirect that has problems. I can probably get apache to do > the redirect instead but that is not the most elegant solution. > > Then I of course have things to do on getting social logins to work. I > currently get "DoesNotExist: SocialApp matching query does not exist." > if trying to connect an account to google (which I started with). Not > a showstopper as passwords do work. Did you follow django-allauth's guide on setting them up?

8 years

[MM3-users] pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

hi, after mark has helped me at the end of january to find users that were not attached to any mailing list (indicating people who pressed the wrong button when trying tosign up), we sent out a 2nd mass mail to our target audience to ask them to subscribe again. we are now getting feedback from people, who say that they are unable to sign up, with mailman3 telling them: > Subscription request already pending this is somewhat bad as: - at least some of the users (who reported the problem) tried to subscribe 2 months ago (2022-01-04) - if they did not confirm their email back then, i'm pretty sure that this email has been lost by now - my /etc/mailman3/mailman.cfg has "pending_request_life: 3d" - i (as administrator) do not see any "pending subscriptions" (the list is setup with a simple "Confirm" subscription policy - i (as administrator) do not find any mention of the user's email address anywhere either in postorious webinterface of the list, nor in the django - in the sql-dump (it's been a while since i worked with postgres on a higher level) i do see the user's email in the workflowstate, address and pendedkeyvalue tables. the installation is (still) mailman_3.2.1-1 on a Debian/buster system (using the Debian/buster packages for mailman3) i wonder: - why are the pending subscriptions not expired? (i guess they should have expired after 3 days) - why can't people re-subscribe while there's a subscription pending (e.g. if the confirmation mail got lost)? - how can i list all pending subscriptions (for a given mailinglist)? - how can i resolve the situtation (e.g. send out another reminder; manually expire the pendings; manually confirm the pendings,...) gfmdsd IOhannes

3 years, 1 month

[MM3-users] Re: Member Issue Discovered

by Alex Schuilenburg

On Wed, 2020-10-28 at 15:07 +0900, Stephen J. Turnbull wrote: [...] > Alex Schuilenburg via Mailman-users writes: > > > Yes, this is social media territory, but with the EU/UK DPA (data > > protection act) and record fines being issued, > > Sure. It's also a pretty big ask of the Mailman developers. As you > are now aware, the architecture of the application is not well-suited > to this. If you're worried about paying fines, maybe a contribution > of a fraction of the average fine would be good insurance? :-) That contribution depends whether I was a large company providing a mailing list service, or an individual supporting breadline charities and a small open source company. I also think myself as technically competant enough to go under the hood and do what I suggested as a one off task, but its not something I would relish doing again - I have other things to spend my time on. Hence the suggestion. Like many others on this list, I tend to volunteer a fair amount of my time. To address your other questions from an EU/UK perspective: > > But it's not just the architecture. Even the requirements are > controversial. I'm on record that it might be a good idea to remove > the User (ie, the profile of PII in the database) when the last > subscription is deleted, but should that be automatic unless > inhibited, should it be an option offered but default to "keep", > should it be an operation done only on specific request? Its rare that someone would want their posts and posting history deleted (e.g. the death of a subscriber would mean the closing of their accounts - but you would not want to delete their legacy. In fact many families would prefer it remain.). So I'd leave their account alone when the last subscription is deleted so posts are still attributable. > In any of > those options, since this is a major deletion of presumed unneeded > but > in some cases valuable data, we should provide a convenient but > cautious UI. Should there be a temporary backup of the data in case > the user changes their mind? > Is that GDPR conformant? No. The requirement is very clear. If you were asked to delete the data, and then later they came back and asked what data you held, you would have to disclose the temporary backup and then would be in breach. FWIW, the EU courts have already ruled that automated periodic backups is permissible as long as the backups are diminishing. i.e. over time the data will eventually disappear - no need to search and remove from backups (unless restored of course). > Maybe the user > could download their profile for later upload? Maybe that could be > portable across Mailman 3 sites, with some kind of semi-automated > merge UI? Overkill. If a user's posts/data is to be deleted, that's final. Once its done, there is no recovery other than diminishing backup/disaster which you would not do unless it was disaster recovery. You just need to ensure the request is genuine. > > How about the user's archived posts? How about quotations of the > user > in *other's* archived posts? Just designing this is not easy, but > because it might involve changes in the architecture, we do need to > design in advance. This is not the kind of change where "move fast, > lose user data, and break everything" makes sense. Actually, its not that tough a task - you have the information available so deleting posts from the archives should not be too hard. to delete the offending posts. I've done this with MM2 under the hood with perl scripts to delete the posts with all mentions in the mbox archive, deleted the web archive and used the cleaned mbox to regenerate the web archive. Having migrated my company's MM" lists to MM3, and hit a couple of migration issues, I can see that it should still be possible to repeat this, buts its now become harder because of the underlying relational database and its dependencies. Its something MM3 developers need to keep in the back of their mind. > > I'm not saying we can't do it, but we also have our priorities, and > limitations. Also, I don't think we can, let alone should, do that > design ourselves. Even if it's not reasonable for you to contribute > code or money, we do need to know the community's requirements, and > because it's often pretty fuzzy stuff, I think it's reasonable to ask > *why* a feature is needed -- we may be able to negotiate a change > that's easier to code or less fragile in operation if we know what > the > underlying need is. So members of this list can help a lot by (1) > answering the questions I asked above, (2) coming up with more > questions (and answering them), and (3) turning the whole thread into > concise requests for enhancement on the tracker. A bit more on my perspective: Mailing lists have become somewhat old- school (I'm old school, prefer it, and mailing lists are far more useful) as social media has grown but I prefer lists as most people have email, everyone who uses social media has email, while not everyone uses/likes fakebook/twitter/etc. Unfortunately, mailing lists can be abused just like social media. Consider for example a self-help group for victims of sexual assult, most preferring to remain anonymous. Then a discussion turns nasty and details which are legally prohibited and morally wrong are published (albeit only to subscribers). Heated discussions ensure and it turns out the original poster was the convicted perpetrator and the victim underage. Now your average list admin has no power to delete the offending posts - they can only take the list and archives offline(?), effectively killing the list. The site owner/admin has neither the finances nor technical capability to remove the offending posts/thread. Moderators are low/unpaid volunteers, so the list is not moderated. So the whole archives are removed - archives which hold valuable information and shared experiences for silent victims. Who is the winner and loser in this scenario? Yes, this is an extreme example, but illustrates why such a feature is needed, not just the ability to hide real email addresses. Is MM3 a suitable tool to provide a list in the above example? I think it is the best candidate, but needs work. Fakebook certainly not - they would not even respond to appeals from police. > > Yes, it would be nice to re-use some of those old mm2 scripts > built > > up over the years on mm3. > > Feel free to post the scripts you want to reuse on the tracker, in > request-for-enhancement issues. Without an accurate idea of what you > want to do, specifically the data the scripts want to access, we'd > have to reproduce the whole Mailman 2 API/UI. Some of that would be > extremely tedious, such as anything that manipulates list config > pickles -- they don't exist any more. But other things might be > fairly easy. Most of my scripts operate on the mbox archives, removing attachments, obfiscating email addresses and contact details from certain posts, and regenerating the web archives & index. They wont work in the current architecture of MM3. For the rest, I've already tapped into the backend (sorry, I don't have time for REST etc) to extract the information I need for my new MM3 lists. But I wont be moving my other MM2 lists over to MM3 for a while. -- Alex

4 years, 5 months

[MM3-users] Mail configuration

by Darren Smith

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

7 years, 1 month

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

by Henrik Rasmussen

> -----Oprindelig meddelelse----- > From: Abhilash Raj [mailto:maxking@asynchronous.in] > Sendt: 19. august 2017 21:32 > > > 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? That would be neat, if any list are associated. Otherwise the current warning is fine. That said, a warning could get very long if the domain has a lot of lists associated. > > 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 Thanks. > >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? You're right. What I meant was that the admin should be required to delete associated lists in order to be able to delete the domain, to avoid accidently deleting the domain. -- Henrik Rasmussen <her(a)adm.ku.dk> København, Danmark

7 years, 8 months

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

by hansen＠rc.org

Mark Sapiro wrote: > Restoring original Subject:, and doesn't this thread belong on > mailman-users(a)msailman3.org - CCing there. Sorry about both, Mark. I'm now here. Didn't know this one existed and was told to use the other list server. > > On 1/4/20 5:47 PM, Allan Hansen wrote: > > > > > a. The server was set up with the wrong domain > > name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ > > in > > the UI and thought that would do it, but Brian kindly sent me a list of additional > > instructions, which we then implemented. That made it possible to create a list in the new > > domain, subscribe people and post messages. However, messages are not archived. What extra > > step is needed to enable archiving? > > What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > > Archive archivers: hyperkitty, prototype > Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new > directory? Yes! I found them. But the message files end with the name of the old host, not the new host name under the new domain. > Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? There are 5 .pck files there dated 1/5/2002. > What's the setting for base_url in mailman-hyperkitty.cfg? It's base_url: https://<OLDHOSTNAME>/archives I suppose it should be changed to base_url: https://<NEWHOSTNAME>/archives But: What if we decided to have more than one domain, as the UI indicates is kosher? > Are there any errors in var/logs/mailman.log? Yep. Lots. They all are of this nature: Exception in "hyperkitty" archiver Traceback: ... File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 430, in _match_hostname match_hostname(cert, asserted_hostname) File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname % (hostname, dnsnames[0])) ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHOSTNAME'",) > > b. When I go to the server using the new domain (both > > before and after logging in), I see not just the lists I created in the new domain, but > > the lists created in the old domain. These lists of lists are domain specific and should > > not be listed together. That’s just IMHO, but not serious, as I will soon get rid of > > anything in the old domain. So feel free to ignore this one if this is intended, which I > > could see might be the case. > Set > FILTER_VHOST = True > in settings_local.py > > Yes, Brian told me to do the same (well, settings.py). > > This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > > # Only display mailing-lists from the same virtual host as the webserver > > FILTER_VHOST = True > You shouldn't edit settings.py. You should override the setting by > putting it in settings_local.py. Silly. I should have remembered that from back in the days. But if the local file is overriding, it should have worked, I'd think. > > Then Brian told me to restart qcluster: > > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster > qcluster is not what you need to restart. You need to restart whatever > is supporting the wsgi interface to Django. This may be uwsgi or > gunicorn or ??. Whatever it is, that's what needs to be restarted. Beats me, Mark. Brian, do you know? > > I then logged in, but the same lists are showing. It > > either takes the system a long time to reset or it has ignored the > > setting. > > Just tried it again, and the lists are all showing. Do I need to manually recompile the > > file? > > > > c. I then > > moved on to the templates and added a template for the message text to send to new > > subscribers. That resulted in the following error message when I went in as moderator to > > approve of a new subscription: > > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I > > see a bunch of postgres, python3, nginx, django-adminp but > > nothing explicitly with a ‘mailman’ string. > If you do ps ax|grep runner=, what do you see? If you don't see at > least three processes with --runner=rest:0:1, stop Mailman and start > Mailman. Yep. I did not get the whole string before. With your options I see three of these rest:0:1 processes. So I guess the REST stuff is running anyway. > If so, what's > in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's > called - defined as filename in the file handler in the LOGGING > definition in settings(_local).py. > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", > line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", > line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line > 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. > This is because of the domain change. In settings(_local).py you have a > setting for SITE_ID. Possibly, setting that in settings_local.py to a > value one greater that the current setting will do. Trying setting it to 1 (it was 0 before). > To be certain of the > correct value, you need to look at the django_site table in mailman's > database. That table has 3 columns, id, domain and name. The id for the > row of your domain is what needs to be set as SITE_ID. You lost me here. No idea how to access the Mailman database. Brian, do you know? > > [ABH] At this point I click to accept a subsription > > request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > > Traceback (most recent call last): > > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line > > 672, in urlopen > > chunked=chunked, > > File "/opt/mailman/mm/venv/lib/python3.7/site packages/urllib3/connectionpool.py", line > > 421, in _make_request > > six.raise_from(e, None) > > File "<string>", line 3, in raise_from > > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line > > 416, in _make_request > > httplib_response = conn.getresponse() > > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > > response.begin() > > File "/usr/lib/python3.7/http/client.py", line 296, in begin > > version, status, reason = self._read_status() > > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > > raise RemoteDisconnected("Remote end closed connection without" > > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? > Stop Mailman and then start it. No idea here, either. I looked online and found this: $ from mailman.commands.cli_control import Stop But it complained: from: too many arguments Must have found an out-of-date page. :-) Yours, Allan

5 years, 3 months

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

by Rafael Mora

El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 10:42 AM, Rafael Mora wrote: > > > > I've found the MX records on my cpanel but how do I redirect the emails > > going to my list to my private server? > > > You have to configure the MTA that is the MX for the domain to relay the > mail to the Mailman server. > Our domain is: LABBRANDS.COM We have that domain config in a Hosgator hosting. The emails sent to labbrands.com go to our hosting, so how do I tell cpanel in hostgator hosting that the mails sent to the list ( mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private server (we have static public IP address) ?? > > > > 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 > _______________________________________________ > 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: Alter Messages: Reply to confusion

by Abhilash Raj

On Mon, Sep 2, 2019, at 11:50 PM, paul(a)arenson.org wrote: > 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. This is something which is specific to Emails. There is a header called "Reply-To" which is used by email clients to send replies. That is the "default" address a reply will go to when you hit "reply button" in you email client. The setting you are talking about can alter the "Reply-To" header in the emails, for whatever reason they might have to do so. Ideally, you don't want to change the settings since it can break things for some of your users who use emails. > _______________________________________________ > 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, 7 months

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

by Mark Sapiro

On 7/12/21 8:25 AM, tibor.molnar(a)waltoninstitute.ie wrote: > Hi, > > I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: > > Superuser: Can do everything. > AnonymousUser: Can view list index and info pages. > Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. > > Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how? The user's `role` is a Django thing. A user can be given either `staff` or `superuser` status or both or neither. As far as Django is concerned, `staff` status only allows the user to visit the Django administration interface. Currently, Postorius has decorators @list_owner_required, @list_moderator_required and @superuser_required defined in postorius/auth/decorators.py. There is also a @login_required decorator in django.contrib.auth.decorators. Postorius decorates the list_new() function in postorius/views/list.py with @login_required and @superuser_required. It would be simple enough to create a new @staff_required decorator which would require staff or superuser status and replace the @superuser_required decorator on the list_new() function with @staff_required. Then any user with `staff` status could create lists. -- 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: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Stephen J. Turnbull

Franklin Weng writes: > In Debian's setting, under /usr/share/mailman3-web/ are these files: > > manage.py > settings_local.py -> /etc/mailman3/mailman-web.py > settings_local.py.sample > settings.py > urls.py > wsgi.py That looks right. This is a typical Debian approach to preserving local configuration automatically when Debian is upgraded. > In the top of settings_locas.py there are comments saying that this > file is to override default settings in > /usr/share/mailman3-web/settings.py, so I suppose hyperkitty > database should define here, Yes. > though it is different from /usr/share/mailman3-web/settings.py. In Debian, you can't control the contents of that file. It may be overwritten in any upgrade. That's why the settings_local.py approach is used. > In the settings_local.py, it defines sqliet3 and the file of 'NAME' > /var/lib/mailman3/web/mailman3web.db exists and is a sqlite3 format file. That's OK (until you need higher performance). > But in settings.py (which is supposed to be overridden by setting_local.py) > it defines using postgresql, which doesn't exist in my Debian system. I assume it is overridden, unless Debian really messed up its packaging. But it seem to be working for other users (at least, no complaints I can recall). > Is there any log I can trace the executing path? You really don't want to do that. > 14233 ? Ss 0:01 /usr/bin/uwsgi --plugin python3 --ini > /etc/mailman3/uwsgi.ini > 14236 ? Sl 0:00 /usr/bin/uwsgi --plugin python3 --ini > /etc/mailman3/uwsgi.ini I don't know much about uswgi, so I can't say whether multiple processes with the same invocation is a problem. It's something to keep in mind. Recently uwsgi is problematic. There are multiple threads in the last few weeks. Unfortunately, Mailman devs are mostly using Apache + mod_swgi or gunicorn, so we can't be terribly helpful if there is a problem with uwsgi. Apparently the Apache process with mod_swgi is irrelevant. > The /var/log/mailman3/web/mailman-web.log is at > https://pastebin.com/U3jHR6JS That log looks perfectly normal to me. Since the log looks normal, you don't need to worry about uwsgi yet, but you should review the threads in our archives. The only thing that strikes me about the log is that there are no accesses to ".../hyperkitty/api/...", which is how HyperKitty receives messages to archive. Perhaps you simply didn't send any messages during the period of the captured log, but if you did, it should be there. Three questions: 1. Do you have HyperKitty configured as the Mailman archiver in Mailman? 2. In mailman.cfg do you have [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /path/to/here/mailman-hyperkitty.cfg where the "configuration" value should give the full path to a mailman-hyperkitty.cfg file? 3. Do your lists have archiving configured on in Postorius? Steve

5 years, 5 months

[MM3-users] Re: Verification links to localhost

by Odhiambo Washington

On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <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]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] > 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 > = '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: https://docs.mailman3.org/en/latest/install/virtualenv.html# It is the official installation guide. There is a step where it tells you to create a file named settings.py, in a particular path. You really need that step. 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 list1(a)domain1.name (venv) [mailman@gw /opt/mailman]$mailman create another-lis(a)domain2.name Mailman will know how to handle this in conjunction with your MTA. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 2 months

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

by Jens Günther

Hey Stephen, thanks again for your reply! And also a late Happy New Year :-) Am 04.01.24 um 15:20 schrieb Stephen J. Turnbull: > > So my main question is now: does anybody know of a possibility with > > this command to extract only writable attributes!? > > If you mean doing this so you can PUT all of those at once, I'm pretty > sure it doesn't work that way. PUT creates or replaces a whole > object. If there's an existing value with read-only attributes, > that's not going to work. It may be possible to specify multiple > values to PATCH, but that's beyond my knowledge. Mh. I tried it this way: - I curled the config - tried to PUT it back into another list (didn't work b/c of read-only attributes) - I deleted all the attributes from the export - then PUT this file and it worked -> it only seems crazy to delete all the attributes myself, I would want to curl and save only writable attributes :-) > > Getting the config: > > curl -u restadmin:restpass > > localhost:8001/3.1/lists/listname.domain/config | jq > listname.domain > > Do you need to use curl (or anything other than Python 3) to do your > work for some reason? Life is a lot easier if you use mailmanclient. I don't need to use curl, no. This was just the only way I found till right now to export and reimport the config of a list. How would this work with mailmanclient? I'v never used it before and didn't find a hop-in for the right usage right away. Could you point me to the right direction or even write some sample-commands to get export and import of a lists config? That would be awesome! > > Just tried getting all the members: > > curl -u restadmin:restpass > > localhost:8001/3.1/lists/listname.domain/roster/member | jq > > > listname.domain.members > > > > But putting them back seems to be a different thing: > > curl -u restadmin:restpass -d @listname.domain.members -H "Content-Type: > > application/json" -X PUT > > localhost:8001/3.1/lists/listname.domain/roster/members > > Do you mean the difference between roster/member and roster/members? > Not sure why the would be, would have to look at the source. This was abviously my bad. It wasn't about members with s or not -> the right one would always be without: localhost:8001/3.1/lists/listname.domain/roster/member -> I just tried to export and import members of a list via the API just as I tried with the config. If you know of another way or how this could work, I also would be really glad. (it works with "mailman members $list > textfile" and reimport them via Postorius, I just tried it like that, since on commandline it would be easier for a whole set of lists) Thanks again and kind regards, Jens.

1 year, 3 months

[MM3-users] Can't deliver mails in queue

by Nathanael Schneider

Hello, I have stumbled upon some weird issues with my migration to mailman3.. I've followed the step by step instructions for installing mm3 manually in a venv with postfix and virtual aliases (if that is of any significance). Now the Problem is, that some lists don't deliver EMails at all. The list was one which I migrated with the mailman21 command. But the Mail I sent did not get through to no one and the mailman logs did not show anything. I then created a completely new List which did not exists in mm2.1, subscribed two addresses and sent myself an EMail. That one worked as intended. I then deleted the whole broken list and created it cleanly, added the same two people, sent an email and nothing. Did not show up in the Moderation Queue or anywhere. it also doesn't get shunted. It just never arrives. I then turned the log level to debug on the smtp module. And I only get the following statement, ever repeating, never ending: [...] May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4978db438> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb497f05f28> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4978adb38> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net [...] I have no clue what to do with this. I then turned the debug module loglevel to debug. Also nothing useful. Just an endless list of [...] May 19 18:17:29 2021 (7209) [outgoing] <function deliver at 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile May 19 18:17:29 2021 (7209) [outgoing] <function deliver at 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> [...] Which also tells me nothing I can understand. I have no clue what's going wrong. (I've turned on debugging both on the original member list and the reduced member list. Both hang on the first delivery they do). If I restart mailman, the message gets correctly shunted as it is interrupted mid-delivery. My maillogs don't register any activity beside the listpost. Any ideas what I need to do to figure out what's not working here or where the culprit could be? Not sure if it is related to the mailinglist being in mailman2.1 before. -- Nathanael Schneider

3 years, 11 months

[MM3-users] Re: Hacking attempts?

by Lists

Hi Steve, No, we’re nothing to do with Fedora, we just run a few low volume mailing lists for our members. Happy to send you example error emails, I received 1,987 in the past 24 hours. They seem to come in waves, it’s particularly bad right now, but it will die off to a lower level for a while, then hit a peak again in a week or so. Let me know how many examples you want and I will send them direct to your email. Thanks, Chris > On 14 Jul 2022, at 13:33, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Lists via Mailman-users writes: > >> We are seeing thousands of these emails every day, looks like >> someone is trying to hack our Mailman3 but would appreciate someone >> with more knowledge of MM3 to confirm. > > Who is "we"? Specifically, do you have something to do with the > Fedora Project (Linux distribution)? > > To be honest, this looks to me more like collateral damage from a web > crawler than a hacking attempt. It's a real service offered by your > server (unlike a lot of the bogus requests I see). More below. > >> Is this a problem with our setup? i.e. the “Internal Server Error” >> bit, or are the hackers just sending bad data that is causing the >> error? > > I don't think this is a Mailman message, but from Django, or perhaps > the 'django_mailman3.lib.auth.fedora' application (not sure whether > that's our code, despite the name it's probably calling into code we > borrow from Fedora). I'll look into an upstream bug report if this > isn't in our code. > >> also how do we stop/block this? > > 1. Put that URL in robots.txt to keep honest crawlers out (see > analysis of example report below). > 2. Firewall bad bots and script kiddies. That's what I do, anyway. > 3. Also, if you aren't associated with the Fedora project, you might > want to disable the Fedora social auth login (remove it from the > installed applications in settings.py). You should be careful > about that, because there's a chance some of your users depend on it. > > I'm surprised at the "thousands" part. I'd have to see a sample of 10 > or 20, and know something about your site, to judge whether *you* are > under attack, or if it's just a bunch of low-tech crawleres and > kiddies. I see up to a couple hundred a day, with most being attempts > to access actual resources via the IP address rather than the domain. > Over a couple of years I've banned 772 separate IP addresses (maybe a > dozen are netblocks, mostly /24s, but a couple of /16s). I suppose > that cuts down the number I see by quite a bit. > >> Subject: [Django] ERROR (EXTERNAL IP): >> Internal Server Error: /mailman3/accounts/fedora/login/ >> >> Internal Server Error: /mailman3/accounts/fedora/login/ >> >> TypeError at /accounts/fedora/login/ >> _openid_consumer() missing 2 required positional arguments: >> 'provider' and 'endpoint' >> Request URL: https://mailman.ardc.net/mailman3/accounts/fedora/login/?process=login&next… > > This looks like somebody tried to access the "44net" mailing list > archive, maybe legitimately but for some reason didn't provide > credentials. > > This could be script kiddies or perhaps somewhat clumsy reconnaissance to > see what social auth you support (although they're usually more secure > than passwords). However, REMOTE_ADDR = '157.90.177.212' resolves to > 212.177.90.157.in-addr.arpa domain name pointer ninja-crawler64.webmeup.com., > which looks like a legitimate but naive web crawler to me. That would > explain why they hit the right address (they got the login URL from > your top page, and then the provide credentials URL from the login > page, and then the submit button). They were just hitting every URL > they could parse. > >> Traceback: > > Nothing unexpected there, or in the rest of the diagnostic > information. > > Steve > > >

2 years, 9 months

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

by Abhilash Raj

On Wed, Mar 24, 2021, at 10:01 AM, bader(a)cchmc.org wrote: > So I am working with our Linux admin to install mailman3 in centos7 > following this instructions > https://docs.mailman3.org/en/latest/install/virtualenv.html# (and > adjusting for centos versus Debian) > The install went fine with the command “pip install wheel mailman > psycopg2-binary”until the config file. /etc/mailman3/mailman.cfg > > > The /etc/mailman3 directory did not get created? Should it have? It should not, `pip` cannot create these directories. You have to create them manually. > > We created it and the config file > > But “mailman info” throws errors > > venv) [mailman@bmimailmandr2 var]$ mailman info > Traceback (most recent call last): > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2336, in _wrap_pool_connect > return fn() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 364, in connect > return _ConnectionFairy._checkout(self) > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 778, in _checkout > fairy = _ConnectionRecord.checkout(pool) > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 495, in checkout > rec = pool._do_get() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/impl.py", line 140, in _do_get > self._dec_overflow() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ > with_traceback=exc_tb, > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ > raise exception > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/impl.py", line 137, in _do_get > return self._create_connection() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 309, in _create_connection > return _ConnectionRecor This seems to be trying to connecting to database. Have you setup the database as described in https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-database and then added the right values in mailman.cfg you created? You will see a [database] section with a placeholder MYPASSWORD to put your database password. > > I suspect it is not using the config file at /etc/mailman3/mailman.cfg It should do that by default, unless you have a `mailman.cfg` in the current working directory. > But we do not even see a mailman service in > /etc/systemd/system/mailman3.service. `pip install` cannot creates these files. You have to manually create both `/etc/mailman3/mailman.cfg` and the above systemd service file. I’ll update the docs to be more explicit about this. > > Also, we are using python 3.6, will that be a major issue? or should > spend the time to install 3.7 from source? 3.6 should be okay for now, we do run CI for 3.6 so we will know if there is any breakage and can let the users know about it. We do run atleast one server on 3.6 ourselves. It doesn’t EOL until end of this calendar year. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/26/19 12:17 PM, Alain Kohli wrote: > Thanks for the great explanation, that helped a lot! I'll try to work on > that issue if I find some time. In the meantime it would be neat to try > to clean up the old messages right before the backup. How can you > distinguish messages that have been moderated already? I couldn't really > find that in the database or the models. You could run the following in `mailman shell` $ /path/to/mailman shell Welcome to the GNU Mailman shell >>> lm = getUtility(IListManager) >>> ms = getUtility(IMessageStore) >>> for mlist in lm.mailing_lists: ... requestdb = IListRequests(mlist) ... for rq in requestdb.held_requests: ... key, msgdata = requestdb.get_request(rq.id) ... if msgdata['_request_type'] != 'held_message': ... continue ... msg = ms.get_message_by_id(key) ... print(msg['Message-ID-Hash']) ... U6QVO2GXMEQ5ZDQR2XCLDOH2FXPKJTWX 32HA6GKYE5FOVORLER7YAC3264BHG264 JM4NP3JRXBKKAL7UMM5XEXX644DQBAFJ L7FX6XKOOBP3YFFXUHA6EEJCQXX5BCHX DOJX55MRY6OYPZ4XFFTAQDD4I5MWJ3AD >>> What that prints is the names of all the files in the var/messages/ hierarchy which are currently held messages. Presumably the others are ones already handled. You could modify the above to write the list to a file and then wrap the whole thing in a shell script which would make the list and then do something like for f in `find var/messages -type f`;do n=`cut -d / -f5 <<<$f` for keep in `cat list` ;do k=0 if [ $n == $keep ] ;then k=1 break fi done if [ $k -eq 0 ]; then rm $f fi done in the above, list is the list of names to keep bade by the first script and -f5 in the cut command assumes the list from find is lines of the form var/messages/TJ/YF/TJYF5FETCRLOQZJ2H6Y4PMZP6M7GNLES. i.e. two subdirectories between messages/ and the file. -- 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] Things I miss about mailman2

by Quanah Gibson-Mount

Now that we are on mailman3, I'm finding things that were really useful in mailman2 are completely missing in mailman3, which seems odd, since they in particular affect the ability of list moderators to do their job well. a) When a post was made to a moderated list in mailman2, I would get an email that included a LINK to the held email. Now I just get a canned email saying I need to go to the dashboard, blah blah. Why was this link removed? It was extremely useful and now I have to jump through extra hoops. b) When a post is made to a moderated list in mailman2, when I went to the page to approve/deny/discard, there was additionally an option to remove the moderated flag from the user for all future emails. This option no longer exists. This was EXTREMELY useful, as we force all new members of the list to be moderated for a time while we evaluate the quality of their postings. Now I have to go manually track down the user and their settings. Unnecessary extra hoops to jump through c) When a post is made to a moderated list, one of the options when selecting REJECT was it allowed me to set a custom message when rejecting the email. This was extremely useful. For example today, someone emailed our bug tracking list directly instead of filing a bug. In the past, I would have added a note to them about what they should do (in this case, I would have told them to send their email to our community technical discussion list). Now I can no longer do that, I can only reject it or discard it. Why was this removed? --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: Mailman 3 stops delivering to a domain after too many bounces

by Tim Cutts

Are you sure that’s mailman doing that? What do your MTA logs say? I’ve certainly seen behaviour that looks like that in the past, but usually my MTA logs show that the first few are accepted by the remote site, and then the subsequent messages get rejected, usually as a result of over-zealous spam filtering. My approach to that has usually been to adjust my MTA settings to be a bit friendlier to the sites that tend to do this, and only send a few messages at a time. Tim > On 12 Jul 2022, at 08:34, Julian Kippels <kippels(a)hhu.de> wrote: > > Hi, > > We have recently upgraded from Mailman 2 to Mailman 3. Since then I > have observed many user reports that mails to mailing lists don't reach > all members. My suspicion is that there are too many "dead" members on > those lists. This was not a problem on Mailman 2, but has become a > problem on Mailman 3. It seems to me that for example Mailman 3 sends > mails to the first 5 existing member addresses from domain A, then > encounters several (20 or so seems to be the threshold) "dead" member > addresses from domain A that generate a bounce and then does not even > attempt to reach the remaining 800 member adresses from domain A and > only sends to members on domain B and domain C. > > Is there a way to globaly ignore bounces and send out mails to all > members of a list, no matter what? > > Thanks, > Julian > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 9 months

[MM3-users] SMTPAuthenticationError at /accounts/login/

by Stephen J. Turnbull

mmasoudf(a)aaas.org writes: > I have setup the stack according to: > Mailman Suite Documentation. Release 3.3 PDF file. > I configured > EMAIL_HOST_USER and > EMAIL_HOST_PASSWORD > in Django settings.py. I could not find the place that I might > configure it for Postfix I think it helps to start thinking about it from the other end. That is, Postfix is the mail server for all users on a multiuser system. Therefore in "normal" configurations it will use the authentication mechanisms provided by the host operating system.[1] You need to have a user for Mailman in any case, typically called "mailman" or "list".[2] Once you've configured a user for Mailman on the Postfix side, you use that user and authentication data for Mailman core, Postorius, and HyperKitty to send mail via Postfix. > I am running the site on AWS and to be able to use AWS mail-servers > I have to define following parameter for AWS: > smtp_sasl_password_maps which points to a hash for AWS 'ACCESS KEY > ID' and 'SECRET ACCESS KEY' I don't think that has anything to do with the Mailman-to-Postfix side of things; that's for Postfix to send to AWS's mail exchanger (aka MX). Steve Footnotes: [1] It may also be possible to create Postfix-only "virtual" users who have no existence as far as the OS is concerned, but I don't know anything about that. [2] I haven't thought carefully about whether using Mailman's user in Django would be a security risk, but as long as it only has access to Mailman I don't see how it can do more harm than Mailman itself can, and I don't see why it would be more subject to exploitation than Mailman itself is. Anybody with security chops who wants to weigh in, please do.

5 years

[MM3-users] Re: Hyperkitty

by Stephen J. Turnbull

Mark Labeste writes: > Thanks for your reply. I was abled point to the mailman.cfg path > appeared in mailman info. Below is the result of mailman conf. But > archive is still now showing on web browser. Sorry, can't help you without more information. Is your archive visible from the Internet? What do you mean by "archive is not showing"? Do you get an error indication (like HTTP 404 error "no such page")? Do you get the archive page but you expect to see email there and there isn't any? If something else, what? I assume you installed Mailman from a distribution. Which one? What does "mailman info" report? If that doesn't work, you'll have to find the installed Mailman hierarchy, probably /var/lib/mailman3 or /usr/lib/mailman3, and run "bin/mailman info" from there. What are the contents of these files: mailman.cfg (probably in /etc/mailman3/mailman.cfg) settings.py (there are a lot of these with different purposes, with luck you'll find the right one in /etc/mailman3/settings.py or possibly in var/etc/settings.py under the Mailman hierarchy) urls.py (may be in /etc/mailman3/urls.py, or next to settings.py) This list strips most attachments. However it should be possible to attach these files as long as the Content-Type is text/plain. If you're not sure what the Content-Type your email program applies, you can include them in the message body at the end. The following version information may be useful later, but it's not urgent. What versions of the following packages are installed: mailman3 (possibly just mailman) postorius hyperkitty gunicorn mailman-web mailmanclient django_mailman (possibly django-mailman) django (or Django) (all of the above may be prefixed with something that indicates that they are Python programs) apache (possibly apache2 or apache24) or possibly nginx uwsgi (may not be in use) Steve

1 year, 7 months

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

by Ruth Ivimey-Cook

Mark, While the venv will to a degree isolate you, my experience of the upgrade from 18 to 20 was that python3.6 was uninstalled and 3.8 installed. In this scenario, the mailman3 installation is subsequently broken because there is no python to run. It *is* possible to reinstall python3.6 after the dist upgrade is complete, and I would presume that after doing so mailman3 would probably resume ok. In my case I decided to continue using 3.8, which meant, in essence, rebuilding my mailman3 install -- not fun given my state of knowledge. I would therefore appreciate some guidance on performing the upgrade from 3.6 to 3.8 with the minimum of fuss. [I am not sure, but it could be possible to install python3.8 while using Ubuntu 18, so that the dist upgrade never breaks anything. Worth exploring.] Ruth On 13/05/2021 19:02, Mark Sapiro wrote: > 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. > > -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 11 months

[MM3-users] Re: Request Entity Too Large

by Stephen J. Turnbull

Christian Stalberg via Mailman-users writes: > I went into nginx.conf and raised the client_max_body_size from the default > 1M to 0, then restarted nginx. The '413 Request Entity Too Large' error has > gone away, but postings to the list are not distributed. The mail queue is > empty. Now what? How do you know the posts aren't distributed? If it's posters using Google mail complaining about not seeing their own posts, tell them to look in their Sent Mail folders. If your HTTPd was configured with a 1MB size limit, how about your MTA(s) and spam/malware filters? Has the mail spool's storage filled up? What is the mail that is not being delivered? If you configure Mailman to strip HTML, it's possible that the messages were empty after stripping an HTML part, in which case Mailman ignores them. In that case, try switching from strip HTML to convert HTML to plain text, or allow HTML. Otherwise, what is your MTA software? What mail filters (spam, size limits) are configured into it? What do you know about the affected posters, in particular, what are their systems' DMARC policies? Is the mail coming from inside your organization and passing through only your MTAs, or are there external MTAs involved? Is Mailman's MTA a boundary MTA (the MTA that talks to systems on the Internet outside your organization)? If not, what is in the logs for the boundary system? What do Mailman's MTA's logs say? Did the posts get to the MTA from wherever? Does the MTA say Mailman accepted them? Mailman can be a bit spotty about logging success, but errors are not supposed to pass silently -- if there was a failure Mailman knows about it should be logged in the Mailman logs. Then, what does the MTA log say about outgoing mail? Steve

3 years, 6 months

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

by Florian Fuchs

On Sat, Dec 03, 2016 at 17:25:24PM -0800, Terri Oda wrote: >On 2016-12-03 12:22 PM, Florian Fuchs wrote: >>I did some manual integration testing today >>(core+mailmanclient+postorius) which looked fine so far. I didn't get >>to test HyperKitty and the bundler though, so any help testing those >>would be very much appreciated. I will have some more time tomorrow. > >I tried to do some testing based on these wiki instructions last weekend >https://wiki.list.org/HyperKitty/DevelopmentSetupGuide > >and hit a "[Errno 61] Connection refused" issue when attempting to log >in to Postorius. I suspect it might be an issue with the mac, since >googling for the error (it's a django one) seems to find a lot of >people on macs with problems, but I didn't manage to narrow it down >more than that to make a useful bug report. Do you have a traceback somewhere? If you're logging in for the first time, it *might* have to do with allauth trying to verify your email address by sending you an confirmation email (which probably fails if you don't have smtp set up on your mac). If that's the case, we should probably try to catch this condition and display a useful error message instead of just letting it break. Cheers Florian >I did set up a new linux install on another machine to work on next, >though, so I may have something else to say on that front tomorrow. > > Terri > > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers(a)python.org >https://mail.python.org/mailman/listinfo/mailman-developers >Mailman FAQ: http://wiki.list.org/x/AgA3 >Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ >Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/f%40florianfuchs… > >Security Policy: http://wiki.list.org/x/QIA9

8 years, 4 months

[MM3-users] [Mailman-Users] Web interface for users (not admins)?

by Stephen J. Turnbull

Hi Skip! First, a bit of admin. Mailman 2 is still in active use, so we've split out a separate list for Mailman 3: mailman-users(a)mailman3.org. Subscribe at https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ You can use several common social media to authenticate yourself. You'll have to do the usual one-time key dance to verify your email address (sorry!) You will get good feedback from the users there (better than the OP list). ** Reply-To set, please use "reply to author" to follow up. ** Skip Montanaro writes: > So, I got to thinking... Are there any free web user (not admin) > interfaces which integrate with MM3? Yes. The HyperKitty archiver, which is part of the Mailman 3 suite[1], provides an interface for submitting posts as well as reading them, and has a few social media features (liking posts). > Something which when combined with MM3 could conceivably be an > alternative to Google Groups, (the now defunct) Yahoo! Groups, or > Groups.o? That's for your users to say. ;-) If you visit https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ you can try it for yourself. To post, you'll need to sign up (you can do that with a Google account, and I think both GitHub and GitLab are accepted as well. > I poked around the archives a bit and browsed list.org for a few > minutes, but turned up nothing. Or rather, all I found related to > web interfaces was the admin interface. HyperKitty issues mostly have to do with importing archives. The webservice being effectively synchronous and centralized doesn't have a lot of problems as compared to email, and many feature suggestions go directly to the tracker for HyperKitty. I'm not surprised you don't find much about HyperKitty as Web UI in the list archives.

3 years, 11 months

[MM3-users] postfix virtual domain and mailman 3

by work＠andrefincato.info

hi everyone! i start by saying that i browsed through the archives in here for the past three days, and re-read the mailman 3 docs several times, as well the postfix docs. the thread closest to my problem is this one https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ; i was not sure if it was good to re-open though. i have a postfix + dovecot setup using the "separate domains and non-unix accounts". problem: ``` postfix/smtpd[26356]: NOQUEUE: reject: RCPT from wout1-smtp.messagingengine.com[64.147.123.24]: 550 5.1.1 <list-name(a)domain.com>: Recipient address rejected: User unknown; from=<some(a)email.com> to=<list-name(a)domain.com> proto=ESMTP helo=<wout1-smtp.messagingengine.com> ``` postfix main.cf relevant portion for virtual users ``` # deliver mail for virtual users to Dovecot's LMTP socket virtual_transport = lmtp:unix:private/dovecot-lmtp # setup virtual domains and non-unix accounts virtual_mailbox_domains = /etc/postfix/vhosts virtual_mailbox_base = /var/spool/vmail virtual_mailbox_maps = hash:/etc/postfix/vmaps virtual_uid_maps = static:1001 virtual_gid_maps = static:1001 virtual_alias_maps = hash:/etc/postfix/valias ``` postfix `main.cf` mailman settings ``` transport_maps = regexp:/opt/mailman/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/var/data/postfix_domains ``` question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so ``` virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap ``` or do you suggest as a simple viable solution to create a new unix account and setup postfix to use local domains? thanks and hopefully my confusion arose from reading all these threads will dissipate soon!

5 years, 3 months

[MM3-users] Re: Setting up Admin Account

by Stephen J. Turnbull

Pierre Abbat writes: > On Friday, November 17, 2017 1:51:15 PM EST Simon Hanna wrote: > > You are not supposed to create the directory mailman-suite_project but > > clone the mailman-suite project from gitlab and use it. > > None of the manage.py commands listed by your search are the right ones. > > The correct one is the one included in the repository of mailman-suite > > It appears that setting up Mailman 3 requires knowledge of Django, which I > don't have. I'm going to try something else. You're welcome to do so since you know your needs better than we do, but please allow me to advise you that running Mailman 3 in most cases doesn't require knowledge of Django as long as (1) you follow the instructions *exactly*, and of course (2) assuming those instructions are correct. Mailman 3 being just on the edge of becoming the industry standard for mailing list managers, yes, assumption (2) is occasionally violated. In my experience, (1) is a more frequent source of user troubles. Either way, we[1] are one heck of a lot faster at responding than most commercial and open source products when users have trouble. And we do have reason to lay claim to "industry standard". Footnotes: [1] By "we" I really mean Mark Sapiro, Abhilash Raj, and off and on Simon Hanna. It's rare that it takes as much as 24 hours to get attention from one of them, and if Mark can handle it, usually you get an immediate solution. I haven't been able to keep up for months, but I hope to get back into the rotation soonish (in the new year). -- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years, 4 months

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

by Stephen J. Turnbull

Hi Serban, s.dobrau(a)ucl.ac.uk writes: > We are currently working on a migration plan for Mailman -> Mailman > 3. We have around over 3000 mailing lists with a total of 50K > members Medium-size. I guess a 2-CPU/4GB Linode or similar should handle the Mailman load (including Postorius and HyperKitty), you might want more memory and maybe more CPUs if you're running the RDBMS on the same host. In the 23k lists/50k users/100k inbound messages/day migration described below, we ended up reconfiguring the VMs 3 times before declaring the system stable. IMO the 2 x 8CPU/16GB final setup was way overpowered for the need, but we didn't try to calibrate finer than that. > and 500 worth of archived data. 500 whats? 500MB, 500GB, 500TB? Assuming 500GB, > Our plan is to have core+web (instance 1) and Hyperkitty (instance > 2). With the archives on the FS local to the Hyperkitty. The archives are in the database as BLOBs. There's no reason to have a separate instance for HyperKitty. It's not obvious to me that you need more than that 2x4 Linode for both Mailman and RDBMS, but if you're going to split it's Mailman vs RDMBS, not Mailman vs HyperKitty. > And all 3 tables (core, web, Hyperkitty) pointing to the same > database on a remote SQL (mysql-enterprise) instance. Using class > mailman.database.mysql.MySQLDatabase (and whatever necessary on the > Django/Hyperkitty instance). Make sure your MySQL database(s) for Mailman are configured with the utf8mb4 option for 4 byte UTF-8 support, or it will choke on emojis and the like. I don't think there are any other gotchas for MySQL. Note there are a lot more than 3 tables in Mailman's databases. The "traditional" configuration is a "mailman" database for core and a "mailmanweb" database for Django and the archives, but Mark says that as the tables are disjoint across Mailman, Django, and the archives there's no reason not to use a single "mailman" database for all of them. I believe that's how this list's host is configured. > Is this feasible, Yes. > if so what would be the recommended compute/storage > requirements. I would start with the spec above (2CPU/4GB). If that doesn't perform, bump it to taste. Mailman itself uses about a GB of RAM for all its runner processes. (I'm not a cloud expert, I just assume you can do that the way we did, very simply.) The Python code (including compiled .pycs) is about 300MB. The database storage requirements are nominal for Mailman and Django (maybe 100MB total in the database for a 23k lists, 50k users installation I worked on recently), and I think the database usage for the archives was approximately 1:1 vs. the Mailman2 mboxes. Mark may have a better estimate on that. There is also the full-text search index for the archives. I recommend Xapian, in my experience Whoosh is really slow.[1] I don't recall offhand how big those were but I would assume they're no smaller than 1/10 the size of the mboxes, and maybe quite a bit bigger. Importing list configurations, users, and subscriptions into Mailman 3 is pretty fast, as long as you're not using the stock Postfix support.[2] The problem is that generating the Postfix alias files for the lists seems to be noticably linear in number of lists, which means it's quadratic for the mass import. IIRC with 5000 lists you'd be looking at >1m/list just to keep regenerating Postfix's alias database, ie 5000 minutes. I found two solutions, both of which required patching Mailman. I hope to get both into the next release. I think we got it down to <5s/list, for 5000 lists that's < 1hr. Importing archives is ... yeeech. The client decided they didn't want a ton of archives anyway (you know corporations, if it's not required by law, shred it after 6 months). I don't recall the size estimate accurately but we kept 6 months X 4500 lists, maybe 100GB out of 2.3TB of mboxes. That took 24 hours to import into HyperKitty, without doing the full-text indexing. I do know the original conservative estimate was 20 days to import the whole 2,3 TB. The full-text indexing took more than a week if I remember correctly. The easiest thing to do is to just do no migration, keep the old archive online, and start populating the new archive when you switch over. It's possible to do both the HyperKitty import and full-text indexing incrementally with a bit of planning. It's also quite possible to migrate incrementally, a few lists at a time. Mailman 2 and Mailman 3 can coexist happily on the same host. Mark can advise on that, I think. The only other advice I remember offhand is that Mailman's outgoing smart host should be in the same datacenter as Mailman. We never did debug it, but the system described above with 23k lists had problems with the out queue stalling when smtp.client.com resolved to a different datacenter 500km away. :-) The problem went away as soon as they pinned the MX to the MTAs in the same datacenter. Footnotes: [1] If you're familiar with another full-text search engine, check the django-haystack docs. Haystack supports several other engines, your preference may be among them. [2] Exim4 does not have this problem. I don't know about other supported MTAs.

1 year, 5 months

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

by Stephen J. Turnbull

Mohsen Masoudfar writes: > It seems anybody can go to the site: > https://LISTSERVNAME/mailman3/postorius/lists/ > and click on the [Sign up] on the top-right corner and create an > account. Yes. > This can easily be automated, even though the next step, confirming > the email address, being ignored. I believe it can be used as a > target for a DOS attack by creating so many accounts, that > eventually causes an 'out of space' error. > > Is this a justified concern? "Justified" depends on who you think the attacker is. Theoretically it's a real possibility, but the space used by an unverified account is not large. I suspect there are always much more painful DoS attacks to worry about. > Is there a way to manage this feature in a secure way? In some sense, I don't think there is. The point of the feature is to allow anybody to sign up without authentication beyond having a usable email address. Either you allow the DoS attack or anything you do is likely to deny service to legitimate users. Brian's approach (cron job purging unverified users) is generally good hygiene, but I don't think it would do much against an deliberate attack. And it shouldn't be hard to automate the confirmation process. I guess you could handle that by purging accounts with no subscriptions or other roles on any lists, but that might annoy a few legitimate users. Probably the best you could do for an open server would be to throttle user creation to say 1 per minute (adjustable to the scale of your site). I don't know if there is currently a way to require admin approval for account creation (as opposed to list subscription). Perhaps we should add that if we don't have it. Steve

4 years, 7 months

[MM3-users] Running customized version of Mailman 3

by Alan Kelm

Since 2005, our organization has been running a customized version of Mailman 2 with extensions that meet our particular needs. The main novelty is support for /fixed subscription lists/, in which the list members are predetermined (corresponding to a "committee"). Fixed list subscribers are not offered the opportunity to unsubscribe, nor can others add themselves to the list. A further enhancement is /hybrid lists/ which, for example, have both a fixed and opt-in part. (This is implemented as a fixed list residing within an opt-in one in a way which is transparent to users). Our customizations consist of code adjustments (patches) to 23 files. We are considering moving to Mailman 3 and would like to do this in a way which makes it possible to periodically upgrade our installation to the newest Mailman version, without clobbering our customizations. Thus, I do not think that installing via "pip" is the right approach for us. While I'm relatively new to git and GitLab, they seem to be ideally suited to this situation. If I understand the developer documentation correctly, I start out by creating a "fork" and can later "fetch" changes from the master branch and "rebase" to bring them into our branch. I would welcome comments on what we are doing. I also wonder whether others might be interested in support for "fixed lists", if they are done in a way which can be "contributed" back into Mailman. I extend our "thank you" to the developers of Mailman who have provided the robust system which has served us well for 15 years and provides the possibility to extend this into the future. -Alan -- Alan Kelm Manager, Electronic Services Canadian Mathematical Society Tel: +1 (613) 733-2662 ext. 799 Please consider the environment. [cms web link] <https://cms.math.ca/> Alan Kelm Chef, services électroniques Société mathématique du Canada Tél : +1 (613) 733-2662 poste 799 Considérez svp l'environnement.

5 years, 1 month

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

by Henrik Rasmussen

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.

5 years, 7 months

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

by Odhiambo Washington

On Tue, Nov 7, 2023 at 2:07 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > bryan.kartzman(a)yu.edu writes: > > > I have both my mailman lists and django config in postgres > > databases. > > These are Mailman 3 lists? What Django config? Do you mean Postorius > and HyperKitty? Do you intend to use Postorius and HyperKitty on the > new server? > > > If I want to move my lists to another server that is running > > mailman 3, aside from copying the databases to the other server, > > Do you mean the other server is already actively distributing Mailman > list traffic, managing users and archives? Or is it fresh instance? > Hello Stephen et al, Since this topic is relevant to something I am faced with at the moment, I believe it's okay if I piggyback on the thread. I have a server that is already actively distributing Mailman list traffic, and managing users and archives. I have offered to take over another community ML (also using MM3) from another server and host the list on my server. 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. Any pointers on how to bring in this new site into my current setup?? -- 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: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

I don't think this reply got to the mailing list, so I am sending it again, sorry if its a duplicate. On Sat, 13 Mar 2021 00:33:58 -0500, Mark Sapiro wrote: > > On 3/12/21 7:36 PM, John Covici wrote: > > Hi. I am having a great deal of difficulty installing mailman3 using > > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > > mailman3. > > > > What I have done so far is to install the mailman3 packages from my > > repository and got this: > > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > > version 3.3.2 (apparently the core), postorius version 1.3.3 and > > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. > > > Are these gentoo packages? If so, I have no idea how they are > configured. Anyway I can tell, there was no configuration (we call them use flags) they just seemed to install the files in what seems to be the correct places. > > > > Now trying to read your documentation, it seems it wants me to > > reinstall some packages using pip in the home directory of the mailman > > user in a python virtual environment, that was the first thing. But I > > would like to avoid multiple package managers wherever possible -- > > gentoo is already a lot of maintainance without dealing with pip's > > maintainance. The binaries also seem to be different from my gentoo packages. > > > Our documantation generally covers installing from source. If you are > installing gentoo packages, you should be looking at gentoo docs and > going to gentoo for help. > > We recommend installing Mailman and the web components in a virtualenv, > but it is not a requirement. We also suggest that postgresql is a better > choice than MariaDB. > I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj. > > > So, how do I proceed with getting mailman3 up and working, configuring > > the database, configs, etc and I guess after doing that upgrading > > mailman2 and getting sendmail to interface properly with mailman3? > > Importing lists from Mailman 2 is done with the `mailman import21` > command. See > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. > Importing archives is done with the Django management > `hyperkitty_import` command. See > <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> > > For sendmail, see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Thanks. -- 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 -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 1 month

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

by Stephen J. Turnbull

worik writes: > People are starting to realise that you always (in the general case) > are paying for a service. Please, send me my checks! The people I follow on Twitter (around half are infosec or natsec professionals, the great majority of the rest are open source software developers) frequently do point out or complain about this kind of "payment". But most "ordinary people" I know (generally Americans and Asians) think that on balance they're well-served by the SNSes they subscribe to and by retailers like Amazon. They *like* the sacrifice of privacy. Especially the Chinese, since the government is already collecting "social credit information" on each and every one of them., they figure they might get the benefit of personalized service. > tl;dr The choice for or against using the big bad corporation > services needs to be clear and usable. It can't get clearer than big colorful buttons that do nothing if you don't click them. (Caveat: I need to check that those buttons' labels are local images or HTTPS URLs that go directly to the auth service.) IMO use of social auth *should* be a subscriber choice. Activists want to take that choice away by default, and impose the burden of providing it on all site administrators, possibly even all list administrators. In some cases, we might consider even providing that choice too much of a risk (canonical example: support list for DV -- domestic violence -- victims). But for most lists providing the choice should be the default IMO. We could provide a warning that "We believe that this authentication provider sells information about what sites you log in to to third parties" or something like that. That wouldn't bother me (as long as it didn't invite anybody to sue *us*, and was configurable by site admins in case they worry about getting sued). > The ship has not sailed. We can get back what we have lost. A huge quantity of data is already out there. Perhaps in Europe you can protect privacy in the future and even claw back PII collected in the past, but not for a decade (or several) in the US, and China and other authoritarian countries (including NATO and EU members!) are already moving fast in the *wrong* direction. > The new generation of web developers are, in my experience, too > enamoured with the cool stuff they can do, and ignore old grey > beards (like myself) talk of "attack surfaces" and "chains of > trust" Sure, I talk about those things frequently, too. But in this case concentrating on the privacy attack misses the fact social auth can reduce the hacking attack surface for many user-service combinations. > > Same thing if you use a weak password. > > Attack surfaces. "Whataboutism" is not a valid argument against the > argument that you should decrease your attack surface. Valid arguments are not "whataboutism." The weak password -- which *Mailman* does nothing to prevent and *Mailman developers* do not know how to prevent -- *is a relevant attack surface* for an attack you are ignoring. Attacks on reused passwords are impossible for a single site to prevent. There's also the attack on the password store itself. The big auth providers seem to be relatively good (compared to random Mom and Pop services) at protecting credentials and are getting better at it. It is not clear to me which attacks are more likely to succeed, and even less clear which ones are of concern to admins and subscribers. > But social authentication is enabled are the trackers are not > loaded too. Which trackers? I'm sure the social auth services do track which of their ids are requesting auth tokens from which services (I guess you could use TOR to obfuscate your server's address? not my pidgen). But that is all they get; stock Mailman doesn't allow any other conversation with the auth provider. > What is required is a configuration option in the interface not in > the text configuration files. The former is for list > administrators the latter is for site administrators. Currently > list administrators do not have that choice. That's right. In fact, domain admins don't have the choice, either. I guess we could give them the choice at the expense of code complexity. List administrators currently *can't* have the choice, by the nature of the URL for the login interface. In theory you could have a subdomain per list, or use the query parameter to identify a list that you want to log in to. The subdomain approach is a large burden on the domain administrator, and current Mailman can't easily handle it. The query parameter would be easier to implement, but users would probably forget it or get it wrong, which would be messy. In any case I think that would be very confusing if different lists on the same domain made the different choices, and the user subscribes to both lists. I'll think about whether the DV case is important enough to cater specially to, but I suspect that users are likely to go to the wrong login page rather often, and the additional complexity increases the attack surface slightly (at least in the subdomain approach, any MITM knows that you're logging in to a protected list, and perhaps so does the auth provider). We could also make this a subscriber choice, by allowing them to set a query parameter or cookie that identifies them or specifically requests no social auth. But that seems fragile and potentially infringes on privacy in a different way. This stuff is hard.... Steve

6 years, 2 months

[Test] Re: mailman-users@mailman3.org

by Barry Warsaw

On Apr 04, 2016, at 07:38 PM, Mark Sapiro wrote: >Things that need to be fixed soon in core are confirmation required for >email unsubscribe <https://gitlab.com/mailman/mailman/issues/213> and >DMARC mitigations, but I think we can open it up and announce it. Yes, let's do. I'll work on #213 asap. It shouldn't be a ton of work since all the workflow infrastructure exists and unsub workflow is easier than sub workflow. >If no one objects, I'll do that tomorrow. \o/ -Barry

9 years

[MM3-users] Re: [Mailman-Developers] Docker files for mailman

by Stephen J. Turnbull

Danil Smirnov writes: > Okay I've found that image can be built if you base on Ubuntu Trusty distro > (line 6 of the Dockerfile: "FROM ubuntu:trusty") and add ruby-sass to the > set of packages to install (line 13: "apt-get install -y git python3-dev > python3-pip python-dev python-pip python-virtualenv ruby-sass"). The absence of sass is a known problem with Debian-derived systems. > I'm not sure whether I need to change it in the Wiki... Please do, but do mention that currently it seems to a problem only for the Debian family of distributions. Steve

8 years, 5 months

[MM3-users] Re: Auth question

by David Krantz

On Sun, Mar 26, 2017 at 5:58 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > 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. When starting this as the recipe seems reasonable I find that I have no reliable source for git links for the parts. Some of the git links I find are marked with "do not use" so it is a bit hard having confidence in selecting one of the others. Cheers // David

8 years

[MM3-users] API Question: map list -> UI URL?

by tlhackque＠yahoo.com

Using the REST API, how do I get from a list / list configuration to the URL of the management GUI? I've looked through the data returned by the API and even the SQL schemas; I don't see the path. Am I missing something, or do I need to log an issue for this? I'm not particularly interested in the subscriber pages, but it ought to be possible to get there too... Thanks.

7 years, 10 months

[Test]What does HyperKitty do with HTML and images

by Mark Sapiro

7 years, 9 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 02:27 PM, Rafael Mora wrote: > > it says it needs whoosh > > How do I install that? on env2 with python2 or env with python3 ??? In env2 do 'pip install whoosh' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 8/1/17 1:14 PM, Rafael Mora wrote: > > Why does it say Address already in use? Because you are starting lm tp runner and it's already running. Do 'mailman stop'. Then ensure no Mailman processes are running. kill any if necessary. Then do 'mailman start'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

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

7 years, 8 months

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

by Rafael Mora

Hello, I created a test list called: testlist1(a)labbrands.com How do I do in order to redirect the incoming emails to that direction to my server with MM3 ?? Thanks -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

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

by Mark Sapiro

On 08/03/2017 12:15 PM, Rafael Mora wrote: > > Should I configure my private Centos7 server with subdomain > lists.labbrands.com? > Doing so how do I redirect the email to the private Centos where postfix > and MM3 are installed? Create a DNS A record for lists.labbrands.com with the IP of the Mailman server. You will also want a rDNS PTR record pointing from the IP to lists.labbrands.com. -- 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] Social Auth, howto?

by Claus-Justus Heine

Hi, sorry, this seems to be a Django stuff, but how do I enable this social auth stuff? I get the following Fedora: gives me a login screen (ok) Yahoo: gives me a login screen and lots of commercials (ok) OpenId: gives me a possibility to sign up or in (ok) Github: internal server error 500, Django log: DoesNotExist: SocialApp matching query does not exist. Same with GitLab and Google. Ok, seemingly I need to do something to make it work, has anyone a link to some snippet of documentation of example setup? Thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 7 months

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

by Dmitry Makovey

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

7 years, 5 months

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

by Barry Warsaw

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. Cheers, -Barry

7 years, 5 months

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

by Dmitry Makovey

On 10/25/2017 07:35 AM, Barry Warsaw wrote: > On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >> >> I just realized that "mailman members" only offers to "add members" via >> "-a filename" but I see no remove option. > > It’s true, `mailman members` doesn’t currently have a —remove option. I found Rest API call for single user removal but I am questioning it's effectiveness given that I need to use this operation to potentially remove 1500 members -- Sr System and DevOps Engineer SoM IRT

7 years, 5 months

[MM3-users] Re: mailman info traceback (Ubuntu Xenial)

by Mark Sapiro

On 10/25/2017 02:06 PM, Pierre Abbat wrote: > I'm trying to set up a mailing list server using Mailman.... Here is the result: > ... > KeyError: 'env_py' > > What am I doing wrong, and how do I fix it? See this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Setting up Admin Account

by Pierre Abbat

On Friday, November 17, 2017 1:51:15 PM EST Simon Hanna wrote: > You are not supposed to create the directory mailman-suite_project but > clone the mailman-suite project from gitlab and use it. > None of the manage.py commands listed by your search are the right ones. > The correct one is the one included in the repository of mailman-suite It appears that setting up Mailman 3 requires knowledge of Django, which I don't have. I'm going to try something else. Pierre -- gau do li'i co'e kei do

7 years, 4 months

[MM3-users] Re: Mailman 3 Installation Assistance

by Abhilash Raj

On Thu, Apr 5, 2018, at 8:36 AM, brian(a)emwd.com wrote: > I have posted the error on Github. Did you see anything wrong with my > docker-compose.yaml file? Probably nothing wrong with your config, I need to do a release :) It has been fixed. > I also have another question. For the HYPERKITTY_API_KEY setting, is > there an API key I need to generate and retrieve from somewhere or do I > just make one up? It is just something random that you should create yourself and add. -- Abhilash Raj maxking(a)asynchronous.in

7 years

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

by Johannes Winter

Am Sun, 6 May 2018 07:26:45 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 5/6/18 7:16 AM, Asaf Ohayon wrote: > > Thanks, > > I understand those features are not available (yet) on Postorius > > > We're working on getting template editing in Postorius for release > later this month. > Cool! I hope you also fix this issue https://gitlab.com/mailman/mailman/issues/409 while doing do? Best, Johannes

6 years, 11 months

[MM3-users] Re: List enumeration problem

by Simon Hanna

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...)

6 years, 11 months

[MM3-users] Re: Mailman 3 localization

by Stephen J. Turnbull

a.matveev(a)lan-project.ru writes: > Is there any documentation how to use this? I searched already, but > without success. This is managed entirely through Launchpad/Ubuntu. Nothing has been contributed back to upstream, and nobody has volunteered to do the work of pulling those files into our source tree and maintaining them as they are updated (there is a lot of churn in translations; keeping them in synch with release code is quite labor intensive). I would assume you can drop the .po file(s) into mailman/src/mailman/messages/ru/LC_MESSAGE/ and the build and install process will do the right thing.

6 years, 9 months

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

by robert.kydd＠gmail.com

Hi Mark, my apologies it is version 2.1.26 1. Do I find Mailman's file system using cPanel ? 2. Your quote: with the various UPPERCASE things replaced appropriately and then 'compile' it via ... msgfmt -o messages/en/LC_MESSAGES/mailman.mo messages/en/LC_MESSAGES/mailman.po Does the compiling happen when I use mailman or do I have to have a compiler for this to happen ? Regards Robert

6 years, 9 months

[MM3-users] Re: mailman command to remove members

by Mark Sapiro

On 07/31/2018 01:14 AM, Asaf Ohayon wrote: > Is there command like mailman members --add, > to mass-remove members from a list ? No. You could make a mailman shell script to do it, but other than that you'd need to do it via Postorius which has a mass removal function or via the REST API. -- 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: Stability issues

by Michael Schultheiss

Mark Sapiro wrote: > When it is unresponsive what is the state of the 'rest' runner and is it > listening on localhost:8001? I believe it's still listening on localhost:8001. I'll add some additional checks to our monitoring system to help us track down process crashes. > > What do you do to 'fix' it? To "fix" it, we restart mailman core with our systemd service script. -- ------------------------------------------------------------- Michael Schultheiss, RHCSA, RHCE OIT Administration Sr. Unix Systems Engineer Ivy Tech Community College schultmc(a)ivytech.edu

6 years, 7 months

[MM3-users] Re: Docker-mailman: Performance issue

by Simon Hanna

Not sure what happened to that email. I used the gmail android app to send it... it somehow ended up being base64 encoded... > Still, mass unsubscribing the members by clicking Unsubscribe all made theinterface time out. Using the REST API succeeded unsubscribing all, but still made the Mailman web interface inaccessible. > > How can I make Docker-mailman perform better, to avoid these timeouts. You (currently) can't. The issue is that the rest API doesn't expose endpoints to do bulk operations. So the Frontend has to do a request per subscription. If you want a perfomant (bulk) operation, you currently have to go through the mailman shell.

6 years, 6 months

[MM3-users] Re: Problem with missing MySQLDatabase

by Mark Sapiro

On 10/21/18 11:59 PM, Peter Sørensen wrote: > > So the problem has probably to do with this installed in python2.7 and not > python3. > How do I solve that ? If your system has a pip3 command, use that or possibly install python3-pip. Also, see some of the hits from googling force pip to use python3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Do not send email "The results of your email commands"

by erlonmz＠hotmail.com

Hello guys. Have to configure the mailman3 for not to send the e-mail " The results of your email commands" when an email is sent to "-leave@" and "-join@" ?? Sorry for my English, i from another country.

6 years, 4 months

[MM3-users] Re: Do not send email "The results of your email commands"

by Mark Sapiro

On 12/7/18 6:21 AM, erlonmz(a)hotmail.com wrote: > > Have to configure the mailman3 for not to send the e-mail " The results of your email commands" when an email is sent to "-leave@" and "-join@" ?? At the moment, you can't. This is a known issue. See <https://gitlab.com/mailman/mailman/issues/516>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Thu, Dec 20, 2018, at 1:44 PM, brian(a)emwd.com wrote: > Thanks. I removed the following from /opt/mailman/web/settings_local.py: > > EMAIL_HOST_USER = <username> > EMAIL_HOST_PASSWORD = <password> > > Do I need to restart mailman and if yes how?> Yes, you do need to restart mailman-web container. $ docker-compose restart mailman-web > > Thanks again, > 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] How can administrator sign people up to a list?

by worik

As a list administrator, how do I add a group of email addresses to a list? 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] Re: How can administrator sign people up to a list?

by worik

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] Re: Tracking from gravatar

by worik

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. 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] Archives visible to all

by worik

When I load my new mailing list system, before I log in, I can see the archives of all the lists. Without logging in. Even lists with archives set to private archives. What can I do about that? 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] How to count the number of members in a list using Mailman client?

by Alan So

I tried to do so using Mailman client but it is really slow for lists with size > 1000. I use the following code snippet: my_list = client.get_list(listname) print ("number of members =", len(my_list.members)) Are there any other ways to do so in a much faster speed? Thanks.

6 years, 1 month

[MM3-users] Re: Welcome Message

by brian＠emwd.com

I don't know how do that with a Docker Installation of Mailman. I believe Python 3 is part of the container. Its not installed natively on the server. I really am starting to hate Mailman 3. Nothing is easy with this application. I have installed it using Docker, via Ubuntu's repos, and now I am doing an installation of it from Source (via PiP) and there are hurdles everywhere. Not a happy camper at the moment. Brian

6 years

[MM3-users] Re: GDPR - save subscriptions confirmation emails

by Stephen J. Turnbull

Jörg Schulz writes: > did you find a way to archive the confirmation requests? Do you need an archive of the actual messages, or would logging be good enough? What information do you need? Is there a request for enhancement in the tracker? Steve

5 years, 11 months

[MM3-users] Do not show archives to public

by andrew.bernard＠gmail.com

Is there a way to have list archives only visible to list subscribers? Presently, they are world visible - unless I have configured my site incorrectly.

5 years, 10 months

[MM3-users] Re: Do not show archives to public

by Abhilash Raj

On Tue, Jun 18, 2019, at 4:32 AM, andrew.bernard(a)gmail.com wrote: > Is there a way to have list archives only visible to list subscribers? > Presently, they are world visible - unless I have configured my site > incorrectly. You can set archives to be private in Postorius under Settings -> Archiving -> Private Archives It might take some time for the changes to sync back to Archiver after you have updated the settings. > _______________________________________________ > 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: Reset digest number and volume

by Mark Sapiro

On 6/26/19 3:08 AM, andrew.bernard(a)gmail.com wrote: > How to do this? After lots of testing on my pre-release beta testing list, I want the first production digest to be reset toVolume 1, Number 1. You can do this in `mailman shell` by setting the list's `volume` and `next_digest_number` to 1. E.g., $ ./mailman shell -l list(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the list(a)example.com mailing list >>> m.volume = 1 >>> m.next_digest_number = 1 >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: ARC

by Mark Sapiro

On 8/13/19 5:04 AM, Marvin Gülker wrote: > > Do any large e-mail providers actually support ARC? Smaller ones like > Fastmail appearently do at least semi-manually[1], but what about the > relevant ones -- GMail, Microsoft, Yahoo (and in Germany, GMX et al.)? Gmail does. The question is not whether they support ARC, but whether they will trust you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Suspend a list temporarily

by Andrew Bernard

I need a bit of handholding here. What settings do I have to make to reject with a message, and how to make or modify a template with my message containing the reason for temporary list processing suspension? The message I get is: The message comes from a moderated member But I do not know where this comes from, or what it means. Sorry to be always so obtuse.

5 years, 7 months

[MM3-users] Re: Basic settings for a discussion list

by paul＠arenson.org

Also with regard to moderate ( SUBSCRIPTION POLICY--MODERATE), it seems only to work for those who do not do the full signup. Those who register with a password automatically appear as members in my two tests. I was glad I could moderate the one email address that applied by the form at the bottom, but I had hoped I could moderate all registrations. Not possible?

5 years, 7 months

[MM3-users] Editing templates from settings

by paul＠arenson.org

Hello again. Gradually coming along thanks to the help of other members. One thing I want to do is edit my headers or footers to have key info about my site. But it seems even if I skip spaces, when a message is received the spaces disappear. Likewise, is there any way to add basic formatting like BOLD? For example, if I make a footer like this... Skipping a space here __/__/__/__/__/_/__/__/__/__/ Our List _/__/__/__/__/_/__/__/__/__/ Skipping a space here ...the centering disappears, as do the skipped spaces, meaning the message after a header or before a footer looks cluttered, Is there a fix? Thank you.

5 years, 7 months

[MM3-users] Editing templates from settings

by paul＠arenson.org

Hello again. Gradually coming along thanks to the help of other members. One thing I want to do is edit my headers or footers to have key info about my site. But it seems even if I skip spaces, when a message is received the spaces disappear. Likewise, is there any way to add basic formatting like BOLD? For example, if I make a footer like this... Skipping a space here __/__/__/__/__/_/__/__/__/__/ Our List _/__/__/__/__/_/__/__/__/__/ Skipping a space here ...the centering disappears, as do the skipped spaces, meaning the message after a header or before a footer looks cluttered, Is there a fix? Thank you.

5 years, 7 months

[MM3-users] Re: My email address appears in quoted test in my list. Hoot change that.

by paul＠arenson.org

Thank you. When you say OPTIONAL, do you mean it is up to me (in the web interface or email client) to remove them as I have done below? Abhilash Raj wrote: > On Wed, Sep 4, 2019, at 5:41 PM, paul@-------- wrote: > > Hi. I thought I had the settings right, but I do not > > see one to get Thanks.

5 years, 7 months

[MM3-users] How to delete an archive

by Andrew Bernard

I deleted a list but I want to delete the archive as well. How do you do that? Also, I had a list called Test. I deleted it. I made a new list called Testing, with a different email address, bu the archive points to the test list. This seems to be messed up. Why? I am sorry to say I have had continuous trouble with many aspects of Hyperkitty from the beginning several months ago. I know that is not helpful, but I am starting to wonder about all this. Andrew

5 years, 7 months

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

by Alan So

Understood that member's moderation_action will supersede non-member's moderation_action. (But how about owner? Owner alone should have no such setting. Sometimes issues occur when one are both owner and non-member) For *_these_nonmembers, should they only exist in Mailman 2 and be converted using the "mailman import21" command? I cannot locate *_these_nonmembers using mailman client.

5 years, 5 months

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

by Alan So

Just aware that *_these_nonmembers in the table mailinglist and we notice that they were migrated when we run 'mailman import21'. The type is BLOB. Can we clear all settings using the mysql command line as they are not exposed as REST API?

5 years, 5 months

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

by Alan So

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.

5 years, 5 months

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

by Mark Sapiro

On 11/1/19 1:34 AM, Alan So wrote: > Understood that member's moderation_action will supersede non-member's moderation_action. (But how about owner? Owner alone should have no such setting. Sometimes issues occur when one are both owner and non-member) The fact that a post's sender might be an owner should have no effect. -- 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: Logging subscribes/unsubscribes

by Mark Sapiro

On 12/9/19 7:14 PM, Paul Arenson wrote: > > Which brings up another question—I don’t see a way to download subscribers in a list, which would be useful in situations like this or when migrating. The 'mailman members' command can do this. In Postorius the 'CSV Export' button at lists/<list-ID>/members/member/ will do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

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

by Torge Riedel

Am 16.01.20 um 20:22 schrieb Terri Oda: > but I've definitely seen this behaviour in Mailman 2 and had trouble with Mailman getting blocked as a result, so I think this would be a very nice feature request. Hi Terri, I agree. So how to proceed on that? Get developers involved, post somewhere a feature request? To be honest I don't know how this is handled in development community of mailman3. Best regards Torge

5 years, 3 months

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

by Torge Riedel

Am 18.01.20 um 19:45 schrieb Mark Sapiro: > The best way to report a bug, feature request, issue, etc is to use the > trackers at gitlab.com. In the case of Mailman core, this is > <https://gitlab.com/mailman/mailman/issues> Hi Mark, just opened a new issue: https://gitlab.com/mailman/mailman/issues/670 Best regards Torge

5 years, 3 months

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

by ghalpern＠shemesh.co.il

I think that database queries would be better for my purposes, but it does lead me to a new problem. My MM3 installation is with Docker, which means that Docker set up the PostgreSQL database automatically, which means that I do not know the password for said database. Do I have any hope of finding it, or will I have to take a different option?

5 years, 2 months

[MM3-users] Re: Archives with encoding characters

by Mark Sapiro

On 3/4/20 1:00 PM, Seth Seeger wrote: > > How do I find the raw digest message? Do you mean asking the member to View Raw Message, and then copy and paste that to me? That would be one way. Or you could subscribe an address of your own to the plain text digest and view the raw message directly. Of course, you'd need to be sure the digest you're looking at is one that has the problem. -- 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: Finding a user to delete them

by Quanah Gibson-Mount

--On Thursday, March 12, 2020 5:09 PM -0400 Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > Have you tried: > > https://yourmailman3domain.com/admin/ > > Mailman 3 uses Django as the user management. Thanks Brian, What permissions do I need to access Django? I made myself a server owner from the python console, but that didn't do it. Regards, 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: Finding a user to delete them

by Brian Carpenter

On 3/12/20 4:56 PM, Quanah Gibson-Mount wrote: > What permissions do I need to access Django? I made myself a server > owner from the python console, but that didn't do it. I believe you have to be a superuser which is created as part of the installation of mailman-core, postorius, and hyperkitty. Please see: https://docs.mailman3.org/en/latest/config-web.html -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 1 month

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

by john_warland＠hotmail.com

I came across this same error and solved it doing some googling and came across this statement. in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp change it to: local_recipient_maps = It fixed the immediate issue but I do not know enough to say why. Hope someone can elaborate on this.

4 years, 11 months

[MM3-users] Post log?

by Mark Dadgar

Is there the equivalent of the post log from mailman 2.x available? I see every logging option but that one listed here: https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm… <https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm…> That was a handy way to track list traffic statistics and I was hoping to munge up the old mm_stats script to use the mailman3 logging format. I am running the ubuntu 3.2.2-based package. Thanks, as always! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 11 months

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

by Alan So

Thanks. So, our current workaround is to add those owners to members such that their moderation action can be controlled correctly through Postorius.

4 years, 10 months

[MM3-users] Re: Running Mailman3 under supervisord

by Mark Sapiro

On 7/26/20 6:08 AM, Odhiambo Washington wrote: > Hello world, > > Is it possible to run MM3 under supervisord? > What would I use for command= ?? I'm sure it's possible, but I can't tell you how to do it. You might get some hints from <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> -- 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: Creating superuser - problem with documentation or it's just me?

by Mark Sapiro

On 7/28/20 2:16 AM, Odhiambo Washington wrote: > > So, I should run /opt/mailman/mm/bin/django-admin with a valid argument, > right? > Like /opt/mailman/mm/bin/django-admin createsuperuser ... > How do I get all the available arguments for django-admin? That is what I > was attempting to do by passing --help to it. /opt/mailman/mm/bin/django-admin with --help or no arguments at all. -- 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] Anyone integrated Single Sign On like Azure SSO with Mailman3?

by Jacob Bargery

We are looking at whether it is possible to integrate Azure Single Sign On with Mailman3 to streamline use for our users, has anyone had any luck with doing this? If so, how did you go about doing so? Thanks

4 years, 8 months

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

by Gilles Filippini

Hi, Jacob Bargery a écrit le 28/07/2020 à 22:28 : > We are looking at whether it is possible to integrate Azure Single Sign On with Mailman3 to streamline use for our users, has anyone had any luck with doing this? If so, how did you go about doing so? I did such a thing with LemonLDAP-ng and the OpenID Connect protocol. I just had to add the django module mozilla-django-oidc and a custom logout method. The mozilla-django-oidc documentation [1] was quite helpful. [1] https://mozilla-django-oidc.readthedocs.io/en/stable/installation.html#quic… Best, _g.

4 years, 8 months

[MM3-users] Re: Problem with list creation

by Abhilash Raj

On Sat, Sep 19, 2020, at 2:39 PM, Pawel Grzywaczewski wrote: > We use Postgres but DB is on remote host. Do you have some sort of instrumentation in the database layer to get the latency for the requests? Also, you mentioned that you are creating lists via the curl command, are you doing in sequence via a loop or parallely via multiple threads at a specific requests/second to the Mailman server? > > Cheers, > Paweł > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 5:05 PM, Mark Sapiro wrote: > 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. Just clarifying Mark. I was surprised by your answer that's all. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] mailman-suite scheduled tasks

by Eric Broens

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? Best Regards,Eric

4 years, 4 months

[MM3-users] Re: Postorius upgrade issue

by Mark Sapiro

On 2/8/21 3:38 PM, Joel Lord wrote: > So I tried to do this after upgrading, fortunately only from 1 point > release back, and I get "ModuleNotFoundError: No module named > 'paintstore'" from the collectstatic. Do you still have 'paintstore' in INSTALLED_APPS in your Django settings? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Postorius upgrade issue

by Joel Lord

Well, for a change that was an easy fix... Thanks! On 2/8/2021 6:47 PM, Mark Sapiro wrote: > On 2/8/21 3:38 PM, Joel Lord wrote: >> So I tried to do this after upgrading, fortunately only from 1 point >> release back, and I get "ModuleNotFoundError: No module named >> 'paintstore'" from the collectstatic. > > > Do you still have 'paintstore' in INSTALLED_APPS in your Django settings? > -- Joel Lord

4 years, 2 months

[MM3-users] Re: spanish localization

by Stephen J. Turnbull

Victoriano Giralt writes: > Mark, I'd say the Mailman core message files taht get installed by pip > are "a bit outdated" (source files dates point to a nightly build) ... > proof here: I don't understand what you think this proves. We can't do the translations ourselves; we don't have the lingistic skills. So the dates on the .po files are going to reflect translator activity as well as core dev activity. Am I missing something that we can do something about?

4 years, 2 months

[MM3-users] Re: Imported Digest Settings

by Brian Carpenter

On 2/16/21 6:13 PM, Mark Sapiro wrote: > On 2/16/21 2:28 PM, Brian Carpenter wrote: >> The beginning of my OP stated I was using Mailman 3.3.3. > Then please get me a copy of the complete raw digest message so I can > try to find the underlying issue. > Not sure how to do that. Do you mean have the list member forward their garbled digest message to me? Is that what you need? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Imported Digest Settings

by Mark Sapiro

On 2/16/21 4:08 PM, Brian Carpenter wrote: > On 2/16/21 6:13 PM, Mark Sapiro wrote: >> On 2/16/21 2:28 PM, Brian Carpenter wrote: >>> The beginning of my OP stated I was using Mailman 3.3.3. >> Then please get me a copy of the complete raw digest message so I can >> try to find the underlying issue. >> > Not sure how to do that. Do you mean have the list member forward their > garbled digest message to me? Is that what you need? > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Domain ownership issues

by Mark Sapiro

On 3/2/21 2:46 PM, peter(a)chubb.wattle.id.au wrote: > > So is there any way to delegate list creation? Or does the site owner You should be able to do it via REST outside of Postorius, but that would involve setting up some web form to actually do it. Or you could work on implementing it in Postorius and submit a merge request. -- 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] hooking up mailman and sendmail

by John Covici

Hi. So, I have sendmail as my mta and I want mailman to use it. So far, I have a local delivery agent able to send on port 8024. So, what do I have to tell mailman to use sendmail and listen on port 8024 and to send on port 25? Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 1 month

[MM3-users] Re: SpamAssassin header confusion

by skenny＠scss.tcd.ie

I figured this out at last. As Mark indicates, it's nothing to do with Mailman. It has everything to do with Amavis. I'll summarize here tomorrow, in case it may be of interest. Stephen

4 years

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

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210621 20:59]: > We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): > > <form method="POST" action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> > <input name="email" value="" type="text"><br> > <input name="email-button" value="Anmelden" type="submit"> > </form> > > When I now enter a mailaddress, the quoted error occurs. We do the same by sending an mail to the -subscribe-adress. This works well. Andi

3 years, 10 months

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

by Andreas Barth

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

3 years, 10 months

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

by Danil Smirnov

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). 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

3 years, 7 months

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

by Torge Riedel

Am 21.09.21 um 15:20 schrieb Philip Colmer: > sharing your configuration I do. What configuration do you need? There is no special rspamd config in mailman3 on my setup. Kind regards Torge

3 years, 7 months

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

by gordon＠dickens.com

Peter, David and Mark, Thanks very much for your prompt replies. I have reported this issue to the Debian folks using the Debian "reportbug" command. 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? Thanks, Gordon

3 years, 3 months

[MM3-users] Re: Templates do not work

by Mark Sapiro

On 4/28/22 15:59, Eggert Ehmke wrote: > It seems my apache vhost settings are messed up. To access the postorius page, I have to > use URLs like this: > > > https://lists.[1]tld_/mailman3/mailman3/lists/_ > -------- > [1] https://lists.ftv-spandau.de/mailman3/mailman3/lists/ I would try ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.ftv-spandau.de/mailman3/' ``` I think that should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

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

by Stefan Bauer

Dear Users, we are very happy mailman3-users but suffer from very old packages in Ubuntu 18LTS. Unfortunately due to some python-restrictions¹, mailman3 is broken in Ubuntu20LTS and gone² in Ubuntu 22LTS, so we do not have any working upgrade-path :/ What do you recommend? Any help is greatly appreciated. thanks in advance. Stefan ¹ https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1877701 ² https://packages.ubuntu.com/search?keywords=mailman3-full

2 years, 11 months

[MM3-users] Re: Templates do not work

by Eggert Ehmke

Thank, you, I cleaned up my apache config, now the url works. Problem solved.

2 years, 11 months

[MM3-users] Re: best pratice - set default MM settings and make them update-save

by Stefan Bauer

Thank you. That works pretty good. I just made all my settings in base.py and have an eye on that file. If doing a mass subscribe, nowadays i have to check Pre Verified If checked, users will not have to verify that their email address is valid. Is there also a way to have this box checked by default or do not request a verifcation at all? Could not find any flag in base.py. Thanks. Stefan

2 years, 11 months

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

by Peter Münster

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

2 years, 7 months

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

by Stephen J. Turnbull

Tibor Molnar writes: > I wonder if anyone else if having this trouble that all the held > message notifications are landing in junk folder. It's reported occasionally. This is automated pattern recognition doing its thing: these notifications *do* present very similar content *repeatedly* and *are* sent by a bot, and the algorithms figure that out quickly. Make sure the site DKIM signs its outgoing mail and whitelist the site, or whitelist the bot's address. Steve

2 years, 7 months

[MM3-users] collectstatic msg

by tflatley＠gmail.com

Hello, in a venv install , after the database migration is complete i run the followign collectstatic compress compilemessages for a package install, i run the following ython3 manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman3/web/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: no CommandError: Collecting static files cancelled. on venv i did not get this msg - venv output 406 static files copied to /opt/mailman/web/static is it safe to overwrite these files? also before i run this do i need the mailman services down? thaniks

2 years, 6 months

[MM3-users] Re: collectstatic msg

by Mark Sapiro

On 9/26/22 11:47, tflatley(a)gmail.com wrote: > > is it safe to overwrite these files? also before i run this do i need the mailman services down? Yes, it is safe. All the Django admin commands only affect the web UI. It is good to stop whatever service (uWSGI, gunicorn, Apache mod_wsgi, ???) supports the web UI while doing these updates or at least restart after. -- 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] 2 postfix instances and 1 mailman instance possible?

by charlie derr

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 postfix: 2.10.1-9.el7 (both via rh/centos repo(s)) thanks so very much for any assistance/direction you're able to provide, ~c -- Charlie Derr Director of Instructional Technology Bard College at Simon's Rock https://simons-rock.edu Encryption key: http://hope.simons-rock.edu/~cderr/ 413-528-7344 Pronouns: he/him/his

2 years, 6 months

[MM3-users] Re: Verification links to localhost

by Odhiambo Washington

On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <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 > 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? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 2 months

Search results for query "dO"