Strange address "=?iso-8859-1?B?VXNlcqAxoA==?= user1@domain.dom" on imap ?

I have a MimeMessage, then I set the From field like this:
mimemsg.setFrom(new InternetAddress("User 1 [email protected]");
mimemsg.setSubject("subject");
mimemsg.setText("something ... ");
mimemsg.saveChanges();
Transport.send(mimemsg);
Everything seem ok. I open User 1 by Pop3 protocol, receive that mail, I receive the From field correct:
User 1 [email protected]
But if I used Imap protocol, retrieve that mail, the From field look like this:
=?iso-8859-1?B?VXNlcqAxoA==?=[email protected]
What's wrong with it ? I don't understand why ? Maybe a bug ? (I've searched but found nothing about that)
That above code were written in a bean class, I present the content on a JSP page, access the page by HTTPS:
https://locahost:8443/jsp/Jsp1.jsp
The WebServer is Tomcat 3.2 (win32) with SSL, MailServer is MDaemon 3, Web browser is IE 5.
Thanks for reading.

part of the From field is coded in base64.
if you decode "VXNlcqAxoA==", you will get "User 1".
I dont know if there is an API which convert this. So I have
passed the string to base64 converter.

Similar Messages

JasperReports Integration PDF is created with ISO-8859-1 instead of UTF-8

Hi,
This is a strange problem i'm struggling with. Since about one month the PDF's are created with the wrong character set. Instead of UTF-8 (this is also given as a parameter calling the procedure as you see below) the PDF are always created with ISO-8859-1.
declare
l_jasper_report_url VARCHAR2(100) DEFAULT 'http://localhost:8180/JasperReportsIntegration/report';
l_rep_name VARCHAR2(80) DEFAULT'SLRReports/SLR_Statistic_Service_Level_Report_Monat';
l_rep_format VARCHAR2(10) DEFAULT 'pdf';
l_data_source VARCHAR2(20) DEFAULT 'default';
l_rep_locale VARCHAR2(10) DEFAULT 'de_CH';
l_rep_encoding VARCHAR2(10) DEFAULT 'UTF-8';
l_StartDate DATE;
l_EndDate DATE;
l_MinDowntime INTEGER DEFAULT 1;
l_ServiceHour CHAR DEFAULT 'Y';
l_name VARCHAR2(50);
l_typ VARCHAR2(20) DEFAULT 'monatsreport_ccps';
l_additional_params VARCHAR2(200);
l_mime_type VARCHAR2(30);
l_blob BLOB;
BEGIN
l_StartDate := to_date('01.'||to_char( add_months(SYSDATE,-12),'MM.YYYY'),'DD.MM.YYYY');
l_EndDate := to_date('30.'||to_char( add_months(SYSDATE,-1),'MM.YYYY'),'DD.MM.YYYY');
l_name := 'slr-statistik-'||to_char(l_StartDate,'YYYY-MM')||'.pdf';
l_additional_params := 'UserName=SYSTEM'||chr(38)||'String_StartDate='||to_char(l_StartDate,'dd.mm.yyyy')||chr(38)||'String_EndDate='||to_char(l_EndDate,'dd.mm.yyyy')||chr(38)||'SLR_MinDowntime='||l_MinDowntime||chr(38)||'SLR_ServiceHour='||chr(38)||l_ServiceHour;
xlog ('PRC_GET_REPORT_TUNNEL', 'url (orig):' || l_rep_name||':'||l_additional_params);
-- generate the report and return in BLOB
xlib_jasperreports.set_report_url (l_jasper_report_url);
xlib_jasperreports.get_report (
p_rep_name => l_rep_name,
p_rep_format => l_rep_format,
p_data_source => l_data_source,
p_rep_locale => l_rep_locale,
p_rep_encoding => l_rep_encoding,
p_additional_params => l_additional_params,
p_out_blob => l_blob,
p_out_mime_type => l_mime_type );
dbms_output.put_line('p_out_mime_type: '||l_mime_type);
-- insert into report (id,name,typ,mime_type,lob_text,datum) values (p_report_seq.nextval,l_name,l_typ,l_mime_type,l_blob,sysdate);
-- commit;
-- apex_application.g_unrecoverable_error := TRUE;
EXCEPTION
WHEN OTHERS THEN
xlog ('PUT_BLB', SQLERRM, 'ERROR');
RAISE;
END;
It looks like the procedure UTL_HTTP.get_header ignores the encoding parameter and overwrites it with ISO-8859-1. I also tried to set it with UTL_HTTP.set_header before calling UTL_HTTP.get_header buth that didn't help either.
Then I started the JVM is started with the UTF-8 option and that made no change.
There were no new installation on Oracle, tomcat or JasperReports side. So I'm wondering what has caused this string behaviour.
Does anyone had this problem before or has a solution for it?
I appreciate your help very much.
Thanks and regards,
Chris

Hi,
As my understanding, you could choose the encoding ways by yourself:
Change your Internet Explorer 9 language
encoding settings
Alex Zhao
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Setting ISO-8859-1 Encoding in AXIS RPC call

As per my understanding UTF-8 is default for webservice call in AXIS implementation I may be wrong.
Is there any way to set ISO-8859-1 encoding in AXIS RPC call?
Below is the WSDL file details.
Thanks for you help.
Regards,
Hemen
<Code>
<?xml version="1.0" encoding="ISO-8859-1"?>
<definitions name="TestService_Service"
targetNamespace="http://webservice.de.rt.wsdl.WebContent/TestService_Service/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
xmlns:java="http://schemas.xmlsoap.org/wsdl/java/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://webservice.de.rt.wsdl.WebContent/TestService_Service/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="getResponseRequest">
<part name="xml" type="xsd:string"/>
<part name="product" type="xsd:string"/>
<part name="source" type="xsd:string"/>
<part name="tran" type="xsd:string"/>
<part name="content" type="xsd:string"/>
</message>
<message name="getResponseResponse">
<part name="return" type="xsd:string"/>
</message>
<portType name="TestService">
<operation name="getResponse" parameterOrder="xml product source tran content">
<input message="tns:getResponseRequest" name="getResponseRequest"/>
<output message="tns:getResponseResponse" name="getResponseResponse"/>
</operation>
</portType>
<binding name="TestServiceJavaBinding" type="tns:TestService">
<java:binding/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap formatType="java.lang.String" typeName="xsd:string"/>
</format:typeMapping>
<operation name="getResponse">
<java:operation methodName="getResponse"
parameterOrder="xml product source tran content" returnPart="return"/>
<input name="getResponseRequest"/>
<output name="getResponseResponse"/>
</operation>
</binding>
<binding name="TestServiceBinding" type="tns:TestService">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getResponse">
<soap:operation soapAction="" style="rpc"/>
<input name="getResponseRequest">
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="distributionengine.com"
parts="xml product source tran content" use="encoded"/>
</input>
<output name="getResponseResponse">
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="distributionengine.com" use="encoded"/>
</output>
</operation>
</binding>
<service name="TestServiceService">
<port binding="tns:TestServiceJavaBinding" name="TestServiceJavaPort">
<java:address className="rt.de.webservice.TestService"/>
</port>
</service>
<service name="TestService_Service">
<port binding="tns:TestServiceBinding" name="TestServicePort">
<soap:address location="http://localhost:9080/servlet/rpcrouter"/>
</port>
</service>
</definitions>
</code>

try to put the below code at the top of the JSP page
<%@ page language="java" pageEncoding="UTF-8"%>

XMLReader throws "Invalid UTF8 encoding." - Need parser for ISO-8859-1 chrs

Hi,
We are facing an issue when we try to send data which is encoded in "ISO-8859-1" charset (german chars) via the EMDClient (agent), which tries to parse it using the oracle.xml.parser.v2.XMLParser . The parser, while trying to read it, is unable to determine the charset encoding of our data and assumes that the encoding is "UTF-8", and when it tries to read it, throws the :
"java.io.UTFDataFormatException: Invalid UTF8 encoding." exception.
I looked at the XMLReader's code and found that it tries to read the first 4 bytes (Byte Order Mark - BOM) to determine the encoding. It is probably expecting us to send the data where the first line is probably:
<?xml version="1.0" encoding="iso88591" ?>
But, the data that our application sends is typically as below:
========================================================
# listener.ora Network Configuration File: /ade/vivsharm_emsa2/oracle/work/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = semsa2)
(ORACLE_HOME = /ade/vivsharm_emsa2/oracle)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = tcp)(HOST = stadm18.us.oracle.com)(PORT = 15100))
========================================================
the first 4 bytes in our case will be, int[] {35, 32, 108, 105} == chars {#, SPACE, l, i},
which does not match any of the encodings predefined in oracle.xml.parser.v2.XMLReader.pushXMLReader() method.
How do we ensure that the parser identifies the encoding properly and instantiates the correct parser for "ISO-8859-1"...
Should we just add the line <?xml version="1.0" encoding="iso88591" ?> at the beginning of our data?
We have tried constructing the inputstream (ByteArrayInputStream) by using String.getBytes("ISO-8859-1") and passing that to the parser, but that does not seem to work.
Please suggest.
Thanks & Regards,
Vivek.
PS: The exception we get is as below:
java.io.UTFDataFormatException: Invalid UTF8 encoding.
at oracle.xml.parser.v2.XMLUTF8Reader.checkUTF8Byte(XMLUTF8Reader.java:160)
at oracle.xml.parser.v2.XMLUTF8Reader.readUTF8Char(XMLUTF8Reader.java:187)
at oracle.xml.parser.v2.XMLUTF8Reader.fillBuffer(XMLUTF8Reader.java:120)
at oracle.xml.parser.v2.XMLByteReader.saveBuffer(XMLByteReader.java:450)
at oracle.xml.parser.v2.XMLReader.fillBuffer(XMLReader.java:2229)
at oracle.xml.parser.v2.XMLReader.tryRead(XMLReader.java:994)
at oracle.xml.parser.v2.XMLReader.scanXMLDecl(XMLReader.java:2788)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:502)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:205)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:180)
at org.xml.sax.helpers.ParserAdapter.parse(ParserAdapter.java:431)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.readXML(RemoteOperationInputStream.java:363)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.readHeader(RemoteOperationInputStream.java:195)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.read(RemoteOperationInputStream.java:151)
at oracle.sysman.emSDK.emd.comm.EMDClient.remotePut(EMDClient.java:2075)
at oracle.sysman.emo.net.util.agent.Operation.saveFile(Operation.java:758)
at oracle.sysman.emo.net.common.WebIOHandler.saveFile(WebIOHandler.java:152)
at oracle.sysman.emo.net.common.BaseWebConfigContext.saveConfig(BaseWebConfigContext.java:505)

