User A was in the organization.  User B is a new user.  User B took over User A's role.  I originally renamed User A to User B, but decided to create a new account and import User A's pst into User B's mailbox.  Deleted User A's account. 

When User B modifies a calendar entry that was originally created by User A, they are able to send updates, but receive a NDR stating they do not have permission to send on behalf as.  

Is there a way to give user B send as rights to a deleted account.  Or take full ownership of the calendar entries. Or clean up the references to User A in these entries.  I have seen posts on how to delete them, but the User B will need these for day to day operation.

I have an Exchange 2007 Server with all the updates and service packs installed. I have just installed Exchange 2013 CU1. I created a test mailbox on Exchange 2007 and migrated over to the 2013 server. When I try to send an internal email from the Exchange 2013 mailbox to a Exchange 2007 mailbox I get the following error and the recipient never receives the email:

Remote Server at  returned '451 4.4.0 Primary target IP address responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

Authentication settings on the send connector is configured to allow Exchange Authentication. Any assistance would be appreciated. Thanks!

Hello all,

I have an Exchange Server 2013 and I would like to limit the allowed external Domains for all Users to just one.

So I created a new send connector with only this domain. Sending to this domain now works fine.

BUT:

All emails send to the other domains will be stuck in the queue for the configured retry time (1day) and then produce an NDR

#550 4.4.7 QUEUE.Expired; message expired in unreachable destination queue. Reason: A matching connector cannot be found to route the external recipient ##

QUESTION:

How can I get the NDR instantly with out the delay of one day. But I would like to still have a high retry value for all other errors.

Thank you,

Alex

During a public folder synchronization between Exchange 2003 and Exchange 2010 there where some problems related to SMTP. We stopped the synchronization and restarted SMTP services. All mail flow returned to normal operation. Only in a specific time window all send e-mails had the following condition if you looked at them in message tracker. It only showed "Message submitted from store" for multiple times and then the log stops. The e-mails do not show any normal followwing events such as advanced queueing and routing. The e-mail are in the users sent items folders they do not receive NDR's but the recipients do not get the e-mail. The e-mails are not visible in any mail queue they appear to be in some grey area. The server also had a reboot but the status of the e-mails stays the same in message tracker. Is there a possibility to see the mails on a physical location or force exchange to still execute the normal procedures so the mails are still delivered. The problem occured 3 days ago i also don't know if there is a time limit for this grey area.

Good morning.

Within my company we have some "trusted EXTERNAL companies" that are not allowed to received emails from "yahoo, gmail, hotmail....). When we receive an email from this domains (Ej, gmail) and we forward it to one of those external companies, their "SPAM filter" block those emails because come from a forbidden domain (gmail) instead of arrive from our company smtp address (ex: steve@mycompanyname.com).

Do you know how can we set to forward emails using our SMTP address instead of use the original one (ex, @gmail.com)?

Sorry for my english, im not native speaker.

THanks in advance.

Hello Guys, I have a new Exchange 2013 install and i am having problems receiving internet email. When testing from https://www.testexchangeconnectivity.com it fails at the last step when it tries to send a test email. I get the following response:

The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Exception details:
Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()

Any Suggestions??

Hi Everybody,

while deploying Exchange 2013 (first Exchange server in organization) I recognized that authorized users are only allowed to send as users configured recording their mailbox.

Now we have users/devices sending with SMTP (no Outlook!) that should be allowed to send as any sender (for who no mailbox might be configured)

We have some internal ReceiveConnector configured (SMTP-LAN-Relay) and I have set extended permissions with:

[PS] C:\Windows\system32>Add-AdPermission -Identity "SMTP-LAN-Relay" -User "NT-AUTORITÄT\Authentifizierte Benutzer" -ExtendedRights ms-Exch-SMTP-Accept-Any-Sender

I can see these permissions also when quering the permissions

[PS] C:\Windows\system32>Get-ReceiveConnector |Get-ADPermission|where {$_.User -like '*authentifi*'}|ft identity,user,extendedrights,accessrights

