Search results for "Postorius" - Mailman-users

Re: How to subscribe members without sending unsubscribe message

by Stephen J. Turnbull

Flo via Mailman-users writes: > Thank you. I don't why I don't find these things in Postorius > easily? There's a common saying among user interface developers that "'intuitive' just means 'what you're used to'". It's not a "you" problem, it's that people have different notions of where such things "should be found" based on their unique experiences. In this case, the "mass subscription" tool has controls for all the things you might care about, including the welcome message. The "mass removal" tool does not, but once you've used "mass subscription", a control for the goodbye message is a reasonable expectation. I think we should add it: https://gitlab.com/mailman/postorius/-/issues/638 -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month

Re: Introducing Mailman Web project

by Abhilash Raj

On Mon, Mar 25, 2019, at 5:25 PM, Ralph Seichter wrote: > * Abhilash Raj: > > > For this reason, I decided to combine all the projects together into > > a Django project which can be easily installed and run: > > > > $ pip install mailman-web > > # Export Settings for commands to just work. > > $ export DJANGO_SETTINGS=mailman_web.settings > > $ django-admin migrate > > $ django-admin runserver > > I've tried things a bit differently so I can use the latest version from > GitLab, and Things Go Boom(TM): > > $ python3.7 -m venv venv > $ . venv/bin/activate > $ pip install -U pip setuptools > $ git clone https://gitlab.com/mailman/mailman-web.git > $ cd mailman-web/ > $ cp docs/mailman-web-example.toml mailman-web.toml > $ pip install . > $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate > Traceback (most recent call last): > [...] > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/views/user.py", line 34, in <module> > from postorius.models import List, MailmanUser > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/models.py", line 223, in <module> > class EmailTemplate(models.Model): > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/django/db/models/base.py", line 95, in __new__ > "INSTALLED_APPS." % (module, name) > RuntimeError: Model class postorius.models.EmailTemplate doesn't > declare an explicit app_label > and isn't in an application in INSTALLED_APPS. > > Did I miss something? So, that's my fault ;-) The example configuration is actually not a working example, but only used for demonstrating how to write a TOML config. But I see that it actually should be a valid configuration, I'll open an issue and fix that. Can you instead remove mailman-web.toml and then again try: $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate This should mostly probably work :) -- thanks, Abhilash Raj (maxking)

6 years, 6 months

Re: lmtp runner not starting

by Odhiambo Washington

On Sat, Apr 1, 2023 at 7:55 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > This morning I upgraded the mailman3 installation of the less traffic > server I have: a bunch of lists, with very slow traffic. > > (see pip lists at the end) > > I sent test mails to a pair of lists, but none were distributed or > archived. postorius seemed working well. First I thought it was some I > did wrong in the upgrade procedure, but then I realized the lmtp runner > was not running. > > I followed old messages about similar problem (many of them in this same > mailman-users list), but I cannot see what is wrong. There is no error > logged in mailman.log. the mailman.cfg of the lmtp is the default (and > was working at least a pair of weeks ago) > > *-*-*-*-*-*-*-*-* from mailman.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: localhost > smtp_port: 25 > configuration: python:mailman.config.postfix > > *-*-*-*-*-*-*-*-* > > There is no one listening in port 8024. I tried changing the port (to > 9024), with the same results. > > postfix seems working well. I's just there is nothing listening on port > 8024 because lmtp runner is not running :) > > (from maillog): > > connect to 127.0.0.1[127.0.0.1]:8024: Connection refused > > (another simple test) > > root@www:/usr/local/mailman3 # telnet localhost 8024 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > > I'm running out of ideas. Any clue to somewhere to dig in? > > > *-*-*-*-*-*-*-*-*-*-* runners started > > Apr 01 17:24:40 2023 (4681) out runner started. > Apr 01 17:24:40 2023 (4680) virgin runner started. > Apr 01 17:24:41 2023 (4679) command runner started. > Apr 01 17:24:42 2023 (4688) retry runner started. > Apr 01 17:24:43 2023 (4686) in runner started. > Apr 01 17:24:44 2023 (4683) digest runner started. > Apr 01 17:24:44 2023 (4684) nntp runner started. > Apr 01 17:24:45 2023 (4682) archive runner started. > Apr 01 17:24:46 2023 (4685) bounces runner started. > Apr 01 17:24:47 2023 (4687) task runner started. > Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages > Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries > Apr 01 17:24:48 2023 (4678) pipeline runner started. > Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages > Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries > > *-*-*-*-*-*-*-*-*-* pip lists with versions installed > > root@www:/usr/local/mailman3 # pip list | grep mailman > django-mailman3 1.3.9 > mailman 3.3.8 > mailman-hyperkitty 1.2.1 > mailmanclient 3.3.5 > > root@www:/usr/local/mailman3 # pip list | grep django > django-allauth 0.51.0 > django-appconf 1.0.5 > django-compressor 4.0 > django-extensions 3.2.0 > django-gravatar2 1.4.4 > django-haystack 3.2.1 > django-mailman3 1.3.9 > django-picklefield 3.1 > django-q 1.3.9 > djangorestframework 3.13.1 > > root@www:/usr/local/mailman3 # pip list | grep postorius > postorius 1.3.8 > > Bumping either mailman|lmtp loglevel to DEBUG might help find out. [logging.lmtp] level: debug And I think you can debug everything with (untested): [logging.here] level: debug And restart mailman. Maybe?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > Then if collapse_alternatives is True (settable here or in Postorius), > any multipart/alternative parts will by replaced by the first, > presumably text/plain, sub-part. > > Finally, if convert_html_to_plaintext is True (settable here or in > Postorius), any remaining text/html parts will be converted to plain > text by lynx or whatever is configured as html_to_plain_text_command in > mailman.cfg. > This will ensure that filter_action is applied only to those messages > which have no text/plain or text/html parts. Great, that helped for the content. Thanks. Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. If that doesn't work, we have talked about deleting the list and add it from scratch. Is the any prolems (with left overs from the old imported list), when deleting the list from Postorius? /Henrik Rasmussen

