Search results for "Postorius" - Mailman-users

Time Zone Issue in Postorius

by Andy Summers

Hello, I'm encountering an error that sounds similar to this previous thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I've tried setting my TIME_ZONE to 'UTC' in my settings.py and settings_local.py files (and restarting Mailman), but when I check the datetime for a held message in Postorius, the datetime seems to be pushed +8 hours unexpectedly. My Postorius account time zone is set to "US/Pacific". As a workaround, I might be able to find a "wrong" time zone that would possibly reduce the unintentional additional hours difference and show the "correct" time zone in Postorius for the "Held Messages" page, but I don't think this is the right way to fix the issue. I think I've tried setting the TIME_ZONE setting to "America/Los_Angeles" in my settings.py file in place of 'UTC' in the past, but the result was still different than expected. Does anyone know if there are other places besides the mailman settings.py and settings_local.py files where something needs to be set so that I don't get an unintentional extra +8 hours of time difference when looking at messages on the "Held Messages" page of a mailing list? Thank you, Andrew

3 years, 8 months

Re: Mailman notify generating emails for request that aren't visible.

by Mark Sapiro

On 10/31/21 10:42 PM, Simon Coggins wrote: > Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: > > https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 > > But it’s not in 1.3.5: > > https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 Yes, I was mistaken. That code was merged on 14 Feb 2021 and is not in Postorius 1.3.4 which was released on 2 Feb. It should have been in 1.3.5 and I don't know why it is not at https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49, but that is moot in any case. > Thats ok, I’m going to 1.3.6 in a few days so that should solve my issue. OK -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: Owner's or Moderator's Lists

by Mark Sapiro

On 7/31/20 11:09 AM, Johnny Cison wrote: > > It's 1.1.2, which is the python3-django-postorius version included with the > package manager on Ubuntu 18.04. > > Is there by chance a mechanism for viewing that information in 1.1.2? You have several choices. 1) Do nothing and wait for Debian/Ubuntu to upgrade the package and backport it. 2) Try upgrading Postorius from source or with pip. This will probably result in disaster, and even if it doesn't, will probably also require upgrading django-mailman3, mailmanclient and mailman core to support new features in Postorius. 3) See the merge requests at <https://gitlab.com/mailman/postorius/-/merge_requests/349>, and if you have >50 lists, <https://gitlab.com/mailman/postorius/-/merge_requests/437> and try patching installing those changes as patches. Note that!349 patches 15 files, but one of them is the change log and 12 are related to tests. The only ones you need to patch are postorius/templates/postorius/index.html and postorius/views/list.py. Likewise, these two are all you need from !437. 4) Abandon the Debian/Ubunto package and install the whole suite from source or with pip. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi, After upgrading my PostgreSQL from 9.2 to 9.6, I was able to up postorius container. But when I try to open UI, I'm getting 500 Internal Server Error all the time - either for /postorius/lists/ as well as for /admin/. I've checked all the logs but haven't found anything there which can bring some light at the issue. Just error 500... I've checked: - nginx logs: just error 500 - mailman-web docker container logs: no errors - mailman-web (postorius) logs: mailmanweb.log is empty, uwsgi*.log with some errors - mailman-core logs: no errors I've also called curl localhost:8000 from inside the mailman-web container and got the same 500 Internal Server Error. Could you guys advise what else should I check? With my best regards, Danil пт, 22 февр. 2019 г. в 09:12, Danil Smirnov <danil(a)smirnov.la>: > Hi Abhilash, > > Thank you for the quick resolution, but I'm still unable t start the > container: > https://github.com/maxking/docker-mailman/issues/309 > > DB migrations are failing. > > Danil > > вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: > >> Hi Abhilash, >> >> Thank you for the explanation, I've created a report: >> https://github.com/maxking/docker-mailman/issues/307 >> >> Danil >> >> >> >> сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: >> >>> On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: >>> > Hi, >>> > >>> > I'm interesting in Mailman3 deployment with archiving feature >>> completely >>> > disabled. >>> > >>> > I've tried to deploy Core + Postorius using this docker-compose >>> > template: >>> > >>> https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… >>> > >>> > Unfortunately Postorius version came with this template is quite >>> outdated: >>> > 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker >>> image I >>> > see version 1.2.3. >>> > >>> > I've also checked image maxking/postorius:rolling but it seems >>> > irrelevant/broken (container exits with error). >>> > >>> > Are there newer Postorius docker image I can use? >>> >>> No, but if you could report the failure and error that you, maybe the >>> Maintainer can help >>> fix that issue you have? >>> >>> P.S. I maintain those images. The Postorius image is kind of neglected >>> since there are >>> fewer people using it, but I'd be happy to fix any error that you see. >>> >>> Package ugprades are merely a version number bump in Dockerfile :) >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>

