Gary Smith:
> I've been getting a lost of "lost connection after DATA" this last
> week. On our low volume servers (that houses some minor clients)
> we are receiving 800/day. We switched over to ipvsadm about 3
> weeks ago and I though maybe it's because of non-persistent
> connections. So I reset ipvsadm to be persistent to a given
> server.
>
> Anyway, we are still receiving them. The firewall allows port 25
> incoming, everything outgoing but there is also some nat'ing going
> on because of the ipvsadm. Anyone ever seen this type of issue
> with this type of config?
If the NAT assumes that everything is a web client and drops
connections after a few seconds, then Postfix will report lost
connections.
If the NAT keeps connections open but it is a crappy box that can
maintain state for only 100 connections, then it will be forced to
to drop connections, and Postfix will report lost connections.
> We are getting mail flow pretty consistently, but today we had a
> report of a bounce from a user who was trying to receive a rather
> large document via email and that's when I noticed that in most
> cases it's "lost connection after DATA from ... " but in the case
> of this users, "lost connection after DATA (xxxxxx bytes) from
> ..."
It would be tremendously useful for the people who are trying to
help you if you were show all the logfile records for a few
transactions including TIME STAMPS, process ID, and the number of
bytes after DATA. You can replace names and addresses by xxx.
Wietse
