Subject: Re: Remote rsh timeout

From: [email-masked] (Sylvain Robitaille)
Date: 11 Jan 1997 21:03:57 GMT

On Tue, 7 Jan 1997 14:45:54 -0800, Charles Mott <[email-masked]> wrote:
>Whenever I connect to my mail server, there is a long delay due to a
>"remote rsh timeout", followed by the username prompt.  How can I avoid
>this delay?

Add your username to the remote inbox definition:

{host/user=userid}inbox

However you'll still get the delay, as it will still want your password. I
don't think there's a way to have it store your password anywhere;
(wouldn't be a safe thing to do, anyway).

-- 
----------------------------------------------------------------------
Sylvain Robitaille
[email-masked]          http://alcor.concordia.ca/~sp_robi

All this wheeling and dealing around, why, it isn't for money, it's for
fun.  Money's just the way we keep score.
----------------------------------------------------------------------

---

From: Mike Brudenell <[email-masked]>
Date: Tue, 14 Jan 1997 09:45:47 +0000 (GMT)

> Add your username to the remote inbox definition:

Not quite: the minimal solution to avoid the long delay due to the "remote
rsh timeout" is to add the port number to the end of the hostname:

	{host.site.domain:143}inbox

This will then prompt you to supply your username and password as usual,
but without the long delay.  This is because by supplying a port number
you are telling Pine (actually the underlying C-client library) to bypass
the rsh mechanism.

> (wouldn't be a safe thing to do, anyway).

If you want to avoid having to enter your username and password...

...if you are using PC-Pine then there is an option to save these.
However be warned that you should only do this if your machine is secure,
otherwise there may be a chance others can make use of the information to
your detriment.

...if you are using the UNIX version of Pine then you should ask your
Systems Administrator to consider setting up the pre-authenticated IMAP
server.  The minimal work they need to perform is simply to create a
symbolic link so that the file /etc/rimapd points to the real imapd
executable.  Each person wanting to make use of the facility will then
need to set up a ".rhosts" file to allow their imap server to accept rsh
connections from the machines they normally use.  (Or else the SysAdmin
could set up a systemwide hosts.equiv file on the imap server computer.)

Cheers,

-- 
Mike Brudenell                                         <[email-masked]>
------------------------------------------------------------------------
The Computing Service, University of York, Heslington, York, YO1 5DD, UK
Tel: +44-1904-433811  FAX: +44-1904-433740  http://www.york.ac.uk/~pmb1/

---

From: Charles Mott <[email-masked]>
Date: Tue, 7 Jan 1997 14:45:54 -0800

Charles Mott

---

From: [email-masked] (Sylvain Robitaille)
Date: 15 Jan 1997 06:18:48 GMT

>you are telling Pine (actually the underlying C-client library) to bypass

Ok, but then this assumes that imapd nust be listening to port 143, right?
In most cases this will be ok, but there's bound to be the odd one...

Two can Live as Cheaply as One for Half as Long.
		-- Howard Kandel
----------------------------------------------------------------------

---

From: Mike Brudenell <[email-masked]>
Date: Mon, 20 Jan 1997 09:07:59 +0000 (GMT)

> In most cases this will be ok, but there's bound to be the odd one...

Correct... I was assuming that if someone is able to set up the IMAP
server on a non-standard port then they'd have enough nouse to realise to
put that port number into the above once they know the syntax exists.

One has to make _some_ assumptions at times.  (sigh:-)