text_combined: matt kettler sgngcnuc_vgverizonnet anny lei wrote dear developers using mailscanner spamassassin want spamassassin lookup ldap user preference put user_scores_dsn user_scores_ldap_username user_scores_ldap_password localcf test running command spamd ldapconfig x cat rootsamplespamtxt spamc u jndxtestdomaincom works perfectly fine mailscanner accepts email spamassassin doesnt lookup ldap user preference observed ldaplog file know specify ldapconfig x command spamassassin mailscanner calling spamassassin daemon spamd could please let know instruct spamassassin lookup ldap user preference running mailscanner thanks advance assistance followup part 2 realized tone message might lost im correcting avoid misguiding however please cease discussion list message belongs users list development list list designed discussion development efforts within spamassassin project usage questions directed users list developers read reply messages posted fundamentally mailscanner designed support peruser configurations isnt anything spamassassin change also something mailscanner easily changed top would also change mailscanner really defeat design criteria mailscanner generally speaking tools run mta mail transport agent layer dont support per user configuration support poorly really truly want peruser configuration best place call sa mda mail delivery agent layer ie via procmail calling mta layer suffers several problems want peruser configuration 1 mta layer tools must guess final recipient rcpt address work however address might alias odds webmaster user system alias roots mailbox etc etc etc generally theres many aliases system sites lots aliases mta layer userguessing breaks happens 2 mta layer message sent multiple users one message multiple recipients mta layer tool must make decision whos user preferences apply theres one message work use one generally use whoever came first recipient list ways around forcing message requeued separately introduces inefficiency mta side something happens naturally mda course mda layer tools call sa per recipient instead per message results calls sa cpu usage thats need peruser configurations properly tue 05 aug 2008 202718 0400 enable spamassassin user preference ldap running mailscanner