Search results for "Postorius" - Mailman-users

Re: Disable user registration

by Mark Sapiro

On 3/20/21 6:22 AM, Stephen J. Turnbull wrote: > > One obvious approach is to add "^.$" to each list's ban list > (eventually that should be configurable as a list style, so "easy" to > make domainwide or sitewide), but that doesn't stop people from > creating users via Postorius. One way to address that would be to > clean out users with no subscriptions once a week or so. I think you mean "^.*$", but that won't work as being banned means you can't be added to the list by any means and you can't post. -- 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

Re: MM3 List Templates

by Odhiambo Washington

On Wed, Dec 21, 2022 at 1:50 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > I am reading > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > regarding templates and I am confused about > whether to treat the path /opt/mailman/mm/var/templates/*site*/en/ > literally or even if that information is still relevant. > I created the exact path and put those templates in there, but they do not > show up on Postorius. > Responding to myself and apologizing for the noise. I have read https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… as regards templates. There is still a lot to learn about MM3. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

Re: Question: as Admin, I disabled the self-registration via settings.py. What is the correct method to register a few new users now?

by Mark Sapiro

On 9/1/25 12:27, Wikinaut wrote: > > Question: is there a better method for admins to register a few new persons to Hyperkitty/Postorius so that they can act as owners and moderators of some of the lists? You can add Users and their email addresses via the Django admin web ui normally at a url like https://example.com/admin/ but see your top level urls.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

Re: Can't subscribe on new site/domain

by Jeremy Stanley

On 2025-10-09 23:39:11 +0200 (+0200), Flo via Mailman-users wrote: [...] > Is there a possibility to export all members including real names. > It doesn't work with Postorius, yet, is there another possibility? [...] It's all stored in a relational database, which you should be able to extract with a tool like mysqldump and then later source that same dump into a new empty database. You can find some information on database setup in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/datab… Some familiarity with backing up, restoring and manipulating databases is a big help for these sorts of tasks, otherwise it may have a fairly steep learning curve. -- Jeremy Stanley

7 months

Re: migration

by Dave McGuire

On 7/30/21 4:25 PM, Mark Sapiro wrote: >> I am not at all fluent in django interactions (I'm still not entirely >> sure of what django actually *is*) so I have some reading to do. Any >> pointers on "django wrangling for n00bs" would be great. As I >> mentioned, I've not been hacking on mm3, just using it. I'm an >> accomplished programmer, but embedded C and assembler are a few >> galaxies away from python and web services! > > > Django is a Python based web framework. It is the framework used to > support HyperKitty and Postorius. To learn more, start at > https://www.djangoproject.com/ I'll get to reading. Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 9 months

Re: migration

by Mark Sapiro

On 7/30/21 1:10 PM, Dave McGuire wrote: > > I am not at all fluent in django interactions (I'm still > not entirely sure of what django actually *is*) so I have some reading > to do. Any pointers on "django wrangling for n00bs" would be great. As > I mentioned, I've not been hacking on mm3, just using it. I'm an > accomplished programmer, but embedded C and assembler are a few galaxies > away from python and web services! Django is a Python based web framework. It is the framework used to support HyperKitty and Postorius. To learn more, start at https://www.djangoproject.com/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

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

11 months, 2 weeks

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, 10 months

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/ >

7 years, 1 month

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

4 years, 6 months

Mailman-users search results for query "Postorius"