On Tue, Aug 23, 2011 at 8:28 AM, [email protected] <[email protected]> wrote: > we have (limited) success !! > > Thanks very much - I can now receive plain text emails from google. > > 1) I had to download the springsource framework and put all of the .jar > files into the "optional" directory as well > 2) some of the demo parameters have changed since camel 2.0. These include > "deleteProcessedMessages" now "delete" and "processOnlyUnseenMessages" now > "unseen"
Must be some old demo. What demo do you refer to? You can see the mail component options here http://camel.apache.org/mail.html > > However, my stomp client only gets the headers and properties for email with > a header of "Content_HYPHEN_Type:multipart/alternative; " for plain text > email, I get the full body. > The JMS spec is limited in what you can send and has restrictions on key names for JMS properties. You cannot use a - sign, so Camel will by default convert - to _HYPHEN_. On the consumer side you would have to restore this, as you are not using Camel. If you dont want this to happen by Camel you can configure a different key format strategy, using the option: jmsKeyFormatStrategy You can read more about this at http://camel.apache.org/jms > I presume that this is something to do with plaintext vs binary in the stomp > message, but how do I get MQ to send a binary stomp message to a client ? > A multipart mail message is all text based, the content is text based encoded in the mail. For stomp and AMQ questions then I would suggest to try the AMQ mailing list also. > Many thanks for the help so far. Impossible to have done this without the > help. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Teach-a-man-to-fish-tp4722377p4725645.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
