Hello Nick,
Sunday, December 31, 2000, 8:53:08 PM, you wrote:
NA> On December 31, 2000, at 6:41:44 AM, Marck D. Pearlstone Wrote:
MDP>> TB employs the other method by default for good reason - it serves as
MDP>> a record of what was sent because original files can be changed after
MDP>> they have gone. What would be the point of keeping a copy of the sent
MDP>> mail anyway if you are going to leave it attached to a non-static copy
MDP>> of an attachment?
NA> I am not sure I follow your logic here Marck. In what manner can original
NA> files be changed after they have gone? Are you referring to a change in the
NA> original file that was attached to an outgoing message?
NA> If I send myself a test message to include a small *.PNG file, TB! will pull
NA> the file out of it's original Folder and put a copy of it in my specified
NA> attachment Folder (C:\Temp) during Send, and then deposit the same file
NA> again during Receive. I now have 3 copies of the original file I sent out as
NA> an attachment.
NA> As a default behaviour, I don't understand the logic behind it. :o(
If a team is working on a file through e-mail is can be less
dangerous though. I switched to storing the attachments in message
bodies for this reason. But I haven't lost any "version" of a file...
I guess this is the only way the program's behavior does not differ
whether or not you store the attachments in message bodies i.e. each
message contains the version of a file it was sent with...
--
Best regards,
Serge Skorokhodov mailto:[EMAIL PROTECTED]
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : archive@jab.org
