Message from customer keeps getting marked bad header

[Jerry Pommer]

On 09/13/2012 10:42 AM, Jeffrey Walls wrote:
>
> We have a very important customer who is getting pissed off that all 
> his PO's sent from his ERP system keep getting bounced.
>
> The issue is both our CSR and his person sending the PO are both on 
> the To: line.
>
> He gets a bounce message:
>
>       Subject:  Purchase Order from XXXXXXX XXXXXX Company: PO#300003466
>
>       Sent:     9/13/2012 11:26 AM
>
> The following recipient(s) cannot be reached:
>
> jwalls@/browntransmission/.com <mailto:jwalls at browntransmission.com> 
> on 9/13/2012 11:27 AM
>
>             The message contains a content type that is not supported
>
>             < kolab.browntransmission.com #5.6.0 smtp; 554-5.6.0 
> Reject, id=03482-10 - BAD_HEADER: Duplicate 554 5.6.0 header field: "To">
>
> In the actual badh file this is part of the header:
>
> X-OptioDCS-Version: 7.7.3
>
> MIME-Version: 1.0
>
> Content-Type: multipart/mixed; boundary="==========_1347550011==_"
>
> Date: Thu, 13 Sep 2012 11:26 EDT
>
> From: brian.xxxxx at xxxxx.com
>
> To: jwalls at browntransmission.com
>
> To: brian.xxxxx at xxxxxx.com
>
> Is there any way to allow this error or simply not check for it? I can 
> send the PO, but that doesn't solve the issue, and if I am not here we 
> are back to square one.
>
>

Jeffrey,

Quick and easy way, edit 
/kolab/etc/kolab/templates/amavisd.conf.template and find this line:

$final_bad_header_destiny = D_BOUNCE;  # (defaults to D_PASS), D_BOUNCE 
suggested

My example is set to D_BOUNCE, and yours probably is too. If you change 
that to D_PASS instead the message should be delivered, if possible. Bad 
headers are bad headers though, so you can't always be sure of what will 
happen.

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20120913/f84b526b/attachment.html>