From: john <jpff@codemist.co.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34252@debbugs.gnu.org
Subject: bug#34252: 27.0.50; rmail-get-new-mail fails
Date: Wed, 30 Jan 2019 20:29:29 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.20.1901302025490.12775@snout.codemist.co.uk> (raw)
In-Reply-To: <83a7ji0y9h.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
Just changing lin 2075 it does not crash but after quite a time it says
Getting mail from /mnt/snout/home/jpff/mbox...
movemail: No locks available for /mnt/snout/home/jpff/mbox
(No new mail has arrived)
0 new messages read
You can run the command ‘rmail-get-new-mail’ with g
0 new messages read
and no mail is read
If I understand the message the problem relates to fie locking somewhee.
I tried earlier o explain this used to work but after a hardware/software
uorade on the server it failed.
==John ff
On Wed, 30 Jan 2019, Eli Zaretskii wrote:
>> Date: Wed, 30 Jan 2019 18:10:29 +0000 (GMT)
>> From: john <jpff@codemist.co.uk>
>> Cc: 34252@debbugs.gnu.org
>>
>> This could be due to a kernel/NFS problem but te effect on using rmail for
>> my user-base is a real problem. The problems with proto being nil in
>> rmail-remote-proto-p is clearly wrong and despite your statement it does
>> happen to me on two diffrent computers/users attempting to read mail in
>> emacs via rmail.
>
> If you leave only the one change in the place where Glenn said proto
> could be nil, and revert the changes in the other two places, does the
> problem still happen to you?
>
> Thanks.
>
next prev parent reply other threads:[~2019-01-30 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 20:57 bug#34252: 27.0.50; rmail-get-new-mail fails John
2019-01-30 0:34 ` Glenn Morris
2019-01-30 18:10 ` john
2019-01-30 18:57 ` Eli Zaretskii
2019-01-30 19:34 ` John ff
2019-01-30 20:29 ` john [this message]
2019-01-31 3:32 ` Eli Zaretskii
2019-02-01 9:18 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1901302025490.12775@snout.codemist.co.uk \
--to=jpff@codemist.co.uk \
--cc=34252@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).