Custom logic

Marc Patermann hans.moser at
Wed Jan 6 09:09:56 CET 2016


Am 19.12.2015 um 02:51 Uhr schrieb Steve Meier:
> The general logic needed is-
> 1) User has provided a "*username at*" address
> 2) Query our LDAP server by the *uid=username* and retrieve the
> *mailRoutingAddress *attribute.
> 3) *mailRoutingAddress *will follow one of *three rules*-
>    a) the "username@*servername*"
>    b) an external "forwarding address" that has been assigned by the
> user (for example a gmail, a yahoo, etc)
>    c) "username@**" (in other words, an
> institution-specific Office 365 instance)
so this is coming out of your directory directly, right?

> 4) Based on the rules above, we need to send the correct response,
> respectively
>    a) respond with settings for IMAP+SMTP email service (based off
> *username, servername*)
>    b) don't send a response (or possibly fall back to settings using a
> different LDAP attribute)
>    c respond with a *redirect to Microsoft O365*
If I understood correctly, you do not have the values for LDAP- and 
SMTP-server in your directory, so you cannot just sends this information 
to automx, right?
This is the problem?

> I have read through the documentation and it appears it may be possible
> to do this using automx, but I am not sure yet.  The documentation
> referenced this listserv, so I thought I would ask.
If the answer form LDAP is
if $addresse  ~= *
	then smptserver = microsoftserver
	then imapserver = microsoftserver

> Can anyone provide some insight into whether or not above would be
> possible, and if so, the general approach to go about it?  I can see it
> may require a combination of things (filters, custom scripts, LDAP, etc).
The easiest way would be to store the information directly in your LDAP 
and send it back to automx.


More information about the automx-users mailing list