Re: Address munging

Osoba podpisana jako Adam Sjøgren <[email protected]>
w artykule <news:[email protected]> pisze:

> All text that looks like an email address is, as far as I know - what
> difference does it make if the list address is?

All - it means, that munging may break:
- Content-ID, which is more or less irrelevant here.
- Message-ID, which may break all Message-ID based features described in
standards, including retrieving messages and threading.

See for example this message:
news://news.gmane.io/[email protected]
You can find URI for another message there, but it's useless, as the 
Message-ID is munged. You can't retrieve anything even using proper server 
name:
news://news.gmane.io/[email protected]...
There's only error mesage "430 No such article" there.

I think it should be easier to unmunge such requests on the server side 
and provide working features than to distinguish which string text@text is 
which when munging them. But at least any news: URI should be NEVER munged 
at all – it's easy to do, isn't it?

-- 
Andrzej P. Woźniak [email protected] (swap z<->h in address)