On 2006-09-21 Marc Haber <[EMAIL PROTECTED]> wrote: [...] > We'll need to think about a way to support sender verification on a > system that uses a smarthost. Andreas' suggestion is a possible > solution, but we'll need to bring our minimaldns configuration option > in the game: We might be using a smarthost because we do not have > world-wide DNS available.
> Probably the most promising idea would be to only activate the > "smarthost_verify_dnslookup" router if minimaldns is not set and to > warn in the config that sender/recipient verification on a > smarthost-based system with minimaldns set is likely to generate false > negatives (verifying false addresses as correct). [...] Hello, I think that it is ok that sender and recipient address verification does not work for smarthost setups by default. - These setups are used mainly or two purposes: leafsite, @home workstation. - These sites generally are not open for remote connections. gateway host: Will need to be manually configured to use callouts or a manually synced list of remote-parts. The fact that it took years for somebody to actually discover that address verification does not work as expected suports my position. Having something like this in docs might do trick: ------------------- Sender and recipient address verification will not work for non-local domains using smarthost setups. As any non-local mail (or for satellite setups all mail) is simply sent on to the smarthost *all* non-local addresses are deliverable for exim and therefore verify. ------------------- cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]