Subject: INBOX CLOSED DUE TO...

From: Yossi Itzkovich <[email-masked]>
Date: Sun, 14 Sep 1997 16:18:01 +0200 (IST)

Hi all !

Sometimes when I have communication problems or when I start another pine
in an another host , pine tells me that :
INBOX IS CLOSED DUE TO ... (I don't remember the rest of the line).

This is OK, but when I solve the problem (communication is back or I quit
the other session of pine), pine still doesn't know that it's OK now.

Is there a way to tell pine to try to open INBOX again, or the only
solution is just to quit and restart ?

Thanks,

Yossi

---

From: "Robin S. Socha" <[email-masked]>
Date: 14 Sep 1997 22:18:56 +0200

>> Yossi Itzkovich writes:

YI> Sometimes when I have communication problems or when I start
YI> another pine in an another host , pine tells me that : INBOX IS
YI> CLOSED DUE TO ... (I don't remember the rest of the line).

Access error...

YI> This is OK, 

No, it isn't.

YI> but when I solve the problem (communication is back or I quit the
YI> other session of pine), pine still doesn't know that it's OK now.

Because it isn't.

YI> Is there a way to tell pine to try to open INBOX again, or the
YI> only solution is just to quit and restart ?

You cannot run more than one pine session at a time, due to the arcane
file locking mechanisms it uses. Your second session is trying to
"override" the lock and pine write-protects both sessions.

Cheers,
Robin

-- 
Robin S. Socha, M.A.
Political Science Dept., Bonn University, Bonn

---

From: Yossi Itzkovich <[email-masked]>
Date: Mon, 15 Sep 1997 08:51:47 +0200 (IST)

> YI> CLOSED DUE TO ... (I don't remember the rest of the line).

For me it is OK, since I know that I am the responsible for it !

> "override" the lock and pine write-protects both sessions.

Thanks Robin for the explanation, but you didn't give me any answer to my
question:

Is there a way to tell pine to try to open INBOX again (after there is
one pine session again) , or the only solution is just to quit and restart ?

Yossi

---

From: Shawn Jeffries <[email-masked]>
Date: Tue, 16 Sep 1997 13:57:12 -0400 (EDT)

Robin,

I've looked everywhere I can think of, but I can't find how to
make the Reply Indicators in a reply to be the sender's initials.

Can you help me out? 

Shawn

>YI> CLOSED DUE TO ... (I don't remember the rest of the line).

 ... rest cut

---

From: "Robin S. Socha" <[email-masked]>
Date: 16 Sep 1997 20:34:09 +0200

>> Regarding Reply indicators; Shawn Jeffries <[email-masked]>
>> adds: 

SJ> Robin, I've looked everywhere I can think of, but I can't find
SJ> how to make the Reply Indicators in a reply to be the sender's
SJ> initials.  Can you help me out?

It's a secret. If I told you, I'd have to shoot you afterwards. 
Sorry, dude...

But a web-search for XEmacs, Gnus and Supercite might be quite
fruitful. Make sure to write-protect anything that says pine
beforehand - you'll never want to switch back }:->

Cheers,
Robin

-- 
Robin S. Socha, M.A.
Political Science Dept., Bonn University, Bonn
"They don't let you teach there, do they?"
Annelise Anderson in comp.mail.pine

---

From: Mike Brudenell <[email-masked]>
Date: Mon, 22 Sep 1997 11:58:46 +0100 (BST)

> > "override" the lock and pine write-protects both sessions.

Ummmm.... actually what _should_ happen is this:

The second Pine session spots that the mailbox is already in use by
another mail client.  It then "negotiates" write-access to the mailbox,
leaving the previous client with read-only access.  A suitable message is
displayed to this effect.

However if file locking isn't working properly on your system the second
Pine _doesn't_ spot the previous instance of a mail client.  Instead they
both happily try to use/update the mail folder.  Fortunately Pine's
defensive behaviour {always? usually?} spots the conflict and one or both
end up with the folder getting unceremoniously closed dues to "an access
error".

The effct is the same however: only one Pine session can have write-access
to a folder at any given time.

> one pine session again) , or the only solution is just to quit and restart ?

In the case of the INBOX you must quit out of and then re-run Pine.

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/

* Unsolicited commercial e-mail is NOT welcome at this e-mail address. *