Skip to content
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

SMTP TLS Reporting: report size should be clarified #113

Open
eyeofthenico opened this issue Oct 24, 2016 · 2 comments
Open

SMTP TLS Reporting: report size should be clarified #113

eyeofthenico opened this issue Oct 24, 2016 · 2 comments

Comments

@eyeofthenico
Copy link
Contributor

I think we should have default report size that should be supported and allow recipient to specify larger limit.
The "commonly observed receiver limit is ten megabytes" applies to SMTP method only imho.
HTTP POST body size typically needs to be configured on webservers. I believe that default requirement will prevent silent failures due to oversize reports.

@abrotman
Copy link
Collaborator

I'm not sure we need this. I think we're unsure how large this will be, but when things are working correctly, the report should be tiny, and if things are bad, they may be large, but that's a good indicator your organization should get things resolved.

If you were to specify a size, where would you like to truncate data? After N items? Try to decide a severity?

@prbinu
Copy link
Collaborator

prbinu commented Nov 15, 2016

10MB max for both email and HTTP post?. Anything that goes beyond the limit should be split into multiple requests.

In general, what I have seen is that unlike DMARC, the report volume is very low.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants