Page 1 of 1
Stranded Delegates
Posted: Mon Mar 08, 2010 3:46 pm
by keywestcity
I'm having the issue where people are receiving NDR's when creating calendar entry's. Apparently this is some kind of outlook issue created after a delegate is removed but it's functionality still remains. I found this MS article on how to remove the stranded delegates when using exchange. Problem is things are different with scalix so not all the steps are the same. Was wondering if anyone has fixed this issue with scalix.
This is the MS article I'm talking about http://support.microsoft.com/kb/253557
Re: Stranded Delegates
Posted: Tue Mar 09, 2010 7:43 am
by ls-al
Use sxaa against the mailbox with the stale delegate.
Re: Stranded Delegates
Posted: Wed Mar 10, 2010 12:35 pm
by keywestcity
Hey can you give me an example of how to use sxaa? I'll start looking for documentation on the command but that can be a struggle sometimes..
Re: Stranded Delegates
Posted: Wed Mar 10, 2010 12:45 pm
by ls-al
Code: Select all
[root@server ~]# sxaa --user "John Doe"
OOF FLT OLK AANO ACTION TITLE STATE
--- --- --- ---- ---------- ------------------------------ --------
Y 450 REDIRECT Scalix redirected message disabled
Y 451 REDIRECT Scalix redirected message enabled
500 FORWARD Scalix OOA Auto Action disabled
Y 501 REPLY Scalix OOF auto-reply disabled
[root@server ~]# sxaa --user "John Doe" --info 451
Conditions
----------
AND (
Item Class = "IPM.Schedule.Meeting%"
)
Action
------
REDIRECT to S=Doe/G=Jane/OU1=company/CN=Jane Doe/INTERNET-ADDR="Jane Doe" <jane.doe@company.com>
Retain intray copy
You should have a look at the redirects with numbers between 450 and 500. Use "sxaa .... --remove <number>" for the redirect that causes the error.
Re: Stranded Delegates
Posted: Wed Mar 10, 2010 2:54 pm
by keywestcity
Thanks for the help. That worked!
For anyone who has this problem in the future here are the commands I used:
This gives you a list of the rules applied on the users account. A stranded delegate will come up as a redirect.
sxaa --user joe@keywestcity.com
if you have several redirects and are not sure which one it the broken setting you can run the info command to find out
sxaa --user joe@keywestcity.com --info 450 (the 450 is the reference number, each redirect will have a unique ref number)
Once you find the stranded delegate you can remove it with
sxaa --user joe@keywestcity.com --remove 450