Exchange 2003: Use both direct delivery and pop3
I'm finally at the point where a SBS2003 network need to use Exchange for direct delivery of incoming mail. Nowadays it used pop3-connector to recieve mail from a webhosting company.
In this fascinating spam-world this causes a lot of error because mail are sended through another host than it first was recieved from..
This pop3-connector is big enough that I can't handle and control the risc of loosing delivery of incoming mail. I want to have the pop3-connector behave just like normal while Exchange operating just normal with direct delivery. How do I do?
I understand that I could,
1. Set our external IP as lowest MX record 10, then use the webhostings e-mail MX as 20. Which will carry the mail if our exchange server not responding.
2. I need to SAT/NAT/Accept open port 25 for incoming traffic in the firewall?
3. What do I (best practic/basic) need to do for security in this case of direct delivery, that our webhosting doing automatically today?
4. If I run the CEICW and select the Exchange for direct delivery, is pop3-connector still working as usual (if it got any mail from the webhosting)
In this fascinating spam-world this causes a lot of error because mail are sended through another host than it first was recieved from..
This pop3-connector is big enough that I can't handle and control the risc of loosing delivery of incoming mail. I want to have the pop3-connector behave just like normal while Exchange operating just normal with direct delivery. How do I do?
I understand that I could,
1. Set our external IP as lowest MX record 10, then use the webhostings e-mail MX as 20. Which will carry the mail if our exchange server not responding.
2. I need to SAT/NAT/Accept open port 25 for incoming traffic in the firewall?
3. What do I (best practic/basic) need to do for security in this case of direct delivery, that our webhosting doing automatically today?
4. If I run the CEICW and select the Exchange for direct delivery, is pop3-connector still working as usual (if it got any mail from the webhosting)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
TYPE HOST DATA
MX domain.com. 20 mx.domain.com.
A mx.domain.com. <external ip>
MX domain.com. 20 mx.domain.com.
A mx.domain.com. <external ip>
If you maintain the POP3 accounts then you have to maintain two sets of accounts. It would be more efficient to drop the POP3 accounts completely by removing the web host from the MX records and then waiting at least 48 hours before doing anything with the POP3 mailboxes.
As for being able to tell if the POP3 connector is receiving email, all you could do is turn on logging on the connector and then look in the event viewer of the server to see how many emails are downloaded for each user.
Simon.
As for being able to tell if the POP3 connector is receiving email, all you could do is turn on logging on the connector and then look in the event viewer of the server to see how many emails are downloaded for each user.
Simon.
ASKER
Thank's, I know it twice the job to set up mail boxes.. ;).
So.. I leave my new nice mx record and deactivate that points to the web hosting company. After a few hours/days the e-mail will going stright to the exchange.. In theory, when dns is activated, i should be able to send mail (from an external host) to a exchange connected SBS user that before only could recieve internal mail (because it has no account in sbs connector)?
So.. I leave my new nice mx record and deactivate that points to the web hosting company. After a few hours/days the e-mail will going stright to the exchange.. In theory, when dns is activated, i should be able to send mail (from an external host) to a exchange connected SBS user that before only could recieve internal mail (because it has no account in sbs connector)?
ASKER
I asking extra ordinary because I can't sit there in about 48 hours to understand that my exchange server rejecting all messages and have no backup through the pop3 connector..
ASKER
Do I need to understand something about this, that are stored in my web hostings dns table?
TXT domain.com. v=spf1 a mx
TXT domain.com. v=spf1 a mx
As long as the user accounts are valid in Exchange, then Exchange will accept the email. However during the propagation period you cannot control which server a remote server will send email to. It may send it to your web hosting company, it may send it to your Exchange server. Therefore it will be 48 hours before you can guarantee that all email is delivered to your Exchange server and email addresses not on the POP3 connector work for external senders.
That DNS record is an SPF record and should be updated to include your server.
There are instructions on how to change it on the SPF web site here:
http://www.openspf.org/
or at Microsoft here: http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/
Simon.
That DNS record is an SPF record and should be updated to include your server.
There are instructions on how to change it on the SPF web site here:
http://www.openspf.org/
or at Microsoft here: http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/
Simon.
ASKER
Everything is transferred to exchange server and seems to works just fine! Next stop is installing antispam software for extra protection. Thank's a lot. I will start a new exchange-related question.
ASKER
Thank's for answer. The port is now open. the TARPIT and recipient filtering is (as i know) untouched. However I know that our Exchange is answering with no mailbox and out of office responders. I will check your link.
I need to use pop3 connector to be sure that no message are being recieved that way. I'm not sure how to check if the e-mail are recieved through our exchange or through pop3?
Is there possible to check if I create a mailbox in exchange that does not exist on the webhosting?