On Wed, Nov 21, 2012 at 05:17:39PM +0100, Wouter Van Rooy wrote:
When configuring curl with --disable-static and then running
curl-config --static-libs it still outputs the non-present libraries.
Attached is a patch to fix this.
The patch removes the non-present libraries, but outputting
Daniel Stenberg dan...@haxx.se wrote:
On Sat, 8 Sep 2012, Daniel Stenberg wrote:
Here's my first take at a CURLOPT_PROXYHEADER option that should allow an
application to select to affect only host, proxy or both request headers.
I've not written any test cases yet for this nor pushed
Hi Naveen,
Please let me know if there is a way to test for proper SMTP server
connectivity using libcurl 'without actually sending an email'.
You can do this with the CURLOPT_CONNECT_ONLY option and setting it to 1.
Although this could otherwise be done with a simple telnet EHLO
(or HELO),
On Thu, Nov 22, 2012 at 11:52:39AM +, Chandran, Naveen wrote:
Please let me know if there is a way to test for proper SMTP server
connectivity using libcurl ‘without actually sending an email’.
Although this could otherwise be done with a simple telnet EHLO (or HELO), I
would like to know
On Thu, 22 Nov 2012, Fabian Keil wrote:
Regarding the documentation I think it would make sense to refer to the
CURLOPT_HTTPHEADER for the syntax description instead of duplication most of
it, or at least making it clear that the syntax is basically the same, so
the user doesn't spend time
Hi Steve,
Thanks for the advice.
You noted that the CURLOPT_CONNECT_ONLY option would actually log into the SMTP
server (if the auth details were to be supplied) and I hope to achieve exactly
this for my testing :)
However, on attempting the test code again with the CURLOPT_CONNECT_ONLY
At 03:52 22-11-2012, Chandran, Naveen wrote:
My presumption was that, after setting up the SMTP server URL (using
CURLOPT_URL), attempting just a 'FROM' alone (using
CURLOPT_MAIL_FROM) would suffice.
However, doing so sort of causes the code to get stalled (and then,
eventually time out),
Correct. I agree with you completely.
However, the only hitch is that, libcurl (probably) doesn't allow us to
customize the SMTP commands to be sent to the server through the SMTP specific
curl options (and for good reasons).
But on the other hand, I am unsure if you are suggesting that I use
On Thu, 22 Nov 2012, William Lear wrote:
I am tasked with updating an existing embedded system to access a web
service using SOAP with Attachments (multipart/related). The system is
locked in to a prebuilt, ROM resident copy of libcurl 7.15.3, so I can't
change it. There is insufficient
Hi Dan,
Thanks for your suggestion.
I did try with the CURLOPT_NOBODY option set to 1. With that change however, I
get the following error after the initial server greeting:
.
.
250-XUSR
250 HELP
MAIL FROM:x...@yyy.com
250 x...@yyy.com ... Sender ok
* response reading failed
QUIT
*
Hi again,
However, on attempting the test code again with the
CURLOPT_CONNECT_ONLY option added, after the initial
SMTP server greeting, the code errors out as follows:
You mentioned in your original post that you are using v7.23.1 and that is
now a year old - Since then I have extended both
Hi SM,
The clean way would be to:
1. send HELO
2. read
3. send FROM
4. read
5. send QUIT
6. read
Just a quick clarification - Did you mean MAIL FROM: in step 3 and is this
step mandatory as all other steps are performed by libcurl?
Kind Regards
Steve
Hi Steve,
At 12:01 22-11-2012, Steve Holme wrote:
The clean way would be to:
1. send HELO
2. read
3. send FROM
4. read
5. send QUIT
6. read
Just a quick clarification - Did you mean MAIL FROM: in step 3 and is this
step mandatory as all other steps are performed by libcurl?
Yes,
Am 17.11.2012 01:05, schrieb Daniel Stenberg:
On Fri, 16 Nov 2012, Daniel Stenberg wrote:
I'll need to think about this some more...
I've nwo created a new test case and a little perl script that scans for
this kind of mistake to make it much harder to happen in the future.
Will push soonish
14 matches
Mail list logo
