From alpine-info at u.washington.edu  Sun Feb  2 11:22:34 2025
From: alpine-info at u.washington.edu (Thomas Gramstad via Alpine-info)
Date: Sun Feb  2 11:22:42 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
Message-ID: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>

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
From alpine-info at u.washington.edu  Sun Feb  2 11:29:06 2025
From: alpine-info at u.washington.edu (Chime Hart via Alpine-info)
Date: Sun Feb  2 11:29:20 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
Message-ID: <281fc5fd-1fc6-58dd-6d08-9b29f28a3efa@hubert-humphrey.com>

Wow, Thomas, while I've never seen an error during regular mail reading, I used 
to get that when saving groups of binary news-group messages to a file. 
Also-and-I guess this isn't your situation, but a second instance of opening 
Alpine will make 1 of them as read only.
Chime

From alpine-info at u.washington.edu  Sun Feb  2 11:31:02 2025
From: alpine-info at u.washington.edu (Bret Busby via Alpine-info)
Date: Sun Feb  2 11:31:21 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
Message-ID: <d5dc0d4a-5c15-4e36-a95e-10075cbdfc41@busby.net>

On 3/2/25 03:22, 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

I think it is due to the connection to the mailserver host, being broken 
or disrupted.

One thing to try, that I apply when connecting to my incoming 
mailserver, is using the back arrow (<) to go up yo the next level, 
then, press Enter/Return (<CR>) to go back to the Inbox.

I use Thunderbird as a webmail interface, to access my incoming 
mailserver, then, once a month, on the last day, I log in to my incoming 
mailserver, using alpine, to download and archive my incoming email, 
and, I frequently get that error to which you refer, and, I simply apply 
what I have said.

It is only when the procedure that I have described, does not work, that 
I have to quit alpine and log in again.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..............

From alpine-info at u.washington.edu  Sun Feb  2 11:32:16 2025
From: alpine-info at u.washington.edu (David Lang via Alpine-info)
Date: Sun Feb  2 11:32:20 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
Message-ID: <alpine.DEB.2.02.2502021128350.26383@nftneq.ynat.uz>

Thomas Gramstad 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.

you can go back to the main menu or the list of folders and reopen the folder 
instead of exiting alpine

This is probably happening because you have a firewall/router that is timing out 
your connection between your client and mail server.

David Lang
From alpine-info at u.washington.edu  Sun Feb  2 11:35:57 2025
From: alpine-info at u.washington.edu (Thomas Gramstad via Alpine-info)
Date: Sun Feb  2 11:36:03 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <281fc5fd-1fc6-58dd-6d08-9b29f28a3efa@hubert-humphrey.com>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<281fc5fd-1fc6-58dd-6d08-9b29f28a3efa@hubert-humphrey.com>
Message-ID: <af34d4fc-b7f4-f51f-d68-b3cfb08ede43@ifi.uio.no>


Thanks Chime, but no, that is not my situation. Only one instance 
of Alpine. I suspect it is something to do with Alpine's 
interaction with Microsoft Exchange/Office365/OAUTH which has 
been enforced at the university. It happens with the same 
frequency while I am at work, as when I'm at home logging into 
the university network with ssh. So I don't think it is anything 
to do with ssh.

And I'm not doing anything specific, I only have a window open
with Alpine running in it.

Thomas


On Sun, 2 Feb 2025, Chime Hart wrote:

> Wow, Thomas, while I've never seen an error during regular mail 
> reading, I used to get that when saving groups of binary 
> news-group messages to a file. Also-and-I guess this isn't your 
> situation, but a second instance of opening Alpine will make 1 
> of them as read only.
> Chime
From alpine-info at u.washington.edu  Sun Feb  2 11:54:19 2025
From: alpine-info at u.washington.edu (David Morris via Alpine-info)
Date: Sun Feb  2 11:54:26 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <af34d4fc-b7f4-f51f-d68-b3cfb08ede43@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<281fc5fd-1fc6-58dd-6d08-9b29f28a3efa@hubert-humphrey.com>
	<af34d4fc-b7f4-f51f-d68-b3cfb08ede43@ifi.uio.no>
Message-ID: <13385d6e-b556-68f1-2fd3-1302a98d45ce@xpasc.com>


I've had this happen when two processes attempt to access the INBOX at the
same time. I think when both are attempting to gain exclusive write
access. In my case, my alpine runs on my mail server so I'm not sure how
this applies to your setup. It might be that exchange/windows file access
control is more restrictive than what alpine experiences on Linux. My
error is associated with alpine as one process and my imap server as
another. On Linux, mail delivery doesn't seem to cause a problem.

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

