Search results for "Postorius" - Mailman-users

Re: restrict sending to owner/moderator

by David Krantz

Hi, I have just tested a variant of this as I got curious: You find the member you want to be able to send emails without moderation, then set Administrative Options to "Accept Immediately (bypass other rules)". That works. I have found no other ways, though. // David On Mon, Sep 18, 2017 at 11:28 AM, <m.dohmen(a)xconnect.de> wrote: > Hello, > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. > > Is there a way to do this? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

9 years, 1 month

Re: Template URI gets written incorrectly

by Mark Sapiro

On 5/23/23 16:51, Mark Dale via Mailman-users wrote: > > When I create a template, it writes the URI incorrectly into the > template table in the mailman3 database and the list stops working. > > For example, it writes: > > http://localhost/mailman3/postorius/api/templates/list/markslist.lists.post… > > When I correct it like so, all is well: > > https://lists.postmark.io/mailman3/postorius/api/templates/list/markslist.l… > > Have I missed a config setting somewhere, or is this a bug with the > older Debian Mailman 3.3.3 ? You need to set POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/' in your Django settings. Debian probably has set it to 'http://localhost/'. -- 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: Sanity check of upgrade procedure

by David Newman

On 10/26/22 3:10 PM, Mark Sapiro wrote: > On 10/26/22 11:08, David Newman wrote: >> >> For these new releases, is that mistune step still needed? > > > No. That is one of the issues fixed in HyperKitty 1.3.6 which now > requires mistune>=2.0.0,<3.0 and will work with those versions. OK, thanks. Before getting to mistune, this command, run as mailman in a venv: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi Mailmanclient produced this error: .. Attempting uninstall: mailman-web Found existing installation: mailman-web 0.0.6.dev9+gc606169 Uninstalling mailman-web-0.0.6.dev9+gc606169: Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: 'WHEEL' Check the permissions. The command also said I needed to upgrade pip. Doing that produced a similar error. How to resolve this error? Thanks again. dn

4 years

Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Mark, Thank you for this reminder, but it’s not really sufficient for most. The ‘Mailman Settings’ dialog does, indeed show the other preferences tags, and yes, as you say, the dialog for ‘List-based preferences’ only shows values that are not inherited and when you set a value there, it shows. There a two problems with this: a. Once a value is overridden on the ‘List-based preferences’ dialog, you cannot go back to it being inherited by removing the override. b. You cannot see, on this dialog, what the inherited value is. This is not user-friendly. May I suggest the following: That each option shows the following: o Value 1 o Value 2 (or the equivalent for pull-down menus) A box showing inheritance status: [ ] Use inherited value from address-based preference: Value2 If the ‘Use inherited value’ is chosen, then the inherited value shows. but the value radio buttons become non-selectable. If not, then whatever value the value radio box has become the value for the list, From what I see, the ‘Use inherited value’ is the default for new lists/addresses. To change a value, the user would uncheck this box, making the radio buttons selectable, and then set the desired value. Yours, Allan > On Feb 12, 2021, at 11:52 , Mark Sapiro <mark(a)msapiro.net> wrote: > >> I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? > > > If the user has a Django account, she can see all that info at (e.g. for > this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/ <https://lists.mailman3.org/mailman3/accounts/subscriptions/>> > She gets there from `Mailman settings` in the dropdown under her user > name. She can also get there via the `Manage Subscription` button on the > list's Info page. That takes her to `List-based preferences` for the > list. Any setting not selected there is inherited from the Address-based > preferences or Global Mailman preferences

5 years, 8 months

Re: Something wrong with my Hyperkitty base_url?

by Andrew Hodder

from django.conf.urls import include, url from django.core.urlresolvers import reverse_lazy from django.views.generic import RedirectView from django.contrib import admin urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('hk_root'))), url(r'^hyperkitty/', include('hyperkitty.urls')), #url(r'^postorius/', include('postorius.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', include(admin.site.urls)), url(r'^hyperkitty/admin/', include(admin.site.urls)), I removed the archives from the base_url, it still errors out just with a different path: ValueError: <h1>Not Found</h1><p>The requested URL /api/mailman/archive was not found on this server.</p> Now I should note, I'm running the web ui for hyperkitty on nginx with http://FQDN/hyperkitty/ (where the non-/hyperkitty/ path would just go to postorius). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Mon, Oct 2, 2017 at 3:22 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Mon, Oct 2, 2017, at 12:17 PM, Andrew Hodder wrote: > > Finally have everything stood up and working, except for HyperKitty > > mailman > > plugin. I'm getting a path issue of sorts I can see in the archiver.log > > (have it set to debug log level in the mailman core): > > > > Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): > > File > > "/opt/mailman/venv3/lib/python3.4/site-packages/ > mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", > > line 154, in _archive_message > > url = self._send_message(mlist, msg) > > File > > "/opt/mailman/venv3/lib/python3.4/site-packages/ > mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", > > line 210, in _send_message > > raise ValueError(result.text) > > ValueError: <h1>Not Found</h1><p>The requested URL > > /archives/api/mailman/archive was not found on this server.</p> > > > > > > My base_url in the mailman-hyperkitty.cfg: > > Can you show the contents of 'urls.py' in mailman-suite or whatever > Django project you are using to deploy hyperkitty? That would give more > ideas about whether the '/archives/' URL is valid or not. > > > -- > Abhilash Raj > maxking(a)asynchronous.in >

