email test project involving php

see attached .zip for more info. the text is shown below as well: We’re struggling with email issues for our site, thefacegame.com. Specifically, emails sent from the site to our users, end up in the bulk/spam folder for services like Yahoo and Hotmail. We have a hunch for why this is happening, but cannot be sure; we think it's because users of [login to view URL] receive emails from our site unexpectedly, or don't recognize it, and categorize it as spam. If enough Yahoo (or Hotmail, etc.) email users categorize our [login to view URL] emails as spam, all emails sent to all users end up in the bulk/spam folder. However, it could be content of the email itself that's causing our emails to end up in the yahoo spam/bulk folder. We want to run a small test to see which it is. Experiment steps: 1. Setup a new domain e.g. "[login to view URL]" at a new hosting provider, e.g. the "discount" package at a2 hosting: [login to view URL] The goal here would be to be sending email from an IP address different from the current IP address in the mail records for [login to view URL] 2. Setup some test accounts at [login to view URL], [login to view URL], and [login to view URL] 3. Setup the shared account at a2 hosting for the new domain so that it sends the [login to view URL] email (the daily email sent from [login to view URL] site today) and other emails sent from [login to view URL] using php (e.g. [login to view URL]) to the test accounts setup at #2. 4. Setup the shared a2 hosting account so that it mimics sending the email that's generated from one or a few games on the current [login to view URL] site when you click "Email this game" link. 5. See whether the emails sent from steps 3 & 4 above end up in the main inbox or spam/bulk folders of the test accounts setup in #2. I would do 1, 2 & 5 I would need you to do 3 & 4. ## Deliverables 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 linux, php, standard email protocols