Possible bug in SASL profile listener code

At various places, the SASL tuning profile listener code sends a blob
containing <abort>s to the initiator if anything goes wrong. I don't
think this is correct. RFC 3080 says:
 
exchange sequence: 

"Challenges" and "responses" are carried in exchanges of the "blob"
element. The "status" attribute of the "blob" element is used both by a
server indicating a successful completion of the exchange, and a client
aborting the exchange, The server indicates failure of the exchange by
sending an "error" element.