Vivek
Your message is not XML. I believe that the XMLParser is going to have problems with that as well. Perhaps you could wrap the message in an XML tag set and begin the document as you suggested with <?xml version="1.0" encoding="iso88591"?>.
You are correct in that the parser uses only the first 4 bytes to detect the encoding of the document. It can only determine if the document in ASCII or EPCDIC based. If it is ASCII it can detect only between UTF-8 and UTF-16. It will need the encoding attribute to recognize the ISO-8859-1 encoding.
hope this helps
tom

Encoding autodetection chooses ISO-8859-5 instead of UTF-8

A certain site producing HTML in UTF-8 without meta tags. The Firefox detects the encoding as ISO-8859-5, an absolutely dead and useless 'standard'. How to exclude it from the autodetection and maki it proper unicode?

It's a strange guess, if it's a guess. Are you sure the server isn't sending a header specifying that encoding? To view the content-type header, you can use an add-on (or if it's not a secure page, an external proxy):
* Live HTTP Headers extension: https://addons.mozilla.org/en-us/firefox/addon/live-http-headers/
* Firebug extension: https://addons.mozilla.org/en-US/firefox/addon/firebug/
* Fiddler debugging proxy: http://www.fiddler2.com/fiddler2/

Strange =?ISO etc. in the 'from'-field

