james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Daring" <cog...@chello.at>
Subject Re: [PATCH] RemoteDelivery multiple delay times
Date Sat, 08 Nov 2003 10:36:57 GMT

----- Original Message -----
From: "Andreas Göggerle" <andreas.goeggerle@pansoft.de>
To: "'James Developers List'" <server-dev@james.apache.org>
Cc: <werling@pansoft.de>
Sent: Friday, November 07, 2003 2:27 PM
Subject: RE: [PATCH] RemoteDelivery multiple delay times

> But why do I need to extend the MimeMessage class? As far as I can see,
> it does nothing new.

That's because of getting rid off all the unwanted default-headers
MimeMessage generates in writeTo(...). Use your original MimeMessage instead
you will see what i mean. You will also get an error message.
But keep in mind with this writeTo version no auto-encoding is done, so you
are responsible for RFC-compliance. As for that matter take a look at
MimeUtiltity.encode(...). This is only necessary when you have non ascii
characters in your text like "Umlaute".
If you dont know your encoding scheme use
MimeUtility.getEncoding(DataHandler dh).


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message