Talk:2822: *@gmail.com - Revision history

172.71.218.46 at 14:56, 9 December 2023

2023-12-09T14:56:34Z

172.71.147.71: Bedlam DL3 at Microsoft

2023-09-26T17:45:23Z

Bedlam DL3 at Microsoft

172.71.147.84: wallet

2023-09-23T04:08:11Z

wallet

162.158.74.23 at 22:12, 1 September 2023

2023-09-01T22:12:16Z

Yorkshire Pudding at 21:49, 1 September 2023

2023-09-01T21:49:20Z

172.70.90.138 at 10:38, 1 September 2023

2023-09-01T10:38:08Z

IMSoP at 09:51, 1 September 2023

2023-09-01T09:51:01Z

RandalSchwartz: add * email

2023-08-31T23:28:42Z

add * email

141.101.68.99 at 16:36, 31 August 2023

2023-08-31T16:36:11Z

IMSoP at 14:14, 31 August 2023

2023-08-31T14:14:45Z

← Older revision		Revision as of 14:56, 9 December 2023
Line 30:		Line 30:

	I wonder if there is a reference here to Microsoft in the late 90s when a no reply distribution list with a third of the employees had permissions set incorrectly. Then somebody on the list noticed noticed. It took down the Microsoft internal network for 2 days (network, not just mail, due to replication between Exchange servers!). The DL was amusingly called Bedlam DL3. For older MSFT employees the phrase “Bedlam DL3. Me too!” has a resonance. I think this might have been the first major email storm. For more details: [https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643] [[Special:Contributions/172.71.147.71\|172.71.147.71]] 17:45, 26 September 2023 (UTC)		I wonder if there is a reference here to Microsoft in the late 90s when a no reply distribution list with a third of the employees had permissions set incorrectly. Then somebody on the list noticed noticed. It took down the Microsoft internal network for 2 days (network, not just mail, due to replication between Exchange servers!). The DL was amusingly called Bedlam DL3. For older MSFT employees the phrase “Bedlam DL3. Me too!” has a resonance. I think this might have been the first major email storm. For more details: [https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643] [[Special:Contributions/172.71.147.71\|172.71.147.71]] 17:45, 26 September 2023 (UTC)
		+
		+	The comic reminds me of some gsuite enumeration tricks I’ve seen on OSINT twitter — getting a big list of an institution’s every email is, well, quite useful. —[[Special:Contributions/172.71.218.46\|172.71.218.46]] 14:56, 9 December 2023 (UTC)

← Older revision		Revision as of 17:45, 26 September 2023
Line 28:		Line 28:

	Fun fact: The Amazon corporate slang term for this is "Walleting", named after the subject line of one of the company's first widespread email storms. [[Special:Contributions/172.71.147.84\|172.71.147.84]] 04:08, 23 September 2023 (UTC)		Fun fact: The Amazon corporate slang term for this is "Walleting", named after the subject line of one of the company's first widespread email storms. [[Special:Contributions/172.71.147.84\|172.71.147.84]] 04:08, 23 September 2023 (UTC)
		+
		+	I wonder if there is a reference here to Microsoft in the late 90s when a no reply distribution list with a third of the employees had permissions set incorrectly. Then somebody on the list noticed noticed. It took down the Microsoft internal network for 2 days (network, not just mail, due to replication between Exchange servers!). The DL was amusingly called Bedlam DL3. For older MSFT employees the phrase “Bedlam DL3. Me too!” has a resonance. I think this might have been the first major email storm. For more details: [https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643] [[Special:Contributions/172.71.147.71\|172.71.147.71]] 17:45, 26 September 2023 (UTC)

← Older revision		Revision as of 04:08, 23 September 2023
Line 26:		Line 26:

	A relatively famous Perl programmer had a legal, deliverable email address of <code>@qz.to</code>, and has retained the for his current email. I have an auto-reply bot at <code>fred&barney@stonehenge.com</code> as a demonstration to anyone that it's a legal address but often rejected by stupid regexen. [[User:RandalSchwartz\|RandalSchwartz]] ([[User talk:RandalSchwartz\|talk]]) 23:28, 31 August 2023 (UTC)		A relatively famous Perl programmer had a legal, deliverable email address of <code>@qz.to</code>, and has retained the for his current email. I have an auto-reply bot at <code>fred&barney@stonehenge.com</code> as a demonstration to anyone that it's a legal address but often rejected by stupid regexen. [[User:RandalSchwartz\|RandalSchwartz]] ([[User talk:RandalSchwartz\|talk]]) 23:28, 31 August 2023 (UTC)
		+
		+	Fun fact: The Amazon corporate slang term for this is "Walleting", named after the subject line of one of the company's first widespread email storms. [[Special:Contributions/172.71.147.84\|172.71.147.84]] 04:08, 23 September 2023 (UTC)

