The screenshot didn't appear so the LDAP query added in LDAP configuration is :
Full Query String :
Query name : Address masquerade
Filter : (mail=%email%)
Identity attribute : mailRoutingAddress
Thanks for your help
could you attach a screenshot of the actual address masquerading configuration (not the LDAP query you set but "option definition screen") and possibly the Test results,too, for us to look at?
Also please state what you mean by "the masquerade did not work" - do you mean that it gives an error, it does not replace sender address with the correct replacement string at all, or replaces with incorrect value, etc.
You can find attached the configuration of email masquerade.
The result is not an error but a wrong answer. When I test the masquerading, I would like to have the good result (email@example.com in my exemple) but I always have the same result who are identical as the email I check.
Current masquerading test who didn't work :
Masquerading I would like to :
Thanks for your help.
I think the search pattern should be firstname.lastname@example.org and not the one you are now using. The logic I see in recipient adress aliasing is that the appliance looks for a certain pattern (which can be regex, too) in email headers (specified in the advanced section), and replaces with a direct string or a string as a result from an LDAP query.
So in my opinion you should replace the Search pattern value with the email address you want to replace and re-try.
Testing may result in success because you can specify directly what to look for and LDAP query runs, but in real situation the @(mail=%email%):mail string may not be found. (Is that supposed to be a regex? I checked regex reference but could not evaluate to email@example.com)