6 years, 4 months

Re: Email discard

by Mark Sapiro

On 4/1/23 08:33, qro(a)xs4all.nl wrote: > Hi > > I have a good working mailman3 list server with 3 mailing lists. > 2 of them work OK, but 1 has a little odd behaiver > > If a non member send an email it will discard while the setting in /postorius/lists/list.name.nl/settings/message_acceptance shows Hold for moderation > > A snip from var/mailman3/mailman.log > Apr 01 10:48:32 2023 (49342) DISCARD: <4359976d-d4bb-9b30-0901-c842aa1fecb3(a)xs4all.nl>; ['The message is not from a list member'] > > Changing and saving a other choice makes no difference. > > Where can I look more to find a solution? (in mysql?) In Postorius, find the nonmember in the Users->Non-Members list. Does that nonmember have a moderation action of discard. Also, what's in Postorius->Settings->Message Acceptance->Discard these non-members? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Re: Hiding the "subscribe without creating an account"

by Mark Sapiro

On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: > > Is there a configuration option that does this, or was it a custom change made in > the templates? Was the change made to reduce fake registrations? Did it work? It was added in Postorius 1.3.9. See the UI section at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 Yes, the change was made in an attempt to reduce fake registrations. We haven't really studied it's effectiveness. It seems to help somewhat, but it also seems that bots may already have a template to POST so removing it from the UI is not a complete solution. There is also a lot of email to innocent third parties and non-existent addresses from attempts to register them for an account. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

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

by John Hein

Mark Sapiro wrote at 12:18 -0700 on May 12, 2016: > On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. > > > This format vs. plain text digests was a user option in Mailman 2. > > > > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. > > > The core still supports the same plain text and MIME format digests and > the same individual subscriber and per-list default formats as did > Mailman 2. The issue is none of these things are exposed in Postorius. > > If you subscribe to digests on this list, you will receive the > 'encapsulated' MIME format because the lists mime_is_default_digest > setting is True, but currently that has to be set through the > bin/mailman shell tool. > > > > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? Thanks for the info - and Barry's reply as well. I understand that MIME digests are supported in Mailman 3 - that's what I'm using (and thanks, Barry, for the info that Summary Digests is the same right now). My quibble is that the multipart/digest encapsulation level is gone. Barry Warsaw wrote at 15:16 -0400 on May 12, 2016: > 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) But mm 2 had: multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer) So was that removal intentional, a bug or ?? Maybe you're saying there is definitely an unexposed (in Postorius) knob for that in mm3. > > It is the intent that Postorius will eventually expose all these > settings. We're not there yet. At present you could possibly do this by > interacting with mailmanclient, although I'm not certain the settings > are exposed there. You can do it via bin/mailman shell if you have > access and know what you're doing (see > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) > > If you file an issue at > <https://gitlab.com/mailman/postorius/issues/new>, it might help > expedite this. Okay.

9 years, 5 months

Problem with redirection when entering alias without a / at the end

by Jens Günther

