Feeds:
Posts
Comments

Online PowerShell


Connect to all Office 365 services in a single Windows PowerShell window

For all online PowerShell commands

https://technet.microsoft.com/en-us/library/dn568015.aspx

 

for exchange online use the following

## Exchange

Import-Module MSOnline

$O365Cred = Get-Credential

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Connect-MsolService -Credential $O365Cred

 

For SharePoint online use the following

 

##Sharepointonline

 

Set-ExecutionPolicy RemoteSigned

$credential = Get-Credential

 

Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking

Connect-SPOService -Url https://domainhost-admin.sharepoint.com -credential $credential


On-premises user isn’t receiving emails from online user

 

First we must move the user to un synced OU

The log in the the server which have the Azure AD sync tool

And open the windows azure active directory tool

Now that we have moved the user in a unsynchronized OU and that it’s appearing in the “Deleted users” section, you have to forcefully delete the user so you won’t have to wait for 30 days:

Run the following command

In the azure power shell

Start-ADSyncSyncCycle -PolicyType Delta

Then open the PowerShell and connect to the online exchange

Use the following command

Import-Module MSOnline

$O365Cred = Get-Credential

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Connect-MsolService -Credential $O365Cred

Then run the following to get the object ID

Get-MsolUser -ReturnDeletedUsers | FL -Property ObjectId,displayname

We must get the user objectID

Remove-MsolUser -ObjectId 080535c0-061a-4b0e-a6fe-48ed7fc9159d -RemoveFromRecycleBin -Force    

Note: make sure you enter the correct ObjectId

After deleting the user, you will have to make sure his cloud mailbox is also deleted using one of the following cmdlets:

Get-Mailbox -Identity “username@domain.com | Remove-Mailbox -PermantentlyDelete $true

Get-Mailbox -SoftDeletedMailbox “ username@domain.com ” | Remove-Mailbox -PermantentlyDelete $true

Now do another delta sync in the azure AD server

Start-ADSyncSyncCycle -PolicyType Delta

After the cloud user and cloud mailbox are completely removed from the tenant, move the user from your local AD back into the synchronized OU, do a Delta Sync and then wait for the user to appear again in the Office 365 cloud, under Active users. Do not assign a license to the user.

Now move him back to the synced OU

And run the command

Start-ADSyncSyncCycle -PolicyType Delta


On-premises user isn’t receiving emails from online user

 

First we must move the user to un synced OU

The log in the the server which have the Azure AD sync tool

And open the windows azure active directory tool

Now that we have moved the user in a unsynchronized OU and that it’s appearing in the “Deleted users” section, you have to forcefully delete the user so you won’t have to wait for 30 days:

Run the following command

In the azure power shell

Start-ADSyncSyncCycle -PolicyType Delta

Then open the PowerShell and connect to the online exchange

Use the following command

Import-Module MSOnline

$O365Cred = Get-Credential

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Connect-MsolService -Credential $O365Cred

Then run the following to get the object ID

 

 

Get-MsolUser -ReturnDeletedUsers | FL -Property ObjectId,displayname

We must get the user objectID

Remove-MsolUser -ObjectId 080535c0-061a-4b0e-a6fe-48ed7fc9159d -RemoveFromRecycleBin -Force    

 

          Note: make sure you enter the correct ObjectId

 

 

After deleting the user, you will have to make sure his cloud mailbox is also deleted using one of the following cmdlets:

 

Get-Mailbox -Identity “username@domain.com | Remove-Mailbox -PermantentlyDelete $true

Get-Mailbox -SoftDeletedMailbox “ username@domain.com ” | Remove-Mailbox -PermantentlyDelete $true

 

Now do another delta sync in the azure AD server

Start-ADSyncSyncCycle -PolicyType Delta

 

After the cloud user and cloud mailbox are completely removed from the tenant, move the user from your local AD back into the synchronized OU, do a Delta Sync and then wait for the user to appear again in the Office 365 cloud, under Active users. Do not assign a license to the user.

 

Now move him back to the synced OU

And run the command

Start-ADSyncSyncCycle -PolicyType Delta

 

 

 


On-premises user isn’t receiving emails from online user

 

First we must move the user to un synced OU

The log in the the server which have the Azure AD sync tool

And open the windows azure active directory tool

Now that we have moved the user in a unsynchronized OU and that it’s appearing in the “Deleted users” section, you have to forcefully delete the user so you won’t have to wait for 30 days:

