Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 23 |
Nodes: | 6 (0 / 6) |
Uptime: | 57:00:35 |
Calls: | 584 |
Calls today: | 1 |
Files: | 1,139 |
D/L today: |
179 files (27,921K bytes) |
Messages: | 112,134 |
you seem to be using an old version of imapd.c. From the current bits
ptext is between lines 3878 and 3883, so it seems you are using an old version.
The advice in these cases is to upgrade your version to a newer version.
Eduardo Chappa dixit:
you seem to be using an old version of imapd.c. From the current bits
ptext is between lines 3878 and 3883, so it seems you are using an old
version. The advice in these cases is to upgrade your version to a
newer version.
AFAICT I have the latest known version, perhaps did the distribution
site change? Can you point me to the latest?
On Sun, 13 Jul 2025, Thorsten Glaser wrote:
Eduardo Chappa dixit:
you seem to be using an old version of imapd.c. From the current bits
ptext is between lines 3878 and 3883, so it seems you are using an
old version. The advice in these cases is to upgrade your version to
a newer version.
AFAICT I have the latest known version, perhaps did the distribution
site change? Can you point me to the latest?
Tough question to answer, since there is no official distribution of
imapd. This is what I can tell you.
The latest bits created by Mark Crispin are located at
https://github.com/jonabbey/panda-imap
I do not know if they have ever been updated. For example to update the
code based on changes in the openssl library API.
The bits for imapd in the source code of alpine have been updated for changes in the openssl library API, but I have never updated the imapd
code, so it is probably the same as in github, but I have updated the underlying c-client library to work with Alpine, no testing of the imapd code has ever been done, so if you go that way, use it at your own risk.
I hope this helps.
TLS_client_method
RSA_generate_key_ex