OneNote emails are bouncing after a GAL change in Exchange

[Brian Krawchuk]

I have an interesting issue. I am seeing mails sent from OneNote bounving
with a "The e-mail account does not exist at the organization" message. Now,
this was the same state we saw initially when updating our GAL on our
exchange servers. We were able to go to `Tools' -> `Send and Receive' ->
`Download Address Book' in Outlook on the client side to re-update thier
cached GAL to correct the problem.

Now, the question is can this happen in OneNote? Is that the issue (cached
e-mail addresses) or is there something else that I am missing that should
be checked/corrected.

Thanks,

Brian Krawchuk

 

[Erik Sojka]

The bounces occur when sending to a person in the same company as you?

OneNote requires Outlook 2003 for its email capability, and you may have
noticed, simply calls up Outlook with "Word as the editor" when creating a
new message. So at first glance I'd expect you to have the same problems
emailing a plain text message to a person as you seem to be having mailing a
OneNote file to that person.

Can you verify that you can send OneNote files to others in the organization
and to external email addresses? Can you send *anything* to the email
address that is bouncing?

 

[Brian Krawchuk]

Erik,

E-mails are working normally. The user can mail to the address in question
directly through Outlook; it is only when attempting to mail from OneNote
they see the bounce. Most of their OneNote mails get through without
problems, only some of the address that were recently added to the GAL
(merger).

The client with the issue has refreshed their Outlook GAL, but this has not
cleared the issue.

Any other ideas or suggestions? Would a re-install work (last option
personally not wanted, but we do what we have to when it fixes things).

Thanks,

Brian K.

 

[Erik Sojka (MVP)]

Do you get any errors when addressing the message? Can you search the
GAL without errors? How about if you type part of the problem user's
name and press Ctrl-K?

That's strange. Can you ask your Exchange administrator to turn up
logging?