9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] mailfilter does not r...
FromSent OnAttachments
Flemming BjerkeNov 27, 2006 2:52 pm 
Sam VarshavchikNov 27, 2006 3:37 pm 
Tony EarnshawNov 27, 2006 11:37 pm 
Flemming BjerkeNov 29, 2006 7:52 am 
Tony EarnshawNov 29, 2006 2:59 pm 
Flemming BjerkeDec 6, 2006 6:24 am 
Sam VarshavchikDec 6, 2006 3:29 pm 
Flemming BjerkeDec 6, 2006 10:27 pm 
Sam VarshavchikDec 7, 2006 4:10 am 
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] mailfilter does not reactActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Nov 27, 2006 3:37:28 pm
List:net.sourceforge.lists.courier-maildrop

Flemming Bjerke writes:

I have a debian sarge installation with vhcs incl. postfix. I have setup maildrop as delivering agent, and it works and delivers mails in Maildir at

/var/spool/mail/virtual/

But, maildrop does not respond in any respect to mailfilter files. In /var/courier/maildroprc, I setup

MAILFILTERDIR="/var/mail/mailfilter"

But, maildrop does react to files in the directory.

Why gave you the idea that it would "react", in the first place?

I thought that maybe I forgot something, at my ripe old age, so just for kicks I searched maildrop's entire tarball for any mention of a variable called "MAILFILTERDIR". I found nothing. You might as well have set "XYZFOOBARBLAZ=/var/mail/mailfilter", and that would not've made any difference either. There's nothing in maildrop's source code that does anything, with this variable. Therefore, you must be referring to something that's particular to the "debian sarge installation with vhcs incl. postfix" version of maildrop, that must have some customized code that does some magic, with this variable. I can't offer any help here, because all I can help you is with plain, garden-vanilla, maildrop.

What is wrong?

Obviously you've installed maildrop with non-default configuration settings, or other customizations. What's wrong is that you have not explained how you installed and configured maildrop, and how you expect your customized configuration to work.

(I have tried to put -M /var/mail/mailfilter in postfix master.cf. It helped

No, it didn't. What would've helped would you if you went back, and read the explanation of this option in maildrop's man page, which tells you that this flag causes maildrop to run in embedded mode. This is followed by an entire section in the man page, called "EMBEDDED MODE", that explains what it does. One of the things is that all commands that actually deliver mail get disabled in embedded mode, and that's obviously not what you wanted.

I think that you just went too fast. You need to slow down, and take things one step at a time. You have a sophisticated Postfix configuration. Trying to integrate maildrop in a custom environment, such as that, without previous experience is just not going to work. First, you should try to get maildrop working with ordinary /etc/passwd accounts. Once you're comfortable

in the sense that maildrop looked for at filterfile, but it gave other problems, i.e. it couldn't find the virtualhosts).

There's nothing in maildrop's code that "finds the virtualhosts", whatever that means. Again, you must be referring to some feature that are particular to whatever custom version of maildrop you installed. You should go back and read the documentation for that feature, also. There's a slight chance that someone on this list might recognize the specific custom version of maildrop you're running, but that's not very likely.