[jira] [Commented] (JAMES-3225) Provide automated builds for Apache James - (restore builds.apache.org ?)
[ https://issues.apache.org/jira/browse/JAMES-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139149#comment-17139149 ] Antoine Duprat commented on JAMES-3225: --- Hi, I will investigate on that next week and give you some feedback. > Provide automated builds for Apache James - (restore builds.apache.org ?) > -- > > Key: JAMES-3225 > URL: https://issues.apache.org/jira/browse/JAMES-3225 > Project: James Server > Issue Type: Task >Reporter: Ioan Eugen Stan >Assignee: Ioan Eugen Stan >Priority: Major > > For a long time we had builds that ran on the Apache Infrastructure > https://builds.apache.org/view/All/job/james-mailet/ . > The build infrastructure is not running for ~ 3 years now. > I believe it is important for us to have automated builds. > This ticket should gather the work needed to make this a reality. > There are lots of things to take into consideration. > My ( [~ieugen] ) opinions on how to handle this. > * builds should run automatically > * builds should run fast < 10 min > * there are several things they should do (not exhaustive) > ** verify the source code > ** compile the source code > ** run the unit tests > ** run the integration tests > ** publish SNAPSHOTS (only from master or develop ?!) > ** run code analytics > ** publish reports relating to build > ** provide build status for other services > For smaller projects this is a no-brainer. > For the current state of Apache James this is a challange, especially in the > context of > - multiple git branches and PR's > - the distributed integration tests which take a long time > Given the limited resources available for us on the Apache infrastructure we > will have to be selective of what we do. > Personally I don't see how we can run the current (40mni +) integration suite > on each push / build. I'm pretty sure we will get banned :) or throttled. > So a discussion should be in order on how to solve these issues but some > options regarding what we can do: > - make integration tests OPT-IN > - run (distributed) integration tests once a day or once every 6h / 12h > - have build profiles that build a common subset all the time and run > The nuclear option: prune some of the components we have in James and we > don't want to support or move them out of the common project. > This is something we should consider especially for buggy components or for > components that don't have a maintainer. > We have limited time and resources. > We can't maintain everything for everybody. > We should be mindful of this. > We can take inspiration from the OFBiz project > https://builds.apache.org/view/All/job/Apache%20OFBiz/ . -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-3031) PATH variable in dockerfiles is wrong
[ https://issues.apache.org/jira/browse/JAMES-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-3031: -- Description: The PATH environment variable declared in the dockerfiles is wrong (equals missing). According to the Dockerfile reference([https://docs.docker.com/engine/reference/builder/#env]) : _The second form, ENV = ..., allows for multiple variables to be set at one time. Notice that the second form uses the equals sign (=) in the syntax, while the first form does not. Like command line parsing, quotes and backslashes can be used to include spaces within values._ was: The PATH environment variable declared in the dockerfiles is wrong (equals missing). According to the [Dockerfile reference](https://docs.docker.com/engine/reference/builder/#env) : _The second form, ENV = ..., allows for multiple variables to be set at one time. Notice that the second form uses the equals sign (=) in the syntax, while the first form does not. Like command line parsing, quotes and backslashes can be used to include spaces within values._ > PATH variable in dockerfiles is wrong > - > > Key: JAMES-3031 > URL: https://issues.apache.org/jira/browse/JAMES-3031 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Assignee: Antoine Duprat >Priority: Major > Fix For: 3.5.0 > > > The PATH environment variable declared in the dockerfiles is wrong (equals > missing). > According to the Dockerfile > reference([https://docs.docker.com/engine/reference/builder/#env]) : > _The second form, ENV = ..., allows for multiple variables to be > set at one time. Notice that the second form uses the equals sign (=) in the > syntax, while the first form does not. Like command line parsing, quotes and > backslashes can be used to include spaces within values._ -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-3031) PATH variable in dockerfiles is wrong
[ https://issues.apache.org/jira/browse/JAMES-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-3031: -- Description: The PATH environment variable declared in the dockerfiles is wrong (equals missing). According to the [Dockerfile reference](https://docs.docker.com/engine/reference/builder/#env) : _The second form, ENV = ..., allows for multiple variables to be set at one time. Notice that the second form uses the equals sign (=) in the syntax, while the first form does not. Like command line parsing, quotes and backslashes can be used to include spaces within values._ was: The PATH environment variable declared in the dockerfiles is wrong (equals missing). According to the [Dockerfile reference]([https://docs.docker.com/engine/reference/builder /#env) : > |https://docs.docker.com/engine/reference/builder/#env)]The second form, ENV >= ..., allows for multiple variables to be set at one time. Notice >that the second form uses the equals sign (=) in the syntax, while the first >form does not. Like command line parsing, quotes and backslashes can be used >to include spaces within values. > PATH variable in dockerfiles is wrong > - > > Key: JAMES-3031 > URL: https://issues.apache.org/jira/browse/JAMES-3031 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Assignee: Antoine Duprat >Priority: Major > Fix For: 3.5.0 > > > The PATH environment variable declared in the dockerfiles is wrong (equals > missing). > According to the [Dockerfile > reference](https://docs.docker.com/engine/reference/builder/#env) : > _The second form, ENV = ..., allows for multiple variables to be > set at one time. Notice that the second form uses the equals sign (=) in the > syntax, while the first form does not. Like command line parsing, quotes and > backslashes can be used to include spaces within values._ -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-3031) PATH variable in dockerfiles is wrong
Antoine Duprat created JAMES-3031: - Summary: PATH variable in dockerfiles is wrong Key: JAMES-3031 URL: https://issues.apache.org/jira/browse/JAMES-3031 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat Assignee: Antoine Duprat Fix For: 3.5.0 The PATH environment variable declared in the dockerfiles is wrong (equals missing). According to the [Dockerfile reference]([https://docs.docker.com/engine/reference/builder /#env) : > |https://docs.docker.com/engine/reference/builder/#env)]The second form, ENV >= ..., allows for multiple variables to be set at one time. Notice >that the second form uses the equals sign (=) in the syntax, while the first >form does not. Like command line parsing, quotes and backslashes can be used >to include spaces within values. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2922) Configure index.write.wait_for_active_shards parameter
[ https://issues.apache.org/jira/browse/JAMES-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2922. - Fix Version/s: 3.5.0 Resolution: Fixed > Configure index.write.wait_for_active_shards parameter > -- > > Key: JAMES-2922 > URL: https://issues.apache.org/jira/browse/JAMES-2922 > Project: James Server > Issue Type: New Feature > Components: elasticsearch >Reporter: Antoine Duprat >Assignee: Antoine Duprat >Priority: Major > Fix For: 3.5.0 > > > According to the ElasticSearch > [documentation]([https://www.elastic.co/guide/en/elasticsearch/reference/6.2/docs-index_.html#index-wait-for-active-shards),] > the `wait_for_active_shards` parameter should be configured while creating > indices. > We should bring such configuration property in the ElasticSearch > configuration file. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2922) Configure index.write.wait_for_active_shards parameter
Antoine Duprat created JAMES-2922: - Summary: Configure index.write.wait_for_active_shards parameter Key: JAMES-2922 URL: https://issues.apache.org/jira/browse/JAMES-2922 Project: James Server Issue Type: New Feature Components: elasticsearch Reporter: Antoine Duprat Assignee: Antoine Duprat According to the ElasticSearch [documentation]([https://www.elastic.co/guide/en/elasticsearch/reference/6.2/docs-index_.html#index-wait-for-active-shards),] the `wait_for_active_shards` parameter should be configured while creating indices. We should bring such configuration property in the ElasticSearch configuration file. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2773) Add glowroot in the docker images
[ https://issues.apache.org/jira/browse/JAMES-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2773. - > Add glowroot in the docker images > - > > Key: JAMES-2773 > URL: https://issues.apache.org/jira/browse/JAMES-2773 > Project: James Server > Issue Type: Bug >Reporter: Rémi Kowalski >Priority: Major > Fix For: 3.4.0 > > > In order to have instrumentation on the JMAP and IMAP transactions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Reopened] (JAMES-2806) Adding bucket capability into BlobStore
[
https://issues.apache.org/jira/browse/JAMES-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat reopened JAMES-2806:
---
> Adding bucket capability into BlobStore
> ---
>
> Key: JAMES-2806
> URL: https://issues.apache.org/jira/browse/JAMES-2806
> Project: James Server
> Issue Type: Sub-task
> Components: Blob
>Reporter: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> You should update current BlobStore API to be able to customize the way we
> storeBlob:
> - We want to store a blob in a specified bucket
> {code:java}
> public interface BlobStore {
> Publisher save(BucketName, byte[] data);
> Publisher save(BucketName, InputStream data);
> Publisher readBytes(BucketName, BlobId blobId);
> InputStream read(BucketName, BlobId blobId);
> }
> {code}
> And to implement the feature of deleting buckets exceed retention time, we
> need to have another additional method of deleting bucket:
> {code:java}
> public interface BlobStore {
> Publisher delete(BucketName bucket);
> }
> {code}
> Scope: API change, contract test, memory + object storage implementation -
> cassandra will be done in a later task
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2816) Append messages optimization
[ https://issues.apache.org/jira/browse/JAMES-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2816. - > Append messages optimization > > > Key: JAMES-2816 > URL: https://issues.apache.org/jira/browse/JAMES-2816 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.4.0 > > > We tend to copy the whole message when only meta-data are needed -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2816) Append messages optimization
[ https://issues.apache.org/jira/browse/JAMES-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2816. --- Resolution: Fixed Fix Version/s: 3.4.0 merged > Append messages optimization > > > Key: JAMES-2816 > URL: https://issues.apache.org/jira/browse/JAMES-2816 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.4.0 > > > We tend to copy the whole message when only meta-data are needed -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2817) Various EventBus fixes
[ https://issues.apache.org/jira/browse/JAMES-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2817. --- Resolution: Fixed Fix Version/s: 3.4.0 merged > Various EventBus fixes > -- > > Key: JAMES-2817 > URL: https://issues.apache.org/jira/browse/JAMES-2817 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2817) Various EventBus fixes
[ https://issues.apache.org/jira/browse/JAMES-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2817. - > Various EventBus fixes > -- > > Key: JAMES-2817 > URL: https://issues.apache.org/jira/browse/JAMES-2817 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2773) Add glowroot in the docker images
[ https://issues.apache.org/jira/browse/JAMES-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2773. --- Resolution: Fixed Fix Version/s: 3.4.0 merged > Add glowroot in the docker images > - > > Key: JAMES-2773 > URL: https://issues.apache.org/jira/browse/JAMES-2773 > Project: James Server > Issue Type: Bug >Reporter: Rémi Kowalski >Priority: Major > Fix For: 3.4.0 > > > In order to have instrumentation on the JMAP and IMAP transactions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2806) Adding bucket capability into BlobStore
[
https://issues.apache.org/jira/browse/JAMES-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat closed JAMES-2806.
-
> Adding bucket capability into BlobStore
> ---
>
> Key: JAMES-2806
> URL: https://issues.apache.org/jira/browse/JAMES-2806
> Project: James Server
> Issue Type: Sub-task
> Components: Blob
>Reporter: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> You should update current BlobStore API to be able to customize the way we
> storeBlob:
> - We want to store a blob in a specified bucket
> {code:java}
> public interface BlobStore {
> Publisher save(BucketName, byte[] data);
> Publisher save(BucketName, InputStream data);
> Publisher readBytes(BucketName, BlobId blobId);
> InputStream read(BucketName, BlobId blobId);
> }
> {code}
> And to implement the feature of deleting buckets exceed retention time, we
> need to have another additional method of deleting bucket:
> {code:java}
> public interface BlobStore {
> Publisher delete(BucketName bucket);
> }
> {code}
> Scope: API change, contract test, memory + object storage implementation -
> cassandra will be done in a later task
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2807) DeletedMessageMetadataVault API + contract +memory
[
https://issues.apache.org/jira/browse/JAMES-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat resolved JAMES-2807.
---
Resolution: Fixed
Fix Version/s: 3.4.0
merged
> DeletedMessageMetadataVault API + contract +memory
> --
>
> Key: JAMES-2807
> URL: https://issues.apache.org/jira/browse/JAMES-2807
> Project: James Server
> Issue Type: Sub-task
> Components: deletedMessageVault
>Reporter: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> We need a sub API for storing per Container metadata of Deleted Messages.
> Here is the API:
> {code:java}
> class StorageInformation {
> private final BucketName bucketName;
> private final BlobId blobId;
> }
> class DeletedMessageWithStorageInformation {
> private final DeletedMessage deletedmessage;
> private final StorageInformation storageInformation;
> }
> interface DeletedMessageMetadataVault {
> Publisher store(BucketName, DeletedMessageWithStorageInformation);
> Publisher removeBucket(BucketName);
> Publisher remove(BucketName, User, MessageId);
> Publisher retrieveStorageInformation(User, MessageId);
> Publisher listMessages(BucketName,
> User);
> Publisher listBuckets();
> }
> {code}
> You will provide the API + contract in
> `mailbox/plugin/deleted-messages-vault`.
> You will provide a memory implementation of it in
> `mailbox/plugin/deleted-messages-vault-memory`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2807) DeletedMessageMetadataVault API + contract +memory
[
https://issues.apache.org/jira/browse/JAMES-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat closed JAMES-2807.
-
> DeletedMessageMetadataVault API + contract +memory
> --
>
> Key: JAMES-2807
> URL: https://issues.apache.org/jira/browse/JAMES-2807
> Project: James Server
> Issue Type: Sub-task
> Components: deletedMessageVault
>Reporter: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> We need a sub API for storing per Container metadata of Deleted Messages.
> Here is the API:
> {code:java}
> class StorageInformation {
> private final BucketName bucketName;
> private final BlobId blobId;
> }
> class DeletedMessageWithStorageInformation {
> private final DeletedMessage deletedmessage;
> private final StorageInformation storageInformation;
> }
> interface DeletedMessageMetadataVault {
> Publisher store(BucketName, DeletedMessageWithStorageInformation);
> Publisher removeBucket(BucketName);
> Publisher remove(BucketName, User, MessageId);
> Publisher retrieveStorageInformation(User, MessageId);
> Publisher listMessages(BucketName,
> User);
> Publisher listBuckets();
> }
> {code}
> You will provide the API + contract in
> `mailbox/plugin/deleted-messages-vault`.
> You will provide a memory implementation of it in
> `mailbox/plugin/deleted-messages-vault-memory`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2806) Adding bucket capability into BlobStore
[
https://issues.apache.org/jira/browse/JAMES-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat resolved JAMES-2806.
---
Resolution: Fixed
Fix Version/s: 3.4.0
merged
> Adding bucket capability into BlobStore
> ---
>
> Key: JAMES-2806
> URL: https://issues.apache.org/jira/browse/JAMES-2806
> Project: James Server
> Issue Type: Sub-task
> Components: Blob
>Reporter: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> You should update current BlobStore API to be able to customize the way we
> storeBlob:
> - We want to store a blob in a specified bucket
> {code:java}
> public interface BlobStore {
> Publisher save(BucketName, byte[] data);
> Publisher save(BucketName, InputStream data);
> Publisher readBytes(BucketName, BlobId blobId);
> InputStream read(BucketName, BlobId blobId);
> }
> {code}
> And to implement the feature of deleting buckets exceed retention time, we
> need to have another additional method of deleting bucket:
> {code:java}
> public interface BlobStore {
> Publisher delete(BucketName bucket);
> }
> {code}
> Scope: API change, contract test, memory + object storage implementation -
> cassandra will be done in a later task
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2621) Creating mailbox is not secure
[ https://issues.apache.org/jira/browse/JAMES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2621. - > Creating mailbox is not secure > -- > > Key: JAMES-2621 > URL: https://issues.apache.org/jira/browse/JAMES-2621 > Project: James Server > Issue Type: New Feature > Components: mailbox >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.4.0 > > > Creating a mailbox is not secure at MailboxManager API. > A user can create a mailbox with a MailboxPath linked to another user. > Here is a test proving this: > https://github.com/linagora/james-project/pull/1992 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Reopened] (JAMES-2621) Creating mailbox is not secure
[ https://issues.apache.org/jira/browse/JAMES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat reopened JAMES-2621: --- > Creating mailbox is not secure > -- > > Key: JAMES-2621 > URL: https://issues.apache.org/jira/browse/JAMES-2621 > Project: James Server > Issue Type: New Feature > Components: mailbox >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > > Creating a mailbox is not secure at MailboxManager API. > A user can create a mailbox with a MailboxPath linked to another user. > Here is a test proving this: > https://github.com/linagora/james-project/pull/1992 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2621) Creating mailbox is not secure
[ https://issues.apache.org/jira/browse/JAMES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2621. --- Resolution: Fixed Fix Version/s: 3.4.0 > Creating mailbox is not secure > -- > > Key: JAMES-2621 > URL: https://issues.apache.org/jira/browse/JAMES-2621 > Project: James Server > Issue Type: New Feature > Components: mailbox >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.4.0 > > > Creating a mailbox is not secure at MailboxManager API. > A user can create a mailbox with a MailboxPath linked to another user. > Here is a test proving this: > https://github.com/linagora/james-project/pull/1992 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2621) Creating mailbox is not secure
[ https://issues.apache.org/jira/browse/JAMES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2621. - > Creating mailbox is not secure > -- > > Key: JAMES-2621 > URL: https://issues.apache.org/jira/browse/JAMES-2621 > Project: James Server > Issue Type: New Feature > Components: mailbox >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > > Creating a mailbox is not secure at MailboxManager API. > A user can create a mailbox with a MailboxPath linked to another user. > Here is a test proving this: > https://github.com/linagora/james-project/pull/1992 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2621) Creating mailbox is not secure
[ https://issues.apache.org/jira/browse/JAMES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2621. --- Resolution: Fixed merged > Creating mailbox is not secure > -- > > Key: JAMES-2621 > URL: https://issues.apache.org/jira/browse/JAMES-2621 > Project: James Server > Issue Type: New Feature > Components: mailbox >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > > Creating a mailbox is not secure at MailboxManager API. > A user can create a mailbox with a MailboxPath linked to another user. > Here is a test proving this: > https://github.com/linagora/james-project/pull/1992 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2709) [BlobSharingMechanism] LinShare implementation
[ https://issues.apache.org/jira/browse/JAMES-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2709. --- Resolution: Fixed merged > [BlobSharingMechanism] LinShare implementation > -- > > Key: JAMES-2709 > URL: https://issues.apache.org/jira/browse/JAMES-2709 > Project: James Server > Issue Type: New Feature >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > Implement as a third-party software a BlobSharingMechanism that: > * Upload the file in the sharee workspace > * Shares it to the reciepient > Implement tests about it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2709) [BlobSharingMechanism] LinShare implementation
[ https://issues.apache.org/jira/browse/JAMES-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2709. - > [BlobSharingMechanism] LinShare implementation > -- > > Key: JAMES-2709 > URL: https://issues.apache.org/jira/browse/JAMES-2709 > Project: James Server > Issue Type: New Feature >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > Implement as a third-party software a BlobSharingMechanism that: > * Upload the file in the sharee workspace > * Shares it to the reciepient > Implement tests about it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2714) Document SuperTrash
[ https://issues.apache.org/jira/browse/JAMES-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2714. - > Document SuperTrash > --- > > Key: JAMES-2714 > URL: https://issues.apache.org/jira/browse/JAMES-2714 > Project: James Server > Issue Type: New Feature >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > We need to write a proper documentation that will serve to explain to the > Apache community : > * why we need a vault for email retention > * what are the mechanisms involved in it > * how can we use it > * tutorial on configuration > * detailed documentation page in the mailbox website. > * medium article about this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2714) Document SuperTrash
[ https://issues.apache.org/jira/browse/JAMES-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2714. --- Resolution: Fixed merged > Document SuperTrash > --- > > Key: JAMES-2714 > URL: https://issues.apache.org/jira/browse/JAMES-2714 > Project: James Server > Issue Type: New Feature >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > We need to write a proper documentation that will serve to explain to the > Apache community : > * why we need a vault for email retention > * what are the mechanisms involved in it > * how can we use it > * tutorial on configuration > * detailed documentation page in the mailbox website. > * medium article about this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2713) [Integration Tests] Webadmin delete and purge APIs
[
https://issues.apache.org/jira/browse/JAMES-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat closed JAMES-2713.
-
> [Integration Tests] Webadmin delete and purge APIs
> --
>
> Key: JAMES-2713
> URL: https://issues.apache.org/jira/browse/JAMES-2713
> Project: James Server
> Issue Type: New Feature
>Reporter: Rene Cordier
>Priority: Major
> Fix For: 3.4.0
>
>
> In cassandra and memory in `/server/protocols/jmap-integration-testing`,
> write following tests to delete and purge mails from the supertrash feature.
> Make sure as well to setup correctly guice bindings to prove that this new
> feature integrates well into our system.
> *Delete API*
> {code}
> Given an user with emails present in the vault
> When admin is using delete with the message ID of one of those emails
> Then the email should be deleted from user's vault
> {code}
> {code}
> Given an user with emails present in the vault
> When admin is using delete with the message ID that doesn't exist
> Then no email should be deleted from user's vault
> {code}
> *Purge API*
> {code}
> Given an user with emails present in the vault matching a configured
> retention policy
> When admin is using purge
> Then the emails matching the configured retention policy should be deleted
> from user's vault
> {code}
> {code}
> Given an user with emails present in the vault not matching a configured
> retention policy
> When admin is using purge
> Then no emails should be deleted from user's vault
> {code}
> {code}
> Given an user with no emails present in the vault
> When admin is using purge
> Then nothing should happen
> {code}
> {code}
> Given two users with emails present in their vault matching a configured
> retention policy
> When admin is using purge
> Then the emails matching the configured retention policy should be deleted
> from both users' vault
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2713) [Integration Tests] Webadmin delete and purge APIs
[
https://issues.apache.org/jira/browse/JAMES-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat resolved JAMES-2713.
---
Resolution: Fixed
merged
> [Integration Tests] Webadmin delete and purge APIs
> --
>
> Key: JAMES-2713
> URL: https://issues.apache.org/jira/browse/JAMES-2713
> Project: James Server
> Issue Type: New Feature
>Reporter: Rene Cordier
>Priority: Major
> Fix For: 3.4.0
>
>
> In cassandra and memory in `/server/protocols/jmap-integration-testing`,
> write following tests to delete and purge mails from the supertrash feature.
> Make sure as well to setup correctly guice bindings to prove that this new
> feature integrates well into our system.
> *Delete API*
> {code}
> Given an user with emails present in the vault
> When admin is using delete with the message ID of one of those emails
> Then the email should be deleted from user's vault
> {code}
> {code}
> Given an user with emails present in the vault
> When admin is using delete with the message ID that doesn't exist
> Then no email should be deleted from user's vault
> {code}
> *Purge API*
> {code}
> Given an user with emails present in the vault matching a configured
> retention policy
> When admin is using purge
> Then the emails matching the configured retention policy should be deleted
> from user's vault
> {code}
> {code}
> Given an user with emails present in the vault not matching a configured
> retention policy
> When admin is using purge
> Then no emails should be deleted from user's vault
> {code}
> {code}
> Given an user with no emails present in the vault
> When admin is using purge
> Then nothing should happen
> {code}
> {code}
> Given two users with emails present in their vault matching a configured
> retention policy
> When admin is using purge
> Then the emails matching the configured retention policy should be deleted
> from both users' vault
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2710) [WebAdmin DMRS Route] Purge API
[
https://issues.apache.org/jira/browse/JAMES-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat closed JAMES-2710.
-
> [WebAdmin DMRS Route] Purge API
> ---
>
> Key: JAMES-2710
> URL: https://issues.apache.org/jira/browse/JAMES-2710
> Project: James Server
> Issue Type: New Feature
> Components: webadmin
>Reporter: Rene Cordier
>Priority: Major
> Fix For: 3.4.0
>
>
> *API proposal*
> {code:java}
> POST /deletedMessages?action=purge
> - 200 success
> {"taskId":"1234-5678"}
> {code}
> * Define POST method in DeletedMessageVaultRoutes(#1024 (closed))
> * Using configuration retention to work with purge
> Document that a CRON needs to be configured to call this endpoint in a
> regular basis.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2710) [WebAdmin DMRS Route] Purge API
[
https://issues.apache.org/jira/browse/JAMES-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat resolved JAMES-2710.
---
Resolution: Fixed
merged
> [WebAdmin DMRS Route] Purge API
> ---
>
> Key: JAMES-2710
> URL: https://issues.apache.org/jira/browse/JAMES-2710
> Project: James Server
> Issue Type: New Feature
> Components: webadmin
>Reporter: Rene Cordier
>Priority: Major
> Fix For: 3.4.0
>
>
> *API proposal*
> {code:java}
> POST /deletedMessages?action=purge
> - 200 success
> {"taskId":"1234-5678"}
> {code}
> * Define POST method in DeletedMessageVaultRoutes(#1024 (closed))
> * Using configuration retention to work with purge
> Document that a CRON needs to be configured to call this endpoint in a
> regular basis.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2714) Document SuperTrash
[ https://issues.apache.org/jira/browse/JAMES-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2714. --- Resolution: Fixed merged > Document SuperTrash > --- > > Key: JAMES-2714 > URL: https://issues.apache.org/jira/browse/JAMES-2714 > Project: James Server > Issue Type: New Feature >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > We need to write a proper documentation that will serve to explain to the > Apache community : > * why we need a vault for email retention > * what are the mechanisms involved in it > * how can we use it > * tutorial on configuration > * detailed documentation page in the mailbox website. > * medium article about this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2714) Document SuperTrash
[ https://issues.apache.org/jira/browse/JAMES-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2714. - > Document SuperTrash > --- > > Key: JAMES-2714 > URL: https://issues.apache.org/jira/browse/JAMES-2714 > Project: James Server > Issue Type: New Feature >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > We need to write a proper documentation that will serve to explain to the > Apache community : > * why we need a vault for email retention > * what are the mechanisms involved in it > * how can we use it > * tutorial on configuration > * detailed documentation page in the mailbox website. > * medium article about this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2704) Create Mailet to assign mails to Random users
[ https://issues.apache.org/jira/browse/JAMES-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2704. - > Create Mailet to assign mails to Random users > - > > Key: JAMES-2704 > URL: https://issues.apache.org/jira/browse/JAMES-2704 > Project: James Server > Issue Type: Improvement > Components: Mailet Contributions >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.4.0 > > > In order to populate users mailboxes for stress tests we want to have a > mailet dispatching randomly incoming mails to all users. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2704) Create Mailet to assign mails to Random users
[ https://issues.apache.org/jira/browse/JAMES-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2704. --- Resolution: Fixed Fix Version/s: 3.4.0 merged > Create Mailet to assign mails to Random users > - > > Key: JAMES-2704 > URL: https://issues.apache.org/jira/browse/JAMES-2704 > Project: James Server > Issue Type: Improvement > Components: Mailet Contributions >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.4.0 > > > In order to populate users mailboxes for stress tests we want to have a > mailet dispatching randomly incoming mails to all users. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2732) Fix checkstyle in tests
[ https://issues.apache.org/jira/browse/JAMES-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2732. --- Resolution: Fixed Fix Version/s: 3.4.0 merged > Fix checkstyle in tests > --- > > Key: JAMES-2732 > URL: https://issues.apache.org/jira/browse/JAMES-2732 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.4.0 > > > Running check-style on the whole project shows mainly errors in tests which > produced a lot of noise -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2732) Fix checkstyle in tests
[ https://issues.apache.org/jira/browse/JAMES-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2732. - > Fix checkstyle in tests > --- > > Key: JAMES-2732 > URL: https://issues.apache.org/jira/browse/JAMES-2732 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.4.0 > > > Running check-style on the whole project shows mainly errors in tests which > produced a lot of noise -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2726) Publish In-Memory image on DockerHub
[ https://issues.apache.org/jira/browse/JAMES-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2726. - > Publish In-Memory image on DockerHub > > > Key: JAMES-2726 > URL: https://issues.apache.org/jira/browse/JAMES-2726 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Minor > Fix For: 3.4.0 > > > In order to make James testable in other projects, a good thing is to create > a DockerHub image with an In-Memory setup -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2726) Publish In-Memory image on DockerHub
[ https://issues.apache.org/jira/browse/JAMES-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2726. --- Resolution: Fixed Fix Version/s: 3.4.0 merged > Publish In-Memory image on DockerHub > > > Key: JAMES-2726 > URL: https://issues.apache.org/jira/browse/JAMES-2726 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Minor > Fix For: 3.4.0 > > > In order to make James testable in other projects, a good thing is to create > a DockerHub image with an In-Memory setup -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2725) Remove the length from blob API
Antoine Duprat created JAMES-2725: - Summary: Remove the length from blob API Key: JAMES-2725 URL: https://issues.apache.org/jira/browse/JAMES-2725 Project: James Server Issue Type: New Feature Components: Blob Reporter: Antoine Duprat Remove the length from blob API. * length is necessary only for one implementation (S3) * this implementation has probably workarounds to not use length (multipart upload) * in the worst case this implementation should handle the computation of the length (through a file backed i/o stream for example) This would also allow to have a proper server-encrypted implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2724) Jenkinsfile for stress testing
[ https://issues.apache.org/jira/browse/JAMES-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807743#comment-16807743 ] Antoine Duprat commented on JAMES-2724: --- this pull request contributes to this issue: https://github.com/linagora/james-project/pull/2285 > Jenkinsfile for stress testing > -- > > Key: JAMES-2724 > URL: https://issues.apache.org/jira/browse/JAMES-2724 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > > We need to introduce a Jenkinsfile which will be used to play some stress > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2724) Jenkinsfile for stress testing
Antoine Duprat created JAMES-2724: - Summary: Jenkinsfile for stress testing Key: JAMES-2724 URL: https://issues.apache.org/jira/browse/JAMES-2724 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat We need to introduce a Jenkinsfile which will be used to play some stress tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2699) Deprecation without documentation
[ https://issues.apache.org/jira/browse/JAMES-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2699. - > Deprecation without documentation > - > > Key: JAMES-2699 > URL: https://issues.apache.org/jira/browse/JAMES-2699 > Project: James Server > Issue Type: Bug > Components: Matchers/Mailets (bundled) >Affects Versions: 3.4.0 >Reporter: Amichai Rothman >Priority: Major > Fix For: 3.3.1 > > > In the current Mailet API there are many deprecated classes and methods > marked with the @Deprecated annotation and some also with the @deprecated > javadoc tag. However, very few of these have any related documentation on > what to use instead, or at least why it is deprecated if there is no > alternative. As it is, someone using or implementing the API has no idea what > the migration path should be to avoid using these deprecated APIs which may > disappear in the future. > Please document all deprecations, most importantly with what is the > recommended way to migrate away from them. > This may be true for other modules as well, but certainly is in this central > API. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2699) Deprecation without documentation
[ https://issues.apache.org/jira/browse/JAMES-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2699. --- Resolution: Fixed Fix Version/s: 3.3.1 > Deprecation without documentation > - > > Key: JAMES-2699 > URL: https://issues.apache.org/jira/browse/JAMES-2699 > Project: James Server > Issue Type: Bug > Components: Matchers/Mailets (bundled) >Affects Versions: 3.4.0 >Reporter: Amichai Rothman >Priority: Major > Fix For: 3.3.1 > > > In the current Mailet API there are many deprecated classes and methods > marked with the @Deprecated annotation and some also with the @deprecated > javadoc tag. However, very few of these have any related documentation on > what to use instead, or at least why it is deprecated if there is no > alternative. As it is, someone using or implementing the API has no idea what > the migration path should be to avoid using these deprecated APIs which may > disappear in the future. > Please document all deprecations, most importantly with what is the > recommended way to migrate away from them. > This may be true for other modules as well, but certainly is in this central > API. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2671) Implement BlobStore for AWS S3
[ https://issues.apache.org/jira/browse/JAMES-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2671. --- Resolution: Fixed Fix Version/s: 3.4.0 > Implement BlobStore for AWS S3 > -- > > Key: JAMES-2671 > URL: https://issues.apache.org/jira/browse/JAMES-2671 > Project: James Server > Issue Type: New Feature > Components: Blob >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.4.0 > > > Here BlobStore interface have to be implemented using jcloud. > A Configuration class maybe be created, but we do not expect it to be > finalized here. > Add Docker's Rules/extension/etc. and duplicate Swift-related tests for AWS > S3. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2671) Implement BlobStore for AWS S3
[ https://issues.apache.org/jira/browse/JAMES-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2671. - > Implement BlobStore for AWS S3 > -- > > Key: JAMES-2671 > URL: https://issues.apache.org/jira/browse/JAMES-2671 > Project: James Server > Issue Type: New Feature > Components: Blob >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.4.0 > > > Here BlobStore interface have to be implemented using jcloud. > A Configuration class maybe be created, but we do not expect it to be > finalized here. > Add Docker's Rules/extension/etc. and duplicate Swift-related tests for AWS > S3. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2692) Blob encryption with InputStream
Antoine Duprat created JAMES-2692: - Summary: Blob encryption with InputStream Key: JAMES-2692 URL: https://issues.apache.org/jira/browse/JAMES-2692 Project: James Server Issue Type: New Feature Components: Blob Reporter: Antoine Duprat Due to the support of the AWS S3 implementation, we had to modify the API in order to give the length of the InputStream. While encrypting the InputStream, we are not able to retrieve it's length with a smart solution. The goal of this issue is to handle encryption with InputStream. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2671) Implement BlobStore for AWS S3
[ https://issues.apache.org/jira/browse/JAMES-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791525#comment-16791525 ] Antoine Duprat commented on JAMES-2671: --- [https://github.com/linagora/james-project/pull/2215] contributed this > Implement BlobStore for AWS S3 > -- > > Key: JAMES-2671 > URL: https://issues.apache.org/jira/browse/JAMES-2671 > Project: James Server > Issue Type: New Feature > Components: Blob >Reporter: Antoine Duprat >Priority: Major > > Here BlobStore interface have to be implemented using jcloud. > A Configuration class maybe be created, but we do not expect it to be > finalized here. > Add Docker's Rules/extension/etc. and duplicate Swift-related tests for AWS > S3. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2671) Implement BlobStore for AWS S3
Antoine Duprat created JAMES-2671: - Summary: Implement BlobStore for AWS S3 Key: JAMES-2671 URL: https://issues.apache.org/jira/browse/JAMES-2671 Project: James Server Issue Type: New Feature Components: Blob Reporter: Antoine Duprat Here BlobStore interface have to be implemented using jcloud. A Configuration class maybe be created, but we do not expect it to be finalized here. Add Docker's Rules/extension/etc. and duplicate Swift-related tests for AWS S3. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2669) Add AWS S3 support for BlobStore
[ https://issues.apache.org/jira/browse/JAMES-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777886#comment-16777886 ] Antoine Duprat commented on JAMES-2669: --- Pull request: https://github.com/linagora/james-project/pull/2198 > Add AWS S3 support for BlobStore > > > Key: JAMES-2669 > URL: https://issues.apache.org/jira/browse/JAMES-2669 > Project: James Server > Issue Type: Bug > Components: Blob >Reporter: Gautier DI FOLCO >Priority: Minor > > Add the ability to use AWS S3 as BlobStore. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2620) Integration test script should install artifacts
[ https://issues.apache.org/jira/browse/JAMES-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2620. --- Resolution: Fixed merged > Integration test script should install artifacts > > > Key: JAMES-2620 > URL: https://issues.apache.org/jira/browse/JAMES-2620 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > The first _mvn_ call, which is used to build dependencies, should install > built artifacts; > else the second call, which is used to run the test, will download the James > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2620) Integration test script should install artifacts
[ https://issues.apache.org/jira/browse/JAMES-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2620. - > Integration test script should install artifacts > > > Key: JAMES-2620 > URL: https://issues.apache.org/jira/browse/JAMES-2620 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > The first _mvn_ call, which is used to build dependencies, should install > built artifacts; > else the second call, which is used to run the test, will download the James > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2610) Enhance MailetPipelineLogging
[ https://issues.apache.org/jira/browse/JAMES-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2610. - > Enhance MailetPipelineLogging > - > > Key: JAMES-2610 > URL: https://issues.apache.org/jira/browse/JAMES-2610 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > This logger is really helpful when debugging a pipeline mailet. > However, some mailets do not override the `getMailetInfo` method, and the > generic implementation of it is returning an empty string. > This means we are blind on some mailet and calls. > To get rid of this, we can log the mailing list in an empty mailet info. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2610) Enhance MailetPipelineLogging
[ https://issues.apache.org/jira/browse/JAMES-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2610. --- Resolution: Fixed merged > Enhance MailetPipelineLogging > - > > Key: JAMES-2610 > URL: https://issues.apache.org/jira/browse/JAMES-2610 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > This logger is really helpful when debugging a pipeline mailet. > However, some mailets do not override the `getMailetInfo` method, and the > generic implementation of it is returning an empty string. > This means we are blind on some mailet and calls. > To get rid of this, we can log the mailing list in an empty mailet info. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2620) Integration test script should install artifacts
[ https://issues.apache.org/jira/browse/JAMES-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-2620: -- Fix Version/s: 3.3.0 > Integration test script should install artifacts > > > Key: JAMES-2620 > URL: https://issues.apache.org/jira/browse/JAMES-2620 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > The first _mvn_ call, which is used to build dependencies, should install > built artifacts; > else the second call, which is used to run the test, will download the James > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2610) Enhance MailetPipelineLogging
[ https://issues.apache.org/jira/browse/JAMES-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-2610: -- Fix Version/s: 3.3.0 > Enhance MailetPipelineLogging > - > > Key: JAMES-2610 > URL: https://issues.apache.org/jira/browse/JAMES-2610 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > This logger is really helpful when debugging a pipeline mailet. > However, some mailets do not override the `getMailetInfo` method, and the > generic implementation of it is returning an empty string. > This means we are blind on some mailet and calls. > To get rid of this, we can log the mailing list in an empty mailet info. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2622) James dockerfile is not production ready
Antoine Duprat created JAMES-2622: - Summary: James dockerfile is not production ready Key: JAMES-2622 URL: https://issues.apache.org/jira/browse/JAMES-2622 Project: James Server Issue Type: New Feature Components: docker Affects Versions: 3.3.0 Reporter: Antoine Duprat In order to be production ready, we should modify our dockerfiles in order to: * depend on a JRE instead of a JDK * add an environment variable in order to be able to configuration JVM options -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2621) Creating mailbox is not secure
Antoine Duprat created JAMES-2621: - Summary: Creating mailbox is not secure Key: JAMES-2621 URL: https://issues.apache.org/jira/browse/JAMES-2621 Project: James Server Issue Type: New Feature Components: mailbox Affects Versions: 3.3.0 Reporter: Antoine Duprat Creating a mailbox is not secure at MailboxManager API. A user can create a mailbox with a MailboxPath linked to another user. Here is a test proving this: https://github.com/linagora/james-project/pull/1992 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2620) Integration test script should install artifacts
Antoine Duprat created JAMES-2620: - Summary: Integration test script should install artifacts Key: JAMES-2620 URL: https://issues.apache.org/jira/browse/JAMES-2620 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat The first _mvn_ call, which is used to build dependencies, should install built artifacts; else the second call, which is used to run the test, will download the James artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2612) Move & copy batch sizes are not loaded from configuration
[ https://issues.apache.org/jira/browse/JAMES-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2612. --- Resolution: Fixed Fix Version/s: 3.3.0 merged > Move & copy batch sizes are not loaded from configuration > - > > Key: JAMES-2612 > URL: https://issues.apache.org/jira/browse/JAMES-2612 > Project: James Server > Issue Type: New Feature > Components: configuration, mailbox >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > Changing the values of move & copy batch sizes in the _batchsizes.properties_ > configuration file has no impact. > They are both always equals to the default value (200). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2612) Move & copy batch sizes are not loaded from configuration
[ https://issues.apache.org/jira/browse/JAMES-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2612. - > Move & copy batch sizes are not loaded from configuration > - > > Key: JAMES-2612 > URL: https://issues.apache.org/jira/browse/JAMES-2612 > Project: James Server > Issue Type: New Feature > Components: configuration, mailbox >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.3.0 > > > Changing the values of move & copy batch sizes in the _batchsizes.properties_ > configuration file has no impact. > They are both always equals to the default value (200). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2612) Move & copy batch sizes are not loaded from configuration
Antoine Duprat created JAMES-2612: - Summary: Move & copy batch sizes are not loaded from configuration Key: JAMES-2612 URL: https://issues.apache.org/jira/browse/JAMES-2612 Project: James Server Issue Type: New Feature Components: configuration, mailbox Reporter: Antoine Duprat Changing the values of move & copy batch sizes in the _batchsizes.properties_ configuration file has no impact. They are both always equals to the default value (200). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2610) Enhance MailetPipelineLogging
Antoine Duprat created JAMES-2610: - Summary: Enhance MailetPipelineLogging Key: JAMES-2610 URL: https://issues.apache.org/jira/browse/JAMES-2610 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat This logger is really helpful when debugging a pipeline mailet. However, some mailets do not override the `getMailetInfo` method, and the generic implementation of it is returning an empty string. This means we are blind on some mailet and calls. To get rid of this, we can log the mailing list in an empty mailet info. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2592) ElasticSearch cluster name should be in the configuration
[ https://issues.apache.org/jira/browse/JAMES-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-2592: -- Affects Version/s: 3.3.0 Component/s: elasticsearch > ElasticSearch cluster name should be in the configuration > - > > Key: JAMES-2592 > URL: https://issues.apache.org/jira/browse/JAMES-2592 > Project: James Server > Issue Type: New Feature > Components: elasticsearch >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > > The ElasticSearch client needs a cluster name in order to connect to a > cluster other than the default one. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2592) ElasticSearch cluster name should be in the configuration
Antoine Duprat created JAMES-2592: - Summary: ElasticSearch cluster name should be in the configuration Key: JAMES-2592 URL: https://issues.apache.org/jira/browse/JAMES-2592 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat The ElasticSearch client needs a cluster name in order to connect to a cluster other than the default one. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2590) Change default ElasticSearch shards & replica values
[ https://issues.apache.org/jira/browse/JAMES-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-2590: -- Affects Version/s: 3.3.0 Component/s: elasticsearch > Change default ElasticSearch shards & replica values > > > Key: JAMES-2590 > URL: https://issues.apache.org/jira/browse/JAMES-2590 > Project: James Server > Issue Type: New Feature > Components: elasticsearch >Affects Versions: 3.3.0 >Reporter: Antoine Duprat >Priority: Major > > The default values of those parameters should match the recommended values: > [https://www.elastic.co/guide/en/elasticsearch/guide/current/_index_settings.html] > We also have to ensure that those configuration entries are really used while > creating the indices. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2590) Change default ElasticSearch shards & replica values
Antoine Duprat created JAMES-2590: - Summary: Change default ElasticSearch shards & replica values Key: JAMES-2590 URL: https://issues.apache.org/jira/browse/JAMES-2590 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat The default values of those parameters should match the recommended values: [https://www.elastic.co/guide/en/elasticsearch/guide/current/_index_settings.html] We also have to ensure that those configuration entries are really used while creating the indices. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2587) Package RabbitMQ
[
https://issues.apache.org/jira/browse/JAMES-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat closed JAMES-2587.
-
> Package RabbitMQ
>
>
> Key: JAMES-2587
> URL: https://issues.apache.org/jira/browse/JAMES-2587
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.3.0
>
>
> {code:java}
> We need to enforce rabbitMQ in the following places
> Docker compose
> Website doc
> ReadMe
> Dependencies in packages (optional, Rabbit may be anywhere)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2587) Package RabbitMQ
[
https://issues.apache.org/jira/browse/JAMES-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat resolved JAMES-2587.
---
Resolution: Fixed
Fix Version/s: 3.3.0
merged
> Package RabbitMQ
>
>
> Key: JAMES-2587
> URL: https://issues.apache.org/jira/browse/JAMES-2587
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.3.0
>
>
> {code:java}
> We need to enforce rabbitMQ in the following places
> Docker compose
> Website doc
> ReadMe
> Dependencies in packages (optional, Rabbit may be anywhere)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2581) Configurable ContentType blacklist for Tika
[ https://issues.apache.org/jira/browse/JAMES-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2581. - > Configurable ContentType blacklist for Tika > --- > > Key: JAMES-2581 > URL: https://issues.apache.org/jira/browse/JAMES-2581 > Project: James Server > Issue Type: Improvement >Reporter: Dat Pham >Priority: Major > > Enhanced production logging upon Tika failing call highlight the fact that > our installation of Tika **can not** handle some kinds of attachments. > Here is a log example: > ``` > org.apache.http.client.HttpResponseException: Unsupported Media Type > at > org.apache.http.impl.client.AbstractResponseHandler.handleResponse(AbstractResponseHandler.java:70) > at org.apache.http.client.fluent.Response.handleResponse(Response.java:90) > at org.apache.http.client.fluent.Response.returnContent(Response.java:97) > at > org.apache.james.mailbox.tika.TikaHttpClientImpl.recursiveMetaDataAsJson(TikaHttpClientImpl.java:62) > at > org.apache.james.mailbox.tika.TikaTextExtractor.performContentExtraction(TikaTextExtractor.java:86) > at > org.apache.james.mailbox.tika.TikaTextExtractor.lambda$extractContent$0(TikaTextExtractor.java:81) > ``` > (131 matches in the last 2 days) > Here is a list if Content types we recurringly fail on: > - application/ics > - application/zip > - application/pgp-signature > - image/jpg > - image/jpeg > - image/png > - message/delivery-status > As an admin, I should be able to specify in `tika.properties` file a coma > separated list of Content type to blacklist. > Benefits: > - Avoid known-to-be-failing Tika calls - reduce log output > - Avoid transmitting potentially big payload over the network for nothing - > performance -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2581) Configurable ContentType blacklist for Tika
[ https://issues.apache.org/jira/browse/JAMES-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2581. --- Resolution: Fixed merged > Configurable ContentType blacklist for Tika > --- > > Key: JAMES-2581 > URL: https://issues.apache.org/jira/browse/JAMES-2581 > Project: James Server > Issue Type: Improvement >Reporter: Dat Pham >Priority: Major > > Enhanced production logging upon Tika failing call highlight the fact that > our installation of Tika **can not** handle some kinds of attachments. > Here is a log example: > ``` > org.apache.http.client.HttpResponseException: Unsupported Media Type > at > org.apache.http.impl.client.AbstractResponseHandler.handleResponse(AbstractResponseHandler.java:70) > at org.apache.http.client.fluent.Response.handleResponse(Response.java:90) > at org.apache.http.client.fluent.Response.returnContent(Response.java:97) > at > org.apache.james.mailbox.tika.TikaHttpClientImpl.recursiveMetaDataAsJson(TikaHttpClientImpl.java:62) > at > org.apache.james.mailbox.tika.TikaTextExtractor.performContentExtraction(TikaTextExtractor.java:86) > at > org.apache.james.mailbox.tika.TikaTextExtractor.lambda$extractContent$0(TikaTextExtractor.java:81) > ``` > (131 matches in the last 2 days) > Here is a list if Content types we recurringly fail on: > - application/ics > - application/zip > - application/pgp-signature > - image/jpg > - image/jpeg > - image/png > - message/delivery-status > As an admin, I should be able to specify in `tika.properties` file a coma > separated list of Content type to blacklist. > Benefits: > - Avoid known-to-be-failing Tika calls - reduce log output > - Avoid transmitting potentially big payload over the network for nothing - > performance -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2584) Define the subset of our tests which is specific to Cassandra
[ https://issues.apache.org/jira/browse/JAMES-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2584. - > Define the subset of our tests which is specific to Cassandra > - > > Key: JAMES-2584 > URL: https://issues.apache.org/jira/browse/JAMES-2584 > Project: James Server > Issue Type: New Feature > Components: integrationTests >Reporter: Antoine Duprat >Priority: Major > > This issue is linked to #JAMES-2580. > Here the goal is to isolate Cassandra releated integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2584) Define the subset of our tests which is specific to Cassandra
[ https://issues.apache.org/jira/browse/JAMES-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2584. --- Resolution: Fixed merged > Define the subset of our tests which is specific to Cassandra > - > > Key: JAMES-2584 > URL: https://issues.apache.org/jira/browse/JAMES-2584 > Project: James Server > Issue Type: New Feature > Components: integrationTests >Reporter: Antoine Duprat >Priority: Major > > This issue is linked to #JAMES-2580. > Here the goal is to isolate Cassandra releated integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2578) MQs should not rely on Serializable
[ https://issues.apache.org/jira/browse/JAMES-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681008#comment-16681008 ] Antoine Duprat commented on JAMES-2578: --- [https://github.com/linagora/james-project/pull/1898] JAMES-2578 Minimal set of changes to reduce warnings due to new Mail API > MQs should not rely on Serializable > --- > > Key: JAMES-2578 > URL: https://issues.apache.org/jira/browse/JAMES-2578 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Major > > Mail interface allows people to insert any Serializable object as an > attribute. > For now, we then relied on java serialization when putting Mail object into a > MQ. > Now that we try to write a new MailQueue on top of RabbitMQ, it makes sense > to try to avoid this use of Serializable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2588) Remove JCR and HBase
[ https://issues.apache.org/jira/browse/JAMES-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2588. --- Resolution: Fixed merged > Remove JCR and HBase > > > Key: JAMES-2588 > URL: https://issues.apache.org/jira/browse/JAMES-2588 > Project: James Server > Issue Type: New Feature > Components: hbase >Affects Versions: 3.2.0 >Reporter: Raphaël Ouazana >Priority: Major > Fix For: 3.3.0 > > > JCR and HBase have been deprecated in last version, see > https://issues.apache.org/jira/browse/JAMES-2571 > > This issue is about to track the removal of these backends. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2588) Remove JCR and HBase
[ https://issues.apache.org/jira/browse/JAMES-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2588. - > Remove JCR and HBase > > > Key: JAMES-2588 > URL: https://issues.apache.org/jira/browse/JAMES-2588 > Project: James Server > Issue Type: New Feature > Components: hbase >Affects Versions: 3.2.0 >Reporter: Raphaël Ouazana >Priority: Major > Fix For: 3.3.0 > > > JCR and HBase have been deprecated in last version, see > https://issues.apache.org/jira/browse/JAMES-2571 > > This issue is about to track the removal of these backends. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2583) [ObjectStore] New Composing ObjectStore ontop of Swift and Cassandra
[ https://issues.apache.org/jira/browse/JAMES-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2583. - > [ObjectStore] New Composing ObjectStore ontop of Swift and Cassandra > > > Key: JAMES-2583 > URL: https://issues.apache.org/jira/browse/JAMES-2583 > Project: James Server > Issue Type: Improvement >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.3.0 > > > Why we need it? > In our production, we're using cassandra blobstore, regards to the purpose of > switching to swift blobstore, we need a kind of new BlobStore which writes > new blobs to swift, read new blobs from swift, read old blobs from cassandra. > Proposal name: JoiningObjectStore > > Definition of Done > 1. new JoiningObjectStore implements BlobStore > 2. JoiningObjectStore should compose primary BlobStore and secondary > BlobStore. > when reading from JoiningObjectStore, read from the primary BlobStore, if not > exist, fallback to the secondary blobstore. > similar to write. > 3. test it -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2583) [ObjectStore] New Composing ObjectStore ontop of Swift and Cassandra
[ https://issues.apache.org/jira/browse/JAMES-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2583. --- Resolution: Fixed Fix Version/s: 3.3.0 merged > [ObjectStore] New Composing ObjectStore ontop of Swift and Cassandra > > > Key: JAMES-2583 > URL: https://issues.apache.org/jira/browse/JAMES-2583 > Project: James Server > Issue Type: Improvement >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.3.0 > > > Why we need it? > In our production, we're using cassandra blobstore, regards to the purpose of > switching to swift blobstore, we need a kind of new BlobStore which writes > new blobs to swift, read new blobs from swift, read old blobs from cassandra. > Proposal name: JoiningObjectStore > > Definition of Done > 1. new JoiningObjectStore implements BlobStore > 2. JoiningObjectStore should compose primary BlobStore and secondary > BlobStore. > when reading from JoiningObjectStore, read from the primary BlobStore, if not > exist, fallback to the secondary blobstore. > similar to write. > 3. test it -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2580) Define the subset of our tests that needs to be run on every product
[ https://issues.apache.org/jira/browse/JAMES-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2580. - > Define the subset of our tests that needs to be run on every product > > > Key: JAMES-2580 > URL: https://issues.apache.org/jira/browse/JAMES-2580 > Project: James Server > Issue Type: Improvement > Components: Blob >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.3.0 > > > You can start by looking at Cassandra tests, btw only JMAP test should be > concerned. > use junit4 categories / junit 5 tags / cucumber tags to annotate these tests > this task must be done in pair programming -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2580) Define the subset of our tests that needs to be run on every product
[ https://issues.apache.org/jira/browse/JAMES-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2580. --- Resolution: Fixed Fix Version/s: 3.3.0 merged > Define the subset of our tests that needs to be run on every product > > > Key: JAMES-2580 > URL: https://issues.apache.org/jira/browse/JAMES-2580 > Project: James Server > Issue Type: Improvement > Components: Blob >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.3.0 > > > You can start by looking at Cassandra tests, btw only JMAP test should be > concerned. > use junit4 categories / junit 5 tags / cucumber tags to annotate these tests > this task must be done in pair programming -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2563) Additional guice HealthChecks for core and optional components
[ https://issues.apache.org/jira/browse/JAMES-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677031#comment-16677031 ] Antoine Duprat commented on JAMES-2563: --- [https://github.com/linagora/james-project/pull/1829] This contribution proposes JPA healthckeck is merged > Additional guice HealthChecks for core and optional components > -- > > Key: JAMES-2563 > URL: https://issues.apache.org/jira/browse/JAMES-2563 > Project: James Server > Issue Type: New Feature > Components: guice >Reporter: Tellier Benoit >Priority: Major > Labels: feature, newbie > > We recently introduced heathChecks, allowing to test the health of a > component. > Results are aggregated and exposed over WebAdmin. > As of today, only 2 health checks are implemented: Guice (stop/start) and > RabbitMQ > We would need health checks for other components, including: > Critical services (if they are failing the service is *unhealthy*) > - Cassandra > - ElasticSearch > - JPA > Optional services (if they are failing, the service is *degraded*) > - Tika > - SpamAssassin > In order to test these services, we need to execute some sample requests. > We would also need to bind these health-checks in guice products where > appropriate. > Please open a separate pull request per health check... > We do stay at your full disposal on Gitter to answer related questions > (https://gitter.im/apache/james-project) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2582) [ObjectStore] New Configurations for choosing BlobStore impl
[ https://issues.apache.org/jira/browse/JAMES-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2582. --- Resolution: Fixed Fix Version/s: 3.2.0 merged > [ObjectStore] New Configurations for choosing BlobStore impl > > > Key: JAMES-2582 > URL: https://issues.apache.org/jira/browse/JAMES-2582 > Project: James Server > Issue Type: Improvement >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.2.0 > > > Why we need it? > At the moment, we are using cassandra blobstore as the default in production. > There are new swift, and new `JoiningBlobStore` (#800) could be used to store > blobs. We need to specify a new configuration file to define which type of > blobstore we want to use. > Definition of Done: > - Create new `.propterties` file. > - Create new POJO for that configuration file, likely > `ObjectStoreConfiguration`. > - Create method to publish that POJO to guice, this should be implemented in > `BlobStoreAPIModule` > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2582) [ObjectStore] New Configurations for choosing BlobStore impl
[ https://issues.apache.org/jira/browse/JAMES-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2582. - > [ObjectStore] New Configurations for choosing BlobStore impl > > > Key: JAMES-2582 > URL: https://issues.apache.org/jira/browse/JAMES-2582 > Project: James Server > Issue Type: Improvement >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.2.0 > > > Why we need it? > At the moment, we are using cassandra blobstore as the default in production. > There are new swift, and new `JoiningBlobStore` (#800) could be used to store > blobs. We need to specify a new configuration file to define which type of > blobstore we want to use. > Definition of Done: > - Create new `.propterties` file. > - Create new POJO for that configuration file, likely > `ObjectStoreConfiguration`. > - Create method to publish that POJO to guice, this should be implemented in > `BlobStoreAPIModule` > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (MPT-43) Add a AWAIT command
[ https://issues.apache.org/jira/browse/MPT-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved MPT-43. --- Resolution: Fixed merged > Add a AWAIT command > --- > > Key: MPT-43 > URL: https://issues.apache.org/jira/browse/MPT-43 > Project: James MPT > Issue Type: New Feature > Components: Main >Reporter: Tellier Benoit >Priority: Major > > Some Host systems might need to wait a bit to make changes available for > search. > Currently, we use a fixed wait strategy that leads to either: > - Lost time waiting for too long > - Or build instability if we did not wait for too long > This strategy a flawed and we should allow using more clever MPT command > I propose an AWAIT command allowing host systems to implement the most > suitable await logic to their needs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MPT-43) Add a AWAIT command
[ https://issues.apache.org/jira/browse/MPT-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed MPT-43. - > Add a AWAIT command > --- > > Key: MPT-43 > URL: https://issues.apache.org/jira/browse/MPT-43 > Project: James MPT > Issue Type: New Feature > Components: Main >Reporter: Tellier Benoit >Priority: Major > > Some Host systems might need to wait a bit to make changes available for > search. > Currently, we use a fixed wait strategy that leads to either: > - Lost time waiting for too long > - Or build instability if we did not wait for too long > This strategy a flawed and we should allow using more clever MPT command > I propose an AWAIT command allowing host systems to implement the most > suitable await logic to their needs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2584) Define the subset of our tests which is specific to Cassandra
Antoine Duprat created JAMES-2584: - Summary: Define the subset of our tests which is specific to Cassandra Key: JAMES-2584 URL: https://issues.apache.org/jira/browse/JAMES-2584 Project: James Server Issue Type: New Feature Components: integrationTests Reporter: Antoine Duprat This issue is linked to #JAMES-2580. Here the goal is to isolate Cassandra releated integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2551) Bind RabbitMQ MailQueueFactory implementation
[ https://issues.apache.org/jira/browse/JAMES-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2551. - > Bind RabbitMQ MailQueueFactory implementation > - > > Key: JAMES-2551 > URL: https://issues.apache.org/jira/browse/JAMES-2551 > Project: James Server > Issue Type: Improvement > Components: Queue >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.2.0 > > > The Cassandra product should use the RabbitMQ implementation of > MailQueueFactory (also the ldap-Cassandra product). > The implementation binding is actually done in james-server-guice-common > (ActiveMQQueueModule class), we should extract this binding to its own > project. > We should pass all integration test on top of RabbitMQ. we may use > rabbitmqadmin in docker for that: > > https://hub.docker.com/r/activatedgeek/rabbitmqadmin/ > and a command like this one: (we will have to provide RABBIT_HOST & > RABBIT_PORT) > $ docker run --rm activatedgeek/rabbitmqadmin:latest purge queue > name=name_of_the_queue_to_be_purged > Docker concerns: how to avoid spawning a Rabbit per test? (how to blow up > data? Use namespaces?) Auto discover to disable? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2551) Bind RabbitMQ MailQueueFactory implementation
[ https://issues.apache.org/jira/browse/JAMES-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2551. --- Resolution: Fixed Fix Version/s: 3.2.0 merged > Bind RabbitMQ MailQueueFactory implementation > - > > Key: JAMES-2551 > URL: https://issues.apache.org/jira/browse/JAMES-2551 > Project: James Server > Issue Type: Improvement > Components: Queue >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.2.0 > > > The Cassandra product should use the RabbitMQ implementation of > MailQueueFactory (also the ldap-Cassandra product). > The implementation binding is actually done in james-server-guice-common > (ActiveMQQueueModule class), we should extract this binding to its own > project. > We should pass all integration test on top of RabbitMQ. we may use > rabbitmqadmin in docker for that: > > https://hub.docker.com/r/activatedgeek/rabbitmqadmin/ > and a command like this one: (we will have to provide RABBIT_HOST & > RABBIT_PORT) > $ docker run --rm activatedgeek/rabbitmqadmin:latest purge queue > name=name_of_the_queue_to_be_purged > Docker concerns: how to avoid spawning a Rabbit per test? (how to blow up > data? Use namespaces?) Auto discover to disable? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2571) Deprecate HBase
[ https://issues.apache.org/jira/browse/JAMES-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668652#comment-16668652 ] Antoine Duprat commented on JAMES-2571: --- The same way, this issue will also deprecate JCR. > Deprecate HBase > --- > > Key: JAMES-2571 > URL: https://issues.apache.org/jira/browse/JAMES-2571 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > > Deprecate HBase, as: > * this implementation needs upgrade of dependencies > * lot of features are not implemented > * is experimental > and sadly, we don't have enough power to maintain it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2573) Error while building site
Antoine Duprat created JAMES-2573:
-
Summary: Error while building site
Key: JAMES-2573
URL: https://issues.apache.org/jira/browse/JAMES-2573
Project: James Server
Issue Type: New Feature
Components: site
Reporter: Antoine Duprat
Building the site with the docker tool is failing:
{code:java}
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
(default) on project apache-mailet-icalendar: Too many files with unapproved
license: 1 See RAT report in:
/home/aduprat/work/james-project/mailet/icalendar/target/rat.txt -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2572) Build fails on test-ja
[ https://issues.apache.org/jira/browse/JAMES-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-2572: -- Description: The build fails sometimes on test-jars dependencies. https://issues.apache.org/jira/browse/MJAR-138 was:The build fails sometimes on test-jars dependencies. > Build fails on test-ja > -- > > Key: JAMES-2572 > URL: https://issues.apache.org/jira/browse/JAMES-2572 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > > The build fails sometimes on test-jars dependencies. > https://issues.apache.org/jira/browse/MJAR-138 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2572) Build fails on test-ja
Antoine Duprat created JAMES-2572: - Summary: Build fails on test-ja Key: JAMES-2572 URL: https://issues.apache.org/jira/browse/JAMES-2572 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat The build fails sometimes on test-jars dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2571) Deprecate HBase
[ https://issues.apache.org/jira/browse/JAMES-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat updated JAMES-2571: -- Description: Deprecate HBase, as: * this implementation needs upgrade of dependencies * lot of features are not implemented * is experimental and sadly, we don't have enough power to maintain it. was:Deprecate HBase > Deprecate HBase > --- > > Key: JAMES-2571 > URL: https://issues.apache.org/jira/browse/JAMES-2571 > Project: James Server > Issue Type: New Feature >Reporter: Antoine Duprat >Priority: Major > > Deprecate HBase, as: > * this implementation needs upgrade of dependencies > * lot of features are not implemented > * is experimental > and sadly, we don't have enough power to maintain it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2571) Deprecate HBase
Antoine Duprat created JAMES-2571: - Summary: Deprecate HBase Key: JAMES-2571 URL: https://issues.apache.org/jira/browse/JAMES-2571 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat Deprecate HBase -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2559) Branch merge should be on a specific original branch
Antoine Duprat created JAMES-2559: - Summary: Branch merge should be on a specific original branch Key: JAMES-2559 URL: https://issues.apache.org/jira/browse/JAMES-2559 Project: James Server Issue Type: New Feature Components: docker Reporter: Antoine Duprat Actually, the branch merging tool is merging one branch into `master`. In order to be more flexible, we have to introduce a new parameter and merge the branch into the given original branch. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2554) Coherence issues between mail repository list and mails
Antoine Duprat created JAMES-2554: - Summary: Coherence issues between mail repository list and mails Key: JAMES-2554 URL: https://issues.apache.org/jira/browse/JAMES-2554 Project: James Server Issue Type: New Feature Components: cassandra, MailStore MailRepository Reporter: Antoine Duprat When getting the list of mails from a repository, some of them does not exist. I don't know what happened with them, but GETting them fails with not found. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2552) Define the policy on mail address matching
[
https://issues.apache.org/jira/browse/JAMES-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat updated JAMES-2552:
--
Description:
The mail address defined in this RFC:
[https://tools.ietf.org/html/rfc5321#section-2.4] is leading to some
interpretation on the case sensitive of user part.
Case insensitiveness of domains is already embeded as part of {{Domain}} object
which MailAddress relies on.
Tests needs to be added in MailAddress tests:
{code:java}
a...@d.com == a...@d.com a...@d.com != a...@d.com {code}
{{ }}
But this commit should be dropped.
(BTW equals already do ignore case assertions...)
{code:java}
@Override
public final boolean equals(Object obj) {
if (obj == null) {
return false;
} else if (obj instanceof String) {
String theString = (String) obj;
return toString().equalsIgnoreCase(theString);
} else if (obj instanceof MailAddress) {
MailAddress addr = (MailAddress) obj;
if (isNullSender() && addr.isNullSender()) {
return true;
}
return equalsIgnoreCase(getLocalPart(), addr.getLocalPart())
&& Objects.equals(getDomain(), addr.getDomain());
}
return false;
}{code}
So I wonder how {{equalsIgnoreCase}} differs from {{equals}}. We may need a
(separate) ticket to fix this incorrect behaviour (James should support case
variation in mailAdresss - or alike)
Maybe TDD would have avoided such duplicated code BTW...
was:
The mail address defined in this RFC:
[https://tools.ietf.org/html/rfc5321#section-2.4] is leading to some
interpretation on the case sensitive of user part.
Case insensitiveness of domains is already embeded as part of {{Domain}} object
which MailAddress relies on.
Tests needs to be added in MailAddress tests:
{code:java}
a...@d.com == a...@d.com a...@d.com != a...@d.com {code}
{{ }}
But this commit should be dropped.
(BTW equals already do ignore case assertions...)
{code:java}
@Override
public final boolean equals(Object obj) {
if (obj == null) {
return false;
} else if (obj instanceof String) {
String theString = (String) obj;
return toString().equalsIgnoreCase(theString);
} else if (obj instanceof MailAddress) {
MailAddress addr = (MailAddress) obj;
if (isNullSender() && addr.isNullSender()) {
return true;
}
return equalsIgnoreCase(getLocalPart(), addr.getLocalPart())
&& Objects.equals(getDomain(), addr.getDomain());
}
return false;
}{code}
{{}}
{{}}{{}}
So I wonder how {{equalsIgnoreCase}} differs from {{equals}}. We may need a
(separate) ticket to fix this incorrect behaviour (James should support case
variation in mailAdresss - or alike)
Maybe TDD would have avoided such duplicated code BTW...
[
|https://tools.ietf.org/html/rfc5321#section-2.4]
> Define the policy on mail address matching
> --
>
> Key: JAMES-2552
> URL: https://issues.apache.org/jira/browse/JAMES-2552
> Project: James Server
> Issue Type: New Feature
>Reporter: Antoine Duprat
>Priority: Major
>
> The mail address defined in this RFC:
> [https://tools.ietf.org/html/rfc5321#section-2.4] is leading to some
> interpretation on the case sensitive of user part.
> Case insensitiveness of domains is already embeded as part of {{Domain}}
> object which MailAddress relies on.
> Tests needs to be added in MailAddress tests:
> {code:java}
> a...@d.com == a...@d.com a...@d.com != a...@d.com {code}
> {{ }}
> But this commit should be dropped.
> (BTW equals already do ignore case assertions...)
> {code:java}
> @Override
> public final boolean equals(Object obj) {
> if (obj == null) {
> return false;
> } else if (obj instanceof String) {
> String theString = (String) obj;
> return toString().equalsIgnoreCase(theString);
> } else if (obj instanceof MailAddress) {
> MailAddress addr = (MailAddress) obj;
> if (isNullSender() && addr.isNullSender()) {
> return true;
> }
> return equalsIgnoreCase(getLocalPart(), addr.getLocalPart())
> && Objects.equals(getDomain(), addr.getDomain());
> }
> return false;
> }{code}
> So I wonder how {{equalsIgnoreCase}} differs from {{equals}}. We may need a
> (separate) ticket to fix this incorrect behaviour (James should support case
> variation in mailAdresss - or alike)
> Maybe TDD would have avoided such duplicated code BTW...
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2552) Define the policy on mail address matching
Antoine Duprat created JAMES-2552:
-
Summary: Define the policy on mail address matching
Key: JAMES-2552
URL: https://issues.apache.org/jira/browse/JAMES-2552
Project: James Server
Issue Type: New Feature
Reporter: Antoine Duprat
The mail address defined in this RFC:
[https://tools.ietf.org/html/rfc5321#section-2.4] is leading to some
interpretation on the case sensitive of user part.
Case insensitiveness of domains is already embeded as part of {{Domain}} object
which MailAddress relies on.
Tests needs to be added in MailAddress tests:
{code:java}
a...@d.com == a...@d.com a...@d.com != a...@d.com {code}
{{ }}
But this commit should be dropped.
(BTW equals already do ignore case assertions...)
{code:java}
@Override
public final boolean equals(Object obj) {
if (obj == null) {
return false;
} else if (obj instanceof String) {
String theString = (String) obj;
return toString().equalsIgnoreCase(theString);
} else if (obj instanceof MailAddress) {
MailAddress addr = (MailAddress) obj;
if (isNullSender() && addr.isNullSender()) {
return true;
}
return equalsIgnoreCase(getLocalPart(), addr.getLocalPart())
&& Objects.equals(getDomain(), addr.getDomain());
}
return false;
}{code}
{{}}
{{}}{{}}
So I wonder how {{equalsIgnoreCase}} differs from {{equals}}. We may need a
(separate) ticket to fix this incorrect behaviour (James should support case
variation in mailAdresss - or alike)
Maybe TDD would have avoided such duplicated code BTW...
[
|https://tools.ietf.org/html/rfc5321#section-2.4]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2549) Default consistency level should be quorum
[ https://issues.apache.org/jira/browse/JAMES-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat closed JAMES-2549. - > Default consistency level should be quorum > -- > > Key: JAMES-2549 > URL: https://issues.apache.org/jira/browse/JAMES-2549 > Project: James Server > Issue Type: New Feature > Components: cassandra >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.2.0 > > > We are not setting the consistency level currently, then the driver set it by > default to local one. > We should modify it and set the consistency level for all queries to quorum. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2549) Default consistency level should be quorum
[ https://issues.apache.org/jira/browse/JAMES-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Duprat resolved JAMES-2549. --- Resolution: Fixed Fix Version/s: 3.2.0 merged > Default consistency level should be quorum > -- > > Key: JAMES-2549 > URL: https://issues.apache.org/jira/browse/JAMES-2549 > Project: James Server > Issue Type: New Feature > Components: cassandra >Reporter: Antoine Duprat >Priority: Major > Fix For: 3.2.0 > > > We are not setting the consistency level currently, then the driver set it by > default to local one. > We should modify it and set the consistency level for all queries to quorum. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2550) geable RabbitMQ: delete
Antoine Duprat created JAMES-2550: - Summary: geable RabbitMQ: delete Key: JAMES-2550 URL: https://issues.apache.org/jira/browse/JAMES-2550 Project: James Server Issue Type: New Feature Reporter: Antoine Duprat 1. query all messages in time range [current message timestamp:now] 2. apply deletion on the given message set 3. store deleted message ids Update dequeue and browse appropriately. For example for dequeue, you'll need to check if the message is in the deleted message ids before returning it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
