[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] protocol.email base64
leduke4223 at gmx.net wrote:
What in this context are illegal characters? I thought I was sending a plaintext XML Structure.
This is decided by the javamail implementation of Sun, see
http://java.sun.com/products/javamail/index.jsp
(we use javamail 1.3.3 from 2005-09-10).
I've just noticed that a new javamail release 1.4 is out and
this supports a |PreencodedMimeBodyPart| class, see
http://java.sun.com/products/javamail/FAQ.html
http://jcp.org/aboutJava/communityprocess/maintenance/jsr919/JavaMail-1.4-changes.txt
Porting to this could help to solve your problem,
the spot in our code to look at is in
org.xmlBlaster.util.protocol.email.SmtpClient.java:sendEmail(EmailData
emailData)
regards
Marcel
Thanks,
Chris
-------- Original-Nachricht --------
Datum: Wed, 06 Sep 2006 20:48:58 +0200
Von: Marcel Ruff <mr at marcelruff.info>
An: xmlblaster at server.xmlBlaster.org
Betreff: Re: [xmlblaster] protocol.email base64
leduke4223 at gmx.net wrote:
Hi,
I just tried to connect a mailclient to xmlBlaster following the Howto.
It worked pretty fast, but now I've got the problem that my messages are
Base64 encoded. I tried to change the configuration in xmlblaster.properties
and .plugins but did not succeed to change base64 to a human readable
encoding....
Is there any chance to do that?
Your message-content is already Base64 encoded before you use the email
protocol?
In this case you need a client side Base64 decoder on the receiver side
as well.
It you want to suppress xmlBlaster to do its inside Base64 encoding:
see
http://www.xmlblaster.org/xmlBlaster/doc/requirements/protocol.email.html
messageIdForceBase64 (defaults to false):
"If the messageId markup contains illegal characters it is automatically
base64 encoded. By setting this to true you can enforce everything to
base64, even it is not necessary."
contentForceBase64 (defaults to false):
"If the email payload (the message content) contains illegal characters
it is automatically base64 encoded, typically this happens for binary
data like gif images. By setting this to true you can enforce every
content email attachment to base64, even it is not necessary."
Note that you can't suppress the Base64 encoding in the current
implementation if your text contains illegal characters,
regards
Marcel
Regards,
Chris