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] DMARC Solution Applied to this Mailing List
- Previous message (by thread): [anti-abuse-wg] DMARC Solution Applied to this Mailing List
- Next message (by thread): [anti-abuse-wg] DMARC Solution Applied to this Mailing List
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ox
andre at ox.co.za
Mon Dec 18 13:23:06 CET 2017
I just realised that my question is confusing :) I mean RIPE does not have dmarc or spf (but does dnssec) so, for me, my spam filters score points on lack of SPF or even hard bounce on wrong SPF RIPE emails (from the mailing list) attracts points - for not having SPF So, more directly, I am asking if it is possible to add SPF even with a "~" is fine? Andre On Mon, 18 Dec 2017 14:16:43 +0200 ox <andre at ox.co.za> wrote: > Hi Adam, > > Please enlighten me why RIPE does not support publish any SPF records? > > I do see the RRSIG, so am keen on understanding why RIPE supports > DMARC and no SPF? > > Andre > > -- > dig TXT ripe.net > ; <<>> DiG 9.9.9-P1 <<>> TXT ripe.net > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25373 > ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: > 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 512 > ;; QUESTION SECTION: > ;ripe.net. IN TXT > > ;; AUTHORITY SECTION: > ripe.net. 299 IN SOA > manus.authdns.ripe.net. dns.ripe.net. 1513415885 3600 600 864000 300 > > > On Mon, 18 Dec 2017 12:29:01 +0100 > Adam Castle <acastle at ripe.net> wrote: > > > Dear Working Group, > > > > As more email providers enable Domain Message Authentication > > Reporting & Conformance (DMARC), some people find they can no longer > > receive emails from the mailing lists they are subscribed to. We > > have deployed a Mailman setting change to address this problem. > > > > After consultation with the RIPE Working Group Chairs, we have > > enabled the DMARC "Munge From" setting on all RIPE mailing lists. > > This means that if your email service provider has DMARC enabled, > > you will continue to receive all emails sent to this mailing list, > > but the "From" part of the header will change. If you don't have > > DMARC enabled, you won't see any change to the emails you receive > > from this mailing list. > > > > You can find more information about how we have been handling DMARC > > in the following RIPE Labs articles: > > > > https://labs.ripe.net/Members/adam_castle/dmarc-and-the-ripe-ncc > > > > https://labs.ripe.net/Members/adam_castle/ripe-mailing-lists-and-dmarc > > > > To ensure all working group participants are aware of the changes, I > > am sending this mail to all working groups. If you have any > > questions or encounter any issues on this mailing list, please let > > me know. > > > > Many thanks. > > > > Adam Castle > > Web Services Manager > > RIPE NCC > > > >
- Previous message (by thread): [anti-abuse-wg] DMARC Solution Applied to this Mailing List
- Next message (by thread): [anti-abuse-wg] DMARC Solution Applied to this Mailing List
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]