Why does LDAP emailSuffix override emailAttr?

[jtfrey]

In the LDAP connector, if emailSuffix is provided in the configuration then all email addresses attached to the returned connector.Identity are manufactured from the idAttr@emailSuffix, regardless of the existence (or not) of a value for the emailAttr on the entity directory. The logical role of emailSuffix seems like it would be for an email address to be synthesized when an explicit emailAttr value is not present on an entity directory -- why was the extant behavior chosen?

Would the developers be open to adding a configuration option that affects the ordering of options, e.g. emailSrcOrder with values of suffix-attr or attr-suffix, for example? Since an email address is mandatory on the connector.Identity that is returned, this flexibility seems valuable and would be straightforward to add.