We have an Internal Application that posts Messages to a MS SQL 2005 database
and then the Database uses SSIS to process the data and send the mail out
using the SMTP Client from the .Net 2.0 framework.

The Messages we send in this fashion reguardless of the content seem to get
High SCL ratings.  I can send the same content from My Yahoo account and the
messages get through with an SCL rating that is 2-3 less then the one I sent
via the SMTP Client.

What can to do to lower the SCL rating or find out why it is getting the
rating it is?

Thank you,
   Scott<-

different ways of handling this:
1. Add the sending host's ip address in Connection Filtering | Global Accept
list and enable Connection Filtering on smtp virtual server properties.
2. If on Exchange 2003 SP2 and those messages have a particular keyword in
subject or body you can use the new Custom Weighting feature to
lower/minimize the SCL. Check SP2 Release Note for details and how to create
the MSExchange.UceContentFilter.xml file
3. Use a 3rd party tool like WinDeveloper IMF Tune to "whitelist" the
sending address:
http://www.windeveloper.com/imftune/
Show quoteHide quote

Thank you for your reply. Though I guess I was not clear on what I am in need
of.

In order to stop filtering our own internal email, I created a second SMTP
Virtual Server and jsut turned off the filtering. The Internal SMTP Virtual
Server is on a different port and only accepts mail from the Database Server.
So internal mail is no longer filtered.

Our Real problem is that the mail we send to the customers this way is not
getting to them. On the customer end, it is getting filtered.

There would be no way for me to add our servers's IP address ot our domain
to a whitelist on all of our customer's email server.

I was hoping if I could understand what in my message is causing it to get a
High SCL, I could do something different in the message to get a lower SCL
rating.

I can send the Exact same content from Outlook and it goes through just fine.

The only big difference I can see is that in the Headers, the mail is coming
from the SQL Server IP, then to the Exchange Server IP, then off to the
customer. Where as with sending via outlook, it originates from the Exchane
Server IP.

Our Sales staff cant use any of the mail features in our application because
they dont know if the mail will ever get to the other end.

Thanks again for your reply.

Show quoteHide quote

Here are some sample messages I've sent:

This is the Headers from a message sent from .Net 2.0 SMTPClinet Class. It
has an SCL of 6

Microsoft Mail Internet Headers Version 2.0
Received: from hbg-smt ([10.1.0.133]) by mail.domain.com with Microsoft
SMTPSVC(6.0.3790.1830);
    Wed, 22 Mar 2006 07:07:06 -0800
mime-version: 1.0
date: 22 Mar 2006 07:07:06 -0800
subject: Hey Scooter
content-type: text/plain; charset=us-ascii
content-transfer-encoding: quoted-printable
Return-Path: use***@domain.com
Message-ID: <SERVERPDVn00000***@mail.domain.com>
X-OriginalArrivalTime: 22 Mar 2006 15:07:06.0815 (UTC)
FILETIME=[48DE24F0:01C64DC2]

From: use***@domain.com [mailto:use***@domain.com]
Sent: Wednesday, March 22, 2006 7:07 AM
To: SMT-Yahoo
Cc: Scott
Subject: Hey Scooter

Want to hit the Thai Place for Lunch?



---------------------------------------------------------------
Here is the same message received at my Yahoo Account
---------------------------------------------------------------

X-Apparently-To: use***@yahoo.com via 68.142.200.111; Wed, 22 Mar 2006
07:07:09 -0800
X-Originating-IP: [w.x.y.z]
Return-Path: <use***@domain.com>
Authentication-Results: mta130.mail.re2.yahoo.com from=domain.com;
domainkeys=neutral (no sig)
Received: from w.x.y.z (EHLO mail.domain.com) (w.x.y.z) by
mta130.mail.re2.yahoo.com with SMTP; Wed, 22 Mar 2006 07:07:08 -0800
Received: from hbg-smt ([10.1.0.133]) by mail.domain.com with Microsoft
SMTPSVC(6.0.3790.1830); Wed, 22 Mar 2006 07:07:06 -0800
mime-version: 1.0
Date: 22 Mar 2006 07:07:06 -0800
Subject: Hey Scooter
content-type: text/plain; charset=us-ascii
content-transfer-encoding: quoted-printable
Return-Path: use***@domain.com
Message-ID: <SERVERPDVn00000***@mail.domain.com>
X-OriginalArrivalTime: 22 Mar 2006 15:07:06.0815 (UTC)
FILETIME=[48DE24F0:01C64DC2]
Content-Length: 39

Want to hit the Thai Place for Lunch?

---------------------------------------------------------------
Same message sent from Outlook received at my Yahoo Account
---------------------------------------------------------------


X-Apparently-To: use***@yahoo.com via 68.142.201.235; Wed, 22 Mar 2006
07:17:44 -0800
X-Originating-IP: [w.x.y.z]
Return-Path: <use***@domain.com>
Authentication-Results: mta346.mail.mud.yahoo.com from=domain.com;
domainkeys=neutral (no sig)
Received: from w.x.y.z (EHLO mail.domain.com) (w.x.y.z) by
mta346.mail.mud.yahoo.com with SMTP; Wed, 22 Mar 2006 07:17:44 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C64DC3.BF10FF58"
Subject: Hey Scooter
Date: Wed, 22 Mar 2006 07:17:33 -0800
Message-ID: <5FACBEE0620BB340B5351C2A94D24B5302620***@server.domain2.COM>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Hey Scooter
Thread-Index: AcZNw76tGQ/r9Fn5RMiEuRkV0T6rjg==
Content-Length: 814

Want to hit the Thai Place for Lunch?





Show quoteHide quote

Copy Microsoft Outlook Calendar folder
Limiting the number of recipients of a message
RUS service created for domain without any Exchange servers
HELP: write-protected contacts
Moving Exchange 2003 to new server.