3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop in delivery ...
FromSent OnAttachments
Holger LibrenzDec 1, 2007 10:18 am 
Tony EarnshawDec 1, 2007 12:16 pm 
Holger LibrenzDec 1, 2007 3:22 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] maildrop in delivery mode does not filter (debian)Actions...
From:Tony Earnshaw (ton@hetnet.nl)
Date:Dec 1, 2007 12:16:27 pm
List:net.sourceforge.lists.courier-maildrop

Holger Librenz skrev, on 01-12-2007 19:19:

[...]

Could anybody help me?

Maybe. It's a long track and I don't know Debian much, I'm Red Hat.

Basically, to debug you have to feed a message to maildrop using its debug feature and read on stdout what it tells you.

Not only that, you *either* have to have your maildrop directive in Postfix's main.conf *or* in master.cf, *not* in both. master.cf is far to be preferred. Your master.cf stuff looks ok, but depends on an entry in your (postmapped) Postfix transport map. When you've done that, delete the entry in main.cf.

Assuming you have /usr/bin/maildrop (that's where it's supposed to be on Red Hat systems) correctly installed, save any message to anyone anywhere to any location sensible and do:

/path/to/maildrop -V5 -d user-to-send-to < /location/message

Watch, less or xterm scroll, stdout step by step and see what it does. Need more debugging? Substitute -V9 - but it shouldn't be necessary.

When you find out it's not doing what you want, go to *every one* of maildrop's many docs to find out why. If they don't help (they're the basis for me *and many thousands of others* being able to make maildrop work at all) then come back with what you've done and what doesn't work for you.

Best,

--Tonni