I am using a similar configuration. In the second server I create a cmdalias tab file in cmdaliases/domain directory for every true email of first server with "smtprelay" command to first server. Bye. Sergio bh
Da: Davide Libenzi <[email protected]> Per: XMail Users Mailing List <[email protected]> Cc: [email protected] Data: 29/12/2008 20.30 Oggetto: Re: [xmail] spam filtering using CustMapsList and a custom domain (custdomains) On Mon, 29 Dec 2008, Gilad Odinak wrote: > I have two independent xmail servers in two physical locations, each hosting a > single domain. The second server is also configured to relay emails received > for the first domain to the first server. Finally the MX records of the first > domain contain two entries: the first entry points to the first server and > second entry points to the second server. > > Thus, emails for the first domain normally go to the first server, but if it > is not reachable they go to the second server, and it forwards them to the > first server. emails for the second domain are only processed by the second > server. > > Both servers are configured to use CustMapsList, with a delay of 3 seconds > from email from suspected sources (i.e. "CustMapsList" "zen.spamhaus.org:-3") > That effectively cuts out all spam... except for spam sent to the first domain > through the second server. With -3 you're not going to cut SPAM. I suggest you use 0 or 1 instead. I'd also suggest to use GLST (greylisting) to help with SPAM and Worms/Viruses. CustMapsList works before routing decisions are taken, so the problem you're seeing is not due to CustMapsList. > My hypothesis is that email send to a custom domain at the second server is > immediately relayed to the first server without checking. At the first server > the source of the email appears to be the second server and thus is not > rejected. > > Is the above correct and is there a workaround? Your setup is fine, but the problem is not what you think. When using a setup like yours, the second domain has no way to know which users are valid for the first domain, so it blindly accept emails for all users of the first domain. IMO the best option to perform a secondary MX setup, is to replicate master domain users into the slave server, and put a single domain global mailproc.tab with an smtprelay to the master server. - Davide _______________________________________________ xmail mailing list [email protected] http://xmailserver.org/mailman/listinfo/xmail ______________________________________________________________________________ --- NOTICE --- This email and any attachments are confidential and are intended for the addressee only. If you have received this message by mistake, please contact us immediately and then delete the message from your system. You must not copy, distribute, disclose or act upon the contents of this email. Personal and corporate data submitted will be used in a correct, transparent and lawful manner. The data collected will be processed in paper or computerized form for the performance of contractual and lawful obligations as well as for the effective management of business relationship. The data processor is Telsey S.p.A. The data subject may exercise all the rights set forth in art. 7 of Law by Decree 30.06.2003 n. 196 as reported in the following url http://www.telsey.com/privacy.asp. ______________________________________________________________________________ 798t8RfNa6Dl8Ilf _______________________________________________ xmail mailing list [email protected] http://xmailserver.org/mailman/listinfo/xmail
