You're right, I missed the "james-is-your-agent" model; instead, I was thinking of the JavaMail model where I get a status code upon each send. With James, I'll just have to be smarter about interpreting bounce messages (ie, VERP). I was hoping for some sort of direct notification mechanism (Observer pattern?) where my code can know the status of each outbound piece of email.
>>All of the MailetContext.sendMail(...) methods return void. >> >> > >They just spool mail. There is no status. I think you are missing the >architectural view. > > > >>When I'm writing a mailet, how can I find out the status of >>a piece of mail I just sent? >> >> > >You didn't send it. You inserted it into a spool for processing along with >all the rest of the messages. > > > >>How do I find out other errors like: no domain, SMTP server down, >>SPEWS blocking, etc? >> >> > >The remote delivery code will handle transient ones, and bounce permanent >ones. Handle the bounce messages. > > > >>BTW, does a VERP matcher already exist in James? >> >> > >Not yet. > -------- processed by Jakarta James -------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
