We have finally moved James into production and we are seeing a lot of
emails gathering in the outgoing directory and not getting processed.
Does anyone know what we can do limit the number of messages gathering
in the outgoing directory and never getting sent? Right now I did a
'find | wc -l' and
A fix for this seems to be to add:
message.saveChanges();
immediately after both calls:
message.setContent(multipart);
in the service method of CommandListservFooter.
I'm not a javamail expert, but from the javadocs it looks like you should
call this whenever the
I've just been hit by this bug trying to set up mail servers which WILL be
using html emails.
Anyway, it seems that it is dropping the content-type headers:
Content-Type: multipart/alternative;
boundary="=_NextPart_000_0022_01C520B7.E185E640"
is in the original, but vanished in the l
It is Debian Sarge.
We have two boxes with Debian Sarge and it is only one of them that has too
many java threads/proccesses.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 4. mars 2005 09:31
To: James Users List
Subject: RE: Too many java processes
> Those
Not sure what you're trying to do (and I might have got totally the wrong
end of the stick!), but James is a mail server! sure you can create html
messages within a James mailet, or you can send html emails through it like
any other mail server but I think what your looking for is javamail, or
> Those are threads. You are probably using an older kernel.
rather old psutils then kernel.
psutils that does not support threads (the -m parameter)
ps: first guess would be debian-woody.
-
To unsubscribe, e-mail: [EMAIL PROTE
