From section 22.2 of the spec:
It is usual to set no_verify on redirect routers which handle
users’ .forward files, as in the example above.
[...]
...the existence of a .forward file is unimportant when verifying an
address. What should be checked is whether the local part is a valid user
name or not.
I don't quite follow this. If I have bgates@??? as a user account,
but bill@???, bgates@???, and bill@??? all go to the same
place via redirect routers, shouldn't any one of these verify? What happens
if the user is sending mail with a default from address set to one of his
aliases (this is the case sometimes)?
I don't have no_verify in place now, and am just a bit hesitant to add it
without understanding the implications more fully.
Cheers,
--
Casey Allen Shobe | cshobe@??? | 206-381-2800
SeattleServer.com, Inc. |
http://www.seattleserver.com
