I understand amavisd-new scans emails differently than spamassassin itself does. When I was running SA on it's own, my "real" account ./ spamassassin/user_prefs white/blacklist items applied to my "real" account and all my mail aliases on the host.
I recently switched my lookups in amavisd-new to sql, so I can have per-recipient spam threshold values and white/blacklist entries. My issue is I'd like to apply my "real" white/blacklist items in amavisd sql to my "real" address/account and all (or a subset) of my mail aliases. I don't want to replicate my white/blacklist for each of my (many!) mail aliases. Ideally I'd like control over which of my "real" account amavisd-new sql white/blacklist items get applied which mail aliases, but would be happy with just applying my "real" W/B values to ALL mail aliases of that account. I've been searching high and low for this sort of thing and trying to figure it out myself, but time has run out on me and I've gotta ask. From what I can tell it may be something done outside of amavisd-new. Is the resolution tied to postfix? I've seen a few posts indicating at least one way to fix this is related to postfix. ubuntu server 8.10 postfix amavisd-new spamassasin Thanks, Mike -- [email protected] "Beware of all enterprises that require new clothes."-Thoreau ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
