On Sat, Apr 14, 2012 at 1:29 PM, Noel Jones <njo...@megan.vbhcs.org> wrote:
> On 4/14/2012 12:16 PM, Schiz0 wrote:
>> Hello list,
>>
>> I currently have a working setup with Postfix 2.9.1 with av and spam
>> filtering with ClamAV and spamassasin, respectively. They are
>> intergrated via amavis-new using a post-queue content filter.
>>
>> I would like to add maildrop into the mix. I have maildrop installed,
>> and I would like to know what the best method is for doing so. I'd
>> like to use maildrop only for filtering mail into specific folders. I
>> am using Maildir format, and system users (No virtual users).
>>
>> I've seen two examples online. The first using:
>> mailbox_command = /usr/local/bin/maildrop -d ${USER}
>
> That's easiest if your domains are listed in mydestination.
>
>>
>> and the second adding a maildrop service into master.cf.
>
> That's easiest if you're using virtual_mailbox_domains.
>
> But either way will work.
>
>>
>> Also, what is the best method of integrating clamav and spamassassin?
>> Right now, as I mentioned, I am using amavis-new.
>
> amavisd-new is fast[1], reliable, and well supported.
>
> [1]spamassassin accounts for 90%+ of the time spent in amavisd-new.
> Amavisd-new speeds up spamassassin by pre-loading modules and
> scanning multiple-recipient mail only a single time. Moving
> spamassassin to maildrop will lose some of this speedup.
>
>> Would it be better
>> to integrate the two filters into maildrop as well?
>
> "better" is very subjective in this case. Doing the filtering in
> maildrop would allow end-users to more easily add or bypass the
> filtering, but will likely be lower performance.
>
> Both are valid solutions; you get to pick what works best in your
> environment.
>
>
>
>
> -- Noel Jones
Ok, thank you for the information and advice. It's very helpful to
have a personal response to all this software, since google returns so
many different ways of doing things.
I appreciate it.
