Hi,
Yes, that's it. The default mailboxmanager is implemented with JPA
framework.
Did you create a domain or a user? James is configured so OpenJPA
automatically creates the tables when needed, so go via remotemanager
(telnet localhost 4555) to create user,....
The strange thing is that the presence of deadletter table. It may be
there is you changed the mailetcontainer to use db:... patterns for
deadletter processor. An other option would be that you use an exisiting
db schema (already used for james 2.3.2) ?
Tks,
Eric
On 12/11/2010 08:58, Mohammad Naghavi wrote:
Hi again
and tanks for infos, it was really good. but it is really confusing so let
me ask if by jpa=database you mean this tag:
<constructor-arg index="2" value="${openjpa.streaming}"/>
in this part of spring-beans.xml:
<bean id="mailboxmanager"
class="org.apache.james.mailbox.jpa.openjpa.OpenJPAMailboxManager">
<constructor-arg index="0" ref="sessionMapperFactory"/>
<constructor-arg index="1" ref="authenticator"/>
<constructor-arg index="2" value="${openjpa.streaming}"/>
</bean>
I did find no where else in spring-beans.xml to be related to mailbox.
and another question that if it is by default configured to use DB why it is
not building the tables in database? I have now just one table in my DB
named as deadletter and as you said before it is not related to mailboxs.
Thanks again
MN
________________________________________
PHP& ASP .Net 3.5 web developer
Java& C# desktop developer
www.mohamnag.com
On Fri, Nov 12, 2010 at 8:42 AM, Eric Charles<[email protected]> wrote:
Hi Mohammad,
Yes,
- maibox is for users' inbox, sent items, trash... folders.
- mailstore is for spam, error,... mails, so nothing to do with users
visible mails.
Both are configurable.
- Mailbox persistence is configured in spring-beans.xml (by default
jpa=database, you set the database connection properties in
database.properties - can also be maildir=file, jcr). We think to move this
config out-of spring-beans.xml.
- Available mailstore persistence are defined in mailstore.xml. Each has an
URL prefix (file, db, dbfile,...) that can be used in mailetcontainer.xml to
define where to store spam,... mails (exemple: file://var/mail/error/).
Both mailbox and mailstore use database connection defined via
database.properties in case of database access.
http://james.apache.org/server/3/feature_stores.html will be updated with
this for 3.0-M2 release.
I will try to also inject it in the quick start, but it must remain quick
:)
Tks,
Eric
On 12/11/2010 08:23, Mohammad Naghavi wrote:
Hi Eric
I didn't get it! maybe cause I'm totally new to James. what do you mean by
mailbox in contrast to mailstore? does mailbox means inbox? and mailstore
as
I understood means spams and deadletters.
also the non-mailbox ones are using database.properties or not? (sure when
it is configured to use DB for storage)
Tanks
MN
________________________________________
PHP& ASP .Net 3.5 web developer
Java& C# desktop developer
www.mohamnag.com
On Fri, Nov 12, 2010 at 6:25 AM, Eric Charles<[email protected]> wrote:
Hi,
To be complete, there are two types of "mail store".
1.- The mailbox store which is configured in spring-beans.xml (if default
jpa is used, you have database.properties to define which database to
use).
2.- The other mails (non-mailbox) that use definitions from mailstore.xml
and that can be used in by mailetcontainer.xml to persist mails that are
spam, error,...
This is really confusing and I'm sure we can do better on conf/doc level.
For example, having an additional mailbox.xml file that contains
definitions for the mailbox. At least, user will see there is two types
of
mail : the mailbox and the mailstore.
Tks,
Eric
On 11/11/2010 22:34, Mohammad Naghavi wrote:
Thanks now it is functioning!
________________________________________
PHP& ASP .Net 3.5 web developer
Java& C# desktop developer
www.mohamnag.com
On Thu, Nov 11, 2010 at 10:27 PM, Gerry Matte<[email protected]>
wrote:
ee repositories - any are available to use.
The mailetcontainer lines se
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
