ben_stanton
asked on
Error 550.5.7.1 Client does not have permissions to send as this sender
Hi Guys and Girls,
I have 250 users all on my exchange 2007 box. All users can send via OWA with no problem what-so-ever. I have one user that needs to use POP or iMAP (in OE) and recieves the following error message when sending (recieveing is fine): Error 550.5.7.1 Client does not have permissions to send as this sender. I assumed it was just a POP/iMAP issue but it turns out she cannot send via OWA either (clicking new/reply/forward produces nothing - not even an error).
I have tried around 10 other users from the same and/or differnet AD OU's and OWA/POP/iMAP all worl hunky dorey - it is purely this one user! I am not yet terribly up to speed on the new 'console for everything' approach so don't even know where to start, all obvious GUI configurations for that mailbox seem fine.
Any help urgently and greatfully recieved!
Ben
I have 250 users all on my exchange 2007 box. All users can send via OWA with no problem what-so-ever. I have one user that needs to use POP or iMAP (in OE) and recieves the following error message when sending (recieveing is fine): Error 550.5.7.1 Client does not have permissions to send as this sender. I assumed it was just a POP/iMAP issue but it turns out she cannot send via OWA either (clicking new/reply/forward produces nothing - not even an error).
I have tried around 10 other users from the same and/or differnet AD OU's and OWA/POP/iMAP all worl hunky dorey - it is purely this one user! I am not yet terribly up to speed on the new 'console for everything' approach so don't even know where to start, all obvious GUI configurations for that mailbox seem fine.
Any help urgently and greatfully recieved!
Ben
ASKER
Not sure what you mean there. But there has been no different configuration made to that one mailbox. It was created just like all the others
Each and every user has SMTP addressed stamped by Exchange.
There will be a Default SMTP address for all the users. If this user has more than one SMTP address, then check for the default SMTP address.
>>>> veera.
There will be a Default SMTP address for all the users. If this user has more than one SMTP address, then check for the default SMTP address.
>>>> veera.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had this problem too. I added my own SMTP Send Connector to the Hub Transport but there was this single user who just couldn't relay mail. I copied the command suggested above and pasted into the CMDlet for Exchange 2007 and it worked instantly!
I had to alter the syntax to get it work. Used this syntax:
get-receiveconnector 'recieveconnectornamegoesh
where 'recieveconnectornamegoesh
I had to alter the syntax to get it work. Used this syntax:
get-receiveconnector 'recieveconnectornamegoesh
where 'recieveconnectornamegoesh
Well the discuss has been great, it is/was a combination of all the discussions that actually solves the problem for all, at least me.
1) the NT_Authority\self resolution has more details than presented. Charlie on another forum gave this clue:
go the the Exchange management console and select the user. Right Click, go to the send as permissions option.. check that User NT AUTHORITY\SELF is listed. If not add it.
2) Another user identifed the following power shell as necessary
[PS] C:\Windows\system32>add-ad
MTP-Accept-Authoritative-D
Note the double quotes when your connector has a space in it. aka "domain users"
You have to perform this on both your internal and external connector, then restart the transport and hub services. These steps were left off many forums.
Note the '-' in front of ExtendedRights. This was originally presented without this '-' and there is a command -AccessRights ExtendedRight which lead many to a goose chase.
3) Many discussions are about one user having sendas on another. The topic was about the actual User1 not being able to send as 'User1'. The above steps are for User1 not being able to send as User1.
4)Within Outlook, If you get an error, it is necesary to remove the account or repair it within Outlook, or else the error will 'stick' until you do. Again, another forum had this hidden gem.
5) The above line: get-receiveconnector Client <servername> | add-adpermission -user AU -extendedrights ms-Exch-SMTP-Accept-Author
fails with Exchange 2007, the modified version is:
get-receiveconnector "ConnectorName" | add-adpermission -user AU -extendedrights ms-Exch-SMTP-Accept-Author
I'm unclear as to the nuance of this vs the above add-adpermission comand, but it took both to make it work.
Note the quotes around "ConnectorName' are unnecessary unless you have a connector name with a space in it.
Thanks for everyones help, I hope the above steps saves the next soul some hours.
1) the NT_Authority\self resolution has more details than presented. Charlie on another forum gave this clue:
go the the Exchange management console and select the user. Right Click, go to the send as permissions option.. check that User NT AUTHORITY\SELF is listed. If not add it.
2) Another user identifed the following power shell as necessary
[PS] C:\Windows\system32>add-ad
MTP-Accept-Authoritative-D
Note the double quotes when your connector has a space in it. aka "domain users"
You have to perform this on both your internal and external connector, then restart the transport and hub services. These steps were left off many forums.
Note the '-' in front of ExtendedRights. This was originally presented without this '-' and there is a command -AccessRights ExtendedRight which lead many to a goose chase.
3) Many discussions are about one user having sendas on another. The topic was about the actual User1 not being able to send as 'User1'. The above steps are for User1 not being able to send as User1.
4)Within Outlook, If you get an error, it is necesary to remove the account or repair it within Outlook, or else the error will 'stick' until you do. Again, another forum had this hidden gem.
5) The above line: get-receiveconnector Client <servername> | add-adpermission -user AU -extendedrights ms-Exch-SMTP-Accept-Author
fails with Exchange 2007, the modified version is:
get-receiveconnector "ConnectorName" | add-adpermission -user AU -extendedrights ms-Exch-SMTP-Accept-Author
I'm unclear as to the nuance of this vs the above add-adpermission comand, but it took both to make it work.
Note the quotes around "ConnectorName' are unnecessary unless you have a connector name with a space in it.
Thanks for everyones help, I hope the above steps saves the next soul some hours.
>>>> Veera.