Lost connection while sending end of data

[Diego Alencar Alves de Lima]

Hello all,

I currently have a postfix MTA working together with a content filtering
solution (Trendmicro's IMSS)and I've been receiving the following errors
constantly:

(lost connection with localhost[127.0.0.1] while sending end of data --
message may be sent more than once)

The message are never delivered and as of now it's causing a queue of
over 100 messages and filling up slowly. Could this be a problem with
postfix?

I've read some suggestions that this error could be caused by path
discovery, but since both postfix and the content filter are in the same
machine I don't think it could be this.

How can I further debug the problem? It's a problem that is really
becoming critical. Thank you.

--
Diego Lima
www.diegolima.org

[Diego Alencar Alves de Lima]

Em Sex, 2007-08-31 às 23:30 -0400, Wietse Venema escreveu:
> The SMTP server on 127.0.0.1 did not respond to "end of data" within
> $smtp_data_done_timeout seconds (default 600s, or 10 minutes, as
> recommended by the RFC).

The messages do not take long to be deferred. I see the error as soon as
I flush or requeue these particular messages. And this doesn't happen to
all messages, just some specific few.

Could there be another reason for this message other than a timeout
while waiting for the smtp response?

[er...@media.virogo.com]

Diego,

Finally someone who has almost the same problems with IMSS 7 as we
have.
There seems to be a problem in IMSS when sending mail to another
server.
My private servers SMTP log notes: connection closed due to 3 bad
commands.
Also changing the IdleWaitingTime=30 to value 60 in tsmtp.ini (Trend
Micro\IMSS\Config) did not work as I see a tsmtp.ini.db which contains
the default 30 seconds.
With us, mail arrives partially at the other side and connection seems
to be closed or not responding and Trend waits for an ACK after
sending QUIT or RSET or whatever.
I think there is a timing problem that Trend is not waiting enough or
is sending data while the other side was not ready yet.
Cause maybe that explains the 3 bad commands, which is in my private
mailserver a setting to close the connection after receiving more than
X bad commands.
It is prety tough to get some support from Trend as we are an
Enterprise user.... So have to contact my Reseller which is nagging me
about service tickets to buy as I already know he won't be able to fix
this. It's up to Trend for this buggy SMTP thing...
BTW, using a Disclaimer Stamp?
See for yourself where Trend puts it in an HTML mail.
Yep, the wrong place.
Some email clients won't see the disclaimer...
Another bug for Trend...