On 06/03/2018 12:34 PM, contact@maadix.net wrote:
Thanks Selva for you answer.
In my Mailman 3 installation there is no /var/log/mailman/subscribe
Correct. Mailman 2.1 had a subscribe log. Mailman 3 does not. Many things are logged in the 'mailman' log, but subscription confirmations are not.
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@maadix.net>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: contact@example.net Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86@list.example.org>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86@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.
Also, while I don't think it is currently possible to confirm a subscription via REST, not to mention Postorius, it may be in the future and this would bypass email all together.
I think the best thing is to implement logging.
Of course, you might be able to get your MTA to save all mail to the LIST-confirm address to a separate mailbox in addition to delivering it to Mailman.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan