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 ]
Suresh Ramasubramanian
ops.lists at gmail.com
Mon Feb 20 16:28:52 CET 2017
DMARC policy compliance is something that RIPE needs to fix at their end – ensuring that the mailing list manager rewrites headers appropriately. Most mailing list manager software has already been rewritten to support this by default, so unless RIPE NCC is using something heavily patched and customized for their own needs upgrading to the latest version should mostly fix this, or it should be fixable with some config change after the upgrade. --srs On 20/02/17, 7:09 AM, "denis" <ripedenis at xs4all.nl> wrote: Thanks for that. I can live with a mail server that is only randomly blocked by a few organisations. I was looking for a mail service that I can use that works with the RIPE NCC's mail server. It seems yahoo, gmail and microsoft mail servers have variable success with these mailing lists. Sometimes I post and many list members reject my mails because of DMARC policies. As I don't have a corporate email address I have limited options.
- 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 ]