On Fri, Apr 15, 2011 at 3:19 PM, Sahil Tandon <[email protected]> wrote: > On Fri, 2011-04-15 at 09:50:16 -0700, Steve Jenkins wrote: > >> I saw this in my maillog just now: >> >> Apr 15 09:03:00 carbonfiber postfix/qmgr[28665]: 53D87104259C: >> from=<[email protected]>, size=16858, nrcpt=1 (queue >> active) Apr 15 09:03:01 carbonfiber amavis[28076]: (28076-20) Blocked >> BAD-HEADER, [50.22.180.134] [50.22.180.134] >> <[email protected]> -> <[email protected]>, Message-ID: >> <[email protected]>, mail_id: mlACmT6BzNRX, >> Hits: -, size: 17055, >> [email protected],[email protected], >> 181 ms Apr 15 09:03:04 carbonfiber postfix/smtp[31065]: 17795104259D: >> to=<[email protected]>, >> relay=ibu134.olepykorin.info[50.22.180.134]:25, delay=3.5, >> delays=0.05/0/3.5/0, dsn=4.0.0, status=deferred (host >> ibu134.olepykorin.info[50.22.180.134] refused to talk to me: 421 >> ibu134.olepykorin.info out of connection slots) >> >> Is that first "postfix/smtp" line sending a reject message to >> olepykorin.info? > > Did you set $final_bad_header_destiny (in amavisd-new) to something > other than D_PASS or D_DISCARD, even though you configured Postfix to > consult your content filter after-queue?
Thanks, Sahil. That was it. It was set to D_BOUNCE. I set it to D_PASS for now, but will set it to discard later if that's problematic. I love how Postfix logs everything, so that even if the problem is with a third-party content filter, Postfix can help me track it down. :) Best, SteveJ
