Email is getting blocked by spam blockers because of BigFish

  • 14 Followers
  • 33 Replies |
  • This post has 0 verified answers |
Answered (Not Verified) This question has suggested answer(s)

We recently moved our domain to Microsoft and switched from a self-hosted Exchange to Office365. Most everything is going well, but many of our clients are government agencies. We are now getting blocked by spam blockers and it has been traced to the fact that the email seems to be going through Bigfish.com. What can Microsoft do to help avoid spam since it comes from their own servers? 

 

Diagnostic information for administrators:

 Generating server: bigfish.com

spamgate.hbuhsd.org #<spamgate.hbuhsd.org #5.0.0 smtp;550-<_____@HBAS.EDU>: User is not accepting mail from this sender or host 550 HBUHSD thinks this email message is spam and has not delivered it to its intended recipient. If this is not spam contact the intended recipient by telephone and ask him/her to contact the I.S. Department. I.S. will need to be told the following information: Date Message was sent Time Message was sent Subject of the message Sender email address> #SMTP#

 Original message headers:

 Received: from mail48-db3-R.bigfish.com (10.3.81.243) by
 DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id
 14.1.225.22; Tue, 27 Sep 2011 21:29:58 +0000
Received: from mail48-db3 (localhost.localdomain [127.0.0.1])      by
 mail48-db3-R.bigfish.com (Postfix) with ESMTP id 08F181848185   for
 <___@HBAS.EDU>; Tue, 27 Sep 2011 21:29:58 +0000 (UTC)
X-SpamScore: -17
X-BigFish: PS-17(zz9371Kc89bhfecMc857h12d5M4015Lzz1202hzz8275bh8275dhz2fh2a8h668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:207.46.198.81;KIP:(null);UIP:(null);IPVD:NLI;H:CH1PRD0502HT001.namprd05.prod.outlook.com;RD:none;EFVD:NLI
Received-SPF: pass (mail48-db3: domain of asapconnected.com designates 207.46.198.81 as permitted sender) client-ip=207.46.198.81; envelope-from=_____@asapconnected.com; helo=CH1PRD0502HT001.namprd05.prod.outlook.com ;.outlook.com ;
Received: from mail48-db3 (localhost.localdomain [127.0.0.1]) by mail48-db3
 (MessageSwitch) id 1317158996438298_27649; Tue, 27 Sep 2011 21:29:56 +0000
 (UTC)
Received: from DB3EHSMHS017.bigfish.com (unknown [10.3.81.241])       by
 mail48-db3.bigfish.com (Postfix) with ESMTP id 652F3A58052       for
 <____@HBAS.EDU>; Tue, 27 Sep 2011 21:29:56 +0000 (UTC)
Received: from CH1PRD0502HT001.namprd05.prod.outlook.com (207.46.198.81) by
 DB3EHSMHS017.bigfish.com (10.3.87.117) with Microsoft SMTP Server (TLS) id
 14.1.225.22; Tue, 27 Sep 2011 21:29:54 +0000
Received: from CH1PRD0502MB116.namprd05.prod.outlook.com ([169.254.2.65]) by
 CH1PRD0502HT001.namprd05.prod.outlook.com ([10.28.29.221]) with mapi id
 14.01.0225.069; Tue, 27 Sep 2011 21:29:53 +0000
From: 
To: 
Subject:

 Thread-Topic:
Thread-Index: Acx8w86Idb20H78fS/y+3x4xxKGVrQAmGIrQ
Date: Tue, 27 Sep 2011 21:29:52 +0000
Message-ID: <09446068D9EA844D9B58AAC98D09EA2F06419562@CH1PRD0502MB116.namprd05.prod.outlook.com>
References: <3AB2B10581270E459AF7D3EBD0C0C629013D407A23F3@HBASXMAIL.HBAS.EDU>
 <79DC30BB-061E-4988-ADFC-737D9E7EBD39@HBAS.EDU>
In-Reply-To: <79DC30BB-061E-4988-ADFC-737D9E7EBD39@HBAS.EDU>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.164.148.157]
Content-Type: multipart/alternative;
            boundary="_000_09446068D9EA844D9B58AAC98D09EA2F06419562CH1PRD0502MB116_"
MIME-Version: 1.0
Return-Path: 
X-OriginatorOrg: asapconnected.com

  • Post Points: 20
