Problem wich attach in e-mail

Hello!
I have problem with attach in e-mail for bidders.
I create a bid invitation and attach any document.
[Attach|http://www.4shared.com/file/67153110/5be21d31/attach01.html]
So, i publish my bid invitation and a e-mail is send to bidder.
But, i go to the SOST and view the e-mail and attach not is there.
[Problem|http://www.4shared.com/file/67153109/3b2594d4/attach02.html]
Who can i resolve this problem? Are there any configuration for that?
Tanks!

Hi Rodrigo
You are absolutely correct. please refer this link.check the mentioned BADI in your systems controls ?
Attachment .PDF in Bid Invitation and Auction e-mail
regards
Muthu

Similar Messages

Problems with attached documents in Mail and Docs To Go

Hello everybody.
I've found a problem with attached documents in Mail. In fact, if I click on attached documents with .doc (microsoft office word 97-2004) and files in .docx Office Open .xml, the iPad doesn't open them, also if I click in "Open with Docs To Go (which should support these files' format)".
How can I do? There's an application or another way to open these files?
Other Informations:
Docs To Go version: 5.2.2

Update the patch to the Sapgui.
Regards,
Ignacio.

Problem in Attachment of the Mail

Hi, I want to send the data in Internal Table as a text attachment to the SAP User Inbox. Problem I am facing is that, the records should go Line by Line i.e. each record should start from a new line but problem I am having is that, the next record starts in the same line where previous record has ended.
E.g. records should appear like this in file :
1. AAA XXX YYY ZZZ
2. XXX YYY ZZZ AAA
rather it is appearing like :
1. AAA XXX YYY ZZZ2. XXX YYY ZZZ AAA
I am giving the Code here to generate attachment and Mail I have used. Please help.
Data Declaration
data : begin of itab occurs 0,
 ws_line(600) type c,
 end of itab.
DATA : file_name TYPE string.
data : path like PCFILE-PATH.
data : extension(5) type c.
data : name(100) type c.
DATA : receiver TYPE somlreci1-receiver VALUE 'AHUJR0'.
DATA : BEGIN OF itab_str,
 text(290) TYPE c,
 END OF itab_str.
DATA: docdata LIKE sodocchgi1,
 objpack LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
 objhead LIKE solisti1 OCCURS 0 WITH HEADER LINE,
 objtxt LIKE solisti1 OCCURS 0 WITH HEADER LINE,
 objbin LIKE itab_str OCCURS 0 WITH HEADER LINE,
 objhex LIKE solix OCCURS 0 WITH HEADER LINE,
 reclist LIKE somlreci1 OCCURS 0 WITH HEADER LINE.
DATA: tab_lines TYPE i,
 doc_size TYPE i,
 att_type LIKE soodk-objtp.
DATA: listobject LIKE abaplist OCCURS 1 WITH HEADER LINE.
Function Called to Prepare & send mail
PERFORM ml_addrecp USING receiver 'B'. "receiver contains SAP User Id
PERFORM doconv TABLES itab objbin. "itab is the table containing Data
PERFORM ml_prepare USING 'X' 'txt' grn_file. "grn_file is the name of attachment file
PERFORM ml_dosend.
Form ml_addrecp
FORM ml_addrecp USING preceiver prec_type.
CLEAR reclist.
reclist-receiver = preceiver.
reclist-rec_type = prec_type.
APPEND reclist.
ENDFORM. "ml_addrecp
Form doconv
FORM doconv TABLES mypdf STRUCTURE itab_str
 outbin STRUCTURE itab_str.
Loop And Put Data
 LOOP AT mypdf.
 outbin = mypdf.
 APPEND outbin.
 CLEAR: outbin.
 ENDLOOP.
ENDFORM. "doconv
Form ml_prepare
FORM ml_prepare USING bypassmemory whatatt_type whatname.
IF bypassmemory = ''.
Fetch List From Memory
 CALL FUNCTION 'LIST_FROM_MEMORY'
 TABLES
 listobject = listobject
 EXCEPTIONS
 OTHERS = 1.
IF sy-subrc <> 0.
 MESSAGE ID '61' TYPE 'E' NUMBER '731'
 WITH 'LIST_FROM_MEMORY'.
ENDIF.
ENDIF.
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
docdata-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objtxt ).
CLEAR objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = 'TXT'.
APPEND objpack.
Packing Info Attachment
att_type = whatatt_type..
DESCRIBE TABLE objbin LINES tab_lines.
READ TABLE objbin INDEX tab_lines.
objpack-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objbin ).
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = att_type.
objpack-obj_name = 'ATTACHMENT'.
objpack-obj_descr = whatname.
APPEND objpack.
ENDFORM. "ml_prepare
Form ml_dosend.
FORM ml_dosend.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 EXPORTING
 document_data = docdata
 put_in_outbox = 'X'
 commit_work = 'X' "used from rel. 6.10
 TABLES
 packing_list = objpack
 object_header = objhead
 contents_bin = objbin
 contents_txt = objtxt
 receivers = reclist
 EXCEPTIONS
 too_many_receivers = 1
 document_not_sent = 2
 document_type_not_exist = 3
 operation_no_authorization = 4
 parameter_error = 5
 x_error = 6
 enqueue_error = 7
 OTHERS = 8.
