Search results for "Postorius" - Mailman-users

Re: confirm-email: error NoReverseMatc

by Simon Hanna

On 01/31/2018 11:59 AM, Peter Münster wrote: > On Wed, Jan 31 2018, Simon Hanna wrote: > >> It's complaining about an empty url used for reversing. Do you mind sharing >> your settings.py file? we don't need the secret key and logins for stuff, so >> you can mask those. the rest should be ok to make public. > Ok, here are the settings (mainly from mailman-suite): > > SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' > LOGIN_URL = 'account_login' > LOGIN_REDIRECT_URL = '' > LOGOUT_URL = 'account_logout' I guess that's the issue. Try using something else for LOGIN_REDIRECT_URL It should either be a valid path so "/postorius/" for instance or a valid view name like "list_index"

8 years, 9 months

Re: How to subscribe members without sending unsubscribe message

by Mark Sapiro

On 9/15/25 14:11, Flo via Mailman-users wrote: > Hi, > > I need to remove subscribed members without sending them an > unsubscription message. Despite of my research I haven't figured out how > to do this using the GUI. With Postorius, you can do it by first setting the list's Automatic Responses -> Send goodbye message to No, and then doing the unsubscribe. From the command line, you can use the `mailman delmembers` command which has options to control the sending of the admin notice and the goodbye message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Re: Subscription requires confirmation when list is set as Open

by Joachim Schrod

Mark writes: > > > On 2024-12-19 02:22, Joachim Schrod wrote: > > > Is there a > > configuration option for a mailing list that sets "Pre Verified" to > > true as a default? > > Hi, > > Editing the list_forms.py file will set the "Pre Verified" checkbox > default to "checked" ... > > /opt/mailman/venv/lib/python3.11/site-packages/postorius/forms/list_forms.py > > ... changing initial=False to initial=True - onLine 1267 > > > pre_verified = forms.BooleanField( > label=_('Pre Verified'), > initial=True, > ... > > And then restart of mailman3 and mailmanweb after editing. Works like a charm, thanks a lot! Happy holidays, Joachim

1 year, 10 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)

4 years, 4 months

Re: Mailman core: basic internationalization howto?

by Mark Sapiro

On 10/06/2017 07:34 AM, thor.rustad(a)gmail.com wrote: > I made it work, sort of, after creating the directory structure templates/site/no and put the templates inside the 'no' folder. However, I can't make it work without setting the language manually for each list first. New lists are created with English as their language, breaking the creation of welcome mail. Also, I can not add members to the lists from Postorius. I want all new lists to use utf-8 without having to use mailman shell. How can it be done? Put [mailman] default_language: no in your mailman config. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

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

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

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

1 year, 1 month

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

1 year

Mailman-users search results for query "Postorius"