Invalid Email Addresses

When importing, you will be able to see the number of invalid email addresses that have been corrected.

Fixing Invalid Addresses

During the import process or when creating an import template, the option to fix invalid email addresses is selected by default. This will allow to make corrections to common errors. If the box is unchecked, will not perform any corrections.

When fixing addresses, applies a number of heuristics in a specific order, developed by examining millions of misspelled addresses for common typographical errors. does not attempt to contact remote servers to ascertain that a particular email address is valid, nor does it guarantee that a "fixed" address will be valid. Not all proprietary details are included in the following description, but the types of heuristics used are listed below:

Check to see if the address already looks valid. This check verifies proper structure, looks for illegal characters and looks for a legal TLD or country code. If the address passes this test, PostUp will not update the address. If the address fails this test, PostUp will proceed to the next step.

• Remove common prefixes added by inexperienced users, such http:// and www.
• Remove or replace characters disallowed by RFC822.
• If the address does not contain an @ symbol, replace the first 2 with an @ and continue. If the address does not contain a 2, PostUp will abort processing. The address cannot be fixed.
• If the domain name contains a comma or a /, replace them with a period. This eliminates two common typos.
• Remove any leading or trailing periods, and replace multiple consecutive periods with a single period. This eliminates other common typos.
• If the TLD or country code (.com, .net, .us, etc) has repeated consecutive characters, collapse them, unless these characters are cc. This eliminates another class of typos, since.cc is the only legal TLD and country code that contains repeated characters.
• Apply a series of other transformations to the domain names based on three different classes of typos:
•  
  • Look for well known domains without suffixes: mailbox@yahoo becomes mailbox@yahoo.com
  • Look for common typos in common suffixes: .cpm, .c0m and .aom all become .com
  • Look for missing periods for common suffixes: mailbox@yahoocom become mailbox@yahoo.com
• Apply the validity check from step 1 again. If the address still appears to be invalid, abort processing. PostUp is unable to fix the address. If the address appears valid, PostUp will return the new address.

Checking Invalid Addresses Statistics

You may monitor the success of the import by visiting the Import History section (located on the Imports tab), and clicking on the import ID. To find the import statistics:

1. Once logged in, click on the Import tab.
2. Scroll to the bottom of the page to find the Import History section.
3. Click on the import ID of the import you wish to view. This will open the Import Status page.

The following image is an example of the Import Status screen from a completed import.