OnlineWoerterBuecher.de
Internes

Lexikon


nastygram


/nas' tee-gram/ 1. A network packet or e-mail message (the latter is also called a letterbomb) that takes advantage of misfeatures or security holes on the target system to do untoward things. 2. Disapproving e-mail, especially from a net.god, pursuant to a violation of netiquette or a complaint about failure to correct some mail- or news-transmission problem. Compare shitogram, mailbomb. 3. A status report from an unhappy, and probably picky, customer. "What did Corporate say in today' s nastygram?" 4. [deprecated] An error reply by mail from a daemon in particular, a bounce message. [Jargon File] (2004-02-17)

In addition suitable contents:
[ 2 ] [ = ] [ ad ] [ ae ] [ ag ] [ ai ] [ al ] [ am ] [ an ] [ app ] [ ar ] [ arc ] [ arg ] [ as ] [ at ] [ b ] [ ba ] [ bo ] [ bomb ] [ bounce ] [ bounce message ] [ by ] [ C ] [ ca ] [ cat ] [ ch ] [ ci ] [ ck ] [ co ] [ com ] [ cu ] [ D ] [ daemon ] [ de ] [ deprecated ] [ do ] [ du ] [ ec ] [ ed ] [ ee ] [ e-mail ] [ er ] [ error ] [ es ] [ et ] [ failure ] [ feature ] [ fi ] [ file ] [ fr ] [ ge ] [ gr ] [ gs ] [ h ] [ hat ] [ hing ] [ hit ] [ hole ] [ hr ] [ id ] [ il ] [ in ] [ int ] [ io ] [ iq ] [ is ] [ it ] [ J ] [ Jargon File ] [ ke ] [ ki ] [ ky ] [ la ] [ lb ] [ letterbomb ] [ Lex ] [ ls ] [ lu ] [ ly ] [ ma ] [ mail ] [ message ] [ misfeature ] [ mo ] [ mod ] [ module ] [ mp ] [ na ] [ nc ] [ ne ] [ net ] [ net.god ] [ netiquette ] [ network ] [ networking ] [ news ] [ ng ] [ ns ] [ om ] [ pa ] [ packet ] [ pe ] [ ph ] [ pl ] [ ply ] [ port ] [ pr ] [ py ] [ query ] [ rc ] [ re ] [ reply ] [ ro ] [ sa ] [ say ] [ se ] [ sh ] [ shitogram ] [ si ] [ sm ] [ so ] [ spec ] [ st ] [ su ] [ sy ] [ system ] [ tag ] [ tar ] [ target ] [ tee ] [ th ] [ to ] [ tr ] [ tt ] [ tw ] [ ua ] [ us ] [ va ] [ vi ] [ ws ]






Go Back ]

Free On-line Dictionary of Computing

Copyright © by OnlineWoerterBuecher.de - (5472 Reads)

All logos and trademarks in this site are property of their respective owner.

Page Generation in 0.1993 Seconds, with 17 Database-Queries
Zurück zur Startseite