nmh-workers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Nmh-workers] Bug? mhstore Will Use Same File.


From: Ralph Corderoy
Subject: [Nmh-workers] Bug? mhstore Will Use Same File.
Date: Tue, 23 Nov 2004 22:49:37 +0000

Hi,

Should mhstore protect itself from

    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="part1_0.dc503142.259d2bb2_boundary"
    X-Mailer: AOL 3.0.1 for Mac sub 84

    --part1_0.dc503142.259d2bb2_boundary
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: quoted-printable

    ...

    --part1_0.dc503142.259d2bb2_boundary
    Content-Type: multipart/appledouble; name="foo"; X-Mac-Creator="3842494d";
            X-Mac-Type="4a504547"; boundary="ad_45416526_boundary"

    --ad_45416526_boundary
    Content-Type: application/applefile; name="foo"; X-Mac-Creator="3842494d";
            X-Mac-Type="4a504547"
    Content-Transfer-Encoding: base64

    ...

    --ad_45416526_boundary
    Content-Type: image/jpeg; name="foo"
    Content-Transfer-Encoding: base64
    Content-Disposition: inline; filename="foo"

    ...

    --ad_45416526_boundary--

    --part1_0.dc503142.259d2bb2_boundary--

Plain mhstore creates

    1.1.txt
    1.2.1.applefile
    1.2.2.jpeg

but add -auto and it uses the filename `foo' above quite a bit resulting
in the applefile being overwritten by the jpeg.

Commands like wget(1) will add suffixes, I wonder if mhstore should also
do something, assuming the above MIME is legal.

Cheers,


Ralph.

PS.  Anyone maintaining a bug/todo/wish list?





reply via email to

[Prev in Thread] Current Thread [Next in Thread]