Subject: Bug in 4.52 (and others)?

From: Stefan Goessling-Reisemann <[email-masked]>
Date: Tue, 21 Jan 2003 12:28:46 +0100 (Westeuropäische Normalzeit)

Dear List,

I mentioned the following two problems in the newsgroup comp.mail.pine,
but got no sufficient answer. Maybe you can comment?

1) I have my .pinerc on my IMAP server (actually it is sitting there in my
home-dir). The server is an IRIX64 6.5, the simapd version I do not know,
but when startet by hand it says: IMAP4rev1 v12.264.

I start Unix-Pine (4.33 on different Unixes/Linux) and PC-Pine (4.44,
4.51, 4.52, 4.53 on Win 98, NT, XP) on different machines with the option
-p{imapserver/user=myusername/ssl}.pinerc, which always works fine.  Just
when I look at the actual .pinerc in my home-dir it tends to get bigger
and bigger over time. To be precise: in doubles in size every once in a
while, and I cannot figure out under what circumstances. If I look at the
.pinerc with Pine (opening it as a mail folder, which it actually is), I
see 5 'messages', the first one being only some general information, the
other four being configurations (3 old ones, one actual one). So far so
good. In the course of a few weeks, the size of the configurations
increased from 8 to 17 to 33 kB to .... Upon inspection, I saw that each
configuration message contained one (two, four, ..) sets of the
configuration settings appended to each other.

It is no problem to work with the multiple settings, since they seem to be
exactly identical. The problem is the file size: the whole .pinerc can get
as big as several MB (!!) which causes a significant slow down.

2) A rather small problem occurs with PC-Pine 4.52 (and 4.53) when used as
the default 'mailto:' client. We want to set up PC-Pine as the default
mailer on Windows NT 4.0 and XP. When 'i' is set as the initial command in
Pine and then one opens a mailto: link from a browser, Pine starts but
hangs indefinitely. This does not happen when sending a web-page via 'File
-> Send -> Send page via email' (i.e. using MAPI). Maybe you can provide a
solution? Otherwise we (IT department) will just write a small readme file
warning about this.

Thanks for your replies!!
Best regards,
Stefan Gößling-Reisemann
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Jeff Franklin <[email-masked]>
Date: Tue, 21 Jan 2003 18:51:45 -0800 (PST)

Hello again Stefan,

On Tue, 21 Jan 2003, Stefan Goessling-Reisemann wrote:

> while, and I cannot figure out under what circumstances.
...

We have definitely not encountered this problem.  One thing I notice is
that you are using a pretty old version of UW-imapd, so the problem might
be with that, but perhaps we can figure out if it's a problem with pine
itself.  Is the problem reproducible?  Try changing something in your
remote pinerc.  Does it double in size when you do that?  If so, if you
could send us some debugging information where you reproduce this, it
would be most helpful.  To do this, run 'pine -d imap=4,verbose=9' and
send us the .pine-debugN file that it creates after having reproduced the
problem and exiting.

> hangs indefinitely.

We've gotten to the bottom of this one, and it looks like it has to do
with the 'i' initial command used in conjunction with a remote address
book.  It's actually prompting for a password without actually showing any
prompts, which is a rather unfortunate bug.  There are a couple of
workarounds that I can think of, but neither of them are all that pretty.
The first workaround is to edit the registry, which the more transparent
workaround.  Both keys
HKEY_LOCAL_MACHINE\Software\Clients\Mail\PC-Pine\Protocols\Mailto\shell\open\command
and HKEY_CLASSES_ROOT\mailto\shell\open\command need to have their default
string changed such that you would add the argument
"-initial-keystroke-list=" added to the list of arguments.  An example
registry entry might be the following line:

"C:\Program Files\PC-Pine\pine.exe" -url "%1" -initial-keystroke-list=

 A second workaround would be to use an exception config and store the
initial-keystroke-list only in that config (I'd certainly go with the
first workaround).

This bug will be fixed in the next version, but hopefully one these
workarounds will be sufficient until that time.

Thanks for the reports!

Jeff

---

From: "Koth Mire" <[email-masked]>
Date: Wed, 22 Jan 2003 01:16:57 -0800

Hi, 

When using "Reverse Thread" sort order on my inbox, I expect the "delete"
to mark current message deleted and go to the "prev" message in the
thread and not the "next". This is because the first message of the
thread is at the bottom of the thread and the subsequent messages are
towards the top. Hence on reading the first message, when I say "delete",
the "prev" message should become the current message. As of now, the
"next" message becomes the current message and as a result, I move out of
the current thread !

1. Is there anyway to achive this ? (Im using 4.44 on RHLinux 8.0)
2. If not, will this be considered feature for some future release of
pine ?
3. Is there a patch to achieve this (by good ol' Eduardo or anyone else)
?

Regards,

Kothmire

-- 
http://fastmail.fm - A no graphics, no pop-ups email service
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------