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

ASF GitHub Bot commented on JAMES-1590:
---------------------------------------

GitHub user chibenwa opened a pull request:

    https://github.com/apache/james/pull/1

    JAMES-1590 containsdomain CLI command should have an output

    This pull request adds an output to the containsdomain command.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chibenwa/james JAMES-1590

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/james/pull/1.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1
    
----
commit 517125f37cdd3346d051eae22b390ea392eac3bd
Author: benwa <[email protected]>
Date:   2015-07-17T16:30:40Z

    JAMES-1590 containsdomain CLI command should have an output

----


> containsDomain command returns nothing
> --------------------------------------
>
>                 Key: JAMES-1590
>                 URL: https://issues.apache.org/jira/browse/JAMES-1590
>             Project: James Server
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Tellier Benoit
>
> containsDomain returns no output, contrary to what is expected.
> Exemple :
> root@yoda:/home/btellier# docker exec 9253 
> /root/james-server-app-3.0.0-beta5-SNAPSHOT/bin/james-cli.sh -h 127.0.0.1 -p 
> 9999 containsdomain domain
> containsdomain command executed sucessfully in 57 ms.
> Note : This bug was present before JAMES-1584, we just didn't notice it.
> Acceptance criteria :
>  - containsDomain command actually returns wether or not the domain is 
> contained.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to