When i send mails to people with Outlook and Exchange they don't get my return adress right. Sometimes it says: =?ISO-8859-1?Q?=22My_Name, somtimes =?ISO-8859-1?Q?=[email protected]
It means people can't press answer, but have to write my mailadress in the 'to'-field.
I only have the right server for outgoing messages in the system.
Anybody have an idea?

SusansBo wrote:
Which they are not either.
This is not a question of not using english, or even ASCII-letters in the e-mailadress. We all know an e-mail address is supposed to be in a-z, 1-9 etc., even the provider who gave me my adresses.
This is a question of why my the address in the 'from'-field is corrupt when i mail corporate mailsystems in Windows, but not standalone applications or macs.
RFC 2822 Internet Message Format April 2001
2.2. Header Fields
Header fields are lines composed of a field name, followed by a colon
(":"), followed by a field body, and terminated by CRLF. *A field*
*name MUST be composed of printable US-ASCII characters* (i.e.,
characters that have values between 33 and 126, inclusive), except
colon. *A field body may be composed of any US-ASCII characters,*
*except for CR and LF.* However, a field body may contain CRLF when
used in header "folding" and "unfolding" as described in section
2.2.3. All field bodies MUST conform to the syntax described in
sections 3 and 4 of this standard.
Whether that character is in your address or not is irrelevant; it's in the headers and these folks are clearly interpreting the spec very strictly. Take it out and the problem should go away.

