[str8down]

No luck here either. Have modified the AdminSDHolder attributes, and then re-modified the domain level attributes, no luck. The "Send As" is there on the users objects, but when I do an effective rights check, no dice.

[hdawg]

Is permission inheritance being blocked to this user object?

[str8down]

No. But I even applied it explicitly just to make sure.

[hdawg]

Something is going on in AD then ... the permission must be explicity denied somewhere. Has the users container permissions or any parent container permissions been modified?

[str8down]

Ok, even more strange. I was able to get the permissions to stick, and checking effective permissions, "send as" is there. SO everything is all good right? Wrong, still can't send mail. Application event log still gives the permissions error. What gives?

[hdawg]

Are the permissions still set? If the permission is still there any you can't send can you provide the error from the ALRT log?

[str8down]

[30000] (09/10 14:21:36.171):{0x744} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent SERVERNAME Agent 1 (Application Event Log on SERVERNAME) | 09/10/2007 14:21:36 (AFFF4F29) -> {My.Name@domain.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed


Renamed the email address and server name for security.



And there is the AD security just to verify.

[exchangesolution]

this may be a long shot....but you can give it a try..

in exchange 2000-2003 environment admin groups have DENIED send as permission assigned to them on the smtp virtual server.....

so using ADSIEdit go to the smtp virtual server

configuration\services\microsoft exchange\CN= yourdomain\administrative group\first administrative group\servers\your server\protocals\smtp\CN=1

right click ....properties....security......and make sure that person or group
is not assigned denied "send as" permission.....

[str8down]

Thanks for trying, unfortunately I guess that's not the issue.

[str8down]

Also, it is obviously an Exchange/AD issue, and nothing to to do cdo.dll or anything to the BES, becasue logged into my outlook client as me using the BBEST credentials, I get the same error trying to send an email. So that at least narrows it to exchange/AD rights.

[hdawg]

Check your permissions inheritance on the user object, and its parent OUs.

The "In Theory Easy" fix: Export mailbox, blow away account, re-create account, create new mailbox, import mailbox reactivate on BES.

Why does the group BB Test have so many permissions on this object?