- Mailman-users - lists.mailman3.org

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

Removing Archives for a Deleted List
by kelly.close＠lrewater.com 09 Jan '19

09 Jan '19

Renewing this question ... maybe, there is now a straightforward way to delete archives associated with a deleted list in MM3? Through the UI would be ideal, but if there is a command line approach, I can make that work. Searching the message boards has not turned up anything either way for me. Thoughts? ~Kelly

2 1

hyperkitty base_url
by Thomas Stein 08 Jan '19

08 Jan '19

Hi all. Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's base_url: http://localhost:8001/hyperkitty/ but that leads to Jan 04 21:01:39 2019 (8322) HyperKitty failure on http://localhost:8000/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) The api_key is set in /usr/share/mailman3-web/settings.py. I suppose I'm doing it wrong. Any hints appreciated. thanks and cheers t.

4 8

Auth question
by David Krantz 08 Jan '19

08 Jan '19

Hi, I have of course activated password login as it was not possible to get the provider based logins to work (might be but not worth the time for me right now). Is there any way for an user to request a new password when it is forgotten? I presume that the Persona login is removed now. I cannot hide it in my version or at least I do not know how. cheers // David

6 25

Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg)
by kelly.close＠lrewater.com 08 Jan '19

08 Jan '19

Happy New Year! I'm setting up my first Mailman 3 server and was delighted to find a distribution package for Ubuntu 18.04, since that's the environment I'm most familiar with working in, that installs an integrated mailman3-hyperkitty-postorius setup. The package install plus the additional config steps in the included README files have gotten me oh-so-very close! What isn't working yet are the archives, specifically the messages sent to lists showing up at .../mailman3/hyperkitty. I'm at a loss and I'm hoping maybe the folks on this list can help me bring it home. Messages are distributed to subscribers as they should be - subscribers can send from their emails or from the web site. People can subscribe, etc. It's all working great. Just no archives. I am able to successfully run these django-admin processes without errors (described here: http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required). I've run them all manually and then I've been running the minutely and hourly ones manually after each test message I send (haven't set up the actual cron jobs yet). I'm not sure what to try next or what info to provide here for help - can anyone suggest where I can look to see why archives aren't getting created, or let me know what information would be essential for me to post to get help on this? I'm using PostgreSQL for the database, Postfix for mail and Apache2 for the web server. Thanks for your time! ~Kelly

2 8

$member does not appear to be dereferencing correctly in moderated subscription requests
by Joel Lord 08 Jan '19

08 Jan '19

So I'm having an issue with a new 3.2 install. All the lists I have are set to confirm + approve on new subscriptions, but it seems that no matter how a new subscription come in, it does not actually pass the applicant's name to the moderator. I've tested now with a new email address previously unknown to the system and made sure I filled in the name field in the form. I've tested with an email address previously KNOWN to the system (subscribed to other lists) that has its display name fields filled in AND filled in the name on the subscription form, and yet again with that account having cleared out the display name fields associated with the account. In all cases I was careful to be sure to fill in the name on the subscription form. Buried somewhere in the templates documenation I found that the $member template variable in the list:admin:action:subscribe.txt template is supposed to be both the email address and the display name of the person applying to subscribe, but it just doesn't appear to be coming up as more than just the email address. Have I missed something horribly, or did I come across a bug? -- Joel Lord

2 1

File Attachments
by brian＠emwd.com 08 Jan '19

08 Jan '19

Happy Monday everyone. Are there any plans to include the ability to attach files via the web interface? Or did I miss something? Thanks, Brian

5 9

Mass subscriptions
by Enrique Terrazas 07 Jan '19

07 Jan '19

Hello, One of our customers has requested a list that will include around 50,000 subscribers. The customers has provided the email addresses in a CSV file, is there a way to import this data to a mailman list from a CSV file or is the Mass Subscribe option the preferred method? Best regards, Enrique J. Terrazas

2 2

ARC support
by Marvin Gülker 05 Jan '19

05 Jan '19

Hi everyone, I just stumbled over an in-progress standard called ARC. It is appearently intended to solve the problems DMARC causes for mailinglists if I understand correctly. Since I've not seen a summary of it somewhere, I just give the plain links to it: * Website: http://arc-spec.org/ * Draft: https://datatracker.ietf.org/doc/draft-ietf-dmarc-arc-protocol/ Will Mailman at some point support this new standard? Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

2 1