Other paid for mail scanner/filters (these are ones that mail just passes thru) have the ability to check rcptto against an LDAP lookup. That would solve the problem, only Xmail would then need to be an LDAP server as well as an LDAP client.
So,...... Helo abc.com Mail from:<[EMAIL PROTECTED]> Rcpt to:<[EMAIL PROTECTED]> Lookup name in LDAP server, found, accept. Rcpt to:<[EMAIL PROTECTED]> Lookup name in LDAP server, not found, reject "unknown user" Data ....Etc. Potentially you would have a TAB that defined the domains and their method/location of LDAP lookup. This could therefore be used for other verification methods, but in the LDAP case, would define the server to query and the base DN. The LDAP support I can see going far further. What about those sites that have an existing x.500 based directory (NDS, MS AD, iPlanet, etc), they could use xmail as a frontend, verifying or even authenticating to the corporate LDAP server. This I can see a use for, but having hooks after each SMTP command (more or less) is a bit much. Recently someone posted having probs with too many filters running because of being hit by a burst of spam. Too many pitfalls. Rob :-) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi > Sent: Wednesday, February 04, 2004 7:19 AM > To: XMail mailing list > Subject: [xmail] Re: AW: Re: AW: Re: AW: Re: AW: Re: AW: Re: > SMTP Dialog Filter Hooks > > Let me think about this issue. It can be eventually solved in > another way. > > - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
