Email Validity Checker

Customer give us their email address at our off-line kiosk at our laser tag facility. We send all of these customers coupons to return to our facility. Unfortunately, some of our customers think it's cute to type in bogus email addresses. In addition, sometimes friends share an email address making it difficult to keep our list up to date. I need a compiled standalone tool for Windows XP that will do the following: 1) Filter out incorrectly formatted emails and allow me to correct them. 2) Filter out duplicate emails. 3) Filter out emails already in the mailing list. 4) Filter out certain strings of characters (foul language, 'spam', 'asdf', etc.) I don't care what it's programmed in as long as it is a compiled program that will run without any other installed components (beyond normal windows stuff). I expect the raw source code, too, in case we want to supplement the software and can't find the original coder (always my preference). Please read the deliverables that clearly describe the application needed. Please **DO NOT** bid or respond until you have fully read the deliverables. I need this app as soon as possible and will probably close bidding early if I see a bid I can live with from a coder who is well-rated. Please don't bid if you can't complete the project in a timely fashion. ## Deliverables Email Validity Checker: 1. Opens a CSV file and and asks you to identify email, birthdate, fname and lname from columns. Asks you if you want to ignore the first row (header row). This is the NEW EMAIL file. 2. CHECK 1. Checks for proper formatting, ie AT. (must allow two character extensions). Be sure to check for spaces in the email. Automatically remove spaces at the beginning and end of emails (all of them). a. Emails that fail the formatting are listed on the screen with fname and lname. b. Beside this listing is a text box with email rewritten inside of it. The email text box for each email is editable so I can make corrections. c. Beside the text box is a check box labeled "delete?". d. At the bottom of the page is a "save changes" button. When this is pressed, any edits will override the original text file and be updated. Any emails marked 'delete' will have the entire line removed from the CSV. 3. CHECK 2. Check against list of existing emails. This is the EXISTING EMAIL file. a. Within the directory of the application is a text file called ExistingEmails.txt. This is a text file full of emails already in the list. b. Each email in the NEW EMAIL file is compared to emails in EXISTING EMAIL file. If there is a match, the entire row in the NEW EMAIL is eliminated. If there are multiple rows matching in the NEW EMAIL file, all matching rows are deleted. 4. CHECK 3. Check for duplicate emails. The app checks for duplicate emails within the NEW EMAIL file. If at least two emails match (could be more) then all matching emails are queued up on the screen. a. The matching email is on the first line. Beside this is a 'Delete All' Check box. b. On each line below the matching email, for each matching row, the following data elements will print: Fname, Lname, Birthdate. c. Beside each listing is a radio button labeled "select this email" d. The radio button is linked to each matching email, although there may be multiple emails on the screen. Example: AT. [] Delete All? JASON BOCK 8/1/69 0 select this email ALEX BOCK 3/18/93 0 select this email AT. [] Delete All? JOHN DOE 1/1/45 0 select this email JOHN SMITH 2/3/88 0 select this email In the above example, the end user could select one of the AT emails for saving and one of the AT emails for saving. The top two radio buttons are linked to AT and the bottom two radio buttons are linked to AT. e. The default selection is the oldest birthdate. This button will be selected by default. f. At the bottom of the page is a "Save Selections" button. When this is pressed, the app looks at each email. If Delete All was selected, then all rows matching the email within the NEW EMAIL file will be deleted. If Delete All was not selected, then the selected email is saved (either the default or if the end user has made changes). All other rows associated with that email will be deleted in the NEW EMAIL file. 5. CHECK 4. Search for objectionable words. In the same directory as the application is a text file called CheckWords.txt. This file contains a string of characters on each line, such as "asdf" or "biteme" This will allow me to easily edit and supplement the objectionable words. a. The actual email portion of each email (i.e. the identifying name or in the email 'AT . ') is checked against this list. The strings in CheckWords are not whole words. b. Any email name that contains one or more of the CheckWords strings is listed on the screen along with Fname, Lname and birthdate. Beside each listing is a "Delete this email" checkbox. c. By default, all emails on this list are checked with "Delete this email"...they are scheduled to be deleted by default. d. At the bottom of the page is a "Save Changes" button. When clicked, all rows marked "Delete this email" are deleted from the NEW EMAIL file. 6. CHECK 5. Look for emails with names shorter than 6 characters. I get a lot of johnATaolDOTcom type emails. In the same vein, check for domains that are less than 3 characters (i.e. [login to view URL]). a. As with the others, list the fname, lname, email and birthdate in a line with an option to "delete this email." b. Default for this Check is leave it in, DO NOT Delete (so the check box is UNCHECKED). c. At the bottom of the page, give me a Save Changes button to delete the unwanted emails. 7. Wrap up. After all of these checks, the app writes a new CSV with all of the corrected and filtered rows of data (must include all data, not just the Fname, Lname, Birthdate and Email elements). The actual columns of data will vary amongst files. This data is saved in a new CSV titled [login to view URL] **IMPORTANT** 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows XP