Forgive me if I've been asleep at the switch on the SSL problem and it's already been figured out, but....could this be what the prob is?
-------- Original Message -------- Subject: Re: [Pine-info] "incomplete SecBuffer exceeds maximum buffer size" ? Date: Mon, 27 Apr 2009 09:47:04 -0700 (PDT) From: Steve Hubert <hubert@washington.edu> Organization: Univ of Washington; UW Technology; Seattle To: Pine Forum <pine-info@u.washington.edu> References: <Pine.WNT.4.64.0904261823300.-1877079@zuluone>
There is a feature called quell-ssl-largeblocks that addresses this. In alpine it is called "Prevent SSL Largeblocks". The help text in alpine says
FEATURE: Prevent SSL LargeblocksPC-Alpine only.
This feature changes the behavior of fetching messages and attachments so that the message data is fetched in chunks no larger than 12K bytes. This works around a bug in Microsoft's SSL/TLS support. Some versions of Microsoft SSL are not able to read full-sized (16K) SSL/TLS packets. Some servers will send such packets and this will cause PC-Alpine to crash with the error
incomplete SecBuffer exceeds maximum buffer sizeMicrosoft is aware of the problem and has developed a hotfix for it, it is discussed in article 300562 in the Microsoft Knowledge Base.
Pine-info mailing list Pine-info@u.washington.edu http://mailman1.u.washington.edu/mailman/listinfo/pine-info
-- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035