I've experimented with direct-out-the-pipe delivery systems. Trust me, you don't want to go there. It's not trivial. Well, it's trivial for 90% of the world that follows the RFCs and behaves as expected and has the right DNS setups and isn't trying to outsmart spammers by being stupid. and you'll spend the other 90% of your time trying to build compatibility in with the other 10%.
You'd have the same sorts of problems if you added your own interpretation of the MIME bodyparts and stored the attachments separately, and then tried to re-integrate everything on transmission.
Indeed, you'd have a whole host of additional problems you'd add because not only would you be trying to format everything on output so that everyone would like what you send, you'd be assuming that you can always correctly parse your inputs and correctly handle the results.
IMO, you're much better just storing exactly what you got, and then sending exactly what you stored when the time comes. Any misunderstandings are therefore the fault of the sender or recipient, and not the result of anything you added to the complexity mix.
Or have I missed something here?
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
