[27409] in Athena Bugs
Re: Debathena: mh-rmail
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Sat Jan 16 06:47:17 2010
Date: Sat, 16 Jan 2010 06:47:13 -0500 (EST)
From: Geoffrey Thomas <geofft@mit.edu>
To: John Carr <jfc@mit.edu>
In-Reply-To: <201001140117.o0E1HtDu002966@outgoing.mit.edu>
Message-ID: <alpine.DEB.1.10.1001160644390.14067@dr-wily.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: bug-dialup@mit.edu, bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
Thanks! As I alluded to in my previous e-mail, I added this setting to our
Emacs configuration package (which includes a bunch of other settings
needed to make MH-E work) and have uploaded that package to the -proposed
apt repositories. It should move to the production repositories on the
public cluster machines in two business days.
Ops: can you take this package on the dialups when it gets to production,
since this bug was reported thrice on linux.dialup?
--
Geoffrey Thomas
geofft@mit.edu
On Wed, 13 Jan 2010, John Carr wrote:
> Adding this to my .emacs seems to have worked around the problem:
>
> (setq mh-send-uses-spost-flag 't)
>
> Searching for spost in the emacs lisp source found this definition
> in mh-e/mh-comp.el:
>
> (defvar mh-send-uses-spost-flag nil
> "Non-nil means \"send\" uses \"spost\" to submit messages.
>
> If the value of \"postproc:\" is \"spost\", you may need to set
> this variable to t to tell MH-E to avoid using features of
> \"post\" that are not supported by \"spost\". You'll know that
> you'll need to do this if sending mail fails with an error of
> \"spost: -msgid unknown\".")
>
>
>> Hi,
>>
>> Thanks for reporting this. We've already had one or two reports of
>> this via OLC, so it's in our bug tracker:
>>
>> http://debathena.mit.edu/trac/ticket/478
>>
>> Unfortunately the most straightforward solution involves figuring out
>> a merge of the Athena-patched nmh, which we haven't updated in a
>> while, and a newer nmh from Debian, and for some reason this is an
>> involved process, so I'm not sure how quickly it will get fixed.
>>
>> I don't know a lot about mh-rmail or even emacs, so I can't figure out
>> if there's a way to do this, but if you can figure out configure
>> mh-smail not to use the "-msgid" flag (which apparently requires a
>> newer version of nmh), there's a decent chance this will then start to
>> work.
>
