If you didn’t read the first part of this post then you might want to start reading from here. This post is the wrap-up. Previously: In order to eliminate Microsoft Exchange server idiosyncracies I ran a pure SMTP (client) to SMTP (server) test with the same (bad) results that Stefan had reported. This test although…
Sorry for the delay in getting back to this assignment note – if you didn’t read the first part you can read it here.
Previously: In order to eliminate Microsoft Exchange server idiosyncracies I ran a pure SMTP (client) to SMTP (server) test with the same (bad) results that Stefan had reported. This test although it failed, did narrow down the problem, indicating that the error, most likely, was not within the Microsoft Exchange server and originated at the client site.
Check to make sure that our domain is not blacklisted.
I went to http://www.anti-abuse.org/multi-rbl-check/ and ran a quick check on our company domain name and the external (internet) email server name both of which came up okay. So the company is not on a general blacklist. I also checked the AT&T blacklist site in case the client used AT&T as their ISP – we were also clean there. Stefan gave me a contact number at the client site which got me to their help-desk. After explaining the situation a couple of times to the folks on the help-desk who promised to open a ticket. I finally got a telephone call back two hours later, from their email administrator. The administrator insisted that they did NOT have any filtering rules or blocks setup against our domain and insisted that they did not subscribe to any Blacklist services that may for some reason have our domain (or IP address) listed. I faxed the admin the output of my tests including the test showing that the port was being closed by a server/firewall/router on their network as soon as we tried to establish a connection. I asked the admin to look into their configuration anyway, perhaps check with their network admins and to get back to me, meanwhile I went back to the drawing board.
Check for DNS, MX record, or mail server configuration problems
I went over to http://www.mxtoolbox.com and ran checks against OUR mail server and MX records verifying that everything on our side looked okay. I then ran the same tests on the client mail server, mail.bigcmailsrvr.com to verify that there are no obvious problems (from an email client perspective) on their end.
Mxtoolbox did not indicate any problems for either our domain or their domain.
Continue Reading »
When the email doesn’t go through
How email travels from your desktop in Brooklyn to your friend’s iPad in Toronto or even to your co-worker’s laptop, two cubicles away is not something that you probably spend too much time thinking about – unless you happen to be the system administrator or your in-box throws out a ‘undeliverable mail’ message.
I was wearing the ‘sysadmin’ hat for this particular company assignment and ended up learning something new while resolving an unusual undeliverable email problem.
……As is usual in these posts, the name of the various parties including the company names have been changed to protect guilty and innocent alike.
HTML5 is (almost) here and the warring camps are lined up for battle. Google, possibly one of the first players out of the gate with its Google Wave application service has been demonstrating some of the improved HTML5 features in Wave like dragging and dropping of photos. The photo effect did require a helper application,…
The Icann blog answered that question back in 2009, far more than I realized. I wonder what the count is now? I got started wondering about how many TLD’s existed because of the DNS SEC changes that begin tomorrow when they begin sending extended DNSSEC signature data in response to DNS queries – I’ve been…
Google just unveiled a strategy for universal printing over on its chromium blog. The technology ties in to the chrome browser but, it will go beyond that to (in Google’s words) allow printing from any web app:
“...design a printing experience that would enable web apps to give users the full printing capabilities that native apps have today. Using the one component all major devices and operating systems have in common– access to the cloud– today we’re introducing some preliminary designs for a project called Google Cloud Print, a service that enables any application (web, desktop, or mobile) on any device to print to any printer.” Continue Reading »
In my last article (part 1) I described the OOMA Logger application that I had running on my development machine, and I promised to make it available by deploying it to Heroku which is a cool service for deploying web based Ruby apps. The application is now live at http://oomalogger.heroku.com (nice name right!)
First off, I ran in to a couple of unforeseen problems like the fact that heroku apps are for all intents and purposes read-only (which meant for example, that I had to figure out the Nokogiri parsing problem and not use the file-system work-around hack that I had come up with).
One of the initial problems that come up with Ruby web application development is where do you host it? A lot of the general web-hosting sources don’t support Ruby unless you are on dedicated servers and roll-your-own environment. Heroku is an amazing service for Ruby developers that makes it drop-dead simple to deploy Heroku apps….
So far, I have been using OOMA (premier) for a little more than three months which means, based on my prior AT&T bills that it has just about paid for itself. It also means that every month from now on without a phone bill is money in my pocket free-is-good.
I’ve been busy over the last few days on a small Ruby programming project. I’m somewhat new to Ruby, but not to programming. I was looking for a project to help me bring some of the Ruby concepts together – while there are some great Ruby tutorials and books available you can’t really learn to program in a language until you actually start to write code. Continue Reading »
Having problems with keeping your OOMA phone system connected? Before you blame OOMA, the problem could lie with your ISP. Fortunately, the fix is relatively easy. The OOMA hub and scout units have a tab indicator that show at a glance when the device is working correctly. A blue tab indicates that the box is…