Exchange 2007 - Send As Permission

Hello, I have Exchange Server 2007 installed on my Windows Server 2008 system and am using an ASP.NET web application to send an e-mail message when certain events occur. My problem is that I have everything set up and functioning properly, the e-mail message is sent with the designated e-mail address and I receive the e-mail message with no problems. In order to do this, I have a generic e-mail address that I created for my domain and granted that generic e-mail address "Send As" permission for a different domain e-mail address and use the generic e-mail address in my ASP.NET web application for security purposes.
My problem is the "Send As" permission seems to disappear very frequently. It seems that I need to go into the Exchange Management Console and grant this Send As permission every time my server is rebooted, or even after going into Exchange Management Console to "Look around" and see what I have set up. Does anybody know if there is a way to make the grant of Send As permission permanent so I don't have to constantly re-grant it? I have applied SP1 to Exchange Server 2007 and am always sure to apply the most recent patches, etc. as soon as they are released.
Thanks in advance!
Tim

Dear customer:
Thanks for Bala’s reply. He is right.
Active Directory uses a protection mechanism to make sure that ACLs are set correctly for members of sensitive groups. The mechanism runs one time an hour on the PDC operations master. The operations master compares the ACL on the user accounts that are members of protected groups against the ACL on the following object:
CN=adminSDHolder,CN=System,DC=<MyDomain>,DC=<Com>
Note "DC=<MyDomain>,DC=<Com>" represents the distinguished name (DN) of your domain.
If the ACL is different, the ACL on the user object is overwritten to reflect the security settings of the adminSDHolder object (and ACL inheritance is disabled). This process protects these accounts from being modified by unauthorized users if the accounts are moved to a container or organizational unit where a malicious user has been delegated administrative credentials to modify user accounts. Be aware that when a user is removed from the administrative group, the process is not reversed and must be manually changed.
The following list describes the protected groups in Windows Server 2003 and in Windows 2000 after you apply the 327825 hotfix or you install Windows 2000 Service Pack 4:
• Administrators
• Account Operators
• Server Operators
• Print Operators
• Backup Operators
• Domain Admins
• Schema Admins
• Enterprise Admins
• Cert Publishers
Additionally the following users are also considered protected:
• Administrator
• Krbtgt
So first, please check whether the user that you grant “sends as” permission for it belongs to the above group. If so, open ADSIEDIT.msc, Check"Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with entries explicitly defined here" option on the adminSDHolder. And replicates all the DC, and grant “send as” permission for the user again via EMC, check whether the “send as” work fine.
For more information about adminSDHolder, please refer to “MORE INFORMATION” section in the following article:
Delegated permissions are not available and inheritance is automatically disabled
http://support.microsoft.com/kb/817433/en-us
Additionally, for more information about Exchange 2007 Permissions, please refer to the following documents:
Exchange 2007 Permissions: Frequently Asked Questions
http://technet.microsoft.com/en-us/library/bb310792.aspx
Hope it helps. If you have any question, please feel free to let me know.
Rock Wang - MSFT

Similar Messages

Exchange 2007 Sending with Second Email Address (trying to use Send As)

