| Dart Home | PowerTCP Mail for ActiveX | Custom Development | Reply | PowerTCP Mail for ActiveX Topics | Forums |
| Author | Forum: PowerTCP Mail for ActiveX Topic: EHLO / HELO hostname enum problem |
| oxident From: Berlin, USA Posts: 4 Member Since: 04/27/03 |
posted August 2, 2003 10:29 AM Hello! I've discovered, that the mail control always uses the local computer name when sending the EHLO / HELO command to a server. This doesn't seem to be a problem when talking to nearly 99% of all server implementations but there -are- servers which do a reverse lookup on this hostname and refuse any connection attempt if this lookup failed. Example: Recv: 220 mail.someserver.com ESMTP Sent: EHLO MYSERVER Recv: 250-mail.someserver.com 250-PIPELINING ... Sent: MAIL FROM: SIZE=197 BODY=7BIT RCPT TO: Recv: 250 Ok 504 : Helo command rejected: need fully-qualified hostname ... As you can see, the remote server rejects this transmission (the verify-method was used in this example). My hostname is MYSERVER (with a FQDN as DNS-Suffix, so the complete hostname, according to sysinfo should be MYSERVER.mydomain.com). I didn't see an option to override the mail control's local hostname retrival function and as I'm unable to include dots in my local hostname, I can't see a solution to this special problem. BTW: This strange behaviour of the remote server isn't really allowed, according to some RFCs, is it? Greetings, .chris |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted August 4, 2003 9:23 AM Thanks. You are entirely correct. We use only the hostname. I have added a feature request to allow this to be more flexible. The issue will be #1932 for future reference. |
| Reply | PowerTCP Mail for ActiveX Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|