the maven artifacts - Upgrade the download page and
the (old) website - Announce the release Cheers, PMC member name|
Le 07/03/2022 à 15:09, Antoine Duprat a écrit :
> +1
>
> Cheers,
> Antoine
>
> Le mer. 2 mars 2022 à 04:44, Tellier Benoit a écrit :
>
>> Hi,
>>
Ok.
I created https://issues.apache.org/jira/browse/JAMES-3718 to make sure
this do not get forgotten...
Regards,
Benoit
Le 02/03/2022 à 15:21, Andreas Joseph Krogh a écrit :
> På onsdag 02. mars 2022 kl. 09:10:16, skrev Tellier Benoit
> mailto:btell...@apache.org>>:
>
>
I sent one week before
explaining I was about to release cf
Le 02/03/2022 à 14:32, Andreas Joseph Krogh a écrit :
> På onsdag 02. mars 2022 kl. 04:44:29, skrev Tellier Benoit
> mailto:btell...@apache.org>>:
>
> Hi,
>
> I would like to propose a new vote for 3.7.0
+1
Le 02/03/2022 à 10:44, Tellier Benoit a écrit :
> 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:
> https://repository.a
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:
https://repository.apache.org/content/repositories/orgapachejames-1062/
- The changelog for
3.7.0:
Hello René,
Thanks 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
The Project Management Committee (PMC) for Apache James
has invited Juhan Aasaru to become a committer and we are pleased
to announce that he has accepted.
In the last few months, Juhan made several Apache James contributions.
Especially regarding JAMES-3564, we believe he is committed to offer a
to be totally out of sync with the repo : it
> mentions an inexistant 0.9.0 and has not been modified for the last 4 years
> ... maybe delete it ?
>
> jean
>
> On Wed, Apr 14, 2021 at 9:09 AM Tellier Benoit wrote:
>
>> Hi,
>>
>> Following a user request (https
nt
- We make it clear the artifact is not to be used yet
This would look like what Juhan proposed in
https://issues.apache.org/jira/browse/JAMES-3565 ...
Thoughts?
Cheers,
Benoit
>
>
>> [1]
>>
>> https://github.com/linagora/openpaas-james/tree/master/ope
verall project, and we miss a good opportunity to promote it.
> Cheers,
> Jean
>
>
>> Otherwise I will proceed, likely on Friday, if not next week when
>> I have time... - I must confess being impatient to be done with it.
>>
>> Cheers,
>>
>> Beno
ject/pull/389 to be consensual.
If the feedback is positive, I can finish the 3.6.0 process as off
today. Otherwise I will proceed, likely on Friday, if not next week when
I have time... - I must confess being impatient to be done with it.
Cheers,
Benoit
Le 14/04/2021 à 10:34, Tellier Benoit a é
Hi,
Following a user request (https://issues.apache.org/jira/browse/MIME4J-297),
I would like to propose a vote for 0.8.4 release of the MIME4J library.
You can find the maven release staged in repository.apache.org as the
artifact #1053:
of /dockerfiles folder (more or less).
[1]
https://github.com/linagora/openpaas-james/tree/master/openpaas-james/apps/memory
README and pom.xml are of interest.
Cheers,
Benoit
Le 11/12/2020 à 16:29, Tellier Benoit a écrit :
> You're right,
>
> I did not follow up on this.
>
> I just cr
Hi all,
I am happy to announce you the vote for the 3.6.0 release did succeed.
The release received 8 positive votes, 3 of them being binding.
Thanks to all contributors, developers and committers who made this
possible!
In the coming hours, I will finalize the release process, namely:
-
Hello there,
The Apache James distributed server has the ambition to scale seamlessly
and relies on proven distributed technologies in order to do so
(Cassandra, ElasticSearch, S3).
However, we currently rely on RabbitMQ for the messaging part, and
despite the addition of Quorum queues in 3.8.0
+1
Le 06/04/2021 à 14:04, Tellier Benoit a écrit :
> 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 mave
2021, 2pm UTC+7
- The vote ends at Tuesday 13th of March 2021, 2pm UTC+7
You can answer to it just with +1 and -1. Down-votes shall be motivated.
3 binding votes are expected move forward on this release.
Cheers,
Benoit Tellier
Le 30/03/2021 à 17:16, Tellier Benoit a écrit :
> The voting per
Hi Jean,
Le 02/04/2021 à 02:52, Jean Helou a écrit :
> Hi all,
>
> Sorry about the spam, I opened a PR to try and improve the build flow for
> james documentation to try and get the staged documentation published
> automatically after each build of james project.
I think we need to update James
/2021 à 15:16, Tellier Benoit a écrit :
> Hi,
>
> I would like to propose a new vote 3.6.0 release of the Apache James server.
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1050:
> https://repository.apache.org/content/
+1
I had been more careful this time. Sorry again for the inconvenience.
Le 22/03/2021 à 15:16, Tellier Benoit a écrit :
> Hi,
>
> I would like to propose a new vote 3.6.0 release of the Apache James server.
>
> You can find:
>
> - The maven release staged in
Hi,
I would like to propose a new vote 3.6.0 release of the Apache James server.
You can find:
- The maven release staged in repository.apache.org as the
artifact #1050:
https://repository.apache.org/content/repositories/orgapachejames-1050/
- The changelog for
3.6.0:
Sorry I messed up, built the wrong SHA-1.
Let's abort this vote,
Sorry for distrurbance.
Le 18/03/2021 à 20:36, Antoine Duprat a écrit :
> +1
>
> Le jeu. 18 mars 2021 à 11:54, Tellier Benoit a écrit :
>
>> +1
>>
>> Le 18/03/2021 à 17:53, Tellier Benoit a écrit
+1
Le 18/03/2021 à 17:53, Tellier Benoit a écrit :
> Hi,
>
> I would like to propose a new vote 3.6.0 release of the Apache James server.
>
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1049:
> https://repository.a
Hi,
I would like to propose a new vote 3.6.0 release of the Apache James server.
You can find:
- The maven release staged in repository.apache.org as the
artifact #1049:
https://repository.apache.org/content/repositories/orgapachejames-1049/
- The changelog for
3.6.0:
Hello Jean,
I do not know if you can do much about it, but your MUA did incorectly
wrapped the previous lines out its answers, quoting some of you replies
and unquoting some of mine. I found it complicated to read.
Le 15/03/2021 à 15:55, Jean Helou a écrit :
> Hi Benoit,
>
>
>> Regarding
Hello Matthieu,
Le 12/03/2021 à 21:14, Matthieu Baechler a écrit :
> Hi,
>
> My answers below.
>
> On Thu, 2021-03-11 at 15:17 +0200, Juhan Aasaru wrote:
>> Hi!
>>
>> There is currently ongoing work to upgrade James to Elasticsearch 7.x
>> See https://github.com/apache/james-project/pull/328
>>
Hello Jean,
Regarding Prometheus setup, we have implemented an optional HTTP
endpoint. I would recommend you to include the following lines in your
webadmin.properties:
extensions.routes=org.apache.james.webadmin.dropwizard.MetricsRoutes
We should then:
- better document this setup
- (provide
+1 I am fine with both proposals
Maybe the documentation needs to be modified to clearly say it.
Benoit
Le 11/03/2021 à 20:34, Juhan Aasaru a écrit :
> If the community agrees then I propose the following.
>
> * we deprecate this functionality in the next release (3.6.0) with a note
> that it
Hi Matthieu, Hi Juhan,
Le 02/03/2021 à 20:36, Matthieu Baechler a écrit :
> Hi Juhan,
>
> On Tue, 2021-03-02 at 11:10 +0200, Juhan Aasaru wrote:
>
> [...]
>
> We probably won't be able to support both versions in the same product
> for a reasonable cost so I propose to drop ElasticSearch 6
Hi Matthieu,
I think that the cut should be done on the later the 15/03, yes.
Regards,
Benoit
Le 02/03/2021 à 20:36, Matthieu Baechler a écrit :
> Hi Juhan,
>
> On Tue, 2021-03-02 at 11:10 +0200, Juhan Aasaru wrote:
>
> [...]
>
> > I think (sadly) ElasticSearch V7 migration (and ES V6
Hey there!
It's been almost a year (!) since we shipped some master code out in a
release (the last release taking me over 3 months!).
As such, I think it would be important, as a project, to make such a
release happen before the next Apache board meeting (mid. April). I
devote myself to perform
Hello there,
I want to thank Jean and Matthieu for their awesome work on the Apache
run CI.
We did discuss it with the @linagora team during our daily, and we would
like to handle eventually all of our contributions through
apache/james-project.
Now the last few days experience makes me fear a
gt;>> To me safety and correctness is much more important than raw
>>> performance so I would like the always-copy implementation to replace
>>> the COW version.
>>>
>>> However, keep in mind that the JMH benchmark figures did not told the
>>>
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 there!
We had been discussing on GitHub recently about an optimization in james
core around the usage of MimeMessage.
Javax.mail MimeMessage is currently used to represent a message of an
email as part of the mail processing in James. It is part of the Mail
interface (mailet-api).
As Mail
Hello Jean,
Nice work!
Le 28/12/2020 à 23:21, Jean Helou a écrit :
> Hello again jamers!
>
> It's time for a new irregular report on the CI effort on apache infra !
>
> Let's start with the good news : today I finally reached a successful build
>
Hello Jean,
Sorry for the late answer.
Le 27/12/2020 à 01:29, Jean Helou a écrit :
> Hi,
>
> While playing around with assemblies, I got an error that vacation mailet
> configuration was missing when I added the JMAP module
>
Le 11/12/2020 à 16:35, Jean Helou a écrit :
I'm in favor for opening a dedicated ticket and merge a disabled version
of this test in order to document the problem.
>>>
>>> it"s been busy and I haven't opened the ticket yet, nor have we managed
>> to
>>> fully fix the issue yet
You're right,
I did not follow up on this.
I just created the INFRA ticket.
https://issues.apache.org/jira/browse/INFRA-21180
As far as I understand, this is not an official release channel but
rather a convenience one.
Cheers,
Benoit
Le 11/12/2020 à 15:18, Jean Helou a écrit :
>>
>> I
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.
>>
>
>
Le 11/12/2020 à 14:53, Matthieu Baechler a écrit :
> Hi,
>
> On Fri, 2020-12-11 at 12:42 +0700, Tellier Benoit wrote:
>> Hello James DEVs !!!
>>
>> I want to start a discussion around
>> https://issues.apache.org/jira/browse/JAMES-3475
>>
>> Our issu
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
> 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,
>>
>>
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
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 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.
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
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
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
>
Le 18/11/2020 à 16:09, Jean Helou a écrit :
> [...]
>> I am not sure where other apache projects source the machines
>>
>> running the CI but at least https://github.com/apache/pulsar-helm-chart
>>> seems to have access to some serious compute power...
>> INFRA is by default not powerful
Le 18/11/2020 à 15:00, Jean Helou a écrit :
>> I would like us to start as part as the release process to publish
>> convenience binaries under apache name, just like some other Apache
>> projects are doing: https://issues.apache.org/jira/browse/INFRA-19650
>
>
> This is a bit of a shameless
Hello,
Following this thread:
I would like us to start as part as the release process to publish
convenience binaries under apache name, just like some other Apache
projects are doing: https://issues.apache.org/jira/browse/INFRA-19650
I propose to ask for rights on apache/james repository
I
Le 18/11/2020 à 03:55, Tobias Verbeke a écrit :
> L.S.
>
> When exploring the getting started guide I noticed the Docker image referred
> to was
>
> docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.5.0
>
> While I very much appreciate and respect the contributions by the
Heelo Jean!
Le 17/11/2020 à 20:37, Jean Helou a écrit :
> Hello again :D
>
> [...]
>
> I suggested creating
>
>> mvn compile -Psort
>
> To make running the sort plugin easier and help make a transition to a
> state where the dependencies are all correctly sorted. To which benoit
> answered
This sounds legitimate to me.
Across the line, there is however the thought that the main - if not
only - delivery of the Apache James project is a mail server.
Things like mailet-api, mailbox, protocols will end up with the same
naming than some over server components like (say) queue.
I
Hello Jean!
Nice to see you around ;-)
Many thanks for what looks like a nice future contribution.
Might you need help, do not hesitate.
Cheers,
Ps: It do not seem like the email was duplicated ^^
Benoit
Le 13/11/2020 à 16:34, Jean Helou a écrit :
> Hello everyone,
>
> I intend to propose
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
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 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
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
>
>[...]
>
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
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 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
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 à
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
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 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
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
:
- 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 à 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
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 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
+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
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:
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 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 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.
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 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 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 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
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 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 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 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 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
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
|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.
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
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 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
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
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
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,
>
>
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
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
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,
>
1 - 100 of 3505 matches
Mail list logo
