You can add a <bounceProcessor> to your RemoteDelivery configurtation.
We confiugure it by default in 2.3.0

Stefano

Shal Jain wrote:
James version 2.2.0
Win 2K3 server
JDK 1.4.x

Under the transport processor - in the remote delivery mailet
is there a way to specify that any messages that don't get delivered
after the max # of retries get sent to a special named folder and so don't
end up cluttering the outgoing repository.

As of last 2 weeks our James server is being hit by vast amounts of spam
(working on putting a barracuda box infront of James)
Since the targeted users for the handled domains don't exist,
James tries to do a bounce back which mostly fail and then
the emails end up staying in the outgoing folder
Since the last two weeks we are seeing about 5000 entries in the outgoing
repository.  What's also occuring is that lot of the valid msgs are
not being delivered. I am assuming that the server is being overwhelmed

I have shortened maxretries to 3
for now and increased the delivery thread count up just to see if
this will help.  Am I on the right track or is there a different way
to solve this.

If the solution is involved, I'd be willing to discuss w/ one of the developers
about a short term contract. I'm currently short handed and in need of
an immediate fix.

Thanx


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

Reply via email to