<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d16851663\x26blogName\x3dBurton+Speaks\x26publishMode\x3dPUBLISH_MODE_HOSTED\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://www.walkingsaint.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://www.walkingsaint.com/\x26vt\x3d-1892815651864643552', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Hidden from sight

Wednesday, August 06, 2008
Behind-the-scenes changes are going on here in terms of domain services and the like. The astute reader might remember that I've accumulated a small collection of domains: WalkingSaint.com, BurtonSimmons.com, BurtonSimmons.info, and more. While I have web pages at all these domains, other services (such as mail) haven't always been fully functional. In the last week or so I've been changing that.

Probably the biggest change is the switch from self-hosting of email services to using Google Apps for email (and other services). This allows me to have the Goog do my spam filtering (which is good) but also use them as a trusted sender. Self-hosting my mail server means that, since at some point it's just on a consumer cable modem, many larger email providers won't accept mail from it because they think it's spam. Irritating, but this gives me a way around it.

The downside to this is that I have a lot of little devices that send email: firewalls, servers, etc., and they aren't necessarily "smart" enough to play well with Google's email service. Still trying to figure that one out (and why it's happening, since I don't exactly get rich error messages from these devices.

So those are some of the changes that are happening. More are going to be coming down the pipeline - some of which will simplify my life, some of which might improve the reader experience, but all of which will probably be long overdue. Stay tuned!


Blogger Jake said...

We use google apps here at the office, and ran into that in a few codebases, specifically the SSL requirement for SMTP (this was more of an issue on Windows IIS codebases -- the linux-based stuff was easy to work with). But most of the times, the oddball port numbers can just be appended on to the IP address (xxx.xxx.xxx.xxx:465) and it'll just work -- assuming your code authenticates you.

That being said, this little bit of code was handy on both windows and linux:


Basically, it's just a relay service program. You can run it on any server (we just run it localhost) and then change your code to SMTP to the local host. Then setup emailrelay to forward that mail onto gmail's servers, using the login/pass you setup for the account you want as the reply-to.

10:57 AM, August 12, 2008  

Post a Comment

<< Home



Twitter Updates

My Other Sites

Site Information

Friend Blogs

Awesome Links

Favorite Webcomics

Previous Posts


Powered by Blogger