I'm talking to Alexander off-list about this; suspect that the file-not-
found stuff is browser opening pages in background, but doing so too
slowly and so missing Nmh's tempfiles.
I am 100% sure that is the problem ... but it just illustrates my point.
What is appropriate for a mailcap entry
I can understand that, but from what we've seen it looks like
run-mailcap simply is non-functional with base nmh (Conrad said it
didn't work; a lot of cases of file not found).
hmm, as far as i'm aware debian's mime-support (and its
run-mailcap component) is very well primed from the get-go, but
I'm talking to Alexander off-list about this; suspect that the file-not-
found stuff is browser opening pages in background, but doing so too
slowly and so missing Nmh's tempfiles.
Conrad
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
Paul F. wrote:
i've recently started getting messages with multiple MIME-Version
headers. they all say 1.0, of course.
i see nothing (just a quick read) in RFC 2045 regarding multiple
MIME-Version headers.
The BNF shows exactly one, so I'd say the messages don't conform.
Are they from more
david wrote:
Paul F. wrote:
i've recently started getting messages with multiple MIME-Version
headers. they all say 1.0, of course.
i see nothing (just a quick read) in RFC 2045 regarding multiple
MIME-Version headers.
The BNF shows exactly one, so I'd say the messages
On Wed, 04 Mar 2015 00:42:44 -0500, Ken Hornstein writes:
I can understand that, but from what we've seen it looks like
run-mailcap simply is non-functional with base nmh (Conrad said it
didn't work; a lot of cases of file not found).
hmm, as far as i'm aware debian's mime-support (and its
