Search results for "Postorius" - Mailman-users

Error Logging - what changed with the New Year releases?

by Odhiambo Washington

Apart from all the defaults in settings.py (derived from gitlab), I also have this line: LOGGING['handlers']['file']['filename'] = '/opt/mailman/mm/var/logs/mailmanweb.log' Before the New Year releases of MM3, I used to get errors written to this file. Not anymore after I updated to the New Year releases. Another thing that I have realized is that prior to the New Year releases, I would get an error logged to that file and also mailed to me. I don't think that I have changed anything in settings,py related to logging. I have been trying to get signup with Twitter working. This used to generate an error that was both logged and emailed, but that isn't happening anymore. I have enabled other social auth providers (in settings.py) which I haven't configured in the admin panel. I expect that tying to use these on Postorius would generate an error that is logged and mailed to admin, but that too is not happening. Just checking out what might have changed - or if I am going nuts :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 6 months

Re: Create a mailman-web admin user

by Odhiambo Washington

On Tue, Jul 30, 2024 at 4:55 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/07/30 15:48, Roland Giesler via Mailman-users wrote: > > However, which user in the mailman user mentioned? > > > > I tried to do this as root, but login in as an admin doesn't give me > > any option to create new lists in postorius. What am I missing / > > doing wrong? > > > I seem to have solved the riddle. The "mailman-web createsuperuser" > command suggest the the mailman user is www-data, which I accepted. That > worked and I can now create a new list from Postorius. > Actually, it wasn't a riddle. You looked at documentation meant for the virtualenv <https://docs.mailman3.org/en/latest/install/virtualenv.html>installation method while your installation seems to be done from your OS package distribution. The OS package installation is fraught with pain. The virtualenv method is the officially recommended. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years

Unable to get mailman3 working on Ubuntu 20.04 LTS

by Michael Heseltine

Hi all, after upgrading an older server to Ubuntu 20.04, I tried to first upgrade my old mailman 2 installation to mailman 3. I've been on it for three weeks now, but unable to get anything working. I have long forgone the idea of upgrading and thus purged everything from mailman2 on my machine, and installed and removed mailman3 several times to no avail. My most recent try (it is currently an empty mailman installation) was done by calling apt install mailman3 mailman3-full mailman3-web and saying "yes" to every question. I'm using Mariadb as the database, and two databases called mailman3 and mailman3web (plus two users with the same names) have been created. I have configured a virtual host for apache (see below) and changed the mailman.cfg and mailman-weg.cfg to match (also see below). I have restarted both mailman3 and mailman3-web several times now, but when I try to access the site, I just get | Something went wrong | Mailman REST API not available. Please start Mailman core. plus an e-mail with subject | [Django] ERROR (EXTERNAL IP): Service Unavailable: /mailman3/postorius/lists/ I'm running | GNU Mailman 3.3.3b1 (Tom Sawyer) | Python 3.8.10 (default, Sep 28 2021, 16:10:42) Can anybody tell me what is going on? Also, the confirmation e-mail I got for registering a user says "example.com" in its subject line, even though I replaced every mention in the config files below with my actual URL. Any help is appreaciated, I can provide logs or other data on request. Cheers, michael /etc/mailman.mailman3.cfg ================== site_owner: postmaster@<site> noreply_address: noreply default_language: en sender_headers: from from_ reply-to sender email_commands_max_lines: 10 pending_request_life: 3d cache_life: 7d pre_hook: post_hook: layout: debian filtered_messages_are_preservable: no html_to_plain_text_command: /usr/bin/lynx -dump $filename listname_chars: [-_.0-9a-z] [shell] prompt: >>> banner: Welcome to the GNU Mailman shell use_ipython: no history_file: [paths.debian] var_dir: /var/lib/mailman3 queue_dir: $var_dir/queue bin_dir: /usr/lib/mailman3/bin list_data_dir: $var_dir/lists log_dir: /var/log/mailman3 lock_dir: $var_dir/locks data_dir: $var_dir/data cache_dir: $var_dir/cache etc_dir: /etc/mailman3 ext_dir: $var_dir/ext messages_dir: $var_dir/messages archive_dir: $var_dir/archives template_dir: $var_dir/templates pid_file: /run/mailman3/master.pid lock_file: $lock_dir/master.lck [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:<password>@localhost/mailman3?charset=utf8&use_unicode=1 debug: no [logging.debian] format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: info path: mailman.log [webservice] hostname: <site> port: 8001 use_https: yes show_tracebacks: yes api_version: 3.1 admin_user: restadmin admin_pass: <pass> [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: python:mailman.config.exim4 virtual host in Apache =============== <VirtualHost <site>:443> AssignUserID www-data www-data ServerAdmin webmaster@<site> ServerName <site> SSLEngine on DocumentRoot /webspace/mailman/www ErrorLog /var/log/apache2/mm3_error_log TransferLog /var/log/apache2/mm3_access_log 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 /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/<site>/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/<site>/privkey.pem </VirtualHost> /etc/mailman3/mailman-web.cfg ========================= SECRET_KEY = <secret> ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) ALLOWED_HOSTS = [ #"localhost", # Archiving API from Mailman, keep it. # "lists.your-domain.org", # Add here all production URLs you may have. '*' ] MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = <secret> MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', ) DATABASES = { 'default': { # Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'. 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': <passwd>, 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { # Set sql_mode to 'STRICT_TRANS_TABLES' for MySQL. See # https://docs.djangoproject.com/en/1.11/ref/ # databases/#setting-sql-mode 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", }, } } USE_X_FORWARDED_HOST = True LANGUAGE_CODE = 'en-us' TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_TZ = True EMAILNAME = '<site>' DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) SERVER_EMAIL = 'root@{}'.format(EMAILNAME) ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" SOCIALACCOUNT_PROVIDERS = { } COMPRESS_OFFLINE = True POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/'

4 years, 9 months

Re: Mail going to Held Messaging even the moderation is set to Accept Immediately

by Mark Sapiro

On 7/21/20 8:09 AM, Shashikanth Komandoor wrote: > > As per my understanding on Mailman 3, if the moderation attribute is > set to "Accept immediately (bypass all other rules)" then without checking > any rules, it should be delivered to the recipients of the list > irrespective of the message or body of the message but is there any such > checking if the body content or subject or any thing else is checked even > if the moderation bit is set to "Accept immediately". Member moderation Accept Immediately does not bypass ALL rules. It only bypasses those rules after member-moderation. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. However, I don't think that's the issue here. I think the issue is the poster is both an owner and a member. There is an issue in Postorius such that in cases like this, setting the member's moderation action actually sets that of the owner which has no effect on posting. See <https://gitlab.com/mailman/mailman/-/issues/659> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Re: spanish localization

by Mark Sapiro

On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > very significant date for me (it is my wedding anniversary) and I'm 90% > sure that I dedicated time to Weblate after that date... With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical. If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>. > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, after > updating to the latest releases, are still in Englanish (more English than > Spanish). > > This is not a fight, we want to help, but do not know how. And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Mass subscribe operation fails with http error

by Stephen J. Turnbull

b.watts(a)ucl.ac.uk writes: > I have reviewed similar threads, including: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… In that thread, it appears that there is some kind of deadlock going on, and increasing the number of gunicorn workers. The configuration for gunicorn is usually in /etc/mailman3/gunicorn.conf, and the line to add or update would be "workers = 3". See https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-guni…, which recommends workers = "ncores + 1". > I have updated the config in: > /etc/mailman3/settings.py > to contain: > POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk' After accessing your external webserver, this is just going to get routed to the internal WSGI server for Postorius, usually "http://127.0.0.1:8000" if you are running Postorius/mailmanweb on the same host as Mailman core. (This is defined in the "bind" parameter in gunicorn.conf if you have a different configuration.) There's no reason to route through the external webserver (I'm not sure why Mark suggested it in that thread, except maybe to test if changing the URL and recreating the template would help). -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 1 week

Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 06/08/2019 09:48, Phil Thompson wrote: > On 06/08/2019 03:38, Abhilash Raj wrote: >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >>> I'm in the process of setting up mailman3. The only problem I seem to >>> be >>> having is getting Hyperkitty to archive messages. Rather than the >>> authorisation problems people have previously asked about on the >>> list, I >>> am getting a 403 error... >>> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >>> <html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >>> <html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> >>> Any suggestions would be appreciated. >> >> How did you install Hyperkitty? > > On Ubuntu... > > apt-get install mailman3-full > >> You probably need to the set the API key correctly in both Core and >> Hyperkitty. >> >> Have you looked at documentation here[1]? >> >> [1]: >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> quotes, single or double, doesn't matter) in your settings.py for Web >> (Django) should be same as the `api_key : value` (without quotes here >> in hyperkitty.cfg config file). > > That's all correct. I'm familiar with the authorisation issues that > other people have had. > > The only thing I'm doing differently (as far as I am aware) is that > I'm using a URL prefixed with /mailman3 which is stripped off in my > nginx configuration... > > # mailman3. > location /mailman3/ { > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > include uwsgi_params; > uwsgi_param SERVER_ADDR $server_addr; > uwsgi_modifier1 30; > uwsgi_param SCRIPT_NAME /mailman3; > } > > location /mailman3/static { > alias /var/lib/mailman3/web/static; > } > > location /mailman3/static/favicon.ico { > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > } > > ...but I don't see this affecting the mailman to Hyperkitty > communication. Posting to lists and the Postorius and Hyperkitty > frontends seem to work fine. I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my public IP address). However I now get a 400 Bad Request error. I have traced this to the archive() function in hyperkitty/views/mailman.py which is expect a POST but is actually getting a GET, specifically... GET '/mailman3/hyperkitty/api/mailman/archive?key=...' ...which seems to be a fairly fundamental problem. Again, any suggestions would be welcome. Phil

7 years

Re: Changing subscription address

by Stephen J. Turnbull

Abhilash Raj writes: > The existing subscription workflow is a multi-step process that can be > paused and resumed. We pause when we send out a confirmation > email and then resume when that confirmation token is somehow > processed via email or API. So, post receiving the confirmation and > before actually subscribing, we can se the address as primary if the > user doesn’t have one and subscribe user as inhert. We don’t do any > of that if user already has chosen a primary address and it doesn’t > match the current address. OK, it sounds like we're thinking basically the same process, just using slightly different words to describe it (and mine have definitely been inaccurate about current logic at points, adding to the confusion :-P ). > Also, mass-subscribe and import does allow you to verify an address by > clicking this “Pre-verified” checkbox, which can be useful if you are > migrating from a different service or you exported a list of users from > somewhere you know to be valid. I wasn't aware of that. I haven't yet done a mass-subscribe from Postorius (I have a bunch of scripts for generating mailing lists from student rosters and just retargeted them to the REST API :-). Steve

5 years, 4 months

Re: Filter who can send on mailman3 list?

by Marcus Granath

It seems like the version used is: Postorius Version 1.1.2 The menus I can see are the following: Info Subscription requests Held messages Members Settings Mass operations Banned addresses Header filters Delete list And from the "Members" I can select "Subscribers", "Moderators", "Owners" - so I can manage to delete "subscribers" and add somebody as Moderator or Owner for my list. But I cannot find anywhere to set or add something like "non-member". What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). Or can I use some other API (then the web-page) to do that kind of operation? ;-)

5 years, 3 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: > > This is all because you are using the Ubuntu 18.04 package which is > about 4 years out of date and is from the era where HyperKitty, > Postorius and django_mailman3 still ran under Python 2.1.7. > > Unless you want to remove the Ubuntu package and install everything > with > pip, you need to just stick with what you have that at least partly > works and we'll try to determine how to fix the utf8mb4 issue. Hi Mark, You're a very patient soul. Thank you. Yes, I'm resigned to exactly that. The archives when folks send emojis will break, but that's just life. Mail will get sent. Heck, I guess I could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to get rid of the emoji in the worst case... Once I've migrated my 1500 mailing lists (this weekend) to the server, I'll think about how to get a new server set up that I can shift to and I'll install that with pip, since that'll clearly give me something more supportable. Is Ubuntu 20.04 a reasonable platform for that? Cheers, David

5 years, 5 months

Mailman-users search results for query "Postorius"