According to the NServiceBus FAQ, we shouldn't handle exceptions. Instead the NServiceBus pipeline will take the error-ing message off the bus, and move it to an error queue. Trouble is, you can't tell by looking at the messages on the error queue what actually caused the error. We work around that by logging any exceptions, but that just means we now have to check the time stamps of the error messages, and match them with the error log.
Is it a good idea to route error-ed messages to a specific queue? If so, how can you do this in NServiceBus?
I was thinking that I could create specific error queues so that support staff could handle errors easier.