On Mon, 2004-08-02 at 00:13 -0400, Jeffrey Stedfast wrote: > it doesn't rely on the name, read up on how the X drag & drop protocol > works.
How does the X protocol matter, when the email may be sent to another machine, possibly not running Evo or maybe not even "Unix"? > On Sun, 2004-08-01 at 23:45, Ron Johnson wrote: > > On Mon, 2004-08-02 at 11:12 +0800, Not Zed wrote: > > > > > > > The problem is "how does Evolution know to scan thru all the emails > > > > on your system, and know exactly which attachments to convert from > > > > application/octet-stream to message/rfc822?" > > > > > > > > I don't think they can. > > > But that isn't how drag and dropped messages work when dragged > > > internally. It sends them as uids+folders in 1.5.something+, so they > > > can't be anything but the right type. > > > > > > They have to be encoded right at the sending end to start with if > > > they're ever to be recognised later. > > > > I thought that was what the bug was. > > > > When I ran 1.5.9.1, a drag-n-dropped email was attached as > > application/octet-stream. > > > > When I upgraded to 1.5.91 and tried again, a drag-n-dropped email > > was attached as message/rfc822. > > > > Do you rely on the pattern of the name of the attachment to notice > > that it is a uids+folder, instead of the mimetype? If so, there > > is still a bug, because Evo 1.5.91 looks at that application/octet- > > stream attachment, and will only let me Save As. -- ----------------------------------------------------------------- Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B "Fair is where you take your cows to be judged." Unknown
signature.asc
Description: This is a digitally signed message part
