Re: Postfix + opemdim -> milter reject, come back later

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Sun, 4 Oct 2015 22:37:22 -0700 (PDT)

On Sat, 4 Jul 2015, Istvan Prosinger wrote:
> [140142330746624] milter_negotiate: mta_actions=0x1ff, mta_flags=0x7f actions=0x111, flags=0x2

Protocol negotiation

> [140142330746624] got cmd 'D' len 63

Declare a macro and its value

> [140142330746624] got cmd 'C' len 35

SMTP connection details

> [140142330746624] got cmd 'D' len 1

Another macro

> [140142330746624] got cmd 'A' len 0
> [140142330746624] abort: cur 2 (4) new 12 (1000) next 2018

MTA aborts the transaction

> [140142330746624] got cmd 'Q' len 0
> [140142330746624] abort: cur 3 (8) new 11 (800) next 12018

MTA quits the connection

> [140142330746624] got cmd 'O' len 12
> [140142330746624] milter_negotiate: mta_actions=0x1ff, mta_flags=0x7f actions=0x111, flags=0x2

New session, option negotiation

> [140142330746624] got cmd 'D' len 63

Macro

> [140142330746624] got cmd 'C' len 35

Connection details

> [140142330746624] got cmd 'D' len 1

Macro

> [140142330746624] got cmd 'A' len 0
> [140142330746624] abort: cur 2 (4) new 12 (1000) next 2018
> [140142330746624] got cmd 'Q' len 0
> [140142330746624] abort: cur 3 (8) new 11 (800) next 12018

MTA aborts and quits again

It looks to me like something in your MTA is deciding it wants to talk to
the filter and then changing its mind. The filter is never getting as far
as making a decision about th emessage; it never even sees the first
header field.

-MSK
Received on Mon Oct 05 2015 - 05:37:39 PST