Search results for "Postorius" - Mailman-users

Re: Emergency moderation and clearing out a lot of held messages

by Abhilash Raj

On 12/14/22 03:31, Mark Sapiro wrote: > On 12/13/22 10:38, Dan Caballero wrote: >> Hi Mark, >> >> I ran the commands and it took about 35 seconds for the loop to run. >> >> Here's the result. >> >>>>> count >> 4168 > > > So that's at least part of the issue. How does 35 seconds compare to the > length of time to process one moderated message through Postorius? > It seems it has to do with in-efficient lookup of the actual entry in the pendings table which needs to be purged after handling a held message. It scales linearly with how many entries are there in pendedkeyvalue and pendings tables. I was actually browsing through the perf metrics on mail.python.org and found the slowest API response from Core is handling held messages and spent some time last night trying to improve it [1]. The linked MR should significantly reduce the time, although there is more that can be done to make it even better. I haven't had a chance to benchmark my solution yet, but I am hoping it will reduce the latency quite significantly. I'll report on the linked issue [2] after deploying [1] on m.p.o. how much it helped. [1]: https://gitlab.com/mailman/mailman/-/merge_requests/1068 [2]: https://gitlab.com/mailman/mailman/-/issues/1045 -- thanks, Abhilash Raj (maxking)

3 years, 3 months

Mixing Mailman 3 with AWS SES

by Stephen J. Turnbull

