Hi You are welcome. We love contributions. http://camel.apache.org/support
If you could make this optional, so you need to turn this on so it wont affect existing users. Then that would be the best imho. On Wed, Jun 18, 2014 at 3:15 PM, cgiera <christoph.gi...@mic-cust.com> wrote: > Hello, > > the camel mail componente determines the content-transfer-encoding itself > based on the content of the message. > We now have a customer we are only allowed to send messages where the > content-transfer-encoding is base64. As most of the messages haven't any > special characters camel determines 7bit or quoted-printable as > content-transfer-encoding and we are not able to manipulate that. > > I wanted to discuss if content-transfer-encoding would be a viable uri > option(like contentType) for the future. > If so, I would create a ticket and try my best to provide a patch for this. > > kind regards, > Christoph > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