I support a company who just bought another company. I'm trying to bring a couple of users' old email addresses in to Exchange and have it work with their old and new addresses. They can receive mail under old and new accounts just fine. Sending
under the old address is the problem. They still need to send under the old address for existing contracts.
My first attempt was to create a distribution group, give it the user's old email address, and then give the user "send as" rights for the group using the Exchange Management Shell. I ended up with the same error I'll detail below.
My next (and current) attempt was to set up a shadow user in AD with the old email address and then give the user "send as" rights to the shadow mailbox. I assigned the "send as" permission by right-clicking on the mailbox and choosing
"Manage Send As Permission" and then adding the real user to the list. In Outlook, I clicked From and then choose the shadow user account from the Global Address Book. This added the address to the From drop down box.
This works, once... Every time I restart the Information Store service, I can get one email to send out successfully. Here is the error I get on every other attempt. Notice it says "send on behalf" in the error. Maybe I'm not
setting it up correctly in Outlook? I didn't make Outlook screenshots but you'll find my AD and Exchange setup screenshots below.
Thanks for the help.
(also posted at http://forums.msexchange.org/m_1800602162/mpage_1/key_/tm.htm#1800602162)
***ERROR START***
Delivery has failed to these recipients or distribution lists:
Tripp Beasley
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required
permission.
Diagnostic information for administrators:
Generating server:
[email protected]
#MSEXCH:MSExchangeIS:/DC=local/DC=XXXXXXXXXX:XXXXXXXXXX[578:0x000004DC:0x0000001D] #SMTP#
***ERROR END***

open the list of previous recipients and select the ones you need by holding the command button. then press "add to address book".

Exchange 2010: Send As Permission for group mailbox...

Our helpdesk has a shared mailbox used for users to submit issues. Up until a week ago, all of the helpdesk techs could send-as the shared mailbox.
Now when they attempt to send as the shared mailbox via Outlook they get the error "You do not have the permission to send the message on behalf of the specified user.". When I attempt to manage send as permission via EMC (using an account
with Domain Admin privileges) I've found that the list of users who can send as is blank. When I attempt to add send as permissions via EMC I get the error below:
domain\username
Failed
Error:
Active Directory operation failed on DC1.xxxxxx.local. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
The user has insufficient access rights.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.3.195.1&t=exchgf1&e=ms.exch.err.Ex6AE46B
Exchange Management Shell command attempted:
Add-ADPermission -Identity 'CN=account,DC=xxxxxx,DC=local'
-User 'domain\username' -ExtendedRights 'Send-as'
Elapsed Time: 00:00:00
Anyone have any advice to fix this issue?
Thanks in advance for your help.

I got this sorted. Here's the fix:
On the problem account: Open up active directory > Select the target user account > properties > Security Tab > advanced button. If
you cannot see the Security tab you have to go to view > advanced features
On the Permissions tab put a check mark in Allow inheritable permissions from
the parent and click ok

Exchange 2007 Send Connectors

Hello,
I'm relatively new to administering Exchange and I had some questions on Send Connectors. We send mail to a few different domains that usually 75% of the time will generate a message saying:
Delivery is delayed to these recipients or distribution lists:
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 1/9/2014 9:31:13 AM (GMT-05:00) Eastern Time (US & Canada). Microsoft Exchange will notify you if the message can't be delivered
by that time.
Sometimes messages will make it to the intended recipients and other times not. Most of the time they are just regular emails without any attachments on them. I'm not exactly sure how connectors work, but I'm thinking that I can set one up to tell exchange
that it should route these certain emails to that domain. Is this the correct thought process on how a send connector would work and are there any ramifications I need to worry about if I set up a second or third send connector?
I apologize if this is naïve or doesn't make sense. Please let me know if you need more information. We run Exchange 2007 on Windows SBS 2008.
Thank you.

Hi,
It seems that it could be a reverse DNS lookup issue. I recommend you check if the reverse DNS record is configured correctly.
If it is ok, I suggest you enable logging at your send connector. Then check the log to see if you could find some clues.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 send as permission not allowed

We have a Exchange 2013 server and Outlook 2010 clients. I have set full permission on other mailboxes with Powershell and in the ECP I set Send As permission for this user. But when I start Outlook 2010, go to the mailbox of one of the users and try to
send an email as this user, the Outlook gives the error that send as is not allowed. What could the problem be?

Hi,
Please log in the Exchange Admin Center in Exchange 2013 to check whether the permissions are configured properly:
1. Access ECP URL in IE to logon EAC as an administrator.
2. Click recipients > Mailbox.
3. Double-click the userA which is set full access permission and send as permission.
4. In the User Mailbox window, click mailbox delegation to check whether the userB is listed under Send As and Full Access permission.
If the permission is configured correctly, please try removing the permission and re-add it to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Import csv file in Address Spaces in an Exchange 2007 Send Connector

hello , i must put more than 300 domains in the addres space of a Send connector.
is possible have a csv file with the 300 domains and a powershell script to import this file in the address space of one send connector?
example csv file :
cepsa.es
repsol.com
parsi.es
Regards
Thansk in advance
mcse 200x + mesaging 2000 2003 2007 2010

Hi
At First, you CSV should be set as the format like
Name
cepsa.es
repsol.com
parsi.es
If you would like to set a new Send Connector. you can simply do
New-SendConnector -Name ConnectName -AddressSpace ((Import-CSV <PathOfCSV>) | ForEach {$_.Name})
If you would like to add to a Send Connector that already existed, Please run
$al = (Get-SendConnector -Identity <ConnectName>).AddressSpaces
$al += (Import-CSV <PathOfCSV>) | ForEach {$_.Name})
Set-SendConnector -Name ConnectName -AddressSpace $al
Cheers
Zi Feng
Zi Feng
TechNet Community Support
The first script is still working as it should under Exchange 2013 when a send connector is created for the first time.
The second part of adding (or removing) address spaces from an existing send connector was a little bit trickier.
the following script did it:
Get-SendConnector "ConnectorName" | Set-SendConnector -AddressSpace ((Import-CSV <PathOfCSV>) | ForEach {$_.Name})
Watch out! this command also removes domains which are not present in the csv file!

