Search results for "Postorius" - Mailman-users

Re: Template - "You can use these variables in the templates" - The variable for "leave" is missing

by Mark Sapiro

On 11/3/23 01:28, Wikinaut wrote: > I suggest to add this is as a new variable $leave_email . > > By the way: how can I access the _short_ list description text as a variable? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information on the variables that can be used in templates. There you will see the variable for "the mailing list’s short description text" is `description`. This is missing from the list displayed in Postorius which needs updating for this and other reasons, e.g. $hyperkitty_url is only available in regular headers and footers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: Mailing list welcome message won't update

by frances.du＠uq.edu.au

Hi Mark, I have a dev mailman server that is having the same problem too. (When updated the welcome text file, then subscribe to the mailing list but still get the old welcome message.) The dev mailman instance is much newer: GNU Mailman 3.3.9 (Tom Sawyer) Postorius Version 1.3.13 I also found that the actual file containing the welcome message and footer message does not have the .txt extension for my dev instance. root@mailman-dev:/var/lib/mailman3/templates/lists/[redacted].mailman-dev.dev.aws.[redacted].org.au/en# ll total 12 drwxr--r-- 2 mailman operations 4096 Jan 22 14:14 ./ drwxr--r-- 3 mailman operations 4096 Oct 1 13:50 ../ -rwxr--r-- 1 mailman operations 0 Oct 1 13:50 list:member:regular:footer* -rwxr--r-- 1 mailman operations 506 Jan 22 14:12 list:user:notice:welcome* What is that * at the end of the file name mean? Thank you. Frances

1 year

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 >

8 years, 3 months

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

2 years, 8 months

Re: Question about lists and domains on Mailman 3

by Jeff

I believe that you need to add "FILTER_VHOST = True” to your “settings.py" > On Dec 29, 2021, at 5:11 AM, Philip Colmer <philip.colmer(a)linaro.org> wrote: > > I've got a single server hosting multiple domains. I've got Apache working > as the proxy in front of MM3. > > Regardless of whether I go to https://lists.domainA.org/mailman3/lists/ or > https://lists.domainB.org/mailman3/lists/, Postorius lists ALL of the lists > across both domains. > > Is there a way of configuring the system so that, if a user goes to "domain > A", only the lists for that domain are listed? > > Thanks. > > Philip > _______________________________________________ > 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

Acceptable aliases defaults to []

by Henrik Rasmussen

* Docker-mail 0.1.1 * Mailman 3.1 * Postorius 1.1.1 * Hyperkitty 1.1.1 Minor issues: Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2: * http://www.list.org/mailman-admin/node23.html * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

8 years, 5 months

Re: Importing config and archives only partially succeeded?

by Mark Sapiro

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

5 years, 1 month

Re: Django administration - User permissions

by Mark Sapiro

On 5/29/24 11:18 AM, advorkin(a)cs.princeton.edu wrote: > > So, just to be clear, in order for someone to have an ability to create/delete a mailing list, they must be a superuser? The reason I'm asking is for security purposes and making sure that specific user has only minimal access. Currently that's true. It should be possible for a domain owner to create a list in that domain, but currently I don't think it is. > What are those Django permissions for...? Is there a use for them? Those permissions correspond to database tables, and I think they allow actions on those tables through the django admin UI. They do not (currently at least) allow any Postorius or HyperKitty UI actions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Member Issue Discovered

by Mark Sapiro

On 10/28/20 1:42 PM, Brian Carpenter wrote: > > This is a bug with Affinity which I have scheduled to be fixed. However > I am confused. Data is completely removed from Mailman 3 core when you > delete the account via Postorius but not when you unsubscribe from a list? Why do you keep bringing this up? The current design of Mailman core does not remove the user when the user unsubscribes from a list, even if it is their only subscription. We know you don't like this behavior, but there are reasons for it. On the other hand, when a user removes their account, the circumstance is different and we do remove the user's information in this case because that's what the user asked for. -- 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: changing the main template for subscriptions and more

by Paul Paulchen

Hi Mark, thanks for your advice. Unfortunately we need some more clues. First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman Our version: Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] We put an example footer.txt into the templates folder as you mentioned: mailman3_core => var/templates/sites/de/list:member:regular:footer.txt Mailman user can read them Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt Much appreciate your effort helping people!

3 years, 11 months

Mailman-users search results for query "Postorius"