Hello Januk,
Monday, June 18, 2001, 6:42:21 AM, you wrote:
PP>> *hmmm* tried the %ATTACHEFILE macro and the file becomes an ATTACHMENT.
PP>> If this get's BASE64 encoded, this is more than usual, an attachment HAS to
PP>> have some encoding, unless it PURE PLAIN 7-BIT text.
JA> That's the thing, the files are just text files (RFC-822 message files
JA> to be precise). If you enable mime-forwarding in TB and forward a
JA> couple of messages, you'll see what I want. But the trick is, I'm
JA> trying to automate the procedure.
Wouldn't it be better then to use the "%INCLUDE=" macro instead? That
way it would not be considered an attachment. As Peter stated, if you
use the "%ATTACHMENT" macro then it will always be an attachment, I
believe.
--
Using The Bat! v1.53bis on Windows NT 5.0 Build 2195
Service Pack 2
Best regards,
Gerry Doyon mailto:[EMAIL PROTECTED]
You are subscribed as : [email protected]
[ attachment or non text part has been remove by MDaemon ]
