date:20200611

[jira] [Updated] (JAMES-3212) Outlook > When rename a folder on OpenPaas, Outlook keeps both the updated folder and the old one.

2020-06-11 Thread Jira



 [ 
https://issues.apache.org/jira/browse/JAMES-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nguyễn Việt Đức updated JAMES-3212:
---
Description: 
We have an issue when mail client integrate with jmap/imap server some kind of 
synchronization:

when i rename a folder - which have sub folder in it, things happened make imap 
synchronization of mail client (out look app in window 10) are not correct, it 
keep the old folder and new updated folder.

I need to investigate more on this.

*On OpenPaas (mail client):*

  !image3.png!

*On Outlook (**mail client)**:*

!image4.png!

 

  was:
We have an issue when mail client integrate with jmap/imap server some kind of 
synchronization:

when i rename a folder - which have sub folder in it, things happened make imap 
synchronization of mail client (out look app in window 10) are not correct, it 
keep the old folder and new updated folder.

I need to investigate more on this.

*On OpenPaas (mail client):*

  !image3.png!

*On Outlook (**mail client)**:*

!image4.png!

 
 * Add to Phrasebook
 
 ** No word lists for English (USA) -> Vietnamese...
 
 ** Create a new word list...
 * Copy

 * Add to Phrasebook
 
 ** No word lists for English (USA) -> Vietnamese...
 
 ** Create a new word list...
 * Copy

 * Add to Phrasebook
 
 ** No word lists for English (USA) -> Vietnamese...
 
 ** Create a new word list...
 * Copy


> Outlook > When rename a folder on OpenPaas, Outlook keeps both the updated 
> folder and the old one.
> --
>
> Key: JAMES-3212
> URL: https://issues.apache.org/jira/browse/JAMES-3212
> Project: James Server
>  Issue Type: Improvement
>Reporter: Nguyễn Việt Đức
>Priority: Major
> Attachments: image3.png, image4.png
>
>
> We have an issue when mail client integrate with jmap/imap server some kind 
> of synchronization:
> when i rename a folder - which have sub folder in it, things happened make 
> imap synchronization of mail client (out look app in window 10) are not 
> correct, it keep the old folder and new updated folder.
> I need to investigate more on this.
> *On OpenPaas (mail client):*
>   !image3.png!
> *On Outlook (**mail client)**:*
> !image4.png!
>  



--
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-3212) Outlook > When rename a folder on OpenPaas, Outlook keeps both the updated folder and the old one.

