>I just verified and the PLAIN SO file is in the SASL library. "Hm". It's not being offered as a valid client mechanism, so I am a bit puzzled there. Exactly what OS are you on, and what version of Cyrus-SASL are you using?
Digging into things, the original error message was: post: problem initializing server; [BHST] SASL client start failed: SASL(-4): no mechanism available: Unable to find a callback: 2 I had to dig into this more: "2" is the callback identifier, which seems to be: #define SASL_CB_LOG 2 I don't create a logging callback in the nmh client side code, but traditionally you didn't need to create one. It looks like ... if you compile with syslog support then that's used as the default logging callback. I am guessing the library is trying to log some error but you're not seeing it because it's not compiled with syslog support and as a result you're getting this unhelpful error (although I suspect ultimately it would fail without PLAIN). >Is the SMTP server 'smtp.fastmail.com'? I specified this in the .netrc >file and -server switch for send. If this is correct, then I can't >figure out what the problem might be. Well, I use smtp.pobox.com because that's what I've used forever, but I tested it with smtp.fastmail.com and it worked fine. So, ways forward. I see two options: - Try compiling a Cyrus-SASL library with syslog support. You should end up with some kind of error message in the logs and that will probably be helpful to determine the real problem. - I should probably add a logging callback since having client error messages end up in syslog isn't super helpful. I could do that and send you patches for the latest nmh. Let me know which way you want to go. --Ken
