----- Original Message -----
From: "Bryan Waters" <[EMAIL PROTECTED]>


> 1) what sort of message volumes can james handle? I know this is dependent
> on a lot of issues like hw, bandwidth,etc, but all other things being
equal,
> how does James stack up?

Completely dependent on the size of the messages.  James slows down
exponentially based on message size (especially when storing messages in a
database)

> 2) is it robust?  Is anyone using it for mission critical apps?

I've been using 1.2rc1 as our main mail server for our company and a few
clients.  Except for the size problem, it works very well.

> 3) I want to set it up as a mail forwarding service for about 50 domains.
I
> thought I would create a modified Forward mailet that used a database to
> perform the address translation...am I missing anything?

Check out the TownAlias mailet... it's a crude version... checks a 2 column
table that basically just rewrites mail addresses.  There is one bug in it
though in that it fails gracelessly when you're rewriting to an address that
the message is already going to, e.g., if a message is sent to [EMAIL PROTECTED]
and [EMAIL PROTECTED], and TownAlias wants to rewrite [EMAIL PROTECTED] to [EMAIL PROTECTED]
(just for example), then TownAlias will fail because [EMAIL PROTECTED] is already a
recipient.  Should be simple to fix though.

Serge Knystautas
Loki Technologies
http://www.lokitech.com/


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

Reply via email to