Hi again, I've setup James as a relay server. It is not directly connected to internet and hence uses a gateway. Because I have no internet access and uses a gateways I don't have access to a DNS server.
I've found that for every mail it relays, james tries to lookup the recipient's mail address FQDN (hostname) with a DNS query to localhost. This cause James to log errors, delay mails processing and even (rarely) lose some mails. I wonder how I could setup james so that not to send any DNS query? Thanks for your help, Vincent. I've found that for every mail relayed by James a name lookup query is sent to localhost (I did not set a valid DNS sever since I don't have I've setup this configuration and now face another issue: james is trying to resolve the domain name of the outgoing mails. Since I use a gateway, I don't have access to any DNS server able to resolve the domains of the outgoing mails. Sample: I'm running james on smtp.mydomain.com with this kind of RemoteDelivery: <mailet match="All" class="RemoteDelivery"> <outgoing> db://maildb/spool/outgoing1 </outgoing> <gateway>192.168.1.10</gateway> </mailet> James don't have access to any DNS server. When I send a mail to [EMAIL PROTECTED] James tries to resolve somewhere.com causing james to log error messages and delay mail processing in some cases. > -----Original Message----- > From: Stefano Bagnara [mailto:[EMAIL PROTECTED] 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="[EMAIL PROTECTED]" class="RemoteDelivery"> > <outgoing> db://maildb/spool/outgoing1 </outgoing> > <gateway>gw1.yourgateway.com</gateway> > </mailet> > > <mailet match="[EMAIL PROTECTED]" class="RemoteDelivery"> > <outgoing> db://maildb/spool/outgoing2 </outgoing> > <gateway>gw2.yourgateway.com</gateway> > </mailet> > > <mailet match="[EMAIL PROTECTED]" 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
