Sam Varshavchik wrote:
Julian Mehnle writes:
I think adding such checks and issuing a syntax error in the <[EMAIL PROTECTED]'>
case would be the way to go. But maybe there's a good reason why Courier
doesn't do that?
Well, I don't think you'd have too much trouble sticking an apostrophe into a hostname in DNS. If you really wanted to, I think you could set up an MX record for foo'bar.example.com.
But that's a stretch. Obviously apostrophes are invalid, however I don't want to start keeping track of which characters are valid in DNS, and which ones aren't. You'll never get this right.
RFC1123 clearly defines valid hostnames and DNs. I would not check the prescribed lengths, but the allowed characters are easy to check.
M4
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
