Mailing List Archive

RT Bounces
Hello,

I have searched through the list archives, and read a ton of posts
regarding bounces but have not been able narrow down what issue I am having
specifically. I have not modified any scrips from default. Have one queue
that is in use "Incident Reports', with the addresses
incident@rt.mydomain.com and incident-comments@rt.mydomain.com configured
in /etc/aliases, any response to the autogenerated emails or new emails to
sent to incident@rt.mydomains.com are showing bounces.

I will include as much information as I have seen asked for in other posts.


/etc/aliases
<snip>
# See man 5 aliases for format
incident: "|/opt/rt4/bin/rt-mailgate --queue 'Incident Reports'
--no-verify-ssl --action correspond --url https://rt.mydomain.com"
incident-comments: "|/opt/rt4/bin/rt-mailgate --queue 'Incident
Reports' --no-verify-ssl --action comment --url https://rt.mydomain.com"

Bounce message:

<snip>

From MAILER-DAEMON Thu Jan 19 22:11:35 2017
Return-Path: <>
X-Original-To: jayson
Delivered-To: jayson@rt.mydomain.com
Received: by rt.mydomain.com (Postfix, from userid 33)
id AEF0A140AB8; Thu, 19 Jan 2017 22:11:35 -0600 (CST)
Content-Type: multipart/mixed; boundary="----------=_1484885495-18000-19"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.508 (Entity 5.508)
To: jayson@rt.mydomain.com
Precedence: bulk
Subject: RT Bounce:
From: incident@rt.mydomain.com
Date: Thu, 19 Jan 2017 22:11:35 -0600
Message-Id: <20170120041135.AEF0A140AB8@rt.mydomain.com>

This is a multi-part message in MIME format...

------------=_1484885495-18000-19
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary

RT thinks this message may be a bounce

------------=_1484885495-18000-19--


</snip>

mail log from rt server

Jan 19 22:21:25 rt postfix/smtpd[18877]: connect from
mail-yw0-f180.google.com[209.85.161.180]
Jan 19 22:21:26 rt postfix/smtpd[18877]: 05F14140AAD: client=
mail-yw0-f180.google.com[209.85.161.180]
Jan 19 22:21:26 rt postfix/cleanup[18881]: 05F14140AAD:
message-id=<CAM32JiToL_cmdW72=D-_PPu_zfHR7UbcNCvF8NEt=bKkYm8
WqQ@mail.gmail.com>
Jan 19 22:21:26 rt postfix/qmgr[13852]: 05F14140AAD: from=<
jayson@private.com>, size=2522, nrcpt=1 (queue active)
Jan 19 22:21:26 rt postfix/smtpd[18877]: disconnect from
mail-yw0-f180.google.com[209.85.161.180]
Jan 19 22:21:26 rt postfix/local[18882]: 05F14140AAD: to=<
incident@rt.mydomain.com>, relay=local, delay=0.93,
delays=0.56/0.02/0/0.35, dsn=2.0.0, status=sent (delivered to command:
/opt/rt4/bin/rt-mailgate --queue 'Incident Reports' --no-verify-ssl
--action correspond --url https://rt.mydomain.com

</snip>

RT Mail gate test from commandline:

root@rt:/opt/rt4/etc# cat /usr/bin/test | /opt/rt4/bin/rt-mailgate --debug
--queue 'Incident Reports' --url http://rt.mydomain.com
/opt/rt4/bin/rt-mailgate: temp file is '/tmp/CWFzDoGg58/O86pl2Sf7i'
/opt/rt4/bin/rt-mailgate: connecting to http://rt.mydomain.com/REST/1.
0/NoAuth/mail-gateway
not ok - Message is a bounce

</snip>

RT_SiteConfig.pm:

use utf8;
Plugin('RT::IR');
Plugin('RT::Extension::ResetPassword');
Set( $rtname, 'mydomain.com');
Set( $Organization, 'rt.mydomain.com <http://rt.mydsomain.com>');
Set( $Timezone, 'US/Central');
Set( $WebDomain, 'rt.mydomain.com <http://rt.reyesautomotive.com>');
Set( $WebPort, 443);
Set( $WebPath, '');
Set($CorrespondAddress, 'incident@rt.mydomain.com
<incident@rt.reyesautomotive.com>');
Set($CommentAddress, 'incident-comments@rt.mydomain.com
<incident-comments@rt.reyesautomotive.com>');
Set($LogToFile, 'debug');
Set($LogToFileNamed, "rt.log"); #log to rt.log
Set($LogDir, '/opt/rt4/var/log');
#Set($RTAddressRegexp,qr{^(?:incident(?:-comment|-comments|
)\@rt\.mydomain\.com)$}i);
Set($OwnerEmail, 'jayson');
Set($LoopsToRTOwner, 1);
# You must install Plugins on your own, this is only an example
# of the correct syntax to use when activating them:
# Plugin( "RT::Authen::ExternalAuth" );




rt.log


[18000] [Fri Jan 20 04:29:36 2017] [debug]: Converting 'utf-8' to 'utf-8'
for text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:289)
[18000] [Fri Jan 20 04:29:36 2017] [debug]: Converting 'utf-8' to 'utf-8'
for text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:289)
[18000] [Fri Jan 20 04:29:36 2017] [debug]: Encode::Guess guessed encoding:
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:568)
[18000] [Fri Jan 20 04:29:36 2017] [debug]: Encode::Guess guessed encoding:
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:568)
[18000] [Fri Jan 20 04:29:36 2017] [critical]: RT Received mail
(<CAM32JiSrEQj1+E62+mYaSbi2r+pq=kxAqC_EB9LBQDLzgts+Hw@mail.gmail.com>
) from itself. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:506)
[18000] [Fri Jan 20 04:29:36 2017] [crit]: RT Bounce: Test: RT thinks this
message may be a bounce (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:698)
Re: RT Bounces [ In reply to ]
Dunno if this helps or not, but maybe the bounce is due to it detecting a loop?



[18000] [Fri Jan 20 04:29:36 2017] [critical]: RT Received mail (<CAM32JiSrEQj1+E62+mYaSbi2r+pq=kxAqC_EB9LBQDLzgts+Hw@mail.gmail.com <mailto:kxAqC_EB9LBQDLzgts%2BHw@mail.gmail.com> >
) from itself. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:506)



Try and take a look at /opt/rt4/lib/RT/Interface/Email.pm around the line numbers reported.

Not suggesting you change anything, looking might give you a few clues…



You didn’t specify a version – this is what I see in 4.2.12.



<snip>

#if it's from a postmaster or mailer daemon, it's likely a bounce.



#TODO: better algorithms needed here - there is no standards for

#bounces, so it's very difficult to separate them from anything

#else. At the other hand, the Return-To address is only ment to be

#used as an error channel, we might want to put up a separate

#Return-To address which is treated differently.



#TODO: search through the whole email and find the right Ticket ID.

<snip>



<snip>

Checks the message to see if it's a bounce, if it looks like a loop, if it's autogenerated, etc.

Returns a triple of ("Should we continue (boolean)", "New value for $ErrorsTo", "Status message",

"This message appears to be a loop (boolean)" );

<snip>



<snip>

# send mail to the sender

if ( $IsBounce || $IsSuspiciousSender || $IsAutoGenerated || $IsALoop ) {

$SquelchReplies = 1;

$ErrorsTo = $owner_mail;

}



# Warn someone if it's a loop, before we drop it on the ground

if ($IsALoop) {

$RT::Logger->crit("RT Received mail (".$args{MessageId}.") from itself.");



#Should we mail it to RTOwner?

if ( RT->Config->Get('LoopsToRTOwner') ) {

MailError(

To => $owner_mail,

Subject => "RT Bounce: ".$args{'Subject'},

Explanation => "RT thinks this message may be a bounce",

MIMEObj => $args{Message}

);

}



#Do we actually want to store it?

return ( 0, $ErrorsTo, "Message Bounced", $IsALoop )

unless RT->Config->Get('StoreLoops');

}

<snip>



Anyway, just a thought.

If it is a bounce loop, might be related to SSL/certificates?



Regards,

Brett





From: rt-users [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jayson Antillon
Sent: Friday, 20 January 2017 3:34 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] RT Bounces



Hello,

I have searched through the list archives, and read a ton of posts regarding bounces but have not been able narrow down what issue I am having specifically. I have not modified any scrips from default. Have one queue that is in use "Incident Reports', with the addresses incident@rt.mydomain.com <mailto:incident@rt.mydomain.com> and incident-comments@rt.mydomain.com <mailto:incident-comments@rt.mydomain.com> configured in /etc/aliases, any response to the autogenerated emails or new emails to sent to incident@rt.mydomains.com <mailto:incident@rt.mydomains.com> are showing bounces.

I will include as much information as I have seen asked for in other posts.



/etc/aliases

<snip>
# See man 5 aliases for format
incident: "|/opt/rt4/bin/rt-mailgate --queue 'Incident Reports' --no-verify-ssl --action correspond --url https://rt.mydomain.com"
incident-comments: "|/opt/rt4/bin/rt-mailgate --queue 'Incident Reports' --no-verify-ssl --action comment --url https://rt.mydomain.com"



Bounce message:

<snip>

From MAILER-DAEMON Thu Jan 19 22:11:35 2017
Return-Path: <>
X-Original-To: jayson
Delivered-To: jayson@rt.mydomain.com <mailto:jayson@rt.mydomain.com>
Received: by rt.mydomain.com <http://rt.mydomain.com> (Postfix, from userid 33)
id AEF0A140AB8; Thu, 19 Jan 2017 22:11:35 -0600 (CST)
Content-Type: multipart/mixed; boundary="----------=_1484885495-18000-19"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.508 (Entity 5.508)
To: jayson@rt.mydomain.com <mailto:jayson@rt.mydomain.com>
Precedence: bulk
Subject: RT Bounce:
From: incident@rt.mydomain.com <mailto:incident@rt.mydomain.com>
Date: Thu, 19 Jan 2017 22:11:35 -0600
Message-Id: <20170120041135.AEF0A140AB8@rt.mydomain.com <mailto:20170120041135.AEF0A140AB8@rt.mydomain.com> >

This is a multi-part message in MIME format...

------------=_1484885495-18000-19
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary

RT thinks this message may be a bounce

------------=_1484885495-18000-19--



</snip>

mail log from rt server

