Search results for "Postorius" - Mailman-users

Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I have fixed the bug on forks of mailman-core, postorius and mailman-client. C Am 02.09.2017 um 14:36 schrieb Claus-Justus Heine via Mailman-users: > I think I found the bug; I have posted a comment to the issue mentioned > by Mark > > https://gitlab.com/mailman/postorius/issues/58 > > Regards > > Claus > > Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: >> Oh well. >> >> Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >>> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>>> >>>> Seemingly, at some point in the deep dungeons of the source code the >>>> "Acceptable aliases" Text-Box is not interpreted correctly. >>>> >>>> Specifically, at the start it contains the string >>>> >>>> [] >>> >>> >>> See <https://gitlab.com/mailman/postorius/issues/58>. >> >> there they talk about fancy "uni-code thinks" (email addresses?) where >> the task is to convert a new-line separated text-field into an array. Oops. >> >> Kind thanks anyway. >> >>> >>> In order to set things on this page, you need to clear the Acceptable >>> aliases box before submitting changes. You can't actually set Acceptable >>> aliases via Postorius until this is fixed. >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. >> >> Thanks >> >> Claus >> >> > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 9 months

Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/2/22 06:39, Michael Hazan wrote: > Hello, > > When creating a list via postorius, i can see 3 style appear (announce, discussion, private). Is it possible to either create a new style and add it to that list or modify one of those style ? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Also, coming from mailman2, you could directly set the members post moderation action when subscribing, now you can only do it via the user menu, is there a way to automate this in mm3 ? I don't understand what you mean here. In MM 2.1 a member had only one setting - moderated yes or no and if moderated there was a list setting for the moderation action. There was also a list setting for whether new members were moderated by default. How were you setting the new member's moderation when subscribing? You are correct that when subscribing a new member, the member gets the default action for members and different action has to be set in a separate operation. I don't think this is significantly different from MM 2.1. Also, can you describe what you mean by "automate this". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Mailman Core 3.3.1 release

by Abhilash Raj

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

