On Sunday, March 21, 2004 7:13 PM
Roland
I have switched to "ArticleStorageFS" as is recommednded for large Attachements. Now I have discovered, that the plain.txt file is nothing more than the complete MIME message. This would not be bad, but this means it already contains all of the attachements. So every article directory will need to hold roughly twice as much space as one would guess.
That's true, sad enough.
I am now wondering which rationale is behind this storage layout.
That way we don't have to parse an email's contents each time the article is requested. Maybe historical reasons, too.
Please don't get me wrong, as I am (almost) perfectly happy with this, since I am still trying to render these RFC 2557 multipart/related beasts.
If you find a convenient and safe way to show them, go ahead. It's long and it's winding, though.
Now that I have found, that plain.txt still contains everything I need, I again have hope to be able to render it, since other perl based programs like OpenWebMail can do it too.
For sure plain.txt is for you, as it's an untouched original, one could say.
Might it be, that I am not aware of other methods of sending attachements, that are not contained within plain.txt?
plain.txt is the whole thing. Nothing more. hth, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388