Re: Call for vote: Apache JAMES MIME4J

+1 Could you update the copyright dates in the NOTICE file for next time please? Le ven. 17 sept. 2021 à 13:25, Vincenzo Gianferrari Pini < vincenzo.gianferrarip...@gocloud.it> a écrit : > +1 > > Vincenzo > > > > > > > Il Ven 17 Set 2021, 13:01 btell...@apache.org ha > scritto: > > > +1 > > >

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

+1 Le 06/09/2021 à 14:54, Jean Helou a écrit : awesome :) On Mon, Sep 6, 2021 at 1:52 PM btell...@apache.org wrote: Hello Jean, On 06/09/2021 18:42, Jean Helou wrote: Hello benoit, There are some alternatives: embedded activeMQ has zero dependencies. Furthermore migrating is easy: just

Re: About James .jks keystore for SSL/TLS

Hello, Le 27/08/2021 à 06:37, Duc Nguyen a écrit : Conclusion: With Kubernetes and containers have become virtually synonymous with cloud-native development, Apache James needs to adapt quickly and catch up with others. JKS keystore is an old topic but I'm bringing this back because the

Re: [VOTE] Retire Apache James HUPA

+1 Le 23/07/2021 à 11:00, btell...@apache.org a écrit : 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: [Discussion] Road to 4.0

Hi David, First thank you very much for your involvement into the community, I hope you'll be able to continue to do so. Le 28/08/2020 à 05:11, David Leangen a écrit : Hi Rene, I have observed a few different types of approaches to OSS: * Haphazard “me” approach. I think you are

Re: Update BouncyCastle

Hello, Thank you for your report. I created an issue: https://issues.apache.org/jira/browse/JAMES-3344 and a matching PR. Regards, Raphaël. Le 22/07/2020 à 10:08, Regan, Aaron a écrit : Hi All, We were running into some issues when working with TLS. The errors we were getting we think

Re: James SMTP Model

Hello, It seems you missed at least one common use case. An external SMTP server should be allowed to contact your SMTP server to send you emails related to your domains. This is the remote delivery part, but for your own server. For this use case you need a SMTP server that is listening on

Re: Call for vote: Apache James 3.5.0

+1 Le 19/06/2020 à 05:44, Tellier Benoit a écrit : 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: Distributed James: make ElasticSearch indexing optional?

prefer that we ask for a vote? Cheers, Raphaël. Le 15/06/2020 à 16:15, Matthieu Baechler a écrit : On Mon, 2020-06-15 at 15:30 +0200, Raphaël Ouazana-Sustowski wrote: [...] I see many use cases where you would not need search, essentially based on automatic mail processing, which is a common James

Re: Distributed James: make ElasticSearch indexing optional?

Hello, Le 15/06/2020 à 09:52, Matthieu Baechler a écrit : Hi Raphael, On Fri, 2020-06-12 at 18:29 +0200, Raphaël Ouazana-Sustowski wrote: Hello Matthieu, Le 12/06/2020 à 10:05, Matthieu Baechler a écrit : Hi Raphael, My answers below On Thu, 2020-06-11 at 18:01 +0200, Raphaël Ouazana

Re: Distributed James: make ElasticSearch indexing optional?

Hello Matthieu, Le 12/06/2020 à 10:05, Matthieu Baechler a écrit : Hi Raphael, My answers below On Thu, 2020-06-11 at 18:01 +0200, Raphaël Ouazana-Sustowski wrote: Hi, Here is a proposal to make ElasticSearch optional in our distributed product/flavor/server. Comments are welcome. ## Why

Distributed James: make ElasticSearch indexing optional?

Hi, Here is a proposal to make ElasticSearch optional in our distributed product/flavor/server. Comments are welcome. ## Why? Some people have expressed the need of using a distributed James without ElasticSearch: - in some comment here: https://issues.apache.org/jira/browse/JAMES-3086 -

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

to use. Regards, Raphaël. Le 11/06/2020 à 08:21, Tellier Benoit a écrit : On 10/06/2020 22:49, Raphaël Ouazana-Sustowski wrote: Hi Benoît, This inventory is amazing, thanks for having issued it. For my part it's just missing the LDAP read only user repository as an implementation of the user

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

Hi Benoît, This inventory is amazing, thanks for having issued it. For my part it's just missing the LDAP read only user repository as an implementation of the user repository. But I probably missed things :) Oh for example the (unfinished?) import / export mechanism. Regards, Raphaël.

Re: Product vs. Profile

