Search results for "Postorius" - Mailman-users

Re: list of subscribers

by Peter Münster

On Sun, Feb 04 2018, Simon Hanna wrote: > You should be able to use mailmanclient to get a list of subscribers with > names. It seems, that mailmanclient does not know about the real name (the first name and the last name in Django). But this seems to work: from django.contrib.auth.models import User user = User.objects.get(email='address(a)of.user') print(user.first_name) print(user.last_name) So, I'll try to make some loop over a list with email addresses, that I can get on the web interface. > Names are optional though, if people signup without them you won't be able to > get them. My usage of mailman is perhaps a bit special: users can't sign up, only the site owner signs up manually with create_user(email=, first_name=...) Then the site owner creates the mailing lists and uses mass subscription (for example all members of a basketball team). At one moment, the list of subscribers should be verified by all members, just to be sure, that nobody got forgotten. > Currently there is no option to require names. I'll open an issue in > postorius about showing the name in the member list if there is one > associated. Thanks. It would be nice, to see the first_name and the last_name of the django-auth user object. > IIRC one person(postorius account) can also signup at different lists using > different names (regardless of address). You mean the "display_name" of mailmanclient here? I won't use it. For my usage, I prefer a clear association of email, first name and last name in one account, no need for "display_name" here. > There was some discussion about names and potentially using the from header to > populate the database but I don't remember the result... Nice idea, especially for the normal use case, the public mailing list (but not for mine). Off topic: I have "Receive own postings = Yes", but I don't receive copies of my postings to this list... Kind regards, -- Peter

7 years, 10 months

Re: Hyperkitty Authorization Required

by Mark Sapiro

On 6/6/19 5:52 AM, andrew.bernard(a)gmail.com wrote: > Nearly there configuring my first Mailman 3 installation with Postorius and Hyperkiity. This issue eludes me: > > When trying to start a new thread in the archive, we have: > > HyperKitty failure on https://list.jackrail.org/hyperkitty/api/mailman/archive: <html><title>Auth required</title><body> > <h1>Authorization Required</h1></body></html> (401) > > I can access this URL just fine" > > https://list.jackrail.org/hyperkitty/api/ > > Where do we look to solve this issue? You have to be logged in to post from HyperKitty. You can't post anonymously. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

how to become member of mailman-users list

by Stephen J. Turnbull

Shashikanth Komandoor writes: > One of my colleagues is trying to become a member of the > mailman-users list but she is not able to become so even after sending > multiple emails to the list. Your colleague needs to either sign up via Postorius at https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ or send mail to mailman-users-subscribe(a)mailman3.org to subscribe. She then needs to respond to the mail that the system sends her by visiting the URL in that mail. Without a subscription, mail to the list will be discarded silently, I believe. Once her subscription is active, her first post will be held for moderation. After that, help posts will be unmoderated. Steve

4 years, 3 months

Website 404 error

by peter＠pi4cc.nl

Hello I'm running Debian 12 with the latest version and installed mailman3 via apt install-mailman3-full. Everything works, I'm using MySQL as the database. There's something strange, and I can't find a source/solution. When I first access the website domain.nl/mailman3, it's redirected to domain.nl/mailman/postorius/lists/, resulting in a 404 error (3 after mailman is missing). When I accessed it a second time with the same link (domain.nl/mailman3), I was redirected to domain.nl/mailman3/postorius/lists and the welcome page appeared. This is strange... I tested it on a mobile device with Chrome and Firefox, and on a desktop with Chrome and Edge. All the results were the same. Is there a specific file to look add? Regards, Peter

4 months

Caching problem with templates

by Mark

Caching problem with templates. GNU Mailman 3.3.10 Python 3.11.2 Postorius Version 1.3.13 Venv installation per docs Hi All, A footer template is created and initially it works as expected. Editing the footer template sees the new content written to the database, In addition to viewing the edited content in the database, the new template can also be viewed in Lynx on localhost at: http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer The problem is that the original template is being cached somewhere and the old footer persists in new emails. In trying to get the edited footer to show in the emails I've restarted mailman3/mailmanweb, rebooted the server - but no joy. Any advice on how to flush the cache or hammer this gremlin greatly appreciated. Thanks, Mark

5 months, 2 weeks

Re: bounce handling in mm3 available?

by Stefan Bauer

