* bsd <[email protected]>: > I am trying to figure out what is the best solution in order to filter > incoming e-mail on a front-end relay server quite heavily loaded (100.000 > messages / day).
Even if you assume that all those messages will be sent within 8 hours (business time) it will boil down to ~ 3.5 msg/sec. Server hardware can do that easily. > We are using LDAP querry in amavisd-new in order to check if the e-mail > account exists in our LDAP DB. Bad idea. > Internet <--> Relay [Postfix + Amavisd-new] <--> Internal postfix > | | > | | > --------[LDAP database]---------- > > > > Since update of our amavisd-new server to version 2.7.0 we are having > problem with the LDAP lookup. > > I was wondering if It was not better to do this lookup before delivering the > e-mail to the amavisd process ? Good idea. Reject any message that can't be delivered immediately. That's cheap. It takes place in the SMTP session before the payload has been sent and before a content filter, such as amavis, does ressource intensive filtering. > If the answer is positive, should I use the "local_recipient_maps" parameter > or is there another more efficient method to be used ? Depends on the namespace the recpient domain is in. p@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>
