-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failure report mail loops #2
Comments
@[email protected] 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. |
@[email protected] set owner to |
@[email protected] changed component from |
@[email protected] changed status from |
@[email protected] set resolution to |
@[email protected] commented Discussion: |
@[email protected] changed status from |
@[email protected] removed resolution (was |
@[email protected] commented Further discussion: |
@[email protected] changed component from |
owner:[email protected]
type_enhancement
| by [email protected]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
The text was updated successfully, but these errors were encountered: