Search results for "Postorius" - Mailman-users

Rejecting held emails

by Darren Smith

Hello, We recently had a phishing message make it through our spam filters and arrive at a mailing list. The good news is that since it was not from a list member it was in the held message queue. I was able to find the message in the var/messages directory by searching for a keyword in the subject. However, after rejecting the message from Postorius, the message doesn't seem to be removed from the var/messages directory. Is this expected behavior? I know that infosec people won't be too happy about a phishing email sitting around on our disk. (Infosec guys are notoriously paranoid. :) ) Is there some sort of cleanup process that would remove these messages? If not, does this pose an issue where over time disk usage will creep up? This could be a pretty significant problem if that is the case. What do you think, sirs? -Darren

6 years, 7 months

Re: django request error

by eggert＠eehmke.de

I did a fresh installation on another machine, and the problem showed up too. I guess it is a Debian bug. The point is, the last letter of mailman3 in the url gets lost somewhere, so all urls get invalid. I could get this workaround to work: in the apache vhost config: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory /var/lib/mailman3/web/static> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> Note I changed the mailman3 to mailman in the uwsgi line. The static files including the css had to be accessed still under mailman3. Still this is an ugly solution, but my mailing lists work again. If someone finds a clean solution, you are welcome. Will try to create a Debian issue.

3 years, 1 month

Remove ALL Members button - was: Re: Setting base_url for the domain to use it in the templates.

by Mark Sapiro

On 7/10/24 10:46 PM, Odhiambo Washington via Mailman-users wrote: > > I find the unsubscribe_all button quite scary! I have never used it though, > so I am not quite sure about its behavior. What scares me > is the possibility of clicking it and then in one fell swoop you've removed > ALL the members without a "confirmation". See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and the issue at https://gitlab.com/mailman/postorius/-/issues/545. Bottom line - there is a confirmation. Try it, perhaps on a test list if you're really scared. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

Re: Mailman 3 - Header Filter

by Mark Sapiro

On 4/22/19 2:34 PM, Thomas Lehker wrote: > I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. The issue may be that in Mailman core's 'builtin' chain, the checking of header_matches occurs after the check for member moderation so if the member moderation check results in the message being held, the header_matches aren't checked. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: Unsubscribe Notifications to List Owners and Members

by Abhilash Raj

On Thu, Oct 22, 2020, at 1:56 PM, Brian Carpenter wrote: > It seems that the only time an unsubscribe notification is sent to a > list owner and/or list member is when a list member sends an email to > lisname-unsubscribe@listdomain and that list member is not registered > with Affinity/Postorius. Can anyone confirm this and if confirmed, is > this considered a bug? This was a bug[1] and has been fixed[2]. [1]: https://gitlab.com/mailman/mailman/-/issues/759 [2]: https://gitlab.com/mailman/mailman/-/merge_requests/699 It should be a part of the upcoming 3.3.2 release. > > > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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)

4 years, 1 month

Upgrading packages

by Eggert Ehmke

Hello Mark & all, I have the venv installation on my Debian 11 system running. I followed your suggestion to upgrade all packages. When upgrading hyperkitty by this command: pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. All packages were upgraded fine. I applied the patch to venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to change the mistune import line. When I run now mailman-web migrate I get: *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* *To fix them run 'python manage.py makemigrations --merge'* However, when I run the suggested command as: $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- merge No conflicts detected to merge. Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my production system. Would be nice to shed some light on this. Eggert

2 years, 1 month

Re: Backup and restore a single list

by Mark Sapiro

On 6/17/22 22:08, sherin(a)raidm.com wrote: > Hi Mark, > Which database store the list data and archives. I am using Mailman3 with Hyperkitty. Does the hyperkity store the mails of the list ? I can write a python script to import the data. I am at the end of completion of a fully pyhton based modern hosting control panel ( better than cpanel ) and at the final stage of backup and restore procedure. Mailman core's database is defined in the `database` section of mailman.cfg. ``` mailman conf -s database ``` The database for HyperKitty, Postorius, django_mailman3 and other Django modules is defined in the `DATABASES` dictionary in Django's settings. Normally these define the same database as the tables don't conflict. -- 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

Re: Migrating from mailman-suite to mailman-web

by Mark Sapiro

On 6/4/22 09:09, Andrew Hodgson wrote: > Hi. > > Any pointers in migrating from Mailman-suite to Mailman-web? I'm interested specifically in configuration changes required to Gunicorn in order to bring up the Django project using Mailman-web. mailman-suite is really just an example containing a Django settings file and urls.py and wsgi.py. mailman-web is a package which installs Mailman's web UI including HyperKitty and Postorius. Neither of these addresses the wsgi server per se. It could be Gunicorn, uWSGI, Apache mod_wsgi or possibly something else. Apparently you are using Gunicorn and want to continue to do so. I think the only required changes to Gunicorn might be file system paths. What specifically are you concerned about? -- 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

Re: signup / registration error - permissions and cert chains

by Mark Sapiro

On 12/30/21 4:48 PM, David Newman wrote: > > The etc/mailman3/settings.py file includes these settings: > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 These 2 (localhost and port 25) are defaults. > EMAIL_HOST_USER = 'dnewman(a)networktest.com' > EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' Why are you authenticating? This should not be necessary. > EMAIL_USE_TLS = 'True' > EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' > EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' And why are you trying to use TLS? This is only for SMTP between Django and the MTA on the loopback port. TLS is overkill. > But this might only be for email, not Postorius/Django. Actually it is only for mail from Django -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Re: Backup and restore a single list

by Mark Sapiro

On 6/16/22 23:53, sherin(a)raidm.com wrote: > Hello, > I am new to mailman3 . I am looking for the procedure to backup and restore a single mailing list from mailman3. If any one know the procedure or the documentation , please point me Unlike Mailman 2.1, Mailman 3 stores all it's list specific data in a database. The database contains data for all lists, so backing up all lists would be a backup procedure for the database which depends on the database manager, i.e., sqlite, MySQL/MariaDB or PostgreSQL. A procedure to backup/restore a single list would require a script to extract/restore the data for that list from the DB. There is an open issue for this at https://gitlab.com/mailman/postorius/-/issues/13 -- 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"