I did exactly as said by the Combined Article. Thanks Steve.

Yes, it do creates contacts in the OU then emails do come to DROP folder.

BUT

The emails still there in drop folder without dissapearing. And it does not get publshed in the sharepoint lists….

I have setup all as said in article. What my concern here is either SMTP or SharePoint being cracky…

Anyone for my rescue?…

I’ve been fighting with the “Error In Application” error as well, and eventually relented from using the “least privileged” configuration of having separate accounts for our CA and web apps, to just having one service account that runs both. That sorted the problem creating Contacts in AD, but if we disable incoming email for a specific list, it still gives the dreaded “Error In Application” error, the Contact is not deleted, and the list remains email enabled. Any ideas? Using the farm account, i can manually delete the Contact from AD, so I don’t think it’s permissions….?

– Step 3 was a typo. I edited my post (I know that’s taboo, but hey I’m not a reporter or anything!). As far as being a host or alias, I’m pretty sure it was an alias. It was a DNS record I had our MCSE “admin guy” put in for us. Essentially making sharepoint..kdhcd.org resolve to the IP of my SMTP mail server.

- .org only because of our organization’s internal domain. (I hide that info because I like my job).

- As far as the FQDN, I would imagine you could use that as long as it points to where your SMTP server resides.

A guess is that your issue is related to a DNS resolving situation. Try pinging your FDQN; does it resolve your SMTP server?

I can’t get emails routed to my SharePoint server from my exchange server. SMTP on SharePoint and incoming email works fine because I can drop a email into the c:\inetpub\mailroot\pickup and it shows up in the drop folder, then gets posted in the SharePoint document library. So emails are not getting delivered correctly. In trying to resolve my issue, I noticed you did some things that other sites I’ve read didn’t.
Namely, creating a new SMTP virtual server, but need some clarification on the following….

- In Step 3, is that a host or alias record being created for sharepoint..com?

- In Step 4, you created a new SMTP virtual server named sharepoint..com, but in the image it shows “.org” instead of “.com”…which one is correct?

- Why did you decide to use “.org” for the name space for SharePoint? Could I just use the server’s FQDN?

I’m not sure if this is where my problem lies, but I’ve also read about maybe needing to create MX records or use an SMTP connector. Do you think I’ll need any of these?

Thanks!

Reviewing SMTP logs doesn’t help much, they are un-decipherable.

Thank you, Tom

Thank you, Tom

I would venture to guess that when the error message refers to the “resource” that it is referring to the document library. Although, that is just a guess.

I wonder if you could open the .eml file in the drop folder before the OSWTIMER.exe grabs it. Compare the header information with an .eml file from the copier that is working.

Possibly the offending copier is adding extra information in the header of the e-mail?

Is the referenced ‘resource’ the involved document library??

Thank you, Tom