Fixed in IMP 4.3.7.

Changes have been made in CVS for this ticket:

Bug: 8872
Submitted by: robin.west@dal.ca
Fix authenticate API call.
http://cvs.horde.org/diff.php/imp/docs/CHANGES?rt=horde&r1=1.699.2.420&r2=1.699.2.421&ty=u
http://cvs.horde.org/diff.php/imp/lib/api.php?rt=horde&r1=1.94.10.21&r2=1.94.10.22&ty=u

Just an update ... I noticed that when the imp_authenticate api calls 
createSession() it makes reference to $result[$server_key]. I'm not 
sure where this $result array is supposed to come from, but if I 
change it to $servers[$server_key], then it picks up the correct IMAP 
server info from servers.php and everything works fine.

Also verified that this code is still the same in your latest version (4.3.6).

-Robin

Hi - using Horde 3.3.4/IMP4.3.4/Ingo1.2.1. I have IMP configured with 
realm='dal.ca', so normally when I log in, Auth::getAuth() would 
return 'rwest@dal.ca' and all my prefs are saved in the backend with 
pref_uid='rwest@dal.ca'.

I have a custom script which connects to IMP using the 
imp_authenticate() api function ... but when I connect this way, there 
is no realm in my username (i.e. Auth::getAuth() returns just 
'rwest'). This is a problem if my custom script wants to retrieve 
prefs from the backend, which are all stored with the 
pref_uid='rwest@dal.ca'.

Is this expected behaviour for using the imp_authenticate() api? Or is 
it a bug? Is there anything I can do so that my custom script ends up 
logging in as 'rwest@dal.ca' instead of just 'rwest'?