[cobalt-users] Attachment problem--Seems to be filtered by file extension

["Roger Majoros" <rmajoros@xxxxxxxxxxxxxxxxx>]

Hi

 

I'm having a problem with email attachments. We sent the Qube 2 up for our POP email server. Messages would come through but any file attachments were empty files. I tried experimenting with the email and found that attachments with certain filename extensions came through correctly. .html, .gif, .txt, and .bmp all come through. All other extensions I tried didn't. Thus, I could rename an .xls file to .txt and it would come through, I just needed to rename it.

 

I telnetted in and looked at the mailbox file.
Here is what an attachment with a .txt extension looks like...

<snip>
------=_NextPart_000_0002_01BFB5BD.B31B9940
Content-Type: text/plain;
 name="Copy of Log1.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Copy of Log1.txt"

 

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAALgAAAAAAAAAA [Message body contiues]
<snip>

 

Here is what a attachment of .doc (one of the extensions that won't email correctly) looks like...
<snip>
------=_NextPart_000_0002_01BFB5BF.4900BF70
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment;
        filename="Copy of index.doc"

 

------=_NextPart_000_0002_01BFB5BF.4900BF70--

 

There is no message body for the attachment.

 

I also found that using UUENCODE as the mail format made the attachment go throught without  any modification to the filename. We use Outlook 2000 here. Any thoughts on how to make MIME attachments come through correctly without having the change the file extension?

 

Thank you,

Roger Majoros  
IFCWA          
360-748-4201 Ext. 206     
rmajoros@xxxxxxxxxxxxxxxxx