Re: MBox format

Serge Knystautas wrote: Danny/Noel, Did you say you had spoken with an author of an mbox java implementation? I checked out EyeBrowse which has a read-only implementation of mbox files, and found a decent description of mbox (http://email.about.com/library/weekly/aa111300a.htm), and with a re

Re: Specific Steps to Release

Noel J. Bergman wrote: 1. Merge File Repository Changes -- DONE 2. Merge the one NNTP patch if Serge OKs -- DO NOT DO 3. Change config.xml to disable NNTP -- DONE 4. Do build website dist -- DONE 5. Update www/ in CVS-- DONE 6. tag the CVS

Re: New repository/new branch

Noel J. Bergman wrote: >> My philosophy on source control assumes the head is the next >> release, as it is what's built every night. > > Well, now that IS an issue. And points to a reason for a separate > CVS module, or at least an inquiry to Sam Ruby. Because for a while > both v2.1+ and v3.0 w

Re: New repository/new branch

Sam Ruby wrote: It is quite possible for a project to have multiple gump descriptors, and for some or all of them to specify a tag. Sounds great. Although, since we depend heavily on Avalon, and they went and rewrote their API, we'd be getting Gump failures on 2.1 for some time... do you thin

Re: MBox format

Nicola Ken Barozzi wrote: If we want James to be used by ASF, it must IIUC work with Eyebrowse. And Eyebrowse uses mbox format. So the options are: 1) store as mbox 2) make a simple conversion script 3) make eyebrowse use the James format I'd like to get mbox supported just because I think a lo

RE: New repository/new branch

> I'm not sure why we would merge changes from head onto an old branch. I > could see us making small fixes to the branch and pushing those changes > back into head, but not really vice versa. Yeah. > It's a meritocracy, so if someone wants to work on it, they can. It's > very hard to keep a pa

RE: New repository/new branch

> My personal opinion closely matches Matthew's. If you want to stabilize > development of 2.1, and encourage development of 3.0, then name 2.1 a > branch. If you want to encourage development of two divergent code > bases, then create two CVS trees. I think we have a concensus then, both intern

Re: Specific Steps to Release

Hi all, While we are on this topic, the best tool I have come across for Software Configuration Management is Perforce. (www.perforce.com) Its cross-platform and free for Open Source projects. It also integrates with bug tracking software like Bugzilla. I don't really know what the ASF policy is

Re: MBox format

Hi Serge, This apeared in an earlier post. http://javamaildir.sourceforge.net/ Serge - Original Message - From: "Serge Knystautas" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Monday, December 30, 2002 3:22 AM Subject: Re: MBox format > Ah ok, yeah maild

Re: Specific Steps to Release

Noel J. Bergman wrote: 1. Merge File Repository Changes -- DONE 2. Merge the one NNTP patch if Serge OKs -- DO NOT DO 3. Change config.xml to disable NNTP -- DONE 4. Do build website dist -- DONE 5. Update www/ in CVS-- DONE 6. tag the CVS

RE: Specific Steps to Release

Serge, send me a patch and I'll apply it. Do you want me to update the jakarta site on daedalus too? You have an account right? d. > -Original Message- > From: Serge Knystautas [mailto:[EMAIL PROTECTED]] > Sent: 30 December 2002 11:25 > To: James Developers List > Subject: Re: Specific Ste

[GUMP] Build Failure - jakarta-james

This email is autogenerated from the output from: Buildfile: build.xml prepare-common: [echo] Preparing code [mkdir]

RE: New repository/new branch

> I think we have a concensus then, both internally and incuding Sam's > comment, for a branch? Just answer a question for me, and I'm happy. :-) I just want to understand the CVS mechanics for working on each branch. After we (Ok, YOU :-)) tag/create the branch, does this work? # hold onto t

RE: Specific Steps to Release

> - need to link to the new release on the binindex.xml and srcindex.xml I would do it if I had a daedalus account (yes, I sent the e-mail to root again). For now, I think that we simply change the static references in those two files to point to http://www.apache.org/dist/jakarta/james/. AIUI, w

RE: Specific Steps to Release

