January 2019 - Mailman-users - lists.mailman3.org

Issue with mySQLdb-module on Debian
by Bjoern Franke 24 Jan '19

24 Jan '19

Hi, I already opened a debian bugreport for it, but I'm still wondering why the following issue appears: File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 30, in <module> 'Did you install mysqlclient or MySQL-python?' % e django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: No module named 'MySQLdb'. Did you install mysqlclient or MySQL-python? python3-pymysql, which is a dependency of mailman3-web and provides mySQLdb, is installed. (Maybe it's time to migrate to postgres.) Kind regards Bjoern

3 4

importing from google groups.
by Abhijith PA 23 Jan '19

23 Jan '19

Hello. Is it possible to import google group archives to mailman3. With this[1] script, I was able to export archives. Please let me know if anyone have tried and succeeded. --abhijith [1] - https://github.com/icy/google-group-crawler

2 1

MAILMAN_HOST_IP_AUTO
by Johannes Winter 22 Jan '19

22 Jan '19

Dear MM3 list, while doing some reboot proofing for our mailman setup, I once more ran into https://github.com/maxking/docker-mailman/issues/133. May it be that https://github.com/maxking/docker-mailman/pull/143 hasn't made it yet into the docker image maxking/mailman-web:0.2 which is the current recommended stable version? Would be real nice (for stability!) to have this feature included. Best regards, Johannes Winter

2 1

MAILMAN_HOST_IP_AUTO
by Johannes Winter 22 Jan '19

22 Jan '19

Dear MM3 list, while doing some reboot proofing for our mailman setup, I once more ran into https://github.com/maxking/docker-mailman/issues/133. May it be that https://github.com/maxking/docker-mailman/pull/143 hasn't made it yet into the docker image maxking/mailman-web:0.2 which is the current recommended stable version? Would be real nice (for stability!) to have this feature included. Best regards, Johannes Winter

1 0

MIME Digests with posts and index inline likewise Plain Text Digests
by Henrik Rasmussen 18 Jan '19

18 Jan '19

Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. Would it be possible for Mailman to send both posts and index inline in the MIME digest? I am pretty sure it's not a feature yet, but if Mailman would be able to, I will submit an issue in core (I presume). /Henrik Rasmussen

2 1

Re: digests are created but not sent out
by "Jörg M. Schulz" 17 Jan '19

17 Jan '19

Well, the template files seem to reside in the database, not on the filesystem. So maybe there is some other issue here?

1 0

Change domain, easy?
by Thor Atle Rustad 14 Jan '19

14 Jan '19

Hello list, How can I change the domain (from spammedtodeath.example.org to newdomain.example.org. The change should apply to all relevant settings as well as existing lists. Sincerely, Thor Atle Rustad

2 1

MM3 Docker
by Odhiambo Washington 11 Jan '19

11 Jan '19

[Requesting everyone to be patient with me because I am not so good with Linux, Docker is a completely new thing to me, and MM3, well....] So, I have a VM running Ubuntu-18.04. It is in a Data Centre somewhere. It has an IP n.n.n.n (a public IP). Also, it does not have high resources. However, I hope I can at least get to install MM3 and test it using https://asynchronous.in/docker-mailman/ If I could run MM3 using the apt-get install method, perhaps that would have made my life a bit easier, hoping that MM3 can actually be run in parallel with MM2.1 on the same host. Is anyone doing that already?? Anyway, I need some hand-holding using the docker method for now. I am reading the steps as documented on the https://asynchronous.in/docker-mailman/ and somethings aren't clear to me: I have created two files: (a) /opt/mailman/web/settings_local.py: SERVE_FROM_DOMAIN: 'mm3.my.co.ke' ALLOWED_HOSTS: 'my.co.ke' HYPERKITTY_API_KEY: 'Whatever' MAILMAN_ADMIN_USER: 'admin' MAILMAN_ADMIN_EMAIL: 'odhiambo(a)gmail.com' SECRET_KEY: 'Whatever' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '172.19.199.1' EMAIL_PORT = 25 (b) /opt/mailman/core/mailman-extra.cfg HYPERKITTY_API_KEY: 'Whatever' DATABASE_URL: 'mysql+pymysql://mailman:mailmanpass@database/mailmandb' DATABASE_TYPE: 'mysql' DATABASE_CLASS: 'mailman.database.mysql.MySQLDatabase' Questions: Are the formats correct? Do I use quotes or not? My docker-compuse.yaml: version: '2' services: mailman-core: image: maxking/mailman-core:latest container_name: mailman-core hostname: mailman-core volumes: - /opt/mailman/core:/opt/mailman/ links: - database:database depends_on: - database environment: - DATABASE_URL=mysql+pymysql://mailman:mailmanpass@database/mailmandb - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase - HYPERKITTY_API_KEY=someapikey networks: mailman: ipv4_address: 172.19.199.2 mailman-web: image: maxking/mailman-web:latest container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - DATABASE_URL=mysql://mailman:mailmanpass@database/mailmandb - DATABASE_TYPE=mysql - HYPERKITTY_API_KEY=someapikey - SECRET_KEY=thisisaverysecretkey - DYLD_LIBRARY_PATH=/usr/local/mysql/lib/ networks: mailman: ipv4_address: 172.19.199.3 database: environment: MYSQL_DATABASE: mailmandb MYSQL_USER: mailman MYSQL_PASSWORD: mailmanpass MYSQL_RANDOM_ROOT_PASSWORD: "yes" restart: always image: mariadb:10.3 volumes: - /opt/mailman/database:/var/lib/mysql After all that, I have run the following: wash@lists:~/docker-mailman$ docker-compose up -d Creating network "docker-mailman_mailman" with driver "bridge" Creating docker-mailman_database_1 ... done Creating mailman-core ... done Recreating 4b7bc1ecef65_mailman-web ... done Question - Should I assume everything is okay and proceed to the next steps? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 21

digests are created but not sent out
by "Jörg M. Schulz" 09 Jan '19

09 Jan '19

sudo -u list mailman digests -vp tells that the most recent digest has been sent, but nobody receives these digests. No mail or other log file has any clue what has happened. digest_queue = config.switchboards['digest'] >>> digest_queue <mailman.core.switchboard.Switchboard object at 0x7f9c8ed14940> >>> digest_queue.files [] m.digest_send_periodic = True Normal, non-digest messages are sent correctly. Administrative messages as well. Using GNU Mailman 3.2.0 (La Villa Strangiato) Where could I look for errors / stuck queues? /var/lib/mailman3/lists /var/lib/mailman3/lists/mailman.unswolke.de /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.3.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.2.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.2.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.6.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.4.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.1.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.1.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.mmdf /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.3.mmdf

2 13

Docker-mailman (performance?): "AH00894: declining URL", "AH01077: declining URL", "AH01105: NOT Closing connection", "AH01076: url: ... proxyname: (null) proxyport: 0"
by Henrik Rasmussen 09 Jan '19

09 Jan '19

I am using docker-mailman with GNU Mailman 3.2.0 (La Villa Strangiato). Even I have had no complains previously, a list admin have received proxy errors a couple of days. Right after one occurrence I immediately looked at the logs and while I had no related errors in the log files in /var/log/mailman/web/{uwsgi,uwsgi-error,mailmanweb}.log, the Apache log often shows "AH00894: declining URL", "AH01077: declining URL", "AH01105: NOT Closing connection", "AH01076: url: ... proxyname: (null) proxyport: 0". The errors seems to go back a long time, also on previous versions of Mailman, but no one have complained about it until now. Apache is version 2.4.6 on a RHEL 7 assuming Red Hat have backported any bugs about timeout previously know as hardcoded timeout of 30s etc. I assume therefore that even Mailman did not indicate any errors, it may have been too slow to respond. The server does not seem to be slow at all. Is there a way I can enhance the performance of Mailman (Docker)? I've asked about performance previously, but as I don't think my current question is related to REST, it's probably not related to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…. Henrik

1 0