@@ Line 19: / Line 19: @@
 :But, if you're more sure/correct than the prior editors apparently were, go ahead and edit it... [[Special:Contributions/141.101.68.99|141.101.68.99]] 16:36, 31 August 2023 (UTC)
 ::Right, [https://en.wiktionary.org/wiki/loop_in#English to loop in] is a common bit of jargon for "include in communication", related to [https://en.wiktionary.org/wiki/in_the_loop in the loop]. "I'm looping in Jane and John" would be a common phrasing in business e-mails. I'll edit that into the explanation. - [[User:IMSoP|IMSoP]] ([[User talk:IMSoP|talk]]) 09:51, 1 September 2023 (UTC)
-:::'Common business phrasings' always make me twitch. I still can't take "touch base" seriously, after all these years. I suspect there are some people out there busy inventing the contexts for new verbed nouns and adjectival verbs just to sound sillier. (They're the ones who invented both "podiumed" and "medal(l)ed" for sports contexts, too.)
+:::'Common business phrasings' always make me twitch. I still can't take "touch base" seriously, after all these years. I suspect there are some people out there busy inventing the contexts for new verbed nouns and adjectival verbs just to sound sillier. (They're the ones who invented both "podiumed" and "medal(l)ed" for sports contexts, too.) [[Special:Contributions/172.70.90.138|172.70.90.138]] 10:38, 1 September 2023 (UTC)
-::::On the other hand, English is very, very adaptable and allows a lot of new usages, such as where a noun becomes a verb. Functionally irrelevant opinion notwithstanding, the meaning is clear, even when you hear it for the first time, as the semantic structure is so robust (yet plastic). Like when you ironied there, in the use of "verbed".[[User:Yorkshire Pudding|Yorkshire Pudding]] ([[User talk:Yorkshire Pudding|talk]]) 21:49, 1 September 2023 (UTC)[[Special:Contributions/172.70.90.138|172.70.90.138]] 10:38, 1 September 2023 (UTC)
+::::On the other hand, English is very, very adaptable and allows a lot of new usages, such as where a noun becomes a verb. Functionally irrelevant opinion notwithstanding, the meaning is clear, even when you hear it for the first time, as the semantic structure is so robust (yet plastic). Like when you ironied there, in the use of "verbed".[[User:Yorkshire Pudding|Yorkshire Pudding]] ([[User talk:Yorkshire Pudding|talk]]) 21:49, 1 September 2023 (UTC)
 On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP|IMSoP]] ([[User talk:IMSoP|talk]]) 14:14, 31 August 2023 (UTC)
 A relatively famous Perl programmer had a legal, deliverable email address of <code>*@qz.to</code>, and has retained the * for his current email. I have an auto-reply bot at <code>fred&amp;barney@stonehenge.com</code> as a demonstration to anyone that it's a legal address but often rejected by stupid regexen. [[User:RandalSchwartz|RandalSchwartz]] ([[User talk:RandalSchwartz|talk]]) 23:28, 31 August 2023 (UTC)

