[
https://issues.apache.org/jira/browse/JAMES-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen updated JAMES-3216:
---------------------------------
Description:
The "James Basic Server" is currently described as:
----
h2. James Basic Mail Server
The James Basic Server is intended for Operators who are just getting initiated
with operating their own Self-Hosted mail server.
The server is intended to be a mostly "out-of-the-box" solution. With a few
small interactions necessary to configure the system, you should be up and
running in no time with all the standard features.
----
This server is currently difficult to set up and use.
To make James more appealing to new users, installation should be simplified.
When input or configuration is required by users, it should be minimized and
well documented.
Note: I am working on this issue with the help of the community, but for some
reason I am not able to assign the issue to myself.
was:
The "James Basic Server" is currently described as:
----
h2. James Basic Mail Server
If you are not sure which server you should be using, then you probably ought
to be using the [*Local
Server*|https://james.leangen.net/main/3.5/servers/local.html]. This server
uses the local file system to store emails, which tends to considerably
simplify the system. To safeguard your emails, you only need a simple generic
backup solution that works with a data volume.
This server is intended to be the simplest to set up and use in production. It
has the least amount of dependencies and complexities. If you do not yet have a
huge amount of emails to process, then usually the simplicity is well worth the
loss of some functionality. The last thing you need is to have to resolve
difficult issues on a production server when you have not yet acquired the
requisite knowledge to deal with those issues. Using the [*Local
Server*|https://james.leangen.net/main/3.5/servers/local.html] will help you
reduce the risk of running into production issues.
This server is:
* Suggested for use with smaller deployments
* Appropriate for use by most operators
* The preferred choice for most installations
* Endowed with fewer dependencies, which makes it simpler and less risky to
use in production
* Only dependent on your local file system for data storage, so very easy to
manage
----
This server is currently difficult to set up and use.
To make James more appealing to new users, installation should be simplified.
When input or configuration is required by users, it should be minimized and
well documented.
Note: I am working on this issue with the help of the community, but for some
reason I am not able to assign the issue to myself.
> Make James Basic Server easier to use
> -------------------------------------
>
> Key: JAMES-3216
> URL: https://issues.apache.org/jira/browse/JAMES-3216
> Project: James Server
> Issue Type: Improvement
> Reporter: David Leangen
> Priority: Major
>
> The "James Basic Server" is currently described as:
> ----
> h2. James Basic Mail Server
> The James Basic Server is intended for Operators who are just getting
> initiated with operating their own Self-Hosted mail server.
> The server is intended to be a mostly "out-of-the-box" solution. With a few
> small interactions necessary to configure the system, you should be up and
> running in no time with all the standard features.
> ----
>
> This server is currently difficult to set up and use.
> To make James more appealing to new users, installation should be simplified.
> When input or configuration is required by users, it should be minimized and
> well documented.
>
> Note: I am working on this issue with the help of the community, but for some
> reason I am not able to assign the issue to myself.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
