Due to a seamless migration of a few thousand fat client users from a very different mail system to kolab
we need imap authentication with shared secret supporting at least CRAM-MD5 mech.
We thought about some other ways to go to do the fat client user/settings migration but non of them was
as painless as getting kolab-saslauthd supporting shared secret auth with at least mech CRAM-MD5.
We know that this requires plaintext passwords stored on the auth backend, because that's how it works now.
For some other reason/tool authentications this will be required in future anyway so it's not making a big