IF sy-subrc <> 0.
 MESSAGE ID 'SO' TYPE 'S' NUMBER '023'
 WITH docdata-obj_name.
ENDIF.
ENDFORM. "ml_dosend

Hi Ravi,
I also had the same problem, the solution to this is.... Instead of giving the TXT type to the attachment give as 'RAW' it will work... it is working for me... note the place for the comment CHANGE I HAVE DONE in the code given by you...
objpack-doc_type = 'RAW'. '' for the attachment instead of TXT...
Eg...
Packing Info Attachment
*att_type = whatatt_type.. '" CHANGE I HAVE DONE
DESCRIBE TABLE objbin LINES tab_lines.
READ TABLE objbin INDEX tab_lines.
objpack-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objbin ).
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
*objpack-doc_type = att_type. " CHANGE I HAVE DONE
objpack-doc_type = 'RAW'. " CHANGE I HAVE DONE
objpack-obj_name = 'ATTACHMENT'.
objpack-obj_descr = whatname.
APPEND objpack.
ENDFORM. "ml_prepare

Problems with Attachment location in Mail

I am using mail in Mountain Lion and whenever I forward or reply to an email and add an attachment it puts the attachment all the way at the bottom of the page. It doesn't matter where the cursor is, which is what I'm used to being the indicator as to where the attachment goes, it just puts it at the bottom of the page regardless. I have to cut the original forwarded message, back the attachment up to the message I typed, and then enter down and paste the original message back in it. It doesn't make sense, I'm around 50 Mac computers daily and mine is the only one that is doing this...
Thanks in advance!

I'm on a tower running 10.6.8 and have had this problem for months. Any help would be great!

Problem with attaching files to mail message

Hello,
I have problem with my mail app. I'm using spaces for better organization. When I wanna add some file to mail message I usually go to different desktop (space), where I have the file I wanna attach. I grab it move to right up corner to activate spaces, than move to desktop (space) with mail.app and press spacebar (it activates the desktop immediately). At that time it also start random app, which is in my dock.
You can see it in my youtube video.
How can avoid this strange thing happen?
http://www.youtube.com/watch?v=KUypUnPHZvc
I'm using MacBook Pro 15'', Snow Leopard - latest updates. I've reinstalled my mac two days ago, so no garbage should be in.

Thanks for quick reply.
I don't have selected "always..." so I also tried it with selected "always...".
Now I discovered that it has nothing to do with the mail. I've tried just move some file from one of spaces (desktop) to another using the spacebar for faster switching and it did the same. It opens random app from Dock.
So now this topic is in wrong discussion. I will post it to correct discussion...

Problems reading attached files in Mail 5.2

After moving messages from inbox to different mailboxes, it sometimes happens that the attached file (exel, word...) disappears as an attachment and is no longer readable. > The content converts itself as a long text looking like this "CBAAAAYFAOwVzQfBwAAABgMAAOEAAgCwBMEAAgAAAOIAAABcAHAADQAAYWRtaW5pc3Ry...." and I can no longer save the file because it has disappeared!!!
I don't want to PRINT or SAVE every attachment. I just want to keep the message as long as I might need it's content. But this is no longer possible nor reliable.
CAN SOMEONE HELP ME??? Thank you :-)

Disable Mac Mail.app Inline Image Attachments
http://micahgilman.com/play/disable-mac-mailapp-inline-image-attachments/
Force Apple mail.app to display attachments as icon
http://www.sant-media.co.uk/2010/11/apple-mail-inline-attachments/
Mail.app attachment as icon
http://creativebits.org/mac_os_x/mail_app_attachment_as_icon/

Facing problem with logo in the PDF attachment when sending mail...

hi friends,
i'm facing problem with logo in the PDF attachment to the mail.
my requirement:
1. enter spool number and mail id in the selection screen.
process:
1. now the program will fetch the spool data and converts it to PDF.
2. but when i'm trying to send mail with this PDF as attachment.
when i open the PDF file from the mail, logo is not coming properly (looks disturbed).
can anyone help me how to resolve this issue...
thanks in advance, murashali.

