Sorry, this is for 1.6.1..

Not sure if removeHeader will help here. For ex: for below route:

from("direct:start")
.processor(customProcessor) //does some processing and sets
mail_alternateBody
.to("smtp://mailhost")

So I cannot remove header before it goes to mail component, and if I remove
it after mail component, it is already to mail envelope?

Any other way to handle this? Let me know if I am confused/missing
something.

Thanks!


Claus Ibsen-2 wrote:
> 
> On Fri, Sep 4, 2009 at 6:06 AM, Claus Ibsen<claus.ib...@gmail.com> wrote:
>> On Thu, Sep 3, 2009 at 11:40 PM, tide08<sachin2...@yahoo.com> wrote:
>>>
>>> I am setting mail_alternateBody header for multipart/alternative and the
>>> problem is that now that header shows up in mail envelope. Header is
>>> added
>>> by custom processor in the route before it comes to mail component. Is
>>> there
>>> a way to tell camel-mail to filter that header? I see that it uses
>>> filterHeaderStrategy but could not figure out how can I configure that?
>>> Any
>>> example?
>>>
>>
> 
> You can use .removeHeader("mail_alternateBody") in the route DSL.
> 
> 
>> Remember to state which version of Camel you are using?
>>
>> I do think we have fixed this in 1.6.2-SNAPSHOT so try that version.
>>
>>
>>> Thanks
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/alternate-body-header-in-mail-envelope-tp25284567p25284567.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
> 
> 
> 
> -- 
> Claus Ibsen
> Apache Camel Committer
> 
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
> 
> 

-- 
View this message in context: 
http://www.nabble.com/alternate-body-header-in-mail-envelope-tp25284567p25298558.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to