cause of enabling a lot of PIX workarounds?

[micah milano]

I recently upgraded one of my debian etch machine's postfix instances
to 2.4.5-4~bpo40+1 from 2.3.8-2+b1. Since then I have been getting a
large number of PIX workaround messages in my log:

Oct 14 07:17:09 mx2 postfix/smtp[19174]: C7A449FF58: enabling PIX
workarounds: disable_esmtp delay_dotcrlf for
mx01.critpath.org[0.0.0.0]:25

In the last week, I've seen on average 3476 of these a day, we
delivered an average of 398279 messages a day, so this is a small
percentage of the total deliveries.

I'm trying to decide what I should do with these, currently I'm
getting them in my logcheck reports. Can I just ignore them? It seems
like a pain to parse the logs every day to pull out the domains and
create a map that needs these domains to have this special
disable_esmtp delay_dotcrlf set.

Thanks,
micah

[Ralf Hildebrandt]

* micah milano <mic...@gmail.com>:

> In the last week, I've seen on average 3476 of these a day, we
> delivered an average of 398279 messages a day, so this is a small
> percentage of the total deliveries.
>
> I'm trying to decide what I should do with these, currently I'm
> getting them in my logcheck reports. Can I just ignore them? It seems
> like a pain to parse the logs every day to pull out the domains and
> create a map that needs these domains to have this special
> disable_esmtp delay_dotcrlf set.

What for? Postfix enables the workarounds automatically.

--
Ralf Hildebrandt (Ralf.Hil...@charite.de) pl...@charite.de
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
Our continuing mission: To seek out knowledge of C, to explore strange
UNIX commands, and to boldly code where no one has man page 4.

[micah milano]

On 10/14/07, Ralf Hildebrandt <Ralf.Hil...@charite.de> wrote:
> What for? Postfix enables the workarounds automatically.

Then it is safe to ignore these errors?

Micah

[Ralf Hildebrandt]

* micah milano <mic...@gmail.com>:

> On 10/14/07, Ralf Hildebrandt <Ralf.Hil...@charite.de> wrote:
> > What for? Postfix enables the workarounds automatically.
>
> Then it is safe to ignore these errors?

These are no errors -- these are warnings :)

--
Ralf Hildebrandt (Ralf.Hil...@charite.de) pl...@charite.de
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de

If JavaScript is walking alone late at night through a bad part of
town with a pocket full of $20 bills, ActiveX is dropping your
trousers in the middle of the yard of a maximum-security prison,
bending over, and yelling 'Come and get it, boys!'

[mouss]

Ralf Hildebrandt wrote:
> * micah milano <mic...@gmail.com>:
>> On 10/14/07, Ralf Hildebrandt <Ralf.Hil...@charite.de> wrote:
>>> What for? Postfix enables the workarounds automatically.
>> Then it is safe to ignore these errors?
>
> These are no errors -- these are warnings :)
>

not even warnings. I'd call them "notices". they may be helpful if you
detect a problem with a remote site and need infos for debugging.

[mic...@gmail.com]

On Oct 14, 5:11 pm, mouss <mlist.o...@free.fr> wrote:
> Ralf Hildebrandt wrote:
> > * micah milano <mic...@gmail.com>:

> >> On 10/14/07, Ralf Hildebrandt <Ralf.Hildebra...@charite.de> wrote:
> >>> What for? Postfix enables the workarounds automatically.
> >> Then it is safe to ignore these errors?
>
> > These are no errors -- these are warnings :)
>
> not even warnings. I'd call them "notices". they may be helpful if you
> detect a problem with a remote site and need infos for debugging.

Ok, so I am getting these with a remote site along with "conversation
timed out while sending end of data -- message may be sent more than
once", I've found out that the remote site is using a Cisco PIX 1510.
Where can I find details about this particular bug so I can send them
on to the remote admin? It seems there is a smtp_fixup mode that
causes this, but is there an actual fix (besides turning that off), or
details about what specifically is happening?

Thanks,
Micah