[ 
https://issues.apache.org/jira/browse/OFBIZ-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023505#comment-17023505
 ] 

ASF subversion and git services commented on OFBIZ-10879:
---------------------------------------------------------

Commit 9706acf064e26c291c0bd10081df8286ae6b359b in ofbiz-framework's branch 
refs/heads/release17.12 from Pawan Verma
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=9706acf ]

Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail 
for CommunicationEvent.subject field
(OFBIZ-10879)

CommunicationEventServices#updateCommEventAfterEmail could generate wrong 
result. If general.properties value 'mail.notifications.redirectTo' is used, it 
is possible that the subject string has more than 255 character.

Thanks, Ulrich Heidfeld for your contribution.


> updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients 
> from mail subject for general redirected mails
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-10879
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10879
>             Project: OFBiz
>          Issue Type: Bug
>    Affects Versions: Trunk
>            Reporter: Ulrich Heidfeld
>            Assignee: Pawan Verma
>            Priority: Minor
>         Attachments: OFBIZ-10879.patch, OFBIZ-10879.patch
>
>
> "updateCommEventAfterEmail" method in CommunicationEventServices.java could 
> generate  wrong result. If general.properties value 
> "mail.notifications.redirectTo" is used, it is possible that the subject 
> string has more than 255 character. 
> Now:
> {code:java}
> Original subject [To: <sendTo>, Cc: <sendCc>, Bcc: <sendBcc>]
> {code}
> Solution:
> {code:java}
> Original subject [RedirectedTo: recipi...@example.com]
> {code}
> In this way we have fixed this in one of our OFBiz forks. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to