Exchange 2007 send connector does nor respect Maximum message size (sometimes...)

Hi to all
We have 9 email server, 5 Mailboxes, 2 CAS and 2 HT, We began to have problems to send and receive from internet; so I checked the queues and I discovered that some users are sending messages with a size greater than 16 MB, althought internally can send
until 40MB, if they send externally, only until 16MB.
I revised all the configuration:
Organization Configuration/Hub Transport/Global Settings/ Maximum send size (KB):40960
Server Configuration/Hub Transport/HT01/Receive Connectors/Default HT01/Maximum message size(KB): 40960 (only this server can send outside, the other server is in spare)
Organization Configuration/Hub Transport/Send Connector/SendMailOuside/Maximum message size(KB) 16386
We send by an Smart host that is used only by the HT01 to a Symantec server.
With this, we have this situations:
In the queue, I see some users are sending emails with a size more than 16MB outside the organization, I revised their configuration and the "maximun send size" is clear the checkbox (just like my account), the weir is if I try to send an email
with a size more than 16MB, I got the message: "#550 5.3.4 ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##", this is not sense because their account configuration is the same like mine, so the Exchange must not let
them to put the email in the queue...
If between internal users try to send an email with size more than 16MB, this is allowed and it's send without any problem
So I don't know where is the misconfiguration, is permited to send mails with size less than 40MB internally, but externally only until to 16MB, but I din't know why the Exchange system let some users to send (or at least put in the queue) this kind of messages,
my account is in the same DB like the other users...
I hope to be clear in the description of the situation, maybe a patch or some thing, the HT server has the January patch and in april will be applied the last patchs.
Doc MX

Hi DocMX,
Thank you for your question.
We could run the following command:
Get-TransportConfig | FL max*size
Then, we could check the send connector by the following command:
Get-SendConnector | FL Identity,MaxMessageSize
We could run the following command to check an individual user maximum size.
Get-Mailbox <username> | FL Name,Max*size
In my solution, we could rebuild the user profile that those users could send emails more than 16MB to check if the issue persist.
We could also restart the service of “Microsoft Exchange Transport”.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Calander Sharing Permission is not effective between Exchange 2007 & Exchange 2013 User

When a Exchange 2013 mailbox user share a calander with user in Exchange 2007 with OWNER permission, but Exchange 2007 user cannot modify or view full details of Exchange 2013 user calander.
And same behavior from Exch2007 user sharing calander with Exch2013 user.
In both scnarioes we can view only free/busy information. Cannot see full details of the meetings, cannot edit/modify. But permissions are set correctly.
Getting Yes or No prompt window with message "You dont have permission to view the calander, Do you want to as User A to share his or her calander with you?"
We are in Co exsistance with Exch2007 and Exch2013 CU3.

Hi,
Does the issue happen to all users? What about Exchange 2007 users share calendar with Exch2007 users?
Please double check whether calendar permissions are configured properly. If possible, we can remove the permission in Outlook then re-add it back later to check whether it works.
Thanks,
Winnie Liang
TechNet Community Support

Manage full access and send as permission in Exchange 2007

