Re: utl_mail adds CRLF at beginning of varchar2 attachments

From: neil kodner <nkodner_at_gmail.com>
Date: Tue, 6 May 2008 14:57:02 -0700 (PDT)
Message-ID: <86d1b22e-1369-4f85-9c1f-2667fba952b2@j22g2000hsf.googlegroups.com>


On May 6, 3:14 pm, yf..._at_vtn1.victoria.tc.ca (Malcolm Dew-Jones) wrote:
> neil kodner (nkod..._at_gmail.com) wrote:
>
> : Using 10.2.0.3.0 on solaris, I'm trying to write some tests against
> : utl_mail.send_attach_varchar2.  I receive the email and the
> : attachments, but the attachment always begins with a leading blank
> : line.  I've tried varying the att_mime_type but am still having the
> : same problem.  The leading blank line is preventing applications from
> : interpreting my RTF text.
>
> : Here's the code I'm using.  This example uses RTF, but examples using
> : straight text have also failed (below)
>
> : rtf example:
> : exec   UTL_MAIL.SEND_ATTACH_VARCHAR2(
> :          sender => '..._at_domain.com'
> :         ,recipients => '..._at_domain.com'
> :         ,cc => NULL
> :         ,bcc =>  NULL
> :         ,subject => 'send_attach_varchar2'
> :         ,message => 'here is a test of send_attach_varchar2'
> :         ,mime_type => 'text/plain; charset=us-ascii'
> :         ,priority => 3
> :         ,attachment => '{\rtf1\ansi{\fonttbl\f0\fswiss Helvetica;}
> : \f0\pard This is some {\b bold} text.\par}'
> :         ,att_inline => TRUE
> :         ,att_mime_type=>'application/rtf'
> :         ,att_filename => 'rtftest2.rtf'
> :     );
>
> : plain text example:
> : exec UTL_MAIL.SEND_ATTACH_VARCHAR2(
> : sender => '..._at_oracle.com'
> : ,recipients => '..._at_domain.com'
> : ,cc => NULL
> : ,bcc => NULL
> : ,subject => 'scheduled disco mail'
> : ,message => 'Testing testing testing'
> : ,mime_type => 'text/plain; charset=us-ascii'
> : ,priority => 1
> : ,attachment => 'should be in my attachment'
> : ,att_inline => FALSE
> : ,att_mime_type => 'text/plain; charset=us-ascii'
> : ,att_filename => 'neil.txt'
> : );
>
> I'm not familiar with UTL_MAIL, but the mime type of a message with
> attachments can't be 'text/plain; charset=us-ascii' .  It has to be some
> sort of multi part, like 'multipart/mixed'

Thanks for the follow-up. I am very inexperienced with email as it relates to MIME types, etc. However, I tried chaing the mime_type and the att_mime_type to multipart/mixed (independently and together), and each time, the email was sent without an attachment. Received on Tue May 06 2008 - 16:57:02 CDT

Original text of this message