[rt-users] Occasional errors sending email through RT: Duplicate header field

[Stephen Switzer]

Hello!

    I'm using RT 4.4.1 sitting behind Kolab 16 as a mail server. This 
includes amavisd-new as a filter, and this combination causes bounces to 
RT occasionally... and my customers aren't getting my replies!

    If I send an email to an RT ticket, which I am the owner of, RT 
sends an email on my behalf to the requestor (as it should). 
Unfortunately, amavisd-new sometimes sees 2 "Sender" headers and rejects 
the email which creates a new ticket in RT with the bounce reason. Here' 
the header-1.hdr attachment that amavis replies with:

    Return-Path: <support at example.com>
    Sender: steve at example.com
    MIME-Version: 1.0
    Content-Type: multipart/alternative;
      boundary="=_b308d10660951d296cc57d268c770c5f"
    Sender: Stephen Switzer <steve at example.com>
    Date: Mon, 19 Dec 2016 23:55:55 -0500
    From: "RT, Support" <support at example.com>
    To: support at example.com
    Subject: Re: [SBS #99845] Laptop will not connect to the internet
    In-Reply-To: <rt-4.4.1-1416-1482202966-319.99845-8-0 at example.com>
    References: <RT-Ticket-99845 at example.com>
      <CY4PR10MB16247C062AD6E90C674E7AE1B4900 at CY4PR10MB1624.namprd10.prod.outlook.com>
      <rt-4.4.1-1416-1482202966-319.99845-8-0 at example.com>
    Message-ID: <a1cd0f3d6b0cc448f7d4dd737df29a80 at example.com>
    X-Sender: support at example.com

Yes, I sanitized, even though you can deduce what it really was easily... :)

I grep'd the RT code, and found that lib/RT/Interface/Email.pm seems to 
be what is responsible... but no obvious line that tells me this code is 
used for OUTBOUND email. Can anyone shed some light on this issue? I'd 
be happy to hack code, I just want it fixed.

Thank you!

-- 

Best regards,
Steve

		
Stephen H. Switzer
President & Chief Technical Consultant
	
steve at SBSroc.com <mailto:steve at sbsroc.com>
	
*Main:*
*Cell:*
	
+1 (585) 298-9420 *Ext:* 7001
+1 (585) 202-8312
	
Support Desk:
support at sbsroc.com <mailto:support at sbsroc.com>

		
*Fax:*
	
+1 (585) 625-0020

This e-mail contains proprietary information some or all of which may be 
legally privileged. It is for the intended recipient only. If an 
addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the 
intended recipient you must not use, disclose, distribute, copy, print 
or rely on this e-mail. The content of this email may contain private 
views and opinions, which do not constitute formal disclosure or 
commitment unless specifically stated. We do not enter into legally 
binding agreements via email.

<http://www.sbsroc.com> 
<https://plus.google.com/+SwitzerBusinessSolutionsLLCRochester> 
<https://www.facebook.com/sbsolutions> 
<https://www.linkedin.com/company/switzer-business-solutions-llc> 
<https://twitter.com/sbsroc> 	
The ASCII Group Xorcom Certified Dealer


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SBS ROC Logo
Type: image/png
Size: 4525 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mgomidlggialaikn.png
Type: image/png
Size: 396 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lahmpiomkimgknap.png
Type: image/png
Size: 448 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gmekaflahfokcbga.png
Type: image/png
Size: 558 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: olcloahpcpcmkpfj.png
Type: image/png
Size: 596 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jpaappljbkjmklpi.png
Type: image/png
Size: 521 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cdijcojgleoomdco.png
Type: image/png
Size: 492 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: behiebnpegehlpga.png
Type: image/png
Size: 550 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kjeildkaigibgilo.png
Type: image/png
Size: 569 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jopiinmpdhejjeka.png
Type: image/png
Size: 7205 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: goajcdpahdpgmedm.png
Type: image/png
Size: 5055 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161220/d8e451ff/attachment-0010.png>