It works correctly now. Thanks!

This affects the sieve backend only, right? Can you try what I just committed?

Yes, I did. This recent fix, strips the realm if hordeauth is set to 
"true" and keeps the realm if hordeauth is set to "full". And it does 
it correctly for the backend. But there are multidomain/server setups 
where people have to use realms for horde applications, because there 
could exist the same usernames on different server (e.g. imapservers 
for imp). Therefore prefs and so on should be distinguishable. On the 
other hand, the imap/sieve backend does not know anything about 
realms. This seems to be the problem. In older versions of ingo this 
situation was handled correctly.

There was a change to Ingo::getUser() recently that seems like it 
should address this. Have you tested it?

If  "'hordeauth' => true" is set (because the sieve backend server 
doesn't know anything about the realm), users get logged in to the 
sieve server correctly but the ingo specific prefs get saved without 
the full hordeauth (user@realm) in the prefs database (the same is for 
the ingo sql storage). This means, that the sieve scripts get 
transferred correctly to the sieve backend but will newer again show 
up on the UI.



A workarround for this is to use Auth::getAuth() instead of 
Ingo::getUser() in horde/ingo/lib/Storage/prefs.php and/or 
horde/ingo/lib/Storage/prefs.php