Search results for "Postorius" - Mailman-users

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

by Mark Sapiro

On 3/19/21 2:55 PM, Jens Günther wrote: > > 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 Huh? that is the same URL as the one above that you say works. Do you mean https://mailman.xyz.de/mailman/postorius/lists without the slash or what. > 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. What is the exact content of your RedirectMatch or ReweriteRule or whatebver you are using? -- 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 postorius cannot retrieve template

by Mark Dadgar

On Nov 4, 2021, at 3:05 PM, Andreas Barth <aba(a)ayous.org> wrote: > * Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: >> >> >> --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro >> <mark(a)msapiro.net> wrote: >> >>> On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >>>> >>>> My conclusion: >>>> I ask you to consider these experiences in an update for the mailman3 >>>> packages in debian bullseye. It would save time, questions and nerves. >>> >>> >>> Issues with Debian packaging should be directed to Debian. >> >> Or as previously discussed, the debian packages should be avoided entirely. > > I strongly disagree with that statement. > > Distribution packages have their own up- and downsides. Of course, how > they are done is to be discussed with the distribution, so: if > something is wrong with a debian package, please follow the > instructions on bugs.debian.org on reporting bugs. > > However, they have the advantage that they're integrated with the > distribution. They have the disadvantage that they're stable for some > time - that is why it's called a stable release. If they have all the > features someone wants, they usually work fine (and my first > mm3-installation was the default debian package). If one looks for > bleeding edge, of course that's not what one can expect from a > distribution package - but that's also a feature. You left out the fact that the distro edition of mailman3 has very poor support because Debian doesn’t know how to do it and the setup is different enough from vanilla that this community has a hard time supporting it as well. You can certainly try to run it, but I’m willing to bet that you’ll regret it. Having tried it myself, I can’t in good conscience recommend it to anyone. The bottom line is that, IMHO, distro works great for fairly mature projects. MM3 isn’t that yet. YMMV, my $0.02, you get what you pay for, etc. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 7 months

mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Stefan Bauer

Dear Users, trying to update mailman3 to lastest version, we fail during mailman-web migrate with: Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower...Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", line 328, in execute return super().execute(query, params) sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email We found a workaround to fake the migration with migrate --fake Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower... FAKED Applying account.0007_emailaddress_idx_email... FAKED Applying account.0008_emailaddress_unique_primary_email_fixup... FAKED Applying account.0009_emailaddress_unique_primary_email... FAKED Applying django_q.0015_alter_schedule_schedule_type... FAKED Applying django_q.0016_schedule_intended_date_kwarg... FAKED Applying django_q.0017_task_cluster_alter... FAKED Applying django_q.0018_task_success_index... FAKED Applying postorius.0019_alter_emailtemplate_data... FAKED And mailman 3 is still processing mails. I'm unsure if i should recover from snapshot or keep it going? Could this be some duplicate users with same mail-address? I have at least spotted one user and delete him. thank you. Stefan

1 year, 3 months

Re: How to configure an announce-only list?

by Mark Sapiro

On 4/28/26 5:17 PM, Craig Leres via Mailman-users wrote: > I want to create a mailing list that is used for announcements only. I'd > like attempts to post to be rejected with a notification. > > I was able to set the list pw and verify it works with the Approved > header using this reference: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/ > docs/approved.html > > I find that if both: > > Default action to take when a member posts to the list > Default action to take when a non-member posts to the list > > are set to "reject (with notification)", the approved header is ignored > and messages are always rejected (posted via "mailman inject") This should not be the case. The message is checked for an Approved: header prior to the member/nonmember checks. > Would it be bad to test the approved header before rejecting a message? > Essentially always accept a message with a valid approved header? Is > there another way for me to achieve this? That's the way it should be working. There is a potential issue if the password in the Approved: header when encrypted doesn't match the encrypted value in the lists moderator_password attribute, it is treated as if there were no Approved: header. This is a bug <https://gitlab.com/mailman/mailman/-/work_items/1276>. I.e., the message should be rejected but with a reason indicating the password was wrong. > On another front, I'm unable to have messages posted via "mailman > inject" use postorius created list templates. Would it be difficult to > add this functionality? That should not be the case. Are you saying messages posted via email use Postorius created templates, but messages posted via mailman inject do not? If the templates are used for messages posted via email, they should also me used for messages posted via mailman inject. Have you verified that the templates are used for messages posted via email? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

Re: Footer from templates not working - DB issue?

by Hans Mayer

