Search results for "Postorius" - Mailman-users

Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Mark Sapiro

On August 20, 2025 4:37:18 AM EDT, "Stephen J. Turnbull" <steve(a)turnbull.jp> wrote: >Odhiambo Washington via Mailman-users writes: > > > > > The superuser account uses my address - odhiambo at gmail dot > > > > com. I am also the listowner for most lists. > > > > I tried unsuccessfully to create an account on Postorious using the same > > > > email address. > >I don't see how you can do this. It's the same user database, and >email addresses are accepted as identifying a unique User object in >the database for authentication and authorization purposes in Django. That is correct. You can't have two accounts in Postorius/Django with the same email address. But why would you want to? There should be no problem with a single Django user being subscribed to a list with more than one role. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 months, 1 week

Re: Redundant and load balanced Mailman3

by Stephen J. Turnbull

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

5 years, 5 months

Re: Captcha or similar for new signups?

by Odhiambo Washington

On Wed, Nov 29, 2023 at 12:44 AM <peter(a)chubb.wattle.id.au> wrote: > Hi Folks, > Does anyone have a recipe for adding captcha or similar to stop bot > accounts signing up with Postorius? We're seeing a heap of fake signups > resulting in confirmation emails going to people who haven't signed > up, with user names like 'CAOXpYhPFPBFr' -- I'd like to make it > just a little harder for bots to sign up. > > Too many confirmation emails going to non-existent email addresses > reduces our mail reputation, and increases the likelihood that > legit email is flagged as spam. Maybe it will come soon seeing as it's already somewhere - https://gitlab.com/mailman/django-mailman3/-/issues/33 or you can patch your install by looking at the patches at https://github.com/pbiering/mailman3-rpm/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

Re: Clean-up of non-members

by Torge Riedel

Feature request created: https://gitlab.com/mailman/postorius/-/issues/617 Am 22.12.24 um 14:25 schrieb Odhiambo Washington: > > > On Sun, Dec 22, 2024 at 3:18 PM Torge Riedel via Mailman-users <mailman-users(a)mailman3.org> wrote: > > Dears, > > I am currently cleaning up a huge list of non-members. In contrast to the members list where I can select multiple entries and delete them at once, this is not possible in the list of non-members? > > Can this be enabled in a future release? > > > > Perhaps you can make a feature request in gitlab? > And while at it, please add: mailman nonmembers LISTSPEC > With the later, it would be easier to delete non-members from the CLI as well. > > -- > 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

Re: Issues with @gmail.com addresses

by Stephen J. Turnbull

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

2 years, 5 months

Re: Migration from old server to new server failed

by Mark Sapiro

On 2/16/24 07:12, Helio Loureiro wrote: > - start mailman3 and mailman-3web > - run mailman3-web migrate You should run mailman3-web migrate when mailman-3web is not running. > django.db.utils.OperationalError: (1050, "Table > 'hyperkitty_mailinglist_moderators' already exists") > > I tried to drop the table, but then it complained about another one. I > dropped all the complained tables and as result hypperkitty never > started. So I went back to see why the first error happened. The errors occurred because you had recently added tables in your database so they couldn't be added by the migrations. Dropping the tables was the correct thing to do. Did you ultimately successfully run all the migrations? When you say `hypperkitty never started`, what exactly does that mean? What happens when you try to access the archives? Can you access postorius? Are any errors logged in mailman3-web's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Re: cache files?

by Dave McGuire

On 7/12/21 10:45 PM, Mark Sapiro wrote: >> Hi folks. I'm seeing quite a few .css files, thousands of them >> totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. >> Some of them date back to when I set up the mm3 instance a few years ago. >> >> Is this expected, or am I missing a cron job or something to clean >> them up? > > This is not expected. I don't see it on the instances I manage. > > In the `static` directory, I see > ``` > $ du -h -d 1 > 1.7M ./admin > 12K ./facebook > 68K ./django_extensions > 4.0K ./browserid > 68K ./django-mailman3 > 2.6M ./postorius > 12K ./paintstore > 1.6M ./rest_framework > 5.2M ./hyperkitty > 404K ./CACHE > 12M . > $ find -type f|wc > 401 401 18253 > ``` > > I think when you run the Django admin `collectstatic` command, you need > to specify the `--clear` option. Interesting, I know nothing of that command. Is that something that should be run periodically? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 7 months

Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Abhilash Raj

On Wed, Jun 12, 2019, at 8:08 AM, Michael Sage wrote: > Hi, > I came across this really useful guide (posted to the list earlier). It > has all gone really well and mailman 3 is installed. However, I have an > issue, when I go to login using Postorius, I get the login page when I > enter my credentials the page appears to hang and eventually goes to a > Error 500 page. This totally hangs all of the mailman 3 web interface > (but not apache). I then have to reboot the server to even get back to > the login page. Sorry, but can you post the URL to the guide you were following? It it hard to keep up with all the previous emails on this list. > > Any tips please? > > Thanks > > _______________________________________________ > 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, 8 months

Re: Can't subscribe on new site/domain

by Flo

On 10/11/25 00:18, Mark Sapiro wrote: > On 10/10/25 1:47 PM, Flo via Mailman-users wrote: >> >> :/var/lib/mailman3/data# sqlite3 mailman.db >> SQLite version 3.46.1 2024-08-13 09:16:08 >> Enter ".help" for usage hints. >> sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON >> site_id = django_site.id; >> Parse error: no such table: django_mailman3_maildomain >> sqlite> > > Is there a second database? Something like mailmanweb.db. If so, use > that one. > I found it, it's in a different directory: /var/lib/mailman3/web# sqlite3 mailman3web.db SQLite version 3.46.1 2024-08-13 09:16:08 Enter ".help" for usage hints. sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON site_id = django_site.id; ... ... 8|lists.example.com|7|7|Lists of Example|lists.example.com sqlite> The two working domains are first (...) . The problematic domain (renamed to lists.example.com) appears when I create it in Postorius. For me the only conspicuous is that the numbers are 8|.|7|7 while at the other two entries they are the same for the whole line: 2|.|2|2 and 4|.|4|4 . Flo

4 months, 2 weeks

Re: Mailman 3 Installation Assistance

by Abhilash Raj

On Sat, Mar 31, 2018, at 9:33 AM, brian(a)emwd.com wrote: > I am making a serious attempt at installing Mailman 3 using docker. I > have a CentOS 7 server setup via Linode. I am using the following > documentation to setup a Mailman 3 server: > > https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/ The official docs for container images sits here[1]. Although, I wen through the above blog very quickly and it seems to me that most of parts related to Mailman are pretty straightforward and similar to official docs. [1]: https://asynchronous.in/docker-mailman/ > > I have Docker, Postfix, and Nginx installed and working fine. The > installation of the Mailman 3 container went fine. However I am getting > the following error when I go to test Posterius via shell: > > curl http://172.19.199.3:8000/postorius/lists/ > curl: (7) Failed connect to 172.19.199.3:8000; Connection refused There are few things you can do to debug: 1. check if mailman-web container is even running $ docker ps 2. check if there are anything in /opt/mailman/web/logs/ . -- Abhilash Raj maxking(a)asynchronous.in

7 years, 10 months

Mailman-users search results for query "Postorius"