Exchange 2003 SMTP messages not goingout

A Few days ago my Exchange 2003 Server stopped sending external email. Internal works fine. External mail stays in he SMTP que. I have verified my smart host setting and set them up in Outlook and they work great.
I have recreate the SMTP virtual server and restarted the server and services many times. Not sure where to go from here. Looking at the event viewer application log, I'm not seeing anything related to this and the exchange events I see are info,
like starting and stopping. These are caused from restarting services.
David Dobson

My files are 6GB and 2GB.
01/01/2014 10:24 PM    <DIR>          ..
01/02/2014 03:17 AM             8,192 E00.chk
01/01/2014 10:23 PM         5,242,880 E00.log
01/01/2014 06:05 PM         5,242,880 E0013C6C.log
01/01/2014 07:19 PM         5,242,880 E0013C6D.log
01/01/2014 10:19 PM         5,242,880 E0013C6E.log
01/02/2014 01:52 AM         4,194,304 E00tmp.log
12/30/2013 03:02 PM     6,487,351,296 priv1.edb
12/30/2013 03:02 PM     2,380,275,712 priv1.stm
12/30/2013 03:02 PM       151,003,136 pub1.edb
12/30/2013 03:02 PM         6,299,648 pub1.stm
12/30/2013 03:02 PM         5,242,880 res1.log
12/30/2013 03:02 PM         5,242,880 res2.log
12/30/2013 03:02 PM         1,056,768 tmp.edb
David Dobson

Similar Messages

Exchange 2003 SP2 messages stuck in queue

HI
I just inherited a exchange 2003 SP2 machine and next month we are migrating to 365. But here is what happen so far and the issue
1. The previous IT company had the emails flowing thru smart host via their own hosted spam filter.
2. I came in and changed my MX records and installed a on server spam filter (ORF) by Vamsoft and configured it. Removed the smart host info and made sure that the firewall is all configured properly.
3. Tested in bound email.
4. Problem. Out bound emails go thru till the server. Some users get a delayed email but others do not. The messages are stuck in the outbound Queue. restarted the SMTP and still no luck. Disabled Spam filter (ORF) still
no luck.
Then I looked at anything which is common.
mails to msn.com & Hotmail.com are stuck. Emails to my company tejes.com are stuck. There are other few companies but do not know their email provider but the common theme between these 3 domains all are hosted by Microsoft. tejes.com
is on office365.
I need help. Please
Anil
Update: Fixed it. The previous company had filters in place.

HI
I just inherited a exchange 2003 SP2 machine and next month we are migrating to 365. But here is what happen so far and the issue
1. The previous IT company had the emails flowing thru smart host via their own hosted spam filter.
2. I came in and changed my MX records and installed a on server spam filter (ORF) by Vamsoft and configured it. Removed the smart host info and made sure that the firewall is all configured properly.
3. Tested in bound email.
4. Problem. Out bound emails go thru till the server. Some users get a delayed email but others do not. The messages are stuck in the outbound Queue. restarted the SMTP and still no luck. Disabled Spam filter (ORF) still
no luck.
Then I looked at anything which is common.
mails to msn.com & Hotmail.com are stuck. Emails to my company tejes.com are stuck. There are other few companies but do not know their email provider but the common theme between these 3 domains all are hosted by Microsoft. tejes.com
is on office365.
I need help. Please
Anil
Update: Fixed it. The previous company had filters in place.
Hi Anil,
Glad to know the issue has been fixed.
Also find this KB for your reference:
How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003
http://support.microsoft.com/kb/823866
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error.
First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
If the user tries to send the email again (from the bounced back message), it some times goes through.
Has anyone know what the problem is?
Have checked the server configuration, DNS configuration, ran all updates, and yet still same result. Is one of the Microsoft Updates causing this issue?

Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
Problem Description
When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
5.5.0 error message.
There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
Eg: Mindspring.com; Earthlink.net
Resolution
Resolve the DNS resolution problems that are causing occasional MX record failures.
Examples:
1. The Exchange server has multiple default gateways set on a multi-homed server.
This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
Action: remove the default gateway from one of the NICs.
This doesn’t applies to us, as we don’t use Internal DNS
2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
Action: remove this DNS server from the external DNS tab.
Workaround:
Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
Exchange Query Explained
1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
For example:
a. A bad DNS server listed as a forwader on the DNS server.
b. A bad DNS server on the TCP/IP properties.
c. A bad DNS server on the SMTP VS (external DNS servers)
d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
Regards,
Shahul Hameed Dasthagir
Support Engineer | Enterprise Communications Support

