t is configured in the default config set.
I also agree that the default config should have remote delivery
enabled.
Gerry Matte
--
From: "Eric Charles"
Sent: Thursday, October 14, 2010 12:17 AM
To: "James Users List" ;
elivery
enabled.
Gerry Matte
--
From: "Eric Charles"
Sent: Thursday, October 14, 2010 12:17 AM
To: "James Users List" ; "James
Developers List"
Subject: 3.0-M1 default configuration
Hi All,
We are preparing the 3.0-M1 release and need to define the de
et.
I also agree that the default config should have remote delivery
enabled.
Gerry Matte
--
From: "Eric Charles"
Sent: Thursday, October 14, 2010 12:17 AM
To: "James Users List" ; "James
Developers List"
Subject: 3.
emote delivery enabled.
Gerry Matte
--
From: "Eric Charles"
Sent: Thursday, October 14, 2010 12:17 AM
To: "James Users List" ; "James
Developers List"
Subject: 3.0-M1 default configuration
Hi All,
We are preparing th
--
From: "Eric Charles"
Sent: Thursday, October 14, 2010 12:17 AM
To: "James Users List" ; "James Developers
List"
Subject: 3.0-M1 default configuration
Hi All,
We are preparing the 3.0-M1 release and need to define the default
config
Small comment : jpa = database of your choice (mysql, postgresql,...,
derby by default)
On 14/10/2010 09:17, Eric Charles wrote:
Hi All,
We are preparing the 3.0-M1 release and need to define the default
configuration.
Currently, when you download James 3 snapshot, you have
virtualHosting:
Hi All,
We are preparing the 3.0-M1 release and need to define the default
configuration.
Currently, when you download James 3 snapshot, you have
virtualHosting: disabled
mailbox: jpa
user: jpa
virtualuser: jpa
domainlist: xml
ValidRcptHandler handler: enabled
jmx: disabled
remote delivery: di