@@ Line 19: / Line 19: @@
 :But, if you're more sure/correct than the prior editors apparently were, go ahead and edit it... [[Special:Contributions/141.101.68.99|141.101.68.99]] 16:36, 31 August 2023 (UTC)
 ::Right, [https://en.wiktionary.org/wiki/loop_in#English to loop in] is a common bit of jargon for "include in communication", related to [https://en.wiktionary.org/wiki/in_the_loop in the loop]. "I'm looping in Jane and John" would be a common phrasing in business e-mails. I'll edit that into the explanation. - [[User:IMSoP|IMSoP]] ([[User talk:IMSoP|talk]]) 09:51, 1 September 2023 (UTC)
-:::'Common business phrasings' always make me twitch. I still can't take "touch base" seriously, after all these years. I suspect there are some people out there busy inventing the contexts for new verbed nouns and adjectival verbs just to sound sillier. (They're the ones who invented both "podiumed" and "medal(l)ed" for sports contexts, too.) [[Special:Contributions/172.70.90.138|172.70.90.138]] 10:38, 1 September 2023 (UTC)
+:::'Common business phrasings' always make me twitch. I still can't take "touch base" seriously, after all these years. I suspect there are some people out there busy inventing the contexts for new verbed nouns and adjectival verbs just to sound sillier. (They're the ones who invented both "podiumed" and "medal(l)ed" for sports contexts, too.)
 On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP|IMSoP]] ([[User talk:IMSoP|talk]]) 14:14, 31 August 2023 (UTC)
 A relatively famous Perl programmer had a legal, deliverable email address of <code>*@qz.to</code>, and has retained the * for his current email. I have an auto-reply bot at <code>fred&amp;barney@stonehenge.com</code> as a demonstration to anyone that it's a legal address but often rejected by stupid regexen. [[User:RandalSchwartz|RandalSchwartz]] ([[User talk:RandalSchwartz|talk]]) 23:28, 31 August 2023 (UTC)

← Older revision		Revision as of 23:28, 31 August 2023
Line 20:		Line 20:

	On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)		On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)
		+
		+	A relatively famous Perl programmer had a legal, deliverable email address of <code>@qz.to</code>, and has retained the for his current email. I have an auto-reply bot at <code>fred&barney@stonehenge.com</code> as a demonstration to anyone that it's a legal address but often rejected by stupid regexen. [[User:RandalSchwartz\|RandalSchwartz]] ([[User talk:RandalSchwartz\|talk]]) 23:28, 31 August 2023 (UTC)

← Older revision		Revision as of 16:36, 31 August 2023
Line 15:		Line 15:

	I don't see any implication in the comic of "attempting to expand the resulting lists within the mail body of the above email"; I just read it as the user typing that literally, like someone might write "I'm looping in sales@" instead of "I'm looping in the Sales Team" - they're not expecting the client to do anything magic with the body of their e-mail, just explaining what they've typed into the To / CC box. - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)		I don't see any implication in the comic of "attempting to expand the resulting lists within the mail body of the above email"; I just read it as the user typing that literally, like someone might write "I'm looping in sales@" instead of "I'm looping in the Sales Team" - they're not expecting the client to do anything magic with the body of their e-mail, just explaining what they've typed into the To / CC box. - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)
		+	:Looked to me like invoking some scripting language. e.g. "loop <address> in (@outlook.com, @yahoo.com) do add_address(_To_,<address>)", or somesuch according to required syntax, but I also didn't know whether this script fragment was supposed to be parsed/expanded/invoked/exec()ed within the To: or Body: fields.
		+	:I suppose "looping in" could well be a synonym for "copying in" (perhaps implicitly ''not'' "Cc:ing in", but adding to To: field), but I've not been aware of that precise terminology so that's probably why I too defaulted to thinking it's some sort of macro command being invoked at some level (despite there being few such mechanisms established to do so).
		+	:But, if you're more sure/correct than the prior editors apparently were, go ahead and edit it... [[Special:Contributions/141.101.68.99\|141.101.68.99]] 16:36, 31 August 2023 (UTC)

	On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)		On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)

← Older revision		Revision as of 14:14, 31 August 2023
Line 13:		Line 13:

	Inevitably someone would reply all with "Me too" to *@aol.com [[User:Rtanenbaum\|Rtanenbaum]] ([[User talk:Rtanenbaum\|talk]]) 13:15, 31 August 2023 (UTC)		Inevitably someone would reply all with "Me too" to *@aol.com [[User:Rtanenbaum\|Rtanenbaum]] ([[User talk:Rtanenbaum\|talk]]) 13:15, 31 August 2023 (UTC)
		+
		+	I don't see any implication in the comic of "attempting to expand the resulting lists within the mail body of the above email"; I just read it as the user typing that literally, like someone might write "I'm looping in sales@" instead of "I'm looping in the Sales Team" - they're not expecting the client to do anything magic with the body of their e-mail, just explaining what they've typed into the To / CC box. - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)
		+
		+	On another note, a notable real-life incident involving this was [https://www.wired.co.uk/article/nhs-email-reply-all-down in the UK National Health Service], involving a distribution list of 1.2 million users! - [[User:IMSoP\|IMSoP]] ([[User talk:IMSoP\|talk]]) 14:14, 31 August 2023 (UTC)