Search results for "Postorius" - Mailman-users

Re: Django: An error occurred while processing your request.

by Mark Sapiro

On 5/26/25 12:08 PM, Florian Sukup wrote: > > When I received emails from postorius, then it came from example.com > which is nonsense as I worked with the real lists. So I deleted > example.com. Set DEFAULT_FROM_EMAIL and SERVER_EMAIL appropriately in your Django settings. > When I call https://.../mailman3/admin or any of the lists, the result is: > Server error > An error occurred while processing your request. You need to set SITE_ID appropriately in your Django settings. See https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

Re: Mailman3 in dockers on EC2 - running out of memory and puking ev.ry.where.

by Danil Smirnov

Hi, I assume micro instance has been used for obvious reason to leverage AWS Free tier. Unfortunately it wouldn't work for Mailman 3 w. Hyperkitty because of large memory footprint of the applications. However, Postorius-only version works just fine on micro instance. I'm providing free AMIs for both cases with zero-configuration needed (but without SES integration) in AWS Marketplace, links could be found on page https://mailman3.com/aws/ Best regards, Danil Smirnov ср, 10 апр. 2019 г., 19:29 Abhilash Raj <maxking(a)asynchronous.in>: > On Tue, Apr 9, 2019, at 2:34 PM, roger.hislop(a)is.co.za wrote: > > Hi all -- really need some help. I'm tech literate, but definitely not > > a sysadmin or dev. > > > > I'm following the tutorial at "Olay's Farmland" at > > https://www.olay.xyz/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > > which seems to be a clone of the same content here > > https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > > The right place to get help regarding these guides would be the author of > the posts, which AFAIK, have no affiliation with Mailman Core Team. > > On a (very) quick glance, it seems fine. > > > Easy enough to get most of the way ... set up EC2 instance, configure > > SES and add DNS settings with DKIM etc. Set up Postfix, test it. All > > working groovy. > > > > I run through the how to all the way through setting up the containers > > and firing it up. This is where things start to get funky. > > > > Once the docker-compose is run, I run "curl > > http://172.19.199.3:8000/postorius/lists/" to test. First time it said > > it couldn't connect to database. So I nuked and restarted from scratch. > > Second time it said the same thing... was reading around the place and > > tried again, and then reran that curl and it worked -- gave me html > > from a page. But the VM started running slowly --taking forever to > > follow keypresses. > > > > Eventually became unresponsive. So I rebooted the machine via AWS > > console, and docker ps showed only the postgres db running. > > docker-compose ps shows > > Name Command State > > Ports > > > ------------------------------------------------------------------------------------------ > > docker-mailman_database_1 docker-entrypoint.sh postgres Up > > 5432/tcp > > mailman-core docker-entrypoint.sh maste ... Exit 255 > > 8001/tcp, 8024/tcp > > mailman-web docker-entrypoint.sh uwsgi ... Exit 255 > > 8000/tcp, 8080/tcp > > > > So rebuilt the container -- same thing. It looks and feels like its > > running out of memory. > > > > I used the compose file from > > > https://gist.githubusercontent.com/Yexiaoxing/833bfcc5d3e4e0c06a8b7f0bac7c4… > (with appropriate edits). > > > How much memory do yo have in your VM? Have you tried using a bigger VM? > > thanks > Abhilash > _______________________________________________ > 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, 5 months

Re: Run 'manage.py makemigrations' to make new migrations

by Abhilash Raj

On Wed, Jun 29, 2022, at 2:21 AM, christopher.claus(a)tgcamberg1848.de wrote: > Hello together, > > at startup of my docker-container with mailman 0.4.3 i got some > warnings to apply some data-model-migrations. I´m very unfamilar with > python and django and be not sure how to handle it. Are these warnings > from mailman and should i migrate the data-model (and how)? Or should > i ignore these message for keeping mailman in a safe state? This might have something to do with the newer Django versions being pulled in during the build. Given that they are warnings, I don't think they will affect data. But regardless, can you open an issue on Github to track this? We want to make sure that either we downgrade Django or make sure affected components are updated to properly support new versions of Django. I can take a look a bit later to see what's this new W402 check that was added. > > Best regards, > chrclaus > > > System check identified some issues: > > WARNINGS: > django_mailman3.MailDomain: (models.W042) Auto-created primary key > used when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a > subclass of AutoField, e.g. 'django.db.models.BigAutoField'. > django_mailman3.Profile: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a > subclass of AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Attachment: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Email: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Favorite: (models.W042) Auto-created primary key used when > not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.LastView: (models.W042) Auto-created primary key used when > not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.MailingList: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Profile: (models.W042) Auto-created primary key used when > not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Tag: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Tagging: (models.W042) Auto-created primary key used when > not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Thread: (models.W042) Auto-created primary key used when > not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Vote: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > postorius.EmailTemplate: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > PostoriusConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > No migrations to apply. > Your models in app(s): 'postorius' have changes that are not yet > reflected in a migration, and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then > re-run 'manage.py migrate' to apply them. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

