Resolve E-mail listener conflict Service Provider and core Maximo

As discussed in case TS003772549 there is a conflict between the Service Provider add on and core Maximo/ICD functionality which occurs in the e-mail listener process.

This has also been registered under APAR no. IJ28630.

Switching on the standard Maximo property mxe.lsnr.validateperson allows you to enable the option that the E-mail listener will also allow/process e-mails of unknown persons. The Service Provider logic will however block an e-mail of a person that does not have access to the PLUSPCUSTOMER record of the SR to which you send an e-mail.

In my case (TS003772549 is a bug confirmed that e-mails without DOCLINKS do not work the same as e-mails without DOCLINKS. The e-mail without DOCLINKS are not blocked by the mail listener SP restrictions, whereas the mails with a DOCLINK are blocked. IBM wants to fix this.

I agree that this can be fixed, however before fixing this I also would like to have the feature that the mxe.lsnr.validateperson property can also be used together with the Service Provider module. It is a bit strange that you allow an e-mail of a user which is not known, but block an e-mail of a user that does not have access to a certain customer.

Therefore I suggest to add an additional property which can be used to switch of the customer authorization validtion in the e-mail listener process.

Proposed solution:

Property: mxe.lsnr.validatecusteromerauth
Default Value: True
Description: Flag to indicate if customer authorization needs to be taken into account. If person is not authorized for customer

the mail will be blocked. Otherwise mail can be processed similar to mxe.lsnr.validateperson (as MAXADMIN person)

Please fix this as soon as possible in an interim fix, so we do not have to await a new product version release. Thanks.