Fine. Provide details. :-) I saw another inquiry on infrastructure@ from Martin Cooper this morning asking precisely the same question, so apparently I'm not the only one wondering. :-) I understand the concept, but what are the specific steps (key acquisition/generation, which keygen/signing

RE: Specific Steps to Release

> I would do it if I had a daedalus account Strike that! Guess what I got this AM? :-) Shiny new access rights. :-) --- Noel -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: New repository/new branch

Noel, to answer your question: > # hold onto the current project, with some private code > $mv jakarta-james jakarta-james.HEAD > # checkout a clean build of the new branch > $cvs checkout -r jakarta-james > # rename the directory to reflect the branch > $mv jakarta-james jakarta-james. >

RE: Specific Steps to Release

Merry Christmas. Don't drink and type. ;-) d. > -Original Message- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: 30 December 2002 16:13 > To: James Developers List > Subject: RE: Specific Steps to Release > > > > I would do it if I had a daedalus account > > Strike that! G

RE: Specific Steps to Release

Noel, Talking about signing? checkout www.pgpi.com and/or www.gnupg.org d. > -Original Message- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: 30 December 2002 16:12 > To: James Developers List; [EMAIL PROTECTED] > Subject: RE: Specific Steps to Release > > > Fine. Provid

RE: New repository/new branch

> I'm not sure why we would merge changes from head onto an old branch. OK, let's say that I create and want to commit a new matcher that we intend to use in both v2.1.5 and v3.0. Where do I put it, and how do I get it into both builds? > Scope is large, or at least could be. Once we've brainst

RE: New repository/new branch

> Sounds great. Although, since we depend heavily on Avalon, and they > went and rewrote their API, we'd be getting Gump failures on 2.1 for > some time... do you think it's worth tagging the branch in we use in > Avalon, or is there a better way to support this? Actually, once we tag v2.1 it is

RE: Specific Steps to Release

> I don't really know what the ASF policy is regarding CVS, > but since someone did mention Subversion ... Subversion is a Collab.net project (http://svn.collab.net/). Guess who is a major part of the ASF infrastructure? :-) Subversion and Eyebrowse both come over from tigris.org. If you have

Re: James ready for mirroring

Noel J. Bergman wrote: In conjunction with the release of James v2.1, Serge Knystautas and I have setup James under /www/www.apache.org/dist/jakarta/james, according to our understanding of the mirroring docs, and are ready to update download pages in the jakarta-site2 module after the mirrors pr

RE: Specific Steps to Release

> Don't drink and type. ;-) I spoke too soon. I can't use the account yet (mismatching directory permissions); sent e-mail to root. Would you please affect those CVS changes? Do you have time today? --- Noel -- To unsubscribe, e-mail: For additional comma

Re: Specific Steps to Release

Noel J. Bergman wrote: Fine. Provide details. :-) I saw another inquiry on infrastructure@ from Martin Cooper this morning asking precisely the same question, so apparently I'm not the only one wondering. :-) I understand the concept, but what are the specific steps (key acquisition/generat

RE: Specific Steps to Release

What am I doing updateing the website? (reply by 22:00 GMT and I'll try'n'do it before I go to bed) > -Original Message- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: 30 December 2002 17:17 > To: James Developers List > Subject: RE: Specific Steps to Release > > > > Don't drin

RE: Specific Steps to Release

Thank you! :-) Hopefully this will make life easy(ier) for you: --- binindex.xml and srcindex.xml: For now, simply change our release URLs to point to http://www.apache.org/dist/jakarta/james/ instead of the current release/2.0a3/ directory. --- index.xml: Add "http://jakarta.a

Re: MBox format

Mbox support definitely improves the migration story. Matt Bishop [EMAIL PROTECTED] "We are all here on earth to help others. What I can't figure out is what the others are here for." - W. H. Auden -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: New repository/new branch

> OK, let's say that I create and want to commit a new matcher that we intend > to use in both v2.1.5 and v3.0. Where do I put it, and how do I get it into > both builds? On the head (v3): cvs commit newMatcher.java In a separate enlistment (v2.1.5 branch) cvs update -j HEAD newMatcher.java

CVS, Perforce, Subversion, et al.

I have used numerous source control systems, including perforce, and I would recommend staying with CVS for several reasons: 1. CVS is a well-known SCM in the open source world, as well as the commercial world. Makes it easier for people to participate in James. Also means there's tons of doc an

