Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Dell Technologies Inc. -- Ignore unavailable to you. Want to Upgrade?

To: ratan lal who wrote (76937)	11/6/1998 9:48:00 PM
From: TigerPaw	Read Replies (1) \| Respond to of 176387

OT Denial of Service return receipt mechanism Some mail like Microsoft Office has a feature which when set on mail will cause a message to be sent back to indicate that the mail has been read. There are also auto-forwarding rules. I suspect any of these features can be spoofed. TP

To: ratan lal who wrote (76937)	11/7/1998 8:13:00 AM
From: rudedog	Respond to of 176387

ratan - When I opened the mail, did the original mail to me get transmitted to the million people on sage1's list ?? That too as a mail from me ?? Under normal rules the receipt will just go to the sender, although there are ways to set rules which do almost anything. Getting someone else's mail system to do that is a lot harder. As intelligent messaging and data-dependent routing become more common (which they will, as in normal use these produce big gains in efficiency of transfer), it becomes more possible to give 'hints' to the various parts of the system which cause these kinds of unfortunate results. For the most part opening mail is 'safe' in the sense of not putting your own system at risk, but increasingly, clever hackers are finding ways to game the system to create nuisance attacks. I think it is unfortunate that people take the time to intentionally screw things up for others but that has been a part of the 'techie' culture since computers were invented. I once had my 2 lead programmers spend a fair amount of their time on this kind of stuff, each finding ways to make the other guy's life hard, doing things like changing the OS to detect that the other programmer was doing a compile, then setting the priority of the compile so low it took forever. Both of them learned a lot about OS fundamentals and security playing this game, and there was no real ill-will. But those same skills can be used to create havoc for the average user.