On Tue, 12 Apr 2011 19:50:20 +0200 (CEST), Daniel Stenberg
dan...@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
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
Hi,
This is a simple patch to allow sending email to more strictly
configured mail servers.
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.
Some mailservers check if the EHLO hostname does resolve using
On Tue, Apr 12, 2011 at 04:06:24PM +0200, Daniël van Eeden wrote:
This patch will add a switch to set the ehlo hostname. This will
cover most cases.
It will not set the HELO hostname.
Why not? It also needs a way to set the hostname and it's only used
if EHLO fails. I would rather it set
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
--
/