hi dinakar, thanks for your mail...
logo looks good in spool/script/smartform.
even it look good when i download this spool to pdf and to the presentation server as pdf file.
i'm using CONVERT_OTFSPOOLJOB_2_PDF.
when i used CONVERT_ABAPSPOOLJOB_2_PDF, is gives a msg - 'spool number not found'.
here i'm using folloing code to pass pdf to the function module: SO_NEW_DOCUMENT_ATT_SEND_API1.
code:
Transfer the 132-long strings to 255-long strings
lt_mtab_pdf[] = pdf[].
LOOP AT lt_mtab_pdf INTO lwa_mtab_pdf.
    TRANSLATE lwa_mtab_pdf USING ' ~'.
    CONCATENATE lv_gd_buffer lwa_mtab_pdf INTO lv_gd_buffer.
    CLEAR lwa_mtab_pdf.
ENDLOOP.
TRANSLATE lv_gd_buffer USING '~ '.
DO.
    lwa_mess_att = lv_gd_buffer.
    APPEND lwa_mess_att TO lt_mess_att.
    CLEAR lwa_mess_att.
    SHIFT lv_gd_buffer LEFT BY 255 PLACES.
    IF lv_gd_buffer IS INITIAL.
      EXIT.
    ENDIF.
ENDDO.
NOTE: problem i believe is with ''. i'm getting this tilt symbol () in my pdf internal table. here in the above code the line   TRANSLATE lv_gd_buffer USING '~ ' is changing the existing tilt to space. so my logo is getting disturbed.
even i tried with REPLACE this tilt with other char, but it doent work.
can you give any idea...

Question: Is there a way to create a PDF from outlook e-mail that does not embed the attachment? better, is there a way to convert the e-mail with attachement (not embeded) as pdf pages? - Problem: I have 1400 e-mails with attachments that need to be conv

Is there a way to create a PDF from outlook e-mail that does not embed the attachment? better, is there a way to convert the e-mail with attachement (not embeded) as pdf pages?
- Problem: I have 1400 e-mails with attachments that need to be converted into pdf and the attachments cannot be embeded.
System: PC Windows 7 using Acrobat X Prof. - Thank you!

Hi ,
There is an option of embedding index for faster search while converting email to a PDF .
However I am not sure that will serve your purpose or not .
I would recommend you to get in touch with Microsoft support as well .
Meanwhile I'll work on it and get back to you in case I get a desired solution .
Regards
Sukrit Dhingra

Problem with package that create mail with PDF attachment