Run the following command

In the azure power shell

Start-ADSyncSyncCycle -PolicyType Delta

Then open the PowerShell and connect to the online exchange

Use the following command

Import-Module MSOnline

$O365Cred = Get-Credential

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Connect-MsolService -Credential $O365Cred

Then run the following to get the object ID

 

 

Get-MsolUser -ReturnDeletedUsers | FL -Property ObjectId,displayname

We must get the user objectID

Remove-MsolUser -ObjectId 080535c0-061a-4b0e-a6fe-48ed7fc9159d -RemoveFromRecycleBin -Force    

 

          Note: make sure you enter the correct ObjectId

 

 

After deleting the user, you will have to make sure his cloud mailbox is also deleted using one of the following cmdlets:

 

Get-Mailbox -Identity “username@domain.com | Remove-Mailbox -PermantentlyDelete $true

Get-Mailbox -SoftDeletedMailbox “ username@domain.com ” | Remove-Mailbox -PermantentlyDelete $true

 

Now do another delta sync in the azure AD server

Start-ADSyncSyncCycle -PolicyType Delta

 

After the cloud user and cloud mailbox are completely removed from the tenant, move the user from your local AD back into the synchronized OU, do a Delta Sync and then wait for the user to appear again in the Office 365 cloud, under Active users. Do not assign a license to the user.

 

Now move him back to the synced OU

And run the command

Start-ADSyncSyncCycle -PolicyType Delta

 

 

 


DSNs and NDRs in Exchange 2013

https://technet.microsoft.com/en-us/library/bb232118(v=exchg.150).aspx

Common enhanced status codes

The following table contains a list of the enhanced status codes that are returned in NDRs for the most common message delivery failures.

 
 

Enhanced status code

Description

Possible cause

Additional information

4.3.1

Insufficient system resources

An out-of-memory error occurred. A resource problem, such as a full disk, can cause this problem.

Instead of getting a disk full error, you might be getting an out-of-memory error.

Ensure that your Exchange server has enough disk storage.

4.3.2

System not accepting network messages

This NDR is generated when a queue has been frozen.

You can resolve this condition by unfreezing the queue.

4.4.1

Connection timed out

The destination server is not responding. Transient network conditions can cause this error. The Exchange server tries automatically to connect to the server again and deliver the mail. If delivery fails after multiple attempts, an NDR with a permanent failure code is generated.

Monitor the situation. This might be a transient problem that might correct itself.

4.4.2

Connection dropped

A connection dropped between the servers. Transient network conditions or a server that is experiencing problems can cause this error. The sending server will retry to deliver the message for a specific time period, and then it will generate further status reports.

Monitor the situation as the server retries delivery. This might be a transient problem that might correct itself.

This situation can also occur when the message size limit for the connection is reached, or if the message submission rate for the client IP address has exceeded the configured limit.

4.4.7

Message expired

The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This message can also indicate that a message header limit has been reached on a remote server, or some other protocol time-out occurred while communicating with the remote server.

This message usually indicates an issue on the receiving server. Check the validity of the recipient address, and determine if the receiving server is configured correctly to receive messages.

You might have to reduce the number of recipients in the message header for the host about which you are receiving this error. If you send the message again, it is placed in the queue again. If the receiving server is available, the message is delivered.

5.0.0

HELO / EHLO requires domain address

This situation is a permanent failure. Possible causes include:

  • There is no route for the given address space; for example, an SMTP connector is configured, but this address does not match.
  • DNS returned an authoritative host that was not found for the domain.
  • An SMTP error occurred.

Some potential resolutions include:

  • On one or more SMTP connectors, add an asterisk (*) value as the SMTP address space.
  • Verify that DNS is working.

5.1.0

Sender denied

This NDR is caused by a general failure (bad address failure). An email address or another attribute could not be found in Active Directory Domain Services. Contact entries without the targetAddress attribute set can cause this problem. Another possible cause could be that the homeMDB attribute of a user could not be determined. The homeMDB attribute corresponds to the Exchange server on which the user’s mailbox resides.

Another common cause of this NDR is when you use Microsoft Outlook to save an email message as a file, and then someone opened the message offline and replied to it. The message property only preserves the legacyExchangeDN attribute when Outlook delivers the message, and therefore the lookup could fail.

