Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: How to interpret CURLE_WEIRD_SERVER_REPLY?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: SherwoodP via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 23 Oct 2025 12:12:05 -0700
This is my reply to Patrick Schlangen and Patrick Monnerat:
Attached is the verbose output from curl when I attempt to send an email using"secure mail keys" for authentication.
Received on 2025-10-23
Date: Thu, 23 Oct 2025 12:12:05 -0700
This is my reply to Patrick Schlangen and Patrick Monnerat:
Message: 1
Date: Sat, 18 Oct 2025 11:11:18 -0700
From: ols6000_at_sbcglobal.net
To: curl-library_at_lists.haxx.se
Subject: How to interpret CURLE_WEIRD_SERVER_REPLY?
Message-ID: <1392465360.442848.1760811085783_at_sbcglobal.net>
Content-Type: text/plain; charset="us-ascii"
Message: 2
Date: Sat, 18 Oct 2025 19:04:14 +0000
From: Patrick Schlangen <patrick_at_schlangen.me>
To: libcurl development <curl-library_at_lists.haxx.se>
Cc: "ols6000_at_sbcglobal.net" <ols6000_at_sbcglobal.net>
Subject: Re: How to interpret CURLE_WEIRD_SERVER_REPLY?
Message-ID: <498ED1E5-8566-41FD-8F67-F79C9409A321_at_schlangen.me>
Content-Type: text/plain; charset="us-ascii"
Did you try capturing a verbose / traffic log for this?
Does it work when using curl from the command line?
Message: 3
Date: Sat, 18 Oct 2025 21:14:23 +0200
From: Patrick Monnerat <patrick_at_monnerat.net>
To: curl-library_at_lists.haxx.se
Subject: Re: How to interpret CURLE_WEIRD_SERVER_REPLY?
Message-ID: <01cd6b49-145e-4c80-8b98-840ecd79b7d2_at_monnerat.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 10/18/25 9:04 PM, Patrick Schlangen via curl-library wrote:
> Did you try capturing a verbose / traffic log for this?
> Does it work when using curl from the command line?
It seems the code activates ther verbose output, but it has not been
posted. This is mandatory to have this to answer the initial question.
Blindy, I can already say PLAIN mechanism is used instead of the Eudora
LOGIN choice, as the former is preferred by curl over the latter.
I don't know if it's the problem, but CURLOPT_LOGIN_OPTIONS could have
been used to force LOGIN mechanism.
Patrick
Attached is the verbose output from curl when I attempt to send an email using"secure mail keys" for authentication.
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- text/plain attachment: Curl_log_for_key.txt