6 years, 8 months

Re: mailman3 postorius cannot retrieve template

by Mark Sapiro

On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to a > suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because django > is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 (175334) > Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is impossible to > configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command which > includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- 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

Re: Postorius performance with over 1000 pending users

by Nick W

On 06/08/19 at 12:13, Nick W <mail(a)nickwynja.com> wrote: > Could it be that these requests are being submitted through Postorius? I'd > assume there would be some sort of honeypot input to prevent abuse. I'll > continue investigating and follow up with any insight I can on the cause of The > Problem. Some follow up here: cat /var/log/nginx/access.log | grep "POST /postorius/lists/mylist.exmple.com/" shows only a recent manual attempt I made to subscribe but not much else, which leads me to believe these requests aren't coming through Postorius. Now the more embarrassing part. The likely culprit is my stupidity. In an attempt to have subscription forms embedded on my static websites, I created this flask app to handle POSTs and subscribe people the the specified lists. https://github.com/nickwynja/fmmss/ I included a menial honeypot feature to handle spam requests, which I thought was working. It must not be but it appeared like it was, likely because I made the honeypot for my app at the same time I changed the subscription policy to 'confirm' and upgraded from Postorius 1.2.3 (when pending user subscriptions were no longer shown). Seems like I have some homework to do to prevent spam subscriptions through my app.

6 years, 4 months

long time user of mailman 2, new to docker-mailman and docker

by pjbondi＠systemdatabase.com

Hello to all: I'm getting this stack trace with the following redacted settings. # ALLOWED_HOSTS * # DEBUG True # HYPERKITTY_API_KEY llllllllllllllllllllllllllllllllllllllllllllllllll # MAILMAN_ADMIN_EMAIL xxxxxxx(a)yyyyyyyyyyyyyy.com # MAILMAN_HOSTNAME mailman-web # MM_HOSTNAME yyyyyyyyyyyyyy.ca # MTA postfix # SECRET_KEY kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk # SERVE_FROM_DOMAIN yyyyyyyyyyyyyy.ca # SMTP_HOST smtp-relay.sendinblue.com # SMTP_HOST_PASSWORD pppppppppppppppp # SMTP_HOST_USER xxxxxxx(a)yyyyyyyyyyyyyy.com # SMTP_PORT 587 # SMTP_USE_TLS True # [very long startup snipped] Applying postorius.0001_initial... OK Applying postorius.0002_auto_20160210_0721... OK Applying postorius.0003_drop_addressconfirmationprofile... OK Applying postorius.0004_create_email_template... OK Applying postorius.0005_auto_20180707_1107... OK Applying postorius.0006_auto_20180711_1359... OK Applying postorius.0007_auto_20180712_0536... OK Applying postorius.0008_auto_20190310_0717... OK Applying postorius.0009_auto_20190508_1604... OK Applying postorius.0010_auto_20190821_0621... OK Applying postorius.0011_auto_20191109_1219... OK Applying postorius.0012_auto_20200420_2136... OK Applying postorius.0013_auto_20201116_0058... OK Applying sessions.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Setting systemdatabase.ca as the default domain ... Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: no such table: django_site The above exception was the direct cause of the following exception: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3.8/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3.8/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/usr/lib/python3.8/site-packages/django/core/management/commands/shell.py", line 86, in handle exec(options['command']) File "<string>", line 1, in <module> File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 741, in update rows = query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: no such table: django_site

