I have the notify sender uncommented so that my fakedomain mailet works.
And I thought of the xxxIsLocal for local users, but it's all about remote
delivery.
Does this mean that I need to write a mailet that does a manual remote
server connect and VRFY on each recipient in order to get the '550 no such
user' for a remote user?
That approach seems to be the job of JAMES rather than a mailet;  unless
there is an API accessable in the mailet that uses the core of JAMES (as a
mailserver) to find this 550 before JAMES gets it and swallows it.
Please let me know if I am way off base here.
I think I am getting the picture..
Let me know if this is correct:
Any error must be found in a configured mailet, or it is not found.
If no mailet can detect 550 before a remote delivery attempt then the error
is lost.

If that is true then I would imagine that someone must have a mailet that
does this.
Although I was surprised that I had to write my own 'RecipientInFakeDomain'
matcher.

Thanks for any help,
Jason

----- Original Message -----
From: "Danny Angus" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 16, 2001 4:44 PM
Subject: RE: Valid Recipient Username Check


> 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]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to