Can i send cloab data from UTL SMTP WRITE RAW DATA?

Question

hi
here is my code to send email from oracle as attachment using demomail package provided by oracle----
create or replace procedure html_mail(
p_sender varchar2, -- sender, example: 'Me <[email protected]>'
p_recipients varchar2, -- recipients, example: 'Someone <[email protected]>'
p_subject varchar2, -- subject
p_text varchar2, -- text
p_filename varchar2, -- name of html file
p_blob blob -- html file
) is
conn utl_smtp.connection;
i number;
len number;
BEGIN
conn := demo_mail.begin_mail(
sender => p_sender,
recipients => p_recipients,
subject => p_subject,
mime_type => demo_mail.MULTIPART_MIME_TYPE);
demo_mail.begin_attachment(
conn => conn,
mime_type => 'application/csv',
inline => TRUE,
filename => p_filename,
transfer_enc => 'base64');
-- split the Base64 encoded attachment into multiple lines
i := 1;
len := DBMS_LOB.getLength(p_blob);
WHILE (i < len) LOOP
IF(i + demo_mail.MAX_BASE64_LINE_WIDTH < len)THEN
UTL_SMTP.Write_Raw_Data (conn
, UTL_ENCODE.Base64_Encode(
DBMS_LOB.Substr(p_blob, demo_mail.MAX_BASE64_LINE_WIDTH, i)));
ELSE
UTL_SMTP.Write_Raw_Data (conn
, UTL_ENCODE.Base64_Encode(
DBMS_LOB.Substr(p_blob, (len - i)+1, i)));
END IF;
UTL_SMTP.Write_Data(conn, UTL_TCP.CRLF);
i := i + demo_mail.MAX_BASE64_LINE_WIDTH;
END LOOP;
demo_mail.end_attachment(conn => conn);
demo_mail.attach_text(
conn => conn,
data => p_text,
mime_type => 'text/csv');
demo_mail.end_mail( conn => conn );
END;
Above i m using
p_blob blob -----to send message as attachment now i have table containg data into clob format nw if i send it as it is just changing coulmn from Pblob--- Clob
then it gives me error at UTL SMTP WRITE RAW DATA...
for that i do wrkaround as i m taking data from table as clob convert it to blob and
send as attachment ...
can any one guide me little that is this approcah proper?do i really need to convert data from clob to blob?
bcause in 10g Mail UTL_MAIL raw attachment i have limitation on size of email.attachment........

Answer 1

> still no email comes. No error as well.
SMTP itself is straight forward. It is a delivery protocol. And very easy to implement. Which is what UTL_SMTP does - without bugs or errors (none to my knowledge and experience using UTL_SMTP extensively for a long time now).
The problems experience are 50% of the time, incorrectly using SMTP. The other 50% of the time, incorrectly constructing a Mime Internet Message Body for SMTP to deliver. Both are issues that the caller (app code using UTL_SMTP) needs to address.
As UTL_SMTP is program-driven, it is not that easy to play with and debug the conversation with the SMTP server - and figure out just what the SMTP server expects, not like, disallows, etc.
In order to make sure that you are having a proper/valid conversation with the SMTP server, do it interactively using a telnet session on the Oracle server platform. All you do with telnet is to send the very same PL/SQL coded SMTP commands and parameters to the SMTP server - but interactively.
E.g.
/home/billy> telnet mail 25
Trying 165.143.128.194...
Connected to mail
Escape character is '^]'.
220 mail Tue, 13 May 2008 11:20:59 +0200
HELO 10.251.93.58
250 mail: Hello [10.251.93.58]
MAIL FROM:<[email protected]>
250 <[email protected]>: Sender Ok
RCPT TO:<[email protected]>
250 <[email protected]>: Recipient Ok
DATA
354 mail: Send data now. Terminate with "."
Subject: Test Message
This is a test e-mail.
250 mail: Message accepted for delivery
QUIT
221 mail closing connection. Goodbye!
Connection closed by foreign host.
/home/billy>
Simply substitute the SMTP parameters you use in your PL/SQL calls to UTL_SMTP above. And use the same SMTP command sequence as you do in your code.
Note that in the above case, the SMTP server quite happily accepted incorrect and undeliverable sender and recipient addresses. Which means that the e-mail will wind up in the Big Bit Bucket In The Sky. No errors.