[Rt-commit] rt branch, master, updated. rt-4.1.19-249-g6193622

[Alex Vandiver]

The branch, master has been updated
       via  6193622085db38ed0eb60d3809737c03eeaf4e48 (commit)
       via  7da4a51b3d725c68cb54498190a2cc4ac78a8fae (commit)
       via  4f34a6f37a4f101729702a4fc9ca497b48284769 (commit)
      from  0f94ece3f42cc082b69ac8d7140f8243136c6b4f (commit)

Summary of changes:
 docs/UPGRADING-4.2                                | 11 +++++++++++
 lib/RT/Action/SendEmail.pm                        |  6 +++---
 t/security/CVE-2012-4730-email-header-injection.t |  8 ++++----
 3 files changed, 18 insertions(+), 7 deletions(-)

- Log -----------------------------------------------------------------
commit 6193622085db38ed0eb60d3809737c03eeaf4e48
Merge: 0f94ece 7da4a51
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Wed Sep 4 19:23:03 2013 -0400

    Merge branch '4.2/put-an-X-on-it'
    
    Conflicts:
    	docs/UPGRADING-4.2

diff --cc docs/UPGRADING-4.2
index 93a6840,3a8ec72..af3f1cc
--- a/docs/UPGRADING-4.2
+++ b/docs/UPGRADING-4.2
@@@ -281,6 -275,15 +281,17 @@@ templates, e.g. "Forward" template coul
  
  { $ForwardTransaction->Content =~ /\S/ ? $ForwardTransaction->Content : "This is a forward of transaction #".$Transaction->id." of ticket #". $Ticket->id }
  
+ =item *
+ 
+ RT has generated RT-Ticket: RT-Originator: and Managed-By: headers in
+ compliance with RFC2822/6648 but we've discovered that some smarthost
+ providers are requiring strict adherence to RFC822 which mandates X-
+ prefixes on these headers. We've made this change in 4.2 for users
+ relying on those providers.
+ 
+ Any external scripts which were parsing on these RT mail headers will
+ need to be updated.
+ 
 +=back
 +
  =cut

-----------------------------------------------------------------------