Why does replying to this Facebook email address trigger a security warning by Yahoo? -
I am developing a Chrome plugin that simplifies the various aspects of handling Facebook advertising platforms. As part of this I have experimented with FB support with related ideas to deal with email. In this context, I have a situation where the only act of responding to an email received from Facebook in part (not forged, American plan Receive to communicate with a real email reason platoform) instantly triggers a security alert on the Yahoo email platform. Responding to this FB email may prevent 24-hour restrictions on Yahoo! once, to stop sending you emails.
This has happened three times. not sure why.
info@w2opo85.aeayqq3dz3idc@support.facebook.com
<: by answering the following facebook email address from yahoo mail, claimed that "suspicious activity" security runs warning p> I am not familiar with the internal of email communication. Does the FB send a response to some type of Yahoo that triggers it? Is there anything from an e-mail address that causes Yahoo to trigger an alarm? Update: I removed the well-out Outlook and sent this feedback header to me without any problem:
Return-path: & lt; Noreply@support.facebook.com> Envelope-to: --redacted-- Delivery date: Sat, 18 Oct 2014 07:50:43 -0700 Received: from outmail018.prn2.facebook.com ([66.220.144.145]: 2218 Accept my request = mx-out .facebook .com) esmtps (with TLSv1 --redacted-- by: DHE-RSA-AES128-SHA: 128) (Exim 4.82) (for envelope & lt; noreply@support.facebook.com>) ID 1XfVL9-0007KM DJ --redacted--; Saturn, October 18, 2014 07:50:43 -0700 Received: From facebook.com (AZoY0ScZLK / Hookies2 Avei 3F7ZTivf7rJmnmoP5Y + 4qOWkIeAaeuu0z4o1geSJ / D10.17.112.51) by Facebook.com Thruft ID 1eed4c9456d611e4af5d0002c9266fc8-48be93e0; Saturn, 18 October 2014 07:50:36 -0700 X-Facebook: From 10.83.20.55 ([MTI 3 LJAMMC 4x]) ASINCPPbook. With htp (zacmel); Date: Saturday, 18 October 2014 07:50:36 -0700 From: - Controlled - To: Facebook & lt; Noreply@support.facebook.com> Answer: Facebook & lt; Noreply@support.facebook.com> Subject: Re-Test Message-ID: --redacted-- X Priority: 3 X-Mailer: ZuckMail [Version 1.00] Mime-version: 1.0 Content-Transfer-Encoding: Cited-Printable Content Type: Text / Plain; Charset = "UTF-8" DKIM-sign: v = 1; A = RSA-SHA256; C = rest / simple; D = support.facebook.com; S = s1024-2013-Q3; T = 1413643836, bh = 2OxaQEfrQJk + 5tQ3x7l7F2VnmqsWQ1uIk + sBaezsXck =; H = Date: To: From: Subject: Mime-Edition: Content-Type; B = cM5N4TwKSHaDoByO5hEF3m73fdJMqxYYZVV6gSy0z4pWBQJu5gU894iMfqQS0LG7z Fm1p / 9Eh6hb2qkc7MCjSD / hWtwlDFF9lhETuaiV3Q + ZyDiZR9yrWUZMcKu + 6mPad3Q a0q6Qf3FL4MCvgej7GRDwUEBrn7mh2wssTSEk668 =
Message:
Hi, we do that we have reached a channel Not Support To get answers to many frequently asked questions and modern methods, please go to the Help Center to get in touch with us: https://www.facebook.com/help We apologize for the inconvenience. Thank you, Facebook Team
Email spoofing fish is a very common way for people. Yahoo probably increased their spam filters and dodging non-word characters and non-prolonged hashes security warnings. @ support.facebook.com is clearly a legal domain, but spammers It is not unheard of to use fake support email for scams in giving your personal information. For this reason it is most likely that security alert was tripped.
Comments
Post a Comment