On 2000-12-05 15:49:53 +0100, Anand Buddhdev wrote:
So the problem boils down to the MUA not generating full and
correct MIME headers. In this case, mutt isn't inserting all the
headers that courier expects (it assumes that the relevant
information will be infered according to RFC 1847).
On 2000-12-05 17:23:30 -0500, Sam Varshavchik wrote:
Well, I really think it's not really the MUA, but it's PGP/MIME
that's broken.
As would be S/MIME (that stuff used by Outlook and Netscape). Sam,
I'd seriously suggest that, for the time being, you just implement
the standards which are
On Tue, Dec 05, 2000 at 08:31:43AM -0500, Sam Varshavchik wrote:
Hi Sam,
Thank you very much for this detailed answer. I now understand what the
problem is. I just concluded a test, where I manually inserted a
Content-Transfer-Encoding: header into the main headers of the mail, and
used only
At 15:49 +0100 05 Dec 2000, Anand Buddhdev [EMAIL PROTECTED] wrote:
On Tue, Dec 05, 2000 at 08:31:43AM -0500, Sam Varshavchik wrote:
Note that the second MIME section does not specify its content transfer
encoding. Neither is the default transfer encoding specified in the top
level MIME
