[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Tmail: Saving Excel attachments to disk.

Andrew M. Campbell

2/5/2007 3:10:00 PM

I'm using ActionMailer, which uses Tmail, to save
Excel attachments to disk. I found a tutorial for
saving attachments. However whether I decode the
message part or not. Excel says the file is corrupt.
I'm using Windows XP, latest stable Ruby and latest
Rails gem. The mails I receive are valid multipart
mail messages. The spreadsheet attachments are valid
as well. Any Suggestions on the proper way to save
Excel attachments using Tmail?

My code is very similar to this tutorial. All I do is
check the content type of each part. If it is an
Excel spreadsheet. I push it onto an array. Then
iterate over the array of spreadsheets, saving them to
disk. The code I use to write to disk is identical to
the tutorial.
http://mondragon.cc/blog/articles/2006/12/30/decoding-email-attachments-with-actionmailer-ba...

Thanks,

1 Answer

Jano Svitok

2/5/2007 3:29:00 PM

0

On 2/5/07, Andrew M. Campbell <listdata@sbcglobal.net> wrote:
> I'm using ActionMailer, which uses Tmail, to save
> Excel attachments to disk. I found a tutorial for
> saving attachments. However whether I decode the
> message part or not. Excel says the file is corrupt.
> I'm using Windows XP, latest stable Ruby and latest
> Rails gem. The mails I receive are valid multipart
> mail messages. The spreadsheet attachments are valid
> as well. Any Suggestions on the proper way to save
> Excel attachments using Tmail?
>
> My code is very similar to this tutorial. All I do is
> check the content type of each part. If it is an
> Excel spreadsheet. I push it onto an array. Then
> iterate over the array of spreadsheets, saving them to
> disk. The code I use to write to disk is identical to
> the tutorial.
> http://mondragon.cc/blog/articles/2006/12/30/decoding-email-attachments-with-actionmailer-ba...
>
> Thanks,

try adding "binary" to File.open() if you're on windows

you can check if this is your problem by sending a known file to
yourself and compare the sent and received files - if there's a
problem, they'd differ in length, just make sure the sent file
contains \n (13)