I haven't seen this one before:
1) UserA (with Outlook 2003) gets an email that is sent to some people in our office, and also some from a client of ours
2) UserA presses "Reply to All" and everyone shows up in the message. The people in our office (and oviously therefore in our ActiveDirectory) show up as underlined names. The clients (not in our office) show up as names and email addresses that are underlined.
3) UserA presses "Send" and the message goes out with no errors
4) We then look in her "Sent Mail" and those users are not in there. They were there prior to pressing "Send"
5) I went through and deleted each email and instead typed in their email addresses directly and then sent it - and that worked.
In the past, I have seen where the address for some reason gets malformed (usually the Exchange/Outlook connection breaks while the message is on screen and so the address data gets confused), but it lets you send, then it goes out and bounces back due to it being malformed.
Does Outlook 2003 quietly kill those off instead of letting the server handle it with an error? That seems like a bad idea.
Any ideas?
We are running on Exchange 2003 and some users have Outlook 2000 and some have Outlook 2003. The Outlook 2000 users don't appear to have this exact same issue.
If this is better suited in the MS Office or Exchange 2003 forums, please let me know.
1) UserA (with Outlook 2003) gets an email that is sent to some people in our office, and also some from a client of ours
2) UserA presses "Reply to All" and everyone shows up in the message. The people in our office (and oviously therefore in our ActiveDirectory) show up as underlined names. The clients (not in our office) show up as names and email addresses that are underlined.
3) UserA presses "Send" and the message goes out with no errors
4) We then look in her "Sent Mail" and those users are not in there. They were there prior to pressing "Send"
5) I went through and deleted each email and instead typed in their email addresses directly and then sent it - and that worked.
In the past, I have seen where the address for some reason gets malformed (usually the Exchange/Outlook connection breaks while the message is on screen and so the address data gets confused), but it lets you send, then it goes out and bounces back due to it being malformed.
Does Outlook 2003 quietly kill those off instead of letting the server handle it with an error? That seems like a bad idea.
Any ideas?
We are running on Exchange 2003 and some users have Outlook 2000 and some have Outlook 2003. The Outlook 2000 users don't appear to have this exact same issue.
If this is better suited in the MS Office or Exchange 2003 forums, please let me know.