This question is somewhat related to this thread - http://support.jodohost.com/showthread.php?t=1685&page=3
I was wondering if the following idea would work. I have a DSL line at home with no ports blocked. My ISP alllows me to run servers (within reason), so I am not breaking my TOS. I have a dynamic IP address. Can I use something like DynDNS to setup my domain, install an SMTP server, and send my mail using my own server?
I would not be sending spam. I would only be sending my own personal mail. A few messages a day.
I know that technically this will work but was wondering what kind of defenses companies and providers have in place to catch what they believe to be sources of spam. I'm thinking that they may look at the IP block of my DSL line and consider it a dynamic IP block and therefore block my messages. But, I believe my IP has a reverse lookup that refers back to my ISP's domain (something like PORT245-MYISP.COM).
Any thoughs on this? I would of course make it require authentication and maybe even move it to a different port other than 25 to try and prevent others from hacking into it and using it to send spam.
I may try this just for the fun of it, but don't want to mess with it if it is going to cause me more problems than it will help.
I was wondering if the following idea would work. I have a DSL line at home with no ports blocked. My ISP alllows me to run servers (within reason), so I am not breaking my TOS. I have a dynamic IP address. Can I use something like DynDNS to setup my domain, install an SMTP server, and send my mail using my own server?
I would not be sending spam. I would only be sending my own personal mail. A few messages a day.
I know that technically this will work but was wondering what kind of defenses companies and providers have in place to catch what they believe to be sources of spam. I'm thinking that they may look at the IP block of my DSL line and consider it a dynamic IP block and therefore block my messages. But, I believe my IP has a reverse lookup that refers back to my ISP's domain (something like PORT245-MYISP.COM).
Any thoughs on this? I would of course make it require authentication and maybe even move it to a different port other than 25 to try and prevent others from hacking into it and using it to send spam.
I may try this just for the fun of it, but don't want to mess with it if it is going to cause me more problems than it will help.