RE: New repository/new branch

Matt, Thanks. But what about when adding it? $cd ~/jakarta/jakarta-james/.../matchers $cvs add newMatcher.java $cvs commit -m "..." newMatcher.java $cd ~/jakarta/jakarta-james.v2/.../matchers $cvs update -j HEAD newMatcher.java Is that last one right? Do I need to do anything else, e.g.,

RE: CVS, Perforce, Subversion, et al.

Matt, We're not talking about unilaterally moving James to another CVS. At some point the word is that all ASF project will migrate to Subversion, as soon as infrastructure is satisfied that the time is right (most likely when they've debugged the CVS -> Subversion conversion script). --

Re: MBox format

- Original Message - From: Matthew Bishop <[EMAIL PROTECTED]> Sent: Dec 30, 11:33 AM > Mbox support definitely improves the migration story. Agreed, but instead of James supporting MBox natively, I think it may be better to support a format like maildir and document a conversion tool fro

Re: New repository/new branch

> Is that last one right? Do I need to do anything else, e.g., add it to the > branch? I believe so, though you may have to update the directory instead of an individual file. Worse case scenario, you have to tag the file and update to the tag. See cederqvist section 5.9: http://www.cvshome.or

Re: New repository/new branch

Wrong URL, here's the right one: http://www.cvshome.org/docs/manual/cvs_5.html#SEC63 Matt Bishop [EMAIL PROTECTED] "We are all here on earth to help others. What I can't figure out is what the others are here for." - W. H. Auden -- To unsubscribe, e-mail: For

RE: MBox format

> instead of James supporting MBox natively It is just another repository type, and Serge seems to think that it is fairly straightforward to code, so I suggest that we just do it. By the way, in an earlier e-mail Serge mentioned that Eyebrowse can handle maildir format. Is this not correct?

[V3] Personal Item List

Now that I can (at long last) post it ( ;-) ), this has been my personal list of items: V3.0: - Matcher Parameters - Extensible User Model - BSF Matcher/Mailet - Replace Mordred - Full Function Mailing Lists - Dynamic Reconfiguration - Configuration in Database - User-specific Pipeline -

Re: [V3] Personal Item List

Hi Noel, A couple of questions.. I know these things are up in the air, etc, but I figure since it's out there might float a few more questions. > - Replace Mordred Are we going to use the Jakarta Commons DBCP? I've started using it in one of my applications and I'm really liking it. > - Full

RE: [V3] Personal Item List

> - Matcher Parameters +1 my idea is to have this new style of conf.. whatever > - Extensible User Model > - BSF Matcher/Mailet > - Replace Mordred .. use commons dbcp > - Full Function Mailing Lists > - Dynamic Reconfiguration

RE: MBox format

to be honest I can't think of a single good reason that we shouldn't churn out whatever file formats people feel like writing, and let people pick the most convenient, or use the default. Like MySQL db formats. its a simple config change to alter the format in use, and from a marketing POV lists o

RE: [V3] Personal Item List

Kenny, Redirect and Forward do this, with the list in the conf file, or JDBCListserve can do it with a db stored list, just leave out the command (subscribe/unsubscribe) mailet from conf and edit the list some other way. an aliases file is a nice idea though, it might help cut across mindset bound

Re: MBox format

Noel J. Bergman wrote: instead of James supporting MBox natively It is just another repository type, and Serge seems to think that it is fairly straightforward to code, so I suggest that we just do it. By the way, in an earlier e-mail Serge mentioned that Eyebrowse can handle maildir format. I

Re: [V3] Personal Item List

How are people differentiating v2.x and v3 items? For instance, v2 changes are internal only, not changing the outward API, and v3 is new features? Matt Bishop [EMAIL PROTECTED] "We are all here on earth to help others. What I can't figure out is what the others are here for." - W. H. Aud

RE: [V3] Personal Item List

> > - Replace Mordred > Are we going to use the Jakarta Commons DBCP? Danny and Kenny. With respect to DBCP, I don't necessarily have anything against it, but JDBC v3 has connection pooling built-in. So from that perspective, my own view is that the issue hinges on whether we adopt JDBC v3, in

