email server Email Server on a Dynamic IP

[pierre626]

Hey all,

Basically looking to replace my Google Apps accounts with an on Prem Exchange 2013 box at home. I understand that most of my mail would be bounced due to running on a Dynamic IP.

Anyone recommend any decent services that will forward my mail on to a Dynamic IP? (With the ability to store mail in case of server outage if possible)

Thanks for your help!

[+virtorio MVC]

There are plenty of Dynamic DNS services that'll do what you want (http://en.wikipedia....iki/Dynamic_DNS, http://dnslookup.me/dynamic-dns/).

I can't recommend an actual service however as I haven't had much experience with them.

[+BudMan MVC]

He is asking for more than just dynamic dns services, this is what it sounds like what he wants

http://dyn.com/email/dyn-email-backup-mx/

We offer backup queuing for unexpected downtime on a main MX server for 10 days, storing and forwarding when you're ready.

So basically they are a secondary MX record for your domain, with a lower priority than your main MX. So if your down, others would send to this MX, they will then store the mail until your primary MX record is back online - and then send you the mail to your primary mx.

So you do understand from this statement

"most of my mail would be bounced due to running on a Dynamic IP."

That you will not be able to send mail to the major players right - yahoo, gmail, hotmail, etc.. Most all of them will not accept mail from a dynamic IP listed IP.

Connected to mailin-03.mx.aol.com.

Escape character is '^]'.

554- (RTR:DU) http://postmaster.info.aol.com/errors/554rtrdu.html

554 Connecting IP: 24.13.xx.xx

554 RTR:DU[/url]

• AOL uses the Spamhaus PBL to block mail from dynamic and residential IP addresses. Per our E-mail Guidelines, we do not accept mail from such addresses. If you believe your IP is listed in error, please contact your ISP directly and have them update their listing with the PBL. If...
  
  • your ISP reports that the IP is correctly listed in the PBL, and that you should be able to send mail from it, or
    
  • you were recently assigned IPs, have changed the rDNS on them, and allowed 48-72 hours for propagation time...and you are still getting the error, please open a support request.
    

Now if your going to go with a backup MX service - might as well go with a delivery service as well ;)

http://dyn.com/email/dyn-standard-smtp/

They also mention in the above link the other reason you can not send mail to major players from a home/dynamic IP - your not able to set the rDNS (ptr) Many major players don't accept mail from them either.

DNS Blocks

• 554 DNS:B1
  
• The reverse DNS

of your IP Address is typical of a dynamic/residential IP Address. Please have it updated to something unique like mail.example.com, or use the mail servers your ISP provides for residential customer traffic. If the rDNS has been updated and the problem persists, please open a support request.

• rDNS must be in the form of a fully-qualified domain name. rDNS containing in-addr.arpa are not acceptable, as these are merely placeholders for a valid PTR record. rDNS consisting of IP addresses are also not acceptable, as they do not correctly establish the relationship between domain and IP address.
  
• rDNS that may be similar to dynamic IP space (containing pool, dhcp, dyn, etc.) may be treated as suspect, and should therefore should be changed to reflect a fully-qualified domain name with standard reverse DNS.
  

[*]554 DNS:B2

• The reverse DNS of your IP Address is typical of a dynamic/residential IP Address and has generated AOL Member complaints. Please have it updated to something unique like mail.example.com, or use the mail servers your ISP provides for residential customer traffic. If the rDNS has been updated and the problem persists, please open a support request.
  
  • rDNS must be in the form of a fully-qualified domain name. rDNS containing in-addr.arpa are not acceptable, as these are merely placeholders for a valid PTR record. rDNS consisting of IP addresses are also not acceptable, as they do not correctly establish the relationship between domain and IP address.
    
  • rDNS that may be similar to dynamic IP space (containing pool, dhcp, dyn, etc.) may be treated as suspect, and should therefore should be changed to reflect a fully-qualified domain name with standard reverse DNS.
    

[*]421 DNS:NR

• The Reverse DNS lookup for your IP address is failing. This could be a transient issue. Confirm the IP that sends your mail. Then check the rDNS of that IP using our troubleshooting tools. If it passes, please wait 24 hours and re-try before opening a support request.
  
  • rDNS must be in the form of a fully-qualified domain name. rDNS containing in-addr.arpa are not acceptable, as these are merely placeholders for a valid PTR record. rDNS consisting of IP addresses are also not acceptable, as they do not correctly establish the relationship between domain and IP address.
    
  • rDNS that may be similar to dynamic IP space (containing pool, dhcp, dyn, etc.) may be treated as suspect, and should therefore should be changed to reflect a fully-qualified domain name with standard reverse DNS.
    

Now if all you want to do is accept incoming mail, and not be able to respond or send to major domains, or any domain that uses standard filtering practices.. Sure go right ahead and run your own email server.. Have fun securing from being an open relay, fighting spam, etc

[pierre626]

Thanks a lot for the hefty response BudMan, thats the exact thought of thing I was looking for :)

If I'm not mistaken, I've got access to an SMTP server to relay with (Through One and One) so was just planning on setting up a send connector within Exchange for that (Correct me if I'm wrong?)

The main thing I was worried about was receiving incoming mail on a Dynamic IP.

Thanks again for all your help!

[+BudMan MVC]

If you going to use a smart host for sending, then you should be fine. Still have to worry about being an open relay, spam though if your going to be accepting email on your dynamic.

Here is the thing, maybe your isp is different - but I am on a dynamic, and been same for years at a time. Unless you go offline for extended period, days! You should just keep renewing the same dhcp lease. Unless you change your mac of the device your isp dhcp server sees there should be no reason your ip should change.

Now that I am running my router in vm, I have its mac set to specific one. I can change over to any VM instance as my router and as long as use that same mac I have the same public IP, etc.