Jan 19 22:21:25 rt postfix/smtpd[18877]: connect from mail-yw0-f180.google.com <http://mail-yw0-f180.google.com> [209.85.161.180]
Jan 19 22:21:26 rt postfix/smtpd[18877]: 05F14140AAD: client=mail-yw0-f180.google.com <http://mail-yw0-f180.google.com> [209.85.161.180]
Jan 19 22:21:26 rt postfix/cleanup[18881]: 05F14140AAD: message-id=<CAM32JiToL_cmdW72=D-_PPu_zfHR7UbcNCvF8NEt=bKkYm8WqQ@mail.gmail.com <mailto:bKkYm8WqQ@mail.gmail.com> >
Jan 19 22:21:26 rt postfix/qmgr[13852]: 05F14140AAD: from=<jayson@private.com <mailto:jayson@private.com> >, size=2522, nrcpt=1 (queue active)
Jan 19 22:21:26 rt postfix/smtpd[18877]: disconnect from mail-yw0-f180.google.com <http://mail-yw0-f180.google.com> [209.85.161.180]
Jan 19 22:21:26 rt postfix/local[18882]: 05F14140AAD: to=<incident@rt.mydomain.com <mailto:incident@rt.mydomain.com> >, relay=local, delay=0.93, delays=0.56/0.02/0/0.35, dsn=2.0.0, status=sent (delivered to command: /opt/rt4/bin/rt-mailgate --queue 'Incident Reports' --no-verify-ssl --action correspond --url https://rt.mydomain.com

</snip>

RT Mail gate test from commandline:

root@rt:/opt/rt4/etc# cat /usr/bin/test | /opt/rt4/bin/rt-mailgate --debug --queue 'Incident Reports' --url http://rt.mydomain.com
/opt/rt4/bin/rt-mailgate: temp file is '/tmp/CWFzDoGg58/O86pl2Sf7i'
/opt/rt4/bin/rt-mailgate: connecting to http://rt.mydomain.com/REST/1.0/NoAuth/mail-gateway
not ok - Message is a bounce

</snip>

RT_SiteConfig.pm:

use utf8;
Plugin('RT::IR');
Plugin('RT::Extension::ResetPassword');
Set( $rtname, 'mydomain.com <http://mydomain.com> ');
Set( $Organization, 'rt.mydomain.com <http://rt.mydsomain.com> ');
Set( $Timezone, 'US/Central');
Set( $WebDomain, 'rt.mydomain.com <http://rt.reyesautomotive.com> ');
Set( $WebPort, 443);
Set( $WebPath, '');
Set($CorrespondAddress, 'incident@rt.mydomain.com <mailto:incident@rt.reyesautomotive.com> ');
Set($CommentAddress, 'incident-comments@rt.mydomain.com <mailto:incident-comments@rt.reyesautomotive.com> ');
Set($LogToFile, 'debug');
Set($LogToFileNamed, "rt.log"); #log to rt.log
Set($LogDir, '/opt/rt4/var/log');
#Set($RTAddressRegexp,qr{^(?:incident(?:-comment|-comments|)\@rt\.mydomain\.com)$}i);
Set($OwnerEmail, 'jayson');
Set($LoopsToRTOwner, 1);
# You must install Plugins on your own, this is only an example
# of the correct syntax to use when activating them:
# Plugin( "RT::Authen::ExternalAuth" );





rt.log


[18000] [Fri Jan 20 04:29:36 2017] [debug]: Converting 'utf-8' to 'utf-8' for text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:289)
[18000] [Fri Jan 20 04:29:36 2017] [debug]: Converting 'utf-8' to 'utf-8' for text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:289)
[18000] [Fri Jan 20 04:29:36 2017] [debug]: Encode::Guess guessed encoding: ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:568)
[18000] [Fri Jan 20 04:29:36 2017] [debug]: Encode::Guess guessed encoding: ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:568)
[18000] [Fri Jan 20 04:29:36 2017] [critical]: RT Received mail (<CAM32JiSrEQj1+E62+mYaSbi2r+pq=kxAqC_EB9LBQDLzgts+Hw@mail.gmail.com <mailto:kxAqC_EB9LBQDLzgts%2BHw@mail.gmail.com> >
) from itself. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:506)
[18000] [Fri Jan 20 04:29:36 2017] [crit]: RT Bounce: Test: RT thinks this message may be a bounce (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:698)
Re: RT Bounces [ In reply to ]
Brett,

That is what the error is indicating, I just cannot seem to determine where
the loop is. If I misconfigured the queue, or if it was in RT_Siteconfig.
Also it is 4.4.1 on Ubuntu 14.04. I am quite sure it is a misconfiguration
on my part but (i tried with RTAddressRegexp configured for the queue
addresses and without), I know outbound mail is sent when creating the
tickets from incident@ when opened in that queue, should it be something
more generic like rt@ .

