I thought there was a message about this in the archive, but I
can't seem to find it...
qpsmtpd responds to EHLO with PIPELINING as one of its
capabilities. Since I am specifically running tests at every stage of the
SMTP conversation, and there is a strong likelihood that a connection will
fail before DATA, it doesn't make sense to me to advertise this
capability.
Perhaps logically, it makes no difference - qpsmtpd will respond
to the stream with an error at some point, but part of my goal is to
reduce the bandwidth used. If I am rejecting a spammer, I don't want to
still accept his entire spew because I've said PIPELINING is okay. I end
up forcing a lot of disconnects, just to be sure.
Am I fussing over nothing?
