- Mailman-users - lists.mailman3.org

Creating and placing custom templates
by kelly.close＠lrewater.com 02 May '19

02 May '19

I know there are previous threads related to this topic but none were very recent so I thought I'd start a new one. I've referenced two of the old ones below. I am attempting to implement a custom footer on one of my lists. This seems like it should be straightforward but I'm clearly doing something wrong, since the default footer keeps coming through despite my efforts. I've referenced the docs as well as these two posts, to no avail. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Here's what I'm doing: I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ In that folder I created the following folders and made sure they were properly owned (by list:list) /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". I have two of my own emails subscribed t my "f2p2-test" list at the domain udfcd-lists.org. When I post to the list, and check my other email for the disseminated post, it still has the default footer. I have restarted the mailman3 service. Can anyone spot an obvious error here or offer troubleshooting suggestions? Thank You! ~Kelly

2 1

We're in Season of Docs!
by Stephen J. Turnbull 01 May '19

01 May '19

So, we're in Season of Docs! Currently, Abhilash and I are registered as mentor/admins. I don't think we need more admins, but more mentors is always a good thing. Hey, users! You don't need to be a programmer to mentor docs, of course, and it may be a *good* thing to *not* be a programmer and even *not* a Mailman developer. :-) Suggestions as to doc projects we *really oughtta do!* are very welcome. (I can't believe we got in with the thin doc proposal I put together literally at the last minute, but here we are. ;-) Feel free to get in touch with us on mailman-developers (reply-to set; please respect) if you're interested in mentoring. Or if you prefer you can contact me or Abhilash directly. We can presumably add mentors up to July 23 (deadline for technical writer selection by orgs). For more information: https://wiki.list.org/DEV/SeasonOfDocs2019 https://developers.google.com/season-of-docs/ https://developers.google.com/season-of-docs/docs/participants/ https://developers.google.com/season-of-docs/docs/timeline Regards, Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

1 0

GDPR - save subscriptions confirmation emails
by contact＠maadix.net 01 May '19

01 May '19

Hi, I am new in the list. I have been looking for this topic in the archives in order to avoid duplicate, but I could not find any thread. According to the new GDPR rules, lists owners need to have a confirmation from subscribers, and this is easy to do with Mailman 3. What I can't figure out is how to save all the confirmation emails received from users. I only see the confirmations commands emails in the logs, Is there another place/way to store them? For GDPR compliance it is important to be able to demonstrate that you received the confirmation, in case you may need it in the future. Bests Maddish -- *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

3 4

HTML email sent to lists migrated from Mailman 2.1
by Nate Coraor 16 Apr '19

16 Apr '19

Hello all, I have some lists migrated from 2.1 that are stripping the HTML parts (perhaps all attachments?) from messages despite the options to do so not being enabled and lynx not even being installed. I'm trying to get a new list to behave the same way so I can figure out what's going on without spamming a production list, but have been unsuccessful: despite setting nearly all the list options the same as the old lists, new lists pass HTML portions and attachments just fine. I've verified the settings using mailing list objects directly with `mailman withlist` on the command line and the only differences are things that I can't imagine would be related like admin_notify_mchanges, advertised, and archive_policy. Are there are really old options that can't be accessed via mailing list objects obtained with `withlist` on the command line? Thanks, --nate

3 3

Mailman in EC2 / Docker -- working but HTTPS not serving static content
by roger.hislop＠is.co.za 15 Apr '19

15 Apr '19

