So you’ve composed an email, and now it’s time to send it, but for some reason the email seems rather reluctant to go. Whilst I’d love to be able to claim that the MyOffice Outbox is just so homely and inviting that the email is reluctant to leave it, I can’t. It’s a rather stark place, devoid of scatter cushions, and the coffee machine’s been out of commission for years. Quite frankly, any emails in there are desparate to get out and get on with their journey, but something’s preventing them. Let’s have a look at what that might be.
Send Failed for message X of Y - Send Failed - DNS Error GetHostByName
Quite simply, the outgoing email server (SMTP) address is wrong. MyOffice has attempted to look up the name you’ve entered, and internet’s equivalent of the telephone directory has come back with “sorry, there’s no-one called that in here”. Your best bet now is to make sure you’ve entered the correct SMTP server address in the email account.
Send Failed for message X of Y - Send Failed - Error connecting to server mail.somedomain.com
If you’ve read my first post on email error messages, you may well remember the incoming mail server (POP3) equivalent of this has a whole series of potential meanings. So as to save you the pain of having to dig about for that post, I’ll recap them here.
The message itself means “I’ve looked where you told me to look, and I couldn’t see an SMTP server”. Discounting the Extremely Obvious (i.e. your net connection’s just gone down), there are four pretty common reasons why you’ll see this message.
Firstly, and perhaps most commonly, is an incorrectly entered outgoing mail server address or port. In short, this leaves MyOffice trying to talk to the wrong thing. If you’ve never been able to send email via the email account in question, this is a good place to start if you see this error message, so it’s best to check your outgoing mail server address and port at this point. If you’re still having trouble, then we can pretty much rule this one out, and it’s on to the next possibility.
Probably the next most likely cause of a failure to contact the outgoing mail server is “something” blocking the connection. In practice, this is most likely to be a software firewall installed on your PC. Software firewalls have come a long way in the last five years, but every so often we come across one that gets a little over-zealous in what it blocks. If you’ve got a software firewall installed on your PC, you’re seeing this error, and you’re sure you’ve got your outgoing server address and port correct, then it’s well worth having a look at the settings on your firewall to see if it’s that getting in the way of things.
The final very common (judging by our support records, at least) situation is that in which “something’s changed”. If you’ve been merrily sending email using an account, and that account’s suddenly decided it doesn’t want to play any more, the chances are this is it.
Top of the list of likely candidates for “changing” is your software firewall. When fiddling with the settings, it’s quite easy to accidentally change something and accidentally end up blocking a program from accessing the bits of the net it needs. Furthermore, software firewall providers have a habit of issuing regular updates for their products, and these can sometimes result in programs being blocked by accident. Make no mistake, these updates are Very Good Things Indeed - they mean your firewall provider’s on the ball, or at least trying to get there - but they can have the odd unforseen consequence. So, if you find yourself suddenly unable to send email on a given account, best give the firewall a quick check.
The next mostly culprit for a sudden “change” is the email server itself. In much the same way as I invariably forget engagements made by the missus (”We’re going to Bob and Freda’s in four weeks”), it’s extremely easy to have that email about changes to your email account your provider sent you two months ago. We’ve all done it. Well, I have anyway. So, if your outgoing email’s suddenly packed up and you’ve ruled out the other possibilities, it’s often worth checking your email provider hasn’t changed anything.
The final, and in the case of some email accounts (including my personal account… hey, it was cheap) extremely common, reason for the “Error connecting to server” error message is the temporary dissappearance of the email server itself. My provider’s server seems to go to sleep from time to time, but it always comes back after a few minutes. If you’re finding yourself unable to send emails every so often, there’s a good chance it’s that, and short of changing email provider, I’m affraid there’s not an awful lot you can do about it.
Send Failed for message X of Y - Send Failed - [A Three Digit Number] [An Incomprehensible Phrase]
In my post regarding incoming mail errors (POP3), I mentioned that outgoing mail errors were a bit on the wierd side. Well, here’s that wierdness. Put simply, we technical types rather like error codes. They’re a great way of communicating what’s gone wrong without ambiguity… providing whoever’s on the receiving end of those error codes has a nice lil’ list from which to translate them which, in reality, is almost never the case. SMTP status codes have been about for years, and they work the way they work because, well, that’s the way they work.
Let’s look at code 550, as that’s the one you’re mostly to encounter, and the one you can do the most to solve. In MyOffice, you’ll see this error returned from the SMTP server presented as ‘Send Failed for message X of Y - Send Failed - 550 Requested actions not taken mailbox unavailable’, or something very similar. The important part of the message is the number. Status code 550 means roughly “Hi, I’m an SMTP server, and I’m not going to do what you just asked me to do, and I’m not going to tell you why.” Not very helpful, is it? So it’s up to us to interpret that message.
The most common cause of a 550 SMTP code is an incorrect or missing user name and password. It would be nice to have been told this by the server, but we can’t have everything. So, if you’re getting a 550 code, it’s worth checking that you have the correct user name and password set up for your outgoing mail server, and that the ‘SMTP Server requires user name and password’ checkbox is checked in the ‘Servers’ tab of your email account details.
Another relatively common cause of 550 SMTP errors is trying to send an email using the ‘wrong’ email address. For example, if the email address for your email account is ‘fred@somedomain.com’, and your email account settings in MyOffice have that email address set as ‘bob@somedomain.com’, your SMTP server might take exception to you trying to pretend to be someone else.
Sadly, there are just too many SMTP error codes for me to go into in detail. It would bore both me and you rigid, and given that the only action you can take regarding most of them is shrug your shoulders, make a coffee, and call your email provider, it seems rather pointless spending the time explaining them. Thankfully, plenty of others have spent the time, so if you’re getting an SMTP error code you don’t understand (honestly, hands up anyone who does understand and hasn’t administered an SMTP server), and you feel like attempting a bit of self-diagnosis, this PDF from AnswersThatWork.com will give you a pretty good pointer as to what the problem is.