Hi David!
A pretty long and interesting email!
On 17/05/2020 13:01, David Leangen wrote:
>
> Hi!
>
> As I just mentioned in a different email:
>
>> As part of my documentation project, I am starting to turn my attention
>> towards the code itself. I am trying to understand how the system
On 18/05/2020 14:35, Matthieu Baechler wrote:
> On Sun, 2020-05-17 at 14:32 +0900, David Leangen wrote:
>> Hello,
[...]
>> I think Guice is easy enough that it would be worthwhile for me to
>> learn it, even if it’s just for James.
>>
>> On that note, what are the plans going forward
On 18/05/2020 16:16, David Leangen wrote:
>
> Thank you for the explanations. I now understand much better the migration
> from Spring to Guice, and the intent behind Guice.
>
> Instead of directly answering the questions you posed, I will make a proposal
> that I think goes in the same
On 18/05/2020 16:23, David Leangen wrote:
>> But maybe all of this should be discussed in a separate thread as a
>> "Guice roadmap"…
>
> These all seem like great ideas to me.
>
> I just had a wild thought based on your ideas. Just like there is a concept
> out there of “headless CMS”, maybe
On 19/05/2020 08:59, David Leangen wrote:
[...]
> Ok, cool. Let’s get back to this after we resolve the current issues.
>
> If you agree with this approach, then I will create a Jira Issue this time
> and work against that. :-)
:+1:
Thanks for taking care about this.
Best regards,
Benoit
>
On 19/05/2020 09:14, David Leangen wrote:
> Hi,
>
> I am having a bit of trouble distinguishing the jsieve API from its
> implementation. It is my intention to document this project, but I find it
> more difficult to understand than it ought to be because of this problem.
>
> If the library is
Hi David,
We are missing this information in our current README.md.
You can simply use a docker volume on your `docker run` command.
The path inside the container is `/root/conf`.
So `docker run ... -v
$PWD/webadmin.properties:/root/conf/webadmin.properties ...` should do
the trick.
Regards,
On 14/05/2020 18:23, David Leangen wrote:
>
> One question: if these projects (Mime4j, JSieve, JSPF, JDKIM) are stable, and
> since they seem to be in use for quite some time, what do you think of
> promoting them to v1.0.0?
>
> According to semantic versioning, keeping the version < 1 implies
Hi David.
It looks like you struggled much with badly written javadoc...
> (I am assuming that “RFC32028” is actually RFC3028 [5], which should be
> updated to RFC5228 [6]).
That typo needs to be fixed.
> So I gather than the email must be RFC882 compliant, which means that its
>
Hello David,
> I know you are all probably very busy, but to allow my contribution to
be useful, it would be very nice to get comments on my journey so far.
If I don’t document the “right” thing and run out of time, it would be a
wasted opportunity. :-(
100% agree with that.
Don't hesitate if
I created https://issues.apache.org/jira/browse/JSIEVE-116 based on this
thread.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[...]
>> - The SieveFactory takes a SieveScript inputstream, and a Mail adapter,
>> and returns a list of Action that results from the sieve script
>> execution against the supplied email.
>
> +1
>
> Perhaps provide a “default” MailAdapter? In that case, then the factory could
> even just take
On 22/05/2020 18:06, David Leangen wrote:
> Thanks Benoit, very helpful! It does lead to more questions, though. :-)
The contrary would have surprised me ;-)
I have been yet again quitte verbose once again, don't hesitate to raise
a warning if the signal/noise ratio gets to low...
Cheers,
>
On 22/05/2020 17:19, David Leangen wrote:
>>> Perhaps provide a “default” MailAdapter? In that case, then the factory
>>> could even just take an email and a SieveScript InputStream and apply the
>>> default MailAdapter. The method with the MailAdapter signature would only
>>> be needed for
Le 28/08/2020 à 14:48, Raphaël Ouazana-Sustowski a écrit :
> 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
Le 31/08/2020 à 09:43, David Leangen a écrit :
>>> From my point of view the most important point is to describe what
>>> James does now.
>> +1
> Yes, I agree.
>
> Again, I do not disagree that this is “most important”. Let me use a more
> concrete example to illustrate why it is not the
Le 31/08/2020 à 18:28, David Leangen a écrit :
> Hi Benoit,
>
> Ok, cool. I think we are making progress.
>
>> Would it answer some of your concerns?
> Let me answer this first: yes. Thank you for patiently tolerating my
> persistence.
>
>
>> Well from what I recall, we had a nice
Hello all,
As Quan did not succeed to send a mail to this list (...) I'm forwarding
it for him!
Cheers,
Benoit Tellier
---
Hi,
Let me introduce myself first. My name is Tran Hong Quan. I am from
Vietnam and studying fourth-year at Hanoi university of science and
Hello there,
Cassandra is an eventually consistent datastore, that can be used in a
consistant fashion. To do so, we rely on a mechanism called "LightWeight
Transactions (LWT)". Lightweight transactions relies on the PAXOS
distributed consensus algorithm to enforce a condition upon data
mutation.
Hello David,
I did actually came back from vacation.
I think I did answer in that thread already. I would love to have other
people feedback as well on the opportunity to market our current
"community roadmap" (documentation, product re-branding, CI) into a
major release.
Le 26/08/2020 à
Le 29/09/2020 à 17:47, Matthieu Baechler a écrit :
> On Tue, 2020-09-29 at 08:59 +0700, Tellier Benoit wrote:
>
> [...]
>
>> Spring deprecation could be seen as this big event for most users ?
>
> You are not very good at public relation, do you? (:
> I do
A big thread, let's jump in.
Le 28/09/2020 à 02:34, Matthieu Baechler a écrit :
> Hi,
>
> I'm not sure which message to answer in the thread so I start a new
> thread to summarize my thoughts on the various topics discussed.
>
> 1. About Roadmap
>
> [...]
>
> 2. About documentation
>
>[...]
>
Hi David,
I gave a shot at defining:
- Core components, that offers services at heart of James
- Utility components, that offers services core-components
implementations can rely on.
- Mailbox sub-components.
Here is the result. I encourage other project members to review it.
- Did I
I am lurking a bit within that interesting conversation and might only
answer some points I might have something to propose.
This thread discusses what we try to do as a project. In my previous
post on this list, I (tried to) explain the legacy behind the James
project goals. But I of course
Hi David,
On 23/05/2020 04:16, David Leangen wrote:
>
> Hi!
>
> Based on things that Benoit has been explaining to me (in threads such as
> [1], [2]), I have been thinking about the top-level description of James.
>
> [1] https://www.mail-archive.com/server-dev@james.apache.org/msg65858.html
I might start tomorrow relaxing LWT transaction for users & domains.
Let's see where it gets us!
Cheers,
Benoit
Le 20/10/2020 à 09:08, Tellier Benoit a écrit :
> Hello there,
>
> Cassandra is an eventually consistent datastore, that can be used in a
> consistant fashion. T
Le 06/07/2020 à 07:13, David Leangen a écrit :
> Hey Benoit,
>
>> Now, that being said, I believe we should always define a "purpose" for
>> an API, and here we mixes things in my opinion.
> Yes, very good point. I agree 100%
>
>
>
>> Are we defining an API for building any arbitrary SMTP
Nice image!
- there is a queue before SMTP outgoing service (as you don't want to
handle SMTP synchronously anyway)
client -> SMTP (in, as a server) -> queue (spool) -> Processing chain ->
Queue (outgoing) -> RemoteDelivery runnable
Also as Matthieu said, RemoteDelivery is a side effect of the
Le 08/07/2020 à 14:40, David Leangen a écrit :
> Sorry, I do have one more question in response to your email…
>
> You wrote:
>
>> In my opinions we should document "How to write hooks with the
>> protocols/smtp library", "How to plug such hooks into a running James
>> server"
>>
>> Then "How to
Le 07/07/2020 à 20:58, David Leangen a écrit :
>> Hope it helps.
> Yes, quite a lot!!
>
> A few clarifications, please.
>
>> SMTP Service is talking TCP with the client. When it is asked to
>> deliver a message, it simply calls `enqueue` on the MailQueue.
> Can you be more precise about what
Le 08/07/2020 à 14:39, David Leangen a écrit :
>> The only wrong thing about this picture is the SMTP Service before
>> "Outgoing".
> Ok, thank you Matthieu.
>
>> As weird as it is, the delivery of messages to a remote server is done by a
>> Mailet called RemoteDelivery and it's not handled by
Le 06/07/2020 à 14:12, David Leangen a écrit :
> Thanks Benoit.
>
> Now, since I already have your attention on this topic, please allow me to
> really push so I can reach some kind of resolution. The resolution will allow
> me to figure out how to move forward with several things. Since I
Le 08/07/2020 à 15:33, David Leangen a écrit :
> Thanks.
>
> I love this James adventure. It is not boring. Every time I scratch the
> surface, a new concept pops out.
>
> Ok, so digging in…
:-)
>> Also as Matthieu said, RemoteDelivery is a side effect of the current
>> Processing chain.
> I
Le 06/07/2020 à 13:12, David Leangen a écrit :
> [...]
>> I believe people are interested by a working SMTP implementation where
>> they can "plug" there behaviors or add the commands they miss.
> I am beginning to think that we may have a fundamentally differing
> understanding of what an API
Le 13/07/2020 à 13:01, David Leangen a écrit :
> Hi,
>
>>> If no objections are received in the next 3 days I'll move forward with
>>> the change.
> Thanks for all your efforts. Sorry that I have not moved forward much in the
> past days. I have been preoccupied with other things.
>
> I am having
Le 02/07/2020 à 23:03, Eugen Stan a écrit :
> Hello David,
>
> [...]
>
> Agian, I do think protocols should be independent since they have
> different rules and share only some technical aspects.
+1
Actually IMAP is independent.
LMTP is based on SMTP implementation.
A current limitation of
Hello David,
Le 03/07/2020 à 04:30, David Leangen a écrit :
>
> [...]
>
>> I don't believe the code is super clean but it does work and is quite
>> efficient and fast.
>
> Yes, that is important, but again, this comment about being “efficient and
> fast” seems perfectly valid for an
Hi all,
In an evening effort, I started writing a documentation skeleton for the
Distributed James server with the new Antora Documentation.
In order to juge the results I came up with (and do some corrections as
I am new to this technology) I would like to generate the result of my work.
I
Hi David,
As I exposed it earlier, protocols-smtp mixes the protocol
implementation and the interface it defines. We would benefit from
separating the too.
Now, that being said, I believe we should always define a "purpose" for
an API, and here we mixes things in my opinion.
Are we defining an
Hi Eugen,
You will find my answers inlined.
>
> I believe you make the assumption that people use and want to use the
> full plethora of protocols we have in James.
>
> Sort of "All or nothing" approach.
>
> Why do you think it is so?
>
> I would argue that we should make little
|The Project Management Committee (PMC) for Apache James has invited
David Leangen to become a committer and we are pleased to announce that
he has accepted. ||David started being active on the James project several
months ago, and
started a huge documentation effort he seems committed to.
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 in the next 3 days I'll move forward with
> the change.
>
>
> Moving forward with the website I would
Le 09/07/2020 à 07:42, David Leangen a écrit :
> Hi Eugen,
>
> Thanks for your support.
>
>> GIven the discussion around the specific topics I think we are getting
>> our documentation.
>> @David: If you can do just that: ask questions and compile the answers
>> it would be a huge win for us.
>
Le 10/07/2020 à 07:34, David Leangen a écrit :
> Hi Eugen,
>
> Thank you very much for all your efforts. The community is fortunate that you
> are able to dedicate so much concentrated effort.
>
>> I've given up on building the old site since I failed several times.
> I think that’s ok, though.
Hello,
Le 17/06/2020 à 09:12, David Leangen a écrit :
> Hello!
>
> When writing the docs, I came to understand that what we mean by “Mail
> Server” is not very clear to me.
>
> There is “SMTP Server” (which is a “Mail Server”).
>
> There is “POP Server” (which is a “Mail Server”).
>
> There
Hello all,
Eugen suggested me to be having a community call.
We have been discussing a lot lately, this could be the occasion to know
each others better, and find some common ground between community members.
I know that live meetings tend to disconnect people (if you cannot
attend you are
Le 18/06/2020 à 17:02, Tellier Benoit a écrit :
> Hello all,
>
> Eugen suggested me to be having a community call.
>
> We have been discussing a lot lately, this could be the occasion to know
> each others better, and find some common ground between community members.
>
I opened the following ADR to better define "quality levels"
https://github.com/apache/james-project/pull/219
Please have a look ;-)
Le 21/06/2020 à 13:03, Tellier Benoit a écrit :
>
>
> Le 19/06/2020 à 20:49, David Leangen a écrit :
>>
>> Hi,
>>
>
Le 19/06/2020 à 20:49, David Leangen a écrit :
>
> Hi,
>
> Please be in a good mood when you read this. Words can be taken the wrong
> way. I am writing this with a big smile on my face, all in good humour.
>
>>>
[... snipped everything ...]
>>
>> I agree with everything you wrote.
>
Le 24/06/2020 à 02:42, Eugen Stan a écrit :
> Hello,
>
> This is a request for early feedback on the Gradle migration.
>
> I'm assuming we are going to adopt Gradle since IMO it does deliver on
> it's promises and opens us for new possibilities.
>
>
> TLDR:
>
> The migration will be ready
minutes)
- Builds (15 minutes)
Notes will need to be taken.
Any potential decision needs to be exposed (and potentially) debated by
mail.
See you tomorrow ;-)
Cheers,
Benoit
Le 18/06/2020 à 17:06, Tellier Benoit a écrit :
> Le 18/06/2020 à 17:02, Tellier Benoit a écrit :
>> Hello all,
>
Hi all,
The voting period is over.
The vote failed as Matthieu Baechler downvoted the release, and we did
not reach the binding vote quorum.
I will work on addressing the blocking points regarding this, and soon
re-trigger a vote.
Best regards,
Benoit
Le 19/06/2020 à 10:44, Tellier Benoit
egarding Apache James
- I plan to approach Mozilla Thunderbird comunity to collaborate on JMAP
development
```
Notes were taken here
https://cryptpad.fr/pad/#/2/pad/edit/46s0WfDVm6A1cUgWZ5Dk1Bte/
Best regards,
Benoit Tellier
Le 18/06/2020 à 17:02, Tellier Benoit a écrit :
> Hello all,
>
>
An extension developer is a special kind of user, who understands and
leverage James extension mechanism (so yes).
Le 15/06/2020 à 13:02, David Leangen a écrit :
>>> * What is meant by “James User” (as opposed to “Developer")?
>> In my opinion a user is someone running James. He don't compile nor
Very likely we have 2 logging dependencies on the classpath.
This needs to be rationalised. I will add this to JAMES-3214 as this
relates to cleaning dependency mess...
Cheers,
Benoit
Le 13/06/2020 à 20:18, David Leangen a écrit :
>
> Hi!
>
> For the documentation, I have been trying to run
We don't have examples for this yet.
The closer could be
https://github.com/apache/james-project/blob/master/server/container/guice/cassandra-ldap-guice/src/main/java/org/apache/james/CassandraLdapJamesServerMain.java
bringing in LDAP UsersRepository for cassandra-guice server.
The "main server"
Le 12/06/2020 à 18:30, David Leangen a écrit :
> Hi!
>
> Looking at this page:
>
> https://james.apache.org/server/3/config-users.html
>
> It looks like there are 4 ways to configure the user repository:
>
> * JPA
> * JDBC
> * File
> * LDAP
>
>
> Is it possible to use a custom
Le 14/06/2020 à 10:46, David Leangen a écrit :
> Hello Apache James Community!
>
> As you may know, I became interested in James and wanted to learn about how
> to set up my own mail server. My main interests in James are (1) the admin
> api and (2) the ability to extend via Mailets. I was
Le 15/06/2020 à 13:43, David Leangen a écrit :
>
>
>> An extension developer is a special kind of user, who understands and
>> leverage James extension mechanism (so yes).
>
> Makes sense! And I like the term “Extension Developer” as opposed to “(James)
> Developer”.
>
> I am currently
Le 15/06/2020 à 16:09, David Leangen a écrit :
>
>> I think it's a good discussion toe establish the terminology and have
>> the same view of this.
>>
>> I hope it gets into the docs as a term deffinition or something similar.
>>
>> +1 for Extension Developer.
>
> I am thinking something
://www.mail-archive.com/server-dev@james.apache.org/msg66332.html
Le 12/06/2020 à 15:29, Eugen Stan a écrit :
> Hi,
>
> Please use Eugen. That is my given name. Stan is my family name.
>
> La 11.06.2020 11:27, Tellier Benoit a scris:
>> On 10/06/2020 15:19, Eugen Stan 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 handle NoClassDefFoundError
5ad068e2da JAMES-3195 Avoid
+1
Le 19/06/2020 à 10: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
> f
peaks French.
>
> Would it be ok to do the call in French instead of English?
>
>
> Cheers,
> =David
>
>
>
>> On Jun 24, 2020, at 20:41, Tellier Benoit wrote:
>>
>> Reminder ;-)
>>
>> Time: Thursday 25th June 2020, from 8am UTC to
Le 18/06/2020 à 11:15, David Leangen a écrit :
>
> Hi,
>
> Thanks for thinking about this.
>
>>> When writing the docs, I came to understand that what we mean by “Mail
>>> Server” is not very clear to me.
>
>> Somehow. Let me give a try at generifying this:
>>
>> A mail server is a
To be honest, given the exchange on the pull request and the content of
the ADR I came to this formulation
(https://github.com/linagora/james-project/pull/3309#issuecomment-620957935)
'that I am not hostile to it', but would also like a broader feedback
(thanks for asking for it!).
To give my own
ards,
Benoit
>
> Regards,
>
> Raphaël.
>
> Le 25/05/2020 à 07:00, Tellier Benoit a écrit :
>> Hi David,
>>
>> I gave a shot at defining:
>>
>> - Core components, that offers services at heart of James
>> - Utility components, that offers servi
On 10/06/2020 15:19, Eugen Stan wrote:
> I'm mostly referring to libraries. Having a library bring a dependency
> like scala is a no-no on my part.
>
> Ideally the lower parts of James should not bring any dependencies.
> Guava is also big and I would like to see that gone as well.
>
> [...]
+1
On 11/06/2020 23:01, Raphaël Ouazana-Sustowski wrote:
> 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
>
Hello David,
This picture is 100% about project structure, and presents James
sub-projects.
It do not describe the actual "James Server" architecture.
Behind that images lies the concept that the JAMES project is not just
about building mail servers but providing tools to the java mail
On 04/06/2020 13:19, David Leangen (Apache) wrote:
> Thank you Benoit.
>> Here is the link: http://james.apache.org/server/install.html (SMTP)
>
> Ok nice, thanks!!
>> We may not want to advertise POP much given that its integration test
>> coverage is low.
>
> Then how about deprecating POP?
On 04/06/2020 12:39, David Leangen wrote:
>
> Hi again,
>
> In the new documentation, I have tried to explain some of the basic concepts:
>
> * Messages
> * Protocols
> * Storage
>
> I am now turning my attention to how it all fits together. Images like this
> one help a lot:
>
>
Let's create a "provide more architecture pictures" on the JIRA, we will
be able to attach images to it.
Me I have access to a drawing board and my phone, so making drafts will
be easy ;-)
On 04/06/2020 13:37, Tellier Benoit wrote:
>
> On 04/06/2020 12:39, David Leangen wrote
Hi all,
It took me quite a while to put down my thoughts on the topic, here is
what I think.
The JAMES project allows people to run "Servers". I currently really
like the wording used in the documentation written by David on the
topic. I don't see why we need a very abstract word like "product",
Hi David,
Some parts of the actual documentation actually do this.
I think it makes perfect sense for the demo.
Here is the link: http://james.apache.org/server/install.html (SMTP)
I think IMAP makes sense for retrieving the mail.
We may not want to advertise POP much given that its
On 04/06/2020 13:49, David Leangen wrote:
>
>> Behind that images lies the concept that the JAMES project is not just
>> about building mail servers but providing tools to the java mail eco-system.
>
> Sure, but is this a really import concept to convey? If this is just
> something else that
Hello,
Thanks for this email. I had back in the days similar issues when trying
to build the various James related projects and can recall how
frustrating it was.
I do believe that every developer or people interested in the James
project should be able to build it, and test it easily.
In the
Hello,
I am making good progress on Antora documentation migration for the
Distributed Server, only a couple of pages are left.
I am encountering difficulties to document mailet/matcher an operator
can currently use.
Nowaday we rely on the mailet doc plugin to compile a website page from
the
Le 23/07/2020 à 14:27, David Leangen a écrit :
>> Cool! I will try to take some time today to comment more thoroughly, likely
>> in the form of a PR.
> There is quite a lot of text there and a lot of concepts, so it will take me
> a while to go through it. :-)
Maybe more importantly than going
:
- Publish the maven artifacts
- Upgrade the download page and the (old) website
- Announce the release
Cheers,
Benoit Tellier
Le 16/07/2020 à 13:44, Tellier Benoit a écrit :
> Hi,
>
> I would like to propose a new vote 3.5.0 release of the Apache James server.
>
> I fixes Matthieu rem
Le 23/07/2020 à 15:44, David Leangen a écrit :
Cool! I will try to take some time today to comment more thoroughly,
likely in the form of a PR.
>>> There is quite a lot of text there and a lot of concepts, so it will take
>>> me a while to go through it. :-)
>> Maybe more importantly
Le 23/07/2020 à 15:57, Eugen Stan a écrit :
> La 23.07.2020 11:17, David Leangen a scris:
>
> It's great to see progress on this.
> I've also been busy with client/internal work.
>
> I'll make some time to finish up the documentation publishing over the
> weekend probably.
>
> Regarding the
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: https://github.com/apache/james-project/pull/187
You can find:
+1
Le 16/07/2020 à 13:44, Tellier Benoit a écrit :
> 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 rel
Hello David.
I found the issue. org.apache.james.sieve.jpa.model.JPASieveQuota &
org.apache.james.sieve.jpa.model.JPASieveScript are not registered as
persistant class hence the failure.
I opened https://issues.apache.org/jira/browse/JAMES-3348 & a fix for
this here:
Le 20/07/2020 à 18:00, Eugen Stan a écrit :
> Hello,
>
> While working on the documentation website I ran into the question of:
> What parts to document?
>
> 1. What are the repositories we still use in James - some like jdkim
> have merged in james-project - others ?
No.
The JDKIM library still
Hello all,
The Distributed Server so far is relying on the BlobStore component to
store potentially large binary data. This includes emails header, bodies
and attachments. The mailbox, mailRepository and mailQueue core
components, as well as the DeletedMessageVault extension relies on it.
The
submission process.
This should enable better productivity.
Le 05/07/2020 à 23:27, Tellier Benoit a écrit :
> |The Project Management Committee (PMC) for Apache James has invited
> David Leangen to become a committer and we are pleased to announce that
> he has accepted. ||David started bei
Hi René
I did a quick review.
As such, given the limited content, I mostly agree with it.
I do think we might want to leverage this opportunity to close
low-traffic unused mailing lists. This includes:
-site-...@james.apache.org : site discussions happens on server-dev and
not there, it is
Hi David!
Le 15/08/2020 à 08:20, David Leangen a écrit :
> Hello!
>
> I wanted to tie together a few ongoing threads and make a proposal for the
> road to a 4.0 release.
I'm uncomfortable with the 4.0 release switch. It gives the impression
that "much" needs to change whilewhat we need is to
Of course.
I created https://issues.apache.org/jira/browse/JAMES-3487
Cheers,
Benoit
Le 29/12/2020 à 15:19, Jean Helou a écrit :
>>
>> Please note that above 100KB the MimeMessage would be stored on disk,
>> thus limiting memory impact (see MimeMessageInputStreamSource). Maybe we
>> should
Hello Pablo.
Thanks for the fix.
Would you agree opening a PR on Github for this?
Otherwise, I could extract the patch too...
Cheers,
Benoit
Le 26/11/2020 à 01:17, Pablo Pita Leira a écrit :
> diff --git a/README.adoc b/README.adoc
> index 1c4fec1c26..a7c92ae896 100644
> --- a/README.adoc
>
Done
Le 26/11/2020 à 16:25, Jean Helou a écrit :
> hi all,
>
> As you know I started a PR to setup jenkins CI, the latest iteration sees
> the compilation of the project complete in 5 minutes ( thanks to T1C) but
> the tests fail to initialize docker containers with the disastrous
> consequences
rabbitmq.RabbitMQConnectionFactoryTest
>>> ℹ︎ Checking the system...
>>> ✔ Docker version should be at least 1.6.0
>>> ✔ Docker environment should have more than 2GB free disk space
>>> [INFO] Running org.apache.james.backends.rabbitmq.RabbitMQ
I'll answer other threads separately.
I created https://issues.apache.org/jira/browse/JAMES-3468 about this.
I asked Quan, our intern, to take a look.
Regards,
Benoit Tellier
Le 09/12/2020 à 12:58, Jean Helou a écrit :
>>> So from a user perspective adding a user would always succeed. But
Hello Matthieu,
Sadly, I'm unable to see what you did write in the email you sent due to
the absence of quote.
Can you review your email client settings, in order to get a readable
output we can start discussing on?
This time, I made the effort, but I would greatly appreciate a better
display.
> sounds like it would already be a huge gain :) The assertions in a number
> of tests will likely have to be updated to rely on `Awaitility.await()` :)
+1, that would be an enhancements.
>
>
> On Wed, Dec 9, 2020 at 2:40 AM Tellier Benoit wrote:
>
>> Sorry for repost,
>>
>>
Sorry for repost,
I sent that response before but it was lost.
Maybe the unfamous text/html format issue.
Le 07/12/2020 à 04:33, Jean Helou a écrit :
> Hello,
>
> I'm currently trying to increase overall efficiency of the Distributed
>> James server.
>>
>
> I have some concerns but i feel
Hello James DEVs !!!
I want to start a discussion around
https://issues.apache.org/jira/browse/JAMES-3475
Our issue is that James so far require administrative rights on RabbitMQ
server.
This of course means that sharing this RabbitMQ with other apps / James
servers of other tenant represent a
Hello Jean,
Le 11/12/2020 à 15:47, Jean Helou a écrit :
> Hello again jamers!
>
> It's time for your irregular report on the CI effort on apache infra :)
\o/
>> I'm in favor for opening a dedicated ticket and merge a disabled version
>> of this test in order to document the problem.
>>
>
>
101 - 200 of 3505 matches
Mail list logo
