Re: [SPAM] Some messages fail delivery in postfix -> maildrop -> crm114 chain

On 01/06/14 04:00, Sam Varshavchik wrote:
> glen martin writes:
>
>> Here is my ~/.mailfilter:
>>
>>    <snip>
>>    MAILDIR="$HOME/.maildir"
>>    DEFAULT="$MAILDIR"
>>
>>    logfile "maildropfilter.log"
>>    log "=========="
>>
>>    xfilter "/usr/bin/crm114 -u $HOME/.crm114/ 
>> $HOME/.crm114/mailfilter.crm"
>>
>>    log "----------"
>>
>>    if (/^X-CRM114-Status: SPAM/)
>>            to "$MAILDIR/.0_checkspam._R_spam"
>>
>>    </snip>
>>
>> The immediate symptom is that the some messages sit spooled forever 
>> (until they expire, I suppose).  mailq gives me a whole bunch of 
>> items that look like this:
>>
>>    <snip>
>>    51EE7520BA     1981 Sat Jan  4 11:27:34  MAILER-DAEMON
>>    (temporary failure. Command output: /usr/bin/maildrop: Unable to 
>> filter
>>    message.)
>
> This usually indicates that the external command invoked via xfilter 
> has terminated with a non-zero exit code, indicating an error.

Hi Sam, Thanks for your response.

That was my suspicion as well.  To test that, I've tried calling the 
maildrop command from the shell, in both delivery mode and not, piping 
the same message content. In essence, trying my best to duplicate how 
postfix would have called.  The return code was 0 in those tests, the 
message was delivered successfully both ways. You'll see details farther 
down in my original message.

Is there a way to catch the return code and log information from 
maildrop when it is called from postfix in delivery mode?

glen




------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk