Barney Desmond wrote:
* Noone's pointed out the your first packet capture also exhibits the
same "missing data" problem. After the client sends RCPT TO and you
respond with an Ok, the next thing it drops on the wire is "Received:
from srv1.shoppingsquare.com.au" in frame 12. I'm not that confident in
my packet capture-reading skills, but I'm not seeing a discontinuity in
the sequence numbers that Wietse saw in the second capture.
I've poked your server a bit and it appears to have zero tolerance for
errors. Your server should have responded immediately with "221 2.7.0
Error: I can break rules, too. Goodbye.". Instead it just ACK'ed the
packet and kept waiting, this seems odd.
All of the above is _way_ over my head, but I thought I'd throw out the
obvious suspect anyway. Silly oddities like above have the stench of
Cisco's attempt to 'fix' things. I've seen similar problems when 'SMTP
Fixup' is enabled (random sites dropping email because of 'timeout
waiting for data'). Unfortunately, these usually are small sites with
Exchange, in which case it is very easy to identify as the connect
string doesn't show the name, it will instead show '******* 220 ******
blah'. This has been on by default in every piece of Cisco equipment
that I've messed with (admittedly not many), did you try and disable it yet?
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
