Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 70710 invoked from network); 30 Jun 2006 15:38:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jun 2006 15:38:53 -0000 Received: (qmail 16269 invoked by uid 500); 30 Jun 2006 15:38:51 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 16006 invoked by uid 500); 30 Jun 2006 15:38:50 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 15995 invoked by uid 99); 30 Jun 2006 15:38:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jun 2006 08:38:50 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of rickmcg@gmail.com designates 64.233.184.228 as permitted sender) Received: from [64.233.184.228] (HELO wr-out-0506.google.com) (64.233.184.228) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jun 2006 08:38:48 -0700 Received: by wr-out-0506.google.com with SMTP id 70so247032wra for ; Fri, 30 Jun 2006 08:38:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=nVkvn3SHcddYRGd+6wIpBlohJtoBFUOmzAXZJAxCc/li6Q5yxCJmOKL+zvFwTY43Bfgx8xuVtXHzhBzFWzUFKhM45nP+95+p1qxwKrhDVc1HE7zxo4KAHYq/nlB8X2+J++zaSmKvcSjCE+Mh4qMHfEZ9xG322x4XkzliTo1hF0U= Received: by 10.54.152.16 with SMTP id z16mr717310wrd; Fri, 30 Jun 2006 08:38:28 -0700 (PDT) Received: from ?192.168.1.102? ( [68.191.49.248]) by mx.gmail.com with ESMTP id 11sm533396wrl.2006.06.30.08.38.27; Fri, 30 Jun 2006 08:38:27 -0700 (PDT) Message-ID: <44A5457A.8060805@gmail.com> Date: Fri, 30 Jun 2006 11:38:34 -0400 From: Rick McGuire Reply-To: rickmcg@gmail.com User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: dev@geronimo.apache.org CC: James Developers List Subject: Re: geronimo javamail and James (Was: [RTC] Removal of the javamail-transport code.) References: <449AD876.7060707@gmail.com> <449E21D7.1080801@toolazydogs.com> <15624540.576661151667445020.JavaMail.root@81-174-50-40.vps.virtuo.it> <44A51B78.6040709@toolazydogs.com> <18166318.580081151672388619.JavaMail.root@81-174-50-40.vps.virtuo.it> <44A53498.6090400@toolazydogs.com> <4229170.586511151679363661.JavaMail.root@81-174-50-40.vps.virtuo.it> In-Reply-To: <4229170.586511151679363661.JavaMail.root@81-174-50-40.vps.virtuo.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Stefano Bagnara wrote: > Alan D. Cabrera wrote: >> Stefano Bagnara wrote: >>> Alan D. Cabrera wrote: >>>> Why would we need both? >>> >>> We don't need both at the same time. >>> But: >>> 1) I guess that geronimo-javamail is not as stable and feature >>> complete as the sun-javamail. >>> 2) We use javamail 1.4 apis (geronimo-javamail seems to be 1.3 >>> compliant) >>> >>> So what I think we could do is adding the handling of geronimo >>> specific stuff while keeping the default to sun. >>> This way one could test it and find out the differences. >> >> 1) Maybe not as stable. What features do you think are missing? > > I've not checked geronimo smtp transport, Is there a feature list for > current geronimo stmp implementation compared to sun smtp transport? All answers below are for the latest version. The one that shipped in Geronimo 1.0 did not support these. > > Does it support the quitwait? yes > bindaddress/port for sockets? yes > does it support appending further strings at the end of the MAIL > command and the RCPT command (ORCPT, NOTIFY). yes > How does it compare in converting messages from 7bit to 8bit when > sending to servers that supports 8bitmime, and from 8bit to 7bit when > sending to servers that do not support 8bitmime? I haven't implemented 8bitmime yet, as I've not really found a good description for what needs to be done to support that. I don't think it's a big issue, I just need to understand what it means to support it. > > Stefano > > PS: About the 7bit<->8bit mime conversion I wrote some mail to the > javamail interest and seems that they are buggy in the sun-javamail > transport. > >