Re: Call for vote: Apache James 0.8.11

+1, Rene. On 3/5/24 23:20, Karsten Otto wrote: +1 I looked at how this change affects the parser, and played a bit with the test. LGTM. Cheers, Karsten OTTO On 05.03.24 4:42 PM, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 0.8.11 release of the Apache James MIME4J

Re: Build metrics

. over time we will be able to target master only to get a better view of what's going on jean Le jeu. 22 févr. 2024 à 04:12, Rene Cordier a écrit : Hi Jean, Thanks for the heads up on your work on this, very interesting. Regarding the test failures, to add a bit more insight

Re: vote : Remote build cache experiment

+1, If there is a chance to make our builds faster, I say we take it! Thanks for this work :) Rene. On 2/20/24 15:18, Jean Helou wrote: Hello devs ! I have not yet moved forward with enabling remote caching for the build and tests in general. It is unclear to me if you are ok with trying

Re: Call for vote: Apache James MIME4J 0.8.10

+1, Rene. On 2/12/24 17:38, Benoit TELLIER wrote: Typo The maven release staged in repository.apache.org as the artifact #1081: https://repository.apache.org/content/repositories/orgapachejames-1081/ On 12/02/2024 11:35, Benoit TELLIER wrote: Hi, I would like to propose a new vote for

Re: Call for vote: Apache James 3.7.5

+1, Rene. On 2/12/24 17:37, Benoit TELLIER wrote: Hi, Taking into account the feedback of this very list, I would like to propose a new vote for 3.7.5 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1079:

Re: Call for vote: Apache James 3.8.1

+1, Rene. On 2/12/24 18:43, Karsten Otto wrote: +1 Looks good to me. Cheers, Karsten OTTO On 12.02.24 11:46 AM, Benoit TELLIER wrote: Hi, Following the feedback of this very list, I would like to propose a new vote for 3.8.1 release of the Apache James server. You can find:   - The

Re: Develocity

I agree caching the test suite is very tempting, it would help gain so much time on the build. But yes the test suite is flaky unfortunately. Maybe we need extra work making it more stable first, but that's not easy task ^^' Or maybe for remote caching on test execution, maybe we can try

Re: Vote to merge the Java 21 adoption for Apache James PR

+1, Thanks for the efforts on this work :) Rene. On 2/6/24 10:36, Quan tran hong wrote: Hi everyone, Following the Jira ticket and the previous mailing list discussion

Re: Call for vote: Apache James 3.8.1

Hi jean, FYI Karsten already proposed fixes for that issue that have been approved and will be part of the releases. It's just a matter now of getting a green build from a rather a bit capricious CI^^' Regards, Rene. On 1/11/24 15:09, Jean Helou wrote: Much clearer thank you ! What do you

Re: Call for vote: Apache James 3.8.1

+1, Rene. On 1/9/24 15:17, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 3.8.1 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1077:

Re: Call for vote: Apache James 3.7.5

+1, Rene. On 1/9/24 15:15, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 3.7.5 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1079:

Re: Call for vote: Apache James MIME4J 0.8.10

+1, Cheers, Rene. On 1/8/24 21:36, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 0.8.10 release of the Apache MIME4J library. You can find:  - The maven release staged in repository.apache.org as the artifact #1076:

Event dead letter group deserialization too strict?

Hello guys, Today I noticed on one of our servers that the redelivery of all event dead letters task was failing. The problem being... too strict on event dead letter group deserialization. The problem I had was that after a migration, I had some groups still registered in group_table that

Re: Proposal about deprecation and removal

Hi Matthieu, I think some people in the community are probably using the Spring version because the official documentation was never really clear about our intentions of potentially deprecating and removing this part. I'm totally for deprecating and removing that part, and I'm very happy

Re: Deprecate and remove JMAP draft implementation

About time :) +1 Rene. On 11/16/23 19:51, Benoit TELLIER wrote: Hello there, I wanted to quickly discussed the deprecation and removal of the JMAP draft implementation. Please raise a voice if this impacts you... ## Why  -> This protocol do no longer match standard specification  ->

Re: Call for vote: Apache James 3.8.0

+1, Rene. On 19/05/2023 09:23, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 3.8.0 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1074:

Re: Call for vote: Apache James 3.7.4

+1 Rene. On 24/03/2023 00:21, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 3.7.4 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1073:

Antora build mis-fonctionning

Hi James community, Recently some people took notice that the Antora documentation hosted on https://james.staged.apache.org/james-site/latest/homepage.html is not always showing. We suspect it's because if the build on the CI fails for some reason, then deployment maybe doesn't go to the

Re: Fwd: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira)

+1, Rene. On 10/11/2022 12:01, Benoit TELLIER wrote: Hello all See the email bellow. This email:  - Warns us that SIGNIFICANT paper work would be needed to create accounts on our JIRA  - Recommends us to activate GitHub issues for user facing interactions (bug reports, feature requests,

Re: Call for vote: Apache James 3.7.2

+1, Rene. On 07/10/2022 14:26, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 3.7.2 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1066:

Re: Call for vote: Apache James JDKIM 0.3

+1, Rene. On 02/10/2022 16:06, Benoit TELLIER wrote: Hi, I would like to propose a new vote for 0.3 release of the Apache James JDKIM library. You can find the maven release staged in repository.apache.org as the artifact #1065:

Re: Call for vote: Apache James 3.7.1

+1, Rene. On 26/08/2022 18:12, Benoit TELLIER wrote: |Hi, I would like to propose a new vote for 3.7.1 release of the Apache James server. You can find: - The maven release staged in repository.apache.org as the artifact #1064:

Re: new committer: Jean Helou

Congrats Jean :) Rene. On 24/06/2022 08:51, Benoit TELLIER wrote: |The Project Management Committee (PMC) for Apache James has invited Jean Helou to become a committer and we are pleased to announce that they have accepted. Jean started to contribute many years ago, starting with the first

Re: Upgrade regarding ElasticSearch

Hi, Overall no problem, maybe I wasn't clear enough on my initial mail, or it was too long to ingest. But it seems we are all on the same page now so all good :) Regards, Rene. On 17/06/2022 14:07, Matthieu Baechler wrote: Hi, On Fri, 2022-06-17 at 10:19 +0700, Rene Cordier wrote

Re: Upgrade regarding ElasticSearch

Hi Matthieu, thanks for joining the discussion. Answers inline... On 17/06/2022 03:28, Matthieu Baechler wrote: Hi René, Thank you for starting this thread. On Wed, 2022-06-15 at 16:37 +0700, Rene Cordier wrote: Hello James community! I would like to start a discussion regarding

Upgrade regarding ElasticSearch

Hello James community! I would like to start a discussion regarding the upgrade of ElasticSearch, hoping we can reach a consensus, as I spent quite a lot of time on this already. As you know, the version 7.10 has reached EOL already, so we need to migrate from it. Thus a while ago I

Re: ElasticSearch upgrade to 8.2

Hello Jean, Thanks for expressing your concern. I reverted the removal of the metrics es reporter. But beware that it hasn't been migrated in the works of the 8.2 migration. First of all when looking at the code it's obvious it hasn't even been migrated when passing to ES7. If it's not

Re: ElasticSearch upgrade to 8.2

/a file and move it to your analytic stack Regards, Benoit On 09/06/2022 11:02, Rene Cordier wrote: Hello guys, As working on the upgrade to ElasticSearch 8.2, I've been wondering if it was still worth it to keep the elasticsearch metrics reporter module. Since we expose a metrics endpoint

ElasticSearch upgrade to 8.2

Hello guys, As working on the upgrade to ElasticSearch 8.2, I've been wondering if it was still worth it to keep the elasticsearch metrics reporter module. Since we expose a metrics endpoint that tools like prometheus can just call to scrap metrics out of James, I think the es metrics

Re: Upcoming "polish" contributions (June-July 2022)

Hello, Just to quickly come back to the ElasticSearch upgrade to 8.2 as I started taking a look. It seems we gonna need to migrate the api client used in our code as the version 8 comes with an entirely new client library:

Re: Call for vote: Apache James MIME4J 0.8.7

+1, Rene. On 01/04/2022 12:04, Benoit TELLIER wrote: |Subject: Hi, I would like to propose a new vote for 0.8.7 release of the Apache James MIME4J library. You can find: - The maven release staged in repository.apache.org as the artifact #1063:

Re: [VOTE] Apache James release 3.7.0

+1, Rene. On 02/03/2022 10:44, Tellier Benoit wrote: Hi, I would like to propose a new vote for 3.7.0 release of the Apache James server. You can find: - The maven release staged in repository.apache.org as the artifact #1062:

Re: [VOTE] Apache James release 3.6.2

+1, Rene. On 27/01/2022 14:08, Benoit TELLIER wrote: Hello, Sorry for the bad formatting. I would like to propose a new vote for 3.6.2 release of the Apache James server. You can find: - The maven release staged in repository.apache.org as the artifact #1061:

Re: About windows support...

Hi, Are the complaints really from people that want to run it on windows server for production, or more like people downloading the project on their windows computer and trying to run it locally to check it out? I thought was mainly the latest (but I might be wrong?) so I think adapting our

Re: New feature: Email rate limiting

+1, Rene. On 10/01/2022 16:22, Tung Tran Van wrote: Hello community! Linagora-email-team proposes the email rate-limit feature to James. Rate limiting is one of the common features. Examples: SaaS is one

Re: About further adoption of Apache Pulsar to back the distributed server messaging use case.

+1, Rene. On 07/01/2022 18:24, Benoit TELLIER wrote: Hello all, Thanks to the very nice work of Matthieu and Jean we now have a working Pulsar implementation for the James Mail Queue component [1]. Koodo! [1] https://github.com/apache/james-project/pull/808 I did put together an ADR [2]

Re: new committer: Karsten OTTO

Congratulations and welcome Karsten :) Rene. On 08/01/2022 11:44, Benoit TELLIER wrote: |The Project Management Committee (PMC) for Apache James has invited Karsten OTTO to become a committer and we are pleased to announce that he has accepted. Karsten have opened several bug reports and

Re: [IMPORTANT] Call for vote: Apache James 3.6.1 (3rd edition...)

+1, Rene. On 16/12/2021 14:27, btell...@apache.org wrote: Hi, I would like to propose a new vote for 3.6.1 release of the Apache James server. This time, as discussed on the JIRA this includes upgrade to Log4J 2.16.0. You can find:  - The maven release staged in repository.apache.org as

Re: Call for vote: Apache James 3.6.1

+1, Rene. On 03/12/2021 08:29, btell...@apache.org wrote: Hi, I would like to propose a new vote for 3.6.1 release of the Apache James server. You can find:  - The maven release staged in repository.apache.org as the artifact #1056:

Re: Authentication in James: Enable/require/disable OpenID for JMAP, IMAP and SMTP

+1, Rene. On 02/12/2021 11:56, btell...@linagora.com wrote: Hopefully rendered correctly in plain text... - Hello Jamers! As part of my work at Linagora, we are looking toward  - better integrating James within our product suite and for us this means

Re: Webadmin: retire Swagger documentation?

+1, Regards, Rene. On 07/10/2021 09:48, btell...@apache.org wrote: Agree, in my opinion the long term place is the Antora documentation. We might have to live with Antora <-> Markdown (old website) duplication for a while longer, until we fully adopt Antora website documentation. Regards,

Re: [VOTE] Deprecate maildir in 3.6.1, removal as part of 3.7.x

+1, Rene. On 19/09/2021 11:30, btell...@apache.org wrote: Hello all, In order to prepare for the 3.6.1 release I did open this fix, https://github.com/apache/james-project/pull/659 ensuring files used by the maildir implementation are sanitized, which I considered being a blocker. However, I

Re: Call for vote: Apache JAMES MIME4J

+1, Rene. On 17/09/2021 17:59, btell...@apache.org wrote: |Subject: Hi, I would like to propose a new vote for 0.8.6 release of the Apache MIME4J library. You can find: - The maven release staged in repository.apache.org as the artifact #1055:

Re: Retiring the File mail queue from James 3.7.x

Hello, Sounds legit to me, +1! Thanks for looking into that deeply. Rene. On 05/09/2021 20:03, btell...@apache.org wrote: Hello there, While working on JAMES-3646 incorrect file validation, I came to discover the file mail queue incorrectly sanitizes file paths. This is one of the many