Either the recipient address is incorrectly formatted, or the recipient could not be correctly resolved. The first step in resolving this error is to check the recipient address, and send the message again.

5.1.1

Bad destination mailbox address

This failure might be caused by the following conditions:

  • The recipient’s email address was entered incorrectly by the sender.
  • No recipient’s exists in the destination email system.
  • The recipient’s mailbox has been moved and the Outlook recipient cache on the sender’s computer has not updated.
  • An invalid legacy domain name (DN) exists for the recipient’s mailbox Active Directory Domain Service.

This error typically occurs when the sender of the message incorrectly enters the email address of the recipient. The sender should check the recipient’s email address and send again. This error can also occur if the recipient email address was correct in the past but has changed or has been removed from the destination email system.

If the sender of the message is in the same Exchange organization as the recipient, and the recipient’s mailbox still exists, determine whether the recipient’s mailbox has been relocated to a new email server. If this is the case, Outlook might not have updated the recipient cache correctly. Instruct the sender to remove the recipient’s address from sender’s Outlook recipient cache and then create a new message. Resending the original message will result in the same failure.

Other issues might cause this error, such as an invalid legacy distinguished name (DN) in Active Directory Domain Services. Examine and correct the former DN of the recipient’s mailbox. Then instruct the sender to remove the recipient’s address from sender’s Outlook recipient cache and then create a new message. Resending the original message will result in the same failure.

5.1.2

Invalid X.400 address

The recipient has a non-SMTP address that can’t be matched to a destination. The address does not appear to be local, and there are no connectors configured with address spaces that contain the recipient’s address.

Verify that the recipient’s address was entered correctly. If the recipient’s address is in a non-SMTP email system that you specifically want to provide mail delivery to, you need to add the appropriate type of connector to your topology and configure it to provide service to the recipient’s email system.

5.1.3

Invalid recipient address

This message indicates that the recipient’s address appears incorrectly on the message.

Either the recipient’s address is formatted incorrectly, or the recipient’s address could not be correctly resolved. The first step in resolving this error is to check the recipient’s address and send the message again.

Also, examine the SMTP recipient policy, and ensure that each mail domain for which you want to accept mail appears correctly.

5.1.4

Destination mailbox address ambiguous

Two or more recipients in the Exchange organization have the same address.

This error typically occurs because of a misconfiguration in Active Directory Domain Services. Possibly because of replication problems, two recipient objects in Active Directory Domain Services have the same SMTP address or Exchange Server (EX) address.

5.1.7

Invalid address

The sender has a malformed or missing SMTP address, the mail attribute in the directory service. The mail item cannot be delivered without a valid mail attribute.

Check the sender directory structure, and determine if the mail attribute exists.

5.2.1

Mailbox cannot be accessed

The mailbox cannot be accessed. The mailbox may be offline, disabled, or the message has been quarantined by a rule.

Check to see if the recipient database is online, the recipient mailbox is disabled, or the message has been quarantined.

5.2.2

Mailbox full

The recipient’s mailbox has exceeded its storage quota and is no longer able to accept new messages.

This error occurs when the recipient’s mailbox has exceeded its storage quota. The recipient must reduce the size of the mailbox or the administrator must increase the storage quota before delivery can be successful.

5.2.3

Message too large

The message is too large, and the local quota is exceeded. For example, a remote Exchange user might have a restriction on the maximum size of an incoming message.

Send the message again without attachments, or set the server or the client-side limit to allow a larger message size limit.

5.2.4

Mailing list expansion problem

The recipient is a misconfigured dynamic distribution list. Either the filter string or the base DN of the dynamic distribution list is invalid.

Set the categorizer event logging level to at least the minimum level, and send another message to the dynamic distribution list. Check the application event log for a 6025 event or a 6026 event detailing which attribute is misconfigured on the dynamic distribution list object.

5.3.3

Unrecognized command

When the Exchange remote server reaches capacity of its disk storage to hold mail, it could respond with this NDR. This error usually occurs when the sending server is sending mail with an ESMTP BDAT command. This error also indicates a possible SMTP protocol error.

Ensure that the remote server has enough storage capacity to hold mail. Check the SMTP log.

5.3.4

Message too big for system

The message exceeds a size limit configured on a transport or mailbox database and can’t be accepted. This failure can be generated by either the sending email system or the recipient email system.

