- Mailman-users - lists.mailman3.org

What is result of planned MM3 integrated installation at Pycon?
by Tom Browder 10 Jun '18

10 Jun '18

I may have missed the announcement, but I thought it was hoped to get a major leap toward an integrated MM3 installation at the May Pycon. Did anything exciting happen toward that goal, or should I just press on with the latest release? Thanks. Best regards, -Tom

2 3

Scheduled tasks
by Darren Smith 08 Jun '18

08 Jun '18

All, I am looking more through the documentation of the Mailman Suite here: https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf In section 3.2.5 it talks about the scheduled tasks that need to be run to do "specific routine functions" in hyperkitty. I installed through the easy install script found here: https://github.com/iomarmochtar/mailman3_ei/ However, I can't find anything in THAT documentation that talks about these cron jobs, and in fact the Mailman Suite isn't installed through that script. Can someone point me to any other documentation about the tasks that need to be run on a continual basis? Our hyperkitty installation seems to be bogging down more and more, and I am hoping that it will be as simple as just running some jobs that haven't been on our radar. Thoughts? -Darren

2 3

Attachments
by Darren Smith 06 Jun '18

06 Jun '18

Guys, Is there a setting to disallow attachments in mailman3? Doing a cursory search I can't find it.

3 2

Re: GDPR - save subscriptions confirmation emails
by contact＠maadix.net 04 Jun '18

04 Jun '18

Thanks Selva for you answer. In my Mailman 3 installation there is no /var/log/mailman/subscribe I have logs about confirmations emails in mailman/var/logs/smtp.log the format is the following: Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO mails.example.com' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL FROM:<contact(a)maadix.net>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: contact(a)example.net Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' So, one solution that comes to my mind is to grep this log file. This is not a perfect solution and the full confirmation email is still missing. I am not sure if this would be GDPR compliant. Maddish El 03/06/18 a las 18:17, Selva Nair escribió: > Hi, > > On Sun, Jun 3, 2018 at 10:12 AM, contact(a)maadix.net <contact(a)maadix.net> wrote: >> >> 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? > > We have been doing this with mailman2 since Canadian Anti-Spam Law (CASL) > got enacted (2014) by independently archiving the confirmation messages. > With postfix we use recipient_bcc_maps and a script to do some extra filtering > but its clunky, and does not check that the confirmation succeeded or not. > > A feature within mailman to archive successful confirmations would be > useful. Keeping unsubscribe requests and evidence of subsequent > actions also seems necessary at least as per CASL. > > That said, we also keep the /var/log/mailman/subscribe logs (not sure > what that would be in mailman 3). Although the log has a single line > for each action, it may be enough to show (?) that a double opt-in process > was properly followed or unsub request was acted up on. > > Thanks, > > Selva > -- Maadix *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

3 3

Delete User
by Kaleb White 25 May '18

25 May '18

Is it possible to delete a user from postorius completely so that they cannot log in again?

2 4

Urgent help needed...
by Darren Smith 24 May '18

24 May '18

Hello, This morning our Mailman 3/Hyperkitty/Postorius installation has become unresponsive. When looking at the machine, postgres is pegging all 4 CPUs on the machine. We did some digging in postgres, and here is the query that is causing problems: "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY hyperkitty_email.date ASC LIMIT 1;" We have found that it doesn't matter what mailinglist_id is being used. We have also found that this might be an issue with the LIMIT 1 - our investigation is showing that using LIMIT 1 in postgres makes things execute very differently than if you use a limit 2 or more, and that this is probably what is going on. Basically, every time this gets called, it pegs an entire CPU for 20-30 seconds. It appears to be called a LOT. So our users are getting 504 gateway timeouts right now. What has changed: We have been in the process of importing our 40 million archived emails from our old mailman 2 archives. Questions: 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, postorius, django - basically anything that might be calling this code, but we can't find it. Does anyone know what generates this query? 2) We are positing that it might be our archive imports that are causing this problem. Does anyone know of any sort of limit/threshold that might cause this to go haywire? Any help you can give, any direction you can point us would be useful. Right now our lists are just down for our users. Thank you, Darren

2 2

Is it possible to use an authenticator with incorrect, missing, or changing email addresses?
by andrew＠fsf.org 24 May '18

24 May '18

Hello Mailman 3 users list, I was wondering if it's possible to set up a CAS authenticator with django-allauth ( https://pypi.org/project/django-allauth-cas/ ) even if we cannot guarantee the correctness of email addresses supplied by our CAS instance? Some contacts may also be missing an email address. I read about this here, and it seems like it wouldn't be possible: http://docs.mailman3.org/en/latest/config-web.html#configure-social-login > To see a list of all the providers, please have a look at the documentation of django-allauth. Make sure that the one you choose provides “email” as part of user data, otherwise it won’t work with Mailman. e.g. Twitter doesn’t give out emails. What if a user's email address changes on the CAS server? Will their email address in Mailman 3 be updated the next time they log in? Thanks, Andrew

2 1

What implications do GDPR have on Mailman, and how to requiring members to accept registration
by Henrik Rasmussen 23 May '18

23 May '18

In regards to GDPR*) I am wondering if there is any ways I can require my current and future subscribers, members and list administrators to accept registration. I am also concerned that new lists are created with a subscription policy "Confirm" as default, rather than at least "Moderate", which can cause people to be subscribed by others against there will. Also, regardless of this setting, administrators can subscribe people without their knowledge. Away from Gravatar, mentioned in another post, what implications do GDPR have on Mailman? *) http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX%… Henrik Rasmussen

4 6

No archived messages in hyperkitty
by Eric Abrahamsen 12 May '18

12 May '18

I've got mailman3 up on Ubuntu 16.04, in a virtualenv, and (eventually) got everything working mostly okay. My last hurdle is archiving into hyperkitty: the web interface says "no archived list yet". The list I'm starting with is set to archive both to prototype (which I set up in the beginning, before I got hyperkitty going) and to hyperkitty. There appear to be no further boxes I can check, and mailman_hyperkitty.cfg is in place and I think correct. I think it's nearly working because new messages get filed to ./var/archives/hyperkitty/spool, in individual *.pck files, but then these files don't go anywhere, and the archives don't appear in the web view. It could be a problem with cronjobs, with qrunner, or maybe there's just one last hidden switch in a database somewhere that I haven't thrown. But I can't find anything. Any hints? TIA, Eric

2 3

List enumeration problem
by kawhite＠ancestry.com 11 May '18

11 May '18

On our mailman instance we see the following enumeration of ALL lists and ALL users consistently every 7.5 minutes. Does anyone know why this would be the case? We have a lot of mailing lists so it slows our machine down a lot. Apr 30 15:31:36 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/a(a)example.com HTTP/1.1" 200 310 Apr 30 15:31:36 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/a(a)example.com/config HTTP/1.1" 200 2021 Apr 30 15:31:36 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/b(a)example.com HTTP/1.1" 200 325 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/b(a)example.com/config HTTP/1.1" 200 2108 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/c(a)example.com HTTP/1.1" 200 326 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/c(a)example.com/config HTTP/1.1" 200 2049 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/d(a)example.com HTTP/1.1" 200 324 ... Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/a@a HTTP/1.1" 404 13 Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/b@b HTTP/1.1" 404 13 Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/c@c HTTP/1.1" 404 13 Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/d@d HTTP/1.1" 404 13

4 3