For whatever reason, Gmail keeps blocking my account alert emails from Chase. In my spam folder, guess which are really spam, and which are legit?

When I move them to my inbox and/or mark them as spam, I get warned that “Warning: This message may not be from whom it claims to be. Beware of following any links in it or of providing the sender with any personal information.”

How do I get Google to believe that my emails from Chase are real? I keep marking them as not spam, but that doesn’t help! Ridiculous that Gmail is hurting Chase Bank’s ability to conduct business and manage their fraud/risk. I highly suspect that account fraud alerts would get thrown into the same bucket…

Update 1:

The message headers seem to indicate a failure between Cornell and Google’s servers on SPF (Sender Policy Framework):

Delivered-To: XXXX@gmail.com
Received: by 10.231.53.18 with SMTP id k18cs6777ibg;
Sat, 24 Sep 2011 05:13:22 -0700 (PDT)
Received: by 10.52.93.112 with SMTP id ct16mr4101007vdb.423.1316866401115;
Sat, 24 Sep 2011 05:13:21 -0700 (PDT)
Return-Path: <Chase@alerts.chase.com>
Received: from limestone3.mail.cornell.edu (limestone3.mail.cornell.edu. [128.253.83.163])
by mx.google.com with ESMTP id bz6si11946296vdc.126.2011.09.24.05.13.20;
Sat, 24 Sep 2011 05:13:21 -0700 (PDT)
Received-SPF: fail (google.com: domain of Chase@alerts.chase.com does not designate 128.253.83.163 as permitted sender) client-ip=128.253.83.163;
Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of Chase@alerts.chase.com does not designate 128.253.83.163 as permitted sender) smtp.mail=Chase@alerts.chase.com; dkim=hardfail header.i=@alerts.Chase.com
X-CornellRouted: This message has been Routed already.
…

Update 2: A helpful Googler/blog reader said this:

It appears to be a problem specifically with Cornell. It’s a known issue when Cornell is forwarding e-mails to GMail. The Cornell IT admins [are fixing] their exchange server. In the meantime you can fix this with either:

- have Chase send info direct to @gmail.com
- create a filter to “never mark as spam” for that address.

My solution is to change my old rules to email directly to gmail rather than forward through Cornell’s servers.

This entry was posted on Friday, September 23rd, 2011 at 6:52 pm and is tagged with sender policy framework, fraud risk, smtp mail, account fraud, chase bank, spam folder, exchan, googler, google, client ip, return path, cornell, 163, authentication, xxxx, inbox, mx, lt, guess, failure. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback.

3 Responses to “GMail Blocking Chase Emails as Spam”

1. raj kumar says:

   9/26/2011 at 6:08 pm

   I got the same message but I noticed that i was forwarding the mail and the forwarder was breaking email authenticity signatures (DKIM http://en.wikipedia.org/wiki/DomainKeys_Identified_Mail). I wonder if this is the same case. I got my forwarder mail server admin fix the configuration and got it working.

   Reply
2. Ben says:

   9/26/2011 at 3:36 pm

   It is possible that the real Chase email contains links of other website (outsourced hosting?). Then the gmail will think the links smell.

   Reply
3. James says:

   9/25/2011 at 2:27 pm

   Are you sure these are really from Chase? Phishing detection in GMail is pretty good. Post or e-mail me the headers from the message. Click the drop down and pick “show original”. I’ll bet you anything the message isn’t actually coming from Chase and is just a really good forgery.

   Reply