On 31-Mar-08, at 11:04 AM, John Peacock wrote:
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.
Hmm. Maybe we should have a hook for parse_command or something? Matt.
