date:20160309

[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: James Server
  Issue Type: Bug
Affects Versions: Trunk
Reporter: Tellier Benoit
 Fix For: Trunk


Here are the following steps I followed :

 - 1. Build James using java 6

# docker build -t james/project/6 dockerfiles/compilation/java-6
# docker run -c 8 -m 16g -v $PWD/.m2:/root/.m2 -v $PWD:/origin -v 
$PWD/dockerfiles/run/spring/destination:/destination -t james/project/6
-s jpa-user-flags

 - 2. Deploy james using java6

# docker build -t james_run dockerfiles/run/spring/
# docker run --hostname any -p "25:25" -p "110:110" -p "143:143" -p "465:465" 
-p "587:587" -p "993:993" --name james_run -t james_run

 - 3. Prepare james for integration testing

# docker exec james_run 
/root/james-server-app-3.0.0-beta5-SNAPSHOT/bin/james-cli.sh  -h 127.0.0.1 -p 
 adddomain domain
# docker exec james_run 
/root/james-server-app-3.0.0-beta5-SNAPSHOT/bin/james-cli.sh  -h 127.0.0.1 -p 
 adduser imapuser@domain password

 - 4. Run integration testing

# docker build -t james/project/8 dockerfiles/compilation/java-8
# docker run -c 8 -m 16g -v $PWD/.m2:/root/.m2 -v $PWD:/origin -t 
james/project/8 -s master

--

The result is : 

jvm 1| WARN  07:27:15,901 | james.imapserver | ID=2094168905 Error while 
processing imap request: java.lang.NullPointerException - null
jvm 1| DEBUG 07:27:15,901 | james.imapserver | ID=2094168905 Error while 
processing imap request
jvm 1| java.lang.NullPointerException
jvm 1|  at 
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createUserFlags(AbstractJPAMailboxMessage.java:528)
jvm 1|  at 
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createFlags(AbstractJPAMailboxMessage.java:524)
jvm 1|  at 
org.apache.james.mailbox.store.MessageResultImpl.getFlags(MessageResultImpl.java:83)
jvm 1|  at 
org.apache.james.imap.processor.base.SelectedMailboxImpl.init(SelectedMailboxImpl.java:124)
jvm 1|  at 
org.apache.james.imap.processor.base.SelectedMailboxImpl.(SelectedMailboxImpl.java:102)
jvm 1|  at 
org.apache.james.imap.processor.AbstractSelectionProcessor.selectMailbox(AbstractSelectionProcessor.java:411)
jvm 1|  at 
org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:118)



MPT tests activated with -Pjpa profile also catch the problem.





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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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 that broke this (I remember something committed
months ago about deleting a JPA raw... Maybe this is the root cause of
your struggles...)

--

Here are the following steps I followed :

 - 1. Build James using java 6

# docker build -t james/project/6 dockerfiles/compilation/java-6
# docker run -c 8 -m 16g -v $PWD/.m2:/root/.m2 -v $PWD:/origin -v
$PWD/dockerfiles/run/spring/destination:/destination -t james/project/6
-s jpa-user-flags

 - 2. Deploy james using java6

# docker build -t james_run dockerfiles/run/spring/
# docker run --hostname any -p "25:25" -p "110:110" -p "143:143" -p
"465:465" -p "587:587" -p "993:993" --name james_run -t james_run

 - 3. Prepare james for integration testing

# docker exec james_run
/root/james-server-app-3.0.0-beta5-SNAPSHOT/bin/james-cli.sh  -h
127.0.0.1 -p  adddomain domain
# docker exec james_run
/root/james-server-app-3.0.0-beta5-SNAPSHOT/bin/james-cli.sh  -h
127.0.0.1 -p  adduser imapuser@domain password

 - 4. Run integration testing

# docker build -t james/project/8 dockerfiles/compilation/java-8
# docker run -c 8 -m 16g -v $PWD/.m2:/root/.m2 -v $PWD:/origin -t
james/project/8 -s master

