-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, March 30, 2003, �sten H�ggmark wrote...
>> The server you've just hit seems to care about the HELO/EHLO name >> and it therefore refused your messages containing an invalid >> DNS-name. > I won't pretend to have a clue about what you are saying... :-) EHLO/HELO is the greeting message you send to a SMTP server when you connect. It's to let the SMTP server know who you are, although it can be forged, most use it as a basic lookup anyway. Here is a basic sample of a SMTP connection: ,----- [ SMTP Transaction ] | 220 [server name] ESMTP Postfix | HELO [my host] | 250 [my host returned] | MAIL FROM: [my email] | 250 Ok | RCPT TO: [who I'm sending too] | 250 Ok | DATA | 354 End data with <CR><LF>.<CR><LF> | From: Jon Angliss <[my email]> | Subject: This is a test | | Hello Me | | . | 250 Ok: queued as D1E8CA80D0 | `----- 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. The interesting thing is that domain names are now supporting extended characters, so I believe the � is a valid character in domain names now. Of course, it's still not going to fail the lookup if the domain isn't registered. - -- Jonathan Angliss ([EMAIL PROTECTED]) -----BEGIN PGP SIGNATURE----- Comment: Fingerprint: 676A 1701 665B E343 E393 B8D2 2B83 E814 F8FD 1F73 iQA/AwUBPodqASuD6BT4/R9zEQJxgwCfZqcy9uVrpZ+194DZK4lXe2GDR6IAoLQu 3A4YKBXPYVG5S40aRyvf8OfY =ztlB -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
