Outbound email not received on the cell phone

From the EPM menu, select Real-Time Monitoring > System Monitor.

Check if the email processor is in Running state.

The System Monitor might show any of the following statuses for the email processor:

Need Configuration: Email processor is not configured and enabled
Need Connection: Email connection is not configured and enabled
Running: The email processor is connected to all email connections
Degraded: Some of the email connections are experiencing a connection issue. For example: Invalid credential, Firewall issue, bad IP address, and so on
Error: All the email connections are experiencing a connection issue

Note:

If the System Monitor does not show an email processor, then check if an email processor is configured and enabled
When multiple email processors are defined, ensure that the connection under test is assigned to the expected processor. You can view a list of the email processors and associated SMPP connections in the primary EPM web page at Home >Multi-Media Configuration > Email. Ensure to check the log file, which is mentioned in the following step, on the correct processor.

If the email processor is in Running state, proceed to the next step. Else, check the error log in EPM Log Viewer, from: EPM Home > System Maintenance > Log Viewer.

Check if the email processor received a request to submit a message to the provider.

To view the email settings, select Home > Multi-Media Configuration > Email > Email Settings
Ensure that all email trace levels are set to finer or finest.
Search for the word sendEmail in /opt/Avaya/ExperiencePortal/VPMS/logs/avaya.email.log. For example:

@2013-10-02 10:14:17,838||FINER|avaya.emailbrowser.EmailBrowser|VoicePortal|pool-2-thread-20| EmailBrowser:sendEmail ret=sessionid=123;ucid=10000000021380734057;requestid=PrimaryEPM-1380734057787-2|####
If the message was sent using the Application Interface web service, search for the word EmailService.sendEmail in avaya.email.log. For example:

@2013-10-02 10:14:17,787||FINER|email.service.EmailService|VoicePortal|pool-2-thread-20|EmailService.sendEmail [requestId: PrimaryEPM-1380734057787-2; app: 0:ColorEmail; from: epm@domain.com; to: user1@domain.com; ; ucid: 10000000021380734057]|####

If a sendEmail request was not logged, proceed to the next step. If a sendEmail request was logged, your email server might generate an undeliverable notification, DSN, within a minute or two.

Use an email client to examine the inbox of the sending mailbox and read the contents of the DSN email. Alternatively, run the Contact Detail report on the EPM.
Select the Message Status column and select a Media Type filter of Email DSN.
The Message Status column might contain any one of the following codes:
- 0: The message was successfully delivered to the specified recipient address. It does not indicate if the message was read. This is a terminal state and does not provide further DSN for this recipient.
- 1: The message could not be delivered to the recipient. The reporting MTA has abandoned any attempts to deliver the message to this recipient. No further notifications.
- 2: The message has been relayed or sent through a gateway into an environment that does not accept responsibility for generating DSNs for successful delivery.
- 3: The reporting MTA is unable to deliver or relay the message. However, the MTA will continue to attempt to deliver the message. Additional notification messages may be issued as the message is further delayed or successfully delivered, or if delivery attempts are later abandoned.
- 4: Unknown error. The details may be in the DSN message.

Check if the Application Interface Web service received a request to submit an email. You can view the activity and error log from /opt/Avaya/ExperiencePortal/VPMS/logs/avaya.appintfservice.log.

Ensure that the sending application is correctly configured to call the Web service.

For more information about Application Interface Web service, see Administering Avaya Experience Portal.

Outbound email not received on the cell phone

Proposed Solution

Procedure