The problem is two-fold; my inability to configure properly, and my failure to understand how James interprets SMTP protocol, RFCS, and standard practice.
As an SMTP server, James should notify senders when delivery/process can not be performed. My assumption was that this is done in the SMTPHandler and not necessarily in the pipeline. I'm just trying to understand - How can/why would James accept mail before it can verify that the mail belongs to it or that it can successfully process it ? Without liberal interpretations of "successfully process" - why would I accept an email to [EMAIL PROTECTED] when BOZO doesn't have an account at CLOWN.COM ?? By accepting the mail from the sender, I am now assuming responsibility for it, but since it doesn't belong here, as a SysOp, I trash it (through ignorance of James configuration...), or respond to the sender that the account doesn't exist here; to wit a mailet needs to be set up and configured to handle this situation. (assume that the pop3 is db and is off line) What outofhtebox mailet will perform this task ?? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
