[jira] [Created] (JAMES-1704) NullPointerException when Selecting a mailbox using JPA mailbox backend

2016-03-09 Thread Tellier Benoit (JIRA)
Tellier Benoit created JAMES-1704: - Summary: NullPointerException when Selecting a mailbox using JPA mailbox backend Key: JAMES-1704 URL: https://issues.apache.org/jira/browse/JAMES-1704 Project:

Re: IMAP mailbox error

2016-03-09 Thread Benoit Tellier
Hi Simon, I reproduced your problem by running some integration tests on a distant James server... I did not succeed yet to write unit tests reproducing your problem... I will open a JIRA issue for this. I will also look why this was not covered by MPT tests... And try to find the change-set

Unable to build james-server-3.0-beta4

2016-03-09 Thread Alan Cabrera
I tried running mvn clean package and got: [ERROR] Failed to execute goal on project james-server-data-hbase: Could not resolve dependencies for project org.apache.james:james-server-data-hbase:jar:3.0-beta4: Failed to collect dependencies at org.apache.hbase:hbase:jar:0.90.4 ->

[jira] [Commented] (JSIEVE-96) How to deploy Sieve scripts

2016-03-09 Thread Eric Charles (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188614#comment-15188614 ] Eric Charles commented on JSIEVE-96: status is closed > How to deploy Sieve scripts >

[jira] [Closed] (JSIEVE-67) Improve Documentation

2016-03-09 Thread Eric Charles (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JSIEVE-67. -- > Improve Documentation > - > > Key: JSIEVE-67 > URL:

[jira] [Closed] (JSIEVE-73) Ensure Body Extension Functions As Per Specification

2016-03-09 Thread Eric Charles (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JSIEVE-73. -- > Ensure Body Extension Functions As Per Specification >

[jira] [Closed] (JSIEVE-79) Implement a mechanism for users to manage their Sieve scripts via SMTP

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-79. Resolution: Fixed > Implement a mechanism for users to manage their Sieve scripts via SMTP >

[jira] [Closed] (JSIEVE-77) Interfaces describing the operations required for managing per user Sieve Scipts and default implementations.

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-77. Resolution: Fixed > Interfaces describing the operations required for managing per user Sieve >

[jira] [Closed] (JSIEVE-96) How to deploy Sieve scripts

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-96. Resolution: Fixed > How to deploy Sieve scripts > --- > >

[jira] [Closed] (JSIEVE-86) Potential bidirectional dependency between jsieve manager and server

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-86. Resolution: Fixed > Potential bidirectional dependency between jsieve manager and server >

[jira] [Resolved] (JSIEVE-67) Improve Documentation

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit resolved JSIEVE-67. -- Resolution: Fixed > Improve Documentation > - > > Key:

[jira] [Closed] (JSIEVE-83) Integrate managesieve in the current jSieve modules

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-83. Resolution: Fixed > Integrate managesieve in the current jSieve modules >

[jira] [Resolved] (JSIEVE-73) Ensure Body Extension Functions As Per Specification

2016-03-09 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit resolved JSIEVE-73. -- Resolution: Fixed Fix Version/s: (was: 0.5) 0.6 Commits are on

Re: IMAP mailbox error

2016-03-09 Thread Matthieu Baechler
Ok, thank you very much for your effort at describing what you did. We'll have a look. -- Matthieu On 09/03/2016 18:32, Simon Roth wrote: Yes, I built from git master. I'm trying to setup the server on a remote VM. Therefore I copied the generated

Re: IMAP mailbox error

2016-03-09 Thread Simon Roth
Yes, I built from git master. I'm trying to setup the server on a remote VM. Therefore I copied the generated james-server-app-3.0.0-beta5-SNAPSHOT-app.tar.gz file from my local PC to the VM, extracted it there, replaced the conf folder from the extracted folder with the conf folder in

IMAP mailbox error

2016-03-09 Thread Simon Roth
I'm trying to setup a James Server built from trunk. Except the ports everything is set up with the provided default configuration in dockerfiles/run/spring/destination/conf and therefore derby is used as database. I added a user as well as a domain. SMTP seems working fine so far. But

james-server-3.0-beta4 does not build for me

2016-03-09 Thread Alan Cabrera
’ tried running mvn clean package and got: [ERROR] Failed to execute goal on project james-server-data-hbase: Could not resolve dependencies for project org.apache.james:james-server-data-hbase:jar:3.0-beta4: Failed to collect dependencies at org.apache.hbase:hbase:jar:0.90.4 ->

Re: Closing / resolving issues on JIRA

2016-03-09 Thread Eric Charles
Hi Benoit, Sorry for this, permissions were not applied... Can you try again? You should normally be able to administer JIRA projects. On 09/03/16 10:20, Benoit Tellier wrote: Sorry for being insistent, but I got no responses for the past week. In my opinion, having tasks in JIRA reflecting

Re: Closing / resolving issues on JIRA

2016-03-09 Thread Benoit Tellier
Sorry for being insistent, but I got no responses for the past week. In my opinion, having tasks in JIRA reflecting the current state of the project is important, and we should be able to work on tasks that already exists. By the way I also found : https://issues.apache.org/jira/browse/IMAP-167