Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Received-SPF: pass (athena.apache.org: domain of markus.wiederkehr@gmail.com
 designates 209.85.218.219 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=cacpgwLhjY1zLQsvasaM6ryXKJ/MgWevna6JCowsnIMxHe3AV8l2mpAQuVdQRhRVfy
         9L4YtOgFWF9A0lNdtnLg1foUQ8wvOO8ZdFFlJFJIi/gZ1eFujgqBE0rG40kruP1rNJtZ
         iESduwm18sivYKfvy85p/1ez3FqwUzG9aC63I=
MIME-Version: 1.0
In-Reply-To: <f470f68e0906110815q791b7859pec29b028b7725ef2@mail.gmail.com>
References: <a92573960906110730x41fc9a2apa1db9826fb2c5e41@mail.gmail.com>
	 <f470f68e0906110815q791b7859pec29b028b7725ef2@mail.gmail.com>
Date: Thu, 11 Jun 2009 23:08:07 +0200
Message-ID: <a92573960906111408h4b8162d8oaa178975bf8d5157@mail.gmail.com>
Subject: Re: SMTP Transport?
From: Markus Wiederkehr <markus.wiederkehr@gmail.com>
To: mime4j-dev@james.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On Thu, Jun 11, 2009 at 5:15 PM, Robert Burrell
Donkin<robertburrelldonkin@gmail.com> wrote:
> On Thu, Jun 11, 2009 at 3:30 PM, Markus
> Wiederkehr<markus.wiederkehr@gmail.com> wrote:
>> 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?
>
> so long as it's in a separate module, i'd say yes for now
>
> commons net (http://commons.apache.org/net/) already supports SMTP.
> it's probably worthwhile having a bit of a think where the new mime4j
> code would fit into the ecosystem...

I ran svn2cl in NET's o.a.commons.net.smtp package and there was no
real development in the last 6 years except for a fix for NET-178 (and
I did not look farther back).

There does not seem to be ESMTP support, not even for EHLO.

SMTPClient.sendMessageData() returns a Writer instead of an OutputStream.

Does not look very promising to me..

> <snip>
>
>> 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..
>
> yes but a little work would be required
>
> BTW the first MPT release needs one more vote if you have a few spare
> cycles to review it

What would you want me to do? Compile and review the source? Is there
some kind of checklist I should follow?

Markus