YOu might want to show a code snippet to illustrate how you are expanding the DL.
-- Sue Mosher, Outlook MVP Author of Configuring Microsoft Outlook 2003 http://www.turtleflock.com/olconfig/index.htm and Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "Sanjay" <spatel005[ at ]gmail.com> wrote in message news:1147449352.148968.141960[ at ]g10g2000cwb.googlegroups.com...
[Quoted Text] > Some more details.. > I have one DL "DL Group ALL" that is composed of 2 DL's "DL Group 1" & > "DL Group 2". Now if I add these DL's individually to a message, > Outlook and the plugin behave as expected. > > But if I add "DL Group ALL" to the "TO" list of a new message and then > expand the "DL" and then hit send, the 2 child DL's are reported as > olUser instead of olDistList. >
"Sue Mosher [MVP-Outlook]" <suemvp[ at ]outlookcode.com> wrote in message news:%23DX5WqddGHA.3348[ at ]TK2MSFTNGP03.phx.gbl... I'd check in ADU&C to see just what kind of Exchange DL this might be -- whether there's a difference between it and one that works as you expect. For example, is the membership hidden?
"Sanjay" <spatel005[ at ]gmail.com> wrote in message news:1147445903.275590.172420[ at ]g10g2000cwb.googlegroups.com... > It is an Exchange DL -- > "Sue Mosher [MVP-Outlook]" <suemvp[ at ]outlookcode.com> wrote in message news:e7ZO7LddGHA.3632[ at ]TK2MSFTNGP05.phx.gbl... What kind of DL -- personal or Exchange? "Sanjay" <spatel005[ at ]gmail.com> wrote in message news:1147441133.727150.141130[ at ]u72g2000cwu.googlegroups.com... > Hello -- > I have a VSTO plugin for Outlook 2003 SP2. It checks the recipients > for each message against a list and issues a warning if there is a > match. If the recipients list contains a Distribution List, it will > resolve all the recipients within that DL and do its validation... > > My issues is that outlook will intermittently report the DL recipient > as a "olUser" instead of "olDistList"... > > ie: Recipient.DisplayType is reported as olUser.. Even the members > property of Recipient.AddressEntry is null. > > Has somebody else faced this issue? Please suggest workarounds.. > > Thanks. > > Sanjay >
|