-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, March 30, 2003, Thomas Fernandez wrote...
>> What Peter referenced too was the first line I sent, HELO [my >> host]. What has happened is when your computer connected to the >> server, it sent it's known name as part of the transaction. As you >> had an extended character (�) in the hostname, the server failed to >> do it's work properly, and as it didn't resolve, it automatically >> rejected. > If the error message came from the server, how come there were no > problems with Outlook or Becky? They might be using a different value for hostname, ie, if you're using dial-up, outlook/becky might use the resolved hostname for that, while TB! uses the hostname found on the computer. >> The interesting thing is that domain names are now supporting >> extended characters, so I believe the � is a valid character in >> domain names now. > I haven't seen such an error message, but can it be possible that TB > checks the validity of the domain name and isn't aware that extended > characters are now allowed, so the error message actually came from > TB and not the server? It that case, Ritlabs would need a little > hint. I doubt TB does that to be honest, would seem a little unusual step, but I could be wrong ;) - -- Jonathan Angliss ([EMAIL PROTECTED]) -----BEGIN PGP SIGNATURE----- Comment: Fingerprint: 676A 1701 665B E343 E393 B8D2 2B83 E814 F8FD 1F73 iQA/AwUBPofSniuD6BT4/R9zEQKNcQCgyeKTfGaO5Z8Zit9cI58oVLeMzbYAn0Nt OSnIsWNsypB+YA4k53KXNU09 =DCD5 -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
