Error Sending Email Notifications: 554 Relay rejected for policy reasons. None of the recipients for notification is valid. Notification will not be sent. Check that the recipients email addresses are valid (Doc ID 1900616.1)

Last updated on AUGUST 22, 2015

Applies to:

Oracle Workflow - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

On Oracle Applications 12.1.3 version, Workflow Mailer,
after configuring the Workflow Notification Mailer, one can send test notifications to email addresses which the domain is the same as the SMTP server's successfully.
but it fails to send test notifications to email addresses of external domains. (eg.test@163.com)

When attempting to send an email to external domains: test@163.com,

Follow note 242941.1 8 a) and run command: rcpt to: test@163.com

the following error occurs.

554 Relay rejected for policy reasons

NOTE:

1. Ensure the recipient role has been assigned a valid email address (test@163.com) and correct notification preference,
the workflow mailer will set it to the Preference to 'Disabled' and notification sent with 'Failed' status.

2. The SMTP server, does not recognize test@163.com as a valid email address justified from workflow mailer logs:

SVC-GSM-WFMLRSVC-103007-10006 : oracle.apps.fnd.wf.mailer.SMTPMessageHandler.sendMessages(String)]:None of the recipients for notification {622506} is valid. Notification will not be sent. Check that the recipients email addresses are valid for [[test@163.COM{LIANG SKY }]]
WFMLRSVC-103007-10006 : oracle.apps.fnd.wf.mailer.SMTPMessageHandler.sendMessages(String)]:Updating notification {622506} status {FAILED} {WFMLRSND_FAILED_UNDELIVERABLE} {{test@163.COM}

3. Currently, the customer uses an Authentication Mechanism as :Login and when using the command: auth login, then rcpt to: test@163.com,
250 test@163.com Recipient gets an OK INSTEAD OF returning 554 Relay rejected for policy reasons.

However, it is not possible to remove the Authentication Mechanism for security considerations.


The issue can be reproduced at will with the following steps:
Send a test email to an external email address of different domain than the SMTP server.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms