Mailbox Not Found, invalid mailbox, User unknown, not our customer: these are all saying the same thing. If you've sent email to "firstname.lastname@example.org" and get a bounce containing one of those complaints, the mail server "example.com" doesn't have an account for anyone with the email name "someone". A couple of common reasons:
* You mistyped the email address. The single most common reason is simply that you made a typographical error in the email name. Check the entire email address for an error. Computers are very picky, and with the exception of upper/lower case email addresses must be exactly correct.
* It's an old address that's no longer in use. Perhaps the person you're attempting to email has changed their email address and you're using an old one which is no longer valid. Make sure what you're using is current.
Mailbox unavailable: 9 times out of 10, this is exactly the same as "mailbox not found". That other 10% of the time it could mean that there's a problem with the recipients email account, though exactly what kind of problem is impossible to say. Check to make sure that you have the email address correct, wait a while and try again, and if it still bounces try contacting the recipient some other way.
Mailbox full, or Quote Exceeded: sometimes this will show up as a part of a "Mailbox unavailable" message. It's fairly clear, though: your recipient has too much email and their server isn't accepting any more. This is most common with web-based email services like Hotmail or Yahoo, which have limits on how much mail you can accumulate. This can also be a sign of an abandoned account - someone's stopped looking at and cleaning out the email. In any case, you'll need to try and contact your recipient through some other email account, or some other way.
Host unknown, Domain Lookup Failed: this means that the mail server you're attempting to use, the "example.com" part doesn't exist. A common reason is, once again, a typo on your part. Make sure you typed it in exactly correct. Another reason are ISPs that change their name and eventually stop supporting the old name. Even though there's typically lots of warning, when the time comes anyone trying to send to an old email address might get this message in return when the switch is finally thrown.
Unable to Relay: this is a terribly obscure error message, but also becoming more and more common as ISPs try to crack down on spam. Mail is sent by relaying email from one server to the next. There could be many servers involved, but typically it's the mail server at your ISP relaying your email to the mail server at your recipients ISP.
In general, a mail server must "know" either the sender of an email, or its recipient, in order to safely transmit mail. Mail servers that do not enforce this requirement are called "open relays" and can be exploited by spammers to send out tons of spam.
Things get complicated because not all ISPs agree on what it means to "know" the sender of an email. All of these might result in an "unable to relay" message, depending entirely on the servers and ISPs involved:
* The "From" address might not match an account on the email server.
* The ISP might require that email comes via a connection (dialup or DSL) actually provided by the ISP - sending using someone else's connection might not be allowed.
* The ISP might require you to authenticate before sending email and you haven't.
* A mail server somewhere could be misconfigured.
There's no blanket answer if "unable to relay" happens only occasionally. Double check the email address you're sending to, for starters.
Temporary Errors: errors like "no adequate servers", "Connection Timed Out", "Resources temporarily unavailable.", "Out of memory" all typically indicate a problem with a mail server that you probably don't have any control over. They are, in general, temporary, and should resolve themselves over time. Look carefully at the bounce message; the email server involved may continue to automatically try to deliver your email without any action required on your part.
Blacklist Filters: If you see messages that indicate your email was "blocked", or "listed in", and references to sites that have things like "spamcop", "dynablock", "blackhole", "spamhaus" and similar in their names, then your email was probably intentionally blocked because the receiving system thinks your ISP's mail server is a source of spam.
Various blacklisting services try to identify servers which are sources of spam. They then make that list available to ISPs, who in turn can block email coming from these sources. The problem is that criteria for addition and removal from these blacklists is vague, at best, and getting a server removed from blacklists can be very difficult. If this happens to mail you send, get in touch with your ISP and explain that their server may be on a blacklist somewhere, and then try to use a different email address, or a different email account of your own, to contact your intended recipient. You might also tell your recipient that their ISP is improperly blocking legitimate email.
Content Filters: Much like blacklists, content filters are an approach many ISPs now implement to stem the tide of spam for their clients. Most will simply discard email that looks like spam, but some servers will actually send a bounce. Phrases in the bounce message like "Message looks like spam", "keywords rejected by the antispam content filter", "scored too high on spam scale" and similar means that your email, for whatever reason, tripped the spam filters on the receiving end. Your email looks too much like spam.
What does it mean to "look like spam"? Here, again, things get vague. That definition will vary greatly based on how your recipient's email server has been configured. Obvious possibilities are the use of pornographic words or phrases, HTML formatted email, currently popular drugs being hawked by spammers, or even having something that looks too much like a sales letter or a scam. The best approach is to scan the bounce for any clues (sometimes there's more information), and then validate your recipient can get any email by sending a simpler message. Assuming that all works, then re-work your message as best you can to not look like spam.
The definition of "a while".
One of the most common solutions for just about any bouncing email problem, after checking that you're sending to the right address, is to "wait a while and try again". The email system, while somewhat random, is also somewhat self-healing. If there's an email server with a problem, chances are it'll get fixed or eventually bypassed, especially if it belongs to a larger ISP. For temporary problems, as noted above, email servers will typically keep trying for up to 4 days before giving up.
My rule of thumb for trying email again, is "one hour, one day, one week". In other words, try again in an hour. There are classes of problems that will resolve themselves that quickly. If that still fails, then I'll try again the next day. If that still fails (and my message can wait that long), I'll try again in a week. If that still fails ... I need to find another way to get my message to my recipient.
When a Bounce Isn't Really a Bounce
Be careful! There's a class of viruses these days that propagate by "looking like" bounce messages. They instruct you to open an attachment for more information. Don't. Especially if you don't recall sending the message in the first place. Don't open any attachment, especially one accompanying what looks like an email bounce unless you are absolutely positively certain that it's legitimate.
You may also be getting bounce messages for email you didn't send. There's another class of virus that "spoofs" or fakes the "From" address on email messages, and as a result you could be getting bounce messages that have nothing to do with you. This scenario is sadly common.
Finally, if every email you send bounces, then you probably have a different problem. Chances are your email client is misconfigured. Double check outgoing or "SMTP" server settings, and double check with your ISP to ensure that you have them set correctly.
The mail server - source IP address which is trying to send mail to vail.net does not have proper reverse DNS entries setup or the DNS server for that mail server was not functioning at the exact instant that the mail was trying to be delivered to lara.on.ca. In other words the IP address from which the mail is being sent could not be converted back to a host name. The owner of that mail server and their ISP (not Lara) needs to correct this issue in order for mail to flow properly.
HOW TO GET THIS FIXED:
The ISP who provides the reverse-DNS mappings for the mail server in question (not Lara) needs to setup a reverse DNS mapping for the IP address of that mail server so that other hosts on the internet that try and convert that IP number back to a hostname will get a result. This is usually only a few minutes of work.
To find out who you need to contact for a given IP address you can visit the American Registery of Internet Numbers (ARIN) "whois" site at http://ws.arin.net/cgi-bin/whois.pl and enter the IP address which was rejected in the "Search for:" dialog. The contact information for the party in charge of that IP space should then be displayed for you.
That party can then be called or emailed and a request to setup a valid reverse-dns (PTR) record for the IP address of the mail server can be made.
In general, computers on the Internet all have an Internet Protocol (IP) address, somewhat like a unique phone number, assigned to them. Each Internet Service Provider is responsible both for allocating these addresses
to devices on their networks as well as for maintaining the mappings of these devices names to their IP address numbers and these IP numbers back to computer names.
In effect, ISPs assign devices something like a phone number from a bank of numbers that are in the realm of that ISP. They then need to provide a "411" service mapping a given devices name to that number as well as a reverse-411mapping of IP address numbers back to device names.
Using this "phone number" analogy, an ISP will assign a customer the phone number of 555-1212 and then must put in a listing for "John Doe" in the 411 database so that anyone asking for John Doe's phone number will be provided with the answer "555-1212" AND anyone asking "whose number is 555-1212" will be provided with the answer "John Doe".
All legitimate mail servers on the Internet will have been assigned an IP address by their ISP and that ISP should have set up both a forward DNS entry (an entry for mail.mycompany.com which points to the IP address for
that mail server) as well as a reverse DNS entry (an entry which given the IP address assigned to that host can return the name mail.mycompany.com).
Many computers on the Internet which are being misused to send SPAM do not have these two entries setup. In almost all cases email from these hosts is SPAM.
Due to the tremendous amount of SPAM on the Internet, Lara along with many other ISPs (like AOL for example) have elected to only accept mail from mail servers which have both a forward and reverse DNS entry. Servers lacking this information are not setup properly and will be blocked. Manual exceptions can be created for individual servers but the long term solution is for the sending server to correct their configuration.
It doesn't particularly matter what these names and IP addresses are as long as a query to convert a name to an IP address or a query to lookup the name associated with a particular IP address return some result other than "no entry found". As almost all legitimate ISPs and mail servers have already done this, this restriction has little to no effect on most mail.
In the event that a legitimate mail sender is getting blocked because proper forward and reverse DNS entries for their mail server have not been setup they should contact their ISP (not VailNet unless we are their ISP) and
inform them that they are unable to send email from their mail server because proper forward and reverse DNS entries have not been setup. Once this is fixed email will work.
Lara has no control over the forward and reverse DNS entries for third parties outside of our network. While we provide this informational document to assist anyone having trouble sending email to our systems because of a lack of proper DNS setup, we have no acesss or control over DNS records not associated with us. With respect to reverse-DNS records (sometimes called "PTR" records) we only have control over those reverse entries in our network space. You will need to contact the ISP in charge of PTR records for any other space. For lookups of who controls the records for other IP spaces visit www.arin.net.