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. > 2) Is available through some OpenSMTPD add-on package > Nope, due to the design of the daemon, it can't be implemented as an add-on, it would have to be part of the daemon itself. > 3) Is on the roadmap for OpenSMTPD and > I'll just have to wait... unless I write it myself ;-) > It's not on any roadmap. Unless you write it yourself and send us a pull request, or find a developer willing to be sponsored to write that feature, you're in for a long wait ;-) > By the way - found OpenSMTPD setup quick and easy > > NICE WORK ;-) > Thanks :-) -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
