• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

configuring mail to pass through a filtering server with exim

Hi,  I'm having a email server issue

what I'd like to do:
my company's domain is xyz.com
we have a mail server (Exchange 2003) whose address is mail.xyz.com
we also have an external server running redhat and exim (it has a static ip address of 123.45.67.89 and a nameserver of ns1.xyz.com)

I'd like to have all email from external domains to first pass through the exim server and then be forwarded on to mail.xyz.com

my understanding is that I should do the following but I'd like some type of verification before I go messing with the system:

1. change mx records so that the highest priority name-server is ns1.xyz.com
2. change the mx records so that mail.xyz.com is the second highest priority
3. modify exim to accept emails that are addressed to *@xyz.com (this presumably is done by modifying the exim.conf file to have relay_hosts accept mail addressed to *@xyz.com)
4. have exim forward those mails to mail.xyz.com

My questions are

1. are these steps accurate?  or is there another/simpler/more correct way?
2. how is step 4 accomplished?  i.e. how do I get exim to funnel emails to our main mail server after it receives them?
3. again, there might be a better way...I *think* steps 1-3 are correct (from reading exim docs), but I'm not sure how 4 is accomplished.

Thanks!
0
pdanese
Asked:
pdanese
  • 2
1 Solution
 
jar3817Commented:
Those steps will work fine. Keep in mind that the "highest priority" is the lowest number when dealing with MX records.

I have no idea how to do #4 with exim, but it's cake with sendmail: just add the domain and the destination server to the /etc/mail/mailertable file. If you're not married to exim that might be easier.
0
 
pdaneseAuthor Commented:
thank you!
0
 
jar3817Commented:
addition thoughts, do your self a favor and change the time to live (TTL) on the dns records you're going to change to a very low number (300 or something like that) a day or so before you actually make the record changes so it only takes 5 minutes or so for the changes to propagate. That way if you make a mistake you can fix it and not have to wait a day while your email bounces. A day or so after you're sure it's all working, move the TTLs back up.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now