Search results for "Postorius" - Mailman-users

Re: Mailman 3 installation from latest Debian packages

by Andreas Barth

* Brian Carpenter (brian_carpenter(a)emwd.com) [210212 19:05]: > On 2/12/21 7:49 AM, Matthew Blissett wrote: > >I found > >https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which > >is running the same version, but presumably not using these Debian > >packages as the Javascript is slightly different. > > > >Could this be a problem with the Debian packaging, or perhaps my > >configuration -- which is very close to the defaults (i.e. Mailman > >and Apache configuration generated by dpkg). > > > >Has anyone set up a working installation using these packages? > > The above reference URL is actually one of our clients running on > one of our Mailman 3 shared servers. Mailman 3/Postorius/Hyperkitty > were all installed using a virtual environment via pip. I don't use > packages at all for our Mailman 3 installations. Sorry I was too fast deleting the original mail, so replying here instead. I used the Debian packages as my original mailman configuration but migrated then to mailman based on git. Still using the configuration settings from the debian packages (e.g. content of mailman3-web.cfg). So yes, the debian packages worked fine for me with just the defaults. (However, I would strongly recommend to use postgres and not sqlite as the database, as sqlite is unfit for production, and migration is not really easily possible, but that's not related to Debian.) Regards, Andi

5 years

Fwd: Problems after Upgrade

by Jeff

Update on this. I fixed the problem logging in to the web interface by changing several instances of smart_text to smart_str. I also notice that I errored in my message below by saying the replaced text was “search_text”. It was actually “smart_text”. I believe my "site-packages/compressor” library was not updated correctly because I had to make many manual changes to get things to work. I still have the problem "mailman-web compress” listed below. However, I was able to login to the web interface and approve messages. > Begin forwarded message: > > From: Jeff <mm3(a)steele.com> > Subject: Problems after Upgrade > Date: October 30, 2022 at 3:24:21 PM EDT > To: mailman-users(a)mailman3.org > > Hello, > > I tried to upgrade to the latest mailman3 version using the following command: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web mailmanclient > > There didn’t appear to be any problems with this step and I’ve since run it again a few times and only see that the requirements have been satisfied. > > When first running the command: > > mailman-web migrate > > I received several errors dealing with search_text in the package compressor (at least that’s as best as I remember, I wasn’t taking notes). I fixed these manually by changing it to search_str. Eventually "mailman-web migrate” started working and has subsequently worked. > > When I run the command: > > mailman-web compress > > I get the following error: > > traceback (most recent call last): > File "bin/mailman-web", line 8, in <module> > sys.exit(main()) > File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 49, in load_command_class > return module.Command() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/base.py", line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > I have not been able to fix this and would appreciate any assistance. > > When I run the command: > > bin/mailman-web collectstatic > > It asks me yes or no continue and when I enter “yes” it displays the following which I assume means it worked: > > 372 static files copied to '/usr/local/mailman3/web/static', 38 unmodified > > > Starting mailman3 seems to work by the status message shows the following: > > systemctl status -l mailman3 > ... > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 259, in send_warnings_and_remove > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: self._send_warnings() > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 310, in _send_warnings > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: member.address, > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/member.py", line 121, in address > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return (self._user.preferred_address > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: AttributeError: 'NoneType' object has no attribute 'preferred_address' > lines 13-35/35 (END) > > I have been receiving admin requests to approve messages. But, I can’t approve them because of the following issue: > > Starting mailman-web seems to work as expected with no errors. However, when I try to login to the web interface, I get a HTML page with the following error: > > init__() got an unexpected keyword argument 'providing_args' > Request Method: GET > Request URL: http://lists.crestwood-dc.org/accounts/login/?next=/mailman3/lists/crestwoo… > Django Version: 4.1.2 > Exception Type: TypeError > Exception Value: > __init__() got an unexpected keyword argument 'providing_args' > Exception Location: /usr/local/mailman3/lib64/python3.8/site-packages/compressor/signals.py, line 4, in <module> > Raised during: allauth.account.views.LoginView > Python Executable: /usr/local/mailman3/bin/uwsgi > Python Version: 3.8.13 > > As a result, I cannot login and approve posts. > > I would greatly appreciate any assistance with these issue. > > Thanks much! >

3 years, 4 months

Re: Installing mailman 3

by Rafael Mora

Postfix is listening on 127.0.0.1:25 is it ok? or should listen on 0.0.0.0:25?? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' > > > This looks good to me. > > > What should I use in user and password?? Does Django use postfix to send > the email??? > > > I think you don't need a password and username as long as your postfix is > configured to relay local emails without authentication (which it is by > default if you installed from distro packages and if you haven't changed > the settings). > > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) > escribió: > > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > _______________________________________________ > > > Mailman-users mailing list > > > mailman-users(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > > > -- > thanks, > Abhilash Raj > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

Re: Templates

by Mark Sapiro

On 09/28/2017 01:56 PM, David Krantz wrote: > Hi again, > > I had the problem with getting two footers, i.e. two expansions of the > template. After some digging in the source code I found out that the > decorator made one expansion (without personalization) and that the > delivery handling made another (with personalization). So I hacked > pipelines/builtin.py with a new pipeline that excluded the decorate > step, recompiled and changed to that pipeline for my personalized > list. That worked. Nothing like a bit of shotgun debugging in > production. > > That solves my immediate problem. Is there a known and recommended way > of configuring personalized delivery so that you only get the > personalized footer? I have ideas, but I probably should share them > with the developer list instead. :-) This is clearly a bug and should be fixed. If you report this issue at <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. > Of course this very nice functionality is a bit buried. I activated it > using the interactive python shell, seems less risky than changing the > database directly. There are many core settings not (yet) exposed in Postorius. This is something we need to fix, but it takes time and resources. In the mean time, 'mailman shell' is probably the best way to set them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

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, 2 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.

4 years, 11 months

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, 3 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, 5 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, 3 months

Mailman-users search results for query "Postorius"