2 years, 9 months

Re: customized welcome message

by Mark Sapiro

On 12/7/23 12:46, Nils wrote: > I didn't try to include html. > It completely ignored the template I've created and sent the html source > of the parent domain. Which seems totally random to me. How and to what did you set the URL for the template? What does the database query SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; show? >> I see no URI setting in Postorius Settings > Automatic Responses. What >> Postorius version is this? Any local mods? > It's Postorius Version 1.2.4 installed through the mailman3-web package > for ubuntu focal (https://packages.ubuntu.com/focal/mailman3-web) This is very old. Current Postorius is 1.3.10. 1.2.4 is from February 2019. The Debian/Ubuntu packages are out of date. We recommend installing via the doc at 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

1 year, 10 months

Re: New messages not being archived

by Sarah H

I have, it just ends up printing out the pages html in the error message after: </html> Jul 14 10:52:31 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Organic BC</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> <link rel="stylesheet" href="/static/postorius/libs/fonts/font-awesome/css/font-awesome.min.css" type="text/css" media="all" />    </head> <body> <nav class="navbar navbar-expand-md navbar-light bg-light navbar-default"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggler collapsed" data-toggle="collapse" data-target="#header-nav" aria-expanded="false"> <span class="sr-only">Toggle navigation</span> <span class="fa fa-bars"></span> </button> <a class="navbar-brand" href="/mailman3/lists/"><span><img src="/static/postorius/img/mailman_logo_small_trans.png" alt="Mailman logo"/> Postorius</span></a> </div> <div class="collapse navbar-collapse" id="header-nav"> <ul class="nav navbar-nav mr-auto"> <li class="nav-item"><a href="/mailman3/lists/" class="nav-link"> <span class="fa fa-envelope"></span> Lists </a></li> <li class="nav-item"><a href="/archives/" class="nav-link"> <span class="fa fa-comment"></span> Archives </a></li> </ul> <ul class="nav navbar-nav navbar-right"> <li class="nav-item"><a class="nav-link" href="/accounts/login/?next=/hyperkitty/api/mailman/archive"> <span class="fa fa-sign-in"></span> Login </a></li> <li class="nav-item"><a class="nav-link" href="/accounts/signup/?next=/hyperkitty/api/mailman/archive"> <span class="fa fa-user-plus"></span> Sign Up </a></li> </ul> </div> </div> </nav> <div class="container" role="main"> <h1>Page not found</h1> <div class="alert alert-danger">This page either doesn't exist, or it moved somewhere else.</div> </div> <footer class="footer"> <div class="container"> <p class="text-center"> <a href="https://postorius.readthedocs.org">Postorius Documentation</a> • <a href="http://list.org">GNU Mailman</a> • Postorius Version 1.3.4 </p> </div> </footer> <script src="/static/postorius/libs/jquery/jquery-1.11.3.min.js"></script> <script src="/static/postorius/libs/popperjs/popper-v1.11.0.min.js"></script> <script src="/static/postorius/libs/bootstrap/js/bootstrap.min.js"></script> <script src="/static/django-mailman3/js/main.js"></script> <script src="/static/postorius/js/script.js"></script> </body> </html>

4 years, 3 months

Re: Changes in Django admin interface are not syncing to postorius gui /database

by ulf.rapphahn＠offis.de

Mark Sapiro wrote: > Lists, not Mailman lists. When you create a list in Postorius or Mailman > core, this is a Mailman list. A corresponding HyperKitty list will also > be created if hyperkitty is one of the active archivers for the list so > you see it in Django. > When you create a list in Django, it is only a HyperKitty list and will > be visible in HyperKitty, but no Mailman list is created so the list is > not in Mailman/Postorius. Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

11 months, 3 weeks

Mailman-users search results for query "Postorius"