--

Le 10/03/2016 00:32, Simon Roth a écrit :
> 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
> dockerfiles/run/spring/destination/conf in the git repository, adapted
> the ports and started the server with the run.sh script located in the
> bin folder. Afterwards I created a user as well as a domain using
> james-cli.sh.
> 
> In order to test the setup, in the first iteration I simply try sending
> an email to myself (the server where james is running), using
> Thunderbird as user agent on my local PC.
> 
> i.e.
> 1st step: Thunderbird -> Server -> Mailbox via SMTP (seems to work by
> inspecting the log file, mail seems to be stored in the mailbox no error
> occurs)
> 2nd step: Read the mail in Thunderbird via IMAP.
> Mailbox->Server->Thunderbird.
> 
> And here, in the 2nd step is where the error occurs, after clicking the
> "Receive" button in Thunderbird. The mail counter in Thunderbird shows
> that there is a new mail, but it is not really there/not readable and
> the NullPointer exception occurs on the server side.
> 
> 
> Quoting Matthieu Baechler :
> 
>> Hi Simon,
>>
>> Do you mean you are building from git master ?
>>
>> If so, could you describe your usecase with more details ? What do you
>> mean by "receive en email via IMAP" ?
>>
>> Cheers,
>>
>> -- 
>> Matthieu
>>
>> On 09/03/2016 17:45, Simon Roth wrote:
>>> 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
>>> if I try to receive an email via IMAP the following error occurs:
>>>
>>> DEBUG 16:48:51,831 | james.imapserver | ID=-2032248463 Loaded mailbox
>>> #private:t...@test.at:Sent
>>> WARN  16:48:51,839 | james.imapserver | ID=-2032248463 Error while
>>> processing imap request: java.lang.NullPointerException - null
>>> DEBUG 16:48:51,839 | james.imapserver | ID=-2032248463 Error while
>>> processing imap request
>>> java.lang.NullPointerException
>>> at
>>> org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createUserFlags(AbstractJPAMailboxMessage.java:528)
>>>
>>>
>>> at
>>> org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createFlags(AbstractJPAMailboxMessage.java:524)
>>>
>>>
>>> at
>>> org.apache.james.mailbox.store.MessageResultImpl.getFlags(MessageResultImpl.java:83)
>>>
>>>
>>> at
>>> org.apache.james.imap.processor.base.SelectedMailboxImpl.init(SelectedMailboxImpl.java:124)
>>>
>>>
>>> at
>>> org.apache.james.imap.processor.base.SelectedMailboxImpl.(SelectedMailboxImpl.java:102)
>>>
>>>
>>> at
>>> org.apache.james.imap.processor.AbstractSelectionProcessor.selectMailbox(AbstractSelectionProcessor.java:411)
>>>
>>>
>>> at
>>> org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:118)
>>>
>>>
>>> at
>>> org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(AbstractSelectionProcessor.java:83)
>>>
>>>
>>>
>>> Am I the only one facing this

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 -> 
org.apache.thrift:thrift:jar:0.2.0: Failed to read artifact descriptor for 
org.apache.thrift:thrift:jar:0.2.0: Could not transfer artifact 
org.apache.thrift:thrift:pom:0.2.0 from/to codehaus 
(http://repository.codehaus.org/ ): 
repository.codehaus.org : unknown error: 
Unknown host repository.codehaus.org : unknown 
error -> [Help 1]

[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&focusedCommentId=15188614#comment-15188614
 ] 

Eric Charles commented on JSIEVE-96:


status is closed

> How to deploy Sieve scripts
> ---
>
> Key: JSIEVE-96
> URL: https://issues.apache.org/jira/browse/JSIEVE-96
> Project: James jSieve
>  Issue Type: Wish
>  Components: JSieve (Main)
>Reporter: Dan
>Priority: Trivial
>
> I looked for two days and could not find an exhaustive documentation of how 
> to use Sieve scripts with James.
> There are bits and pieces all over the place but there is no single 
> authoritative source that would explain steps necessary to successfully 
> deploy scripts on James.
> Note: I am currently working with version 2.2, but even documentation for 
> latest version can not be found.



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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: https://issues.apache.org/jira/browse/JSIEVE-67
> Project: James jSieve
>  Issue Type: Improvement
>Affects Versions: 0.2, 0.3, 0.4
>Reporter: Robert Burrell Donkin
>Assignee: Robert Burrell Donkin
> Fix For: 0.5
>
>
> Improve JavaDocs and website 



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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
> 
>
> Key: JSIEVE-73
> URL: https://issues.apache.org/jira/browse/JSIEVE-73
> Project: James jSieve
>  Issue Type: Improvement
>Affects Versions: 0.2, 0.3, 0.4
>Reporter: Robert Burrell Donkin
>Assignee: Robert Burrell Donkin
> Fix For: 0.6
>
>
> The Body Extension is now a standard. The implementation needs to be checked 
> against the specification, and any differences corrected.



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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
> --
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: James jSieve
>  Issue Type: Improvement
>Reporter: Steve Brewin
>Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP 
> session, but if this exists why not use it to allow users to manage their 
> Sieve scripts by mail?
> Simple get and put operations should be sufficient.



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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: JSIEVE-67
> URL: https://issues.apache.org/jira/browse/JSIEVE-67
> Project: James jSieve
>  Issue Type: Improvement
>Affects Versions: 0.2, 0.3, 0.4
>Reporter: Robert Burrell Donkin
>Assignee: Robert Burrell Donkin
> Fix For: 0.5
>
>
> Improve JavaDocs and website 



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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 
> Scipts and default implementations. 
> --
>
> Key: JSIEVE-77
> URL: https://issues.apache.org/jira/browse/JSIEVE-77
> Project: James jSieve
>  Issue Type: Improvement
>Affects Versions: 1.0
>Reporter: Steve Brewin
>Assignee: Steve Brewin
> Fix For: 1.0
>
>
> The simplest interface would allow per user retrieval of a script. Its 
> default implementation would be encapsulate current practise and stream it 
> from the file system.
> An extended interface would allow per user persisting of a script. Its 
> default implementation would be to replace the script stored on the file 
> system.
> Other implementations may use other persistence mechanisms, including JPA, 
> JDBC, LDAP...



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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
> ---
>
> Key: JSIEVE-96
> URL: https://issues.apache.org/jira/browse/JSIEVE-96
> Project: James jSieve
>  Issue Type: Wish
>  Components: JSieve (Main)
>Reporter: Dan
>Priority: Trivial
>
> I looked for two days and could not find an exhaustive documentation of how 
> to use Sieve scripts with James.
> There are bits and pieces all over the place but there is no single 
> authoritative source that would explain steps necessary to successfully 
> deploy scripts on James.
> Note: I am currently working with version 2.2, but even documentation for 
> latest version can not be found.



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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
> 
>
> Key: JSIEVE-86
> URL: https://issues.apache.org/jira/browse/JSIEVE-86
> Project: James jSieve
>  Issue Type: New Feature
>Reporter: Eric Charles
>
> sieve manager is aimed to be used in server
> james-server-filesystem-api is the one to talk about...



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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
> ---
>
> Key: JSIEVE-83
> URL: https://issues.apache.org/jira/browse/JSIEVE-83
> Project: James jSieve
>  Issue Type: Improvement
>Affects Versions: 0.5
>Reporter: Eric Charles
>Assignee: Eric Charles
> Fix For: 0.5
>
>
> Move https://svn.apache.org/repos/asf/james/mangesieve/trunk/ as a jsieve 
> submodule.
> The managesieve may be independent of jsieve, but this will allow to quickly 
> ship it in a release without having to define a new web site, jira,...



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[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 trunk for about a month

> Ensure Body Extension Functions As Per Specification
> 
>
> Key: JSIEVE-73
> URL: https://issues.apache.org/jira/browse/JSIEVE-73
> Project: James jSieve
>  Issue Type: Improvement
>Affects Versions: 0.2, 0.3, 0.4
>Reporter: Robert Burrell Donkin
>Assignee: Robert Burrell Donkin
> Fix For: 0.6
>
>
> The Body Extension is now a standard. The implementation needs to be checked 
> against the specification, and any differences corrected.



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

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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
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
dockerfiles/run/spring/destination/conf in the git repository, adapted
the ports and started the server with the run.sh script located in the
bin folder. Afterwards I created a user as well as a domain using
james-cli.sh.

In order to test the setup, in the first iteration I simply try sending
an email to myself (the server where james is running), using
Thunderbird as user agent on my local PC.

i.e.
1st step: Thunderbird -> Server -> Mailbox via SMTP (seems to work by
inspecting the log file, mail seems to be stored in the mailbox no error
occurs)
2nd step: Read the mail in Thunderbird via IMAP.
Mailbox->Server->Thunderbird.

And here, in the 2nd step is where the error occurs, after clicking the
"Receive" button in Thunderbird. The mail counter in Thunderbird shows
that there is a new mail, but it is not really there/not readable and
the NullPointer exception occurs on the server side.


Quoting Matthieu Baechler :


Hi Simon,

Do you mean you are building from git master ?

If so, could you describe your usecase with more details ? What do you
mean by "receive en email via IMAP" ?

Cheers,

--
Matthieu

On 09/03/2016 17:45, Simon Roth wrote:

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
if I try to receive an email via IMAP the following error occurs:

DEBUG 16:48:51,831 | james.imapserver | ID=-2032248463 Loaded mailbox
#private:t...@test.at:Sent
WARN  16:48:51,839 | james.imapserver | ID=-2032248463 Error while
processing imap request: java.lang.NullPointerException - null
DEBUG 16:48:51,839 | james.imapserver | ID=-2032248463 Error while
processing imap request
java.lang.NullPointerException
at
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createUserFlags(AbstractJPAMailboxMessage.java:528)


at
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createFlags(AbstractJPAMailboxMessage.java:524)


at
org.apache.james.mailbox.store.MessageResultImpl.getFlags(MessageResultImpl.java:83)


at
org.apache.james.imap.processor.base.SelectedMailboxImpl.init(SelectedMailboxImpl.java:124)


at
org.apache.james.imap.processor.base.SelectedMailboxImpl.(SelectedMailboxImpl.java:102)


at
org.apache.james.imap.processor.AbstractSelectionProcessor.selectMailbox(AbstractSelectionProcessor.java:411)


at
org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:118)


at
org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(AbstractSelectionProcessor.java:83)



Am I the only one facing this problem? Any suggestions for solving it?


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org




-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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  
dockerfiles/run/spring/destination/conf in the git repository, adapted  
the ports and started the server with the run.sh script located in the  
bin folder. Afterwards I created a user as well as a domain using  
james-cli.sh.


In order to test the setup, in the first iteration I simply try  
sending an email to myself (the server where james is running), using  
Thunderbird as user agent on my local PC.


i.e.
1st step: Thunderbird -> Server -> Mailbox via SMTP (seems to work by  
inspecting the log file, mail seems to be stored in the mailbox no  
error occurs)

2nd step: Read the mail in Thunderbird via IMAP. Mailbox->Server->Thunderbird.

And here, in the 2nd step is where the error occurs, after clicking  
the "Receive" button in Thunderbird. The mail counter in Thunderbird  
shows that there is a new mail, but it is not really there/not  
readable and the NullPointer exception occurs on the server side.



Quoting Matthieu Baechler :


Hi Simon,

Do you mean you are building from git master ?

If so, could you describe your usecase with more details ? What do  
you mean by "receive en email via IMAP" ?


Cheers,

--
Matthieu

On 09/03/2016 17:45, Simon Roth wrote:

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
if I try to receive an email via IMAP the following error occurs:

DEBUG 16:48:51,831 | james.imapserver | ID=-2032248463 Loaded mailbox
#private:t...@test.at:Sent
WARN  16:48:51,839 | james.imapserver | ID=-2032248463 Error while
processing imap request: java.lang.NullPointerException - null
DEBUG 16:48:51,839 | james.imapserver | ID=-2032248463 Error while
processing imap request
java.lang.NullPointerException
at
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createUserFlags(AbstractJPAMailboxMessage.java:528)

at
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createFlags(AbstractJPAMailboxMessage.java:524)

at
org.apache.james.mailbox.store.MessageResultImpl.getFlags(MessageResultImpl.java:83)

at
org.apache.james.imap.processor.base.SelectedMailboxImpl.init(SelectedMailboxImpl.java:124)

at
org.apache.james.imap.processor.base.SelectedMailboxImpl.(SelectedMailboxImpl.java:102)

at
org.apache.james.imap.processor.AbstractSelectionProcessor.selectMailbox(AbstractSelectionProcessor.java:411)

at
org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:118)

