From: Jeremy Hankins <nowan@nowan.org>
To: info-gnus-english@gnu.org
Subject: Re: Mail source problem (?)
Date: Sat, 26 Jan 2019 19:08:37 -0500 [thread overview]
Message-ID: <875zubrmgq.fsf@opal.nowan.org> (raw)
In-Reply-To: <87fttf3s17.fsf@opal.nowan.org>
Just did a bit more looking around and happened to check the messages
buffer, and it turns out there was a more complete error message there.
The problem was movemail. mail-source-movemail-program wasn't set, and
the default value mail-source.el was looking in exec-directory, which
didn't have it. Setting the variable manually to "/usr/bin/movemail"
solved the problem loading mail from my mail spool. Doesn't explain why
toggling debug-on-quit made the message go away, of course.
Is this a packaging problem? Should I file a bug with debian? Or
should mail-source.el check the path for movemail?
--
Jeremy Hankins <nowan@nowan.org>
next prev parent reply other threads:[~2019-01-27 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 17:44 Jeremy Hankins
2019-01-26 20:05 ` Eric Abrahamsen
2019-01-26 23:42 ` Jeremy Hankins
2019-01-27 0:08 ` Jeremy Hankins [this message]
2019-01-29 20:24 ` Eric Abrahamsen
2019-01-30 13:28 ` Jeremy Hankins
2019-02-02 16:29 ` Eric Abrahamsen
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=875zubrmgq.fsf@opal.nowan.org \
--to=nowan@nowan.org \
--cc=info-gnus-english@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.
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).