You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by cgiera <ch...@mic-cust.com> on 2014/06/18 15:15:59 UTC
camel mail: content-transfer-encoding configurable
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.
Re: camel mail: content-transfer-encoding configurable
Posted by cgiera <ch...@mic-cust.com>.
Ticket created, see https://issues.apache.org/jira/browse/CAMEL-7536.
Looking forward to provide a patch.
kind regards,
Christoph
--
View this message in context: http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752791.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel mail: content-transfer-encoding configurable
Posted by cgiera <ch...@mic-cust.com>.
Maybe something similar to the ContentTypeResolver is also a good solution
--
View this message in context: http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752744.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel mail: content-transfer-encoding configurable
Posted by cgiera <ch...@mic-cust.com>.
Hi,
ok, just for clarification what would be a good solution for this:
I've not mentioned that we need the content-transfer-encoding for the
attachments of the mail.
Some ideas from my side:
1. use a parameter like contentType, let's say content-transfer-encoding:
If this parameter is set ALL attachments will have this
content-transfer-encoding.
The problem I see here is that it's probably a bit misleading as the
contentType parameter affects the mailbody and content-transfer-encoding the
attachments. Maybe this issue could be solved by renaming the parameter to
something like "attachment-transfer-encoding"
2. when an attachment will be added to the exchange object the contentType
could be defined like this:
In the org.apache.camel.component.mail.MailBinding class then we extract the
content transfer encoding, for example:
Maybe we discuss the possible solutions before I start patching.
kind regards,
Christoph
--
View this message in context: http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752738.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel mail: content-transfer-encoding configurable
Posted by Claus Ibsen <cl...@gmail.com>.
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 <ch...@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: cibsen@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/