[jira] [Commented] (JAMES-3277) Don't read outbox mailbox for each message in SetMessagesUpdateProcessor
[
https://issues.apache.org/jira/browse/JAMES-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144583#comment-17144583
]
Benoit Tellier commented on JAMES-3277:
---
We are in my opinion missing valuable information to understand this work.
> Don't read outbox mailbox for each message in SetMessagesUpdateProcessor
>
>
> Key: JAMES-3277
> URL: https://issues.apache.org/jira/browse/JAMES-3277
> Project: James Server
> Issue Type: Bug
> Components: JMAP
>Affects Versions: 3.5.0
>Reporter: Rémi Kowalski
>Assignee: Antoine Duprat
>Priority: Major
>
> {{}}
> We are reading system mailboxes to validate each updates.
> *DoD*
> it should be done only once
--
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-3202) ReIndexing "filtering" for only outdated indexed data
[
https://issues.apache.org/jira/browse/JAMES-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3202.
-
Fix Version/s: 3.6.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/3429 contributed this
> ReIndexing "filtering" for only outdated indexed data
> -
>
> Key: JAMES-3202
> URL: https://issues.apache.org/jira/browse/JAMES-3202
> Project: James Server
> Issue Type: Improvement
>Reporter: René Cordier
>Priority: Major
> Fix For: 3.6.0
>
>
> *Why?*
> ReIndexing can be slow, and requires to read all messages in the DB, then
> trigger the full reIndexing, even when the document is not outdated.
> All these document changes creates a lot of deleted documents. Lucene "marks
> them as deleted", polluting the entire index until segment merging happens
> (yet another costly operation). The less we do updates the better. To be
> noted that partial updates still leads to a full new document in Lucene, and
> just optimises bandwith + avoids reads.
> *Need specification*
> As an admin, I want to run a reIndex.
> We furtermore handle `RunningOptions` allowing to specify the message rate
> attempted. See [https://github.com/linagora/james-project/pull/3394]
> We still need, given a message, get it's search index representation (at
> least for its mutable data). From this we will be able to condition the
> reindexing to outdated/non exsting data, significantly fasting up the
> reindexing process on mostly valid indexes. The admin could then mention via
> query parameter this option (carried over in running options).
> *MessageSearchIndex API changes*:
> {code:java}
> inderface MessageSearchIndex {
>//...
>Mono retrieveIndexedFlags(MailboxId mailboxId, MessageUid uid);
>//...
> }
> {code}
> ElasticSearch will rely on the _GET_ verb (not search).
> Unit test will be written for this new method.
> ReIndexing `RunningOptions` will then carry over the option, that
> ReIndexerPerformer will need to take into account.
> Sample webadmin API:
> {code:bash}
> curl -XPOST http://james:8000/mailboxes?action=reindex=outdatedIndex
> {code}
--
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-3184) Concurrency for consistency tasks
[ https://issues.apache.org/jira/browse/JAMES-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144599#comment-17144599 ] Benoit Tellier commented on JAMES-3184: --- https://github.com/linagora/james-project/pull/3409 contributed a refactoring using reactor transform operation for better composability > Concurrency for consistency tasks > - > > Key: JAMES-3184 > URL: https://issues.apache.org/jira/browse/JAMES-3184 > Project: James Server > Issue Type: Improvement >Reporter: Lan Khuat >Priority: Major > Fix For: 3.6.0 > > > We currently limit concurrency of consistency tasks to 1 in order to avoid > unbounded concurrency. > When running a consistency task, an admin should be able to precise the > concurrency he wishes to use. > To do so, each task will expose (optional) concurrency parameters, that an > admin can provide via query parameters of the corresponding webadmin > endpoints. > * RecomputeUserFastViewProjectionItems > * RecomputeCurrentQuotas > * RecomputeMailboxCounters > * SolveMailboxInconsistencies > * SolveMessageInconsistencies > * FullReindexing > * UserReindexing > * SingleMailboxReindexing > * ErrorRecoveryReindexation -- 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-3284) Reduce logging level of converters to TRACE
[
https://issues.apache.org/jira/browse/JAMES-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146202#comment-17146202
]
Benoit Tellier commented on JAMES-3284:
---
Please configure the logger to exclude INFO / DEBUG log not starting by
org.apache.james
> Reduce logging level of converters to TRACE
> ---
>
> Key: JAMES-3284
> URL: https://issues.apache.org/jira/browse/JAMES-3284
> Project: James Server
> Issue Type: Sub-task
>Reporter: David Leangen
>Priority: Major
>
> Log entries like these from the various converters should be reduced to TRACE
> from DEBUG:
> {noformat}
> 09:35:15.493 [DEBUG] o.a.c.b.c.BooleanConverter - Setting default value: false
> 09:35:15.494 [DEBUG] o.a.c.b.c.BooleanConverter - Converting 'Boolean' value
> 'false' to type 'Boolean'
> 09:35:15.496 [DEBUG] o.a.c.b.c.BooleanConverter - No conversion required,
> value is already a Boolean
> 09:35:15.499 [DEBUG] o.a.c.b.c.ByteConverter - Setting default value: 0
> 09:35:15.499 [DEBUG] o.a.c.b.c.ByteConverter - Converting 'Integer' value '0'
> to type 'Byte'
> 09:35:15.499 [DEBUG] o.a.c.b.c.ByteConverter - Converted to Byte value '0'
> 09:35:15.500 [DEBUG] o.a.c.b.c.CharacterConverter - Setting default value:
> 09:35:15.500 [DEBUG] o.a.c.b.c.CharacterConverter - Converting 'Character'
> value ' ' to type 'Character'
> 09:35:15.500 [DEBUG] o.a.c.b.c.CharacterConverter - No conversion
> required, value is already a Character
> 09:35:15.501 [DEBUG] o.a.c.b.c.DoubleConverter - Setting default value: 0
> 09:35:15.521 [DEBUG] o.a.c.b.c.DoubleConverter - Converting 'Integer' value
> '0' to type 'Double'
> 09:35:15.521 [DEBUG] o.a.c.b.c.DoubleConverter - Converted to Double
> value '0.0'
> 09:35:15.522 [DEBUG] o.a.c.b.c.FloatConverter - Setting default value: 0
> 09:35:15.522 [DEBUG] o.a.c.b.c.FloatConverter - Converting 'Integer' value
> '0' to type 'Float'
> 09:35:15.522 [DEBUG] o.a.c.b.c.FloatConverter - Converted to Float value
> '0.0'
> 09:35:15.523 [DEBUG] o.a.c.b.c.IntegerConverter - Setting default value: 0
> 09:35:15.523 [DEBUG] o.a.c.b.c.IntegerConverter - Converting 'Integer' value
> '0' to type 'Integer'
> 09:35:15.523 [DEBUG] o.a.c.b.c.IntegerConverter - No conversion required,
> value is already a Integer
> 09:35:15.524 [DEBUG] o.a.c.b.c.LongConverter - Setting default value: 0
> 09:35:15.524 [DEBUG] o.a.c.b.c.LongConverter - Converting 'Integer' value '0'
> to type 'Long'
> 09:35:15.524 [DEBUG] o.a.c.b.c.LongConverter - Converted to Long value '0'
> 09:35:15.525 [DEBUG] o.a.c.b.c.ShortConverter - Setting default value: 0
> 09:35:15.525 [DEBUG] o.a.c.b.c.ShortConverter - Converting 'Integer' value
> '0' to type 'Short'
> 09:35:15.525 [DEBUG] o.a.c.b.c.ShortConverter - Converted to Short value
> '0'
> 09:35:15.527 [DEBUG] o.a.c.b.c.BigDecimalConverter - Setting default value:
> 0.0
> 09:35:15.527 [DEBUG] o.a.c.b.c.BigDecimalConverter - Converting 'BigDecimal'
> value '0.0' to type 'BigDecimal'
> 09:35:15.529 [DEBUG] o.a.c.b.c.BigDecimalConverter - No conversion
> required, value is already a BigDecimal
> 09:35:15.530 [DEBUG] o.a.c.b.c.BigIntegerConverter - Setting default value: 0
> 09:35:15.530 [DEBUG] o.a.c.b.c.BigIntegerConverter - Converting 'BigInteger'
> value '0' to type 'BigInteger'
> 09:35:15.530 [DEBUG] o.a.c.b.c.BigIntegerConverter - No conversion
> required, value is already a BigInteger
> 09:35:15.530 [DEBUG] o.a.c.b.c.BooleanConverter - Setting default value: false
> 09:35:15.530 [DEBUG] o.a.c.b.c.BooleanConverter - Converting 'Boolean' value
> 'false' to type 'Boolean'
> 09:35:15.530 [DEBUG] o.a.c.b.c.BooleanConverter - No conversion required,
> value is already a Boolean
> 09:35:15.530 [DEBUG] o.a.c.b.c.ByteConverter - Setting default value: 0
> 09:35:15.530 [DEBUG] o.a.c.b.c.ByteConverter - Converting 'Integer' value '0'
> to type 'Byte'
> 09:35:15.530 [DEBUG] o.a.c.b.c.ByteConverter - Converted to Byte value '0'
> 09:35:15.530 [DEBUG] o.a.c.b.c.CharacterConverter - Setting default value:
> 09:35:15.530 [DEBUG] o.a.c.b.c.CharacterConverter - Converting 'Character'
> value ' ' to type 'Character'
> 09:35:15.530 [DEBUG] o.a.c.b.c.CharacterConverter - No conversion
> required, value is already a Character
> {noformat}
--
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-3286) Improve BTreeIndex log message
[
https://issues.apache.org/jira/browse/JAMES-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146198#comment-17146198
]
Benoit Tellier commented on JAMES-3286:
---
Can we configure logback.xml to exclude INFO logs not prefixed by
org.apache.james ?
> Improve BTreeIndex log message
> --
>
> Key: JAMES-3286
> URL: https://issues.apache.org/jira/browse/JAMES-3286
> Project: James Server
> Issue Type: Sub-task
>Reporter: David Leangen
>Priority: Major
>
> This message is quite useless:
> {noformat}
> 09:35:21.860 [DEBUG] o.a.a.s.k.d.i.BTreeIndex - loading
> 09:35:21.861 [DEBUG] o.a.a.s.k.d.i.BTreeIndex - loading
> 09:35:21.861 [DEBUG] o.a.a.s.k.d.i.BTreeIndex - loading
> 09:35:21.861 [DEBUG] o.a.a.s.k.d.i.BTreeIndex - loading
> 09:35:21.861 [DEBUG] o.a.a.s.k.d.i.BTreeIndex - loading
> {noformat}
--
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-3284) Reduce logging level of converters to TRACE
[
https://issues.apache.org/jira/browse/JAMES-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146204#comment-17146204
]
Benoit Tellier commented on JAMES-3284:
---
https://github.com/apache/james-project/pull/225 makes my proposal the default,
and addresses other tickets.
> Reduce logging level of converters to TRACE
> ---
>
> Key: JAMES-3284
> URL: https://issues.apache.org/jira/browse/JAMES-3284
> Project: James Server
> Issue Type: Sub-task
>Reporter: David Leangen
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Log entries like these from the various converters should be reduced to TRACE
> from DEBUG:
> {noformat}
> 09:35:15.493 [DEBUG] o.a.c.b.c.BooleanConverter - Setting default value: false
> 09:35:15.494 [DEBUG] o.a.c.b.c.BooleanConverter - Converting 'Boolean' value
> 'false' to type 'Boolean'
> 09:35:15.496 [DEBUG] o.a.c.b.c.BooleanConverter - No conversion required,
> value is already a Boolean
> 09:35:15.499 [DEBUG] o.a.c.b.c.ByteConverter - Setting default value: 0
> 09:35:15.499 [DEBUG] o.a.c.b.c.ByteConverter - Converting 'Integer' value '0'
> to type 'Byte'
> 09:35:15.499 [DEBUG] o.a.c.b.c.ByteConverter - Converted to Byte value '0'
> 09:35:15.500 [DEBUG] o.a.c.b.c.CharacterConverter - Setting default value:
> 09:35:15.500 [DEBUG] o.a.c.b.c.CharacterConverter - Converting 'Character'
> value ' ' to type 'Character'
> 09:35:15.500 [DEBUG] o.a.c.b.c.CharacterConverter - No conversion
> required, value is already a Character
> 09:35:15.501 [DEBUG] o.a.c.b.c.DoubleConverter - Setting default value: 0
> 09:35:15.521 [DEBUG] o.a.c.b.c.DoubleConverter - Converting 'Integer' value
> '0' to type 'Double'
> 09:35:15.521 [DEBUG] o.a.c.b.c.DoubleConverter - Converted to Double
> value '0.0'
> 09:35:15.522 [DEBUG] o.a.c.b.c.FloatConverter - Setting default value: 0
> 09:35:15.522 [DEBUG] o.a.c.b.c.FloatConverter - Converting 'Integer' value
> '0' to type 'Float'
> 09:35:15.522 [DEBUG] o.a.c.b.c.FloatConverter - Converted to Float value
> '0.0'
> 09:35:15.523 [DEBUG] o.a.c.b.c.IntegerConverter - Setting default value: 0
> 09:35:15.523 [DEBUG] o.a.c.b.c.IntegerConverter - Converting 'Integer' value
> '0' to type 'Integer'
> 09:35:15.523 [DEBUG] o.a.c.b.c.IntegerConverter - No conversion required,
> value is already a Integer
> 09:35:15.524 [DEBUG] o.a.c.b.c.LongConverter - Setting default value: 0
> 09:35:15.524 [DEBUG] o.a.c.b.c.LongConverter - Converting 'Integer' value '0'
> to type 'Long'
> 09:35:15.524 [DEBUG] o.a.c.b.c.LongConverter - Converted to Long value '0'
> 09:35:15.525 [DEBUG] o.a.c.b.c.ShortConverter - Setting default value: 0
> 09:35:15.525 [DEBUG] o.a.c.b.c.ShortConverter - Converting 'Integer' value
> '0' to type 'Short'
> 09:35:15.525 [DEBUG] o.a.c.b.c.ShortConverter - Converted to Short value
> '0'
> 09:35:15.527 [DEBUG] o.a.c.b.c.BigDecimalConverter - Setting default value:
> 0.0
> 09:35:15.527 [DEBUG] o.a.c.b.c.BigDecimalConverter - Converting 'BigDecimal'
> value '0.0' to type 'BigDecimal'
> 09:35:15.529 [DEBUG] o.a.c.b.c.BigDecimalConverter - No conversion
> required, value is already a BigDecimal
> 09:35:15.530 [DEBUG] o.a.c.b.c.BigIntegerConverter - Setting default value: 0
> 09:35:15.530 [DEBUG] o.a.c.b.c.BigIntegerConverter - Converting 'BigInteger'
> value '0' to type 'BigInteger'
> 09:35:15.530 [DEBUG] o.a.c.b.c.BigIntegerConverter - No conversion
> required, value is already a BigInteger
> 09:35:15.530 [DEBUG] o.a.c.b.c.BooleanConverter - Setting default value: false
> 09:35:15.530 [DEBUG] o.a.c.b.c.BooleanConverter - Converting 'Boolean' value
> 'false' to type 'Boolean'
> 09:35:15.530 [DEBUG] o.a.c.b.c.BooleanConverter - No conversion required,
> value is already a Boolean
> 09:35:15.530 [DEBUG] o.a.c.b.c.ByteConverter - Setting default value: 0
> 09:35:15.530 [DEBUG] o.a.c.b.c.ByteConverter - Converting 'Integer' value '0'
> to type 'Byte'
> 09:35:15.530 [DEBUG] o.a.c.b.c.ByteConverter - Converted to Byte value '0'
> 09:35:15.530 [DEBUG] o.a.c.b.c.CharacterConverter - Setting default value:
> 09:35:15.530 [DEBUG] o.a.c.b.c.CharacterConverter - Converting 'Character'
> value ' ' to type 'Character'
> 09:35:15.530 [DEBUG] o.a.c.b.c.CharacterConverter - No conversion
> required, value is already a Character
> {noformat}
--
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-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147549#comment-17147549
]
Benoit Tellier commented on JAMES-3214:
---
https://github.com/apache/james-project/pull/209 is related to some of the
issue comments, and reduced dependencies needed for the CLI (merged)
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
[jira] [Commented] (JAMES-3253) Delay of 8 minutes 20 seconds is now attempted
[ https://issues.apache.org/jira/browse/JAMES-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147543#comment-17147543 ] Benoit Tellier commented on JAMES-3253: --- https://github.com/apache/james-project/pull/224 is merged and is supposed to solve the aforementioned problem. [~dleangen] do you think we can close this now? > Delay of 8 minutes 20 seconds is now attempted > -- > > Key: JAMES-3253 > URL: https://issues.apache.org/jira/browse/JAMES-3253 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > > [WARN ] o.a.j.t.m.r.d.DelaysAndMaxRetry - Delay of 8 minutes 20 seconds is > >now attempted: 1 times > This one is a badly configured default file, it should get fixed too. I will > have a look -- 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-3276) TemporaryJamesServer leaks between tests
[ https://issues.apache.org/jira/browse/JAMES-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3276. - Fix Version/s: 3.6.0 Resolution: Fixed https://github.com/linagora/james-project/pull/3477 is merged > TemporaryJamesServer leaks between tests > > > Key: JAMES-3276 > URL: https://issues.apache.org/jira/browse/JAMES-3276 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Minor > Fix For: 3.6.0 > > > When tests are running with TemporaryJamesServer, some information are > leaking, it is visible when different configurations are set-up, because the > previous configuration is put. -- 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-3224) Make Cassandra Consistency levels configurable
[
https://issues.apache.org/jira/browse/JAMES-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3224.
-
Fix Version/s: 3.6.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/3448 contributed this
> Make Cassandra Consistency levels configurable
> --
>
> Key: JAMES-3224
> URL: https://issues.apache.org/jira/browse/JAMES-3224
> Project: James Server
> Issue Type: Improvement
> Components: cassandra
>Reporter: Gautier DI FOLCO
>Priority: Minor
> Fix For: 3.6.0
>
>
> Consistency level in Cassandra queries is set explicitly to QUORUM in some
> cases, and to SERIAL in some other cases (lightweight transactions).
> The goal is to make these queries globally configurable.
> In the {{cassandra.properties}} file, I propose we add two configuration
> properties:
> * {{cassandra.consistency_level.regular}} (default to QUORUM to avoid
> breaking changes)
> * {{cassandra.consistency_level.lightweight_transaction}} (default to SERIAL)
--
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-3264) MAILBOX details are read 3 times upon indexing
[ https://issues.apache.org/jira/browse/JAMES-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3264. - Fix Version/s: 3.6.0 Resolution: Fixed https://github.com/linagora/james-project/pull/3473 contributed this. > MAILBOX details are read 3 times upon indexing > -- > > Key: JAMES-3264 > URL: https://issues.apache.org/jira/browse/JAMES-3264 > Project: James Server > Issue Type: Improvement >Reporter: Nguyễn Việt Đức >Priority: Major > Fix For: 3.6.0 > > > !https://ci.linagora.com/linagora/lgs/openpaas/james/uploads/e66e59cdfb7bf1e09e103a71ebad7b89/Capture_d_%C3%A9cran_de_2020-06-22_12-05-54.png! > We can notice 3 mailbox reads for each indexed message > This is too much, we should reduce this to a single mailbox read. > *Definition of done* > * Indexing a mail do the same count (or less) of mailbox reads (compared to > messages reads) -- 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-3223) Bump guava and bean-utils to fix vulnerability
[ https://issues.apache.org/jira/browse/JAMES-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136501#comment-17136501 ] Benoit Tellier commented on JAMES-3223: --- https://github.com/linagora/james-project/pull/3445 > Bump guava and bean-utils to fix vulnerability > -- > > Key: JAMES-3223 > URL: https://issues.apache.org/jira/browse/JAMES-3223 > Project: James Server > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Rémi Kowalski >Priority: Major > > h5. [CVE-2018-10237|https://github.com/advisories/GHSA-mvr2-9pj6-7w5j] > moderate severity > *Vulnerable versions:* > 11.0, < 24.1.1 > *Patched version:* 24.1.1 > Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 > allows remote attackers to conduct denial of service attacks against servers > that depend on this library and deserialize attacker-provided data, because > the AtomicDoubleArray class (when serialized with Java serialization) and the > CompoundOrdering class (when serialized with GWT serialization) perform eager > allocation without appropriate checks on what a client has sent and whether > the data size is reasonable. > h5. [CVE-2019-10086|https://github.com/advisories/GHSA-6phf-73q6-gh87] > high severity > *Vulnerable versions:* < 1.9.4 > *Patched version:* 1.9.4 > In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added > which allows suppressing the ability for an attacker to access the > classloader via the class property available on all Java objects. We, however > were not using this by default characteristic of the PropertyUtilsBean. -- 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-2826) Improve compile time
[ https://issues.apache.org/jira/browse/JAMES-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136518#comment-17136518 ] Benoit Tellier commented on JAMES-2826: --- I would tend to agree. The point is, I am wondering if some tasks currently carried out by maven are easily done with gradle. I'm thinking of: - Mailet documentation generation - Release - Website generation (not an issue imo given that it is now isolated from the code base & given the antora migration) I wonder if maintaining several dependency systems at the same time could be error prone (maintaining one is already challenging, but 2 could run out of sync, for instance). > Improve compile time > > > Key: JAMES-2826 > URL: https://issues.apache.org/jira/browse/JAMES-2826 > Project: James Server > Issue Type: Improvement >Reporter: Matthieu Baechler >Assignee: Ioan Eugen Stan >Priority: Major > > Given that javac is a very fast compiler, we should be able to have a very > fast compile phase with maven. > However, it takes several minutes right now. > We should bring back some sanity to this build. -- 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-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135402#comment-17135402
]
Benoit Tellier commented on JAMES-3214:
---
https://www.mail-archive.com/server-dev@james.apache.org/msg66343.html
describes a dependency issue that causes multiple logging jars to end up on the
classpath. We should fix it as well.
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail:
[jira] [Commented] (JAMES-3220) Clarify DomainList Configuration
[ https://issues.apache.org/jira/browse/JAMES-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135501#comment-17135501 ] Benoit Tellier commented on JAMES-3220: --- > Can we simply remove this confusing text, since the Local Server uses Guice? Definitly yes. > I am having trouble understanding exactly what this means: Let's discard it, it only applies to XMLDomainList implementation, that is not part of basic server. > Clarify DomainList Configuration > > > Key: JAMES-3220 > URL: https://issues.apache.org/jira/browse/JAMES-3220 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > As part of the Local James Server, there is a domainlist.xml configuration. > Not all aspects of this are clear, and perhaps there are some simplifications > that could be made. -- 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-3219) Clarify DNS configuration
[ https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135510#comment-17135510 ] Benoit Tellier commented on JAMES-3219: --- > Please confirm: updating this configuration would require a restart of the > server. Is that correct? Yes. Any configuration change needs a server reload. > Clarify DNS configuration > - > > Key: JAMES-3219 > URL: https://issues.apache.org/jira/browse/JAMES-3219 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > I would like to provide a little more detailed documentation for the DNS > service, since users are required to configure this service (or use the > default config) in order to run the James Local Server. -- 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-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135532#comment-17135532
]
Benoit Tellier commented on JAMES-3214:
---
Regarding Jenkins setup, you could get a look at
https://github.com/linagora/james-jenkins
[~aduprat] is also working on a Jenkins 2 build whose pipeline should live in
James Apache code.
Don't hesitate to share your setup too.
Hope it helps,
Regards,
Benoit
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This
[jira] [Commented] (JAMES-3219) Clarify DNS configuration
[ https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135511#comment-17135511 ] Benoit Tellier commented on JAMES-3219: --- > Cannot get IP address(es) for Domain : james.linagora.com We need to in my opinion : - Remove linagora mention for configuration examples. - Comment configuration example that brings in these warnings... > Clarify DNS configuration > - > > Key: JAMES-3219 > URL: https://issues.apache.org/jira/browse/JAMES-3219 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > I would like to provide a little more detailed documentation for the DNS > service, since users are required to configure this service (or use the > default config) in order to run the James Local Server. -- 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-3220) Clarify DomainList Configuration
[ https://issues.apache.org/jira/browse/JAMES-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135503#comment-17135503 ] Benoit Tellier commented on JAMES-3220: --- >autodetect : Is this still even relevant in our now mostly >containerized world?? No. This brings in significant complexity. We should configure it by default to false, maybe even for all products. I think we should not expose domainlist.xml at all for the basic server. > Clarify DomainList Configuration > > > Key: JAMES-3220 > URL: https://issues.apache.org/jira/browse/JAMES-3220 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > As part of the Local James Server, there is a domainlist.xml configuration. > Not all aspects of this are clear, and perhaps there are some simplifications > that could be made. -- 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-3219) Clarify DNS configuration
[ https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135512#comment-17135512 ] Benoit Tellier commented on JAMES-3219: --- > Is my understanding correct? I think > But in what order? Do not know. Round robin? > Is my understanding correct? :+1: > What would be the reason / benefit of setting to true? Why does this > "feature" even exist?? That's a very good question! I don't know... > Clarify DNS configuration > - > > Key: JAMES-3219 > URL: https://issues.apache.org/jira/browse/JAMES-3219 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > I would like to provide a little more detailed documentation for the DNS > service, since users are required to configure this service (or use the > default config) in order to run the James Local Server. -- 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-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135515#comment-17135515
]
Benoit Tellier commented on JAMES-3214:
---
https://github.com/apache/james-project/pull/207 fixes this and brings down
dependencies for JPA James server down to 94 MB.
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail:
[jira] [Commented] (JAMES-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135691#comment-17135691
]
Benoit Tellier commented on JAMES-3214:
---
https://github.com/linagora/james-jenkins2/ (work in progress)
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional
[jira] [Commented] (JAMES-3219) Clarify DNS configuration
[ https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135699#comment-17135699 ] Benoit Tellier commented on JAMES-3219: --- > for our own implementation, we currently use dnsjava . Yes. James abstracts DNS resolution (for email use cases at least) to the DNSService interface relying on DNS Java. Autodetect is more about relying on DHCP collected information to locate the DNS server (and is a configuration for dnsjava) > (and we should update) https://github.com/dnsjava/dnsjava/releases :+1: we generally do a "dependency upgrade round" during a few weeks in summer to keep things up to date. We should include that one it it. > Clarify DNS configuration > - > > Key: JAMES-3219 > URL: https://issues.apache.org/jira/browse/JAMES-3219 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > I would like to provide a little more detailed documentation for the DNS > service, since users are required to configure this service (or use the > default config) in order to run the James Local Server. -- 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-3220) Clarify DomainList Configuration
[ https://issues.apache.org/jira/browse/JAMES-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135702#comment-17135702 ] Benoit Tellier commented on JAMES-3220: --- > Last question: is it safe to just remove the config file? It will result in a warning with today code. Hopefully by reworking guice servers to match the documentation (huge work coming!) this will not be an issue... > Clarify DomainList Configuration > > > Key: JAMES-3220 > URL: https://issues.apache.org/jira/browse/JAMES-3220 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > As part of the Local James Server, there is a domainlist.xml configuration. > Not all aspects of this are clear, and perhaps there are some simplifications > that could be made. -- 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-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=17140961#comment-17140961 ] Benoit Tellier commented on JAMES-3225: --- I think a upper bound could be 5 servers; exclusive for the James project. (disclaimer: it still requires discussions) A first milestone here could be to first get a build passing on Apache CI, and then migrate some infra. [~gmcdonald] our build relies on maven 3.6.3 and launches some docker containers to abstract some of our databases. Would we hit some known limitations ? Also which version of Jenkins do the infra runs? We have a current deployment on Jenkins 1.642.4 but we plan to migrate to jenkins2. > 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] [Commented] (JAMES-1766) Design a IMAP search test with gatling
[ https://issues.apache.org/jira/browse/JAMES-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141901#comment-17141901 ] Benoit Tellier commented on JAMES-1766: --- I would move it as an issue of https://github.com/linagora/james-gatling as this is not part of the James project. Of course such performance tests could be done as part of postage subproject, or some "gatling performance tests" can be donated as a postage replacement. (I really need one day to diagnose what actually exist is postage...) I would agree to reformulate this issue as "evaluate performance of IMAP SEARCH" as a JAMES ticket, but the development of a Gatling test suite have (sadly) not been done in an Apache context. > Design a IMAP search test with gatling > -- > > Key: JAMES-1766 > URL: https://issues.apache.org/jira/browse/JAMES-1766 > Project: James Server > Issue Type: Sub-task > Components: IMAPServer >Reporter: btell...@apache.org >Priority: Major > Fix For: 3.0.0 > > > Run the tests for a constant number of users, with ~1000 mails in there inbox. > You will demonstrate the number of supported users (during 4 hours at > constant latency) between : > - the simpleMessageSearchIndex implementation > - the ElasticSearch implementation -- 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-3261) Provide ZIP distribution for Guice servers application
[ https://issues.apache.org/jira/browse/JAMES-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141620#comment-17141620 ] Benoit Tellier commented on JAMES-3261: --- (however I'm not altering the POM structure, but only adding a plugin in some very specific pom. I believe that even if I carry this work out yours should mostly be unaffected) > Provide ZIP distribution for Guice servers application > -- > > Key: JAMES-3261 > URL: https://issues.apache.org/jira/browse/JAMES-3261 > Project: James Server > Issue Type: Task > Components: guice >Affects Versions: master >Reporter: Benoit Tellier >Assignee: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Today, a user wishing to run a Guice server needs either to compile it > himself, or run it via docker. > Given that (1) we do not expect operators to compile James source code and > given (2) the docker images are so far only built and distributed by some > external suppliers, the operators cannot run the guice servers in a vendor > indepandant way. > As such, in order to promote guice servers adoption, we need to build a ZIP > distribution for them. This ZIP distribution would then be built upon the > release and easily uploaded on the website. > The maven-assembly-plugin can be leveraged to reach that goal. > Docker distributions would then reuse this ZIP in order to build the > resulting image. Note that sample configuration will then be centralized to > the APP maven project. -- 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-3261) Provide ZIP distribution for Guice servers application
[ https://issues.apache.org/jira/browse/JAMES-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141618#comment-17141618 ] Benoit Tellier commented on JAMES-3261: --- I'm not in a hurry. I won't invest more time in this then. > Provide ZIP distribution for Guice servers application > -- > > Key: JAMES-3261 > URL: https://issues.apache.org/jira/browse/JAMES-3261 > Project: James Server > Issue Type: Task > Components: guice >Affects Versions: master >Reporter: Benoit Tellier >Assignee: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Today, a user wishing to run a Guice server needs either to compile it > himself, or run it via docker. > Given that (1) we do not expect operators to compile James source code and > given (2) the docker images are so far only built and distributed by some > external suppliers, the operators cannot run the guice servers in a vendor > indepandant way. > As such, in order to promote guice servers adoption, we need to build a ZIP > distribution for them. This ZIP distribution would then be built upon the > release and easily uploaded on the website. > The maven-assembly-plugin can be leveraged to reach that goal. > Docker distributions would then reuse this ZIP in order to build the > resulting image. Note that sample configuration will then be centralized to > the APP maven project. -- 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] (MAILBOX-394) Merge MessageMetaData & MetadataWithMailboxId POJOs
[ https://issues.apache.org/jira/browse/MAILBOX-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed MAILBOX-394. -- Resolution: Won't Fix Within EventBus MailboxEvent serialization, breaking changes would be needed for this cosmetic refactoring. > Merge MessageMetaData & MetadataWithMailboxId POJOs > --- > > Key: MAILBOX-394 > URL: https://issues.apache.org/jira/browse/MAILBOX-394 > Project: James Mailbox > Issue Type: Improvement > Components: api, events >Reporter: Benoit Tellier >Priority: Major > > By adding mailboxId within MessageMetaData, both class content is identical > meaning MetadataWithMailboxId POJO can be removed. > The upgrade should be done with an 'empty' event bus (as JSON structure of > Added and Expunged events is altered with mailboxId field addition). > We will write an upgrade instruction on how to achieve this. -- 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] (MAILBOX-257) Create a tool to re-index documents in search index and recalculate quotas
[ https://issues.apache.org/jira/browse/MAILBOX-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed MAILBOX-257. -- Fix Version/s: (was: 0.6) Resolution: Implemented Quota recomputation had been contributed by [~rcordier] Reindexing is now the generic feature described here. > Create a tool to re-index documents in search index and recalculate quotas > -- > > Key: MAILBOX-257 > URL: https://issues.apache.org/jira/browse/MAILBOX-257 > Project: James Mailbox > Issue Type: Improvement >Affects Versions: 0.6 >Reporter: Benoit Tellier >Priority: Major > > These operations are currently error prone due to the event system : > - Some event can be lost if a James server fails (just after writing to the > data store, but before firing the event ) > - Non CRDT problems with possible event reordering (example with reordering > between message creation and deletion might result in a still present message > ) > - Data loss in the data store : > https://aphyr.com/posts/323-call-me-maybe-elasticsearch-1-5-0 > We should implement a tool that allows us to re-compute this and expose it to > the administrative interface. > Computation can affect all mailboxes (cold fixup / migration) or one specific > mailbox / namespace. -- 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] (MAILBOX-253) Provide the option to use Hystrix on top of all IO operations
[ https://issues.apache.org/jira/browse/MAILBOX-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed MAILBOX-253. -- Resolution: Abandoned This work is abandonned > Provide the option to use Hystrix on top of all IO operations > - > > Key: MAILBOX-253 > URL: https://issues.apache.org/jira/browse/MAILBOX-253 > Project: James Mailbox > Issue Type: New Feature >Reporter: Benoit Tellier >Priority: Major > > Mailbox implementations needed for JAMES-1623 > I introduced a new module for hystrix mailbox. > Implementation is made at the mapper level, and wraps a > MailboxSessionMapperFactory. > Quota stuff is also handled. Idem for Subscriptions and search indexes. -- 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] (MAILBOX-86) Cache MessageMapper.countMessagesInMailbox()
[ https://issues.apache.org/jira/browse/MAILBOX-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed MAILBOX-86. - Resolution: Won't Fix We removed mailbox/cache project as it was unused and unmaintained. > Cache MessageMapper.countMessagesInMailbox() > > > Key: MAILBOX-86 > URL: https://issues.apache.org/jira/browse/MAILBOX-86 > Project: James Mailbox > Issue Type: Improvement >Reporter: Norman Maurer >Assignee: Norman Maurer >Priority: Minor > > We should maybe cache the message count in mailbox to speed up things a bit. > There may be other areas which could cache some data. -- 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] (MAILBOX-303) tests ensuring consistency on mailbox name are broken with cassandra 3
[ https://issues.apache.org/jira/browse/MAILBOX-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed MAILBOX-303. -- Resolution: Fixed These rules are now handled at the manager layer > tests ensuring consistency on mailbox name are broken with cassandra 3 > -- > > Key: MAILBOX-303 > URL: https://issues.apache.org/jira/browse/MAILBOX-303 > Project: James Mailbox > Issue Type: Bug > Components: cassandra >Reporter: Matthieu Baechler >Priority: Major > > When updating to cassandra 3, long mailbox names are not consistent with what > our testsuites expect. -- 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] (MAILBOX-348) MapperProvider don't need to provide AnnotationMapper
[ https://issues.apache.org/jira/browse/MAILBOX-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed MAILBOX-348. -- Resolution: Implemented MapperProvider no longer supplies AnnotationMapper > MapperProvider don't need to provide AnnotationMapper > - > > Key: MAILBOX-348 > URL: https://issues.apache.org/jira/browse/MAILBOX-348 > Project: James Mailbox > Issue Type: Improvement >Reporter: Benoit Tellier >Priority: Major > > This can help to make the tests faster as we can drop the > CassandraAnnotationModule. > This will also simplify code. -- 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-3262) Cannot run fix mailboxes inconsistencies task
[
https://issues.apache.org/jira/browse/JAMES-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141668#comment-17141668
]
Benoit Tellier commented on JAMES-3262:
---
Is there some more clues (like a stacktrace?) about what happened?
> Cannot run fix mailboxes inconsistencies task
> -
>
> Key: JAMES-3262
> URL: https://issues.apache.org/jira/browse/JAMES-3262
> Project: James Server
> Issue Type: Bug
>Reporter: René Cordier
>Priority: Major
>
> Some user reported that when trying to run the fixing mailboxes
> inconsistencies task
> [https://github.com/apache/james-project/blob/master/src/site/markdown/server/manage-webadmin.md#fixing-mailboxes-inconsistencies]
>
> They got this as a response:
> {code:java}
> {
> "statusCode": 500,
> "type": "ServerError",
> "message": "WebAdmin encountered an unexpected internal error",
> "details": null
> }
> {code}
> A first investigation reveals that they might have forgotten to add the
> `{{I-KNOW-WHAT-I-M-DOING}}` header, leading to a 500 response. However, we
> should not return 500 in this case.
>
> *DoD* :
> * Reproduce the error with a unit test
> * fix it: upon missing header we should return 400
> * eventually rework the webadmin documentation to make it more clear that
> this header is needed
--
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] (MAILBOX-398) Backend is responsible of RECENT search
[ https://issues.apache.org/jira/browse/MAILBOX-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141948#comment-17141948 ] Benoit Tellier commented on MAILBOX-398: https://github.com/linagora/james-project/pull/3458 proved the diverging behavior between ElasticSearch VS lucene & scanning implementations We will need to review the validity (which from quotes mentionned above is questionnable) of handling RECENT flags on a per session basis. > Backend is responsible of RECENT search > --- > > Key: MAILBOX-398 > URL: https://issues.apache.org/jira/browse/MAILBOX-398 > Project: James Mailbox > Issue Type: Improvement >Reporter: Benoit Tellier >Priority: Major > > Why? > - A search query should not require stored information to be built -- 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-2541) In order to support distributed deployment, we should write a MailQueue implementation using RabbitMQ
[ https://issues.apache.org/jira/browse/JAMES-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140080#comment-17140080 ] Benoit Tellier commented on JAMES-2541: --- https://issues.apache.org/jira/browse/JAMES-2896 treats about it. Either we close this issue, or we turn JAMES-2896 as a sub issue of this one. > In order to support distributed deployment, we should write a MailQueue > implementation using RabbitMQ > - > > Key: JAMES-2541 > URL: https://issues.apache.org/jira/browse/JAMES-2541 > Project: James Server > Issue Type: Task > Components: Queue >Affects Versions: 3.1.0 >Reporter: Matthieu Baechler >Priority: Major > Fix For: 3.2.0 > > > Default MailQueue for Cassandra/Elasticsearch James product is embedded > ActiveMQ. > After a review of available distributed MQ, we decided that we should support > RabbitMQ to replace ActiveMQ in distributed scenario. > And as we don't want to rely on filesystem for mail content neither, we > decided that only meta-data would go into the MQ and that the raw email would > be stored in a blob-store. > This ticket is supposed to track progress at implementing basic > MailQueueFactoryContract and MailQueueContract on top of RabbitMQ and > blob-store. -- 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-2510) use a consistent artifact naming scheme
[ https://issues.apache.org/jira/browse/JAMES-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140085#comment-17140085 ] Benoit Tellier commented on JAMES-2510: --- Maybe all server artifacts (located in server folder) should come with james-server prefix? By moving back mailbox as a server component we would furthermore be able to re-qualify many sub components (like event sourcing) as server components and let them embrass this scheme. > use a consistent artifact naming scheme > --- > > Key: JAMES-2510 > URL: https://issues.apache.org/jira/browse/JAMES-2510 > Project: James Server > Issue Type: Task > Components: Build System >Affects Versions: 3.1.0 >Reporter: Matthieu Baechler >Priority: Major > > Maven modules have different naming scheme, for example : > * apache-james-* > * james-server-* > * protocols-* > it makes everything hard to read and to find and it's redundant because > groupId already gives context about an artifact. > I'll make a proposal to reduce the noise in our maven files. -- 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-3244) Clarify Listeners Configuration (listeners.xml)
[ https://issues.apache.org/jira/browse/JAMES-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140099#comment-17140099 ] Benoit Tellier commented on JAMES-3244: --- To me too. Listeners are an extension mechanism. > Clarify Listeners Configuration (listeners.xml) > --- > > Key: JAMES-3244 > URL: https://issues.apache.org/jira/browse/JAMES-3244 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3244) Clarify Listeners Configuration (listeners.xml)
[ https://issues.apache.org/jira/browse/JAMES-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140100#comment-17140100 ] Benoit Tellier commented on JAMES-3244: --- You should be able to just delete the file (a WARN log will be emitted) > Clarify Listeners Configuration (listeners.xml) > --- > > Key: JAMES-3244 > URL: https://issues.apache.org/jira/browse/JAMES-3244 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3241) Clarify Extension Configuration (extensions.properties)
[ https://issues.apache.org/jira/browse/JAMES-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140108#comment-17140108 ] Benoit Tellier commented on JAMES-3241: --- +1 > Clarify Extension Configuration (extensions.properties) > --- > > Key: JAMES-3241 > URL: https://issues.apache.org/jira/browse/JAMES-3241 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3232) Clarify Mail Repository Stores Configuration (mailrepositorystore.xml)
[ https://issues.apache.org/jira/browse/JAMES-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140107#comment-17140107 ] Benoit Tellier commented on JAMES-3232: --- The "Basic server" should only expose "file" MailRepository and yes we should hide this, +1 You should be able to start James without this file, a log will be emitted (and we will address this log for basic server separately) > Clarify Mail Repository Stores Configuration (mailrepositorystore.xml) > -- > > Key: JAMES-3232 > URL: https://issues.apache.org/jira/browse/JAMES-3232 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3239) Clarify Logging Configuration (logback.xml & log4j.properties)
[ https://issues.apache.org/jira/browse/JAMES-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140122#comment-17140122 ] Benoit Tellier commented on JAMES-3239: --- I think Operator want to easily tune logging. Unability to do so will get them grumpy. IMO we should keep the logback file event for the basic server. Maybe provide a simple version of it. > Clarify Logging Configuration (logback.xml & log4j.properties) > -- > > Key: JAMES-3239 > URL: https://issues.apache.org/jira/browse/JAMES-3239 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3249) Fix some webadmin documentations errors
[ https://issues.apache.org/jira/browse/JAMES-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier updated JAMES-3249: -- Summary: Fix some webadmin documentations errors (was: Fix documentations errors) > Fix some webadmin documentations errors > --- > > Key: JAMES-3249 > URL: https://issues.apache.org/jira/browse/JAMES-3249 > Project: James Server > Issue Type: Improvement >Reporter: Nguyễn Việt Đức >Priority: Major > > A number of documentation-related issues have been created by the QA team, > this is a meta issue, in order to track them at once: > * DOCUMENT > Task management > Listing tasks query should be updated to > fully form a little fix in webadmin-management.md > * DOCUMENT > Even Dead Letter > Correcting the document idem > * Administrating DLP Configuration > "ReIndexing a user mails" has incorrect > request idem > * DOCUMENT > Administrating mail repositories > returned value example is > incorrect when retrieving email details with Accept header is > "message/rfc822" example fix > * Able to create an alias to non-handle destination domain -- 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-3243) Clarify HealthCheck Configuration (healthcheck.properties)
[ https://issues.apache.org/jira/browse/JAMES-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140102#comment-17140102 ] Benoit Tellier commented on JAMES-3243: --- > I was not able to find any existing documentation about this configuration. > The link provided in the file > (https://james.apache.org/server/config-healthcheck.html) leads to a 404. https://github.com/apache/james-project/blob/master/src/site/xdoc/server/config-healthcheck.xml is the related source code. Current latest Website is not deployed yet, I will redeploy it as part of JAMES-3207 JAMES 3.5.0 release. The healthchecks could be queried as part of WebAdmin REST api, even outside docker. The idea of course is to offer some liveness probes for running James in Kubernetes. This file "just" controls the frequency at wich helthchecks logs are emmitted. > However, we could simply *tell* the Operator how it works without providing a > configuration option. We could therefore eliminate the configuration for this > feature for the Basic Server. +1 In the context of the Basic server we can safely not specify this file. (And the classic WARN will be emitted but let's fix that in another issue). > Clarify HealthCheck Configuration (healthcheck.properties) > -- > > Key: JAMES-3243 > URL: https://issues.apache.org/jira/browse/JAMES-3243 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3230) Clarify JMAP Configuration (jmap.properties)
[ https://issues.apache.org/jira/browse/JAMES-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140104#comment-17140104 ] Benoit Tellier commented on JAMES-3230: --- Yes I agree. There is so far no JPA support for JMAP anyway. Hence this configuration file makes little sense in the first place. To be exposed on the basic server we would need JPA support, & a final RFC-8621 JMAP implementation (& not today draft) > Clarify JMAP Configuration (jmap.properties) > > > Key: JAMES-3230 > URL: https://issues.apache.org/jira/browse/JAMES-3230 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3235) Clarify Recipient Rewrite Table Configuration (recipientrewritetable.xml)
[ https://issues.apache.org/jira/browse/JAMES-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140116#comment-17140116 ] Benoit Tellier commented on JAMES-3235: --- This file only present technical details orthogonal to the rewritting feature: not including it won't break anything (just a log will be emitted but let's adress this separately). I do think that documentation for some Recipent Table Rewriting rules could make sense for the basic server. I'm thinking to Alias, DomainAlias, Forward & Group mappings. But the configuration file is definitly uneeded. > Clarify Recipient Rewrite Table Configuration (recipientrewritetable.xml) > - > > Key: JAMES-3235 > URL: https://issues.apache.org/jira/browse/JAMES-3235 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3234) Clarify POP3 Configuration (pop3server.xml)
[ https://issues.apache.org/jira/browse/JAMES-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140112#comment-17140112 ] Benoit Tellier commented on JAMES-3234: --- +1 I propose nonetheless to document it "opt-in" for the basic server. > Clarify POP3 Configuration (pop3server.xml) > --- > > Key: JAMES-3234 > URL: https://issues.apache.org/jira/browse/JAMES-3234 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3229) Clarify IMAP Configuration (imapserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140139#comment-17140139 ] Benoit Tellier commented on JAMES-3229: --- Well we still have the SSL configuration issue (keystore). So far we rely on provided defaults which is unsecure. So I prefer having a configuration file where I could just update the keystore used by IMAP in the basic server. (So removing all the values not related to port binding and keystore.) A long term solution would be to have : - 1/ A easy keystore generation script - 2/ From keystore setting let the basic server deduce the IMAP configuration (which would then not need to be provided) - 3/ This requires reworking the IMAP configuration in order to get a POJO representing it and thus be able to have several generation mechanisms for it. > Clarify IMAP Configuration (imapserver.xml) > --- > > Key: JAMES-3229 > URL: https://issues.apache.org/jira/browse/JAMES-3229 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3236) Clarify SMTP Configuration (smtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140140#comment-17140140 ] Benoit Tellier commented on JAMES-3236: --- Well we still have the SSL configuration issue (keystore). So far we rely on provided defaults which is unsecure. So I prefer having a configuration file where I could just update the keystore used by SMTP in the basic server. (So removing all the values not related to port binding and keystore.) A long term solution would be to have : - 1/ A easy keystore generation script - 2/ From keystore setting let the basic server deduce the SMTP configuration (which would then not need to be provided) - 3/ This requires reworking the SMTP configuration in order to get a POJO representing it and thus be able to have several generation mechanisms for it. > Clarify SMTP Configuration (smtpserver.xml) > --- > > Key: JAMES-3236 > URL: https://issues.apache.org/jira/browse/JAMES-3236 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3242) Clarify JWT Configuration (jwt_publickey)
[ https://issues.apache.org/jira/browse/JAMES-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140141#comment-17140141 ] Benoit Tellier commented on JAMES-3242: --- Given that the basic server will not ship JM%AP & webadmin you can safely get rid of this file. > Clarify JWT Configuration (jwt_publickey) > - > > Key: JAMES-3242 > URL: https://issues.apache.org/jira/browse/JAMES-3242 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-2394) Re-organize configure section
[
https://issues.apache.org/jira/browse/JAMES-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140147#comment-17140147
]
Benoit Tellier commented on JAMES-2394:
---
One "big" problem we have today is that a given documentation files is relevant
for several servers.
We end up saying "ah and euh this configuration is not applicable for you".
I think we need to completly avoid that sheme again for the new documentation
and we should get it adressed with the file hierarchy. I propose:
{code:java}
- Basic Server (see relevant JIRA for file inclusion/exclusion - we don't
document all possible values)
- imapServer.xml
- smtpServer.xml
- mailetContainer.xml (optional, should be oriented toward use cases like
specifying an SMTP gateway, DKIM/SPF records. Maybe we should be exposing some
templates here)
- logback.xml
- Advanced Server [Today configuration documentation, centered on the advanced
server (remove unrelevant documentation entries), organized the way you
proposed it]
- Core components:
- Domain list
- DNS
- Mailet containet
- MailRepositoryStore
- RRT
- Protocols
- SMTP/LMTP
- IMAP4
- POP3
- FetchMail
- Sieve
- Backend specific configuration
- JPA postgrey
- Guice specific configuration
- listeners
- How to...
- Anti-Spam
- Dizstributed Server [Today configuration documentation, centered on the
advanced server (remove unrelevant documentation entries), organized the way
you proposed it]
{code}
Let's skip Spring documentation for now IMO.
> Re-organize configure section
> -
>
> Key: JAMES-2394
> URL: https://issues.apache.org/jira/browse/JAMES-2394
> Project: James Server
> Issue Type: New Feature
> Components: configuration, Documentation
>Reporter: Benoit Tellier
>Priority: Major
>
> I would like to propose to re-organize `configure` section of James website.
> Currently, many pages about many different topics are mixed together, making
> it hard to differenciate the various topics.
> Also the current navigation menu do not reflect well the impact of wiring on
> the configuration: some components are only available under some packagings,
> and thus their configuration is wiring solution specific.
> I'd like to subdivide this section into:
> {code:java}
> - Core components:
> - Domain list
> - DNS
> - Mailet containet
> - MailRepositoryStore
> - RRT
> - Protocols
> - SMTP/LMTP
> - IMAP4
> - POP3
> - FetchMail
> - Sieve
> - Backend specific configuration
> - ElasticSearch
> - Cassandra
> - JPA postgrey
> - Spring specific configuration
> - mailbox
> - events
> - quota
> - Guice specific configuration
> - listeners
> - How to...
> - Anti-Spam
> {code}
> We are also missing config about... Tika, WebAdmin, JMAP, JMX, indexer...
> This new organisation will allow adding them in the corresponding sections.
--
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-3210) Handle Return-Path header in DSNBounce mailet
[ https://issues.apache.org/jira/browse/JAMES-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140197#comment-17140197 ] Benoit Tellier commented on JAMES-3210: --- https://github.com/linagora/james-project/pull/3446 JAMES-3210 add integration tests to verify that the bounce is sent to the sender & https://github.com/linagora/james-project/pull/3441 [Refactoring] Refactor BounceIntegrationTest Are merged. > Handle Return-Path header in DSNBounce mailet > - > > Key: JAMES-3210 > URL: https://issues.apache.org/jira/browse/JAMES-3210 > Project: James Server > Issue Type: Bug > Components: Matchers/Mailets (bundled) >Affects Versions: 3.5.0 >Reporter: Rémi Kowalski >Priority: Major > > ``` > At the origin of the complain: > ``` > This message was created automatically by mail delivery software. > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > 0102016ca8bd7b6d-b28772f6-6c71-4676-8834-c48740efb2a8-000...@eu-west-1.amazonses.com > (generated from > SRS0=78Gj=WP=eu-west-1.amazonses.com=0102016ca8bd7b6d-b28772f6-6c71-4676-8834-c48740efb2a8-000...@ik2.com) > host feedback-smtp.eu-west-1.amazonses.com [54.239.37.176] > SMTP error from remote mail server after end of data: > 554 DSN is not RFC 3464 compliant. MSGID: (FleYRCEogpaDtH6q8Ml2-1): > The DSN MUST be addressed (in both the message header and the transport > envelope) to the return address from the transport envelope which accompanied > the original message for which the DSN was generated. > https://tools.ietf.org/html/rfc3464 > ``` > DOD: > handle the Return-Path header in the DSNBounce mailet and add an integration > test -- 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-3223) Bump guava and bean-utils to fix vulnerability
[ https://issues.apache.org/jira/browse/JAMES-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140198#comment-17140198 ] Benoit Tellier commented on JAMES-3223: --- https://github.com/linagora/james-project/pull/3445 on ferme? > Bump guava and bean-utils to fix vulnerability > -- > > Key: JAMES-3223 > URL: https://issues.apache.org/jira/browse/JAMES-3223 > Project: James Server > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Rémi Kowalski >Priority: Major > > h5. [CVE-2018-10237|https://github.com/advisories/GHSA-mvr2-9pj6-7w5j] > moderate severity > *Vulnerable versions:* > 11.0, < 24.1.1 > *Patched version:* 24.1.1 > Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 > allows remote attackers to conduct denial of service attacks against servers > that depend on this library and deserialize attacker-provided data, because > the AtomicDoubleArray class (when serialized with Java serialization) and the > CompoundOrdering class (when serialized with GWT serialization) perform eager > allocation without appropriate checks on what a client has sent and whether > the data size is reasonable. > h5. [CVE-2019-10086|https://github.com/advisories/GHSA-6phf-73q6-gh87] > high severity > *Vulnerable versions:* < 1.9.4 > *Patched version:* 1.9.4 > In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added > which allows suppressing the ability for an attacker to access the > classloader via the class property available on all Java objects. We, however > were not using this by default characteristic of the PropertyUtilsBean. -- 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] [Comment Edited] (JAMES-3223) Bump guava and bean-utils to fix vulnerability
[ https://issues.apache.org/jira/browse/JAMES-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140198#comment-17140198 ] Benoit Tellier edited comment on JAMES-3223 at 6/19/20, 4:17 AM: - https://github.com/linagora/james-project/pull/3445 is merged was (Author: btellier): https://github.com/linagora/james-project/pull/3445 on ferme? > Bump guava and bean-utils to fix vulnerability > -- > > Key: JAMES-3223 > URL: https://issues.apache.org/jira/browse/JAMES-3223 > Project: James Server > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Rémi Kowalski >Priority: Major > > h5. [CVE-2018-10237|https://github.com/advisories/GHSA-mvr2-9pj6-7w5j] > moderate severity > *Vulnerable versions:* > 11.0, < 24.1.1 > *Patched version:* 24.1.1 > Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 > allows remote attackers to conduct denial of service attacks against servers > that depend on this library and deserialize attacker-provided data, because > the AtomicDoubleArray class (when serialized with Java serialization) and the > CompoundOrdering class (when serialized with GWT serialization) perform eager > allocation without appropriate checks on what a client has sent and whether > the data size is reasonable. > h5. [CVE-2019-10086|https://github.com/advisories/GHSA-6phf-73q6-gh87] > high severity > *Vulnerable versions:* < 1.9.4 > *Patched version:* 1.9.4 > In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added > which allows suppressing the ability for an attacker to access the > classloader via the class property available on all Java objects. We, however > were not using this by default characteristic of the PropertyUtilsBean. -- 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-3213) Enrich contact auto completion mailet pipeline with replyTo field
[ https://issues.apache.org/jira/browse/JAMES-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140200#comment-17140200 ] Benoit Tellier commented on JAMES-3213: --- https://github.com/linagora/james-project/pull/3438 is merged. > Enrich contact auto completion mailet pipeline with replyTo field > - > > 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 a third party sends an ITIP request to the CardAV server to handle > realtime update. > To achieve that, the third party send a message to James which output > received events to an AMQP channel that could be consumed by a CardAV server. > In the mean time James enrich the event sent to this server. > If the sender email does not exist in the list attendee, the CardAV ITIP > broker will add him to the attendee list. > This is not correct in cases: > * When an external attendee accept the event, the notification email should > send from the third party system > ([no-re...@example.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-3231) Clarify LMAP Configuration (lmtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140111#comment-17140111 ] Benoit Tellier commented on JAMES-3231: --- Are you speaking of LMTP ? Because LMAP is unknown to me. I agree to hide LMTP by default but we should document as part of the basic server how to document it "opt-in". > Clarify LMAP Configuration (lmtpserver.xml) > --- > > Key: JAMES-3231 > URL: https://issues.apache.org/jira/browse/JAMES-3231 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3237) Clarify Users Configuration (usersrepository.xml)
[ https://issues.apache.org/jira/browse/JAMES-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140118#comment-17140118 ] Benoit Tellier commented on JAMES-3237: --- Yes, we should. Embedded database for storing user sounds like a nice idea for the basic server, and sane defaults could be provided for it. Not specifying this configuration file should work. (there will be a warning log) > Clarify Users Configuration (usersrepository.xml) > - > > Key: JAMES-3237 > URL: https://issues.apache.org/jira/browse/JAMES-3237 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3233) Clarify Mailet Container Configuration (mailetcontainer.xml)
[ https://issues.apache.org/jira/browse/JAMES-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140130#comment-17140130 ] Benoit Tellier commented on JAMES-3233: --- Yes we are providing sane defaults when the file is missing. That configuration might need to be refreshed (for instance `server/container/guice/jpa-guice/src/main/resources/defaultMailetContainer.xml` do not allow relay for emails generated by the mailet pipeline, rrt errors are not well managed, bcc-stripping errors too, some metrics are not positioned, the spam processor is useless). Given that we refresh it, it should be doing the job, not providing the file will do the trick (and we will get the unfamous warn log ^^) > Clarify Mailet Container Configuration (mailetcontainer.xml) > > > Key: JAMES-3233 > URL: https://issues.apache.org/jira/browse/JAMES-3233 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3233) Clarify Mailet Container Configuration (mailetcontainer.xml)
[ https://issues.apache.org/jira/browse/JAMES-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140131#comment-17140131 ] Benoit Tellier commented on JAMES-3233: --- I wonder however 'if' in some use cases even a "Basic server user" should touch this file: for instance if you rely on a SMTP gateway (could be an easy solution for "trust"). I wonder to what extent what I said above is valid. Maybe we can think of a more concise format for "BasicServer" mailet configuration, but it will require significant work (Represent the configuration as a POJO should enable us to generate it from several "models", we would be able to define a simplified format for it fitting basic server needs. > Clarify Mailet Container Configuration (mailetcontainer.xml) > > > Key: JAMES-3233 > URL: https://issues.apache.org/jira/browse/JAMES-3233 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3246) Clarify DB Configuration (james-database.properties & META-INF/persistence.xml)
[ https://issues.apache.org/jira/browse/JAMES-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140142#comment-17140142 ] Benoit Tellier commented on JAMES-3246: --- I must admit I am less knowledgeable on this file. Can we get rid of it? I +1 the fact of not exposing it! > Clarify DB Configuration (james-database.properties & > META-INF/persistence.xml) > --- > > Key: JAMES-3246 > URL: https://issues.apache.org/jira/browse/JAMES-3246 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3236) Clarify SMTP Configuration (smtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140148#comment-17140148 ] Benoit Tellier commented on JAMES-3236: --- My comment long term proposition relates to JAMES-2335 > Clarify SMTP Configuration (smtpserver.xml) > --- > > Key: JAMES-3236 > URL: https://issues.apache.org/jira/browse/JAMES-3236 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3229) Clarify IMAP Configuration (imapserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140149#comment-17140149 ] Benoit Tellier commented on JAMES-3229: --- My comment long term proposition relates to JAMES-2335 > Clarify IMAP Configuration (imapserver.xml) > --- > > Key: JAMES-3229 > URL: https://issues.apache.org/jira/browse/JAMES-3229 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3248) Eliminate log warnings
[ https://issues.apache.org/jira/browse/JAMES-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140179#comment-17140179 ] Benoit Tellier commented on JAMES-3248: --- I deally, we should be able to create a separate application for the BasicSearch and overload guice injections for these configurations, in order to remove that warning log. I propose it as a middle term solution. > Eliminate log warnings > -- > > Key: JAMES-3248 > URL: https://issues.apache.org/jira/browse/JAMES-3248 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > Warnings generated in the logs should be ideally completely eliminated, as it > creates anxiety for the Basic Operator and is bad for mental health. ;) > I will post the warnings here one by one so we can figure out how to deal > with each of them (simple resolution, or something that requires a separate > issue). -- 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-3231) Clarify LMTP Configuration (lmtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140178#comment-17140178 ] Benoit Tellier commented on JAMES-3231: --- I propose that we don't put the configuration file but if the operator specifies it we would take it into account. > Clarify LMTP Configuration (lmtpserver.xml) > --- > > Key: JAMES-3231 > URL: https://issues.apache.org/jira/browse/JAMES-3231 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- 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-3184) Concurrency for consistency tasks
[ https://issues.apache.org/jira/browse/JAMES-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140196#comment-17140196 ] Benoit Tellier commented on JAMES-3184: --- https://github.com/linagora/james-project/pull/3449 limited the concurrency before throttling to generate the entries to reindex. > Concurrency for consistency tasks > - > > Key: JAMES-3184 > URL: https://issues.apache.org/jira/browse/JAMES-3184 > Project: James Server > Issue Type: Improvement >Reporter: Lan Khuat >Priority: Major > Fix For: 3.6.0 > > > We currently limit concurrency of consistency tasks to 1 in order to avoid > unbounded concurrency. > When running a consistency task, an admin should be able to precise the > concurrency he wishes to use. > To do so, each task will expose (optional) concurrency parameters, that an > admin can provide via query parameters of the corresponding webadmin > endpoints. > * RecomputeUserFastViewProjectionItems > * RecomputeCurrentQuotas > * RecomputeMailboxCounters > * SolveMailboxInconsistencies > * SolveMessageInconsistencies > * FullReindexing > * UserReindexing > * SingleMailboxReindexing > * ErrorRecoveryReindexation -- 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-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140195#comment-17140195
]
Benoit Tellier commented on JAMES-3214:
---
https://github.com/apache/james-project/pull/210 solved it.
Given that test dependencies are no longer present in released artifacts,
should we consider this done?
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JAMES-3248) Eliminate log warnings
[ https://issues.apache.org/jira/browse/JAMES-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140216#comment-17140216 ] Benoit Tellier commented on JAMES-3248: --- > To start, there is lots of "INFO" chatter that is not necessary. Maybe the "Basic Server operator" just needs to be aware of warnings & error, we can increase the logging level. We will need to better refine the "Basic server" application and split it from the advanced server one. Once we do it, we should be able to address all warnings & errors related to configuration. We "may" put to the INFO level like org.apache.james.GuiceJamesServer I believe a couples of annoying logs you mentioned should be addressed for all James server distributions. > [ERROR] o.a.j.d.l.AbstractDomainList - Cannot get IP address(es) for Domain : > localhost We can easily fix that one with a switch of default value. I will contribute this. > [WARN ] o.a.j.t.m.r.d.DelaysAndMaxRetry - Delay of 8 minutes 20 seconds is > now attempted: 1 times This one is a badly configured default file, it should get fixed too. I will have a look > james_1 | java.lang.IllegalStateException: Lookup of localhost A isn't done > I would like to have a look at that one too. Can you detail me ? > [WARN ] o.a.j.m.i.JamesMailetContext - The specified postmaster address ( > postmas...@james.minet.net ) is not a local address. Let's remove this (stupid) default value... > james_1 | 04:25:13.144 [WARN ] o.a.a.b.BrokerService - Memory Usage for the > Broker (1024mb) is more than the maximum available for the JVM: 986 mb - > resetting to 70% of maximum available: 690 mb > james_1 | 04:25:13.537 [WARN ] o.a.a.b.BrokerService - Store limit is 102400 > mb (current store usage is 0 mb). The data directory: > /opt/apache-james/james-server/var/store/activemq/brokers/KahaDB only has > 49438 mb of usable space. - resetting to maximum available disk space: 49438 > mb > james_1 | 04:25:13.539 [WARN ] o.a.a.b.BrokerService - Temporary Store limit > is 51200 mb (current store usage is 0 mb). The data directory: > /opt/apache-james/james-server/var/store/activemq/brokers only has 49437 mb > of usable space. - resetting to maximum available disk space: 49437 mb I don't know which setting we should tune to get rid of this. We maybe should have a look. > WARN [main] openjpa.Runtime - Could not create the optional validation > provider. Reason returned: "A default ValidatorFactory could not be created." :-( I'm a JPA noob, can't help for that one! > james_1 | 04:25:21.596 [ERROR] o.a.j.m.l.AbstractStateMailetProcessor - > Unable to init mailet ro.ieugen.sample.mailets.LogAndDoNothingMailet > james_1 | java.lang.ClassNotFoundException: > ro.ieugen.sample.mailets.LogAndDoNothingMailet That one hopefully is not James server fault ^^ > Eliminate log warnings > -- > > Key: JAMES-3248 > URL: https://issues.apache.org/jira/browse/JAMES-3248 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > Warnings generated in the logs should be ideally completely eliminated, as it > creates anxiety for the Basic Operator and is bad for mental health. ;) > I will post the warnings here one by one so we can figure out how to deal > with each of them (simple resolution, or something that requires a separate > issue). -- 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-3252) Cannot get IP address(es) for Domain : localhost
[ https://issues.apache.org/jira/browse/JAMES-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140247#comment-17140247 ] Benoit Tellier commented on JAMES-3252: --- https://github.com/apache/james-project/pull/213 is an attempt to address this by turning auto detection to false by default. Also I took this opportunity to clean up default files. > Cannot get IP address(es) for Domain : localhost > > > Key: JAMES-3252 > URL: https://issues.apache.org/jira/browse/JAMES-3252 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > > [ERROR] o.a.j.d.l.AbstractDomainList - Cannot get IP address(es) for Domain > >: localhost > We can easily fix that one with a switch of default value. I will contribute > this. -- 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-3255) The specified postmaster address ( postmas...@james.minet.net ) is not a local address
[ https://issues.apache.org/jira/browse/JAMES-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140255#comment-17140255 ] Benoit Tellier commented on JAMES-3255: --- https://github.com/apache/james-project/pull/214 changes this default value to postmaster@localhost eventually addressing this issue > The specified postmaster address ( postmas...@james.minet.net ) is not a > local address > -- > > Key: JAMES-3255 > URL: https://issues.apache.org/jira/browse/JAMES-3255 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > > [WARN ] o.a.j.m.i.JamesMailetContext - The specified postmaster address ( > >postmas...@james.minet.net ) is not a local address. > Let's remove this (stupid) default value... -- 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-3253) Delay of 8 minutes 20 seconds is now attempted
[ https://issues.apache.org/jira/browse/JAMES-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140266#comment-17140266 ] Benoit Tellier commented on JAMES-3253: --- https://github.com/apache/james-project/pull/215 is an attempt to solve this > Delay of 8 minutes 20 seconds is now attempted > -- > > Key: JAMES-3253 > URL: https://issues.apache.org/jira/browse/JAMES-3253 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > > [WARN ] o.a.j.t.m.r.d.DelaysAndMaxRetry - Delay of 8 minutes 20 seconds is > >now attempted: 1 times > This one is a badly configured default file, it should get fixed too. I will > have a look -- 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-3254) Lookup of localhost A isn't done
[ https://issues.apache.org/jira/browse/JAMES-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140279#comment-17140279 ] Benoit Tellier commented on JAMES-3254: --- https://github.com/apache/james-project/pull/216 is an attempt to fix this. Rational: google dns (default supplied configuration!) do not know which IP is localhost. I cleaned it. > Lookup of localhost A isn't done > > > Key: JAMES-3254 > URL: https://issues.apache.org/jira/browse/JAMES-3254 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > > james_1 | java.lang.IllegalStateException: Lookup of localhost A isn't done > > > I would like to have a look at that one too. Can you detail me ? -- 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-2510) use a consistent artifact naming scheme
[ https://issues.apache.org/jira/browse/JAMES-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140282#comment-17140282 ] Benoit Tellier commented on JAMES-2510: --- +1 > I also have in mind some refactoring of the source tree but I'll put that in > another ticket. Please do. Some refactorings might require project level decisions (like moving mailbox folder as a server sub-folder) > use a consistent artifact naming scheme > --- > > Key: JAMES-2510 > URL: https://issues.apache.org/jira/browse/JAMES-2510 > Project: James Server > Issue Type: Task > Components: Build System >Affects Versions: 3.1.0 >Reporter: Matthieu Baechler >Priority: Major > > Maven modules have different naming scheme, for example : > * apache-james-* > * james-server-* > * protocols-* > it makes everything hard to read and to find and it's redundant because > groupId already gives context about an artifact. > I'll make a proposal to reduce the noise in our maven files. -- 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-3278) Simplify POP3 Configuration
[ https://issues.apache.org/jira/browse/JAMES-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144671#comment-17144671 ] Benoit Tellier commented on JAMES-3278: --- https://issues.apache.org/jira/browse/JAMES-2335 would make introducing such a specific configuration possible. > Simplify POP3 Configuration > --- > > Key: JAMES-3278 > URL: https://issues.apache.org/jira/browse/JAMES-3278 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, it has been decided (ref??) that POP3 > will be an included feature, but will be disabled by default. > The current mechanism by which POP3 is configured is questionable in this > context because: > * It exposes a lot of technical details that are not appropriate for a Basic > Operator > * It seems to require a lot of unnecessary configurations (to be discussed) > * It mixes in the security (SSL) concern, which is another large and > important issue > * It is in XML 冷 > We should determine how this configuration can be made more > "Operator-friendly". > > (Note: we do not expect to work on this immediately. This is more of a > placeholder for later work once an initial version of the Basic Server has > been released.) -- 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-3253) Delay of 8 minutes 20 seconds is now attempted
[ https://issues.apache.org/jira/browse/JAMES-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144672#comment-17144672 ] Benoit Tellier commented on JAMES-3253: --- Can you run `cat conf/mailetcontainer.xml` ? > Delay of 8 minutes 20 seconds is now attempted > -- > > Key: JAMES-3253 > URL: https://issues.apache.org/jira/browse/JAMES-3253 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > > [WARN ] o.a.j.t.m.r.d.DelaysAndMaxRetry - Delay of 8 minutes 20 seconds is > >now attempted: 1 times > This one is a badly configured default file, it should get fixed too. I will > have a look -- 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-3265) Investigate Slow IMAP SELECT (26 minutes +)
[
https://issues.apache.org/jira/browse/JAMES-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3265.
-
Resolution: Fixed
All mentionned PR are merged
> Investigate Slow IMAP SELECT (26 minutes +)
> ---
>
> Key: JAMES-3265
> URL: https://issues.apache.org/jira/browse/JAMES-3265
> Project: James Server
> Issue Type: Task
> Components: cassandra, IMAPServer
>Affects Versions: master
>Reporter: Benoit Tellier
>Priority: Major
> Labels: perf
> Fix For: 3.6.0
>
> Attachments: Capture_d_écran_de_2020-06-22_11-42-01.png,
> Capture_d_écran_de_2020-06-22_11-48-28.png
>
>
> Using glowroot APM on Linagora run instances, I noticed some select commands
> takes around 20 minutes.
> A performance review shows thousands of MODSEQ updates undermines the
> performance.
> {code:java}
> Transaction type: IMAP
> Transaction name: IMAP processor :
> org.apache.james.imap.processor.SelectProcessor
> Start: 2020-06-22 2:28:04.433 am (+07:00)
> Duration: 1,618,718.3 milliseconds
> {code}
> I noticed a high allocation of new ModSeq (28.000 instead of 1) due to uid
> set disjonction.
> I believe a solution would be to implement a new MessageMapper method:
> Mono removeRecentFlags(Mailbox mbox);
> That would enable some Cassandra query optimizations...
> # DOD
> - unlock significant performance improvments for such queries (x100)
> Attached you will find the query stats and flame graph backing up the
> analysis.
--
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-3253) Delay of 8 minutes 20 seconds is now attempted
[ https://issues.apache.org/jira/browse/JAMES-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144697#comment-17144697 ] Benoit Tellier commented on JAMES-3253: --- Oki I found some more! > Delay of 8 minutes 20 seconds is now attempted > -- > > Key: JAMES-3253 > URL: https://issues.apache.org/jira/browse/JAMES-3253 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > > [WARN ] o.a.j.t.m.r.d.DelaysAndMaxRetry - Delay of 8 minutes 20 seconds is > >now attempted: 1 times > This one is a badly configured default file, it should get fixed too. I will > have a look -- 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-3253) Delay of 8 minutes 20 seconds is now attempted
[ https://issues.apache.org/jira/browse/JAMES-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144698#comment-17144698 ] Benoit Tellier commented on JAMES-3253: --- Here we go https://github.com/apache/james-project/pull/224 > Delay of 8 minutes 20 seconds is now attempted > -- > > Key: JAMES-3253 > URL: https://issues.apache.org/jira/browse/JAMES-3253 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > > [WARN ] o.a.j.t.m.r.d.DelaysAndMaxRetry - Delay of 8 minutes 20 seconds is > >now attempted: 1 times > This one is a badly configured default file, it should get fixed too. I will > have a look -- 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-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=17139183#comment-17139183 ] Benoit Tellier commented on JAMES-3225: --- > I would love for us to have a community call and discuss what we want out of > this and setup how we are going to approach the move. This is to align our objectives and get to a common ground on this important issue. +1 (but we would need to take notes and make them public) > Please ask internally what Linagora is willing to offer. Note that this could take some time :-) > 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] [Commented] (JAMES-3219) Clarify DNS configuration (dnsservice.xml)
[ https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139191#comment-17139191 ] Benoit Tellier commented on JAMES-3219: --- > If the system uses dnsjava, then is this configuration file only there to > configure dnsjava? Yes > Looking at dnsjava, there are quite a few configuration parameters available. > This is exactly the type of thing that, if possible, I would like to > eliminate from the Basic Server. +1 dnsjava should so far rely on system defaults in the basic server. (dnsjava is usefull to read MX & TXT records, for mail purposes, not only do dns resolution) > Clarify DNS configuration (dnsservice.xml) > -- > > Key: JAMES-3219 > URL: https://issues.apache.org/jira/browse/JAMES-3219 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > I would like to provide a little more detailed documentation for the DNS > service, since users are required to configure this service (or use the > default config) in order to run the James Local Server. -- 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-3228) Allow me to resolve JIRA issues
[ https://issues.apache.org/jira/browse/JAMES-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139196#comment-17139196 ] Benoit Tellier commented on JAMES-3228: --- I David, Either commiter or PMC responsibility is needed to close other people JIRA. For the time being , you can tag me there, I will close it for you. If not you can ask on server-dev. Cheers, Benoit > Allow me to resolve JIRA issues > --- > > Key: JAMES-3228 > URL: https://issues.apache.org/jira/browse/JAMES-3228 > Project: James Server > Issue Type: Wish >Reporter: David Leangen >Priority: Minor > > I am not able to change the resolution of JIRA issues. -- 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-3227) Can't assign JIRA issues to myself
[ https://issues.apache.org/jira/browse/JAMES-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139156#comment-17139156 ] Benoit Tellier commented on JAMES-3227: --- Hi david. After reading https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization I believe that all was needed was granting you to the contributor role on our specific project. I just did it. > Can't assign JIRA issues to myself > -- > > Key: JAMES-3227 > URL: https://issues.apache.org/jira/browse/JAMES-3227 > Project: James Server > Issue Type: Bug >Reporter: David Leangen >Priority: Minor > > I am not able to assign JIRA issues to myself. -- 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-3227) Can't assign JIRA issues to myself
[ https://issues.apache.org/jira/browse/JAMES-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139157#comment-17139157 ] Benoit Tellier commented on JAMES-3227: --- Can you see if this solved it? Otherwize I will have to ask INFRA... > Can't assign JIRA issues to myself > -- > > Key: JAMES-3227 > URL: https://issues.apache.org/jira/browse/JAMES-3227 > Project: James Server > Issue Type: Bug >Reporter: David Leangen >Priority: Minor > > I am not able to assign JIRA issues to myself. -- 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-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=17138991#comment-17138991 ] Benoit Tellier commented on JAMES-3225: --- > With my Apache hat on: +1 The current situation is not acceptable. > ASF does accept donations. After having read the page you linked it looks we could be working on the following solution: Linagora donates (most of) our current CI infrastructure so that we could build everything on Apache GitHub repository the way we currently do on Linagora one. Of course we would have to : - Ensure we could run current build & test suite. (Can we launch docker containers on Apache Jenkins CI?) - Of course discuss this internally. There might be some legal aspects... We won't get the 20 minute build but we could be working on progressive improvements for it. And we would be more open. I agree to defend this option. > 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] [Commented] (JAMES-2535) Add declaration order checks to checkstyle
[ https://issues.apache.org/jira/browse/JAMES-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139016#comment-17139016 ] Benoit Tellier commented on JAMES-2535: --- This is not addressed. I wonder if any one is willing to dedicate time to this. > Add declaration order checks to checkstyle > -- > > Key: JAMES-2535 > URL: https://issues.apache.org/jira/browse/JAMES-2535 > Project: James Server > Issue Type: Task >Reporter: Jean Helou >Priority: Minor > > Currently checkstyle doesn't check the declaration order of various class > components. This was made quite clear by > [https://github.com/linagora/james-project/pull/1681#discussion_r212547046] > The default checkstyle rules do not include a rule which would make such a > check possible but the incubator project for checkstyle > ([http://sevntu-checkstyle.github.io/sevntu.checkstyle/)] > I tried to add it but finding the correct order is not trivial and is quickly > escaping the scope of my current goal hence the issue. > Note that configuring this checkstyle for > [intellij|https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/How-to-use-SevNTU-Checkstyle-in-Intellij-IDEA] > and > [netbeans|https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/How-to-use-SevNTU-Checkstyle-in-NetBeans] > requires some additional efforts. Eclipse can be made to use a specfic > checkstyle plugin > Note that configuring this checkstyle for > [sonar|[https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/How-to-integrate-sevntu-checks-into-SonarQubeTM-(user's-guide)]] > requires some additional efforts > -- 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-2586) Implement a Postgres-specific backend
[ https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139010#comment-17139010 ] Benoit Tellier commented on JAMES-2586: --- > We also have github and this creates duplication and we should discuss this > in another thread. In my opinion github should be limited to reviewing code. So I see little overlap. > I think ideas should be discussed on the mailing list. +1 I just want to add nuance. Browsing mailing list to retrieve things could be harder than JIRA tickets where you can link things together, rely on components, label things, etc... Maybe the right thing to do is leverage our tooling to allow both of your goals to be achievable. Maybe we could introduce a 'label' for long term propositions that could easily be filtered in & out ? > Implement a Postgres-specific backend > - > > Key: JAMES-2586 > URL: https://issues.apache.org/jira/browse/JAMES-2586 > Project: James Server > Issue Type: New Feature >Reporter: Matthieu Baechler >Priority: Major > > James has a JPA implementation of most interfaces that allows to deploy it on > top of some popular RDBMS. > However, while useful for some kind of applications, ORM are usually a bad > fit for applications requiring high performance like a mail server. > As an abstraction, it also prevents from using advanced features of a given > RDBMS. > For most usages, James would probably run great on top of Postgres, given > that we use advanced features to implement search, for example. > A good strategy would be to implement all interfaces implemented by JPA with > a modern Postgres driver. -- 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-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139018#comment-17139018 ] Benoit Tellier commented on JAMES-3226: --- > We should have documentation for every release we make. > This is important since people don't upgrade immediately after release and > might use an older release for some time. That is in my opinion the biggest limitation of the current website, yes. > or publish them for download next to it. +1 > This way we can keep only the latest 1-3 versions online. IMO should be more than one. > Provide a process around documentation publishing and deployment > > > Key: JAMES-3226 > URL: https://issues.apache.org/jira/browse/JAMES-3226 > Project: James Server > Issue Type: Sub-task >Reporter: Ioan Eugen Stan >Assignee: Ioan Eugen Stan >Priority: Major > > We have started working on the documentation and it's great. > We should also document the processes around documentation: > - when we publish the docs > - how to publish the docs > - where to publish the docs > - when we retire old docs ?! > This task should aggregate discussion and decisions. > The process should be written as asciidoc. > We decided to use antora as a documentation system so the features are going > to depend on that technology. > We should have documentation for every release we make. > This is important since people don't upgrade immediately after release and > might use an older release for some time. > I'm not sure if the documentation for all versions should be online. > We can build zip archives of each documentation release and include it in the > binary release or publish them for download next to it. > This way we can keep only the latest 1-3 versions online. -- 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-2410) Column name 'KEY' in JPAMailboxAnnotation not allowed by SQL Server
[
https://issues.apache.org/jira/browse/JAMES-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139022#comment-17139022
]
Benoit Tellier commented on JAMES-2410:
---
The fix (changing the column name) is relatively easy.
However the data migration part is more tricky.
> Column name 'KEY' in JPAMailboxAnnotation not allowed by SQL Server
> ---
>
> Key: JAMES-2410
> URL: https://issues.apache.org/jira/browse/JAMES-2410
> Project: James Server
> Issue Type: Bug
> Components: mailbox
>Affects Versions: 3.0-beta4
> Environment: Windows Server 2016, MS SQL Server 2016, Java
> 1.8.0_171-b11, JDBC driver 4.2.6420.100
>Reporter: Matt Pryor
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: james-server.log
>
>
> James 3-0-beta4 fails to start using MS SQL Server 2016 for persistence due
> to the following create table statement:
> {{CREATE TABLE JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL,
> MAILBOX_ID BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY,
> MAILBOX_ID))}}
> "KEY" is a reserved keyword in SQL Server.
> Logs attached.
>
--
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-2932) Upgrade runtime to Java 11
[ https://issues.apache.org/jira/browse/JAMES-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2932. - Fix Version/s: (was: 3.5.0) 3.6.0 Resolution: Fixed I am closing this issue as it is addressed on master after 3.5.x tags > Upgrade runtime to Java 11 > -- > > Key: JAMES-2932 > URL: https://issues.apache.org/jira/browse/JAMES-2932 > Project: James Server > Issue Type: Task >Affects Versions: 3.4.0 >Reporter: Matthieu Baechler >Priority: Major > Fix For: 3.6.0 > > > Java 11 is the only "Long Term Support" java release right now so more and > more people will use it exclusively. > Now that James builds to java 11 for some time, we should target java 11 as > the runtime. -- 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-3132) Unable to obtain a connection to the POP3 server
[ https://issues.apache.org/jira/browse/JAMES-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139024#comment-17139024 ] Benoit Tellier commented on JAMES-3132: --- `Caused by: java.net.UnknownHostException: pop.server.com` Does your host succeed to resolve this address (via nslookup?) > Unable to obtain a connection to the POP3 server > - > > Key: JAMES-3132 > URL: https://issues.apache.org/jira/browse/JAMES-3132 > Project: James Server > Issue Type: Bug >Affects Versions: 3.4.0 >Reporter: LARBI YOUCEF Rafik >Priority: Blocker > Attachments: fetchmail.log, pop3server.log, smtpserver.log > > > Hi, > I'm trying to use Apache JAMES for my end of studies' project > In summary > I install the zip file i extract it, I install james & create a domain & 2 > users, > I use telnet 192.168.1.4 25 to send a mail with SMTP protocol, in the log > file I have this message " look in file SMTPSERVER.LOG" > after when I use telnet 192.168.1.4 110 to check mail of recipîent I see > that there is no message received but in "POP3SERVER.LOG" I don't have any > ERROR > after I enable FETCHMAIL.XML (because by default it's desable), hoping I can > receive a mail > and I have an other ERROR > can you help me please > thanks -- 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-1418) SMTP authentication verifyIdentity is passed off
[ https://issues.apache.org/jira/browse/JAMES-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-1418. - Resolution: Abandoned I'm closing this as it affects a beta version. Please reopen if relevant. > SMTP authentication verifyIdentity is passed off > > > Key: JAMES-1418 > URL: https://issues.apache.org/jira/browse/JAMES-1418 > Project: James Server > Issue Type: Bug > Components: SMTPServer >Affects Versions: 3.0-beta3, 3.0-beta4 >Reporter: Serkant Uluderya >Priority: Critical > Labels: smtp > Attachments: MailSender.java, james.out, smtpserver.conf > > Original Estimate: 24h > Remaining Estimate: 24h > > I've been trying to enable SMTP authentication on apache-james-3.0-beta4 but > I can't manage it. I made the log level as DEBUG for SMTP service. It seems > that although the identity verification fails, the user is enable to post a > mail. > In smtpserver.conf file I made the following changes, it is attached also. > announce > > true > Here is the log parts that I suspected. > INFO 17:53:08,746 | james.smtpserver | This SMTP server requires > authentication. > .. > DEBUG 18:03:33,798 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.SenderAuthIdentifyVerificationRcptHook: result=8 > (DECLINED) > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.PostmasterAbuseRcptHook > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.log.HookResultLogger@10a3ffc > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' > org.apache.james.protocols.smtp.core.PostmasterAbuseRcptHook: result=8 > (DECLINED) > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,800 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.JamesRcptCmdHandler: [250 2.1.5 Recipient > OK] > DEBUG 18:03:33,815 | james.smtpserver | Id='9403936' User='' > org.apache.james.protocols.api.handler.CommandDispatcher received: DATA > DEBUG 18:03:33,815 | james.smtpserver | Id='9403936' User='' Lookup command > handler for command: DATA > DEBUG 18:03:33,826 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.JamesDataCmdHandler: [354 Ok Send data ending > with .] > DEBUG 18:03:33,870 | james.smtpserver | Id='9403936' User='' executing james > message handler > org.apache.james.protocols.smtp.core.esmtp.MailSizeEsmtpExtension@4a1908 > DEBUG 18:03:33,872 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.log.HookResultLogger@10a3ffc > DEBUG 18:03:33,872 | james.smtpserver | Id='9403936' User='' > org.apache.james.protocols.smtp.core.esmtp.MailSizeEsmtpExtension: result=8 > (DECLINED) > DEBUG 18:03:33,874 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,874 | james.smtpserver | Id='9403936' User='' executing james > message handler > org.apache.james.smtpserver.AddDefaultAttributesMessageHook@1cfb84c > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.log.HookResultLogger@10a3ffc > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.AddDefaultAttributesMessageHook: result=8 > (DECLINED) > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' executing james > message handler org.apache.james.smtpserver.SendMailHandler@4cb3a4 > DEBUG 18:03:33,876 | james.smtpserver | Id='9403936' User='' sending mail > INFO 18:03:33,906 | james.smtpserver | Id='9403936' User='' Successfully > spooled mail Mail1339427013851-53bd7bc6-0c36-417f-acee-8af76691b35e from > sen...@mail.test.com on 192.168.200.90/192.168.200.90 for > [recei...@mail.test.com] -- 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-1694) POP3 CAPA command returns different capabilities in different states.
[
https://issues.apache.org/jira/browse/JAMES-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139035#comment-17139035
]
Benoit Tellier commented on JAMES-1694:
---
https://tools.ietf.org/html/rfc1939#section-9
States that:
{code:java}
Minimal POP3 Commands:
USER name valid in the AUTHORIZATION state
PASS string
QUIT
STATvalid in the TRANSACTION state
LIST [msg]
RETR msg
DELE msg
NOOP
RSET
QUIT
Optional POP3 Commands:
APOP name digestvalid in the AUTHORIZATION state
TOP msg n valid in the TRANSACTION state
UIDL [msg]
POP3 Replies:
+OK
-ERR
{code}
CAPA command is defined in https://tools.ietf.org/html/rfc2449 POP3 Extension
Mechanism
{code:java}
A capability description MUST document in which states the capability
is announced, and in which states the commands are valid.
{code}
Reading TOP description for instance:
https://tools.ietf.org/html/rfc2449#section-6.1
{code:java}
Announced states / possible differences:
both / no
Commands valid in states:
TRANSACTION
{code}
So your report is likely valid (I'm sadly not POP3 fluent...)
Reading TopCmdHandler code:
{code:java}
@Override
public Set getImplementedCapabilities(POP3Session session) {
if (session.getHandlerState() == POP3Session.TRANSACTION) {
return CAPS;
} else {
return Collections.emptySet();
}
}
{code}
likely needs to be modified.
> POP3 CAPA command returns different capabilities in different states.
> -
>
> Key: JAMES-1694
> URL: https://issues.apache.org/jira/browse/JAMES-1694
> Project: James Server
> Issue Type: Bug
> Components: POP3Server
>Affects Versions: 3.0.0-beta5
> Environment: Linux
>Reporter: Sandeep Savarala
>Priority: Critical
>
> After you connect to the POP3 server and issue CAPA command it returns:
> capa
> +OK Capability list follows
> PIPELINING
> USER
> STLS
> .
> After you authenticate it returns additional UIDL capability.
> capa
> +OK Capability list follows
> PIPELINING
> USER
> UIDL
> TOP
> .
> The CAPA command should return the same output in any state.
--
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-3056) Unit tests for mailbox inconsitencies
[ https://issues.apache.org/jira/browse/JAMES-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3056. - Resolution: Fixed Contributed > Unit tests for mailbox inconsitencies > - > > Key: JAMES-3056 > URL: https://issues.apache.org/jira/browse/JAMES-3056 > Project: James Server > Issue Type: Improvement > Components: mailbox >Reporter: René Cordier >Priority: Major > > *Circumstances* > - mailboxPath exists but not the mailbox > - mailbox exists but not the mailboxPath > - if mailbox has id1/path1 and id2/path1 but mailboxPath only have id1/path1 > (GhostMailbox) > - mailbox renames > https://ci.linagora.com/linagora/lgs/openpaas/james/issues/1586#note_246053 > *How* > _mailboxPath exists but not the mailbox_ > - create a mailbox by `CassandraMailboxMapper.trySave()` > - trigger failure on the second step (mailboxDAO.save()) - (mockito) > _mailbox exists but not the mailboxPath_ > - delete a mailbox `CassandraMailboxMapper.delete()` > - trigger failure on the second step (mailboxDAO.delete()) - (mockito) > _if mailbox has id1/path1 and id2/path1 but mailboxPath only have id1/path1 > (GhostMailbox)_ > - Create a mailbox with id1/path1 with pathV1 (pathV1 only, assuming old > data at the moment V2 is not yet implemented) > - migrate pathV1 -> pathV2 (insert pathV2, then delete pathV1). Trigger a > failure on delete pathV1, then we have both pathV1 and pathV2 exist. > (id1/path1) > - delete mailbox id1/path1 (delete pathV1, pathV2 -> delete mailbox). > Trigger a failure on delete pathV1 but pathV2 still success. => pathV2 > deleted but pathV1, mailbox (id1/path1) still remain. > - create a new mailbox with exact name (id2/path1) -> at this stage we have > id1/path1 and id2/path1 on mailbox, id1/path1 on pathV1 and id2/path1 on > pathV2. > *DOD* > tests show that there're inconsistencies after creating or deleting a > mailbox. They should be located in CassandraMailboxManagerTest -- 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-3060) Evaluate impact of Cassandra ACL
[ https://issues.apache.org/jira/browse/JAMES-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3060. - Resolution: Fixed Impact prooved to be limited. We saw no performance difference. > Evaluate impact of Cassandra ACL > > > Key: JAMES-3060 > URL: https://issues.apache.org/jira/browse/JAMES-3060 > Project: James Server > Issue Type: Improvement >Reporter: René Cordier >Priority: Major > > Run James performance test with, and without cassandra authentification with > restrictive rights (keyspace level acls) to evaluate the runtime impact. > *DOD*: gatling performance result -- 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-3037) Spring XSD not found debug log
[
https://issues.apache.org/jira/browse/JAMES-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3037.
-
Resolution: Fixed
https://github.com/linagora/james-project/pull/3082 had been abandoned
> Spring XSD not found debug log
> --
>
> Key: JAMES-3037
> URL: https://issues.apache.org/jira/browse/JAMES-3037
> Project: James Server
> Issue Type: Improvement
> Components: Spring Container
>Affects Versions: 3.4.0
>Reporter: Benoit Tellier
>Priority: Major
> Fix For: 3.5.0
>
>
> Jerry Malcolm reported the following log:
> https://www.mail-archive.com/server-dev@james.apache.org/msg64206.html
> {code:java}
> DEBUG 23:12:10,456 |
> org.springframework.beans.factory.xml.ResourceEntityResolver | Could not
> resolve XML entity
> [classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd]
> against syjava.net.MalformedURLException: unknown protocol: classpath at
> java.net.URL.(URL.java:607) at java.net.URL.(URL.java:497) at
> java.net.URL.(URL.java:446) at
> org.springframework.beans.factory.xml.ResourceEntityResolver.resolveEntity(ResourceEntityResolver.java:79)
> at
> com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(EntityResolverWrapper.java:110)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:1081)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.resolveDocument(XMLSchemaLoader.java:654)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(XMLSchemaValidator.java:2431)
>
> {code}
> classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd is only
> used in two places:
> -
> server/container/spring/src/main/resources/META-INF/org/apache/james/spring-mailbox-authenticator.xml
> -
> server/container/spring/src/main/resources/META-INF/org/apache/james/spring-mailbox-authorizator.xml
> We should rather rely on the standard we are using in other places:
> http://www.springframework.org/schema/beans/spring-beans.xsd
--
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-2919) Allow partial message read in JMAP DRAFT
[ https://issues.apache.org/jira/browse/JAMES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2919. - Resolution: Fixed Contributed > Allow partial message read in JMAP DRAFT > > > Key: JAMES-2919 > URL: https://issues.apache.org/jira/browse/JAMES-2919 > Project: James Server > Issue Type: Wish > Components: JMAP >Reporter: Benoit Tellier >Assignee: Benoit Tellier >Priority: Major > Fix For: 3.5.0 > > Attachments: adr-0001-jmap-partial-reads.md, > adr-0001-jmap-partial-reads.md, adr-0002-precompute-jmap-preview.md, > adr-0002-precompute-jmap-preview.md > > > Please find attached the two technical decisions being proposed. > h1. Objectives: > - Reduce the pressure exerced by JMAP on underlying data stores > - Improve network usage between James & JMAP client > h2. Proposal for JMAP partial reads > Introduce two projections for JMAP messages: > - One with only metadata > - One with metadata + headers > Given the properties requested by the client, the most appropriate message > projection will be returned. > Finally, we should nullify JSON fields not requested by the client before > sending it to the client. > h2. Proposal for JMAP preview computation > We should pre-compute message preview. > A MailboxListener will compute the preview and store it in a > MessagePreviewStore. > We should have a Cassandra and memory implementation. > When the preview is precomputed then for these messages we can consider the > "preview" property as a metadata. > We should provide a webAdmin task allowing to rebuild the projection. -- 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-2925) Decreasing chunk_length_in_kb for read heavy workloads
[ https://issues.apache.org/jira/browse/JAMES-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2925. - Resolution: Abandoned Preliminary performance tests were not conclusive > Decreasing chunk_length_in_kb for read heavy workloads > -- > > Key: JAMES-2925 > URL: https://issues.apache.org/jira/browse/JAMES-2925 > Project: James Server > Issue Type: Improvement > Components: cassandra, mailbox >Reporter: Benoit Tellier >Priority: Major > > James mostly serve primarily reads with a ration often other 80%. > We often benefit from read optimization. > Such an optimization is the size of chunks being LZ4 compressed within > SSTables files: > - bigger chunks means better compression > - but also means all reads need to load the full chunk size, thus costing IOs > For read heavy workloads, experiment shows decreasing the chunk size from > 64KB (default) to a more reasonable value (like 4KB) often leads to > significant performance enhancement. > As an adoption step, we should conduct a performance test on read-heavy > mailbox-metadata. If conclusive, we can consider adoption on some other often > read metadata. > As a reference here is a reference article on the last pickle blog: > https://thelastpickle.com/blog/2018/08/08/compression_performance.html -- 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-2853) Testing toolbox for Remote Delivery
[ https://issues.apache.org/jira/browse/JAMES-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2853. - Fix Version/s: 3.5.0 Resolution: Fixed All sub-issues are closed, so should be the story ticket > Testing toolbox for Remote Delivery > --- > > Key: JAMES-2853 > URL: https://issues.apache.org/jira/browse/JAMES-2853 > Project: James Server > Issue Type: Test > Components: Remote Delivery, tests >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.5.0 > > > Today, remoteDelivery is lightly tested and error corner cases are not tested. > Several bugs are already known cf JAMES-2097 > JAMES-2442 is an attempt to write such tests but some of these tests require > not-yet available tooling. > In order to write such tests we need : > - 1. a tcp mock server (replying smtp error codes) > - 2. listening on port 25 > - 3. on it's own IP > The FakeSmtp docker approach we had so far covers 2 & 3. We did not find yet > a good solution for 1. > What we had in mind is: > - Writing our own SMTP mock server (POC available here: > https://github.com/linagora/james-project/pull/2545 > - Introduce a JSON format corresponding to the behavior of this Mock server > - load this via HTTP to allow remote setup > - exposes delivered emails over HTTP to allow writing assertions > - dockerizing this. > This will allow writing the tests we are missing. -- 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-2819) Upgrade pdfbox following CVE-2019-0228
[ https://issues.apache.org/jira/browse/JAMES-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2819. - Resolution: Fixed 739f1a4286dbb7a20ba738c7fb72f87c1d11fe9b commit did contribute this. > Upgrade pdfbox following CVE-2019-0228 > -- > > Key: JAMES-2819 > URL: https://issues.apache.org/jira/browse/JAMES-2819 > Project: James Server > Issue Type: Task >Affects Versions: 3.3.0, 3.4.0 >Reporter: Matthieu Baechler >Priority: Major > > James uses pdfbox library and a vulnerability was disclosed recently : > CVE-2019-0228 > We have to update pdfbox version in supported branches -- 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-2856) Add quotaRoot in mailboxDetails over webAdmin
[
https://issues.apache.org/jira/browse/JAMES-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2856.
-
Resolution: Won't Fix
quotaRoot is a teckie IMAP detail that we don't want to leak over webadmin.
> Add quotaRoot in mailboxDetails over webAdmin
> -
>
> Key: JAMES-2856
> URL: https://issues.apache.org/jira/browse/JAMES-2856
> Project: James Server
> Issue Type: New Feature
> Components: webadmin
>Reporter: Benoit Tellier
>Priority: Major
>
> This command takes 3 argument **namespace**, **username**, **mailboxName**
> and return the corresponding **QuotaRoot**.value() in String.
> For example:
> {code:java}
> GETQUOTAROOT #private b...@james.org inbox
> {code}
> should return
> {code:java}
> #private@james.org
> {code}
> WebAdmin should allow to get mailbox quotaRoot as well. (This will help
> dropping the CLI in the future)
> Proposal is to add it as part of mailbox details on this endpoint:
> {code:java}
> GET /users/{username}/mailboxes/{mailboxName}
> {code}
--
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
