Hello Jonathan, On Monday, March 31, 2003 at 7:31:02 AM you [JA]wrote (at least in part):
>>> 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? JA> They might be using a different value for hostname, ie, if you're JA> using dial-up, outlook/becky might use the resolved hostname for that, JA> while TB! uses the hostname found on the computer. That's my assumption as well. I don't think Becky, OE & Co replace the '�' by their own, so this seem to be the only logical way out of the opposite behaviors. >>> 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'm not sure their're really allowed. I can't remember having read I could register a domain using something like 'umlauts' or similar and a quick test with my local DNS didn't succeed too. I'm using bind version 9.2.1 here, so one of the more latest versions. But nevertheless this is quite OT, so I'd like to stop it here or move over to TBOT :-) >> 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. JA> I doubt TB does that to be honest, would seem a little unusual step, JA> but I could be wrong ;) I do agree completely here too. The given error message looks like a classical server side error message and error code and the text itself state it as well: "Server reports error: The response is: 5.0.0 Invalid domain name" ^^^^^^^^^^^^^^^^^^^^ And beside that: I've _never_ seen The Bat! giving such error messages, especially not those with x.y.z codes. Nevertheless RITLabs could make use of a little hint on this issue: strip all non-7-bit characters form the name sent in HELO/EHLO. That should solve this issue, and it's not the first time reported, so I think this could be a good idea nonetheless. It seems people tend to name their computers not every time following valid rules and as long as Windows is not going to tell them, but accepting it they can't know about this issue. So the best best is to make it fail safe and use only allowed parts of a computers name on The Bat!'s side. -- Regards Peter Palmreuther (The Bat! v1.63 Beta/7 on Windows 2000 5.0 Build 2195 Service Pack 3) Sound really has almost nothing to do with true music. ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