Re: [V3] Personal Item List

Hi Danny, Can you give an example of what you mean? I'll look into JDBCListserve, I don't think I saw that one before. I looked at some other mailets that were JDBC/list-centric, but I didn't find anything I could really use. The hacked version of JDBCVirtualUserTable I'm using just allows the

Re: [V3] Personal Item List

Hi Danny, I looked at Redirect/Forward and JDBCListserv and they are close to what I'm looking for, but I really want the whole thing to be configured in a database. Does JDBCAlias support a one to many relationship? I'll look when I get home, but that will be a long time from now. Kenny Smi

Re: [V3] Personal Item List

Noel J. Bergman wrote: Now that I can (at long last) post it ( ;-) ), this has been my personal list of items: V3.0: - Replace Mordred Yes, with DBCP, or maybe we use another pool. Aside from removing what isn't the best pooler, I want to expose javax.sql.DataSource's via JNDI so matchers/m

Re: [V3] Personal Item List

Noel J. Bergman wrote: One thing I'm very interested in is multiple recipient aliases/forwards. Obviously full function mailing lists are totally important, but I'm also interested in something in between. Let's address this when we look at the user repository model. For example, I want to con

RE: [V3] Personal Item List

Matt, James v3 includes Mailet API v3 as well as major revisions to the user and message store models. Therefore, at least from my perspective, James v3 items are generally (a) major changes, or (b) rely upon other James v3 changes. For example, we could do full feature mailing lists for James v

RE: [V3] Personal Item List

Kenny, One of the things I intend to do is to fix up a few things in Redirect, and then re-code most of the current similar classes to be Redirect subclasses. That should clean up the entire area. Forwarding to a group would be trivial at that point, with multiple ways to encode the group address

Re: [V3] Personal Item List

Hi Noel, I want to have the group aliases controlled in an alias database table, just like JDBCVirtualUserTable. I don't want to have to update the config every time I add another group alias. Do the changes you plan on for the Redirect stuff involve functionality like that? I really like JDBC

RE: [V3] Personal Item List

> I'm not sure exactly what Kenny is using this for ... Basically, he just wants: user@domain --> user1@domain, user2@domain2, user3@domain3, ... In other words, just a list of addresses associated with a single address. In an address book that is typically called a group address. In sendmail

RE: [V3] Personal Item List

Danny, - Matcher Parameters I think we're back to this discussion: http://www.mail-archive.com/james-dev@jakarta.apache.org/msg02345.html, yes? I had initially favored something like: me.com somevalue> somevalue othervalue some value for the mailet where

Re: [V3] Personal Item List

Hi Noel, Sure, I'll send it over tonight. The computer-scientist in me dislikes parsing database that comes from a database. I inherently want it to be in the proper sizes chunks. However, I've been unable to come up with a good database design that allows me to have mulitple rows represent th

Re: New repository/new branch

Danny Angus wrote: My personal opinion closely matches Matthew's. If you want to stabilize development of 2.1, and encourage development of 3.0, then name 2.1 a branch. If you want to encourage development of two divergent code bases, then create two CVS trees. I think we have a concensus then

Re: [V3] Personal Item List

Err... "dislikes parsing data that comes from a database." The computer-scientist in me dislikes parsing database that comes from a database. Kenny -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: [V3] Personal Item List

> I want to have the group aliases controlled in an alias database table, > just like JDBCVirtualUserTable. I don't want to have to update the > config every time I add another group alias. Do the changes you plan on > for the Redirect stuff involve functionality like that? When I am finished, Red

RE: [V3] Personal Item List

> I want to expose javax.sql.DataSource's via JNDI so matchers/mailets ... Do we really want to require JNDI in the Mailet API? If you say yes, I won't grouse, but it will open the door to a lot of stuff. If you say no, then we'll need an alternative way to pass the DataSource (which I agree wi

Re: [V3] Personal Item List

- Original Message - From: "Noel J. Bergman" <[EMAIL PROTECTED]> > > I want to expose javax.sql.DataSource's via JNDI so matchers/mailets ... > > Do we really want to require JNDI in the Mailet API? If you say yes, I > won't grouse, but it will open the door to a lot of stuff. If you s