Keith Mastin said:
>>Hi, Keith:
> <snip>
>>Are you using the MySQL support?  Are you using virtual accounts?  Can
>> you please turn on verbose logging in procmail, send yourself a message
>> that should be blocked then send me the log output?
>>
>>Thanks,
>>
>>Derek
>
> And so the fun begins:
> My procmail.rc file:
> # Procmail run-control file for mcleodlake.com
> # Installed and configured by Keith Mastin
> #
> #The following are used to test the block_senders SM plugin:
> VERBOSE=on
> LOGFILE=/var/log/procmaillog
>
> # Make sure procmail accesses the block-sender run-control file
> INCLUDERC=/web/mlib/html/mlib/webmail/plugins/block_sender/sqblock.rc.maildir
>
> # Procmail to deliver mail to $HOME/Maildir
> :0 c
> $HOME/Maildir/new
>
> Contents of /var/log/procmaillog after sending a message from a blocked
> domain:
> /var/log/procmaillog (END)
>
> The blocked senders list:
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]             <-
> [EMAIL PROTECTED]             <-
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]     <-
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]     <-
> [EMAIL PROTECTED]     <-
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]     <-
> [EMAIL PROTECTED]             <- <-- this is me
>
> <- indicates a domain or sender whom I have received a message from
> after  adding them to my block_senders list.
>
> However, the first problem seems to be that procmail is logging
> absolutely  nothing. I have to assume thqt procmail is working since all
> the mail gets  delivered.
>
> Here's the relevent line from my postfix/main.cf:
> mailbox_command = /usr/bin/procmail -m /etc/procmailrc
>
> Contents of the $mailuser$HOME:
> [EMAIL PROTECTED] root]# ls -a /web/mlib/members/keith.mastin/Maildir/
> .   .2002     courierimapuiddb  .Drafts   new    .Server      tmp
> ..  courierimapsubscribed  cur        .Mailman  .Sent  .Squirrelmail  .Trash
>
> And finally the headers from a message that should have been blocked
> according to the test:
> From [EMAIL PROTECTED] Sat Feb 22 10:08:24 2003
> Return-Path: <[EMAIL PROTECTED]>
> Delivered-To: [EMAIL PROTECTED]
> Received: from mail.beechtree.ca (beechtree.ca [216.138.194.32])
>      by mail.mcleodlake.com (Postfix) with ESMTP id C630FBB34
>      for <[EMAIL PROTECTED]>; Sat, 22 Feb 2003 10:08:23 -0800 (PST)
>
> Received: from soldier.beechtree.ca (unknown [192.168.0.117])
>      by mail.beechtree.ca (Postfix) with ESMTP id E14D3AD6A
>      for <[EMAIL PROTECTED]>; Sat, 22 Feb 2003 13:11:30 -0500 (EST)
>
> Received: by soldier.beechtree.ca (Postfix, from userid 500)
>      id F1282C753; Sat, 22 Feb 2003 13:12:23 -0500 (EST)
> Received: from localhost (localhost [127.0.0.1])
>      by soldier.beechtree.ca (Postfix) with ESMTP id EDB42D74B
>      for <[EMAIL PROTECTED]>; Sat, 22 Feb 2003 13:12:23 -0500 (EST)
>
> Date: Sat, 22 Feb 2003 13:12:23 -0500 (EST)
> From: Keith Mastin <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: block_senders test 5
> Message-ID:
> <[EMAIL PROTECTED]>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Everything seems to be in order from what I can tell, yet the mail  that
> should be blocked continues to be delivered.

But where's the verbose procmail log?  You say procmail's not logging
anything?  If procmail is indeed running then there should be a log file. 
If no log file is being produced by procmail then that would be a good
reason as to why the plugin isn't working.  You assume procmail is running
because your mail continues to be delivered.  This is not true.  If
postfix can't invoke the mailbox_command then it should, I believe, just
forget it and deliver the mail to the user's mailbox.

Finally,

> # Procmail to deliver mail to $HOME/Maildir
> :0 c
> $HOME/Maildir/new

To deliver a message to a maildir mailbox you should just specify
$HOME/Maildir/
The trailing slash is critical, that's what tells procmail it is indeed a
maildir mailbox.  Anyway, this is getting way off topic now... the first
thing you need to do is get procmail running and/or producing the verbose
log.  Whatever the problem is can usually be easily identified from the
verbose output of the procmail log.

HTH,

Derek




-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

Reply via email to