[jira] [Commented] (JAMES-4022) James server is getting crashed or stopped after 20 mins or with load

[ https://issues.apache.org/jira/browse/JAMES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829944#comment-17829944 ] Jean Helou commented on JAMES-4022: --- can you provide the steps to reproduce ? * information

[jira] [Commented] (JAMES-3978) Investigate using develocity to improve james build

[ https://issues.apache.org/jira/browse/JAMES-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823786#comment-17823786 ] Jean Helou commented on JAMES-3978: --- a formal vote has validated an experimentation enabling develocity

Re: vote : Remote build cache experiment

why my comment was left unanswered :facepalm: cheers jean Le mer. 28 févr. 2024 à 19:57, Jean Helou a écrit : > hello, > > I'm happy that the vote has succeded with 3 votes (I'm an idiot and forgot > to send my vote in a separate message T_T) > > I'll ask infra to proceed

Re: Result of Proof Of Concept for Redis Event bus user notifications

? > > Best regards, > > Benoit TELLIER > > On 01/03/2024 13:17, Jean Helou wrote: > > Hello  > > > > I'm not (yet) familiar with the event bus :) > > > > Out of curiosity could you describe what made you chose redis and what > > other system

Re: Result of Proof Of Concept for Redis Event bus user notifications

Hello  I'm not (yet) familiar with the event bus :) Out of curiosity could you describe what made you chose redis and what other systems you considered ? What characteristics you thought would match well with the problem. I'm interested in part because there is a Jira to implement the event

Re: vote : Remote build cache experiment

for your enthusiastic effort on the topic. > > Cheers, > > Quan > > Vào Th 3, 20 thg 2, 2024 vào lúc 16:07 Rene Cordier > > đã viết: > > > +1, > > > > If there is a chance to make our builds faster, I say we take it! Thanks > > for this work

Build metrics

Hi fellows, The Develocity integration of james-project build has now been running for long enough that we can start seeing interesting things beyond the raw build scans. First we can give a short look at build trends

vote : Remote build cache experiment

Hello devs ! I have not yet moved forward with enabling remote caching for the build and tests in general. It is unclear to me if you are ok with trying it from the previous discussion. So I'll call a more formal vote: Are you ok with experimenting enabling remote build cache for james (ci

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

Hello Eugen, Libraries IMO should be released with support for older versions versions. > Not every project can use the latest and greatest JVM. > And I don't think low level libraries (mime4j) will benefit a lot from > new Java language features. Just to clarify : what do you mean by libraries

Re: Develocity

equires > > extra work, efforts and attention yes, but I hardly see how else we can > > go safely forward on this. But somebody else has a better idea maybe? :) > > > > Regards, > > > > Rene. > > > > On 2/7/24 02:58, Jean Helou wrote: > > > Thanks fo

Re: Develocity

757 from cache, saving at least 3m 11s > > Thank you for the initiative :-) > > Quan > > Vào Th 3, 6 thg 2, 2024 vào lúc 14:48 Jean Helou đã > viết: > > > Hi devs, > > > > I realized this morning that I initiated the conversation on the wrong

Fwd: Develocity

- From: Jean Helou Date: Mon, Feb 5, 2024 at 3:52 PM Subject: Develocity To: James Users List Hello fellow james devs, I'm not sure how much context to provide in the email you can read more in https://issues.apache.org/jira/projects/JAMES/issues/JAMES-3978?filter=allopenissues TLDR; A few

[jira] [Updated] (JAMES-3978) Investigate using develocity to improve james build

