Email address syntax correction with MLW

This action corrects wrong e-mail address in a source file using unique algorithms. Action result example:

SRC 11: jpiracy@adobe.comjB
NEW 11: jpiracy@adobe.com
SRC 467: "Mr. Potter" <potter@port.com">
NEW 467: "Mr. Potter" <potter@port.com>
SRC 724: "martyb" <martyb@ultraint.com%20(train%20to%20trane)>
NEW 724: "martyb" <martyb@ultraint.com>
SRC 733: "MAXOMENOS" <maxomenos@SPAM=DEATH.hushmail.com>
NEW 733: "MAXOMENOS" <maxomenos@hushmail.com>
SRC 743: tycho@penny-arcade.com,gabriel@penny-arcade.com
NEW 743: tycho@penny-arcade.com
SRC 772: krodim@hotmail.comt
NEW 772: krodim@hotmail.com
SRC 1263: "info@spinnaker.co.jp" <//info@spinnaker.co.jp>
NEW 1263: "info@spinnaker.co.jp" <info@spinnaker.co.jp>
SRC 2267: "Laurent Clevy" <lclevy@club-internet.fr@subject=[ADF_FAQ]>
NEW 2267: "Laurent Clevy" <lclevy@club-internet.fr>
SRC 2480: "guylhem@metalab.unc.edu" <guylhem@LDP_NO_SPAM.metalab.unc.edu>
NEW 2480: "guylhem@metalab.unc.edu" <guylhem@metalab.unc.edu>
SRC 3955: "abuse@ihateclowns.com" <abuse@ihateclowns.com,rodneyb@ihateclowns.com>
NEW 3955: "abuse@ihateclowns.com" <rodneyb@ihateclowns.com>
SRC 4083: abuse@bfp.net)
NEW 4083: abuse@bfp.net
SRC 4229: (djackson@aol.net)
NEW 4229: djackson@aol.net
SRC 11832: "Daniel Stenberg" <daniel_at_haxx.se>
NEW 11832: "Daniel Stenberg" <daniel@haxx.se>
SRC 13550: "lena@lenagames.com" <Lena%20Games>
NEW 13550: "Lena Games" <lena@lenagames.com>
SRC 19699: mailto:kurtcpa@bright.net
NEW 19699: kurtcpa@bright.net
SRC 19846: "JAMM <mike.gole@sun.com>" <JAMM%20<mike.gole@sun.com>>
NEW 19846: "JAMM <mike.gole@sun.com>" <mike.gole@sun.com>

We achieved 100% error correction in real text address lists we had. However, we suppose MLW to restore 95% of theoretically restorable addresses. Addresses are often written in exotic ways, e.g. (my)*(email)!(com) for spam-protection purposes. Intellect of our software cannot match human fantasy so far.

No correct address can be damaged by this action: MLW only attempts to correct incorrect addresses. The list of processed addresses is stored in the log as shown above. Each line starts with the three-letter code (SRC - source address; NEW - corrected address; INV - invalid address, recovery failed), followed by the address line number, colon, and the address proper.

The Wizard will also offer you the following options:

Remove ?subject= from addresses. Nominally, providing message subject together with e-mail address is quite allowable, but in most mailing lists this is unnecessary.
Add mailbox (user-defined) to domains with no mailbox. Some addresses in a list may be absolutely unrecoverable, e.g.:
```
NetSoap <netsoap.com>
Jane Smith <http://www.jsmith.com>
mycorp.net
Sergio <mailto:sergio.com>
```
MLW cannot detect a mailbox if it is not contained in an address. If this option is disabled, all addresses of the kind will be considered invalid. If the option is enabled and a mailbox is defined (e.g. "info"), the addresses will be restored as follows:
```
NetSoap <info@netsoap.com>
Jane Smith <info@jsmith.com>
info@mycorp.net
Sergio <info@sergio.com>
```
Remove user-defined substring. MLW will attempt to remove the defined substring from all addresses in the list, both correct and incorrect ones (prior to the restore procedure). The string is case-sensitive (if you set it to "REMOVEIT", the substring "RemoveIt" won't be removed). The substring is searched for throughout the entire address line, including address owner name, if any.
Recovery emails by known domains list. If this option is enabled, MLW will recovery emails without first-level domain like mike@hotmail, jane@aol to mike@hotmail.com and jane@aol.com. You can add any number of domains to domains list.
Remove known 'REMOVEIT' substrings. This option may affect on valid emails. Addresses like mikeREMOVEIT@hotmail.com and jane@NOSPAMaol.com are syntactically correct and may exist. If this option is on, MLW will try to recovery such emails to mike@hotmail.com and jane@aol.com.
Verify emails by first-level domains list. It is the simple check procedure, it compare the first-level domain (e.g., '.com' for jane@somesite.domain.com) with all domains in list. But it helpful to remove 'antispam jokes' in mailing lists, like hahaha@dont.spam, someone@invalid.address and so on. To quality emails verifing we recommend Advanced Maillist Verify.
Remove unrestored addresses. If the option is disabled, an address which recovery failed would be written in the destination file unchanged.

The action upon a list of one million addresses takes 5 to 60 second on a machine with Intel Pentium III 933 MHz depending on the number of incorrect addresses in the list and on the recovery difficulty.

Next operation: Filter emails by mask or by regular expression