On 22. 03. 26 14:52, Stephen Farrell wrote:
On 22/03/2026 10:07, Neil Cook wrote:
On 21 Mar 2026, at 01:58, Stephen Farrell
<[email protected]> wrote:
More apologies for thinking this through slowly, but there may be
another issue with this spec that just occurred to me:
If the QNAME that caused the error message here was
bad.example.com and the response contains
"mailto:[email protected]"; then the client will be kinda
stuck won't it? Is that addressed in the draft?
That won’t be a problem unless the email server is using the same
DNS resolver as the user.
Yes, but it could be. Not sure what'd apply wrt sips: URLs.
And if other schemes are added, who knows.
I can’t think of many scenarios where a mail server would be setup
to use a resolver that performs filtering like this.
I agree this shouldn't be common, but the question is: should
the client do something about it? Perhaps just drop any URI
where the authority part is the QNAME that caused the error?
I think it is not worth the effort. Worst case the e-mail gets queued.
So what.
(Besides it would be incomplete anyway. What if @rhsname is a CNAME to a
blocked name ...)
--
Petr Špaček
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