Hi again ... I got everything working thanks to Danil, Abhilash, and finally found a simple NGINX conf that worked, using WSGI. Cool. Set up certificates using LetsEncrypt, used another conf to set up SSL, like the conf pasted below. I edited nginx.conf so that it only takes server config from the nginx/conf.d/blahblah.conf below. This works for HTTP, HTTPS works but it (apparently) is not serving static content. There are loads of how-tos to get this to work, but I've failed in all -- it seems to be the static path (I've not tried option using thttpd I've not tried as there is no easy install onto AQWS AMI and it seems like it's not specifically necessary. I'm so close... so close... ------------------------------- server { listen 80 default_server; # listen [::]:80 default_server ipv6only=on; root /usr/share/nginx/html; index index.html index.htm; server_name listman.iotcouncil.org.za; return 301 https://$server_name$request_uri; #<< AUTO_REDIRECT HTTP TO HTTPS # location / { # proxy_pass http://172.19.199.3:8000/; # 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; # } # # location /static/ { # alias /var/spool/mailman-web/static/; # } # # location /robots.txt { # alias /var/spool/mailman-web/static/hyperkitty/robots.txt; # } # # location /favicon.ico { # alias /var/www/listorg/images/favicon.ico; # } # } server { listen 443 default_server; # listen [::]:443 default_server ipv6only=on; #root /usr/share/nginx/html; #index index.html index.htm; server_name listman.iotcouncil.org.za; ssl on; ssl_certificate /etc/letsencrypt/live/listman.iotcouncil.org.za/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/listman.iotcouncil.org.za/privkey.pem; ssl_session_timeout 5m; ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES"; ssl_prefer_server_ciphers on; location / { proxy_pass http://172.19.199.3:8000/; 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; } location /static/ { alias /opt/mailman/web/static; } location /robots.txt { alias /var/spool/mailman-web/static/hyperkitty/robots.txt; } location /favicon.ico { alias /var/www/listorg/images/favicon.ico; } }

4 3

Mailman Core 3.2.2 is now out
by Abhilash Raj 14 Apr '19

14 Apr '19

Hello Everyone, Mailman Core 3.2.2 is released and available on PyPI[1]. This is a regular bugfix release and I had to do that to fix a version constraint which pulled in a pre-release of a dependency (falcon) when installed via pip and caused the default install to break. There are few other changes included in this release, including a big refactor of error reporting in Core's REST API. All the error responses are now correctly formatted as JSON with more information about the error. For example, invalid inputs for Enum data types return the valid options. Other error message are now generated from the input validtor and will be more informative. REST API also accepts input as JSON formatted body, alongside the x-www-form-urlencoded. A full list of changes are available here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 This release supports Python 3.5-3.7. Thanks very much to all the contributors involved in this release. [1]: https://pypi.org/project/mailman/ -- thanks, Abhilash Raj (maxking)

2 3

List options question
by Phil Stracchino 13 Apr '19

13 Apr '19

So, I've just sucscribed to this list, and when I go to set subscription options, I find: Receive list copies (possible duplicates) Yes No When you are listed explicitly in the To: or Cc: headers of a list message, you can opt to not receive another copy from the mailing list. Select No to receive copies. Select Yes to avoid receiving copies from the mailing list. This seems rather ... backwards. "Receive copies? Answer no for yes, yes for no." Is that how the option actually works in mailman3, or is the text of the option decription garbled? -- Phil Stracchino Babylon Communications phils(a)caerllewys.net phil(a)co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958

2 1

Mailman3 in dockers on EC2 - running out of memory and puking ev.ry.where.
by roger.hislop＠is.co.za 11 Apr '19

11 Apr '19

