We are a record label who sends out HTML newsletters to our fans. We would like to stream *non-cacheable* and *non-downloadable* music in these newsletters by incorporating a "player"-gif/jpg in our newsletter, and if you click it (while connected to the internet) a website or pop-up opens up with a player (in flash perhaps?) where you can listen to one or more different tracks pre-decided by us (and subject to change from newsletter to newsletter). The player should be 'skin-able', able to display a picture (e.g. gif/jpg album cover art), a small descriptive text for each song, and the ability to include a few "buy it here" gif/jpg logos that links to online music stores such as iTunes or Klicktrack. As the purpose of this project is to incite newsletter recipients to buy the music that we are streaming (rather than e.g. link to the webstream from their blog), the solution needs to pay max attention to protection of the source file(s) which should only be streamable through aforementioned player, while at the same time be a solution that is available "as is" from/to users of any operating system and/or browser platform, and coded in such a way that our newsletter featuring the player will not be deemed as "spam" by antivirus/spam email filters (incl. common "free" email services such as hotmail and gmail). The prep and handling of the playlist and player should be made through a login-protected administrative web interface, designed in such a user-friendly and intuitive way that even a person with no particular skills will be able to successfully generate a new player by: 1) upload the song(s) you want to be played back 2) upload a picture 3) upload a text 4) upload one or more "buy" links 5) the option to either end the upload or to add another song to the player 6) skin the player. Also, we will need a logging functionality that will keep track of 1) how many unique people have loaded the player as of a particular newsletter 2) which songs they have played 3) how many times a particular song has been played 4) if they clicked on the "buy"-links; and preferrably 5) other good and valuable userdata, such as geographic location (country, city). These data should be displayed on a password protected webpage (part of the administrative interface) and extractable by export of a comma-separated text file through the administrative interface. ps: we can supply the visual layout for the player ourselves. It is the coding we need help with!