RE: James SMTP routing

[Vi...@nokia.com]

Hi again,

We'll implement this this solution (a RemoteDelivery mailet per routing rule).

Do you have any experience regarding the optimum number of threads per RemoteDelivery mailet and maximum number of global RemoteDelivery threads for production usage?

Thanks for your help,
Vincent.

> -----Original Message-----
> From: Stefano Bagnara [mailto:io@bago.org]On Behalf Of ext 
> Sent: Thursday 26 May 2005 15:09
> To: 'James Users List'
> Subject: Re: James SMTP routing
> 
> 
> > I would like to setup james so that it relays incoming 
> > messages according to the recipient. I also need a default 
> > rule to relay messages to unknown domains to a default relay.
> >
> > I can't find documenttion about this. Any idea?
> 
> Hi Vincent,
> 
> Can you provide better information?
> 
> Do you need something like this?
> 
> domain1.com => gw1.yourgateway.com
> domain2.com => gw2.yourgateway.com
> domain3.com => gw3.yourgateway.com
> Other domains => smarthost.yourdomain.com
> 
> If you need this then I think you need to subclass 
> RemoteDelivery mailet to
> add this behaviour.
> 
> If the known domain are only a few you can fallback to this:
> 
> <mailet match="IsRecipient=*@domain1.com" class="RemoteDelivery">
>   <outgoing> db://maildb/spool/outgoing1 </outgoing>
>   <gateway>gw1.yourgateway.com</gateway>
> </mailet>
> 
> <mailet match="IsRecipient=*@domain2.com" class="RemoteDelivery">
>   <outgoing> db://maildb/spool/outgoing2 </outgoing>
>   <gateway>gw2.yourgateway.com</gateway>
> </mailet>
> 
> <mailet match="IsRecipient=*@domain3.com" class="RemoteDelivery">
>   <outgoing> db://maildb/spool/outgoing3 </outgoing>
>   <gateway>gw3.yourgateway.com</gateway>
> </mailet>
> 
> <mailet match="All" class="RemoteDelivery">
>   <outgoing> db://maildb/spool/outgoing </outgoing>
>   <gateway>smarthost.yourdomain.com</gateway>
> </mailet>
> 
> Consider that every remoteDelivery will instantiate its own 
> delivery threads
> (add <deliveryThreads> 5 </deliveryThreads> to each block).
> 
> I would use this solution only with few custom gateway. IMHO too many
> RemoteDelivery will bloat your configuration and your runtime 
> environment.
> 
> 
> Stefano
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

Re: James SMTP routing

[Stefano Bagnara <ap...@bago.org>]

> We'll implement this this solution (a RemoteDelivery mailet 
> per routing rule).
> 
> Do you have any experience regarding the optimum number of 
> threads per RemoteDelivery mailet and maximum number of 
> global RemoteDelivery threads for production usage?

How many mails is your server going to handle per hour?
You can try 5 threads for each RemoteDelivery and increase them if the spool
grow too much.

I use 40 threads in my RemoteDelivery to handle about 20000 mails/hour.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org