On 6/13/2008, GrayHat ([EMAIL PROTECTED]) wrote: > Maybe I was unclear; I'll try to explain it better; let's say we have > ASSP sitting somewhere and acting as an MX (MTA);
Well, it is NOT an MTA... it is a PROXY... but yeah, I am with you so far... > our ASSP receives an SMTP connection from an external MUA, ? it generally only accepts connections from other MTAs, not MUAs... at least that is the only way I have ever used it... > the sender starts the session then sends in an "RCPT TO" command; at > this point ASSP sends a "VRFY" command to the backend mail server to > check it the entered recipient address is valid, and, depending on > the response ASSP accepts or reject the recipient (as it happens now > if you enable the LDAP validation); on the other hand, if an outside > MTA connects to ASSP and sends in a VRFY command, ASSP will disallow > it (from the external) and emit an error > > more clear now ? No... I WANT ASSP to only accept mail from other MTAs for valid recipients... thats the whole point of recipient validation. Let *me* be clear... ASSP should almost *always* (there are some very specific and rare circumstances where this may not be the case) perform recipient validation for *all* domains - and *only* domains - that it is authoritative for. -- Best regards, Charles ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
