We have been using James for over a year to provide email to our customers. Off 
and
on we have had really bad problems that we have been able to deal with by either
upgrading to the latest James or tinkering with the config.xml for several 
days. We
now have several hundred users who depend on our email to run their day-to-day
businesses, and James has once again started to fail miserably. We do not have 
time
any more to tinker around in the dark with config.xml.

We need help from someone who knows James much better than whoever wrote the
documentation knows James. Please help.

If you are qualified, please contact me by email at [EMAIL PROTECTED]

Here are the symptoms:

As of early Friday morning James had been working fine for a couple months, 
sending
and receiving on the order of 10's of thousands of emails per day. Then 
something
happened. I don't know what happened. It may have been that were several 
hundred more
messages sent than usual. But anyway, something happened, and James decided not 
to work
any more. It would allow POPping about 50% of the time, it would claim to fail 
when
sending an email through SMTP, but then about 25% of the time actually send the 
message
several hours later. It continued like that throughout the weekend. After 
fiddling with
it for a while today, and blocking our web application from reaching the mail 
server
using iptables (so that only people using their own email clients could access 
it),
I actually got it to send several thousand spooled emails over the period of 
about an
hour. Then, without warning, it stopped again--with about 6000 emails left in 
the
'root' message_state and 11 in 'transport'. Our web application has another 
1000 mails
or so queued up that it's trying to send (but can't thanks to iptables). So 
we're behind
about 7000 emails and we've got several hundred angry clients.

As I said, please help.

Thank you,

Nathan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to