Matt Sergeant wrote:
But there's a patch in this thread to fix that, right?
Not a complete one, no. I'm at $WORK now, and I can't take a look at it
Changing %hooks to an "our" makes that work though.
Yes, but my mind automatically recoils at using package globals like that. YMMV ;-)
I still don't quite understand why AUTH wasn't implemented as an unrecognised command hook... I'm sure it would have been possible, no?
It was because AUTH might have two roundtrips with the client (or not) depending on the AUTH method used. The first AUTH command is clearly defined (since it starts with "AUTH" ;-), but the client response to the server challenge has no obvious prefix. If the QPSMTPD core had a more generic event loop, it would be trivial, but because every line has to go through the main loop, it was a pain to do it any other way.
John
