Labels

3300 (1) 3PAR (1) Active Directory (1) ADFS (1) Admin Share (1) Auto-Sync (2) Auto-Sync locked (1) AWS (3) AzCopy (1) Azure (3) Backups (2) Broadcom (1) Call Forwarding (1) CLI (2) cmd (1) Compatibility View (1) Dameware MRC (1) Databases (1) DFS (1) DNS (1) Domain Admin (1) domain controller (1) Enterprise Mode (1) ESXi 5.0 (1) ESXi 5.1 (5) ESXi 5.5 (3) Exchange (3) Exchange 2010 (5) Extreme (1) ExtremeXOS (1) Federation (1) File Share (1) FSMO (1) GPO (1) Group Policy (1) Group Policy Client (1) Hardware Acceleration (1) Helpdesk (1) HP-UX (1) Hyper-V (2) IAM (1) IE10 (1) IE11 (1) IP conflict (1) Kayako (3) LDAP (1) Licence (1) Links (9) local groups (1) LUN lock (1) LUN number (1) MAC address (1) Microsoft Teams (1) Mitel (1) Namespaces (1) Networking (6) Nexenta (6) NMC (1) Office 365 (4) OneDrive (1) Outlook 2003 (1) Outlook 2013 (1) PC (1) Physical (1) PowerCLI (10) Powershell (10) promoted links (2) Public Folders (1) RDP (1) RDS (1) Recovery Services (1) RedShift (1) Registry (3) Reports (1) Resolve (2) Restart (1) RSA (1) Run As (1) SAML (1) SAN (1) Scavenging (1) script (10) Server 2003 (3) Server 2008 R2 (1) Server 2012 R2 (2) Servers (2) sharepoint 2013 (3) SMTP (3) Snapshot (2) SRM (1) SSH (5) SSL Certificate (2) Temporary profile (1) Terminal Server (3) Troubleshooting (5) Ubuntu (1) Update Manager (1) Useful Apps (1) VAAI (1) vCenter Server Appliance (1) VDI (1) VDP (1) Veeam Backup and Replication (2) VM (1) VM Error (1) vmdk (1) VMFS (1) vMotion (2) VMware (20) VoiP (1) vSphere 5.5 (4) vSphere 6.0 (2) vSphere 6.5 (1) vUM (1) webpart (1) Windows (3) Windows 10 (1) Windows 7 (2)

Monday, 7 July 2014

Exchange 2010 / Kayako Case - Error 500 5.3.3 Unrecognized Command

We encountered an issue this morning where our Kayako Case (formally known as Kayako Resolve) was repeatedly logging a ticket from it's email queue as the email was not being deleted. When manually running the email parser cron job I was seeing the following error;
  1. Running parser for Queue ID '7': mail@domain.com Uncaught Exception Router: http://helpdesk.domain.com/cron/index.php?/Parser/ParserMinute/POP3IMAP Expected response code 220 but got code "500", with message "500 5.3.3 Unrecognized command " in ./__swift/thirdparty/SwiftMailer/classes/SwiftMailer/Transport/AbstractSmtpTransport.php:386

After speaking with Kayako support it was determined that the problem lay with our Exchange 2010 server.

On checking the error logs on Exchange I found an Application Error event 12014, under Task Category TransportService;
Microsoft Exchange could not find a certificate that contains the domain name name.domain.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector CONNECTOR-NAME with a FQDN parameter of name.domain.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

As we recently had to change our email SSL certificate, I checked the Receive Connectors named in the errors and found that the FQDN provided in response to EHLO or HELO did not match the name on the new SSL certificate.

After updating this connector, email began to flow in and out of our helpdesk again.

No comments:

Post a comment