Exchange 2003 push notifications not working on iPhone4 running iOS 5

My Exchange 2003 push notifications are not working on my iPhone4 (iOS5). For this account I need to fetch. I know that at one point I was receiving push notifications from the Exchange 2003 account prior to upgrading to iOS 5 but unfortunately I did not actively monitor push notifications for this accout prior to upgrading to iOS 5. Push notifications work fine for other email accounts on this phone including an Exchange 2007 account. Are there any issues specific to iOS 5 and Exchange 2003 with regard to push notifications?

This is an issue that a lot of people are having... it's all on this thread.
https://discussions.apple.com/thread/4345374?start=0&tstart=0
The 'fix' that is decribed in the first post does not work. The only workaround is if you are on Wi-Fi, turn off Cellular Data and then reset the push service by turning on Airplane mode for a few seconds and then turn it back off. Seems to be an issue with the iOS talking to the new LTE CDMA chip on Verizon and Sprint iPhone 5s.

Upon opening Outlook 2003 get message "Not closed properly. File is being checked for erros."

When opening Outlook 2003 get an error message stating that is was not closed propertly and that the file is being checked. It can sometimes take up to 5-10
minutes for outlook to open. How can I stop this?

You need to figure out why Outlook is not closing property. The usual culprits are addins that access Outlook data.
Are you closing outlook before shutting down windows? If you let windows shut it down, you can corrupt the pst.
Does it work better in Safe mode? To open Outlook in Safe mode: Close Outlook then hold Ctrl as you click on the Outlook icon. You'll get a message asking if you want to start in Safe mode. Click Ok.
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

SAP Internet Mail Gateway for MS Exchange 2003 Server

Hi,
Has anybody successfully configured the IMG to work with MS Exchange 2003?
We have our 4.6C currently configured to talk to Exchange 2000 through SXC
Note 594428 - SXC: Exchange 2003 Server is not supported
Solution
R/3 Basis Release 3.1I to 4.6D:
Use IMG 4.6D and sendmail instead of the SXC (see note 101573), or
Upgrade your SAP system to Web Application Server (WAS) 6.10 or later and then use the SMTP plugin.
We only use outbound mail from SAP and this is sent to intranet users only, we are not planning on upgrading for a at least a year and would like to avoid installing another mail server.
Note 363154 - Internet mail gateway: use other MTA than Sendmail
This note suggests that any MTA (Mail Transfer Agent) can be used so long as it can be called from the command line, Exchange is an MTA, anybody now how to do a command line call for Exchange?
I have read the documentation
http://help.sap.com/saphelp_46c/helpdata/en/0c/39c93589c5ab53e10000009b38f839/frameset.htm
Jasper

hi,
we are in the process of configuring the Internet Mail Gateway on R/3 4.6c on Unix platform.
I have created the RFC Destinations in SM59 and also checked the Test Connection and its working fine. I then did the Unix configuration and went on to the check whether the configuration was successful in SO01 by sending a sample text message to my company's mail address. but i did not recieve any mails on my Microsoft Outlook, instead the count under the errors column increased by one.
on checking the status for the sent message in SO01, its saying "No Delivery to [email protected](for reason, see long text)... but there's no long text either...
Can anyone please let me know the reasons for it and it would also be really helpful if someone can let me know whether i have missed any configuration settings.
Also, can someone send the list of parameters that are to be entered for the Unix configuration under mlsomadm mailgw.ini, so that i can verify whether i have entered the parameters correctly....
Kindly revert back at the earliest...
Thanks & Regards
Manicks

