From: Gaute B Strokkenes <biggaute@uwc.net>
Subject: movemail dies on me.
Date: Wed, 27 Aug 2003 09:00:02 +0100 [thread overview]
Message-ID: <87r837fs3h.fsf@srcf.ucam.org> (raw)
For some time now, I have occasionally had to deal with queries like
this:
movemail: (Drept return). Continue? (yes or no)
popping up in my minibuffer when I hit `g' in the group buffer.
("Drept" is Norwegian for "killed".) It doesn't happen every time,
just often enough to be severly annoying. It seems that movemail
always dies _after_ it has done its job (moving everything from
/var/mail/gs234 to ~/.emacs-mail-crash-box,) so this is no more than
an annoyance.
Unfortunately I'm finding this rather hard to debug. movemail is
suid so that it can manipulate my mail spool, and the intermittent
nature doesn't help either. Is anyone else seeing this?
--
Gaute Strokkenes http://www.srcf.ucam.org/~gs234/
I just bought FLATBUSH from MICKEY MANTLE!
next reply other threads:[~2003-08-27 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 8:00 Gaute B Strokkenes [this message]
2003-10-17 19:14 ` Lars Magne Ingebrigtsen
2003-10-17 20:13 ` Gaute B Strokkenes
2003-10-17 20:22 ` Ted Stern
2003-10-17 21:11 ` Lars Magne Ingebrigtsen
2003-10-17 22:58 ` Ted Stern
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r837fs3h.fsf@srcf.ucam.org \
--to=biggaute@uwc.net \
/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.
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 NNTP newsgroup(s).