Identity                              User                                  ExtendedRights                       AccessRights
--------                              ----                                  --------------                       ------------
VM-EXCHANGE01\Default VM-EXCHANGE01   NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Submit}                {ExtendedRight}
VM-EXCHANGE01\Default VM-EXCHANGE01   NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Bypass-Anti-Spam}           {ExtendedRight}
VM-EXCHANGE01\Default VM-EXCHANGE01   NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Accept-Headers-Routing}     {ExtendedRight}
VM-EXCHANGE01\Default VM-EXCHANGE01   NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Recipient}  {ExtendedRight}
VM-EXCHANGE01\Default VM-EXCHANGE01   NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}
VM-EXCHANGE01\Client Proxy VM-EXCH... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Submit}                {ExtendedRight}
VM-EXCHANGE01\Client Proxy VM-EXCH... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Bypass-Anti-Spam}           {ExtendedRight}
VM-EXCHANGE01\Client Proxy VM-EXCH... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Accept-Headers-Routing}     {ExtendedRight}
VM-EXCHANGE01\Client Proxy VM-EXCH... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Recipient}  {ExtendedRight}
VM-EXCHANGE01\Client Proxy VM-EXCH... NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}
VM-EXCHANGE01\SMTP-Anywhere-Relay     NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Sender}     {ExtendedRight}
VM-EXCHANGE01\SMTP-Anywhere-Relay     NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Recipient}  {ExtendedRight}
VM-EXCHANGE01\SMTP-Anywhere-Relay     NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Accept-Headers-Routing}     {ExtendedRight}
VM-EXCHANGE01\SMTP-Anywhere-Relay     NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Bypass-Anti-Spam}           {ExtendedRight}
VM-EXCHANGE01\SMTP-Anywhere-Relay     NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Submit}                {ExtendedRight}
VM-EXCHANGE01\SMTP-Anywhere-Relay     NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}
VM-EXCHANGE01\Outbound Proxy Front... NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}
VM-EXCHANGE01\Client Frontend VM-E... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Recipient}  {ExtendedRight}
VM-EXCHANGE01\Client Frontend VM-E... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Accept-Headers-Routing}     {ExtendedRight}
VM-EXCHANGE01\Client Frontend VM-E... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Bypass-Anti-Spam}           {ExtendedRight}
VM-EXCHANGE01\Client Frontend VM-E... NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Submit}                {ExtendedRight}
VM-EXCHANGE01\Client Frontend VM-E... NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}
VM-EXCHANGE01\SMTP-DMZ-NoRelay        NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Accept-Headers-Routing}     {ExtendedRight}
VM-EXCHANGE01\SMTP-DMZ-NoRelay        NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-Bypass-Anti-Spam}           {ExtendedRight}
VM-EXCHANGE01\SMTP-DMZ-NoRelay        NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Recipient}  {ExtendedRight}
VM-EXCHANGE01\SMTP-DMZ-NoRelay        NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Submit}                {ExtendedRight}
VM-EXCHANGE01\SMTP-DMZ-NoRelay        NT-AUTORITÄT\Authentifizierte Benu... {ms-Exch-SMTP-Accept-Any-Sender}     {ExtendedRight}
VM-EXCHANGE01\SMTP-DMZ-NoRelay        NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}
VM-EXCHANGE01\SMTP-MX-NoRelay         NT-AUTORITÄT\Authentifizierte Benu...                                      {ReadProperty}

Unfortunately this setting is not working at all, that means I still get errors

5.7.1 Client does not have permissions to send as this sender

when sending as nomailboxexists@domain.tld while authenticating as my.user@domain.local
I also tried ms-Exch-SMTP-Accept-Authoritative-Domain-Sender already instead of Accept-Any-Sender, no change.

Any ideas? Any help?

Thanks a lot in advance!

Matt

In a Ex2010/2013 coexistence scenario, and you configure an Ex2010 Edge server to route inbound and outbound SMTP traffic, how does the Ex2013 mailbox server route emails to mailboxes that are still on Ex2010 mailboxes?

ST

I have no problem sending e-mail from any account of my corporate mail to other accounts including gmail, outlook, yahoo.<o:p></o:p>

Receiving works good too except from when someone is trying to send me from outlook/hotmail account  (that includes web interface services). Then I get the classic error: smtp 530 5.7.0 must issue a starttls command first.<o:p></o:p>

I have tried to follow several approaches I found on web such as activating/deactivating tls, creating an additional connector on exchange server but with no luck.<o:p></o:p>

Has anyone any idea why this is happening for outlook/hotmail and not the others? Could it be due to the fact that the certificate I use is self-signed? Any pointers or other ideas would be much appreciated.

(My installation is on Exchange Server 2003, on Windows Server 2003. Sorry for posting into Exchange Server 2013 forum I had no other option).

Hi everybody,

we are implementing a MX Exchange 2013 (CU 2) as the first Exchange server in the organization.

A ReceiveConnector for connections from our LAN network should allow authenticated users to send mails as any sender string. The solution I found here and elsewhere on the net seems to be simple:

Add-ADPermission -identity smtp-lan-relay -user "nt-autorität\anonymous-anmeldung" -extendedrights "ms-Exch-SMTP-Accept-Any-Sender"
Add-ADPermission -identity smtp-lan-relay -user "nt-autorität\anonymous-anmeldung" -extendedrights "ms-Exch-SMTP-Accept-Authoritative-Domain-Sender"

Unfortunately it is not working with FrontendTransports!
If I delete the connector and set it up as HubTransport it works!

Now my questions:

• is that a known issue / bug or a wanted behaviour?
• is there any disadvantage if I am running the connector as Hubtransport instead of FrontendTransport (as it should be)?

Thanks a lot for your help!

Hi everyone,

I'm testing to create an auto forward rule from user's OWA, forward all incoming mails to addresses in the outside world (Yahoo, Gmail, ...). It does not work at all.

