Solved

Exchange 2007/Outlook 2013: Distribution Group SendAs Issue

Posted on 2016-08-19
4
44 Views
Last Modified: 2016-09-24
I have an annoying weird issue where doing a SendAs with a DL only works if picking the address from the GAL. However if the second time I pick it from the now cached entry, it tries to do a Send on Behalf.....which of course is denied and I get an NDR. Of course have had no luck searching forums or the Internet.

Here is the current environment:
2008 Forest and Domain
Exchange 2007 SP3
Outlook 2013

This issue of course only occurs in Cached Mode. I have gone so far to even delete the Outlook OAB file and redownload it. Again this works every time, even in cached mode, when I pick the address from the GAL. Just for some reason tries to send with Send on Behalf Of permissions which choosing it from the cached entry in the auto-complete list.

Is this just one of those weird rarely known issues? FYI: I am looking for a fix.....if there is one.....not a work-around or unsupported fix.
0
Comment
Question by:Silverwolf
  • 3
4 Comments
 
LVL 18

Expert Comment

by:Serena Hsi
ID: 41764126
It would appear that this issue comes up frequently, regardless of the version of Outlook. It's like this recurring bug that never gets fixed from version to version. You'd think that after n-iterations of the application, the fix would get in eventually...

Here is what Microsoft suggest for Office 365 "Send As" error for sending.

Here is how to clear the caching issue for Outlook 2010.

And some other suggestions on the fix
0
 
LVL 1

Author Comment

by:Silverwolf
ID: 41765305
Serena,

Thank you however those don't work or apply in my situation. The first link refers to only a feature in Office 365 or Outlook 2016. The second link doesn't apply because it is talking about a mailbox, not a distro list. Also I stated in my initial question that I have already cleaned the Autocomplete cache. The other suggestions also do not apply and are already things I have tried.
0
 
LVL 1

Accepted Solution

by:
Silverwolf earned 0 total points
ID: 41805299
Update:

Turns out the issue was do to the OS for the CAS server being corrupted. Had to setup a new VM and then restore Exchange to it. Worked fine after that.
0
 
LVL 1

Author Closing Comment

by:Silverwolf
ID: 41813558
Only one suggested solution provided, which I had stated in my question that that was tried. Also my notes showed that the suggestions given did not relate in anyway. However it mostly was due to my issue being caused by a corrupt OS, which none of the suggestions relayed to that issue.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Large Outlook files lead to various unwanted errors and corruption issues. Furthermore, large outlook files can also make Outlook take longer to start-up, search, navigate, and shut-down. So, In this article, i will discuss a method to make your Out…
This article runs through the process of deploying a single EXE application selectively to a group of user.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

791 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question