Alex van den Bogaerdt wrote:
On Sun, Feb 27, 2005 at 07:00:06PM -0500, Radu Hociung wrote:
I think we need to define two levels:
minimum requirement = "no one stops validating after less than X"
max recommendation = "probably no-one does more than Y queries"
For any set of values where X != Y:
This is where the unreliability of email starts.
Seriously: I think there should be no "min" and "max" limit.
There should be a specification; no less no more.
If there is a gray area, people _will_ end up in there.
Then the publisher is right (X < number of records <= Y)
and the recipient domain is also right (number of records
is above the domain's limit (X <= limit < Y)
The publisher would be right only if his record is X queries or fewer.
A record between X and Y would be reported as "invalid" and a record
more than Y would be reported as "DoS/abusive"
"Hey Mister, you said I could have $foo records according to
the spec ?!?" `Yes, that's correct but they are allowed to
check no more than $(foo-1) so your record doesn't work in
this specific case'
If X = 10 and Y = 111, it would mean all recipients check the first 10.
Between 10-111, it's up to the recipient if they are lenient, as the
spec does not require them to be.
Over 111, the recipient will take cover, report you to your ISP, add you
to the local blacklist and block your connections at the firewall.
/s/allowed to/recommended to/
/s/doesn't work/does work as long as you keep it to 10 max/
> "Hey Mister, you said I could have 10 records according to
> the spec ?!?" `Yes, that's correct but they are recommended to
> check no more than 111 so your record does work as long as you keep it
> to 10 or under'
If you exceed the limit of 10 (X) you won't be reported to your ISP or
the police, but your mail might not go through. Don't complain, as
you've been warned.