Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 26 Jun 2011 11:16:47 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1722325086.41292.1309087007498.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1553227249.616.1307869071444.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-4093) pop3 component parameter
 deliverRawMailMessage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055052#comment-13055052 ] 

Claus Ibsen commented on CAMEL-4093:
------------------------------------

You should be able to do this already. There is a Camel MailMessage type which allows you to get access to the javax.mail.Message instance where you can get the raw message.

I have just committed an unit test showing that
http://svn.apache.org/viewvc?rev=1139760&view=rev

> pop3 component parameter deliverRawMailMessage
> ----------------------------------------------
>
>                 Key: CAMEL-4093
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4093
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-mail
>    Affects Versions: 2.7.2
>         Environment: Solaris and Windows
>            Reporter: Dr. Martin Menzel
>            Assignee: Richard Kettelerij
>            Priority: Minor
>             Fix For: 2.9.0
>
>         Attachments: CAMEL-4093.diff, CAMEL-4093_with_unit_test.diff
>
>
> Old Subject: s/Mime signed Mails lead to Exceptions in pop3 component
> If a s/mime signed Mail is received by the pop3 Mail component a expection is thrown during handling the body of the message. This happens because a different type of body object is delivered by javamail.
> I fixed this issue by introducing a new parameter which makes it possible to deliver the complete mail source in the Camel message body. In this way you are able to handle the content with processors in a very flexiable way.
> ------------ additional remark -------------
> During my preparation of testcases I reduced the complexity of my former project, removed classpath jars just to the basics jars needed to run pop3 retieval. In this situation I don't get the error anymore (for Java DSL and Spring configuration).
> => The included patch is therefore just a new feature which is helpfull if a processor/consumer would like to get the complete mail source instead of just the payload. This can be controlled by a new pop3 component uri parameter  
> deliverRawMailMessage
> example spring  URL: pop3s://camel.test@pop.googlemail.com?password=pazzword&amp;debugMode=true&amp;deliverRawMailMessage=true
> I will deliver a unit test which tests the different behavior without disturbing the normal way of delivering mail content.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira