Shad L. Lords wrote: > > Robert Spier wrote: > > Charlie Brady wrote: > >> > >> On Wed, 4 Nov 2009, Filippo Carletti wrote: > >> > >>> In sme server we have some email aliases defined as visible=internal, > >>> that is internal users (relayclients) could write to them, but from > >>> outside the lan (non relay clients) the email address is not reachable > >>> (non existent). > >> I don't think this is the correct way to implement that feature. What > >> this patch says is to ignore badrcptto for relay clients. What you > >> really want is a different set of valid local recipients for relay > >> clients. The set of valid local recipients is being checked by a > >> different plugin. > > This might not be the best way to implement the feature but it is how > we implement it in SME currently. > > > I agree with Charlie. This isn't the right plugin for this change. > > If you want this functionality, you might want a plugin wrapper. > > What you need to ensure you can do is classify RCPT TO addresses into > the following categories: > > - Doesn't exist (nobody should send to this address) > - Exists but only allowed for local relay (internal) > - Exists but not allowed to receive email for anywhere > - Exists and allowed to receive mail from anyone > > The badrcptto plugin handles the third case but there isn't a plugin > to handle the second case. If an address is listed in badrcptto then > nobody can send to that address. The patch changes the behavior from > #3 to #2 and makes it so addresses that exist can be blocked from > external receipt but internal/auth users can send to it. However it > make it so there isn't a way to implement #3.
As I suggested before, a plugin wrapper is the way to do these site specific customizations. See "Inheritance" in docs/plugin.pod -R
