Tickets :: Comment on [#6903] Silence warning on creation/update of a Kolab object

* Your Email Address
* Spam protection	Enter the letters below: .__.. ..__ . ..__ \| \|\| \|\| \\|__\|[__) \|__\\|/\\|\|__/\| \|\|
Comment	>>>> Auth::getAuth() is defined as "user id". I'm not sure if it always > >>>> must contain an @domain part. > >>> > >>> Are you using the Auth::kolab driver then? The kolab driver should > >>> rewrite the user id to the primary mail adress (see the setAuth() > >>> function in that driver). It looks like you are using UIDs in your > >>> system. At least in former times that was problematic for other Horde > >>> subsystems and that is why the kolab driver does the rewrite. I admit > >>> I don't remember exactly what the effects of using a UID were. But my > >>> gut feeling is that even with our new infrastructure it makes more > >>> sense to use the primary Kolab ID. > >> > >> I'm using IMP as Auth backend, which authenticates against an IMAP server. > > > > Ah, now I understand. > > > >> > >> Everything works fine, no complaints from the users so far. If some > >> part of the Kolab subsystem does work only with the Kolab Auth > >> backend, > >> then it needs fixing :-) > > > > Yes, true. > > > >> > >> I'll have an idea that satisfies both your needs: Why not check the > >> From: and To: address for the "@" character and append "@localhost" > >> only if it is not found? > > > > As this is just the mail address in the object I guess it could be > done that way. But it feels little bit too much like a hack to me. > Especially since we should have the possibility to retrieve the users > primary mail address from LDAP on any reasonable Kolab server. > > > > This is what I implemented in the new framework now. The Session > handler was fetching the Kolab user object anyhow, so retrieving and > storing the primary mail was just a small addon. I added your > solution in the session handler as a last backup in case querying the > LDAP server didn't help. > > > > The session handler caches the primary mail address so it should not > slow down the writing of Kolab messages to IMAP by first querying > LDAP. > > > >> > >> Thomas > >> > >
Attachment
Watch this ticket

Saved Queries