testing pipelining

Hi List,

Is there a command line trick to test pipelining?

We found some very old mail servers (non postfix btw) which don't seem
to properly support pipelining, although they EHLO greet with the
PIPELINING extention....

I haven't been able to find a way to enforce actual pipelining via
simple telnet commands...

If there are better mailinglists for these kind of questions then let me
know as well!


Marco van Kammen
Springer Science+Business Media
System Manager & Postmaster

van Godewijckstraat 30 | 3311 GX
Office Number: 05E21
Dordrecht | The Netherlands





<a href="" title=""></a> <>
<a href="" title=""></a> <>


Re: testing pipelining

By Ulrich Zehl at 09/22/2010 - 09:37

On Wed, Sep 22, 2010 at 02:17:40PM +0200, Kammen van, Marco, Springer SBM NL wrote:
swaks (<a href="" title=""></a>) can do pipelining.

swaks --pipeline -f <a href="mailto: ... at topfen dot net"> ... at topfen dot net</a> -t <a href="mailto: ... at topfen dot net"> ... at topfen dot net</a>

It's a perl program, so I do not know if you consider it "a command line

Re: testing pipelining

By Wietse Venema at 09/22/2010 - 08:35

Kammen van, Marco, Springer SBM NL:
No, but you could use Postfix instead.

Sometimes the problem is not with the SMTP server itself, but with
a %#^#&% firewall that mis-implements the protocol. With pipelining,
multiple commands are bundled together and the result may fill more
than one TCP packet. Some CISCO implementations can't handle that.

<a href="" title=""></a>