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

[Landon Stewart]

On Dec 20, 2016, at 8:46 AM, Stephen Switzer 
> wrote:


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:


Hi Steve,

What is the wording of the actual reason for the bounce within the bounce 
message? What do the headers of the message that bounced look like?  Does the 
email that's being bounced actually have multiple From: fields?  Have you tried 
whitelisting senders in amavisd?


--
Landon Stewart
Lead Analyst - Abuse and Security Management
INTERNAP ®
 lstew...@internap.com
 www.internap.com

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

[Stephen Switzer]

This is actually now happening on every email I try to send to a ticket.
I have customer complaints that I'm not responding when I AM. Any ideas
on this? I'm open to anything... 

Steve 

On 2016-12-20 11:46 am, Stephen Switzer wrote:

> 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: 
>> Sender: st...@example.com
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="=_b308d10660951d296cc57d268c770c5f"
>> Sender: Stephen Switzer 
>> Date: Mon, 19 Dec 2016 23:55:55 -0500
>> From: "RT, Support" 
>> To: supp...@example.com
>> Subject: Re: [SBS #99845] Laptop will not connect to the internet
>> In-Reply-To: 
>> References: 
>> 
>> 
>> Message-ID: 
>> X-Sender: supp...@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 
> 
> st...@sbsroc.com 
> 
> MAIN:
> CELL: 
> +1 (585) 298-9420   EXT: 7001
> +1 (585) 202-8312 
> 
> Support Desk:
> supp...@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. 
> 
> [1]
> [2]
> [3]
> [4]
> [5]
 

Links:
--
[1] http://www.sbsroc.com
[2] https://plus.google.com/+SwitzerBusinessSolutionsLLCRochester
[3] https://www.facebook.com/sbsolutions
[4] https://www.linkedin.com/company/switzer-business-solutions-llc
[5] https://twitter.com/sbsroc

[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: 
   Sender: st...@example.com
   MIME-Version: 1.0
   Content-Type: multipart/alternative;
 boundary="=_b308d10660951d296cc57d268c770c5f"
   Sender: Stephen Switzer 
   Date: Mon, 19 Dec 2016 23:55:55 -0500
   From: "RT, Support" 
   To: supp...@example.com
   Subject: Re: [SBS #99845] Laptop will not connect to the internet
   In-Reply-To: 
   References: 
 

 
   Message-ID: 
   X-Sender: supp...@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

st...@sbsroc.com 

*Main:*
*Cell:*

+1 (585) 298-9420 *Ext:* 7001
+1 (585) 202-8312

Support Desk:
supp...@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.


 
 
 
 
 	

The ASCII Group Xorcom Certified Dealer