I digged deeper and find out that "... When a mailbox is created, the value of the DeliverToMailboxAndForward parameter is set to $false by default", so I run the following command in Exchange PowerShell:

Set-Mailbox -Identity "MailboxName" -DeliverToMailboxAndForward $true
No error returned. But the auto forward rule still didn't work.
When I use the Admin EAC to look at the recipient properties/mailbox features/forwarding address, there's an option to enable forwarding , but only to internal accounts/pre-created contacts.
Is Exchange Server 2013 restricted the ability that allows normal users create auto forward rules?
We are using Exchange Server 2013 CU1.
Any idea would be highly appreciated. Thank you!

Hi,

I am looking at Exchange 2013 plus DLP.  I am also looking at Sophos to do Antivirus plus DLP since they have a much more comprehensive coverage.  My question here is,  Does anyone know if Exchange or Sophos can provide multi level approval before an sensitive email or attachment can be sent out?  Thanks.

Regards,

Hi,

Our edge server seems to delay emails sent to some domains without an DNS/MX record. For example emails sent to a gmail.com.au account will be delayed instead of rejected. It appears to be related to the fact that @gmail.com exists.

____________________________________________________________________________________________________

Delivery is delayed to these recipients or groups:

user@gmail.com.au

Subject: test

This message hasn't been delivered yet. Delivery will continue to be attempted.

The server will keep trying to deliver this message for the next 3 days, 19 hours and 53 minutes. You'll be notified if the message can't be delivered by that time.

___________________________________________________________________________________________________

However, if the domain does not exist at all it does reject them:

Diagnostic information for administrators:

Generating server: xxxxx

test@fnidsncoindscoid.com
#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##

__________________________________________________________________________________________________

It appears that it will delay emails sent to any @domain.com.au if the @domain.com exists. This is means that end users are not provided with instant feedback that they are inadvertantly attempting to send to a wrong email address. Anyone dealt with this issue previously? Any advise assistance would be appreciated. 

Hi, I receive in my Exchange PEC mail (italy electronic certified mail) this mail include in attach the original mail and is .eml. When I receive this mail, the attach is 35 byte and not the real size and is empty.

I full patch my Exchange 2010 sp3, I reboot the server and for 6 hours all work perfectly. Then If I receive another pec, the problem come back. I reboot and for 6 hours I work perfectly.

In addition: the mail already downloaded in my account or any account if it's downloaded when the problem is present are not visible after the restart of my Exchange. And he remain lost. Only the new mail are working after reboot.

I try to disable all tranfert agent but the problem persist. Can you help me? Thank's

Alessandro Romualdi

Thanks for taking the time to look, I really appreciate it!

Not sure what I missed but these are the steps I've taken.

I added the domain to postini.

Updated the MX records to point to postini (domain.com.s8a1.psmtp.com.......)

Added the domain as an accepted domain to our exchange hub.

Add the domain to my inbox.

When trying to send to this it keeps bouncing back.

Here is the SMTP test I did at www.testexchangeconnectivity.com

We have a motley collection of COTS business applications with limited SMTP capabilities.  These applications generate e-mail messages to customers on behalf of our employees.  For instance an application will send a confirmation or invoice to a customer with a specific account manager as the from address.  All of these COTS applications use the same IIS SMTP server to send out of our network to the world.  I'd like to be able to modify some of these messages as they go out.  For example add CC, add receipt requests, append legal disclaimers, etc, all details that the COTS applications don't support.

Is it possible to make the basic SMTP server append header?  Would an Exchange SMTP be able to do this?  Anyone know of any other SMTP relay solutions that can modify headers?

Hi all,

The next issue is bothering me for days now.. hope someone can point me to the solution :)

I've got an Exchange 2010 server (14.03.0146.000) with all roles installed (except Lync)  

I've got an application who uses an SMTP relay. 
I've set-up a recieve connector, to allow the IP adress of the application server, with anonymous access. 

I can send an e-mail to a user, or to distribution group A. But it doesen't work for distribution group B.

Offcouse I checked if the "require that all senders are authenticated" is not checked. Even with Get-DistributionGroup <<naam>> | fl  I can't find an diference between group A and B..

- The message doesn't stay in the queue
- Mails to Group A are in the message tracking, messages for Group B are not.
- I can send mails from Hotmail/Gmail to Group B
- No difference if I make it an Mail Universal Group or Mail Universal Security Group. 

Hope someone can point me in the right direction! 
Kind regards,
Robert

Robert Jager

The Microsoft Exchange Frontend Transport service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Invalid agent configuration in file 'C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Shared\fetagents.config'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Invalid agent configuration in file 'C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Shared\fetagents.config'. ---> System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at Microsoft.Exchange.Compliance.Xml.SafeXmlDocument.Load(XmlReader reader)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExConfiguration.LoadPublicAgents(String filePath, List`1& publicAgents)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExConfiguration.LoadPublicAgents(String filePath, List`1& publicAgents)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExConfiguration.Load(String filePath)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath)
   at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()

Hi,