Hola,
I've this problem when I use the Oracle Package called "demo_mail",
that I have download from this forum en september.
The code of the Package, I post bottom, now I
write the records of the Package,
that I believe is the core of the problem:
demo_mail.begin_attachment( conn => conn,
mime_type => 'application/pdf',
inline => TRUE, filename => ''|| VC_NOMEFILE ||'',
transfer_enc => 'base64');
The mime_type is correct?
Why when I open the attachment of the mail, it say me that file type
is not correct or the file has been damneged? I need help!
Thank's
*********************************************************The steps that I've done:
1. PACKAGE demo_mail
2. PACKAGE BODY demo_mail
3. procedure P_SPEDMAILSERVATTA (that call package) this
Cannot write the code, because this the result. :(((
thank's
CREATE OR REPLACE PACKAGE demo_mail IS
-- Customize the SMTP host, port and your domain name below.
smtp_host VARCHAR2(256) := 'XXX.YYYY.IT';
smtp_port PLS_INTEGER := 25;
smtp_domain VARCHAR2(256) := 'YYYY.it';
-- Customize the signature that will appear in the email's MIME header.
-- Useful for versioning.
MAILER_ID CONSTANT VARCHAR2(256) := 'Mailer by Oracle UTL_SMTP';
--------------------- End Customizable Section ---------------------
-- A unique string that demarcates boundaries of parts in a multi-part email
-- The string should not appear inside the body of any part of the email.
-- Customize this if needed or generate this randomly dynamically.
BOUNDARY CONSTANT VARCHAR2(256) := '-----7D81B75CCC90D2974F7A1CBD';
FIRST_BOUNDARY CONSTANT VARCHAR2(256) := '--' || BOUNDARY || utl_tcp.CRLF;
LAST_BOUNDARY CONSTANT VARCHAR2(256) := '--' || BOUNDARY || '--' ||
utl_tcp.CRLF;
-- A MIME type that denotes multi-part email (MIME) messages.
MULTIPART_MIME_TYPE CONSTANT VARCHAR2(256) := 'multipart/mixed; boundary="'||
BOUNDARY || '"';
MAX_BASE64_LINE_WIDTH CONSTANT PLS_INTEGER := 76 / 4 * 3;
-- A simple email API for sending email in plain text in a single call.
-- The format of an email address is one of these:
-- someone@some-domain
-- "Someone at some domain" <someone@some-domain>
-- Someone at some domain <someone@some-domain>
-- The recipients is a list of email addresses separated by
-- either a "," or a ";"
PROCEDURE mail(sender IN VARCHAR2,
 recipients IN VARCHAR2,
 subject IN VARCHAR2,
 message IN VARCHAR2);
-- Extended email API to send email in HTML or plain text with no size limit.
-- First, begin the email by begin_mail(). Then, call write_text() repeatedly
-- to send email in ASCII piece-by-piece. Or, call write_mb_text() to send
-- email in non-ASCII or multi-byte character set. End the email with
-- end_mail().
FUNCTION begin_mail(sender IN VARCHAR2,
 recipients IN VARCHAR2,
 subject IN VARCHAR2,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 priority IN PLS_INTEGER DEFAULT NULL)
 RETURN utl_smtp.connection;
-- Write email body in ASCII
PROCEDURE write_text(conn IN OUT NOCOPY utl_smtp.connection,
 message IN VARCHAR2);
-- Write email body in non-ASCII (including multi-byte). The email body
-- will be sent in the database character set.
PROCEDURE write_mb_text(conn IN OUT NOCOPY utl_smtp.connection,
 message IN VARCHAR2);
-- Write email body in binary
PROCEDURE write_raw(conn IN OUT NOCOPY utl_smtp.connection,
 message IN RAW);
-- APIs to send email with attachments. Attachments are sent by sending
-- emails in "multipart/mixed" MIME format. Specify that MIME format when
-- beginning an email with begin_mail().
-- Send a single text attachment.
PROCEDURE attach_text(conn IN OUT NOCOPY utl_smtp.connection,
 data IN VARCHAR2,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 inline IN BOOLEAN DEFAULT TRUE,
 filename IN VARCHAR2 DEFAULT NULL,
 last IN BOOLEAN DEFAULT FALSE);
-- Send a binary attachment. The attachment will be encoded in Base-64
-- encoding format.
PROCEDURE attach_base64(conn IN OUT NOCOPY utl_smtp.connection,
 data IN RAW,
 mime_type IN VARCHAR2 DEFAULT 'application/octet',
 inline IN BOOLEAN DEFAULT TRUE,
 filename IN VARCHAR2 DEFAULT NULL,
 last IN BOOLEAN DEFAULT FALSE);
-- Send an attachment with no size limit. First, begin the attachment
-- with begin_attachment(). Then, call write_text repeatedly to send
-- the attachment piece-by-piece. If the attachment is text-based but
-- in non-ASCII or multi-byte character set, use write_mb_text() instead.
-- To send binary attachment, the binary content should first be
-- encoded in Base-64 encoding format using the demo package for 8i,
-- or the native one in 9i. End the attachment with end_attachment.
PROCEDURE begin_attachment(conn IN OUT NOCOPY utl_smtp.connection,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 inline IN BOOLEAN DEFAULT TRUE,
 filename IN VARCHAR2 DEFAULT NULL,
 transfer_enc IN VARCHAR2 DEFAULT NULL);
-- End the attachment.
PROCEDURE end_attachment(conn IN OUT NOCOPY utl_smtp.connection,
 last IN BOOLEAN DEFAULT FALSE);
-- End the email.
PROCEDURE end_mail(conn IN OUT NOCOPY utl_smtp.connection);
-- Extended email API to send multiple emails in a session for better
-- performance. First, begin an email session with begin_session.
-- Then, begin each email with a session by calling begin_mail_in_session
-- instead of begin_mail. End the email with end_mail_in_session instead
-- of end_mail. End the email session by end_session.
FUNCTION begin_session RETURN utl_smtp.connection;
-- Begin an email in a session.
PROCEDURE begin_mail_in_session(conn IN OUT NOCOPY utl_smtp.connection,
 sender IN VARCHAR2,
 recipients IN VARCHAR2,
 subject IN VARCHAR2,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 priority IN PLS_INTEGER DEFAULT NULL);
-- End an email in a session.
PROCEDURE end_mail_in_session(conn IN OUT NOCOPY utl_smtp.connection);
-- End an email session.
PROCEDURE end_session(conn IN OUT NOCOPY utl_smtp.connection);
END;
CREATE OR REPLACE PACKAGE BODY demo_mail IS
-- Return the next email address in the list of email addresses, separated
-- by either a "," or a ";". The format of mailbox may be in one of these:
-- someone@some-domain
-- "Someone at some domain" <someone@some-domain>
-- Someone at some domain <someone@some-domain>
FUNCTION get_address(addr_list IN OUT VARCHAR2) RETURN VARCHAR2 IS
addr VARCHAR2(256);
i pls_integer;
FUNCTION lookup_unquoted_char(str IN VARCHAR2,
 chrs IN VARCHAR2) RETURN pls_integer AS
c VARCHAR2(5);
i pls_integer;
len pls_integer;
inside_quote BOOLEAN;
BEGIN
inside_quote := false;
i := 1;
len := length(str);
WHILE (i <= len) LOOP
 c := substr(str, i, 1);
 IF (inside_quote) THEN
 IF (c = '"') THEN
 inside_quote := false;
 ELSIF (c = '\') THEN
 i := i + 1; -- Skip the quote character
 END IF;
 GOTO next_char;
 END IF;
 IF (c = '"') THEN
 inside_quote := true;
 GOTO next_char;
 END IF;
 IF (instr(chrs, c) >= 1) THEN
 RETURN i;
 END IF;
 <<next_char>>
 i := i + 1;
END LOOP;
RETURN 0;
END;
BEGIN
addr_list := ltrim(addr_list);
i := lookup_unquoted_char(addr_list, ',;');
IF (i >= 1) THEN
addr := substr(addr_list, 1, i - 1);
addr_list := substr(addr_list, i + 1);
ELSE
addr := addr_list;
addr_list := '';
END IF;
i := lookup_unquoted_char(addr, '<');
IF (i >= 1) THEN
addr := substr(addr, i + 1);
i := instr(addr, '>');
IF (i >= 1) THEN
 addr := substr(addr, 1, i - 1);
END IF;
END IF;
RETURN addr;
END;
-- Write a MIME header
PROCEDURE write_mime_header(conn IN OUT NOCOPY utl_smtp.connection,
 name IN VARCHAR2,
 value IN VARCHAR2) IS
BEGIN
utl_smtp.write_data(conn, name || ': ' || value || utl_tcp.CRLF);
END;
-- Mark a message-part boundary. Set <last> to TRUE for the last boundary.
PROCEDURE write_boundary(conn IN OUT NOCOPY utl_smtp.connection,
 last IN BOOLEAN DEFAULT FALSE) AS
BEGIN
IF (last) THEN
utl_smtp.write_data(conn, LAST_BOUNDARY);
ELSE
utl_smtp.write_data(conn, FIRST_BOUNDARY);
END IF;
END;
PROCEDURE mail(sender IN VARCHAR2,
 recipients IN VARCHAR2,
 subject IN VARCHAR2,
 message IN VARCHAR2) IS
conn utl_smtp.connection;
BEGIN
conn := begin_mail(sender, recipients, subject);
write_text(conn, message);
end_mail(conn);
END;
FUNCTION begin_mail(sender IN VARCHAR2,
 recipients IN VARCHAR2,
 subject IN VARCHAR2,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 priority IN PLS_INTEGER DEFAULT NULL)
 RETURN utl_smtp.connection IS
conn utl_smtp.connection;
BEGIN
conn := begin_session;
begin_mail_in_session(conn, sender, recipients, subject, mime_type,
priority);
RETURN conn;
END;
PROCEDURE write_text(conn IN OUT NOCOPY utl_smtp.connection,
 message IN VARCHAR2) IS
BEGIN
utl_smtp.write_data(conn, message);
END;
PROCEDURE write_mb_text(conn IN OUT NOCOPY utl_smtp.connection,
 message IN VARCHAR2) IS
BEGIN
utl_smtp.write_raw_data(conn, utl_raw.cast_to_raw(message));
END;
PROCEDURE write_raw(conn IN OUT NOCOPY utl_smtp.connection,
 message IN RAW) IS
BEGIN
utl_smtp.write_raw_data(conn, message);
END;
PROCEDURE attach_text(conn IN OUT NOCOPY utl_smtp.connection,
 data IN VARCHAR2,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 inline IN BOOLEAN DEFAULT TRUE,
 filename IN VARCHAR2 DEFAULT NULL,
 last IN BOOLEAN DEFAULT FALSE) IS
BEGIN
begin_attachment(conn, mime_type, inline, filename);
write_text(conn, data);
end_attachment(conn, last);
END;
PROCEDURE attach_base64(conn IN OUT NOCOPY utl_smtp.connection,
 data IN RAW,
 mime_type IN VARCHAR2 DEFAULT 'application/octet',
 inline IN BOOLEAN DEFAULT TRUE,
 filename IN VARCHAR2 DEFAULT NULL,
 last IN BOOLEAN DEFAULT FALSE) IS
i PLS_INTEGER;
len PLS_INTEGER;
BEGIN
begin_attachment(conn, mime_type, inline, filename, 'base64');
-- Split the Base64-encoded attachment into multiple lines
i := 1;
len := utl_raw.length(data);
WHILE (i < len) LOOP
IF (i + MAX_BASE64_LINE_WIDTH < len) THEN
 -- After upgrade to Oracle 9i, replace demo_base64.encode with the
 -- native utl_encode.base64_encode for better performance:
 -- utl_smtp.write_raw_data(conn,
-- utl_encode.base64_encode(utl_raw.substr(data, i,
 -- MAX_BASE64_LINE_WIDTH)));
 utl_smtp.write_raw_data(conn,
utl_encode.base64_encode(utl_raw.substr(data, i,
 MAX_BASE64_LINE_WIDTH)));
ELSE
 -- After upgrade to Oracle 9i, replace demo_base64.encode with the
 -- native utl_encode.base64_encode for better performance:
 -- utl_smtp.write_raw_data(conn,
 -- utl_encode.base64_encode(utl_raw.substr(data, i)));
 utl_smtp.write_raw_data(conn,
 utl_encode.base64_encode(utl_raw.substr(data, i)));
END IF;
utl_smtp.write_data(conn, utl_tcp.CRLF);
i := i + MAX_BASE64_LINE_WIDTH;
END LOOP;
end_attachment(conn, last);
END;
PROCEDURE begin_attachment(conn IN OUT NOCOPY utl_smtp.connection,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 inline IN BOOLEAN DEFAULT TRUE,
 filename IN VARCHAR2 DEFAULT NULL,
 transfer_enc IN VARCHAR2 DEFAULT NULL) IS
BEGIN
write_boundary(conn);
write_mime_header(conn, 'Content-Type', mime_type);
IF (filename IS NOT NULL) THEN
IF (inline) THEN
 write_mime_header(conn, 'Content-Disposition',
 'inline; filename="'||filename||'"');
ELSE
 write_mime_header(conn, 'Content-Disposition',
 'attachment; filename="'||filename||'"');
END IF;
END IF;
IF (transfer_enc IS NOT NULL) THEN
write_mime_header(conn, 'Content-Transfer-Encoding', transfer_enc);
END IF;
utl_smtp.write_data(conn, utl_tcp.CRLF);
END;
PROCEDURE end_attachment(conn IN OUT NOCOPY utl_smtp.connection,
 last IN BOOLEAN DEFAULT FALSE) IS
BEGIN
utl_smtp.write_data(conn, utl_tcp.CRLF);
IF (last) THEN
write_boundary(conn, last);
END IF;
END;
PROCEDURE end_mail(conn IN OUT NOCOPY utl_smtp.connection) IS
BEGIN
end_mail_in_session(conn);
end_session(conn);
END;
FUNCTION begin_session RETURN utl_smtp.connection IS
conn utl_smtp.connection;
BEGIN
-- open SMTP connection
conn := utl_smtp.open_connection(smtp_host, smtp_port);
utl_smtp.helo(conn, smtp_domain);
RETURN conn;
END;
PROCEDURE begin_mail_in_session(conn IN OUT NOCOPY utl_smtp.connection,
 sender IN VARCHAR2,
 recipients IN VARCHAR2,
 subject IN VARCHAR2,
 mime_type IN VARCHAR2 DEFAULT 'text/plain',
 priority IN PLS_INTEGER DEFAULT NULL) IS
my_recipients VARCHAR2(32767) := recipients;
my_sender VARCHAR2(32767) := sender;
BEGIN
-- Specify sender's address (our server allows bogus address
-- as long as it is a full email address ([email protected]).
utl_smtp.mail(conn, get_address(my_sender));
-- Specify recipient(s) of the email.
WHILE (my_recipients IS NOT NULL) LOOP
utl_smtp.rcpt(conn, get_address(my_recipients));
END LOOP;
-- Start body of email
utl_smtp.open_data(conn);
-- Set "From" MIME header
write_mime_header(conn, 'From', sender);
-- Set "To" MIME header
write_mime_header(conn, 'To', recipients);
-- Set "Subject" MIME header
write_mime_header(conn, 'Subject', subject);
-- Set "Content-Type" MIME header
write_mime_header(conn, 'Content-Type', mime_type);
-- Set "X-Mailer" MIME header
write_mime_header(conn, 'X-Mailer', MAILER_ID);
-- Set priority:
-- High Normal Low
-- 1 2 3 4 5
IF (priority IS NOT NULL) THEN
write_mime_header(conn, 'X-Priority', priority);
END IF;
-- Send an empty line to denotes end of MIME headers and
-- beginning of message body.
utl_smtp.write_data(conn, utl_tcp.CRLF);
IF (mime_type LIKE 'multipart/mixed%') THEN
write_text(conn, 'This is a multi-part message in MIME format.' ||
 utl_tcp.crlf);
END IF;
END;
PROCEDURE end_mail_in_session(conn IN OUT NOCOPY utl_smtp.connection) IS
BEGIN
utl_smtp.close_data(conn);
END;
PROCEDURE end_session(conn IN OUT NOCOPY utl_smtp.connection) IS
BEGIN
utl_smtp.quit(conn);
END;
END;
PROMPT **********************************************************
PROMPT CREAZIONE PROCEDURA P_SPEDMAILSERVATTA
PROMPT **********************************************************
create or replace procedure P_SPEDMAILSERVATTA( VC_DESCDENOAZIE IN VARCHAR2,
 VC_DESCINDIEMAI IN VARCHAR2,
 VC_NUMEBOLL IN VARCHAR2,
 VC_PATHFILE IN VARCHAR2,
 VC_NOMEFILE IN VARCHAR2,
 VC_DESCINDIEMAIMITT IN VARCHAR2)
IS
conn utl_smtp.connection;
req utl_http.req;
resp utl_http.resp;
data RAW(200);
BEGIN
conn := demo_mail.begin_mail(
sender => 'SIAG srl <'|| VC_DESCINDIEMAIMITT ||'>',
recipients => ''|| VC_DESCDENOAZIE ||' '||'<'|| VC_DESCINDIEMAI ||'>'||'',
subject => 'Invio Bollettino n.'|| VC_NUMEBOLL ||'',
mime_type => demo_mail.MULTIPART_MIME_TYPE);
demo_mail.attach_text(
conn => conn,
data => 'Spett.le '|| VC_DESCDENOAZIE ||' in allegato Le invio il Bollettino n. '|| VC_NUMEBOLL ||'. Distinti Saluti <hr align="left" width="20%"> ',
mime_type => 'text/html');
demo_mail.begin_attachment(
conn => conn,
mime_type => 'application/pdf',
inline => TRUE,
filename => ''|| VC_NOMEFILE ||'',
transfer_enc => 'base64');
-- In writing Base-64 encoded text following the MIME format below,
-- the MIME format requires that a long piece of data must be splitted
-- into multiple lines and each line of encoded data cannot exceed
-- 80 characters, including the new-line characters. Also, when
-- splitting the original data into pieces, the length of each chunk
-- of data before encoding must be a multiple of 3, except for the
-- last chunk. The constant demo_mail.MAX_BASE64_LINE_WIDTH
-- (76 / 4 * 3 = 57) is the maximum length (in bytes) of each chunk
-- of data before encoding.
req := utl_http.begin_request('http://localhost/'|| VC_PATHFILE ||'/'|| VC_NOMEFILE ||'');
resp := utl_http.get_response(req);
BEGIN
LOOP
utl_http.read_raw(resp, data, demo_mail.MAX_BASE64_LINE_WIDTH);
demo_mail.write_raw(
conn => conn,
message => utl_encode.base64_encode(data));
END LOOP;
EXCEPTION
WHEN utl_http.end_of_body THEN
utl_http.end_response(resp);
END;
demo_mail.end_attachment( conn => conn );
demo_mail.end_mail( conn => conn );
END;
Message was edited by:
mosquito70
Message was edited by:
mosquito70

Hola, I've this problem when I use the Oracle Package called "demo_mail",
that I have download from this forum en september.
The code of the Package, I post bottom, now I
write the records of the Package,
that I believe is the core of the problem:
demo_mail.begin_attachment( conn => conn,
mime_type => 'application/pdf',
inline => TRUE, filename => ''|| VC_NOMEFILE ||'',
transfer_enc => 'base64');
The mime_type is correct?
Why when I open the attachment of the mail, it say me that file type
is not correct or the file has been damneged? I need help!
Thank's
The steps that I've done:
1. PACKAGE demo_mail
2. PACKAGE BODY demo_mail
3. procedure P_SPEDMAILSERVATTA (that call package)
I cannot post the code :((

Problem in attach a file during mail

I am facing problem while attaching a file during mailing

What file ?
If its some Office document (word / excel) .. first open the document and then (...)-->share and select your mail client ..

Mail problems,,no attachements options

HI,
I just started to use iPad 2 And having problems with mail accounts. I am trying to compose mail and I am not getting an option to add or change front, add attachements.... And all the other options associated with creating emails... All I am seeing is to, from, subject . Please help. Thanks

With attachments, you don't add them to the mail as much as you go to where the attachment is stored or the app that manages it and send the attachment to the mail to be mailed.
In other words, I can't go into mail and attach a photo, but I can go into the photo app, choose the photo I want to mail and send it to the mail app to be attached.
The symbol for that is the little box with the little arcing arrow coming out of it.
As to changing fonts, etc, I believe that the options for that are pretty limited on the iPad.

What's with the new edition of Pages using Maverick? Google rejects the files with the following message attached "The reason for the problem: 5.3.0 - Other mail system problem 552-'5.7.0 This message was blocked as its content security threat?

I recently upgraded both Pages 09 (I believe) and went to OSX 10.9 Maverick .... now I am unable to send a pages document to a friend on gmail. Google rejects the message and attachment with the following explanation -
The reason for the problem:
5.3.0 - Other mail system problem 552-'5.7.0 This message was blocked because its content presents a potential\n5.7.0 security issue.

Same Problem here
IWORKS 09 pages, keynote, numbers does not send in MAIL (mac) because of "This message was blocked because its content presents a potentialsecurity issue"
its a problem not only on GMAIL but also Live, Hotmail, Yahoo, and other services...
The problem is that gmail and others haved yet accepted the latest iworks 09 files. its a problem that apple can ask then to fix but its up to the gmail and others to fix it.
Solution!!!:
1 - Send it by exporting to office files
2 - Saving the files as old iwork documents
3 - Command P and save as PDF
4 - Save in icloud and send the URL
So you can still send them but have to take a bit more of your time
i hope you understand my english is not optimal
And if you have any questions feel free to ask me

Problem receiving attachment with Mail 5.1

Hi all,
Just got the New Macbook Pro 15". Superb machine!
But since i set up my Mail account on Mail 5.1, I can receive and send mails... but have problems opening attachements.
It tells me that there have been a problem with the file and that It has crashed.
I don't have any problems when I open the same mail from my internet provider site.
Any suggestions are welcome.
Thank you in advance
Julien

solved by a colleague

Problems with photos attached to a mail

Normally a photo attached to a mail arrives at the addressee as a separate file which can be detached and stored separately.
Since a couple of days it does not work this way, when I use the Apple mail program to send messages from my iMac (OSX 10.5.3). Now they are embedded into the mail as very large pictures. I think there must be something wrong with the settings of mail.
Does anybody know what I can do in order to get back the "normal" state?
Message was edited by: bazsarozsa

Hallo Björn,
nochmals danke für den Tip. Es hat funktioniert. Aber normal ist das nicht. Ich vermute der Bug ist hineinoperiert worden beim Fixing eines anderen Bugs, auf den ich schon vor über einem halben Jahr in diesem Forum aufmerksam machte: seit 10.5.1 oder 10.5.2 (die kamen ja beide sehr schnell hintereinander) konnte man nicht mehr zeitgesteuert (aus den Systemeinstellungen, Energie sparen) den Ruhezustand der Festplatte anfahren. Ich habe elend lange herumexperimentiert, um herauszufinden, ob der Fehler eventuell bei meinen Macs lag. Die Ratschläge, die ich aus dem Forum bekam, waren allesamt Blödsinn. Und Apple sitzt offenbar auf einem so hohen Ross, dass die es nicht für nötig hielten, auf meinen Hilferuf im Forum zu reagieren. Gelesen hat es wohl doch einer von denen, denn als ich im Zuge dieses Schriftverkehrs aus meinem Unmut heraus eine entsprechende Bemerkung loließ, war da sofort einer, dem der Schuh offenbar passte. Der fühlte sich nämlich befleißigt, mich darüber aufzuklären, dass das Forum der Hilfe von User zu User diene und die Apple-Leute in der Regel die Beiträge nicht lesen würden. Zum Abschluss des Posts (mit 10.5.3 war der Bug nämlich behoben, und in einer Notiz im Kleingedruckten vor dem Herunterladen des updates stand ein Hinweis, dass ein Fehler im Mailprogramm daran schuld war) habe ich dann nochmal einen Hieb auf Apple ausgeteilt, und gleich war der selbe zur Stelle, um sein Statement (s. oben) zu wiederholen.
Es wäre doch schön, wenn die mal zugeben könnten, dass hier ein Fehler von Apple vorlag, bevor man wie doof im eigenen Kram nach möglichen Fehlern sucht.
Eine Hotline zur Meldung von Bugs habe ich bei Apple bisher vergeblich gesucht.
Sogar Microsoft hat so was...
(Hoffentlich hat das jetzt auch einer von denen gelesen - und verstanden!)
Gruß
Dietmar

Open Attachment option in Mail opens incorrect invite in Calendar

My issue: if I double click or use the Open Attachment option in Mail for calendar invites, an invite from 2 years ago opens in Calendar for me to accept. If I use the Add to Calendar function, no problem & reads like it should do.
I upgraded to ML about 2-3 weeks ago and Mail was spectacularly painful with the merge from SL not working at all. Calendar seemed to be ok, however this usse has started to appear in the last 24 hours.
Ivites can be accepted no dram using the iPad or my wifes iPhone just seesm to beon the Mac that its a problem.
Any thoughts/ideas/fixes would be great.
Cheers.

This link solved the problem
https://discussions.apple.com/thread/4165985?start=15&tstart=0

Problem wich attach in e-mail

Similar Messages

Maybe you are looking for