[ https://issues.apache.org/jira/browse/JAMES-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated JAMES-3978: -- Description: Hello, A while ago I noticed [this announcement|https://news.apache.org/foundation

[jira] [Updated] (JAMES-3978) Investigate using develocity to improve james build

[ https://issues.apache.org/jira/browse/JAMES-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated JAMES-3978: -- Description: Hello, A while ago I noticed [this announcement|https://news.apache.org/foundation

[jira] [Commented] (JAMES-3978) Investigate using develocity to improve james build

[ https://issues.apache.org/jira/browse/JAMES-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813731#comment-17813731 ] Jean Helou commented on JAMES-3978: --- benchmark for the first naive approach   mvn clean build cache

[jira] [Updated] (JAMES-3978) Investigate using develocity to improve james build

[ https://issues.apache.org/jira/browse/JAMES-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated JAMES-3978: -- Attachment: image-2024-02-02-16-31-24-883.png > Investigate using develocity to improve james bu

[jira] [Updated] (JAMES-3978) Investigate using develocity to improve james build

[ https://issues.apache.org/jira/browse/JAMES-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated JAMES-3978: -- Attachment: image-2024-02-02-16-30-20-026.png > Investigate using develocity to improve james bu

[jira] [Created] (JAMES-3978) Investigate using develocity to improve james build

Jean Helou created JAMES-3978: - Summary: Investigate using develocity to improve james build Key: JAMES-3978 URL: https://issues.apache.org/jira/browse/JAMES-3978 Project: James Server Issue

Re: Call for vote: Apache James 3.7.5

same +1 as for 3.8.1 Le mer. 10 janv. 2024 à 12:11, Karsten Otto a écrit : > -1 > > I propose to also fix JAMES-3968 in the next release, which is a > critical mail loss bug. This way we can avoid another release > immediately after. > > Cheers, > Karsten > > On 09.01.24 9:15 AM, Benoit TELLIER

Re: Call for vote: Apache James 3.8.1

; > > > FYI Karsten already proposed fixes for that issue that have been > > approved and will be part of the releases. It's just a matter now of > > getting a green build from a rather a bit capricious CI^^' > > > > Regards, > > > > Rene. > > >

Re: Call for vote: Apache James 3.8.1

a hotfix jean Le mer. 10 janv. 2024 à 16:44, btell...@linagora.com a écrit : > I just merged the changelog updates, this should be better now. > > On 10/01/2024 11:26, Jean Helou wrote: > > hmm the linked changelog doesn't list any unreleased changes is that > normal >

Re: Call for vote: Apache James MIME4J 0.8.10

+1 Le mar. 9 janv. 2024 à 03:50, Quan tran hong a écrit : > +1 > > Cheers, > > Quan > > Vào Th 2, 8 thg 1, 2024 vào lúc 21:36 Benoit TELLIER < > btell...@apache.org> > đã viết: > > > Hi, > > > > I would like to propose a new vote for 0.8.10 release of the Apache > > MIME4J library. > > > >

Re: Call for vote: Apache James 3.8.1

hmm the linked changelog doesn't list any unreleased changes is that normal ? Le mar. 9 janv. 2024 à 09:17, Benoit TELLIER a écrit : > Hi, > > I would like to propose a new vote for 3.8.1 release of the Apache James > server. > > You can find: > > - The maven release staged in

Re: Proposal about deprecation and removal

looks like my reploy below never reached the list Le lun. 27 nov. 2023 à 15:04, Jean Helou a écrit : > I'm all for it as long as we give a fighting chance to users :) > > I see 3 different user population with regard to spring support > > - basic users who want an pre-assembl

OpenJPA

Hello, I have been following the discussion on pg mailbox but every jpa mention makes me think of how bad I found the developer experience with open jpa when playing with scaling-smtp. (having to set the agent manually for tests in the ide is a pain. having to list the classes to instrument isn't

Re: Building a PostgreSQL mailbox for James?

I somehow messed up my email config and the following message never reached the list (but never got a nack either so it took me a week and 2 emails without response to detect the problem) Hello Benoit I think having a postgresql backed mailbox server sounds great  It should not come as a

[jira] [Created] (JAMES-3877) Allow to configure jpa pool max connections in juice module

Jean Helou created JAMES-3877: - Summary: Allow to configure jpa pool max connections in juice module Key: JAMES-3877 URL: https://issues.apache.org/jira/browse/JAMES-3877 Project: James Server

[jira] [Resolved] (JAMES-3836) Proposal: Improved mail repository loading

[ https://issues.apache.org/jira/browse/JAMES-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou resolved JAMES-3836. --- Resolution: Fixed > Proposal: Improved mail repository load

[jira] [Created] (JAMES-3836) Proposal: Improved mail repository loading

Jean Helou created JAMES-3836: - Summary: Proposal: Improved mail repository loading Key: JAMES-3836 URL: https://issues.apache.org/jira/browse/JAMES-3836 Project: James Server Issue Type

[jira] [Commented] (JAMES-3793) OOM when loading a very large object from S3?

[ https://issues.apache.org/jira/browse/JAMES-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574924#comment-17574924 ] Jean Helou commented on JAMES-3793: --- Regarding the second part of the issue, it would be nice to  crash

[jira] [Comment Edited] (JAMES-3793) OOM when loading a very large object from S3?

[ https://issues.apache.org/jira/browse/JAMES-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574919#comment-17574919 ] Jean Helou edited comment on JAMES-3793 at 8/3/22 8:46 PM: --- +1 for a hard crash

[jira] [Commented] (JAMES-3793) OOM when loading a very large object from S3?

[ https://issues.apache.org/jira/browse/JAMES-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574919#comment-17574919 ] Jean Helou commented on JAMES-3793: --- +1 for a hard crash on non recoverable errors. The Scala standard

Merging

Hello committers, So I have a couple MRs approved CI is unhappy for now but I hope I can get to a state where merging is ok at some point. I realize I am unsure what the merge policy is. Looking at the repo history it seems to be rebase & merge ( fully linearized history ) but I wonder how other

Re: ElasticSearch upgrade to 8.2

2. Today we could add an extension mechanism exposing metrics and > enabling exports. > > Concretely, takes a dropwizard MetricRegistry in, outputs metrics out. > > The downside is that we enforce the dropwizard choice onto out users, > thus making it harder to change this component when required.

Re: MailstoreApi (was Re: ElasticSearch upgrade to 8.2)

to address it during our next session, see attached picture of our wip marker :D Regards, Jean > Regards, > > Benoit > > On 10/06/2022 15:53, Benoit TELLIER wrote: > > Hello Jean, > > > > Answers inlined. > > > > On 10/06/2022 1

Re: OpenTelemetry (was Re: ElasticSearch upgrade to 8.2)

hi, I did not read much about the topic, but I got the impression that using > OpenTelemetry requires to use OpenTelemetry server and integrations > happens in there. > > > https://grafana.com/blog/2022/05/10/how-to-collect-prometheus-metrics-with-the-opentelemetry-collector-and-grafana/ > > This

Re: MailstoreApi (was Re: ElasticSearch upgrade to 8.2)

Thanks a lot for the additional context, benoit I have added that as a comment on the issue to make it more readily discoverable. When we reach cleanup phase, I'll try to add some documentation to the interfaces in the code. Cheers jean > One case is "it was mentioned in the server

[jira] [Commented] (JAMES-2418) Store repository APIs that are being used

[ https://issues.apache.org/jira/browse/JAMES-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552639#comment-17552639 ] Jean Helou commented on JAMES-2418: --- Additional context that popped up in the mailing list while I

Re: ElasticSearch upgrade to 8.2

Hey benoit, First I am happy to see this component raise such interest, and gets so > much attention! For the record, I want to establish that I don't use nor actually like ES for such use cases so the ES part doesn't really matter to me. I do care a lot about metrics collection and I generally

MailstoreApi (was Re: ElasticSearch upgrade to 8.2)

I fork the thread to respond on the MailRepository part :D > fun quiz can you tell looking > > only at the documentation and code comments the difference between : > > MailRepositoryStore, MailRepositoryUrlStore and MailRepository all of > which > > are in mailrepository-api ) > Game accepted.

Re: ElasticSearch upgrade to 8.2

Hello all, >We IMO need to add that direct reporting (for logs or metrics) from the application to ElasticSearch is an anti-pattern, and pretty uncommon. Doesn't sound quite right : Pushing logs from the app the ES is exactly what the whole ELK thing is all about. Given the amount of literature

Re: "Branding" of pulsar-cassandra-smtp-relay

riteTable. We would likely > miss a corresponding XML user repository but this should not be hard to > implement if needed. > > For the artifact name, +1 for scaling-pulsar-smtp. > > Best regards, > > Benoit > > On 11/05/2022 04:50, Jean Helou wrote: > > Hel

Re: "Branding" of pulsar-cassandra-smtp-relay

Hello Benoit ! Matthieu and I are trying to create a server instance to host our family's email :) Being the geeks that we are, we are not satisfied with a single node JPA deployment and want to preserve the scalability and resilience properties of distributed james while minimizing the run cost

[jira] [Commented] (JAMES-3760) MailRepositoryContract is not cleaning the created Mails

[ https://issues.apache.org/jira/browse/JAMES-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534300#comment-17534300 ] Jean Helou commented on JAMES-3760: --- Wouldn't that make it tricky to distinguish between "exp

[jira] [Commented] (JAMES-3700) Dead letter policy for the Pulsar MailQueue

[ https://issues.apache.org/jira/browse/JAMES-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505027#comment-17505027 ] Jean Helou commented on JAMES-3700: --- I'm passing by and it seems the related merge request is merged

[jira] [Created] (JAMES-3721) Browse on the Pulsar mailqueue fails with ObjectNotFoundException

Jean Helou created JAMES-3721: - Summary: Browse on the Pulsar mailqueue fails with ObjectNotFoundException Key: JAMES-3721 URL: https://issues.apache.org/jira/browse/JAMES-3721 Project: James Server

[jira] [Commented] (JAMES-3700) Dead letter policy for the Pulsar MailQueue

[ https://issues.apache.org/jira/browse/JAMES-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494080#comment-17494080 ] Jean Helou commented on JAMES-3700: --- The schema way is really neat but I feel a small word of warning

[jira] [Commented] (JAMES-3698) Pulsar MailQueue should support deletion of scheduled messages.

[ https://issues.apache.org/jira/browse/JAMES-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494074#comment-17494074 ] Jean Helou commented on JAMES-3698: --- I might be wrong but I think this is fixed no ? > Pul

[jira] [Comment Edited] (JAMES-3696) Solve instable test for the pulsar mail queue

[ https://issues.apache.org/jira/browse/JAMES-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476117#comment-17476117 ] Jean Helou edited comment on JAMES-3696 at 1/14/22, 12:45 PM: -- > This ma

[jira] [Commented] (JAMES-3696) Solve instable test for the pulsar mail queue

[ https://issues.apache.org/jira/browse/JAMES-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476117#comment-17476117 ] Jean Helou commented on JAMES-3696: --- > This makes build profiles harder to grasp, issues har

[jira] [Commented] (JAMES-3696) Solve instable test for the pulsar mail queue

[ https://issues.apache.org/jira/browse/JAMES-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472805#comment-17472805 ] Jean Helou commented on JAMES-3696: --- The tests actually already account for the eventual consistency

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

Hello, I'm obviously favorable to using pulsar :) You mention : > I think a good long term objective for the PMC is to drop RabbitMQ in favor of pulsar And in the ADR you also mention deprecating the RabbitMQ component. Can you clarify which implementations would be preserved/dropped (I'm

[jira] [Comment Edited] (JAMES-3687) Implements Apache Pulsar based Mailqueue

[ https://issues.apache.org/jira/browse/JAMES-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472650#comment-17472650 ] Jean Helou edited comment on JAMES-3687 at 1/11/22, 10:52 AM: -- all

[jira] [Commented] (JAMES-3687) Implements Apache Pulsar based Mailqueue

[ https://issues.apache.org/jira/browse/JAMES-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472650#comment-17472650 ] Jean Helou commented on JAMES-3687: --- all these already have a wait time built in to account

Re: [jira] [Commented] (JAMES-3689) JMSCacheableMailQueue remove is buggy

MES-3689 > > Project: James Server > > Issue Type: Bug > >Reporter: Jean Helou > >Priority: Major > > > > While implementing the pulsar mailqueue we accidentally discovered this &g

[jira] [Updated] (JAMES-3689) JMSCacheableMailQueue remove is buggy

[ https://issues.apache.org/jira/browse/JAMES-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated JAMES-3689: -- Description: While implementing the pulsar mailqueue we accidentally discovered this bug

[jira] [Created] (JAMES-3689) JMSCacheableMailQueue remove does not works for the the first recipient

Jean Helou created JAMES-3689: - Summary: JMSCacheableMailQueue remove does not works for the the first recipient Key: JAMES-3689 URL: https://issues.apache.org/jira/browse/JAMES-3689 Project: James

[jira] [Updated] (JAMES-3687) Implements Apache Pulsar based Mailqueue

[ https://issues.apache.org/jira/browse/JAMES-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated JAMES-3687: -- Description: An apache pulsar based mailqueue offers a different set of compromises over the existing

[jira] [Created] (JAMES-3687) Implements Apache Pulsar based Mailqueue

Jean Helou created JAMES-3687: - Summary: Implements Apache Pulsar based Mailqueue Key: JAMES-3687 URL: https://issues.apache.org/jira/browse/JAMES-3687 Project: James Server Issue Type

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

+1 On Thu, Dec 2, 2021 at 5:57 AM btell...@linagora.com wrote: > Hopefully rendered correctly in plain text... > > - > > Hello Jamers! > > As part of my work at Linagora, we are looking toward > - better integrating James within our product suite and for

[jira] [Commented] (JAMES-3487) Configure MimeMessageInputStreamSource THRESHOLD

[ https://issues.apache.org/jira/browse/JAMES-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437838#comment-17437838 ] Jean Helou commented on JAMES-3487: --- It would definitely be an improvement over the current situation

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

Hello devs, I switch threads because I agree with the removal of the FS based mailqueue but still find the maildir removal to be a bit more difficult. Quoting from the other thread at https://www.mail-archive.com/server-dev@james.apache.org/msg70960.html What protocols are supported by the 2.3

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

i < > rouaz...@apache.org> wrote: > > > +1 > > > > Le 06/09/2021 à 14:54, Jean Helou a écrit : > > > awesome :) > > > > > > On Mon, Sep 6, 2021 at 1:52 PM btell...@apache.org < > btell...@apache.org> >

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

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 migrat

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

Hello benoit, > There are some alternatives: embedded activeMQ has zero dependencies. > Furthermore migrating is easy: just migrate with an empty queue - which > can be done easily with a SMTP downtime. > > Also the component is deprecated for 1.5 years, given the many flows it > have, given

Re: [VOTE] Retire Apache James HUPA

+1 Le ven. 23 juil. 2021 à 11:28, Antoine Duprat a écrit : > +1 > > Le ven. 23 juil. 2021 à 11:01, 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] >

Re: [VOTE] Retire Apache James Postage

+1 Le ven. 23 juil. 2021 à 11:28, Antoine Duprat a écrit : > +1 > > Le ven. 23 juil. 2021 à 11:03, 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 Postage retirement. > > > > [1] >

Re: Retire Apache James Postage ?

Hi benoit While looking at unmaintained pieces of code that might have now better > alternatives, being hosted under the Apache James umbrella, I cannot but > think about Apache Postage. > > Given the maturity of the project, the presence of alternatives, and the > absence of development, in the

Re: Retire Apache James Hupa ?

I think this is an excellent idea ! +1 thank you benoit ! jean On Mon, Jul 19, 2021 at 10:16 AM btell...@apache.org wrote: > Hello all, > > While fixing our download pages following some infra bot complains, I > ended up fixing the downloads for Apache James Hupa. > > - The latest release

Re: Should we have a checkstyle for Scala?

ames-project/pull/538 > > Cheers, > Tung > > On Tue, Jul 13, 2021 at 6:59 PM Jean Helou wrote: > > > > Yes, I did. I forked this plugin and manual change scala version on > > local. > > > As I wrote > > > > > > > sorry I didn't catch tha

Re: Should we have a checkstyle for Scala?

g to use :) can you try upgrading scalafix version from 9.23 at least to 9.26 (even better to 9.29 in your local build ? [1] https://github.com/scalacenter/scalafix/pull/1334/files cheers, jean Thank you, > > On Tue, Jul 13, 2021 at 6:34 PM Jean Helou wrote: > > > This is my configur

Re: Should we have a checkstyle for Scala?

used ? > > [1] https://github.com/evis/scalafix-maven-plugin#tips-and-tricks > > > > I don't use the maven plugin itself, all my scala projects use either SBT > > or mill so I don't have this layer of issues. > > > > Regards, > > Jean > > >

Re: Should we have a checkstyle for Scala?

ds, Jean [1] https://github.com/evis/scalafix-maven-plugin/pull/12 > > Regards, > Tung > > On Fri, Jun 25, 2021 at 2:44 PM Jean Helou wrote: > > > Hi tung, > > > > Have you looked at scalafix[1]? it seems to be much more actively > > maintained than scalas

Re: Should we have a checkstyle for Scala?

Hi tung, Have you looked at scalafix[1]? it seems to be much more actively maintained than scalastyle and I feel that it's scope overlaps scalatyle's quite a bit... [1]https://github.com/scalacenter/scalafix Regards, jean On Fri, Jun 25, 2021 at 8:14 AM tungtv...@gmail.com wrote: > Hello

Re: Code organisation: makes guice application easier to discover

Thank you benoit for clarifying the goals you are reaching for, it's very clear for me now I agree with the goal, the plan and the first step :D regards, Jean On Wed, Jun 9, 2021 at 7:15 AM btell...@apache.org wrote: > Hello Jean! > > On 08/06/2021 17:21, Jean Helou wrote: >

Re: What's the reason for having Username's constructor private?

Hello Andreas, We have an environment where usernames can be *any* character thus the > rules enforced by Username does not apply to us. We were thinking about > subclassing it, until we saw it has a private constructor signaling that it > isn't meant for extending. > Do you mean

Re: Code organisation: makes guice application easier to discover

Hi benoit ! On my crusade to reorganize James code related to Guice apps (and > promote their adoption), I come to the next item of the tick list (after > ZIP packaging, JIB packaging to enable distribution). > These were great improvements > I would like to make those application easier to

Re: Removal of stale branches for apache/james projects

Thank you Benoit ! On Mon, Jun 7, 2021 at 4:01 AM btell...@apache.org wrote: > Hey there, > > I deleted the before mentioned branches. > > I opened https://issues.apache.org/jira/browse/INFRA-21969 for the empty > project removal. > > Cheers, > > Benoit > > O

Re: Removal of stale branches for apache/james projects

On Wed, Jun 2, 2021 at 9:54 AM btell...@apache.org wrote: > > A bit of house cleaning might be beneficial Without objections, I > will clean these brnches in a few days. > +9001 (cuz it's over 9000) ! > Furthermore the following projects do not have code associated to them: > > -

Re: Github token for Apache JAMES ASF build

> I just set up additional builds for JSPF, JSPF, JSIEVE and MIME4J > projects, and successfully used the asf-ci tokens. > > Is there any reasons not to switch these two projects to use the ASF > tokens too? > Not that I know of, but it is possible that the tokens were unavailable when the builds

[jira] [Commented] (JAMES-3569) RecipientRewriteTable sometimes drops attributes from emails

[ https://issues.apache.org/jira/browse/JAMES-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330234#comment-17330234 ] Jean Helou commented on JAMES-3569: --- Hmm  I don't know, the processing for rewrites to local addresses

[jira] [Created] (JAMES-3569) RecipientRewriteTable sometimes drops attributes from emails

Jean Helou created JAMES-3569: - Summary: RecipientRewriteTable sometimes drops attributes from emails Key: JAMES-3569 URL: https://issues.apache.org/jira/browse/JAMES-3569 Project: James Server

[jira] [Commented] (JAMES-3330) Clarify Recipient Rewrite Table Configuration (recipientrewritetable.xml)

[ https://issues.apache.org/jira/browse/JAMES-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329408#comment-17329408 ] Jean Helou commented on JAMES-3330: --- it feels like this has been completed, can it be closed

[jira] [Commented] (JAMES-3565) Publish and use apache/james docker images

[ https://issues.apache.org/jira/browse/JAMES-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322671#comment-17322671 ] Jean Helou commented on JAMES-3565: --- Here is what I had in mind when I answered on the mailing list

Re: apache/james on docker hub.

Hi benoit, > This would look like what Juhan proposed in > https://issues.apache.org/jira/browse/JAMES-3565 ... > > Thoughts? > interesting, I'll comment with ideas over there thanks jean

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

> > I am about to conclude the 3.6.0 release (publish the website & announce) > :rocket: However I would like the website to advertise the maintained, apache > images rather than the unmaintained ones of an undisclosed third party. > > I imagine the changes in >

Re: apache/james on docker hub.

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 propose to ask for rights on apache/james repository > >>

Re: [Vote] Call for vote: Apache Mime4J 0.8.4

Hi benoit, The changelog has not been updated which is a bit sad (and i know it's painful to do but it's s helpful for developers who use the library) On a semi-related note : the release notes have not been updated either but that last file actually seems to be totally out of sync with the

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

go ! +1 :) On Tue, Apr 6, 2021 at 10:27 AM Antoine Duprat wrote: > +1 > > Le mar. 6 avr. 2021 à 09: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

Re: [BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]'

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. Unfortunately the Jenkinsfile currently in the staging branch of james-site is out of date (the

Re: Remove functionality that saves James metrics into Elasticsearch

Hi Benoit, > 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 > Thanks! I'll have a look. > We should then:

Re: Remove functionality that saves James metrics into Elasticsearch

Hello all, I agree that ES is not the best tool for metrics but it's implemented, documented and demonstrated - https://james.apache.org/server/metrics.html - https://james.apache.org/server/config-elasticsearch.html -

Re: Time for a 3.6.0 release

> > - First, previous release had been rejected once. And one time where we > struggle to get the approval on time. > - Second, the numerous maven project counts makes the upload (mvn > deploy / mvn release prepare / perform) long. I generally plan a day, > and do it on my laptop not to copy my

Re: The case of javax.mail MimeMessage CopyOnWrite optimization

> for both entities. The underlying MimeMessage may - or may not be > >> modified. > >> > >> In order to prevent MimeMessage duplication in the event the > >> underlying > >> MimeMessage is not modified, a Copy On Write mechanism was introduced > >

Re: Jenkins CI setup

oduce a green build on my local > computer, while it works pretty smoothly on the CI. > > Raphaël. > > Le 14/01/2021 à 09:37, Jean Helou a écrit : > >> My 2 cents trying to bring a little force in this nice project :) > >> > > Thanks Raphaël :) > > > > A

Re: Jenkins CI setup

kerfiles without finding anything > that > > looked related to memory configuration of maven itself, If people who run > > the build locally with success or on their own CI could check the > MVN_OPTS > > and let me know if they override maven's Xmx itself I would appreciate

Re: Jenkins CI setup

lf I would appreciate it. thanks for your help jean On Tue, Dec 29, 2020 at 9:10 AM Jean Helou wrote: > Hi Benoit, > > As someone operating another CI, I want to play even unstable test on >> every runs. Is there some adaptation needed to do this? >> > > Yes you will

Re: IMAP Fetch behavior on not found messages

> > > When doing a fetch with some > non existing messages Cyrus will do a best effort and return the > existing messages whereas James will return a BAD response. I would preserve Cyrus's behavior as a defacto standard, not honoring this incurs the risk of breaking existing client software

Re: IMAP Fetch behavior on not found messages

> > The discussion can be found here: > https://github.com/linagora/gatling-imap/pull/3 > actually it's here https://github.com/linagora/gatling-imap/pull/37 I think the url got truncated :)

Re: linagora Docker images

Hi jamers, Cleaning up my mailbox, I stumbled on this subject. I was actually looking into how the docker images are currently created, in order to add one for my own (pure smtp relay) assembly. Work needs to be done on that. I'll open a INFRA ticket to get the > permission. Commiter conducting

  1   2   >