You should be able to confirm that the problem is the mail being
received multiple times looking at the smtpserver logs.
You should also find exceptions thrown from the the smtpserver while
accepting new messages.
Can you post a few "duplicate" mail headers (se that we can confirm your
ideas) and look in the logs for any exceptions?
1000 messages per hour is not a big deal for james.
Have you ever personally experienced the "resend" behaviour from your
email client?
The db pool running out of connections could be for sure a contributing
factor. The SMTP protocol ensure that a message is delivered at least once.
You could try to fine-tune your db pool configuration. You could
increase the "max" number of connections or increase the "max_wait" time
it waits for a connection to be returned before failing.
----- e.g:
<max_wait>60000</max_wait>
<max_idle>5</max_idle>
<max>20</max>
-----
Server connections + Spool threads + Delivery threads all need db
connections so you should tune your db pool size starting from that numbers.
Stefano
Nathan Cheng wrote:
Judging from the email headers, when any sending SMTP client--user or
server--attaches to our James SMTP server to pass along an email, it
will think it didn't get through the first time, and send it again a few
seconds or a few minutes later. This cycle usually happens more than
twice, and like I said occasionally up to 50 times. What could James be
doing that would make SMTP clients think that James didn't get the
message when in fact James did get the message?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
