This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Remedy AR System Server
1. STEPS TO REPRODUCE:
If you are using any invalid email address as '@xxx.com' stated it appears to pass through any validation check from email engine and is passed onto the SMTP server. And it is the SMTP server that reports back the error about the badly formatted email address.
following output from test using '@yahoo.com' as an email address.
In 8.x environment :emails_sh.log below is error sample:
Aug 14, 2017 11:21:45 PM com.sun.mail.smtp.SMTPTransport sendMessage
SEVERE: 250 ok: Message 5852517 accepted
com.sun.mail.smtp.SMTPSendFailedException: 250 ok: Message 5852517 accepted;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 501 #5.1.1 bad address @yahoo.com
Caused by: com.sun.mail.smtp.SMTPAddressFailedException: 501 #5.1.1 bad address @yahoo.com
... 4 more
In 9.1.03 logs It says:
<EML> <TID: 29> <SEVERE > <SenderModule> /* Fri Sep 01 2017 20:45:10.722 */ 250 2.0.0 v81Jkvww015761 Message accepted for delivery
[Invalid email address --> @yahoo.com , @equinix.com ]
Here you can see that the message was accepted for delivery. Which means that it was indeed sent to the SMTP server. The last email listed there shows that @yahoo.com and @equinix.com were added to the address fields. But by email standards they are incomplete and should have been identified as invalid emails without sending the email out to the SMTP server
2 ACTUAL RESULTS:
In this use case of just providing a domain name causes the email engine to send it to SMTP without erring out on the bad email address
3. EXPECTED RESULTS:
It should throw bad email address error at email engine level only.
This is raise as defect : SW00540597
Hotfix provided for this & available on :