Return-Path: Delivered-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Received: (qmail 93634 invoked from network); 12 Jun 2009 06:09:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jun 2009 06:09:54 -0000 Received: (qmail 98891 invoked by uid 500); 12 Jun 2009 06:10:05 -0000 Delivered-To: apmail-james-mime4j-dev-archive@james.apache.org Received: (qmail 98859 invoked by uid 500); 12 Jun 2009 06:10:05 -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 Delivered-To: moderator for mime4j-dev@james.apache.org Received: (qmail 97406 invoked by uid 99); 12 Jun 2009 06:06:55 -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 209.85.221.196 as permitted sender) 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:content-transfer-encoding; bh=K2McPj1PV1inqvWNTgSvtGXlsnyzVo94HHs6AyjhU60=; b=MBpK3YV4VNiDDFO08okejrWy0XLbSyrxbDtrOox9fM5XWcr6V6ADmZjhM5sr3elCp3 9D7SbVePsXx3QG3wm1VGGDir33CnKI2mrcyR48YGkbTOZzFTkq2X98CMYwN/xGNPZtwi SmPYzihCLnEQ+4QrMuAz0+645pp7vXXUKqR7k= 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 :content-transfer-encoding; b=tlNePyGjKxf61938Zc3bZcVilUPexOI+B1J4NbkbDglOhU53+kL0szSpyVNKUM+bmZ u2NJW/AEDbwuvHGDsDvU6lpfCOY1fQ5yq7TZgunbgtqCJ+x8KSYENGOD2+m/Zq/jD7Zw 4Tuf1A5jBpIWOkYiKmpPzC+23LO7BLnY2jB3Y= MIME-Version: 1.0 Sender: norman.maurer@googlemail.com In-Reply-To: References: <4A312353.5010402@bago.org> Date: Fri, 12 Jun 2009 08:06:22 +0200 X-Google-Sender-Auth: 6fac1b116cc1a3d8 Message-ID: <75bda7a00906112306r3359fa42p7558c3159e4ac17e@mail.gmail.com> Subject: Re: SMTP Transport? From: Norman Maurer To: mime4j-dev@james.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Markus, what about trying to get in in commons net ? Bye, Norman 2009/6/11 Markus Wiederkehr : > On Thu, Jun 11, 2009 at 5:31 PM, Stefano Bagnara wrote: >> I'm not sure how MIME4J and SMTP transport are related. >> SMTP and MIME spec have not "interfaces" between them and for SMTP a >> mime message is simply a stream. > > You are right but AFAIK there is no simple way to send a Mime4j > message. You cannot use the Java Mail API because it expects a > MimeMessage. Commons Net does not look very attractive.. I don't know > of other alternatives. > >> An SMTP client should simply have a way to offer an outputstream to the >> mime library or ask for an inputstream from the mime library: do I miss >> any other integration point? > > No, except a higher level API could automatically extract sender and > recipient addresses from the message, for example. > > Do you know of a solid low-level API that offers an output stream? > That would be ideal. > > It should offer authentication and TLS, otherwise I have to write that > stuff myself. > > Markus > >> Stefano >> >> Markus Wiederkehr ha scritto: >>> I've written a class SmtpTransport that can be used to send a Mime4j >>> message to an SMTP server. >>> >>> Currently it is very simple. Meaning it is not yet capable of >>> authentication or TLS or other extensions. >>> >>> Would it be worth to include this code in Mime4j? >>> >>> Cheers, >>> Markus >>> >>> PS: Testing is a bit of a PITA with sockets and all.. Robert, could >>> MPT help with that? I haven't looked into it yet.. >