>From: "Darrell May" <[EMAIL PROTECTED]>
>
> or [option-2]:
>
> # Allow any of our valid e-mail accounts per any of our domains
> allow:ALL:ALL:[EMAIL PROTECTED]
> allow:ALL:ALL:[EMAIL PROTECTED]
> allow:ALL:ALL:[EMAIL PROTECTED]
> allow:ALL:ALL:[EMAIL PROTECTED]
> allow:ALL:ALL:[EMAIL PROTECTED]
> allow:ALL:ALL:[EMAIL PROTECTED]
> <snip>
>
> Both are possible. The logic would be based on what is already in
> '30InternalOnly' & '60AllowLocalDomains' with only minor modifications. I
> suppose [option-2] may be preferrable but I'm also wondering if [option-1]
> would be enough on it's own.
>
> Any comments/concerns before I build and release for testing?
It has to also catch the lists automatically constructed for 'groups' and
it would be nice to have a provision for additional aliases/lists that
might be added with ezmlm or similar tools.
Also, I have a case where I'd like something different, at least temporarily.
I'd like to be able to let an SMEserver accept mail as the primary MX for
a domain, but only host a subset of the addresses. This would be a lot
easier if there were a way to set the equivalent of sendmail's LUSER_RELAY
to forward unknown local-looking addresses to another machine. Otherwise
I'll have to add all the addresses as local users and forward individually to
the other destination. It would also help for similar situations if the
'pseudonym' form allowed you to supply arbitrary remote addresses instead
of being restricted to existing local users.
Les Mikesell
[EMAIL PROTECTED]
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
