Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

event id 7515 Catergory smtp Protocol

Posted on 2008-06-23
5
Medium Priority
?
1,668 Views
Last Modified: 2008-07-15
The Exchange Intelligent Message Filter attempted to filter a message, The message could not be filtered,
Error code 0x800710f0. The messages were from users and to users AOL accounts and not our exchange store. Is their a way to prevent the msexchange Transport from trying to process this, so an error doesn't occur and slow down performance on the exchange serve

0
Comment
Question by:jim3725
  • 3
  • 2
5 Comments
 
LVL 23

Expert Comment

by:TheCleaner
ID: 21903065
Best way to prevent such a thing would be to not send emails from AOL accounts through the SMTP engine on the Exchange server.  They should be connecting to the AOL mail servers to send and receive email, not relaying through your Exchange server.
0
 

Author Comment

by:jim3725
ID: 21908890
Is their a setting on exchange server that I can use to stop that?
0
 
LVL 23

Expert Comment

by:TheCleaner
ID: 21908984
This is done at the client.  Their client should be set up with a POP3 account connecting to AOL instead of sending outbound email through Exchange.  (It's inbound/outbound mail server)

Is this how it is setup?

You may need to explain the setup more thoroughly.  Are you allowing relaying?  If they are from AOL accounts and TO AOL accounts then going through your Exchange server for inbound and outbound processing would be kind of pointless.

Also, what's the Exchange server for?  I mean, are their AOL accounts their primary accounts or just personal stuff?
0
 

Author Comment

by:jim3725
ID: 21909023
I am not allowing email relay from exchange server, No AOL accts should be going thru exchange server. AOL is just personal
0
 
LVL 23

Accepted Solution

by:
TheCleaner earned 1500 total points
ID: 21909127
It sounds like they may be either replying using their Exchange account or sending email to an AOL account from their exchange account.  You would have to enable message logging to be certain.

In either regards, the error code is explained in this KB article:  http://support.microsoft.com/kb/907691

and basically says that the emails are larger than 3MB and therefore not scanned.   You can safely disregard the message, and I don't think performance is suffering, since this is by design.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to effectively resolve the number one email related issue received by helpdesks.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

927 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question