Return-Path: Delivered-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Received: (qmail 4786 invoked from network); 9 Nov 2009 13:08:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Nov 2009 13:08:49 -0000 Received: (qmail 20718 invoked by uid 500); 9 Nov 2009 13:08:49 -0000 Delivered-To: apmail-james-mime4j-dev-archive@james.apache.org Received: (qmail 20696 invoked by uid 500); 9 Nov 2009 13:08:49 -0000 Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mime4j-dev@james.apache.org Delivered-To: mailing list mime4j-dev@james.apache.org Received: (qmail 20686 invoked by uid 99); 9 Nov 2009 13:08:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 13:08:49 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of norman.maurer@googlemail.com designates 74.125.78.150 as permitted sender) Received: from [74.125.78.150] (HELO ey-out-1920.google.com) (74.125.78.150) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 13:08:38 +0000 Received: by ey-out-1920.google.com with SMTP id 26so168557eyw.44 for ; Mon, 09 Nov 2009 05:08:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=W0palQHLLa9VN8Ah5tIlloqAWZUfcdRvgx9odEEh7tM=; b=a4YynCYNHU6+47QY0UOshTay8/RnPK2mL0YAVm9D5VifzPi48QfsGnouqUBNMdbmQM 0VFzKeQDjNuSwZsLXXbd54lIShwGThQLoTUEMb5Pw5jyqAbbR15hvwGTMAloFkt2wR4/ VLUaem4VMsBWOJyNFSmqbkj4eJYTvUefSnrRY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ax6YOUrh3b4UqlfFGdtYdb6bKF6eMiXR+OdySvzlDIbj6FC7AvYazpA2BWyiEitzl3 AN8N9oy8XczI2HtVpmsXXR9hXGPtbqrti5ax677SueTVPDyf0jtGnrGpcrcnbwlrTRV2 YsyiGLYaVXom4PLIq386f2B3CCkv4+/k0UWBM= MIME-Version: 1.0 Sender: norman.maurer@googlemail.com Received: by 10.216.87.68 with SMTP id x46mr2686368wee.2.1257772098198; Mon, 09 Nov 2009 05:08:18 -0800 (PST) In-Reply-To: <4AF812EC.6070309@zimmer428.net> References: <4AF812EC.6070309@zimmer428.net> Date: Mon, 9 Nov 2009 14:08:18 +0100 X-Google-Sender-Auth: f6fdf0c1f8f52b1d Message-ID: <75bda7a00911090508r66328da6j2e0120b20cb43b8b@mail.gmail.com> Subject: Re: using mime4j to work with IMAP messages? From: Norman Maurer To: mime4j-dev@james.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi Kristian, why not use MimeMessage.getRawInputStream() as source for Mime4j ? Bye, Norman 2009/11/9 Kristian Rink : > Folks; > > maybe a pretty basic question (sorry if so), but at least browsing the > mime4j documentation didn't really get me very far here: I want to integrate > mime4j with an environment that so far uses javax.mail to pull messages off > IMAP and have them processed (i.e. extract textual content, store > attachments, ...). For what I have seen so far, the mime4j parsers do > _rather_ well here, but most examples just rely upon operating on top of > message files stored somewhere on a hard drive whereas I want to use > messages accessible via IMAP rather than that. > > Is there any way of doing so? Am I so far missing the point how to get it > done, or will copying the message to some temporary file be the only way to > go here? > > TIA and all the best, > Kristian >