fre, 2002-08-23 kl. 17:37 skrev Peter Williams:
During an SMTP conversation, if an EHLO fails, then evolution should drop to HELO, and not report any errors.
This is the way it's coded now. Maybe that bit of the code is broken at the moment.
You should file a bug at bugzilla.ximian.com
! RFC 2821: Contemporary SMTP implementations MUST support the basic extension mechanisms. For instance, servers MUST support the EHLO command even if they do not implement any specific extensions and clients SHOULD preferentially utilize EHLO rather than HELO. (However, for compatibility with older conforming implementations, SMTP clients and servers MUST support the original HELO mechanisms as a fallback.) Unless the different characteristics of HELO must be identified for interoperability purposes, this document discusses only EHLO. Best, Tony --- Tony Earnshaw The usefulness of RTFM is vastly overrated. e-post: tonni billy demon nl www: http://www.billy.demon.nl gpg public key: http://www.billy.demon.nl/tonni.armor Telefoon: (+31) (0)172 530428 Mobiel: (+31) (0)6 51153356 GPG Fingerprint = 3924 6BF8 A755 DE1A 4AD6 FA2B F7D7 6051 3BE7 B981 3BE7B981
Attachment:
signature.asc
Description: Dette er en digitalt signert meldingsdel