First, before you even try to figure it out, try this. Set your email to use plain text instead of html or xml or whatever else you may be using. In Microsoft email programs that will be found on the format tab, open the email, click on the format dropdown menu, and pick plain text. Now try sending. This will usually remove the type of things that can cause problems and should be a simple test. We do accept html email but some features in html emails are invisible to the user and can trigger the filters.

If you are viewing this page then you had an email bounced by one of our mail servers. The possible reasons for bounced emails are as follows:

If you got a "blacklisted" error, go here and check the IP address of your mail server to see if one of the blacklists has it listed, if it is then you need to talk to that blacklist to get unlisted.

1) The most common reason lately seems to be people emailing web pages to each other, normal web pages should be no problem but many sites include live scripts on their pages, these scripts are usually harmless but this is the method that most of the web based virus use to spread so we are currently blocking all live scripts in emails, this includes executable attachments. If you must send an executable file via email then we would suggest you zip it before attaching it.

We have had so many tech support calls by customers who got infected by email virus that we had to do something to try and stop the spread.

You can check to see if your email contains a script by viewing the source for the email (assuming you are sending it in html format) and looking for the string "<script language=", if your email contains this, then it's not going to pass thru the server.

If you are a customer who is having a problem receiving a mailing list that includes ads as a way to finance the mailing list, see if there is an option to have them send the mailing list as "plain text". This will usually allow you to get around some of the filters that advertising based mailing lists run into with spam filters.

Because of the recent volume of executable infected emails being developed and being passed around, we have temporarily blocked all executable attachments from passing thru our mail server. If you need to pass an executablet to someone via email you will have to zip it to get it thru the server. Currently we are being hit by about 11,000 infected emails per day so we needed to take this measure to try to protect our users from virus infected emails.

The executable file types being blocked are .exe, .bat, .com, .cmd,  .vb, .vbe, .vbs. .wsc. .wsf, and .wsh, no email with an attached file that has those extensions will pass thru the mail server.

2) Your email contains a virus. We filter the most common virus. 

3) Check required RFC822 headers - RFC822 requires emails to have a certain set of header lines. Some mail clients do not insert the required headers, with typically the From: field missing.

4) Your email was a spam. We bounce spams for some of our domains at the request of our customers. We use a number of methods to do this and they change on a daily basis. If you think this could have caused a valid email to bounce please notify abuse@getinfo.org right away and we will look into it.

5) If you are trying to report a spam and it bounced back to you that means that we have terminated the account and added it to our filters. We have zero tolerance for spammers.

6) You may be trying to reply to a spam with a remove email. If that spam has been reported to abuse@getinfo.org it is likely that it is now blocked by our spam filters and you are quoting back the whole spam in your email, try removing the actual spam from your email.

7) Your email contains a webbug. Webbugs are being used by spammers to verify email address lists. Basically it works like this, the spammer sends out a mailing with HTML code in it that looks like this <img src="http://somewhere.com/image/yourid.jpg"> but this is a tiny 1bit image that you can't see. Now when you open the email using Outlook or Outlook Express your computer makes a connection to that server and the server logs the URL. You need do nothing but view the email, even preview pane will cause the connection to be established.

Once the connection happens, the spammer now KNOWS that you saw the email, they also know the time, your IP address, and if they wanted they could have set a cookie on your machine identifying you BY NAME if they know your name. The result, we block webbugs because it is an invasion of privacy. for more on webbugs see http://www.privacyfoundation.org/privacywatch/report.asp?id=40&action=0

8) Message lines not terminated by CRLF - According to RFC standards all lines must be terminated with a carriage return, line feed pair . Unfortunately, some mail servers (especially old versions of Sendmail) only terminate with a carriage return.

9) Message line exceeds RFC2822 limits - According to RFC2822 standards section 2.1.1 there are two limits placed characters in a line. Each line of characters must be no more than 998 characters (this is the one we check), and should be no more than 78 characters (we don't check this), excluding the CRLF.

10) Check for IP rather than hostname in URL - http URL should have a hostname rather than an IP in the address part of the URL. The code detects normal dotted IP addresses and obfuscated IP addresses, for example those presented in binary, octal, decimal and hexadecimal formats with and without numeric overflow.

11) Attachment name is too long - If the attachment name exceeds 256 characters the message will be rejected.

12) UUEncode begin in subject - The UUEncode begin statement should never appear in the subject line of the message. It is placed in the subject line as a method to bypass virus scanners.

13) UUEncode data invalid - UUEncoded data should only contain ASCII text.

14) UUEncode data invalid decode - When a message is received with UUEncoding GMS will decode the attachment, to allow it to be checked.

15) MIME invalid message/rfc822 content type - If a message includes the "rfc 822 content type" it can be used to include a message within a message as an attempt to bypass virus or anti spam scanning.