Re: do I always need to specify an encoding with Email::MIME?

2011-05-05 Thread Ricardo Signes
* James Peregrino james_peregr...@harvard.edu [2011-05-02T12:53:46]
 I'm trying to use Email::MIME to send a simple email with a .doc file as an
 attachment.  I receive it fine with Gmail, but my job email chokes on it when
 it tries to scan the attachment for viruses ('UNSCANABLE').
 
 send SMTP = Email::MIME-create(

Please consider using Email::Sender instead of Email::Send.  Seriously, it's
just as easy and so much better in the long run.  Ask me more on IRC if you
like.

 parts = [
 Email::MIME-create(
 body = The exam file is attached to this message.,
 ),
 Email::MIME-create(
 body   = io($EXAM),
 attributes = {
 filename = $EXAM_FILE_NAME,
 content_type = 'application/msword',
 },
 ),
 ],
 

I suggest doing so.  It won't hurt, and it can prevent various forms of
error.  I suggest using quoted-printable for the text and base64 for the
Word document.

-- 
rjbs


do I always need to specify an encoding with Email::MIME?

2011-05-02 Thread James Peregrino
Hi,

I'm trying to use Email::MIME to send a simple email with a .doc file as an 
attachment.  I receive it fine with Gmail, but my job email chokes on it when 
it tries to scan the attachment for viruses ('UNSCANABLE').

send SMTP = Email::MIME-create(
header = [
To  = $FROMADDR,
From= $OWNER_EMAIL,
Subject = Your exam file,
],
parts = [
Email::MIME-create(
body = The exam file is attached to this message.,
),
Email::MIME-create(
body   = io($EXAM),
attributes = {
filename = $EXAM_FILE_NAME,
content_type = 'application/msword',
},
),
],
);


Should I include an 'encoding' attribute for both parts, and if so, what should 
it be?  Would that make it more friendly to different MTAs?

-James (mako132)

--
-- James Peregrino - http://people.dce.harvard.edu/~peregrin/business-card.html