4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] trying to get /usr/lo...
FromSent OnAttachments
Richard BatesJun 19, 2007 8:40 am 
Tony EarnshawJun 19, 2007 8:57 pm 
Devin RubiaJun 28, 2007 8:01 am 
Tony EarnshawJun 28, 2007 9:37 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] trying to get /usr/local/etc/maildroprc to workActions...
From:Devin Rubia (dev@thezone.net)
Date:Jun 28, 2007 8:01:53 am
List:net.sourceforge.lists.courier-maildrop

On Wed, Jun 20, 2007 at 05:58:14AM +0200, Tony Earnshaw wrote:

Richard Bates skrev, on 19-06-2007 17:41:

I am in the middle of a new mailserver config.

FYI: On the original Mailserver I used Qpopper. on this mailserver I am using courier-imap so these configs are new to me.

I have FreeBSD 6.2 with postfix,procmail,tls,sasl2, and maildrop installed

I got it to where I can send (postfix) and receive(IMAP) email I am trying to get spamassassin to kick in.

Hint: Don't do this with maildrop, do it in Postfix with a content filter (before or after queue), use amavisd-new, ask questions on the Postfix ML.

Just back from vacation. Sorry for the late reply, hope it helps..

If he can't or won't put it in a proper content filter then I noticed this snippet:

--- mailbox_command = /usr/local/bin/maildrop ${revipient}

---

Should be:

mailbox_command = /usr/local/bin/maildrop -d ${recipient}

Note the "-d" and the correct spelling of "recipient"

Also, in maildroprc there's "spamc -u spamd". maildrop will switch to the user being delivered to so ensure that all users are able to read spamd's spamassassin config file.