Microsoft Windows Server 2003 Standard Edition
GroupWise Gateway for Lotus Notes 7 SP1
When you send to a GroupWise distribution list thru the Notes gateway when the
GW recipient reads the message, the first name in the distribution list is
duplicated on the TO: line.
If I have a distribution list with lets say 10 users in it as members (User1 >
USER10) on the TO: line participation.
This distribution list is replicated to the Notes system via the Notes gateway.
NOTE: You of course must change the visibility of the GroupWise distribution
list from Post Office to System in order for the distribution list to replicate
over to the Notes address book.
The Notes user sends a message to this GroupWise distribution list(on the TO:
line in Notes client) that is chosen from the Notes address book, the GW user
reads the message and the USER1 name is duplicated 10 times on the TO: line.
If you have 100 users in the Distribution list then USER1's name would be
duplicated 100 times on the TO: line. All other members do not show up on the
Very similar but slightly different problem when sending to a distribution list
from Notes to GW:
1. Distribution list members are User1 (TO: line participation), User2 (CC:
line participaton), and User3 (BC: line participaton).
2. If USER1 reads the message, that name is on the TO: line and CC: line.
3. If USER2 reads the message, USER1's name is on the TO: line and CC: line.
Problem as USER2's name does not showing at all.
4. If USER3 reads the message, USER1's name is on the TO: line and CC: line.
However USER3's name is on the BC: field.
It this situation it appears that the first user (USER1) in the distribution
list that is in the TO: field participation is duplicated on the CC: field, and
the other users never show up on the TO: line or CC: line in the message when
Misc. Info: Defect268080 states that the sending client field used ( TO: , CC:
or BC: ) will take precedence over the GroupWise Distribution list member
participation attribute (TO:, CC: or BC:)
This problem has been duplicated and reported to GroupWise development. No current workaround.