5 years, 1 month

Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (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 > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (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 > SocialAccountConfig.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. This is from Django >=3.2 can be fixed by adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to your settings. This has been done in HyperKitty's example_project/settings.py for the not yet released 1.3.6 version. These warnings are only warnings, they aren't fatal. ... > Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows > the same warning listed before and some new errors: > > *-*-*-*-*-*-* > > Migrations for 'postorius': > /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py > > - Alter field name on emailtemplate > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 419, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 413, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 354, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 398, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 89, in wrapped > res = handle_func(*args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 190, in handle > self.write_migration_files(changes) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 228, in write_migration_files > with open(writer.path, "w", encoding='utf-8') as fh: > PermissionError: [Errno 13] Permission denied: > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > > > *-*-*-*-*-*-* > > The file > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > does not exist at all makemigrations is trying to create that migration and you don't have permission to create the file. I don't know why it's trying to do that. Postorius 1.3.6 has migrations through 0016_auto_20210810_2157.py and shouldn't need more. To you have modificationd to Postorius? > Despite the error, I did a 'su -m mailman3 -c "python3 manage.py > compress"' and the subsequent "django-admin compilemessages" in > > /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and > ../django_mailman3 > > And the log continues showing the same error when trying archive a new > message. > > ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. These messages come from some HyperKitty version between commit b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 -0700 and commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 2021 +0000 They do not come from HyperKitty 1.3.5 but from something later than 1.3.4 which makes be think your mailman-hyperkitty version is not 1.2.0 either. I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Re: Timeout error on anonymous subscribe

by Gerald Vogt

On 23.10.24 00:09, Mark Sapiro wrote: > How are you creating the template? If you are creating it via Postorius, Yes, via Postorius created using the url https://lists.example.org/mailman3/lists/community.lists.example.com/templa… > what is your setting for POSTORIUS_TEMPLATE_BASE_URL and what does the I did not set POSTORIUS_TEMPLATE_BASE_URL in settings.py. > entry in the template table in the database look like? in mailman.template: mailman=# select * from template where id = 6; 6|list:user:action:subscribe|community.lists.example.com|http://localhost:8… in mailmanweb.template: mailmanweb=# select * from postorius_emailtemplate where id = 6; 6|list:user:action:subscribe|test1234||2024-09-09 13:52:22.377792+02|2024-10-14 15:11:43.029873+02|list|community.lists.example.com > POSTORIUS_TEMPLATE_BASE_URL should be the same URL you use to access > Postorius up to but not including the `/postorius/` or `/mailman3/` > part. I.e, for this list whose info page is at https:// > lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/, the > setting is > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` For testing I have set POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' to the URL of our main domain, however, if I test an anonymous subscribe through the list info page I still get the timeout error ``` HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) ``` Logs still show the same behaviour: the request for the template comes into the server but is finished and logged after 5 seconds: 127.0.0.1 - - [23/Oct/2024:05:51:38 +0000] "GET /mailman3/api/templates/list/community.lists.example.com/list:user:action:subscribe HTTP/1.1" 200 8 "-" "python-requests/2.32.3" The tcpdump of the tcp conection also looks the same: the response is pushed with the termination of the connection. I can access http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… with curl and immediately get the response. So it still looks to me as if the response is stuck in the tcp buffers of the connection and not pushed immediately, but only once the requestor times out after 5 seconds and closes the connection. Thanks, Gerald

7 months, 3 weeks

problem with postorius initial setup

by John Covici

Hi. I am trying to setup postorius, but I have run into a problem. I am using the example project, except I am using postgresql instead of sqlite3. I ran python manage.py migrate which was successful. On running the development server I get: Exception in thread django-main-thread: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", line 20, in import_string return getattr(module, class_name) AttributeError: module 'postorius.middleware' has no attribute 'APICountingMiddleware' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/core/servers/basehttp.py", line 45, in get_internal_wsgi_application return import_string(app_path) File "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", line 17, in import_string module = import_module(module_path) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/home/covici/mailman_django/example_project/wsgi.py", line 17, in <module> application = get_wsgi_application() File "/usr/lib/python3.8/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application return WSGIHandler() File "/usr/lib/python3.8/site-packages/django/core/handlers/wsgi.py", line 127, in __init__ self.load_middleware() File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py", line 40, in load_middleware middleware = import_string(middleware_path) File "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", line 22, in import_string raise ImportError('Module "%s" does not define a "%s" attribute/class' % ( ImportError: Module "postorius.middleware" does not define a "APICountingMiddleware" attribute/class The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3.8/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3.8/site-packages/django/utils/autoreload.py", line 53, in wrapper fn(*args, **kwargs) File "/usr/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 138, in inner_run handler = self.get_handler(*args, **options) File "/usr/lib/python3.8/site-packages/django/contrib/staticfiles/management/commands/runserver.py", line 27, in get_handler handler = super().get_handler(*args, **options) File "/usr/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 65, in get_handler return get_internal_wsgi_application() File "/usr/lib/python3.8/site-packages/django/core/servers/basehttp.py", line 47, in get_internal_wsgi_application raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: WSGI application 'wsgi.application' could not be loaded; Error importing module. Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 2 months

Question after upgrade to mm 3.2.3 and latest postorius

by Stephen J. Turnbull

David Krantz writes: > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, I see elsewhere that this is mod_wsgi. I forget exactly what my story was, but I did recompile on Linux and it was straightforward. Of course there are a million reasons why you might not want to do that. I just wanted to take this chance to report that for 3.6 and 3.7 this was very straightforward, in case anybody else is thinking about doing it.

5 years, 10 months

Re: Set Postorius interface locale

by Duane Raymond

Thanks - here is where that got ne so far... I have set the modest goal of changing a string on the list subscription page from the form label "Your name (optional)" to "Your name (and organisation)" What I did was 1) I edited /opt/mailman/mm/settings.py and changed the LANGUAGE_CODE from 'en-us' to 'en-gb' (or should I do it at /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/dj/settings.py or another location?) 2) Then I switched user using "su mailman" and started the venv environment (using: source /opt/mailman/mm/venv/bin/activate) 3) I edit the po file at /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/locale/ and specifically I am testing it on editing en_GB/LC_MESSAGES/django.po - is this the correct location? 4) I run: mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py compilemessages - is this the correct one to run? After this, nothing changed on the list page yet. 5) After that I changed directory into "/opt/mailman/mm/static" and run python ./mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py collectstatic - but this produces an error about ROOT_STATIC not being set ...and I didn't want to fiddle too much in case I overwrote the current functioning site ;-) Is the collectstatic static necessary after running compilemessages? Am I using the right files to run it? Am I editing them in the right location? Cheers, Duane

4 years, 3 months

Re: Default values for lists in Mailman 3

by Mark Sapiro

On 9/19/24 05:46, Markus Grandpré wrote: > Dear list, > > I would like to activate the invitation setting for all lists as > default. In Mailman 2.1 I have done this in the file > </etc/mailman/mm_cfg.py>: > > > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > > > How can I do this in Mailman 3? There is a draft merge request at https://gitlab.com/mailman/postorius/-/merge_requests/930 which implements a framework for setting Postorius defaults and creates a setting to set the default for pre-verified on the mass subscription page. Once merged, this can easily be extended to provide a default for Invitation. In the mean time, you can only do this by patching src/postorius/forms/list_forms.py like ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): invitation = forms.BooleanField( label=_('Invitation'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' ``` > Can I also transfer other default values > like: > > ... > DEFAULT_SERVER_LANGUAGE = 'en' > DEFAULT_SEND_REMINDERS = 1 > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > DEFAULT_PRIVATE_ROSTER = 2 > DEFAULT_ARCHIVE = Off > DEFAULT_ARCHIVE_PRIVATE = 1 > ... > > from the very same configuration file to Mailman 3? Is there a > documentation of the default values for lists in Mailman 3? This is done by creating a list style with the desired defaults. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for documentation of styles and see https://gitlab.com/mailman/example-mailman-plugin for an example of creating a plugin in Mailman core to make a persistent style. There is no specific doc for the list settings. You need to look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for the various settings and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default… to see which default classes are applied for various styles. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 14:06, William Oliver wrote: > > So.. as an aside, it was a bit of a hassle to copy and paste all the > usernames from the "Users" list in Postorius to the "Mass subscribe." > The only way I could see to do it was copy and paste them one at a > time. Postorius Users -> Members view has a CSV Export button. That exports a CSV with all the member addresses. It's actually just a flat list as it only has one column. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Mailman-users search results for query "Postorius"