[quote user="tlkramer"]

I've been having trouble with attachments that I send to my home address (viewed with Pegasus mail) from my work address (can only use Outlook). When I send an attachment, even a simple text file, it comes through at home as "Unknown" and no filename. I've tried opening the attachment with several different programs but they all say it's either corrupted or not the correct format. I can forward that email back to work and it shows up just fine. I can also see and download the attachment just fine if I send it to a web based email client I also have.

 I can't find any settings in Outlook that appear to be effecting the attachments, nor can I find any settings in Pegasus that I would think might effect it (least not that aren't already set correctly). I can get mail from others just fine, it only seems to be from my Outlook at work. I've had emails with inline images attached from others and from my work Outlook. They display just fine from others but not from my work Outlook.

 I should mention that I'm using Pegasus ver. 4.41 at home and my Outlook ver at work is 2002 SP3 (10.6838.6839)

Can anybody suggest anything?

[/quote]

This problem is quite easy for resolving. There are many ways of helping here with the help of various methods. I used some tools for solving out like troubles, the next application easily will help here - outlook repair.

I've been having trouble with attachments that I send to my home address (viewed with Pegasus mail) from my work address (can only use Outlook). When I send an attachment, even a simple text file, it comes through at home as "Unknown" and no filename. I've tried opening the attachment with several different programs but they all say it's either corrupted or not the correct format. I can forward that email back to work and it shows up just fine. I can also see and download the attachment just fine if I send it to a web based email client I also have.

 I can't find any settings in Outlook that appear to be effecting the attachments, nor can I find any settings in Pegasus that I would think might effect it (least not that aren't already set correctly). I can get mail from others just fine, it only seems to be from my Outlook at work. I've had emails with inline images attached from others and from my work Outlook. They display just fine from others but not from my work Outlook.

 I should mention that I'm using Pegasus ver. 4.41 at home and my Outlook ver at work is 2002 SP3 (10.6838.6839)

Can anybody suggest anything?

Do the have a 'TNEF' header and a 'winmail.dat' attachment? (Another M$ bending of the rules)

Fentun.exe (google is your friend) can extract the attachments from winmail.dat.

You should be able to configure Outlook to not send in this format (OL rich text ??) but I don't use it so can't tell you how exactly, sorry [:(] 

I think you may have nailed my problem on the head, and unfortunately I do not think I have any recourse other than to try the Fentun. It appears that the TNEF is being utilized by the Exchange server that my company uses and there's no chance of getting that changed[:'(]. That may solve the issue of attached files but I don't think there will be any solution to HTML email that has attached images which has also been a problem from the same system. 

 I'm a little unsure even with regular attachments because I was breifly reading about Fentun.exe on one of the search results from Google. If I understand correctly Fentun can/will associate itself with the file name and/or extension and work automatically but I am not getting any file name for the attachments. When I open Pegasus' attachments tab, all I'm presented with is "Multipart section" which has two branches. One says "Plain Text" and the other says "Type Unknown". There is no filename or description so I don't know what Fentun could be associated with.

 If I look at the message in Raw View I can see  where it mentions in the headers "X-MS-TNEF-Correlator:" and in the body there is the attachment section which mentions "Content-Type: Application/ms-tnef" and "Content-transfer-encoding: Base64" but no mention of filename.

Thanks for the push in the right direction. I was even thinking it might be somehow related to my McAfee scanning my email and messing with the attachments but I turned that off and tested with another email with the same results. [Y]

Have a look at this thread, it may help.

http://community.pmail.com/forums/thread/8736.aspx

Try Winmail Opener. Configure the same way as it is described for fentun. Works for me.

You can find Winmail Opener here: http://www.eolsoft.com/freeware/winmail_opener/

Good luck!

OK this may be a silly suggestion but if there is a scroll bar displayed on the part of the attachments pane where the list is, that's where plain text etc are listed then you need to either scroll down to find the attachment or move the bar which separates the attachments list from the attachments view to give more room for the list.

 On the business of Exchange sending out attachments in this way we have used fenton for years and it seems to work just fine.   If I remember correctly this happens when exchange is incorrectly configured to send attachments to external addresses in this format as well as using it for local mail.

On the business of Exchange sending out attachments in this way we

have used fenton for years and it seems to work just fine.   If I

remember correctly this happens when exchange is incorrectly configured

to send attachments to external addresses in this format as well as

using it for local mail.

[quote user="dilberts_left_nut"]

Have a look at this thread, it may help.

http://community.pmail.com/forums/thread/8736.aspx

[/quote]

Thanks, I do think that will help. It would be so much easier if I could get the Mail Admins to correctly configure Exchange. I highly doubt they would bother because I am most likely the only one in the organization who uses a NON M$ email program at home so I'm the only one with this problem. What's more I'm just a very low Pion in the company so they won't care. [:(]

[quote user="Thomas R. Stephenson"]

On the business of Exchange sending out attachments in this way we

have used fenton for years and it seems to work just fine.   If I

remember correctly this happens when exchange is incorrectly configured

to send attachments to external addresses in this format as well as

using it for local mail.

Correct, the people running the Exchange server should fix this one.  There is no reason in the world for anyone to be sending these screwy attachments to the outside world. [/quote]

I would welcome any recommendations of how to pose it to the exchange admins regarding this issue. As I mentioned before I am most likely the only person having this problem, their most likely response would be "Use Outlook!"

[quote user="tlkramer"][quote user="Thomas R. Stephenson"]

On the business of Exchange sending out attachments in this way we

have used fenton for years and it seems to work just fine.   If I

remember correctly this happens when exchange is incorrectly configured

to send attachments to external addresses in this format as well as

using it for local mail.

Correct, the people running the Exchange server should fix this one.  There is no reason in the world for anyone to be sending these screwy attachments to the outside world. [/quote]

I would welcome any recommendations of how to pose it to the exchange admins regarding this issue. As I mentioned before I am most likely the only person having this problem, their most likely response would be "Use Outlook!"

[/quote]

You are not the only one having this problem.  Anyone not using Outlook is going to have a problem with these messages without resorting to some sort of "fentun" type workaround.  This conversion of "Rich Text" to "HTML" and MIME is pretty much an industry standard and the Exchange server system admins should be able to do this.  If nothing else they can do a search of their manuals and/or the MS knowledgebase for the way to accomplish this.