Re: Time to retire maildir from James 3.7.X ?

Hello, I think you are making good points. It's probably better to focus on what works well if it's enough of an alternative to maildir (like embedded JPA as you mentionned), with little resources we have. +1 ! Rene. On 05/09/2021 19:58, btell...@apache.org wrote: Hello all, While

Re: The road to a (POP3) multi-dc friendly distributed email server

Hello, Nice POC thanks! +1 to have the contribution back to the community project. Cheers, Rene. On 03/08/2021 11:11, btell...@apache.org wrote: Hello all, For some of my customers, we did develop a multi-datacenter friendly POP3 server as a derivate of James distributed server. It fully

Re: End of support for Apache James 2.3.2 ?

Hello, I can understand some people are still running this version of James, it's never easy to migrate from a major version to an other. But community support... Even if the decision has not been taken officially (thus the discussion happening right now), do we still have that honestly? I

Re: [VOTE] Retire Apache James Postage

+1, Rene. On 23/07/2021 16:03, btell...@apache.org wrote: Hello all, Following a first email on the topic [1] I would like to call for a formal vote on Apache James Postage retirement. [1] https://www.mail-archive.com/server-dev@james.apache.org/msg70576.html Rationnals: this project...  -

Re: [VOTE] Retire Apache James HUPA

+1, Rene. On 23/07/2021 16:00, btell...@apache.org wrote: Hello all, Following a first email on the topic [1] I would like to call for a formal vote on Apache James Hupa retirement. [1] https://www.mail-archive.com/server-dev@james.apache.org/msg70575.html Rationnals:  - The latest release

Re: Retire Apache James Postage ?

Nice catch, +1! Rene. On 19/07/2021 15:33, Jean Helou wrote: Hi benoit While looking at unmaintained pieces of code that might have now better alternatives, being hosted under the Apache James umbrella, I cannot but think about Apache Postage. Given the maturity of the project, the presence

Re: Retire Apache James Hupa ?

Nice catch, +1! Rene. On 19/07/2021 15:30, Jean Helou wrote: I think this is an excellent idea ! +1 thank you benoit ! jean On Mon, Jul 19, 2021 at 10:16 AM btell...@apache.org wrote: Hello all, While fixing our download pages following some infra bot complains, I ended up fixing the

Re: Call for vote: Apache MIME4J 0.8.5

+1 :) Cheers, Rene. On 01/07/2021 14:51, btell...@apache.org wrote: |Hi, I would like to propose a new vote for 0.8.5 release of the Apache MIME4J library. You can find: - The maven release staged in repository.apache.org as the artifact #1054:

Re: Removal of stale branches for apache/james projects

+1 Rene. On 02/06/2021 14:54, btell...@apache.org wrote: Hello all, While having a look at branches built by the ASF CI when switching the tokens I noticed we have many stale, meaningless branches on some of our repositories. This includes:  -

Re: Major bug: Camel mailet container and partial matches.

Hi Benoit, Thanks for raising this concern it's rather interesting, despite my limited knowledge on Camel processing and MailetContainer execution. I think if we can come up with a robust Java implementation allowing to discard yet an other dependency (Camel) from James, that would be a win

Re: Actively warn against Cassandra Blob Store usage.

+1 Sure we probably need to keep it as some people will always have a use for it somehow at the end, but a good warning explaining why should be in place. Rene. On 22/05/2021 14:57, btell...@apache.org wrote: Hello there, As I did state it in

Re: SMTP server configuration issue

for raising the topic here. Le 05/05/2021 à 16:31, Rene Cordier a écrit : Hello guys, [...] 1. If authRequired is set to false, we should reject verifyIdenty=true, as it makes no logical sense. People might need to update their James running installation though (but easy) By far my prefered option

SMTP server configuration issue

Hello guys, While running some performance tests against SMTP protocol, I crossed what I believe being potentially an issue regarding the configuration of SMTP in James through the smtpserver.xml file. What I observed is that we have two params that, according to the official doc, are supposed

Re: [VOTE] Call for vote: Apache James 3.6.0 (round 3)

