Hi!
Ok, found the source and have been poking around. Amazing some of the similarities, also with Avalon, very similar to some of the abstractions I'm using. It still hasn't quite clicked with me how James processes mails. With Gem, it gets stored in MSG database table. That has foreign key to QUEUE table. The queue that the message is stored in is determined by email addresses attached to that queue. A queue can be thought of as a mailbox. The message initially has a status of 'U'nprocessed. The processing thread picks it up and it goes through 'P'rocessing phase, then to 'S'uccess or otherwise 'F'ailed stage if the Gemlet signals a problem. There is also a 'R'etry status if the Gemlet would like to take another shot at it later on. Messages can be reprocessed by resetting the status. It hasn't clicked with me which Mailets get called in James and how control moves to some other Mailet. I guess transport/ classes are the interesting ones. Is it documented somewhere what the Mail statuses mean? I see there is mention of writing an IMAP interface. This was what I was researching doing when I came across James. Would it run straight from the database (if you are using database) in this case? It's not clear to me how the single table datamodel would support this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
