On Tue, 12 Apr 2011 19:50:20 +0200 (CEST), Daniel Stenberg
 <daniel_at_haxx.se> wrote:
> On Tue, 12 Apr 2011, Daniël van Eeden wrote:
>
>> Curl was using the shore hostname of my machine as EHLO hostname,
>> not the FQDN. I also couldn't find an option to set the EHLO hostname.
>
> If specified, it uses the "path" path of the SMTP URL as host name:
>
> smtp://example.com/fake-host.com
 Maybe that behaviour should be documented in the manpage?

 -------------------------------------------------------------------------
 diff --git a/docs/curl.1 b/docs/curl.1
 index 04511fa..62bce3a 100644
 --- a/docs/curl.1
 +++ b/docs/curl.1
 @@ -84,6 +84,8 @@ getting many files from the same server will not do
 multiple connects /
  handshakes. This improves speed. Of course this is only done on files
  specified on a single command line and cannot be used between separate
 curl
  invokes.
 +
 +For the SMTP protocol the path is used as HELO/EHLO hostname.
  .SH "PROGRESS METER"
  curl normally displays a progress meter during operations, indicating
 the amount
  of transferred data, transfer speeds and estimated time left, etc.
 -------------------------------------------------------------------------

 I don't find using the path as HELO/EHLO hostname very intuitive. And I
 doubt if
 it is completely compliant with section 3.3 of RFC 3986.
 http://www.apps.ietf.org/rfc/rfc3986.html#sec-3.3

 What whould be a better option: Fixing the docs or adding a --mail-helo
 switch?

 Regards,

 Daniël van Eeden
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-04-13