SMTP: message submitted to categorizer

Hi
A few e-mails are recieved by the Exchange 2003 server but not delieverd to the recipent. When I track e-mails with Message tracking center Tool there are 3 lines in the dialog-box. These are:
SMTP: Message Submitted to Advanced Cueuing
SMTP: Started Message Submission to Advanced Queue
SMTP:Message Submitted to Catagorizer
These e-mails are 1 and 2 days old and of course important for the recipent. I've tried to reboot the server but this did not solve the problem.
We're using Microsoft Small Business Server 2003 Premium edition
Thanks for help

I've had the same problems.
Try disabling Antigen.
1. Stop the following services:
- Microsoft Exchange System Attendant
- Microsoft Exchange Information Store
- Microsoft Exchange MTA Stacks
- Microsoft Exchange Routing Engine
- Simple Mail Transfer Protocol (SMTP)
- IIS Admin Service
- Windows Management Instrumentation
2. In a command promtp disable Antigen
- C:\Program Files\Sybari Software\Antigen for Exchange
- antutil /disable
3. Start the stopped services of step 1.
Hope this is usefull!

Exchange 2003: Collab/Notification email relay issues

We use Exchange 2003 SMTP email server which is open internally and has relaying disabled.
The portal is installed on internal servers yet is having a problem sending notifications to external email addresses.
In the notification config file there are settings for email servers that have relaying disabled however this functionality doesn't work and the bug ticket for it has been opened for 4 years I'm told.
I'm wondering how smaller companies (<2000 employees) handle this issue.
Do you:
*enable relaying on your main email servers?
*setup a notification specific SMTP server?
*use a 3rd party email company?
What steps are there to reduce the threat of spammers and blacklists while still allowing email to be relayed?
I'm trying to work through this with our IT department but the idea of enabling relaying is a very touchy subject here as we have been burned by being blacklisted a few times in the past.
Thanks for any help!
Geoff

After going back and forth with Plumtree support for about 3 weeks we have solved the problem.
The problem came from a misunderstanding on what needed to be relayed. It turns out that external relaying is not needed, but internal relaying is.
Explicitly granting trust to the notification server allowed emails to begin flowing.
Geoff

Is Exchange 2003 Uninstalled?

I recently did a migration from Exchange 2003 to 2010. Everything seems to be working. After having the 2003 server shut down for a week or two with no issues, I decided to uninstall it.
After a few issues with remaining mailboxes etc, the uninstall process via Add/Removed ran. I had one error during the uninstall but unfortunately I didn't write it down. I believe it said something the effect of an error with messaging or something.
After click past that, the uninstall proceeded. If I now go into Add/Remove, the option for MS Exchange is no longer there however some of the services are still on the server, specifically the System Attendant and Exchange Management and they were running.
I have stopped and disable all Exchange services.
So my question is - how can I be sure it has uninstalled correctly and what are the ramifications if it didn't? Everything seems to be working but I just have this feeling that something is still left out there and things weren't completely cleaned
up.
Thank you for your help.

Agree with ExchangeITPro to see if ExBPA gives any error.
If Exchange 2003 Server object is removed from AD (Under configuration partition) then I wouldn't worry about it.
Open ADSI Edit, expand Configuration, expand CN=Configuration,CN=<domain>, expand CN=Services, expand CN=Microsoft Exchange, expand CN=<Exchange organization name>, CN=Administrative Groups, cn = CN=Exchange Administrative Group (FYDIBOHF23SPDLT),
CN=Servers, If Exchange 2003 server is not listed here then Uninstaller should have uninstalled it properly...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Office 365 Deployment w/Decommissioned Exchange 2003 environment