This error occurs when the size of the message that was sent by the sender exceeds the maximum allowed message size when passing through a transport component or mailbox database. The sender must reduce the size of the message for the message to be successfully delivered. For more information about how to configure message size limits, see Message size limits.

5.3.5

System incorrectly configured

A mail-looping situation was detected, which means that the server is configured to loop mail back to itself.

Check the configuration of the server’s connectors for loops, and ensure that each connector is defined by a unique incoming port. If there are multiple virtual servers, ensure that none are set to “All Unassigned.”

5.4.4

Invalid arguments

This NDR occurs if no route exists for message delivery, or if the categorizer could not determine the next-hop destination.

Check that the domain name specified is valid and that a mail exchanger (MX) record exists.

5.4.6

Routing loop detected

A configuration error has caused an email loop. By default, after 20 iterations of an email loop, Exchange interrupts the loop and generates an NDR to the sender of the message.

This error occurs when the delivery of a message generates another message in response. That message then generates a third message, and the process is repeated, creating a loop. To help protect against exhausting system resources, Exchange interrupts the mail loop after 20 iterations. Mail loops are typically created because of a configuration error on the sending mail server, the receiving mail server, or both. Check the sender’s and the recipient’s mailbox rules configuration to determine whether automatic message forwarding is enabled.

5.5.2

Send hello first

A generic SMTP error occurs when SMTP commands are sent out of sequence. For example, a server attempts to send an AUTH (authorization) command before identifying itself with an EHLO command.

It is possible that this error can also occur when the system disk is full.

View the SMTP Log or a Netmon trace, and ensure that there is adequate disk storage and virtual memory available.

5.5.3

Too many recipients

The combined total of recipients on the To, Cc, and Bcc lines of the message exceeds the total number of recipients allowed in a single message.

This error occurs when the sender has included too many recipients on the message. The sender must reduce the number of recipient addresses in the message or the maximum number of recipients must be increased to allow the message to be successfully delivered.

5.5.4

Invalid domain name

The message contains either an invalid sender or an incorrect recipient address format.

One possible cause is that the recipient address format might contain characters that are not conforming to Internet standards.

Check the recipient’s address for nonstandard characters.

5.5.6

Invalid message content

This message indicates a possible protocol error.

Check Event Log for possible failures.

5.7.1

Delivery not authorized

The sender of the message is not allowed to send messages to the recipient.

This error occurs when the sender tries to send a message to a recipient but the sender is not authorized to do this. This frequently occurs when a sender tries to send messages to a distribution group that has been configured to accept messages only from members of that distribution group or other authorized senders. The sender must request permission to send messages to the recipient.

This error can also occur if an Exchange transport rule rejects a message because the message matched conditions that are configured on the transport rule.

5.7.1

Unable to relay

The sending email system is not allowed to send a message to an email system where that email system is not the final destination of the message.

This error occurs when the sending email system tries to send an anonymous message to a receiving email system, and the receiving email system does not accept messages for the domain or domains specified in one or more of the recipients. The following are the most common reasons for this error:

  • A third party tries to use a receiving email system to send spam, and the receiving email system rejects the attempt. By the nature of spam, the sender’s email address might have been forged, and the resulting NDR could have been sent to the unsuspecting sender’s email address. It is difficult to avoid this situation.
  • An MX record for a domain points to a receiving email system where that domain is not accepted. The administrator responsible for the specific domain name must correct the MX record or configure the receiving email system to accept messages sent to that domain, or both.
  • A sending email system or client that should use the receiving email system to relay messages does not have the correct permissions to do this.

5.7.1

Client was not authenticated

The sending email system did not authenticate with the receiving email system. The receiving email system requires authentication before message submission.

This error occurs when the receiving server must be authenticated before message submission, and the sending email system has not authenticated with the receiving email system. The sending email system administrator must configure the sending email system to authenticate with the receiving email system for delivery to be successful. This error can also occur if you try to accept anonymous messages from the Internet on a Mailbox server that has not been configured to do this.

5.7.3

Not Authorized

The sender prohibited reassignment to the alternate recipient.

  


 


Email non-delivery reports in Office 365

Applies To: Office for business

When there’s a problem delivering an email message that you sent, Office 365 sends an email to let you know. The email you receive is a delivery status notification, also known as a bounce message. The most common type is called a non-delivery report (NDR) and they tell you that a message wasn’t delivered. Non-delivery can be caused by something as simple as a typo in an email address. NDRs include a code that indicates why your email wasn’t delivered, solutions to help you get your email delivered, a link to more help on the web, and technical details for administrators. Find out

 More about what’s included in my NDR email.

