Hi All, Here is the situation.
We have two locations, X and Y which are geographically far apart. At X, we run a courier mail server, and at Y, we run a CRM software. This software polls the server at X using POP3. This CRM software's POP client is buggy I guess - every now and then the client goes to sleep eating up CPU cycles and bandwidth without actually achieving anything. So, we have decided to have a server at location Y itself, so that the POP transaction will at least be over ethernet. There is a further complication that the MX of all the domains (or rather, the entry point of all emails into our control) has to be hosted at location X. There are a large number of domains configured on the server at X - we want the mails that arrive at X to be pushed to another server at Y (which will also run courier). What I want to try is: For each domain xyz.com, the courier server at X (X server) will have an entry in esmtpacceptmailfor and esmtproutes. The server at Y (Y server) will have the same domain in esmtpacceptmailfor, hosteddomains and will have user accounts configured. Also, MX entries for xyz.com will have the Y server at higher priority. But Y server will also have ipchains rules to REJECT all traffic on port 25 unless it originates from X server. Is my approach fine? Any better, cleaner way (basically, without resorting to ipchains) of achieving this? I don't want to experiment since both X and Y servers are in production, and this CRM system is my employer's lifeline (it was moved from Exchange to Courier at my insistence ;) Any suggestions will be appreciated. TIA, Binand ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