Hello, For me "server" is nice to describe a particular packaged James setup. The term might me a little too much generic, but if you prefer it above "flavor" or "product" or "profile", why not. On the other hand, when you customize a particular "server" (to use an LDAP user repository for

Re: Product vs. Profile

Hello David, Le 28/05/2020 à 07:55, David Leangen a écrit : Hello Raphaël, Someone (aka Michael Bailly) suggested "Flavor" instead of "Product". I also think it's a nice way to speak about a product already configured to match some specific needs. Yes, “flavor” could be a good concept. I

Re: Product vs. Profile

Hello, Someone (aka Michael Bailly) suggested "Flavor" instead of "Product". I also think it's a nice way to speak about a product already configured to match some specific needs. Regards, Raphaël. Le 14/05/2020 à 13:52, David Leangen a écrit : Hello! While writing the documentation, I

Re: Lay of the land

Hi David, Quick answer: most of these projects (Mime4j, JSieve, JSPF, JDKIM) are libraries that are implementing a specific protocol / RFC. They are not meant to change much because these protocols don't neither. But they are still interesting because they could be useful for other people

Re: Call for vote: Apache James 3.5.0

+1 Le 06/04/2020 à 13:07, Tellier Benoit a écrit : 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:

Re: About Cassandra Inconsistencies

ple, if you can "fix it" in a lightweight transaction assuring your assumption is correct. (night is generally of good advice) On 19/02/2020 23:27, Raphaël Ouazana-Sustowski wrote: Hello, My main concern is that trying to solve some inconsistencies, we risk to introduce some incorrectness. Your

Re: About Cassandra Inconsistencies

Ouazana-Sustowski wrote: Hello, Is there a way to solve inconsistencies while not adding new ones? When you solve inconsistencies, you have a view of data in memory and try to fix it. If the data change between the moment you take this view and the moment you try to fix the inconsistency, you risk

Re: About Cassandra Inconsistencies

Hello, Is there a way to solve inconsistencies while not adding new ones? When you solve inconsistencies, you have a view of data in memory and try to fix it. If the data change between the moment you take this view and the moment you try to fix the inconsistency, you risk to add an other

Re: Client Authentication

Hi, It seems right at first sight. Do you plan to contribute it? Then I guess engine.setNeedClientAuth(true); should be made configurable depending on the provided parameters. Don't hesitate to open a pull request so that we look at it and integrate it in the main code. Regards,

Re: RecipientIsLocal false negative on james_domain table case mismatch

Hi again, This issue seems very similar to the username's one. But the fix could be simpler, because Domain class already exists in James, so it would need only to ensure the Domain objects are always lower case. Could you provide a fix for this? It would be very welcomed. Thanks, Raphaël.

Re: User-From-Sender Problem

Hi Jerry, For your information the problem has been definitively solved with this ticket: https://issues.apache.org/jira/browse/JAMES-2949 As you identified it, the best way to solve this kind of problem is 'finding all situations where...'. To do this, we relied on strong typing

Re: Delete after 90 Days Task

Hi, Le 2019-10-21 08:12, Regan, Aaron a écrit : I wrote on the Gitter last Friday about wanting to create a function for deleting messages not collected from the server after 90 days. It was mentioned that this may be a job for a task. I have written a task with a API that while delete all

Architectural Decision Records about Distributed Task Manager

Hi, Following the proposal from Gautier and Benoît, see [1], I will now share the architectural decision records we took while implementing the distributed task manager. We are beginning in this process, so we are sharing our records after most of the implementation, but please be assured

Re: LDAP users repository feature deprecation

the authentication system fits together? Robert On Mar 14, 2016, at 7:37 AM, Raphaël Ouazana-Sustowski <raphael.ouaz...@linagora.com> wrote: Hi, I agree with you. This search is suboptimal. But the memberOf attribute is not really available on every LDAP directory. An other way

Re: LDAP users repository feature deprecation

Hi, I agree with you. This search is suboptimal. But the memberOf attribute is not really available on every LDAP directory. An other way should be find to allow to restric on a group. Regards, Raphaël Ouazana. Le 2016-03-11 21:36, Robert Munn a écrit : Hi all. I’ve been using James for

Implementation of JMAP protocol in James

Hi, JMAP is a transport-agnostic, stateless JSON-based API for synchronising a mail client with a mail server [1]. As some of you may know we are working on implementing JMAP in James. We are in the early stage of architecting the code. The current specification [2] supports only HTTP(S)