Search results for "Postorius" - Mailman-users

Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

7 years, 10 months

Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/19/20 6:42 AM, Torge Riedel wrote: > > One final question: When adding a new header filter I can select between > different actions. And there is one named "Default Anti-Spam action" > (roughly translated from German). I cannot find anything else about this > somewhere else in the settings (Postorius). So what it is the "Default > Anti-Spam action"? There is a configuration setting with default [antispam] jump_chain: hold "Default Anti-Spam action" should set the action for that rule to None which means use the configured [antispam]jump_chain: value. However, there is a bug in REST in core that doesn't allow setting `None` so you can't chose that setting anyway. See <https://gitlab.com/mailman/mailman/issues/671>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Thanks Mark for your time. I will follow your recommendation and try mailman bundler again, with care so that new conflicts won't occur as happened yesterday. Mailman bundler docs, in the first paragraph, refer to combined installation of GNU Mailman, Postotius, and Hyperkitty. Does that mean that mailman.client will be installed later separately? My CentOs 7 distribution does not offer python3.4.pip. https://pypi.python.org/pypi/pip offers pip 8.1.2 in two versions: Python Wheel pip-8.1.2-py2.py3-none-any.whl (md5, pgp) Source pip-8.1.2.tar.gz (md5, pgp) Which one should I choose? I also notice that postfix is required. yum offers the following options: pcp-pmda-postfix.x86_64 : Performance Co-Pilot (PCP) metrics for the Postfix (MTA) postfix.x86_64 : Postfix Mail Transport Agent postfix-perl-scripts.x86_64 : Postfix utilities written in perl postfix-sysvinit.noarch : SysV initscript for postfix spamass-milter-postfix.noarch : Postfix support for spamass-milter postgrey.noarch : Postfix Greylisting Policy Server pypolicyd-spf.noarch : SPF Policy Server for Postfix (Python implementation) sqlgrey.noarch : Postfix grey-listing policy service Which of these options are useful? Which ones are unnecessary? Again, thanks very much for your time and hope that the other subscribers in this list find this thread adequate. Haven't found the link on our distribution list profile settings for uploading an avatar. Best regards, Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) 2016-05-28 14:06 GMT-04:00 Mark Sapiro <mark(a)msapiro.net>: > On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > > > In order to avoid compatibility issues, I reinstalled CentOs 7. > Firewalld, Apache and BIND are operational. I also installed Python 3.4 at > http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; > however I understand that Python 2.7 is still available and am confused > about usage of each version. > > > Mailman 3 consists of several pieces. There is a core engine which is > Python 3. The core does the basic email list management and exposes many > options and settings via a RESTful API. > > There is also mailman.client which provides Python bindings for the REST > API. This is Python 2. > > We also provide a web management UI, Postorius and an archiver, > HyperKitty. These are Django applications and all of this is Python 2. > > There are other pieces as well. > > > > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if > you quickly let me know how to install it. I do not wish to use mailman > bundler. > > > This is only the core. You can install it with > > python3 setup.py install > > either in a python 3 virtualenv or not, but this will only give you the > core. > > I suggest you see the docs at <http://docs.list.org/en/latest/>, and if > you don't want to use bundler, see > <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the > recommended way to set up a working, non-development Mailman suite. > > In short, the core requires Python 3.4, most of the rest of the suite > requires Python 2.7 because of dependencies not yet ported to Python 3. > > -- > 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/ >

9 years, 2 months

Messages not picking up header or footer template

by benjamin＠tougshire.com

Hi I can't figure out how to get headers or footers on my messages Example: I create a footer in Postorius. The name in the form is '[list:member:regular:footer] - The footer for a regular (non-digest) message.' The data is 'Test Footer' I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… I can do a wget on that uri and download a copy of the footer, and it looks right But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message So what am I doing wrong? Thank you Ben

2 years, 5 months

Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 01:55, Élodie BOSSIER via Mailman-users wrote: > Thank you for your response Mark, > > With Mailman 2.1, the lists were split on their webpage respectively. > How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? > > My domain table SQL have this result : > id, mail_host, description, alias_domain > 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr > 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr If you go to https://example.com/mailman3/domains/ (the Domains view in Postorius) you will see at least two entries, one with Mail Host ml.franceserv.fr and one with Mail Host ml.viticreation.fr. What are the Web Host entries for these? You should have two separate site entries in the django_site table (https://example.com/admin/sites/site/) for these domains. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Re: MM3 gateway errors and frequent reboot needs