Hi Mark, thank you. We are running 3.1.1-9. So to get you right, this version only records the bounces in database and nothing more? No disabling of users etc. Stefan Am Mo., 24. Jan. 2022 um 23:32 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 1/24/22 05:20, Stefan Bauer wrote: > > Hi, > > > > what happens with bounce-mails that are processed by mailmans postfix > > instance? > > > What Mailman core version? Prior to 3.3.1, bounce events were recorded > in the bounceevent table but not otherwise processed. Subsequent to > that, they are scored if recognized and what notices are sent depends on > list settings. > > > > Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: > > to=<company-newsletter-bounces(a)lists.company.tld>, > > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, > > dsn=2.0.0, status=sent (250 Ok) > > > > But the list-owner does not get any notification, nor do i see any > > bounce-information in the pistorious-gui. > > What are you expecting to see in Postorius? All you can see is if a > member's delivery status is Disabled by Bounces. Things like Bounce > score are not available in Postorius. > > What notices are sent depends on the settings in the Bounce Processing > section in Postorius. For example, if your message logged by postfix was > spam to the <company-newsletter-bounces(a)lists.company.tld> address that > is not recognized as a DSN and `Forward unrecognized bounces` is > Discard, the message will be silently discarded. > > Also, if that message was a non-fatal, message-delayed type of DSN, it > will be ignored. > > -- > 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/ >

3 years, 10 months

(SOLVED) Re: Problems with web interface after upgrade

by Victoriano Giralt

The relevant part of the error was not the one about sassc, it was this other one: ''' CommandError: An error occurred during rendering /usr/local/lib/python3.6/site-packages/django_mailman3/templates/account/email_confirm.html: Error: It's not clear which file to import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. Candidates: ../libs/bootstrap/stylesheets/_bootstrap.scss ../libs/bootstrap/stylesheets/bootstrap.scss Please delete or rename all but one of these files. on line 4 of static/hyperkitty/sass/hyperkitty.scss >> @import "../libs/bootstrap/stylesheets/bootstrap"; ''' The _bootstrap.scss was lingering from the previously running version, and bootstrap.scss had been added wth the upgrade. This was confussing the templating engine ... Mailman 3.3.3 humming happily with Postorius 1.3.4 and Hyperkitty 1.3.4 Thanks for your time!

4 years, 10 months

Re: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

On 7/27/20 3:38 PM, Brian Carpenter wrote: > I recently imported a number of MM2 lists into MM3. Unfortunately, the person had emergency moderation turned on for these lists. Since EM is not exposed to Postorius what can be done to reverse this? To do one list: mailman shell -l <list-id> m.emergency = False commit() To do several lists: mailman shell from mailman.models.mailinglist import MailingList mlist = MailingList('first.list.id') mlist.emergency = False commit() mlist = MailingList('second.list.id') mlist.emergency = False commit() And so on for more lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Brian Carpenter

On 2/26/21 6:55 AM, Andreas Barth wrote: > * Lars Schimmer (l.schimmer(a)cgv.tugraz.at) [210226 10:15]: >> On 26/02/2021 00:55, Brian Carpenter wrote: >>> I have finished my how-to install Mailman 3 on Debian 10 completed to >>> the point where you can use it to get a fully functional Mailman 3 >>> environment up and running. This is a comprehensive guide that walks you >>> through installing EVERYTHING (currently!) that Mailman 3 needs to run. >>> It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have >>> not added the update directions yet but will very soon. I also plan on >>> adding a section on setting up DKIM and Xapian with Mailman 3. >>> >>> I hope this helps those who wish to get a Mailman 3 server up and >>> running quickly and brings a sense of sanity to the confusion regarding >>> the various documentation out there concerning the installation of >>> Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 >>> at some point. >>> >>> Without further ado: >>> >>> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 >>> >>> I am sure the above guide can use improvements. Feel free to contact me >>> off-list to point out mistakes/improvements, etc. >>> >> Hm, it completely ignores the standard way for Debian: >> apt-get install mailman3-full >> also exim4 as standard mailer. >> And apache2. > That's how I did it (for my first installation), and it worked out of > the box. However I would recommend to directly use a real database > (e.g. postgresql). > > > > Andi > _______________________________________________ > Except my How-to will give you the latest stable versions of Mailman 3, Postorius, and Hyperkitty and PostgreSQL instead of sqlite. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

Re: FILTER_VHOST for 3.2.1 not working after install

by Mark Sapiro

On 1/8/20 2:33 AM, Élodie BOSSIER via Mailman-users wrote: > > I would like with Mailman 3.2.1 see into : > - "example1.com/postorius/lists/" only the mailing list related to example1, > - and into "example2.com/postorius/lists/" only the mailing list related > to example2 as Mailman 2.1.x do it. > > I don't understand what I missed, could you help me please ? It works for me. I suspect in your case it has something to do with how ngnix is set up to forward to Django. What are your nginx settings for this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Mailman-users search results for query "Postorius"