[jira] [Commented] (JAMES-2902) Integration tests for SMTP extention mechanisms.
[
https://issues.apache.org/jira/browse/JAMES-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937850#comment-16937850
]
Tellier Benoit commented on JAMES-2902:
---
Note: we should also try some "combinaisons"
> Integration tests for SMTP extention mechanisms.
>
>
> Key: JAMES-2902
> URL: https://issues.apache.org/jira/browse/JAMES-2902
> Project: James Server
> Issue Type: Improvement
> Components: SMTPServer, tests
>Affects Versions: 3.4.0
>Reporter: Tellier Benoit
>Priority: Major
>
> Jannik Junk reported on GitHub issues supplying JamesMessageHook:
> {code:java}
> 2019-09-25 11:44:10.060 INFO 30588 --- [w I/O worker #1]
> o.a.j.p.n.BasicChannelUpstreamHandler: Connection established from
> 127.0.0.1
> 2019-09-25 11:44:19.726 INFO 30588 --- [w I/O worker #1]
> d.o.b.s.s.MessageHook: JAMES Sender: sen...@email.com
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.jboss.netty.util.internal.ByteBufferUtil
> (file:/C:/Users/jjung/.gradle/caches/modules-2/files-2.1/io.netty/netty/3.10.6.Final/18ed04a0e502896552854926e908509db2987a00/netty-3.10.6.Final.jar)
> to method java.nio.DirectByteBuffer.cleaner()
> WARNING: Please consider reporting this to the maintainers of
> org.jboss.netty.util.internal.ByteBufferUtil
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 2019-09-25 11:44:20.256 INFO 30588 --- [w I/O worker #1]
> o.a.j.p.n.BasicChannelUpstreamHandler: Connection closed for 127.0.0.1
> {code}
> We miss tests on the registration of such components.
> Write integration tests on top of guice-memory demonstrating one can register
> SMTP extensions.
> This includes the following APIs:
> - MessageHook / JamesMessageHook
> - MailHook / MailParametersHook
> - RcptHook / DeliverToRecipientHook
> - QuitHook
> - HeloHook
> - AuthHook
> - UnknownHook
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2902) Integration tests for SMTP extention mechanisms.
Tellier Benoit created JAMES-2902:
-
Summary: Integration tests for SMTP extention mechanisms.
Key: JAMES-2902
URL: https://issues.apache.org/jira/browse/JAMES-2902
Project: James Server
Issue Type: Improvement
Components: SMTPServer, tests
Affects Versions: 3.4.0
Reporter: Tellier Benoit
Jannik Junk reported on GitHub issues supplying JamesMessageHook:
{code:java}
2019-09-25 11:44:10.060 INFO 30588 --- [w I/O worker #1]
o.a.j.p.n.BasicChannelUpstreamHandler: Connection established from 127.0.0.1
2019-09-25 11:44:19.726 INFO 30588 --- [w I/O worker #1] d.o.b.s.s.MessageHook
: JAMES Sender: sen...@email.com
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.jboss.netty.util.internal.ByteBufferUtil
(file:/C:/Users/jjung/.gradle/caches/modules-2/files-2.1/io.netty/netty/3.10.6.Final/18ed04a0e502896552854926e908509db2987a00/netty-3.10.6.Final.jar)
to method java.nio.DirectByteBuffer.cleaner()
WARNING: Please consider reporting this to the maintainers of
org.jboss.netty.util.internal.ByteBufferUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
2019-09-25 11:44:20.256 INFO 30588 --- [w I/O worker #1]
o.a.j.p.n.BasicChannelUpstreamHandler: Connection closed for 127.0.0.1
{code}
We miss tests on the registration of such components.
Write integration tests on top of guice-memory demonstrating one can register
SMTP extensions.
This includes the following APIs:
- MessageHook / JamesMessageHook
- MailHook / MailParametersHook
- RcptHook / DeliverToRecipientHook
- QuitHook
- HeloHook
- AuthHook
- UnknownHook
--
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-2881) Add test for HeadersToHTTP/SerialiseToHTTP mailets
[ https://issues.apache.org/jira/browse/JAMES-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2881. - > Add test for HeadersToHTTP/SerialiseToHTTP mailets > -- > > Key: JAMES-2881 > URL: https://issues.apache.org/jira/browse/JAMES-2881 > Project: James Server > Issue Type: Test >Reporter: Sergio >Priority: Minor > > Add test for HeadersToHTTP and SerialiseToHTTP mailets -- 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-2813) Implement a distributed task manager
[ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937370#comment-16937370 ] Tellier Benoit commented on JAMES-2813: --- https://github.com/linagora/james-project/pull/2698 added task additional information DTO + serialization for reprocessing related classes > Implement a distributed task manager > > > Key: JAMES-2813 > URL: https://issues.apache.org/jira/browse/JAMES-2813 > Project: James Server > Issue Type: Task >Reporter: Matthieu Baechler >Priority: Major > > Following JAMES-2272, we now would like to handle tasks at a cluster level. > For that, we intend to use a combination of Event Sourcing for keeping track > of Tasks submitted and RabbitMQ for dispatching the tasks in the cluster. -- 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-2881) Add test for HeadersToHTTP/SerialiseToHTTP mailets
[ https://issues.apache.org/jira/browse/JAMES-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937369#comment-16937369 ] Tellier Benoit commented on JAMES-2881: --- https://github.com/linagora/james-project/pull/2709 proposed some small code enhancements > Add test for HeadersToHTTP/SerialiseToHTTP mailets > -- > > Key: JAMES-2881 > URL: https://issues.apache.org/jira/browse/JAMES-2881 > Project: James Server > Issue Type: Test >Reporter: Sergio >Priority: Minor > > Add test for HeadersToHTTP and SerialiseToHTTP mailets -- 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] [Resolved] (JAMES-2898) Move org.apache.james.backend.rabbitmq to org.apache.james.backends.rabbitmq
[ https://issues.apache.org/jira/browse/JAMES-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit resolved JAMES-2898. --- Fix Version/s: 3.5.0 Resolution: Fixed https://github.com/linagora/james-project/pull/2710 solved this. > Move org.apache.james.backend.rabbitmq to org.apache.james.backends.rabbitmq > > > Key: JAMES-2898 > URL: https://issues.apache.org/jira/browse/JAMES-2898 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Trivial > Fix For: 3.5.0 > > > Currently there are three backends: > > * org.apache.james.backend.rabbitmq > * org.apache.james.backends.cassandra > * org.apache.james.backends.es > > RabbitMQ's is mispelled -- 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-2893) Provided unified testing dependencies
[ https://issues.apache.org/jira/browse/JAMES-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936608#comment-16936608 ] Tellier Benoit commented on JAMES-2893: --- https://github.com/linagora/james-project/pull/2708 added the resulting log file in the gitIgnore file > Provided unified testing dependencies > - > > Key: JAMES-2893 > URL: https://issues.apache.org/jira/browse/JAMES-2893 > Project: James Server > Issue Type: Improvement > Components: Build System, tests >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > This enables: > - A single declaration of logback classic. We can then systematically log > test output to file thus cleaning console output. > - Systematic equalsVerifier & JUnit jupiter + vintage imports : this > mitigates the risk of not having the tests running in maven because of a > JUnit dependency combination mistake. > - Simplification of maven dependencies unlocking compile-time improvements. -- 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-1906) Add a JPA cluster util
[ https://issues.apache.org/jira/browse/JAMES-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936604#comment-16936604 ] Tellier Benoit commented on JAMES-1906: --- https://github.com/linagora/james-project/pull/2707 did fix a typo in JPATestCluster > Add a JPA cluster util > -- > > Key: JAMES-1906 > URL: https://issues.apache.org/jira/browse/JAMES-1906 > Project: James Server > Issue Type: Improvement >Reporter: Tellier Benoit >Priority: Major > > Also : use it everywhere > Put it in a backend jpa project > Then factorize JPA dependencies in this backend 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-2897) Cassandra Lightweight Transaction requires specific consistency level
[ https://issues.apache.org/jira/browse/JAMES-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936601#comment-16936601 ] Tellier Benoit commented on JAMES-2897: --- https://github.com/linagora/james-project/pull/2683 solved this. > Cassandra Lightweight Transaction requires specific consistency level > - > > Key: JAMES-2897 > URL: https://issues.apache.org/jira/browse/JAMES-2897 > Project: James Server > Issue Type: Bug > Components: cassandra >Reporter: Matthieu Baechler >Priority: Major > > After reading > https://docs.datastax.com/en/ddac/doc/datastax_enterprise/dbInternals/dbIntLtwtTransactions.html > , > https://docs.datastax.com/en/ddaccql/doc/cql/cql_reference/cqlsh_commands/cqlshConsistency.html > and > https://docs.datastax.com/en/ddaccql/doc/cql/cql_reference/cqlsh_commands/cqlshSerialConsistency.html > It looks like we should be more careful about consistency when reading > tables that use LWT. > Basically, to ensure we always read the last value, we must read with SERIAL > consistency. -- 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-2813) Implement a distributed task manager
[ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936600#comment-16936600 ] Tellier Benoit commented on JAMES-2813: --- Just merged https://github.com/linagora/james-project/pull/2653, adding a timeout parameter for await. > Implement a distributed task manager > > > Key: JAMES-2813 > URL: https://issues.apache.org/jira/browse/JAMES-2813 > Project: James Server > Issue Type: Task >Reporter: Matthieu Baechler >Priority: Major > > Following JAMES-2272, we now would like to handle tasks at a cluster level. > For that, we intend to use a combination of Event Sourcing for keeping track > of Tasks submitted and RabbitMQ for dispatching the tasks in the cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2896) RabbitMQ MailQueue should support delays
Tellier Benoit created JAMES-2896: - Summary: RabbitMQ MailQueue should support delays Key: JAMES-2896 URL: https://issues.apache.org/jira/browse/JAMES-2896 Project: James Server Issue Type: Improvement Components: Queue, rabbitmq Reporter: Tellier Benoit MX (mail exchange) servers do rely on delays for some things like spam and abuse detection thus this is a critical capability for a mail queue component of a server aiming at being used as an MX. So far, RabbitMQ mail queue does not support delays. Its usage is then discouraged within an MX server (though it is perfectly suited for an MDA). We can relatively easily implement delays within the RabbitMQ mail queue: - When a delay is specified, we save the message in the object storage, fire a message on a **MailQueueDelayExchange**, and persist it on the MailQueueView. - Each James listens on a single Queue plugged to the **MailQueueDelayExchange**. - For each incoming message, the receiver will position a timer until the planned delivery (date). - Upon timer completion, we ack the message of MailQueueDelayExchange, then we put the corresponding message in the mail RabbitMQMailQueue (no need to update the mailQueueView nor store again the blob). - Upon connection loss, the message will be nacked and will be then handled by another s/consumer/jamesServer/. Obviously: - We need synchronized clocks "best-effort" - think NTP - This solution can duplicate emails upon connection loss - a local James needs to invalidate the entries he is waiting for upon connection loss. - **flush** needs to be broadcasted so that all James servers can release the retained delayed emails into the mail queue. -- 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-2881) Add test for HeadersToHTTP/SerialiseToHTTP mailets
[ https://issues.apache.org/jira/browse/JAMES-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936305#comment-16936305 ] Tellier Benoit commented on JAMES-2881: --- Hi [~splainez], would you consider this job as 'done'? > Add test for HeadersToHTTP/SerialiseToHTTP mailets > -- > > Key: JAMES-2881 > URL: https://issues.apache.org/jira/browse/JAMES-2881 > Project: James Server > Issue Type: Test >Reporter: Sergio >Priority: Minor > > Add test for HeadersToHTTP and SerialiseToHTTP mailets -- 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-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936295#comment-16936295
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2705 did remove duplicated
subproject maven plugins
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration ..
> 1.9 -> 1.10
> 223 [INFO] commons-daemon:commons-daemon
[jira] [Commented] (JAMES-2895) Remove link to the outdated wiki on the website
[ https://issues.apache.org/jira/browse/JAMES-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935682#comment-16935682 ] Tellier Benoit commented on JAMES-2895: --- See https://issues.apache.org/jira/browse/INFRA-19134 for removal of wiki > Remove link to the outdated wiki on the website > --- > > Key: JAMES-2895 > URL: https://issues.apache.org/jira/browse/JAMES-2895 > Project: James Server > Issue Type: Improvement > Components: site >Reporter: Tellier Benoit >Priority: Major > > Articles on the wiki are from 2007 which is clearly outdated. > Unreferencing this wiki, which just add confusion, would be a good step. -- 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-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935679#comment-16935679
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2704 JAMES-2855 Upgrade
maven-assembly-plugin to 3.1.1 unlock significant performance improvement when
building jar-withdependencies
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration
[jira] [Commented] (JAMES-2886) Unable to usetransitive dependencies at runtime in Guice extension jars
[
https://issues.apache.org/jira/browse/JAMES-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935677#comment-16935677
]
Tellier Benoit commented on JAMES-2886:
---
https://github.com/linagora/james-project/pull/2699 provides the new hability
to define guice modules that will be used for extension instanciation, covering
some lacks of Guice wiring.
> Unable to usetransitive dependencies at runtime in Guice extension jars
> ---
>
> Key: JAMES-2886
> URL: https://issues.apache.org/jira/browse/JAMES-2886
> Project: James Server
> Issue Type: Bug
> Components: guice, Matchers/Mailets (bundled)
>Affects Versions: 3.4.0
>Reporter: Tellier Benoit
>Priority: Major
>
> As reported by @AaronRegan , we are unable to resolve transitive dependencies
> in extension jars.
> # Steps to reproduce
> Given a maven module containing a custom mailet, instanciating objects as
> part of the *service* method that are NOT part of James classpath:
> - 1. Start *any* James guice application
> - 2. Drop the JAR of the aforementioned in extension-jars folder
> - 3. Configure the mailet within the mailet pipeline
> - 4. Process a mail and
> - 5. Notice runtime failures! The service method does not succeed to
> instanciate the object not being part of James classpath.
> As off commit 42d7d55d5380d13648533160844d30f765a2c6f1, such a JAR could very
> well be the *apache-mailet-crypto* JAR.
> This would result in :
> {code:java}
> java.lang.ClassNotFoundException:
> org.bouncycastle.mail.smime.SMIMESignedGenerator
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 82 common frames omitted
> Wrapped by: java.lang.NoClassDefFoundError:
> org/bouncycastle/mail/smime/SMIMESignedGenerator
> at
> org.apache.james.transport.SMIMEKeyHolder.createGenerator(SMIMEKeyHolder.java:208)
> at org.apache.james.transport.SMIMEKeyHolder.generate(SMIMEKeyHolder.java:251)
> at
> org.apache.james.transport.mailets.AbstractSign.service(AbstractSign.java:486)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:81)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.handleMailet(CamelMailetProcessor.java:178)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.lambda$configure$0(CamelMailetProcessor.java:155)
> at
> org.apache.camel.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:63)
> ... 75 common frames omitted
> {code}
> # What to do from here
> - Write a test reproducing that behavior...
> - Bundle *apache-mailet-crypto* within supported guice app mailets
> - Fix that annoying transitive dependency issue - this is in my opinion a
> blocker for Guice adoption.
--
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-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935676#comment-16935676
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2686 contributed a massive
dependency cleanup (remove dependencies where not used)
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration ..
> 1.9 -> 1.10
> 223 [INFO]
[jira] [Commented] (JAMES-2885) Avoid concurrent nexModSeq during flags update
[ https://issues.apache.org/jira/browse/JAMES-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935609#comment-16935609 ] Tellier Benoit commented on JAMES-2885: --- `This fix should not have a big impact on performance because the concurrent update of the modSeq happens where there is multiple mailbox passed in parameter. In the normal of usage of this method only one mailbox is provided.` Not sure about it concerning IMAP range flag update. > Avoid concurrent nexModSeq during flags update > -- > > Key: JAMES-2885 > URL: https://issues.apache.org/jira/browse/JAMES-2885 > Project: James Server > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Rémi Kowalski >Priority: Major > Fix For: 3.5.0 > > > When updating flags, the nextmodSeq is called concurrently. This PR aims to > fix this. > > The concurrent update of nextModSeq is a problem, because on the cassandra > backend this method will retry until the update succeed using a lightweight > transaction > where the condition is that the current mod seq in database match the current > mod seq provide. Which will not happen this method is called concurrenty. It > will then retry until the max number of retry is exhausted. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSPF-105) Rely on slf4j-api for logging
Tellier Benoit created JSPF-105: --- Summary: Rely on slf4j-api for logging Key: JSPF-105 URL: https://issues.apache.org/jira/browse/JSPF-105 Project: James jSPF Issue Type: Improvement Reporter: Tellier Benoit By using a modern logging API, we can: - Avoid the Logger frontend API which: - Makes using JSPF easier - Reduces code size - Avoid forcing the Log4J dependency (that is later excluded in James) - Allow using placeholders - Remove the need of Logger wiring - Allow more precise logs: the classname the log is emmited from is then explicitly used. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JDKIM-44) Use JDK 8 as a target JDK
Tellier Benoit created JDKIM-44: --- Summary: Use JDK 8 as a target JDK Key: JDKIM-44 URL: https://issues.apache.org/jira/browse/JDKIM-44 Project: James jDKIM Issue Type: Improvement Reporter: Tellier Benoit In this thread [1] , we voted for switching JDKIM to the 1.8 target JDK. [1]: https://www.mail-archive.com/server-dev@james.apache.org/msg62167.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] [Created] (JSIEVE-113) Use JDK 8 as a target JDK
Tellier Benoit created JSIEVE-113: - Summary: Use JDK 8 as a target JDK Key: JSIEVE-113 URL: https://issues.apache.org/jira/browse/JSIEVE-113 Project: James jSieve Issue Type: Improvement Reporter: Tellier Benoit In this thread [1] , we voted for switching JSIEVE to the 1.8 target JDK. [1]: https://www.mail-archive.com/server-dev@james.apache.org/msg62167.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] [Created] (JSPF-104) Use JDK 8 as a target JDK
Tellier Benoit created JSPF-104: --- Summary: Use JDK 8 as a target JDK Key: JSPF-104 URL: https://issues.apache.org/jira/browse/JSPF-104 Project: James jSPF Issue Type: Improvement Components: Core Reporter: Tellier Benoit In this thread [1] , we voted for switching JSPF to the 1.8 target JDK. [1]: https://www.mail-archive.com/server-dev@james.apache.org/msg62167.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] [Commented] (JAMES-2895) Remove link to the outdated wiki on the website
[ https://issues.apache.org/jira/browse/JAMES-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935514#comment-16935514 ] Tellier Benoit commented on JAMES-2895: --- https://github.com/linagora/james-project/pull/2702 proposes to fix this > Remove link to the outdated wiki on the website > --- > > Key: JAMES-2895 > URL: https://issues.apache.org/jira/browse/JAMES-2895 > Project: James Server > Issue Type: Improvement > Components: site >Reporter: Tellier Benoit >Priority: Major > > Articles on the wiki are from 2007 which is clearly outdated. > Unreferencing this wiki, which just add confusion, would be a good step. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2895) Remove link to the outdated wiki on the website
Tellier Benoit created JAMES-2895: - Summary: Remove link to the outdated wiki on the website Key: JAMES-2895 URL: https://issues.apache.org/jira/browse/JAMES-2895 Project: James Server Issue Type: Improvement Components: site Reporter: Tellier Benoit Articles on the wiki are from 2007 which is clearly outdated. Unreferencing this wiki, which just add confusion, would be a good step. -- 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-2813) Implement a distributed task manager
[ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935512#comment-16935512 ] Tellier Benoit commented on JAMES-2813: --- https://github.com/linagora/james-project/pull/2616 demonstrated the behavior of exclusive consumers > Implement a distributed task manager > > > Key: JAMES-2813 > URL: https://issues.apache.org/jira/browse/JAMES-2813 > Project: James Server > Issue Type: Task >Reporter: Matthieu Baechler >Priority: Major > > Following JAMES-2272, we now would like to handle tasks at a cluster level. > For that, we intend to use a combination of Event Sourcing for keeping track > of Tasks submitted and RabbitMQ for dispatching the tasks in the cluster. -- 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-2885) Avoid concurrent nexModSeq during flags update
[ https://issues.apache.org/jira/browse/JAMES-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935511#comment-16935511 ] Tellier Benoit commented on JAMES-2885: --- PR: https://github.com/linagora/james-project/pull/2682 > Avoid concurrent nexModSeq during flags update > -- > > Key: JAMES-2885 > URL: https://issues.apache.org/jira/browse/JAMES-2885 > Project: James Server > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Rémi Kowalski >Priority: Major > Fix For: 3.5.0 > > > When updating flags, the nextmodSeq is called concurrently. This PR aims to > fix 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] (JAMES-2894) Run intellij inspections : java language feature migration
[ https://issues.apache.org/jira/browse/JAMES-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2894. - Resolution: Fixed > Run intellij inspections : java language feature migration > -- > > Key: JAMES-2894 > URL: https://issues.apache.org/jira/browse/JAMES-2894 > Project: James Server > Issue Type: Improvement >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > This would easily improve overall project code quality. -- 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-2893) Provided unified testing dependencies
[ https://issues.apache.org/jira/browse/JAMES-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2893. - Resolution: Fixed > Provided unified testing dependencies > - > > Key: JAMES-2893 > URL: https://issues.apache.org/jira/browse/JAMES-2893 > Project: James Server > Issue Type: Improvement > Components: Build System, tests >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > This enables: > - A single declaration of logback classic. We can then systematically log > test output to file thus cleaning console output. > - Systematic equalsVerifier & JUnit jupiter + vintage imports : this > mitigates the risk of not having the tests running in maven because of a > JUnit dependency combination mistake. > - Simplification of maven dependencies unlocking compile-time improvements. -- 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-2894) Run intellij inspections : java language feature migration
[ https://issues.apache.org/jira/browse/JAMES-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934322#comment-16934322 ] Tellier Benoit commented on JAMES-2894: --- https://github.com/linagora/james-project/pull/2678 contributes this > Run intellij inspections : java language feature migration > -- > > Key: JAMES-2894 > URL: https://issues.apache.org/jira/browse/JAMES-2894 > Project: James Server > Issue Type: Improvement >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > This would easily improve overall project code quality. -- 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-2894) Run intellij inspections : java language feature migration
[ https://issues.apache.org/jira/browse/JAMES-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit updated JAMES-2894: -- Fix Version/s: 3.5.0 > Run intellij inspections : java language feature migration > -- > > Key: JAMES-2894 > URL: https://issues.apache.org/jira/browse/JAMES-2894 > Project: James Server > Issue Type: Improvement >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > This would easily improve overall project code quality. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2894) Run intellij inspections : java language feature migration
Tellier Benoit created JAMES-2894: - Summary: Run intellij inspections : java language feature migration Key: JAMES-2894 URL: https://issues.apache.org/jira/browse/JAMES-2894 Project: James Server Issue Type: Improvement Reporter: Tellier Benoit This would easily improve overall project code quality. -- 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-2893) Provided unified testing dependencies
[ https://issues.apache.org/jira/browse/JAMES-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934321#comment-16934321 ] Tellier Benoit commented on JAMES-2893: --- https://github.com/linagora/james-project/pull/2676 proposes a fix regarding this. > Provided unified testing dependencies > - > > Key: JAMES-2893 > URL: https://issues.apache.org/jira/browse/JAMES-2893 > Project: James Server > Issue Type: Improvement > Components: Build System, tests >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > This enables: > - A single declaration of logback classic. We can then systematically log > test output to file thus cleaning console output. > - Systematic equalsVerifier & JUnit jupiter + vintage imports : this > mitigates the risk of not having the tests running in maven because of a > JUnit dependency combination mistake. > - Simplification of maven dependencies unlocking compile-time improvements. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2893) Provided unified testing dependencies
Tellier Benoit created JAMES-2893: - Summary: Provided unified testing dependencies Key: JAMES-2893 URL: https://issues.apache.org/jira/browse/JAMES-2893 Project: James Server Issue Type: Improvement Components: Build System, tests Reporter: Tellier Benoit Fix For: 3.5.0 This enables: - A single declaration of logback classic. We can then systematically log test output to file thus cleaning console output. - Systematic equalsVerifier & JUnit jupiter + vintage imports : this mitigates the risk of not having the tests running in maven because of a JUnit dependency combination mistake. - Simplification of maven dependencies unlocking compile-time improvements. -- 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-2886) Unable to usetransitive dependencies at runtime in Guice extension jars
[
https://issues.apache.org/jira/browse/JAMES-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932044#comment-16932044
]
Tellier Benoit commented on JAMES-2886:
---
This issue can be solved by packaging things in a jar-with-dependencies as
demonstrated in https://github.com/linagora/james-project/pull/2695
> Unable to usetransitive dependencies at runtime in Guice extension jars
> ---
>
> Key: JAMES-2886
> URL: https://issues.apache.org/jira/browse/JAMES-2886
> Project: James Server
> Issue Type: Bug
> Components: guice, Matchers/Mailets (bundled)
>Affects Versions: 3.4.0
>Reporter: Tellier Benoit
>Priority: Major
>
> As reported by @AaronRegan , we are unable to resolve transitive dependencies
> in extension jars.
> # Steps to reproduce
> Given a maven module containing a custom mailet, instanciating objects as
> part of the *service* method that are NOT part of James classpath:
> - 1. Start *any* James guice application
> - 2. Drop the JAR of the aforementioned in extension-jars folder
> - 3. Configure the mailet within the mailet pipeline
> - 4. Process a mail and
> - 5. Notice runtime failures! The service method does not succeed to
> instanciate the object not being part of James classpath.
> As off commit 42d7d55d5380d13648533160844d30f765a2c6f1, such a JAR could very
> well be the *apache-mailet-crypto* JAR.
> This would result in :
> {code:java}
> java.lang.ClassNotFoundException:
> org.bouncycastle.mail.smime.SMIMESignedGenerator
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 82 common frames omitted
> Wrapped by: java.lang.NoClassDefFoundError:
> org/bouncycastle/mail/smime/SMIMESignedGenerator
> at
> org.apache.james.transport.SMIMEKeyHolder.createGenerator(SMIMEKeyHolder.java:208)
> at org.apache.james.transport.SMIMEKeyHolder.generate(SMIMEKeyHolder.java:251)
> at
> org.apache.james.transport.mailets.AbstractSign.service(AbstractSign.java:486)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:81)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.handleMailet(CamelMailetProcessor.java:178)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.lambda$configure$0(CamelMailetProcessor.java:155)
> at
> org.apache.camel.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:63)
> ... 75 common frames omitted
> {code}
> # What to do from here
> - Write a test reproducing that behavior...
> - Bundle *apache-mailet-crypto* within supported guice app mailets
> - Fix that annoying transitive dependency issue - this is in my opinion a
> blocker for Guice adoption.
--
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-2884) Update JMAP implementation to conform to RFC 8620/8621
[ https://issues.apache.org/jira/browse/JAMES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932002#comment-16932002 ] Tellier Benoit commented on JAMES-2884: --- I did also create a first batch of sub-tasks to reflect the first steps of the aforementioned approach. Concretely, the first target is: Getting a 'memory-guice' powered 'jmap' server, distinct from 'jmap-draft', handling only the 'echo' command in a RFC-8620 compliant way. > Update JMAP implementation to conform to RFC 8620/8621 > -- > > Key: JAMES-2884 > URL: https://issues.apache.org/jira/browse/JAMES-2884 > Project: James Server > Issue Type: Improvement > Components: JMAP >Reporter: cketti >Assignee: Antoine Duprat >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Historically, James is an early adopter for the JMAP specification, and a > first partial implementation was conducted when JMAP was just a draft. IETF > draft undergo radical changes and the community could not keep this > implementation up to date with the spec changes. > As off summer 2019, JMAP core ([RFC > 8620|https://tools.ietf.org/html/rfc8620]) and JMAP mail ([RFC > 8621|https://tools.ietf.org/html/rfc8621]) had been officially published > (will not change anymore). Thus we should implement these new specifications. > Point of attention: part of the community actively rely on the actual 'draft' > implementation of JMAP existing in James. We should ensure no changes is done > to that 'draft' protocol is done while implementing the new one. > The proposed approach is to keep the current implementation under the > `jmap-draft` name, and implement step by step a `jmap` compliant > implementation, that will be exposed on a separate port. No modification in > `jmap-draft` integration test should be counducted. > This will allow existing `jmap-draft` clients to smoothly transition to > `jmap`, then trigger the classic "deprecation-then-removal" process. > For now, as a first implementation step, we will only support `jmap` on top > of memory-guice (ease testing, speed of development). To ensure a > `storage-compliant` behavior of newly introduced storage APIs, we should use > persistent datastructures (like the one in vavr) and always deep-copy objects > at the storage boundaries. -- 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-2889) `jmap` should match RFC-8620 protocol structure - request/response
[
https://issues.apache.org/jira/browse/JAMES-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit updated JAMES-2889:
--
Summary: `jmap` should match RFC-8620 protocol structure - request/response
(was: `jmap` should match RFC-2860 protocol structure - request/response)
> `jmap` should match RFC-8620 protocol structure - request/response
> --
>
> Key: JAMES-2889
> URL: https://issues.apache.org/jira/browse/JAMES-2889
> Project: James Server
> Issue Type: Sub-task
> Components: JMAP
>Reporter: Tellier Benoit
>Assignee: Antoine Duprat
>Priority: Major
>
> JAMES-2888 bootstrap a jmap server, but with jmap-draft protocol structure.
> The goal of this ticket is to match RFC-2860 protocol structure:
> Request:
> {code:java}
> {
> "using": [ "urn:ietf:params:jmap:core", "urn:ietf:params:jmap:mail" ],
> "methodCalls": [
> [ "method1", {
> "arg1": "arg1data",
> "arg2": "arg2data"
> }, "c1" ],
> [ "method2", {
> "arg1": "arg1data"
> }, "c2" ],
> [ "method3", {}, "c3" ]
> ]
> }
> {code}
> Response:
> {code:java}
> {
> "methodResponses": [
> [ "method1", {
> "arg1": 3,
> "arg2": "foo"
> }, "c1" ],
> [ "method2", {
> "isBlah": true
> }, "c2" ],
> [ "anotherResponseFromMethod2", {
> "data": 10,
> "yetmoredata": "Hello"
> }, "c2"],
> [ "error", {
> "type":"unknownMethod"
> }, "c3" ]
> ],
> "sessionState": "75128aab4b1b"
> }
> {code}
> Update echo integration tests accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2892) JMAP protocol-level error handling
Tellier Benoit created JAMES-2892: - Summary: JMAP protocol-level error handling Key: JAMES-2892 URL: https://issues.apache.org/jira/browse/JAMES-2892 Project: James Server Issue Type: Sub-task Components: JMAP Reporter: Tellier Benoit Assignee: Antoine Duprat JMAP error handling related logic needs to be reviewed in order to match [this|https://jmap.io/spec-core.html#errors] Test the following (protocol level) errors: - The user is passing an unknown capability - The user is passing a non parsable JSON - The user did not use `application/json` content type - The method being used does not exist -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2891) JMAP protocol structure: GET /jmap/session
Tellier Benoit created JAMES-2891:
-
Summary: JMAP protocol structure: GET /jmap/session
Key: JAMES-2891
URL: https://issues.apache.org/jira/browse/JAMES-2891
Project: James Server
Issue Type: Sub-task
Components: JMAP
Reporter: Tellier Benoit
Assignee: Antoine Duprat
Implement a
`[Session|https://jmap.io/spec-core.html#the-jmap-session-resource]` object.
Don't hesitate to:
- Return default values even if not enforced.
- Return null for not implemented yet features ("download/uploadUrl"?)
Regarding AccountId, each User (as in james-core, and must be contained in
UsersRepository) have an AccountId associated to him (username). That is the
single account he is owning.
In order to retrieve the Session object, one can:
{code:java}
GET /jmap/session
{code}
Write memory integration tests for 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] [Created] (JAMES-2890) JMAP simple auth
Tellier Benoit created JAMES-2890: - Summary: JMAP simple auth Key: JAMES-2890 URL: https://issues.apache.org/jira/browse/JAMES-2890 Project: James Server Issue Type: Sub-task Components: JMAP Reporter: Tellier Benoit Assignee: Antoine Duprat Implement a simple auth mechanism for JMAP Modify the `echo` command integration test accordingly. Ensure that non-authenticated requests are 401 rejected. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2889) `jmap` should match RFC-2860 protocol structure - request/response
Tellier Benoit created JAMES-2889:
-
Summary: `jmap` should match RFC-2860 protocol structure -
request/response
Key: JAMES-2889
URL: https://issues.apache.org/jira/browse/JAMES-2889
Project: James Server
Issue Type: Sub-task
Components: JMAP
Reporter: Tellier Benoit
Assignee: Antoine Duprat
JAMES-2888 bootstrap a jmap server, but with jmap-draft protocol structure.
The goal of this ticket is to match RFC-2860 protocol structure:
Request:
{code:java}
{
"using": [ "urn:ietf:params:jmap:core", "urn:ietf:params:jmap:mail" ],
"methodCalls": [
[ "method1", {
"arg1": "arg1data",
"arg2": "arg2data"
}, "c1" ],
[ "method2", {
"arg1": "arg1data"
}, "c2" ],
[ "method3", {}, "c3" ]
]
}
{code}
Response:
{code:java}
{
"methodResponses": [
[ "method1", {
"arg1": 3,
"arg2": "foo"
}, "c1" ],
[ "method2", {
"isBlah": true
}, "c2" ],
[ "anotherResponseFromMethod2", {
"data": 10,
"yetmoredata": "Hello"
}, "c2"],
[ "error", {
"type":"unknownMethod"
}, "c3" ]
],
"sessionState": "75128aab4b1b"
}
{code}
Update echo integration tests accordingly.
--
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-2887) Implement JMAP RFC-8620 & RFC-8621
[ https://issues.apache.org/jira/browse/JAMES-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2887. - Resolution: Duplicate See JAMES-2884 > Implement JMAP RFC-8620 & RFC-8621 > -- > > Key: JAMES-2887 > URL: https://issues.apache.org/jira/browse/JAMES-2887 > Project: James Server > Issue Type: New Feature > Components: JMAP >Reporter: Tellier Benoit >Assignee: Antoine Duprat >Priority: Major > Labels: feature > > Historically, James is an early adopter for the JMAP specification, and a > first partial implementation was conducted when JMAP was just a draft. IETF > draft undergo radical changes and the community could not keep this > implementation up to date with the spec changes. > As off summer 2019, JMAP core (RFC-2860) and JMAP mail (RFC 8621) had been > officially published (will not change anymore). Thus we should implement > these new specifications. > Point of attention: part of the community actively rely on the actual 'draft' > implementation of JMAP existing in James. We should ensure no changes is done > to that 'draft' protocol is done while implementing the new one. > The proposed approach is to keep the current implementation under the > `jmap-draft` name, and implement step by step a `jmap` compliant > implementation, that will be exposed on a separate port. No modification in > `jmap-draft` integration test should be counducted. > This will allow existing `jmap-draft` clients to smoothly transition to > `jmap`, then trigger the classic "deprecation-then-removal" process. > For now, as a first implementation step, we will only support `jmap` on top > of memory-guice (ease testing, speed of development). To ensure a > `storage-compliant` behavior of newly introduced storage APIs, we should use > persistent datastructures (like the one in vavr) and always deep-copy objects > at the storage boundaries. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2888) Bootstrap the JMAP server - echo command
Tellier Benoit created JAMES-2888: - Summary: Bootstrap the JMAP server - echo command Key: JAMES-2888 URL: https://issues.apache.org/jira/browse/JAMES-2888 Project: James Server Issue Type: Sub-task Components: JMAP Reporter: Tellier Benoit Assignee: Antoine Duprat Definition of done: The `memory-guice` application will ship a `jmap` server containing only the [core/echo|https://jmap.io/spec-core.html#the-coreecho-method] method. A simple integration test demonstrating this will be written. Note that 'protocol structure' (using, methodCalls) correction is **not included** in this ticket (will be fixed later). To be performing this: - Create a new `server/protocols/jmap` project - Copy in it the minimal subset of classes from `server/protocols/jmap-draft` - Implement a EchoMethod - Implement guice bindings in `server/container/guice/protocols/jmap` - Load `JMAP guice module` within MemoryJamesServerMain - Write a simple integration test in `server/protocols/jmap-integration-testing` demonstrating the echo command behaviour. -- 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-2884) Update JMAP implementation to conform to RFC 8620/8621
[ https://issues.apache.org/jira/browse/JAMES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931983#comment-16931983 ] Tellier Benoit commented on JAMES-2884: --- https://github.com/apache/james-project/pull/164 renames existing JMAP implementation into `jmap-draft` > Update JMAP implementation to conform to RFC 8620/8621 > -- > > Key: JAMES-2884 > URL: https://issues.apache.org/jira/browse/JAMES-2884 > Project: James Server > Issue Type: Improvement > Components: JMAP >Reporter: cketti >Assignee: Antoine Duprat >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Historically, James is an early adopter for the JMAP specification, and a > first partial implementation was conducted when JMAP was just a draft. IETF > draft undergo radical changes and the community could not keep this > implementation up to date with the spec changes. > As off summer 2019, JMAP core ([RFC > 8620|https://tools.ietf.org/html/rfc8620]) and JMAP mail ([RFC > 8621|https://tools.ietf.org/html/rfc8621]) had been officially published > (will not change anymore). Thus we should implement these new specifications. > Point of attention: part of the community actively rely on the actual 'draft' > implementation of JMAP existing in James. We should ensure no changes is done > to that 'draft' protocol is done while implementing the new one. > The proposed approach is to keep the current implementation under the > `jmap-draft` name, and implement step by step a `jmap` compliant > implementation, that will be exposed on a separate port. No modification in > `jmap-draft` integration test should be counducted. > This will allow existing `jmap-draft` clients to smoothly transition to > `jmap`, then trigger the classic "deprecation-then-removal" process. > For now, as a first implementation step, we will only support `jmap` on top > of memory-guice (ease testing, speed of development). To ensure a > `storage-compliant` behavior of newly introduced storage APIs, we should use > persistent datastructures (like the one in vavr) and always deep-copy objects > at the storage boundaries. -- 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-2884) Update JMAP implementation to conform to RFC 8620/8621
[ https://issues.apache.org/jira/browse/JAMES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931982#comment-16931982 ] Tellier Benoit commented on JAMES-2884: --- https://github.com/apache/james-project/pull/163 did rename some class to closely match RFC-8620 wording. > Update JMAP implementation to conform to RFC 8620/8621 > -- > > Key: JAMES-2884 > URL: https://issues.apache.org/jira/browse/JAMES-2884 > Project: James Server > Issue Type: Improvement > Components: JMAP >Reporter: cketti >Assignee: Antoine Duprat >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Historically, James is an early adopter for the JMAP specification, and a > first partial implementation was conducted when JMAP was just a draft. IETF > draft undergo radical changes and the community could not keep this > implementation up to date with the spec changes. > As off summer 2019, JMAP core ([RFC > 8620|https://tools.ietf.org/html/rfc8620]) and JMAP mail ([RFC > 8621|https://tools.ietf.org/html/rfc8621]) had been officially published > (will not change anymore). Thus we should implement these new specifications. > Point of attention: part of the community actively rely on the actual 'draft' > implementation of JMAP existing in James. We should ensure no changes is done > to that 'draft' protocol is done while implementing the new one. > The proposed approach is to keep the current implementation under the > `jmap-draft` name, and implement step by step a `jmap` compliant > implementation, that will be exposed on a separate port. No modification in > `jmap-draft` integration test should be counducted. > This will allow existing `jmap-draft` clients to smoothly transition to > `jmap`, then trigger the classic "deprecation-then-removal" process. > For now, as a first implementation step, we will only support `jmap` on top > of memory-guice (ease testing, speed of development). To ensure a > `storage-compliant` behavior of newly introduced storage APIs, we should use > persistent datastructures (like the one in vavr) and always deep-copy objects > at the storage boundaries. -- 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-2884) Update JMAP implementation to conform to RFC 8620/8621
[ https://issues.apache.org/jira/browse/JAMES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit updated JAMES-2884: -- Description: Historically, James is an early adopter for the JMAP specification, and a first partial implementation was conducted when JMAP was just a draft. IETF draft undergo radical changes and the community could not keep this implementation up to date with the spec changes. As off summer 2019, JMAP core ([RFC 8620|https://tools.ietf.org/html/rfc8620]) and JMAP mail ([RFC 8621|https://tools.ietf.org/html/rfc8621]) had been officially published (will not change anymore). Thus we should implement these new specifications. Point of attention: part of the community actively rely on the actual 'draft' implementation of JMAP existing in James. We should ensure no changes is done to that 'draft' protocol is done while implementing the new one. The proposed approach is to keep the current implementation under the `jmap-draft` name, and implement step by step a `jmap` compliant implementation, that will be exposed on a separate port. No modification in `jmap-draft` integration test should be counducted. This will allow existing `jmap-draft` clients to smoothly transition to `jmap`, then trigger the classic "deprecation-then-removal" process. For now, as a first implementation step, we will only support `jmap` on top of memory-guice (ease testing, speed of development). To ensure a `storage-compliant` behavior of newly introduced storage APIs, we should use persistent datastructures (like the one in vavr) and always deep-copy objects at the storage boundaries. was: At the time this issue was created James implements an outdated draft version of the JMAP protocol. Since then the protocol has been changed and standardized as [RFC 8620|https://tools.ietf.org/html/rfc8620] and [RFC 8621|https://tools.ietf.org/html/rfc8621]. James' implementation needs to be updated to match the final specification. > Update JMAP implementation to conform to RFC 8620/8621 > -- > > Key: JAMES-2884 > URL: https://issues.apache.org/jira/browse/JAMES-2884 > Project: James Server > Issue Type: Improvement > Components: JMAP >Reporter: cketti >Assignee: Antoine Duprat >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Historically, James is an early adopter for the JMAP specification, and a > first partial implementation was conducted when JMAP was just a draft. IETF > draft undergo radical changes and the community could not keep this > implementation up to date with the spec changes. > As off summer 2019, JMAP core ([RFC > 8620|https://tools.ietf.org/html/rfc8620]) and JMAP mail ([RFC > 8621|https://tools.ietf.org/html/rfc8621]) had been officially published > (will not change anymore). Thus we should implement these new specifications. > Point of attention: part of the community actively rely on the actual 'draft' > implementation of JMAP existing in James. We should ensure no changes is done > to that 'draft' protocol is done while implementing the new one. > The proposed approach is to keep the current implementation under the > `jmap-draft` name, and implement step by step a `jmap` compliant > implementation, that will be exposed on a separate port. No modification in > `jmap-draft` integration test should be counducted. > This will allow existing `jmap-draft` clients to smoothly transition to > `jmap`, then trigger the classic "deprecation-then-removal" process. > For now, as a first implementation step, we will only support `jmap` on top > of memory-guice (ease testing, speed of development). To ensure a > `storage-compliant` behavior of newly introduced storage APIs, we should use > persistent datastructures (like the one in vavr) and always deep-copy objects > at the storage boundaries. -- 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-2884) Update JMAP implementation to conform to RFC 8620/8621
[ https://issues.apache.org/jira/browse/JAMES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit updated JAMES-2884: -- Parent: (was: JAMES-2887) Issue Type: Improvement (was: Sub-task) > Update JMAP implementation to conform to RFC 8620/8621 > -- > > Key: JAMES-2884 > URL: https://issues.apache.org/jira/browse/JAMES-2884 > Project: James Server > Issue Type: Improvement > Components: JMAP >Reporter: cketti >Assignee: Antoine Duprat >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > At the time this issue was created James implements an outdated draft version > of the JMAP protocol. Since then the protocol has been changed and > standardized as [RFC 8620|https://tools.ietf.org/html/rfc8620] and [RFC > 8621|https://tools.ietf.org/html/rfc8621]. > James' implementation needs to be updated to match the final specification. -- 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-2884) Update JMAP implementation to conform to RFC 8620/8621
[ https://issues.apache.org/jira/browse/JAMES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit updated JAMES-2884: -- Parent: JAMES-2887 Issue Type: Sub-task (was: Improvement) > Update JMAP implementation to conform to RFC 8620/8621 > -- > > Key: JAMES-2884 > URL: https://issues.apache.org/jira/browse/JAMES-2884 > Project: James Server > Issue Type: Sub-task > Components: JMAP >Reporter: cketti >Assignee: Antoine Duprat >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > At the time this issue was created James implements an outdated draft version > of the JMAP protocol. Since then the protocol has been changed and > standardized as [RFC 8620|https://tools.ietf.org/html/rfc8620] and [RFC > 8621|https://tools.ietf.org/html/rfc8621]. > James' implementation needs to be updated to match the final specification. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2887) Implement JMAP RFC-8620 & RFC-8621
Tellier Benoit created JAMES-2887: - Summary: Implement JMAP RFC-8620 & RFC-8621 Key: JAMES-2887 URL: https://issues.apache.org/jira/browse/JAMES-2887 Project: James Server Issue Type: New Feature Components: JMAP Reporter: Tellier Benoit Assignee: Antoine Duprat Historically, James is an early adopter for the JMAP specification, and a first partial implementation was conducted when JMAP was just a draft. IETF draft undergo radical changes and the community could not keep this implementation up to date with the spec changes. As off summer 2019, JMAP core (RFC-2860) and JMAP mail (RFC 8621) had been officially published (will not change anymore). Thus we should implement these new specifications. Point of attention: part of the community actively rely on the actual 'draft' implementation of JMAP existing in James. We should ensure no changes is done to that 'draft' protocol is done while implementing the new one. The proposed approach is to keep the current implementation under the `jmap-draft` name, and implement step by step a `jmap` compliant implementation, that will be exposed on a separate port. No modification in `jmap-draft` integration test should be counducted. This will allow existing `jmap-draft` clients to smoothly transition to `jmap`, then trigger the classic "deprecation-then-removal" process. For now, as a first implementation step, we will only support `jmap` on top of memory-guice (ease testing, speed of development). To ensure a `storage-compliant` behavior of newly introduced storage APIs, we should use persistent datastructures (like the one in vavr) and always deep-copy objects at the storage boundaries. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2886) Unable to usetransitive dependencies at runtime in Guice extension jars
Tellier Benoit created JAMES-2886:
-
Summary: Unable to usetransitive dependencies at runtime in Guice
extension jars
Key: JAMES-2886
URL: https://issues.apache.org/jira/browse/JAMES-2886
Project: James Server
Issue Type: Bug
Components: guice, Matchers/Mailets (bundled)
Affects Versions: 3.4.0
Reporter: Tellier Benoit
As reported by @AaronRegan , we are unable to resolve transitive dependencies
in extension jars.
# Steps to reproduce
Given a maven module containing a custom mailet, instanciating objects as part
of the *service* method that are NOT part of James classpath:
- 1. Start *any* James guice application
- 2. Drop the JAR of the aforementioned in extension-jars folder
- 3. Configure the mailet within the mailet pipeline
- 4. Process a mail and
- 5. Notice runtime failures! The service method does not succeed to
instanciate the object not being part of James classpath.
As off commit 42d7d55d5380d13648533160844d30f765a2c6f1, such a JAR could very
well be the *apache-mailet-crypto* JAR.
This would result in :
{code:java}
java.lang.ClassNotFoundException:
org.bouncycastle.mail.smime.SMIMESignedGenerator
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 82 common frames omitted
Wrapped by: java.lang.NoClassDefFoundError:
org/bouncycastle/mail/smime/SMIMESignedGenerator
at
org.apache.james.transport.SMIMEKeyHolder.createGenerator(SMIMEKeyHolder.java:208)
at org.apache.james.transport.SMIMEKeyHolder.generate(SMIMEKeyHolder.java:251)
at
org.apache.james.transport.mailets.AbstractSign.service(AbstractSign.java:486)
at
org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:81)
at
org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.handleMailet(CamelMailetProcessor.java:178)
at
org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.lambda$configure$0(CamelMailetProcessor.java:155)
at
org.apache.camel.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:63)
... 75 common frames omitted
{code}
# What to do from here
- Write a test reproducing that behavior...
- Bundle *apache-mailet-crypto* within supported guice app mailets
- Fix that annoying transitive dependency issue - this is in my opinion a
blocker for Guice adoption.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2477) Allow partial, incremental James build
[ https://issues.apache.org/jira/browse/JAMES-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931020#comment-16931020 ] Tellier Benoit commented on JAMES-2477: --- https://github.com/linagora/james-project/pull/2685 allowed passing extra MVN arguments to the integration tests > Allow partial, incremental James build > -- > > Key: JAMES-2477 > URL: https://issues.apache.org/jira/browse/JAMES-2477 > Project: James Server > Issue Type: Improvement > Components: Build System >Reporter: Tellier Benoit >Priority: Major > > We should have a profile allowing to only test maven modules impacted by > changes. > This would allow reducing a bit pull request test time. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931019#comment-16931019 ] Tellier Benoit commented on JAMES-2865: --- https://github.com/linagora/james-project/pull/2675 provided a fluent HTTP client written in Java thanks to the Feign library. > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2882) Document IMAP delegation using administratorId property.
[ https://issues.apache.org/jira/browse/JAMES-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2882. - Fix Version/s: 3.5.0 Resolution: Fixed https://github.com/linagora/james-project/pull/2689 added an example. Note that this was documented, just the newest version of the site was not deployed... > Document IMAP delegation using administratorId property. > > > Key: JAMES-2882 > URL: https://issues.apache.org/jira/browse/JAMES-2882 > Project: James Server > Issue Type: Improvement > Components: Documentation, IMAPServer, UsersStore > UsersRepository >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > As reported by Jerry Malcom on the mailing list, we miss documentation - & > example- regarding this... -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930227#comment-16930227 ] Tellier Benoit commented on JAMES-2865: --- https://github.com/linagora/james-project/pull/2672 proposed a nicer builder > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2883) SearchIndex should not attempt to read a deleted mailbox
[ https://issues.apache.org/jira/browse/JAMES-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2883. - > SearchIndex should not attempt to read a deleted mailbox > > > Key: JAMES-2883 > URL: https://issues.apache.org/jira/browse/JAMES-2883 > Project: James Server > Issue Type: Bug > Components: mailbox >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > Currently, deleting a mailbox leads to errors as the search index tries to > resolve the mailboxId of a no more existing mailbox. > It's failing. > It's retied. > It waists test time. And data are no longer cleared. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2883) SearchIndex should not attempt to read a deleted mailbox
[ https://issues.apache.org/jira/browse/JAMES-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit resolved JAMES-2883. --- Fix Version/s: 3.5.0 Resolution: Fixed https://github.com/linagora/james-project/pull/2687 fixed the issue > SearchIndex should not attempt to read a deleted mailbox > > > Key: JAMES-2883 > URL: https://issues.apache.org/jira/browse/JAMES-2883 > Project: James Server > Issue Type: Bug > Components: mailbox >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > Currently, deleting a mailbox leads to errors as the search index tries to > resolve the mailboxId of a no more existing mailbox. > It's failing. > It's retied. > It waists test time. And data are no longer cleared. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JSIEVE-111) Libraries upgrade
[
https://issues.apache.org/jira/browse/JSIEVE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JSIEVE-111.
-
Fix Version/s: 0.6
Resolution: Fixed
> Libraries upgrade
> -
>
> Key: JSIEVE-111
> URL: https://issues.apache.org/jira/browse/JSIEVE-111
> Project: James jSieve
> Issue Type: Wish
>Reporter: Rene Cordier
>Priority: Major
> Fix For: 0.6
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Libs update:
> {code:java}
> 4 [INFO] com.google.guava:guava .. 18.0 ->
> 28.1-jre
> 4 [INFO] commons-logging:commons-logging . 1.1.1 ->
> 1.2
> 4 [INFO] javax.mail:mail ... 1.4.4 ->
> 1.5.0-b01
> 4 [INFO] jmock:jmock . 1.2.0 ->
> 20031129.200437
> 4 [INFO] junit:junit .. 4.10 ->
> 4.13-beta-3
> 4 [INFO] log4j:log4j . 1.2.14 ->
> 1.2.17
> 4 [INFO] org.apache.james:apache-mime4j-core ... 0.8.1 ->
> 0.8.3
> 8 [INFO] org.apache.maven.doxia:doxia-core . 1.2 ->
> 1.9
> 2 [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.13.2
> 4 [INFO] org.mockito:mockito-core .. 1.9.0 ->
> 3.0.0{code}
>
> Plugins update:
> {code:java}
> 1 [INFO] maven-compiler-plugin .. 3.0 -> 3.3
> 1 [INFO] maven-compiler-plugin 3.0 -> 3.7.0
> 1 [INFO] maven-compiler-plugin 3.0 -> 3.8.0
> 2 [INFO] maven-site-plugin .. 3.5.1 -> 3.7.1
> 1 [INFO] org.apache.felix:maven-bundle-plugin ... 2.3.7 -> 2.5.4
> 1 [INFO] org.apache.felix:maven-bundle-plugin ... 2.3.7 -> 4.0.0
> 1 [INFO] org.apache.felix:maven-bundle-plugin ... 2.3.7 -> 4.2.0
> 2 [INFO] org.apache.felix:maven-bundle-plugin ... 4.2.0 -> 4.0.0
> 1 [INFO] org.codehaus.mojo:build-helper-maven-plugin .. 1.7 ->
> 3.0.0{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JSIEVE-112) Use SLF4J & logback for logging
[ https://issues.apache.org/jira/browse/JSIEVE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-112. - Fix Version/s: 0.6 Resolution: Fixed > Use SLF4J & logback for logging > --- > > Key: JSIEVE-112 > URL: https://issues.apache.org/jira/browse/JSIEVE-112 > Project: James jSieve > Issue Type: Improvement >Reporter: Tellier Benoit >Priority: Major > Fix For: 0.6 > > Time Spent: 2.5h > Remaining Estimate: 0h > > We should rely on SLF4J for logging within JSIEVE library and use > logback-classic for tests. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2883) SearchIndex should not attempt to read a deleted mailbox
Tellier Benoit created JAMES-2883: - Summary: SearchIndex should not attempt to read a deleted mailbox Key: JAMES-2883 URL: https://issues.apache.org/jira/browse/JAMES-2883 Project: James Server Issue Type: Bug Components: mailbox Reporter: Tellier Benoit Currently, deleting a mailbox leads to errors as the search index tries to resolve the mailboxId of a no more existing mailbox. It's failing. It's retied. It waists test time. And data are no longer cleared. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2882) Document IMAP delegation using administratorId property.
Tellier Benoit created JAMES-2882: - Summary: Document IMAP delegation using administratorId property. Key: JAMES-2882 URL: https://issues.apache.org/jira/browse/JAMES-2882 Project: James Server Issue Type: Improvement Components: Documentation, IMAPServer, UsersStore UsersRepository Reporter: Tellier Benoit As reported by Jerry Malcom on the mailing list, we miss documentation - & example- regarding this... -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2813) Implement a distributed task manager
[ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927452#comment-16927452 ] Tellier Benoit commented on JAMES-2813: --- I just merged Pull Requests related to Additional Information serialization: - https://github.com/linagora/james-project/pull/2654 - https://github.com/linagora/james-project/pull/2663 - https://github.com/linagora/james-project/pull/2660 > Implement a distributed task manager > > > Key: JAMES-2813 > URL: https://issues.apache.org/jira/browse/JAMES-2813 > Project: James Server > Issue Type: Task >Reporter: Matthieu Baechler >Priority: Major > > Following JAMES-2272, we now would like to handle tasks at a cluster level. > For that, we intend to use a combination of Event Sourcing for keeping track > of Tasks submitted and RabbitMQ for dispatching the tasks in the cluster. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSIEVE-112) Use SLF4J & logback for logging
Tellier Benoit created JSIEVE-112: - Summary: Use SLF4J & logback for logging Key: JSIEVE-112 URL: https://issues.apache.org/jira/browse/JSIEVE-112 Project: James jSieve Issue Type: Improvement Reporter: Tellier Benoit We should rely on SLF4J for logging within JSIEVE library and use logback-classic for tests. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2703) Deprecation after 3.3.0 - Removal after 3.4.0
[ https://issues.apache.org/jira/browse/JAMES-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926302#comment-16926302 ] Tellier Benoit commented on JAMES-2703: --- See https://github.com/linagora/james-project/pull/2679 for removals after 3.4.0 > Deprecation after 3.3.0 - Removal after 3.4.0 > - > > Key: JAMES-2703 > URL: https://issues.apache.org/jira/browse/JAMES-2703 > Project: James Server > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.4.0 > > > In order to improve overall James development experience, I propose to do a > bit of post 3.3.0 cleanup. > The proposal is to mark the given components as deprecated now, then, if no > contributor shows up and give some love to these components, remove it after > 3.4.0 release. > An associated vote will be started on the mailing list. > Here are the rationals: > - Some components are not exposed to end users and affect our ability to > refactor code. > - These components do not receive contributions > - These components are not well enough tested > - We introduced some components that are better at performing that very task > The components are: > *mailbox* > - mailbox/cache >Unused, not tested, low code quality >End user will not be affected by this removal > *server/data* > - SieveDefaultRepository >Read the filesystem to retrieve sieve scripts, read only, one file per user >This does not support sieve script management and rtequires dropping > manually the filesystem >Migration strategy: use SieveFileRepository & CLI to upload scripts > - MBoxFileRepository >Already deprecated, will target removal after 3.4.0 >Use FileMailRepository instead. Data migration can be done with > reprocessing + specific configuration > - JDBCRecipientRewriteTable >Already deprecated, will target removal after 3.4.0 >Use another RRT implementation > - AbstractJdbcUsersRepository DefaultUsersJdbcRepository & > JamesUsersJdbcRepository >Already deprecated, will target removal after 3.4.0 >Use another UsersRepository implementation > *mailets* > Note: these mailets are leveraging some storage capabilities of mailbox or > server/data. > - AbstractRecipientRewriteTable >Already deprecated, will target removal after 3.4.0 >The mailet is responsible for the rule storage. No tests. >Note that this would allow removing JDBCRecipientRewriteTable and > XMLRecipientRewriteTable. >Migration plan: add the rules in the standard RRT and use the classic RRT > mailet. > > - JDBCAlias >Already deprecated, will target removal after 3.4.0 >This mailet does the RRT. No tests. >Migration plan: add the rules in the standard RRT and use the classic RRT > mailet. > - UsersRepositoryAliasingForwarding >Already deprecated, will target removal after 3.4.0 >This buggy mailet expects the UsersRepository to be also a > RecipientRewriteTable. Hopefully, we have no such freaks. >Otherwise behaves as the classic RRT mailet. >Migration: Replace in the configuration by the classic RRT mailet > - MailboxQuotaFixed, AbstractStorageQuota, AbstractQuotaMatcher >Not using the quota API, these matchers do full inbox scans on each > processed email. >It adds confiusion with the non-experimental well tests IsOverQuota > matcher, relying on the mailbox quota system. >No test, big hierarchy >Migration plan: Use IsOverQuota + quota APIs -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2701) Drop deprecations for JAMES 3.4.0
[ https://issues.apache.org/jira/browse/JAMES-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2701. - Resolution: Duplicate JAMES-2703 > Drop deprecations for JAMES 3.4.0 > - > > Key: JAMES-2701 > URL: https://issues.apache.org/jira/browse/JAMES-2701 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Trivial > > Numerous deprecated code remains since a long time, this ticket is present to > remove them. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2813) Implement a distributed task manager
[ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926273#comment-16926273 ] Tellier Benoit commented on JAMES-2813: --- https://github.com/linagora/james-project/pull/2670 *expose node informations in webadmin execution details* is merged > Implement a distributed task manager > > > Key: JAMES-2813 > URL: https://issues.apache.org/jira/browse/JAMES-2813 > Project: James Server > Issue Type: Task >Reporter: Matthieu Baechler >Priority: Major > > Following JAMES-2272, we now would like to handle tasks at a cluster level. > For that, we intend to use a combination of Event Sourcing for keeping track > of Tasks submitted and RabbitMQ for dispatching the tasks in the cluster. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2097) Using full recipients for following MX iteration when partial fails on delivering
[
https://issues.apache.org/jira/browse/JAMES-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2097.
-
Fix Version/s: 3.5.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/2662 solved that
> Using full recipients for following MX iteration when partial fails on
> delivering
> -
>
> Key: JAMES-2097
> URL: https://issues.apache.org/jira/browse/JAMES-2097
> Project: James Server
> Issue Type: Bug
> Components: Remote Delivery
>Reporter: TzeKai Lee
>Priority: Major
> Fix For: 3.5.0
>
>
> Untested, just looks weird to me when browsing code.
> In the {{SendFailedExceptionMail}} handling of {{Delivrer.doDeliver}}, there
> is no update of recipients to valid unsent addresses like it did in the
> exception handling of {{Delivrer.deliver}}.
> It seems to me that if dns resolved more than one MX and for some reason the
> first MX only accept partial recipients and the other MX accept full
> recipients, it will result duplicated mail for the partially accepted
> recipients
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2880) disable auto_snapshot for cassandra in test
[
https://issues.apache.org/jira/browse/JAMES-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926271#comment-16926271
]
Tellier Benoit commented on JAMES-2880:
---
https://github.com/linagora/james-project/pull/2677 becreased auto_snapshot
size in tests, that caused the leak.
> disable auto_snapshot for cassandra in test
> ---
>
> Key: JAMES-2880
> URL: https://issues.apache.org/jira/browse/JAMES-2880
> Project: James Server
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Rémi Kowalski
>Priority: Major
>
> Only 200mo are allocated to
> {color:#008000}/var/lib/cassandra{color}
> Some repeated tests failed after some time because the volume was full.
> With the logs we could see that there was some space usage leak.
> It was due to using auto_snapshot in cassandra.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSPF-103) Library upgrade
Tellier Benoit created JSPF-103:
---
Summary: Library upgrade
Key: JSPF-103
URL: https://issues.apache.org/jira/browse/JSPF-103
Project: James jSPF
Issue Type: Improvement
Reporter: Tellier Benoit
{code:java}
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO] commons-cli:commons-cli ... 1.2 -> 1.4
[INFO] dnsjava:dnsjava ... 2.0.8 -> 2.1.9
[INFO] junit:junit . 3.8.1 -> 4.13-beta-3
[INFO] log4j:log4j . 1.2.14 -> 1.2.17
[INFO]
[INFO] The following dependencies in pluginManagement of plugins have newer
versions:
[INFO] org.apache.maven.doxia:doxia-core . 1.2 -> 1.9
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JDKIM-43) Libraries upgrade
[
https://issues.apache.org/jira/browse/JDKIM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JDKIM-43.
---
Fix Version/s: 0.3
Resolution: Fixed
> Libraries upgrade
> -
>
> Key: JDKIM-43
> URL: https://issues.apache.org/jira/browse/JDKIM-43
> Project: James jDKIM
> Issue Type: Wish
>Reporter: Rene Cordier
>Priority: Major
> Fix For: 0.3
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Libraries upgrade:
> {code:java}
> 4 [INFO] org.apache.geronimo.javamail:geronimo-javamail_1.4_mail1.8.3 ->
> 1.9.0-alpha-2
> 4 [INFO] commons-codec:commons-codec .. 1.7 ->
> 1.13
> 4 [INFO] commons-logging:commons-logging . 1.1.1 ->
> 1.2
> 4 [INFO] dnsjava:dnsjava ... 2.1.1 ->
> 2.1.9
> 4 [INFO] junit:junit .. 4.10 ->
> 4.13-beta-3
> 5 [INFO] log4j:log4j . 1.2.16 ->
> 1.2.17
> 4 [INFO] org.apache.james:apache-mailet-api 3.1.0 ->
> 3.3.0
> 4 [INFO] org.apache.james:apache-mailet-base ... 3.1.0 ->
> 3.3.0
> 4 [INFO] org.apache.james:apache-mime4j-core ... 0.8.1 ->
> 0.8.3
> 4 [INFO] org.apache.james:apache-mime4j-dom 0.8.1 ->
> 0.8.3
> 8 [INFO] org.apache.maven.doxia:doxia-core . 1.2 ->
> 1.9
> 4 [INFO] org.apache.maven.wagon:wagon-ssh 2.0 ->
> 3.3.3
> {code}
>
> Plugins upgrade:
> {code:java}
> 1 [INFO] maven-compiler-plugin .. 3.0 -> 3.3
> 1 [INFO] maven-compiler-plugin 3.0 -> 3.7.0
> 1 [INFO] maven-compiler-plugin 3.0 -> 3.8.0
> 1 [INFO] maven-site-plugin 3.3 -> 3.7.1
> 1 [INFO] maven-site-plugin .. 3.5.1 -> 3.7.1
> 1 [INFO] org.apache.felix:maven-bundle-plugin ... 2.3.7 -> 2.5.4
> 1 [INFO] org.apache.felix:maven-bundle-plugin ... 2.3.7 -> 4.0.0
> 1 [INFO] org.apache.felix:maven-bundle-plugin ... 2.3.7 -> 4.2.0
> 2 [INFO] org.apache.felix:maven-bundle-plugin ... 4.2.0 -> 4.0.0
> 1 [INFO] org.apache.rat:apache-rat-plugin .. 0.8 -> 0.11
> 1 [INFO] org.apache.rat:apache-rat-plugin .. 0.8 -> 0.13
> 1 [INFO] org.codehaus.mojo:versions-maven-plugin 2.0 ->
> 2.7{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2097) Using full recipients for following MX iteration when partial fails on delivering
[
https://issues.apache.org/jira/browse/JAMES-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923869#comment-16923869
]
Tellier Benoit commented on JAMES-2097:
---
https://github.com/linagora/james-project/pull/2658 (integration test) is merged
> Using full recipients for following MX iteration when partial fails on
> delivering
> -
>
> Key: JAMES-2097
> URL: https://issues.apache.org/jira/browse/JAMES-2097
> Project: James Server
> Issue Type: Bug
> Components: Remote Delivery
>Reporter: TzeKai Lee
>Priority: Major
>
> Untested, just looks weird to me when browsing code.
> In the {{SendFailedExceptionMail}} handling of {{Delivrer.doDeliver}}, there
> is no update of recipients to valid unsent addresses like it did in the
> exception handling of {{Delivrer.deliver}}.
> It seems to me that if dns resolved more than one MX and for some reason the
> first MX only accept partial recipients and the other MX accept full
> recipients, it will result duplicated mail for the partially accepted
> recipients
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2442) Integration tests for RemoteDelivery
[ https://issues.apache.org/jira/browse/JAMES-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2442. - Fix Version/s: 3.5.0 Resolution: Fixed https://github.com/linagora/james-project/pull/2641 contributed remaining integration tests mentioned here on top of the brand new Mock SMTP server > Integration tests for RemoteDelivery > > > Key: JAMES-2442 > URL: https://issues.apache.org/jira/browse/JAMES-2442 > Project: James Server > Issue Type: New Feature > Components: DNSServer, Matchers/Mailets (bundled) >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.5.0 > > > Currently tested: > Gateway is working > Direct resolution is working > DNS failures generate a bounce. When bounce processor is specified, and when > it is not. > We would need to test : > * That an unreachable MX IP will generate a failover to the second MX when > direct resolution > * That an unreachable gateway IP will generate a failover to the second > gateway > * If all MX/gateway IPs are not reachable, a bounce is sent > * 5XX Errors don't trigger failover and a bounce is directly sent > * 4XX codes don't trigger failover, and will be retried. Moreover they can > succeed on second try, generating no bounce. > * 4XX codes, if answered on each try, will lead to a bounce > Partial failure (some recipients are failing, some success): > * Only failed (but valid) recipients should be retried (EG 450) and can > suddeed on second try > * Only failed (but valid) recipients should be retried (EG 450) and will > generate a bounce if repeated > * Invalid recipients (EG 550) directly generate a bounce, and will not be > retried > * Valid, and well delivered recipients wont be re-delivered -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923867#comment-16923867 ] Tellier Benoit commented on JAMES-2865: --- https://github.com/linagora/james-project/pull/2659 Did a bit of cleanup > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2865. - Fix Version/s: 3.5.0 Resolution: Fixed > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2876) Add Github metadata
[ https://issues.apache.org/jira/browse/JAMES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2876. - Fix Version/s: 3.5.0 Resolution: Fixed https://github.com/linagora/james-project/pull/2664 solved that > Add Github metadata > --- > > Key: JAMES-2876 > URL: https://issues.apache.org/jira/browse/JAMES-2876 > Project: James Server > Issue Type: Improvement >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.5.0 > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > allows us to add metadata to the project on GitHub: description, homepage, > labels... > This will help the project gaining some visibility. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923864#comment-16923864
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2668 JAMES-2855 Upgrade to
maven 3.6.2
This significantly decrease head allocation.
CF:
https://github.com/quick-perf/maven-test-bench#benchmark-heap-allocation-of-several-maven-releases
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223
[jira] [Created] (JAMES-2876) Add Github metadata
Tellier Benoit created JAMES-2876: - Summary: Add Github metadata Key: JAMES-2876 URL: https://issues.apache.org/jira/browse/JAMES-2876 Project: James Server Issue Type: Improvement Reporter: Tellier Benoit https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories allows us to add metadata to the project on GitHub: description, homepage, labels... This will help the project gaining some visibility. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2097) Using full recipients for following MX iteration when partial fails on delivering
[
https://issues.apache.org/jira/browse/JAMES-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922200#comment-16922200
]
Tellier Benoit commented on JAMES-2097:
---
https://github.com/linagora/james-project/pull/2658 added an integration test
for this bug report
https://github.com/linagora/james-project/pull/2662 proposed a fix for this bug
> Using full recipients for following MX iteration when partial fails on
> delivering
> -
>
> Key: JAMES-2097
> URL: https://issues.apache.org/jira/browse/JAMES-2097
> Project: James Server
> Issue Type: Bug
> Components: Remote Delivery
>Reporter: TzeKai Lee
>Priority: Major
>
> Untested, just looks weird to me when browsing code.
> In the {{SendFailedExceptionMail}} handling of {{Delivrer.doDeliver}}, there
> is no update of recipients to valid unsent addresses like it did in the
> exception handling of {{Delivrer.deliver}}.
> It seems to me that if dns resolved more than one MX and for some reason the
> first MX only accept partial recipients and the other MX accept full
> recipients, it will result duplicated mail for the partially accepted
> recipients
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1994) Merge marketting website and current website
[ https://issues.apache.org/jira/browse/JAMES-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921936#comment-16921936 ] Tellier Benoit commented on JAMES-1994: --- https://github.com/linagora/james-project/pull/2650 is adding a link for non-docker getting started tutorial on the homepage > Merge marketting website and current website > > > Key: JAMES-1994 > URL: https://issues.apache.org/jira/browse/JAMES-1994 > Project: James Server > Issue Type: Task >Reporter: Quynh Nguyen >Priority: Major > > Its source code should be in src/site > The docker should generate the complete website. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921935#comment-16921935
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2644 contributed a plugin upgrade
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration ..
> 1.9 -> 1.10
> 223 [INFO] commons-daemon:commons-daemon .
>
[jira] [Resolved] (JAMES-2868) Http route for getting all mails stored in the MockSmtpServer
[
https://issues.apache.org/jira/browse/JAMES-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit resolved JAMES-2868.
---
Fix Version/s: 3.4.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/2649 is merged
> Http route for getting all mails stored in the MockSmtpServer
> -
>
> Key: JAMES-2868
> URL: https://issues.apache.org/jira/browse/JAMES-2868
> Project: James Server
> Issue Type: Sub-task
> Components: Remote Delivery, tests
>Reporter: Tellier Benoit
>Assignee: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> List all of mails (JAMES-2864 + JAMES-2865) are successfully stored in the
> MockSmtpServer
> ```
> GET /mails
> - 200: ok
> ```
> ```json
> [
> {
>"envelope": {
> "from": "f...@domain.tld",
> "recipients": ["recipie...@domain.tld", "recipie...@domain.tld"]
> },
>"content": "mail content here"
> },
> ...
> ]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2867) dockerize the MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2867. - Resolution: Fixed https://github.com/linagora/james-project/pull/2614 is merged > dockerize the MockSmtpServer > > > Key: JAMES-2867 > URL: https://issues.apache.org/jira/browse/JAMES-2867 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > > - Create a standalong java application for this. > - Provide the Dockerfile, and a container > The MockSmtpServer will be used for RemoteDelivery intergration tests where > james connect to SMTP server by remote IP address (not local host), we need > to have docker containers running this MockSmptServer inside, exposing port > 25. Then add the docker container IPs to DNS service. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921109#comment-16921109 ] Tellier Benoit commented on JAMES-2865: --- https://github.com/linagora/james-project/pull/2647 added condition filtering > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919170#comment-16919170 ] Tellier Benoit commented on JAMES-2865: --- https://github.com/linagora/james-project/pull/2631 added answer counting > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918356#comment-16918356
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2643 upgraded commons-compress
to 1.19
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration ..
> 1.9 -> 1.10
> 223 [INFO] commons-daemon:commons-daemon
[jira] [Commented] (JAMES-2545) Implement a HealthCheck for RabbitMQ component
[ https://issues.apache.org/jira/browse/JAMES-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918355#comment-16918355 ] Tellier Benoit commented on JAMES-2545: --- https://github.com/linagora/james-project/pull/2636 binded that healthcheck in guice products > Implement a HealthCheck for RabbitMQ component > -- > > Key: JAMES-2545 > URL: https://issues.apache.org/jira/browse/JAMES-2545 > Project: James Server > Issue Type: Improvement > Components: Queue >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.2.0 > > > This health check will simply try to open a connection to rabbitMQ -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917656#comment-16917656
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2642 fixed some log issue after
the upgrade
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration ..
> 1.9 -> 1.10
> 223 [INFO] commons-daemon:commons-daemon
[jira] [Commented] (JAMES-2865) Implementing a MockSmtpServer
[ https://issues.apache.org/jira/browse/JAMES-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917654#comment-16917654 ] Tellier Benoit commented on JAMES-2865: --- https://github.com/linagora/james-project/pull/2623 proposed a simple mocked SMTP server - No answer count - No condition filtering - No soft failure - only hard reject is supported > Implementing a MockSmtpServer > - > > Key: JAMES-2865 > URL: https://issues.apache.org/jira/browse/JAMES-2865 > Project: James Server > Issue Type: Sub-task > Components: Remote Delivery, tests >Reporter: Tellier Benoit >Assignee: Tellier Benoit >Priority: Major > > Draft version [here](https://github.com/linagora/james-project/pull/2545) > The MockSmtpServer should match these criteria: > - can return error responses > - can return error responses but actually still success to deliver the mails > (450 - server retry and will be success) > - act like a simple smtp server if no mock setup, when mails come, save them > in to the memory > Regarding the behaviour: > - a behaviour can be applied to all given commands or a subset of them > (condition) > - A number of answer can be specified, after X answers the behaviour will no > longer be applied. > You need to rely on the following POJOs : see JAMES-2853 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2874) Maven should reuse forks
[ https://issues.apache.org/jira/browse/JAMES-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2874. - Fix Version/s: 3.4.0 Resolution: Fixed https://github.com/linagora/james-project/pull/2566 proposed this We still remain to reuse forks in server/app project > Maven should reuse forks > > > Key: JAMES-2874 > URL: https://issues.apache.org/jira/browse/JAMES-2874 > Project: James Server > Issue Type: Improvement > Components: Build System >Reporter: Tellier Benoit >Priority: Major > Fix For: 3.4.0 > > > This enables: > - to fasten tests > - to detect some leaks > This could be a first moving step for gradle hypothetic adoption. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2874) Maven should reuse forks
Tellier Benoit created JAMES-2874: - Summary: Maven should reuse forks Key: JAMES-2874 URL: https://issues.apache.org/jira/browse/JAMES-2874 Project: James Server Issue Type: Improvement Components: Build System Reporter: Tellier Benoit This enables: - to fasten tests - to detect some leaks This could be a first moving step for gradle hypothetic adoption. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2855.
-
Fix Version/s: 3.4.0
Resolution: Fixed
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12 ->
> 2.0.15
> 223 [INFO] commons-configuration:commons-configuration ..
> 1.9 -> 1.10
> 223 [INFO] commons-daemon:commons-daemon .
> 1.1.0 -> 1.2.0
> 223 [INFO] commons-logging:commons-logging
[jira] [Closed] (JAMES-2866) MockSMTP server behaviors setup over HTTP
[
https://issues.apache.org/jira/browse/JAMES-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2866.
-
Fix Version/s: 3.4.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/2625
> MockSMTP server behaviors setup over HTTP
> -
>
> Key: JAMES-2866
> URL: https://issues.apache.org/jira/browse/JAMES-2866
> Project: James Server
> Issue Type: Sub-task
> Components: Remote Delivery, tests
>Reporter: Tellier Benoit
>Assignee: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> You can setup your route by using spark-java library or any other light HTTP
> server library written in Java as you think it's better.
> JSON serialization for JAMES-2853 POJOs is needed as well. No data stability
> required (not an external API, it's for testing purposes).
> {code:java}
> PUT /smtpBehaviors
> - 204: ok, created
> GET /smtpBehaviors
> - 200 OK, JSON:
> [
> {
> "command": "RCPT",
> "condition": {
> "operator": "contains",
> "matchingValue": "pippin got the ring"
> },
> "response": {
> "code": 504,
> "rejected": false,
> "message": "server is out of memory"
> },
> "numberOfAnswer": 7
> },
> ...
> ]
> DELETE /smtpBehaviors
> - 204: ok, cleared the mock setups
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2855) James dependencies upgrade 08/2019
[
https://issues.apache.org/jira/browse/JAMES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916479#comment-16916479
]
Tellier Benoit commented on JAMES-2855:
---
https://github.com/linagora/james-project/pull/2606 upgraded docker files
https://github.com/linagora/james-project/pull/2613 fixed logging issues
introduced by the commons configuration upgrade
https://github.com/linagora/james-project/pull/2630 Upgraded Junit 5 and solved
related problems
> James dependencies upgrade 08/2019
> --
>
> Key: JAMES-2855
> URL: https://issues.apache.org/jira/browse/JAMES-2855
> Project: James Server
> Issue Type: Improvement
>Reporter: Trần Tiến Đức
>Priority: Major
>
> List of the dependencies
> {code:java}
> From: mvn versions:display-dependency-updates | grep -- '->' | sort | uniq -c
> 1 [INFO]
> net.javacrumbs.future-converter:future-converter-java8-guava 0.3.0 -> 1.2.0
> 223 [INFO]
> org.apache.karaf.tooling.exam:org.apache.karaf.tooling.exam.container
> ...2.3.0 -> 3.0.0.RC1
> 223 [INFO] org.apache.maven.plugin-tools:maven-plugin-annotations
> ... 3.4 -> 3.6.0
> 223 [INFO] ch.qos.logback:logback-classic . 1.2.3 ->
> 1.3.0-alpha4
> 223 [INFO] ch.qos.logback:logback-core 1.2.3 ->
> 1.3.0-alpha4
> 1 [INFO] com.amazonaws:aws-java-sdk-s3 ... 1.11.532
> -> 1.11.602
> 1 [INFO] com.datastax.cassandra:cassandra-driver-core ..
> 3.7.0 -> 4.0.0
> 223 [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-core .. 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] com.fasterxml.jackson.core:jackson-databind .. 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-annotations 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-core ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.core:jackson-databind ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-cbor ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-smile ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-xml ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.dataformat:jackson-dataformat-yaml ... 2.9.6
> -> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-guava ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jdk8 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-joda ... 2.9.6
> ->2.10.0.pr1
> [INFO] com.fasterxml.jackson.datatype:jackson-datatype-jsr310 ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... 2.9.6 ->
> 2.10.0.pr1
> [INFO] com.fasterxml.jackson.module:jackson-module-afterburner ... 2.9.6 ->
> 2.10.0.pr1
> 223 [INFO] org.codehaus.jackson:jackson-core-asl 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-jaxrs ... 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-mapper-asl .. 1.9.2
> -> 1.9.11
> 223 [INFO] org.codehaus.jackson:jackson-xc .. 1.9.2
> -> 1.9.11
> 223 [INFO] com.github.kongchen:swagger-maven-plugin ..
> 3.1.7 -> 3.1.8
> 223 [INFO] com.github.spullara.mustache.java:compiler
> 0.9.5 -> 0.9.6
> 1 [INFO] com.github.stefanbirkner:system-rules ... 1.18.0
> -> 1.19.0
> 1 [INFO] com.google.crypto.tink:tink ... 1.2.0 ->
> 1.3.0-rc1
> 1 [INFO] com.google.guava:guava .. 13.0
> -> 28.0-jre
> 1 [INFO] com.google.guava:guava .. 20.0
> -> 28.0-jre
> 223 [INFO] com.google.guava:guava .. 25.1-jre
> -> 28.0-jre
> 25 [INFO] com.google.inject.extensions:guice-assistedinject ...
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject.extensions:guice-assistedinject .
> 4.2.0 -> 4.2.2
> 223 [INFO] com.google.inject.extensions:guice-multibindings
> 4.0 -> 4.2.2
> 25 [INFO] com.google.inject:guice .
> 4.0 -> 4.2.2
> 198 [INFO] com.google.inject:guice ...
> 4.2.0 -> 4.2.2
> 223 [INFO] com.ibm.icu:icu4j ...
> 62.1 -> 64.2
> 223 [INFO] com.jayway.awaitility:awaitility ..
> 1.6.5 -> 1.7.0
> 223 [INFO] org.awaitility:awaitility . 3.1.2 ->
> 4.0.0-rc1
> [INFO] org.apache.pdfbox:pdfbox 2.0.12
[jira] [Updated] (JAMES-2866) MockSMTP server behaviors setup over HTTP
[
https://issues.apache.org/jira/browse/JAMES-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit updated JAMES-2866:
--
Description:
You can setup your route by using spark-java library or any other light HTTP
server library written in Java as you think it's better.
JSON serialization for JAMES-2853 POJOs is needed as well. No data stability
required (not an external API, it's for testing purposes).
{code:java}
PUT /smtpBehaviors
- 204: ok, created
GET /smtpBehaviors
- 200 OK, JSON:
[
{
"command": "RCPT",
"condition": {
"operator": "contains",
"matchingValue": "pippin got the ring"
},
"response": {
"code": 504,
"rejected": false,
"message": "server is out of memory"
},
"numberOfAnswer": 7
},
...
]
DELETE /smtpBehaviors
- 204: ok, cleared the mock setups
{code}
was:
You can setup your route by using spark-java library or any other light HTTP
server library written in Java as you think it's better.
JSON serialization for JAMES-2853 POJOs is needed as well. No data stability
required (not an external API, it's for testing purposes).
{code:java}
POST /smtpBehaviors
- 204: ok, created
GET /smtpBehaviors
- 200 OK, JSON:
[
{
"command": "RCPT",
"condition": {
"operator": "contains",
"matchingValue": "pippin got the ring"
},
"response": {
"code": 504,
"rejected": false,
"message": "server is out of memory"
},
"numberOfAnswer": 7
},
...
]
DELETE /smtpBehaviors
- 204: ok, cleared the mock setups
{code}
> MockSMTP server behaviors setup over HTTP
> -
>
> Key: JAMES-2866
> URL: https://issues.apache.org/jira/browse/JAMES-2866
> Project: James Server
> Issue Type: Sub-task
> Components: Remote Delivery, tests
>Reporter: Tellier Benoit
>Assignee: Tellier Benoit
>Priority: Major
>
> You can setup your route by using spark-java library or any other light HTTP
> server library written in Java as you think it's better.
> JSON serialization for JAMES-2853 POJOs is needed as well. No data stability
> required (not an external API, it's for testing purposes).
> {code:java}
> PUT /smtpBehaviors
> - 204: ok, created
> GET /smtpBehaviors
> - 200 OK, JSON:
> [
> {
> "command": "RCPT",
> "condition": {
> "operator": "contains",
> "matchingValue": "pippin got the ring"
> },
> "response": {
> "code": 504,
> "rejected": false,
> "message": "server is out of memory"
> },
> "numberOfAnswer": 7
> },
> ...
> ]
> DELETE /smtpBehaviors
> - 204: ok, cleared the mock setups
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2864) POJO for Mock Smtp server behavior, receive email
[
https://issues.apache.org/jira/browse/JAMES-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2864.
-
Fix Version/s: 3.4.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/2610 solved this
> POJO for Mock Smtp server behavior, receive email
> -
>
> Key: JAMES-2864
> URL: https://issues.apache.org/jira/browse/JAMES-2864
> Project: James Server
> Issue Type: Sub-task
> Components: Remote Delivery, tests
>Reporter: Tellier Benoit
>Assignee: Tellier Benoit
>Priority: Major
> Fix For: 3.4.0
>
>
> Designing POJO models be used by the MockSMTPServer and the HttpRoutes.
> {code:java}
> We will merge the java bean (POJO) and DTO into one so no need to the
> translator.
> ### The final MockSetup format:
> {
> "command": "RCPT",
> "condition": {
> "operator": "contains",
> "matchingValue": "pippin got the ring"
> },
> "response": {
> "code": 504,
> "rejected": false,
> "message": "server is out of memory"
> },
> "numberOfAnswer": 7
> }
> ### The MockMail format this will be used in the route of getting all stored
> email of the SMTP server
> {
>"envelope": {
>"from": "f...@domain.tld",
>"recipients": ["recipie...@domain.tld", "recipie...@domain.tld"]
>},
>"content": "mail content here"
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2858) Fix plugin cannot found issue maven-mailetdocs-plugin
[
https://issues.apache.org/jira/browse/JAMES-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2858.
-
Resolution: Fixed
> Fix plugin cannot found issue maven-mailetdocs-plugin
> -
>
> Key: JAMES-2858
> URL: https://issues.apache.org/jira/browse/JAMES-2858
> Project: James Server
> Issue Type: Bug
>Reporter: Rene Cordier
>Priority: Minor
> Fix For: 3.4.0
>
>
> I keep getting sync errors with IntelliJ that it couldn't find the plugin
> {{maven-mailetdocs-plugin}} from the parent pom 1.2 (quite the old version of
> james...)... Then I saw that we have a module {{mailetdocs-maven-plugin}} in
> James that seems to be it, so I think so deps have not been updated correctly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2856) Add quotaRoot in mailboxDetails over webAdmin
[
https://issues.apache.org/jira/browse/JAMES-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915421#comment-16915421
]
Tellier Benoit commented on JAMES-2856:
---
While working on this issue we highlighted a serialization issue leading to
bugs in distributed-james (quota search domain criterion not working)
> 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: Tellier Benoit
>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.2#803003)
-
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-2856) Add quotaRoot in mailboxDetails over webAdmin
[
https://issues.apache.org/jira/browse/JAMES-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915421#comment-16915421
]
Tellier Benoit edited comment on JAMES-2856 at 8/26/19 2:11 AM:
While working on this issue we highlighted a serialization issue leading to
bugs in distributed-james (quota search domain criterion not working)
See https://github.com/linagora/james-project/pull/2601 (merged)
was (Author: btellier):
While working on this issue we highlighted a serialization issue leading to
bugs in distributed-james (quota search domain criterion not working)
> 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: Tellier Benoit
>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.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2850) Exception calling RemoteDelivery: Multiple entries with same key
[
https://issues.apache.org/jira/browse/JAMES-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2850.
-
Resolution: Fixed
https://github.com/linagora/james-project/pull/2563
> Exception calling RemoteDelivery: Multiple entries with same key
>
>
> Key: JAMES-2850
> URL: https://issues.apache.org/jira/browse/JAMES-2850
> Project: James Server
> Issue Type: Bug
> Components: Queue, rabbitmq
>Affects Versions: 3.4.0
>Reporter: Tellier Benoit
>Priority: Major
> Labels: bug
>
> Encountered on sandbox when receiving an external email
> CassandraMailQueueMailStore.storeMail needs to allow multiple entries per
> user in PerHeader Recipients
> {code:java}
> We were unable to deliver the attached message because of an error in the
> mail server.
> Error message below:
> Exception calling RemoteDelivery: Multiple entries with same key:
> nparquet.linag...@gmail.com={headername:'org.apache.james.spamassassin.status',headervalue:'No,
> hits=2.4 required=5.0'} and
> nparquet.linag...@gmail.com={headername:'org.apache.james.spamassassin.flag',headervalue:'NO'}
> java.lang.IllegalArgumentException: Multiple entries with same key:
> nparquet.linag...@gmail.com={headername:'org.apache.james.spamassassin.status',headervalue:'No,
> hits=2.4 required=5.0'} and
> nparquet.linag...@gmail.com={headername:'org.apache.james.spamassassin.flag',headervalue:'NO'}
> at
> com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:215)
> at
> com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:209)
> at
> org.apache.james.queue.rabbitmq.view.cassandra.CassandraMailQueueMailStore.storeMail(CassandraMailQueueMailStore.java:57)
> at
> org.apache.james.queue.rabbitmq.view.cassandra.CassandraMailQueueView.storeMail(CassandraMailQueueView.java:86)
> at
> reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:118)
> at
> reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
> at
> reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
> at
> reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1515)
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder.lambda$configure$0(CamelMailetProcessor.java:155)
> at
> org.apache.camel.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:63)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:715)
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:638)
> at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:248)
> org.apache.james.mailetcontainer.lib.AbstractStateCompositeProcessor.service(AbstractStateCompositeProcessor.java:84)
> at
> org.apache.james.mailetcontainer.impl.JamesMailSpooler.performProcessMail(JamesMailSpooler.java:153)
> at
> org.apache.james.mailetcontainer.impl.JamesMailSpooler.lambda$processMail$2(JamesMailSpooler.java:140)
> at reactor.core.publisher.MonoCallable.call(MonoCallable.java:91)
> at
> reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:135)
> at
> reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.ignoreDone(MonoIgnoreThen.java:190)
> at
> reactor.core.publisher.MonoIgnoreThen$ThenIgnoreInner.onComplete(MonoIgnoreThen.java:240)
> at
> reactor.core.publisher.FluxSubscribeOnCallable$CallableSubscribeOnSubscription.run(FluxSubscribeOnCallable.java:235)
> ... 9 more
> Message details:
> Subject: coucou
> Sent date: Fri Jul 12 14:26:36 UTC 2019
> MAIL FROM: abbey.cu...@sandbox.integration-open-paas.org
> RCPT TO: nparquet.linag...@gmail.com
> From:
> Abbey CURRY
> To:
> "nparquet.linag...@gmail.com"
> Size: 520 B
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2871) ConfigurationProvider cannot load env variable as list of Strings
[
https://issues.apache.org/jira/browse/JAMES-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit resolved JAMES-2871.
---
Fix Version/s: 3.4.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/2622 fixed this by overriding
lib behaviour
> ConfigurationProvider cannot load env variable as list of Strings
> -
>
> Key: JAMES-2871
> URL: https://issues.apache.org/jira/browse/JAMES-2871
> Project: James Server
> Issue Type: Wish
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> for example there is one item in the properties file:
> {code:java}
> cassandra.nodes=${env:CASSANDRA_NODES}{code}
> The configuration.getArrayString("cassandra.nodes") is supposed to return a
> list but acutally return a string incase passing list value into
> CASSANDRA_NODES env
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2871) ConfigurationProvider cannot load env variable as list of Strings
[
https://issues.apache.org/jira/browse/JAMES-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2871.
-
> ConfigurationProvider cannot load env variable as list of Strings
> -
>
> Key: JAMES-2871
> URL: https://issues.apache.org/jira/browse/JAMES-2871
> Project: James Server
> Issue Type: Wish
>Reporter: Trần Tiến Đức
>Priority: Major
> Fix For: 3.4.0
>
>
> for example there is one item in the properties file:
> {code:java}
> cassandra.nodes=${env:CASSANDRA_NODES}{code}
> The configuration.getArrayString("cassandra.nodes") is supposed to return a
> list but acutally return a string incase passing list value into
> CASSANDRA_NODES env
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2872) Broken links for JAMES 3.3.0 release source code
[ https://issues.apache.org/jira/browse/JAMES-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2872. - Fix Version/s: 3.4.0 Resolution: Fixed > Broken links for JAMES 3.3.0 release source code > > > Key: JAMES-2872 > URL: https://issues.apache.org/jira/browse/JAMES-2872 > Project: James Server > Issue Type: Bug > Components: Documentation >Reporter: Rene Cordier >Priority: Major > Fix For: 3.4.0 > > > The links to download the source code of the 3.3.0 release are broken : > [https://james.apache.org/download.cgi#Apache_James_Server] > Looks like a file naming issue, with the zip in the link having the name > james-server-sources-3.3.0.zip , while on the archive and mirrors > ([https://archive.apache.org/dist/james/server/3.3.0/)] we can see the file > name being james-project-3.3.0-src.zip > -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
