[Tcpick-project] Tcpick 0.1.23 bug?

[Penelope F. <ke...@pk...>]

Hi..

I've got a tcpdump program running that logs all email to & from the
mail server.

When I use 'tcpick -wR -r log-2004.xx.xx', and look at the resulting
client and server files, there are binary strings stuck in the middle of
the conversation:


           0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
       0:  a0 00 00 00 00 00 45 48 4c 4f 20 6d 78 31 30 30  "......EHLO mx100"
      10:  2e 64 61 63 65 68 61 64 6f 2e 75 73 0d 0a a0 00  ".dacehado.us...."
      20:  00 00 00 00 52 43 50 54 20 54 4f 3a 20 3c 64 77  "....RCPT TO: <pr"
      30:  6f 6f 64 40 76 69 73 69 6f 6e 32 68 69 72 65 2e  "ood@vista2river."
      40:  63 6f 6d 3e 0d 0a a0 00 00 00 00 00 44 41 54 41  "com>........DATA"
      50:  0d 0a a0 00 00 00 00 00 46 72 6f 6d 3a 20 22 50  "........From: "P"
      60:  61 72 61 64 69 67 6d 20 43 6f 6d 6d 75 6e 69 63  "aradigm Communic"
      70:  61 74 69 6f 6e 73 22 20 3c 48 65 69 64 69 52 6f  "ations" <HeidiRo"
      80:  73 65 40 6d 78 31 30 30 2e 64 61 63 65 68 61 64  "se@mx100.dacehad"

Where are these 'A0 00 00 00 00 00' chunks coming from?  I thought that
-wR was binary-safe.  When I follow the stream using Ethereal, the
problem goes away.

Thanks!
-- 
Penelope Fudd <ke...@pk...>