Danny Angus wrote:
I am a little confused as to why Danny/Noel believe it isn't part of the
Mailet API? What is the remit of the Mailet API? What is its purpose
in life if not a hook for developers to process mails?
Yeah, but the API doesn't assume that the system doing the processing
is also implementing any of the mail protocols. It could be that the
mail is all sitting in an archive and needs to be mined for some
reason.
Gotcha, that makes sense from that aspect.
Therefore protocol related API's are out of scope, but that doesn't
make it a bad idea.
I guess this is always the balance, purist vs. reality. In reality the
majority of mailets are probably being called upon the SMTP trigger,
therefore it makes sense to involve that protocols behaviour in the API.
However, you could make it completely protocol agnostic and treat it a
little like how Servlets manage HEAD/GET/POST/DELETE etc.
For example, we are discussing whether or not we want to process the
mail. Therefore, you could make a strong argument, that the Matcher
classes are invoked at the wrong part of the chain. Maybe they should
be invoked as and when the email address is available, and not when the
whole body has arrived.
So for SMTP that would be in response to a MAIL FROM / RCPT TO; for IMAP
that would be when the email was downloaded (does JAMES support IMAP
btw?); etc.
Right ... i really have to go for tonight, i have 3 boys waiting for
their father to watch a movie!!! Have a good evening gentlemen.
