I messaged Ben on LinkedIn. I got the following response: "Man, to be honest, I’m not responsible for acquiring potential prospect contact information. I am in sales and follow up with current leads. I apologize if all those emails got on our mailing list. Just respond “stop” and I’ll get whoever taken off the list. The response emails come to me.”
I’m under the impression that he himself did not do this but rather someone who dumped the mailing list addresses as “leads”. If you do email Ben personally, please don’t be rude with him. Though someone at the company still did a very bad thing. Best, Tanner > On Oct 22, 2019, at 12:55, Erik Lentz via Outages <[email protected]> wrote: > > After emailing the group yesterday, Ben Reynolds contacted me as well. Can he > be banned, please? > > On Mon, Oct 21, 2019 at 9:37 AM DaZZa via Outages <[email protected] > <mailto:[email protected]>> wrote: > Count me in too. Gmail was kind enough to identify it for what it was and > send it to spam. > > On Tue, 22 Oct 2019 at 00:35, Christopher Conley via Outages > <[email protected] <mailto:[email protected]>> wrote: > Late to the party, but I received it as well. Exact same message (attached) > as OP. Banhammer time? > > > > Also, hi spammy Ben! Bye spammy Ben. > > > > -- > > Christopher Conley > > Systems Administrator | Fors Marsh Group > > 1010 N. Glebe Rd, Suite 510 > > Arlington, VA 22201 > > > > > > From: Outages <[email protected] > <mailto:[email protected]>> On Behalf Of Matt Harris via Outages > Sent: Saturday, October 19, 2019 10:14 PM > To: Jared Mauch <[email protected] <mailto:[email protected]>> > Cc: Shawn Solomon via Outages <[email protected] > <mailto:[email protected]>> > Subject: Re: [outages] sales critter Ben Reynolds > > > > I can confirm that I also received spam from that organization. Can't > remember if the name was the same. > > > > > > On Sat, Oct 19, 2019 at 11:54 AM Jared Mauch via Outages <[email protected] > <mailto:[email protected]>> wrote: > > This person spammed all sorts of weird addresses for projects that I run (eg: > Open Resolver) so clearly has no clue. > > That domain is currently banned on my mail server so it’s unlikely they can > get anything else through. > > - Jared > > > On Oct 19, 2019, at 12:37 PM, PE via Outages <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > I'm sure many of us got email from this critter, since he seems to be > > scraping posts to get email addrs to annoy with spam. > > > > List moderator: can you please yank them? > > > > List: got another company/critter to add to the "never do business with > > ever list"... > > > > -- > > <1.eml>_______________________________________________ > > Outages mailing list > > [email protected] <mailto:[email protected]> > > https://puck.nether.net/mailman/listinfo/outages > > <https://puck.nether.net/mailman/listinfo/outages> > > _______________________________________________ > Outages mailing list > [email protected] <mailto:[email protected]> > https://puck.nether.net/mailman/listinfo/outages > <https://puck.nether.net/mailman/listinfo/outages> > > > > -- > > Matt Harris - Chief Security Officer > > Security, Compliance, and Engineering > > Phone: +1-816-256-5446 > > Email: [email protected] <mailto:[email protected]> > _______________________________________________ > Outages mailing list > [email protected] <mailto:[email protected]> > https://puck.nether.net/mailman/listinfo/outages > <https://puck.nether.net/mailman/listinfo/outages> > > > -- > veg·e·tar·i·an: > Ancient tribal slang for the village idiot who can't hunt, fish or ride > _______________________________________________ > Outages mailing list > [email protected] <mailto:[email protected]> > https://puck.nether.net/mailman/listinfo/outages > <https://puck.nether.net/mailman/listinfo/outages> > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
