[Rt-commit] rt branch, 4.2-trunk, updated. rt-4.2.3-39-gcd4443e

[Wallace Reis]

The branch, 4.2-trunk has been updated
       via  cd4443edb251466215de11ec7097dc7f2fe85703 (commit)
       via  4e0e092e39c8c9d39e5eccf6118a0515938cbcca (commit)
      from  7fc0a6ab8a9234a88f2538e9d00cc53de9db5430 (commit)

Summary of changes:
 bin/rt-mailgate.in  | 7 ++-----
 etc/RT_Config.pm.in | 4 ++--
 2 files changed, 4 insertions(+), 7 deletions(-)

- Log -----------------------------------------------------------------
commit 4e0e092e39c8c9d39e5eccf6118a0515938cbcca
Author: Wallace Reis <wreis at bestpractical.com>
Date:   Wed Mar 19 19:56:17 2014 -0300

    Minor doc patch to avoid confusion

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 1a8a640..7d686ba 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -425,8 +425,8 @@ Set($RTAddressRegexp, undef);
 
 RT provides functionality which allows the system to rewrite incoming
 email addresses.  In its simplest form, you can substitute the value
-in C<CanonicalizeEmailAddressReplace> for the value in
-C<CanonicalizeEmailAddressMatch> (These values are passed to the
+in C<CanonicalizeEmailAddressMatch> for the value in
+C<CanonicalizeEmailAddressReplace>> (These values are passed to the
 C<CanonicalizeEmailAddress> subroutine in F<RT/User.pm>)
 
 By default, that routine performs a C<s/$Match/$Replace/gi> on any

commit cd4443edb251466215de11ec7097dc7f2fe85703
Author: Wallace Reis <wreis at bestpractical.com>
Date:   Wed Mar 19 19:58:33 2014 -0300

    Remove old mailgate info from RT 2.1

diff --git a/bin/rt-mailgate.in b/bin/rt-mailgate.in
index 7589701..b270c4c 100644
--- a/bin/rt-mailgate.in
+++ b/bin/rt-mailgate.in
@@ -400,12 +400,9 @@ equivalent.
 =head1 SETUP
 
 Much of the set up of the mail gateway depends on your MTA and mail
-routing configuration. However, you will need first of all to create an
-RT user for the mail gateway and assign it a password; this helps to
-ensure that mail coming into the web server did originate from the
-gateway.
+routing configuration.
 
-Next, you need to route mail to C<rt-mailgate> for the queues you're
+You need to route mail to C<rt-mailgate> for the queues you're
 monitoring. For instance, if you're using F</etc/aliases> and you have a
 "bugs" queue, you will want something like this:
 

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