I think this bug is resulted in my contributed code :P
Because some messages lack of a MIME header of "Charset",
my contributed code simply crashes in looking up a null character encoding.
It was fixed on my server just one week after I submitted the code.
but I've not yet download JAMES 1.2.1 to apply a patch in it.
In this fix, my code read a default encoding attribute from the
configuration node of
SMTP handler in conf/JAMES.conf.xml, if the default encoding attribute
doesn't
exist in the xml file, then it's supposed to be "ISO-8859-1".
I will post a URL to the patch later.
Indeed, I installed CVS, but....it never works as it should be.
Not knowing why. So unfriendly. :-(
----- Original Message -----
From: "Oki DZ" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 15, 2001 4:04 PM
Subject: Serious bug
> Hi,
>
> Has anyone encountered the empty Subject: line bug?
> Recently one of my users sent out an email without entering a subject
> line; the message got stuck in the spool, and got duplicated many times.
> Then I tried it myself (sending a message to me); the message got
> duplicated into 13 times, and the state was "transport."
>
> I think this is pretty serious; we couldn't guarantee that all the users
> send out all their messages with proper headers, and I think it is the
> responsibility of the mail servers to handle all those "various" inputs.
>
> BTW, I use James 1.2.1 and MySQL.
>
> Oki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
