Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

odd issue - not able to send or forward messages from just 1 mailbox

Status
Not open for further replies.

ayavauser

Technical User
Sep 22, 2005
388
US
MM3.1 with exchange 2003 - for some reason just one user is unable to send or forward messages from their TUI - allows them to record message , lets them enter the mailboxes to send = follow prompts to send says cancelled


fyi - using aria tui

same can be said for forwarded messages

just odd .....

yet in the OHV trace says its sent to recipients - logging it to the other mailboxes announces no new messages

its just this one mailbox - setup as the same as others


cheers

would a rebuild be in order ? as this has cleared all sorts of funky issues in the past

ayavauser
 
It sounds like their send as. You may want to look at the user in AD and make sure they are able to send on behalf of them self

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
Ken ,
good thought - checked AD account they are setup as others - members of vmdom

Security / MM Security Permissions - allow : special permissions -

Security / Self - allow : read , read phone and mail options , special permissions -


when sending or forwarding when pressing the # to send - comes back with " message cancelled "

we can send or forward messages to said troubled user without issue just not like wise

will keep looking to see if we find anything :)

cheers



ayavauser
 
I have had this same issue at two different installs with MM3.1 exchange back end with the aria interface. Message forwarding works for all users with the exception of one or two users (All users are setup the same). I have not been able to find a solution to this as yet. I hope someone out there has figured it out. In the last case the MAS died and was rebuit from scratch by avaya tier 4. The user that had the problem prior to rebuild continued to have the problem after. All other users are fine.

The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to the office.
 
after sifting through - compared apples to apples on a few accounts that could and the 2 that could not

The issue ended up being that the 2 troubled users did not have MM Service Permissions in thier AD / Security setting
although it was assigned as members of : /Security


The reason for this is inheritance was turned off in the security tab/advanced for these 2 users so unlike all the other users they were missing this as it did not propagate down from the parent - resolve was to just added MM Service Permissions and check off only send as - uncheck all others



hope this helps

ayavauser
 
if accounts are members of protected groups within AD (usually administrators run into this issue alot) then they will not inheirit permissions and the Send As permission has to be set at the adminSDholder object before their accounts will have the correct permissions so that they can send, forward and reply to messages.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top