All Replies
  • Hi JMeyer,

    Even if the emails go through with same server as Microsoft Forefront Online Protection for Exchange (FOPE), it might still be blocked if it triggers the recipient's spam rules, as FOPE is a multi-engine, heuristics-enabled anti-virus and multi-layered anti-spam architecture. You may check your emails for any external links, pictures or signatures est. in case any content would trigger the spam.

    Moreover, please contact your recipients and ask them to set your email addresses or domain as safe sender list.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
    Suggested by
  • Hi JMeyer,

    How are things going?

    Please post back at your convenience if we can help further.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
  • The frustrating thing is that our domain when hosted by our own Exchange server had no issues. But now all of a sudden, clients can no longer receive our emails. Their IT group doesn't believe it is their problem so it is causing great difficulty in communication. Yes its easy to release a domain from SPAM, but that is assuming the IT person in charge believes the person and acts on it quickly --- not going to happen in most organizations.

    • Not Ranked
    • Post Points: 0
  • Hi JMeyer,

    I would like to know whether the mail header you posted is from your client's email or from the NDR you received.

    If your clients can not receive your emails, did you receive any NDR? If so, please post it on the forum.

    Moreover, you could try to set your clients' email addresses in your safe sender list in Outlook Web App to test it.

    Here are the general steps:

    1. Log in Outlook Web App, click Options from the right up corner under your display name and click See All Options.

    2. Under Options: Manage Myself, click Block or Allow.

    3. On the Junk E-Mail Settings page, set your Safe Senders and Recipients.

    4. Click Save.

    After doing this, you may try to send an email to your client to check if they could receive it.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
    Suggested by
  • Hi Anna,

    The item I posted is the response we received. The Subject line was: Undeliverable: subject of my email

    That was followed by this:

    The server has tried to deliver this message, without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.

    Then came the content shown above (I removed some identifiers on people to make it OK to post).

    We are trying your idea above to see if it will work.

    • Not Ranked
    • Post Points: 0
  • Hi JMeyer,

    Given the current situation, you could provide your domain information for us to further research. Since this is your privacy, I will send a private message to you to request your domain information. Therefore, you could reply me through private message.

    To access the private message with the subject of <Domain Information>:

    1.Please go to the Your details section on the right side of the community site.

    2.Click Private messages.

    3.Click the subject title of the response to read the message and reply with your domain information.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
  • Hi JMeyer,

    Based on the current troubleshooting, there might be different causes for this issue. To further checking this, I would reply you with a private message for the contact information of FOPE. You may contact them directly for this error.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
  • Hi JMeyer,

    We have not heard from you in a couple of days.

    Please post back at your convenience if we can help further.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
  • We put a call into FOPE and discussed this with them. They now have a ticket with the details of the spam blocking. They will keep this in mind, but there is not much more than they can do. It appears that some spam 3rd parties have blacklisted BigFish but there is not much Microsoft can do until it learns more.

    Such is life. Thanks for your help.

    • Not Ranked
    • Post Points: 0
  • Hi JMeyer,

    I really appreciate your update and response.

    If you have any other questions or concerns, please do not hesitate to contact us. It is always our pleasure to be of assistance.

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
  • I continue to get the same problem, and today, I even got it from a Google Apps hosted domain I own.  It happened with I forwarded my BLOCKED message sent from my Office365 domain to my Google Apps Domain (my intention was to retry sending the mail from the Google Apps hosted domain).

    As with the other posters, this also happens quite frequently with governmental agencies.  Here is the bounce message:

    From: MAILER-DAEMON@MAILER-DAEMON [mailto:MAILER-DAEMON@MAILER-DAEMON]

    Sent: Wednesday, October 19, 2011 2:35 PM

    To: Paul Billings

    Subject: Undeliverable: Fwd: Professional Liability

    Delivery has failed to these recipients or groups:

    paul@appraisalchallenge.com

    A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.

    The following organization rejected your message: m1.dnsix.com.

    Diagnostic information for administrators:

    Generating server: bigfish.com

    paul@appraisalchallenge.com

    m1.dnsix.com #<m1.dnsix.com #5.0.0 smtp;550 unrouteable address> #SMTP#

    Original message headers:

    Received: from mail74-am1-R.bigfish.com (10.3.201.254) by

    AM1EHSOBE004.bigfish.com (10.3.204.24) with Microsoft SMTP Server id

    14.1.225.22; Wed, 19 Oct 2011 19:34:12 +0000

    Received: from mail74-am1 (localhost.localdomain [127.0.0.1]) by

    mail74-am1-R.bigfish.com (Postfix) with ESMTP id A128E1AB02FE; Wed, 19 Oct

    2011 19:34:12 +0000 (UTC)

    X-SpamScore: -15

    X-BigFish: PS-15(zf7Iz9371K1431J1454Kc85eh1b0bM12d5Mc0c9kzz1202hzz8275bhf3c47iz2fh793h2a8h668h839h34h61h)

    X-Spam-TCS-SCL: 0:0

    X-Forefront-Antispam-Report: CIP:207.46.4.139;KIP:(null);UIP:(null);IPVD:NLI;H:SN2PRD0402HT002.namprd04.prod.outlook.com;RD:none;EFVD:NLI

    Received-SPF: pass (mail74-am1: domain of paulbillingslaw.com designates 207.46.4.139 as permitted sender) client-ip=207.46.4.139; envelope-from=paul@paulbillingslaw.com; helo=SN2PRD0402HT002.namprd04.prod.outlook.com ;.outlook.com ;

    Received: from mail74-am1 (localhost.localdomain [127.0.0.1]) by mail74-am1

    (MessageSwitch) id 1319052832141553_4001; Wed, 19 Oct 2011 19:33:52 +0000

    (UTC)

    Received: from AM1EHSMHS019.bigfish.com (unknown [10.3.201.253]) by

    mail74-am1.bigfish.com (Postfix) with ESMTP id 00A58CA8052; Wed, 19 Oct 2011

    19:33:52 +0000 (UTC)

    Received: from SN2PRD0402HT002.namprd04.prod.outlook.com (207.46.4.139) by

    AM1EHSMHS019.bigfish.com (10.3.206.22) with Microsoft SMTP Server (TLS) id

    14.1.225.22; Wed, 19 Oct 2011 19:33:45 +0000

    Received: from SN2PRD0402MB110.namprd04.prod.outlook.com ([169.254.9.6]) by

    SN2PRD0402HT002.namprd04.prod.outlook.com ([10.27.50.80]) with mapi id

    14.01.0225.071; Wed, 19 Oct 2011 19:33:30 +0000

    From: Paul Billings <paul@paulbillingslaw.com>

    To: "jbglassco@clayandland.com" <jbglassco@clayandland.com>

    CC: "paul@appraisalchallenge.com" <paul@appraisalchallenge.com>

    Subject: Fwd: Professional Liability

    Thread-Topic: Professional Liability

    Thread-Index: AcxkO/CYUhX3rJYmRhaYnWaP4AtPkQEhhtcgAAQUviAAAWU6QAW3PmJgA4wKmnAALDjC9Q==

    Date: Wed, 19 Oct 2011 19:33:30 +0000

    Message-ID: <5924B1B6-E13E-4E1F-80F4-3956C4EF4CE4@paulbillingslaw.com>

    References: <EE3AABCBA4854F069139BF57E5B639D8@ClayandLand.local>,<917CDB2415B20240AD990AB41AF4AC100385123F@SN2PRD0402MB110.namprd04.prod.outlook.com>

    In-Reply-To: <917CDB2415B20240AD990AB41AF4AC100385123F@SN2PRD0402MB110.namprd04.prod.outlook.com>

    Accept-Language: en-US

    Content-Language: en-US

    X-MS-Has-Attach: yes

    X-MS-TNEF-Correlator:

    x-originating-ip: [66.193.225.64]

    Content-Type: multipart/mixed;

    boundary="_005_5924B1B6E13E4E1F80F43956C4EF4CE4paulbillingslawcom_"

    MIME-Version: 1.0

    Return-Path: paul@paulbillingslaw.com

    X-OriginatorOrg: paulbillingslaw.com

    Anna has attempted to help me with this in the past, and I appreciated her help.  The problem still remains.

    • Not Ranked
    • Post Points: 0
  • I am having the exact same problem, so I don't think this is actually fixed yet.

    Delivery has failed to these recipients or groups:

    cm-intro@lists.sunsetfilms.com

    A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.

    The following organization rejected your message: BAY0-PAMC1-F5.Bay0.hotmail.com.

    Diagnostic information for administrators:

    Generating server: bigfish.com

    cm-intro@lists.sunsetfilms.com

    BAY0-PAMC1-F5.Bay0.hotmail.com #<BAY0-PAMC1-F5.Bay0.hotmail.com #5.0.0 smtp;550 Requested action not taken: mailbox unavailable> #SMTP#

    Original message headers:

    Received: from mail87-am1-R.bigfish.com (10.3.201.245) by

    AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id

    14.1.225.22; Wed, 19 Oct 2011 20:18:02 +0000

    Received: from mail87-am1 (localhost.localdomain [127.0.0.1]) by

    mail87-am1-R.bigfish.com (Postfix) with ESMTP id ACCF01618446 for

    <cm-intro@lists.sunsetfilms.com>; Wed, 19 Oct 2011 20:18:02 +0000 (UTC)

    X-SpamScore: 0

    X-BigFish: PS0(zzc85ehzz1202hzz8275bhz2fh2a8h668h839h65h)

    X-Spam-TCS-SCL: 4:0

    X-Forefront-Antispam-Report: CIP:157.55.49.13;KIP:(null);UIP:(null);IPVD:NLI;H:SN2PRD0802HT004.namprd08.prod.outlook.com;RD:none;EFVD:NLI

    Received-SPF: pass (mail87-am1: domain of sunsetfilms.com designates 157.55.49.13 as permitted sender) client-ip=157.55.49.13; envelope-from=dankney@sunsetfilms.com; helo=SN2PRD0802HT004.namprd08.prod.outlook.com ;.outlook.com ;

    Received: from mail87-am1 (localhost.localdomain [127.0.0.1]) by mail87-am1

    (MessageSwitch) id 1319055480199684_21170; Wed, 19 Oct 2011 20:18:00 +0000

    (UTC)

    Received: from AM1EHSMHS005.bigfish.com (unknown [10.3.201.250]) by

    mail87-am1.bigfish.com (Postfix) with ESMTP id 03DC2270046 for

    <cm-intro@lists.sunsetfilms.com>; Wed, 19 Oct 2011 20:18:00 +0000 (UTC)

    Received: from SN2PRD0802HT004.namprd08.prod.outlook.com (157.55.49.13) by

    AM1EHSMHS005.bigfish.com (10.3.207.105) with Microsoft SMTP Server (TLS) id

    14.1.225.22; Wed, 19 Oct 2011 20:17:59 +0000

    Received: from SN2PRD0802MB112.namprd08.prod.outlook.com ([169.254.4.253]) by

    SN2PRD0802HT004.namprd08.prod.outlook.com ([10.27.84.30]) with mapi id

    14.01.0225.071; Wed, 19 Oct 2011 20:17:58 +0000

    From: Don Ankney <dankney@sunsetfilms.com>

    To: "cm-intro@lists.sunsetfilms.com" <cm-intro@lists.sunsetfilms.com>

    Subject: Max/MSP

    Thread-Topic: Max/MSP

    Thread-Index: AcyOnDC4lw+wV/WFRfmhnid6bPkxZA==

    Date: Wed, 19 Oct 2011 20:17:57 +0000

    Message-ID: <5E5B9AC90EF6E04F95B68CABE4A28E47455AC6@SN2PRD0802MB112.namprd08.prod.outlook.com>

    Accept-Language: en-US

    Content-Language: en-US

    X-MS-Has-Attach:

    X-MS-TNEF-Correlator:

    x-originating-ip: [10.27.84.7]

    Content-Type: multipart/alternative;

    boundary="_000_5E5B9AC90EF6E04F95B68CABE4A28E47455AC6SN2PRD0802MB112na_"

    MIME-Version: 1.0

    Return-Path: dankney@sunsetfilms.com

    X-OriginatorOrg: sunsetfilms.com

    • Not Ranked
    • Post Points: 0
  • Hi,

    Have you ever been BPOS users? If so, you need to remove the domain from BPOS with the help of the Forefront Online Protection for Exchange (FOPE) support and change the MX record. Otherwise, e-mail sent to users is still routed to where your previous MX record pointed to.

    Given the current situation, I will send you two a private message about the contact information for FOPE support, respectively. You could contact FOPE directly about this issue.

    To access the private message: 

    1.Please go to the Your details section on the right side of the community site. 

    2.Click Private messages. 

    3.Click the subject title of the response to read the message. 

    Thanks,
    Anna Guo

    • Top 50 Contributor
    • Post Points: 0
  • I have having the same issue with my emails.  How do I fix the issue?  

    • Not Ranked
    • Post Points: 0
Page 1 of 3 (34 items) 1|2|3|