I'm using perdition quite successfully to
present a unified interface for users whose mail
resides on various back-end servers, using LDAP
routing.
But I foresee trouble ahead. A gmail backend, for example,
requires an imaps connection, regardless of how
the user reached the perdition proxy. gmail also
requires the full email address (foobar(a)gmail.com),
but other services just want the user id -- i.e.
the part before the '@'. There will probably be
cases where the user id on the backend is quite different
from the user id the user knows about and logs in with.
In short -- maybe it's a good idea to start thinking
about having more stuff be LDAP-driven than the
current three elements. Has there ever been a discussion
of some scriptable or extensible facility for
driving more back-end parameters from LDAP -- maybe
including even parameters that are normally driven
by command-line or config file parameters, on a per-
connection basis?
If this sounds like a good idea at all I'd be happy
to help with the work.
Best,
Michael J Smith
mjs(a)smithbowen.net
Show replies by date