> How about replacing the attachment with an attachment of type 
> message/external-body with an access-type of "LOCAL-FILE", as defined in 
> RFC 2046 
> <http://www.nacs.uci.edu/indiv/ehood/MIME/2046/rfc2046.html#5.2.3>? That 
> could contain all of the necessary information (a short disclaimer could 
> go in the attachment's "phantom body").

This looks promising, Timeless seems to favor using 
message/external-body as well; however, the first stage of work, the 
work specifically covered by bug 2920, doesn't cover saving and linking 
to attachments (detaching files from a message), it only covers deleting 
attachments.


But for future reference, to help coordinate some of the discussions 
here with later work done on saving and linking to attachments, and for 
clarification...

Are attachments part of the body of a message, or are they separate from 
the body?  Can message/external-body be applied to an attachment?  Would 
message/external-body only be useful for saving and linking to 
attachments (detaching files), or would it also be useful for deleting 
attachments?


Thanks for the input

-- 
Matt Coughlin

[EMAIL PROTECTED]
<remove "sp4mless_" from the e-mail address to reply>


Reply via email to