FS#1819 - Communicate via email

Need to be able to email back and forth to communicate with flyspray. Ideally flyspray can be CC'ed on an email or can replay to a notification which would add the body and/or attachments to the thread. This goes back to reworking the way people interact with and view tickets

I have already added this in my 0.9.9.7 version. Its not the best piece of coding I have ever written but works a treat.It has made a massive difference for the organisation I work for, it now allows for non registered users to email in their support tasks and permits them to simply reply to the email sent back to them to add new comments to the task.Doesn't handle attachments though.

I have attached 2 files.The file that I am currently using (cron.emailParser.php) gets called every minute via a cron job.It is certainly not pretty code, but, for my purposes it works a treat.

The second file is a email parser script that I use in another project I have. I was planning on using this to replace the email parts of the other script as it handles attachments and generally is more bullet proof.

TODOs for an Email2Flyspray create task/update task feature

imap server INBOX settings for the inbox configurable in Flyspray global admin area similiar to the smtp settings

Simple test button so admin user can do a simple check if it is setup correct

what methods do we implement to be sure the Email comes really from an authorized Flyspray user and is not faked? Checking PGP signatures or similiar comes to my mind.

Format for the users that Flyspray can analyze easy:For example create a new task:

email subject: FS[projectname or project_id] followed by task summary
email body(text):
severity: one integer (optional, acceptence depends on user rights in the project)
priority: one integer (optional, acceptence depends on user rights in the project)
assignees: usernames (comma separated, optional, acceptence depends on user rights in the project)
status: one integer (optional, acceptence depends on user rights in the project)
all text following goes to the task description.
links: links (optional, urls with or without protocol prefix (fallback to http://?) comma separated, acceptence depends on user rights in the project)
attachments: check if they are only signature images or real attachments for the task. Validation of attachments (file types, content,..) if checks ok, add them to the created task.

If the email subject contains only a html part and no text part, the html should be stripped from html tags first.

Before implementing this, there must be the "multiple email feature" done right, see FS#1812.