Ralph Weber writes: > I am moving the website www.t10.org from a private/corporate VM to > AWS EC2s. > > For many years, t10.org has had very happy results with using > Mailman 2 for its email reflector, and I have no real concerns > about moving to Mailman 3. My bugbear is the fact that I need the > following mixed bag of incoming email addresses to work in concert > with each other to receive and handle emails. > > > t10(a)t10.org (Primary Mailman Reflector) > > chair(a)t10.org (Mailman Reflector to direct messages to the T10 > > chair and his designates) > * docs(a)t10.org (document posting mechanics - serviced by a small > mountain of home-grown code code > * bbs(a)t10.org (other publicly accessible services - serviced by > code that recalls the days when everything as done on a Bulletin > Board System, BBS) This isn't a Mailman question, to be frank. As Abhilash points out, Mailman doesn't care about other mailboxes served by its host (unless they conflict with list names or adinistrative addresses derived from list names, which evidently yours do not). It's a question about the mail service at AWS. I've not seen any documentation in our project about setting up at AWS; I don't know anybody who has done so. (I haven't looked for either though.) I took a quick look for AWS SES documentation. They don't seem to have any real documentation online for the general public, only lists of features. They also seem to be very focused on sending rather than receiving. Much talk of how much mail you can send, bulk emailing, statistics on responses, and the like. None about setting up for incoming mail. Probably I could get access to online help if I signed up for a free account, but that's above my pay grade. > My best guess is that the AWS Simple Email Service (SES) needs to > sit in front of both Mailman and the home-grown code, I don't know if AWS provides an alternative Complicated Email Service, but yes, something like SES is going to have to sit in front of the various mailboxes. Mailman itself has a certain amount of capability to deal with the main email protocols, but it is definitely not capable of replacing the main mail server. For security reasons I would definitely advise against any Mailman 3 presence directly on the Internet. It was designed on the assumption that it would talk to the Internet via a standard mail server, Postorius (for administration), and HyperKitty (for mail archives)[1], and occasionally to admins logging in with shell accounts. > All available evidence read to date URLs, please. As I wrote above, Amazon's documentation is at best not very discoverable. > suggests that the default AWS installation Whose default installation of Mailman? AWS's? Typical 3rd party configurations? > of Mailman 3 assumes that Mailman 3 is the *only* receiver of > emails in the configuration. That's possible, but it's likely an artifact of the application -- I would expect that many who host Mailman on AWS do so to isolate Mailman from other services they provide. So it seems reasonable that in many such installations Mailman is *the* service for that instance. But mail servers are designed to be many inputs, many outputs services. If SES itself is as restricted as you fear, surely AWS provides an alternative, more powerful mail service. I can imagine quite a few restrictions, other than the backing application, on the SES that Amazon *might* impose. But without access to documentation, we can't say much. > Or... Hercules may have already cleaned the Augean Stables, and > left behind a AWS Lambda function that can serve as a keystone > puzzle piece for solving my dilemma. Good luck on that. I don't know of any, but that would be a quick solution for you. I hope somebody here knows more. As evidenced by Andrew's post, there are folks thinking about it, so maybe somebody's actually tried -- anybody? Successes? Pitfalls to watch for? The other issue Andrew mentions could be important. Since Solar Winds I'm seeing daily attempts to access my O365 server (nonexistent) from AWS. Given the size of AWS, I think they probably actually do a good job of keeping felonious behavior to a minimum[2], but a lot of folks I know are happy to cut off huge netblocks until somebody they know actually complains. :-( Footnotes: [1] Or more precisely, some webservice providing those services mediating between the Internet and Mailman sitting cozily behind a firewall. [2] DigitalOcean, on the other hand, is accumulating blocked /24s, and even /16s, at my firewall. But that's another story.

5 years

Re: Post-installation documentation?

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/24/21 9:40 AM, David Newman wrote: > > > > IMO post-installation docs for list admins would be a big help in > > Mailman3 adoption. I'm willing to help with this. > > > Thank you for being willing to contribute. +1 > I think the place for list admin docs would be in the > https://gitlab.com/mailman/mailman-suite-doc project which is the > source for https://docs.mailman3.org/en/latest/. +1 > Here are the steps to migrate a 2.1 list named `alist(a)example.com` and > its archives. This is documented at https://docs.list.org/en/latest/ (prominent link in sidebar). This appears to be completely different from https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which I guess is just a redirect). But it looks like the sources are in the some gitlab repo?! > > And I don't know where to add list members. I guess it would be a good idea to provide an image of the menu tree for Postorius. > Did you specify the list's fqdn as in > https://www.example.com/archives/list/list@example.com/ That's not an FQDN, though. "example.com" might be one, but that whole thing is the URL to the archive. Pedantry aside, I think we should probably have a Mailman-specific glossary for many terms, including the tests we use for validation. In this case, FQDN appears to be "sequence of characters not containing '@' or '/'." Steve

4 years, 4 months

Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/14/23 2:09 AM, Alex Schuilenburg via Mailman-users wrote: > > I am migrating from mailman 3.2.1 & mailman3-web 0+20180916-8 on Debian Buster to mailman 3.3.8 & mailman3-web 0+20200530-2.1 on Debian bookworm, have mailman3 and mailman3-web configured (and running on bookworm) from the initial install. But when I use the mailman3-web 0+20180916-8 database (after stopping mailman3 and mailman3-web) on bookworm, unfortunately migrate fails: ... > But the migrate fails at the first operation: > # mailman-web migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > Applying contenttypes.0001_initial...Traceback (most recent call last): ... > MySQLdb._exceptions.OperationalError: (1050, "Table 'django_content_type' already exists") You are attempting to apply migrations that have already been applied. Apparently the django_migrations table is inconsistent with the state of the database. > Indeed the table django_content_type already exists on 0+20180916-8 . Apart from fields changes, there are an additional 4 tables in mailman3-web 0+20200530-2.1 > > I managed to import the mailman 3.2.1 database to the mailman 3.3.8 database, and all lists, subscriptions and settings looks fine. > > So how can I upgrade my existing mailman3-web database? This appears to be a Debian package issue. I suggest you ask Debian. -- 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

Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 01:22 PM, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> > >> 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. > > > As I said, for mail delivery you need to forward port 25 to the Mailman > server. > Ok so I'll redirect in my zentyal firewall the port 25 to my local centos7 with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

Re: Hyperkitty no longer archiving

by Hirayama, Pat

Steve wrote: >So we need to figure out >where HyperKitty is getting its setting for MAILMAN_ARCHIVER_FROM. > >1. Are there multiple copies of settings_local.py lying around? There only appears to be the one in /opt/mailman/mailman-suite/mailman-suite_project >2. Does settings.py have "from settings_local import *" in it? Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other related settings defined at the top of the settings.py file? Or should I update settings.py based on what is in settings_local.py? >3. Are there multiple copies of settings.py lying around? Well, there are these: ./usr/local/lib/python3.8/site-packages/rest_framework/settings.py ./usr/local/lib/python3.8/site-packages/postorius/doc/settings.py ./usr/local/lib/python3.8/site-packages/django_q/tests/settings.py ./usr/local/lib/python3.8/site-packages/django_extensions/settings.py ./usr/local/lib/python3.8/site-packages/mailmanclient/restobjects/settings.py ./usr/local/lib/python3.8/site-packages/example_project/settings.py Only the last has MAILMAN_ARCHIVER_FROM defined in it, but I was assuming from the example_project subdirectory name that this was just a sample file, and besides, "from settings_local import *" is also set in it. >4. What else may have changed in the migration? Any software > upgrades in mailman, hyperkitty, mailman-web (or wherever the > settings*.py are coming from)? So, I actually converted the instance to a template, copied and deployed to the new account. So, all the mailman, hyperkitty & nginx versions stayed the same. Thanks for any assistance. Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

3 years, 4 months

Re: mailqueue shows bounces for emails that are not on the mailing list

by Mark Sapiro

On 11/3/25 04:18, Stephen J. Turnbull wrote: > Paul via Mailman-users writes: > > > Iam getting alot of such from my mail server mail queue lately > > 4d08rT4xMHzMCD6S 2393 Mon Nov 3 01:43:21 > > list-bounces+makeupbymichelle=aol.com(a)lists.mydomain > > (host mx-aol.mail.gm0.yahoodns.net[67.195.228.84] said: > > 421 4.7.0 [TSS04] Messages from my-mail-server-IP temporarily > > deferred due to unexpected volume or user complaints - 4.16.55.1 > > If "my-mail-server-IP" is in fact your mail server's IP, then you may > have a problem: spammers may be using your server as a relay for > spoofed emails. It is also possible, or even likely that these are the result of bad actors maliciously requesting subscriptions for 3rd parties. Since this is a 421 status, these mails should remain queued in your mail server for a while and can be examined[1]. If this is the case, you may be able to mitigate this by setting SHOW_ANONYMOUS_SUBSCRIBE_FORM = False in your Django settings. See https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 [1] For example if your MTA is Postfix postcat /var/spool/deferred/4/4d08rT4xMHzMCD6S and if that shows a subscription or email verification request postsuper -d 4d08rT4xMHzMCD6S to delete it so it isn't retried. -- 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

Re: sending messages in response to posts from non-members

by Mark Sapiro

On 2/26/22 04:26, David Bremner wrote: > > I'd like to turn off the "bounce messages" sent by mailman to > non-members. My reasoning is that most such posts are spammers, and > often use forged return-paths / From's, so I end of sending steady > stream of backscatter to amazon.com etc... > > Is this configurable (without postorius) somehow? What exactly do you want? Do you want to discard without notice any nonmember posts or do you want to hold them but not send a notice of the hold to the poster? For the former, you want to set the list's default_nonmember_action to discard. For the latter you want to set the list's respond_to_post_requests to False. To make either of these settings the default for new lists, you'd need to patch mailman/styles/base.py. To set them for all lists you could do the following in `mailman shell` ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager).mailing_lists: ... # Pick the appropriate one of the following. ... mlist.default_nonmember_action = Action.discard ... mlist.respond_to_post_requests = False ... >>> commit() ``` -- 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

Re: Apache Conf

by Thomas G

Hi tried both. Same result. xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > Hi, > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > I tried to do the same with Apache, but the statics files are not > > delivered (404). > ... > > <VirtualHost *:80> > > ServerName mailing.ddd.fr > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > <Location /static/> > > Alias "/opt/mailman/static/" > > </Location> > > > > <Location /> > > ProxyPass http://localhost:8000/ > > ProxyPassReverse http://localhost:8000/ > > ProxyPreserveHost On > > </Location> > > </VirtualHost>/ > > > In Apache, location > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > appropriate for resources in the file system. > > Try > > Alias /static/ /opt/mailman/static/ > > not within a location block. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 5 months

Re: Problem with digests not being sent daily

by Mark

On 2024-06-23 00:51, Mark Sapiro wrote: >> Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> > > Probably because (in Postorius) Settings->Digest->Enable Digests is No Double checked that Enabled Digest s= Yes >> Then, as "mailman", I ran "mailman digests --periodic" manually and >> got the same error (as expected since there is nothing there) ... > This error should not occur if there is no digests.mmdf. It only does > occur because you have set Digest size threshold to 0 under the > assumption that 0 means unlimited which it doesn't. If you don't want > digests sent on size, you need to set Digest size threshold to a very > large number. > > I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid > throwing the exception, but setting the threshold to 0 is still wrong Oh? I was indeed assuming that 0 meant unlimited. The threshold was set at 0. My thinking was that meant the file size was not a factor in determining when the digest was sent and that the sending would be triggered by the daily cron. When I set the threshold very low - 10kB - it sends a digest on every post. So my understanding of what you are saying is: if the threshold is set very large, say 100,000 kB - then a digest will be be sent by the daily cron even if it is smaller than 100,000 kB. Am I understanding correctly?

1 year, 9 months

Mailman-users search results for query "Postorius"