[ 
https://issues.apache.org/jira/browse/NIFI-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173658#comment-16173658
 ] 

ASF GitHub Bot commented on NIFI-4326:
--------------------------------------

Github user btwood commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2111#discussion_r140057900
  
    --- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/ExtractEmailHeaders.java
 ---
    @@ -103,6 +103,22 @@
                 .defaultValue("x-mailer")
                 .build();
     
    +    private static final AllowableValue STRICT_ADDRESSING = new 
AllowableValue("true", "Strict Address Parsing", "Strict email address format 
will be enforced. FlowFiles will be transfered to the failure relationship if 
the email address is invalid.");
    --- End diff --
    
    @kevdoran I've committed the fix. I didn't know about the -Pcontrib-check 
build. I added that to my build config and got it to pass. Should be good now. 
Thanks.


> ExtractEmailHeaders.java unhandled Exceptions
> ---------------------------------------------
>
>                 Key: NIFI-4326
>                 URL: https://issues.apache.org/jira/browse/NIFI-4326
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.3.0
>         Environment: jdk 1.8.0_121-b13
> openjdk 8u131-b11
>            Reporter: Benjamin Wood
>            Assignee: Benjamin Wood
>            Priority: Minor
>             Fix For: 1.4.0
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The ExtractEmailHeaders  processor throws a NullPointerException if there is 
> no TO, CC, and BCC recipients.
> If there are no recipients "originalMessage.getAllRecipients()" returns NULL, 
> and not a 0 length array.
> If an address is empty (<> or " ") then getRecipients() will throw an "Empty 
> Address" AddressException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to