Mail adapter - content coming as attachment

Hellow experts,
I am sending data from R3 to emails using mail adapter.  I am using the follwoing mail package format.  
<?xml version="1.0" encoding="UTF-8" ?>
  <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30">
  <Subject>Water Catchment Form</Subject>
  <From>[email protected]</From>
  <To>[email protected]</To>
  <Reply_To>[email protected]</Reply_To>
  <Content_Type>text/plain</Content_Type>
  <Content>You have work order(s) !!</Content>
  </ns1:Mail>
In my mail adapter, I have ticked
  Use Mail Package Format and
  Keep Attachments
I am getting the content as an attachment - I want it inside the email.
The attachment is coming with a name Untitled.pdf  - I need the actual name.
Am I missing anything?
What can I do to get things right?
Thnx

Hi Sabbir
refer this Pdf may be helpful for u
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e6c7911-0d01-0010-1aa3-8e1bb1551f05
Thanks!!

Similar Messages

  • Mail content coming as Attachment too.

    Hi -
    While we are trying to send mails using SO_DOCUMENT_SEND_API1 ,
    the mail content is coming as attachment .
    Can you suggest whats worng ?
    Thanks,
    sandhya

    Hi,
    Try using the sample code below:
    *& Report  ZBC_ITAB_TO_EXCEL_NEW                                       *
    REPORT  ZBC_ITAB_TO_EXCEL_NEW                   .
    CLASS: cl_abap_char_utilities DEFINITION LOAD.
    DATA: docdata LIKE sodocchgi1,
          objpack LIKE sopcklsti1 OCCURS 1 WITH HEADER LINE,
          objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE,
          objbin1 LIKE solisti1 OCCURS 10 WITH HEADER LINE,
          objbin2 LIKE solisti1 OCCURS 10 WITH HEADER LINE,
          objbin_final LIKE solisti1 OCCURS 10 WITH HEADER LINE,
          reclist LIKE somlreci1 OCCURS 1 WITH HEADER LINE,
          tab_lines TYPE sy-tabix.
    DATA: gd_sender_type LIKE soextreci1-adr_typ.
    DATA: c_tab TYPE c VALUE cl_abap_char_utilities=>horizontal_tab,
          c_ret TYPE c VALUE cl_abap_char_utilities=>cr_lf.
    DATA: c_dev TYPE sy-sysid.
    DATA: BEGIN OF i_data OCCURS 0,
          a(20),
          b(20),
          END OF i_data.
    DATA: BEGIN OF st,
          f1(2) TYPE c,
          f2(2) TYPE n,
          END OF st.
    DATA: itab1 LIKE TABLE OF st WITH HEADER LINE,
          itab2 LIKE TABLE OF st WITH HEADER LINE.
    DATA: n TYPE i.
    PARAMETER: p_email1 LIKE somlreci1-receiver,
                           p_sender LIKE somlreci1-receiver.
    START-OF-SELECTION.
      itab1-f1 = 'AA'. itab1-f2 = '01'. APPEND itab1.
      itab1-f1 = 'BB'. itab1-f2 = '02'. APPEND itab1.
      itab1-f1 = 'CC'. itab1-f2 = '03'. APPEND itab1.
      itab2-f1 = 'ZZ'. itab2-f2 = '26'. APPEND itab2.
      itab2-f1 = 'YY'. itab2-f2 = '25'. APPEND itab2.
      LOOP AT itab1.
        CONCATENATE itab1-f1 itab1-f2 INTO objbin1 separated BY c_tab.
        CONCATENATE c_ret objbin1 INTO objbin1.
        APPEND objbin1.
      ENDLOOP.
      LOOP AT itab2.
        CONCATENATE itab2-f1 itab2-f2 INTO objbin2 separated BY c_tab.
        CONCATENATE c_ret objbin2 INTO objbin2.
        APPEND objbin2.
      ENDLOOP.
      LOOP AT objbin1.
        MOVE objbin1-line TO objbin_final-line.
        APPEND objbin_final.
      ENDLOOP.
      LOOP AT objbin2.
        MOVE objbin2-line TO objbin_final-line.
        APPEND objbin_final.
      ENDLOOP.
      PERFORM process_email.
      c_dev = sy-sysid.
      IF sy-sysid = c_dev.
        wait up to 5 seconds.
        SUBMIT rsconn01 WITH mode = 'INT'
        WITH output = 'X'
        AND RETURN.
      ENDIF.
      IF sy-subrc = 0.
        WRITE: / 'Email succesfilly delivered'.
      ELSE.
        WRITE: / 'failure'.
      ENDIF.
    *&      Form  process_email
    *       text
    FORM process_email.
      IF p_sender EQ space.
        gd_sender_type = space.
      ELSE.
        gd_sender_type = 'INT'.
      ENDIF.
    *Body
      docdata-obj_name = 'Mail_Excel_File'.
      docdata-obj_descr = 'Excel file attachment'.
      objtxt = 'Attached is the sample Excel file'.
      APPEND objtxt.
      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 = 'RAW'.
      APPEND objpack.
    *Attachment
      n = 1.
      DESCRIBE TABLE objbin1 LINES tab_lines.
      objpack-doc_size = tab_lines * 255.
      objpack-transf_bin = 'X'.
      objpack-head_start = 1.
      objpack-head_num = 1.
      objpack-body_start = n.
      objpack-body_num = tab_lines.
      objpack-doc_type = 'XLS'.
      docdata-obj_name = 'Excel_File_Attachment1'.
      objpack-obj_descr = 'Excel File Attachment1'.
      APPEND objpack.
      n = n + tab_lines.
      DESCRIBE TABLE objbin2 LINES tab_lines.
      objpack-doc_size = tab_lines * 255.
      objpack-transf_bin = 'X'.
      objpack-head_start = 1.
      objpack-head_num = 1.
      objpack-body_start = n.
      objpack-body_num = tab_lines.
      objpack-doc_type = 'XLS'.
      docdata-obj_name = 'Excel_File_Attachment2'.
      objpack-obj_descr = 'Excel File Attachment2'.
      APPEND objpack.
    *Create the list of recipients
      reclist-receiver = p_email1.
      reclist-rec_type = 'U'.
      reclist-express = 'X'.
      APPEND reclist.
    *Send the e-mail
      CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
        EXPORTING
          document_data              = docdata
          put_in_outbox              = 'X'
          commit_work                = 'X'
        TABLES
          packing_list               = objpack
          contents_bin               = objbin_final
          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.
      COMMIT WORK.
    ENDFORM.                    "process_email
    Hope it helps
    Regards
    Mansi

  • Sender Mail Adapter Content Conversion

    Hi All,
         I just want to know if we can send a flat file(Rather Than the XML) with content conversion using Mail Adapter. If yes then what are all the possible ways for this.
    I have tried but i am sucessful in sending the complete payload as a XML file, but i want the file with the content conversion, so that this should be able to picked by the third party systems.
    Will be oblidge if any supported blog or pdf is provided for the same.
    Thanks in Advance.
    Jay

    Hi,
    Now for the negative items, i want to send them back to business as flat file format
    using the mail adapter as attachment. This will help them to process the file as for there
    requirement.
    Since you need to send an email message you have to use the format mentioned here: (S-UserID required)
    https://websmp205.sap-ag.de/~sapidb/012006153200000361852004E/ximail30_xsd.txt
    Save this file as an XSD in you local system and upload it as an External Definition in your XI server.
    Develop MI based on this External Definition (IN, ASYNC)
    Create an Interface Mapping with Source as the file containing Negative items and target as the above developed MI
    Now you need to develop an XSLT mapping (can use StylusStudio to do it) between the source and target Message Types
    This XSLT mapping has to be designed in such a way that it extracts the payload out of the Negative Items message and maps it to the target (Content) field....you need to use CDATA element of XSLT here.
    In this mapping itself you can define to what email-id you want to send the message.....
    Everything happens on the XI --> Business service side...so it is not the sender channel but is the receiver channel:)
    Your XSLT mapping will look something like:
    <Mail>
         <Content>
              XSLT CODE
         </Content>
    </Mail>
    where Mail and Content are the tags in the email message format...the External definition one.....
    If you are new to XSLT then refer to my answer in this thread...
    Re: JAVA MAPPING
    regards,
    Abhishek.

  • XI Mail Adapter: sending emails with attachment with help of java mapping

    Hi ,
    On trying out the scenerio mentioned in the blog, using the java mapping provided
    "XI Mail Adapter: An approach for sending emails with attachment with help of Java mapping
    The scenerio works just fine.
    But the payload as the content of the attachment is not getting generated in proper XML format.
    I suppose it's because of the replace special characters code part..
    Can anyone help me state the modification required in the code.
    Thanks!
    Regards,
    Faria Mithani

    It might be a codepage issue. Is your original payload UTF-8?

  • XI Mail Adapter TXT file as attachment

    Hi, I am using Mail Receiver adapter to receive data from Sender ABAP Proxy.The attachment file contains data with all Labels, i used in the Target Message Type.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:XogisticsOB_MT1 xmlns:ns0="http://selectcomfort.com/sapcrm/xogistics/outbound"><HEADER1000><EDI_HEADER_STR></EDI_HEADER_STR><TASK_ID>8000001959</TASK_ID><TOT_BOXES>        1</TOT_BOXES><NAME_LAST>Di Capri</NAME_LAST><NAME_FIRST>Sheela</NAME_FIRST>
    Please let me know how can i exclude these labels such as
    <HEADER1000> </HEADER1000> , <TASK_ID></TASK_ID>,
    <NAME_LAST></NAME_LAST> etc...
    from appearing in the File Content.
    The ModuleKey contains
    Transform.ContentDisposition attachment;filename="Outbound1.txt"
    Transform.ContentDescription Outbound1
    Transform.ContentType text/txt;name="Outbdound1.txt"
    Thanks.
    Rushikesh

    Hi,
    If ur using the mail adapter as receiver then if u dont use mail package then the attachment will come as it is file.
    If u use mail package then it will come in XML format
    for reference please check some links.
    Receiver Mail Adapter.
    /people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
    eMail Reporting
    eMail Report as Attachment (Excel/Word)
    The specified item was not found.
    The specified item was not found.
    The specified item was not found.
    Regards,
    Phani

  • Receiver Mail Adapter content conversion

    Hi
    I have read a lot of forums, etc and changed much on my adapter, but still get a xml file send as an attachment instead of a text file.
    Can anyone please advise on how to change the receiver adapter to covert from xml to text.
    I have added the module processing sequence like follow - please help.
    Processing sequence
    localejbs/AF_Modules/MessageTransformBean  Local Enterprise Bean XML2Plain
    sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean Local Enterprise Bean Mail
    Module configuration
    XML2Plain Details.endSeparator                               'nl'
    XML2Plain Details.fieldName                               ZINDUS,TCODE,TDATE,RDATE
    XML2Plain Details.fieldSeparator                          |
    XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion      xml/txt
    XML2Plain Transform.ContentDisposition                          attachment;filename="TEBA.txt"
    XML2Plain Transform.ContentType                          xml/plain
    XML2Plain xTransform.recordsetStructure                     Details
    Thanks
    Clinton

    Hi,
    From the mail adapter FAQ,
    <i>How can I set the file name of a mail attachment?
               There are several MIME headers that play a role in how the client retrieves the file name of an attachment. Unfortunately, this behavior differs among various mail clients. The reason for this inconsistent behavior comes from the fact that this mechanism has been extended incrementally. The old way is to use the name parameter in the Content-Type header as specified in RFC1341. For example, you can set the content type of an XML attachment as:
               Content-Type: application/xml; name="abc.xml"
               RFC1521 discourages the use of this name parameter in anticipation of the new header Content-Disposition, which is defined in RFC1806.
               With this Content-Disposition header, you can set the file name as:
               Content-Disposition: attachment; filename="abc.xml"
               Some clients may show the Content-Description value as the file name. The Content-Description header is typically used to associate some descriptive information to an attachment (RFC1341) as in
               Content-Description: my xml file
               To avoid potential interpretation problems, it is recommended to combine the use of these headers.</i>
    Also, the note 779981 describes how to set Content Type in the mapping program. Am not sure, but combining the two, maybe it should be possible! Havent tried something of this sort though!
    Regards
    Bhavesh

  • BPEL Workflow mail  Notification content coming as attchment

    Hi All,
    iam using actionable notifications in bpel workflow.
    iam getting mails properly but problem with payload part coming as attachment (as content.html).iam facing this problem only with Microsoft outlook.
    Here are server deatils.
    Server version: SOA suite 10.1.3.4
    My Email Client: Microsoft Outlook
    Please advice..
    Regards,
    Sudhakar.M

    Hi ,
    in workflow notification mail some part of message is coming in body ...payload details of workflow coming as attachment (as content.html)
    i tried to apply patch 8279781..but iam getting some errors
    OPatch detects your platform as 207 while this patch 8279781 supports platforms:
    0 (Generic Platform 1)
    This patch is not suitable for this operating system.
    Please contact support for the correct patch.
    ERROR: OPatch failed during pre-reqs check.
    OPatch returns with error code = 150
    can u plz me help me on this...
    Regards,
    Sudhakar.M

  • File to Mail with content as excel attachment

    Hi there,
    Can somebody please guide me in achieving this goal.
    I have a requirement in which I have to send the email content as an excel attachment which is very new to me.
    Requirement
    File.............XI............Mail
    Sender File: xyz.xml
    Mapped with standard mail.xsd and concat all the requested filed to the content but now the requirement is changed and I need to send the content as an excel attachment.
    I don't know JAVA & ABAP and this is the first time I am using mail adapter.
    Can somebody please guide me how to achieve this.
    In Another interface I have to send the source file name as a mail attachment, By Default mail adapter send the filename as untitled.
    Is there easy way to changed the name of the attachment to the source file name.
    File ............... XI.........Mail.
    Source file: xyz.xml
    No mapping required just send the file to the mail adapter but condition is that the file name should be the same.
    Mail (Attachment: xyz.xml)
    Please can somebody suggest me how to achieve this.
    Thanks,

    Hi,
    Please refer the blogs given which help you a lot regarding your requirement.
    /people/community.user/blog/2006/09/08/email-report-as-attachment-excelword
    /people/michal.krawczyk2/blog/2005/12/10/xi-generating-excel-files-without-the-java-nor-the-conversion-agent-not-possible
    /people/sap.user72/blog/2005/07/04/read-excel-instead-of-xml-through-fileadapter
    /people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
    /people/sravya.talanki2/blog/2006/01/12/xi-triggering-e-mails-with-multiple-attachments--problems

  • Sender mail adapter - filter emails by attachment?

    Dear experts,
    I have a sender mail adapter that picks an XSL (EXCEL) attachment from an incoming email and converts it (with a custom adapter module) to XML.
    But now how can I make the adapter only process emails with XLS - attachments? In that Inbox I also have emails with HTML-attachments for example. And now my adapter also wants to process those messages.
    In my adapter module that makes XLS to XML I see an exception in RWB but the message still gets through to SXMB_MONI where it gets stuck with a red flag.
    Can I somehow tell the adapter to only process emails with XLS attachments?
    Or can I stop the processing in the adapter module that converts XLS to XML?
    Thank you for any input or ideas on this!
    Best regards,
    Peter
    PS: I am using this code to convert XLS to XML:
    http://wiki.sdn.sap.com/wiki/display/ABAP/AdapterModuleToReadExcelFilewithMultipleRowsandMultiple+Columns

    Hello ChizzT,
    Thank you for your idea. I went with this one and it worked.
    Best regards,
    Peter

  • Receiver Mail Adapter message with PDF attachment

    Hi.
    We are trying to generate emails from the mail adapter that includes the plain text in the body of the resulting email and an attached PDF file. We receive the following structure:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:newMailRequest_MT xmlns:ns0="http:/pdk/sap/TorstenTest">
       <Sender/>
       <Receiver/>
       <BodyContent/>
       <Subject/>
       <Attachment/>
    </ns0:newMailRequest_MT>
    I have set up an interface and mail adapter to be able to produce emails with plain text in the body. I used SAP note 748024 for this.
    So right now I can make XI send emails with dynamic mail addresses. My problem lies in sending attached files with the mails as well.
    I have read most of the threads in here, but none of them seem to answer just how to include the attachment. Which field in the 'Mail' message type is used for the attachment??
    What needs to be added to the communication channel and adapter for it to include attachments, while the body of the mail still keeps the plain text message??

    hi
    I have used the following links to send the file as an attachement and as payload.
    so it may help u.
    links:
    /people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure - Mail Adaptor options , mail attatchment
    Sender mail adapter - PayloadSwapBean - Step by step - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6d967fbc-0a01-0010-4fb4-91c6d38c5816
    /people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken]
    /people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter
    points if helpful.
    regards
    sreeni

  • Receiver Mail adapter Content type issue

    Hello,
    I am formatting the body of the receiver mail. The body of the email  should look like below.
    Dear PI User,
    The following Interface has been successfully processed by the middleware PI system.
    Please do not reply to this email. If you need more information please contact the Super User.
    Regards,
    SAP PI Team
    The mapping looks fine and My source MT looks like this:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:MT_Mail_Reply xmlns:ns1="http://test.com/Mail/Reply"> 
    - <Reply>  [0..unbounded] 
    - <Item> [0..unbounded] 
    <MESSAGE>Dear Business User, </MESSAGE>   [0..1] 
    /Item>
    - <Item> 
    <MESSAGE>The following Interface has been successfully processed by the middleware PI system.</MESSAGE> [0..1]
    </Item>
    - <Item> 
    <MESSAGE>Please do not reply to this email. If you need more information please contact the Super User.</MESSAGE> [0..1]
    </Item>
    - <Item>
    <MESSAGE>Regards,</MESSAGE> [0..1] 
    </Item>
    - <Item>
    <MESSAGE>SAP PI Team </MESSAGE>  [0..1]
    </Item>
    </Reply>
    </ns1:MT_Mail_Reply>
    The mapping works fine without errors and I get the target message as below after mapping-
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30"> 
    <Subject>ISAP PI Interface Status</Subject> 
    <From>[email protected]</From> 
    <To>[email protected]</To> 
    <Content>Dear Business User</Content> 
    <Content>The following Interface has been successfully processed by the middleware PI system.</Content> 
    <Content>Please do not reply to this email. If you need more information please contact the Super User</Content>
      <Content>Regards,</Content>
      <Content>SAP PI Team</Content>
    </ns1:Mail>
    t
    The context of MESSAGE has been changed to Reply.
    In the adapter I still get the following error.       
    Delivery of the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: Failed to call the endpoint  [null "null"]; nested exception caused by: com.sap.aii.af.sdk.xi.util.XMLScanException: expecting end tag: {http://sap.com/xi/XI/Mail/30}Mail, but found {}Content at state 1
    Please advise !!
    Thanks,
    Teresa
    **I changed the receiver mail adapter to not use Mail package and I receive an email without errors with the Content as mentioned above. **

    Hi Teresa,
    I think the problem is that you are using multiple "Content" tags. Have you tried to use only one?, you can concatenate all your text.
    Check the page 3 of this document to know how introduce new-line character http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0964d7c-e66e-2910-24bb-ac535e4a5992?overridelayout=t…
    Regards.

  • XI Mail Adapter: Sending an XML attachment

    Hi
    I want to send an xml attachment using the XI Mail adapter. I have configured the adapter correctly and am currently receiving the email message.
    My issue is that my attachment has a .txt extention and I want it to have a .xml extn.
    I have seen a variety of web blogs around but none of these have helped.
    I have also changed my configuration from XIPAYLOAD to XIALL and still cannot get my payload message as a .xml attachment.
    When I config my adapter to use XIALL i get 2 attachments, a SOAP.xml and the my payload wiht the filename:
    [email protected]
    When I use XIPAYLOAD, with the keep attachment option ticked, I get an attachment with a .txt extn.
    I am convinced there must be a J2EE setting or maybe a ABAP config paramter that I need to update to get the .xml extn.
    Any help is greatly appreciated.
    Regards
    Yackeen

    Hi Yackeen,
    You can use localejbs/AF_Modules/MessageTransformBean
    You have to set the parameter :
    Transform.ContentDisposition as  
    attachment;filename=”myFileName.xml”>
    Best regards,
    Bela

  • Receiver Mail adapter  - Text as a attachment

    HI folks,
    These are my  screen shot link of my receiver CC
    http://farm4.static.flickr.com/3279/2946574549_aa08b8464c_o.jpg
    http://farm4.static.flickr.com/3063/2946575933_e8689c240d_o.jpg
    In my receiver  Communication channel,
    I mentioned these parameters also,
    From : xxxxATxyz.com  ( i could not at the rate symbol ..bec it considers as a email)
    to : sapATmye.com
    subject: test
    Content encoding: none
    I am mailing with in network only
    I could get email in my receiver (sapATmye.com ) inbox but only i am getting message in text format only.
    I could not get as a the attachment.
    I want the output in text format as a attachment
    My advanced thanks for the inputs.
    Thanks
    Prabaharan

    HI Gaurav,
    I am getting the error ( i tried like as u said) . even i tried that way before also ( i got the same error)
    I am getting the error RWB , CC monitoring,
         Message processing failed. Cause: com.sap.aii.af.modules.conversion.xml2plain.ConversionException: Insufficient number of fields read for structure SalesEmployee. Expected 4, got 3 at XML element MT_Receiver,SalesEmployee
    Even link for Receiver CC
    http://farm4.static.flickr.com/3289/2947598091_6dc5423a82_o.jpg
    I do not know why i am getting this kind of error even though,
    i mentioned SalesEmployee.fieldLengthExceeded ; = ignore
    in my receiver message type 2 attributes has occurence as  1 to unbounded, another 2 attributes occurence as 0 to unbounded
    Thanks
    Praba
    Edited by: Prabaharan on Oct 17, 2008 3:04 AM

  • Mail adapter - how to get rid of attachment

    Hi XI Forum,
    I want to send a simple mail notification to a user, that his/her data has passed through XI. In that connection I don't want the default behaviour of the mail adapter, which is to attach the message payload to the mail.
    In other words - I want to send a mail with NO attachment.
    How do I accomplish that ?

    Hi,
    Change the Message protocol to 'XIPAYLOAD'. Make sure you uncheck the 'Keep Attachments' checkbox. This should send the email with the xml message in the body of the email with no attachments.
    If you do not need the xml message in the body, you could use 'Mail Package' by checking the Mail Package checkbox. In this case, you need to have a mail package xml created with email id, subject and content (that could be custom text). For more instructions on how to do this, refer to Michal's weblog:
    /people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
    Regards,
    Suresh.

  • Security requirements on sender mail adapter

    I have set up a sender mail adapter to fetch the email with attachment from MS exchange mail server. The sender mail adapter can process the attachment well and convert it to XML format. Now I have a new requirement to determine if the email comes from a particular user. I can see the FROM field in the payload "MailMessage" But I don't know how to get the value of this field. Any idea on how to set up the message mapping? Thanks in advance.

    Before the sender mail adapter processes the attachment in the email, it need to determine the email is actaully from the business user not someone else on server. Cuz everyone can send email to the email address the mail adapter connects to, that is why this security issue comes from.
    Basically when you fetch a email with attachment, in Sxi_monitor, you can see two field in the payload, One is MailMessage and the other is MailAttachment-1. In the MailMessage, you can see all the emial header fields, such as From, To, Subject, Content etc. I need to check if the FROM field is email address we allowed. That is basic requirements. Let me knwo if you want me to explain it further.
    Edited by: Bai Li on Dec 23, 2010 6:02 AM

Maybe you are looking for