Matthias Wimmer [EMAIL PROTECTED] wrote: > If there are implementations that try to guess is something is an IP or > a domain, than they can make wrong assumptions [...]
There's no need to guess. There are no official digit-only top-level domains, and digit-only top-level domains are not widely used in private, either. > [...] > it's that courier does not implement a workaround for a bug ... not only > because it's not legal according to the RFC ... it's even wrong from the > natural sematics. What natural semantics? Despite your weak reasoning, there actually *is* a strong reason why *putting* IP addresses in MX records is a bad idea: In DNS, IP addresses are encoded as a binary quadruple of bytes, while domains are encoded as a series of zero-terminated strings (one for each label), potentially using a simple compression scheme. *Recognizing* IP addresses in MX records is a somewhat different matter, though. Yes, it requires some additional code. But, no, it's not actually harmful beyond tolerating RFC-incompliant configurations. ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
