> 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.
The problem here is that in a typical postfix post-queue setup, amavisd is invoked before local delivery agent, which means that aliases are not yet expanded by the time a message reaches a content filter. If you'd do your mail address rewrites by a virtual map (instead of by aliases), then you have some control over it - virtual maps can apply before or after a content filter. So this is one possibility of getting around the issue, although admittedly it is not to everybody's liking. If your aliases are in SQL tables too, then, as Thomas said, it is possible to wrestle SQL select templates used by amavisd to take into account aliases expansions before it actually happens. A third option that I see, in case you could do without feeding outbound mail to amavisd, is to splice amavisd between a Postfix LDA and a back-end LMTP mailbox delivery (like cyrus or dovecot). In this case amavisd would speak LMTP both on its input and on its output side. A drawback to this solution is that outbound mail is not checked for viruses and spam, DKIM signing can't be used, and penpals does not work. Mark ------------------------------------------------------------------------------ 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/
