Feature Addtions to RoundCube web mail

| | We're looking for some who has past experience working on the Roundcube (henceforth referred to as RC) webmail interface. If you do not have specific experience with RC, then you must be able to prove strong skills in PHP and Javascript/AJAX. Bids that do not contain specific examples of previous work in this area will be ignored. We have a few features we need to add to the RC interface: 1. Spam/ham flagging 2. Email forwarding setup 3. Email sorting rules setup The features are already implemented on the backend (the mail server), but we need to add the user interface portions. | ## Deliverables Here are some more details of how each of the features must be accomplished: 1. We use spamassassin as one of our content-based spam filtering measures. We would like to add buttons into RC that allow a user to mark a message as spam or to select a message in the "Junk" folder (where our detected spam is routed) and flag it as "ham". When the user does this, the message should be written to a temporary file in /tmp and then the following shell command should be run: sa-learn --spam <file> or sa-learn --ham <file> as appropriate. Once the file has been submitted to SA, it must be removed from /tmp 2. We need to add a control to the main settings tab that allows a user to specificy a destination address to which all mail should be forwarded. Our mail system is based around an LDAP directory that controls all details of delivery and access to the mail system. Only users with a particular LDAP attribute ("accountStatus: active" in this case) will have access to the mail forwarding feature. Users who are not in the "active" state (usually they are labeled "active-webonly") should be shown a grayed out box for the forward address and be given a link to our enhanced mail services page where they can upgrade their account. Users who are "active" will be able to specify the address to forward mail to. When an address is specifies, it must be entered as the value for the LDAP attribute "mailforwardingaddress:". 3. Email filtering is the ability for a user to specify rules that match the To, From, CC, Subject, etc lines and a folder which should contain messages that match the pattern. This features is also controlled by LDAP attributes. We need a front-end implemented that will allow a user to add/edit/and remove rules from their filter. Please find attached a text file that explains how the LDAP attributes for filtering work and how they should be constructed. Note that the file shows examples using LDAP command line tools, but we will of course be implementing all of this in PHP. Example PHP code for manipulating our LDAP directory is available, it's all fairly basic use of the PHP ldap functions: [login to view URL] In terms of time frame, I'd like to see this completed within 2 weeks if possible. If you think it will take longer then please specify that in your bid and we'll plan for it. I will give the winning bidder SSH access to our development server where you can have an SVN copy of our website code to work on. I will take care of deploying the finished code to our production server when it is ready. * * *This broadcast message was sent to all bidders on Saturday Feb 23, 2008 2:12:14 PM: The issue has come up of whether we should stick with RoundCube at all, or opt for a more "tried and tested" solution. Let me tell you a bit about the company I work for. We are the owners of the domain and trademark for "[login to view URL]" - please go check out our free webmail service. This website is extremely high traffic, and we've signed up nearly 20,000 email users since Dec 17 2007. We are getting ready enter the market with a very strong position in major markets such as search, domains, mail, and hosting. In the long run, the web mail service we are building will be competing against top-level providers such as [login to view URL] and mail.com. We picked RoundCube because of the ease of setup, the lightweight database requirements, the good integration with IMAP features, the AJAX library, and the ability to customize the hell out of it (even fork it for our own use). At this point not much has been invested in RC except a slight bit of customization and some theme changes; but we have invested heavily in our IMAP, LDAP, and Postgresql infrastructure, all running on FreeBSD. Changing mail systems must not mean changing our mail backend. I am open to hearing suggestions for a system that we can use to grow our platform to 1 Million users and beyond. We need to maintain 100% ability to customize the system and integrate with our other site features. Having a good head start on modern web UI features is also a plus. Assume the backend infrastructure (web, mail, and database clusters) are well taken care of - talk to me about the perfect web front end for the big leagues. I look forward to hearing your comments.