The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Fri, 21 May 2004 10:51 PM
Body:
> james at the end of doPASS does a stat() that brings all
> messages in their entirety (not just referenced by their
> key)
doPASS()
->stat()
-> us
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Fri, 21 May 2004 10:44 PM
Body:
> mc = null;
Won't help, since the object is in the userInbox collection.
> mc.setMessage(null);
If we were to do that, subsequent calls to mc.getMessageSize(), m
The following comment has been added to this issue:
Author: Serge Knystautas
Created: Fri, 21 May 2004 10:18 PM
Body:
Explicit nulling objects can do exact opposite you intend, i.e., it can make the JVM
less efficient at garbage collection.
http://www-106.ibm.com/developerworks/j
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-283
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 21 May 2004 10:10 PM
Changes:
assignee changed to Noel J. Bergman
summary changed from Mail not correctly deliverd after DNS time-out on
From: address to P
The following comment has been added to this issue:
Author: Ralf Hauser
Created: Fri, 21 May 2004 9:25 PM
Body:
Noel, I never said that the current implementation is a defect. I only think it is not
very memory efficient. One more degree of sophistication what I am proposing comes
noel2004/05/21 21:10:07
Modified:.Tag: branch_2_1_fcs build.xml
Log:
bump revision to RC4
Revision ChangesPath
No revision
No revision
1.116.2.30 +2 -2 james-server/build.xml
Index: build.xml
noel2004/05/21 20:55:03
Modified:src/java/org/apache/james/util Tag: branch_2_1_fcs
CharTerminatedInputStream.java
Log:
Fix JAMES-282. If the stream closes before the terminator is seen, throw an
Exception, since returning -1 (end of stream) is the NORMA
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 21 May 2004 8:50 PM
Changes:
Fix Version changed to 2.2.0RC4
-
For a full history of the issue, s
[EMAIL PROTECTED] wrote:
OK, this partial message problem is reproducible and comes from the fact that when the socket prematurely closes (as opposed to times out, which does generate an exception), the associated stream just returns -1 when asked for more data. This gets passed back through the c
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Fri, 21 May 2004 4:20 PM
Body:
OK, this partial message problem is reproducible and comes from the fact that when the
socket prematurely closes (as opposed to times out, which does generate an exc
> I'm very leery of distracting a push to get IMAP implemented to
> another extended design thread.
As long as we can keep it isolated, sure. I just want us to have the
flexiblity to look at our design decisions coherently down the road.
> > I would also like to see the system support better opt
Noel J. Bergman wrote:
defining a standard API for IMAP mail store is great.
Revising an API for mail stores, period. Right now we don't have one to
delete, for example, when a user is no longer served. However, I am not
entirely sure where best to do some of this. For example, if JNDI were
mand
> defining a standard API for IMAP mail store is great.
Revising an API for mail stores, period. Right now we don't have one to
delete, for example, when a user is no longer served. However, I am not
entirely sure where best to do some of this. For example, if JNDI were
mandatory for User Repos
Adam Fowler wrote:
I have now successfully managed to get Alex's Maildir code working with
James. Or at least I think it's working! My system uses IMAP so I need to
test it through that, unfortunately the IMAP2 proposal code uses an in
memory store instead of using the configured Maildir inboxRepos
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-292
Here is an overview of the issue:
-
Message:
The following issue has been resolved as DUPLICATE.
Resolver: Noel J. Bergman
Date: Fri, 21 May 2004 8:00 AM
Duplicate of JAMES-260
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-292
Here i
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-293
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-291
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-292
Here is an overview of the issue:
-
Sorry guys,
Just added a duplicate issue in JIRA. Number 292 is a duplicate of 260.
I got over zealous in my issue adding.
Sorry guys, won't happen again.
Adam.
This email and any files attached is intended for the addressee only and may contain
information that is confidential and/or legally
Hello all,
I have now successfully managed to get Alex's Maildir code working with
James. Or at least I think it's working! My system uses IMAP so I need to
test it through that, unfortunately the IMAP2 proposal code uses an in
memory store instead of using the configured Maildir inboxRepository.
22 matches
Mail list logo
