GitHub user svanders opened a pull request:

    https://github.com/apache/camel/pull/453

    8569 Ability to easily extract email attachments

    Pull request for feature request 
https://issues.apache.org/jira/browse/CAMEL-8569
    
    Ability to easily extract email attachments
    
    The existing support for splitting an email by it's attachments 
(org.apache.camel.component.mail.SplitAttachmentsExpression) is limiting that 
the attachments are still mime encoded, and cannot be easily used by the next 
stage in a route.
    e.g.
    ```
    from("pop3://ja...@mymailserver.com?...
    .split(new SplitAttachmentsExpression())
    .to("file:///myAttachmentsFolder")
    ```
    doesn't work
    An improved splitter that decodes the mime parts into byte arrays would be 
more useful
    
    Added an alternative to SplitAttachmentsExpression called 
ExtractAttachmentsExpression
    which will split a (multipart) mime encoded email into new camel messages 
where the body of each message is the email attachment as a byte array, with a 
header "CamelSplitAttachmentName" containing the attachment name.
     

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/svanders/camel 
8569-AbilityToEasilyExtractEmailAttachments

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/453.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #453
    
----
commit 1cdb685115e802eb129454aad1fb2767c6e8a585
Author: Simon van der Sluis <simon.vandersl...@edmi.co.nz>
Date:   2015-03-29T22:42:37Z

    8569 Ability to easily extract email attachments
    
    Code + unit for feature request 8569-Ability to easily extract email 
attachments

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to