> -----Original Message----- > From: curl-library [mailto:[email protected]] On Behalf Of > Daniel Stenberg > Sent: Sunday, September 28, 2014 4:54 AM > To: libcurl development > Subject: RE: [PATCH] smtps with openssl > > On Fri, 26 Sep 2014, Nagel, Bill wrote: > > > There is a thread about it here: > > > > > http://cp.mcafee.com/d/5fHCMUSyMyyYqem7DbCXCQXK6zBVxxVZMSDssy > yOOyMMrjK > > UqenC67DTzqdShP9EVouhodC8qhYY5jbmHa4-ndPbmHa4- > ndA6fIejovW_9FTKNRXBQSm6 > > upjjsvVqWtAklkrzKl3PWApmU6CQjr9K_3AmkXzDS1OpKVI07iuSaRc_5Q- > FzBY5C_Felo > > > kNcQsCzAsCyZxwCmbWGnAn8_esE4i_Nzmab5PhOXssXixVudmVOxZakfpbC > 8ODVtrU8iwh > > > bAdgbC8ODVufPyrIT4YKv8x7oByV2Hsbvg5mHk_yuxUvRfdIL3Cjob6Azh0qm > MI80Ai2VF > > td455pHkd41ykOpEwGJYakfdITdKK1UO1T2 > > > > One comment mentions that even the address of the pointer has to be > > the same. I was only able to hit this failure with the native Windows > > build of curl while sending attachments with smtps, but that is my > > primary usage cause, so I see this failure frequently. > > Yeah, we've run into this issue in the past with OpenSSL (with HTTPS) and we > had to fix it this way there too in order for it to work properly when > retrying a > send that previously had returned the EWOULDBLOCK equivalent. > > -- > > / daniel.haxx.se
Since this appears to be the precedent, can this patch be merged? thanks, -Bill ________________________________ This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
