On May 18, 7:21 pm, "Michael Santovec" <michael_santo...@prodigy.net> wrote: Based on messages that I've received from other Outlook users, the attachment shows up in the message body as encoded text. In that case, it is possible to use a 3rd party decoder to decode the attachment, but it is a bit involved. See the Decoding Mechanics section of Decoding Internet Attachments
Based on messages that I've received from other Outlook users, the attachment shows up in the message body as encoded text. In that case, it is possible to use a 3rd party decoder to decode the attachment, but it is a bit involved. See the Decoding Mechanics section of Decoding Internet Attachments - A Tutorial http://pages.prodigy.net/michael_santovec/decode.htm I don't know how much
I'm having a similar problem with Outlook 2003 (and Bell South). I can receive attachments in the BellSouth web mail, but not in Outlook. Any thoughts and help would be greatly appreciated. This was not a problem until about 1-2 weeks ago. "Michael Santovec" wrote: I've managed to get some samples of the problem messages. I had some issues with my ISP's anti-virus on the mail
I've since heard from some BellSouth customers that BellSouth has admitted to the problem and is working on it. We'll see how long it takes to fix it. Based on reports from some others, it seems that the colon in the Yahoo boundary string is what's tripping up the Spam filter. It thinks the boundary string is a header, even though it's in the body of the message. That would also explain
Nice catch. I have an account with them, but don't use their email much and never from the web. steve "Michael Santovec" <michael_santovec@prodigy.net> wrote in message news:uXDJEf3kHHA.3928@TK2MSFTNGP02.phx.gbl... I've managed to get some samples of the problem messages. I had some issues with my ISP's anti-virus on the mail server deleting the attachments because it detected
