[jira] [Commented] (JDKIM-45) Mime4j-core dependency is outdated
[ https://issues.apache.org/jira/browse/JDKIM-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138291#comment-17138291 ] Benoit Tellier commented on JDKIM-45: - The JDKIM mailet have been moved over into James in order to ease mantainence. org.apache.james.jdkim.mailets.DKIMSign & org.apache.james.jdkim.mailets.DKIMVerify should be on James 3.4.0 classpath. > Mime4j-core dependency is outdated > -- > > Key: JDKIM-45 > URL: https://issues.apache.org/jira/browse/JDKIM-45 > Project: James jDKIM > Issue Type: Bug > Components: library >Affects Versions: 0.2 >Reporter: Darren Bishop >Priority: Major > > Dependency incompatibility issues when using JDKIM 0.2 with James 3.4.0. Both > have dependencies on the mime4j-core lib. JDKIM is using an older version of > the lib and one class in particular, MimeConfig, has been reimplemented in > the newer version that James uses. MimeConfig in the newer version of core > (James uses 0.8.2, JDKIM uses 0.7) has constants to define MimeConfig, ie: > PERMISSIVE - this doesn't exist in the older version. In addition, the older > version call's MimeConfig's default constructor which has been removed in the > newer version. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3225) Provide automated builds for Apache James - (restore builds.apache.org ?)
[ https://issues.apache.org/jira/browse/JAMES-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138991#comment-17138991 ] Benoit Tellier commented on JAMES-3225: --- > With my Apache hat on: +1 The current situation is not acceptable. > ASF does accept donations. After having read the page you linked it looks we could be working on the following solution: Linagora donates (most of) our current CI infrastructure so that we could build everything on Apache GitHub repository the way we currently do on Linagora one. Of course we would have to : - Ensure we could run current build & test suite. (Can we launch docker containers on Apache Jenkins CI?) - Of course discuss this internally. There might be some legal aspects... We won't get the 20 minute build but we could be working on progressive improvements for it. And we would be more open. I agree to defend this option. > Provide automated builds for Apache James - (restore builds.apache.org ?) > -- > > Key: JAMES-3225 > URL: https://issues.apache.org/jira/browse/JAMES-3225 > Project: James Server > Issue Type: Task >Reporter: Ioan Eugen Stan >Assignee: Ioan Eugen Stan >Priority: Major > > For a long time we had builds that ran on the Apache Infrastructure > https://builds.apache.org/view/All/job/james-mailet/ . > The build infrastructure is not running for ~ 3 years now. > I believe it is important for us to have automated builds. > This ticket should gather the work needed to make this a reality. > There are lots of things to take into consideration. > My ( [~ieugen] ) opinions on how to handle this. > * builds should run automatically > * builds should run fast < 10 min > * there are several things they should do (not exhaustive) > ** verify the source code > ** compile the source code > ** run the unit tests > ** run the integration tests > ** publish SNAPSHOTS (only from master or develop ?!) > ** run code analytics > ** publish reports relating to build > ** provide build status for other services > For smaller projects this is a no-brainer. > For the current state of Apache James this is a challange, especially in the > context of > - multiple git branches and PR's > - the distributed integration tests which take a long time > Given the limited resources available for us on the Apache infrastructure we > will have to be selective of what we do. > Personally I don't see how we can run the current (40mni +) integration suite > on each push / build. I'm pretty sure we will get banned :) or throttled. > So a discussion should be in order on how to solve these issues but some > options regarding what we can do: > - make integration tests OPT-IN > - run (distributed) integration tests once a day or once every 6h / 12h > - have build profiles that build a common subset all the time and run > The nuclear option: prune some of the components we have in James and we > don't want to support or move them out of the common project. > This is something we should consider especially for buggy components or for > components that don't have a maintainer. > We have limited time and resources. > We can't maintain everything for everybody. > We should be mindful of this. > We can take inspiration from the OFBiz project > https://builds.apache.org/view/All/job/Apache%20OFBiz/ . -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2586) Implement a Postgres-specific backend
[ https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139011#comment-17139011 ] Benoit Tellier commented on JAMES-2586: --- > It's easy for someone who joins the community to identity the current issues > and work on them. At some point we introduced a @newbie label for this purpose. BTW I agree that a project with loads of open, outdated tickets looks unfriendly. > Implement a Postgres-specific backend > - > > Key: JAMES-2586 > URL: https://issues.apache.org/jira/browse/JAMES-2586 > Project: James Server > Issue Type: New Feature >Reporter: Matthieu Baechler >Priority: Major > > James has a JPA implementation of most interfaces that allows to deploy it on > top of some popular RDBMS. > However, while useful for some kind of applications, ORM are usually a bad > fit for applications requiring high performance like a mail server. > As an abstraction, it also prevents from using advanced features of a given > RDBMS. > For most usages, James would probably run great on top of Postgres, given > that we use advanced features to implement search, for example. > A good strategy would be to implement all interfaces implemented by JPA with > a modern Postgres driver. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2605) Cassandra MailQueue implementation has a 20% fail rate on load
[ https://issues.apache.org/jira/browse/JAMES-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139014#comment-17139014 ] Benoit Tellier commented on JAMES-2605: --- I think we can. Let's give some time to Matthieu to confirm. > Cassandra MailQueue implementation has a 20% fail rate on load > -- > > Key: JAMES-2605 > URL: https://issues.apache.org/jira/browse/JAMES-2605 > Project: James Server > Issue Type: Bug > Components: cassandra >Reporter: Matthieu Baechler >Priority: Major > > RabbitMQ + Cassandra implementation of Mailqueue proved to be brittle, we > have around 20% error rate for SMTP mail delivery under heavy load. > It's probably linked to the heavy use of parallelism into Cassandra Mailqueue > code that can submit an unbounded numer of request for a single Mailqueue > operation. > > We should try to remove this unbounded parallelism and check the failure rate > under load. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2535) Add declaration order checks to checkstyle
[ https://issues.apache.org/jira/browse/JAMES-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139016#comment-17139016 ] Benoit Tellier commented on JAMES-2535: --- This is not addressed. I wonder if any one is willing to dedicate time to this. > Add declaration order checks to checkstyle > -- > > Key: JAMES-2535 > URL: https://issues.apache.org/jira/browse/JAMES-2535 > Project: James Server > Issue Type: Task >Reporter: Jean Helou >Priority: Minor > > Currently checkstyle doesn't check the declaration order of various class > components. This was made quite clear by > [https://github.com/linagora/james-project/pull/1681#discussion_r212547046] > The default checkstyle rules do not include a rule which would make such a > check possible but the incubator project for checkstyle > ([http://sevntu-checkstyle.github.io/sevntu.checkstyle/)] > I tried to add it but finding the correct order is not trivial and is quickly > escaping the scope of my current goal hence the issue. > Note that configuring this checkstyle for > [intellij|https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/How-to-use-SevNTU-Checkstyle-in-Intellij-IDEA] > and > [netbeans|https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/How-to-use-SevNTU-Checkstyle-in-NetBeans] > requires some additional efforts. Eclipse can be made to use a specfic > checkstyle plugin > Note that configuring this checkstyle for > [sonar|[https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/How-to-integrate-sevntu-checks-into-SonarQubeTM-(user's-guide)]] > requires some additional efforts > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2586) Implement a Postgres-specific backend
[ https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139010#comment-17139010 ] Benoit Tellier commented on JAMES-2586: --- > We also have github and this creates duplication and we should discuss this > in another thread. In my opinion github should be limited to reviewing code. So I see little overlap. > I think ideas should be discussed on the mailing list. +1 I just want to add nuance. Browsing mailing list to retrieve things could be harder than JIRA tickets where you can link things together, rely on components, label things, etc... Maybe the right thing to do is leverage our tooling to allow both of your goals to be achievable. Maybe we could introduce a 'label' for long term propositions that could easily be filtered in & out ? > Implement a Postgres-specific backend > - > > Key: JAMES-2586 > URL: https://issues.apache.org/jira/browse/JAMES-2586 > Project: James Server > Issue Type: New Feature >Reporter: Matthieu Baechler >Priority: Major > > James has a JPA implementation of most interfaces that allows to deploy it on > top of some popular RDBMS. > However, while useful for some kind of applications, ORM are usually a bad > fit for applications requiring high performance like a mail server. > As an abstraction, it also prevents from using advanced features of a given > RDBMS. > For most usages, James would probably run great on top of Postgres, given > that we use advanced features to implement search, for example. > A good strategy would be to implement all interfaces implemented by JPA with > a modern Postgres driver. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139018#comment-17139018 ] Benoit Tellier commented on JAMES-3226: --- > We should have documentation for every release we make. > This is important since people don't upgrade immediately after release and > might use an older release for some time. That is in my opinion the biggest limitation of the current website, yes. > or publish them for download next to it. +1 > This way we can keep only the latest 1-3 versions online. IMO should be more than one. > Provide a process around documentation publishing and deployment > > > Key: JAMES-3226 > URL: https://issues.apache.org/jira/browse/JAMES-3226 > Project: James Server > Issue Type: Sub-task >Reporter: Ioan Eugen Stan >Assignee: Ioan Eugen Stan >Priority: Major > > We have started working on the documentation and it's great. > We should also document the processes around documentation: > - when we publish the docs > - how to publish the docs > - where to publish the docs > - when we retire old docs ?! > This task should aggregate discussion and decisions. > The process should be written as asciidoc. > We decided to use antora as a documentation system so the features are going > to depend on that technology. > We should have documentation for every release we make. > This is important since people don't upgrade immediately after release and > might use an older release for some time. > I'm not sure if the documentation for all versions should be online. > We can build zip archives of each documentation release and include it in the > binary release or publish them for download next to it. > This way we can keep only the latest 1-3 versions online. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2932) Upgrade runtime to Java 11
[ https://issues.apache.org/jira/browse/JAMES-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139020#comment-17139020 ] Benoit Tellier commented on JAMES-2932: --- 3.5.0 release ticket is https://issues.apache.org/jira/browse/JAMES-3207 > Upgrade runtime to Java 11 > -- > > Key: JAMES-2932 > URL: https://issues.apache.org/jira/browse/JAMES-2932 > Project: James Server > Issue Type: Task >Affects Versions: 3.4.0 >Reporter: Matthieu Baechler >Priority: Major > Fix For: 3.5.0 > > > Java 11 is the only "Long Term Support" java release right now so more and > more people will use it exclusively. > Now that James builds to java 11 for some time, we should target java 11 as > the runtime. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2932) Upgrade runtime to Java 11
[ https://issues.apache.org/jira/browse/JAMES-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2932. - Fix Version/s: (was: 3.5.0) 3.6.0 Resolution: Fixed I am closing this issue as it is addressed on master after 3.5.x tags > Upgrade runtime to Java 11 > -- > > Key: JAMES-2932 > URL: https://issues.apache.org/jira/browse/JAMES-2932 > Project: James Server > Issue Type: Task >Affects Versions: 3.4.0 >Reporter: Matthieu Baechler >Priority: Major > Fix For: 3.6.0 > > > Java 11 is the only "Long Term Support" java release right now so more and > more people will use it exclusively. > Now that James builds to java 11 for some time, we should target java 11 as > the runtime. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2410) Column name 'KEY' in JPAMailboxAnnotation not allowed by SQL Server
[
https://issues.apache.org/jira/browse/JAMES-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139022#comment-17139022
]
Benoit Tellier commented on JAMES-2410:
---
The fix (changing the column name) is relatively easy.
However the data migration part is more tricky.
> Column name 'KEY' in JPAMailboxAnnotation not allowed by SQL Server
> ---
>
> Key: JAMES-2410
> URL: https://issues.apache.org/jira/browse/JAMES-2410
> Project: James Server
> Issue Type: Bug
> Components: mailbox
>Affects Versions: 3.0-beta4
> Environment: Windows Server 2016, MS SQL Server 2016, Java
> 1.8.0_171-b11, JDBC driver 4.2.6420.100
>Reporter: Matt Pryor
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: james-server.log
>
>
> James 3-0-beta4 fails to start using MS SQL Server 2016 for persistence due
> to the following create table statement:
> {{CREATE TABLE JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL,
> MAILBOX_ID BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY,
> MAILBOX_ID))}}
> "KEY" is a reserved keyword in SQL Server.
> Logs attached.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3132) Unable to obtain a connection to the POP3 server
[ https://issues.apache.org/jira/browse/JAMES-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139024#comment-17139024 ] Benoit Tellier commented on JAMES-3132: --- `Caused by: java.net.UnknownHostException: pop.server.com` Does your host succeed to resolve this address (via nslookup?) > Unable to obtain a connection to the POP3 server > - > > Key: JAMES-3132 > URL: https://issues.apache.org/jira/browse/JAMES-3132 > Project: James Server > Issue Type: Bug >Affects Versions: 3.4.0 >Reporter: LARBI YOUCEF Rafik >Priority: Blocker > Attachments: fetchmail.log, pop3server.log, smtpserver.log > > > Hi, > I'm trying to use Apache JAMES for my end of studies' project > In summary > I install the zip file i extract it, I install james & create a domain & 2 > users, > I use telnet 192.168.1.4 25 to send a mail with SMTP protocol, in the log > file I have this message " look in file SMTPSERVER.LOG" > after when I use telnet 192.168.1.4 110 to check mail of recipîent I see > that there is no message received but in "POP3SERVER.LOG" I don't have any > ERROR > after I enable FETCHMAIL.XML (because by default it's desable), hoping I can > receive a mail > and I have an other ERROR > can you help me please > thanks -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2911) Unable to send mail from James using an SMTP gateway
[ https://issues.apache.org/jira/browse/JAMES-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2911. - Fix Version/s: 3.5.0 Resolution: Fixed > Unable to send mail from James using an SMTP gateway > - > > Key: JAMES-2911 > URL: https://issues.apache.org/jira/browse/JAMES-2911 > Project: James Server > Issue Type: Bug > Components: SMTPServer >Affects Versions: 3.4.0 >Reporter: David Arendt >Priority: Blocker > Fix For: 3.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In James 3.3.0 mail sending from James using an SMTP gateway is working > flawlessly. On 3.4.0 it produces the following exceptions: > INFO | jvm 1 | 2019/10/04 13:35:49 | ERROR 13:35:49,067 | > org.apache.james.transport.mailets.remote.delivery.MailDelivrer | Generic > exception = permanent failure: org.apache.geronimo.ja > vamail.transport.smtp.SMTPTransport cannot be cast to > com.sun.mail.smtp.SMTPTransport > INFO | jvm 1 | 2019/10/04 13:35:49 | java.lang.ClassCastException: > org.apache.geronimo.javamail.transport.smtp.SMTPTransport cannot be cast to > com.sun.mail.smtp.SMTPTransport > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.MailDelivrerToHost.tryDeliveryToHost(MailDelivrerToHost.java:66) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.doDeliver(MailDelivrer.java:126) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.tryDeliver(MailDelivrer.java:108) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.deliver(MailDelivrer.java:77) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.attemptDelivery(DeliveryRunnable.java:126) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.processMail(DeliveryRunnable.java:109) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.runStep(DeliveryRunnable.java:96) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > reactor.core.publisher.FluxFlatMap$FlatMapMain.onNext(FluxFlatMap.java:350) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runAsync(FluxPublishOn.java:398) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:484) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > java.util.concurrent.FutureTask.run(FutureTask.java:266) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > INFO | jvm 1 | 2019/10/04 13:35:49 | at java.lang.Thread.run(Thread.java:748) > INFO | jvm 1 | 2019/10/04 13:35:49 | ERROR 13:35:49,123 | > org.apache.james.mailetcontainer.impl.camel.CamelProcessor | Exception > calling DSNBounce: null > INFO | jvm 1 | 2019/10/04 13:35:49 | java.lang.NullPointerException > INFO | jvm 1 | 2019/10/04 13:35:49 | at > javax.mail.internet.MimeMessage.setHeader(MimeMessage.java:1547) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > javax.mail.internet.MimeMessage.setRecipients(MimeMessage.java:449) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.server.core.MimeMessageCopyOnWriteProxy.setRecipients(MimeMessageCopyOnWriteProxy.java:390) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.redirect.MailModifier.setTo(MailModifier.java:127) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.DSNBounce.trySendBounce(DSNBounce.java:269) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.transport.mailets.DSNBounce.service(DSNBounce.java:240) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:81) > INFO | jvm 1 | 2019/10/04 13:35:49 | at > org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$Maile
[jira] [Commented] (JAMES-2722) org.apache.james.transport.mailets.delivery.MailDispatcher | Error while storing mail
[ https://issues.apache.org/jira/browse/JAMES-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139025#comment-17139025 ] Benoit Tellier commented on JAMES-2722: --- I don't understand why there is no user part in the MailboxPath, the right exception is likely coming from it. Can you share the envelope of the mail? > org.apache.james.transport.mailets.delivery.MailDispatcher | Error while > storing mail > - > > Key: JAMES-2722 > URL: https://issues.apache.org/jira/browse/JAMES-2722 > Project: James Server > Issue Type: Bug > Components: James Core >Affects Versions: 3.2.0, 3.3.0 >Reporter: vincent >Priority: Blocker > Attachments: image-2019-04-02-12-14-51-155.png, > image-2019-04-02-12-15-02-391.png > > > !image-2019-04-02-12-14-51-155.png! > !image-2019-04-02-12-15-02-391.png! > > I can send mail to each other in the internal environment, but when other > mailboxes send mail to my James server, it shows that the acceptance is > successful, but subsequent save will report an error. I changed the default > file storage mode to mysql, and the other configurations were basically > unchanged. > run in centos7 > I can run with james 2.3.2.1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1418) SMTP authentication verifyIdentity is passed off
[ https://issues.apache.org/jira/browse/JAMES-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-1418. - Resolution: Abandoned I'm closing this as it affects a beta version. Please reopen if relevant. > SMTP authentication verifyIdentity is passed off > > > Key: JAMES-1418 > URL: https://issues.apache.org/jira/browse/JAMES-1418 > Project: James Server > Issue Type: Bug > Components: SMTPServer >Affects Versions: 3.0-beta3, 3.0-beta4 >Reporter: Serkant Uluderya >Priority: Critical > Labels: smtp > Attachments: MailSender.java, james.out, smtpserver.conf > > Original Estimate: 24h > Remaining Estimate: 24h > > I've been trying to enable SMTP authentication on apache-james-3.0-beta4 but > I can't manage it. I made the log level as DEBUG for SMTP service. It seems > that although the identity verification fails, the user is enable to post a > mail. > In smtpserver.conf file I made the following changes, it is attached also. > announce > > true > Here is the log parts that I suspected. > INFO 17:53:08,746 | james.smtpserver | This SMTP server requires > authentication. > .. > DEBUG 18:03:33,798 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.SenderAuthIdentifyVerificationRcptHook: result=8 > (DECLINED) > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.PostmasterAbuseRcptHook > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.log.HookResultLogger@10a3ffc > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' > org.apache.james.protocols.smtp.core.PostmasterAbuseRcptHook: result=8 > (DECLINED) > DEBUG 18:03:33,799 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,800 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.JamesRcptCmdHandler: [250 2.1.5 Recipient > OK] > DEBUG 18:03:33,815 | james.smtpserver | Id='9403936' User='' > org.apache.james.protocols.api.handler.CommandDispatcher received: DATA > DEBUG 18:03:33,815 | james.smtpserver | Id='9403936' User='' Lookup command > handler for command: DATA > DEBUG 18:03:33,826 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.JamesDataCmdHandler: [354 Ok Send data ending > with .] > DEBUG 18:03:33,870 | james.smtpserver | Id='9403936' User='' executing james > message handler > org.apache.james.protocols.smtp.core.esmtp.MailSizeEsmtpExtension@4a1908 > DEBUG 18:03:33,872 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.log.HookResultLogger@10a3ffc > DEBUG 18:03:33,872 | james.smtpserver | Id='9403936' User='' > org.apache.james.protocols.smtp.core.esmtp.MailSizeEsmtpExtension: result=8 > (DECLINED) > DEBUG 18:03:33,874 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,874 | james.smtpserver | Id='9403936' User='' executing james > message handler > org.apache.james.smtpserver.AddDefaultAttributesMessageHook@1cfb84c > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.protocols.smtp.core.log.HookResultLogger@10a3ffc > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' > org.apache.james.smtpserver.AddDefaultAttributesMessageHook: result=8 > (DECLINED) > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' executing hook > org.apache.james.smtpserver.jmx.HookResultJMXMonitor@1eee3fb > DEBUG 18:03:33,875 | james.smtpserver | Id='9403936' User='' executing james > message handler org.apache.james.smtpserver.SendMailHandler@4cb3a4 > DEBUG 18:03:33,876 | james.smtpserver | Id='9403936' User='' sending mail > INFO 18:03:33,906 | james.smtpserver | Id='9403936' User='' Successfully > spooled mail Mail1339427013851-53bd7bc6-0c36-417f-acee-8af76691b35e from > sen...@mail.test.com on 192.168.200.90/192.168.200.90 for > [recei...@mail.test.com] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1694) POP3 CAPA command returns different capabilities in different states.
[
https://issues.apache.org/jira/browse/JAMES-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139035#comment-17139035
]
Benoit Tellier commented on JAMES-1694:
---
https://tools.ietf.org/html/rfc1939#section-9
States that:
{code:java}
Minimal POP3 Commands:
USER name valid in the AUTHORIZATION state
PASS string
QUIT
STATvalid in the TRANSACTION state
LIST [msg]
RETR msg
DELE msg
NOOP
RSET
QUIT
Optional POP3 Commands:
APOP name digestvalid in the AUTHORIZATION state
TOP msg n valid in the TRANSACTION state
UIDL [msg]
POP3 Replies:
+OK
-ERR
{code}
CAPA command is defined in https://tools.ietf.org/html/rfc2449 POP3 Extension
Mechanism
{code:java}
A capability description MUST document in which states the capability
is announced, and in which states the commands are valid.
{code}
Reading TOP description for instance:
https://tools.ietf.org/html/rfc2449#section-6.1
{code:java}
Announced states / possible differences:
both / no
Commands valid in states:
TRANSACTION
{code}
So your report is likely valid (I'm sadly not POP3 fluent...)
Reading TopCmdHandler code:
{code:java}
@Override
public Set getImplementedCapabilities(POP3Session session) {
if (session.getHandlerState() == POP3Session.TRANSACTION) {
return CAPS;
} else {
return Collections.emptySet();
}
}
{code}
likely needs to be modified.
> POP3 CAPA command returns different capabilities in different states.
> -
>
> Key: JAMES-1694
> URL: https://issues.apache.org/jira/browse/JAMES-1694
> Project: James Server
> Issue Type: Bug
> Components: POP3Server
>Affects Versions: 3.0.0-beta5
> Environment: Linux
>Reporter: Sandeep Savarala
>Priority: Critical
>
> After you connect to the POP3 server and issue CAPA command it returns:
> capa
> +OK Capability list follows
> PIPELINING
> USER
> STLS
> .
> After you authenticate it returns additional UIDL capability.
> capa
> +OK Capability list follows
> PIPELINING
> USER
> UIDL
> TOP
> .
> The CAPA command should return the same output in any state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3194) Rely on DTOConverter in TaskRoute
[ https://issues.apache.org/jira/browse/JAMES-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3194. - Resolution: Fixed > Rely on DTOConverter in TaskRoute > - > > Key: JAMES-3194 > URL: https://issues.apache.org/jira/browse/JAMES-3194 > Project: James Server > Issue Type: Improvement > Components: task, webadmin >Affects Versions: master >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > > The taskManager defines task serialization, used to persist a task and > additional information, in order to be accessible in a distributed context. > However, we rely on implicit Jackson serialization for returning task details > over webadmin. > This results in confusing expectation as a developer. We furthermore "leak" > jackson annotation in the details models. > We should rely on the DTOs for details serialization over webadmin. > https://github.com/linagora/james-project/pull/3382 is a trial to reach this > prurpose. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3168) Integration tests with echo method
[ https://issues.apache.org/jira/browse/JAMES-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3168. - Resolution: Fixed Contributed > Integration tests with echo method > -- > > Key: JAMES-3168 > URL: https://issues.apache.org/jira/browse/JAMES-3168 > Project: James Server > Issue Type: New Feature >Reporter: Nguyễn Việt Đức >Priority: Major > > Integration test for echo method with memory + distributed james backend > Guice bindings for Jmap Routes of new version > smoke testing > Scala and junit 5 and assertj and restassured -- 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-3155) Reactify mailbox listeners
[ https://issues.apache.org/jira/browse/JAMES-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3155. - Resolution: Fixed Relevant issue merged > Reactify mailbox listeners > -- > > Key: JAMES-3155 > URL: https://issues.apache.org/jira/browse/JAMES-3155 > Project: James Server > Issue Type: Improvement >Affects Versions: 3.6.0 >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > > Mailbox listener execution is synchronous. > Wiring them with the eventBus using reactor will enable us to achieve a > better thread usage by avoiding needless "block()" calls. -- 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-3149) Extend reactive coverage in JMAP draft
[ https://issues.apache.org/jira/browse/JAMES-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3149. - Resolution: Fixed This effort is done. > Extend reactive coverage in JMAP draft > -- > > Key: JAMES-3149 > URL: https://issues.apache.org/jira/browse/JAMES-3149 > Project: James Server > Issue Type: Improvement > Components: JMAP >Affects Versions: 3.5.0 >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > Labels: perf > Fix For: 3.6.0 > > > JMAP relies on reactor-netty for it's HTTP layer. The Cassandra layers, > ElasticSearch layers relies on reactor too. > Some calls to `block` in the middle prevent us from having an optimal thread > usage. > We should enforce where we can the reactive chain to be unaltered in order to > optimize resource usage. > This had been contributed for GetVacationResponse, SetVacationResponse, > GetFilter, SetFilters. > We can easily contribute this for GetMailboxes and GetMessageList. -- 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-3148) Cassandra mailbox deletion cleanup
[ https://issues.apache.org/jira/browse/JAMES-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3148. - Resolution: Fixed Merged > Cassandra mailbox deletion cleanup > -- > > Key: JAMES-3148 > URL: https://issues.apache.org/jira/browse/JAMES-3148 > Project: James Server > Issue Type: New Feature > Components: cassandra, mailbox >Affects Versions: 3.5.0 >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > > Cassandra is used within distributed James product to hold messages and > mailboxes metadata. > Cassandra holds the following tables: > - mailboxPathV2 + mailbox allowing to retrieve mailboxes informations > - acl + UserMailboxACL holds denormalized information > - messageIdTable & imapUidTable allows to retrieve mailbox context > information > - messageV2 table holds message matadata > - attachmentV2 holds attachment for messages > - References to these attachments are contained within the attachmentOwner > and attachmentMessageId tables > > Currently, the deletion only deletes the first level of metadata. Lower level > metadata stay unreachable. The data looks > deleted but references are actually still present. > Concretely: > - Upon mailbox deletion, only mailboxPathV2 & mailbox content is deleted. > messageIdTable, imapUidTable, messageV2, > attachmentV2 & attachmentMessageId metadata is left undeleted. > - Upon mailbox deletion, acl + UserMailboxACL is not deleted. > - Upon message deletion, only messageIdTable & imapUidTable content is > deleted. messageV2, attachmentV2 & > attachmentMessageId metadata is left undeleted. > This jeopardize efforts to regain disk space and privacy, for example through > blobStore garbage collection. > We need to cleanup Cassandra metadata. They can be retrieved from dandling > metadata after the delete operation had been > conducted out. We need to delete the lower levels first so that upon failures > undeleted metadata can still be reached. > This cleanup is not needed for strict correctness from a MailboxManager point > of view thus it could be carried out > asynchronously, via mailbox listeners so that it can be retried. > Mailbox listener failures leads to eventBus retrying their execution, we need > to ensure the result of the deletion to be > idempotent. This might have consequences on the blobStore garbage collection > design. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3060) Evaluate impact of Cassandra ACL
[ https://issues.apache.org/jira/browse/JAMES-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3060. - Resolution: Fixed Impact prooved to be limited. We saw no performance difference. > Evaluate impact of Cassandra ACL > > > Key: JAMES-3060 > URL: https://issues.apache.org/jira/browse/JAMES-3060 > Project: James Server > Issue Type: Improvement >Reporter: René Cordier >Priority: Major > > Run James performance test with, and without cassandra authentification with > restrictive rights (keyspace level acls) to evaluate the runtime impact. > *DOD*: gatling performance result -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3056) Unit tests for mailbox inconsitencies
[ https://issues.apache.org/jira/browse/JAMES-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3056. - Resolution: Fixed Contributed > Unit tests for mailbox inconsitencies > - > > Key: JAMES-3056 > URL: https://issues.apache.org/jira/browse/JAMES-3056 > Project: James Server > Issue Type: Improvement > Components: mailbox >Reporter: René Cordier >Priority: Major > > *Circumstances* > - mailboxPath exists but not the mailbox > - mailbox exists but not the mailboxPath > - if mailbox has id1/path1 and id2/path1 but mailboxPath only have id1/path1 > (GhostMailbox) > - mailbox renames > https://ci.linagora.com/linagora/lgs/openpaas/james/issues/1586#note_246053 > *How* > _mailboxPath exists but not the mailbox_ > - create a mailbox by `CassandraMailboxMapper.trySave()` > - trigger failure on the second step (mailboxDAO.save()) - (mockito) > _mailbox exists but not the mailboxPath_ > - delete a mailbox `CassandraMailboxMapper.delete()` > - trigger failure on the second step (mailboxDAO.delete()) - (mockito) > _if mailbox has id1/path1 and id2/path1 but mailboxPath only have id1/path1 > (GhostMailbox)_ > - Create a mailbox with id1/path1 with pathV1 (pathV1 only, assuming old > data at the moment V2 is not yet implemented) > - migrate pathV1 -> pathV2 (insert pathV2, then delete pathV1). Trigger a > failure on delete pathV1, then we have both pathV1 and pathV2 exist. > (id1/path1) > - delete mailbox id1/path1 (delete pathV1, pathV2 -> delete mailbox). > Trigger a failure on delete pathV1 but pathV2 still success. => pathV2 > deleted but pathV1, mailbox (id1/path1) still remain. > - create a new mailbox with exact name (id2/path1) -> at this stage we have > id1/path1 and id2/path1 on mailbox, id1/path1 on pathV1 and id2/path1 on > pathV2. > *DOD* > tests show that there're inconsistencies after creating or deleting a > mailbox. They should be located in CassandraMailboxManagerTest -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3037) Spring XSD not found debug log
[
https://issues.apache.org/jira/browse/JAMES-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3037.
-
Resolution: Fixed
https://github.com/linagora/james-project/pull/3082 had been abandoned
> Spring XSD not found debug log
> --
>
> Key: JAMES-3037
> URL: https://issues.apache.org/jira/browse/JAMES-3037
> Project: James Server
> Issue Type: Improvement
> Components: Spring Container
>Affects Versions: 3.4.0
>Reporter: Benoit Tellier
>Priority: Major
> Fix For: 3.5.0
>
>
> Jerry Malcolm reported the following log:
> https://www.mail-archive.com/server-dev@james.apache.org/msg64206.html
> {code:java}
> DEBUG 23:12:10,456 |
> org.springframework.beans.factory.xml.ResourceEntityResolver | Could not
> resolve XML entity
> [classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd]
> against syjava.net.MalformedURLException: unknown protocol: classpath at
> java.net.URL.(URL.java:607) at java.net.URL.(URL.java:497) at
> java.net.URL.(URL.java:446) at
> org.springframework.beans.factory.xml.ResourceEntityResolver.resolveEntity(ResourceEntityResolver.java:79)
> at
> com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(EntityResolverWrapper.java:110)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:1081)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.resolveDocument(XMLSchemaLoader.java:654)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(XMLSchemaValidator.java:2431)
>
> {code}
> classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd is only
> used in two places:
> -
> server/container/spring/src/main/resources/META-INF/org/apache/james/spring-mailbox-authenticator.xml
> -
> server/container/spring/src/main/resources/META-INF/org/apache/james/spring-mailbox-authorizator.xml
> We should rather rely on the standard we are using in other places:
> http://www.springframework.org/schema/beans/spring-beans.xsd
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3141) Performance test for CachedBlobStore
[ https://issues.apache.org/jira/browse/JAMES-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3141. - Resolution: Invalid > Performance test for CachedBlobStore > > > Key: JAMES-3141 > URL: https://issues.apache.org/jira/browse/JAMES-3141 > Project: James Server > Issue Type: Improvement >Reporter: René Cordier >Priority: Major > > Gatling test performancer results for CachedBlobStore -- 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-3146) Optimize JMAP default mailbox provisionning speed
[ https://issues.apache.org/jira/browse/JAMES-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139042#comment-17139042 ] Benoit Tellier commented on JAMES-3146: --- This is contributed > Optimize JMAP default mailbox provisionning speed > - > > Key: JAMES-3146 > URL: https://issues.apache.org/jira/browse/JAMES-3146 > Project: James Server > Issue Type: New Feature > Components: JMAP >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > Labels: perf > > JMAP default mailbox provisionning checks wether default mailboxes (inbox, > spam, outbox, sent, draft, trash) exists and create them if needed. > It performs full mailbox load (retrieve mailboxId by it's path, load mailbox > informations, then load it's ACLs) while we could be considering the mailbox > do not exist if it's mailboxId can't be retrieved. > This will, on top of the cassandra backend save 2 Cassandra requests per > mailbox, and thus 12 Cassandra requests per JMAP request, improving speed, > and lowering pressure on the Cassandra database. -- 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-3023) Encryption for Cassandra blobStore
[ https://issues.apache.org/jira/browse/JAMES-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3023. - Resolution: Won't Fix > Encryption for Cassandra blobStore > -- > > Key: JAMES-3023 > URL: https://issues.apache.org/jira/browse/JAMES-3023 > Project: James Server > Issue Type: Sub-task > Components: Blob, cassandra >Reporter: Benoit Tellier >Priority: Major > > Following JAMES-2921 Hybrid BlobStore we end up storing 'blobs' into > Cassandra. > Given a multi-tenant environment, if I run two James servers on top of the > same Cassandra database, I don't want one server to be able to read the > content of the other one. > Such isolation is currently achievable by having separate keyspaces, and > separate users with different right settings. However given a cassandra acls > misconfiguration, such content could still be leaked from one tenant to the > other one in case of James compromision. > Encrypting blobs into cassandra, with an encryption key specific per James > server can be a good second line of defense to mitigate this risk. Only > metatdata would be readable, raw content (headers & body) staying encrypted. > As such, I should be able to configure AES encryption of top of Cassandra > storage (just like on top of ObjectStorage). -- 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-3146) Optimize JMAP default mailbox provisionning speed
[ https://issues.apache.org/jira/browse/JAMES-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3146. - Fix Version/s: 3.6.0 Resolution: Fixed > Optimize JMAP default mailbox provisionning speed > - > > Key: JAMES-3146 > URL: https://issues.apache.org/jira/browse/JAMES-3146 > Project: James Server > Issue Type: New Feature > Components: JMAP >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > Labels: perf > Fix For: 3.6.0 > > > JMAP default mailbox provisionning checks wether default mailboxes (inbox, > spam, outbox, sent, draft, trash) exists and create them if needed. > It performs full mailbox load (retrieve mailboxId by it's path, load mailbox > informations, then load it's ACLs) while we could be considering the mailbox > do not exist if it's mailboxId can't be retrieved. > This will, on top of the cassandra backend save 2 Cassandra requests per > mailbox, and thus 12 Cassandra requests per JMAP request, improving speed, > and lowering pressure on the Cassandra database. -- 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-3127) Cassandra migrations should not depend on Guice
[ https://issues.apache.org/jira/browse/JAMES-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139045#comment-17139045 ] Benoit Tellier commented on JAMES-3127: --- What is the status of this work? > Cassandra migrations should not depend on Guice > --- > > Key: JAMES-3127 > URL: https://issues.apache.org/jira/browse/JAMES-3127 > Project: James Server > Issue Type: Improvement > Components: cassandra, guice >Reporter: Matthieu Baechler >Priority: Major > > For now, Cassandra migrations are associated to schema versions in a guice > module, preventing the reuse of the versions in other parts of the code. > We don't really need guice to build a Map so we should move this code in the > non-guice module and stop duplicating schema version information in the > codebase. -- 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-3124) Recomend upgrading to Tika 1.24
[ https://issues.apache.org/jira/browse/JAMES-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3124. - Resolution: Fixed Done > Recomend upgrading to Tika 1.24 > --- > > Key: JAMES-3124 > URL: https://issues.apache.org/jira/browse/JAMES-3124 > Project: James Server > Issue Type: New Feature >Reporter: Benoit Tellier >Priority: Major > > Prior 1.24, Tika is subject to 2 CVEs: > - [CVE-2020-1951] Infinite Loop (DoS) vulnerability in Apache Tika's > PSDParser > - [CVE-2020-1950] Excessive memory usage (DoS) vulnerability in Apache > Tika's PSDParser > We need to test & recommend the upgrade -- 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-3147) Group localDomain calls for RecipientIsLocal
[ https://issues.apache.org/jira/browse/JAMES-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3147. - Resolution: Fixed > Group localDomain calls for RecipientIsLocal > > > Key: JAMES-3147 > URL: https://issues.apache.org/jira/browse/JAMES-3147 > Project: James Server > Issue Type: New Feature > Components: Mailet Contributions >Affects Versions: 3.5.0 >Reporter: Benoit Tellier >Priority: Major > Labels: perf > Fix For: 3.6.0 > > > When a mail is processed, very often recipients shares the same domain. > To check if a recipient is local we start a lookup to check its domain is > local then lookup its user. And this for each recipient. > Obviously we can group recipient by domains in order to do the check only > once. > Similary calls can also be groups by domains upon RRT processing and in > HostIsLocal. > This is an interesting area of improvment as glowroot profiling session > showed Cassandra GET domain request was by far the most time consumming > request with a cumulated time of 76 seconds and 38 thousands calls. -- 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-3129) Race condition upon flag update for message sent via JMAP
[ https://issues.apache.org/jira/browse/JAMES-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3129. - Resolution: Fixed Contributed > Race condition upon flag update for message sent via JMAP > - > > Key: JAMES-3129 > URL: https://issues.apache.org/jira/browse/JAMES-3129 > Project: James Server > Issue Type: New Feature > Components: JMAP, MailStore & MailRepository, Queue >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > Fix For: 3.5.0 > > > https://github.com/linagora/james-project/pull/3242/commits/62bab3269ceef65c1741fbbf243e5c109307ad8c > highlighted a race condition when sending a mail via JMAP. > Cause: the mail is processedn, and marked for outgoing delivery. > It is reenqueued, and appended to outgoing queue. > The post dequeue decorator, moving JMAP mails from outbox to sent is applied > to times, leading eventualy to invalid results and race condition. > Proposed fix: only apply post dequeue decorator to "spool" -- 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-3027) Encryption for messageFastView previews
[ https://issues.apache.org/jira/browse/JAMES-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3027. - Resolution: Won't Fix > Encryption for messageFastView previews > --- > > Key: JAMES-3027 > URL: https://issues.apache.org/jira/browse/JAMES-3027 > Project: James Server > Issue Type: Sub-task > Components: cassandra, JMAP >Affects Versions: master >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > > Overwise on a shared Cassandra DB in a multi-tenant context, other Cassandra > users might have access to our precious preview. > Proposal: offer AES encryption option... > See connex issue JAMES-3023 -- 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-3133) EventSourcing should be reactive
[ https://issues.apache.org/jira/browse/JAMES-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3133. - Fix Version/s: 3.6.0 Resolution: Fixed Contributed > EventSourcing should be reactive > > > Key: JAMES-3133 > URL: https://issues.apache.org/jira/browse/JAMES-3133 > Project: James Server > Issue Type: New Feature > Components: eventsourcing >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > > In order to allow better thread and resource usage EventSourcing APIs needs > to be reactive. > This will enable to write some reactive MailboxListeners and JMAP methods. -- 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-3008) BlobId list in Cassandra - pre-write check
[
https://issues.apache.org/jira/browse/JAMES-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3008.
-
Resolution: Abandoned
> BlobId list in Cassandra - pre-write check
> --
>
> Key: JAMES-3008
> URL: https://issues.apache.org/jira/browse/JAMES-3008
> Project: James Server
> Issue Type: New Feature
>Reporter: Trần Tiến Đức
>Priority: Major
>
> Started from
> https://github.com/apache/james-project/blob/master/src/adr/0015-objectstorage-blobid-list.md
> Introduced a `BlobIdExistantTester` API within blob-api:
> {code:java}
> interface BlobIdExistantTester {
> Mono add(BlobId blobId);
> Mono testExistance(BlobId blobId);
> }
> {code}
>
> Create a `FakeBlobIdExistantTester` that always returs false.
> Create a `CassandraBlobIdExistantTester` and the related tests.
> Ensure `ObjectStorageBlobDAO`:
> - Don't persist small blobs that already exist
> - Don't attempt to rename (copy) big blobs that already exist - deleting the
> intermediary blob supplied is enough - and faster.
> when cassandra is down, just store it as normal
> Propose a proof of concept regarding these changes.
--
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-3016) Remote delivery modifies message breaking DKIM signature
[
https://issues.apache.org/jira/browse/JAMES-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139056#comment-17139056
]
Benoit Tellier commented on JAMES-3016:
---
[~rcordier] why did you reopened this?
> Remote delivery modifies message breaking DKIM signature
>
>
> Key: JAMES-3016
> URL: https://issues.apache.org/jira/browse/JAMES-3016
> Project: James Server
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Sergey B.
>Priority: Major
> Fix For: 3.5.0
>
>
> Remote delivery modifies message and breaks its DKIM signature. This happens
> when Content-Type is 'text/plain; charset=UTF-8' and body contains non-ascii
> symbols.
> Here is an example. This message was about to be sent.
> {code:java}
> Date: Sun, 22 Dec 2019 12:42:43 + (GMT)
> From: mysen...@example.com
> To: myrecei...@example.org
> Message-ID: <1071314998.134.1577018563940.JavaMail.root@19084506dd1d>
> Subject: MySender email notification test
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> {code}
> This is how it looked like at receiver side.
> {code:java}
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> DKIM-Signature: a=rsa-sha256; b=DKIMSIGNATURE=; s=mail; c=relaxed/relaxed;
> d=example.com; v=1; bh=BHDATA=;
> h=Message-ID:Date:Subject:From:To:MIME-Version:Content-Type;
> Date: Sun, 22 Dec 2019 12:42:43 + (GMT)
> From: mysen...@example.com
> To: myrecei...@example.org
> Message-ID: <1071314998.134.1577018563940.JavaMail.root@19084506dd1d>
> Subject: MySender email notification test{code}
> Mailet configuration is like this
> {code:java}
>
>
> v=1; s=mail; d=example.com;
> h=Message-ID:Date:Subject:From:To:MIME-Version:Content-Type; a=rsa-sha256;
> bh=; b=; c=relaxed/relaxed;
> true
>
>
>
> false
> false
> {code}
> Adding property mail.smtp.allow8bitmime=false to configuration of
> RemoteDelivery mailet solves the problem effectively.
> Disabling 8bit MIME extension, when DKIM signature is present, seems to be
> the right solution.
--
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-3011) ReindexingWithEventDeadLettersTest broken test
[ https://issues.apache.org/jira/browse/JAMES-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3011. - Resolution: Fixed This had been fixed > ReindexingWithEventDeadLettersTest broken test > -- > > Key: JAMES-3011 > URL: https://issues.apache.org/jira/browse/JAMES-3011 > Project: James Server > Issue Type: Bug >Reporter: Trần Tiến Đức >Priority: Major > > Investigate why the > `indexationShouldBeFailingWhenElasticSearchContainerIsPaused` is broken -- 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-2999) Reuse SpamAssassin container image between test runs
[ https://issues.apache.org/jira/browse/JAMES-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2999. - Resolution: Abandoned > Reuse SpamAssassin container image between test runs > > > Key: JAMES-2999 > URL: https://issues.apache.org/jira/browse/JAMES-2999 > Project: James Server > Issue Type: Improvement > Components: tests >Reporter: Matthieu Baechler >Priority: Major > > I found that we built the spamassassin container image everytime we run a > test using this container. > It's testcontainer default behavior when a container image is built > programmatically. However, it not only deletes the image but any cached > layer, preventing reuse and thus speed gains. > By the way, as images share the same layers, not deleting the images has > almost no space usage. > We should disable deleteOnExit option. -- 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-3005) Rebuild MessageFastViewProjection
[ https://issues.apache.org/jira/browse/JAMES-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3005. - Fix Version/s: 3.5.0 Resolution: Fixed Single message handling is not contributed yet. As it is not schedules and likely not needed I close this issue. > Rebuild MessageFastViewProjection > - > > Key: JAMES-3005 > URL: https://issues.apache.org/jira/browse/JAMES-3005 > Project: James Server > Issue Type: New Feature >Reporter: Trần Tiến Đức >Priority: Major > Fix For: 3.5.0 > > > > > *Rebuild MessageFastViewProjection* > **We need a generic task generation mechanism for routes having same path but > different action parameter representing different tasks but pointing the same > resource. Rebuildding MessageFastViewProjection will leverage on this feature > because same endpoint path are same with other routes. To have a way to > determine the decision to run those task, we can rely on a will be > implemented healthcheck reated to MessageFastViewProjection > JAMES-3006: Extension mechanism for WebAdmin task generation > JAMES-3007: Health check for JMAP MessageFastViewProjection consistency > JAMES-3014: Health check for JMAP MessageFastViewProjection consistency > Integration Test > JAMES-2993: [FastView] Rebuild all projections > JAMES-2993: [FastView] Rebuild User's message projections > JAMES-2993: [FastView] Rebuild a message projection > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2979) Message delivery rate with activemq is too slow since 3.4
[
https://issues.apache.org/jira/browse/JAMES-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2979.
-
Resolution: Fixed
3.5.0 JAMES-3207 release will eventually unlock and restore previous
performances.
> Message delivery rate with activemq is too slow since 3.4
> -
>
> Key: JAMES-2979
> URL: https://issues.apache.org/jira/browse/JAMES-2979
> Project: James Server
> Issue Type: Bug
>Reporter: René Cordier
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> From a James user:
> {code:java}
> Hi, I have a problem with the last version, 3.4.0, i've running a server with
> 3.3.0 cassandra+activemq with a messages rate 50/1 min approx, but when i
> upgrade to the 3.4.0, the rate is only 1 or 2 each minute, with the same
> configuration, i'm try to up the number of deliveryThreads, and when i'm
> connect with JMX only 2 threads of RemoteDelivery are running, one running
> and other waiting, but the outgoing queue have more than 200 message pending,
> any solutions?
> {code}
> We need to investigate and fix the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2976) Subproject should not duplicate license
[ https://issues.apache.org/jira/browse/JAMES-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2976. - Resolution: Fixed Solved > Subproject should not duplicate license > --- > > Key: JAMES-2976 > URL: https://issues.apache.org/jira/browse/JAMES-2976 > Project: James Server > Issue Type: New Feature >Reporter: Benoit Tellier >Priority: Major > > We should group notice and licenses file at the project root. Repeating them > in sub projects do not make sens. -- 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-3076) Systematically use 'concat' upon denormalization scheduling
[ https://issues.apache.org/jira/browse/JAMES-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3076. - Resolution: Fixed Done > Systematically use 'concat' upon denormalization scheduling > --- > > Key: JAMES-3076 > URL: https://issues.apache.org/jira/browse/JAMES-3076 > Project: James Server > Issue Type: Bug > Components: cassandra, mailbox >Reporter: Benoit Tellier >Assignee: Benoit Tellier >Priority: Major > > This ensures the projection is updated if, and only if, the source of truth > is updated. > This limits inconsistencies. -- 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-3073) HybridBlobStore: Option to always write to ObjectStorage
[ https://issues.apache.org/jira/browse/JAMES-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3073. - Resolution: Won't Fix We introduced BlobStore cache to better achieve hybrid Blob store purposes. > HybridBlobStore: Option to always write to ObjectStorage > > > Key: JAMES-3073 > URL: https://issues.apache.org/jira/browse/JAMES-3073 > Project: James Server > Issue Type: Improvement >Reporter: Nguyễn Việt Đức >Priority: Major > > About storing small blobs in Cassandra, I think we should also be able to > store them (duplicate them) in the object storage. > More precisely, even if an e-mail is so small we can entirely store it in > Cassandra, we should have an option to say: "let's store it also in the > object storage". So that there one location with all e-mails, in case of > rough backup. > Here I propose the name of the configuration property: > hybrid.duplicate.writes=true > Configuration files to modify: > james-project/dockerfiles/run/guice/cassandra-rabbitmq/destination/conf/blob.properties > james-project/dockerfiles/run/guice/cassandra-rabbitmq-ldap/destination/conf/blob.properties > Website documentation: james-project/src/site/xdoc/server/config-blobstore.xml > Name of the configuration POJO: HybridBlobStore.Configuration -- 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-3070) RabbitMQ MailQueue should not share Receiver for several purpose
[ https://issues.apache.org/jira/browse/JAMES-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139049#comment-17139049 ] Benoit Tellier commented on JAMES-3070: --- What is the status of this work? > RabbitMQ MailQueue should not share Receiver for several purpose > > > Key: JAMES-3070 > URL: https://issues.apache.org/jira/browse/JAMES-3070 > Project: James Server > Issue Type: Improvement > Components: Queue >Reporter: Matthieu Baechler >Priority: Major > > "spool" MailQueue is used in several places in James code. > The usage pattern is quite different in those different places. > While trying to control accurately the rate of James dequeue, we found that > sharing a single RabbitMQ Receiver can prevent from passing it specific > parameters at construction. > We should try make James work without the MailQueue sharing for RabbitMQ. -- 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-2967) Add Logging of IMAP Command
[ https://issues.apache.org/jira/browse/JAMES-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2967. - Resolution: Fixed https://github.com/linagora/james-project/pull/3402 enabled this. > Add Logging of IMAP Command > --- > > Key: JAMES-2967 > URL: https://issues.apache.org/jira/browse/JAMES-2967 > Project: James Server > Issue Type: Improvement > Components: IMAPServer > Environment: All >Reporter: Jerry Malcolm >Priority: Minor > Fix For: 3.3.0 > > > Debugging the issue I encountered with the iPhone mail was hindered by the > inability to easily view the IMAP request commands. I had to use > tcpdump/wireshark to see what was being sent from the iPhone. Ultimately I > found where/how to add a log entry containing the IMAP request. I recommend > adding this logging capability at the LOGGER.debug(...) level. I have the > code completed/tested and will create a pull request. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2925) Decreasing chunk_length_in_kb for read heavy workloads
[ https://issues.apache.org/jira/browse/JAMES-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2925. - Resolution: Abandoned Preliminary performance tests were not conclusive > Decreasing chunk_length_in_kb for read heavy workloads > -- > > Key: JAMES-2925 > URL: https://issues.apache.org/jira/browse/JAMES-2925 > Project: James Server > Issue Type: Improvement > Components: cassandra, mailbox >Reporter: Benoit Tellier >Priority: Major > > James mostly serve primarily reads with a ration often other 80%. > We often benefit from read optimization. > Such an optimization is the size of chunks being LZ4 compressed within > SSTables files: > - bigger chunks means better compression > - but also means all reads need to load the full chunk size, thus costing IOs > For read heavy workloads, experiment shows decreasing the chunk size from > 64KB (default) to a more reasonable value (like 4KB) often leads to > significant performance enhancement. > As an adoption step, we should conduct a performance test on read-heavy > mailbox-metadata. If conclusive, we can consider adoption on some other often > read metadata. > As a reference here is a reference article on the last pickle blog: > https://thelastpickle.com/blog/2018/08/08/compression_performance.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2919) Allow partial message read in JMAP DRAFT
[ https://issues.apache.org/jira/browse/JAMES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2919. - Resolution: Fixed Contributed > Allow partial message read in JMAP DRAFT > > > Key: JAMES-2919 > URL: https://issues.apache.org/jira/browse/JAMES-2919 > Project: James Server > Issue Type: Wish > Components: JMAP >Reporter: Benoit Tellier >Assignee: Benoit Tellier >Priority: Major > Fix For: 3.5.0 > > Attachments: adr-0001-jmap-partial-reads.md, > adr-0001-jmap-partial-reads.md, adr-0002-precompute-jmap-preview.md, > adr-0002-precompute-jmap-preview.md > > > Please find attached the two technical decisions being proposed. > h1. Objectives: > - Reduce the pressure exerced by JMAP on underlying data stores > - Improve network usage between James & JMAP client > h2. Proposal for JMAP partial reads > Introduce two projections for JMAP messages: > - One with only metadata > - One with metadata + headers > Given the properties requested by the client, the most appropriate message > projection will be returned. > Finally, we should nullify JSON fields not requested by the client before > sending it to the client. > h2. Proposal for JMAP preview computation > We should pre-compute message preview. > A MailboxListener will compute the preview and store it in a > MessagePreviewStore. > We should have a Cassandra and memory implementation. > When the preview is precomputed then for these messages we can consider the > "preview" property as a metadata. > We should provide a webAdmin task allowing to rebuild the projection. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2908) Use cassandra-rabbitmq in webadmin integration tests
[ https://issues.apache.org/jira/browse/JAMES-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2908. - Fix Version/s: 3.5.0 Resolution: Fixed Duc Tran did contribute this > Use cassandra-rabbitmq in webadmin integration tests > > > Key: JAMES-2908 > URL: https://issues.apache.org/jira/browse/JAMES-2908 > Project: James Server > Issue Type: Task > Components: tests >Reporter: Matthieu Baechler >Priority: Major > Fix For: 3.5.0 > > > webadmin integration tests are not run on all products because it's a bit > slow to run. > As cassandra-rabbitmq product is now the preferred distributed > implementation, we should make webadmin integration tests to run on this > product. -- 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-2909) Use Architectural Decision Records
[ https://issues.apache.org/jira/browse/JAMES-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139071#comment-17139071 ] Benoit Tellier commented on JAMES-2909: --- Now that we use ADRs, could this be closed? > Use Architectural Decision Records > -- > > Key: JAMES-2909 > URL: https://issues.apache.org/jira/browse/JAMES-2909 > Project: James Server > Issue Type: Improvement >Reporter: Gautier DI FOLCO >Priority: Major > Time Spent: 3h 10m > Remaining Estimate: 0h > > In order to adopt a more community-oriented, we should use an Architectural > Decision Records-based processus, being the support of discussion on the > developers mailing-lists. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2856) Add quotaRoot in mailboxDetails over webAdmin
[
https://issues.apache.org/jira/browse/JAMES-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2856.
-
Resolution: Won't Fix
quotaRoot is a teckie IMAP detail that we don't want to leak over webadmin.
> Add quotaRoot in mailboxDetails over webAdmin
> -
>
> Key: JAMES-2856
> URL: https://issues.apache.org/jira/browse/JAMES-2856
> Project: James Server
> Issue Type: New Feature
> Components: webadmin
>Reporter: Benoit Tellier
>Priority: Major
>
> This command takes 3 argument **namespace**, **username**, **mailboxName**
> and return the corresponding **QuotaRoot**.value() in String.
> For example:
> {code:java}
> GETQUOTAROOT #private b...@james.org inbox
> {code}
> should return
> {code:java}
> #private&b...@james.org
> {code}
> WebAdmin should allow to get mailbox quotaRoot as well. (This will help
> dropping the CLI in the future)
> Proposal is to add it as part of mailbox details on this endpoint:
> {code:java}
> GET /users/{username}/mailboxes/{mailboxName}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2853) Testing toolbox for Remote Delivery
[ https://issues.apache.org/jira/browse/JAMES-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2853. - Fix Version/s: 3.5.0 Resolution: Fixed All sub-issues are closed, so should be the story ticket > Testing toolbox for Remote Delivery > --- > > Key: JAMES-2853 > URL: https://issues.apache.org/jira/browse/JAMES-2853 > Project: James Server > Issue Type: Test > Components: Remote Delivery, tests >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.5.0 > > > Today, remoteDelivery is lightly tested and error corner cases are not tested. > Several bugs are already known cf JAMES-2097 > JAMES-2442 is an attempt to write such tests but some of these tests require > not-yet available tooling. > In order to write such tests we need : > - 1. a tcp mock server (replying smtp error codes) > - 2. listening on port 25 > - 3. on it's own IP > The FakeSmtp docker approach we had so far covers 2 & 3. We did not find yet > a good solution for 1. > What we had in mind is: > - Writing our own SMTP mock server (POC available here: > https://github.com/linagora/james-project/pull/2545 > - Introduce a JSON format corresponding to the behavior of this Mock server > - load this via HTTP to allow remote setup > - exposes delivered emails over HTTP to allow writing assertions > - dockerizing this. > This will allow writing the tests we are missing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2819) Upgrade pdfbox following CVE-2019-0228
[ https://issues.apache.org/jira/browse/JAMES-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2819. - Resolution: Fixed 739f1a4286dbb7a20ba738c7fb72f87c1d11fe9b commit did contribute this. > Upgrade pdfbox following CVE-2019-0228 > -- > > Key: JAMES-2819 > URL: https://issues.apache.org/jira/browse/JAMES-2819 > Project: James Server > Issue Type: Task >Affects Versions: 3.3.0, 3.4.0 >Reporter: Matthieu Baechler >Priority: Major > > James uses pdfbox library and a vulnerability was disclosed recently : > CVE-2019-0228 > We have to update pdfbox version in supported branches -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2796) enhance Docker usage during tests
[
https://issues.apache.org/jira/browse/JAMES-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139080#comment-17139080
]
Benoit Tellier commented on JAMES-2796:
---
{code:java}
% git log --grep=JAMES-2796
commit be8cf352e65d3d659aa477ea01aed86438f9fe28
Author: Matthieu Baechler
Date: Tue Jun 18 19:06:47 2019 +0200
JAMES-2796 Drop DockerContainer tryConnect method
commit 45def3f2a54b206d044789f4fb7b51cbfd9d80f2
Author: Matthieu Baechler
Date: Tue Jun 18 18:52:39 2019 +0200
JAMES-2796 rename DockerGenericContainer to DockerContainer
commit db29d2e112acf3713ca9bfc24b98ee789d52054f
Author: Matthieu Baechler
Date: Tue Jun 18 18:50:20 2019 +0200
JAMES-2796 Split the check for Docker from remaining code and provide
factory methods for containers
{code}
Is this solved?
> enhance Docker usage during tests
> -
>
> Key: JAMES-2796
> URL: https://issues.apache.org/jira/browse/JAMES-2796
> Project: James Server
> Issue Type: Improvement
>Reporter: Matthieu Baechler
>Priority: Major
>
> Docker is used extensively for testing. However, it grew organically and the
> codebase can be enhanced/simplified at this point.
--
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-2774) RabbitMQEventBusTest stability
[ https://issues.apache.org/jira/browse/JAMES-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2774. - Resolution: Fixed This is likely solved now. > RabbitMQEventBusTest stability > -- > > Key: JAMES-2774 > URL: https://issues.apache.org/jira/browse/JAMES-2774 > Project: James Server > Issue Type: Improvement >Reporter: Trần Tiến Đức >Priority: Trivial > > because of the tests are unstable -- 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-2760) Performance indicators: Indexation time & dataset size
[ https://issues.apache.org/jira/browse/JAMES-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2760. - Resolution: Invalid > Performance indicators: Indexation time & dataset size > -- > > Key: JAMES-2760 > URL: https://issues.apache.org/jira/browse/JAMES-2760 > Project: James Server > Issue Type: New Feature > Components: elasticsearch >Reporter: René Cordier >Priority: Major > Fix For: 3.4.0 > > > You will design a protocol for measuring the following ES related performance > indicator > Protocol: > * run the provisioning of a James server > * Use grafana to monitor ES indexation (latency p99+p90+p75+p50 + throughtput) > * Mesure total on disk data for ElasticSearch. > You will measure the following performance indicator for master. -- 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-2718) Performance indicator: Default Inbox search
[ https://issues.apache.org/jira/browse/JAMES-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2718. - Resolution: Invalid > Performance indicator: Default Inbox search > --- > > Key: JAMES-2718 > URL: https://issues.apache.org/jira/browse/JAMES-2718 > Project: James Server > Issue Type: New Feature > Components: elasticsearch >Reporter: René Cordier >Priority: Major > Fix For: 3.4.0 > > > Given a provisioned James server, > You will develop a Gatling scenario where users list their 20 more recent > emails ordered by dates. They also fetch basic properties (subject + from + > to + dates + summary) within the result of this search. > You will measure this performance indicator on master. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Comment Edited] (JAMES-2679) Some Mail instance can have a null name
[
https://issues.apache.org/jira/browse/JAMES-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139086#comment-17139086
]
Benoit Tellier edited comment on JAMES-2679 at 6/18/20, 5:01 AM:
-
This is likely solved ?
was (Author: btellier):
This is likely closed ?
> Some Mail instance can have a null name
> ---
>
> Key: JAMES-2679
> URL: https://issues.apache.org/jira/browse/JAMES-2679
> Project: James Server
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Matthieu Baechler
>Priority: Major
> Fix For: 3.3.0
>
>
> During a stress test, I encountered this kind of errors :
> {code}
> java.lang.NullPointerException: null
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:877)
> at
> org.apache.james.queue.rabbitmq.view.api.DeleteCondition.withName(DeleteCondition.java:170)
> at
> org.apache.james.queue.rabbitmq.Dequeuer.lambda$ack$1(Dequeuer.java:106)
> at
> com.github.fge.lambdas.consumers.ThrowingConsumer.accept(ThrowingConsumer.java:22)
> at
> org.apache.james.queue.rabbitmq.Dequeuer$RabbitMQMailQueueItem.done(Dequeuer.java:62)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:80)
> at
> org.apache.james.mailetcontainer.impl.JamesMailSpooler.lambda$run$0(JamesMailSpooler.java:164)
> {code}
> It looks like there's some code path that allows a Mail to have a null name.
--
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-2659) RabbitMQ EventBus test `RabbitMQEventBusTest` is unstable
[
https://issues.apache.org/jira/browse/JAMES-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2659.
-
Resolution: Fixed
I would say this no longer is an issue
> RabbitMQ EventBus test `RabbitMQEventBusTest` is unstable
> -
>
> Key: JAMES-2659
> URL: https://issues.apache.org/jira/browse/JAMES-2659
> Project: James Server
> Issue Type: Bug
> Components: rabbitmq
>Reporter: Matthieu Baechler
>Priority: Major
>
> Master build fails often with that error
> {code:java}
> [null] org.junit.ComparisonFailure: expected:<3[1]> but was:<3[2]>
> [null]at
> org.apache.james.mailbox.events.RabbitMQEventBusTest$LifeCycleTest$MultiEventBus.registrationsShouldNotHandleEventsAfterStop(RabbitMQEventBusTest.java:568)
> {code}
> We should first disable this test to have a green build back then fix the
> instability.
--
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-2679) Some Mail instance can have a null name
[
https://issues.apache.org/jira/browse/JAMES-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139086#comment-17139086
]
Benoit Tellier commented on JAMES-2679:
---
This is likely closed ?
> Some Mail instance can have a null name
> ---
>
> Key: JAMES-2679
> URL: https://issues.apache.org/jira/browse/JAMES-2679
> Project: James Server
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Matthieu Baechler
>Priority: Major
> Fix For: 3.3.0
>
>
> During a stress test, I encountered this kind of errors :
> {code}
> java.lang.NullPointerException: null
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:877)
> at
> org.apache.james.queue.rabbitmq.view.api.DeleteCondition.withName(DeleteCondition.java:170)
> at
> org.apache.james.queue.rabbitmq.Dequeuer.lambda$ack$1(Dequeuer.java:106)
> at
> com.github.fge.lambdas.consumers.ThrowingConsumer.accept(ThrowingConsumer.java:22)
> at
> org.apache.james.queue.rabbitmq.Dequeuer$RabbitMQMailQueueItem.done(Dequeuer.java:62)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:80)
> at
> org.apache.james.mailetcontainer.impl.JamesMailSpooler.lambda$run$0(JamesMailSpooler.java:164)
> {code}
> It looks like there's some code path that allows a Mail to have a null name.
--
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-2658) Generic mailet to call an external microservice, and add extra information to an email
[
https://issues.apache.org/jira/browse/JAMES-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2658.
-
Resolution: Won't Fix
> Generic mailet to call an external microservice, and add extra information to
> an email
> --
>
> Key: JAMES-2658
> URL: https://issues.apache.org/jira/browse/JAMES-2658
> Project: James Server
> Issue Type: Wish
>Reporter: Michael Bailly
>Priority: Minor
>
> Hello team. This is a Request For Comments for a feature, to be able to add
> extra information to an email on delivery to a local mailbox.
> h2. Principle
> the mailet calls a remote webservice, with a pre-specified payload. It gets
> back, either an error, or another specific payload. This payload can instruct
> the James server to add informations to the email. The first case, that we
> handle here, is to add extra headers.
>
> h2. Implementation
> OK, I'll try to map the mailet syntax, but I'll make mistakes, it's to
> illustrate the principle.
> James configuration:
> {{ endpoint="https://server.com/api/infos"; />}}
> Seeing this, the mailer issues a POST on {{[https://server.com/api/infos]}}
> with the following payload structure:
> {
> {{ "messageId" : "messageId",}}
> {{ "from" : {}}
> {{ "address" : "f...@test.com",}}
> {{ "personal" : "first_name last_name"}}
> {{ },}}
> {{ "to" : [ {}}
> {{ "address" : "t...@test.com",}}
> {{ "personal" : "first_name last_name of to1"}}
> {{ } ],}}
> {{ "cc" : [ {}}
> {{ "address" : "c...@test.com",}}
> {{ "personal" : null}}
> {{ }, {}}
> {{ "address" : "c...@test.com",}}
> {{ "personal" : "first_name last_name of cc2"}}
> {{ }, {}}
> {{ "address" : "c...@test.com",}}
> {{ "personal" : "first_name last_name of cc3"}}
> {{ } ],}}
> {{ "bcc" : [ ],}}
> {{ "Received" : "Mon, 28 Jan 2019 07:56:43 +",}}
> {{ "Date" : "Mon, 28 Jan 2019 07:56:43 +",}}
> {{ "in-Reply-To" : "messageId_in_reply_to",}}
> {{ "subject" : "IMPORTANT: Testing The Priority Inbox",}}
> {{ "body" : "\nDear, \n\n this a test of the priority inbox\n
> regards,\nfirst_name last_name\nDirector Tester",}}
> {{ "attachments" : [{}}
> {{ "file_size" : "243534",}}
> {{ "content_name" : "presentation.pdf",}}
> {{ "content_type" : "APPLICATION/PDF"}}
> {{ }, {}}
> {{ "file_size": "243534",}}
> {{ "content_type" : "APPLICATION/PDF",}}
> {{ "content_name" : "performance.pdf"}}
> {{ }],}}
> {{ "emailFolder" : "INBOX",}}
> {{ "user" : "first_name last_name of to1",}}
> {{ "alternativeAddress" : [ "t...@test.com",
> "first_name.last_n...@test.com" ],}}
> {{ "X-Spam-Flag" : "NO"}}
> {{}}}
> Worth noting: all those attributes are JSON formatting of an email contents,
> EXCEPT:
> * emailFolder : the destination folder of the email
> * user & alternativeAddress : the user the email is delivered to
> This mailet expects a specific format for the response. Here is a proposal:
> 1/ "bypass" (do nothing)
> {{{}}}
> 2/ "add headers"
> {
> "addHeaders": [
> {name: "X-INFO1", value: "some header value"},
> \{name: "X-INFO1-SCORE", value: "0.4"}
> ]
> }
> h3. Handling failure
> The mailet may support a specific attribute to define the behaviour in case
> of failure.
> {{ endpoint="https://server.com/api/infos"; on-failure="ignore" />}}
> h3. Configuring retries
> The mailet may support a retry parameter, allowing to retry x times before
> "really" failing. The additional, optional retry delay parameter could set
> the time, in seconds, to wait between each retry.
> {{ endpoint="https://server.com/api/infos"; on-failure="ignore" retry="5"
> retry-delay="0.5" />}}
> h3. Setting blocking behaviour
> Some processing may not require an immediate response, and may allow further
> processing of the mailet chain. Here, either the "blocking" or the "async"
> attribute, I can't choose, may be used.
> {{ endpoint="https://server.com/api/infos"; on-failure="ignore" retry="5"
> retry-delay="0.5" blocking="false" />}}
> or, as a second proposal
> {{ endpoint="https://server.com/api/infos"; on-failure="ignore" retry="5"
> retry-delay="0.5" async="true" />}}
> h2. Things I don't know
> * Where to send email on failure, if the "on-failure" attribute is not
> "ignore".
--
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-2614) RabbitMQMailQueueTest::concurrentEnqueueDequeueShouldNotFail is unstable
[
https://issues.apache.org/jira/browse/JAMES-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2614.
-
Resolution: Fixed
Likely fixed
> RabbitMQMailQueueTest::concurrentEnqueueDequeueShouldNotFail is unstable
>
>
> Key: JAMES-2614
> URL: https://issues.apache.org/jira/browse/JAMES-2614
> Project: James Server
> Issue Type: Bug
> Components: Queue, rabbitmq
>Reporter: Benoit Tellier
>Priority: Major
>
> RabbitMQMailQueueTest::concurrentEnqueueDequeueShouldNotFail is unstable and
> have high probability of failing in some environments.
> The related test is disabled, and need to be re-enabled after investigation
> and a fix.
> Here are the related stacktrace:
> {code:java}
> [null] 11:45:50.630 [ERROR] o.a.j.u.c.ConcurrentTestRunner - Error caught
> during concurrent testing
> [null] com.rabbitmq.client.ShutdownSignalException: channel error; protocol
> method: #method(reply-code=404, reply-text=NOT_FOUND - no
> queue 'JamesMailQueue-workqueue-spool' in vhost '/', class-id=60,
> method-id=70)
> [null]at
> com.rabbitmq.client.impl.ChannelN.asyncShutdown(ChannelN.java:516)
> [null]at
> com.rabbitmq.client.impl.ChannelN.processAsync(ChannelN.java:346)
> [null]at
> com.rabbitmq.client.impl.AMQChannel.handleCompleteInboundCommand(AMQChannel.java:178)
> [null]at
> com.rabbitmq.client.impl.AMQChannel.handleFrame(AMQChannel.java:111)
> [null]at
> com.rabbitmq.client.impl.AMQConnection.readFrame(AMQConnection.java:670)
> [null]at
> com.rabbitmq.client.impl.AMQConnection.access$300(AMQConnection.java:48)
> [null]at
> com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:597)
> [null]... 1 common frames omitted
> [null] Wrapped by: com.rabbitmq.client.ShutdownSignalException: channel
> error; protocol method: #method(reply-code=404,
> reply-text=NOT_FOUND - no queue 'JamesMailQueue-workqueue-spool' in vhost
> '/', class-id=60, method-id=70)
> [null]at
> com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
> [null]at
> com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:36)
> [null]at
> com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:494)
> [null]at
> com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:288)
> [null]at
> com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:138)
> [null]... 16 common frames omitted
> [null] Wrapped by: java.io.IOException: null
> [null]at com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:126)
> [null]at com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:122)
> [null]at
> com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:144)
> [null]at
> com.rabbitmq.client.impl.ChannelN.basicGet(ChannelN.java:1148)
> [null]at
> com.rabbitmq.client.impl.recovery.AutorecoveringChannel.basicGet(AutorecoveringChannel.java:431)
> [null]at
> org.apache.james.queue.rabbitmq.RabbitClient.lambda$poll$4(RabbitClient.java:86)
> [null]at
> org.apache.james.backend.rabbitmq.SimpleChannelPool.execute(SimpleChannelPool.java:46)
> [null]at
> org.apache.james.queue.rabbitmq.RabbitClient.poll(RabbitClient.java:87)
> [null]at
> org.apache.james.queue.rabbitmq.Dequeuer.singleChannelRead(Dequeuer.java:136)
> [null]at
> com.nurkiewicz.asyncretry.AsyncRetryExecutor.lambda$getWithRetry$1(AsyncRetryExecutor.java:62)
> [null]at
> com.nurkiewicz.asyncretry.SyncRetryJob.run(SyncRetryJob.java:23)
> [null]... 8 common frames omitted
> [null] Wrapped by: java.util.concurrent.CompletionException:
> java.io.IOException
> [null]at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
> [null]at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
> [null]at
> java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)
> [null]at
> java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
> [null]at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> [null]at
> java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> [null]at
> com.nurkiewicz.asyncretry.RetryJob.retryOrAbort(RetryJob.java:74)
> [null]at
> com.nurkiewicz.asyncretry.RetryJob.handleUserThrowable(RetryJob.java:58)
> [null]at
> com.nurkiewicz.asyncretry.RetryJob.handleThrowable(RetryJob.java:50)
> [null]at
> com.nurkiewicz.asyncretry.SyncRetryJob.run(SyncR
[jira] [Closed] (JAMES-2565) Webadmin: allow EML upload
[ https://issues.apache.org/jira/browse/JAMES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2565. - Resolution: Duplicate > Webadmin: allow EML upload > -- > > Key: JAMES-2565 > URL: https://issues.apache.org/jira/browse/JAMES-2565 > Project: James Server > Issue Type: New Feature > Components: mailbox, webadmin >Reporter: Benoit Tellier >Priority: Major > Labels: feature > > In an effort to drop the CLI completely in Guice products, we need to support > all features of the CLI in the webAdmin alternative. > Currently, one of the features missing are related to "message upload". > As an admin, I should be able to upload a message in any mailbox. > Proposed API is > ``` > POST /users/b...@domain.tld/mailboxes/INBOX -d 'header: A BIG EML\r\nWith a > bi body' > 204 > ``` > You will add it as part of UserMailboxesRoutes class. -- 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-2564) WebAdmin: Mappings 'address + regex' support
[
https://issues.apache.org/jira/browse/JAMES-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2564.
-
Resolution: Fixed
Contributed
> WebAdmin: Mappings 'address + regex' support
>
>
> Key: JAMES-2564
> URL: https://issues.apache.org/jira/browse/JAMES-2564
> Project: James Server
> Issue Type: New Feature
> Components: data, webadmin
>Reporter: Benoit Tellier
>Priority: Major
> Labels: feature
>
> In an effort to drop the CLI completly in Guice products, we need to support
> all features of the CLI in the webAdmin alternative.
> Currently, one of the features missing are related to "mappings".
> We would like to implement them on top of webadmin.
> Create routes for:
> - Reading, adding and removing address mappings
> - Reading, adding and removing regex mappings
> - List all mappings
> Here is a _suggestion_ of APIs:
> - Address mapping
> ```
> GET /mappings/address/al...@apache.org
> 200
> [
>{ "toAddress": "b...@apache.org"},
>...
> ]
> PUT /mappings/address/al...@apache.org
> With body { "toAddress": "b...@apache.org"}
> Will add the mapping
> DELETE /mappings/address/al...@apache.org
> With body { "toAddress": "b...@apache.org"}
> Will remove the mapping
> ```
> Regarding regex mapping:
> ```
> GET /mappings/regex/fromDomain.tld
> 200
> [
>{ "expression": "prefix_(.*)@test:admin@${1}"},
>...
> ]
> PUT /mappings/regex/fromDomain.tld
> With body {"expression": "prefix_(.*)@test:admin@${1}"}
> Will add the mapping
> DELETE /mappings/regex/fromDomain.tld
> With body {"expression": "prefix_(.*)@test:admin@${1}"}
> Will remove the mapping
> ```
> Regarding listing mappings:
> ```
> GET /mappings
> [
>{
> "type": "Domain", // One of Domain, Address, Regex, Group, Forward,
> Error
>"source": {
> "fixedUser": "*",
> "fixedDomain": "domain.tld"
>},
>"mapping" : "newDomain.tld"
> }, ...
> ]
> ```
> Open separate pull requests for each sets of routes.
> We do stay at your full disposal on Gitter to answer related questions
> (https://gitter.im/apache/james-project)
--
This message was sent by Atlassian Jira
(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-2532) Investigate why guice-mutlibindings doesn't use guice.version
[ https://issues.apache.org/jira/browse/JAMES-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2532. - Resolution: Fixed guice-multibings is now part of guice. > Investigate why guice-mutlibindings doesn't use guice.version > - > > Key: JAMES-2532 > URL: https://issues.apache.org/jira/browse/JAMES-2532 > Project: James Server > Issue Type: Task >Reporter: Jean Helou >Priority: Minor > > When merging the pom files, guice-multibindings was fixed at version 4.0 and > not pinned to guice.version > [https://github.com/linagora/james-project/pull/939/files#diff-600376dffeb79835ede4a0b285078036R1419] > is the change which introduced that. -- 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-2483) Email search hogs processor
[ https://issues.apache.org/jira/browse/JAMES-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2483. - Resolution: Abandoned I'm closing this bug report given the detailed answer of matthieu and the lack of activity. > Email search hogs processor > --- > > Key: JAMES-2483 > URL: https://issues.apache.org/jira/browse/JAMES-2483 > Project: James Server > Issue Type: Bug > Components: elasticsearch >Affects Versions: 3.0.1 > Environment: Ubuntu 18.04 Server (Apache James with PostgreSQL 10) > Ubuntu 16.04 Clients with Evolution configured to use IMAP+ accounts >Reporter: John Bester >Priority: Major > Labels: features, performance > > We have a James server with a database of about 17G in a LAN. There are 10 > email clients - all Evolution running on top of Ubuntu 16.04. The James > server holds email in a Postgresql 10 database on an Ubuntu 18.04 Server VM. > The James installation is fairly new and all emails were copied from previous > local email boxes from the various workstations. > Whenever someone tries to do a search, the James server completely comes to > grinding halt with all processors hogged at 100% (java/james - postgres > processes are all idle). This results in the entire office not being able to > do any email activity and the only way to get going again is to restart the > James service. > This may be because of a search index being built, because having all > resources go into a search of one client does not seem like a good idea to > me. If it is index building, then why is this not done during the night and > why have indexes not been created even though the server have been running > for more than a month? As an alternative, why is James doing all the work > when there are full text indexes available in Postgres (and maybe other > database options as well)? Surely it would be possible to define a search > statement like all the other SQL statements are defined for a specific > database. And if the database cannot handle full text searches, then leave > the statement empty and fall back to whatever search algorithm is currently > 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] [Closed] (JAMES-2466) Reduce build logging
[ https://issues.apache.org/jira/browse/JAMES-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2466. - Resolution: Fixed The build log size are now way smaller, this likely is no longer an issue. > Reduce build logging > > > Key: JAMES-2466 > URL: https://issues.apache.org/jira/browse/JAMES-2466 > Project: James Server > Issue Type: Improvement > Components: Build System >Reporter: Benoit Tellier >Priority: Major > > When building James, we currently generate a ~200MB file of logs. > This is too much: downloading it is long, analysing it is complicated and > storing it is costly. > Hence, as we don't care about detailed logs, and as we can easily turn > logging level higher when debugging, I'd like to suggest enforcing WARN > logging level for test in projects using *logback* -- 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-2397) UsersRepository should return the right case variation
[ https://issues.apache.org/jira/browse/JAMES-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2397. - Fix Version/s: 3.6.0 Resolution: Fixed Fixed on recent James versions > UsersRepository should return the right case variation > -- > > Key: JAMES-2397 > URL: https://issues.apache.org/jira/browse/JAMES-2397 > Project: James Server > Issue Type: New Feature >Reporter: Benoit Tellier >Priority: Major > Fix For: 3.6.0 > > > Currently, UsersRepository only handles virtual hosting. > We need to be able to handle case variations as well. > See JAMES-2389 -- 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-2375) DSNBounce mailet do not provide a subject
[
https://issues.apache.org/jira/browse/JAMES-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2375.
-
Resolution: Fixed
c17b2ad4fef46600601878d5ed7866c674872616 did fix this
> DSNBounce mailet do not provide a subject
> -
>
> Key: JAMES-2375
> URL: https://issues.apache.org/jira/browse/JAMES-2375
> Project: James Server
> Issue Type: Bug
> Components: Mailet Contributions
>Reporter: Benoit Tellier
>Priority: Major
> Labels: bug, easy-fix
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> As reported by Craig Cudmor,
> DSNBounce never position a subject on sent emails, independently from the
> "prefix" configuration option.
> {code:java}
> @Test
> public void test() throws Exception {
> FakeMailetConfig mailetConfig = FakeMailetConfig.builder()
> .mailetName(MAILET_NAME)
> .mailetContext(fakeMailContext)
> .setProperty("prefix", "Re:")
> .build();
> dsnBounce.init(mailetConfig);
> MailAddress senderMailAddress = new MailAddress("sen...@domain.com");
> FakeMail mail = FakeMail.builder()
> .sender(senderMailAddress)
> .mimeMessage(MimeMessageBuilder.mimeMessageBuilder()
> .setSubject("Toto")
> .setText("My content"))
> .name(MAILET_NAME)
> .recipient("recipi...@domain.com")
>
> .lastUpdated(DateTime.parse("2016-09-08T14:25:52.000Z").toDate())
> .build();
> dsnBounce.service(mail);
> List sentMails = fakeMailContext.getSentMails();
> assertThat(sentMails).hasSize(1);
> SentMail sentMail = sentMails.get(0);
> MimeMessage sentMessage = sentMail.getMsg();
> assertThat(sentMessage.getSubject()).isEqualTo("Re: Toto");
> }
> {code}
> will fail.
> We need to use a default 'Re: ' prefix, and ensure a subject is always sent.
> We need to check subjects for the RedirectNotify mailet hierarchy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3227) Can't assign JIRA issues to myself
[ https://issues.apache.org/jira/browse/JAMES-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139156#comment-17139156 ] Benoit Tellier commented on JAMES-3227: --- Hi david. After reading https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization I believe that all was needed was granting you to the contributor role on our specific project. I just did it. > Can't assign JIRA issues to myself > -- > > Key: JAMES-3227 > URL: https://issues.apache.org/jira/browse/JAMES-3227 > Project: James Server > Issue Type: Bug >Reporter: David Leangen >Priority: Minor > > I am not able to assign JIRA issues to myself. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3227) Can't assign JIRA issues to myself
[ https://issues.apache.org/jira/browse/JAMES-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139157#comment-17139157 ] Benoit Tellier commented on JAMES-3227: --- Can you see if this solved it? Otherwize I will have to ask INFRA... > Can't assign JIRA issues to myself > -- > > Key: JAMES-3227 > URL: https://issues.apache.org/jira/browse/JAMES-3227 > Project: James Server > Issue Type: Bug >Reporter: David Leangen >Priority: Minor > > I am not able to assign JIRA issues to myself. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3225) Provide automated builds for Apache James - (restore builds.apache.org ?)
[ https://issues.apache.org/jira/browse/JAMES-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139183#comment-17139183 ] Benoit Tellier commented on JAMES-3225: --- > I would love for us to have a community call and discuss what we want out of > this and setup how we are going to approach the move. This is to align our objectives and get to a common ground on this important issue. +1 (but we would need to take notes and make them public) > Please ask internally what Linagora is willing to offer. Note that this could take some time :-) > Provide automated builds for Apache James - (restore builds.apache.org ?) > -- > > Key: JAMES-3225 > URL: https://issues.apache.org/jira/browse/JAMES-3225 > Project: James Server > Issue Type: Task >Reporter: Ioan Eugen Stan >Assignee: Ioan Eugen Stan >Priority: Major > > For a long time we had builds that ran on the Apache Infrastructure > https://builds.apache.org/view/All/job/james-mailet/ . > The build infrastructure is not running for ~ 3 years now. > I believe it is important for us to have automated builds. > This ticket should gather the work needed to make this a reality. > There are lots of things to take into consideration. > My ( [~ieugen] ) opinions on how to handle this. > * builds should run automatically > * builds should run fast < 10 min > * there are several things they should do (not exhaustive) > ** verify the source code > ** compile the source code > ** run the unit tests > ** run the integration tests > ** publish SNAPSHOTS (only from master or develop ?!) > ** run code analytics > ** publish reports relating to build > ** provide build status for other services > For smaller projects this is a no-brainer. > For the current state of Apache James this is a challange, especially in the > context of > - multiple git branches and PR's > - the distributed integration tests which take a long time > Given the limited resources available for us on the Apache infrastructure we > will have to be selective of what we do. > Personally I don't see how we can run the current (40mni +) integration suite > on each push / build. I'm pretty sure we will get banned :) or throttled. > So a discussion should be in order on how to solve these issues but some > options regarding what we can do: > - make integration tests OPT-IN > - run (distributed) integration tests once a day or once every 6h / 12h > - have build profiles that build a common subset all the time and run > The nuclear option: prune some of the components we have in James and we > don't want to support or move them out of the common project. > This is something we should consider especially for buggy components or for > components that don't have a maintainer. > We have limited time and resources. > We can't maintain everything for everybody. > We should be mindful of this. > We can take inspiration from the OFBiz project > https://builds.apache.org/view/All/job/Apache%20OFBiz/ . -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3219) Clarify DNS configuration (dnsservice.xml)
[ https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139191#comment-17139191 ] Benoit Tellier commented on JAMES-3219: --- > If the system uses dnsjava, then is this configuration file only there to > configure dnsjava? Yes > Looking at dnsjava, there are quite a few configuration parameters available. > This is exactly the type of thing that, if possible, I would like to > eliminate from the Basic Server. +1 dnsjava should so far rely on system defaults in the basic server. (dnsjava is usefull to read MX & TXT records, for mail purposes, not only do dns resolution) > Clarify DNS configuration (dnsservice.xml) > -- > > Key: JAMES-3219 > URL: https://issues.apache.org/jira/browse/JAMES-3219 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > I would like to provide a little more detailed documentation for the DNS > service, since users are required to configure this service (or use the > default config) in order to run the James Local Server. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3228) Allow me to resolve JIRA issues
[ https://issues.apache.org/jira/browse/JAMES-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139196#comment-17139196 ] Benoit Tellier commented on JAMES-3228: --- I David, Either commiter or PMC responsibility is needed to close other people JIRA. For the time being , you can tag me there, I will close it for you. If not you can ask on server-dev. Cheers, Benoit > Allow me to resolve JIRA issues > --- > > Key: JAMES-3228 > URL: https://issues.apache.org/jira/browse/JAMES-3228 > Project: James Server > Issue Type: Wish >Reporter: David Leangen >Priority: Minor > > I am not able to change the resolution of JIRA issues. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2541) In order to support distributed deployment, we should write a MailQueue implementation using RabbitMQ
[ https://issues.apache.org/jira/browse/JAMES-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140080#comment-17140080 ] Benoit Tellier commented on JAMES-2541: --- https://issues.apache.org/jira/browse/JAMES-2896 treats about it. Either we close this issue, or we turn JAMES-2896 as a sub issue of this one. > In order to support distributed deployment, we should write a MailQueue > implementation using RabbitMQ > - > > Key: JAMES-2541 > URL: https://issues.apache.org/jira/browse/JAMES-2541 > Project: James Server > Issue Type: Task > Components: Queue >Affects Versions: 3.1.0 >Reporter: Matthieu Baechler >Priority: Major > Fix For: 3.2.0 > > > Default MailQueue for Cassandra/Elasticsearch James product is embedded > ActiveMQ. > After a review of available distributed MQ, we decided that we should support > RabbitMQ to replace ActiveMQ in distributed scenario. > And as we don't want to rely on filesystem for mail content neither, we > decided that only meta-data would go into the MQ and that the raw email would > be stored in a blob-store. > This ticket is supposed to track progress at implementing basic > MailQueueFactoryContract and MailQueueContract on top of RabbitMQ and > blob-store. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2510) use a consistent artifact naming scheme
[ https://issues.apache.org/jira/browse/JAMES-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140085#comment-17140085 ] Benoit Tellier commented on JAMES-2510: --- Maybe all server artifacts (located in server folder) should come with james-server prefix? By moving back mailbox as a server component we would furthermore be able to re-qualify many sub components (like event sourcing) as server components and let them embrass this scheme. > use a consistent artifact naming scheme > --- > > Key: JAMES-2510 > URL: https://issues.apache.org/jira/browse/JAMES-2510 > Project: James Server > Issue Type: Task > Components: Build System >Affects Versions: 3.1.0 >Reporter: Matthieu Baechler >Priority: Major > > Maven modules have different naming scheme, for example : > * apache-james-* > * james-server-* > * protocols-* > it makes everything hard to read and to find and it's redundant because > groupId already gives context about an artifact. > I'll make a proposal to reduce the noise in our maven files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3244) Clarify Listeners Configuration (listeners.xml)
[ https://issues.apache.org/jira/browse/JAMES-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140099#comment-17140099 ] Benoit Tellier commented on JAMES-3244: --- To me too. Listeners are an extension mechanism. > Clarify Listeners Configuration (listeners.xml) > --- > > Key: JAMES-3244 > URL: https://issues.apache.org/jira/browse/JAMES-3244 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3244) Clarify Listeners Configuration (listeners.xml)
[ https://issues.apache.org/jira/browse/JAMES-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140100#comment-17140100 ] Benoit Tellier commented on JAMES-3244: --- You should be able to just delete the file (a WARN log will be emitted) > Clarify Listeners Configuration (listeners.xml) > --- > > Key: JAMES-3244 > URL: https://issues.apache.org/jira/browse/JAMES-3244 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3243) Clarify HealthCheck Configuration (healthcheck.properties)
[ https://issues.apache.org/jira/browse/JAMES-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140102#comment-17140102 ] Benoit Tellier commented on JAMES-3243: --- > I was not able to find any existing documentation about this configuration. > The link provided in the file > (https://james.apache.org/server/config-healthcheck.html) leads to a 404. https://github.com/apache/james-project/blob/master/src/site/xdoc/server/config-healthcheck.xml is the related source code. Current latest Website is not deployed yet, I will redeploy it as part of JAMES-3207 JAMES 3.5.0 release. The healthchecks could be queried as part of WebAdmin REST api, even outside docker. The idea of course is to offer some liveness probes for running James in Kubernetes. This file "just" controls the frequency at wich helthchecks logs are emmitted. > However, we could simply *tell* the Operator how it works without providing a > configuration option. We could therefore eliminate the configuration for this > feature for the Basic Server. +1 In the context of the Basic server we can safely not specify this file. (And the classic WARN will be emitted but let's fix that in another issue). > Clarify HealthCheck Configuration (healthcheck.properties) > -- > > Key: JAMES-3243 > URL: https://issues.apache.org/jira/browse/JAMES-3243 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3230) Clarify JMAP Configuration (jmap.properties)
[ https://issues.apache.org/jira/browse/JAMES-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140104#comment-17140104 ] Benoit Tellier commented on JAMES-3230: --- Yes I agree. There is so far no JPA support for JMAP anyway. Hence this configuration file makes little sense in the first place. To be exposed on the basic server we would need JPA support, & a final RFC-8621 JMAP implementation (& not today draft) > Clarify JMAP Configuration (jmap.properties) > > > Key: JAMES-3230 > URL: https://issues.apache.org/jira/browse/JAMES-3230 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3232) Clarify Mail Repository Stores Configuration (mailrepositorystore.xml)
[ https://issues.apache.org/jira/browse/JAMES-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140107#comment-17140107 ] Benoit Tellier commented on JAMES-3232: --- The "Basic server" should only expose "file" MailRepository and yes we should hide this, +1 You should be able to start James without this file, a log will be emitted (and we will address this log for basic server separately) > Clarify Mail Repository Stores Configuration (mailrepositorystore.xml) > -- > > Key: JAMES-3232 > URL: https://issues.apache.org/jira/browse/JAMES-3232 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3241) Clarify Extension Configuration (extensions.properties)
[ https://issues.apache.org/jira/browse/JAMES-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140108#comment-17140108 ] Benoit Tellier commented on JAMES-3241: --- +1 > Clarify Extension Configuration (extensions.properties) > --- > > Key: JAMES-3241 > URL: https://issues.apache.org/jira/browse/JAMES-3241 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3231) Clarify LMAP Configuration (lmtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140111#comment-17140111 ] Benoit Tellier commented on JAMES-3231: --- Are you speaking of LMTP ? Because LMAP is unknown to me. I agree to hide LMTP by default but we should document as part of the basic server how to document it "opt-in". > Clarify LMAP Configuration (lmtpserver.xml) > --- > > Key: JAMES-3231 > URL: https://issues.apache.org/jira/browse/JAMES-3231 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3234) Clarify POP3 Configuration (pop3server.xml)
[ https://issues.apache.org/jira/browse/JAMES-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140112#comment-17140112 ] Benoit Tellier commented on JAMES-3234: --- +1 I propose nonetheless to document it "opt-in" for the basic server. > Clarify POP3 Configuration (pop3server.xml) > --- > > Key: JAMES-3234 > URL: https://issues.apache.org/jira/browse/JAMES-3234 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3235) Clarify Recipient Rewrite Table Configuration (recipientrewritetable.xml)
[ https://issues.apache.org/jira/browse/JAMES-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140116#comment-17140116 ] Benoit Tellier commented on JAMES-3235: --- This file only present technical details orthogonal to the rewritting feature: not including it won't break anything (just a log will be emitted but let's adress this separately). I do think that documentation for some Recipent Table Rewriting rules could make sense for the basic server. I'm thinking to Alias, DomainAlias, Forward & Group mappings. But the configuration file is definitly uneeded. > Clarify Recipient Rewrite Table Configuration (recipientrewritetable.xml) > - > > Key: JAMES-3235 > URL: https://issues.apache.org/jira/browse/JAMES-3235 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3237) Clarify Users Configuration (usersrepository.xml)
[ https://issues.apache.org/jira/browse/JAMES-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140118#comment-17140118 ] Benoit Tellier commented on JAMES-3237: --- Yes, we should. Embedded database for storing user sounds like a nice idea for the basic server, and sane defaults could be provided for it. Not specifying this configuration file should work. (there will be a warning log) > Clarify Users Configuration (usersrepository.xml) > - > > Key: JAMES-3237 > URL: https://issues.apache.org/jira/browse/JAMES-3237 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)
[ https://issues.apache.org/jira/browse/JAMES-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140122#comment-17140122 ] Benoit Tellier commented on JAMES-3239: --- I think Operator want to easily tune logging. Unability to do so will get them grumpy. IMO we should keep the logback file event for the basic server. Maybe provide a simple version of it. > Clarify Logging Configuration (logback.xml & log4j.properties) > -- > > Key: JAMES-3239 > URL: https://issues.apache.org/jira/browse/JAMES-3239 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3238) Clarify WebAdmin Configuration (webadmin.properties)
[ https://issues.apache.org/jira/browse/JAMES-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140126#comment-17140126 ] Benoit Tellier commented on JAMES-3238: --- We have a middle-term goal of powering the Command Line Interface via webadmin. I proposed an internship hosted by Linagora on that very topic last week. As part of the current release this is not-yet the case so I agree to not try to enable it on the Basic server. Security is an issue as (1) authentication would need to be configured and (2) we rely on default signing key. This is an issue we will need to address when we will want to enable it. +1 to not expose it now. > Clarify WebAdmin Configuration (webadmin.properties) > > > Key: JAMES-3238 > URL: https://issues.apache.org/jira/browse/JAMES-3238 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3233) Clarify Mailet Container Configuration (mailetcontainer.xml)
[ https://issues.apache.org/jira/browse/JAMES-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140130#comment-17140130 ] Benoit Tellier commented on JAMES-3233: --- Yes we are providing sane defaults when the file is missing. That configuration might need to be refreshed (for instance `server/container/guice/jpa-guice/src/main/resources/defaultMailetContainer.xml` do not allow relay for emails generated by the mailet pipeline, rrt errors are not well managed, bcc-stripping errors too, some metrics are not positioned, the spam processor is useless). Given that we refresh it, it should be doing the job, not providing the file will do the trick (and we will get the unfamous warn log ^^) > Clarify Mailet Container Configuration (mailetcontainer.xml) > > > Key: JAMES-3233 > URL: https://issues.apache.org/jira/browse/JAMES-3233 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3233) Clarify Mailet Container Configuration (mailetcontainer.xml)
[ https://issues.apache.org/jira/browse/JAMES-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140131#comment-17140131 ] Benoit Tellier commented on JAMES-3233: --- I wonder however 'if' in some use cases even a "Basic server user" should touch this file: for instance if you rely on a SMTP gateway (could be an easy solution for "trust"). I wonder to what extent what I said above is valid. Maybe we can think of a more concise format for "BasicServer" mailet configuration, but it will require significant work (Represent the configuration as a POJO should enable us to generate it from several "models", we would be able to define a simplified format for it fitting basic server needs. > Clarify Mailet Container Configuration (mailetcontainer.xml) > > > Key: JAMES-3233 > URL: https://issues.apache.org/jira/browse/JAMES-3233 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3229) Clarify IMAP Configuration (imapserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140139#comment-17140139 ] Benoit Tellier commented on JAMES-3229: --- Well we still have the SSL configuration issue (keystore). So far we rely on provided defaults which is unsecure. So I prefer having a configuration file where I could just update the keystore used by IMAP in the basic server. (So removing all the values not related to port binding and keystore.) A long term solution would be to have : - 1/ A easy keystore generation script - 2/ From keystore setting let the basic server deduce the IMAP configuration (which would then not need to be provided) - 3/ This requires reworking the IMAP configuration in order to get a POJO representing it and thus be able to have several generation mechanisms for it. > Clarify IMAP Configuration (imapserver.xml) > --- > > Key: JAMES-3229 > URL: https://issues.apache.org/jira/browse/JAMES-3229 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3236) Clarify SMTP Configuration (smtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140140#comment-17140140 ] Benoit Tellier commented on JAMES-3236: --- Well we still have the SSL configuration issue (keystore). So far we rely on provided defaults which is unsecure. So I prefer having a configuration file where I could just update the keystore used by SMTP in the basic server. (So removing all the values not related to port binding and keystore.) A long term solution would be to have : - 1/ A easy keystore generation script - 2/ From keystore setting let the basic server deduce the SMTP configuration (which would then not need to be provided) - 3/ This requires reworking the SMTP configuration in order to get a POJO representing it and thus be able to have several generation mechanisms for it. > Clarify SMTP Configuration (smtpserver.xml) > --- > > Key: JAMES-3236 > URL: https://issues.apache.org/jira/browse/JAMES-3236 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3242) Clarify JWT Configuration (jwt_publickey)
[ https://issues.apache.org/jira/browse/JAMES-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140141#comment-17140141 ] Benoit Tellier commented on JAMES-3242: --- Given that the basic server will not ship JM%AP & webadmin you can safely get rid of this file. > Clarify JWT Configuration (jwt_publickey) > - > > Key: JAMES-3242 > URL: https://issues.apache.org/jira/browse/JAMES-3242 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3246) Clarify DB Configuration (james-database.properties & META-INF/persistence.xml)
[ https://issues.apache.org/jira/browse/JAMES-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140142#comment-17140142 ] Benoit Tellier commented on JAMES-3246: --- I must admit I am less knowledgeable on this file. Can we get rid of it? I +1 the fact of not exposing it! > Clarify DB Configuration (james-database.properties & > META-INF/persistence.xml) > --- > > Key: JAMES-3246 > URL: https://issues.apache.org/jira/browse/JAMES-3246 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2394) Re-organize configure section
[
https://issues.apache.org/jira/browse/JAMES-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140147#comment-17140147
]
Benoit Tellier commented on JAMES-2394:
---
One "big" problem we have today is that a given documentation files is relevant
for several servers.
We end up saying "ah and euh this configuration is not applicable for you".
I think we need to completly avoid that sheme again for the new documentation
and we should get it adressed with the file hierarchy. I propose:
{code:java}
- Basic Server (see relevant JIRA for file inclusion/exclusion - we don't
document all possible values)
- imapServer.xml
- smtpServer.xml
- mailetContainer.xml (optional, should be oriented toward use cases like
specifying an SMTP gateway, DKIM/SPF records. Maybe we should be exposing some
templates here)
- logback.xml
- Advanced Server [Today configuration documentation, centered on the advanced
server (remove unrelevant documentation entries), organized the way you
proposed it]
- Core components:
- Domain list
- DNS
- Mailet containet
- MailRepositoryStore
- RRT
- Protocols
- SMTP/LMTP
- IMAP4
- POP3
- FetchMail
- Sieve
- Backend specific configuration
- JPA postgrey
- Guice specific configuration
- listeners
- How to...
- Anti-Spam
- Dizstributed Server [Today configuration documentation, centered on the
advanced server (remove unrelevant documentation entries), organized the way
you proposed it]
{code}
Let's skip Spring documentation for now IMO.
> Re-organize configure section
> -
>
> Key: JAMES-2394
> URL: https://issues.apache.org/jira/browse/JAMES-2394
> Project: James Server
> Issue Type: New Feature
> Components: configuration, Documentation
>Reporter: Benoit Tellier
>Priority: Major
>
> I would like to propose to re-organize `configure` section of James website.
> Currently, many pages about many different topics are mixed together, making
> it hard to differenciate the various topics.
> Also the current navigation menu do not reflect well the impact of wiring on
> the configuration: some components are only available under some packagings,
> and thus their configuration is wiring solution specific.
> I'd like to subdivide this section into:
> {code:java}
> - Core components:
> - Domain list
> - DNS
> - Mailet containet
> - MailRepositoryStore
> - RRT
> - Protocols
> - SMTP/LMTP
> - IMAP4
> - POP3
> - FetchMail
> - Sieve
> - Backend specific configuration
> - ElasticSearch
> - Cassandra
> - JPA postgrey
> - Spring specific configuration
> - mailbox
> - events
> - quota
> - Guice specific configuration
> - listeners
> - How to...
> - Anti-Spam
> {code}
> We are also missing config about... Tika, WebAdmin, JMAP, JMX, indexer...
> This new organisation will allow adding them in the corresponding sections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3236) Clarify SMTP Configuration (smtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140148#comment-17140148 ] Benoit Tellier commented on JAMES-3236: --- My comment long term proposition relates to JAMES-2335 > Clarify SMTP Configuration (smtpserver.xml) > --- > > Key: JAMES-3236 > URL: https://issues.apache.org/jira/browse/JAMES-3236 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3229) Clarify IMAP Configuration (imapserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140149#comment-17140149 ] Benoit Tellier commented on JAMES-3229: --- My comment long term proposition relates to JAMES-2335 > Clarify IMAP Configuration (imapserver.xml) > --- > > Key: JAMES-3229 > URL: https://issues.apache.org/jira/browse/JAMES-3229 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3231) Clarify LMTP Configuration (lmtpserver.xml)
[ https://issues.apache.org/jira/browse/JAMES-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140178#comment-17140178 ] Benoit Tellier commented on JAMES-3231: --- I propose that we don't put the configuration file but if the operator specifies it we would take it into account. > Clarify LMTP Configuration (lmtpserver.xml) > --- > > Key: JAMES-3231 > URL: https://issues.apache.org/jira/browse/JAMES-3231 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > In the context of the *Basic Server*, determine if (1) this configuration is > necessary, and if so (2) how can we minimize it and (3) document it better. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3248) Eliminate log warnings
[ https://issues.apache.org/jira/browse/JAMES-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140179#comment-17140179 ] Benoit Tellier commented on JAMES-3248: --- I deally, we should be able to create a separate application for the BasicSearch and overload guice injections for these configurations, in order to remove that warning log. I propose it as a middle term solution. > Eliminate log warnings > -- > > Key: JAMES-3248 > URL: https://issues.apache.org/jira/browse/JAMES-3248 > Project: James Server > Issue Type: Sub-task >Reporter: David Leangen >Priority: Major > > Warnings generated in the logs should be ideally completely eliminated, as it > creates anxiety for the Basic Operator and is bad for mental health. ;) > I will post the warnings here one by one so we can figure out how to deal > with each of them (simple resolution, or something that requires a separate > issue). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3214) Remove test only libraries from being pulled as transitive dependencies of production artifacts
[
https://issues.apache.org/jira/browse/JAMES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140195#comment-17140195
]
Benoit Tellier commented on JAMES-3214:
---
https://github.com/apache/james-project/pull/210 solved it.
Given that test dependencies are no longer present in released artifacts,
should we consider this done?
> Remove test only libraries from being pulled as transitive dependencies of
> production artifacts
> ---
>
> Key: JAMES-3214
> URL: https://issues.apache.org/jira/browse/JAMES-3214
> Project: James Server
> Issue Type: Improvement
>Reporter: Ioan Eugen Stan
>Assignee: Ioan Eugen Stan
>Priority: Major
> Attachments: runtimeClasspath.txt
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> assertj-core , equalsverifier, rest-assured (and maybe other libraries)
> belong to testing (probably more). And they leaked to our "production" builds
> which depends on just 2 jars from James:
> implementation "org.apache.james:james-server-jpa-guice:${jamesVersion}"
> implementation "org.apache.james:james-server-cli:${jamesVersion}"
> == Context
> I'm working with David @dleangen on the self hosting with Apache James. We
> built a sandbox to play around and experiment:
> https://github.com/ieugen/james-self-hosting-sandbox .
> Current setup is to use gradle + application plugin to build a custom
> distribution.
> We build a zip distribution that pulls in all the dependencies including the
> offending ones used in testing.
> The distribution has 137MB unpacked. files just James, without the JRE.
> On initial inspection it seems there are test only dependencies that are
> being pulled as transitive dependencies of the 2 dependencies:
> Bellow is a list of top most large dependencies with ls -lSh
> james-self-hosting-sandbox/lib | head -n 40
> total 132M
> -rw-r--r-- 1 ieugen ieugen 13M iun 12 13:19 icu4j-64.2.jar
> -rw-r--r-- 1 ieugen ieugen 12M iun 12 13:19 testcontainers-1.12.0.jar
> -rw-r--r-- 1 ieugen ieugen 5,5M iun 12 13:19 scala-library-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 5,3M iun 12 13:19 groovy-2.5.6.jar
> -rw-r--r-- 1 ieugen ieugen 5,0M iun 12 13:19 camel-core-2.24.1.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 openjpa-3.1.0.jar
> -rw-r--r-- 1 ieugen ieugen 4,4M iun 12 13:19 bcprov-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 4,2M iun 12 13:19 assertj-core-3.12.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,7M iun 12 13:19 jaxb-osgi-2.2.10.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 scala-reflect-2.13.1.jar
> -rw-r--r-- 1 ieugen ieugen 3,5M iun 12 13:19 lucene-smartcn-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 3,2M iun 12 13:19 shapeless_2.13-2.3.3.jar
> -rw-r--r-- 1 ieugen ieugen 3,1M mai 3 05:45 derby-10.14.2.0.jar
> -rw-r--r-- 1 ieugen ieugen 2,8M iun 12 13:19 equalsverifier-3.1.9.jar
> -rw-r--r-- 1 ieugen ieugen 2,7M iun 12 13:19 guava-28.1-jre.jar
> -rw-r--r-- 1 ieugen ieugen 2,6M iun 12 13:19 jna-platform-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 2,4M iun 12 13:19 jgroups-3.6.13.Final.jar
> -rw-r--r-- 1 ieugen ieugen 2,2M feb 17 21:24 commons-math3-3.6.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 lucene-core-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 reactor-core-3.3.0.RELEASE.jar
> -rw-r--r-- 1 ieugen ieugen 1,5M iun 12 13:19 jna-5.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 activemq-client-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 jackson-databind-2.10.1.jar
> -rw-r--r-- 1 ieugen ieugen 1,4M iun 12 13:19 httpclient-osgi-4.5.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,3M iun 12 13:19 netty-3.10.6.Final.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 activemq-broker-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 1,2M iun 12 13:19 lucene-analyzers-3.6.2.jar
> -rw-r--r-- 1 ieugen ieugen 1,1M iun 12 13:19 jaxb-impl-2.3.1.jar
> -rw-r--r-- 1 ieugen ieugen 851K iun 12 13:19 bcpkix-jdk15on-1.62.jar
> -rw-r--r-- 1 ieugen ieugen 827K iun 12 13:19 guice-4.2.2.jar
> -rw-r--r-- 1 ieugen ieugen 757K iun 12 13:19 httpclient-4.5.10.jar
> -rw-r--r-- 1 ieugen ieugen 737K iun 12 13:19 commons-collections4-4.3.jar
> -rw-r--r-- 1 ieugen ieugen 732K iun 12 13:19 play-json_2.13-2.8.1.jar
> -rw-r--r-- 1 ieugen ieugen 718K iun 12 13:19 javassist-3.21.0-GA.jar
> -rw-r--r-- 1 ieugen ieugen 715K iun 12 13:19 artemis-core-client-2.9.0.jar
> -rw-r--r-- 1 ieugen ieugen 687K iun 12 13:19 rest-assured-4.0.0.jar
> -rw-r--r-- 1 ieugen ieugen 670K iun 12 13:19
> activemq-openwire-legacy-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 663K iun 12 13:19 activemq-kahadb-store-5.15.9.jar
> -rw-r--r-- 1 ieugen ieugen 644K mai 3 05:45 javax.mail-1.6.2.jar
> I believe this is quite big.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
[jira] [Commented] (JAMES-3184) Concurrency for consistency tasks
[ https://issues.apache.org/jira/browse/JAMES-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140196#comment-17140196 ] Benoit Tellier commented on JAMES-3184: --- https://github.com/linagora/james-project/pull/3449 limited the concurrency before throttling to generate the entries to reindex. > Concurrency for consistency tasks > - > > Key: JAMES-3184 > URL: https://issues.apache.org/jira/browse/JAMES-3184 > Project: James Server > Issue Type: Improvement >Reporter: Lan Khuat >Priority: Major > Fix For: 3.6.0 > > > We currently limit concurrency of consistency tasks to 1 in order to avoid > unbounded concurrency. > When running a consistency task, an admin should be able to precise the > concurrency he wishes to use. > To do so, each task will expose (optional) concurrency parameters, that an > admin can provide via query parameters of the corresponding webadmin > endpoints. > * RecomputeUserFastViewProjectionItems > * RecomputeCurrentQuotas > * RecomputeMailboxCounters > * SolveMailboxInconsistencies > * SolveMessageInconsistencies > * FullReindexing > * UserReindexing > * SingleMailboxReindexing > * ErrorRecoveryReindexation -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3210) Handle Return-Path header in DSNBounce mailet
[ https://issues.apache.org/jira/browse/JAMES-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140197#comment-17140197 ] Benoit Tellier commented on JAMES-3210: --- https://github.com/linagora/james-project/pull/3446 JAMES-3210 add integration tests to verify that the bounce is sent to the sender & https://github.com/linagora/james-project/pull/3441 [Refactoring] Refactor BounceIntegrationTest Are merged. > Handle Return-Path header in DSNBounce mailet > - > > Key: JAMES-3210 > URL: https://issues.apache.org/jira/browse/JAMES-3210 > Project: James Server > Issue Type: Bug > Components: Matchers/Mailets (bundled) >Affects Versions: 3.5.0 >Reporter: Rémi Kowalski >Priority: Major > > ``` > At the origin of the complain: > ``` > This message was created automatically by mail delivery software. > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > 0102016ca8bd7b6d-b28772f6-6c71-4676-8834-c48740efb2a8-000...@eu-west-1.amazonses.com > (generated from > SRS0=78Gj=WP=eu-west-1.amazonses.com=0102016ca8bd7b6d-b28772f6-6c71-4676-8834-c48740efb2a8-000...@ik2.com) > host feedback-smtp.eu-west-1.amazonses.com [54.239.37.176] > SMTP error from remote mail server after end of data: > 554 DSN is not RFC 3464 compliant. MSGID: (FleYRCEogpaDtH6q8Ml2-1): > The DSN MUST be addressed (in both the message header and the transport > envelope) to the return address from the transport envelope which accompanied > the original message for which the DSN was generated. > https://tools.ietf.org/html/rfc3464 > ``` > DOD: > handle the Return-Path header in the DSNBounce mailet and add an integration > test -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
