search

ietf-wg-dmarc / draft-ietf-dmarc-failure-reporting

0 stars 3 forks source link

failure report mail loops #2

Open ietf-svn-bot opened 5 years ago

ietf-svn-bot commented 5 years ago

owner:draft-ietf-dmarc-rfc7601bis@ietf.org type_enhancement | by tim@eudaemon.net

Apropos recent discussions, we could recommend that failure reports be rate limited per recipient both to break loops and to deter indirect mail bombing.

Issue migrated from trac:28 at 2022-01-24 16:15:15 +0000

ietf-svn-bot commented 5 years ago

@tim@eudaemon.net commented

This might be a candidate for the DMARC Usage Guide. People also talking about DMARC Deployment Guide, which right now may/may-not be the same thing.

ietf-svn-bot commented 4 years ago

@seth@sethblank.com set owner to draft-ietf-dmarc-rfc7601bis@ietf.org

ietf-svn-bot commented 4 years ago

@seth@sethblank.com changed component from dmarc-future-notes to rfc7601bis

ietf-svn-bot commented 4 years ago

@seth@sethblank.com commented

See: https://mailarchive.ietf.org/arch/msg/dmarc/TPUpxEFCM39JyPLWmL49mY4cFS8/

ietf-svn-bot commented 3 years ago

@vesely@tana.it changed status from new to closed

ietf-svn-bot commented 3 years ago

@vesely@tana.it set resolution to wontfix

ietf-svn-bot commented 3 years ago

@vesely@tana.it commented

Discussion: https://mailarchive.ietf.org/arch/msg/dmarc/W3uGPEpT3Yi5lqKntZXyL8jkNjk

ietf-svn-bot commented 3 years ago

@vesely@tana.it changed status from closed to new

ietf-svn-bot commented 3 years ago

@vesely@tana.it removed resolution (was wontfix)

ietf-svn-bot commented 3 years ago

@vesely@tana.it commented

Further discussion: https://mailarchive.ietf.org/arch/msg/dmarc/iFJWghWV1eSNkaWfmeguO9aRzjw

ietf-svn-bot commented 3 years ago

@todd.herr@valimail.com changed component from rfc7601bis to dmarc-failure-reporting