small email processing project - perhaps php or ruby, mysql and cron

The project is to code some scripts and a small database users will email a midi file to an email address on the server the scripts will extract the midi file from this mail and save it to a directory. a seperate process, not part of this project will make an mp3 from this midi file. when the mp3 is ready, which could be days or weeks later email the user a link to download the mp3 detail: 1 user sends email to a special email account 2 is there a file attached? (if no, send error message email) 3 is the file too big? (if yes send error message) the maximum size needs to be customisable 4 is it a valid midi file? (if no, send error message email) *Depending on preferences allow one or both of: midi single track (format 0) midi multi track (format 1) these can be differentiated using the 'file' command: frog:/users/mathew/midi_net mathew$ file [login to view URL] [login to view URL]: Standard MIDI data (format 1) using 3 tracks at 1/384 frog:/users/mathew/mathew_mid/mathew$ file [login to view URL] [login to view URL]: Standard MIDI data (format 0) using 1 track at 1/96 5 save email details to database, get an id number for song the sender address, subject, message body, date and time all need to be saved to the database. 6 save midi file to 'midi' directory as [idNumber].mid eg: [login to view URL] 7 a seperate process, which is not part of this project will make an mp3 file from the midi file and save it in the audio directory as [idNumber].mp3 eg: [login to view URL] 8 regularly check for new mp3 files in the audio directory, if a new mp3 is found send the user a link to download the file, and record that this has happened in the database this will run on on a site hosted by dreamhost.com. so it needs to use technologies that can run on a dreamhost account, I'd prefer to use ruby on rails with mysql, 'cron' and 'file'. And if you can add virus checking to the incoming email i'd be really happy! theres a diagram of this at [login to view URL] open source and gpl components are fine ## 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). * * *This broadcast message was sent to all bidders on Saturday May 27, 2006 12:30:25 PM: hello, because some bidders have been confused by my description, i have put up a new description of the project with more detail. just to make it very clear: the conversion of the midi file to mp3 is not part of this project. that part happens on real instruments, and has already been completed. thanks mat ## Platform [login to view URL] webserver