3 years, 2 months

Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/14/21 7:51 PM, Shawn Heisey wrote: > I'm having a lot of trouble with trying to set up mailman3 on my mail > server. > > It's on an AWS instance, running Ubuntu 20.04 LTS. All software is > installed from Ubuntu packages. Mailman version is 3.2.2. Please see <https://wiki.list.org/x/12812344>[1] > The problem I am trying to troubleshoot first is how this can be happening: > > Oct 14 11:27:26 2021 (2341) ACCEPT: > <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> > Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on > port 25 > > From the shell, I can "telnet localhost 25" successfully, even as the > "list" user. Apparmor is disabled. The UFW firewall is enabled, which > allows all traffic on the loopback interface. I disabled ipv6 at the > kernel level, but had the same problem with ipv6 enabled, so I don't > think ipv6 is related at all. I do not see any connections in the > postfix log that correspond to the mailman connection error. There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed. > From a fresh install of mailman, I created two mailing lists. Once upon > a time I had those lists active on a Debian 6 machine running mailman > 2.1.13 ... I copied the mailing list config from that machine over and > used the "import21" facility to import the configuration into the new > mailman3 install. That worked without error and I can see the lists and > their members with the "mailman" command. I found instructions for > integration with postfix, and added the required three config lines to > the postfix config. > > When I try to send a message to the list, I get what I pasted above in > the mailman log. I think that means the postfix integration is working, > and is forwarding to mailman. Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table. > I'm hoping somebody can give me some pointers, and if more information > is needed for troubleshooting, let me know what is needed. If your web UI isn't working, you probably haven't created any templates in Postorius, but import21 will create templates and if you ran import21 as root, you may have created templates and perhaps other things that can't be accessed by the Mailman user (`list` in your case). All Mailman related commands should be run only by the Mailman user. [1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <https://docs.mailman3.org/en/latest/install/virtualenv.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

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

by Barry Warsaw

On May 12, 2016, at 04:16 PM, deu8yz2mpq(a)snkmail.com wrote: >[1] Mime Digests & Summary Digests - I didn't see any difference for those >two options. There currently is no different between MIME and summary digests. We talked a long while ago about summary digests, but they've never been implemented. However, MM3 does implement RFC 1153 (i.e. "plaintext") and MIME digests and it should be possible to select your choice on your membership record, although I don't know whether this is plumbed through to Postorius. The MIME format of MIME digests should roughly be: multipart/mixed text/plain (the digest heading) text/plain (the TOC) message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer) Cheers, -Barry

9 years, 4 months

Re: Any known limit of number of lists that one can be owner/member of?

by Alan So

It can now display 66 lists but the total should be 70 after cross checking with colleagues. Besides a few lists are missing, there are also a few lists are listed that the user is not the owner. However, by browsing to the lists directly, the list of owners was correctly migrated. If I query the mysql table member using the address_id and role=1, the same 66 lists are displayed. If I query using role=2, it displays the 70 lists correctly. The user also subscribe to the lists she owned. Therefore, beside the view limit of 50 in Postorius, there is also an issue of data integrity after the migration.

6 years, 4 months

Re: Debian Package Install - Ownership and Permissions

by Mark Sapiro

On 4/7/23 09:14, Dave Hall via Mailman-users wrote: > > I'm seeing an interplay between 'list' (the existing Mailman2 user), > www-data (the Apache user) and root. Given that it seems like almost > everything that's part of mailman3-web/django/hyperkitty is running in > uwsgi, should I maybe change /etc/mailman3/uwsgi.ini to use 'list' as the > uid/gid rather than www-data and then also change any user/group permission > to 'list' as well? With the Debian packages, all Mailman processes including Django, HyperKitty, Postorius, etc. should run as user `list`. -- 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

Setup Mailman 3 using Apache/Mod_WSGI

by Erin Justice