Hi,
I try to delegeate helpdesk the permission in ECM to manage Full Access and Send As permission.
I ran the PS command
Add-ADPermission -Identity "CN=Exchange Org,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local" -User "domain\ADGroupDelegation" -ExtendedRights ms-Exch-Store-Admin -InheritanceType
All
Now the helpdesk tech are can manage Full Access permission in EMC, but still not have access to manage Send As permission.
Thanks for your help !
MA
M.A.

Hi,
The issue maybe related to the Active Directory Replication Latency. The Send As permission is not granted until after replication has occurred. Replication times depend on your Microsoft Exchange and network configuration. To grant the permission immediately,
stop and then restart the Microsoft Exchange Information Store service. You can restart the Microsoft Exchange Information Store service to check the result.
Here is a relate article for your reference.
How to: Send As permissions and how long it takes for them to apply
http://blogs.technet.com/b/pakaloge/archive/2009/08/21/send-as-permissions-are-not-enforced-immediately.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Cannot send email from Exchange 2007 to Exchange 2013

Hello Anyone,
Anyone can help? I've prepare MS Exchange 2013 already, for Migration MS Exchange 2007 and I got the issue.
My issue is I can't send email from Exchange 2007 to Exchagen 2013, but for Exchange 2013 can send email to Exchange 2007,
is my issue only internal email for external email both Exchange server is working fine.
Regards,
Eakkasak

Thanks for your reply, when I send email from Exchange 2007 to Exchange 2013 I'm get the error message below.
Delivery is delayed to these recipients or distribution lists:
Eakkasak Buajan
Subject:
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 8/29/2014 8:30:29 PM (GMT+07:00) Bangkok, Hanoi, Jakarta. Microsoft Exchange will notify you if the message can't be delivered by that time."
I'm already tick "Exchange server Authentication" in the Default Receive connector properties of Exchange 2013"
I'm restart services and restart all Exchange Server but doesn't work.
Thanks,
Eakkasak
Sent by Microsoft Exchange Server 2007

Cannot send email from Exchange 2007 to Exchange 2013 - Coexistence

Existing Exchange 2007 SP3 1 MBX, 2 CAS/HT, 2 ET servers.
I have added an Exchange 2013 server with MBX/CAS role.
Email will flow from Ex2013 server no problem. Mail from Ex2007 systems cannot deliver to Ex2013 boxes, it dies in queue with a 4.4.7 expired message after issuing a delay message.
I can telnet to ports 25, 587,717,465,475, and 2525 from Ex2007 HT role to new Exchange 2013 server. I can send email from Ex2007 HT role server to new Exchange 2013 server using telnet to port 25.
A ‘get-mailbox’ from the Ex2007 HT role server returns the server and database properly on the test users on Exchange 2013 server.
The only strange thing I am seeing is from the Ex2007 systems, a ‘get-exchange server’ command shows the new Ex2013 server as role ‘16439’ which looks to perhaps be normal.
Why is email not flowing to the new users on Exchange 2013?

You should have exchange server authentication ticked in Default Receive connector in Exchange2007.
Exchange 2007 and Exchange 2013 in the same subnet/network. if not please check any spam agent running between the networks. Are you running antispam on Exchange2013 ?
MAS

Send connector from exchange 2007

Currently since I have both environments up, I see that Exchange 2013 is using the send connector that was created in my exchange 2007 environment. Will this send connector go away once I bring down my exchange 2007 environment? Shoould I create
a new one for Exchange 2013?

Hi
From what i have seen running ex2010 and upgrading to 2013 it stayed (exchange 2013 is clever :-)). you can just modify your send connector and make sure that the settings are for your exchange 2013 server.

Cannot send mail from Exchange 2013 to Exchange 2007

