Answering my own question:
After the pop saga in the previous post, I downloaded a pop message to
mail.app, and it failed to show the body as well.
I suspect that this is a dbmail bug. Not sure how it got in this far, since I
don't actually expect that any pop/imap client should have been able to deal
with this.
The following is a transcript from a telnet session, with unimportant data
elided. Note that there is no blank line between the header and the body of the
mail message, as is required by mime standards.
..
+OK [EMAIL PROTECTED] has 1 messages (153 octets)
retr 1
+OK 153 octets
Received: from l2.socialecology.com (l2.socialecology.com [4.42.179.131])
by serrano.pepper.socialecology.com (Postfix) with ESMTP id
..
Subject: hello!
Content-Type: text/plain; charset=us-ascii
this is ta test
--
Hope is a choice, not a sum
You can have as much of it as you damn well feel like having,
Regardless of the actual circumstances.
.
What I was seeing in mail.app was the one blank line at the end of my .sig.
Going back (and finding the view source command in mail.app) confirms that this
is the same issue that underlies the imap problem.
eric