Find my NDR code and get help delivering my email

The following table contains the NDR codes (also called enhanced status codes) for the most common bounce messages and NDRs that you might encounter in Office 365.

NDR code

Description

Possible cause

Additional information

4.4.7

Message expired

The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This message can also indicate that a message header limit has been reached on a remote server, or some other protocol time-out occurred while communicating with the remote server.

This message usually indicates an issue on the receiving server. Check the validity of the recipient address, and determine if the receiving server is configured correctly to receive messages.

You might have to reduce the number of recipients in the message header for the host about which you are receiving this error. If you send the message again, it is placed in the queue again. If the receiving server is available, the message is delivered.

For more information, see Fix email delivery issues for error code 4.4.7 in Office 365.

4.7.26

Access denied, a message sent over IPv6 [2a01:111:f200:2004::240] must pass either SPF or DKIM validation, this message is not signed

The sending message sent over IPv6 must pass either SPF or DKIM.

For more details, see Support for anonymous inbound email messages over IPv6.

4.7.500-699

Access denied, please try again later

Suspicious activity has been detected on the IP in question, and it has been temporarily restricted while it is being further evaluated.

If this activity is valid, this restriction will be lifted shortly.

4.7.850-899

Access denied, please try again later

Suspicious activity has been detected on the IP in question, and it has been temporarily restricted while it is being further evaluated.

If this activity is valid, this restriction will be lifted shortly.

5.1.0

Sender denied

A common cause of this NDR is when you use Microsoft Outlook to save an email message as a file, and then someone opened the message offline and replied to it. The message property only preserves the legacyExchangeDN attribute when Outlook delivers the message, and therefore the lookup could fail.

Either the recipient address is incorrectly formatted, or the recipient could not be correctly resolved. The first step in resolving this error is to check the recipient address, and send the message again.

For more information, see Fix email delivery issues for error code 5.1.0 in Office 365.

5.1.1

Bad destination mailbox address

This failure might be caused by the following conditions:

  • The recipient’s email address was entered incorrectly by the sender.
  • No recipient’s exists in the destination email system.
  • The recipient’s mailbox has been moved and the Outlook recipient cache on the sender’s computer has not updated.
  • An invalid legacy domain name (DN) exists for the recipient’s mailbox Active Directory Domain Service.

This error typically occurs when the sender of the message incorrectly enters the email address of the recipient. The sender should check the recipient’s email address and send again. This error can also occur if the recipient email address was correct in the past but has changed or has been removed from the destination email system.

If the sender of the message is in the same organization as the recipient, and the recipient’s mailbox still exists, determine whether the recipient’s mailbox has been relocated to a new email server. If this is the case, Outlook might not have updated the recipient cache correctly. Instruct the sender to remove the recipient’s address from sender’s Outlook recipient cache and then create a new message. Resending the original message will result in the same failure.

For more information, see Fix email delivery issues for error code 5.1.1 through 5.1.20 in Office 365.

5.4.1

Relay Access Denied

The mail server that’s generating the error doesn’t accept mail for the recipient’s domain. This error is generally caused by mail server or DNS misconfiguration.

For more information, see Fix email delivery issues for error code 5.4.1 in Office 365.

5.4.6

Routing loop detected

A configuration error has caused an email loop. By default, after 20 iterations of an email loop, Exchange interrupts the loop and generates an NDR to the sender of the message.

This error occurs when the delivery of a message generates another message in response. That message then generates a third message, and the process is repeated, creating a loop. To help protect against exhausting system resources, Exchange interrupts the mail loop after 20 iterations. Mail loops are typically created because of a configuration error on the sending mail server, the receiving mail server, or both. Check the sender’s and the recipient’s mailbox rules configuration to determine whether automatic message forwarding is enabled.

For more information, see Fix email delivery issues for error code 5.4.6 through 5.4.20 in Office 365.

5.6.11

Invalid characters

Your email program added invalid characters (bare line feed characters) into a message you sent.

For more information, see Fix email delivery issues for error code 5.6.11 in Office 365.

5.7.1

Delivery not authorized

The sender of the message is not allowed to send messages to the recipient.

