Exchange Server Forums

how to solve this false postive issue with anti-spam...

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> how to solve this false postive issue with anti-spam...

Page: [1]

Message

<< Older Topic Newer Topic >>

how to solve this false postive issue with anti-spam... - 26.Aug.2010 9:01:29 AM

carboncow

Posts: 11
Joined: 26.Aug.2010
Status: offline

I've got a fresh Exchange 2007 install on SBS 2008. I'm only running Exchange's tools RBL, ect for spam control at the moment.

Any BlackBerry users who try to email anyone in our organization are getting tagged as spam and thrown in quarantine, which I can only lower the value of so much. I've turned off RBLs for testing so they are not tagging them...so my guess is something in Exchange does't like to see our domain emails coming from another IP/domain (blackberry). I know I can white list by IP but they simply have to many servers and you cannot whitelist by domain name (not that I can find) in Exchange 2007.

Can someone please explain how to solve this...I don't want to have to remove the quarantine functionality.

Post #: 1

Featured Links*

RE: how to solve this false postive issue with anti-spa... - 2.Nov.2010 1:38:42 PM

djaish

Posts: 1
Joined: 2.Nov.2010
Status: offline

I know that this is an old topic, but I have joined the forum in efforts to troubleshoot the same issues with the spam quarantine. Basically Blackberry IS users (those not on our or other ES systems) are marked as spoofers since the email address viewed (@specialdomain.com) is not the same as the one sent from (@provider.blackberry.com). The same issue seems to happen with sites using google accounts. (The actual SMTP domain is @...google.com as opposed to @specialdomain.com.)

The real question is, is there a way to mark certain spoofing domains (in the instance of blackberry, where I've yet to see spam sent from) or certain spoofed domains (in the example of a domain you know is using google accounts) as safe senders.

Another way to deal with this is if the content filter can search the headers as opposed to just the message.

Anyone can help with either of these two suggested solutions to this problem?

(in reply to carboncow)

Post #: 2