On Sun, 31 Oct 2010, Daniel Stenberg wrote: > If we focus on the gmail case, can you please provide a full trace/debug log > for a failed attempt? (edit out sensitive data)
>>Ah, perhaps even one then using the easy interface so that we can more easily >>detect exactly when they deviate. >>I would like to know that if I try to repeat or fix this, that I actually work >>with the problem you're having. -- This is a failure with multi_perform(): INFO_TEXT: About to connect() to smtp.gmail.com port 587 (#0) INFO_TEXT: Trying 74.125.95.109... INFO_TEXT: Connected to smtp.gmail.com (74.125.95.109) port 587 (#0) INFO_HEADER_IN: 220 mx.google.com ESMTP u6sm11694984ibd.12 INFO_HEADER_OUT: EHLO geniosol9.hcl.com INFO_HEADER_IN: 250-mx.google.com at your service, [199.85.101.2] INFO_HEADER_IN: 250-SIZE 35651584 INFO_HEADER_IN: 250-8BITMIME INFO_HEADER_IN: 250-STARTTLS INFO_HEADER_IN: 250-ENHANCEDSTATUSCODES INFO_HEADER_IN: 250 PIPELINING INFO_HEADER_OUT: STARTTLS INFO_HEADER_IN: 220 2.0.0 Ready to start TLS INFO_TEXT: SSLv3, TLS handshake, Client hello (1): INFO_HEADER_OUT: EHLO geniosol9.hcl.com INFO_HEADER_IN: Curl error message is "Failure when receiving data from the peer" ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
