Re: Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

I can see, why you wish to keep lastUpdated as the time the mail was actually put in the spool for diagnostic purposes. I was hoping to keep the changes local to RemoteDelivery, but this boils down to that not being possible. So I will start working on Spool.Filter and Spool.TimeFilter. and ac

Re: Exposing classes with Merlin

Noel J. Bergman wrote: The level of exposure of these classes to client code is a function of the container support for isolation. If your running James in Phoneix then these classes will be exposed. If you running under Merlin then they will be isolated to the implementing container. For examp

Exposing classes with Merlin

> The level of exposure of these classes to client code is a function of > the container support for isolation. If your running James in Phoneix > then these classes will be exposed. If you running under Merlin then > they will be isolated to the implementing container. For example, under > Merlin

Re: candidates/commons-collections

Noel J. Bergman wrote: Commons-collection is a dependent jar from the cornerstone threads component (actually the dep traces back to the latest excalibur-threads release). OK. And apparently no issues with those classes being exposed to client code. At one point, I had thought that there

RE: candidates/commons-collections

> Commons-collection is a dependent jar from the cornerstone threads > component (actually the dep traces back to the latest excalibur-threads > release). OK. And apparently no issues with those classes being exposed to client code. At one point, I had thought that there was going to be some cha

Re: candidates/commons-collections

Noel J. Bergman wrote: Stephen, Why is Commons Collections in the candidates directory? Should that be one level up in lib/? Commons-collection is a dependent jar from the cornerstone threads component (actually the dep traces back to the latest excalibur-threads release). Steve. --- Noel

cvs commit: james-server/proposals/imap2/test/org/apache/james/imapserver CommandParserTest.java

noel2003/10/22 18:55:13 Modified:proposals/imap2/java/org/apache/james/imapserver ImapHandler.java ImapHost.java ImapServer.java ImapSession.java JamesImapHost.java proposals/imap2/java/org/apache/james/imapserver/command

cvs commit: james-server/src/java/org/apache/james/util/dbcp JdbcDataSource.java

noel2003/10/22 18:53:21 Modified:src/java/org/apache/james James.java src/java/org/apache/james/core AvalonUsersStore.java src/java/org/apache/james/pop3server POP3Handler.java src/java/org/apache/james/transport/mailets

RE: [patch] fixing a compilation and cleaning up imports

> Find attached a patch for making the tree compile and for cleaning up > the unused imports (makes it nicer to work with eclipse). Sorry ... that was a change in an imported library. Will apply the imports change. --- Noel --

cvs commit: james-server/src/java/org/apache/james/dnsserver DNSServer.java

noel2003/10/22 18:46:21 Modified:src/java/org/apache/james/dnsserver DNSServer.java Log: dnsjava v1.4.0 changed its interfaces from short to int. Revision ChangesPath 1.22 +4 -4 james-server/src/java/org/apache/james/dnsserver/DNSServer.java Index: DNSS

cvs commit: james-server/src/java/org/apache/james/util/connection ServerConnection.java

noel2003/10/22 18:45:57 Modified:src/java/org/apache/james/util/connection ServerConnection.java Log: remove tabes Revision ChangesPath 1.13 +1 -1 james-server/src/java/org/apache/james/util/connection/ServerConnection.java Inde

[patch] fixing a compilation and cleaning up imports

Find attached a patch for making the tree compile and for cleaning up the unused imports (makes it nicer to work with eclipse). HTH Index: proposals/imap2/java/org/apache/james/imapserver/ImapHandler.java === RCS file: /home/cvspubl

candidates/commons-collections

Stephen, Why is Commons Collections in the candidates directory? Should that be one level up in lib/? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maximum number of users

> > Has anybody ever tested the maximum number of users JAMES can handle? > > There should not be a limit, although there are two places in the code where > a Map keeps track all of the mailboxes currently in use. They could be > replaced with a ReferenceMap. > > I just entered this into bugzilla.

DO NOT REPLY [Bug 24022] - Don't keep all mailboxes in-memory forever

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Maximum number of users

> Has anybody ever tested the maximum number of users JAMES can handle? There should not be a limit, although there are two places in the code where a Map keeps track all of the mailboxes currently in use. They could be replaced with a ReferenceMap. I just entered this into bugzilla. --

DO NOT REPLY [Bug 24022] New: - Don't keep all mailboxes in-memory forever

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Maximum number of users

Has anybody ever tested the maximum number of users JAMES can handle? I mean not concurrently, only the local accounts, irrespective of the traffic they produce. M

RE: Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

> > Mind you, I'd also like to see Spool.accept() return the message, not the > > key. There are exactly two calls to Spool.accept()/accept(long) in James. > > In both cases, we immediately follow up by retrieving the message, but we > > have a much more complex synchronization process because of

Re: Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

Noel J. Bergman wrote: My idea was to always do an outgoing.accept(0) and set the Mails lastUpdated to currentTimeMillis+the next delay for that mail- MailImpl.writeObject always does a lastUpdated=new Date() prior to the actual storing of the object, which effectly prevents me from dating the mai

RE: Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

> My idea was to always do an outgoing.accept(0) and set the Mails lastUpdated > to currentTimeMillis+the next delay for that mail- > MailImpl.writeObject always does a lastUpdated=new Date() prior to > the actual storing of the object, which effectly prevents me from > dating the mail into the fu

Re: Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

Søren Hilmer wrote: Does it actually make sense to have a setLastUpdated method, when the effect of it is changed behind your back? I'm happy with removing Mail.setLastUpdated and just having MailImpl.setLastUpdated. I think the behavior makes sense, but can see how exposing the setter method c

Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

Hi, During my implementation the multiple delay times in RemoteDelivery, I have run into a little problem. My idea was to always do an outgoing.accept(0) and set the Mails lastUpdated to currentTimeMillis+the next delay for that mail- But alas in MailImpl.writeObject always does a lastUpdated=

Mail to Quarantined

I'm getting spammed by this kind of thing (below) everytime I post, can we unsubscribe this person? I personally believe that this is as anti-social as requesting a read receipt from a list. We only have their word that this isn't an attempt to harvest addresses. Sorry but, to coin a phrase,it

JDK 1.3 vs 1.4 (was: RE: Excluding DNS entries from lookup?)

(this went to the wrong list ..) Guys, I have a *little* insight into this since taking up my *new**job* ;-) Serge wrote: > Sounds like a better approach, but then do we require JDK 1.4? With JDK > 1.5 on the horizon, maybe it's not such a bad idea. Noel added: > We would require it for t