On Wed, 13 Apr 2011, Daniël van Eeden wrote:

>> 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?

Yes it should! I think the problem I've had is just to figure out where to
document it...

> I don't find using the path as HELO/EHLO hostname very intuitive.

I agree, but I made it so basically since that's a "free" string passed in
that isn't used for anything else.

> 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

No, it is a bit of a stretch but then there is not even an RFC for the SMTP
URL syntax. There's an old draft from 1997, but that of course didn't say the
path part would be used like this either.

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

As libcurl already works this way I think we should document it.

And as libcurl already works this way, the --mail-helo option for 'curl' would
then just need to make sure that the host name string is put as the path part
of the URL so then it won't have to invent and use a new option for libcurl...

-- 
  / daniel.haxx.se

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