Search results for "Postorius" - Mailman-users

Domain ownership issues

by peter＠chubb.wattle.id.au

Hi, I wanted to give another user the ability to create lists, so added that user as 'owner' of the domain. But he does not see the 'create list' button. I decided to try deleting him as owner, and the result is a python exception: KeyError: 'file' ERROR 2021-03-01 20:35:07,195 550 django.request Internal Server Error: /postori us/domains/sel4.systems/owners/b55d58c434c94f6dbd19ae338502dd2e/remove Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40 , in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/auth/decorators.py", line 75, i n wrapper return fn(*args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/domain.py", line 182, in remove_owners remove_email = client.get_user(user_id).addresses[0].email File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 324, in get_user display_name=display_name)) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 111, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: 404 Not Found Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.9.0+ (default, Oct 19 2020, 09:51:18) [GCC 10.2.0] Peter C

5 years

Upgrading mailman 3 venv installation

by Morris Jones

Congratulations on the new release for Mailman 3 Core! I'm not a daily pip/python user, so I'm probably behind on the safe and proper way to update my installation (which is working pretty well). In my virtual environment, I ran `pip list -o` and got a significant list. I noticed that all of the mailman packages seemed to be "Type sdist" and the framework packages "Type wheel". (Dunno what "Type" means in this context.) So I tried `pip list -o | grep sdist` and got a smaller list: (venv) mailman@mail:~$ pip list -o | grep sdist atpublic 2.1.1 2.3 sdist django-allauth 0.43.0 0.45.0 sdist django-mailman3 1.3.4 1.3.7 sdist flufl.i18n 3.1.3 3.2 sdist flufl.lock 5.0.3 6.0 sdist HyperKitty 1.3.3 1.3.4 sdist lazr.config 2.2.2 2.2.3 sdist mailman 3.3.2 3.3.5 sdist mailmanclient 3.3.1 3.3.3 sdist mysqlclient 2.0.1 2.0.3 sdist postorius 1.3.3 1.3.6 sdist Is this a reasonable list of the packages that I should update? Are there framework updates I should be concerned with? I'm remembering that a specific non-current version of django was required for mailman. The one I have installed is 3.0.11, with 3.2.7 listed as Latest. My plan is to archive the virtualenv directory, upgrade the packages listed above. If something breaks, I should be able to restore the archived virtualenv. I'm running a single server, Ubuntu 18.04.6, with Zimbra running alongside. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 5 months

Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 01:19, Odhiambo Washington wrote: > > Apart from all the defaults in settings.py (derived from gitlab), I also > > have this line: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > > Before the New Year releases of MM3, I used to get errors written to this > > file. > > Not anymore after I updated to the New Year releases. > > Another thing that I have realized is that prior to the New Year > releases, > > I would get an error logged to that file and also mailed to me. > > I don't think that I have changed anything in settings,py related to > > logging. > > > Nothing in those releases per se would affect this. This is Django and > django-allauth. Perhaps when you updated the Mailman packages, you also > updated these dependencies. > Which dependencies would those be? When I upgraded, the command I ran was: pip install --upgrade --force mailman mailmanclient postorius hyperkitty mailman-hyperkitty django-mailman3 And how do I find out what is suppressing the logging for the social accounts? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

Re: Importing config and archives only partially succeeded?

by Eric Broens

