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: email@example.comB NEW 11: firstname.lastname@example.org SRC 467: "Mr. Potter" <email@example.com"> NEW 467: "Mr. Potter" <firstname.lastname@example.org> SRC 724: "martyb" <email@example.com%20(train%20to%20trane)> NEW 724: "martyb" <firstname.lastname@example.org> SRC 733: "MAXOMENOS" <maxomenos@SPAM=DEATH.hushmail.com> NEW 733: "MAXOMENOS" <email@example.com> SRC 743: firstname.lastname@example.org,email@example.com NEW 743: firstname.lastname@example.org SRC 772: email@example.com NEW 772: firstname.lastname@example.org SRC 1263: "email@example.com" <//firstname.lastname@example.org> NEW 1263: "email@example.com" <firstname.lastname@example.org> SRC 2267: "Laurent Clevy" <email@example.com@subject=[ADF_FAQ]> NEW 2267: "Laurent Clevy" <firstname.lastname@example.org> SRC 2480: "email@example.com" <guylhem@LDP_NO_SPAM.metalab.unc.edu> NEW 2480: "firstname.lastname@example.org" <email@example.com> SRC 3955: "firstname.lastname@example.org" <email@example.com,firstname.lastname@example.org> NEW 3955: "email@example.com" <firstname.lastname@example.org> SRC 4083: email@example.com) NEW 4083: firstname.lastname@example.org SRC 4229: (email@example.com) NEW 4229: firstname.lastname@example.org SRC 11832: "Daniel Stenberg" <daniel_at_haxx.se> NEW 11832: "Daniel Stenberg" <email@example.com> SRC 13550: "firstname.lastname@example.org" <Lena%20Games> NEW 13550: "Lena Games" <email@example.com> SRC 19699: mailto:firstname.lastname@example.org NEW 19699: email@example.com SRC 19846: "JAMM <firstname.lastname@example.org>" <JAMM%20<email@example.com>> NEW 19846: "JAMM <firstname.lastname@example.org>" <email@example.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 <firstname.lastname@example.org> Jane Smith <email@example.com> firstname.lastname@example.org Sergio <email@example.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 firstname.lastname@example.org and email@example.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 firstname.lastname@example.org and email@example.com.
- Verify emails by first-level domains list. It is the simple check procedure, it compare the first-level domain (e.g., '.com' for firstname.lastname@example.org) with all domains in list. But it helpful to remove 'antispam jokes' in mailing lists, like email@example.com, firstname.lastname@example.org 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