[Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"

[Thomas Gramstad via Alpine-info]

That one is set in my config. Yes, maybe test turning it off?

But when I changed "Incoming Check Timeout" from 1500 to 30, I 
also adjusted "Incoming Check Interval" from 15 to 30, to align
with the old postings' recommendations. I didn't think that would
mean much, but perhaps it did.

Thomas


On Thu, 6 Feb 2025, Barry Landy wrote:


> I notice this only has an effect if "Enable Incoming Folders Checking" 

> is set. Maybe unset that (if it is set)?

> 

> On Thu, 6 Feb 2025, Thomas Gramstad wrote:

> 

> :>

> :>I changed "Incoming Check Timeout" from 1500 to 30. This has 

> :>greatly reduced the problem. Not eliminated it, but it happens

> :>much less frequently.

> :>

> :>Thanks for the TCP values, I'll add those too.

> :>

> :>PS: Also, the > and then choose INBOX folder works too -- not

> :>necessary to quit or logout+login.

> :>

> :>Thomas

> :>

> :>

> :>On Wed, 5 Feb 2025, Barry Landy via Alpine-info wrote:

> :>

> :>> I experimented with some settings which have helped a lot but not cured 

> :>> the problem completely.

> :>> 

> :>> the settings are

> :>> 

> :>> mail checkinterval has always been large

> :>> 

> :>> TCP open timeout = 100

> :>> TCP query timeout = 100

> :>> TCP close connection timeout=150 

> :>> (this i first made 100 then raised it)

> :>> 

> :>> I put these in individually and observed effects.

> :>> 

> :>> I still get the dread message occasionally with no common factor that I 

> :>> can spot. I would be greateful for other suggestions of what to try.

> :>> 

> :>> FYI I am running under Windows (11) and not UNix.

> :>> 

> :>> 

> :>> 

> :>> On Sun, 2 Feb 2025, Barry Landy via Alpine-info wrote:

> :>> 

> :>> :>I have exactly the same problem for exactly the same reason. 

> :>> :>

> :>> :>Not due to mail check interval as that was already large.

> :>> :>

> :>> :>I am extremely interested to know if any of you get anywhere with 

> :>> :>setting timeout values.

> :>> :>

> :>> :>

> :>> :>On Sun, 2 Feb 2025, Thomas Gramstad via Alpine-info wrote:

> :>> :>

> :>> :>:>

> :>> :>:>Thank you Milt, those links were very informative!

> :>> :>:>

> :>> :>:>Then I checked all the timeout values in my config:

> :>> :>:>

> :>> :>:>I have Check incoming mail interval at 15 seconds, and

> :>> :>:>vaguely remember there was a reason for that many years

> :>> :>:>ago.

> :>> :>:>

> :>> :>:>I have at least 4 TCP-related timeouts, but they are all

> :>> :>:>set at "No Value". I suspect I should do something about

> :>> :>:>that. What does "No Value" mean for those?

> :>> :>:>

> :>> :>:>Then there is this one, which I have no idea what means:

> :>> :>:>

> :>> :>:>User Input Timeout              = <No Value Set: using "0"> 

> :>> :>:>

> :>> :>:>There are a few others (like "Rsh timeout") which sound

> :>> :>:>less relevant.

> :>> :>:>

> :>> :>:>So there seem to be quite a few more timeouts in Alpine now than 

> :>> :>:>in 2016.

> :>> :>:>

> :>> :>:>(By "logging into Alpine" I meant the OAuth thing which requires

> :>> :>:>me to enter a password that it has stored.)

> :>> :>:>

> :>> :>:>I'll try the < up one level thing the next time the disconnect 

> :>> :>:>occurs.

> :>> :>:>

> :>> :>:>But please advise about the 4 TCP settings above.

> :>> :>:>

> :>> :>:>Thomas Gramstad

> :>> :>:>

> :>> :>:>

> :>> :>:>On Sun, 2 Feb 2025, Milt Epstein via Alpine-info wrote:

> :>> :>:>

> :>> :>:>> I didn't think I had anything to say about this because I haven't

> :>> :>:>> experienced this error, but then I found a reference to this error

> :>> :>:>> message in my saved mail, in an old thread on this mailing list (from

> :>> :>:>> January 28, 2016).

> :>> :>:>> 

> :>> :>:>> So I went to the mailing list info url in each list message:

> :>> :>:>> 

> :>> :>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info

> :>> :>:>> 

> :>> :>:>> and went to the list archives.  But the list archives there only goes

> :>> :>:>> back about three years.  But I did find a list archive at marc.info:

> :>> :>:>> 

> :>> :>:>> https://marc.info/?l=alpine-info&r=1&w=2

> :>> :>:>> 

> :>> :>:>> And then from January 2016:

> :>> :>:>> 

> :>> :>:>> https://marc.info/?l=alpine-info&r=1&b=201601&w=2

> :>> :>:>> 

> :>> :>:>> And then the thread in question ([Alpine-info] Best timeout settings

> :>> :>:>> for connecting to Exchange server?):

> :>> :>:>> 

> :>> :>:>> https://marc.info/?t=145399947700006&r=1&w=2

> :>> :>:>> 

> :>> :>:>> You might take a look at that to see if there's anything helpful

> :>> :>:>> there.

> :>> :>:>> 

> :>> :>:>> Also, people's suggestion to back out of the folder (using "<") and

> :>> :>:>> re-enter it (rather than quitting Alpine) seems worth a try.

> :>> :>:>> 

> :>> :>:>> BTW, what do you mean by "log in to Alpine"?  (Because one doesn't

> :>> :>:>> really have to log in to alpine.  Probably you're having alpine

> :>> :>:>> connect to some mail server -- which may be relevant to getting that

> :>> :>:>> error message; but it does seem that others replying to your message

> :>> :>:>> have figured that out.)

> :>> :>:>> 

> :>> :>:>> Milt Epstein

> :>> :>:>> mepstein at illinois.edu

> :>> :>:>> 

> :>> :>:>> 

> :>> :>:>> On Sun, 2 Feb 2025, Thomas Gramstad via Alpine-info wrote:

> :>> :>:>> 

> :>> :>:>> > The Subject: line is an error message that I get very often

> :>> :>:>> > in Alpine, like several times per hour:

> :>> :>:>> > 

> :>> :>:>> > [MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]

> :>> :>:>> > 

> :>> :>:>> > When this happens, in the folder I am in I can still see the 

> :>> :>:>> > numbered list of messages, but if I try to open a message to read 

> :>> :>:>> > it, there is nothing to read. I then have to quit Alpine, start 

> :>> :>:>> > Alpine a new, and log in to Alpine, and then I can read the 

> :>> :>:>> > messages.

> :>> :>:>> > 

> :>> :>:>> > This frequent need to quit and restart is annoying. Is there 

> :>> :>:>> > something I can do to prevent, or at least reduce the number of 

> :>> :>:>> > such incidents? Like checking something more often, or less 

> :>> :>:>> > often, or switch something off?

> :>> :>:>> > 

> :>> :>:>> > Thomas Gramstad

> :>> :>:>> > _______________________________________________

> :>> :>:>> > Alpine-info mailing list

> :>> :>:>> > Alpine-info at u.washington.edu

> :>> :>:>> > https://urldefense.com/v3/__http://mailman12.u.washington.edu/mailman/listinfo/alpine-info__;!!DZ3fjg!6Wjel1CAJEdPWB9pFlfWG1dMiSfiJ70n2wME-SxsxsrM_yvDp8HOFQEpNkJ9DuV2GFcMP7yAahkNSOuXydQJE5tIQQhdAB0i$ 

> :>> :>:>> > 

> :>> :>:>> _______________________________________________

> :>> :>:>> Alpine-info mailing list

> :>> :>:>> Alpine-info at u.washington.edu

> :>> :>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info

> :>> :>:>> 

> :>> :>:>_______________________________________________

> :>> :>:>Alpine-info mailing list

> :>> :>:>Alpine-info at u.washington.edu

> :>> :>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info

> :>> :>:>

> :>> :>

> :>> :>

> :>> 

> :>> 

> :>

> 

>