Solved

event id 7515 Catergory smtp Protocol

Posted on 2008-06-23
5
1,634 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 500 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

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
exchange 2 34
Scan to email stopped working for 2 clients. 9 39
Change SMTP port on Exchange Send Connector 4 25
outlook, MIME 6 11
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
how to add IIS SMTP to handle application/Scanner relays into office 365.

758 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now