This has been one of the toughest assignments for a while due to the lack of error
details. No eventlog and no AD or MOSS Logs.
Basically setting up In-coming Emails works like this:
1) the MOSS Server in the farm will poll a SMTP ‘drop’ directory (usually c:\inetpub\mailroot\drop).
So mail has to find its way to that drop directory.
2) The Sharepoint Directory Management Service will (if told to) go and automatically
create ‘entities’ (contacts) and assign them email addresses in the OU specified below.
That’s the theory!!
The DM causes a couple of issues – you’ve got to run the site under an acct. that
has access to the OU (you may need to assign assign the appropriate permissions to
the OU in AD for this user)
The DM creates these Contacts by supplying a Schema full of info and this inturn creates
the Contact. Problem – what if your AD schema doesnt match what DM expects…..“Error
in Application!”
(This took me the longest – as I had this running in 5 mins on a client site and then
on a different site….no go)
The schema ‘additions needed’ for the DM to work ‘seemlessly’ are added when you install Exchange2003/2007 –
the initial parts of the install are ForestPrep and DomainPrep – I
ran these on their own without installing Exchange and the DM worked a treat!!!
(I’m sure you’d be able to add the appropriate schema extensions 1 by 1 without the
need for Exchange and then be able to run any mail server – but which ones?)
3) Within Central Operations setup the incoming emails to be something like this:
My server is called MOSS and it’s part of the LITWAREINC
Domain
3) Now under site settings you can easily enable Incoming emails