(line 509 of Email.pm)
# Warn someone if it's a loop, before we drop it on the ground
if ($IsALoop) {
my $MessageId = Encode::decode( "UTF-8", $head->get('Message-ID') );
$RT::Logger->crit("RT Received mail ($MessageId) from itself.");

</snip>



On Thu, Jan 19, 2017 at 11:15 PM, Brett Chambers <bchambers@ambertech.com.au
> wrote:

> Dunno if this helps or not, but maybe the bounce is due to it detecting a
> loop?
>
>
>
> [18000] [Fri Jan 20 04:29:36 2017] [critical]: RT Received mail
> (<CAM32JiSrEQj1+E62+mYaSbi2r+pq=kxAqC_EB9LBQDLzgts+Hw@mail.gmail.com>
> ) from itself. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:506)
>
>
>
> Try and take a look at /opt/rt4/lib/RT/Interface/Email.pm around the line
> numbers reported.
>
> Not suggesting you change anything, looking might give you a few clues…
>
>
>
> You didn’t specify a version – this is what I see in 4.2.12.
>
>
>
> <snip>
>
> #if it's from a postmaster or mailer daemon, it's likely a bounce.
>
>
>
> #TODO: better algorithms needed here - there is no standards for
>
> #bounces, so it's very difficult to separate them from anything
>
> #else. At the other hand, the Return-To address is only ment to be
>
> #used as an error channel, we might want to put up a separate
>
> #Return-To address which is treated differently.
>
>
>
> #TODO: search through the whole email and find the right Ticket ID.
>
> <snip>
>
>
>
> <snip>
>
> Checks the message to see if it's a bounce, if it looks like a loop, if
> it's autogenerated, etc.
>
> Returns a triple of ("Should we continue (boolean)", "New value for
> $ErrorsTo", "Status message",
>
> "This message appears to be a loop (boolean)" );
>
> <snip>
>
>
>
> <snip>
>
> # send mail to the sender
>
> if ( $IsBounce || $IsSuspiciousSender || $IsAutoGenerated || $IsALoop
> ) {
>
> $SquelchReplies = 1;
>
> $ErrorsTo = $owner_mail;
>
> }
>
>
>
> # Warn someone if it's a loop, before we drop it on the ground
>
> if ($IsALoop) {
>
> $RT::Logger->crit("RT Received mail (".$args{MessageId}.") from
> itself.");
>
>
>
> #Should we mail it to RTOwner?
>
> if ( RT->Config->Get('LoopsToRTOwner') ) {
>
> MailError(
>
> To => $owner_mail,
>
> Subject => "RT Bounce: ".$args{'Subject'},
>
> Explanation => "RT thinks this message may be a bounce",
>
> MIMEObj => $args{Message}
>
> );
>
> }
>
>
>
> #Do we actually want to store it?
>
> return ( 0, $ErrorsTo, "Message Bounced", $IsALoop )
>
> unless RT->Config->Get('StoreLoops');
>
> }
>
> <snip>
>
>
>
> Anyway, just a thought.
>
> If it is a bounce loop, might be related to SSL/certificates?
>
>
>
> Regards,
>
> Brett
>
>
>
>
>
> *From:* rt-users [mailto:rt-users-bounces@lists.bestpractical.com] *On
> Behalf Of *Jayson Antillon
> *Sent:* Friday, 20 January 2017 3:34 PM
> *To:* rt-users@lists.bestpractical.com
> *Subject:* [rt-users] RT Bounces
>
>
>
> Hello,
>
> I have searched through the list archives, and read a ton of posts
> regarding bounces but have not been able narrow down what issue I am having
> specifically. I have not modified any scrips from default. Have one queue
> that is in use "Incident Reports', with the addresses
> incident@rt.mydomain.com and incident-comments@rt.mydomain.com configured
> in /etc/aliases, any response to the autogenerated emails or new emails to
> sent to incident@rt.mydomains.com are showing bounces.
>
> I will include as much information as I have seen asked for in other
> posts.
>
> /etc/aliases
>
> <snip>
> # See man 5 aliases for format
> incident: "|/opt/rt4/bin/rt-mailgate --queue 'Incident Reports'
> --no-verify-ssl --action correspond --url https://rt.mydomain.com"
> incident-comments: "|/opt/rt4/bin/rt-mailgate --queue 'Incident
> Reports' --no-verify-ssl --action comment --url https://rt.mydomain.com"
>
>
>
> Bounce message:
>
> <snip>
>
> From MAILER-DAEMON Thu Jan 19 22:11:35 2017
> Return-Path: <>
> X-Original-To: jayson
> Delivered-To: jayson@rt.mydomain.com
> Received: by rt.mydomain.com (Postfix, from userid 33)
> id AEF0A140AB8; Thu, 19 Jan 2017 22:11:35 -0600 (CST)
> Content-Type: multipart/mixed; boundary="----------=_1484885495-18000-19"
> Content-Transfer-Encoding: binary
> MIME-Version: 1.0
> X-Mailer: MIME-tools 5.508 (Entity 5.508)
> To: jayson@rt.mydomain.com
> Precedence: bulk
> Subject: RT Bounce:
> From: incident@rt.mydomain.com
> Date: Thu, 19 Jan 2017 22:11:35 -0600
> Message-Id: <20170120041135.AEF0A140AB8@rt.mydomain.com>
>
> This is a multi-part message in MIME format...
>
> ------------=_1484885495-18000-19
> Content-Type: text/plain; charset="UTF-8"
> Content-Disposition: inline
> Content-Transfer-Encoding: binary
>
> RT thinks this message may be a bounce
>
> ------------=_1484885495-18000-19--
>
> </snip>
>
> mail log from rt server
>
> Jan 19 22:21:25 rt postfix/smtpd[18877]: connect from
> mail-yw0-f180.google.com[209.85.161.180]
> Jan 19 22:21:26 rt postfix/smtpd[18877]: 05F14140AAD: client=
> mail-yw0-f180.google.com[209.85.161.180]
> Jan 19 22:21:26 rt postfix/cleanup[18881]: 05F14140AAD:
> message-id=<CAM32JiToL_cmdW72=D-_PPu_zfHR7UbcNCvF8NEt=bKkYm8
> WqQ@mail.gmail.com>
> Jan 19 22:21:26 rt postfix/qmgr[13852]: 05F14140AAD: from=<
> jayson@private.com>, size=2522, nrcpt=1 (queue active)
> Jan 19 22:21:26 rt postfix/smtpd[18877]: disconnect from
> mail-yw0-f180.google.com[209.85.161.180]
> Jan 19 22:21:26 rt postfix/local[18882]: 05F14140AAD: to=<
> incident@rt.mydomain.com>, relay=local, delay=0.93,
> delays=0.56/0.02/0/0.35, dsn=2.0.0, status=sent (delivered to command:
> /opt/rt4/bin/rt-mailgate --queue 'Incident Reports' --no-verify-ssl
> --action correspond --url https://rt.mydomain.com
>
> </snip>
>
> RT Mail gate test from commandline:
>
> root@rt:/opt/rt4/etc# cat /usr/bin/test | /opt/rt4/bin/rt-mailgate
> --debug --queue 'Incident Reports' --url http://rt.mydomain.com
> /opt/rt4/bin/rt-mailgate: temp file is '/tmp/CWFzDoGg58/O86pl2Sf7i'
> /opt/rt4/bin/rt-mailgate: connecting to http://rt.mydomain.com/REST/1.
> 0/NoAuth/mail-gateway
> not ok - Message is a bounce
>
> </snip>
>
> RT_SiteConfig.pm:
>
> use utf8;
> Plugin('RT::IR');
> Plugin('RT::Extension::ResetPassword');
> Set( $rtname, 'mydomain.com');
> Set( $Organization, 'rt.mydomain.com <http://rt.mydsomain.com>');
> Set( $Timezone, 'US/Central');
> Set( $WebDomain, 'rt.mydomain.com <http://rt.reyesautomotive.com>');
> Set( $WebPort, 443);
> Set( $WebPath, '');
> Set($CorrespondAddress, 'incident@rt.mydomain.com
> <incident@rt.reyesautomotive.com>');
> Set($CommentAddress, 'incident-comments@rt.mydomain.com
> <incident-comments@rt.reyesautomotive.com>');
> Set($LogToFile, 'debug');
> Set($LogToFileNamed, "rt.log"); #log to rt.log
> Set($LogDir, '/opt/rt4/var/log');
> #Set($RTAddressRegexp,qr{^(?:incident(?:-comment|-comments|
> )\@rt\.mydomain\.com)$}i);
> Set($OwnerEmail, 'jayson');
> Set($LoopsToRTOwner, 1);
> # You must install Plugins on your own, this is only an example
> # of the correct syntax to use when activating them:
> # Plugin( "RT::Authen::ExternalAuth" );
>
>
>
> rt.log
>
>
> [18000] [Fri Jan 20 04:29:36 2017] [debug]: Converting 'utf-8' to 'utf-8'
> for text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:289)
> [18000] [Fri Jan 20 04:29:36 2017] [debug]: Converting 'utf-8' to 'utf-8'
> for text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:289)
> [18000] [Fri Jan 20 04:29:36 2017] [debug]: Encode::Guess guessed
> encoding: ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:568)
> [18000] [Fri Jan 20 04:29:36 2017] [debug]: Encode::Guess guessed
> encoding: ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:568)
> [18000] [Fri Jan 20 04:29:36 2017] [critical]: RT Received mail
> (<CAM32JiSrEQj1+E62+mYaSbi2r+pq=kxAqC_EB9LBQDLzgts+Hw@mail.gmail.com>
> ) from itself. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:506)
> [18000] [Fri Jan 20 04:29:36 2017] [crit]: RT Bounce: Test: RT thinks this
> message may be a bounce (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:698)
>
>