The fix to make autosecure compatible with always sign ( 7486c0bf18a59e531144901b97e4c7c352acf5c2 ) had a side effect to expose a bug caused by inconsistent use of "opt.autosecure" vs. "opt.autoresolve".

This leads to the problem that "Resolve recipient keys automatically" and "Sign new messages by default" causes the autosecure code to trigger even if "automatically secure messages" is off.