On 18/06/15 12:22, James Triplett wrote:
On (16/06/15 18:15), [email protected] wrote:
Date: Tue, 16 Jun 2015 18:15:58 +0100
From: "[email protected]" <[email protected]>
To: [email protected]
Subject: Extended SMTP: Pipelining
Setup: OpenBSD5.7 with default OpenSMTPD
Changes: Firewall, One user, Nothing radical
Working fine:
SMTP dispatch
from second OpenBSD5.7 with OpenSMTPD (VM#2)
to receiving OpenBSD5.7 with OpenSMTPD (VM#1)
Problem:
Alien client (VxWorks-based device) won't connect
but clearly speaks to OpenSMTPD
Server Maillog message:
500-Pipelining not supported (... from OpenSMTPD...)
I had a similar error crop up when I was first installing OpenSMTPD.
So, I had to figure out what pipelining is, and why OpenSMTPD
thought it was being called for.
It turned out not be about pipelining, but a configuration issue that
eventually disappeared.
I wish I could remember the exact fix...
It may be that the 'pipelining' message is leading you in the wrong direction.
Good Luck.
James
I've read that OpenSMTPD doesn't support pipelining.
Is this something that:
1) Will never be implemented in OpenSMTPD:
OpenSMTPD frowns on pipelining and doesn't like
clients that don't follow the RFCs strictly
i.e. They ignore "NO. I don't do pipe-lining"
James,
Thanks you for your comments.
Error message 500 is "Command not supported"
which leads me to think that following the initial handshake
which completes successfully the VxWorks sender simply
goes on its' merry way - assuming it can just send in its
usual format (ignoring the responses).
The VxWorks sender expects to be working with Exchange
(Which I believe does support pipelining).
Not to worry - once (or IF) I've got it working with sendmail
I'll try it again with OpenSMTPD.
I was just wondering if in a release or two I might be
able to expect this device to work with OpenSMTPD
because pipellning was supported (IF indeed that is the
problem - since you are suggesting there might be
some other reason...)
I'll keep at it ;-)
Mike
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
