Re: Retire Apache James Hupa ?
More on the retirement topic. Getting inspired by https://ant.apache.org/processes.html#Retire:%20Mailing%20List the procedure would be to: - 1. Get a formal vote on server-dev mailing list - 2. Place a RETIRED_PROJECT file marker in the git - 3. Add a note in the project README - 4. Retire the ISSUE trackers (Project names HUPA and POSTAGE) - 5. Announce it on gene...@james.apache.org and announce@apache - 6. Add a notice to the Apache website, if present - 7. Remove releases from downloads.apache.org - 8. Add notices on the Apache release archives (example https://archive.apache.org/dist/ant/antidote/) Note that there is also a procedure to re-activate a previously retired sub-project. Best regards, Benoit TELLIER On 19/07/2021 15:30, Jean Helou wrote: > 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 (0.3.0) dates from 2012 which is an eternity in >> computing. >> - The latest tag on Github is 0.0.3 >> - The pom references 0.0.5-SNAPSHOT suggesting that 0.0.4 release is >> lost :-( >> - This repository is crippled by multiple CVEs (quick dependabot review): >> - CVE-2021-29425 (commons-io) >> - GHSA-m6cp-vxjx-65j6 CVE-2017-7656 CVE-2015-2080 CVE-2017-7657 >> CVE-2019-10241 CVE-2019-10247 (Jetty server) >> - CVE-2020-9447 (gwtupload) >> - GHSA-g3wg-6mcf-8jj6 (jetty-webapp) >> - CVE-2019-17571 (log4j) >> - CVE-2016-131 CVE-2016-3092 (commons-fileupload) >> - Sporadic activity since 2012 >> - Zero to no exchanges for several years on the mailing lists. >> >> From the Readme: >> >>> Hupa is able to discover most of the imap/smtp configuration based on >> the email domain part. When you are prompted to login, type your email >> address and wait few seconds, if you click on the gear button you can >> see the configuration discovered by Hupa, you can modify it if it does >> not match your email provider configuration. Then type your inbox >> password and you will be logged into your email provider servers. >> >>> Hupa is compatible with most email providers, gmail, yahoo, hotmail, >> outlook, exchange, james, etc. >> >> I fail to see the value added compared to other webmails like roundcube, >> rainloops to quote a few... >> >> As such, given that alternatives exists, given that the project is >> likely not mature, unmaintained and unsecure, I propose to retire this >> Apache James subproject. >> >> I will do research on procedures and best practices to do so. I guess a >> formal vote would be necessary. Likely contact Apache Labs were the >> project originated from in 2009... >> >> Best regards, >> >> Benoit TELLIER >> >> >> - >> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org >> For additional commands, e-mail: server-dev-h...@james.apache.org >> >> - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Implement ThreadIdGuessingAlgorithm for the distributed module
Hello Quan, On 19/07/2021 17:59, Quan tran hong wrote: > Hi, > I am starting to implement ThreadIdGuessingAlgorithm for the distributed > module. Because this is a breaking change and I am new to Cassandra also, > therefore I want to have some discussion with you about how to do this. As long as we introduce a new table there is no reason that it creates breaking change, but getting the format right will ease our life down the line. > > For the ones who did not catch up with this work, please have a look at > JMAP Threads specs [1] and my work related to this [2]. > > So my ideas on how to do this: > - Add a needed inputs Cassandra Table for guessing threadId algorithm. > Maybe a table likes: > CREATE TABLE ThreadRelatedTable ( > threadId timeuuid, > messageId timeuuid, > mimeMessageIds SET, > subject text, > PRIMARY KEY (mimeMessageIds, subject) > ); > - Whenever we guess threadId for a new message, we access this table and do > the matching query to get related threadId(if there is) or decide new > message should have a new threadId. > - Whenever we save a new message, we save the thread-related data to this > table. > > This is my first come-up idea. Please express your thoughts about this. Collections are an advanced data modeling tool, that should be used with caution. I am not sure using it in a PRIMARY KEY is a good idea. I am not sure that does what you want (the full primary key should be specified to know which node hold the data. Also, once you found the message related to a thread you want to validate that the subject matches. This can be done on application side (James), and avoids complicated data model. I encourage you to validate your data model using a Cassandra in docker and executing CQL commands locally with CQLSH tool to simulate the queries you whish to do, and learn about your data model before even starting to implement it. IMO sharing CQL commands for creating the table, inserting data in it, and retrieving data from it would be a great follow up to this email. How would you populate the data of that table? Best regards, Benoit > > Best regards, > > Quan > > [1] https://jmap.io/spec-mail.html#threads > [2] https://issues.apache.org/jira/browse/JAMES-3516 > - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Implement ThreadIdGuessingAlgorithm for the distributed module
Hi, I am starting to implement ThreadIdGuessingAlgorithm for the distributed module. Because this is a breaking change and I am new to Cassandra also, therefore I want to have some discussion with you about how to do this. For the ones who did not catch up with this work, please have a look at JMAP Threads specs [1] and my work related to this [2]. So my ideas on how to do this: - Add a needed inputs Cassandra Table for guessing threadId algorithm. Maybe a table likes: CREATE TABLE ThreadRelatedTable ( threadId timeuuid, messageId timeuuid, mimeMessageIds SET, subject text, PRIMARY KEY (mimeMessageIds, subject) ); - Whenever we guess threadId for a new message, we access this table and do the matching query to get related threadId(if there is) or decide new message should have a new threadId. - Whenever we save a new message, we save the thread-related data to this table. This is my first come-up idea. Please express your thoughts about this. Best regards, Quan [1] https://jmap.io/spec-mail.html#threads [2] https://issues.apache.org/jira/browse/JAMES-3516
Re: Retire Apache James Postage ?
Nice catch, +1! Rene. On 19/07/2021 15:33, Jean Helou wrote: 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 absence of mainteners, it could be wise to consider retiring it. Thoughts? I had no idea it even existed :) I feel there is no greater bane than dead/unused/unmaintained code +1 for dropping it jean - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Retire Apache James Hupa ?
Nice catch, +1! Rene. On 19/07/2021 15:30, Jean Helou wrote: 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 (0.3.0) dates from 2012 which is an eternity in computing. - The latest tag on Github is 0.0.3 - The pom references 0.0.5-SNAPSHOT suggesting that 0.0.4 release is lost :-( - This repository is crippled by multiple CVEs (quick dependabot review): - CVE-2021-29425 (commons-io) - GHSA-m6cp-vxjx-65j6 CVE-2017-7656 CVE-2015-2080 CVE-2017-7657 CVE-2019-10241 CVE-2019-10247 (Jetty server) - CVE-2020-9447 (gwtupload) - GHSA-g3wg-6mcf-8jj6 (jetty-webapp) - CVE-2019-17571 (log4j) - CVE-2016-131 CVE-2016-3092 (commons-fileupload) - Sporadic activity since 2012 - Zero to no exchanges for several years on the mailing lists. From the Readme: Hupa is able to discover most of the imap/smtp configuration based on the email domain part. When you are prompted to login, type your email address and wait few seconds, if you click on the gear button you can see the configuration discovered by Hupa, you can modify it if it does not match your email provider configuration. Then type your inbox password and you will be logged into your email provider servers. Hupa is compatible with most email providers, gmail, yahoo, hotmail, outlook, exchange, james, etc. I fail to see the value added compared to other webmails like roundcube, rainloops to quote a few... As such, given that alternatives exists, given that the project is likely not mature, unmaintained and unsecure, I propose to retire this Apache James subproject. I will do research on procedures and best practices to do so. I guess a formal vote would be necessary. Likely contact Apache Labs were the project originated from in 2009... Best regards, Benoit TELLIER - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Breaking changes regarding Thread/get implementation?
Hi Benoit, Sure. I will do it. Quan Vào Th 2, 19 thg 7, 2021 vào lúc 16:32 btell...@apache.org < btell...@apache.org> đã viết: > Hello Quan, > > I have the impression we missed the upgrade instructions [1] related to > your mapping changes when adding the threadId to the ElasticSearch index > [2]. > > This is a breaking change as after that newly indexed documents will > reference a field that does not yet exist on previously created indexes, > we likely need to explicitly modify the mapping. > > Could you carry out this change? > > Best regards, > > Benoit > > [1] > https://github.com/apache/james-project/blob/master/upgrade-instructions.md > [2] https://github.com/apache/james-project/pull/539 > [3] > > https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-mapping.html > > > - > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org > >
Breaking changes regarding Thread/get implementation?
Hello Quan, I have the impression we missed the upgrade instructions [1] related to your mapping changes when adding the threadId to the ElasticSearch index [2]. This is a breaking change as after that newly indexed documents will reference a field that does not yet exist on previously created indexes, we likely need to explicitly modify the mapping. Could you carry out this change? Best regards, Benoit [1] https://github.com/apache/james-project/blob/master/upgrade-instructions.md [2] https://github.com/apache/james-project/pull/539 [3] https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-mapping.html - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
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 absence of mainteners, it could be wise > to consider retiring it. > > Thoughts? > I had no idea it even existed :) I feel there is no greater bane than dead/unused/unmaintained code +1 for dropping it jean
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 (0.3.0) dates from 2012 which is an eternity in > computing. > - The latest tag on Github is 0.0.3 > - The pom references 0.0.5-SNAPSHOT suggesting that 0.0.4 release is > lost :-( > - This repository is crippled by multiple CVEs (quick dependabot review): > - CVE-2021-29425 (commons-io) > - GHSA-m6cp-vxjx-65j6 CVE-2017-7656 CVE-2015-2080 CVE-2017-7657 > CVE-2019-10241 CVE-2019-10247 (Jetty server) > - CVE-2020-9447 (gwtupload) > - GHSA-g3wg-6mcf-8jj6 (jetty-webapp) > - CVE-2019-17571 (log4j) > - CVE-2016-131 CVE-2016-3092 (commons-fileupload) > - Sporadic activity since 2012 > - Zero to no exchanges for several years on the mailing lists. > > From the Readme: > > > Hupa is able to discover most of the imap/smtp configuration based on > the email domain part. When you are prompted to login, type your email > address and wait few seconds, if you click on the gear button you can > see the configuration discovered by Hupa, you can modify it if it does > not match your email provider configuration. Then type your inbox > password and you will be logged into your email provider servers. > > > Hupa is compatible with most email providers, gmail, yahoo, hotmail, > outlook, exchange, james, etc. > > I fail to see the value added compared to other webmails like roundcube, > rainloops to quote a few... > > As such, given that alternatives exists, given that the project is > likely not mature, unmaintained and unsecure, I propose to retire this > Apache James subproject. > > I will do research on procedures and best practices to do so. I guess a > formal vote would be necessary. Likely contact Apache Labs were the > project originated from in 2009... > > Best regards, > > Benoit TELLIER > > > - > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org > >
Retire Apache James Postage ?
Hello all, 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. This subproject: - Have no website page (not deployed) - Have no README - Have no formal release, but a tag named "james-2_20120613" dating from 2012 which is quite old already... - Their exists some alternatives both for JMETER, and Gatling performance testing tools. - Lack of support for recent mail protocols like IMAP and JMAP - Hard to scale blocking architecture (from what I understood?) - No development activity since 2013. - 5 forks in total on github, none of them did extra developments. - Relies on 3.0-beta5-SNAPSHOT which is quite old but also unreleased. Proting postage to a released version would likely be already quite of a fight... - Affected by CVE-2021-29425 (commons-io) Given the maturity of the project, the presence of alternatives, and the absence of development, in the absence of mainteners, it could be wise to consider retiring it. Thoughts? Best regards, Benoit - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Retire Apache James Hupa ?
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 (0.3.0) dates from 2012 which is an eternity in computing. - The latest tag on Github is 0.0.3 - The pom references 0.0.5-SNAPSHOT suggesting that 0.0.4 release is lost :-( - This repository is crippled by multiple CVEs (quick dependabot review): - CVE-2021-29425 (commons-io) - GHSA-m6cp-vxjx-65j6 CVE-2017-7656 CVE-2015-2080 CVE-2017-7657 CVE-2019-10241 CVE-2019-10247 (Jetty server) - CVE-2020-9447 (gwtupload) - GHSA-g3wg-6mcf-8jj6 (jetty-webapp) - CVE-2019-17571 (log4j) - CVE-2016-131 CVE-2016-3092 (commons-fileupload) - Sporadic activity since 2012 - Zero to no exchanges for several years on the mailing lists. >From the Readme: > Hupa is able to discover most of the imap/smtp configuration based on the email domain part. When you are prompted to login, type your email address and wait few seconds, if you click on the gear button you can see the configuration discovered by Hupa, you can modify it if it does not match your email provider configuration. Then type your inbox password and you will be logged into your email provider servers. > Hupa is compatible with most email providers, gmail, yahoo, hotmail, outlook, exchange, james, etc. I fail to see the value added compared to other webmails like roundcube, rainloops to quote a few... As such, given that alternatives exists, given that the project is likely not mature, unmaintained and unsecure, I propose to retire this Apache James subproject. I will do research on procedures and best practices to do so. I guess a formal vote would be necessary. Likely contact Apache Labs were the project originated from in 2009... Best regards, Benoit TELLIER - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r48875 - /release/james/mailets/3.3.0/
Author: btellier Date: Mon Jul 19 07:43:50 2021 New Revision: 48875 Log: Archive mailets 3.3.0 Removed: release/james/mailets/3.3.0/ - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r48874 - /release/james/mailets/3.2.0/
Author: btellier Date: Mon Jul 19 07:43:29 2021 New Revision: 48874 Log: Archive mailets 3.2.0 Removed: release/james/mailets/3.2.0/ - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r48872 - in /release/james/hupa: 0.0.2/ 0.2.0/
Author: btellier Date: Mon Jul 19 07:35:33 2021 New Revision: 48872 Log: Fix Hupa version typo Added: release/james/hupa/0.0.2/ release/james/hupa/0.0.2/hupa-0.0.2.war (with props) release/james/hupa/0.0.2/hupa-0.0.2.war.asc (with props) release/james/hupa/0.0.2/hupa-0.0.2.war.sha512 release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip (with props) release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.asc (with props) release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.sha512 Removed: release/james/hupa/0.2.0/ Added: release/james/hupa/0.0.2/hupa-0.0.2.war == Binary file - no diff available. Propchange: release/james/hupa/0.0.2/hupa-0.0.2.war -- svn:mime-type = application/zip Added: release/james/hupa/0.0.2/hupa-0.0.2.war.asc == Binary file - no diff available. Propchange: release/james/hupa/0.0.2/hupa-0.0.2.war.asc -- svn:mime-type = application/octet-stream Added: release/james/hupa/0.0.2/hupa-0.0.2.war.sha512 == --- release/james/hupa/0.0.2/hupa-0.0.2.war.sha512 (added) +++ release/james/hupa/0.0.2/hupa-0.0.2.war.sha512 Mon Jul 19 07:35:33 2021 @@ -0,0 +1 @@ +5f47e91bfac59f9de5ba238ac993b1d822ce8461a8a66cbd3859c30266c3e7a41d768010ebe540e5b1c7128cba9253609089c492be8c5830633de23a8101696f hupa-0.0.2.war Added: release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip == Binary file - no diff available. Propchange: release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip -- svn:mime-type = application/zip Added: release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.asc == Binary file - no diff available. Propchange: release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.asc -- svn:mime-type = application/octet-stream Added: release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.sha512 == --- release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.sha512 (added) +++ release/james/hupa/0.0.2/hupa-parent-0.0.2-source-release.zip.sha512 Mon Jul 19 07:35:33 2021 @@ -0,0 +1 @@ +0416513682c0e8cb5c78c48312736d984c89406c652c5a2d5109aafe683a19b0c413c9468ce512a9ace4d1c40c1a10671109827d433910a09d086afc155fdd41 hupa-parent-0.0.2-source-release.zip - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r48871 - in /release/james/hupa: ./ 0.2.0/
Author: btellier Date: Mon Jul 19 07:33:13 2021 New Revision: 48871 Log: Host Hupa 0.2.0 release on dowloads.apache.org Added: release/james/hupa/ release/james/hupa/0.2.0/ release/james/hupa/0.2.0/hupa-0.0.2.war (with props) release/james/hupa/0.2.0/hupa-0.0.2.war.asc (with props) release/james/hupa/0.2.0/hupa-0.0.2.war.sha512 release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip (with props) release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.asc (with props) release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.sha512 Added: release/james/hupa/0.2.0/hupa-0.0.2.war == Binary file - no diff available. Propchange: release/james/hupa/0.2.0/hupa-0.0.2.war -- svn:mime-type = application/octet-stream Added: release/james/hupa/0.2.0/hupa-0.0.2.war.asc == Binary file - no diff available. Propchange: release/james/hupa/0.2.0/hupa-0.0.2.war.asc -- svn:mime-type = application/octet-stream Added: release/james/hupa/0.2.0/hupa-0.0.2.war.sha512 == --- release/james/hupa/0.2.0/hupa-0.0.2.war.sha512 (added) +++ release/james/hupa/0.2.0/hupa-0.0.2.war.sha512 Mon Jul 19 07:33:13 2021 @@ -0,0 +1 @@ +5f47e91bfac59f9de5ba238ac993b1d822ce8461a8a66cbd3859c30266c3e7a41d768010ebe540e5b1c7128cba9253609089c492be8c5830633de23a8101696f hupa-0.0.2.war Added: release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip == Binary file - no diff available. Propchange: release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip -- svn:mime-type = application/octet-stream Added: release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.asc == Binary file - no diff available. Propchange: release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.asc -- svn:mime-type = application/octet-stream Added: release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.sha512 == --- release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.sha512 (added) +++ release/james/hupa/0.2.0/hupa-parent-0.0.2-source-release.zip.sha512 Mon Jul 19 07:33:13 2021 @@ -0,0 +1 @@ +0416513682c0e8cb5c78c48312736d984c89406c652c5a2d5109aafe683a19b0c413c9468ce512a9ace4d1c40c1a10671109827d433910a09d086afc155fdd41 hupa-parent-0.0.2-source-release.zip - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r48870 - /release/james/mailets/3.6.0/
Author: btellier Date: Mon Jul 19 07:12:26 2021 New Revision: 48870 Log: Mailet items should be downloadable from ASF download page Added: release/james/mailets/3.6.0/ release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar (with props) release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.sha512 release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar (with props) release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.sha512 release/james/mailets/3.6.0/apache-mailet-base-3.6.0-sources.jar (with props) release/james/mailets/3.6.0/apache-mailet-base-3.6.0-sources.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-base-3.6.0-sources.jar.sha512 release/james/mailets/3.6.0/apache-mailet-base-3.6.0.jar (with props) release/james/mailets/3.6.0/apache-mailet-base-3.6.0.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-base-3.6.0.jar.sha512 release/james/mailets/3.6.0/apache-mailet-crypto-3.6.0-sources.jar (with props) release/james/mailets/3.6.0/apache-mailet-crypto-3.6.0-sources.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-crypto-3.6.0-sources.jar.sha512 release/james/mailets/3.6.0/apache-mailet-crypto-3.6.0.jar (with props) release/james/mailets/3.6.0/apache-mailet-crypto-3.6.0.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-crypto-3.6.0.jar.sha512 release/james/mailets/3.6.0/apache-mailet-standard-3.6.0-sources.jar (with props) release/james/mailets/3.6.0/apache-mailet-standard-3.6.0-sources.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-standard-3.6.0-sources.jar.sha512 release/james/mailets/3.6.0/apache-mailet-standard-3.6.0.jar (with props) release/james/mailets/3.6.0/apache-mailet-standard-3.6.0.jar.asc (with props) release/james/mailets/3.6.0/apache-mailet-standard-3.6.0.jar.sha512 Added: release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar == Binary file - no diff available. Propchange: release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar -- svn:mime-type = application/octet-stream Added: release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.asc == Binary file - no diff available. Propchange: release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.asc -- svn:mime-type = application/octet-stream Added: release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.sha512 == --- release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.sha512 (added) +++ release/james/mailets/3.6.0/apache-mailet-api-3.6.0-sources.jar.sha512 Mon Jul 19 07:12:26 2021 @@ -0,0 +1 @@ +16bdb6bb118751dc9a0a377ff6aa974a9548299d1da3ebd54f081cfe7ad4845bac9d11ceb1a5d26d293b9308859131f3a16aebbd80c297271a7f4061280a2c4a apache-mailet-api-3.6.0-sources.jar Added: release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar == Binary file - no diff available. Propchange: release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar -- svn:mime-type = application/octet-stream Added: release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.asc == Binary file - no diff available. Propchange: release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.asc -- svn:mime-type = application/octet-stream Added: release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.sha512 == --- release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.sha512 (added) +++ release/james/mailets/3.6.0/apache-mailet-api-3.6.0.jar.sha512 Mon Jul 19 07:12:26 2021 @@ -0,0 +1 @@ +3a1b92a4537b4756135eddfa9ba35117a086a764b0a179f6a43ef1eb68c46387107dfd3029028fc373ebb81a76a6ba0846ba33a80fa7ac1190bc4f6a7714fe58 apache-mailet-api-3.6.0.jar Added: release/james/mailets/3.6.0/apache-mailet-base-3.6.0-sources.jar == Binary file - no diff available. Propchange: release/james/mailets/3.6.0/apache-mailet-base-3.6.0-sources.jar --
