You can add mailboxes on your server, and you can add contacts. So if you have a distribution group that you need an external email address in it, add a contact for the email address then add the contact to the distribution list.
All distribution lists will have a email address that if you send email to it all members will get the email.
I think this is what you want.
A member of a DL has to be an object, user, contact, or else. What is the email associated with? Where does it live?
What is the object that contains the email.
@Nosh
I am adding a mailbox on a DL/DG. I was able to add it on Advanced View>extended attribute.
@ Nosh @Darren
I think i resolved it. I added the mailbox in the "Advanced view" tab > Extended Attributes, added the mailbox under Manually managed Membership > verified.
I kept on adding the mailbox using "Add member" and "Members" Tab that's why i'm getting "Please remove, correct or resolve unresolved name."
Thanks a lot to your replies! Appreciate it!
I am sorry, but I don't see how this answers my question I asked twice already. Can you show some screen shots perhaps of what you are doing and the error.
Again, you need to add by displayName or accountName or something that is part of the search scope. You cannot add by emailAddress. So if this is a user whose displayName is bugundi and email is b@something.com, you need to type budgundi. You can also click the little book and select from the
I am confused by the conflicting statements here. I resolved, and I need help on the same thread. Are you still having issues? If yes, please read my first response.
An email address is a property of an object. In FIM you can only add an object to a DL, not a property.
So, please pay attention here and tell us what type of object are you adding to this DL? User, Group, DL, Contact? Or what??
Technically, if you include the Email attribute in the AttributesToSearch property of the UOCIdentityPicker control, you could type in the SMTP address, and RESOLVE to find the Object that contains that Email Address.
The point is, the ExplicitMember attribute is a reference type, so it must contain references to other FIM Objects in FIM.