You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2006/10/15 02:56:49 UTC
Testing SMTP pipelining
Bernd (or anyone else feeling like working on this),
As I'm working on the revised I/O handling, I've been paying attention to
issues related to pipelining. Would you please make sure that we have some
tests to validate proper behavior for RFC 2920?
Also, we currently show RFC 2197 as the RFC for pipelining, but that has
been superceded by RFC 2920, so we should update the web site and ensure our
compliance with the latest revision.
Likewise, we list RFC 1830, which has been superceded by RFC 3030, although
we do not declare (or implement) it. Does anyone know if RFC 3030 is widely
implemented?
ref: http://www.ietf.org/rfc/rfc3030.txt
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Testing SMTP pipelining
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Bernd (or anyone else feeling like working on this),
>
> As I'm working on the revised I/O handling, I've been paying attention to
> issues related to pipelining. Would you please make sure that we have some
> tests to validate proper behavior for RFC 2920?
>
> Also, we currently show RFC 2197 as the RFC for pipelining, but that has
> been superceded by RFC 2920, so we should update the web site and ensure our
> compliance with the latest revision.
From a fast review of the RFC I can't see protocol differences between
this and the previous specification.
As a note the RFC does not require that the buffers are handled
correctly also after the DATA command, but our current implementation is
able to recieve the full conversation in a single buffer: this is really
useful while testing. IIRC the RFC require the client to flush and read
the replies after the DATA.
> Likewise, we list RFC 1830, which has been superceded by RFC 3030, although
> we do not declare (or implement) it. Does anyone know if RFC 3030 is widely
> implemented?
>
> ref: http://www.ietf.org/rfc/rfc3030.txt
http://fortytwo.ch/smtp
From this link it seems that only Microsoft support this rfc.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Testing SMTP pipelining
Posted by Guillermo Grandes <gu...@gmail.com>.
Helo Noel,
This appears in some of the machines that we have.
** SMTP of IIS/W2003
220 xxxxxxXX.xx Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready
at Sun, 15 Oct 2006 12:36:17 +0200
EHLO pepe
250-xxxxxxXX.xx Hello [127.0.0.1]
250-TURN
250-SIZE 20480000
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK
QUIT
221 2.0.0 xxxxxxXX.xx Service closing transmission channel
Connection closed by foreign host.
** SMTP of IIS/W2000.
220 xxxxxxXX.xx Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready
at Sun, 15 Oct 2006 13:01:07 +0200
EHLO pepe
250-xxxxxxXX.xx Hello [127.0.0.1]
250-TURN
250-ATRN
250-SIZE 20480000
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK
QUIT
221 2.0.0 xxxxxxXX.xx Service closing transmission channel
Connection closed by foreign host.
** postfix 2.2.5....
220 xxxX.xxxxx ESMTP Postfix
EHLO pepe
250-xxxxX.xxxxx
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250 8BITMIME
QUIT
221 Bye
Connection closed by foreign host.
** qmail 1.03
220 xx.x.xxx.xxx ESMTP
EHLO pepe
250-xx.x.xxx.xxx
250-PIPELINING
250 8BITMIME
QUIT
221 xx.x.xxx.xxx
Connection closed by foreign host.
** sendmail 8.11.6
220 xxxxxx.xxxxxxXX.xx ESMTP Sendmail 8.11.6/8.11.6; Sun, 15 Oct 2006
12:50:02 +0200
EHLO pepe
250-xxxxxx.xxxxxxXX.xx Hello localhost [127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-SIZE
250-DSN
250-ONEX
250-ETRN
250-XUSR
250 HELP
QUIT
221 2.0.0 xxxxxx.xxxxxxXX.xx closing connection
Connection closed by foreign host.
** sendmail 8.12.11
220 xxxxxxxxx; ESMTP Sun, 15 Oct 2006 12:51:50 +0200; Hello 127.0.0.1:XXXXX
EHLO pepe
250-xxxxxxxxx.xxxxxx.xxxxxxxxx.xxx Hello localhost [127.0.0.1], pleased to
meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-DELIVERBY
250 HELP
QUIT
221 2.0.0 xxxxxxxxx.xxxxxx.xxxxxxxxx.xxx closing connection
Connection closed by foreign host.
bye.
Guillermo
----- Original Message -----
From: "Noel J. Bergman" <no...@devtech.com>
To: "James-Dev Mailing List" <se...@james.apache.org>
Sent: Sunday, October 15, 2006 2:56 AM
Subject: Testing SMTP pipelining
> Bernd (or anyone else feeling like working on this),
>
> As I'm working on the revised I/O handling, I've been paying attention to
> issues related to pipelining. Would you please make sure that we have
> some
> tests to validate proper behavior for RFC 2920?
>
> Also, we currently show RFC 2197 as the RFC for pipelining, but that has
> been superceded by RFC 2920, so we should update the web site and ensure
> our
> compliance with the latest revision.
>
> Likewise, we list RFC 1830, which has been superceded by RFC 3030,
> although
> we do not declare (or implement) it. Does anyone know if RFC 3030 is
> widely
> implemented?
>
> ref: http://www.ietf.org/rfc/rfc3030.txt
>
> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org