From: Bud Rogers <budr@tanet.net>
Subject: Re: help, I've crippled my gnus (resend...)
Date: Wed, 8 Jul 1998 18:47:29 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.3.96.980708183648.709A-100000@twocups.tanet.net> (raw)
I tried to send this earlier, but I'm not sure it actually went out. At
any rate, I didn't see it come back from the list. My apologies if this
is redundant. Good old pine...
gnus 5.6.10, xemacs 20.3
I inadvertently started gnus while fetchmail was retrieving new mail and
hit the movemail file lock problem. Thought I got that straightened out
last night. Thought everything was fine until I tried to send a reply
this morning. When I try to send any mail I get this error.
Signaling: (file-error "Cannot open" "Bad file number" t)
call-process-internal("/usr/lib/sendmail" "/tmp/emacsa10377" 0 nil "-oi" "-f" "budr" "-oem" "-odb" "-t")
apply(call-process-internal "/usr/lib/sendmail" "/tmp/emacsa10377" 0 nil ("-oi" "-f" "budr" "-oem" "-odb" "-t"))
call-process("/usr/lib/sendmail" "/tmp/emacsa10377" 0 nil "-oi" "-f" "budr" "-oem" "-odb" "-t")
apply(call-process "/usr/lib/sendmail" "/tmp/emacsa10377" 0 nil ("-oi" "-f" "budr" "-oem" "-odb" "-t"))
call-process-region(1 310 "/usr/lib/sendmail" nil 0 nil "-oi" "-f" "budr" "-oem" "-odb" "-t")
apply(call-process-region (1 310 "/usr/lib/sendmail" nil 0 nil "-oi" "-f" "budr" "-oem" "-odb" "-t"))
message-send-mail-with-sendmail()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit)
I did this to myself, but I'm not sure what I did. I would appreciate
any suggestions. This is like having a stroke and being suddenly struck
dumb.
Bud Rogers <budr@tanet.net>
I wore khaki when khaki wasn't cool.
reply other threads:[~1998-07-08 23:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.3.96.980708183648.709A-100000@twocups.tanet.net \
--to=budr@tanet.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).