[
https://issues.apache.org/jira/browse/CAMEL-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049860#comment-14049860
]
Christoph Giera commented on CAMEL-7536:
----------------------------------------
Personally I don't like the idea of a global resolver in this case.
In my opinion camel and/or smtp does a good job when it is autodetecting the
content-transfer-encoding.
We have a lot of mailing routes, but only one needs this "override" of the
content-transfer-encoding, so I think it's more viable to use an uri parameter.
We also try to don't update our camel-context.xml file as it has too much
impact on all our processes, so configuration as uri parameter is much more
confortable as configuration on the component it self.
But if you say it has to be that way, I will do it. I just wanted to give an
input or rather have implemented this the way I think it is most usefull :).
> camel mail: content-transfer-encoding configurable
> --------------------------------------------------
>
> Key: CAMEL-7536
> URL: https://issues.apache.org/jira/browse/CAMEL-7536
> Project: Camel
> Issue Type: New Feature
> Components: camel-mail
> Reporter: Christoph Giera
> Fix For: 2.14.0
>
> Attachments: camel-mail.patch
>
>
> It should be possible to set the content-transfer-encoding for attachments,
> normally it will be automatically determined based on the content of the
> attachment.
> see
> http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-td5752504.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
