Vladimir G. Ivanovic | 14 Aug 20:56 2002
Picon

Encoding/decoding MIME messages with mh-e 6.1 and XEmacs 21.5.8

When I send a MIME message using mh-e 6.1 and XEmacs 21.5.8, I get this

   --[[application/octet-stream
   Content-Disposition: attachment; filename="auto.master"][base64]]
   IyAkSWQ6IGF1dG8ubWFzdGVyLHYgMS4yIDE5OTcvMTAvMDYgMjE6NTI6MDMgaHBhIEV4cCAk
   CiMgU2FtcGxlIGF1dG8ubWFzdGVyIGZpbGUKIyBGb3JtYXQgb2YgdGhpcyBmaWxlOgojIG1v
   dW50cG9pbnQgbWFwIG9wdGlvbnMKIyBGb3IgZGV0YWlscyBvZiB0aGUgZm9ybWF0IGxvb2sg
   YXQgYXV0b2ZzKDgpLgovbWlzYwkvZXRjL2F1dG8ubWlzYwktLXRpbWVvdXQ9NjAK

instead of

   --Multipart_Thu_Aug__1_00:08:09_2002-1
   Content-Type: application/octet-stream
   Content-Disposition: attachment; filename="auto.master"
   Content-Transfer-Encoding: base64

   IyAkSWQ6IGF1dG8ubWFzdGVyLHYgMS4yIDE5OTcvMTAvMDYgMjE6NTI6MDMgaHBhIEV4cCAk
   CiMgU2FtcGxlIGF1dG8ubWFzdGVyIGZpbGUKIyBGb3JtYXQgb2YgdGhpcyBmaWxlOgojIG1v
   dW50cG9pbnQgbWFwIG9wdGlvbnMKIyBGb3IgZGV0YWlscyBvZiB0aGUgZm9ybWF0IGxvb2sg
   YXQgYXV0b2ZzKDgpLgovbWlzYwkvZXRjL2F1dG8ubWlzYwktLXRpbWVvdXQ9NjAK

   --Multipart_Thu_Aug__1_00:08:09_2002-1
   Content-Type: text/plain; charset=US-ASCII

I built XEmacs 21.5.8 from sources with no errors, and I byte-recompiled
all the packages in xemacs-sumo-2002-07-20.tar.bz2. There were errors,
but I don't think any of them affect this problem.

Any ideas on how I can diagnose my MIME encoding problem and fix it?

(Continue reading)

Peter S Galbraith | 15 Aug 18:53 2002
X-Face
Picon

Re: Encoding/decoding MIME messages with mh-e 6.1 and XEmacs 21.5.8

"Vladimir G. Ivanovic" <vladimir <at> acm.org> wrote:

> When I send a MIME message using mh-e 6.1 and XEmacs 21.5.8, I get this
> 
>    --[[application/octet-stream
>    Content-Disposition: attachment; filename="auto.master"][base64]]
>    IyAkSWQ6IGF1dG8ubWFzdGVyLHYgMS4yIDE5OTcvMTAvMDYgMjE6NTI6MDMgaHBhIEV4cCAk
>    CiMgU2FtcGxlIGF1dG8ubWFzdGVyIGZpbGUKIyBGb3JtYXQgb2YgdGhpcyBmaWxlOgojIG1v
>    dW50cG9pbnQgbWFwIG9wdGlvbnMKIyBGb3IgZGV0YWlscyBvZiB0aGUgZm9ybWF0IGxvb2sg
>    YXQgYXV0b2ZzKDgpLgovbWlzYwkvZXRjL2F1dG8ubWlzYwktLXRpbWVvdXQ9NjAK

I can't reproduce this using the released 6.1 with 21.4 (patch 6).
That's the version of mh-e what you're using and not CVS (which also
advertises itself as 6.1, which we should tweak), right?

I get something like:

MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
Content-ID: <10416.1029429896.0 <at> mixing.qc.dfo.ca>

------- =_aaaaaaaaaa0
Content-Type: application/x-gzip; name="xemacs.tar.gz"
Content-ID: <10416.1029429896.2 <at> mixing.qc.dfo.ca>
Content-Description: test
Content-Transfer-Encoding: base64

H4sIAOtQ9jgAA+xc6ZMb13HfiisMuSzTqcpHleneIeXFLDmzABYL7MFIpJYrWZZ4hEvZTgmUNQAe
gPECM+DMgLtwWPoQ28nSn5wviv+M+D+QqIM6qNvOVflj0t3vzQXMYA+RjFzRqLiamXf169fdr/v3
[cut]
(Continue reading)

Peter S Galbraith | 16 Aug 18:57 2002
X-Face
Picon

Re: Encoding/decoding MIME messages with mh-e 6.1 and XEmacs 21.5.8

[Redirecting later discussion to -devel instead of -users]

I installed xemacs-21.5.8 and xemacs-sumo-2002-07-20 and can't reproduce
your problem with either mh-e version 6.1 or CVS.

Note that in 6.1, it's nmh's mhbuild that is building the message for
mh-e, so maybe that's where you should look?

You have nmh 1.0.4 and I have some patched -dev version (from Debian).

I may soon make a Debian package of the CVS version of mh-e, and that
will make a nice tar ball for you to download if you're not a fan of
CVS access.  You can then use that instead of 6.1.

Peter


Gmane