New sasl init script looks for different options variable name

[Adam Crosby]

I recently upgraded from LTS to Gutsy, and my postfix/saslauthd connection stopped working.
After looking around, I discovered the new init script (not sure when it was changed?) for sasauthd users the $OPTIONS variable from /etc/default/saslauthd rather than $PARAMS , which is the variable name used in LTS. This wasn't a huge deal, once I figured it out, but either both variables should be checked, or a notice during upgrade flashed by (unless I missed it and it did, in which case I apologize!).

[Serge van Ginderachter (svg)]

AFAIK directly upgrading from LTS/Dapper to Gutsy is not supported. If this was the only issue you had, I'd think you got lucky :-)

[Adam Crosby (adam-uptill3)]

It wasn't a direct upgrade, it was a 3 hour process going from LTS->Edgy->Fiesty->Gutsy :)
And yes, it was the only issue I had (the box doesn't do anything but email and apache, so not much to break).
It's a testament to how well Ubuntu is handling things!

[Scott Kitterman (kitterman)]

This is probably related to it being a different package. Going Feisty -> Gutsy you changed from libsasl2 to libsasl2-2.

[Adam Crosby (adam-uptill3)]

Did it prompt to resolve / change the config file, and I just missed it? If not, I would still say that's a bug - I went from working to non-working by upgrading.
If it did prompt, then no problem, I just need to pay better attention!

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, you are not using the most recent version of Ubuntu. Please upgrade to the most recent version and when you are still having this issue, feel free to file a new bug-report. Thanks in advance.

[Adam Crosby (adam-uptill3)]

I reported this nearly a year ago, at which time I was using the most recent version.