Adam Fowler wrote:
It says in the WIKI that it does not yet support permanent storage of
messages. I'm going to take a look at it tomorrow night, and was wondering
if there's any simple pointers anyone could give me on writing a storage
mechanism. i.e. is there an API available to build such a 'plu
> I tested it and Phoenix DID NOT find the files at startup. I just tested
> again and it DID find the files.
That's really odd. We haven't had any other reports of problems and, IIRC,
Phoenix will fail to start if it can't load the entity.
--- Noel
noel2004/05/12 20:06:59
Modified:src/java/org/apache/james/core Tag: branch_2_1_fcs
AbstractJamesService.java
Log:
Fix JAMES-283. Allow connection (server socket) backlog to be configurable)
Revision ChangesPath
No revision
noel2004/05/12 19:56:03
Modified:lib Tag: branch_2_1_fcs readme.xml
Log:
update JavaMail version in the readme
Revision ChangesPath
No revision
No revision
1.2.4.3 +3 -3 james-server/lib/readme.xml
Index: readme
Install and try James 2.2.0RC3 and see if your problems are resolved.
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Your version of James?
The 2.1.x series has a thread problem. Bad. Unsolved until the 2.2.x
series, according to the developers.
In my meagre experience I set the spool threads to 1 and restart until
the queue is down; delete hopelessly message_state="error" messages
(impossible addresses like
Hi,
I implanted a system that uses
james to send mails.
This error ocurred three
times:
james has stopped to
process mails, the list of mails in the spool was growing up, but no mail was
processed or sended. We restart james and it start to process the mails
again. And we see
> How do I get these changes into JAMES?
http://james.apache.org/contribute.html
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
NOT ENTERED IN JIRA!!
Noel,
I tested it and Phoenix DID NOT find the files at startup. I just tested
again and it DID find the files. Maybe I'm doing something stupid or maybe
there is something we are missing. Either way, we know that the previous
version worked over several alpha releases, on t
And as of tomorrow, for the next 10 days I'm happily disconnected. Gone
sailing.
Feels like I'm leaving you guys, particularly Noel who is trying to get a
release out, in the lurch. Sorry!
-- Steve
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 12 May 20
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Wed, 12 May 2004 2:02 PM
Body:
Before committing the change, I had tested it. My configuration here IS using:
]>
And the lists ARE working. Are you saying that the above does not work for yo
The following comment has been added to this issue:
Author: Steve Brewin
Created: Wed, 12 May 2004 1:53 PM
Body:
Should have said that I have committed a change which reverts the ENTITY declarations
back to their working forms.
I have left the issue open with the expectation to r
Message:
The following issue has been reopened.
Reopener: Steve Brewin
Date: Wed, 12 May 2004 1:47 PM
Bit of a misunderstanding here, which is my fault for not being clear. I entered this
as something to look at based on a suggestion from the community.
I had no intention to apply
sbrewin 2004/05/12 13:35:20
Modified:src/conf Tag: branch_2_1_fcs james-config.xml
Log:
Reverted to prior Entity declarations where '..' is assumed to be PHOENIX_HOME.
Revision ChangesPath
No revision
No revision
1.40.2.25 +3 -3
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Wed, 12 May 2004 10:44 AM
Comment:
Patch to add configurable connection backlog.
Changes:
Attachment changed to backlog-patch.txt
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Wed, 12 May 2004 10:42 AM
Body:
I agree that a change should be made, but am reluctant to change the backlog value at
this late date without putting the release through testing again. There is a
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Wed, 12 May 2004 9:09 AM
Body:
Please try to avoid using JIRA as a discussion tool. Use the mailing list(s) to
discuss potential problems.
The DEBUG level for the the smtphandler will log all of
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-283
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Hes Siemelink
Created: Wed, 12 May 2004 1:46 AM
Body:
Thanks, will do that. I saw no exceptions in the James log on the INFO level (I assume
that exceptions are never logged on the DEBUG level?).
We're a bit puzzled by t
19 matches
Mail list logo