Hey there, I'm using Apache2 as the webserver, configured https://mailman.xyz.de as Web host. When I want to get to Mailman Starting Page now I need to Enter the following URL: https://mailman.xyz.de/mailman3/ to be directly redirected as expected to https://mailman.xyz.de/mailman3/postorius/lists/ -> works. Problem: When leave out the slash at the end and I ONLY enter the following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly redirected to a page, taht does not exist: https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Where can I change this misbehaviour? In Apache-conf everything seems as it'S in the docs, for the vHost I do not have any other custom settings. Thank you in advance. By the way: Is there an easy way to redirect directly from https://mailman.xyz.de to https://mailman.xyz.de/mailman3/postorius/lists/ -> what would be a possibility for that?

4 years, 7 months

Re: Another interesting error...

by Darren Smith

As for the traceback - I'm assuming it's from postorius, as this happens when attempting to load the held messages in the Postorius UI. On Mon, Apr 23, 2018 at 3:29 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > "It's in Mailman's database in the 'message' table." > > I can see the message table - is there a way to see where it is marked as > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > and path. > > I'm wanting to be able to query for held messages for a given mailing > list, as there are currently over 98,000 entries in the message table. > > -Darren > > > On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/23/2018 01:31 PM, Darren Smith wrote: >> > So it appears that there was a message sent to one of our mailing lists >> > that was put into the held message queue. However, when attempting to >> go to >> > the message to do the moderation, the web page returns and Error 500. >> > >> > Looking in the mailman log, I found this: >> > >> > Apr 23 14:21:02 2018 (17878) REST request handler error: >> > Traceback (most recent call last): >> > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line >> 137, >> > in run >> > self.result = application(self.environ, self.start_response) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> database/transac >> > tion.py", line 50, in wrapper >> > rtn = function(*args, **kws) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/wsgiapp.py" >> > , line 214, in __call__ >> > return super().__call__(environ, start_response) >> > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", >> > line 227 , in __call__ >> > responder(req, resp, **params) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 167, in on_get >> > resource = self._make_collection(request) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in _make_collection >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in <listcomp> >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 157, in _resource_as_dict >> > resource = self._make_resource(request.id) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 100, in _make_resource >> > make_header(decode_header(resource['subject']))) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, >> in >> > make_he ader >> > h.append(s, charset) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, >> in >> > append >> > s = s.decode(input_charset, errors) >> > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: >> > illegal multibyte sequence >> > >> > It LOOKS as if there might be a character in the email somewhere - >> possibly >> > in the subject or sender fields? - that is somehow unexpected. >> >> >> It appears that the Subject: header is RFC 2047 encoded and there is an >> encoded word with charset gb2312 that contains an invalid encoding. >> >> The message is apparently defective, but this kind of defect shouldn't >> cause a 500 error. >> >> I can't tell for sure from the traceback if this is Postorius or some >> other application accessing the REST api. Is it Postorius or something >> else? >> >> >> > I am attempting to find the held message - can someone point me where I >> can >> > go to see the message so that I can see what might be causing the >> problem? >> >> >> It's in Mailman's database in the 'message' table. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 5 months

localtime() cannot be applied to a naive datetime

by Freerk Bosscha

Since yesterday I get the following error-message when I go to the webinterface: ValueError at /admin/login/ localtime() cannot be applied to a naive datetime Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Exception Type: ValueError Exception Value: localtime() cannot be applied to a naive datetime Exception Location: /usr/lib/python3/dist-packages/django/utils/timezone.py in localtime, line 207 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: vr, 1 Mrt 2024 11:52:50 +0100 Mailman info: mailman info GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman3:xxxxxxx If this issue was posted before, i'm sorry, i haven't found it: Any ideas how to solve this issue would be appreciated Environment: Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Python Version: 3.9.2 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 145. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 143. response = response.render() File "/usr/lib/python3/dist-packages/django/template/response.py" in render 106. self.content = self.rendered_content File "/usr/lib/python3/dist-packages/django/template/response.py" in rendered_content 83. content = template.render(context, self._request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py" in render 61. return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 169. with context.bind_template(self): File "/usr/lib/python3.9/contextlib.py" in __enter__ 117. return next(self.gen) File "/usr/lib/python3/dist-packages/django/template/context.py" in bind_template 246. updates.update(processor(self.request)) File "/usr/lib/python3/dist-packages/postorius/context_processors.py" in postorius 38. mailman_day=(timezone.localtime(timezone.now()).day == MAILMAN_DAY), File "/usr/lib/python3/dist-packages/django/utils/timezone.py" in localtime 207. raise ValueError("localtime() cannot be applied to a naive datetime") Exception Type: ValueError at /admin/login/ Exception Value: localtime() cannot be applied to a naive datetime

1 year, 7 months

Mailman-users search results for query "Postorius"