SPA504G SPA514G Default Character Encoding stay in ISO-8859-1

Hi,
I have configure like:
<Dictionary_Server_Script ua="na">serv=http://{{ provisioning.server }}/telecom/language/;d0=English;x0=spa50x_30x_en_v754.xml;d1=French;x1=spa50x_30x_fr_v754.xml;</Dictionary_Server_Script>
<Language_Selection ua="na">French</Language_Selection>
<Default_Character_Encoding ua="na">UTF-8</Default_Character_Encoding>
<Locale ua="na">fr-FR</Locale>
Dictionary and Provisioning Profile are encoded in UTF-8.
but when the phone start after provisioning the Default_Character_Encoding set to ISO-8859-1
and the lines labels are misprinted.
Ligne 1
Ligne 2
Olivier
FranÃ§oise
instead of
Ligne 1
Ligne 2
Olivier
Françoise
Any idea ?

I got an answer from the developer.
Pasted here.
I think the default encoding is set back to ISO8859 after customer download the dictionary.
Here is the reason: after 7.5.3, SPA 50x will parse the trkLocaleName in dictionary, for French it will set the phone’s default encoding to iso8859-1 since it is good to French.
French
=================================
•1. If the customer want to use UTF-8 after xml downloading, please modify the trkLocaleName in the French dictionary xml as following:
croatian
It is a workaround, but it's strange why French user will use UTF8. Thanks.
•2. Another way is that user can manually set the default encoding value to UTF-8 after xml downloading.

Put euro symbol in ISO-8859-1 database

is it possible to use jdbc to store a euro symbol in oracle with character set ISO-8859-1 then retrieve the information with jdbc and write it to a ISO-8859-15 textfile and display the euro symbol properly. i'm trying to do this and it doesn't work. as output i use a OutputStreamWriter object in Java using ISO-8859-15 to create an XML file and then i open it in Internet Explorer. it doen't recognize the euro symbols. strange thing is that when i view the source in notepad it does display the euro symbols properly. just using the OutputStreamWriter to write euro symbols also works well.
i'm trying to find out what is causing this problem but i'm not quite sure. i never before had problems with character sets so it's all a bit new to me.
thank you in advance.

