Re: Exchange 2003 SP2, IMF and Sender ID issue

IMF Problem. Make sure the Junk Email folder is enabled for each mailbox.
Check these links:
http://www.exchangeinbox.com/articles/015/outlookjunk.htm
http://www.exchangeinbox.com/articles/008/centraljunk.htm

cheers,

Alexander Zammit
WinDeveloper Software
IMF Tune - Unleash the Full Intelligent Message Filter Power
http://www.windeveloper.com/imftune/


"akhilesh" <akhilesh.agarwal@xxxxxxxxx> wrote in message
news:1147838828.930643.314560@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I am using Windows SBS with SP1 and Exchange 2003 SP2.

I configured IMF to reject messages with SCL >= 8 and move messages
with an SCL >= 4 to Junk Mail folder. I configured Outlook to show SCL
rating in Inbox.

I receive several messages which show SCL rating by Exchange IMF >= 4,
but they are not being moved to Junk Email folder by Exchange Server. I
have configured Virtual SMTP server to allow IMF filtering as well.

Can anyone suggest what may be wrong?

Also, I have configured Message Delivery Properties, to Reject messages
which fail Sender ID filtering. I have configured Virtual SMTP to allow
sender ID filtering as well. Outlook is configured to show Sender ID
value from Exchange Server for each message.

Sender ID seems to be working well. However I am facing a problem with
message from my own domain name adityainternational.com, I have created
a SPF record and validated it from various tools available from
http://spf.pobox.com, therefore the record is correct.

However, any message sent from @adityainternational.com gets a TEMP_ERR
in sender ID. Whereas on other domains Exchange is able to contact DNS
and validate Sender ID. My network adapters are configured to use local
DNS server on Exchange Server. I am able to nslookup
adityainternational.com on the exchange server using command prompt, so
DNS is also configured correctly.

Can anyone suggest why I only get TEMP_ERR for messages sent from
@adityainternational.com, while other messages work ok?

Akhilesh Agarwal



.

Relevant Pages

  • Re: Exchange 2003 SP2, IMF and Sender ID issue
    ... If you don't see it then IMF is not setup right. ... You may want to try and get just IMF working before tackling sender ID to ... but they are not being moved to Junk Email folder by Exchange Server. ... have configured Virtual SMTP server to allow IMF filtering as well. ...
    (microsoft.public.windows.server.sbs)
  • Re: Question about IMF v2
    ... IMF learns from new signatures. ... The Safe Sender and Blocked Sender lists in Outlook 2003/2007 do not have any impact on Exchange Server 2003. ...
    (microsoft.public.exchange.admin)
  • Re: SP2 Caveats
    ... When you start your upgrade, start with the FE server, then do the BE ... If you were using the IMF, the IMF settings on the SMTP virtual server ... If you plan to use Sender ID, ... shared mailbox in Exchange 2000 Server and in Exchange Server 2003" ...
    (microsoft.public.exchange.admin)
  • RE: IMF safe sender list
    ... Outlook client included in IMF by default, this means we don't have a way ... IMF is installed on the Exchange Server gateway server to ... This rating is stored as a message property called a spam confidence ... action to take on messages above this threshold, and a mailbox store ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP logging
    ... I bet it wouldn't be a problem with essentially any kind of internal monitoring report imaginable, with the exception of a spam report email, which will make IMF automatically apply an 8 to it and archive it if the IP is not on the right list in the right way. ... The various list combinations make my head hurt, but originally I didn't even have the Connection Filter (or Sender ID) enabled so had nothing in General, which only applies to those two. ... So then I investigated the problem and through that article found that it was the Accept List in Connection Filtering that allows you to make IMF host exceptions. ...
    (microsoft.public.windows.server.sbs)