This error occurs when the sender tries to send a message to a recipient but the sender is not authorized to do this. This frequently occurs when a sender tries to send messages to a distribution group that has been configured to accept messages only from members of that distribution group or other authorized senders. The sender must request permission to send messages to the recipient.

This error can also occur if an Exchange transport rule rejects a message because the message matched conditions that are configured on the transport rule.

For more information, see Fix email delivery issues for error code 5.7.1 in Office 365.

5.7.1

Unable to relay

The sending email system is not allowed to send a message to an email system where that email system is not the final destination of the message.

This error occurs when the sending email system tries to send an anonymous message to a receiving email system, and the receiving email system does not accept messages for the domain or domains specified in one or more of the recipients. The following are the most common reasons for this error:

  • A third party tries to use a receiving email system to send spam, and the receiving email system rejects the attempt. By the nature of spam, the sender’s email address might have been forged, and the resulting NDR could have been sent to the unsuspecting sender’s email address. It is difficult to avoid this situation.
  • An MX record for a domain points to a receiving email system where that domain is not accepted. The administrator responsible for the specific domain name must correct the MX record or configure the receiving email system to accept messages sent to that domain, or both.
  • A sending email system or client that should use the receiving email system to relay messages does not have the correct permissions to do this.

For more information, see Fix email delivery issues for error code 5.7.1 in Office 365.

5.7.1

Client was not authenticated

The sending email system did not authenticate with the receiving email system. The receiving email system requires authentication before message submission.

This error occurs when the receiving server must be authenticated before message submission, and the sending email system has not authenticated with the receiving email system. The sending email system administrator must configure the sending email system to authenticate with the receiving email system for delivery to be successful.

For more information, see Fix email delivery issues for error code 5.7.1 in Office 365.

5.7.12

Sender was not authenticated by organization

The sender’s message is rejected because the recipient address is set up to reject messages sent from outside of its organization. Only an email admin for the recipient’s organization can change this.

For more information, see Fix email delivery issues for error code 5.7.12 in Office 365.

5.7.124

Sender not in allowed-senders list

The sender doesn’t have permission to send to the distribution group because the sender is not in the group’s allowed-senders list. Depending how the group is set up, even the group’s owner may need to be added to the allowed sender list in order to send messages to the group.

For more information, see Fix email delivery issues for error code 5.7.124 in Office 365.

5.7.133

Sender not authenticated for group

The recipient address is a group distribution list that is set up to reject messages sent from outside of its organization. Only an email admin for the recipient’s organization or the group owner can change this.

For more information, see Fix email delivery issues for error code 5.7.133 in Office 365.

5.7.134

Sender was not authenticated for mailbox

The recipient address is a mailbox that is set up to reject messages sent from outside of its organization. Only an email admin for the recipient’s organization can change this.

For more information, see Fix email delivery issues for error code 5.7.134 in Office 365.

5.7.13 or 135

Sender was not authenticated for public folder

The recipient address is a public folder that is set up to reject messages sent from outside of its organization. Only an email admin for the recipient’s organization can change this.

For more information, see Fix email delivery issues for error code 5.7.13 or 5.7.135 in Office 365.

5.7.136

Sender was not authenticated

The recipient address is a mail user that is set up to reject messages sent from outside of its organization. Only an email admin for the recipient’s organization can change this.

For more information, see Fix email delivery issues for error code 5.7.136 in Office 365.

5.7.25

Access denied, the sending IPv6 address [2a01:111:f200:2004::240] must have a reverse DNS record

The sending IPv6 address must have a reverse DNS record in order to send email over IPv6.

For more details, see Support for anonymous inbound email messages over IPv6.

5.7.501

Access denied, spam abuse detected

The sending account has been banned due to detected spam activity.

For details, see Fix email delivery issues for error code 451 5.7.500-699 (ASxxx) in Office 365.

Verify that any account issues have been resolved, and reset its credentials. To restore this account’s ability to send mail, contact support through your regular channel.

5.7.502

Access denied, banned sender

The sending account has been banned due to detected spam activity.

Verify that any account issues have been resolved, and reset its credentials. To restore this account’s ability to send mail, please contact support through your regular channel.

5.7.503

Access denied, banned sender

The sending account has been banned due to detected spam activity.

Verify that any account issues have been resolved, and reset its credentials. To restore this account’s ability to send mail, please contact support through your regular channel.

5.7.504

[email@contoso.com]: Recipient address rejected: Access denied

