Email Prob - Content-Transfer-Encoding: base64

Using APEX to send an email to a CA product. We are doing this successful with another source (not Apex). The email that is sent opens a Help Desk ticket in the CA tool.
Another development tool has the this in the mime.822 file:
Content-Transfer-Encoding: 8 bit
The email send from APEX has Content-Transfer-Encoding: base64.
The look of the emails are different, this is why it is not working correctly when sent from APEX.
Does anyone know about base64 versus 8-bit?

Steve,
>> Yes, I am sure. This all being done inside our firewall and domain.
For an e-mail message to get from point A to point B, it must go through some message transfer agent somewhere, regardless whether it's all within the same firewall, domain, or otherwise.
>> Is there a work-around for this?
There can only be a workaround when the definitive problem has been identified. That has not been done.
I just sent myself a message from apex.oracle.com, which is running APEX 3.0.1. I examined the entire message source in Thunderbird. I found no occurrence of Content-Transfer-Encoding in my message whatsoever. Hence, I believe this is not APEX which is injecting this into your message.
My suggestion - take a look at what your SMTP server settings are for your APEX instance. Ensure that you are routing your e-mail to the SMTP server which works from the other "source" which is done successfully.
Joel

Similar Messages

  • Five days ago I received an email from an anonymous sender with the subject: Your Apple ID was just used to buy full album Elton John 312.99. Your receipt No. 37930343160405752. the content began: Content-Transfer-Encoding: base64 From (my email add

    Five days ago I received an anonymous email with the subject:
    Your Apple ID was just used to buy full album Elton John £12.99.Your receipt No.37930343160405752
    The content started: Content-Transfer-Encoding: base64 From:(my email address) followed by a very,very,very long stream of gobbledygook. There is no record of it in my i-tunes purchases or my credit card statement but that might only be because I have not updated my credit card details. Should I be worried that my account has been compromised? Does anyone know how I can get through to the right section of Apple to deal with this - all the emails I get say no-reply so I don't have an email address to contact them on.
    I would be most grateful if anyone could help me with this.
    Thanks in advance
    Walwal

    It's a phishing attempt to try and get your account and payment details - forward it to Apple : [email protected] , and then delete it
    Phishing emails : Identifying fraudulent "phishing" email - Apple Support
    Genuine emails : Identifying legitimate emails from the iTunes Store - Apple Support

  • Running mac OS 10.5.8, Using Mail 3.5, Text encoding set to Automatic. messages arrive, but the message is 200  lines of alphanumerics. Top says Content-Type: text/plain;      charset=utf-8 Content-Transfer-Encoding: base64.

    I use Mail 3.6 and some incoming email messages start with
    Content-Type: text/plain;
        charset=utf-8
    Content-Transfer-Encoding: base64
    then go on to 200+ lines of alphanumerics (mostly upper and lower case letters). 
    What causes this problem, how can I fix it?
    Text encoding is set to Automatic, and  I'm not using any fancy fonts.  Senders are usually
    sending from PCS that may well use Outlook.
    Rosemary C.  Chicago

    Does it look something like this...
    JVBERi0xLjYNJeLjz9MNCjMyNCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvRmlyc3QgNi9M
    ZW5ndGggMTU4L04gMS9UeXBlL09ialN0bT4+c3RyZWFtDQohx6hAp7lMT4WVkGpP6z3UpIQfO4eN
    QRbgjhTqX5mfaabWcvQk/hLnUX6MpKiXwist+RiaiGrzj8XGSNFXuvETWsnoPoV687Exvzo1KYV4
    jIuPmKXlRJvESTE/K2htJihPMS/o6fo3i+nHbTBRWpyrXSfmCPVEgsAzcyECvSU0Rz4MJsEXpdu6
    6u/hg1hlPkb2gpkUQJv50YtWhkD/Jg0KZW5kc3RyZWFtDWVuZG9iag0zMjUgMCBvYmoNPDwvRmls
    Check Mail>View>Message, does it say View Raw Source, Long Headers, or Default Headers?
    See if view Plaintext version helps.

  • I want to convison the mail body 's Content-Transfer-Encoding to base64

    Return-Path: <[email protected]>
    Received: from tobacco ([130.130.160.76]) by webapp.tobacco
    (Netscape Messaging Server 3.6) with ESMTP id AAA70AC;
    Tue, 6 Nov 2001 18:26:28 +0800
    type: ���� intra@ius_center 1670
    subject: ������gggggg��
    Content-Type: text/html; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Date: Tue, 6 Nov 2001 18:26:28 +0800
    Message-ID: <[email protected]>
    From: [email protected]
    <center><h1>����</h1><TABLE BORDER=1 CELLPADDING=5 width=90%%>
    <TR><TD BGCOLOR=#CCCC99 width=74 valign=top><STRONG>��������</STRONG></TD><TD BGCOLOR=#EEEEEE>gggggg</TD> </tr>
    <TR><TD BGCOLOR=CCCC99 VALIGN=TOP><STRONG>�� �� ��</STRONG></TD><TD BGCOLOR=#EEEEEE>������ ������������������</td></tr>
    <tr><TD BGCOLOR=#CCCC99 VALIGN=TOP><STRONG>�� �� ��</STRONG></TD><TD BGCOLOR=#EEEEEE >������ ������������������</td></tr>
    <tr><TD BGCOLOR=#CCCC99 VALIGN=TOP><STRONG>��������</STRONG></TD><TD BGCOLOR=#EEEEEE >fdsf</td></tr></TABLE>

    Me too. I want to find out what encoding a particular $INPUT_FILE part is when I need to parse it in my conversions script.

  • How to change the Content-Transfer-Encoding for the fmddataa.fmd from base

    Dear all,
       When I using this SO_DOCUMENT_REPOSITORY_MANAGERto send email,I find the fmddata.fmd  file have been changed  to binary file attachment. I don't hope so.any one have good idea to avoid this case occur?
      Can you tell me how to change the Content-Transfer-Encoding for the fmddata.fmd from base64 to quoted-printable.  The quoted-printable is the Content-Transfer-Encoding for text file with extension .txt
    Best Regards,
    Merry

    Thank you

  • Content-Transfer-Encoding is possible to change of received mail?

    Its possible change Content-Transfer-Encoding 7bit to 8bit in received mail?
    If yes please let me know how?
    Thanks
    Sanjay kashyap

    Hi Sanjay Did u get any answer to ur problem as i also have problem with encoding problems and would like to change the encoding of the email message in the case when it is not specified with the email itself
    Thanks

  • Content-Transfer-Encoding Header missing?

    Hello,
    our Exchange 2013 CU 6 won't send "Content-Transfer-Encoding" Header when sending Mails to external Domains. (This Header is present if Mail stays within our Org)
    Already tried to set different Encodings - but without luck ... Exchange just won't generate this Header ...
    [PS] C:\Windows\system32>Set-RemoteDomain -Identity Default -ByteEncoderTypeFor7BitCharsets Use7Bit
    [PS] C:\Windows\system32>Set-RemoteDomain -Identity Default -ByteEncoderTypeFor7BitCharsets UseBase64
    [PS] C:\Windows\system32>Set-RemoteDomain -Identity Default -ByteEncoderTypeFor7BitCharsets UseQP
    Hope someone here can help me with this!?
    Thank you, bye from Austria
    Andreas Schnederle-Wagner

    Hi,
    I suggest try to re-start the Transport service after running the commands you mentioned.
    Please try to refer following KB to change the encoding type. I suggest make a backup before changing the value.
    How to change the method for transfer encoding after you apply Exchange 2007 SP1 to the Exchange 2007-based server that is running the Hub Transport role
    https://support.microsoft.com/kb/946641?wa=wsignin1.0
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • How to change Content-Transfer-Encoding for mail sending

    Hello Experts,
    I need to send some documents through mail which i am doing with the help of cl_output_service=>document_output method. Mail is been send succesfully.
    But in the payload content which got from Exchange server:
       X-Mailer: SAP Web Application Server 7.10
       Content-Type: text/plain;
        charset="us-ascii"
       Content-Transfer-Encoding: quoted-printable
    Can any one help me, how i can change Content-Transfer-Encoding field to some other format which is not  'quoted-printable'.
    Thanks & Regards,
    Dheeraj

    Do you documents contain an XML Declaration like this at the top?
    <?xml version="1.0" encoding="ISO-8859-2"?>
    If not, then they need to. The XML 1.0 specification says that if an XML declaration is not present, the processor must default to assume its in UTF-8 encoding.

  • Content-Transfer-Encoding for mail from Portal

    Hi,
    I work on Portal 7.0 SP 12.
    Do You know how to change encoding (Content-Transfer-Encoding) for mails send from portal by users (ex. from Collaboration Launch Pad) ?
    Regards,
    Jarek

    Thank you

  • Email attachment content corrupted, Encoding Issue

    Hi all, I have problem with corrupted email attachments.
    I write JSP codes to send the html file I have created as an ATTACHMENT by using codes:
    messageBodyPart = new MimeBodyPart();
    FileDataSource fds = new FileDataSource(tempAttachment);
    messageBodyPart.setDataHandler(new DataHandler(fds));
    messageBodyPart.setFileName(filename);
    multipart.addBodyPart(messageBodyPart);
    I can successfully send out an email with attachment, however, the attachment when received by Outlook Express, Gmail, Thunderbird are fine without any corruption, but it was corrupted when received with my Outlook 2000. It is totally corrupted and cannot be converted even I change any encodings to view it. Please find below the corrupted text for your reference:
    [email protected]& @{83;g@Z8i 1MGO 6G4B 1MGO@G ?)G` 0hH94c4g@Z0! ?9>`GR 6' A$H.GQ <:8m 9W ?y5eF\=: 9xH#8& >K7AAV=C1b 9Y6x4O4Y.
    I found many resources to help people to do encoding for the mail subject and attachment file name, but coundn't find any for the encoding of the attachment content, many authors even suggest that the email client will do the job for attachment encoding conversion. But, Outlook 2000 sucks, I need to do it explicitly in the coding, would anyone of you help me?
    Thanks a lot for your help and this is urgent, your help is highly appreciated.

    Hey, where are the experts?Maybe the JavaMail experts view the JavaMail forum!
    >
    OMG, people in this forum only know how to get stuff
    from the others and never thinking of sharing your
    knowledge with the others?This is just stupid! If nobody is "sharing your knowledge" then how can others "get stuff"?
    >
    Or there are no experts in this forum???Plenty! Many have written well thought of books on various Java topics.
    I am not an expert in JavaMail but I use JavaMail and have sent JavaMail with attachments to Outlook 2000 but I have never seen your problem. Don't you think it significant that all woks OK except on Outlook 2000! Maybe printing the raw email will help you decide what is wrong.
    P.S. Consider moving the code that sends the email out fo the JSP to a class that can be tested outside the web server. Then if you have a problem you can post more than just a fragment.

  • TS3276 Content-Transfer-Encodong: quoted-printable?

    Does anyone know why I'm receiveing emails that look like this? Is it a setting on my end or the sending emailer?
    Thanks in advacne for your help.
    --Apple-Mail-425-337390284
    Content-Type: multipart/mixed;
              boundary=Apple-Mail-426-337390286
    --Apple-Mail-426-337390286
    Content-Transfer-Encoding: quoted-printable
    Content-Type: text/html;
              charset=us-ascii
    <html><head></head><body style=3D"word-wrap: break-word; =
    -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
    "><div>Here are the adjustments from 3/4 through =
    3/10.</div><div><br></div><div><font class="3D""Apple-style-span" =
    size=3D"4"><b><u>I huge kudos to Los Gatos and San Jose for having spot =
    on bike inventories!  Great =
    work!!!</u></b></font></div><div><br></div><br><div>
    <span class="3D""Apple-style-span" style=3D"border-collapse: separate; =
    color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
    font-variant: normal; font-weight: normal; letter-spacing: normal; =
    line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
    white-space: normal; widows: 2; word-spacing: 0px; =
    -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
    0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
    auto; -webkit-text-stroke-width: 0px; "><span class="3D""Apple-style-span" =
    style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
    Helvetica; font-style: normal; font-variant: normal; font-weight: =
    normal; letter-spacing: normal; line-height: normal; orphans: 2; =
    text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
    word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
    -webkit-border-vertical-spacing: 0px; =
    -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
    auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
    break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
    after-white-space; "><span class="3D""Apple-style-span" =
    style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
    Helvetica; font-style: normal; font-variant: normal; font-weight: =
    normal; letter-spacing: normal; line-height: normal; orphans: 2; =
    text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
    word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
    -webkit-border-vertical-spacing: 0px; =
    -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
    auto; -webkit-text-stroke-width: 0px; "><span class="3D""Apple-style-span" =
    style=3D"font-size: 13px; =
    "></span></span></div></span></span></div></body></html>

    How exactly are you accessing the original attachment data?  If you use getInputStream to read the original data store it, then the data is going to be decoded when you read it.  When you attach it to the new message, that data is going to be re-encoded when the message is sent (or saved).  JavaMail may not be encoding it in exactly the way the original sender did, although in most cases that shouldn't make a difference.  Depending on the content of the PDF file, quoted-printable might not be the best choice for encoding.
    You  might be better off storing the encoded original data, using getRawInputStream, then using PreencodedMimeBodyPart when you construct the new message.

  • Transfer-Encoding is set depending on server

    Hi everyone!
    I have a serious problem concerning message encoding on different machines. On my development machine (running WinXP) I can send email messages perfectly with this code:
    MimeMessagePreparator pwMessagePreparator = new MimeMessagePreparator() {
        public void prepare(MimeMessage mimeMessage) throws MessagingException {
        mimeMessage.setHeader("Content-Transfer-Encoding", "8bit");
        MimeMessageHelper message = new MimeMessageHelper(mimeMessage, false, "ISO-8859-1");
        message.setSubject("Engineering-Days - Neues Passwort");
        message.setTo(address);
        String messageText = "Hallo!\n\n" +
            "Dein Passwort wurde neu gesetzt. Es lautet jetzt: " + newPw + "\n" +
            "Logge Dich damit bitte auf der Homepage ein und �ndere unter \"Mein Konto\" das Passwort.\n\n" + 
        try {
            message.setText(new String(messageText.getBytes("ISO-8859-1")));
        } catch (UnsupportedEncodingException ex) {
            logger.error(ex);
            try {
                mailSender.send(pwMessagePreparator);
            } catch (MailException e) {
                logger.warn("Senden der Mail f�r User " + address + " nicht erfolgreich: " + e.getMessage());
            }The text is German, never mind its meaning, what counts is that there are umlauts in it. The message is displayed correctly, the header is also correct:
    Content-Type: text/plain; charset=ISO-8859-1
    Content-Transfer-Encoding: 8bitI set mail.smtp.allow8bitmime to true.
    As soon as I deploy the code on my production machine, the header looks like this:
    Content-Type: text/plain; charset=ISO-8859-1
    Content-Transfer-Encoding: 7bitNo matter what I do, it is always set to 7bit. Therefore, the umlauts are not transmitted correctly. I also tried lots of different things, including setting the charset to different values, using MimeUtility and so on. Nothing worked.
    Any suggestions are highly appreciated.
    Best regards,
    Jan-Philipp Stegh�fer

    I now set the Tomcat Locale to de_CH. This had no effect on the encoding. I also changed the code and removed the MimeMessageHelper. It now looks like this:
    MimeMessagePreparator pwMessagePreparator = new MimeMessagePreparator() {
         public void prepare(MimeMessage mimeMessage) throws MessagingException {
              //mimeMessage.setHeader("Content-Transfer-Encoding", "8bit");
              mimeMessage.setSubject("Engineering-Days - Neues Passwort", "ISO-8859-1");
              mimeMessage.addRecipient(RecipientType.TO, new InternetAddress(address));
              mimeMessage.setFrom(new InternetAddress("[email protected]"));
              mimeMessage.setText("Hallo!\n\n" +
                   "Dein Passwort wurde neu gesetzt. Es lautet jetzt: " + newPw + "\n" +
                   "Logge Dich damit bitte auf der Homepage ein und �ndere unter \"Mein Konto\" das Passwort.\n\n" , "ISO-8859-1");                  
    try {
         mailSender.send(pwMessagePreparator);
    } catch (MailException e) {
         logger.warn("Senden der Mail f�r User " + address + " nicht erfolgreich: " + e.getMessage());
    }The problem remains. Is it possible that the switch from a Windows to a Linux machine causes this effect?
    On the other hand, most e-mails are encoded with "quoted-printable". In this encoding, the special signs are encoded as a sequence of characters starting with '='. Can I force JavaMail to use this transfer encoding?
    Message was edited by:
    Jan-Philipp.Steghoefer

  • Mail attachement content trnsfer encoding 8bit , 7bit

    Good morning to everybody.
    I have a problem reading mail attachement.
    When the attachement is 8bit encoded the exadecimal char "3D" is write in a file as "0D". This is wrong
    When the attachement is 7bit encoded the exadecimal char "3D" is write in a file as "3D" . Thi is right
    Is there anyone who knows why of this beaviour?
    Many thanks

    I'm using the msgshow.java that is the example included in the java mail library.
    Attachement downloaded with JavaMail (the bad one):
    �� 3D ==> 0D (CR)
    2007-05-15;18.11.26;978;000469,00;380;Italy
    ;LUISA SPAGNOLI NAPOLI IT;34009575;8036527 ;5651;00;
    Attachement downloaded with outlook (the good one):
    �� 3D not translated
    2007-05-15;18.11.26;978;000469,00;380;Italy =
    ;LUISA SPAGNOLI NAPOLI IT;34009575;8036527 ;5651;00;
    Here the properties of the mail message:
    Microsoft Mail Internet Headers Version 2.0
    Received: from EXSMTP-IN2.sede.corp.sanpaoloimi.com ([10.244.7.21]) by EVS01.sede.corp.sanpaoloimi.com with Microsoft SMTPSVC(6.0.3790.2499);
         Mon, 28 May 2007 08:09:14 +0200
    Received: from secgw-b-e02.intesabci.it ([172.19.0.27]) by EXSMTP-IN2.sede.corp.sanpaoloimi.com with Microsoft SMTPSVC(6.0.3790.2499);
         Mon, 28 May 2007 08:09:13 +0200
    Received: MHUBINT
    Received: FW
    Received: from mail1.ssb.it ([192.106.129.13])
         by mailbox.intesabci.it with SMTP id l4S696n5006757
         for <[email protected]>; Mon, 28 May 2007 08:09:09 +0200
    Received: (qmail 11377 invoked by uid 509); 28 May 2007 06:02:04 -0000
    Received: from 127.0.0.1 by Imhotep (envelope-from <[email protected]>, uid 501) with qmail-scanner-2.01
    (spamassassin: 3.1.3.
    Clear:RC:1(127.0.0.1):.
    Processed in 0.078893 secs); 28 May 2007 06:02:04 -0000
         Mon, 28 May 2007 08:02:03 +0200 (CEST)
         (Postfix) with SMTP id 6798F34257;Mon, 28 May 2007 08:02:03 +0200 (CEST)
    to: <[email protected]>,
    from: <[email protected]>
    subject: 28 May 2007 08:00 PS12 FROD-ATM1
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
         boundary="P=_NextPart_000_01BD3BAF.A762FD80"
    Date: Mon, 28 May 07 08:00:27 B
    Message-Id: <[email protected]>
    Return-Path: [email protected]
    X-OriginalArrivalTime: 28 May 2007 06:09:13.0674 (UTC) FILETIME=[B707A2A0:01C7A0EE]
    --P=_NextPart_000_01BD3BAF.A762FD80
    CONTENT-TYPE: TEXT/PLAIN; CHARSET="US-ASCII"
    Content-Transfer-Encoding: 8bit
    --P=_NextPart_000_01BD3BAF.A762FD80
    Content-Type: text/plain; charset=us-ascii; name="SPIMI.TXT"
    Content-Disposition: attachment
    Content-Transfer-Encoding: quoted-printable
    X-MIME-Autoconverted: from 8bit to quoted-printable by mailbox.intesabci.it id l4S696n5006757
    --P=_NextPart_000_01BD3BAF.A762FD80
    CONTENT-TYPE: TEXT/PLAIN; CHARSET="US-ASCII"
    Content-Transfer-Encoding: 8bit �������� I think the problem is here
    P=_NextPart_000_01BD3BAF.A762FD80

  • Help me...How to read the content if "Transfer-Encoding:chunked" is used?

    I am doing a project for internet control using Java,PHP and MySql.All sites should go through the proxy server only.If the HTTP header contains Content-Length,am getting the content length as below:
    public class HTTPResponseReader extends HTTPMessageReader
        String statusCode;
        public HTTPResponseReader(InputStream istream) throws IOException,                     NoSuchElementException
      BufferedInputStream distream = new BufferedInputStream(istream);
      retrieveHeader(distream);
      StringTokenizer st =  new StringTokenizer(new String(HTTPMessageReader.toArray(header)));
      versionProtocol = st.nextToken();
      statusCode = st.nextToken();
      String s;
      while (st.hasMoreTokens())
            s = st.nextToken();
            if (s.equals("Transfer-Encoding:"))
           transferEncoding = new String(st.nextToken());
         if (s.equals("Content-Length:"))
           contentLength = Integer.parseInt(st.nextToken());
         if (s.equals("Connection:"))
          connection = new String(st.nextToken());
          if (connection.equals("keep-alive")) mustCloseConnection = false;
       retrieveBody(distream);     
    }After getting the Content-Length,i used read method to read the content upto that content length.Then i concatenated the HTTP header and body and the requested site was opened.But some sites dont have Content-Length.Instead of that,Transfer-Encoding is used.I got the HTTP Response header as "Transfer-Encoding:chunked" for some sites.If this encoding is used how to get the length of the message body and how to read the content.
    Can anybody help me.
    Thanks in advance...
    Message was edited by:
    VeeraLakshmi

    Why don't you use HttpUrlConnection class to retrieve data from HTTP server? This class already supports chunked encoding...
    If you want to do anything by yourself then you need to read HTTP RFC and find all required information. Well in two words you may reject advanced encoding by specifying HTTP 1.0 in your request or download chunked answer manually. Read RFC anyway :)

  • How to read the content of  "Transfer-Encoding: chunked" header

    Can anybody tell me how to get or read the value of transfer encoding.
    I got the HTTP Response header as "Transfer-Encoding: chunked".But i can't get the chunk size or the chunked data.
    Without getting those details i cant read the content of the site.If Content-Length is in the HTTP header,i can read upto that length.But in this Transfer-Encoding case,i cant know any other details except the value "chunked".So suggest me to read the content of the site using Transfer-Encoding.
    Message was edited by:
    VeeraLakshmi

    I used HTTPURLConnection also.If i use that am getting the values in request headers only and not in Response headers.So i cant read the content.
    Then i went through RFC 2616.There i can only understand about chunked transfer encoding.Still i cant get any idea to know the chunk-size and the chunked data of the transfer encoding.Because i am getting the HTTP Header Response as "Transfer-Encoding: chunked".Below that am not getting the size and data.If i know the size or data,i can proceed by converting the hex into bytes and i can read.

Maybe you are looking for