Robin S. Socha writes:
> * Sam Varshavchik <[EMAIL PROTECTED]> [010515 23:41]:
>> This build adds an autoreply capability. maildrop 1.3.2 is required.
>> Earlier versions of maildrop must be upgraded to 1.3.2 (conveniently
>> downloaded from the same page). The autoreply capability is implemented as
>> part of mail filtering, and mail filtering must be enabled.
>
> First of all: wow. This is *very* neat. However... :-)
>
> I'm running vpopmail/sqwebmail. What do I put in maildirfilterconfig to
> enable filtering for various domains? Right now, I have this for
> testing:
> MAILDIRFILTER=/usr/local/bin/maildrop
> MAILDIR=/home/vpopmail/domains/socha.net/$USER/Maildir/
It really depends on your actual layout. I would guess that for this
particular account you'll need to have maildrop invoked as "maildrop
domains/socha.net/$USER/.mailfilter", and put
MAILDIRFILTER=../.mailfilter
MAILDIR=domains/socha.net/$USER/Maildir
into maildirfilter.
> This won't work for the other domains on my machines. Also, I'm getting
> this error:
> "ERROR: You have an incompatible existing mail filter, contact your
> system administrator"
> He does not have a clue and talking to myself felt kinda weird, anyway.
>
> Also: this is, ummm... big?
>
> (root@mail1):(/home/vpopmail/domains/socha.net/robin/Maildir)# du -h
>maildirfilter.tmp
> 1.1M maildirfilter.tmp
That's because you told sqwebmail that the maildrop binary is the actual
mail filtering recipe, it obeyed and made a copy of the binary for itself.
And since it doesn't really look like a filtering recipe, sqwebmail returned
that error, without touching it.
--
Sam