Hello,
I'm having an issue creating Office365 mailboxes. Here's my situation:
In 2011 we we migrated off of an on-premise Exhange 2003 server and on to Google Apps (Gmail). To my knowledge the on-premise Exchange 2003 server was fully decommissioned and removed from our network. Now we're try to move from Google Apps (Gmail)
to Office365. I've set up AD synchronization and all my AD accounts synchronize as expected. However, only some of my synchronized accounts are provisioning mailboxes correctly. After some troubleshooting on the Office365 community we were
able to narrow down the issue: http://community.office365.com/en-us/f/156/t/252194.aspx. It appears that the only accounts that are successully provisioning mailboxes are accounts that DID NOT previously have a mailbox associated on the on-premise
Exchange 2003 server...Accounts that DID hold a mailbox on the on-premise Exchange 2003 server are NOT being successfully provisioned with an Office365 mailbox. My understanding is that this is actually expected functionality...Per MS support techs:
If an AD account has attributes indicating an on-premise Exchange server, then Office365 will not provision a mailbox until the on-premise mailbox is migrated. The issue I have is, I do not have an on-premise mailbox to migrate or an on-premise Exchange
server at all.
My on-premise Exchange 2003 server no longer exists. What attributes do I need to remove and/or reset on my accounts for Office365 to be able to provision a mailbox correctly?
Thank you in advance!

Hi,
What’s the error message do you receive when trying to create the mailbox?
You can check the user’s AD properties by:
ldifde -f c:\<Name of User>.txt -d "distinguishedName of User"
Here is the detailed steps for getting the
distinguishedName of a user:
a. Run the Adsiedit.msc from a command prompt.
b. Expand “Domain”->”DC=domainName,DC=com”->”CN=Users”
c. Right click on ”CN=the problematic user name”, click “Properties”.
d. Find the attribute “distinguishedName” attribute. Double click copy the value of it.
Thanks,
Simon Wu
TechNet Community Support

Snow Leopard and MS Exchange 2003 -USING OWA-

I have a new 27" iMac with Snow Leopard. I am trying to connect to my company's MS Exchange 2003 via OWA NOT IMAP or POP, OWA. I dont like mail.app or like using iCal for calendering. So I like OWA using Safari or FF.
I also have several other machines in my home office: 8 Macs (Dual G5 - Leopard, 27" iMac - Snow Leopard, G4 Mini - Leopard, 15" Powerbook - Leopard, 15" MacBook Pro - Snow Leopard, 24" iMacs - Snow Leopard, and quad Intel XServe - Tiger) and a couple of Dells one with XP and one with Vista. I'm a geek, can you tell?
On every machine using Leopard and Snow Leopard, I cannot connect to Exchange 2003 OWA using Safari or FF. It takes forever and then once I get the login dialog it eventually times out.
HOWEVER, on Tiger no mater if on Quad Intel XServe or the Dual G5 (I can boot Leopard or Tiger), there are no problems. There are no problems conecting or logging into Exchange via Safari or FF.
Also, to reiterate, XP and Vista on a Dell have no issues, nor does XP on Fusion 3.0 int the 27" iMac.
So it HAS to be related to Leopard and Snow Leopard. Remember it is not an issue of time outs after logging in as some posts on ArsTechnica suggests, here we cant even get to the exchange server in a timely manor. When I ping the server it just sits there.
Ping results
PING chilcoinc.com (72.215.225.9): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
And it just keeps going.
Frankly, I am ****** and don't know what I am to do. I need this access and dread having to be forced into using imap or pop.
Microsoft was been useless. Their solution is Exchange 2007, But they cant seem to understand that I do not want to use mail.app and ical. I want to use the OWA!
Thanks for any help you guys can provide.
Mark