Hi all, I'm trying to setup Mailman 3 to run using apache. I've downloaded and installed mailman core, django, Postorius & Hyperkitty I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However I've been unsuccessful in getting the site to run via apache w/ Mod_WSGI. Note: I have a number of virtual hosts setup for various PHP sites and am trying to add the mailman install as another virtual host. I'm using MAMP for managing my website setup on my local machine. The addition to the virtual hosts file is: <VirtualHost *:80> #Mailman3 stuff ServerName mailman.local Alias /static /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static"> Order deny,allow Allow from all </Directory> WSGIScriptAlias / /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project"> <Files wsgi.py> Order deny,allow Allow from all </Files> </Directory> </VirtualHost> I also have the following in my https.conf. WSGIPythonPath /Applications/MAMP/Library/lib/python2.7/ The 500 and related Errors I'm getting in Apache are: [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Create interpreter 'mailman.local|'. [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Adding '/Applications/MAMP/Library/lib/python2.7/' to path. [Thu Aug 03 14:18:55 2017] [info] [client ::1] mod_wsgi (pid=80044, process='', application='mailman.local|'): Loading WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Target WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py' cannot be loaded as Python module. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Exception occurred processing WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] Traceback (most recent call last): [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py", line 38, in <module> [Thu Aug 03 14:18:55 2017] [error] [client ::1] application = get_wsgi_application() [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application [Thu Aug 03 14:18:55 2017] [error] [client ::1] django.setup(set_prefix=False) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/__init__.py", line 22, in setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 56, in __getattr__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._setup(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._wrapped = Settings(settings_module) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 110, in __init__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod = importlib.import_module(self.SETTINGS_MODULE) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/importlib/__init__.py", line 37, in import_module [Thu Aug 03 14:18:55 2017] [error] [client ::1] __import__(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] ImportError: No module named settings Any thoughts would be greatly appreciated. Thank you, -Erin Justice

8 years, 1 month

Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 3:06 PM, William Oliver wrote: > > When running mailman3, do I need to set up a completely different > virtual domain for it to run in? No. > My "real" domain name is > libertyfp.org, and I'm trying to make mailman work on that domain, e.g. > "testlist(a)libertyfp.org." I'm starting to get the idea that I need to > stick a completely different domain in there for the mailinglist. No. However, in Postfix, libertyfp.org is a virtual_mailbox_domain so you have to use an alias domain in Mailman. An alias domain is not a real domain. It is only known to Mailman and Postfix. It is not exposed in DNS or anywhere outside your server. Have you actually set an alias domain in Postorius for the libertyfp.org domain. It doesn't matter what name it is as long as it isn't a real domain. A good choice is x.libertyfp.org. Have you set that or something similar? If you do and run `mailman aliases` you should get things like testlist(a)libertyfp.org testlist(a)x.libertyfp.org testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org ... in postfix_vmap and things like testlist(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 ... in postfix_lmtp > Which I can do -- I've got another two or three domain names to play > with. Is it a problem to run the mailinglist on the same domain that > the machine sits on for its regular business? A lot of the errors I'm > getting seem to be from trying to do regular mail *and* the mailinglist > on the same domain. > > Now that I've installed all this stuff a couple of times, I can easily > re-install for a second virtual domain, if that's what I should be > doing. > > But, on to what's not working now... > > Unfortunately, I seem to have completely screwed the pooch on getting > postfix/dovecot to play nicely with respect to *receiving* mail. > > First, adding "virtual_alias_domains" (and putting libertyfp.org in it) > and commenting out "virtual_mailbox_domains" resulted in postfix > ignoring all my virtual mailboxes. Don't do that. Leave libertyfp.org as a virtual_mailbox_domain and don't set it as a virtual_alias_domain. I think that should work., but you may need to add hash:hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_mailbox_maps instead of virtual_alias_maps. ... > # mailman3 changes > > owner_request_special = no > always_add_missing_headers = yes > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp You shouldn't need to add hash:/opt/mailman/mm/var/data/postfix_lmtp to local_recipient_maps, but it probably doesn't hurt. > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > default_destination_recipient_limit = 30 > default_destination_concurrency_limit = 15 > virtual_alias_domains = hash:/etc/postfix/domains You don't want virtual_alias_domains. > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > #hash:/etc/postfix/virtual Everything you've posted so far says you haven't set an alias domain in Mailman for the libertyfp.org domain. Please be sure you have. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: Is logging.subscribe working in /etc/mailman.cfg?

by Alan So

I just tested it and observe that, 1) If the member send the request to list-leave(a)example.com, the user can confirm and the request is then moderated. The held request is also logged as expected and a notification is also sent to the owner or moderator. However, the owner cannot fulfill his/her request like those under "Subscription requests" in Postorius. The owner have to remove the address manually as a workaround. 2) If the member unsubscribe through the web interface after logging into the system, the unsubscription request is processed immediately. Nothing is logged in subscribe.log. However, subscription requests are held and logged as expected if the policy is set to confirm then moderate though there is no need to confirm.

6 years, 6 months

Mailman-users search results for query "Postorius"