2020-06-11 Thread Jira



 [ 
https://issues.apache.org/jira/browse/JAMES-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nguyễn Việt Đức updated JAMES-3212:
---
Description: 
We have an issue when mail client integrate with jmap/imap server some kind of 
synchronization:

when i rename a folder - which have sub folder in it, things happened make imap 
synchronization of mail client (out look app in window 10) are not correct, it 
keep the old folder and new updated folder.

I need to investigate more on this.

*On OpenPaas (mail client):*

  !image3.png!

*On Outlook (**mail client)**:*

!image4.png!

 
 * Add to Phrasebook
 
 ** No word lists for English (USA) -> Vietnamese...
 
 ** Create a new word list...
 * Copy

 * Add to Phrasebook
 
 ** No word lists for English (USA) -> Vietnamese...
 
 ** Create a new word list...
 * Copy

 * Add to Phrasebook
 
 ** No word lists for English (USA) -> Vietnamese...
 
 ** Create a new word list...
 * Copy

  was:
*Preconditions*

A folder has been created on Outlook and synchronize to OpenPaas.

*Description*

After synchronize the change from Openpaas folder, Outlook keeps both updated 
folder and the old one.

*On OpenPaas:*

  !image3.png!

*On Outlook:*

!image4.png!

User cannot delete the old folder on Outlook. He need to unsubscribe first then 
delete the folder.

*Expected result*

Please investigate if it's outlook feature.

If not, Outlook should keep only the updated folder.

*Reproduction Steps*

1. On OpenPaas, rename a folder

2. On Outlook desktop app, restart the app to synchronize the change.

3. After the change is synchronized, verify the issue.

*Environment*
 - Sandbox account, version RC-1.7.8

 - Outlook App on Windows 10


> Outlook > When rename a folder on OpenPaas, Outlook keeps both the updated 
> folder and the old one.
> --
>
> Key: JAMES-3212
> URL: https://issues.apache.org/jira/browse/JAMES-3212
> Project: James Server
>  Issue Type: Improvement
>Reporter: Nguyễn Việt Đức
>Priority: Major
> Attachments: image3.png, image4.png
>
>
> We have an issue when mail client integrate with jmap/imap server some kind 
> of synchronization:
> when i rename a folder - which have sub folder in it, things happened make 
> imap synchronization of mail client (out look app in window 10) are not 
> correct, it keep the old folder and new updated folder.
> I need to investigate more on this.
> *On OpenPaas (mail client):*
>   !image3.png!
> *On Outlook (**mail client)**:*
> !image4.png!
>  
>  * Add to Phrasebook
>  
>  ** No word lists for English (USA) -> Vietnamese...
>  
>  ** Create a new word list...
>  * Copy
>  * Add to Phrasebook
>  
>  ** No word lists for English (USA) -> Vietnamese...
>  
>  ** Create a new word list...
>  * Copy
>  * Add to Phrasebook
>  
>  ** No word lists for English (USA) -> Vietnamese...
>  
>  ** Create a new word list...
>  * Copy



--
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

Re: Distributed James: make ElasticSearch indexing optional?

2020-06-11 Thread Tellier Benoit

+1

On 11/06/2020 23:01, Raphaël Ouazana-Sustowski wrote:
> Hi,
> 
> Here is a proposal to make ElasticSearch optional in our distributed
> product/flavor/server.
> 
> Comments are welcome.
> 
> 
> ## Why?
> 
> Some people have expressed the need of using a distributed James without
> ElasticSearch:
> - in some comment here: https://issues.apache.org/jira/browse/JAMES-3086
> - one of our customers plan to deploy a distributed James server for
> serving POP3 encrypted emails. This deployment does not rely on
> searching features. However as part of current Distributed James server
> he is forced to rely on ElasticSearch email indexing.
> 
> This results in wasted resources as maintaining an ElasticSearch cluster
> to keep up with the volume is expensive.
> Maintaining an ElasticSearch cluster when not needed is costly at
> several levels:
> - cost of infrastructure to deploy it
> - cost of people having to maintain it
> - performance cost on James to unnecessarily index data
> 
> ## How ?
> 
> Scanning search is a search implementation that is running on top of any
> mailbox implementation, even distributed ones and does not require to
> index data.
> 
> Scanning Search is tested both at the component level (unit test) but
> also passes IMAP (MPT) tests on top of Cassandra implementation, as well
> as JMAP memory tests, thus delivers correct results. Of course it does
> not support full text search.
> 
> We should allow Distributed James to optionally rely on scanning search
> instead of ElasticSearch.
> 
>  - Scanning search should be advised for deployments rarely searching data
>  - ElasticSearch should be advised when search is frequent or requires
> high performance
> 
> We could use module choosing [1] to choose between scanning search and
> ElasticSearch.
> 
> To be noted that scanning search introduces no other dependencies as it
> is part of mailbox-store thus causes no risk of library clashes.
> 
> To be noted also that metric collection and log collection using
> ElasticSearch is unaffected.
> 
> ## Alternative
> 
> The alternative would be to build a different product/flavor/server than
> the distributed one, where the only difference with the distributed one
> is that indexing will rely on scanning instead of ElasticSearch.
> 
> The maintenance cost of such a product/flavor/server is higher than of a
> configuration option (Docker images to release, time and energy to run
> integration tests on it).
> 
> Such a product/flavor is hard to brand because even if it answers a
> need, it is not so far of the distributed one, and does not answer needs
> that are very far from it neither.
> 
> The advantage is that is would allow to more fine tune this solution to
> answer to the exact needs.
> 
> ## Work in Progress
> 
> See pull request: https://github.com/linagora/james-project/pull/3425
> 
> Regards,
> 
> Raphaël.
> 
> 
> 
> [1]
> https://github.com/apache/james-project/blob/master/src/adr/0036-against-use-of-conditional-statements-in-guice-modules.md
> 
> 
> 
> -
> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
> For additional commands, e-mail: server-dev-h...@james.apache.org
> 

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

[jira] [Commented] (JAMES-3213) Prevent non-participant add in Sabre

2020-06-11 Thread Benoit Tellier (Jira)



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

Benoit Tellier commented on JAMES-3213:
---

Please be more careful when you feed Apache James bugtracker. ESN, Sabre are 
not part of the Apache James project and thus are not relevant in this context.

> Prevent non-participant add in Sabre
> 
>
> Key: JAMES-3213
> URL: https://issues.apache.org/jira/browse/JAMES-3213
> Project: James Server
>  Issue Type: Improvement
>Reporter: Gautier DI FOLCO
>Priority: Minor
>
> When an attendee changes his participant status, there is a notification 
> email is sent to the event organizer from the attendee.
> Then ESN send an ITIP request to Sabre to handle realtime update.
> If the sender email does not exist in the list attendee, Sabre ITIP broker 
> will add him to the attendee list. 
> [https://github.com/sabre-io/vobject/blob/master/lib/ITip/Broker.php#L373-L382]
> This is not correct in cases:
>  * When an external attendee accept the event, the notification email should 
> send from OpenPaaS system 
> ([no-re...@open-paas.org|mailto:no-re...@open-paas.org])
>  * When the attendee forwards the invitation email to an external user, then 
> the external user (is not included in attendee list) accepts.
> Both cases above should not lead to the behavior that adding the sender to 
> the attendee list.



--
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] [Commented] (JAMES-3209) Auth Module to make James usable with Nginx mail proxy for TLS termination

2020-06-11 Thread David Leangen (Jira)



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

David Leangen commented on JAMES-3209:
--

I tried the process without using Docker Compose, and nginx does indeed make 
the call to my auth server, so there must be a problem with the Docker Compose 
configuration in the files I attached.

> Auth Module to make James usable with Nginx mail proxy for TLS termination 
> ---
>
> Key: JAMES-3209
> URL: https://issues.apache.org/jira/browse/JAMES-3209
> Project: James Server
>  Issue Type: New Feature
>Reporter: Ioan Eugen Stan
>Priority: Major
> Attachments: docker-compose.yaml, nginx.conf
>
>
> Apache James needs to be deployed with TLS encryption to ensure security of 
> emails during transport. 
> We could use Nginx as a mail proxy and use it for TLS termination. 
> However we need to implement an HTTP auth service for that to work. 
> This issue should cover work on making Nginx a valid mail proxy in front of 
> Apache James.
> References:
> https://docs.nginx.com/nginx/admin-guide/mail-proxy/mail-proxy/ 
> https://nginx.org/en/docs/mail/ngx_mail_auth_http_module.html#protocol
> == Context
> Unfortunately, Java has only the keystore for managing TLS certificates. This 
> is makes deploying TLS certificates hard for Apache James since the internet 
> does not use. keystore format. 
> We could use Nginx as a amil proxy. Nginx supports the certificate format 
> that all other tools use. (add format here - PKCS #XXX ). People know how to 
> setup Nginx with LetsEncrypt and benefit from free TLS certificates with 
> automatic renewal. 
> However we need an integration piece: the nginx auth service. It's an http 
> service that works only with headers. It should be simple to write and work 
> integrate.



--
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] [Commented] (JAMES-3206) Keystore Exception when running the "Basic" Server

2020-06-11 Thread David Leangen (Jira)



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

David Leangen commented on JAMES-3206:
--

Yes, I did indeed use that password. I even `docker exec`ed into the container 
to double check.

> Keystore Exception when running the "Basic" Server
> --
>
> Key: JAMES-3206
> URL: https://issues.apache.org/jira/browse/JAMES-3206
> Project: James Server
>  Issue Type: Bug
>Reporter: David Leangen
>Priority: Blocker
>
> When attempting to run the "Basic" server (jpa-guice) out-of-the-box, I am 
> unable to get the server running due to a password exception:
> {code:java}
> 12:13:26.044 [ERROR] o.a.j.GuiceJamesServer - Fatal error while starting James
> java.security.UnrecoverableKeyException: failed to decrypt safe contents 
> entry: java.lang.IllegalStateException: password has been cleared
>  ... 32 common frames omitted
> Wrapped by: java.io.IOException: keystore password was incorrect
>  at java.base/sun.security.pkcs12.PKCS12KeyStore.engineLoad(Unknown Source)
>  at java.base/sun.security.util.KeyStoreDelegator.engineLoad(Unknown Source)
>  at java.base/java.security.KeyStore.load(Unknown Source)
>  at 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer.buildSSLContext(AbstractConfigurableAsyncServer.java:396)
>  at 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer.init(AbstractConfigurableAsyncServer.java:264)
>  at 
> org.apache.james.protocols.lib.netty.AbstractServerFactory.init(AbstractServerFactory.java:58)
>  at 
> org.apache.james.modules.protocols.IMAPServerModule.lambda$configureImap$0(IMAPServerModule.java:93)
>  at 
> org.apache.james.utils.InitilizationOperationBuilder$PrivateImpl.initModule(InitilizationOperationBuilder.java:52)
>  at 
> com.github.fge.lambdas.consumers.ConsumerChainer.lambda$sneakyThrow$9(ConsumerChainer.java:73)
>  at java.base/java.util.stream.ReferencePipeline$11$1.accept(Unknown Source)
>  at java.base/java.util.stream.DistinctOps$1$2.accept(Unknown Source)
>  at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown 
> Source)
>  at java.base/java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
>  at 
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown 
> Source)
>  at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
>  at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown 
> Source)
>  at 
> java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown 
> Source)
>  at 
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown
>  Source)
>  at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
>  at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
>  at java.base/java.util.stream.ReferencePipeline$7$1.accept(Unknown Source)
>  at 
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown 
> Source)
>  at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
>  at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown 
> Source)
>  at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown 
> Source)
>  at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
>  at java.base/java.util.stream.ReferencePipeline.collect(Unknown Source)
>  at 
> org.apache.james.utils.InitializationOperations.processConfigurables(InitializationOperations.java:53)
>  at 
> org.apache.james.utils.InitializationOperations.initModules(InitializationOperations.java:43)
>  at org.apache.james.GuiceJamesServer.start(GuiceJamesServer.java:93)
>  at org.apache.james.JamesServerMain.main(JamesServerMain.java:24)
>  at org.apache.james.JPAJamesServerMain.main(JPAJamesServerMain.java:105)
> 12:14:23.287 [ERROR] o.a.j.PeriodicalHealthChecks - UNHEALTHY: Guice 
> application lifecycle : James server is not started.
> {code}
>  I opened a session into the docker container to test the keystore. It exists 
> in the conf directory and works as intended with the default password.
> So I do not know why this exception occurs and the server does not start. :(



--
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

Distributed James: make ElasticSearch indexing optional?

2020-06-11 Thread Raphaël Ouazana-Sustowski

Hi,

Here is a proposal to make ElasticSearch optional in our distributed
product/flavor/server.

Comments are welcome.

## Why?

Some people have expressed the need of using a distributed James without
ElasticSearch:

- in some comment here: https://issues.apache.org/jira/browse/JAMES-3086
- one of our customers plan to deploy a distributed James server for
serving POP3 encrypted emails. This deployment does not rely on
searching features. However as part of current Distributed James server
he is forced to rely on ElasticSearch email indexing.

This results in wasted resources as maintaining an ElasticSearch cluster
to keep up with the volume is expensive.
Maintaining an ElasticSearch cluster when not needed is costly at
several levels:

- cost of infrastructure to deploy it
- cost of people having to maintain it
- performance cost on James to unnecessarily index data

## How ?

Scanning search is a search implementation that is running on top of any
mailbox implementation, even distributed ones and does not require to
index data.

Scanning Search is tested both at the component level (unit test) but
also passes IMAP (MPT) tests on top of Cassandra implementation, as well
as JMAP memory tests, thus delivers correct results. Of course it does
not support full text search.

We should allow Distributed James to optionally rely on scanning search
instead of ElasticSearch.

- Scanning search should be advised for deployments rarely searching data
- ElasticSearch should be advised when search is frequent or requires
high performance

We could use module choosing [1] to choose between scanning search and
ElasticSearch.

To be noted that scanning search introduces no other dependencies as it
is part of mailbox-store thus causes no risk of library clashes.

To be noted also that metric collection and log collection using
ElasticSearch is unaffected.

## Alternative

The alternative would be to build a different product/flavor/server than
the distributed one, where the only difference with the distributed one
is that indexing will rely on scanning instead of ElasticSearch.

The maintenance cost of such a product/flavor/server is higher than of a
configuration option (Docker images to release, time and energy to run
integration tests on it).

Such a product/flavor is hard to brand because even if it answers a
need, it is not so far of the distributed one, and does not answer needs
that are very far from it neither.

The advantage is that is would allow to more fine tune this solution to
answer to the exact needs.

## Work in Progress

See pull request: https://github.com/linagora/james-project/pull/3425

Regards,

Raphaël.

[1]
https://github.com/apache/james-project/blob/master/src/adr/0036-against-use-of-conditional-statements-in-guice-modules.md

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

Re: James architecture: core components, sub-components and utility components

2020-06-11 Thread Raphaël Ouazana-Sustowski


Hello,

Even if I globally agree with your definition of extension, I think 
import/export is a very valuable feature and should be promoted (when 
finished). Of course from an architecture point of view it could be seen 
as an extension but for an admin it should be well integrated and easy 
to use.


Regards,

Raphaël.

Le 11/06/2020 à 08:21, Tellier Benoit a écrit :


On 10/06/2020 22:49, Raphaël Ouazana-Sustowski wrote:

Hi Benoît,

This inventory is amazing, thanks for having issued it.

For my part it's just missing the LDAP read only user repository as an
implementation of the user repository.

True.


But I probably missed things :)

