> Q> [NON-Text Body part not included]
>
> Not sure what happenned, but your message was listed as an attachment
> to a binary message, hence the above.
It is just a multipart/signed message conforming to RFC 2015 and
Pine doesn't seem to be able to understand a message/rfc822
Content-type. True, this is "NON-Text", but I'd expect a MIME
complient mail client to know about a "message/rfc822" MIME
type. It certainly is not "binary", though.
BTW, mutt does the right thing, elm basicly... It's just Pine that
cannot reply to such a message.
*SIGH*
> Many years back, I was involved in a project using a Z8530 essentially
> connected through a parallel port adapter, and I remember having some
> problems getting that to work. There was some problem concerned with
> having to acknowledge ALL interrupts, so if one was missed, the thing
> stopped working until it saw as many acknowledgements as it had issued
> interrupts.
I know, but how am I supposed to acknowledge an interrupt I've lost? I
need some kind of watchdog to find those occurences... Well, at least
it's rather simple to implement...
73,
Joerg Reuter http://poboxes.com/jreuter/
And I make my way to where the warm scent of soil fills the evening air.
Everything is waiting quietly out there.... (Anne Clark)
PGP signature
