Does anyone have some suggestions for how to set the SCL level on
messages flowing into an Exchange 2003 server?  I've been struggling
with this problem for a few days and haven't found a good solution
yet.

We have an Exchange 2000 Server that is giving us some
grief.  We are having problems with only a select few mail
addresses when sending mail; which have worked in the
past, but have recently stopped. We have noticed this

Goal: Write C# managed sink against the SMTP OnSubmission event.
Compare
recipient list against known "good" list and remove invalid recipients.
Make

sorry, I am not an Exchange guru, so maybe some of
words I am using are not the right ones. But I try
to explain my problem.
My network has a small number of workstations and

I have a user, who upon emailing a certain person externally receives this
error:
The following recipient(s) could not be reached:
     'user@usersaddress' on 19/11/2004 11:30

The messages come in to our SMTP Server. If i do a message tracking it says
SMTP: MESSAGE QUEUED FOR LOCAL DELIVERY. After this nothing is done to
deliver the message to the mailbox. Where does the message go. how can i
trace this message. Can i try and trigger this mail to be ...

We had problems with missing messages and when i ran the advanced message
tracker, it said SMTP: message queued for local delivery. Where can i find
this message or how can i trigger this to be delivered to mail boxes.
Thanks,

sbs patched SP1a exh SP3.  This week all of a sudden POP3 Connector has
started going down periodically.  Also emails do not seem to be getting thru
to user accounts.  No changes were made in this time frame that I amaware of.
Have run eseutil and isinteg

I have a Windows 2000 Domain with an Exchange 2000 Organization.
Sometimes users are receiving messages sent to different users. Yes, the
domain address is valid but the mail is being delivered to the wrong mailbox.
Example: user1 is reciving mail for User1 and with SMTP address

On certain email coming into our exchange server seems to be getting stuck in
the categorizer.  Looking into message tracking the last thing I see is
Message submitted to categorizer.  Is there any place I can go to see what is
the problem?

We are running a Exchange 5.5 on W2K SP4 for both. The server is a bridgehead
server. There are messages that are stuck in the MTA for about 3 days to one
of X400 connected international offices. Messages are flowing fine to the
other MTA queues. I can however successfully send ...

This problem has just started yesterday for no reason. We use Exchange Server
5.5 Inter-Ofice e-mail works fine but when you try to send to an email
account (ex: name@hotmail.com) it comes back as undeliverable. No transport
provider was available.

I have a front end back end mail configuration. Exhcange 2003 SP1/ Windows
2003 SP1. every thing was working ok. we have a group of ursers who have mail
boxes on another server, which is not exchange server, and they have
forwarded the mails from there to their mail boxes here.  ...

I have followed the advice of a few online articles and allowed all the
wizards to configured this system.  My first problem was that they did not
configure my plug and play router.  I re-configured it with two network
cards.  Now everything works but I can not receive email.

I keep getting Event ID 4000 (Source - MSExchange Transport) in my
Application Log in Event Viewer.
Basically I have a few e-mails backed up in Exchange System Manager (SMTP
Queue)