at
org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(AbstractSelectionProcessor.java:83)


Am I the only one facing this problem? Any suggestions for solving it?


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org




-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Re: IMAP mailbox error

2016-03-09 Thread Matthieu Baechler


Hi Simon,

Do you mean you are building from git master ?

If so, could you describe your usecase with more details ? What do you 
mean by "receive en email via IMAP" ?


Cheers,

--
Matthieu

On 09/03/2016 17:45, Simon Roth wrote:

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
if I try to receive an email via IMAP the following error occurs:

DEBUG 16:48:51,831 | james.imapserver | ID=-2032248463 Loaded mailbox
#private:t...@test.at:Sent
WARN  16:48:51,839 | james.imapserver | ID=-2032248463 Error while
processing imap request: java.lang.NullPointerException - null
DEBUG 16:48:51,839 | james.imapserver | ID=-2032248463 Error while
processing imap request
java.lang.NullPointerException
 at
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createUserFlags(AbstractJPAMailboxMessage.java:528)

 at
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createFlags(AbstractJPAMailboxMessage.java:524)

 at
org.apache.james.mailbox.store.MessageResultImpl.getFlags(MessageResultImpl.java:83)

 at
org.apache.james.imap.processor.base.SelectedMailboxImpl.init(SelectedMailboxImpl.java:124)

 at
