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/[email protected]/
[anti-abuse-wg] an ISP can't do anything?
- Previous message (by thread): [anti-abuse-wg] an ISP can't do anything?
- Next message (by thread): [anti-abuse-wg] an ISP can't do anything?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hans Petter Holen
hph at oslo.net
Wed Feb 22 20:23:44 CET 2017
On 21 February 2017 at 16:27, Suresh Ramasubramanian <ops.lists at gmail.com> wrote: > The question before the house is ripe's mailing list software being > configured to appropriately rewrite headers to support dmarc > > As this is a topic that interests me in my day job, I tried to read up on the IETF list on how to " appropriately rewrite headers to support dmarc" I was not able to see that there was consensus on how that should be done. The consensus seemed to be that there is still work to be done for *Domain-based Message Authentication, Reporting & Conformance WG - *but I am not sure I understand the problems well enough. Perhaps a topic for the wg to discuss further at the upcoming meeting - if somebody has some experiences to share. My own conclusion is that I cannot turn on DMAC other than for logging, if I still want to be subscribed to mailinglists. I have turned it on for oslo.net and using dmarcian.com to analyse the results. -hph -- Sincerely, Hans Petter Holen - hph at oslo.net - +47 45066054 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20170222/65e0de75/attachment.html>
- Previous message (by thread): [anti-abuse-wg] an ISP can't do anything?
- Next message (by thread): [anti-abuse-wg] an ISP can't do anything?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]