Empty Attachment after sending with JAVAMAIL

Hey!
In my stand-alone-application works like a observer and i have the following problem:
I send a zipfile that contains a xsl-document. I also us the AES256 encryption for the Zip-File.
So my apllication send a mail depending on the database-tables.
After getting the mails:
First run
The first one contains the xls-document but the content is not right (some hex codes)
Second run
Zip-file is empty
Third run
Correct
Fourth run
Zip-file is empty.
Further Information:
After Transport.send(msg); i rename the attachment-files in my java-code automatically
Please help me?

Sorry, I'm not understanding what you're doing.
On the mail sending side, does the file exist? Is the file content present in the message
you send?
I'm sure you understand that file names sent by the sender have no meaning to the recipient.
You need to send the file contents. Normally, attaching a file to a message will send the
contents, and will send the name in case the recipient wants to save the file under the same
name.
If you're properly attaching the file to the message, and you're not getting the file contents
included in the message when you send it, you're doing something wrong on the sending
side.
JavaMail comes with demo programs that show how to attach a file. Try to get the
sendfile.java demo program to work for you first. If that doesn't work, provide more
details of what you're doing, including a protocol trace.

Similar Messages

  • PCA AR/AP transfer with 1KEK after sending with 3KEH

    My company for some reason has the AR and AP accounts set up to post realtime to PCA, being set within 3KEH.  This obviously creates high volumes of data with the preferred method being running 1KEK to load the open items at month end.  Has anyone coverted from the 'wrong' way to the 'right' way.  Is it as simple as removing the entries from 3KEH at the the beginning of a fiscal month then begin running 1KEK at month end?

    Yes 1230 AP supports WPA2.
    ***Most of those older APs don't have the hardware to support WPA2. It's not the software but the hardware/radios.
    Just try to configure WPA2 under :
    dot11 ssid xyz
    vlan xx
    authentication key-management wpa version 2
    Regards

  • Mail will not quit after sending message with attachment

    B&W G3-450
    OSX 10.2.8
    640 MB RAM
    I recently switched to using an email account through AOL Instant Messenger (AIM.com). The only way to connect to their service is via IMAP. I have all the correct settings, I can send and receive email no problem.
    However, when I attempt to send a message that contains an attachment (.zip, jpeg, anything) the email will send just find. The problem is when I try to quit mail it wont' respond. I can continue to send or receive after sending the message but it will not quit. Trying to log out does not work either as it reports a problem with Mail that prevents closing the session. The only thing I can do is force quit mail.
    The next time I use mail it works fine and there are no problems. The only issue seems to be this hanging problem. I've never experienced this problem using POP3 accounts.
    Any suggestions?
    B&W G3-450   Mac OS X (10.2.x)  

    Does anyone have a suggestion here?

  • Send message windows doesn't close after sending attached PDF from Acrobat

    I have several forms that I have created in Acrobat 9 Pro. These forms have a button set to submit to an email address. After filling out the form, and clicking on the submit button some, but not all, of users with Outlook 2007 are having a problem with the send message window not closing after sending the email.
    When they click the button the email is created with the form as an attachment. When they click the send button in the send message window the message goes into the outbox, and then gets sent no problems. But the send message window never closes after sending the message. So my users think the message never got sent.
    The computers that I am seeing this on all run XP, have Outlook 2007, and use Acrobat Standard 8. On some computers it works just fine, and on others it has the problem. It must be a setting somewhere but I can not figure it out.
    Closing the window by clicking on the "X" is no problem, but many of my users are pretty new to computers know very little about them. So something like this causes them a lot of problems.
    Any suggestions?
    Trudy

    My apologies, when I said "instance" I meant window.
    I also just realized the new window and then closing behavior only happens when the iTunes link clicked is in an email in Mail (presumably, this would also happen in other desktop email clients). When an iTunes link in Safari is clicked, the "iTunes loading" white page appears for a moment and then Safari navigates back to the page with the link. However, that isn't working properly, either. The white page continues to "load" indefinitely and never returns to the previous page.
    Here is a link:
    http://www.imogenheap.com/buy/

  • 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.

  • Sending chinese HTML with javamail - is there no definitive answer ?

    I'm using the following code to send a HTML and text e-mail
    (text for people with HTML-challenged email clients). I sent
    2 emails to 2 email addresses which reside on the same server
    - eg. [email protected] and [email protected] - and read the
    emails with the same e-mail client (Eudora) on the same PC.
    The HTML and Chinese displays perfectly when it's sent to one
    of the email addresses ([email protected]) but the HTML and
    Chinese are always corrupt when I send them to the other.
    This is a repeatable error and it has me completely stumped.
         // Example Initial values (drawn from a database) :
         String smtpHost = "mail.mydomain.com";
         String sender = "[email protected]";
         String subject = "Give me strength.... ";
         InternetAddress sender = new InternetAddress("[email protected]");
         InternetAddress receiver = new InternetAddress("[email protected]");
         String txtMsg = "a long text message blah...";
         String htmlMsg = "<h1>Wooo</h1><img src='http://mydomain.com/blink.gif'>";
         String language = "zh-tw" // can also be "en-us" or "zh-cn"
         // CREATE MAIL MESSAGE & HEADERS
         Properties props = System.getProperties();
         props.put("mail.smtp.host", smtpHost);
         Session session = Session.getDefaultInstance(props, null);
         Message msg = new MimeMessage(session);
         msg.setFrom(sender);
         msg.addRecipient(Message.RecipientType.TO, receiver);
         msg.setSubject(subject);
         msg.setSentDate(new Date());
         msg.setHeader("Mime-Version" , "1.0" );
         msg.setHeader("Content-Transfer-Encoding", "quoted-printable");
         // MESSAGE BODY - TEXT & HTML
         MimeMultipart mimeAllContent = new MimeMultipart("alternative");
         MimeBodyPart mimeText = new MimeBodyPart();
         MimeBodyPart mimeHtml = new MimeBodyPart();
         mimeText.setText(textMsg);
         mimeText.setHeader("Mime-Version" , "1.0" );
         mimeText.setHeader("Content-Type" , "text/plain");
         mimeText.addHeader("Content-Type", "charset=UTF-8");
         if (!language.equals("")) {
              mimeText.setHeader("Content-Language", language);
         mimeText.setHeader("Content-Transfer-Encoding", "quoted-printable");
         mimeHtml.setContent(htmlMsg, "text/html");
         mimeHtml.setHeader("Mime-Version" , "1.0" );
         mimeHtml.setHeader("Content-Type" , "text/html");
         mimeHtml.addHeader("Content-Type", "charset=UTF-8");
         if (!language.equals("")) {
              mimeHtml.setHeader("Content-Language", language);
         mimeHtml.setHeader("Content-Transfer-Encoding", "quoted-printable");
         mimeAllContent.addBodyPart(mimeText);
         mimeAllContent.addBodyPart(mimeHtml);
         msg.setContent(mimeAllContent);
         msg.setHeader("Content-Type" , mimeAllContent.getContentType());
         // SEND THE MESSAGE
         msg.saveChanges();
         Transport.send(msg);
         return true;
    Let me repeat - Using the code below, a HTML & Text ("Alternative"
    MimeMultiPart) message is sent, and arrives at the recipient's
    mailbox. When it is sent to one user ([email protected]), it never
    renders properly. When it is sent to another ([email protected]), it's
    OK. The destination server, email client, PC are the same in both
    cases and the only variable is the recipient's email address.
    How can this be ?
    I think I've gone overboard by setting the Content-Transfer-Encoding
    for both the HTML and Text MimeParts as well as the actual Message.
    Could somebody please confirm which parts I should set the Content-
    -Language, Content-Transfer-Encoding and Content-Type b/c I'm
    going in circles at the moment.
    Thanks indeed, to anybody who has experience sending doublebyte
    with Javamail and can help me clear this up once and for all.
    I find it incredible that after 3 years, there is still no
    definitive answer to accomplishing this, and it remains an
    elusive black art.
    Regards,
    chas
    ps. The data being sent is in MySQL not that that matters at all.

    Try adding code to validate submitted email addresses before they go into your database.
    String emailAddress = (from where ever)
    if(emailAddress != null) emailAddress = emailAddress.trim();
    if(emailAddress == null) // skip this address
    // I also check for a list of illegal internet email address characters, as I think the email addresses allowed by Javamail are too lenient.

  • Send an attachment in email with length more than 255 char per line

    Hi All,
    I have to send an attachment in email with length more than 255 char per line. I dont want to break the line after 255 char and add it in another line.
    Please suggest me any function module which can perform this.
    Thank you all.

    I looked at all threads in the forum, there was about 5 or 6 identical questions, but surprise, nobody knows! It seems that SO_NEW_DOCUMENT_ATT_SEND_API1 function module does not allow more than 255 characters by line.
    It would surprise me a lot if there is no workaround !
    As it is very easy to add any binary attachment which is like a very long line, PDF for example (several kilobytes), via the function module above (lots of examples in the forum), I would advise you to try to use the same way, i.e. use the contents_bin parameter instead of the contents_txt parameter (convert the text into binary) and add the line feeds yourself (okay I know, it's not very smart).
    Last thing, this function module is deprecated, and we should use BCS classes, maybe they work better.

  • How to send "Blob" in mail Attacthemnt with Javamail

    Hi,
    I need send a mail with attach file that is stored in bd. The column is a BLOB (any file) , and i need send directly with JavaMail..
    Any idea or sample???
    Thanks

    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:255615160805

  • Using Firefox 4 & Windows 7. Everytime I start Firefox from a shortcut to a website it comes up with the following error 'there was a problem sending the command to the program'. The requested website does load after this. with no problems.

    Using Firefox 4 & Windows 7. Everytime I start Firefox from a shortcut to a website it comes up with the following error 'there was a problem sending the command to the program'. The requested website does load after this. with no problems.
    If a shortcut is used while Firefox is already open the error does not occur.

    As reported in earlier replies, the annoyance disappeared after I upgraded to Roboform 7.5.6, from 7.5.4.
    Regards, Steve

  • Anyone having problem with iphone getting not delivered message after sending picture and it really is getting delivered to recipient.

    Anyone having problem with iphone getting a not delivered message after sending pic and it really is getting delivered to recipient.

    Same problem here with and I've done everything shy of a total reset which I also find unacceptable. This problem exists on all iMessage platforms (iPhone, iPad, and Mac) so I don't see how restoring my iPhone would help the problem.

  • SOAP Axis sender with CSV file attachment

    Hi Experts,
    I have a requirement where I receive a CSV file attachment from a Web Service post ( i.e a SOAP sender with attachment). I decided to use SOAP with Servlet(Axis) protocol, since standard SOAP sender does not allow modules to be used.
    I am able to test this interface through SOAPUI with attachment to the point where I can get the attachment payload as my main payload in IE, but it fails in mapping since CSV needs to be converted to XML. I have following queries for proceeding ahead with this scenario:
    1. How do I convert the CSV attachment to XML inorder for mapping to be used in IE. Is there a standard axis handler available for this ???? Also where should this handler be called in the sequence of Axis modules ???
    2. Can I use MessageTransformationBean for converting plain to XML ??? If yes where should this module be called in the sequence of Axis modules. I tried using this module between the CallSapAdapter and the first AdapterBean but it returns exception in SOAPUI saying " Messaging exception: No Main"
    3. Is there a blog available which illustrates about using additional modules/handlers in Axis. I have had a look at the FAQ note of Axis but it just gives the overview.
    Thanks.
    Siddhesh S.Tawate

    Solved :).
    1     AF_Adapters/axis/HandlerBean                     Local Enterprise Bean                              xireq
    2     AF_Adapters/axis/AFAdapterBean                     Local Enterprise Bean                              afreq
    3     localejbs/AF_Modules/MessageTransformBean    Local Enterprise Bean                     Plain2XML
    4     CallSapAdapter                                          Local Enterprise Bean                              sap
    5     AF_Adapters/axis/AFAdapterBean                    Local Enterprise Bean                             afresp
    6     AF_Adapters/axis/HandlerBean                    Local Enterprise Bean                             xires
    Above sequence worked. I guess I was missing some parameter in content conversion earlier.
    Thanks.

  • How to send a message with javamail api

    Hi, anybody can tell me how i do to send a message with javamail?
    Thanks.
    Daniele.

    [rossifumi80],
    Here's a simple JavaMail application SendMessage.java that will connect a SMTP host and send a mail message out:
    import java.util.Properties;
    import javax.mail.*;
    import javax.mail.internet.*;
    public class SendMessage {
      public static void main (String args[]) throws Exception {
        String host = args[0];
        String from = args[1];
        String to = args[2];
        // Get system properties
        Properties props = System.getProperties();
        // Setup mail server
        props.put("mail.smtp.host", host);
        // Get session
        Session session = Session.getDefaultInstance(props, null);
        // Define message
        MimeMessage message = new MimeMessage(session);
        // Set the from address
        message.setFrom(new InternetAddress(from));
        // Set the to address
        message.addRecipient(Message.RecipientType.TO,
          new InternetAddress(to));
        // Set the subject
        message.setSubject("Hello JavaMail");
        // Set the content
        message.setText("Welcome to JavaMail");
        // Send message
        Transport.send(message);
    }HTH.
    Allen Lai
    Developer Technical Support
    SUN Microsystems
    http://www.sun.com/developers/support/

  • Mail Sending- with Unicode enabled text in the attachment

    hi,
    i have a specific requirement for JAPAN country. its as follows:
    i am retrieving delivery details into my program & i need to send them as in a mail attachment(as CSV file) to particular mail id.
    for sending mail, i am using the function module "SO_NEW_DOCUMENT_ATT_SEND_API1".
    here is my problem :
    as this program will be used by JAPAN people, some of the delivery details are stored in Japanese (text like Customer name,street address etc..)
    .so when i am trying to send it as attachment these japanese text is not appearing correctly in the mail attachment. its appearing as Junk characters.
    i observed here the problem is may be because these Texts are not sending with UNICODE format. may be the default format is ASCII, which can not
    interpret Japanese text properly.
    so pl let me know is there any new function module where we can mention the Encoding format like UNICODE ?? or can i use the
    same above mentioned function module with providing this UNICODE value somewhere....
    regards
    srikanth,Intelligroup.
    Message was edited by: Srikanth Kidambi

    Hi,
    Check the answer from xiaoming cai in this thread:
    Send mails with attachment to external email id
    Eddy

  • Sending � signs with JavaMail

    Hi chaps,
    At our company we use the JavaMail API through JNI to send emails externally to customers.
    Recently the business has decided that it would be nice to send pound (�) through, however it's not going to plan.
    Normally the messages are encoded in 7-bit which would seem to exclude the � (163), however it seems that it is first converted to a (=80, hex with no ascii correlation) and then to a Euro symbol.
    I've tried setting the "allow8bitmime" property in order to enable the SMTP service to support 8-bit encoding, but it's not working AND Microsoft say that our Exchange (v5.5) doesn't support 8-bit MIME types. The odd thing is that sending external emails via Exchange supports the � with no problems and is read in the mail reader as 8-bit encoded (!).
    Has anybody had any experience with issues like this ? Any reply appreciated.
    Thanks
    Ammonite

    Ammonite,
    I am working on a similar problem.. Did you say your
    email gets translated and prints the Euro symbol... I
    actually need out email to print Both the pound and
    the Euro and it does niether right now.. The current implementation I am working on will display a Euro instead of a pound, although this isn't by design. The message is encoded using "Quoted-Printable" and substitutes the pound for a =80 character. How this maps to a Euro is unknown to me :(
    In standard ascii the pound is outside the standard 7-bit encoding range (163) and featured in the Extended Set on the platform we use. I'm not sure about the Euro. The Iso-8859-1 charset which SH provided supports the pound in "Quoted-Printable" encoding, but this hasn't been well received by JavaMail MIME objects that I have tried.
    I haven't managed any sort of 8-bit encoding with JavaMail as yet, due to supposed lack of support in Exchange 5.5 and lack of response to the "allow8bitmime" property.
    does anyone know is using MimeMessage limit the
    message to ASCII characters only and does that rule
    out the Euro and the Pound symbol/
    It shoudn't rule them out, but I'm starting to believe that MimeMessages are necessarily helping things here :)

  • HT201342 what is the max size of attachment that possible to send with icloud email?

    what is the max size of attachment that possible to send with icloud email?

    Welcome to the Apple Community.
    There isn't an attachment size limit as such, the limit applies to the entire message including all attachments, which is 20 MB.
    if you are using a mail application to send emails (ie not via a web browser) you may be subject to smaller limits imposed by your own ISP.

Maybe you are looking for