![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
![]() We have been running into an issue with several of our end user Outlook attachment decoding. We have an AIX (IBM unix) server that sends out reports automatically via email. These reports can be either a .pdf, .rtf, or plain text file. The problem is when some users (ones who have outlook 2000) receive these emails, they get the full ASCII uuencode file in the body of the email message (no matter what file type pdf, rtf or txt) and not as an attachment. I have tried multiple updates, and nothing seems to work out. My research on the net just tells me to use mime encoding. That’s not possible with our AIX server, which only uses uuencode for attachments. The weird thing is, when said users forward me the email, it shows up with the correct attachment on my end (I’m using Outlook 2003), and then when I forward it back to them, they can then see the attachment correctly. So this leads me to believe that their outlook client is having issues decoding uuencode attachments. I know I can have the user’s manually decode the attachment, but that really isn’t an efficient solution. Things that I know are true: It’s a Client side issue. Nothing with accounts, because we used same accounts on different systems and the attachment shows up fine. Installing a newer version of outlook for the user does not work either. I have installed Outlook 2003 on several of the effected users and the same issue occurs. Registry problem? Full format of the system works! Is a solution, but not a very efficient one either. Thanks for any help you can offer.... -Jim |
Ads |
#2
|
|||
|
|||
![]() BUMP !! Am I invisible here? No MVPs have any suggestions? On Wed, 01 Feb 2006 16:52:58 -0500, Jim Smith wrote: We have been running into an issue with several of our end user Outlook attachment decoding. We have an AIX (IBM unix) server that sends out reports automatically via email. These reports can be either a .pdf, .rtf, or plain text file. The problem is when some users (ones who have outlook 2000) receive these emails, they get the full ASCII uuencode file in the body of the email message (no matter what file type pdf, rtf or txt) and not as an attachment. I have tried multiple updates, and nothing seems to work out. My research on the net just tells me to use mime encoding. That’s not possible with our AIX server, which only uses uuencode for attachments. The weird thing is, when said users forward me the email, it shows up with the correct attachment on my end (I’m using Outlook 2003), and then when I forward it back to them, they can then see the attachment correctly. So this leads me to believe that their outlook client is having issues decoding uuencode attachments. I know I can have the user’s manually decode the attachment, but that really isn’t an efficient solution. Things that I know are true: It’s a Client side issue. Nothing with accounts, because we used same accounts on different systems and the attachment shows up fine. Installing a newer version of outlook for the user does not work either. I have installed Outlook 2003 on several of the effected users and the same issue occurs. Registry problem? Full format of the system works! Is a solution, but not a very efficient one either. Thanks for any help you can offer.... -Jim |
#3
|
|||
|
|||
![]()
No, not invisible, but others who regularly answer questions here may not
have experience with AIX systems, sending automated reports, etc. so you should not expect an answer for such a specific situation that is not the norm. I would suggest that you consult with your AIX supplier as well as Microsoft Product Support Services for an answer to your situation. -- Milly Staples [MVP - Outlook] Post all replies to the group to keep the discussion intact. All unsolicited mail sent to my personal account will be deleted without reading. After furious head scratching, Dr. VanNostrin asked: | BUMP !! | | Am I invisible here? No MVPs have any suggestions? | | On Wed, 01 Feb 2006 16:52:58 -0500, Jim Smith | wrote: | || || We have been running into an issue with several of our end user || Outlook attachment decoding. We have an AIX (IBM unix) server that || sends out reports automatically via email. These reports can be || either a .pdf, .rtf, or plain text file. The problem is when some || users (ones who have outlook 2000) receive these emails, they get the || full ASCII uuencode file in the body of the email message (no matter || what file type pdf, rtf or txt) and not as an attachment. I have || tried multiple updates, and nothing seems to work out. || || My research on the net just tells me to use mime encoding. That’s || not possible with our AIX server, which only uses uuencode for || attachments. The weird thing is, when said users forward me the || email, it shows up with the correct attachment on my end (I’m using || Outlook 2003), and then when I forward it back to them, they can then || see the attachment correctly. So this leads me to believe that their || outlook client is having issues decoding uuencode attachments. I || know I can have the user’s manually decode the attachment, but that || really isn’t an efficient solution. || || || Things that I know are true: || || It’s a Client side issue. Nothing with accounts, because we used || same accounts on different systems and the attachment shows up fine. || Installing a newer version of outlook for the user does not work || either. I have installed Outlook 2003 on several of the effected || users and the same issue occurs. Registry problem? || Full format of the system works! Is a solution, but not a very || efficient one either. || || Thanks for any help you can offer.... || -Jim |
#4
|
|||
|
|||
![]() Gee...thanks Milly. That was real helpful....... On Sat, 4 Feb 2006 12:43:23 -0800, "Milly Staples [MVP - Outlook]" wrote: No, not invisible, but others who regularly answer questions here may not have experience with AIX systems, sending automated reports, etc. so you should not expect an answer for such a specific situation that is not the norm. I would suggest that you consult with your AIX supplier as well as Microsoft Product Support Services for an answer to your situation. --? Milly Staples [MVP - Outlook] Post all replies to the group to keep the discussion intact. All unsolicited mail sent to my personal account will be deleted without reading. After furious head scratching, Dr. VanNostrin asked: | BUMP !! | | Am I invisible here? No MVPs have any suggestions? | | On Wed, 01 Feb 2006 16:52:58 -0500, Jim Smith | wrote: | || || We have been running into an issue with several of our end user || Outlook attachment decoding. We have an AIX (IBM unix) server that || sends out reports automatically via email. These reports can be || either a .pdf, .rtf, or plain text file. The problem is when some || users (ones who have outlook 2000) receive these emails, they get the || full ASCII uuencode file in the body of the email message (no matter || what file type pdf, rtf or txt) and not as an attachment. I have || tried multiple updates, and nothing seems to work out. || || My research on the net just tells me to use mime encoding. That’s || not possible with our AIX server, which only uses uuencode for || attachments. The weird thing is, when said users forward me the || email, it shows up with the correct attachment on my end (I’m using || Outlook 2003), and then when I forward it back to them, they can then || see the attachment correctly. So this leads me to believe that their || outlook client is having issues decoding uuencode attachments. I || know I can have the user’s manually decode the attachment, but that || really isn’t an efficient solution. || || || Things that I know are true: || || It’s a Client side issue. Nothing with accounts, because we used || same accounts on different systems and the attachment shows up fine. || Installing a newer version of outlook for the user does not work || either. I have installed Outlook 2003 on several of the effected || users and the same issue occurs. Registry problem? || Full format of the system works! Is a solution, but not a very || efficient one either. || || Thanks for any help you can offer.... || -Jim |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
strange encryption behavior | Larry | Outlook - General Queries | 0 | January 24th 06 10:26 PM |
Strange Files | Newsgroups | Outlook - General Queries | 0 | January 22nd 06 03:12 PM |
attachment problem | JoHNY | Outlook - General Queries | 3 | January 17th 06 09:34 PM |
Not receiving Attachment Outlook 2003 | Joe F. | Outlook - General Queries | 1 | January 16th 06 03:57 PM |
Outlook Express E-mail Attachment Is Gone | Ray10X10 | Outlook - General Queries | 1 | January 10th 06 11:16 AM |