Oh for example the (unfinished?) import / export mechanism.

I would count it as a mailbox extension. I did not listed them on
purpose as I think these subproject parts address very specific needs
and should not be packaged as part of out-of-the-box servers.

I rather think that each server should have a list of extensions that we
can use with it.

So far I can come up with the following list of extensions candidates
(not only mailbox ones):
  - Data Leak Prevention
  - SpamAssassin
  - OverQuota mailing
  - Quota search
  - Of course mailbox import/export
  - DeletedMessages vault
  - Maybe even Sieve support could live as an extension?
  - WKD would IMO also qualify...
  - ...

As a regular user, I don't really care about them. They should not
complexify the configuration, documentation or the server itself that I
am running.

I started detailing my thoughts about extension mechanism in this email
https://www.mail-archive.com/server-dev@james.apache.org/msg66206.html

I believe that extracting extensions out of default servers would ease
reducing build time.

But I also believe it would help us building (guice based) servers that
are easier to extend.

Regards,

Benoit


Regards,

Raphaël.

Le 25/05/2020 à 07:00, Tellier Benoit a écrit :

Hi David,

I gave a shot at defining:

   - Core components, that offers services at heart of James
   - Utility components, that offers services core-components
implementations can rely on.
   - Mailbox sub-components.

Here is the result. I encourage other project members to review it.

   - Did I forgot some components?
   - Is the way I split them relevant?
   - Is the way to describe a component (descriptions, entities, key
interfaces, plugin) relevant? Would you add/remove something?
   - Of course all the component level details...