9 years, 1 month

Re: Hyperkitty using wrong email address in archive view

by Mark Sapiro

On 5/16/23 01:42, peter(a)chubb.wattle.id.au wrote: > Hi Folks, > I notice that for people with multiple email addresses, the email > address that appears as the 'FROM' address in the hyperkitty > archive is not the primary address, nor is it the address that the > email actually came from, but the address that was created first. > (Hyperkitty version 1.3.7) Where exactly do you see this address? Normally, if the From: header of the mail contains a display name, it is that name which is displayed as the author of the email. The display is only an address if the From: header of the mail had no display name or if it had a display name which was an email address as in From: user(a)example.com <user(a)example.com> > When I click on that from address in the archive view, I see all > the email addresses for the user -- these do not match up with the > ones in the django admin screen from .../admin/account/emailaddress/ Because they are not the Django user's email addresses, they are the Mailman user's email addresses. > When I see 'User profile for Fred Frog' > it shows obsolete addresses (not subscribed, not in the Django > profile for the user). Again these are the Mailman user's addresses. The Mailman users are listed at the Users tab on the top Postorius nav bar. > How can I as administrator get rid of bogus addresses? Or do I > have to ask each user to do this? The user can do it at https://example.com/accounts/email/ but the admin can't do it from Postorius. A site admin can do it via REST or `mailman shell`. > and how can I ensure that the email address displayed in the > archive is the primary address, not some address that no longer > works? Again, where do you see this? You may want to download that thread and see what that shows as the From: header of the email. -- 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: Unknown attribute: max_message_size

by Alexander Klotz

Hi, unfortunately we still have problems configuring a list so that it allows a message size larger than 40 KB. Neither the workaround described here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… (required was already set to false) nor this docker setup by yova https://gitlab.com/mailman/postorius/issues/246 worked. Are there any other options we could try? Thanks! Regards, Alex Klotz (CultureBase editorial staff) Am 28.05.18 um 17:16 schrieb Mark Sapiro: > On 05/28/2018 08:05 AM, Alexander Klotz wrote: >> Hi, >> >> just encountering the same problem in postorious, how are the chances of >> a fix being released soon? > > > It is fixed in the current branch heads. We plan a new release very > soon. There are still a few things we want to get in the release, so > it's not quite ready yet, but we're working on it. >

8 years, 4 months

Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Danil Smirnov

Hi Mark, On Fri, May 24, 2024 at 11:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I'd vote for disabling it by default and also for moving the Postorius NNTP-related settings from the "Settings - List Identity" page (the last five settings) to a separate page. Users who are born later than my generation are sometimes confused and misinterpret those settings. Once a user set "Newsgroup moderation" to "Moderated" by mistake which implicitly made the mailing list moderated too. Sincerely, Danil Smirnov

2 years, 5 months

Github auth deprecated API

by Quanah Gibson-Mount

The version of mailman3 I'm running apparently uses a deprecated API for GitHub authentication. Does anyone know if this has been fixed? I couldn't find an issue for it on the postorius issue tracker. Sample email: ==================================================== Hello there! On May 14th, 2020 at 00:38 (UTC) your application used an access token (with the User-Agent python-requests/2.21.0) as part of a query parameter to access an endpoint through the GitHub API. https://api.github.com/user Please use the Authorization HTTP header instead as using the `access_token` query parameter is deprecated. Depending on your API usage, we'll be sending you this email reminder on a monthly basis. Visit https://developer.github.com/changes/2020-02-10-deprecating-auth-through-qu… for more information about suggested workarounds and removal dates. ==================================================== Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 years, 5 months

[Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 28/02/21 19:31, Abhilash Raj ha scritto: > On Sun, Feb 28, 2021, at 10:17 AM, blackout69 wrote: >> Hello everybody,I received this error message and from that moment the >> maiilan3 has stopped working.I restarted the following services mailman3 >> and mailman3-web and everything started working fine.Can you tell me >> what is the problem my django server has encountered? > What version of Hyperkitty are you running? It might be useful to include the versions of all the related Mailman packages, including: hyperkitty, django-mailman3, mailmanclient. Thanks Abhilash Raj for the reply Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] Postorius 1.2.4 HyperKitty 1.2.2 mailmanclient 3.2.2 django-mailman3 1.2.0-3 mailmanclient 3.2.2-1 -- blackout69

5 years, 8 months

Mailman-users search results for query "Postorius"