Regular Expressios for Breaklines

[Brandon!]

My ISP's webmail sends it's e-mails with the breakline of:

---- Customer Name <email@isp.com> wrote:

I'm sure my ISP (charter.net) isn't the only one that does that, so I think it might be a nice feature to offer (optional of course).

[eiden]

I agree, it would be great with regexp for the breaklines.

This is already in the bugtracker, requested in july 2005:
http://bugs.kayako.net/?do=details&id=415

We have the same problem as you.


There is also one other thing that's a bit annoying as well.

Some of our clients always type in their reply on the bottom of the mail (god knows why).
So when the reply from the client is parsed, it's appears as a blank reply in SupportSuite since everything below the breakline is removed.

I think that if the reply is empy after the breakline-processing, the whole mail should be inserted as a reply. It makes no sense to insert a blank/empty reply in the ticket history

[eiden]

Originally Posted by eiden

There is also one other thing that's a bit annoying as well.

Some of our clients always type in their reply on the bottom of the mail (god knows why).
So when the reply from the client is parsed, it's appears as a blank reply in SupportSuite since everything below the breakline is removed.

I think that if the reply is empy after the breakline-processing, the whole mail should be inserted as a reply. It makes no sense to insert a blank/empty reply in the ticket history

Here is a quickfix for "clients who write their reply below the breakline"

- Open the file modules/parser/functions_parsercore.php
- Go to the function processBreakLines.
- In the foreach loop, change from

if ($breakcontent)

to

if (trim($breakcontent))

[limbo]

Originally Posted by eiden

I agree, it would be great with regexp for the breaklines.

This is already in the bugtracker, requested in july 2005:
http://bugs.kayako.net/?do=details&id=415

Did this ever get added? It seems that email sent with Gmail also needs a RegExp type breakline.

[luiz]

This a plan for next release?

[craigbrass]

It is just up for consideration at the moment. Jamie and the developers have yet to meet and decide on what will / won't be implemented.

[Jamie Edwards]

We'll implement this in V3, next release hopefully

[Jamie Edwards]

Implemented in 3.30.01