Re: .mailfilter rule mysteriously not followed

On Sat, Jan 26, 2013 at 8:01 PM, Dr Michael Daly <[email protected]> wrote:
> thanks, but still have a major anomaly.

I just wanted to reiterate what Sam said.  It does not appear that the
problem is with maildrop.  It appears that your issue is how mail is
being handled in Postfix.

Let's get rid of all of the extra stuff in your logs:

> fetchmail: 6.3.24 querying mydomain.com.au (protocol POP3) at Sun Jan 27
> fetchmail: 1 message for lists at mydomain.com.au (1357 octets).

So you're querying for user "lists".

> fetchmail: reading message [email protected]:1 of 1 (1357 octets)About
> fetchmail: Trying to connect to 127.0.0.1/25...connected.
> fetchmail: SMTP< 220 NASC2089B.localdomain ESMTP Postfix

And it gave it to your local Postfix.  Your local postfix then must be
configured to pass that mail to maildrop for the recipient that it's
addressed.

Thus far, you have shown how maildrop is configured, but you have not
shown how you have configured postfix to call maildrop.  That is where
your problem will lie.

...Todd
-- 
The total budget at all receivers for solving senders' problems is $0.
 If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d