The recipient address that you are attempting to contact is not valid.

Verify the recipient’s email address, and try again.

5.7.505

Access denied, banned recipient

The recipient that you are attempting to contact is not valid.

If you feel this is in error, contact support.

5.7.506

Access Denied, Bad HELO

Your server is attempting to introduce itself (HELO according to RFC 821) as the server it is trying to connect to, rather than its own fully qualified domain name.

This is not allowed, and it is characteristic of typical spambot behavior.

5.7.507

Access denied, rejected by recipient

The IP that you are attempting to send from has been blocked by the recipient’s organization.

Contact the recipient in order to resolve this issue.

5.7.508

Access denied, [$SenderIPAddress] has exceeded permitted limits within $range range

The sender’s IPv6 range has attempted to send too many messages in too short a time period.

Not applicable

5.7.509

Access denied, sending domain [$SenderDomain] does not pass DMARC verification

The sender’s domain in the 5322.From address does not pass DMARC.

Not applicable

5.7.510

Access denied, [contoso.com] does not accept email over IPv6

The sender is attempting to transmit a message to the recipient over IPv6, but the recipient does not accept email messages over IPv6.

Not applicable

5.7.511

Access denied, banned sender

The account you are attempting to send from has been banned.

For more information, see Removing a user, domain, or IP address from a block list after sending spam email.

5.7.512

Access denied, message must be RFC 5322 section 3.6.2 compliant

Message was sent without a valid “From” email address.

Office 365 only. Each message must contain a valid email address in the “From” header field. Proper formatting of this address includes angle brackets around the email address, for example, <security@contoso.com>. Without this address Office 365 will reject the message.

5.7.513

Service unavailable, Client host [$ConnectingIP] blocked by $recipientDomain using Customer Block list (AS16012607)

The recipient domain has added your sending IP address to its custom block list.

The domain that received the email has blocked your sender’s IP address. If you think your IP address has been added to the recipient domain’s custom block list in error, you need to contact them directly and ask them to remove it from the block list.

5.7.606-649

Access denied, banned sending IP [IP1.IP2.IP3.IP4]

The IP that you are attempting to send from has been banned.

Verify that you are following the best practices for email deliverability, and ensure your IPs’ reputations have not been degraded as a result of compromise or malicious traffic. If you believe you are receiving this message in error, you can use the self-service portal to request to be removed from this list. For more information, see Use the delist portal to remove yourself from the Office 365 blocked senders list.

5.7.700-749

Access denied, tenant has exceeded threshold

The majority of traffic from this tenant has been detected as suspicious and has resulted in a ban on sending ability for the tenant.

Ensure that any compromises or open relays have been resolved, and then contact support through your regular channel.


 

Exchange Server Patching


Exchange Server Patching

As we’ve mentioned before, you must patch Exchange 2007 to the very latest Service Pack and Update Rollup before you attempt to do anything with Exchange 2013.

Download and install these patches from here:

  •  

     

     

    Continue

     

     

     

     

    Preparing server for ex2013

    Server prerequisites

    Install the following


    Windows Server 2012 R2 and Windows Server 2012 prerequisites


    Mailbox client access server Roles

    Open PowerShell

    Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

     

    Then restart

    After installing feature

    Install the following

    Unified Communications Managed API 4.0 Runtime

    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx

     

    Edge transport Role

    Install-WindowsFeature ADLDS
    

     

     

    Preparing the domain

    Permissions required:

    Your login id must have following group membership:

             Domain Admins

             Schema Admins

             Enterprise Admins

            Organization management if any (2010/2007) exchange org exist.

     
     

    Open power shell run the following command

    Install-windowsfeature RSAT-ADDS

    First extract the installation files

    Choose directory to extract

     

     

    Prepare the schema

    Then open command Prompt

    Go to the location of the installation file

    setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

    PrepareAD

    setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms /OrganizationName:PGesco

     

    PrepareDomain

    setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms

    Restart

    Check the following before installation

    The replication

    Go to cmd and run the command “repadmin /replsum” and check for error

    If replication is fine we can continue

     

    Installing EX2013Sp1

    Run the setup.exe and you will see the below screen


     



     

    Choose the Roles and un check the automatic roles and feature


    Malware protection


    Readiness check


     

    Installation starts


     

     

     

    Moving mailboxes from 2007 to 2013

    First create database


     

     

        

%d bloggers like this: