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

x
?
Solved

How to allow all traffic from a specific host as "safe" or "not spam"

Posted on 2008-06-26
4
Medium Priority
?
377 Views
Last Modified: 2011-09-20
We have a voicemail system that will send users their voicemail by email. Trouble is that Exchange will categorize most of these messages as "junk email" and put them in that folder. The only smtp traffic we receive from the voicemail system at 10.10.1.41 is this type of message. Is there a way to flag ANYTHING from this particular host as safe? The "from" address is always different. It doesn't look like an email address. instead, it is formatted like this:  Phone_1112223333 where the numbers are the caller ID for the person who left the message. There is no @ sign. All messages contain a WAV attachment.

Thanks to anyone who can give me step-by-step instructions to configure Exchange to allow all these messages.
0
Comment
Question by:RadioActiveLamb
  • 2
4 Comments
 
LVL 1

Accepted Solution

by:
itmonitor earned 1000 total points
ID: 21877352
have you tried to go under the message delivery properties in the exchange system manager and add the IP as an accepted ip delivery address?
0
 
LVL 4

Expert Comment

by:antioed
ID: 21877563
Are you using the Microsoft Intelligent Message Filter?  itmonitor's suggestion would apply if that is the case, and IMF is marking those messages with an SCL that categorizes those messages as possible Junk thus causing them to wind up in the users JEF.  With IMF, messages from an "allowed" IP defined in Exchange will not be filtered.  Otherwise it is the Junk Email filter in Outlook...since there is no <@domain> to "wildcard allow" and the messages always come from different senders, lowering the Junk Email sensitivity is the only thing I can can think of to try.  Not sure if the Junk Email settings in Outlook would allow a wildcard "safe sender" setting for *Phone* without a domain.  Perhaps others out there have dealt with this and have more/better feedback on how to address this.
0
 
LVL 1

Author Closing Comment

by:RadioActiveLamb
ID: 31471098
IMF is enabled, and it appears that this will resolve the problem. Thanks for the quick response.
0
 
LVL 1

Author Comment

by:RadioActiveLamb
ID: 21877920
IMF is enabled. This should fix the problem. Thanks for the quick response.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

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

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
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…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses

971 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