I hope it helps your documentation effort.

Best regards,

Benoit

-

# Core components

## MailetContainer

Enables mail processing.

Entity:
   - **Mails**: Message transiting between a sender and recipients

Key interfaces:
   - **Mailet**: Enables to act upon an email: modify it, trigger side
effects
   - **Matcher**: Condition to trigger a mailet action

Plugin: A user can register their own mailets / matchers

Here is a list of mailets providing central services, and bridges other
core components defined here after :

   - **RemoteDelivery** enables sending emails to other mail servers,
using the SMTP protocol.
   - **LocalDelivery** enables delivering emails to local user mailboxes.
   - **RecipientRewriteTable** queries and applied recipient rewritting
rules.
   - **ToMailRepository** stores emails in a given mail repository.
   - **Sieve** executes stored sieve scripts against incoming emails.

## MailQueue

Enables asynchronous mail processing. Enables review and administration
of mail traffic awaiting processing.

Entity: **Mails**

Key interface: **MailQueue**, **ManageableMailQueue**

Implementations:
   - Memory
   - (embedded) ActiveMQ
   - Distributed (RabbitMQ + Cassandra)
   - Files

## MailRepositories

Enables storing emails, along with their processing context. Enables
traffic review.

Can be used to recover error, stores spam, etc...

