[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2725
  • Last Modified:

Configure WSS 3.0 to accept incoming email messages.

Need help configuring WSS 3.0 to receive incoming mail.  My scenario is that I have exchange 2003 running on a separate server than my Sharepoint server.  Since I'm already using a farm configuration is it really necsesary to:  Install SMTP on my sharepoint server, add mx record to my dns & add a Exchange SMTP Connector to get incoming email to work? The WSS help says that you don't have to specify a smtp server if you use the "advanced" option and specify a drop folder.  I've tried all of these configurations and I'm still unable to receive mail.  The error I get over and over again is "The destination server for this recipient could not be found in Domain Name Service (DNS).  Please verify the email address and retry.  If that fails, contact your administrator."

This error makes perfect since because I've created a "friendly" domain name in the Operations, Incoming Email Settings section...  When I use my mail domain name, I get an error that the user can't be found..What am I missing?  
0
TravelSmith
Asked:
TravelSmith
  • 5
  • 4
1 Solution
 
kaushal2004Commented:
not clear what you are trying to achieve here.  are you trying to have WSUS send you email when new updates are pushed or approved through WSUS?
0
 
trippleO7Commented:
Please take a look at these articles.  They helped me with my WSS 3.0 setup and Exchange 2007.  Their is tutorials for Exchange 2003 however.  It's a very precise step-by-step....great tutorial!  You'll still have to set up SMTP on the WSS server and add a 2nd MX record (20) with a priority value greater than your primary mx record (10).

http://www.combined-knowledge.com/Downloads%202007.htm

http://msmvps.com/blogs/obts/archive/2006/10/30/229077.aspx

0
 
TravelSmithAuthor Commented:
I used the combined-knowledge article and I'm still having issue...does the dns entry need to be made to my external dns server (hosted by my isp) or my internal dns server (my domain controller?)  I only tried it on the internal dns.  I'll look at th msmvps link to see if that makes a difference.  The end result is that I want our users to send meeting requests that include the sharepoint calendar and have these meetings show up in sharepoint.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
trippleO7Commented:
I guess I only did the internal DNS since I was using sharepoint strictly on our Intranet.  Are you doing the same thing?  My desired result was to do exactly what you wanted to do.  E-mail meeting requests to sharepoint Calendars.

I'll be out of the office for a couple of days, but I'll try to post back if I get some free time.
0
 
TravelSmithAuthor Commented:
Thanks - yes that's exactly what I"m trying to do..I'm redoing all steps from scratch including the SMTP connector in Exchange..Not sure of the settings on that connector but I'll fiddle around to see if I can get it to work.
0
 
TravelSmithAuthor Commented:
OK I'm almost there..everything is working up to the point where the messages are sitting on the Sharepoint server -they are sitting in the queue folder (c:/inetpub/mailroot/queue).  When I open the message using outlook express the error is that delivery has failed.  SO it looks like the SMTP service is receiving the messages but doesn't know what to do with them.  Checked the Sharepoint timer service and it's working fine.
0
 
trippleO7Commented:
Thought I'd check back in one last time before I left....Good to see you're making progress!

At the end of the Combined knowlege document there's some extra tips....two that might be causing your issue could be (first two on that list):

* Ensure that the Central Administration Application pool account and the SharePoint Timer Service account are using the same service account.

* Make sure the above account has access rights to all files on the server used by incoming mail such as the sharepointemailws.asmx file on the Moss server that is receiving the incoming mails. Alternatively make these accounts local administrators on the web servers receiving the incoming mail

Maybe verify those are correct quick...

We'll touch base in a day or so.

Rory
0
 
trippleO7Commented:
So what ended up being the issue with them sitting in the drop folder?
0
 
TravelSmithAuthor Commented:
It was because the server name was wrong...I used the syntax servername.domain.com instead I should have used the FQDN of our doman which ends in intl not .com.
0
 
trippleO7Commented:
ahhh...ok.  Well good to hear you got it resolved.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now