Adding a distribution list to another list

  • Thread starter Thread starter Amin
  • Start date Start date
How do i add a distributio list to another distribution list and update it
Click to expand...

Click Select Members in one DL, click To, and selec the other DL as a member.
Click OK.
 
Brian said:
How is nesting DL2 under DL1 any differnet than DL2 under a DL3?
Click to expand...

Because DL1 would have actual contact records which sometimes prevents
expansion of other DLs nested inside of it. If DL1 had 10 contact
records and DL2 had 5 records, and you nested DL2 into DL1, and you
tried to use DL1, you could end up sending only to the 10 records in DL1
and to none of those in DL2. Expansion of a nested DL sometimes does
not work if there are contact records inside the parent DL.

I don't use distros so the above is merely what I read from other users
complaining that nested DLs resulted in only using the contact records
in the parent DL and that the nested DLs did not get expanded. Once
they made a distro that *only* contained nested DLs and no contact
records then the expansion of the nested DLs worked.

What wasn't clear in those forum posts (where using a master DL that
only contained nested DLs and no contact records) is if the user had
added separate contact records. When defining a DL, you can click on
"Members" or "Add contact". Members are those already defined in your
contact-type folders. Adding a contact adds a separate entry inside the
DL that isn't attached to anything outside the DL. I couldn't tell if
these users had added independent contact records inside the DL or if
all contacts were added as Members (defined in a different record
outside the DL). So, from what I've seen work for users that complained
that nested DLs were not getting expanded and the solution that worked
for them, the parent DL must contain only member records and no contact
records. I don't recall which version of Outlook they were having a
problem with this nested DL expansion.

I found another reply post of yours in which you said there was no max
count limit for a DL defined within Outlook but there is one when using
Exchange. You sure? I've found articles that discuss this limit, like
http://www.sperrysoftware.com/Blog/...istribution-list-limitations-and-workarounds/,
and they don't mention Exchange is involved. Yet I found KB articles,
like http://support.microsoft.com/kb/238569, which specifically mention
the limit is when using Exchange. Non-Microsoft articles say the limit
is within Outlook while Microsoft articles say the limit is in Exchange.
 
Because DL1 would have actual contact records which sometimes prevents
expansion of other DLs nested inside of it. If DL1 had 10 contact
records and DL2 had 5 records, and you nested DL2 into DL1, and you
tried to use DL1, you could end up sending only to the 10 records in DL1
and to none of those in DL2. Expansion of a nested DL sometimes does
not work if there are contact records inside the parent DL.
Click to expand...

Is this your own experience? If not, upon what you you base it? I've never
seen anything in what I've read that nesting a DL inside another DL that also
contains contacts causes problems.
I found another reply post of yours in which you said there was no max
count limit for a DL defined within Outlook but there is one when using
Exchange. You sure? I've found articles that discuss this limit, like
http://www.sperrysoftware.com/Blog/...istribution-list-limitations-and-workarounds/,
and they don't mention Exchange is involved.
Click to expand...

And yet that don't explicitly say that their description applies when Exchange
is not involved. The limit without Exchange, if one exists, is significanlt
higher that when using an Exchange account, from what I've read and, as you
point out, Microsoft mentions a limit only in conjunction with Exchange. SMTP
protocols don't mention a limit in the number of RCPT TO commands, that I
recall, plus people I trust have said that if there's a limit, it's very high.
I'm not convinced there's a (practical) limit when the account is only SMTP
for outgoing messages.
 
Back
Top