SharePoint Distribution Lists - don't populate with users, unknown alias when sending email
I have MOSS 2007 set up to allow distribution lists. I have a specific OU and MX record. I can create the distribution list, but it doesn't populate any users. I add the users manually and the mail goes to the drop folder, but then gets "unknown alias" in the sharepoint log files. Also, when creating the distribution list, it doesn't fill in the correct/complete email address in the ou file.
Should be: spwebsitesowners@spdoc1.do
Not: spwebsitesowner@wa.gov
I'm not sure where to go from here.
Should be: spwebsitesowners@spdoc1.do
Not: spwebsitesowner@wa.gov
I'm not sure where to go from here.
ASKER
Ok, If I have a DL created from SharePoint, showing in the global address list. I send an email to that DL, it goes to the MOSS server (SMTP). Then it fails. Even though I've manually added the members into the list via AD OU. The alias for the DL in the Approve/Reject properties (on the CA) only shows the email, not the complete address. (i.e. spwebsitesowners)
so in your gal you see spwebsiteowners@spdoc1.doc
and from there you want it to send the message to the list of users and that part doesn't work?
I just want to make sure I understand the problem before suggesting a solution
and from there you want it to send the message to the list of users and that part doesn't work?
I just want to make sure I understand the problem before suggesting a solution
ASKER
Correct. But I also have the issue that when I create the list in SharePoint on the group, I go to the CA and approve it (rename the Title to DOC DL SP in front of it), the alias is showing only the email, not the complete address. I approve and in the OU: no members are populated and the email address is not complete. It only shows spwebsitesowners@wa.gov (should be ......@spdoc1.doc1.wa.lcl)
ASKER
I'm also getting errors when we try to add a new member to a group. It says that there is a problem with the directory management service.
The Directory Management Service has reported an error which is not recognized by Windows SharePoint Services.
The Directory Management Service has reported an error which is not recognized by Windows SharePoint Services.
what are the permissions that you granted the central admin application pool account on the OU you are using?
ASKER
Full control and it's inheireted down.
ASKER
Both the application pool account for the the CA and the web app have full control. I did read someplace that they had to be the same account. Is this true?
No it isn't true. Alot of the documentation out there is missing a required permission and the work around is to make them the same account and then everything works.
It is a good test to use the same account and see if everything works for now just to ensure that we are dealing with an account permission issue.
It is a good test to use the same account and see if everything works for now just to ensure that we are dealing with an account permission issue.
ASKER
I'll have to wait until our maintenance window to change that. Thursday evening. But I can probably try in our testing environment. I'm out the rest of today, will do it first thing tomorrow morning. Thanks
ASKER
Ok, fixed the routing issue. I had the wrong information in for the smtp server on incoming email. Now if I can just figure out why the directory management service errors when trying to add a user to the group with an email address for a DL and why there are no users added as members to the DL in AD. Also, if I try to find the DL to set up an alert, I can't find it. But I can find it if I'm looking in outlook to send an email to the DL.
ASKER
I reset the account for the application pools to be the same as the CA app pool account. That worked. I now have the distribution lists working correctly on the test site. But when I tried to do the same in prod using the sts command to updateaccountpassword, it didn't reset the account. Can I change them in IIS?
ok so that does prove its permission related. You need to delegate the app pool account permission in AD To the OU that you want to create contacts in. Make sure that it gets create contant objects, Create all children and delete contact objects and all children.
ASKER
It has the exact same permissions as the CA account has.
and the CA account adds users into the AD object and the web app account doesn't?
ASKER
Right now on production - the web apps run under a different account than the CA. Distribution lists get created, but no membership and not discussion contacted is done.
On dem - all web apps, including CA, run under one account. Distribution lists works as it's suppose to. Members are added to the list and the discussion contact is created. They work fine.
On prod, both accounts have the same exact permissions in AD on the OU and child objects.
On dem - all web apps, including CA, run under one account. Distribution lists works as it's suppose to. Members are added to the list and the discussion contact is created. They work fine.
On prod, both accounts have the same exact permissions in AD on the OU and child objects.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'll go through this today and see if I can find what's missed. Thanks
It sounds like you have a alias - Exchange(if that is your mail system) routing issue. You need to make sure that Exchange is configured to route all emails with the suffix @spdoc1.doc1.wa.lcl to C:\Inetpub\mailroot\Drop folder of SMTP Virtual Server installed on your MOSS Server.