Marcus Ilgner wrote:
> On 10/12/06, Stephen Reese <[EMAIL PROTECTED]> wrote:
> > Shortly have emailing the listserv I though about that and change
> > the maildroprc file around so that spam would hopefully be flagged
> > and dealt with before the .mailfilter was read. After making the
> > change and reloading courier no mail or spam were processed. Any
> > other ideas?
>
> That is indeed quite strange. On my server, every user has a
> .mailfilter file (mostly empty, though). My configuration is not very
> different from yours and looks like this:
>
> import SENDER
> # send all messages < 512KB through spamassassin
> if ($SIZE < 524288)
> {
> exception {
> xfilter "/usr/bin/spamc"
> }
> }
>
> if ( /^X-Spam-Flag: YES/ )
> {
> to "$HOME/Maildir/.Spam/"
> }
> else
> {
> # execute the users mailfilter
> include "$HOME/.mailfilter"
> # if it didn't do this already, deliver to the Inbox.
> to "$HOME/Maildir/"
> }
Unless I'm missing something... Isn't that last 'else' block
completely unnecessary? As I understand it, maildrop works like this:
- Process maildroprc file
- Process $HOME/.mailfilter
- Deliver to $HOME/Maildir
(of course, a final delivery instruction interrupts the process)
So what is the point of specifying this behavior explicitly?
--
Bowie
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
