[Rt-commit] rt branch, 4.0-trunk, updated. rt-4.0.13-52-g8764829

[Alex Vandiver]

The branch, 4.0-trunk has been updated
       via  87648298858ddf40a03f17934f9e6692f69ab310 (commit)
      from  5154856f8d35889789732b666d71c6ef6cd7aecf (commit)

Summary of changes:
 docs/UPGRADING-4.0 | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

- Log -----------------------------------------------------------------
commit 87648298858ddf40a03f17934f9e6692f69ab310
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Thu May 30 11:01:20 2013 -0700

    Upgrade notes for the Set/OverrideOutgoingMailFrom changes

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index 687dfbc..9bca8f1 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -189,3 +189,19 @@ these types before insertion.
 
 Site-specific custom types (anything but ticket, reminder or approval)
 are not affected by these changes.
+
+=head1 UPGRADING FROM 4.0.13 AND EARLIER
+
+The "Default" key of the C<$OverrideOutgoingMailFrom> config option now,
+as previously documented, only applies when no ticket is involved.
+Previously it was also used when a ticket was involved but the
+associated queue had no specific correspond address.  In such cases the
+global correspond address is now used.
+
+The config option C<$SetOutgoingMailFrom> now accepts an email address
+as a value which will act as a global default.  This covers the simple
+case of sending all bounces to a specific address, without the previous
+solution of resorting to defining all queues in
+$OverrideOutgoingMailFrom.  Any definitions in the Override option
+(including Default) still take precedence.  See
+L<RT_Config/$SetOutgoingMailFrom> for more information.

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