Entity: **Mails**

Key interfaces:
   - **MailRepository**
   - **MailRepositoryStore**: enables instanciation of MailRepositories

Plugins:
   - A user can register new classes of MailRepository, that he can then
configure within it's Mailet Container

Bundled implementation:
   - Memory
   - Cassandra
   - JDBC
   - File

## Mailbox

The mailbox stores user messages for later retrieval.

Entities:
   - **Messages**: a mime message belonging to a user, along with their
mailbox context.
   - **Mailboxes**: a group of messages

Sample operations:
   - Mailboxes can be created, deleted, renamed
   - Messages can be appended, deleted, moved, copied, their flags can be
modified

Key interfaces:
   - **MailboxManager**: Enable managing and accessing mailboxes
   - **MessageManager**: Enables accessing messages within a given
mailbox. Can be obtained via the MailboxManager.
   - **MessageIdManager**: Enables accessing messages by their unique
identifier.. Can be obtained via the MailboxManager.

Implementations:
   - Memory implementation
   - Maildir implementation
   - JPA implementation
   - Cassandra implementa

[jira] [Commented] (JAMES-3204) CassandraMessageMapper badly applies LIMIT

2020-06-11 Thread Raphael Ouazana (Jira)



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

Raphael Ouazana commented on JAMES-3204:


[https://github.com/linagora/james-project/pull/3428] should have taken care of 
it, but we still need to run some load testing to check the global behavior

> CassandraMessageMapper badly applies LIMIT
> --
>
> Key: JAMES-3204
> URL: https://issues.apache.org/jira/browse/JAMES-3204
> Project: James Server
>  Issue Type: Improvement
>  Components: cassandra, mailbox
>Affects Versions: 3.5.0
>Reporter: Benoit Tellier
>Priority: Major
> Fix For: 3.6.0
>
>
> We noticed some `BusyPool` exceptions filling up the driver queue upon IMAP 
> query (FETCH flags for all the messages in the mailbox).
> The MessageManager do batch those reads (by default by 200 for metadata)., 
> wich then call the MessageMapper with this limit.
> Some unit tests performed at the Cassandra mailbox level proved the soft 
> filtering did badly applies, and that we were performing uneeded extra reads 
> for the full batch read from the database.
> One good mitigation strategy is to push the limit to the Cassandra query, and 
> ensures filtering happens before the extra reads are performed.
> https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Flux.html#take-long-
>  documents that it just don't propagate downstream request once a given 
> amount is reached however it do not ensure any form of backpressure. We might 
> want to further audit our code, looking for similar take mis-usages. 



--
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] [Commented] (JAMES-3194) Rely on DTOConverter in TaskRoute

2020-06-11 Thread Raphael Ouazana (Jira)



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

Raphael Ouazana commented on JAMES-3194:


[https://github.com/linagora/james-project/pull/3382] takes care of this, 
please close this issue

> Rely on DTOConverter in TaskRoute
> -
>
> Key: JAMES-3194
> URL: https://issues.apache.org/jira/browse/JAMES-3194
> Project: James Server
>  Issue Type: Improvement
>  Components: task, webadmin
>Affects Versions: master
>Reporter: Benoit Tellier
>Priority: Major
> Fix For: 3.6.0
>
>
> The taskManager defines task serialization, used to persist a task and 
> additional information, in order to be accessible in a distributed context.
> However, we rely on implicit Jackson serialization for returning task details 
> over webadmin.
> This results in confusing expectation as a developer. We furthermore "leak" 
> jackson annotation in the details models.
> We should rely on the DTOs for details serialization over webadmin.
> https://github.com/linagora/james-project/pull/3382 is a trial to reach this 
> prurpose.



--
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] [Commented] (JAMES-3182) Fetching message in getMessageList ignore inMailbox filter when in a combination of filter

2020-06-11 Thread Raphael Ouazana (Jira)



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

Raphael Ouazana commented on JAMES-3182:


[https://github.com/linagora/james-project/pull/3427] fixes some related issues

> Fetching message in getMessageList ignore inMailbox filter when in a 
> combination of filter
> --
>
> Key: JAMES-3182
> URL: https://issues.apache.org/jira/browse/JAMES-3182
> Project: James Server
>  Issue Type: Test
>  Components: JMAP
>Affects Versions: 3.6.0
>Reporter: Rémi Kowalski
>Assignee: Antoine Duprat
>Priority: Major
> Fix For: 3.6.0
>
>
> The  inMailbox, notInMailbox filters are ignored when they are placed in a 
> combination of filter.
> The reason is :
>  * Mailboxes the query is run against are resolved against cassandra before 
> being pushed to the search index.
>  * The bit of code handling this conversion only take into consideration TOP 
> LEVEL liters and not those wrapped by some FilterOperatrs (AND, OR, NOT)
> for more context see  #3180: 
>  [https://github.com/linagora/james-project/pull/3374]
> DOD : 
>  make
> {color:#00627a}`GetMessageListMethodTest.getMessageListShouldFetchUnreadMessagesInMailboxUsingACombinationOfFilter`
>  
>  pass and add test to ensure the notInMailbox filter is handled as well.
>  
>  
>  create some other tests with nested mailbox filters
>  {color}



--
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

50 matches

Mail list logo