On 20/06/15 19:09, Gilles Chehade wrote:
On Tue, Jun 16, 2015 at 06:15:58PM +0100, [email protected] wrote:
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'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"
That's a fair point of view ;-)
(Sendmail for this VxWorks device, then... and, at
least, for the time being)
I would not say "never" but it's unlikely it gets implemented by us.
We have no interest (for the time being) in that feature.
Gilles,
Thank you for your straightforward answers.
The fault lies with the device not properly observing
the RFCs and making assumptions regarding server
functionality.
So while I'll have to employ an alternative server
specifically for that device; all of the other
OpenBSD systems I am running will continue to
run OpenSTMP.
I really like the way you employ a pf-form vocabulary.
Excellent consistency with that other great OpenBSD
vanguard.
It's as if OpenSTMP were serendipitously following the
UNIX KISS philosophy and some OpenBSD setup
template :-)
I'm not saying the sendmail binary and it's s*.cfs
are not KISS but I would conjecture the binary has
marginally more complexity and the config files
somewhat steeper learning curves.
Mike (The last of the noise for a longish while)
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
