Disclaimer : the following message is long, and might take time to read,
but I think this is a topic we have to exchange on in order to have a
working James in a distributed environment...
=
Hi every one,
I am working on a
I really think JMAP is a nice protocol to use to implement a web mail as
it allows user to speak directly to the e-mail server without the need
of an IMAP proxy.
Protocol structure is clean and well defined. JSON is easy to parse.
So I am really excited to see such an implementation in James. I
Hi,
I just waned to explain the work we (Erwan Guyomarc'h and me) have done
on quota so far, and what will follow next.
I will also try to write this kind of mail more often, to offer more
readability on my work on James.
The goal of our project is to solve most issues related to Sieve :
-
+1
Le 02/11/2016 à 13:46, Benoit Tellier a écrit :
> Hello every one,
>
> I'm very happy to announce the vote for the upcoming 3.0.0-beta5 version
> of our beloved james server.
>
> You can access sources on github
>
> https://github.com/apache/james-project/releases
>
> Nexus artifact to be
+1
Le 11/10/2016 à 16:04, Benoit Tellier a écrit :
>
> Hello every one,
>
> As you may know, we want to release James 3.0.0-beta5. This release
> demands us to remove every SNAPSHOT dependency, including the one to JSPF.
>
> You can access sources on github.
>
> Nexus artifact to be released
Hello every one,
As you may know, we want to release James 3.0.0-beta5. This release
demands us to remove every SNAPSHOT dependency, including the one to JSIEVE.
You can access sources on github.
Nexus artifact to be released can be found here :
Hello every one,
As you may know, we want to release James 3.0.0-beta5. This release
demands us to remove every SNAPSHOT dependency, including the one to MIME4J.
You can access sources on github.
Nexus artifact to be released can be found here :
+1
Regards,
Benoit
Le 12/10/2016 à 13:15, Tellier Benoit a écrit :
>
> Hello every one,
>
> As you may know, we want to release James 3.0.0-beta5. This release
> demands us to remove every SNAPSHOT dependency, including the one to MIME4J.
>
> You can access sources
approved, we will commit the changes to the current website
Cheers,
--
Tellier Benoit
PMC for the Apache JAMES project
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e
Hi everyone,
Today I would like to submit the following vote:
"Do you support a Java6 -> Java8 on all core James projects?"
Core projects includes:
- Apache James mailbox
- Apache James protocols
- Apache James MPT
- Apache James Mailet
- Apache James Server
Note that they are already
The delay for the vote is passed, and I am happy to announce it is a
success.
We will soon process to the merge of the concerned branches.
Thanks for your involvement on the James project.
Cheers,
Benoit Tellier
Le 04/08/2017 à 14:23, Tellier Benoit a écrit :
> Hi everyone,
>
> Toda
Hi,
One week ago we called for the vote of the Apache James 3.0.0 release.
After a one week voting process, we have decided to re-upload the
pre-compiled jars with:
- A more understandable README
- An already working configuration
Thus we will trigger a new voting process including the freshly
Hello every one,
I'm very very very happy to announce the second vote for the upcoming
3.0.0 version of our beloved James server.
You can access sources on GitHub:
https://github.com/apache/james-project/releases
Nexus artifact to be released can be found here :
+1
Le 07/07/2017 à 18:25, Tellier Benoit a écrit :
> Hello every one,
>
> I'm very very very happy to announce the second vote for the upcoming
> 3.0.0 version of our beloved James server.
>
> You can access sources on GitHub:
>
> https://github.com/apache/james-pro
+1
Le 04/08/2017 à 14:23, Tellier Benoit a écrit :
> Hi everyone,
>
> Today I would like to submit the following vote:
>
> "Do you support a Java6 -> Java8 on all core James projects?"
>
> Core projects includes:
>
> - Apache James mailbox
> - A
Hi every one,
The new website proposal have been accepted by a qualified majority. We
will now merge related branches and deploy the new website
Thank you for again for your involvement on the James project.
Cheers,
Benoit Tellier
Le 21/04/2017 à 18:07, Tellier Benoit a écrit :
> He
Hi,
Following the vote results, I am happy to tell you the new version of
the James website is online. The address is unchanged:
https://james.apache.org/
We also opened a Gitter chat room to allow us to discuss more easily
James related issues. Here is the link:
Hi everyone,
I, in the name of Apache James PMCs, am glad to announce you the release
version 3.0.1 of Apache James server.
It fixes vulnerability described in CVE-2017-12628. The JMX server, also
used by the command line client is exposed to a java de-serialization
issue, and thus can be used
The Apache James community is proud to announce you the 3.2.0 release of
the Apache James server.
Apache James provides a complete, stable, secure and extendable Mail
Servers running on the JVM. More details about Apache James can be found
at: https://james.apache.org/
The release is available
Hi,
After the one week voting period, I am proud to announce the release of
Apache JAMES 3.2.0.
Summary of votes:
- +1 : 5 including chairman and 4 PMCs
- -1 : 0
I will now proceed to the release and related communication as described
in https://github.com/linagora/james-project/pull/1869
+1
On 05/09/2019 20:51, Matthieu Baechler wrote:
> Hi,
>
> I would like to propose the 3.4.0 release of the Apache James server.
>
> You can see changes proposed to the website at the occasion
> of that release, as well as communication on this GitHub pull
> request:
+1 for all projects
On 09/09/2019 14:59, Tellier Benoit wrote:
> Hi,
>
> In order to improve maintenance of James related libraries, I propose to
> switch target JDK version to JDK 1.8.
>
> This means:
> - Upgrading JDK from 1.5 to 1.8 for JSPF project
> - Upgra
Hello all,
We are 21 days away of the month of October and its traditional
HacktoberFest [1].
The HacktoberFest is a one month challenge to promote Open source
contributions on GitHub. Using this event we can easily spread the world
about Apache James, work on some easy features, and hopefully
On 16/09/2019 15:38, Matthieu Baechler wrote:
> Hi,
>
> On Mon, 2019-09-16 at 10:19 +0700, Tellier Benoit wrote:
>> Hello all,
>>
>> [...]
>>
>> What would you think of such an approach?
>>
>
> There's a small detail that bothers me: in the
Hi,
In order to improve maintenance of James related libraries, I propose to switch
target JDK version to JDK 1.8.
This means:
- Upgrading JDK from 1.5 to 1.8 for JSPF project
- Upgrading JDK from 1.6 to 1.8 for JSIEVE project
- Upgrading JDK from 1.6 to 1.8 for JSDKIM project
I do propose
I updated https://issues.apache.org/jira/browse/JAMES-2884 accordingly
to what had been discussed in this thread.
I did also create a first batch of sub-tasks to reflect the first steps
of the aforementioned approach.
Concretely, the first target is:
Getting a 'memory-guice' powered 'jmap'
use what endpoint he wants.
>
> An other point is about the name `draft`, don't is it more useful to add
> the RFC number instead?
>
> Antoine
>
>
> Le lun. 16 sept. 2019 à 05:19, Tellier Benoit a
> écrit :
>
>> Hello all,
>>
>> @cketti menti
Hello all,
@cketti mentioned his interest for helping updating our JMAP
implementation to final RFCs.
We should be careful not breaking things for existing James clients
using the deprecated/outdated JMAP specification. Maybe the best thing
would be to expose the final JMAP spec on an other port
Hello,
That is a very good question.
We currently have in the development backlog the plan to develop a SMTP
test suite for outbound SMTP.
This question is quitte touchy as:
- We want a complete customisation of the return code of the various
servers
- We want to test the complete mechanism,
1/ +1
2/ +1
3/ +1 overall however I believe we have to make improvements to the
guice extension mechanism.
Some example of things that would make sense:
- As a user I want to inject dependencies non bundled in James for my
extensions.
I also think deprecation/removal of spring-only features
+1
On 18/07/2019 14:25, Matthieu Baechler wrote:
> Hi community,
>
> I've been working on the subject of the build time for James lately.
>
> TL;DR;
>
> I'd like to require JDK-11 as the default compiler for James to use the
> `-release` flag to fasten the build (while still targeting Java 8
additional commands.
What do you think of these ideas?
Do you get other ideas?
Best regards,
Benoit Tellier
On 09/09/2019 14:03, Tellier Benoit wrote:
> Hello all,
>
> We are 21 days away of the month of October and its traditional
> HacktoberFest [1].
>
> The
Hello all,
As off 20/09/2019 delays are not supported on top of RabbitMQ MailQueue.
While this is not a problem for a "Mail Delivery Agent" server, this is
a major concern for a "Mail Exchange" server, as stated out by @splainez
on the gitter channel.
A possible implementation came to my mind
Hi Matthieu,
It look like it is going to be a long thread...
Yes, that is definitly worth the discussion.
On 20/09/2019 16:00, Matthieu Baechler wrote:
> Hi Benoit,
>
> Thank you for bringing that subject to the mailing list.
>
> On Fri, 2019-09-20 at 13:46 +0700, Telli
; I had already changed back to luceneIndex from lazyIndex and rebooted.
> I also removed the lazyIndex's version of the lucene folder. But I'm
> still getting the same exception.
>
>
> On 11/5/2019 12:07 AM, Tellier Benoit wrote:
>> ReIndexing is not implemented on top of l
Hi Jerry,
Thanks for the updated details, it now makes perfect sens!
Long story short: Your Lucene index needs to be migrated as well. I
suspect you migrated only your database (full copy), hence issues.
To do migration, at Linagora, we prefer using external protocols, and
leaving the inner
at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> On 11/4/2019 8:48 PM, Tellier Benoit wrote:
Hi all,
Having fixed, or working on fixes that users did report to us, there is
a big list of meaningful features stacking up in the changelog [1].
Thus I would propose us to pursue a release of James server version
3.5.0 by the end of November.
As with most recent releases, that is also the
Hi,
Within [2] I do work on documenting how to secure remote delivery with
SSL and startTls.
Matthieu Baechler asks wether we should require encrypted delivery
(startTls / ssl) by default in shipped configuration.
This comes with trust issues, we might end up enabling
mail.smtp.ssl.trust as a
s to me a much better option
> would be a 'build it once if it doesn't exist' option. That would be
> one less thing for an overwhelmed administrator (me) to remember to do
> when migrating James. Ideas?
>
> Jerry
>
> On 11/5/2019 1:04 AM, Tellier Benoit wrote:
>> M
Hi Jerry,
You need also to specify `mail.smtp.localaddress`
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
Local address (host name) to bind to when creating the SMTP socket.
Defaults to the address picked by the Socket class. Should not normally
need to be
ntly, finding the "Main" class is quite a task. It's buried
> pretty deep in one of a hundred sub-projects on the left. Really need
> some navigation/path info for how to find the Main class.
>
> Tellier, sorry to bring all of these things up. But at this point I'm a
> co
Hi Jerry,
I'm working on a refresh of build instructions for contributors [1].
IntelliJ (community version) is working great.
[1] https://github.com/linagora/james-project/pull/2792
Regards,
Benoit
On 01/11/2019 03:50, Jerry Malcolm wrote:
> What is the recommended development environment
My bad, answer inlined...
On 13/11/2019 15:24, Matthieu Baechler wrote:
> Hi Benoit,
>
> It looks like you forgot the answer to the mailing list.
>
> On Wed, 2019-11-13 at 14:46 +0700, Tellier Benoit wrote:
>> Hi Matthieu
>>
>> On 12/11/2019 15:19, Matth
gt; Jerry
>
> On 10/29/2019 1:19 PM, Jerry Malcolm wrote:
>> I created JAMES-2942 <https://issues.apache.org/jira/browse/JAMES-2942>.
>>
>> The emails in question do not have any additional explicitly-added
>> user flags.
>>
>> Jerry
>>
>>
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
mailet/ai mailets to be used instead.
- ToRecipientFolder.
and the missing
> "install" goal on the maven panel?
>
> On 10/31/2019 11:29 PM, Tellier Benoit wrote:
>> Hi Jerry!
>>
>> Thanks for the precise feedback.
>>
>> I updated the pull request accordingly.
>>
>> Regards,
>>
>> Benoit
&g
After this changeset is applied I notice this test being unstable:
RabbitMQEventBusTest$ConcurrentTest.concurrentDispatchKeyShouldDeliverAllEventsToListenersWithSingleEventBus
This fails in the following fashion:
[88d7e4736e39a75058f168ae217549ada9884623] 05:40:07.877 [ERROR]
On 26/10/2019 09:27, Garry Hurley wrote:
> -1
>
> While I agree it is good to support Java 11, forcing a move to Java 11 will
> hamstring some users of James. First of all, government agencies are slow
> to adopt new versions, mainly because they have few actual employees
> well-versed enough to
+1
Thanks for the proposal.
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:
>
>
Hi Jerry,
Recipient rewrite is not a bijection, as one recipient might be
rewritten into several addresses.
This means that, in some corner cases, you might end up with "two" senders.
So solving that problem is not easy, and corner cases will arise.
To answer you, I'm not sure "sender mapping"
Looks like a serious JPA bug, yes...
Can you open a JIRA (https://issues.apache.org/jira/browse/JAMES) for it?
"Unable to perform range deletes with JPA" could be a good name.
What are the flags of the messages you delete? Do they have user flags?
Regards,
Benoit
On 26/10/2019 10:48, Jerry
Looks great!
You are very welcome to propose a pull request regarding this.
Benoit
On 26/10/2019 10:19, Jerry Malcolm wrote:
> I have located the code that is apparently causing this problem. It's an
> easy fix, and it's now working for me. But I would like to get
> verification from some
Hi everyone,
Let me post here a proposal made by Gautier which I find of interest:
Over the last months, my company (Linagora) have done a large set of deep
changes in James' architecture without much discussion with the community.
In order to change that, we would like to propose an
w in a different folder.
>
> I've got to dig in and learn about writing a MailboxListener. But
> assuming my assumptions for the steps above are valid, I can make it
> happen. If I don't have the steps correct, please set me straight.
>
> It looks like my next step is going to
get a list
> (efficiently) of all matching to/from emails, I'm ready to learn a
> different way.
>
> Thx as always.
>
> Jerry
>
> On 10/14/2019 10:09 PM, Tellier Benoit wrote:
>> Hi Jerry,
>>
>> First I'd begin with a quick thought that might save you
as well as having inbound map recipient to mysupercryptic.
> Otherwise, user is going to need to have two different user accounts to
> see both inbound and outbound mail.
>
> Am I still missing something?
>
> Thanks,
>
> Jerry
>
> On 10/28/2019 6:00 AM, Tellier Benoit
Hi Jerry, answers inlined.
Cheers,
Benoit
On 28/10/2019 00:38, Jerry Malcolm wrote:
> When storing mail, the target account and folder are passed in to one of
> the three mail-store mailets. If the folder doesn't exist on the target
> account, it makes sense that this folder be created
Hi all,
Then it is my turn to propose some architecture decision records
regarding our ongoing work to improve ElasticSearch efficiency.
You can find the ADR there:
https://github.com/linagora/james-project/pull/2772
Best regards,
Benoit
And here are the Architecture Decision Records for the work of our
upcoming months.
The target: JMAP Draft GetMessageList should not end up calling the
blobStore.
To do this:
- We need to have partial reads
- And precompute the preview
- We need to enable storage policies on top of an hybrid
Sounds great!
On 16/10/2019 22:07, Raphaël Ouazana-Sustowski wrote:
> 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
Hi all,
## Context
While contributing a way to rebuild JMAP fast messageView projection via
webadmin, we end up with the need of supporting the following actions on
the same endpoint:
Example:
POST /users/BOB/mailboxes?task=rebuildMessageFastViewProjection
POST
On 02/12/2019 16:18, Matthieu Baechler wrote:
> Hi,
>
> Could you please give us a end-to-end example of what you describe?
>
I will give that below.
> How does a Task declare the endpoint it contribute to?
It takes a `Set` with a @Named annotation for it as a
constructor parameter.
> How
Hi Matthieu,
On 28/11/2019 23:08, Matthieu Baechler wrote:
> On Thu, 2019-11-28 at 18:04 +0700, Tellier Benoit wrote:
>> Thanks for the reply!
>>
>> [...]
>>
>> My concern of the day is the fact **To read fast JMAP property I need
>> slow full message loa
Hello all,
## Context
We are working on JMAP, and EMail::hasAttachments metadata is listed as
a fast property.
However to retrieve it today, we need to do a full message read in order
to load attachment (as JMAP hasAttachment do not take inlined
attachments into account and mailbox property
/2019 17:26, Matthieu Baechler wrote:
> Hi,
>
> On Thu, 2019-11-28 at 15:51 +0700, Tellier Benoit wrote:
>> Hello all,
>>
>> ## Context
>>
>> We are working on JMAP, and EMail::hasAttachments metadata is listed
>> as
>> a fast property.
>>
&
Hi Aaron,
We get this working great with the Cassandra/ElasticSearch setup.
Are you sure:
- That ElasticSearch indexing is working fine (ERROR logs + dead-letter
[1])
- That these mail accounts are not empty?
I'm quite surprise that you get no results for this well tested method...
[1]
On 30/10/2019 01:08, Jerry Malcolm wrote:
> I am curious, though, why you said it wouldn't be enabled for sending by
> default.
I say that because what you describe is well defined specific use cases
(internal vs external mailboxes).
As a James user, I don't have such needs, and I don't expect
gee.org resolves to 90
> mxf-2.aegee.org. / 10 mail.aegee.org. / 1 mxf-1.aegee.org. and on
> mxf-1,2.aegee.org there is no SMTP server.
>
> What is the impact of fake records on the retry strategy?
>
> Regards
> Dilyan
>
> On Mon, 2019-07-29 at 17:06 +0200, Tellier B
cts
>
> Thanks
>
> On Mon, Sep 9, 2019 at 11:04 AM Antoine Duprat wrote:
>
>> +1 for all projects
>>
>> Le lun. 9 sept. 2019 à 10:03, Tellier Benoit a
>> écrit :
>>
>>> +1 for all projects
>>>
>>> On 09/09/2019 14:59, Tellier Benoit
:
- https://issues.apache.org/jira/browse/JSIEVE-113
- https://github.com/apache/james-jsieve/pull/19
Best regards,
Benoit Tellier
On 23/09/2019 11:01, Tellier Benoit wrote:
> Hi,
>
> This proposal received 3 vote for (+1), 0 vote against, and reached the
> required PMC quor
Hi Jerry,
This is a bug, based on your mail I opened a report there:
https://issues.apache.org/jira/browse/JAMES-2913
I'll write a failing integration test regarding this during my lunch
pause but I won't have the time for writing the fix...
Best regards,
Benoit Tellier
On 07/10/2019 03:15,
Hi Jerry,
Regarding that one I believe the best move is relying on the mailet
extension system by defining a 'onSuccessProcessor' configuration option
in the RemoteDelivery mailet.
This requires adapting 'RemoteDelivery' code for allowing such an
extension mechanism.
I dropped what I had in
Thanks for the move, that's really nice to have you on board!
We don't "shoot" people at sunrise :-)
As a contributor, you can propose some github pull request (that we
prefer to JIRA attached patches). The people endorsing the
responsibility is the 'committer' merging your patch into the James
The Project Management Committee (PMC) for Apache James
has invited René Cordier to become a committer and we are pleased
to announce that he has accepted.
René is contributing to the James project for one year so far. He was
invested on features like the mailboxListener event bus, the
order to get a JIRA account
> set up? And is there a home page for JAMES JIRA?
>
> On 10/7/2019 9:34 PM, Tellier Benoit wrote:
>> Sounds like a great proposal!
>>
>> Don't you mind opening a JIRA ticket about this?
>>
>> Best regards,
>>
>&
RFC-4314 IMAP4 Access Control List (ACL) Extension seems like the way to go.
A mailbox listener could give you the right on newly created mailbox I
guess.
We have a working delegation implementation on top of JMAP however
implementing it in IMAP proved to be difficult (especially regarding
LIST
Sounds like a great proposal!
Don't you mind opening a JIRA ticket about this?
Best regards,
Benoit
On 08/10/2019 01:53, Jerry Malcolm wrote:
> As a bit of background for this proposal, I personally have no problem
> trading a small overhead of some additional headers in a delivered
> email if
Hello all,
At Linagora we rely on the distributed James Guice implementation.
We are willing to improve mail (JMAP) experience on top of Object storage.
In order to do so, we want the "list emails in a mailbox scenario" to
not lead to read the slow object storage.
In order to achieve this, I
Hi Jerry,
Globally, we expect users to rely on extensions mechanisms James
provides, and not on DB schemas (that might change in the future!)
I would advise you to rely on MailboxListeners (that receives events
from users mailboxes)
The Added event is here the one that interest you. You can
Hi Matthieu,
I think this is a great suggestion.
On 09/12/2019 23:25, Matthieu Baechler wrote:
> Hi,
>
> [...]
>
> Given everything is reactor based, it would be a much better use of
> resources to let the listeners work with `Publisher` type and use non-
> block APIs.
I think this is a great
On 10/12/2019 15:28, matthieu.baech...@gmail.com wrote:
> [...]
> Writing an Architecture Decision Record would mean it's a decision we
> took (and implemented). It's not the case for now so I didn't wrote it.
>
> Now, either we agree about it and it can become an improvement issue in
> JIRA or we
+1
We should make this happen.
On 12/02/2020 17:29, Matthieu Baechler wrote:
> On Wed, 2020-02-12 at 16:27 +0700, Tellier Benoit wrote:
>
>> - Through grafana, the admin will have the information directly
>> available. Nowaday, health-checks requires her to execute the
n't it be more logic to log only status changes ?
>
> I mean, if you are in a degraded state, you will log the same thing each
> minute else if you have fixed the issue.
>
> Le mer. 12 févr. 2020 à 11:43, Tellier Benoit a
> écrit :
>
>> +1
>>
>> We should m
Hello all,
Recently, as part of our work documenting Administration Procedures for
the Distributed Guice James product, we are having some reflections
regarding the way to conduct monitoring, which undertook some nice
discussions.
Currently, monitoring of `mailbox event processing` and `mail
e didn't appear to find any problems.
>
> I understand what you said about Guavate bridging Guava and java8. But
> Guava is part of Guice, correct? Since my configuration is spring/jpa,
> should I even be going into code that talks to Guice? Could that be the
> problem?
>
> Jerr
Hi Jerry,
Looking at
https://mvnrepository.com/artifact/com.github.steveash.guavate/guavate
Guavate is a tiny library to help bridge the gap between gauva and java8
while the Guava team figures out what they are going to release
We use it as a java utility for that very purpose.
Now about your
Hello Jerry,
The debug log you mention is benign, and can safely be ignored.
When the lookup is performed, JPA don't find the record (as it's an
external mail) and throws an exception that we log.
Regards,
Benoit
On 05/02/2020 06:43, Jerry Malcolm wrote:
> I've set up an out-of-the-box
Hi Jerry,
I have little clue about this Spring related issue.
It looks like two files reference this XSD in there metadata:
-
server/container/spring/src/main/resources/META-INF/org/apache/james/spring-mailbox-authenticator.xml
-
Hello Raphael,
The simple fix could be :
- 1. Iterating the in memory list of record
- 2. For each record, refresh it (re read it from DB to be sure to have
the latest version of it)
- 3. Then detect inconsistencies (reading the associated
denormalization table)
Step 2., currently not
Hello Duc, answers inlined.
On 14/02/2020 17:06, Đức Trần Tiến wrote:
> Hello people,
>
> In recent days, James had been recieved a report about the strage
> *MailboxNotFoundException*. There were some investigation to find the cause
> of the issue.
> We found that there are some inconsistent
ncorrectness.
>
> Your proposal is probably reducing the window of error, but it
> potentially adds errors where we had only inconsistencies. Do we accept
> that trade-off?
An inconsistency is an error in itself, so I am.
Regards,
Benoit
>
> Regards,
>
> Raphaël.
4, 19 thg 2, 2020 vào lúc 15:10 Tellier Benoit
> đã viết:
>
>> Hello Raphael,
>>
>> The simple fix could be :
>>
>> - 1. Iterating the in memory list of record
>> - 2. For each record, refresh it (re read it from DB to be sure to have
>&
Hello Raphael,
On 20/02/2020 14:35, Raphaël Ouazana-Sustowski wrote:
> Hello,
>
[...]
>
>
> I don't see how you expect waiting for some time on one node of a
> distributed system can help. Distributed concensus cannot be resolved
> just by waiting some time on one node.
>
>
>> - Confirm
Hi René,
My answers are inlined...
Best regard,
Benoit
On 22/01/2020 10:21, Rene Cordier wrote:
> Hi guys,
>
> I would like to bring on the table some proposition to refactor our
> session usage within James.
>
> # Context
> [...]
> Then I tried to use a `MailboxMapper` defined in the
+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/j
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:
- The maven release staged in repository.apache.org
Hello all,
While working on Cassandra blob store cache, we discussed our usage of
conditional logic within Guice modules.
Our conclusion so far is:
```
Should we have the DistributedJamesServerMain doing a lookup on the
configuration to know if it should compose the cache module?
yes
```
Hi Matthieu,
My answers are inlined.
On 20/04/2020 16:25, Matthieu Baechler wrote:
> Hi,
>
> [...]
>
> We studied a lot of solutions, ranging from having a standalone
ActiveMQ server to implementing the MailQueue using RabbitMQ or Kafka.
Why we chose RabbitMQ deserves an ADR don't you think?
Hi David,
Answers inlined.
Cheers,
On 16/05/2020 14:36, David Leangen wrote:
> Hi!
>
> I noticed that there is a “util” module that is released as a separate jar.
>
> Given that the size of the jsieve project is so small, is it really necessary
> to release it as two separate jar files?
1 - 100 of 3505 matches
Mail list logo