I have an
Exchange 2007server with all roles in the same server (Version:
08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
(full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
few articles on the Internet.
Any suggestions?

These two sentences are in conflict : "I can also send
internal mail
from Exchange
2007 to
Exchange 2013. But
the problem is
that I am unable
to send from Exchange
2007 to
Exchange 2013. "
Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

Exchange 2007 OWA sends attachments Outlook connector clients cannot send attachments.

Exchange Server 2007 SP1 + Rollup ***Problem with sending email attachments from Outlook 2007***
* Inbound mail arrives in OWA and Outlook normally with and without attachments.
* OWA email to external email account with attachment goes thru successfully.
* Outlook 2007 sends to an external email address with attachments the message does not arrive at the external mailbox. The messages leave Outbox but are never delivered. The messages appear in Sent Items also.
* Outlook sends non attachment emails to external addresses successfully.
* Outlook sends email attachments to local domain accounts fine.
#1 Exchange Server on Server 2013 fully patched problem commences. Exchange Server on version less than first RTM release of Exchange 2007.
#2 Outlook profiles were changed to see if that is the problem.
#3 Upgraded Exchange to SP1 and Rollup 10(Rollup was autodownloaded by MSUpdate)
#4 Ran EXBPA nothing of any interest in the report.
--Unified Messaging not configed (Done nothing)
--SenderID (Re-enabled) I had shut all of the antispam to eliminate these.
-- Junk Store threshold not configed (No change)
Any suggestions to get Outlook clients capable of sending attachments configured.
Thx,
-Scot

Hi Scot,
Providing some information on Poison Queue:
The poison message queue is a special queue that's used to isolate messages that are determined to be harmful to the Exchange system after a transport server or service failure.
The messages may be genuinely harmful in their content and format.
Alternatively, they may be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
The poison message queue is typically empty. If the poison message queue contains no messages it doesn't appear in Queue Viewer or
Get-Queue results. The messages in the poison message queue are never automatically resumed or expired. Messages remain in the poison message queue until they're manually resumed or removed by an administrator.
According to the description above, I suspect Outlook 2007 changed the email's format when send email with attachment. The reason as below:
If the original email's (with attachment) content or format is harmful to the Exchange 2007 server, it will go to the Poison Queue when sending via OWA. However it didn't, sending via OWA is perfect. So I suspect it is an issue on the Outlook 2007
client side.
Please using Pipeline Tracing to verify whether there is something changed during transmission.
More details in the following article:
Using Pipeline Tracing to Diagnose Transport Agent Problems
http://technet.microsoft.com/en-us/library/bb125198(v=exchg.80).aspx
If it is convenient, I suggest doing following tests to narrow down this issue:
Note: Same content, same attachment, same format.
1. Please using Outlook 2010/2013 or others' Outlook clients for testing.
2. Please change to another format for testing. More details in the following article:
Change the message format to HTML, Rich Text, or plain text
http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HP001232996.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Mail Sender Adapter for Exchange 2007 IMAPS account

Hi everybody,
I have the following todo:
I configured a Mail Sender Adapter that is supposed to fetch mails from an IMAP account.
The mails contain text files with data to be processed by XI 3.0 SP 22.
The mail server is Exchange 2007 and requires IMAPS. IMAP is not enough. I read the notes
- 893590 - XI 3.0 Mail sender adapter with IMAP or POP with SSL problem
- 856599 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 Mail Adapter
and configured the sender apapter as follows:
URL:                     imaps://<ip address>/owa
Authentication method:     Plain
User:                    <domain>\<user>
Password:                       topsecret
Poll Interval: 5
The first challenge is to setup the adapter with SSL. To do so, I added the Exchange server's
root SSL certificate in the default truststore service-ssl via the KeyStorage service.
This is necessary, as far as I know, to successfully validate the Exchange server's trusted
certifacate which is being transfered to XI during SSL handshake.
Since the communication channel in RWB is in status error with following message:
mail client job stopped completly
exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO owa doesn't exist.
mail client job scheduled,
I do not know how to setup SSL for IMAPS. I successfully tested a PING to the Exchange server.
Are there already experiences with Exchange 2007?
What I have to do to fetch mails from an Exchange 2007 IMAPS folder/account with a Mail Sender Adapter?
Kind regards,
Andreas

Hi,
It should be imap and not imaps.
You can try imap://xxx.xxx.de:993/Inbox
Make sure that port 993 is correct. If you have doubt, then you may try 143 which is default port instead of 993 in the above url.
regards,
ganesh.

Exchange 2007 - Send As Permission

Similar Messages

Maybe you are looking for