I was reading over austin hook's problems with the alpine email client
that were posted in misc@. I too have been having problems with alpine in
6.8 stable which are new. I have used alpine for many many years and it
just worked fine.
Like austin, I have had lockups and with the program doing things like
composing, to chaining to external programs like a browser to using xv to
display images. The problems are intermittment but never occurred prior
to 6.8. I guess ktrace is in my future?
Couple of questions about alpine:
Question 1
In working through some of my problems I found that the pkg and port are
compiled with debug disabled. Is there a reason for that default
instead of compiling with debuglevel=0 and setting a low number for the
number of debug files to save?
I created an install with debug enabled which allowed me to use various
command line switches to control how much information was being written to
the debug files. This helped show a communication problem with a
particular imap server was not a timeout but rather an SSL
handshake failure that occurs intermittmently. The debug log minus my
email address as logged
IMAP 11:56:18 1/8 mm_log tcp: DNS resolution mail.acsalaska.net
IMAP 11:56:18 1/8 mm_log tcp: DNS resolution done
IMAP 11:56:18 1/8 mm_log babble: Trying IP address [66.226.70.80]
IMAP 11:56:18 1/8 mm_log tcp: Stream open and ready for read
IMAP 11:56:18 1/8 mm_log tcp: Reading SSL data
IMAP 11:56:22 1/8 mm_log tcp: SSL data read I/O error 54 SSL error 5
IMAP 11:56:22 1/8 mm_notify bye:
{mail.acsalaska.net/user=xx...@xxxxxx.xxx/ssl/novalidate-cert}inbox:
[CLOSED] IMAP connection broken (server response)
IMAP 11:56:22 1/8 mm_log error: [CLOSED] IMAP connection broken (server
response)
error 54 SSL error 5 is the problem still looking how to fix it or if it
something with that particular server.
Question 2
The version in ports and pkgs is shown as 2.21 with some patches. The
source location is pointed to alpine.x10host.com which is apparently the
"new" home for the program. The current version is shown as version 2.24.
Is there a reason this isn't being used. One of the interesting issues in
this version is trying to address issues connecting to the yahoo imap
server, which for me stopped working a couple of months ago. Debug logs
showed (with the source ip blanked out)
IMAP DEBUG 21:15:06 1/7: 00000000 OK AUTHENTICATE completed
IMAP DEBUG 21:15:06 1/7: 00000001 ID ("name" "alpine" "version" "2.21")
IMAP DEBUG 21:15:06 1/7: * ID ("remote-host" "xxx.xxx.xxx.xxx" "vendor"
"Yahoo! Inc." "support-url" "http://help.yahoo.com/"; "name" "Y!IMAP"
"host" "sky300148.imap.mail.yahoo.com" "version" "1.1.16979")
IMAP DEBUG 21:15:06 1/7: 00000001 OK ID completed
IMAP DEBUG 21:15:06 1/7: 00000002 SELECT INBOX
IMAP DEBUG 21:15:11 1/7: 00000002 BAD [CLIENTBUG] SELECT Command is not
valid in this state
IMAP 21:15:11 1/7 mm_log error: IMAP protocol error: [CLIENTBUG] SELECT
Command is not valid in this state
IMAP 21:15:11 1/7 mm_log error: [CLIENTBUG] SELECT Command is not valid in
this state
I have yet to figure out what "Command is not valid in this state" means
I just show these as examples of the debug log that alpine can create if
debug is enabled.
peter