Hi Mark, many thanks for this hint. I updated table "template" and replaced "localhost" with the real name and it worked. // Hans -- On 25.09.22 19:28, Mark Sapiro wrote: > On 9/25/22 05:26, mailman--- via Mailman-users wrote: >> Dear All, >> I have a similar issue. Also on Debian 11. Also installed as Debian >> PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) >> I am using sqlite3. When I do the SQL-query I get an URI which is in >> multiple reasons wrong >> http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… >> > > The initial part of that URL is set from the Django setting > `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to > `http://localhost/mailman3/`, it should probably be just > `http://localhost/`. > > >> OK - the hostname could be changed but the path is not existing at all. >> There is no file "list:member:regular:footer" on the complete >> filesystem. > > It's not a file. It refers to an entry in the postorius_emailtemplate > table in the database which is retrieved via the Postorius API. >

3 years, 8 months

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

by Mark Sapiro

On 3/19/21 3:12 PM, Jens Günther wrote: > > > -> the first one works and leeds to > https://mailman.xyz.de/mailman3/postorius/lists > -> the second one redirects to > https://mailman.xyz.de/mailman/postorius/lists > -> which does not exist, since Apache-alias is only for mailman3 Sorry, I missed that it was mailman vs mailman3. > > I only use the apache-conf given in the documentation: > > <code> > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 > unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > </code> I don't use uwsgi so I can't advise on its configuration, but do you have USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') in your Django settings? -- 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: [Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

Mark, Is it only this list that has an issue? Yes, this is the only list that is having the issue. Can you visit other pages for this list? Yes, I'm able to view the members list, list settings, templates, etc. I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen chunked=chunked, File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib64/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 756, in urlopen method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/util/retry.py", line 531, in increment raise six.reraise(type(error), error, _stacktrace) File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/packages/six.py", line 734, in reraise raise value.with_traceback(tb) File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen chunked=chunked, File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib64/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call headers=headers) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/postorius/auth/decorators.py", line 60, in wrapper return fn(*args, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/postorius/views/list.py", line 620, in list_moderation paginator_class=MailmanPaginator) File "/opt/mailmanve/lib64/python3.6/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/opt/mailmanve/lib64/python3.6/site-packages/django_mailman3/lib/paginator.py", line 47, in page result = self.function(count=self.per_page, page=number) File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 132, in get_held_page return Page(self._connection, url, HeldMessage, count, page) File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/connection.py", line 136, in call 'Could not connect to Mailman API: ', repr(e)) mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', "ConnectionError(ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)),)") ERROR 2021-02-25 17:28:14,271 393 django.request Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages ERROR 2021-02-25 17:28:14,271 393 django.request Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages

5 years, 3 months

Error while mass operation, no progress display while mass operation is running

by Markus Grandpré

Dear List, At the University of Konstanz we have mailing list administrators who frequently add and remove up to 10000 (and sometimes more) list members. I have therefore tested the “Mass subscription” and “Mass removal” operations and found that both the “Remove ALL members” operation and the “Mass subscription” operation report an internal server error on the website, but continue to run in the background until all new members have been successfully added or deleted. Unfortunately, I have not found any error message in the log files. I also tested that mass operations “Remove listed users” and “Remove Selected” ran successfully and without any errors. Regardless of whether a mass operation process runs without errors or continues to run despite an error, I find it hard that Postorius does not display the progress of such a mass operation in order to monitor the process, as mass operations with more than 1000 members are very time-consuming. Perhaps this could be changed in a future version of Postorius? Best Markus -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 4 months

Re: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Thank you so much, Mark and Stephen, for the quick action and response. Waiting for the next release. On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/28/25 10:55, Mark Sapiro wrote: > > > > `mailman import21` will import the setting, but per the above comment, > > it doesn't yet work. The setting exists and is exposed in REST, but it > > appears it is not actually implemented. > > > This is now implemented for the next release. See > https://gitlab.com/mailman/mailman/-/issues/1215 and > https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman > core and https://gitlab.com/mailman/postorius/-/issues/628 and > https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

1 year, 1 month

Re: MM3 not starting afte an upgrade

by Gelpi Andrea

Il 23/07/20 23:05, Mark Sapiro ha scritto: > On 7/23/20 4:35 AM, Gelpi Andrea wrote: >> Hi, >> to day in a Debian system I upgraded some packages. >> >> After the MM3 doesn't start anymore. . . . >> Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0) >> Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1] >> Operation not permitted > > > I think you have a stale lock issue and the master is trying to > determine if the process that set it still exists. > > Remove Mailman's var/locks/master.lck* > Thanks Mark, now MM3 star but postorius is not working. The web pagge return: An error occurred while processing your request. I receive an email with: ... Exception Type: KeyError at /postorius/lists/ Exception Value: 'file' Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data Is that related to Django id setting or there is a passphrase mismach some where? How can I check? -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 10 months

Mailman-users search results for query "Postorius"