On 25.07.2008, at 10:50, Stefano Bagnara wrote:
zkn ha scritto:
On 25.07.2008, at 10:12, Stefano Bagnara wrote:
With many mails the db based spool repository is much better.
Change of processor is done by updating few fields in a db record.
Stefano
Thanks Stefano.
Now when we have so many files in the file system is it still
possible to switch to db spool and would that help processing these
emails faster?
I say it would be much more fast, but it highly depends on your
system setup.
In order to move mails the only solution with james 2.3.1 is to move
it to db and then use the FromRepository mailet to retrieve mails
from the file repository to the spool repository.
I'm not sure but it seems to me that if I use FromRepository I will
loose new emails. The mailet is triggered by a new email and then it
starts retrieving emails from the repository to the spool. And the
original email is GHOSTed.
Is that correct?
Also what would happen to the mail server if the db server is down
for any reason? Would JAMES continue to accept emails?
Good question. The current behaviour is that James will save them in
a temp folder and then will fail accepting the mail. The sender will
receive an error so it will have to retry sending later.
Stefano
---------------------------------------------------------------------
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]
