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://mailman
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 nothin
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
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, tho
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
__
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, bu
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
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
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 defaul
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".
10 matches
Mail list logo
