This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] DMARC issue
- Previous message (by thread): DMARC issue
- Next message (by thread): DMARC issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at yahoo.co.uk
Thu Mar 23 13:10:43 CET 2017
Actually Reply does still work and sends the mail back to the original sender. It does set the Reply-To correctly.
I successfully received this post on my yahoo, gmail and xs4all accounts. So from now on no list member's email provider should reject posts to the DB-WG because of DMARC policies.
cheersdenisco-chair DB-WG
From: denis walker via db-wg <db-wg at ripe.net>
To: Database WG <db-wg at ripe.net>
Sent: Thursday, 23 March 2017, 12:58
Subject: [db-wg] DMARC issue
Colleagues
The RIPE NCC has applied a mailman work around for DMARC to the DB-WG mailing list. This effectively wraps the sender inside the list address. The only real significance of this is that if you hit Reply the mail goes to the list and not the original sender. So if you want to send a private comment back to the original sender 'off list' you need to either hit Reply All and delete the addresses you don't want or Forward it.
cheersdenisco-chair DB-WG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20170323/4039c685/attachment.html>
- Previous message (by thread): DMARC issue
- Next message (by thread): DMARC issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]