SBS POP3 connector error: invalid header fields

If you are using the POP3 Connector on Windows SBS 2008, you may encounter this error in the event log:

One or more (5) e-mail messages in the POP3 mailbox account ‘’ on the POP3 server ‘’ have invalid header fields. Because of this, the messages cannot be delivered to the Exchange Server mailbox ‘’ in Windows Small Business Server. The messages are still on the POP3 server. To resolve this issue, connect to the POP3 mailbox account, and then manually retrieve or delete the messages.

By default the POP3 connector will stop processing new messages after 5 protocol errors so once this happens, you will not receive any email.

Increase the MaxProtocolErrors from 5 to something bigger:

Set-ReceiveConnector -identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -MaxProtocolErrors 300

Next step: remaining messages to be downloaded, but the messages with invalid headers will still not be downloaded.
To fix this:

Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain

Exchange 2010 unable to access EMC or EMS

Error:
Exchange 2010 Management Console

Initialization failed.

The following error occurred while attempting to connect to the specified Exhange Server ‘name of the server’

The attempt to connect to server using ‘kerberos’ authentication failed:Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has exceeded. Send future requests at a slower rate or raise the system quota. The next request from this user will not be approved for atleast 324122176 milliseconds. for more information, see the about_remote_troubleshooting Help topic.

Solution:
try restart IIS (or IISReset command)

Logging SMTP Protocol Activity in Exchange 2007 / 2010

Enable protocol logging on a Receive Connector

Set-ReceiveConnector “Connector Name” -ProtocolLoggingLevel verbose

Receive Connector logs default path:

  • Exchange 2010: \Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive
  • Exchange 2007: \Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive

To change:

Set-TransportServer “TRANSPORT SERVER NAME” -ReceiveProtocolLogPath “C:\Directory”

Enable protocol logging on a Send Connector

Set-SendConnector “Send Connector Name” -ProtocolLoggingLevel verbose

Send Connector logs default path:

  • Exchange 2010: \Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend
  • Exchange 2007: \Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend

To change:

 Set-TransportServer “TRANSPORT SERVER NAME” -SendProtocolLogPath “C:\Directory”

Mail acceptance failure, BDAT command

The BDAT ESMTP command verb is an alternative to the DATA command. When an SMTP virtual server responds to the EHLO keyword with CHUNKING, the SMTP server indicates that it supports the BDAT command and will accept messages in chunks.

To resolve this error, check the messaging environment for issues or configurations that might be blocking the BDAT command verb such as:

  • Transient network outages
  • SMTP proxies
  • Firewalls
  • Applications

Exchange 2010: Unable to open Exchange Management Console – Initialization Failed

Message:
The attempt to connect to http://exchange.contoso.com’/powershell using ‘Kerberosauthentication failed: Connecting to the remote server failed with the following error message : WinRM cannot process the request…

#1
Close EMC. Open regedit and delete ‘NodeStructureSetting’  from registry: HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools.

#2
Make sure that the Kerbauth module (C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll) is not enabled on the default website but is, instead, enabled only for the PowerShell virtual directory.
AND
Make sure that the WSMan module (C:\Windows\system32\wsmsvc.dll) is registered but not enabled at the Server level.

TMG 2010 SP1 and Exchange 2010 SP1: TMG Managed Control service hangs (event id 31306 and 31309)

  • Run the Remove-EdgeSubscription Cmdlet in an administrative Exchange Powershell console
  • Manually remove any receive connectors in the Exchange Management Console
  • Removing all configuration settings in the E-mail policy group
  • Restarting the TMG Managed Control Service
  • Reconfiguring the E-mail policy

Exchange max e-mail size settings

1. Organization Configuration:

Organization Configuration | Hub Transport | Global Settings tab | Transport Settings

2. Server Configuration:

Server Configuration | Hub Transport | select a HT server | Receive Connectors -> select a connector | Properties

3. Send Connector Configuration

Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties

4. Recipients Configuration:

Recipients Configuration | Mailbox | select mailbox | properties | Mail Flow Settings | Message Size Restrictions

5. Recipients Group Configuration:

Recipients Configuration |Distribution Group | select Group | properties | Mail Flow Settings | Message Size Restrictions

6. Global Setting in ADSIEdit:

Configuration container | Services | Microsoft Exchange |YourOrgName| Global Settings | Message Delivery | Properties

7. Transport Rules:

Organization Configuration | Hub Transport | Transport Rules

 

Exchange 2010 DAG: Manually disable database activation

Blocks the copy of the database DATABASE on the server SERVER for activation:

Suspend-MailboxDatabaseCopy -Identity DATABASE\SERVER -ActivationOnly

Resumes:

Resume-MailboxDatabaseCopy -Identity DATABASE\SERVER

Update:
Another option is to block ALL databases hosted on a server from activating:

Set-MailboxServer –identity SERVER –DatabaseCopyAutoActivationPolicy Blocked

Resumes:

Set-MailboxServer –identity SERVER –DatabaseCopyAutoActivationPolicy Unrestricted