Search results for "Postorius" - Mailman-users

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

10 months, 1 week

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

5 years, 2 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!

5 years, 2 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, 9 months

Re: Unadvertised lists accessible even if not signed in

by Mark Sapiro

On 1/5/26 12:54, Peter Chubb via Mailman-users wrote: > > How can I prevent anyone not logged in, and not a member of an > unadvertised list, from seeing it? You could probably modify code to do that. For Postorius, the mods would probably be in the ListSummaryView class in postorius/views/list.py. It seems to me that in the general case, this would not be desirable as it would prevent things like a user being told out of band that they should go to, e.g., https://www.example.com/mailman3/lists/unadvertized.example.com/ and subscribe. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 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

6 years, 3 months

No styling for web apps?

by Morris Jones

I have most of a new mailman suite server built and working ... collectstatic gathered a good array of static files (uncompressed so far) nginx appears to be serving them successfully The Firefox developer tools show css and js files all being delivered But none of the postorius or hyperkitty pages exhibit any styling at all, only bare HTML elements. The Firefox inspector will show the available styles being requested and delivered (style.css, bootstrap, jquery, all the things). But if I use the inspector to look at the page, nothing has any CSS properties. I know I'm missing something simple. (Happy Thanksgiving!) Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 5 months

Re: Starting new thread in Postorius -> disappears

by Cameron Smith

Mark, My apologies for not investigating more thoroughly before opening my mouth (so to speak). You are, of course, correct in your analysis of what happened to my emails, and this is not the first time that my email setup has caused me problems. I’ve added my alternate email address to my lists.mailman3.org user profile, so hopefully it won’t happen again. > On 2017.11.29, at 18:09 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/29/2017 05:05 PM, Cameron Smith wrote: >> >> On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. > > > Your post was received: > > Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: > message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: > from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) > > delivered to Mailman core: > > Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: > to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) > > and immediately discarded: > > Nov 21 14:31:21 2017 (19106) DISCARD: > <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > > >> Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. > > > Possibly you never received a list copy of his message because you were > directly addressed and your list option "Receive list copies (possible > duplicates)" is set to No. > > >> So, what’s going on? > > > As to why your post was discarded, unfortunately, the logs don't give > more info. There are a couple of possibilities. If your post contained > an attachment with Content=Type: application/subtype where sub-type > doesn't contain 'signature' it would have been discarded by a header > filter rule. Also it looks like you sent the message From: > <ccsmith(a)mail2.cetsi.com>. If that is not an address on your > <ccsmith(a)cetsi.com> account, it would have been discarded as a > non-member post. > > >> What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. > > > I see nothing so far to indicate anything at lists.mailman3.org is > broken in this respect. The only "unusual" thing is this is now a new > thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, > but presumably that is because your post was in reply to your earlier > post which wasn't archived. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Cameron Smith Nanaimo, BC tel:1.604.803.0051

8 years, 4 months

Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? > On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini > 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 > 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 > 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini > > This fishy, why do you have both uwsgi and "python manage.py runserver" running? > > You only need one of those, since they both do the exact same thing. Please remove > whatever is running the "python manage.py runserver" part and only use uwsgi. > >> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >> May mailman processes are next: >> >> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >> >> Looks like there are no double. Nothing more is running. >> >> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >> >>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>> >>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>> $ sudo pip3 install mailman >>> $ sudo pip3 install postorius >>> $ sudo pip3 install hyperkitty >>> $ sudo pip3 install mailman-hyperkitty >>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >> >> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >> >>> >>> >>> >>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>> >>> >>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>> > Hi. All the project installation is under the same user / path and >>> > it works. Archiving working as well, (just one remark: no matter what >>> > to set in postorius, hyperkitty shows list as public) >>> > I have found work around - it is possible to change list as private in >>> > "admin" page. >>> > I started to get issues with runjobs after I have created couple of >>> > new lists with "no archive" option. >>> >>> How did you install all these components. It seems there the installation is broken in weird ways. >>> >>> > >>> > If as owner user from project home I run: >>> > >>> > django-admin mailman_sync >>> > >>> > Traceback (most recent call last): >>> > File >>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>> > line 84, in _execute >>> > return self.cursor.execute(sql, params) >>> > File >>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>> > line 383, in execute >>> > return Database.Cursor.execute(self, query, params) >>> > sqlite3.OperationalError: attempt to write a readonly database >>> > >>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>> > "django-admin runjob new_lists_from_mailman" >>> > django.db.utils.OperationalError: attempt to write a readonly database >>> > END TRACEBACK >>> > >>> > I did not find information how to fix this. It was worked without errors >>> > before. >>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>> > to work. >>> > If I start "mailman start", then "django-admin mailman_sync" failing >>> > again. >>> > I did not check other jobs, but I think what is related to database, >>> > will get errors. >>> > Seems mailman locking the database. It is not a file permissions issue. >>> > Mailman db location is: /project_directory/var/data/mailman.db >>> > >>> > if to rename /project_directory/var/data/mailman.db to something, >>> > mailman creates database file size 0, django-admin runjobs start >>> > working, but of course postorius stops working. I did it for testing. >>> > I have returned this database file back, postorius started to work >>> > again, but django-admin runjobs does not work, error: "database read >>> > only". >>> > Please help me how to fix this issue. >>> > _______________________________________________ >>> > 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/ >>> > >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years, 8 months

Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 7:53 AM, Jered Floyd wrote: > > File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/rules/dmarc.py", line 284, in maybe_mitigate > for address in mlist.dmarc_addresses: > TypeError: 'NoneType' object is not iterable > Nov 25 15:49:26 2023 (90) SHUNTING: 1700927366.81852+6d2f84a8eb97e64c3ee93662f1744a2a756c7ca9 > [...] This may be a bug. I need to investigate. Meanwhile, go to the list's settings in Postorius and under DMARC Mitigations, put something in DMARC Addresses, save it and then remove it and save again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Mailman-users search results for query "Postorius"