>
> Thanks Chime, but no, that is not my situation. Only one instance
> of Alpine. I suspect it is something to do with Alpine's
> interaction with Microsoft Exchange/Office365/OAUTH which has
> been enforced at the university. It happens with the same
> frequency while I am at work, as when I'm at home logging into
> the university network with ssh. So I don't think it is anything
> to do with ssh.
>
> And I'm not doing anything specific, I only have a window open
> with Alpine running in it.
>
> Thomas
>
>
> On Sun, 2 Feb 2025, Chime Hart wrote:
>
> > Wow, Thomas, while I've never seen an error during regular mail
> > reading, I used to get that when saving groups of binary
> > news-group messages to a file. Also-and-I guess this isn't your
> > situation, but a second instance of opening Alpine will make 1
> > of them as read only.
> > Chime
> _______________________________________________
> Alpine-info mailing list
> Alpine-info@u.washington.edu
> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
>
> ----------
>
> This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the following link to report this email as spam:
> https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5fdc145c50d69f12ae61efdeed04d564660e4a167826de8481520af3faa2656781fdd1865bee73b6314211a57d75fe88b42093ebb7bd00e85d1631fad73f459691342b0c70026fceda7c501326c19ae063c20cccb1e1b4c7e5d5ed4bf3b24f99a577733f7576a31545026a8e38294e9d7004ffe6a303313fcc5e6e403a2957c8d20079a9845837529d
>
From alpine-info at u.washington.edu  Sun Feb  2 12:00:50 2025
From: alpine-info at u.washington.edu (Milt Epstein via Alpine-info)
Date: Sun Feb  2 12:01:07 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
Message-ID: <0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>

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@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@u.washington.edu
> https://urldefense.com/v3/__http://mailman12.u.washington.edu/mailman/listinfo/alpine-info__;!!DZ3fjg!6Wjel1CAJEdPWB9pFlfWG1dMiSfiJ70n2wME-SxsxsrM_yvDp8HOFQEpNkJ9DuV2GFcMP7yAahkNSOuXydQJE5tIQQhdAB0i$ 
> 
From alpine-info at u.washington.edu  Sun Feb  2 12:42:28 2025
From: alpine-info at u.washington.edu (Thomas Gramstad via Alpine-info)
Date: Sun Feb  2 12:42:36 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
Message-ID: <a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>


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@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@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@u.washington.edu
> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
> 
From alpine-info at u.washington.edu  Sun Feb  2 14:02:51 2025
From: alpine-info at u.washington.edu (Barry Landy via Alpine-info)
Date: Sun Feb  2 14:03:00 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
Message-ID: <1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>

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@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@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@u.washington.edu
:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>> 
:>_______________________________________________
:>Alpine-info mailing list
:>Alpine-info@u.washington.edu
:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>

-- 
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-362062
				   Mobile	+44-7771-933945
Cambridge CB4 3PB
England				   Email	BarryLandy@cantab.net
From alpine-info at u.washington.edu  Sun Feb  2 17:25:34 2025
From: alpine-info at u.washington.edu (Milt Epstein via Alpine-info)
Date: Sun Feb  2 17:25:43 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
Message-ID: <1a3f4306-69a9-fe8f-13a8-b996ff91a382@illinois.edu>

