Sounds like it might be nice to point cfpop against a directory instead of a server and socket? Really cfpop already does all this stuff via javax.mail.*
.pjf On Mar 6, 2011 5:12 PM, "AlexS" <[email protected]> wrote: > Hi, > > There are two instances effectively when being able to parse a raw > email file as generated by Open BD back into its component parts could > be useful > > 1. Im currently prototyping an add-in to the openbd admin to give some > oversight of the current state of the given spool and undelivered > folders, this is made easy by the new function Alan added for locating > the spool directory programmatically. > > 2. The second instance where we are presented with email files in this > format is when using the spoolMailToDir() function on the cfsmtp > plugin functionality, this is very exciting as it means you can > effectively have one listening process generating the emails down to > file and other process or processes later picking them up parsing them > or working with them, i like this idea more than triggering my > application logic on the incoming mail request. > > In both of these instances having access to a library that would parse > one of these email files and generate effectively a mail object as > received by the cfsmtp functionality would be really useful ? > > Thoughts ? > > Alex > > -- > official tag/function reference: http://openbd.org/manual/ > mailing list - http://groups.google.com/group/openbd?hl=en -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