org.apache.james.imap.processor.base.SelectedMailboxImpl.(SelectedMailboxImpl.java:102)

 at
org.apache.james.imap.processor.AbstractSelectionProcessor.selectMailbox(AbstractSelectionProcessor.java:411)

 at
org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:118)

 at
org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(AbstractSelectionProcessor.java:83)


Am I the only one facing this problem? Any suggestions for solving it?


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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 if I try to receive an email via IMAP the following error occurs:


DEBUG 16:48:51,831 | james.imapserver | ID=-2032248463 Loaded mailbox  
#private:t...@test.at:Sent
WARN  16:48:51,839 | james.imapserver | ID=-2032248463 Error while  
processing imap request: java.lang.NullPointerException - null
DEBUG 16:48:51,839 | james.imapserver | ID=-2032248463 Error while  
processing imap request

java.lang.NullPointerException
	at  
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createUserFlags(AbstractJPAMailboxMessage.java:528)
	at  
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMailboxMessage.createFlags(AbstractJPAMailboxMessage.java:524)
	at  
org.apache.james.mailbox.store.MessageResultImpl.getFlags(MessageResultImpl.java:83)
	at  
org.apache.james.imap.processor.base.SelectedMailboxImpl.init(SelectedMailboxImpl.java:124)
	at  