From my MBP with 10.6.2 I can connect using OWA both to a hosted service running Exchange 2007 and an internal service running Exchange 2003.
It sounds as if there is a problem with the network configuration. Is there any firewall between your client system and your company server? Are you using the same IP information (DNS, GW, etc) on the client as on the other systems which work for you?

Cannot Connect to Microsoft Exchange 2003

Hello all ,
I just bought my new iMac , i have been trying ti synchronize my internal emails ( work emails ) with Microsoft exchange 2003 but was not able to do so . I was using my laptop ( power book ) that has leopard 10.5.8 and mail 3.5 , it was working perfectly . Any new update that will fix this issue ? or is there a way to configure mail to synchronize with exchange 2003 ?

What is really weird from Apple is that the Iphone is connecting to exchange without wondering wether it's an exchange 2003 or 2007, but Mail does....
I connected my Iphone in a matter of minutes, but I just realized that it is a 2003 exchange server that I'm connected with.
So I asked my Admin wether I can connect thru IMAP.
Gilles

Exchange 2003 Provisioning issue

Hi All,
I am trying to create a user on Exchange 2003.In my setup AD & Exchange running on same host win2003 r2.As AD has configured in SSL Mode, i have not done any ssl configuration for Exchange.
User Provisioning to AD is happening successfully and when I am trying to do provisioing to Exchange OIM returning errors.In weblogic server trace, I am seeing some exceptions
*ERROR,27 Jan 2011 22:29:07,661,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getITAttrVal encounter some problems: Could not find attibute value for IT Resource*
Key = 0 and attribute = Remote Script Location
*ERROR,27 Jan 2011 22:29:07,786,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getITAttrVal encounter some problems: Could not find IT asset value for Svr_key = 0*
and attribute = Remote Script Location
*ERROR,27 Jan 2011 22:29:07,833,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getITAttrVal encounter some problems: DATA_ERROR*
com.thortech.xl.dataobj.util.tcAdapterTaskException: DATA_ERROR
As I am usiing Exchange 2003 I have not mentioned Remote Script Location and I have not created Seperate IT Resource, I am using ADITResource while provisioning.
Please Help me on this...
Regards,
Madhu

Hi,
Thanks for the reply..
I am using the same resource (ADITResource) with which I am able to provision to AD.From errors on weblogic console,it seems it is looking for Remote script which is required while provisioning to Exchange 2007.But I am using Exchange 2003.
Regards,
Madhu

Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

Hi
We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
from happening.
We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
Thanks
Nauman.

Hello,
Why do you want to use the 'internal relay domain' authentication?
Thanks,
Simon Wu
TechNet Community Support

Can't send using SMTP with SSL on Exchange 2003

We have an exchange 2003 server. The iPhone is configured for IMAP w/SSL for incoming and works fine. When we have SSL turned on on the outgoing SMTP, we get the message "Cannot send mail. Check the account settings for the outgoing server mail.domain.com". With SSL turned off, it works fine.
I set up outlook on a PC to use IMAP/SMTP w/ SSL and it works fine. I can send and recieve with no errors.
We're sure the user name and password entered for the outgoing are correct.
What else could be causing the iPhone not to send, but where Outlook works fine?

The new phone at the Verizon store had the exact same symptoms. Ergo...the problem was in my server.
So...if anyone else has this problem (can't send file attachments)...go to Exchange Server (I'm running 2007..settings on other version are slightly different), server settings, find the send hub. Click on it then look for the Exchange Active Sync tab and click it. Check the Ignore Client Certificates. This may only apply to those who run self generated SSL certs on thier Exchange Server...cheap **bleep**. LOL
I swear...last week, before buying this Thunderbolt my OG Droid sent file attachments just fine. Somehow I inadvertantly set the Active Sync to accept client certificates. To err is human...to blame it on Verizon is more so. LOL
Nate

Exchange 2003 SMTP messages not goingout

Similar Messages

Maybe you are looking for