T.37 onramp fax sometimes sends empty attachment

We have T.37 onramp fax set up with incoming calls arriving on a T1 line into a Cisco 2811, and SMTP emails with fax attachments going out to our custom mailserver. We have many of these systems in the field. Most of the time onramp faxes work fine, but we sometimes see the 2811 sending an empty attachment to the mailserver. We have captured the incoming audio and decoded the fax using the Asterisk PBX utilities, with no errors at all.
What could cause a 2811 to send an empty fax attachment even though the incoming fax is good?
Here is the SMTP conversation (with names and numbers changed) -- red from the 2811, blue from the mailserver:
220-svr02.company.com Simple Mail Transfer Service Ready
220 ESMTP spoken here.
EHLO faxgateway.company.com
250-svr02.company.com
250-CHUNKING
250-DSN
250-AUTH CRAM-MD5 LOGIN PLAIN
250-AUTH=CRAM-MD5 LOGIN PLAIN
250-X-DCL-SOURCE
250-X-DCL-CALLID
250-X-DCL-DSN
250-X-DCL-REPLACE
250-X-DCL-TRANSCRIPT
250-X-DCL-SENT-ITEMS
250-X-DCL-GHOST
250-X-MSW-NOTIFY-SUPPRESS
250-X-MSW-OP
250 SIZE 0
MAIL FROM:<[email protected]>
250 OK
RCPT TO:<[email protected]>
250 OK
DATA
354 Start mail input, end with <CRLF>.<CRLF>
Received: by faxgateway.company.com for <[email protected]> (with Cisco NetWorks); Thu, 21 Nov 2013 16:22:01 -0500
To: "1231231234" <[email protected]>
Message-ID: <[email protected]>
Date: Thu, 21 Nov 2013 16:22:01 -0500
Subject: Fax
X-Mailer: Technical Support: http://www.cisco
MIME-Version: 1.0
Content-Type: multipart/fax-message;
boundary="yradnuoB=_7FCF2013162201695.faxgateway.company.com"
From: "2342342345" <[email protected]>
X-Account-Id: 0
--yradnuoB=_7FCF2013162201695.faxgateway.company.com
Content-ID: <[email protected]>
Content-Type: image/tiff; name="Cisco_fax.tif"; application=faxbw
Content-Disposition: attachment
Content-Transfer-Encoding: base64
--yradnuoB=_7FCF2013162201695.faxgateway.company.com--
550 Fax message contains 0 pages
Note that our custom mailserver rejects these empty fax attachments because we want the sending fax machine to see a failure in this case. (If the mailserver were to accept the empty attachment, then the sender would see success but the receiver would receive no fax.)
The 2811 is running IOS 12.4(25d) and non-default DSP software 26.4.501 (updated to fix a problem with the DIS tones). But we've been seeing this problem since 12.4(6)T7 with no DSP firmware patch.
We've enabled all the relevant fax debug logs we can find, and here's the debug output for a 'zero-page fax' call from the point where the T1 connection is established, down to the point where the empty attachment is sent and the mailserver rejects it (names and numbers changed as before):
Nov 21 21:21:53.511: ISDN Se1/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0xAA14
        Channel ID i = 0xA98382
                Exclusive, Channel 2
Nov 21 21:21:53.511: ISDN Se1/0:23 Q931: TX -> CONNECT pd = 8 callref = 0xAA14
Nov 21 21:21:53.539: ISDN Se1/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x2A14
Nov 21 21:21:53.543: %ISDN-6-CONNECT: Interface Serial1/0:1 is now connected to N/A N/A
Nov 21 21:21:56.511: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   CSI_PACKET(1231231234)
   DIS_PACKET(speed=5, resolution=1, encoding=1)
Nov 21 21:21:56.511: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_response_receive, PROCESSING
Nov 21 21:21:59.399: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
   received flag of modulation: 0
Nov 21 21:21:59.399: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_response_receive, PROCESSING
Nov 21 21:21:59.739: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
   received flag of modulation: 0
Nov 21 21:22:00.719: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_response_receive, PROCESSING
Nov 21 21:22:01.311: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
   msg dump (size=23):
   FF C0 C2 1C EC 8C 2C 8C 2C 4C 6C AC 4C 04 04 04 04 04 04 04
   04 04 04
Nov 21 21:22:01.311: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
   received=TSI, remote id string:=          2342342345
Nov 21 21:22:01.311: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_response_receive, PROCESSING
Nov 21 21:22:01.407: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_response_receive, PROCESSING
Nov 21 21:22:01.647: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
   msg dump (size=10):
   FF C8 C1 00 45 1F 01 01 01 00
Nov 21 21:22:01.647: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_response_receive, PROCESSING
Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
   in response receive WAIT FOR CD
Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/CCAPI/cc_api_event_indication:
   Event=36, Call Id=50796
Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   received DCS_PACKET, BR=9, resolution=0,encoding=1, remote_id_string=          2342342345
Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   wait for ready for data from application
Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
   Event(Tag=36, Name=CC_EV_FROM_FMSP_ON_CALL_DETAIL, Disposition=0)
   Call Record(Call State=LAPP_ON_CS_FMSP_CALL_DETAIL(2))
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_msp_event:
   Event(Tag=36, Name=CC_EV_FROM_FMSP_ON_CALL_DETAIL)
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Prepare MSPI Call Setup Request
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Envelope [email protected]
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Envelope [email protected]
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   RFC822 To Comment=1231231234
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Faxmail Subject=Fax
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Disposition Notification=
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Originator TSI=RFC822 From Comment=2342342345
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Auth/Account ID: `0'
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
   Call Setup Request To MSPI
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/CCAPI/ccCallSetupRequest:
   Destination=, Calling IE Present=FALSE, Mode=0,
   Outgoing Dial-peer=3, Params=0x45E136F0, Progress Indication=NULL(0)
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/CCAPI/ccCallSetupRequest:
   Destination Pattern=.T, Called Number=1231231234, Digit Strip=FALSE
Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/CCAPI/ccCallSetupRequest:
   Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=1231231234(TON=Unknown, NPI=Unknown),
   Redirect Number=, Display Info=
   Account Number=, Final Destination Flag=TRUE,
   Guid=C6DA8CB3-5229-11E3-B86D-58BC273896C0, Outgoing Dial-peer=3
Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=1231231234
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=-1
   cisco-rdnplan=-1
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1
Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x453B5564, Interface Type=19, Destination=, Mode=0x0,
   Call Params(Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Al                                                                                      lowed),
   Called Number=1231231234(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3, Call Count                                                                                       On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=                                                                                      )
Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_new_context_guid:exit@2190
Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/MSPI_ON/mspi_call_setup_request:
   Outgoing Peer Tag=3
   Envelope [email protected]
   Envelope [email protected]
   Mime Outer Type=2
Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_open:
   [email protected], [email protected]
Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_open:exit@1881
Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_add_headers:
   from_comment=2342342345
Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/VTSP:(1/0:23):1:1:1/vtsp_spi_event_handler:
   Event Category=1, Event=138
Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/CCAPI/ccIFCallSetupRequestPrivate:
   SPI Call Setup Request Is Success; Interface Type=19, FlowMode=1
Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/CCAPI/ccCallSetContext:
   Context=0x44047884
Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:exit@791
Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_fmsp_dmsp:
    Starting Conference with FMSP and DMSP
Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_fmsp_dmsp:
   Tiff File Created; Time=2013:11:21 16:22:01
Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_call_setup_request:
   ramp data dir=ONRAMP, conf dir=DEST
Nov 21 21:22:01.699: //50796/xxxxxxxxxxxx/CCAPI/ccConferenceCreate:
   (confID=0x440478F0, callID1=0xC66C, callID2=0xC66E, tag=0x0)
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
   Conference Id=0x440478F0, Call Id1=50796, Call Id2=50798, Tag=0x0
Nov 21 21:22:01.699: //50796/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
   Conference Id=0x8B2C, Source Interface=0x45F255A0, Source Call Id=50796,
   Destination Call Id=50798, Disposition=0x0, Tag=0x0
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/cc_api_caps_ind:
   Destination Interface=0x45F2554C, Destination Call Id=50798, Source Call Id=50796,
   Caps(Codec=0x4, Fax Rate=0x2, Vad=0x2,
   Modem=0x0, Codec Bytes=20, Signal Type=2)
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/cc_api_caps_ind:
   Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),
   Playout Max=250(ms), Fax Nom=300(ms))
Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_caps_ind:
   CallId=50798, srcCallId=50796
Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
   conf id=0x8B2C, srcCallId=50798, dstCallId=50796,
   ramp data dir=ONRAMP, conf dir=DEST, encode out=0
Nov 21 21:22:01.699: //50798/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
   Conference Id=0x8B2C, Source Interface=0x45F2554C, Source Call Id=50798,
   Destination Call Id=50796, Disposition=0x0, Tag=0x0
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/cc_generic_bridge_done:
   Conference Id=0x8B2C, Source Interface=0x45F2554C, Source Call Id=50798,
   Destination Call Id=50796, Disposition=0x0, Tag=0x0
Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
   Bridge done
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
   Call Entry(Conference Id=0x8B2C, Destination Call Id=50795)
Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
   Call Entry(Conference Id=0x8B2C, Destination Call Id=50796)
Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/CCAPI/ccCallSetContext:
   Context=0x44047884
Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_change_state:
   Old State=LAPP_ON_CS_FMSP_CALL_DETAIL(2),
   New State=LAPP_ON_CS_FMSP_DMSP_CONFERENCING(3)
Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_msp_event:exit@2079
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
   Event(Tag=29, Name=CC_EV_CONF_CREATE_DONE, Disposition=0)
   Call Record(Call State=LAPP_ON_CS_FMSP_DMSP_CONFERENCING(3))
Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_created:
   FMSP and DMSP Are Conferenced
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_created:
   Sending RECEIVE ENABLE to FMSP
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/ccDeliverEvent:
   Event Category=0, Call Id=50796
Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_change_state:
   Old State=LAPP_ON_CS_FMSP_DMSP_CONFERENCING(3),
   New State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4)
Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   send CFR_PACKET
Nov 21 21:22:01.703: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_configure_rx_data, STILL_LOOKING, T2 timer not expired
Nov 21 21:22:01.703: //50796/C6DA8CB3B86D/CCAPI/cc_process_notify_bridge_done:
   Conference Id=0x8B2C, Call Id1=50796, Call Id2=50798
Nov 21 21:22:01.847: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   socket 0 readable for first time
Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   socket 0 readable for first time
Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 220-svr02.company.com Simple Mail Transfer Service Ready
Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   socket 0 readable for first time
Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 220 ESMTP spoken here.
Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: EHLO faxgateway.company.com
Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.875: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-svr02.company.com
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-CHUNKING
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-DSN
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-AUTH CRAM-MD5 LOGIN PLAIN
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-AUTH=CRAM-MD5 LOGIN PLAIN
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-SOURCE
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-CALLID
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-DSN
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-REPLACE
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-TRANSCRIPT
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-SENT-ITEMS
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-DCL-GHOST
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-MSW-NOTIFY-SUPPRESS
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-MSW-OP
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250 SIZE 0
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: MAIL FROM:<[email protected]>
Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.895: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250 OK
Nov 21 21:22:01.895: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: RCPT TO:<[email protected]>
Nov 21 21:22:01.895: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.911: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 250 OK
Nov 21 21:22:01.911: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 354 Start mail input, end with <CRLF>.<CRLF>
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Received: by faxgateway.company.com for <[email protected]> (with Cisco NetWorks); Thu, 21 Nov 2013 16:22:01 -0500
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: To: "1231231234" <[email protected]>
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Message-ID: <[email protected]>
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Date: Thu, 21 Nov 2013 16:22:01 -0500
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Subject: Fax
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: X-Mailer: Technical Support: http://www.cisco
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: MIME-Version: 1.0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Content-Type: multipart/fax-message;
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: boundary="yradnuoB=_7FCF2013162201695.faxgateway.company.com"
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: From: "2342342345" <[email protected]>
Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:01.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: X-Account-Id: 0
Nov 21 21:22:01.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/MSPI_ON/mspi_check_connect:
   MMccb(Count=0)
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/MSPI_ON/mspi_check_connect:
   SMTP Connected To The Server !
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_connected:
   Interface=0x453B5564, Data Bitmask=0x0, Progress Indication=NULL(0),
   Connection Handle=0
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_connected:
   Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0)
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
   Event(Tag=8, Name=CC_EV_CALL_CONNECTED, Disposition=0)
   Call Record(Call State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4))
Nov 21 21:22:02.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_call_connected:
   MSPI call connected:
   Start Conferencing DMSP and MSPI
Nov 21 21:22:02.695: //50798/xxxxxxxxxxxx/CCAPI/ccConferenceCreate:
   (confID=0x440478F4, callID1=0xC66E, callID2=0xC66D, tag=0x0)
Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
   Conference Id=0x440478F4, Call Id1=50798, Call Id2=50797, Tag=0x0
Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
   conf id=0x8B2D, srcCallId=50798, dstCallId=50797,
   ramp data dir=ONRAMP, conf dir=SRC, encode out=0
Nov 21 21:22:02.695: //50798/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
   Conference Id=0x8B2D, Source Interface=0x45F2554C, Source Call Id=50798,
   Destination Call Id=50797, Disposition=0x0, Tag=0x0
Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
   Bridge done
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/MSPI/mspi_bridge:
   MMccb(State=CONNECTED, Type=Onramp), Destination Call Id=50798
Nov 21 21:22:02.695: //50797/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
   Conference Id=0x8B2D, Source Interface=0x453B5564, Source Call Id=50797,
   Destination Call Id=50798, Disposition=0x0, Tag=0x0
Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/CCAPI/cc_generic_bridge_done:
   Conference Id=0x8B2D, Source Interface=0x453B5564, Source Call Id=50797,
   Destination Call Id=50798, Disposition=0x0, Tag=0x0
Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
   Call Entry(Conference Id=0x8B2D, Destination Call Id=50796)
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
   Call Entry(Conference Id=0x8B2D, Destination Call Id=50795)
Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/ccCallSetContext:
   Context=0x44047884
Nov 21 21:22:02.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_call_connected:exit@2508
Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
   Event(Tag=29, Name=CC_EV_CONF_CREATE_DONE, Disposition=0)
   Call Record(Call State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4))
Nov 21 21:22:02.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
Nov 21 21:22:02.699: //50798/C6DA8CB3B86D/CCAPI/cc_process_notify_bridge_done:
   Conference Id=0x8B2D, Call Id1=50798, Call Id2=50797
Nov 21 21:22:06.487: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
   received flag of modulation: 0
Nov 21 21:22:06.487: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_configure_rx_data, DETECTED_COMMAND
Nov 21 21:22:06.487: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_command_receive, NO_COMMAND, T2 timer not expired
Nov 21 21:22:12.275: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
   received flag of modulation: 0
Nov 21 21:22:13.207: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_command_receive, PROCESSING
Nov 21 21:22:13.267: //50796/C6DA8CB3B86D/FMSP/fax2_command_receive:
   msg dump (size=3):
   FF C8 F4
Nov 21 21:22:13.267: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_command_receive, PROCESSING
Nov 21 21:22:13.287: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
   fax2_command_receive, RECEIVED_COMMAND
Nov 21 21:22:13.287: //50796/C6DA8CB3B86D/FMSP/fax2_phaseD_receive:
   received EOP
Nov 21 21:22:13.287: //50798/C6DA8CB3B86D/DMSP/docmsp_xmit:
   srcCallId=50796, dstCallId=50798, direction=0
Nov 21 21:22:13.287: //50796/C6DA8CB3B86D/FMSP/fax2_phaseD_receive:
   waiting for page acceptance by the application
Nov 21 21:22:13.287: //50797/C6DA8CB3B86D/MSPI_ON/mspi_xmit:
   MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=0),
   Source Call Id=50798
Nov 21 21:22:13.287: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_xmit:
   EOD Received
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: --yradnuoB=_7FCF2013162201695.faxgateway.company.com
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Content-ID: <[email protected]>
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Content-Type: image/tiff; name="Cisco_fax.tif"; application=faxbw
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Content-Disposition: attachment
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: Content-Transfer-Encoding: base64
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_send_data_cisco:exit@849
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: --yradnuoB=_7FCF2013162201695.faxgateway.company.com--
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   Sending terminating dot ...(socket=0)
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
   (C)S: .
Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
   return code=0
Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
   (C)R: 550 Fax message contains 0 pages
Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   error in SMTP server's response to terminating "."
Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   ERROR, socket=0
Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
   Finishing, socket=-1, bytes send=1091
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
   MMccb(Call State=CONFERENCED, Buffer Count=1)
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
   EOD Received; Status=1
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
   Message [email protected]
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
   Status=1
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI/mspi_set_disconnect_text:
   MMccb(Disconnect Cause=network out of order (38): SMTP client engine not completed)
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_disconnected:
   Cause Value=38, Interface=0x453B5564, Call Id=50797
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_disconnected:
   Call Entry(Responsed=TRUE, Cause Value=38, Retry Count=0)
Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
   Event(Tag=11, Name=CC_EV_CALL_DISCONNECTED, Disposition=0)
   Call Record(Call State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4))
Nov 21 21:22:13.963: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984

Still not solved. Cisco support suggested adding the config command 'mta send success-fax-only' which is supposed to prevent sending empty emails or partial faxes, however there's a bug that means that has no effect IOS 12.4. We're looking at upgrading to 15.1(4)M8 which has the fix, but that will take some time.
Your problem sounds slightly different. See if you can get a network capture of the SMTP conversation with the target mailserver, to see if something's going wrong there.

Similar Messages

Send order attachment by fax

Hi friends,
I need to send the order attachment as well as the order by fax.
1. is it possible?
2. how can this be achieved?
thanks in advance,
Michal.

Hello,
As you know you can't send an attachment through FAX.
But you can send an order through fax. For that you have to do the following setting.
1. Set the Medium as FAX for the vendor for a purchasing organisation .
2. You have to create a smart from and using BADI bbp_output_change badi you have to set that smartfrom for a logical system.
3. Now when a PO will be created on that purchasing organisation for that Vendor , PO will automatically send to the vendor through FAX . Vendor will get a documents which is created using the smartfrom.
Regards,
Anindya

How to send an attachment thru mail in SAP?

Hi all,
I have an file which has been sent by the customer. The file type may vary each & every week (sometimes XLS, sometimes CSV & sometimes notepad). This file has to be sent to another person thru mail as an attachment.
Is it possible to send thru the fun mod 'SO_SEND_NEW_*'.
If so how to send as attachment. If not thru this fun mod, how to send?
Thanks,
Vijay.

I am enclosing the sample code to trigger an email, The logic for this is in comments, check this I am shure yuor problem will be solved.
*& Report ZGBL_SLA_PER
REPORT zgbl_sla_per NO STANDARD PAGE HEADING LINE-COUNT 26(3) MESSAGE-ID
zmsg2.
DECLARATION OF DB TABLES
TABLES: zncrfid, zrule_id.
DECLARATION OF INTERNAL TABLES
DATA: BEGIN OF ncrf OCCURS 0,
zncrf_id(15) TYPE c,
zncrf_l4_name(60) TYPE c,
z9gl_sla_flag(1) TYPE c,
zowners(30) TYPE c,
zowners_value(30) TYPE c,
zdate_changed(8) TYPE n,
ztime_changed(6) TYPE n,
END OF ncrf.
*DATA: NCRF LIKE ZNCRFID OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF it_ruleid OCCURS 0,
zrule_id(10) TYPE c,
zowners(30) TYPE c,
zowners_value(30) TYPE c,
END OF it_ruleid.
*data: wa like ncrf occurs 0 with header line.
DATA: BEGIN OF itab OCCURS 0,
zncrf_id(15) TYPE c,
zncrf_l4_name(60) TYPE c,
z9gl_sla_flag(1) TYPE c,
zowners(30) TYPE c,
zowners_value(30) TYPE c,
zdate_changed(8) TYPE n,
ztime_changed(6) TYPE n,
END OF itab.
data: file(10) type c,
dates type date.
EMAIL DECLARATION
*CONSTANTS: c_subject LIKE sodocchgi1-obj_descr VALUE 'Subject',
*c_tab TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*DATA: g_time TYPE char8,
*g_email(40) TYPE c,
*g_sent_all(1) TYPE c,
*g_doc_data LIKE sodocchgi1,
*g_error TYPE sy-subrc.
*DATA: i_message LIKE solisti1 OCCURS 0 WITH HEADER LINE,
*i_packing_list LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
*i_receivers LIKE somlreci1 OCCURS 0 WITH HEADER LINE.
*DATA: BEGIN OF mailid OCCURS 0,
zemail_id TYPE zrule_id-zemail_id,
END OF mailid.
*data: mailid like zrule_id occurs 0 with header line.
UPLOADING FLAT FILE TO INTERNAL TABLE NCRF
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = 'C:\VAMSY\file.txt'
filetype = 'ASC'
has_field_separator = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
data_tab = ncrf[]
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
IF sy-subrc EQ 0.
Checking internal table ncrf is empty then
*delete records from TABLE ZNCRF_ID ******************************
IF ncrf[] IS INITIAL.
MESSAGE i003(ZMSG2).
ELSE.
DELETE FROM zncrfid.
ENDIF.
*****Values are read from rule table and checking owner and owner_value
*from zrule_id table and inserted into ZNCRFID **************
SELECT * FROM zrule_id INTO CORRESPONDING FIELDS OF TABLE it_ruleid
WHERE zrule_id IN ('OWNER1', 'OWNER2').
append IT_RULEID.
LOOP AT ncrf WHERE z9gl_sla_flag EQ 'Y'.
READ TABLE it_ruleid WITH KEY zowners = ncrf-zowners
zowners_value = ncrf-zowners_value.
IF ncrf-zowners = it_ruleid-zowners AND ncrf-zowners_value =
it_ruleid-zowners_value AND ncrf-z9gl_sla_flag ='Y'.
itab-zncrf_id = ncrf-zncrf_id.
itab-zncrf_l4_name = ncrf-zncrf_l4_name.
itab-z9gl_sla_flag = ncrf-z9gl_sla_flag.
itab-zdate_changed = sy-datum.
itab-ztime_changed = sy-uzeit.
itab-zowners = it_ruleid-zowners.
itab-zowners_value = it_ruleid-zowners_value.
APPEND itab.
ENDIF.
ENDLOOP.
modify database table zncrfid FROM ITAB
LOOP AT itab.
WRITE:/ itab-zncrf_id, itab-zncrf_l4_name, itab-z9gl_sla_flag,
itab-zowners, itab-zowners_value, itab-zdate_changed,
itab-ztime_changed.
zncrfid-zncrf_id = itab-zncrf_id.
zncrfid-zncrf_l4_name = itab-zncrf_l4_name.
zncrfid-z9gl_sla_flag = itab-z9gl_sla_flag.
zncrfid-zowners = itab-zowners.
zncrfid-zowners_value = itab-zowners_value.
zncrfid-zdate_changed = itab-zdate_changed.
zncrfid-ztime_changed = itab-ztime_changed.
INSERT INTO zncrfid VALUES zncrfid.
ENDLOOP.
ENDIF.
ENDIF.
*CALL FUNCTION 'DATE_TO_DAY'
EXPORTING
DATE = sy-datum
IMPORTING
WEEKDAY = file.
**CHECKING FOR THE FIRST MONDAY OF THE MONTH.
dates = sy-datum.
shift dates by 6 places left.
if file CO 'monday' and dates < 7 and dates >= 1.
else.
message e004(zmsg2).
endif.
EMAIL SEND TO OWNERS LIST
**Fill the mail body in i_message.
get email id's from database into internal table et_mailid
Fill the document data.
*g_doc_data-doc_size = 1.
Populate the subject/generic message attributes
*g_doc_data-obj_langu = sy-langu.
*g_doc_data-obj_name = 'SAPRPT'.
*g_doc_data-obj_descr = c_subject .
*g_doc_data-sensitivty = 'F'.
Describe the body of the message
Information about structure of data tables
*CLEAR i_packing_list.
*REFRESH i_packing_list.
*i_packing_list-transf_bin = space.
*i_packing_list-head_start = 1.
*i_packing_list-head_num = 0.
*i_packing_list-body_start = 1.
*DESCRIBE TABLE i_message LINES i_packing_list-body_num.
*i_packing_list-doc_type = 'RAW'.
*APPEND i_packing_list.
Add the recipients email address
*LOOP AT mailid.
*CLEAR i_receivers.
*i_receivers-receiver = mailid-zemail_id.
*i_receivers-rec_type = 'U'.
*i_receivers-com_type = 'INT'.
*i_receivers-notif_del = 'X'.
*i_receivers-notif_ndel = 'X'.
*APPEND i_receivers.
*ENDLOOP.
Call the FM to post the message to SAPMAIL
*CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
*EXPORTING
*document_data = g_doc_data
*put_in_outbox = 'X'
*commit_work = 'X'
*IMPORTING
*sent_to_all = g_sent_all
*TABLES
*packing_list = i_packing_list
*contents_txt = i_message
*receivers = i_receivers
*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.
Store function module return code
*g_error = sy-subrc.
Get i_receivers return code
*LOOP AT i_receivers.
*ENDLOOP.
**Instructs mail send program for SAPCONNECT to send email(rsconn01)
*WAIT UP TO 2 SECONDS.
*IF g_error EQ 0.
*SUBMIT zgbl_sla_per WITH mode = 'INT'
*WITH output = 'X'
*AND RETURN.
REWARD IF FOUND USEFULL,
Cheers,

Need HELP - Need to send MIME attachements, not UU-encoded.

Some important recipients are unable to view attachments I send them b/c Mail, by default, sends UU-encoded attachements instead of MIME attachements.
Is there any way to configure Mail to send MIME attachements?
FYI to any other people having problems SENDING attachements (this took a while to figure out):
Google, Yahoo, and some other mail services are not particularly UU-encoding friendly, and the recipients at those addresses sometimes receive a bunch of garbled 'code' or 'script' instead of the actual attachment file.
I've read lots on these discussions from people trying to deal with READING MIME attachements that other people have sent them, but cannot find any info on switching the SENT preferences to use UU encoding for attachments instead of MIME.
If anyone can clarify, PLEASE, PLEASE HELP.
I use .mac to sync my 2 Mac Pros, MB Pro, iPhone, and three Mac Minis, so I'd really like to keep everything 'in sync' with Apple apps. Otherwise I'll have to switch to Entou-rage or Mozilla, which I don't really want to do...
Thanks in advance for any insight or advice...
- Sarge

I've taken the liberty of re-arranging your question for clarification.
Sarge_ wrote:
Some important recipients are unable to view attachments I send them b/c Mail, by default, sends UU-encoded attachements instead of MIME attachements.
I've read lots on these discussions from people trying to deal with READING MIME attachements that other people have sent them, but cannot find any info on switching the SENT preferences to use UU encoding for attachments instead of MIME.
Which one do you want to use? UU or MIME?
I do not think that Apple Mail sends UU-encoded attachments. UU is really old.
There are two settings that can fundamentally change the way Apple Mail sends messages.
1) Plain text vs. Rich text. With plain text you can't change the fonts or colors or anything else. There is a slight possibility that this mode sends UU attachments, but I can't check from the PC in front of me. Still, I doubt it. Rich text allows fancy fonts and colors.
2) Send Windows-friendly attachments. This will prevent Apple Mail from sending Macintosh-specific information in an e-mail message. In all cases, Apple Mail only sends standards-forming MIME e-mail messages, but many (all?) PC e-mail clients barf on this 100%-legal MIME e-mail message.
Is there any way to configure Mail to send MIME attachements?
Make sure that Windows-friendly attachments is turned on. The only downside is that other Mac users might not get resource data or might have problems with files lacking extensions. No one should be using resource data or files without extensions anymore, so this question is moot. If you do need to do that, wrap your files in a ZIP.
Google, Yahoo, and some other mail services are not particularly UU-encoding friendly, and the recipients at those addresses sometimes receive a bunch of garbled 'code' or 'script' instead of the actual attachment file.
This may happen regardless of what you do.
If anyone can clarify, PLEASE, PLEASE HELP.
Here is a little write-up I did a few years back on this issue. According the the Apple discusssion regulations, I should say that I do sell a MIME-decoding tool through the link above. However, that tool will not help you send MIME e-mail messages. I'm not trying to sell you anything. These days, any decent e-mail client can handle either UU or MIME messages with no problem. There are a few notable exceptions to this, and unfortunately, those exceptions tend to have millions of customers. It is getting better though.

Can not open attachments or sometimes send attachments

Unable to opoen e-mail attachments and when sending an attachment receivers report unable to open.
long time for printer to sometimes start.

You mean company Adobe does not allow you to open attachments received on emails? Or is it a specific product you're using? Which one, which version (including minor), which platform/OS? Which mail client do you use? Is it Web-based (like gmail)? What is the exact manifestation of your problem? Are attachments that you're getting PDFs? Do you download them to your computer before you try to open them?

How to send an attached folder without compressing?

When using Mail 2.1.3 on 10.4.11 and sending more than one photo, I like to put them in a folder, so they get better organized. However, the application Mail will zip this folder on sending. Sometimes my recipients (on PC) have then difficulties opening this zipped folder. I don't want to tell them "you should install this and that application for unzipping".
In settings of Mail I find no checkbox for this- it does it by itself...
Is there any way to send an attached folder without compressing it, just plain?

Frederick,
thank you for the reply.
Maybe I did not explain clearly enough. Let's say I have ten JPEGs. I make a new folder in Finder, call it "Pictures" or so, put the JPEGs in it and then, after writing the mail, I click "attach" and select the newly generated folder so that it will be attached. In the outgoing window of the mail I see it then as the "Pictures" folder. The recipient then gets the mail with an attachment called "pictures.zip" that calls for an unzip application in order to take a look at those JPEGs.
Now the problem is, Mail app will automatically make a zip out of it. Yes, I have "Send PC-compatible" turned on. I use, b.t.w. plain text, not formatted. Some recipients have no problems with the zip, I know, but some do have.
I want Mail to send the folder without zipping it. Making it a little bit smaller in size is (indeed only a little bit!), in many cases, not necessary and, like I wrote, often only confusing (especially when the recipient PC asks "...this is a programme, do you want it to open?- Of course, most reasonable users are afraid of those messages!).
The point is, my application is doing something that I don't want and I find no way to tell it "please, no".

Cannot send email. When I click Write the window does not open properly. Does not have the "send, spelling, attach security save" line.

Cannot send email. When I click Write the window does not open properly. Does not have the "send, spelling, attach, security, save line there. Then when I click File, then Send now it will not send. A message comes up saying my SMTP server failed. Have check and everything appears to be o.k.

Hi Stephen,
What version of MS Office are you using?
Are you facing the issue similar to that mentioned here: Acrobat/Reader: Attach to Email button not working for PDFs referenced from long URLs
Open Acrobat. Use the click-path Edit - Preferences - select the Category "Email Accounts". In the dialog there is the "Add Account" drop-down. Select "Add Other". The "Add Webmail Account" dialog presents. You'll fill out the dialog's fields with Outlook.com settings. (don't forget the "Advance Settings" button)
From a look-see on the web it appears that the following are the needed settings. BUT, you'll be wanting to validate.
The Outlook.com SMTP server settings for sending outgoing messages from an email program on desktop, cell phone or mobile device are:
• Outlook.com SMTP server address: smtp.live.com
• Outlook.com SMTP user name: Your full Outlook.com email address (not an alias)
• Outlook.com SMTP password': Your Outlook.com password
• Outlook.com SMTP port: 587
• Outlook.com SMTP TLS/SSL encryption required: yes
For incoming messages from an Outlook.com account to an email program using POP, use the Windows Live Hotmail POP3 server settings.
The Outlook.com POP server settings for downloading new incoming messages to email program, cell phone or mobile device are:
• Outlook.com POP server address: pop3.live.com
• Outlook.com POP user name: Your full Outlook.com email address (not an alias)
• Outlook.com POP password: Your Outlook.com password
• Outlook.com POP port: 995
• Outlook.com POP TLS/SSL encryption required: yes
Regards,
Rave

Send excel attachment using FM SO_NEW_DOCUMENT_ATT_SEND_API1

Hi ABAPers,
I managed to send excel attachment using FM SO_NEW_DOCUMENT_ATT_SEND_API1.
Let say I send it to my own email account.
But, when try to open the excel document, from lotus notes, there is warning message produced by the microsoft excel saying:
"The file is not in a recognizable format.
and so on....."
Anyway, when I click button 'OK', excel sheet will be opened and no information lost.
How can we code the abap program so that the message will not come each time I open the attachment from my lotus notes?
Or this is just the tab delimited issue?
Thank you.
Regards,
Edward.

Hi Shan,
Thank you for replying.
I have the same as follows:
DESCRIBE TABLE lt_contents_hex LINES lv_lines.
lt_packing_list-transf_bin = 'X'.
lt_packing_list-head_start = 1.
lt_packing_list-head_num   = 1.
lt_packing_list-body_start = 1.
lt_packing_list-body_num   = lv_lines.
lt_packing_list-doc_type   = 'XLS'.
lt_packing_list-obj_name   = 'ATTACHMENT'.
lt_packing_list-obj_descr = 'Attachment'.
lt_packing_list-doc_size   = lv_lines * 255.
APPEND lt_packing_list.
I'm using lt_contents_hex instead of lt_contents_bin.
Still the problem is there.
Is there any other way to calculate the doc size correctly?
Regards,
Edward.

Using SO_NEW_DOCUMENT_ATT_SEND_API1 to send .xls attachment.

Hi,
I'm using the FM SO_NEW_DOCUMENT_ATT_SEND_API1 to send xls attachements.
All works fine, the only issue is that in the requirements the attachemnt should have fixed width columns.
I think that is not possible, everyone have done that?
If not there an alternative to the SO_NEW_DOCUMENT_ATT_SEND_API1?
Thanks for answers.

Hello,
You can have the fixed width of the colums in excel (No additional spaces in the column) is you use, the seperator between the fields.
For eg : If you are displaying 3 fields in the excel file, say MATNR, WERKS and QUANTITY.
Then you need to
Concatenate matnr
                      werks
                      quantity
into                ls_contents_bin-line
separated by lc_tab.
append ls_contents_bin to lt_contents_bin.
Here lc_tab is the tab seperator to be declared as follows : -
CONSTANTS : lc_tab         TYPE char01     VALUE cl_abap_char_utilities=>horizontal_tab.
The internal table lt_contents_bin is then passed to the table parameters contents_bin of the FM SO_NEW_DOCUMENT_ATT_SEND_API1.
Thanks.
Regards,
Rinkesh Doshi

Error when trying to send an attachment

Hi there,
I am running an application in Tomcat 5.5 and I am trying to send an email with an attachment via java mail. The attachment will eventually be a zip file containing wav files but I can't seem to get it to work with a text file yet.
I may be a little confused...I am especially confused with the DataHandlerSet stuff.
Here is the code:
public String sendmail(String msgSubject)
     //Sets some variables.
    String emailmultipart = "true"; //if this is set to false sends a simple message.
    String msgText = "Some text \n\n";
    String smtphost = "myhost";
    String emailto = "[email protected]";
    String emailfrom = "[email protected]";
    //Gives the path of where the sound files are.
    File soundfile = new File("myfile.txt");
    boolean debug = true; // change to get more information
    String msgText2 = "multipart message";
    boolean sendmultipart = Boolean.valueOf(emailmultipart).booleanValue();
     // set the host
    Properties props = new Properties();
    props.put("mail.smtp.host", smtphost);
      // create some properties and get the default Session
    Session session = Session.getDefaultInstance(props, null);
    session.setDebug(debug);
    try
          // create a message
           Message msg = new MimeMessage(session);
           // set the from address
           InternetAddress from = new InternetAddress(emailfrom);
           msg.setFrom(from);
           //set the to address
           InternetAddress[] address =
               new InternetAddress(emailto)
           msg.setRecipients(Message.RecipientType.TO, address);
           //set subject - support request id
           msg.setSubject(msgSubject);
          //decides whether to send plain text message or multi text message (from true/false in the command line)
          //sends a simple plain text email
          if(!sendmultipart)
             // send a plain text message
             msg.setContent(soundfile, "text/plain");
          //sends an attached file.
          else
             // send a multipart message// create and fill the first message part
             MimeBodyPart mbp1 = new MimeBodyPart();
             //adds the text as normal
             mbp1.setContent(msgText, "text/plain");
             // create and fill the second message part
            MimeBodyPart mbp3 = new MimeBodyPart();
            // attach the file to the message
              //FileDataSource fds = new FileDataSource(filen);
              FileDataSource fds = new FileDataSource(soundfile);
             mbp3.setDataHandler(new DataHandler(fds));
             mbp3.setFileName(fds.getName());
//             mbp3.setContent();
            Multipart mp = new MimeMultipart();
            //adds the text to the message
            mp.addBodyPart(mbp1);
              //adds the attachment to the message
              mp.addBodyPart(mbp3);
            // adds the content to the message
            msg.setContent(mp);
         //Transport - sends the message.
         Transport.send(msg);
    catch(MessagingException mex)
      mex.printStackTrace();
    //log.debug("At end of Send email");
    return "nothing";
}Here is the error:
javax.mail.MessagingException: IOException while sending message;
nested exception is:
     java.io.IOException: "text/html" DataContentHandler requires String object, was given object of type class javax.mail.internet.MimeMultipart
     at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:566)
     at javax.mail.Transport.send0(Transport.java:151)
     at javax.mail.Transport.send(Transport.java:80)
     at questionnaireweb.Formemail.sendmail(Formemail.java:337)
     at org.apache.jsp.web.emailrecorded_jsp._jspService(org.apache.jsp.web.emailrecorded_jsp:338)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:731)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
I'd be really grateful for any help. I can't seem to get past this error not matter what I try. Sending the simple mail works, but sending an attachment produces the error above. I have seen similar errors before but when the user actually wants to send html and not a file.
Thanks a lot,
Jess

HI ,Thanks for your response. That was an error in the code I posted, but wasn't the error I was trying to solve. Once correcting that error you pointed out I am getting the problems not when I send a plain text email like:
          if(!sendmultipart)
             // send a plain text message
             msg.setContent(msgText, "text/plain");
          }but when I try and send multipart messages doing this:
          else
             // send a multipart message// create and fill the first message part
                   MimeBodyPart mbp1 = new MimeBodyPart();
     mbp1.setText(msgText);
      // create and fill the second message part
     MimeBodyPart mbp3 = new MimeBodyPart();
     // attach the file to the message
     FileDataSource fds = new FileDataSource(soundfile);
     mbp3.setDataHandler(new DataHandler(fds));
     mbp3.setFileName(fds.getName());
                   Multipart mp = new MimeMultipart();
     //adds the text to the message
      mp.addBodyPart(mbp1);
      //adds the attachment to the message
      mp.addBodyPart(mbp3);
       // adds the content to the message
      msg.setContent(mp);
     }So i get the error when executing the else branch.
Can you spot any errors here? I get the same error as mentioned earlier.
Thanks a lot,
Jess

MS Project 2010 with Outlook 2013 - "send as attachment" missing function / not working

Office 2013 Professional running on Windows 7 (64bit).
After Re-installing MS Project 2010 today the option under
File (alt-f) --> 'Save & Send' --> 'Send as Attachment' is shaded out / unavailable.
Is this a known integration gap between the older MS Project and Current Outlook ? Alternatively, does anyone have any recommendations to troubleshoot and / or enable the function within MS Project 2010?
Thanks for any suggestions , guidance or pointers.
p.s I have tried completing a repair on Office 2013 and the MS Project 2010 from within the control panel.
This functionality is working with all other Office 2013 applications in the suite (Excel, PowerPoint, Word, Visio etc.)

Julie ,
Kinda / sorta ... In Mid 2014 I had MS Project installed and working (I can't confirm if the Send as Attachment was working at that time...) A few days ago I was sent an '.mpp' (MS Project file) for review. When I attempted to open it MS Project
gave me a warning message that it needed to start in safe mode but then failed to start. This seemed weird and thus began two days of googling and investigation.
I elected to uninstall (which also failed) and reinstall (which also failed) the MS Project 2010 since I have the media at hand to do so. At this point I was really truly 'stuck' (p.c term for the younger audience reading this).
My course of action was to engage Microsoft Support (specifically the MS Office group). They verified some registry entries, confirmed installation of MS Project 2010 , confirmed files were installed , available and in the appropriate
spots (files etc.) , tried a few 'fixit' tools , made multiple suggestions that I spend $1000+ on upgrading to MS Project 2013. After ~90 minutes or so they were able to 'Force' the orphaned installation to uninstall. (although
they needed to install and use a 3rd party tool to do it) We then re-installed MS Project 2010 and verified it could start.
After using project a little bit I realized that 'Send as Attachment' option was non-functional. I spent a few hours trying to research (more google) and finally threw in the towel and cried out for help (i.e posted the message that started this
thread).
Thanks again for any suggestions or wisdom you are willing to share.

Since installing 8.0.1 I cannot send an attachment in AOL mail when I could with previous versions.

When I try to send an attachment in AOL mail I get an error message "We encountered a technical issue, please try again."
This happens every time over the past few days.

Never mind the above message....I uninstalled Firefox 4.0.1 and reinstalled 3.6 and then updated to 3.6.7. Now I've lost all my Bookmarks. This is really getting to be frustrating and ridiculously hard to find answers!! What's up with the brains behind Mozilla?? Are they all hacked??

Is it possible to send xls attach in mail in background ?

is it possible to send xls attach in mail in background ?
i build/copy program to send attach file in xls format ,
its work fine in foreground but do nothing in background ,
What can be the reason?
the section of the sending :
DATA: LD_ERROR    TYPE SY-SUBRC,
        LD_RECIEVER TYPE SY-SUBRC,
        LD_MTITLE LIKE SODOCCHGI1-OBJ_DESCR,
        LD_EMAIL LIKE SOMLRECI1-RECEIVER,
        LD_FORMAT TYPE SO_OBJ_TP ,
        LD_ATTDESCRIPTION TYPE SO_OBJ_NAM ,
        LD_ATTFILENAME TYPE SO_OBJ_DES ,
        LD_SENDER_ADDRESS LIKE SOEXTRECI1-RECEIVER,
        LD_SENDER_ADDRESS_TYPE LIKE SOEXTRECI1-ADR_TYP,
        LD_RECEIVER LIKE SY-SUBRC.
LD_EMAIL   = P_EMAIL.
LD_MTITLE = P_MTITLE.
LD_FORMAT              = P_FORMAT.
LD_ATTDESCRIPTION      = P_ATTDESCRIPTION.
LD_ATTFILENAME         = P_FILENAME.
LD_SENDER_ADDRESS      = P_SENDER_ADDRESS.
LD_SENDER_ADDRESS_TYPE = P_SENDER_ADDRES_TYPE.
Fill the document data.
W_DOC_DATA-DOC_SIZE = 1.
Populate the subject/generic message attributes
W_DOC_DATA-OBJ_LANGU = SY-LANGU.
W_DOC_DATA-OBJ_NAME = 'SAPRPT'.
W_DOC_DATA-OBJ_DESCR = LD_MTITLE .
W_DOC_DATA-SENSITIVTY = 'F'.
Fill the document data and get size of attachment
CLEAR W_DOC_DATA.
READ TABLE IT_ATTACH INDEX W_CNT.
W_DOC_DATA-DOC_SIZE =
     ( W_CNT - 1 ) * 255 + STRLEN( IT_ATTACH ).
W_DOC_DATA-OBJ_LANGU = SY-LANGU.
W_DOC_DATA-OBJ_NAME   = 'SAPRPT'.
W_DOC_DATA-OBJ_DESCR = LD_MTITLE.
W_DOC_DATA-SENSITIVTY = 'F'.
CLEAR T_ATTACHMENT.
REFRESH T_ATTACHMENT.
T_ATTACHMENT[] = PIT_ATTACH[].
Describe the body of the message
CLEAR T_PACKING_LIST.
REFRESH T_PACKING_LIST.
T_PACKING_LIST-TRANSF_BIN = SPACE.
T_PACKING_LIST-HEAD_START = 1.
T_PACKING_LIST-HEAD_NUM = 0.
T_PACKING_LIST-BODY_START = 1.
DESCRIBE TABLE IT_MESSAGE LINES T_PACKING_LIST-BODY_NUM.
T_PACKING_LIST-DOC_TYPE = 'RAW'.
APPEND T_PACKING_LIST.
Create attachment notification
T_PACKING_LIST-TRANSF_BIN = 'X'.
T_PACKING_LIST-HEAD_START = 1.
T_PACKING_LIST-HEAD_NUM   = 1.
T_PACKING_LIST-BODY_START = 1.
DESCRIBE TABLE T_ATTACHMENT LINES T_PACKING_LIST-BODY_NUM.
T_PACKING_LIST-DOC_TYPE   = LD_FORMAT.
T_PACKING_LIST-OBJ_DESCR = LD_ATTDESCRIPTION.
T_PACKING_LIST-OBJ_NAME   = LD_ATTFILENAME.
T_PACKING_LIST-DOC_SIZE   = T_PACKING_LIST-BODY_NUM * 255.
APPEND T_PACKING_LIST.
Add the recipients email address
CLEAR T_RECEIVERS.
REFRESH T_RECEIVERS.
T_RECEIVERS-RECEIVER = LD_EMAIL.
T_RECEIVERS-REC_TYPE = 'U'.
T_RECEIVERS-COM_TYPE = 'INT'.
T_RECEIVERS-NOTIF_DEL = 'X'.
T_RECEIVERS-NOTIF_NDEL = 'X'.
APPEND T_RECEIVERS.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
    EXPORTING
      DOCUMENT_DATA              = W_DOC_DATA
      PUT_IN_OUTBOX              = 'X'
      SENDER_ADDRESS             = LD_SENDER_ADDRESS
      SENDER_ADDRESS_TYPE        = LD_SENDER_ADDRESS_TYPE
      COMMIT_WORK                = 'X'
    IMPORTING
      SENT_TO_ALL                = W_SENT_ALL
    TABLES
      PACKING_LIST               = T_PACKING_LIST
      CONTENTS_BIN               = T_ATTACHMENT
      CONTENTS_TXT               = IT_MESSAGE
      RECEIVERS                  = T_RECEIVERS
    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.
Populate zerror return code
LD_ERROR = SY-SUBRC.
Populate zreceiver return code
LOOP AT T_RECEIVERS.
    LD_RECEIVER = T_RECEIVERS-RETRN_CODE.
ENDLOOP.

Try this example, not sure where I got this, but it works.
report zmail_excel.
parameters: p_email   type somlreci1-receiver
                               default '[email protected]'.
data: begin of it001 occurs 0,
      bukrs type t001-bukrs,
      butxt type t001-butxt,
      end of it001.
data:   imessage type standard table of solisti1 with header line,
        iattach type standard table of solisti1 with header line,
        ipacking_list like sopcklsti1 occurs 0 with header line,
        ireceivers like somlreci1 occurs 0 with header line,
        iattachment like solisti1 occurs 0 with header line.
start-of-selection.
select bukrs butxt into table it001 from t001.
*   Populate table with detaisl to be entered into .xls file
perform build_xls_data .
* Populate message body text
clear imessage.   refresh imessage.
imessage = 'Please find attached excel file'.
append imessage.
* Send file by email as .xls speadsheet
perform send_email_with_xls tables imessage
                                      iattach
                                using p_email
                                      'Example Excel Attachment'
                                      'XLS'
                                      'TestFileName'
                                      'CompanyCodes'.
*      Form BUILD_XLS_DATA
form build_xls_data .
constants: con_cret type x value '0D', "OK for non Unicode
             con_tab type x value '09'.   "OK for non Unicode
*If you have Unicode check active in program attributes thnen you will
*need to declare constants as follows
*class cl_abap_char_utilities definition load.
*constants:
*    con_tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB,
*    con_cret type c value cl_abap_char_utilities=>CR_LF.
concatenate 'BUKRS' 'BUTXT'
         into iattach separated by con_tab.
concatenate con_cret iattach into iattach.
append iattach.
loop at it001.
    concatenate it001-bukrs it001-butxt
           into iattach separated by con_tab.
    concatenate con_cret iattach into iattach.
    append iattach.
endloop.
endform.
*      Form SEND_EMAIL_WITH_XLS
form send_email_with_xls tables pit_message
                                          pit_attach
                                    using p_email
                                          p_mtitle
                                          p_format
                                          p_filename
                                          p_attdescription.
data: xdocdata like sodocchgi1,
        xcnt type i.
* Fill the document data.
xdocdata-doc_size = 1.
* Populate the subject/generic message attributes
xdocdata-obj_langu = sy-langu.
xdocdata-obj_name = 'SAPRPT'.
xdocdata-obj_descr = p_mtitle .
* Fill the document data and get size of attachment
clear xdocdata.
read table iattach index xcnt.
xdocdata-doc_size =
     ( xcnt - 1 ) * 255 + strlen( iattach ).
xdocdata-obj_langu = sy-langu.
xdocdata-obj_name   = 'SAPRPT'.
xdocdata-obj_descr = p_mtitle.
clear iattachment. refresh iattachment.
iattachment[] = pit_attach[].
* Describe the body of the message
clear ipacking_list. refresh ipacking_list.
ipacking_list-transf_bin = space.
ipacking_list-head_start = 1.
ipacking_list-head_num = 0.
ipacking_list-body_start = 1.
describe table imessage lines ipacking_list-body_num.
ipacking_list-doc_type = 'RAW'.
append ipacking_list.
* Create attachment notification
ipacking_list-transf_bin = 'X'.
ipacking_list-head_start = 1.
ipacking_list-head_num   = 1.
ipacking_list-body_start = 1.
describe table iattachment lines ipacking_list-body_num.
ipacking_list-doc_type   = p_format.
ipacking_list-obj_descr = p_attdescription.
ipacking_list-obj_name   = p_filename.
ipacking_list-doc_size   = ipacking_list-body_num * 255.
append ipacking_list.
* Add the recipients email address
clear ireceivers. refresh ireceivers.
ireceivers-receiver = p_email.
ireceivers-rec_type = 'U'.
ireceivers-com_type = 'INT'.
ireceivers-notif_del = 'X'.
ireceivers-notif_ndel = 'X'.
append ireceivers.
call function 'SO_DOCUMENT_SEND_API1'
       exporting
            document_data              = xdocdata
            put_in_outbox              = 'X'
            commit_work                = 'X'
       tables
            packing_list               = ipacking_list
            contents_bin               = iattachment
            contents_txt               = imessage
            receivers                  = ireceivers
       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.
endform.
Regards,
Rich Heilman

Problem to send out attachment

Hi all,
This is urgent. Any advice is appreciated. I have java class to send out attachement. The program was working fine without any issues until last Friday. Suddenly, it could not send any attachment email out. I was able to send out a simple email without attachment. I did not know what changed. I ran out of resources for troubleshooting it.
Here is my code:
import java.util.Properties;
import javax.mail.*;
import javax.mail.internet.*;
import javax.activation.*;
public class SendAttachment {
public void Send (String MailHost, String AddFrom, String AddTo, String FileAttName)
throws Exception {
String host = MailHost;
String from = AddFrom;
String to = AddTo;
String fileAttachment = FileAttName;
// Get system properties
Properties props = System.getProperties();
// Setup mail server
props.put("mail.smtp.host", host);
// Get session
Session session =
Session.getInstance(props, null);
// Define message
Message message =
new MimeMessage(session);
message.setFrom(
new InternetAddress(from));
message.addRecipient(
Message.RecipientType.TO,
new InternetAddress(to));
message.setSubject(
"Hello JavaMail Attachment");
// create the message part
BodyPart messageBodyPart =
new MimeBodyPart();
//fill message
messageBodyPart.setText("Hi");
Multipart multipart = new MimeMultipart();
multipart.addBodyPart(messageBodyPart);
// Part two is attachment
messageBodyPart = new MimeBodyPart();
DataSource source =
new FileDataSource(fileAttachment);
messageBodyPart.setDataHandler(
new DataHandler(source));
messageBodyPart.setFileName(fileAttachment);
multipart.addBodyPart(messageBodyPart);
// Put parts in message
message.setContent(multipart);
// Send the message
Transport.send( message );
my test program:
import java.io.File;
import java.io.IOException;
import java.io.OutputStream;
public class TestJavaMail {
public static void main(String[] args) {
String myhost =args[0];
String from =args[1];
String to = args[2];
String filename = args[3];
try {
System.out.println("Start .....");
System.out.println("Preparing...");
SendAttachment app = new SendAttachment();
app.Send(myhost, from, to, filename);
System.out.println("Success!");
} catch (Exception e) {
//System.err.println(ExceptionUtil.printStackTrace(e));
System.exit(-1);
After successful compilation, here is how I ran the class:
java TestJavaMail mymaihost.com [email protected] [email protected] /tmp/test.txt
It stops just before it calls Transport.send( message );
Any ideas are greatly appreciated.

Hello,
This could help you.
http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010
if the reply help you mark it as your answer.
Free Managed .NET
Word Component(Create, Modify, Convert & Print)

Mail:send mail:attachment. Is there a simplest way to send a file as an email attachment ? or more correct ?

<satellite:form method="post" id="contact-form" enctype="multipart/form-data">
     <input type="file" name="adjunto" />
</satellite:form>
FTValList ftListaFichero = new FTValList(1);
ftListaFichero.setValBLOB(ics.GetVar("adjunto_file"), ics.GetBin("adjunto"));
<mail:send
       to="<%=to_emailaddress %>"
       from="<%=from_emailaddress%>"
       subject="Subject"
       body="<%=body %>" >
    <mail:attachment value='<%=ftListaFichero.getVal(ics.GetVar("adjunto_file"))%>'/>
</mail:send>
http://docs.oracle.com/cd/E29542_01/apirefs.1111/e39371/JSP/mail-attachment.html
http://docs.oracle.com/cd/E29542_01/apirefs.1111/e39371/JSP/mail-send.html
Regards,

Simplest might well be to use javamail API instead of the two tags that Sites provides, e.g. see email - Sending mail attachment using Java - Stack Overflow for a full example.
Phil

T.37 onramp fax sometimes sends empty attachment

Similar Messages

Maybe you are looking for