Search results for "Postorius" - Mailman-users

Re: Extracting mailing list users

by Odhiambo Washington

On Fri, Dec 30, 2022 at 1:57 PM Jan Eden via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi, > > I would like to export users of my mailing lists including their full > name (if present). The export button in Postorius creates a CSV with > addresses only, and the tool bin/list_members mentioned in the > [Mailman 2 FAQ] does not seem to be available in Mailman 3. > > I have full access to the server/database, so scraping the web interface > with [Mark's script] seems unneccessary. Is there an SQL statement (or > an equivalent of bin/list_members) to extract the data? > > Thanks, > Jan > > For MM3: (venv) [mailman@gw ~/mm]$ mailman members listname@domain --output some_file.txt -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

Re: Unable to remove non-member

by Mark Sapiro

On 7/22/24 13:31, kapoortoman--- via Mailman-users wrote: > Hi Everyone, > > I ran across a strange issue today. A client reported the inability to > remove a non-member in the following format: > > z_email/domain.org.za(a)domain.org.za An unquoted local part cannot contain a slash. > The reported error from Postorius was: > > "The user could not be removed" > > I used https://mailtester.ninja/ to validate the email > address and it is syntactically correct. If I ask https://mailtester.ninja/ to validate `z_email/domain.org.za(a)domain.org.za` it tells me that `domain.org.za(a)domain.org.za` is valid, not that `z_email/domain.org.za(a)domain.org.za` is valid. What's in Mailman core's mailman.log for this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

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

4 years, 9 months

Re: Where is the site to translate HyperKitty?

by Mark Sapiro

On 9/25/18 11:17 PM, Ooyama Yosiyuki wrote: > I think that mailman website is not clear where the translation will be done even if reading the page ? > > http://www.gnu.org/software/mailman/index.html > > Even looking at "Developers" page, I can not find the translation phrase. > > Are you going to leave this problem? Are you planning not to internationalize? Is not ? Yes, we are planning to internationalize all of Mailman 3, but we have been focusing more on other issues and also trying to find an appropriate translation site. We have just started a project at <https://hosted.weblate.org/engage/postorius/> for Postorius. We have nothing for HyperKitty yet, but would welcome your help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

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, 1 month

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

10 months, 3 weeks

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/

3 years, 11 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 >

8 years, 2 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, 6 months

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, 3 months

Mailman-users search results for query "Postorius"