The ISO-8859-1 character set does not contain the Euro character, so the database cannot hold it properly. If you want the Euro character to appear in your database, you would have to change the database character set to something that can store the euro character (or make use of your national character set, if that will store the euro character).
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Sun Java System Messaging Server doesn't support some ISO 8859 charsets

Hello,
I couldn't find any link to report bugs on the Sun Java System Messaging Server, so i guess i'll report it here:
Sun Java System Messaging Server currently doesn't support the ISO 8859-13 charset, which is the standard charset in the Baltic states. When a person recieves an email in that charset, every non-ASCII character in the message becomes absolutely unreadable when displayed in this webmail application.
This has been tested with this version of the product:
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.01 (built Jun 24 2004)
Furthermore, you can test the case by yourself using this link: http://www.lietuvybe.org/testas/. You can enter your e-mail address there to get a few sample messages in Baltic and Cyrillic charsets. You will see that the Sun Java System Messaging Server passes all those tests except this particular one. So, it's a very nice product. :)
It would be very very very cool if Sun would fix this small, but very important issue.
regards,
Rimas Kudelis

Hey! :)
I am feeling some bad vibes, here.Hey, sorry, I didn't want you to think it's personal. I didn't really mean to hurt you or whatever. You are trying to help and I do appreciate that. I really do.
The reason i'm a bit sad is about the policy of others:
First, i am not a provider of that webmail service i'm talking about. A big Lithuanian company is. Personally, I rarely use webmail apps at all, and even when i do, i use an app i internationalized myself. :). Meanwhile, i install Horde IMP as a webmail application for my small servers, and i'm satisfied with it.
The problem i described is literally not my problem. It's a problem of that big Lithuanian company mentioned above (and the users of its webmail system). I suppose this company does have that account already and, furthermore, they are the ones who should post to this forum or file a support request., and they are the ones who should be worried about that bug. However, reality differs. In reality, big companies in Lithuania don't care about correctness of their webmail apps too much. However, there are a few maniacs like me who do. We test their webmail apps, we contact them and describe them their problems and ask them to fix those problems. Sometimes, they do that, but in most cases we either don't get a reply at all, or we get something like "we'll take a look at it later". For example, lately, we had an issue with one of the most popular webmail providers in Lithuania skipping a MIME-version header. Fixing this issue is just a single line of code. However, we had to push them annoyingly for kinda few months until they finally fixed it.
That was the first aspect.
The second is that i don't really like to create hundreds of accounts for myself just to ocasionally report bugs like this one. If only Sun would let me to simply file a bug, and forget that, i would gladly do it. But no, i have to find a deeply hiden support page, then fill a form, create myself an account and a password, then log on, then fill some misterious support request... Do I have to do that for a company that won't even consider thanking me? I think that's too much. Furthermore, every party on the net enforces it's own username and password restrictions. That sucks too. I wish i could just log on as "rq" everywhere like this forum, using the same password i could easily remember. However, i have to use "rq", "er-ku" or "erku" or "rq@something" as my username on different platforms, and sometimes even my (long enough) password is not accepted. It's hard to track such accounts, and in most cases like this one, i don't really want to have an account at all, as i'm just passing by.
To summarize the post: I'm NOT a licenced user, and all I wanted was to file a bug, which affects licenced users and ordinary people.
How do i remove my account from this forum now? :)

DB2 with iso-8859-15 text encoding

Hi,
I develop an application on weblogic server configure with a db2 data source. The application is using hibernate 3 (jpa). I cannot write correcly some characters in the database. Text encoding is not converted from utf-16 (java string) to iso-8859-15. Weblogic is installed with the last db2 jdbc driver (9.7).
Is there a data source property that inform the driver to convert utf-16 to the db2 encoding ?

