Neil - thanks for contributing to this issue, I built off of your handler and added regular expression splitting for issue creation.
I'm attaching the two compiled classes with source in a zip (RegexCreateOrComment.zip). Disclaimer: these were only tested in jira 4.2.2 standalone. Hope this helps.

I changed the CreateOrCommentHandler to use the RegexCommentHandler if the splitregex parameter is set. To use it, see http://confluence.atlassian.com/display/JIRA/Adding+your+own+email+handling+classes

I would like this feature very much, and looking at the source, this seems relatively easy. If an issue is found, CreateOrCommentHandler simple delegates to the CreateIssueHandler. If no issue is found, it delegates to either the FullCommentHandler or NonQuotedCommentHandler depending on the presence of a stripquotes parameter. It would be quite simple to check for a splitregex parameter and delegate to the RegexCommentHandler. I would do this myself but I don't have the time to set up a development environment, create test cases, etc.

Since a lot of people are redirected to this JRA issue, I think it would be helpful to post some solutions for the outlook problem. Maybe some good-to-go regular expression to split emails from outlook 2003/2007 would help people. It would help me.

We have the same problem with the CreateOrCommentHandler. It was ok with Outlook 2003, but now some of our users are using Outlook 2007 and it does not manage to strip the quoted text from their e-mails. This results in huge comments that contain the entire quote. I would switch to the RegexCommentHandler, but we want the ability to either create or comment which doesn't seem to be available with the RegexCommentHandler (judging by the name and documentation).

Has there been any word on when this would be implemented?

In our Jira system the comments area gets very messy.

Why? Because we use Microsoft Exchange and 99% of the emails are in html, so in the comment area there're lots of html garbage. Also because 99% of the users do not remove the original email when they reply, so sometimes there's 1 line comment with 100 lines of old comments.

Hi Roy,

> Is there anything scheduled for an upcoming release?

At the moment this issue is not scheduled, and therefore I am not able to provide an implementation date for it.

May I ask why without regexp parsing the comments in your system look ugly? We find that most users use the regular CreateOrCommentHandler.

Cheers,
Anton

Without regular expression parsing, comments in reply to notification emails make the view screen and the notifications virtually unreadable. My group quickly switched over to the RegexCommentHandler. One major drawback with the RegexCommentHandler is it's dependence on POP rather than IMAP, which will not let us configure a folder on the mailserver to point the service to. I have been navigating the forums and issues to see if this will be dealt with in the forseeable future, but couldn't find a document dealing with this. Is there anything scheduled for an upcoming release?