[AMBARI-13540] Emails Dispatched From Ambari Are Not RFC 2822 Compliant And May Be Rejected

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.2.0
• Component/s: ambari-server
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 23/Oct/15 12:47
• Updated: 27/Oct/15 21:11
• Resolved: 27/Oct/15 16:04

Description

When dispatching alert emails through some servers they are rejected with:

<[e-mail]>: host smtp.apache.org1.2.3.4 said: 
550-5.7.1 1.2.3.4 11 Our system has detected that this 
message is 550-5.7.1 not RFC 2822 compliant. To reduce the amount of spam 
sent to Gmail, 550-5.7.1 this message has been blocked. Please review 550 
5.7.1 RFC 2822 specifications for more information. f188si13510144qhe.108

This is because strict RFC 2822 compliance expects the From and To headers in the data of the message body as opposed to the MAIL FROM and RCPT TO directives.

Rejected

>telnet smtp.ambari.apache.org 25
EHLO
MAIL FROM: [e-mail]
RCPT TO: [e-mail]
DATA
Subject: Test message with From and To header
Test.
.
QUIT

Accepted

>telnet smtp.ambari.apache.org 25
EHLO
MAIL FROM: [e-mail]
RCPT TO: [e-mail]
DATA
From: [e-mail]
To: [e-mail]
Subject: Test message with From and To header
Test.
.
QUIT

We should be setting the headers on the MimeMessage as well.

Issue Links

• links to: Reviewboard