D
Danny Dorsey
This one is odd and I was wondering if anyone else has seen it.
I've got a user who is sending attachments and the whole thing is
coming through on the other end as ATT#####.dat (the # being some
alpha-num). This is where you say, "Have him send as plain text!" but
it goes through with the .DAT even when sending in plain text. Splain
that one to me.
I downloaded a utility to check the DAT the other end is receiving and
it does appear to be valid TNEF with the attachment still in there. Has
anyone else seen this? Outlook isn't supposed to send TNEF from plain
text messages, but Outlook has a mind of its own quite often.
Please help! If you don't and I'm forced to solve this one on my own,
I'll post the answer, or at least a list of the random munging I did to
fix it.
- Danny
I've got a user who is sending attachments and the whole thing is
coming through on the other end as ATT#####.dat (the # being some
alpha-num). This is where you say, "Have him send as plain text!" but
it goes through with the .DAT even when sending in plain text. Splain
that one to me.
I downloaded a utility to check the DAT the other end is receiving and
it does appear to be valid TNEF with the attachment still in there. Has
anyone else seen this? Outlook isn't supposed to send TNEF from plain
text messages, but Outlook has a mind of its own quite often.
Please help! If you don't and I'm forced to solve this one on my own,
I'll post the answer, or at least a list of the random munging I did to
fix it.
- Danny