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@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.
Maddish
El 03/06/18 a las 18:17, Selva Nair escribió:
Hi,
On Sun, Jun 3, 2018 at 10:12 AM, contact@maadix.net <contact@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
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
Mark Sapiro writes:
I think the best thing is to implement logging.
With a blockchain!
"Blockchain" is a joke, of course, but I think there would need to be some way to verifiably construct an audit trail. Maybe the OTK is enough?
El 04/06/18 a las 05:52, Mark Sapiro escribió:
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. Ye , this is the best solution. That's what I finally did. Thank you very much Mark.
Maddish
-- Maadix
*MaadiX*
Tu nube en tus manos
participants (3)
-
contact＠maadix.net -
Mark Sapiro -
Stephen J. Turnbull