On Sunday Oct 30 2016, Joerg wrote:
> Ah, thank you. I didn't have that in my previous version which worked.
>
> Unfortunately, it turns out that was only a first step towards a working
> setup. It now complains that the mu version should be 0.9.16, but is
> 0.9.15. It is, but I don't know why. I compiled from the mu-0.9.16 download
> and did a "make clean" before "make".
If you don't set the mu binary path, mu4e picks it up using PATH
(`executable-find`).
> I appreciate your help - it would be a disaster if after years of mu4e I
> would have to revert to one of the common mail programmes.
Well, you are lucky, the error messages tell you exactly what's wrong :)
Seems you're trying to use an older mu binary with a newer mu4e. You
probably haven an older version of mu lying around; and the fix is to
set mu4e-mu-binary to the new mu, not the old one.