For more information on these timeouts (like what exactly they affect
and what it means if there're no values set), you'll have to hear from
others, perhaps Eduardo.  I'll just add that my .pinerc has comments
before these settings that give some explanation of what they control
and what the default values are (which are sometimes 0, which may mean
the timeout is off).  Also, in the config, I think you can hit "?" for
help when looking at a setting to get more info about it.

I thought it might be the check incoming mail timeout value, which was
somewhat highlighted in that previous thread -- but someone responded
in this thread that they were having the same problem as you and had
already tried changing that value.

Some other suggestions:

You can try changine one or two of these timeouts, to see whether that
makes a difference in the behavior.

Maybe you can run alpine with a higher debug level, and then when it
disconnects, you may have more information there that can guide you to
a soluation.

Milt Epstein
mepstein@illinois.edu


On Sun, 2 Feb 2025, Thomas Gramstad 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:
> > 
> > https://urldefense.com/v3/__http://mailman12.u.washington.edu/mailman/listinfo/alpine-info__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWQAvCSiA$ 
> > 
> > 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://urldefense.com/v3/__https://marc.info/?l=alpine-info&r=1&w=2__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWLZeUaRE$ 
> > 
> > And then from January 2016:
> > 
> > https://urldefense.com/v3/__https://marc.info/?l=alpine-info&r=1&b=201601&w=2__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWfLSzz-w$ 
> > 
> > And then the thread in question ([Alpine-info] Best timeout settings
> > for connecting to Exchange server?):
> > 
> > https://urldefense.com/v3/__https://marc.info/?t=145399947700006&r=1&w=2__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjW6gYrRDQ$ 
> > 
> > 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@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@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@u.washington.edu
> > https://urldefense.com/v3/__http://mailman12.u.washington.edu/mailman/listinfo/alpine-info__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWQAvCSiA$ 
> > 
> 
From alpine-info at u.washington.edu  Wed Feb  5 14:09:35 2025
From: alpine-info at u.washington.edu (Barry Landy via Alpine-info)
Date: Wed Feb  5 14:09:41 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
Message-ID: <cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>

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@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@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@u.washington.edu
:>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>:>> 
:>:>_______________________________________________
:>:>Alpine-info mailing list
:>:>Alpine-info@u.washington.edu
:>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>:>
:>
:>

-- 
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-362062
				   Mobile	+44-7771-933945
Cambridge CB4 3PB
England				   Email	BarryLandy@cantab.net
From alpine-info at u.washington.edu  Wed Feb  5 23:10:04 2025
From: alpine-info at u.washington.edu (Barry Landy via Alpine-info)
Date: Wed Feb  5 23:10:11 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <1a3f4306-69a9-fe8f-13a8-b996ff91a382@illinois.edu>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1a3f4306-69a9-fe8f-13a8-b996ff91a382@illinois.edu>
Message-ID: <bd29acfc-f115-8ea9-36a6-011ea90ec03d@cantab.net>

Just BTW when I get the dread message I type "L" "enter" to reopen 
whatever folder I was reading. That's just TWO key strokes and not FOUR.

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

:>For more information on these timeouts (like what exactly they affect
:>and what it means if there're no values set), you'll have to hear from
:>others, perhaps Eduardo.  I'll just add that my .pinerc has comments
:>before these settings that give some explanation of what they control
:>and what the default values are (which are sometimes 0, which may mean
:>the timeout is off).  Also, in the config, I think you can hit "?" for
:>help when looking at a setting to get more info about it.
:>
:>I thought it might be the check incoming mail timeout value, which was
:>somewhat highlighted in that previous thread -- but someone responded
:>in this thread that they were having the same problem as you and had
:>already tried changing that value.
:>
:>Some other suggestions:
:>
:>You can try changine one or two of these timeouts, to see whether that
:>makes a difference in the behavior.
:>
:>Maybe you can run alpine with a higher debug level, and then when it
:>disconnects, you may have more information there that can guide you to
:>a soluation.
:>
:>Milt Epstein
:>mepstein@illinois.edu
:>
:>
:>On Sun, 2 Feb 2025, Thomas Gramstad 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:
:>> > 
:>> > https://urldefense.com/v3/__http://mailman12.u.washington.edu/mailman/listinfo/alpine-info__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWQAvCSiA$ 
:>> > 
:>> > 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://urldefense.com/v3/__https://marc.info/?l=alpine-info&r=1&w=2__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWLZeUaRE$ 
:>> > 
:>> > And then from January 2016:
:>> > 
:>> > https://urldefense.com/v3/__https://marc.info/?l=alpine-info&r=1&b=201601&w=2__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWfLSzz-w$ 
:>> > 
:>> > And then the thread in question ([Alpine-info] Best timeout settings
:>> > for connecting to Exchange server?):
:>> > 
:>> > https://urldefense.com/v3/__https://marc.info/?t=145399947700006&r=1&w=2__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjW6gYrRDQ$ 
:>> > 
:>> > 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@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@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@u.washington.edu
:>> > https://urldefense.com/v3/__http://mailman12.u.washington.edu/mailman/listinfo/alpine-info__;!!DZ3fjg!5fUGYHXfaXJLpzIkhH62fsjzbXcAMwd4o4D6KyWsm0EE-ac6NuokM9kRsDz6MYylDPg1fnxhVyjWQAvCSiA$ 
:>> > 
:>> 
:>_______________________________________________
:>Alpine-info mailing list
:>Alpine-info@u.washington.edu
:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>

-- 
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-362062
				   Mobile	+44-7771-933945
Cambridge CB4 3PB
England				   Email	BarryLandy@cantab.net
From alpine-info at u.washington.edu  Thu Feb  6 04:03:46 2025
From: alpine-info at u.washington.edu (Thomas Gramstad via Alpine-info)
Date: Thu Feb  6 04:03:52 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
	<cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
Message-ID: <ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>


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@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@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@u.washington.edu
> :>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
> :>:>> 
> :>:>_______________________________________________
> :>:>Alpine-info mailing list
> :>:>Alpine-info@u.washington.edu
> :>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
> :>:>
> :>
> :>
> 
> 
From alpine-info at u.washington.edu  Thu Feb  6 04:14:44 2025
From: alpine-info at u.washington.edu (Barry Landy via Alpine-info)
Date: Thu Feb  6 04:14:52 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
	<cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
	<ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>
Message-ID: <324ecc8b-96d4-6d57-6ed7-ff122a1d01d1@cantab.net>

interesting that "incoming check" benefits from a **lower** timeout.

Will try that.

Most of the time I use "L" "enter" to reopen the relevant folder. If I 
am reading an email it needs "I" "L" "enter"

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@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@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@u.washington.edu
:>> :>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>> :>:>> 
:>> :>:>_______________________________________________
:>> :>:>Alpine-info mailing list
:>> :>:>Alpine-info@u.washington.edu
:>> :>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>> :>:>
:>> :>
:>> :>
:>> 
:>> 
:>

-- 
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-362062
				   Mobile	+44-7771-933945
Cambridge CB4 3PB
England				   Email	BarryLandy@cantab.net
From alpine-info at u.washington.edu  Thu Feb  6 04:23:55 2025
From: alpine-info at u.washington.edu (Barry Landy via Alpine-info)
Date: Thu Feb  6 04:24:02 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
	<cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
	<ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>
Message-ID: <bb35e3f5-1e7c-06e9-6b54-82aac89acfa3@cantab.net>

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@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@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@u.washington.edu
:>> :>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>> :>:>> 
:>> :>:>_______________________________________________
:>> :>:>Alpine-info mailing list
:>> :>:>Alpine-info@u.washington.edu
:>> :>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>> :>:>
:>> :>
:>> :>
:>> 
:>> 
:>

-- 
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-362062
				   Mobile	+44-7771-933945
Cambridge CB4 3PB
England				   Email	BarryLandy@cantab.net
From alpine-info at u.washington.edu  Thu Feb  6 04:38:55 2025
From: alpine-info at u.washington.edu (Thomas Gramstad via Alpine-info)
Date: Thu Feb  6 04:39:03 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <bb35e3f5-1e7c-06e9-6b54-82aac89acfa3@cantab.net>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
	<cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
	<ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>
	<bb35e3f5-1e7c-06e9-6b54-82aac89acfa3@cantab.net>
Message-ID: <10706b15-7d35-3f87-6c17-1d8378ef2b9a@ifi.uio.no>


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@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@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@u.washington.edu
> :>> :>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
> :>> :>:>> 
> :>> :>:>_______________________________________________
> :>> :>:>Alpine-info mailing list
> :>> :>:>Alpine-info@u.washington.edu
> :>> :>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
> :>> :>:>
> :>> :>
> :>> :>
> :>> 
> :>> 
> :>
> 
> 
From alpine-info at u.washington.edu  Thu Feb  6 12:22:00 2025
From: alpine-info at u.washington.edu (David Lang via Alpine-info)
Date: Thu Feb  6 12:22:06 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <324ecc8b-96d4-6d57-6ed7-ff122a1d01d1@cantab.net>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
	<cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
	<ba8d8f9-d852-8f9d-3291-7077bb842a51@ifi.uio.no>
	<324ecc8b-96d4-6d57-6ed7-ff122a1d01d1@cantab.net>
Message-ID: <2o29998p-5244-35n5-4092-o3n27o8700qp@ynat.uz>

Barry Landy wrote:

> interesting that "incoming check" benefits from a **lower** timeout.

that means that there is a firewall, nat device, or load balancer between you 
and the server that is timing out your connection so when you send more packets 
it no longer knows what to do with them so it drops them

a shorter timeout means that the connection is excercised more frequently, so 
you are less likely to time out.

If a longer timeout helped, that would mean you have something in your network 
path disconnecting you frequently but then reconnecting. This is a very rare 
situation.

David Lang
From alpine-info at u.washington.edu  Tue Feb 11 13:14:16 2025
From: alpine-info at u.washington.edu (Barry Landy via Alpine-info)
Date: Tue Feb 11 13:14:23 2025
Subject: [Alpine-info] "[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]"
In-Reply-To: <cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
References: <ecead180-72aa-cd57-4db-2696686dcb2c@ifi.uio.no>
	<0d5b1a97-cc61-896e-9eb5-fbc0399aefe9@illinois.edu>
	<a4fb3911-9f27-b6d4-7565-fc3618397fb1@ifi.uio.no>
	<1ee25c0f-42b1-8226-a5d2-7d54f982a95b@cantab.net>
	<cf103400-258d-7d28-e3ec-d30bd0a75b87@cantab.net>
Message-ID: <4f6330da-1c48-da13-10d0-5d7a424037ad@cantab.net>

meanwhile with exactly those settings (I havent changed anything) the 
interruptions have got bad again.

On Wed, 5 Feb 2025, Barry Landy 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@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@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@u.washington.edu
:>:>:>> http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>:>:>> 
:>:>:>_______________________________________________
:>:>:>Alpine-info mailing list
:>:>:>Alpine-info@u.washington.edu
:>:>:>http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
:>:>:>
:>:>
:>:>
:>
:>

-- 
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-362062
				   Mobile	+44-7771-933945
Cambridge CB4 3PB
England				   Email	BarryLandy@cantab.net