+1 Rene. On 06/04/2021 14:04, Tellier Benoit wrote: I would like to propose a new vote 3.6.0 release of the Apache James server. After an initial mistake (sorry), a failed vote (could not achieve a PMC quorum), and more issues I did not yet complain about (closing the maven artifact #1051

Re: [Discussion] Road to 4.0

Hi again David, On 28/08/2020 10:11, David Leangen wrote: Perhaps we should just wait in case anybody else would also like to add something? So I would describe James as: * Currently in a state of transition (this is what James is now) * What we aspire it to be for version xxx (I am

Re: [Discussion] Road to 4.0

Hi David, On 27/08/2020 10:21, David Leangen wrote: I have observed a few different types of approaches to OSS: * Centered on a specification. The spec development has a formal process, and the spec becomes the driving force. There is a “reference implementation” to show that the spec

Re: [Discussion] Road to 4.0

Hello David, On 26/08/2020 18:10, David Leangen wrote: Hello, I am still trying to get a sense of the community’s vision, and it’s thoughts relating to how to treat users. Unfortunately I have not heard too many comments so far on this topic. Trying to read between the lines, I could think

Re: Which repositories are we using and going to document? Let's retire the ones we don't

On 20/08/2020 11:23, Rene Cordier wrote: Based on Eugen comments in the INFRA ticket, I did this: https://github.com/apache/james-project/pull/244 for redirecting notifications to the new ML for this. However I don't think as a commiter I can create the ML, so if a PMC could manage

Re: Which repositories are we using and going to document? Let's retire the ones we don't

On 19/08/2020 17:49, Eugen Stan wrote: I've created an issue to make the ML changes: https://issues.apache.org/jira/browse/INFRA-20735 -- Please add: - notificati...@james.apache.org Please remove: - site-...@james.apache.org - mailet-...@james.apache.org Based on Eugen comments in the

Re: Which repositories are we using and going to document? Let's retire the ones we don't

I think we should have separate channels for: - development: how we implement features and what features we work on - users: how to use James:deploy it, create back-ups, etc. Those 2 mailing lists exist already I believe. We have `server-dev` for development related things and `server-user`

Re: Which repositories are we using and going to document? Let's retire the ones we don't

Hello, There are things that need to me documented that are not technical: - what / where are the project resources (website, CI, git repos, mailing list) - how to contribute, engage with the community - etc. Just to say I started migrating and writing this part of the documentation here:

Re: Call for vote: Apache James 3.5.0

+1 Rene. On 16/07/2020 13:44, Tellier Benoit wrote: Hi, I would like to propose a new vote 3.5.0 release of the Apache James server. I fixes Matthieu remarks since last proposal. You can see changes proposed to the website at the occasion of that release on this GitHub pull request:

Re: Consensus needed: replace james-site master branch with live branh - reset

+1! I don't see any issues with it too. Thank you Eugen ! Rene. On 13/07/2020 07:10, Tellier Benoit wrote: Le 13/07/2020 à 03:29, Eugen Stan a écrit : Hello, I would like to use james-site#master branch to hold the code to build the website automatically. +1 If no objections are received

Re: Call for vote: Apache James 3.5.0

+1 Rene. On 19/06/2020 10:44, Tellier Benoit wrote: Hi, I would like to propose the 3.5.0 release of the Apache James server. Here are the changes since the previous proposal: ``` JAMES-3197 Matcher processing should handle NoClassDefFoundError f0c6576760 JAMES-3197 Mailet processing should

Re: Call for vote: Apache James 3.5.0

+1 On 06/04/2020 18:07, Tellier Benoit wrote: Hi, I would like to propose the 3.5.0 release of the Apache James server. You can see changes proposed to the website at the occasion of that release on this GitHub pull request: https://github.com/apache/james-project/pull/187 You can find: -

Development directions for the coming weeks

objects and that we need to think in the future of a more systematic approach to address this problem. If you have any comments or feedbacks to this, please don't hesitate to answer us. Best regards, Rene Cordier

Re: Session refactoring discussion

Hi Benoit, Thank you for your feedback. Answers are inline as well but overall it looks good feedback to me. Best regards, Rene. On 22/01/2020 12:10, Tellier Benoit wrote: Hi René, My answers are inlined... Best regard, Benoit On 22/01/2020 10:21, Rene Cordier wrote: Hi guys, I would

Session refactoring discussion

Hi guys, I would like to bring on the table some proposition to refactor our session usage within James. # Context The problem starts from https://issues.apache.org/jira/browse/JAMES-2993, more particularly the API `POST /jmap/messages/:messageId?action=recomputeJmapPreview` to recompute

Re: [Call for vote] Upcoming 3.5.0 Deprecation plan

+1, Rene Cordier. On 18/11/2019 16:22, Tellier Benoit wrote: Hello everyone, I propose to submit to a vote the following deprecation:  - To be deprecated in upcoming 3.5.0 and removed in 3.6.0:     - james-server-mailet BayesianAnalysis + BayesianAnalysisFeeder + JDBCBayesianAnalyser

Re: Complete Code Contribution Lifecycle?

Hi Jerry! Is this enough to answer your concerns regarding the code contribution documentation? https://james.apache.org/contribute.html Feel free of course to give your feedback on it, if you think some points are missing or unclear. Cheers, Rene Cordier. On 05/11/2019 23:12, Jerry

Re: Trouble building the latest master.

"-DskipTests". It will skip the test phase. I think the README at the base of the github project is better up-to-date for project's compilation. Regards, Rene Cordier. On 26/10/2019 09:14, Mark Gordon wrote: I got past the previous problem by commenting out the release line on the fol

Re: [Vote] migration to java 11

+1 On 24/10/2019 21:43, Matthieu Baechler wrote: Hi, I would like to propose the migration to Java 11 as a runtime. I opened an ADR here: https://github.com/apache/james-project/pull/174 Here is the content of this ADR: --- #

[jira] [Commented] (JAMES-2241) Headers containing dot character are not indexed in ElasticSearch

[ https://issues.apache.org/jira/browse/JAMES-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939193#comment-16939193 ] Rene Cordier commented on JAMES-2241: - It seems that from ES5 it's possible again to index field

[jira] [Commented] (JSIEVE-112) Use SLF4J & logback for logging

[ https://issues.apache.org/jira/browse/JSIEVE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930198#comment-16930198 ] Rene Cordier commented on JSIEVE-112: - PR was : https://github.com/apache/james-jsieve/pull/18 >

[jira] [Commented] (JSIEVE-111) Libraries upgrade

[ https://issues.apache.org/jira/browse/JSIEVE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926328#comment-16926328 ] Rene Cordier commented on JSIEVE-111: - PR: https://github.com/apache/james-jsieve/pull/17

[jira] [Created] (JSIEVE-111) Libraries upgrade

Rene Cordier created JSIEVE-111: --- Summary: Libraries upgrade Key: JSIEVE-111 URL: https://issues.apache.org/jira/browse/JSIEVE-111 Project: James jSieve Issue Type: Wish Reporter

[jira] [Commented] (JDKIM-43) Libraries upgrade

[ https://issues.apache.org/jira/browse/JDKIM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922350#comment-16922350 ] Rene Cordier commented on JDKIM-43: --- PR for upgrades : [https://github.com/apache/james-jdkim/pull/9

[jira] [Created] (JDKIM-43) Libraries upgrade

Rene Cordier created JDKIM-43: - Summary: Libraries upgrade Key: JDKIM-43 URL: https://issues.apache.org/jira/browse/JDKIM-43 Project: James jDKIM Issue Type: Wish Reporter: Rene

[jira] [Commented] (JAMES-2868) Http route for getting all mails stored in the MockSmtpServer

[ https://issues.apache.org/jira/browse/JAMES-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919141#comment-16919141 ] Rene Cordier commented on JAMES-2868: - PR solving this matter: https://github.com/linagora/james

[jira] [Commented] (JAMES-2867) dockerize the MockSmtpServer

[ https://issues.apache.org/jira/browse/JAMES-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916329#comment-16916329 ] Rene Cordier commented on JAMES-2867: - PR with dockerized dummy Mock smtp server : https

[jira] [Commented] (JAMES-2872) Broken links for JAMES 3.3.0 release source code

[ https://issues.apache.org/jira/browse/JAMES-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914036#comment-16914036 ] Rene Cordier commented on JAMES-2872: - Found out that the docker image used to compile the website

[jira] [Created] (JAMES-2872) Broken links for JAMES 3.3.0 release source code

Rene Cordier created JAMES-2872: --- Summary: Broken links for JAMES 3.3.0 release source code Key: JAMES-2872 URL: https://issues.apache.org/jira/browse/JAMES-2872 Project: James Server Issue

[jira] [Commented] (JAMES-2860) Read partial blob issue with Scality

[ https://issues.apache.org/jira/browse/JAMES-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911141#comment-16911141 ] Rene Cordier commented on JAMES-2860: - Unfortunately, the issue still occurs with our integration

[jira] [Commented] (JAMES-2860) Read partial blob issue with Scality

[ https://issues.apache.org/jira/browse/JAMES-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911139#comment-16911139 ] Rene Cordier commented on JAMES-2860: - PR to upgrade to cloudserver 8.1.17 : https://github.com

[jira] [Updated] (JAMES-2860) Read partial blob issue with Scality

[ https://issues.apache.org/jira/browse/JAMES-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene Cordier updated JAMES-2860: Description: For some reasons, the test readShouldNotReadPartiallyWhenDeletingConcurrentlyBigBlob

[jira] [Created] (JAMES-2860) Read partial blob issue with Scality

Rene Cordier created JAMES-2860: --- Summary: Read partial blob issue with Scality Key: JAMES-2860 URL: https://issues.apache.org/jira/browse/JAMES-2860 Project: James Server Issue Type: Bug

[jira] [Updated] (JAMES-2859) Missing pages on the documentation's website

[ https://issues.apache.org/jira/browse/JAMES-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene Cordier updated JAMES-2859: Labels: documentation newbie website (was: docuentation newbie website) > Missing pa

[jira] [Created] (JAMES-2859) Missing pages on the documentation's website

Rene Cordier created JAMES-2859: --- Summary: Missing pages on the documentation's website Key: JAMES-2859 URL: https://issues.apache.org/jira/browse/JAMES-2859 Project: James Server Issue Type

[jira] [Commented] (JAMES-2858) Fix plugin cannot found issue maven-mailetdocs-plugin

[ https://issues.apache.org/jira/browse/JAMES-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908803#comment-16908803 ] Rene Cordier commented on JAMES-2858: - PR: https://github.com/linagora/james-project/pull/2599 >

[jira] [Created] (JAMES-2858) Fix plugin cannot found issue maven-mailetdocs-plugin

Rene Cordier created JAMES-2858: --- Summary: Fix plugin cannot found issue maven-mailetdocs-plugin Key: JAMES-2858 URL: https://issues.apache.org/jira/browse/JAMES-2858 Project: James Server

[jira] [Closed] (JAMES-2829) Implementation of delete in BlobStore

[ https://issues.apache.org/jira/browse/JAMES-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene Cordier closed JAMES-2829. --- > Implementation of delete in BlobStore > - > >

[jira] [Resolved] (JAMES-2829) Implementation of delete in BlobStore

[ https://issues.apache.org/jira/browse/JAMES-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene Cordier resolved JAMES-2829. - Resolution: Done Both merged. > Implementation of delete in BlobSt

[jira] [Commented] (JAMES-2837) [New Vault] MetricableBlobStore missing grafana boards

[ https://issues.apache.org/jira/browse/JAMES-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891590#comment-16891590 ] Rene Cordier commented on JAMES-2837: - PR with metrics for delete and deleteBucket on BlobStore

[jira] [Commented] (JAMES-2829) Implementation of delete in BlobStore

[ https://issues.apache.org/jira/browse/JAMES-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885835#comment-16885835 ] Rene Cordier commented on JAMES-2829: - Second PR with object storage impl : https://github.com

[jira] [Commented] (JAMES-2829) Implementation of delete in BlobStore

[ https://issues.apache.org/jira/browse/JAMES-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885082#comment-16885082 ] Rene Cordier commented on JAMES-2829: - First PR with memory impl and contract update : https

[jira] [Created] (JAMES-2829) Implementation of delete in BlobStore

Rene Cordier created JAMES-2829: --- Summary: Implementation of delete in BlobStore Key: JAMES-2829 URL: https://issues.apache.org/jira/browse/JAMES-2829 Project: James Server Issue Type: New

  1   2   3   >