Hi all -- really need some help. I'm tech literate, but definitely not a sysadmin or dev. I'm following the tutorial at "Olay's Farmland" at https://www.olay.xyz/2018/01/01/deploy-mailman-3-on-aws-using-docker/ which seems to be a clone of the same content here https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ Easy enough to get most of the way ... set up EC2 instance, configure SES and add DNS settings with DKIM etc. Set up Postfix, test it. All working groovy. I run through the how to all the way through setting up the containers and firing it up. This is where things start to get funky. Once the docker-compose is run, I run "curl http://172.19.199.3:8000/postorius/lists/" to test. First time it said it couldn't connect to database. So I nuked and restarted from scratch. Second time it said the same thing... was reading around the place and tried again, and then reran that curl and it worked -- gave me html from a page. But the VM started running slowly --taking forever to follow keypresses. Eventually became unresponsive. So I rebooted the machine via AWS console, and docker ps showed only the postgres db running. docker-compose ps shows Name Command State Ports ------------------------------------------------------------------------------------------ docker-mailman_database_1 docker-entrypoint.sh postgres Up 5432/tcp mailman-core docker-entrypoint.sh maste ... Exit 255 8001/tcp, 8024/tcp mailman-web docker-entrypoint.sh uwsgi ... Exit 255 8000/tcp, 8080/tcp So rebuilt the container -- same thing. It looks and feels like its running out of memory. I used the compose file from https://gist.githubusercontent.com/Yexiaoxing/833bfcc5d3e4e0c06a8b7f0bac7c4… (with appropriate edits). I have no idea how to proceed from here... Go to logs... Partial log (they're LONG) docker logs docker-mailman_database_1 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.utf8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /var/lib/postgresql/data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting dynamic shared memory implementation ... posix creating configuration files ... ok running bootstrap script ... ok sh: locale: not found performing post-bootstrap initialization ... No usable system locales were found. Use the option "--debug" to see details. ok syncing data to disk ... ok WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. Success. You can now start the database server using: pg_ctl -D /var/lib/postgresql/data -l logfile start waiting for server to start....LOG: database system was shut down at 2019-04-09 14:37:48 UTC LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started done server started CREATE DATABASE /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* LOG: received fast shutdown request LOG: aborting any active transactions LOG: autovacuum launcher shutting down LOG: shutting down waiting for server to shut down....LOG: database system is shut down done server stopped PostgreSQL init process complete; ready for start up. LOG: database system was shut down at 2019-04-09 14:37:50 UTC LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started ERROR: relation "social_auth_usersocialauth" does not exist at character 15 STATEMENT: SELECT 1 from social_auth_usersocialauth LOG: database system was interrupted; last known up at 2019-04-09 14:48:37 UTC LOG: database system was not properly shut down; automatic recovery in progress LOG: invalid record length at 0/1767BB8: wanted 24, got 0 LOG: redo is not required LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started LOG: received smart shutdown request LOG: autovacuum launcher shutting down LOG: shutting down LOG: database system is shut down LOG: database system was shut down at 2019-04-09 15:18:06 UTC LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started ERROR: duplicate key value violates unique constraint "auth_user_username_key" DETAIL: Key (username)=(lists) already exists. STATEMENT: INSERT INTO "auth_user" ("password", "last_login", "is_superuser", "username", "first_name", "last_name", "email", "is_staff", "is_active", "date_joined") VALUES ('!lS8pgTTV7CyhUbZItku00ZnUGxLQkVEuc3ENZKbV', NULL, true, 'lists', '', '', 'iotic-za(a)reasondigital.co.za', true, true, '2019-04-09T15:39:57.715036+00:00'::timestamptz) RETURNING "auth_user"."id" TopMemoryContext: 8192 total in 1 blocks; 3480 free (0 chunks); 4712 used smgr relation table: 24576 total in 2 blocks; 13008 free (4 chunks); 11568 used WAL record construction: 49768 total in 2 blocks; 6584 free (0 chunks); 43184 used Checkpointer: 8192 total in 1 blocks; 7992 free (3 chunks); 200 used PrivateRefCount: 8192 total in 1 blocks; 2840 free (0 chunks); 5352 used MdSmgr: 8192 total in 1 blocks; 8120 free (0 chunks); 72 used Pending ops context: 0 total in 0 blocks; 0 free (0 chunks); 0 used Pending Ops Table: 8192 total in 1 blocks; 2840 free (5 chunks); 5352 used LOCALLOCK hash: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used Timezones: 104120 total in 2 blocks; 2840 free (0 chunks); 101280 used ErrorContext: 8192 total in 1 blocks; 8152 free (0 chunks); 40 used Grand total: 235808 bytes in 13 blocks; 56632 free (12 chunks); 179176 used ERROR: out of memory DETAIL: Failed on request of size 4032. CONTEXT: writing block 0 of relation base/16384/16797 TopMemoryContext: 8192 total in 1 blocks; 3480 free (0 chunks); 4712 used smgr relation table: 24576 total in 2 blocks; 13008 free (4 chunks); 11568 used WAL record construction: 49768 total in 2 blocks; 6584 free (0 chunks); 43184 used Checkpointer: 8192 total in 1 blocks; 7992 free (2 chunks); 200 used PrivateRefCount: 8192 total in 1 blocks; 2840 free (0 chunks); 5352 used LOG: could not fork autovacuum worker process: Out of memory MdSmgr: 8192 total in 1 blocks; 8120 free (0 chunks); 72 used Pending ops context: 0 total in 0 blocks; 0 free (0 chunks); 0 used Pending Ops Table: 8192 total in 1 blocks; 2840 free (5 chunks); 5352 used LOCALLOCK hash: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used LOG: could not fork autovacuum worker process: Out of memory Timezones: 104120 total in 2 blocks; 2840 free (0 chunks); 101280 used ErrorContext: 8192 total in 1 blocks; 8152 free (0 chunks); 40 used Grand total: 235808 bytes in 13 blocks; 56632 free (11 chunks); 179176 used LOG: could not fork autovacuum worker process: Out of memory ERROR: out of memory DETAIL: Failed on request of size 4032. CONTEXT: writing block 0 of relation base/16384/16797 LOG: could not fork autovacuum worker process: Out of memory WARNING: could not write block 0 of base/16384/16797 DETAIL: Multiple failures --- write error might be permanent. TopMemoryContext: 8192 total in 1 blocks; 3480 free (0 chunks); 4712 used smgr relation table: 24576 total in 2 blocks; 13008 free (4 chunks); 11568 used WAL record construction: 49768 total in 2 blocks; 6584 free (0 chunks); 43184 used Checkpointer: 8192 total in 1 blocks; 7992 free (2 chunks); 200 used PrivateRefCount: 8192 total in 1 blocks; 2840 free (0 chunks); 5352 used MdSmgr: 8192 total in 1 blocks; 8120 free (0 chunks); 72 used Pending ops context: 0 total in 0 blocks; 0 free (0 chunks); 0 used Pending Ops Table: 8192 total in 1 blocks; 2840 free (5 chunks); 5352 used LOCALLOCK hash: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used TopMemoryContext: 51040 total in 4 blocks; 1344 free (1 chunks); 49696 used TopTransactionContext: 8192 total in 1 blocks; 6968 free (0 chunks); 1224 used Timezones: 104120 total in 2 blocks; 2840 free (0 chunks); 101280 used Statistics snapshot: 0 total in 0 blocks; 0 free (0 chunks); 0 used ErrorContext: 8192 total in 1 blocks; 8152 free (0 chunks); 40 used Grand total: 235808 bytes in 13 blocks; 56632 free (11 chunks); 179176 used Per-database function: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used Per-database table: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used Per-database function: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used Per-database table: 8192 total in 1 blocks; 776 free (0 chunks); 7416 used Databases hash: 24576 total in 2 blocks; 15072 free (5 chunks); 9504 used ERROR: out of memory For UWSGI cat uwsgi.log [pid: 49|app: 0|req: 1/1] 172.19.199.1 () {24 vars in 291 bytes} [Tue Apr 9 14:43:43 2019] GET /postorius/lists/ => generated 3710 bytes in 705 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 0) [pid: 39|app: 0|req: 1/1] 172.19.199.1 () {24 vars in 291 bytes} [Tue Apr 9 15:40:12 2019] GET /postorius/lists/ => generated 3710 bytes in 694 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 0) [ec2-user@ip-172-31-23-250 logs]$ cat uwsgi-error.log cat: uwsgi-error.log: Permission denied [ec2-user@ip-172-31-23-250 logs]$ sudo cat uwsgi-error.log *** Starting uWSGI 2.0.15 (64bit) on [Tue Apr 9 14:38:03 2019] *** compiled with version: 6.3.0 on 29 December 2017 00:16:31 os: Linux-4.14.77-70.59.amzn1.x86_64 #1 SMP Mon Nov 12 22:02:45 UTC 2018 nodename: mailman-web machine: x86_64 clock source: unix detected number of CPU cores: 1 current working directory: /opt/mailman-web detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! setgid() to 101 setuid() to 100 chdir() to /opt/mailman-web your processes number limit is 3860 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 Python version: 2.7.14 (default, Dec 19 2017, 17:52:21) [GCC 6.3.0] Python main interpreter initialized at 0x55ca1d90e1e0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds [uwsgi-cron] command "./manage.py runjobs minutely" registered as cron task [uwsgi-cron] command "./manage.py runjobs quarter_hourly" registered as cron task [uwsgi-cron] command "./manage.py runjobs hourly" registered as cron task [uwsgi-cron] command "./manage.py runjobs daily" registered as cron task [uwsgi-cron] command "./manage.py runjobs monthly" registered as cron task [uwsgi-cron] command "./manage.py runjobs weekly" registered as cron task [uwsgi-cron] command "./manage.py runjobs yearly" registered as cron task mapped 166144 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x55ca1d90e1e0 pid: 1 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 49, cores: 2) Tue Apr 9 14:38:04 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 51) [uwsgi-daemons] spawning "./manage.py qcluster" (uid: 100 gid: 101) 14:38:07 [Q] INFO Q Cluster-52 starting. 14:38:07 [Q] INFO Process-1 guarding cluster at 67 14:38:07 [Q] INFO Process-1:1 ready for work at 68 14:38:07 [Q] INFO Process-1:3 pushing tasks at 70 14:38:07 [Q] INFO Q Cluster-52 running. 14:38:07 [Q] INFO Process-1:2 monitoring at 69 [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 51 exited after 4 second(s) Tue Apr 9 14:39:04 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 71) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 71 exited after 269 second(s) Tue Apr 9 14:43:33 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 79) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 79 exited after 3 second(s) Tue Apr 9 14:51:35 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 89) *** Starting uWSGI 2.0.15 (64bit) on [Tue Apr 9 15:39:58 2019] *** compiled with version: 6.3.0 on 29 December 2017 00:16:31 os: Linux-4.14.109-80.92.amzn1.x86_64 #1 SMP Mon Apr 1 23:07:39 UTC 2019 nodename: mailman-web machine: x86_64 clock source: unix detected number of CPU cores: 1 current working directory: /opt/mailman-web detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! setgid() to 101 setuid() to 100 chdir() to /opt/mailman-web your processes number limit is 3860 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 Python version: 2.7.14 (default, Dec 19 2017, 17:52:21) [GCC 6.3.0] Python main interpreter initialized at 0x562e2c0b11e0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds [uwsgi-cron] command "./manage.py runjobs minutely" registered as cron task [uwsgi-cron] command "./manage.py runjobs quarter_hourly" registered as cron task [uwsgi-cron] command "./manage.py runjobs hourly" registered as cron task [uwsgi-cron] command "./manage.py runjobs daily" registered as cron task [uwsgi-cron] command "./manage.py runjobs monthly" registered as cron task [uwsgi-cron] command "./manage.py runjobs weekly" registered as cron task [uwsgi-cron] command "./manage.py runjobs yearly" registered as cron task mapped 166144 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x562e2c0b11e0 pid: 1 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 39, cores: 2) Tue Apr 9 15:39:59 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 41) [uwsgi-daemons] spawning "./manage.py qcluster" (uid: 100 gid: 101) 15:40:02 [Q] INFO Q Cluster-43 starting. 15:40:02 [Q] INFO Process-1:1 ready for work at 58 15:40:02 [Q] INFO Process-1:2 monitoring at 59 15:40:02 [Q] INFO Process-1 guarding cluster at 57 15:40:02 [Q] INFO Process-1:3 pushing tasks at 60 15:40:02 [Q] INFO Q Cluster-43 running. [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 41 exited after 4 second(s) Tue Apr 9 15:40:59 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 63) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 63 exited after 13 second(s) Tue Apr 9 15:41:59 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 71) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 71 exited after 33 second(s) Tue Apr 9 15:42:59 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 79) 16:33:36 [Q] ERROR could not translate host name "database" to address: Try again 16:35:17 [Q] INFO Process-1:3 stopped pushing tasks 16:35:25 [Q] ERROR reincarnated pusher Process-1:3 after sudden death 16:35:25 [Q] INFO Process-1:4 pushing tasks at 87 [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 79 exited after 3146 second(s) Tue Apr 9 16:35:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 88) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 88 exited after 3 second(s) Tue Apr 9 16:36:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 96) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 96 exited after 3 second(s) Tue Apr 9 16:37:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 104) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 104 exited after 3 second(s) Tue Apr 9 16:38:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 112) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 112 exited after 3 second(s) Tue Apr 9 16:39:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 120) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 120 exited after 3 second(s) Tue Apr 9 16:40:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 128) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 128 exited after 3 second(s) Tue Apr 9 16:41:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 136) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 136 exited after 3 second(s) Tue Apr 9 16:42:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 144) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 144 exited after 3 second(s) Tue Apr 9 16:43:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 152) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 152 exited after 3 second(s) Tue Apr 9 16:44:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 160) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 160 exited after 3 second(s) Tue Apr 9 16:45:00 2019 - [uwsgi-cron] running "./manage.py runjobs quarter_hourly" (pid 168) [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running with pid 168 exited after 2 second(s) Tue Apr 9 16:45:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 176) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 176 exited after 3 second(s) Tue Apr 9 16:46:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 184) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 184 exited after 2 second(s) Tue Apr 9 16:47:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 192) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 192 exited after 3 second(s) Tue Apr 9 16:48:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 200) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 200 exited after 3 second(s) Tue Apr 9 16:49:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 208) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 208 exited after 3 second(s) Tue Apr 9 16:50:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 216) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 216 exited after 3 second(s) Tue Apr 9 16:51:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 224) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 224 exited after 3 second(s) Tue Apr 9 16:52:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 232) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 232 exited after 3 second(s) Tue Apr 9 16:53:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 240) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 240 exited after 2 second(s) Tue Apr 9 16:54:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 248) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 248 exited after 2 second(s) Tue Apr 9 16:55:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 256) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 256 exited after 3 second(s) Tue Apr 9 16:56:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 264) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 264 exited after 3 second(s) Tue Apr 9 16:57:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 272) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 272 exited after 3 second(s) Tue Apr 9 16:58:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 280) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 280 exited after 3 second(s) Tue Apr 9 16:59:25 2019 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 288) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 288 exited after 3 second(s) Tue Apr 9 17:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs quarter_hourly" (pid 296) Tue Apr 9 17:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs hourly" (pid 297) Traceback (most recent call last): File "./manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line Traceback (most recent call last): File "./manage.py", line 10, in <module> execute_from_command_line(sys.argv) utility.execute() File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 337, in execute utility.execute() File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 337, in execute django.setup() django.setup() File "/usr/local/lib/python2.7/site-packages/django/__init__.py", line 27, in setup File "/usr/local/lib/python2.7/site-packages/django/__init__.py", line 27, in setup apps.populate(settings.INSTALLED_APPS) apps.populate(settings.INSTALLED_APPS) File "/usr/local/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate File "/usr/local/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate app_config.import_models() app_config.import_models() File "/usr/local/lib/python2.7/site-packages/django/apps/config.py", line 202, in import_models File "/usr/local/lib/python2.7/site-packages/django/apps/config.py", line 202, in import_models self.models_module = import_module(models_module_name) self.models_module = import_module(models_module_name) File "/usr/local/lib/python2.7/importlib/__init__.py", line 37, in import_module File "/usr/local/lib/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) __import__(name) File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/__init__.py", line 28, in <module> File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/__init__.py", line 28, in <module> from .email import Email, Attachment from .email import Email, Attachment File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/email.py", line 37, in <module> File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/email.py", line 37, in <module> from hyperkitty.lib.analysis import compute_thread_order_and_depth from hyperkitty.lib.analysis import compute_thread_order_and_depth File "/usr/local/lib/python2.7/site-packages/hyperkitty/lib/analysis.py", line 28, in <module> File "/usr/local/lib/python2.7/site-packages/hyperkitty/lib/analysis.py", line 28, in <module> import networkx as nx import networkx as nx File "/usr/local/lib/python2.7/site-packages/networkx/__init__.py", line 114, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/__init__.py", line 114, in <module> import networkx.generators import networkx.generators File "/usr/local/lib/python2.7/site-packages/networkx/generators/__init__.py", line 6, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/generators/__init__.py", line 6, in <module> from networkx.generators.classic import * from networkx.generators.classic import * File "/usr/local/lib/python2.7/site-packages/networkx/generators/classic.py", line 26, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/generators/classic.py", line 26, in <module> from networkx.algorithms.bipartite.generators import complete_bipartite_graph from networkx.algorithms.bipartite.generators import complete_bipartite_graph File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/__init__.py", line 57, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/__init__.py", line 57, in <module> import networkx.algorithms.connectivity import networkx.algorithms.connectivity File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/connectivity/__init__.py", line 3, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/connectivity/__init__.py", line 3, in <module> from .connectivity import * from .connectivity import * File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/connectivity/connectivity.py", line 13, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/connectivity/connectivity.py", line 13, in <module> from networkx.algorithms.flow import boykov_kolmogorov from networkx.algorithms.flow import boykov_kolmogorov File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/flow/__init__.py", line 1, in <module> File "/usr/local/lib/python2.7/site-packages/networkx/algorithms/flow/__init__.py", line 1, in <module> from .maxflow import * from .maxflow import * MemoryErrorMemoryError 18:16:37 [Q] ERROR could not translate host name "database" to address: Try again ...etc ... For Mailman cat mailmanweb.log ERROR 2019-04-09 20:05:48,878 934 hyperkitty.lib.utils Failed to update the fulltext index: could not translate host name "database" to address: Try again Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/hyperkitty/lib/utils.py", line 186, in run_with_lock fn(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/search_indexes.py", line 87, in update_index update_cmd.update_backend("hyperkitty", "default") File "/usr/local/lib/python2.7/site-packages/haystack/management/commands/update_index.py", line 240, in update_backend total = qs.count() File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 363, in count return self.query.get_count(using=self.db) File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/query.py", line 498, in get_count number = obj.get_aggregation(using, ['__count'])['__count'] File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/query.py", line 479, in get_aggregation result = compiler.execute_sql(SINGLE) File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 874, in execute_sql cursor = self.connection.cursor() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 254, in cursor return self._cursor() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 229, in _cursor self.ensure_connection() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 213, in ensure_connection self.connect() File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 213, in ensure_connection self.connect() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 189, in connect self.connection = self.get_new_connection(conn_params) File "/usr/local/lib/python2.7/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection connection = Database.connect(**conn_params) File "/usr/local/lib/python2.7/site-packages/psycopg2/__init__.py", line 130, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) OperationalError: could not translate host name "database" to address: Try again ERROR 2019-04-09 20:15:08,192 983 hyperkitty.lib.utils Failed to update the fulltext index: could not translate host name "database" to address: Try again Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/hyperkitty/lib/utils.py", line 186, in run_with_lock fn(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/search_indexes.py", line 87, in update_index update_cmd.update_backend("hyperkitty", "default") File "/usr/local/lib/python2.7/site-packages/haystack/management/commands/update_index.py", line 240, in update_backend total = qs.count() File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 363, in count return self.query.get_count(using=self.db) File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/query.py", line 498, in get_count number = obj.get_aggregation(using, ['__count'])['__count'] File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/query.py", line 479, in get_aggregation result = compiler.execute_sql(SINGLE) File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 874, in execute_sql cursor = self.connection.cursor() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 254, in cursor return self._cursor() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 229, in _cursor self.ensure_connection() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 213, in ensure_connection self.connect() File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 213, in ensure_connection self.connect() File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 189, in connect self.connection = self.get_new_connection(conn_params) File "/usr/local/lib/python2.7/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection connection = Database.connect(**conn_params) File "/usr/local/lib/python2.7/site-packages/psycopg2/__init__.py", line 130, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) OperationalError: could not translate host name "database" to address: Try again

3 3

Simplified installation instructions
by Frank Yappa 08 Apr '19

08 Apr '19

I've looked at installing Mailman3 many times but have never succeeded - there simply too many instructions. Is there a simple guide to get just web front end to Mailman3 where you can import an existing mailing list simply for viewing? Which is the easiest system to install Mailman3 on? I have a Debian system and would be grateful for any pointers showing how to install it . I came across:- https://iomarmochtar.wordpress.com/2017/07/21/mailman3-easy-installation/ but this is for Centos and I don't know what to change. Elsewhere I came across a list of apps which needed to be installed on Debian but that didn't work because of missing packages. apt-get install python3-setuptools python3-virtualenv python3-dev git gcc node-less nodejs postfix python3-tox

2 1

easy way to delete old mails in hyperkitty?
by l.schimmer＠cgv.tugraz.at 08 Apr '19

08 Apr '19

Hi! is thjere a easy way to delete old mails in hyperkitty? e.g. with a list and checkmarks, or via a cli command? We got several mailinglists and we did import them from mailman2.x into mailman 3.2. Now it is time to remove old posts before 2016. But I do not see a easy way to remove old posts in one go, just the "remove thread" button in each mail view. thank you, Lars

2 1