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 mepst...@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 > > mepst...@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
