Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/187#issuecomment-176807151
@rpmiskin
Following the RFC 822 guideline (that the MimeMessage class is based on) it
says this about the "From" header:
4.4.1. FROM / RESENT-FROM
This field contains the identity of the person(s) who wished
this message to be sent. The message-creation process should
default this field to be a single, authenticated machine
address, indicating the AGENT (person, system or process)
entering the message. If this is not done, the "Sender" field
MUST be present. If the "From" field IS defaulted this way,
the "Sender" field is optional and is redundant with the
"From" field. In all cases, addresses in the "From" field
must be machine-usable (addr-specs) and may not contain named
lists (groups).
MimeMessage doesn't recognize the "Sender" field as being different from
"From" (in comments uses the terms interchangeably) so I'd say leave the "From"
header as required.
I am on board with creating a custom validator for the internet addresses
though, that would be great.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
