Now I think I understand what you're saying.. James will send your mail back to you with the specific error if you uncomment the NotifySender mailet lines in the error processor secion of the configuration file.
James won't respond "unknown user", and refuse to accept the mail during an SMTP session, because it works by sending mails through the Mailet/matchers. Perhaps this is a potential DOS vulnerability, I don't know. But the combination of RecipientIsLocal, and HostIsLocal will trap mail to unknown users in the local domain, and send it to the error processor. This will then run its own set of matchers/mailets on the message, and respond however you want it to. notify sender and/or postmaster and/or store the mail in the error repository, destroy the mail, or anything else you might add. Adding new behavior is simply a matter of writing or using other matchers and mailets. d. > -----Original Message----- > From: jason sackett [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 16, 2001 7:21 PM > To: [EMAIL PROTECTED] > Subject: Valid Recipient Username Check > > > I wrote a working mailet to check each recipient's domain for > validity, but > I am also interested in the validity of the username portion of the email > address. > It seems that, for instance, I send an email using @home to a bad hotmail > address, @home responds with 'bad user', but JAMES is silent when > sending to > the same recipient. > Where might I look for more info on adding functionality to JAMES > to report > invalid usernames ala @home mailservers? > > Thank you for any help, > Jason > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
