I have installed RT and have successfully created the users and queues I need to begin managing requests. Emails addressed to queuename@myrt.blahmailto:queuename@myrt.blah create a ticket and the autoreply generates exactly as expected.
When I do this, tickets create, but the autoresponse doesn’t fire.
Does anyone have any insight as to how I can correct this? I used and maintained RT at another organization, but they had a Virtual Post Office that handled the redirection and delivery. I do not have such a setup available to me here.
I have installed RT and have successfully created the users and queues
I need to begin managing requests. Emails addressed to
queuename@myrt.blah mailto:queuename@myrt.blah create a ticket and
the autoreply generates exactly as expected.
I’ve looked at the headers from one of the messages and I cannot find anything related to bulk preference (literally, a string search cannot find “bulk” anywhere in the headers), but I do have a line “RT-Squelch-Replies-To” which is populated with the sender’s address.
I’ve so far been unable to find anywhere I can disable this.
I have installed RT and have successfully created the users and queues I need to begin managing requests. Emails addressed to queuename@myrt.blahmailto:queuename@myrt.blah create a ticket and the autoreply generates exactly as expected.
I�ve looked at the headers from one of the messages and I cannot find
anything related to bulk preference (literally, a string search cannot
find �bulk� anywhere in the headers), but I do have a line
�RT-Squelch-Replies-To� which is populated with the sender�s address.
I�ve so far been unable to find anywhere I can disable this.
Further suggestions?
Searching through the source of rt-4.2.5 I had lying around I came
across RedistributeAutoGeneratedMessages. What is this config parameter
set to in RT_Config.pm and more importantly RT_SiteConfig.pm?
Its indicating that it shouldn’t redistribute messages to unprivilged users.
What might be helpful too is headers captured at the Exchange level and
again at the RT level. Maybe somebody will spot the problem.
I’ve also opened a support ticket with Microsoft to see if they can strip the header at the Exchange level. Not terribly hopeful.From: rt-users [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Joop
Sent: Wednesday, July 29, 2015 5:04 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Creating Tickets in RT with a redirected email
Thanks for your insight.
I’ve looked at the headers from one of the messages and I cannot find anything related to bulk preference (literally, a string search cannot find “bulk” anywhere in the headers), but I do have a line “RT-Squelch-Replies-To” which is populated with the sender’s address.
I’ve so far been unable to find anywhere I can disable this.
Further suggestions?
Searching through the source of rt-4.2.5 I had lying around I came across RedistributeAutoGeneratedMessages. What is this config parameter set to in RT_Config.pm and more importantly RT_SiteConfig.pm?
Its indicating that it shouldn’t redistribute messages to unprivilged users.
What might be helpful too is headers captured at the Exchange level and again at the RT level. Maybe somebody will spot the problem.
I did grep that config setting in RT_Config.pm and changed it to unprivileged with no result. It did not appear in RT_SiteConfig.pm at all.
Headers captured at the RT level are below. Unfortunately it doesn’t appear that Exchange writes a sent item on redirected messages and I haven’t yet been able to find it in the Office365 Exchange management portal either.
X-MS-Exchange-Crosstenant-Fromentityheader: Hosted
X-MS-Exchange-Crosstenant-Fromentityheader: Hosted
MIME-Version: 1.0
X-MS-Exchange-Parent-Message-ID: BN4PR11MB094521C3BAAD82602829338AD28D0@BN4PR11MB0945.namprd11.prod.outlook.com
Content-Type: multipart/related; boundary=“004_613ca39631a2450d834ccfd0a1d0b7dbBLUPR11MB0083namprd11pr”; type=“multipart/alternative”
X-MS-Exchange-Transport-Endtoendlatency: 00:00:02.2154948
X-Exchange-Antispam-Report-Test: UriScan:(108003899814671);UriScan:(108003899814671);
Authentication-Results: hoosiercancer.org; dkim=none (message not signed) header.d=none;
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0077.outbound.protection.outlook.com [157.56.111.77]) by rt.hcrn.hoosiercancer.org (Postfix) with ESMTP id 50F8B80396 for hcrntech@hcrnsupport.org; Tue, 28 Jul 2015 08:49:48 -0400 (EDT)
Received: from BLUPR11MB0083.namprd11.prod.outlook.com (10.160.37.20) by BLUPR11MB0082.namprd11.prod.outlook.com (10.160.37.19) with Microsoft SMTP Server (TLS) id 15.1.225.19; Tue, 28 Jul 2015 12:49:47 +0000
Received: from BLUPR11MB0083.namprd11.prod.outlook.com ([127.0.0.1]) by BLUPR11MB0083.namprd11.prod.outlook.com ([10.160.37.20]) with Microsoft SMTP Server id 15.01.0225.018; Tue, 28 Jul 2015 12:49:46 +0000
Delivered-To: myqueue@myrtserver.blah
Thread-Index: AdDJM6IG3diL5wq8SWqD03TgSgnalg==
X-Originatororg: myhostedmaildomain.blah
X-MS-Exchange-Crosstenant-ID: 7339cc1b-025e-4d51-bde7-1fa620901b4d
X-MS-Exchange-Crosstenant-ID: 7339cc1b-025e-4d51-bde7-1fa620901b4d
X-Microsoft-Exchange-Diagnostics-Untrusted: 1;DM2PR11MB0089;23:2F4CAPMDkYchYvGtZHqZ+i36MXpYRQp87riCUgq50gUFkaGJN0jZfjbjMlxrkwInZDnnHdl/L9rXJ0lmjfliKcn2ksBmDFdtVRoOWOZYufyWjxfgZLd2iWDicucUtMplmbzzT8TgAozsIxnzsP5OmdpbrzT9Gm+/bPARsk3R3yh0bNFWG6oRoWWrY5Z1jMTErFHgQPFQZEBgSPjIbFu+gS7SpiQfiiZIfyRayoX4SFhblLAjMB9rZTCJZAQrHDy/;5:Hwb8QMGk597nYwz3sKsKL+Fi8hO4oaZphESS86Rwbo6llfaj6BiPc75c91DCTJcNhzEfwoBlBqqc4XZeiGGTzICW9k5m0XA3EQ3y2P8oOxSGnB5DNPrr1uz2Wyg+w7LoBVk1tOvpF3fyjGVuAdQTzA==;24:oEdwayxinVTjzuDCWVUNrZ5sjb8u1PjfijYk2KS9eyMXm+HFzRnIFaU8q/Gmloi8C2lYtAdExITHhKCwK7Btcno92t9YQd2hljQRsSv8bBc=;20:/BDFa27uqdsepSdFM+mAboO/dEMGbv11kB7382KPKxdwN/xns5NVPUvB0JhdWASr9HHqnKL7xdiZ1eCydb7pMA==
X-Exchange-Antispam-Report-Cfa-Test: BCL:0;PCL:0;RULEID:(601004)(3002001);SRVR:DM2PR11MB0089;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0089;BCL:0;PCL:0;RULEID:(601004)(5005006)(3002001);SRVR:BLUPR11MB0082;BCL:0;PCL:0;RULEID:;SRVR:BLUPR11MB0082;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0089;UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR11MB0082;
I’ve looked at the headers from one of the messages and I cannot find anything related to bulk preference (literally, a string search cannot find “bulk” anywhere in the headers), but I do have a line “RT-Squelch-Replies-To” which is populated with the sender’s address.
I’ve so far been unable to find anywhere I can disable this.
Further suggestions?
Searching through the source of rt-4.2.5 I had lying around I came across RedistributeAutoGeneratedMessages. What is this config parameter set to in RT_Config.pm and more importantly RT_SiteConfig.pm?
Its indicating that it shouldn’t redistribute messages to unprivilged users.
What might be helpful too is headers captured at the Exchange level and again at the RT level. Maybe somebody will spot the problem.
I did grep that config setting in RT_Config.pm and changed it to
unprivileged with no result. It did not appear in RT_SiteConfig.pm at
all.
Headers captured at the RT level are below. Unfortunately it doesn�t
appear that Exchange writes a sent item on redirected messages and I
haven�t yet been able to find it in the Office365 Exchange management
portal either.
I did grep that config setting in RT_Config.pm and changed it to
unprivileged with no result. It did not appear in RT_SiteConfig.pm at all.
The proper way to do this is to copy the setting from RT_Config.pm to
RT_SiteConfig.pm and change it there. That way you won’t loose your
changes when you upgrade to a newer RT and RT_Config.pm changes under
your feet. RT_SiteConfig.pm logically overwrites RT_Config.pm as far as
settings go and doesn’t change during upgrades.
On 29-7-2015 1:12, Joop writes:>On 29-7-2015 1:12, Jeff Smith wrote:
Thanks for your insight.
I’ve looked at the headers from one of the messages and I cannot find
anything related to bulk preference (literally, a string search cannot
find “bulk” anywhere in the headers), but I do have a line
“RT-Squelch-Replies-To” which is populated with the sender’s address.
I’ve so far been unable to find anywhere I can disable this.
Further suggestions?
Searching through the source of rt-4.2.5 I had lying around I came
across RedistributeAutoGeneratedMessages. What is this config parameter
set to in RT_Config.pm and more importantly RT_SiteConfig.pm?
Its indicating that it shouldn’t redistribute messages to unprivilged users.
What might be helpful too is headers captured at the Exchange level and
again at the RT level. Maybe somebody will spot the problem.
The text “RT-Squelch-Replies-To” occurs in:
lib/RT/Action/SendEmail.pm (sub RemoveInappropriateRecipients)
lib/RT/Interface/Email.pm (sub _HandleMachineGeneratedMail)
I don’t know which is preventing the mail you want, but one of these files is the one you want to patch.
/jeff
PS: the Email.pm file has a documentation error fir the _HandleMachineGeneratedMail sub:
Returns a triple of (…
Should be:
Returns a quad of (…
Since there are 4 values.
The information contained in this e-mail is for the exclusive use of the
intended recipient(s) and may be confidential, proprietary, and/or
legally privileged. Inadvertent disclosure of this message does not
constitute a waiver of any privilege. If you receive this message in
error, please do not directly or indirectly use, print, copy, forward,
or disclose any part of this message. Please also delete this e-mail
and all copies and notify the sender. Thank you.