You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Johannes Correa <jo...@factoringmarket.com> on 2004/01/21 23:21:21 UTC
James + Exchange Server 5.5
Hello everybody
We are using a James+Jboss configuration to send some emails to our users.
Our emails are constructed using a html template with some design and inside
we put the different texts that are readed from an xml file.
This schema worked fine last year but now we are getting the next message
when some users receive mail from a Exchange Server (others users from
hotmail or another servers don't have any problem):
//Message sent by Exchange
This message uses a character set that is not supported by the Internet
Service. To view the original message content, open the attached message.
If the text doesn't display correctly, save the attachment to disk, and then
open it using a viewer that can display the original character set.
<<message.txt>>
Reviewing the messages from past year and this year we found a little
difference between them: the initial header show "Content-Type: text/html;
charset="iso-8859-1"" instead of "Content-Type: text/html; charset=Cp1252"
of current messages.
//Original header when it worked fine
Received: from ntodd5.grupomun.com ([10.60.1.5]) by csm01.grupomun.com with
SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
id XH4Q8NN3; Mon, 1 Dec 2003 17:22:17 -0500
Content-Class: urn:content-classes:message
Received: from ils ([200.31.15.139]) by ntodd5.grupomun.com with Microsoft
SMTPSVC(5.0.2195.5329);
Mon, 1 Dec 2003 17:22:15 -0500
Return-Path: [some-email-addr]
Received: from 127.0.0.1 ([127.0.0.1])
by ils (JAMES SMTP Server 2.1.3) with SMTP ID 60
for [some-email-addr];
Mon, 1 Dec 2003 17:22:15 -0500 (GMT-05:00)
Message-ID: <30...@grupomun.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
To: [some-email-addr]
Subject: Activacion de cuenta, Sistema de comunicacion Inversiones Mundial
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 1 Dec 2003 17:22:15 -0500 (GMT-05:00)
From: [some-email-addr]
X-OriginalArrivalTime: 01 Dec 2003 22:22:15.0843 (UTC)
FILETIME=[933E2730:01C3B859]
//Actual Header.. it doesn't work
Received: from ntodd5.grupomun.com ([10.60.1.5]) by csm01.grupomun.com with
SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
id C9S5D0QZ; Wed, 14 Jan 2004 17:03:55 -0500
Received: from ils ([200.31.15.139]) by ntodd5.grupomun.com with Microsoft
SMTPSVC(5.0.2195.5329);
Wed, 14 Jan 2004 17:02:04 -0500
Return-Path: [some-email-addr]
Received: from 127.0.0.1 ([127.0.0.1])
by ils (JAMES SMTP Server 2.1.3) with SMTP ID 216
for [some-email-addr];
Wed, 14 Jan 2004 17:02:32 -0500 (GMT-05:00)
Message-ID: <30...@grupomun.com>
To: [some-email-addr]
Subject: Activacion de cuenta, Sistema de comunicacion Inversiones Mundial
Mime-Version: 1.0
Content-Type: text/html; charset=Cp1252
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Jan 2004 17:02:32 -0500 (GMT-05:00)
From: [some-email-addr]
X-OriginalArrivalTime: 14 Jan 2004 22:02:04.0197 (UTC)
FILETIME=[0B38A550:01C3DAEA]
Does anybody have some idea?
Thanks a lot for ane advice
Johannes Correa
IT Developer
FactoringMarket
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: max attachment size?
Posted by J Rollo --Admin <ad...@warthong.org>.
I get a
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
.
.
.
message when I send a message with a big attachment (10mb most recently).
I have to clean the message out of the spool manually to get James back to
normal.
My message size is set for unlimited message size in the config.
Any ideas on how to get James to handle big attachments?
---------------------------------------
Support Open Source,
Demand Quality Software
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James + Exchange Server 5.5
Posted by Johannes Correa <jo...@factoringmarket.com>.
A lot of thanks to Vincenzo Gianferrari for your advice. I did the changes
you suggested in our applicationand it worked fine. Again, thanks.
-----Original Message-----
From: Vincenzo Gianferrari Pini
[mailto:vincenzo.gianferraripini@praxis.it]
Sent: Jueves, 22 de Enero de 2004 07:22 a.m.
To: James Users List; robert@rjamestaylor.com
Subject: RE: James + Exchange Server 5.5
Johannes,
The charset setting is inserted by the MUA preparing the message, not by
James (the MTA). If your MUA is a java application using javamail, I noticed
that there has been a change in javamail 1.3.1 compared to a previous
release exactly in this area: if your text message has special characters
(as accented letters etc), and the application does not explicitely set a
charset (the one to use is charset="iso-8859-1"), then the new javamail sets
it by default to Cp1252 and you may, as I did, encounter exactly the
problems you mentioned.
The problem arose when I upgraded the javamail release.
I was using:
MimeBodyPart mbp = new MimeBodyPart();
StringBuffer sb = new StringBuffer();
...
if (isHTML != 0) {
mbp.setDataHandler(new DataHandler(sb.toString(), "text/html"));
} else {
mbp.setText(sb.toString());
}
and changed to:
MimeBodyPart mbp = new MimeBodyPart();
StringBuffer sb = new StringBuffer();
...
if (isHTML != 0) {
mbp.setDataHandler(new DataHandler(sb.toString(), "text/html;
charset=ISO-8859-1"));
} else {
mbp.setText(sb.toString(), "ISO-8859-1");
}
Setting "-Dmail.mime.charset=ISO-8859-1" and "-Dfile.encoding=ISO-8859-1" as
told in
http://www.mail-archive.com/james-user@jakarta.apache.org/msg05393.html did
solve the problem in one Windows machine where my MUA application was
running (Windows 2k server Italian?), but non in another one (Windows 2k
US) - I don't remember exactly the differences - so I implemented the code
fix shown above, and the problem was solved.
Notice that James was not involved at all.
Hope it helps,
Vincenzo
> -----Original Message-----
> From: Robert J Taylor [mailto:rjamestaylor@cox.net]
> Sent: giovedi 22 gennaio 2004 0.01
> To: James Users List
> Subject: Re: James + Exchange Server 5.5
>
>
> Johannes Correa wrote:
>
> > //Message sent by Exchange
> > This message uses a character set that is not supported by the Internet
> > Service. To view the original message content, open the attached
message.
> > If the text doesn't display correctly, save the attachment to disk, and
then
> > open it using a viewer that can display the original character set.
> > <<message.txt>>
> >
> >
> > Reviewing the messages from past year and this year we found a little
> > difference between them: the initial header show "Content-Type:
text/html;
> > charset="iso-8859-1"" instead of "Content-Type: text/html;
charset=Cp1252"
> > of current messages.
> >
> >
> > Does anybody have some idea?
> >
>
> http://www.mail-archive.com/james-user@jakarta.apache.org/msg05393.html
>
> This should answer your question!
>
> Robert Taylor
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James + Exchange Server 5.5
Posted by Vincenzo Gianferrari Pini <vi...@praxis.it>.
Johannes,
The charset setting is inserted by the MUA preparing the message, not by James (the MTA). If your MUA is a java application using javamail, I noticed that there has been a change in javamail 1.3.1 compared to a previous release exactly in this area: if your text message has special characters (as accented letters etc), and the application does not explicitely set a charset (the one to use is charset="iso-8859-1"), then the new javamail sets it by default to Cp1252 and you may, as I did, encounter exactly the problems you mentioned.
The problem arose when I upgraded the javamail release.
I was using:
MimeBodyPart mbp = new MimeBodyPart();
StringBuffer sb = new StringBuffer();
...
if (isHTML != 0) {
mbp.setDataHandler(new DataHandler(sb.toString(), "text/html"));
} else {
mbp.setText(sb.toString());
}
and changed to:
MimeBodyPart mbp = new MimeBodyPart();
StringBuffer sb = new StringBuffer();
...
if (isHTML != 0) {
mbp.setDataHandler(new DataHandler(sb.toString(), "text/html; charset=ISO-8859-1"));
} else {
mbp.setText(sb.toString(), "ISO-8859-1");
}
Setting "-Dmail.mime.charset=ISO-8859-1" and "-Dfile.encoding=ISO-8859-1" as told in http://www.mail-archive.com/james-user@jakarta.apache.org/msg05393.html did solve the problem in one Windows machine where my MUA application was running (Windows 2k server Italian?), but non in another one (Windows 2k US) - I don't remember exactly the differences - so I implemented the code fix shown above, and the problem was solved.
Notice that James was not involved at all.
Hope it helps,
Vincenzo
> -----Original Message-----
> From: Robert J Taylor [mailto:rjamestaylor@cox.net]
> Sent: giovedi 22 gennaio 2004 0.01
> To: James Users List
> Subject: Re: James + Exchange Server 5.5
>
>
> Johannes Correa wrote:
>
> > //Message sent by Exchange
> > This message uses a character set that is not supported by the Internet
> > Service. To view the original message content, open the attached message.
> > If the text doesn't display correctly, save the attachment to disk, and then
> > open it using a viewer that can display the original character set.
> > <<message.txt>>
> >
> >
> > Reviewing the messages from past year and this year we found a little
> > difference between them: the initial header show "Content-Type: text/html;
> > charset="iso-8859-1"" instead of "Content-Type: text/html; charset=Cp1252"
> > of current messages.
> >
> >
> > Does anybody have some idea?
> >
>
> http://www.mail-archive.com/james-user@jakarta.apache.org/msg05393.html
>
> This should answer your question!
>
> Robert Taylor
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James + Exchange Server 5.5
Posted by Robert J Taylor <rj...@cox.net>.
Johannes Correa wrote:
> //Message sent by Exchange
> This message uses a character set that is not supported by the Internet
> Service. To view the original message content, open the attached message.
> If the text doesn't display correctly, save the attachment to disk, and then
> open it using a viewer that can display the original character set.
> <<message.txt>>
>
>
> Reviewing the messages from past year and this year we found a little
> difference between them: the initial header show "Content-Type: text/html;
> charset="iso-8859-1"" instead of "Content-Type: text/html; charset=Cp1252"
> of current messages.
>
>
> Does anybody have some idea?
>
http://www.mail-archive.com/james-user@jakarta.apache.org/msg05393.html
This should answer your question!
Robert Taylor
RE: James + Exchange Server 5.5
Posted by Jason Webb <jw...@inovem.com>.
I don't think this is a James problem because James is not interested
in:
Content-Type: text/html; charset="iso-8859-1"
I would look very carefully at any other updates you have done to other
parts of your infrastructure, particularly the code that renders the
HTML. JavaMail is responsbile for that header, so it must feel that is
the correct thing to do. This may be due to local machine configuration,
or , more likely, due to how your are constructing the MimeMessage.
I'm also surprised (and not at the same time) that Exchange server does
not support iso-8859-1, but then Exchange's SMTP support has always been
grim.
-- Jason
> -----Original Message-----
> From: Johannes Correa [mailto:johannes.correa@factoringmarket.com]
> Sent: 21 January 2004 22:21
> To: server-user@james.apache.org
> Subject: James + Exchange Server 5.5
>
>
> Hello everybody
>
> We are using a James+Jboss configuration to send some emails
> to our users. Our emails are constructed using a html
> template with some design and inside we put the different
> texts that are readed from an xml file.
>
> This schema worked fine last year but now we are getting the
> next message when some users receive mail from a Exchange
> Server (others users from hotmail or another servers don't
> have any problem):
>
> //Message sent by Exchange
> This message uses a character set that is not supported by
> the Internet Service. To view the original message content,
> open the attached message. If the text doesn't display
> correctly, save the attachment to disk, and then open it
> using a viewer that can display the original character set.
> <<message.txt>>
>
>
> Reviewing the messages from past year and this year we found
> a little difference between them: the initial header show
> "Content-Type: text/html; charset="iso-8859-1"" instead of
> "Content-Type: text/html; charset=Cp1252" of current messages.
>
>
> //Original header when it worked fine
> Received: from ntodd5.grupomun.com ([10.60.1.5]) by
> csm01.grupomun.com with SMTP (Microsoft Exchange Internet
> Mail Service Version 5.5.2653.13)
> id XH4Q8NN3; Mon, 1 Dec 2003 17:22:17 -0500
> Content-Class: urn:content-classes:message
> Received: from ils ([200.31.15.139]) by ntodd5.grupomun.com
> with Microsoft SMTPSVC(5.0.2195.5329); Mon, 1 Dec 2003 17:22:15 -0500
> Return-Path: [some-email-addr]
> Received: from 127.0.0.1 ([127.0.0.1])
> by ils (JAMES SMTP Server 2.1.3) with SMTP ID 60
> for [some-email-addr];
> Mon, 1 Dec 2003 17:22:15 -0500 (GMT-05:00)
> Message-ID: <30...@grupomun.com>
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> To: [some-email-addr]
> Subject: Activacion de cuenta, Sistema de comunicacion
> Inversiones Mundial
> MIME-Version: 1.0
> Content-Type: text/html; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Date: Mon, 1 Dec 2003 17:22:15 -0500 (GMT-05:00)
> From: [some-email-addr]
> X-OriginalArrivalTime: 01 Dec 2003 22:22:15.0843 (UTC)
> FILETIME=[933E2730:01C3B859]
>
>
> //Actual Header.. it doesn't work
> Received: from ntodd5.grupomun.com ([10.60.1.5]) by
> csm01.grupomun.com with SMTP (Microsoft Exchange Internet
> Mail Service Version 5.5.2653.13)
> id C9S5D0QZ; Wed, 14 Jan 2004 17:03:55 -0500
> Received: from ils ([200.31.15.139]) by ntodd5.grupomun.com
> with Microsoft SMTPSVC(5.0.2195.5329);
> Wed, 14 Jan 2004 17:02:04 -0500
> Return-Path: [some-email-addr]
> Received: from 127.0.0.1 ([127.0.0.1])
> by ils (JAMES SMTP Server 2.1.3) with SMTP ID 216
> for [some-email-addr];
> Wed, 14 Jan 2004 17:02:32 -0500 (GMT-05:00)
> Message-ID: <30...@grupomun.com>
> To: [some-email-addr]
> Subject: Activacion de cuenta, Sistema de comunicacion
> Inversiones Mundial
> Mime-Version: 1.0
> Content-Type: text/html; charset=Cp1252
> Content-Transfer-Encoding: quoted-printable
> Date: Wed, 14 Jan 2004 17:02:32 -0500 (GMT-05:00)
> From: [some-email-addr]
> X-OriginalArrivalTime: 14 Jan 2004 22:02:04.0197 (UTC)
> FILETIME=[0B38A550:01C3DAEA]
>
>
>
> Does anybody have some idea?
>
> Thanks a lot for ane advice
>
> Johannes Correa
> IT Developer
> FactoringMarket
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org