. And likely more
features too :) (like the JMAP protocol for example depending on the
flavor of James?)
Well there is many reasons to upgrade the version of an old software.
But that mainly depends as well about your usage of it, and the time you
are ready to invest in it, cause a migration from those 2
Hello James users,
Happy new year 2024 !!!
I have been using James 2.2.0 in production for years. I am new to
this product. We upgraded to use Java 8 too. Can this James 2.2 work with
Java 11 too? Additionally, could you please help in understanding, what
are the benefits of upgrading to James
a while ago (Antoine Duprat) and in our company, we would be glad for
such an upgrade as well.
Might need a bit of work but the project could definitely benefit from
it: records (finish the long verbose POJOs), pattern matching, better GC
handling, etc.
Would other people be interested about it too
. Should we think about upgrading
to at least the next LTS, JDK 17? (or why even not the current LTS,
which is the JDK 21?) I saw it being asked by a community member on a PR
a while ago (Antoine Duprat) and in our company, we would be glad for
such an upgrade as well.
Might need a bit of work
not the current LTS, which is the JDK 21?) I saw it being asked by a community
member on a PR a while ago (Antoine Duprat) and in our company, we would be glad for such an upgrade
as well.
Might need a bit of work but the project could definitely benefit from it: records (finish the long
verbose
gt; >
> >
> > Le nov. 6, 2023 4:47 AM, de Rene Cordier Hello guys,
> >
> > Well currently James is based on JDK 11. Should we think about upgrading
> > to at least the next LTS, JDK 17? (or why even not the current LTS,
> > which is the JDK 21?) I saw it being
a while ago (Antoine Duprat) and in our company, we would be glad for
such an upgrade as well.
Might need a bit of work but the project could definitely benefit from
it: records (finish the long verbose POJOs), pattern matching, better GC
handling, etc.
Would other people be interested about it too
be glad for
such an upgrade as well.
Might need a bit of work but the project could definitely benefit from
it: records (finish the long verbose POJOs), pattern matching, better GC
handling, etc.
Would other people be interested about it too? Is it a problem for some
others in the community?
Rene
and in our company, we would be glad for
> such an upgrade as well.
>
> Might need a bit of work but the project could definitely benefit from
> it: records (finish the long verbose POJOs), pattern matching, better GC
> handling, etc.
>
> Would other people be interested about it
for
such an upgrade as well.
Might need a bit of work but the project could definitely benefit from
it: records (finish the long verbose POJOs), pattern matching, better GC
handling, etc.
Would other people be interested about it too? Is it a problem for some
others in the community?
Rene
Thanks for this release! I have an instance of James 3.3.0 using maildir
for the mailboxes. I was hoping to upgrade to 3.7.0 and convert to JPA
(Derby) using the instructions here:
https://james.apache.org/server/3/upgrade-database.html.
Is this still a viable option? The mailboxcopier
org> schrieb am Do., 8. März 2018 um
08:53 Uhr:
> Hi Andrej,
>
> It's definitively something we have to do (alongside Cassandra 3
> upgrade), but we are currenlty working on Quota features and Spam
> detection right now, so we don't have time to handle that for now.
>
> Of
Hi Andrej,
It's definitively something we have to do (alongside Cassandra 3
upgrade), but we are currenlty working on Quota features and Spam
detection right now, so we don't have time to handle that for now.
Of course, if you want to look at this task we can offer our help.
Cheers
Dear all,
is there any plans to upgrade the elasticsearch client compatibility of
James to newer versions like 5 or even 6? Running with an Elasticsearch
5.x.x gives me this Error message: "IllegalStateException: Received message
from unsupported version: [2.0.0] minimal compatible ve
he newest version of these jar is in
> the 3.0.1 downloadable ZIP.
>
> Cheers,
>
> Benoit
>
> Le 02/12/2017 à 10:01, Mark Gordon a écrit :
> > What is the best method to upgrade from 3.0.0 to 3.0.1 without lo
hat is the best method to upgrade from 3.0.0 to 3.0.1 without loosing
> current configuration?
>
> thanks,
> mark
>
-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-m
What is the best method to upgrade from 3.0.0 to 3.0.1 without loosing
current configuration?
thanks,
mark
--
Mark Gordon <m...@ordertech.com>
OrderTech Corporation | 819 W Fairmont Dr Ste 2 | Tempe, AZ 85282
*o:* (480) 285-1403 <4802851403> | *f:* (480) 464-5824 <4804645824>
Hi,
Anybody knows how to upgrade from James 2.2.0 to newest stable version?
Are there any descriptions somewhere?
Is this the correct forum to ask?
Med venlig hilsen / Best regards
Christian Rozet
Beskrivelse: cid:image001.gif@01CA2F91.442D3FE0
Beskrivelse: tieto
wrote:
Hi Roy,
2.3.2 is still working withe servername. Its just deprecated...
Bye,
Norman
2010/7/2 Roy Smith roy.smith@googlemail.com:
I'm trying to upgrade from 2.3.1 to 2.3.2 but the new release is spitting
out my config.xml file. eg domainname is now servername etc.
I can't
,
2.3.2 is still working withe servername. Its just deprecated...
Bye,
Norman
2010/7/2 Roy Smith roy.smith@googlemail.com:
I'm trying to upgrade from 2.3.1 to 2.3.2 but the new release is spitting
out my config.xml file. eg domainname is now servername etc.
I can't see anything
I'm trying to upgrade from 2.3.1 to 2.3.2 but the new release is spitting
out my config.xml file. eg domainname is now servername etc.
I can't see anything in the documentation which lists the config file
changes.
Hi Roy,
2.3.2 is still working withe servername. Its just deprecated...
Bye,
Norman
2010/7/2 Roy Smith roy.smith@googlemail.com:
I'm trying to upgrade from 2.3.1 to 2.3.2 but the new release is spitting
out my config.xml file. eg domainname is now servername etc.
I can't see anything
I'd like to know what the process is for upgrading to the new mailet 2.4
api/base 1.0 implementation. The http://james.apache.org/mailet/api/index.html
page only contains a brief blurb about inserting the api jar file in the front
of the classpath. Since there aren't any explicit classpath
Dain Kaplan ha scritto:
The memory settings were set by someone else, I assumed he had a reason,
but he could have been overzealous in his pursuit. Though we do have
230 domains, and process a lot of mail.
ok.
Anyways, I looked at the configuration files, and there are two salient
should
copy
it as-is in your configuration file. The way you mixed the
objectstorage
inside the mailstore is not ok.
Ah, perhaps this is it. In the upgrade document, it only says:
Step 2.5 : Move the objectstore
Move the objectstore config into the mailstore config.
But perhaps I
outofmemory (with
a different error than the swap space one?)?
I read about the error above very often in this list
(ChunkPool::allocate). Each time I suggest to not use an Xmx too big for
the machine and to upgrade the jvm to the latest available. IIRC I never
received a feedback about the solution
is making your 2.3.1 to run outofmemory (with
a different error than the swap space one?)?
I read about the error above very often in this list
(ChunkPool::allocate). Each time I suggest to not use an Xmx too big for
the machine and to upgrade the jvm to the latest available. IIRC I never
Dain Kaplan ha scritto:
The settings i copied over from the 2.2.0 installation are: -Xms1536m
-Xmx2048m
1.5GB and 2GB ?? what kind of use do you make of JAMES ?
I manage almost 1 million mail per day with an Xmx set to 300MB, with
2.3.1
The system has 4GB of memory, and James is the
the error above very often in this list
(ChunkPool::allocate). Each time I suggest to not use an Xmx too big
for
the machine and to upgrade the jvm to the latest available. IIRC I
never
received a feedback about the solution.
Stefano
I would recommend changing the WIKI to read:
Step 2.5 : Move
The memory settings were set by someone else, I assumed he had a
reason, but he could have been overzealous in his pursuit. Though we
do have 230 domains, and process a lot of mail.
Anyways, I looked at the configuration files, and there are two
salient differences:
(1) the default uses
Hi,
1) Database storage should be no problem
2) No the logic was not changed, it should work without problems. Many
of the new Mailets are just examples
I still not get why you have such problems :-/
bye
Norman
Am Donnerstag, den 13.12.2007, 13:22 +0900 schrieb Dain Kaplan:
The memory
-threads100/max-threads
On Dec 11, 2007, at 12:35 AM, Stefano Bagnara wrote:
Either you send your config.xml or you tell us exactly what changes
you
did to config.xml in 2.2.0 and in 2.3.1.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade
In my previous email i put many servernames here, but not in the
last email. There are 100+ servernames listed, i removed them to
protect the privacy of my clients. You will also find XXX.XXX.XXX.XXX
where IPs should be, please assume those are actual IPs as well, and
not Xs.
Sorry for
Dain Kaplan ha scritto:
In my previous email i put many servernames here, but not in the last
email. There are 100+ servernames listed, i removed them to protect the
privacy of my clients. You will also find XXX.XXX.XXX.XXX where IPs
should be, please assume those are actual IPs as well, and
XML configuration: please
take a
look at the james original config.xml mailstore item. You should
copy
it as-is in your configuration file. The way you mixed the
objectstorage
inside the mailstore is not ok.
Ah, perhaps this is it. In the upgrade document, it only says:
Step 2.5
After an upgrade to the stable release of 2.3.1, following the
included upgrade instructions, James starts up fine. Incoming mail
also seems to be processed as well (after looking in the logs and
watching the spool DB table).
However, mails simply don't show up in the user's inbox via
Either you send your config.xml or you tell us exactly what changes you
did to config.xml in 2.2.0 and in 2.3.1.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the included
upgrade
at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the
included
upgrade instructions, James starts up fine. Incoming mail also
seems to
be processed as well (after looking in the logs and watching the
spool
DB
:
Either you send your config.xml or you tell us exactly what changes
you
did to config.xml in 2.2.0 and in 2.3.1.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the
included
upgrade
you send your config.xml or you tell us exactly what changes you
did to config.xml in 2.2.0 and in 2.3.1.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the included
upgrade instructions
.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the
included
upgrade instructions, James starts up fine. Incoming mail also
seems to
be processed as well (after looking
I've added How to upgrade James? to the FAQ at
http://wiki.apache.org/james/FrequentlyAskedQuestions .
I'm waiting for a response on How to configure a mailing list? and for some
help/explanations on How to prevent spam?
Should someone tell me Mailing List is good enough to post on the FAQ
I used as a reference mostly the ./UPGRADE.txt file and the pre existent entry
on the FAQ. It turned out like this:
How do I upgrade James?
0. Stop the James server and rename the previous James directory to
another name.
1. Run phoenix to let the new james.sar to be deployed
Alessandro Delgado ha scritto:
[...]
2.6 To be able to use SSL you need to add this SSL config to the
server-sockets block:
[...]
But on step 2.6, a doubt strikes me: I've copied the code block from the
UPGRADE.txt file, but to me it seems like it wouldn't have any effect, since
Himanshu Singh ha scritto:
Hi,
We have been running a customized mailet under james-2.2.1-RC1 to
process emails to a specific mailbox, and are now trying to set up the
same under 2.3.1.
After installing the server and running it as a service, I have made
required changes in
Hi,
We have been running a customized mailet under james-2.2.1-RC1 to
process emails to a specific mailbox, and are now trying to set up the
same under 2.3.1.
After installing the server and running it as a service, I have made
required changes in james-fetchmail.xml and following changes in
You can find an UPGRADING.txt in the zip/tar.gz file.
Bye
Norman
Bud Bach schrieb:
Are there instructions on the web for upgrading from a 2.2 to a 2.3
installation? Thanks. -- Bud
!EXCUBATOR:1,45ae0e7639412075771710!
47 matches
Mail list logo