The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 2 months

Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/2/23 03:54, Onyeibo Oku wrote: > > I pulled the plugs on uwsgi and installed Gunicorn. Gunicorn gave more > mileage but something is still not right. When I visit the mailmanweb > home with a browser, I see the following: > > "Server Error. An error occurred while processing your request." > > Mailmanweb and mailman3 services are running. I perused the log file > at /opt/mailman/web/logs/mailmanweb.log and found the following: > > > raise MailmanConnectionError( > mailmanclient.restbase.connection.MailmanConnectionError: ('Could not > connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', > port=8001): Max retries exceeded with url: > /3.1/lists?advertised=true&count=0&page=1 (Caused by > NewConnectionError(\'<urllib3.connection.HTTPConnection object at > 0x7f7f4b128c40>: Failed to establish a new connection: [Errno 111] > 0x7f7f4b128c40>Connection refused\'))"))') Postorius is unable to connect to Mailman core's REST API. Are your settings for accessing Mailman's REST API correct? E.g., does MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' match $ mailman info ... REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Note the 3.1/ in REST root url is not included in MAILMAN_REST_API_URL. What do you get from, e.g. curl -urestadmin:restpass http://localhost:8001/3.1/lists It should return JSON with information about your lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Circumstances in which a subscriber is added to Pending Confirmation list

by David Owen

Hi I wondered if anybody would be able to assist me in my understanding of the Pending Confirmation list, please. In our Mailman mailing list, our Member Policy settings for both Subscription Policy and Un-subscription Policy are set to Open. Therefore we don't require subscribers to confirm their subscription after they submit a request to join our mailing list. Despite this, a number of subscribers seem to be arriving in the Pending Confirmation (Subscriptions pending user confirmation) list. Others correctly arrive in the Members list, as we would expect. All subscription requests are made by the subscriber sending an email to our "join" email address with the subject "subscribe". I've looked at the settings carefully and can't seem to see any that may cause the above behaviour at any time (although I may have missed something of course). Therefore, does anybody know the circumstances in which subscribers to an open mailing list may somehow arrive in the Pending Confirmation list? If I could understand the cause(s) I could then consider ways to manage it or prevent it from happening. Our Mailman installation is hosted centrally in a large organisation so we while we can alter our mailing list's settings in Postorious, we can't alter the source code or similar, so we don't have great room for manoeuvre. Our Postorius version is 1.3.6. Thanks and regards David

1 year, 9 months

Re: redirecting -bounces replies

by Mark Sapiro

On 6/25/25 10:53, Hirayama, Pat wrote: > Thanks, Mark. > > I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. > > The current postfix_vmap has entries like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 This looks very strange. It should be something like ``` list-bounces(a)lists.domain.info list-bounces(a)alias.domain ``` where alias.domain is the configured alias domain for the mail host lists.domain.info. > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. > > If I do: > > list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 > > Then it goes to the gmail address, and no bounce processing happens. The issue here is the value `lmtp:[mailman-core]:24` is completely wrong. It should be an email address with a syntactically valid domain name. The domain name isn't a real domain. It is only a name exposed to Postorius in the postfix_vmap and postfix_lmtp files. What do you have configured for the alias domain for the lists.domain.info domain? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… If you have this properly configured, adding user(a)gmail.com in either order in postfix_vmap should work. -- 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: Template Ignored?

by Stephen Daniel

That pulls a 404 error. Thanks for the hint. I will investigate. On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 08:04, Stephen Daniel wrote: > > Mailman3 people -- > > > > I created a new list, and used postorius to create a template for " > > list:user:notice:welcome". I then used the mass subscription feature to > > add myself to the list, having checked "pre-confirmed", "pre-approved", > and > > "pre-verified". > > > > I received a welcome message that appears to be the default welcome > > message. It certainly wasn't what I put into my template. > > > > Any suggestions on how I get mailman to use my template? Things I might > be > > doing wrong? > > > What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a > full URL by appending > `/api/templates/list/list.example.com/list:user:notice:welcome` > <http://list.example.com/list:user:notice:welcome> to that > where `list.example.com` is the actual list_id of your list, and go to > that URL, what do you get? > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years

Re: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: changing the main template for subscriptions and more

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210621 17:05]: > Hey there, > > in Mailman2 there was a simple link in the moderation-emails, with > which I was able to open directly the "held-messages". I know how to > manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > But: > > How can I change the template for all the lists (respectively > maildomains/webdomains) so that I don't have to do this manually for > all lists? I searched a bit for the corresponding template, but > didn't find it. At the end it only says the following: I'm using this patch (however, german-only) Andi diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt index bc76a54c4..85cdd9376 100644 --- a/src/mailman/templates/de/list:admin:action:post.txt +++ b/src/mailman/templates/de/list:admin:action:post.txt @@ -9,5 +9,6 @@ Die Nachricht wurde aus folgenden Gründen zurückgehalten: $reasons -Besuchen Sie die Administrations-Seiten, um die Nachricht +Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/held_messages diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt index 88427c8d0..ba77aa3ce 100644 --- a/src/mailman/templates/de/list:admin:action:subscribe.txt +++ b/src/mailman/templates/de/list:admin:action:subscribe.txt @@ -3,3 +3,7 @@ die Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Anmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt index c794355e8..0bace3950 100644 --- a/src/mailman/templates/de/list:admin:action:unsubscribe.txt +++ b/src/mailman/templates/de/list:admin:action:unsubscribe.txt @@ -3,3 +3,7 @@ der Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Abmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt index 3efc32bd1..974d8e465 100644 --- a/src/mailman/templates/de/list:user:notice:welcome.txt +++ b/src/mailman/templates/de/list:user:notice:welcome.txt @@ -1,16 +1,18 @@ Willkommen auf der Mailingliste "$display_name"! -Um an diese Liste zu schreiben, senden Sie eine E-Mail an: - +E-Mails an die Adresse $listname +werden an alle Teilnehmer verteilt. -Sie können Einstellungen vornehmen, indem Sie eine E-Mail an +Auf der Webseite https://$domain/ können Sie Ihre Einstellungen verwalten. +Wer dies möchte, kann sich dort registrieren - bitte mit der E-Mail-Adresse, +die auf der Mailingliste eingetragen ist. Nach dem Einloggen ist auch +möglich, die Empfangsadresse für die Mailinglisten zu ändern, oder +zusätzliche Sendeadressen einzurichten. +Sie können auch Einstellungen vornehmen, indem Sie eine E-Mail an $request_email - mit dem Wort 'help' (ohne Anführungszeichen) im Betreff oder im Inhalt -senden, Sie erhalten dann eine automatisierte Antwort mit weiteren -Instruktionen. Sie werden Ihr Passwort benötigen, um Änderungen an Ihren -Einstellungen vorzunehmen, aber aus Sicherheitsgründen wird dieses hier -nicht angegeben. Sollten Sie Ihr Passwort vergessen haben, nutzen Sie bitte -die 'Passwort vergessen'-Funktion auf der Login-Seite. +senden. Sie erhalten dann eine automatisierte Antwort mit weiteren +Instruktionen. Um Änderungen bei den Einstellungen vorzunehmen, wird das auf +https://$domain/ vereinbarte Passwort benötigt.

4 years, 8 months

Mailman-users search results for query "Postorius"