org.apache.james.imap.processor.base.SelectedMailboxImpl.(SelectedMailboxImpl.java:102)
	at  
org.apache.james.imap.processor.AbstractSelectionProcessor.selectMailbox(AbstractSelectionProcessor.java:411)
	at  
org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:118)
	at  
org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(AbstractSelectionProcessor.java:83)


Am I the only one facing this problem? Any suggestions for solving it?


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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 -> 
org.apache.thrift:thrift:jar:0.2.0: Failed to read artifact descriptor for 
org.apache.thrift:thrift:jar:0.2.0: Could not transfer artifact 
org.apache.thrift:thrift:pom:0.2.0 from/to codehaus 
(http://repository.codehaus.org/): repository.codehaus.org: unknown error: 
Unknown host repository.codehaus.org: unknown error -> [Help 1]


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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 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
https://issues.apache.org/jira/browse/IMAP-370

That is 13 tickets to resolve / close...

Thank you,

Benoit

Le 02/03/2016 17:11, Benoit Tellier a écrit :

Hi,

As part of my work on JSIEVE first at Télécom Sudparis, and then at
Linagora, I solved several issues.

Unfortunately, I lack rights on the JIRA to be able to close the issues
my self.

And I have troubles finding people to close it for me.

Here is the list of issues :

https://issues.apache.org/jira/browse/JSIEVE-79
https://issues.apache.org/jira/browse/JSIEVE-86
https://issues.apache.org/jira/browse/JSIEVE-96
https://issues.apache.org/jira/browse/JSIEVE-67
https://issues.apache.org/jira/browse/JSIEVE-77
https://issues.apache.org/jira/browse/JSIEVE-83
https://issues.apache.org/jira/browse/JSIEVE-73
https://issues.apache.org/jira/browse/JAMES-1192
https://issues.apache.org/jira/browse/JAMES-1482
https://issues.apache.org/jira/browse/JAMES-511
https://issues.apache.org/jira/browse/JAMES-650

I then have other questions :

  - Is that normal that, as a PMC member, I can't close / resolve other
people JIRA ?
  - If it is not, how do I get this right ?
  - If it is, how do I proceed ?

Thanks,

And best regards,

Benoit

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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
https://issues.apache.org/jira/browse/IMAP-370

That is 13 tickets to resolve / close...

Thank you,

Benoit

Le 02/03/2016 17:11, Benoit Tellier a écrit :
> Hi,
> 
> As part of my work on JSIEVE first at Télécom Sudparis, and then at
> Linagora, I solved several issues.
> 
> Unfortunately, I lack rights on the JIRA to be able to close the issues
> my self.
> 
> And I have troubles finding people to close it for me.
> 
> Here is the list of issues :
> 
> https://issues.apache.org/jira/browse/JSIEVE-79
> https://issues.apache.org/jira/browse/JSIEVE-86
> https://issues.apache.org/jira/browse/JSIEVE-96
> https://issues.apache.org/jira/browse/JSIEVE-67
> https://issues.apache.org/jira/browse/JSIEVE-77
> https://issues.apache.org/jira/browse/JSIEVE-83
> https://issues.apache.org/jira/browse/JSIEVE-73
> https://issues.apache.org/jira/browse/JAMES-1192
> https://issues.apache.org/jira/browse/JAMES-1482
> https://issues.apache.org/jira/browse/JAMES-511
> https://issues.apache.org/jira/browse/JAMES-650
> 
> I then have other questions :
> 
>  - Is that normal that, as a PMC member, I can't close / resolve other
> people JIRA ?
>  - If it is not, how do I get this right ?
>  - If it is, how do I proceed ?
> 
> Thanks,
> 
> And best regards,
> 
> Benoit
> 
> -
> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
> For additional commands, e-mail: server-dev-h...@james.apache.org
> 

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

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

Re: IMAP mailbox error

Unable to build james-server-3.0-beta4

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

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

[jira] [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

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

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

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

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

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

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

Re: IMAP mailbox error

Re: IMAP mailbox error

Re: IMAP mailbox error

IMAP mailbox error

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

Re: Closing / resolving issues on JIRA

Re: Closing / resolving issues on JIRA

20 matches

Site Navigation

Mail list logo

Footer information