Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

tab and multiple incoming folders

0 views
Skip to first unread message

Marc

unread,
May 27, 2005, 10:53:28 AM5/27/05
to
Hello,

let me describe my problem, maybe someone will see what I am doing wrong.
I have several incoming folders, one local, the others using imap/ssl.
Sometimes I just want to read the last new local message, so I enter my
inbox and press TAB several times to reach that message. But if I press
TAB one extra time, pine tries to open the imap folders, whereas I do not
want to leave the current folder. Then it asks for my password (I have a
ssh-agent running, couldn't it use it somehow?), and when I press CTRL-C
because I actually do not want to open that mailbox, it still asks me for
my password 3 times, when it seems cancel should meen: "I won't give you
my password".

Any help would be appreciated. For now I am using two different .pinerc
depending on the situation...

Marc

unread,
May 27, 2005, 1:31:54 PM5/27/05
to
Ok, let's concentrate on one single problem.
I have:
incoming-folders=Ens {myimapserver/ssl/novalidate-cert/user=glisse}INBOX
ssh-command="%s %s -x -q -l %s exec /usr/sbin/%sd"
ssh-path=/usr/bin/ssh
ssh-open-timeout=10

When I execute by hand:
/usr/bin/ssh myimapserver -x -q -l glisse exec /usr/sbin/imapd
I get (almost instantly):
* PREAUTH [...]
so everything is fine.
But pine still asks for my password to open this mailbox, and as far as I
can tell from using strace, it does not even try to call ssh (it just
checks whether it has the execution permission on /usr/bin/ssh).

Since I clearly did not write "norsh" anywhere, I do not understand why
pine does not try to connect with ssh...

Eduardo Chappa

unread,
May 27, 2005, 1:56:38 PM5/27/05
to
*** Marc (emarc....@gmail.comet) wrote in comp.mail.pine today:

:) incoming-folders=Ens {myimapserver/ssl/novalidate-cert/user=glisse}INBOX
:) ssh-command="%s %s -x -q -l %s exec /usr/sbin/%sd"
:) ssh-path=/usr/bin/ssh
:) ssh-open-timeout=10
:)
:) When I execute by hand:
:) /usr/bin/ssh myimapserver -x -q -l glisse exec /usr/sbin/imapd
:) I get (almost instantly):
:) * PREAUTH [...]
:) so everything is fine.
:) But pine still asks for my password to open this mailbox, and as far as I
:) can tell from using strace, it does not even try to call ssh (it just
:) checks whether it has the execution permission on /usr/bin/ssh).

ssl and ssh have more than one letter difference. They are completely
different mechanisms of authentication. That's why ssl does not pick your
ssh agent.

--
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Please send spam to webmaster@localhost

Eduardo Chappa

unread,
May 27, 2005, 2:00:55 PM5/27/05
to
*** Marc (emarc....@gmail.comet) wrote in comp.mail.pine today:

:) I have several incoming folders, one local, the others using imap/ssl.
:) Sometimes I just want to read the last new local message, so I enter my
:) inbox and press TAB several times to reach that message. But if I press
:) TAB one extra time, pine tries to open the imap folders, whereas I do not
:) want to leave the current folder. Then it asks for my password (I have a
:) ssh-agent running, couldn't it use it somehow?), and when I press CTRL-C
:) because I actually do not want to open that mailbox, it still asks me for
:) my password 3 times, when it seems cancel should meen: "I won't give you
:) my password".

I agree. I am writing a patch to avoid this problem. Your report made me
realize about a problem that I had found earlier about cancelling a
connection to a server while pressing TAB. Thank you!

Marc

unread,
May 27, 2005, 2:08:38 PM5/27/05
to
Eduardo Chappa wrote:

> ssl and ssh have more than one letter difference. They are completely
> different mechanisms of authentication. That's why ssl does not pick your
> ssh agent.

Right, I removed /ssl and it works fine now, thank you very much!
(well there is still the issue about ssh-command being the same for every
remote server, but this is already cool)

0 new messages