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:Tony Earnshaw (teri@barlaeus.nl)
Date:Nov 29, 2006 2:59:10 pm
List:net.sourceforge.lists.courier-maildrop

Flemming Bjerke wrote:

To Sam and Tony, thank you for your replies. Of course, you are right that I don't know enough about maildrop.

But, well, I feel that the documentation is like many other man pages: The basic things are mentioned on equal footing with the refined details, and much information is just taken for granted. This is fine for the experienced user, but for the newbie it is confusing information overload and "under"load at the same time. It is not that I haven't tried reading documentation etc.

I quotes Sam: "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."

My basic question is: How do I get maildrop to read certain mailfilter files?

maildrop as built from standard source and installed as source or from rpms (the latter which we as Red Hat shop do) follows LFH (http://linuxgazette.net/issue93/lechnyr.html) rules reads a single configuration file in /etc, maildroprc, and/or user configuration files, ~/.mailfilter. The parameters these files obey are documented in man and html pages included with the source code and installed in standard locations at install time. Ok, it can take some time to go through this documentation (there's a fair deal of it and most of it is fairly complicated) and try things out to suit one's own site and one can expect some difficulties - that's what this mail list is for, and people will help if they can.

You want your maildrop (you still don't write what version it is [1], or where you got it [2], or exactly how you configured it ]3]) to read a non-standard configuration file in /var/courier and behave in an undocumented way. You write: 'I setup MAILFILTERDIR="/var/mail/mailfilter" But, maildrop does react to files in the directory. The same goes for .mailfilter files in the virtual directories.'

But in the real world of mostly everyone on this list there is *NO* /var/mail/mailfilter and there are *NO* .mailfilter files in any (which? what are?) virtual directories. Where did you "set it up" (I presume this is another Debian - "I have a debian sarge installation" - peculiarity) and why should Courier maildrop care anyway?

And I am not the only one who have had that problem: http://forums.bsdnexus.com/viewtopic.php?pid=3385 I must admit I haven't found any answers to that question ...

This is a Red Hat vs. BSD problem that has *nothing* to do with what you describe.

Please give the answers to [1], [2] and [3]. I'm no Debian man and my mindset (Unix SYSV and Linux LFH) can't cope with Debian vagaries (nett som jeg som nordmann ofte ikke kan med danske likedanne), but maybe there's a kind Debian person on the list who can.

--Tonni