Is the value (text) of header outputText a static text or it is binded to some bindings attribute or backing bean attribute?
If it is a static text then probably the JSF page encoding (not only the JSP tag specifying the encoding, but the whole file) may be broken. Once I had similar issues, and the only thing that helped was to Ctrl+A, Ctrl+X, Ctrl+V (cut all content of file and paste it back - it restores messed-up utf-8 encoding).
If it is not a static text, then check the "source" of the text: it should be the java class file also encoded in utf-8 (also, check Compiler options for your projects - plural). Also, chcek the default IDE encoding... Finally, the database also should have utf-8 encoding (if you are retrieving data from database to show in these header outputTexts).
As I stated before, I had a lot of issues and finally I learned that EVERYTHING should be set correctly to utf-8 in order not to have these strange effects...
Have in mind that Java is very complex in terms of string/text encodings, much more complex than e.g. MS.Net. Internally, Java uses utf-16 encoded strings while most of web applications use utf-8 (for efficiency reasons). So, the gap between Java and web is present, and legacy Java encodings support is quite impractical in modern applications where no one should ever have reason to use anything else than utf-8!

Como deixar a codificação padrão "iso-8859-1" ao invés de "utf-8" no navegador?

Quando faço o acesso ao banco do meu cartão de crédito, a primeira pagina deles é codificada com "UTF-8" e também existe o comando "charset=utf-8" no código HTML, após digitar o número do cartão, ele direciona para outra página, porém codificada com "iso-8859-1", mas sem nenhuma codificação no código HTML.
Identifiquei que o navegador usa por padrão o "utf-8" quando não existe codificação no código HTML, então gostaria de modificar esse padrão para "iso-8859-1".
O único lugar que encontrei para essa codificação foi ao pressionar o botão de avançado em "Fontes e cores", porém não funcionou.
A versão do meu navegado é 23.0.1, entretanto desde a versão 18 que encontro esse problema.

It is possible that the server sends the file(s) by default with UTF-8 and in such a case this encoding send by the server prevails over all other settings.
You can see the encoding here: Tools > Page Info > General
*Press the F10 key or tap the Alt key to bring up the hidden "Menu Bar" temporarily.

Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default]

When trying to load data into Essbase I get this error dialogue
Object [65313270] is locked by user [admin@Native Directory]
Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default] and [English_UnitedStates.Latin1@Binary] are not compatible
Object [65313270] unlocked by user [admin@Native Directory]
Unexpected Essbase error 1019057
Have checked essbase.properties files (all 10 of them!) and the 2 references that I could find both point to the default value of [English_UnitedStates.Latin1@Binary]
So is the problem with the CSV file?

Have you looked at the Load Rule (yes, I know, developed in Studio, but it generates Load Rules which I believe you can open in EAS)? Is the dimension that contains BON accounted for?
Your second issue(s) seems to be that you have conflicting locales -- are you in SA? Could it be that Studio is installed with English as the language and EAS with Arabic (or vice versa)? Sorry, I have hardly any experience in languages other than English. Maybe one of the non-English language posters can chime in.
I can't say whether that load buffer issue means anything at all or not -- it could be a red herring.
Regards,
Cameron Lackpour

UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

Codepage coverting error utf-8 from System codepage to iso-8859-1 (PI 7.1)

Hello Experts,
In our Prcess, we receive an Idoc from an IS-U system and then we send this Idoc with some Header-Information via http-Adapter to a Seeburger System.
In the outbound communication Channel we have a XI Payload manipulation with xml-Code iso-8859-1.
We get the Error: Codepage coverting error utf-8 from System codepage to iso-8859-1, and only for this Idoc, where othe similar Idocs runs correctly.
Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
PS: another XI in our landscape uses a http-Channel with the same configuration in a similar process, an it work, so guess the Problem is not in the communication channel.
thanks,
best regards

> Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
A would rather think, that there could be any non-iso-8859-1 character be in the IDoc. For example an czech or polish character.

Strange address "=?iso-8859-1?B?VXNlcqAxoA==?= user1@domain.dom" on imap ?

Similar Messages

Maybe you are looking for