Am 2012-09-19 22:27, schrieb Wietse Venema:
Michael Storz:
The consistency check requires that a user object is first
(correctly)
defined in OpenLDAP. Only then the second check looks for the
correct
definition in Active Directory. If it is not then we defer the email
(we
...
If a new user
Michael Storz:
seems I was
not able to show the underlying problem, let me rephrase my problem:
How can I configure arbitrarily complex if-then-else constructs
for every possible table type?
You will have to outsource that logic with tcp_table lookups.
Considering that
On Thu, Sep 20, 2012 at 10:48:15AM +0200, Michael Storz wrote:
This is an account provisioning problem, not an MTA routing problem.
The best solution is to not send email to the user until the
provisioning is complete.
Unfortunately we can't tackle the account provisioning problem
Am 2012-09-19 21:41, schrieb Viktor Dukhovni:
On Wed, Sep 19, 2012 at 07:13:49PM +0200, Michael Storz wrote:
The consistency check requires that a user object is first
(correctly) defined in OpenLDAP. Only then the second check looks
for the correct definition in Active Directory. If it is not
Am 2012-09-14 17:24, schrieb Wietse Venema:
Michael Storz:
If a new parameter no_result_format would exist, we could define the
ldap procedure with
result_format = DUNNO
no_result_format = 450 User not yet available in Exchange
which is very straightforward and understandable.
Except that
Coming back to the original problem, if you don't want to reject
mail with user unknown when a user might still be in the process
of being created, how are you going to deal with really unknown
addresses, like a sender who mistyped something?
Wietse
Am 2012-09-19 18:50, schrieb Wietse Venema:
Coming back to the original problem, if you don't want to reject
mail with user unknown when a user might still be in the process
of being created, how are you going to deal with really unknown
addresses, like a sender who mistyped something?
On Wed, Sep 19, 2012 at 07:13:49PM +0200, Michael Storz wrote:
Am 2012-09-19 18:50, schrieb Wietse Venema:
Coming back to the original problem, if you don't want to reject
mail with user unknown when a user might still be in the process
of being created, how are you going to deal with really
Michael Storz:
The consistency check requires that a user object is first (correctly)
defined in OpenLDAP. Only then the second check looks for the correct
definition in Active Directory. If it is not then we defer the email (we
...
If a new user is created the user object appears instantly
Michael Storz:
If a new parameter no_result_format would exist, we could define the
ldap procedure with
result_format = DUNNO
no_result_format = 450 User not yet available in Exchange
which is very straightforward and understandable.
Except that this returns false rejects with for
10 matches
Mail list logo
