I would suggest using smtptest (part of cyrus) to confirm that your
server correctly authenticates using CRAM-MD5. If it works, then there's
a problem with thunderbird. If not, then you can either stop advertising
CRAM or look into fixing the problem on the server side.
that looks a lot like what this will do:
openssl s_client -starttls smtp ....
but the problem is i don't know how to supply the
AUTH CRAM-MD5 ....this part....
or i could use openssl to test it.
That's why I suggested smtptest - it implements several auth mechs,
including CRAM - a tool like this really should be supplied with postfix.
Also note, in my experience T-Bird caches and does not refresh the list
of available auth mechs without a restart. So if you change available
mechs on the server, t-bird will not notice and may continue to try and
authenticate using the now unsupported mech. I've seen this silly
ohhhhh... i think i didn't restart....
j.
behavior after making account server/port settings changes. This would
explain point #1 above.
--Blake
