Re: pine 4.62 doesn't re-login for sent-mail folder if connection lost

On Fri, 16 Feb 2007, Matt Ackeret wrote:
> On Fri, 16 Feb 2007, Ross wrote:
>> On Wed, 14 Feb 2007, Matt Ackeret wrote:
>>> If my INBOX is "CLOSED DUE TO ACCESS ERROR"(*), and I try to 
>>> send mail, it tells me that sent-mail doesn't exist, do you 
>>> want to create? It doesn't automatically log me back in.

>> An IMAP sent-mail folder would not exist if the INBOX folder 
>> is closed. Pine would offer to create a local version. For 
>> auto-relogin - how do you have the folder-reopen-rule set? 
>> Or any of the keep open folder settings?

> I don't see anything relating to "keep open folder" settings. 
> I looked over all instances of "folder" in the setup/config 
> screen.  (Remember, I'm using old 4.62 because I had weird 
> issues whenever I tried newer versions.)

My mistake for being half asleep/tired, my intent was stay-open 
or reopen folders, there is no keep-open.

> I *did* just turn on Always for the reopen rule.  That sounds 
> like it'd be good.  I hate having to < out and > back in.

That was one of my references that may solve the problem. While 
Pine help says the INBOX is a stay-open folder by default, if it 
is closed for any reason, it apparently by defualt does not 
reopen until told, or by setting the reopen rule appropriately.

>> Is the sending server authenticated with a read-before-send timer design?

> ?SYNTAX ERROR<BEEP>
> I don't understand what that means.

If the system/server is not a true authenticated setup, it may be 
setup as read-before-send authentication (Pine help refers to 
this as POP before SMTP / IMAP before SMTP) that is typically 
timer controlled. This is explained to some degree in Pine help 
for the Setup-Config SMTP-server entry.

In a read-before-send design, the user must perform an INBOX read 
before sending a message. The read starts a timer for say 30 
minutes. That supposedly blocks the junk mail relay problem I 
guess in a cheap way.

But if you don't access the INBOX often to read it (within the 
timer setting of ? - ask the server admin for the minutes they 
set), the ability to send ends until you do another INBOX read. 
The INBOX staying open don't count. And if the INBOX closes for 
any reason, the ability to send ends, I believe even if the 
reopen rule reopens it, until user performs a read. The 
authentication wants to see an actual read of the INBOX.

Sounds goofy really, but multiple server admins explained this to 
me over past problems I suffered. So I prefer true authentication 
systems.

-- 
RossARR
[email protected]
mrossarr.nixsyspaus.org/ 
---end-of-message---
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info