No I have never tried it with a file captured on another computer, nor do I think I ever will. However that should not matter in any way as long as the file is properly captured and has not become corrupt. Are you absolutely sure that there is any relevant info in the file for mailsnarf and msgsnarf to filter out for you?
The following commands work perfectly for me using a file captured with:
Code:
tcpdump -i eth1 -s 0 -w /tmp/testfile
Which is naturally done while properly connected to the network I am capturing on. In case you use a file sniffed with airodump-ng over wireless you will have to run it through airdecap-ng first to be able to replay it using:
Code:
tcpreplay /tmp/testfile -i lo -r 2
And finally I have both mailsnarf and msgsnarf running using:
Code:
msgsnarf -i lo
mailsnarf -i lo
And I am currently using BT3b.