Derek Broughton wrote: > From: "Viraj Alankar" <[EMAIL PROTECTED]> > >>Now by being able to see this traffic, we can do some interesting things. > > If > >>anyone has played with dsniff, there are 2 tools in that package that come > > to > >>mind: mailsnarf and tcpkill :). For those that do not know, mailsnarf >>basically dumps out SMTP monitored traffic in mbox format. tcpkill can be > > used > >>to kill TCP connections by sending RST's to both endpoints. >> >>So we have a way of seeing all mail traffic, and a way to kill a > > connection. > > You're treading on _very_ dicey legal ground. If you were to deliberately > take a copy of MY outbound mail, for any purpose whatsoever, I'd certainly > want to sue you. If you can _count_ the mails they send (without copying > the contents) _and_ you have contractual limits on their accounts, you may > be fine, but I wouldn't want to count on it.
The laws for this sort of thing focus around long-term storage and human reading, not computer reading. I don't think there'd be any legal issue for a carrier, provided it didn't break their contract (which is the only area of relevant legality). Matt. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
