You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/01/29 03:42:00 UTC
[jira] [Closed] (JAMES-2163) Passing null parameters to Mail seems
possible
[ https://issues.apache.org/jira/browse/JAMES-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tellier Benoit closed JAMES-2163.
---------------------------------
> Passing null parameters to Mail seems possible
> ----------------------------------------------
>
> Key: JAMES-2163
> URL: https://issues.apache.org/jira/browse/JAMES-2163
> Project: James Server
> Issue Type: Bug
> Components: James Core
> Affects Versions: master
> Reporter: Tellier Benoit
> Priority: Major
> Fix For: master
>
>
> As reported by @arpitsriv on Gitter, it seems possible to write an email with possibly null parameters.
> This causes defacts later on, for instance in his case when enqueing the email.
> We need upfront null value rejection on the MailImpl object, via Preconditions. This will bring the error closer to the code causing the defect, and makes debugging easier.
> Unit tests should be provided on the MailImpl object.
> Thanks to @arpitsriv for his time spotting and understanding this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org