Mail Security does not act RFC compliant as the system ignores the original notation of mail adresses. The System always convert the mail adresses to "smal-letter" notations ... as per RFC standard:
The local-part is case sensitive, so "jsmith@example.com" and "JSmith@example.com" may be delivered to different people. This practice is discouraged by RFC 5321. However, only the authoritative mail servers for a domain may make that decision. The only exception is for a local-part value of "postmaster" which is case insensitive, and should be forwarded to the server's administrator.
This is not correct. we have a current issue in which a customer configured his Mail server to take care of the notation of the mail adresses and so John.Smith@customer.com and john.smith@customer.com are different people ... or in this case Jonh.Smith@customer.com is a "known" User and will be accepted by the Server an a Mail adressed to john.smith@customer.com will be rejected with error 5x User unknown ...
Currently there seems to be no Up2Date resistant patch to solve this problem.So even if you don´t care about RFC this can realy kick you out of an Mail Security Project within no time.
This is the description it used within my Feaature Request... you can vote for it here:
Mail security is not RFC compliant ...
This thread was automatically locked due to age.