by Mark Sapiro

On 4/19/20 1:21 PM, hansen(a)rc.org wrote: > We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? We are not seeing an issue like this on either lists.mailman3.org (this list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) What are you seeing in web server logs? -- 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: Disable user registration

by Stephen J. Turnbull

jens.guenther(a)posteo.de writes: > Same question here :-) This is not a simple question. Mailman is built from the ground up on the assumption that users sign up. Making sign-up easy and powerful is the raison d'etre of Mailman. One obvious approach is to add "^.$" to each list's ban list (eventually that should be configurable as a list style, so "easy" to make domainwide or sitewide), but that doesn't stop people from creating users via Postorius. One way to address that would be to clean out users with no subscriptions once a week or so. I guess you could go into the templates and remove the accounts/signup/ links everywhere if "denial by obscurity" is enough, or into urls.py and send that URL to a "Get out of here you hacker!" view. Since these interventions are global, though, so the desideratum of "no site admin intervention" is right out. Users are site-global.

4 years, 4 months

Re: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 09:18, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > this is with "Postorius Version 1.2.4" (as installed by the mailman3 > Debian package). The Debian packages are OK for people who want to install things via a package manager, but they are quite out of date. Something like the following in `mailman shell` can do it. ``` >>> # Cutoff date delete pended subscriptions older than this >>> cutoff = '2022-03-01' >>> pendings = getUtility(IPendings) >>> # Prior to Mailman core 3.3.5 need to explicitly delete workflow >>> wfm = getUtility(IWorkflowStateManager) >>>for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['when'] >= cutoff: ... continue ... pendings.confirm(token, expunge=True) ... # for MM < 3.3.5 ... wfm.discard(token) ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: User cannot reset password

by Mark Sapiro

On 8/11/24 11:27, Greg Newby wrote: > > 1. Will the new (Django) and imported (Postorius) usernames automatically > be matched to the same email address? > > The goal is for someone to use the web-based front end to manage their > migrated subscriptions. Yes, The user creates an account with one of their MM 2.1 email addresses and adds any other MM 2.1 addresses to that account. That account will be associated with all their list subscriptions. > 2. How can I customize the email that went to users who selected "Forgot > password?" ( > > You are receiving this email because you, or someone else, tried to access > an account with email > > > I didn't find that string in the source code. It comes from Django-allauth. See allauth/templates/account/email/unknown_account_message.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

multiple sites on a mailman3 server question

by William Oliver

So, I have successfully installed mailman3 and it's working great. However, the way it works now, if someone goes to the domain website, he or she will get the mailman page. I'd prefer that it work something like: My www.example.com goes to a home page lists.example.com goes to the mailman3 page mail.example.com goes to a roundcube page I'm using nginx, and this is the first time I've set up an nginx server (I have traditionally done apache), and I'm still figuring out the syntax. My sites-available file is below, for the domain emergenus.com. The behavior I'm getting is that if I go to mail.emergenus.com, it still redirects to mail.emergenus.com/mailman3/lists, but gives a 404 page not found. If I go to lists.emergenus.com, it redirects to lists.emergenus.com/mailman3/lists and gives the nice postorius page, and works fine. So, I'm trying to figure out how to stop that redirect. When I look at my nginx access.log file for mail.emergenus.com, I see: 174.212.104.153 - - [28/Dec/2021:21:03:21 -0500] "GET /mailman3/lists/ HTTP/1.1" 404 188 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36" Aha! says I. My ip address is 203.159.80.234, not 174.212.104.153. Thus, uwsgi (I think) is sneaking in there and taking over regardless of what I'm trying to do. Is there a way to tell mailman to only take over for lists.emergenus.com and not for www.emergenus.com or mail.emergenus.com? Here's my uwsgi.ini (without then env= PYTHONPATH change discussed in another thread: # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log Here's my /etc/nginx/sites-enabled/emergenus.com looks like: server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name emergenus.com, mail.emergenus.com, www.emergenus.com; location /{ try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.emergenus.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } listen 443 ssl ; listen [::]:443 ssl ; location /static/ { alias /opt/mailman/web/static/; } ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = mail.emergenus.com) { # return 301 https://$host$request_uri; return 301 https://mail.emergenus.com; } # managed by Certbot if ($host = www.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.emergenus.com lists.emergenus.com mail.emergenus.com emergenus.com; return 404; # managed by Certbot } Thanks billo

3 years, 7 months

Mailman-users search results for query "Postorius"