Re: Placement of reject_unverified_recipient in main.cf
- Robert Fitzpatrick wrote:
> On Fri, 2007-04-27 at 15:12 +0200, mouss wrote:that would be good. but you can do the verification with
>> also, if you can put constraints on authorized sender domains for each
>> (or some) customers, it will help eliminate part of the spam (viruses
>> using random sender addresses.... etc).
> Thanks again, we are currently trying to setup LDAP to handle this as it
> already does have the domains we handle for transports. I would also
> need all the user info in LDAP as well I'm assuming to verify senders?
reject_unverified_sender, but again, do this only for the domains you
relay for (let a check_sender_access return a reject_unverified_sender
if the sender is in one of these domains). It is however better to have
the list locally, but that may or may not be pratical.
> Once we have integrated our scripts with our user systems, I plan to
> drop AV. We use CentOS+BQ on those user managed servers and don't want
> to have to build or switch GUI's. I just finished the script to load
> entries into LDAP from those DB files used on those systems, just need
> to integrate with the GUI so user changes are live. Otherwise, I'll be
> getting those calls to find out why they just entered a user and it
> doesn't work.