Email Connector Troubleshooting - Revision history

Dina at 12:45, 3 February 2023

2023-02-03T12:45:34Z

← Older revision		Revision as of 12:45, 3 February 2023
Line 11:		Line 11:
	*[[Email Connector Troubleshooting#I can't see email attachments on emails that are opened in Outlook Express\|I can't see email attachments on emails that are opened in Outlook Express]]		*[[Email Connector Troubleshooting#I can't see email attachments on emails that are opened in Outlook Express\|I can't see email attachments on emails that are opened in Outlook Express]]
	*[[Email Connector Troubleshooting#HTML format Emails not being processed correctly (Exchange)\|HTML format Emails not being processed correctly (Exchange)]]		*[[Email Connector Troubleshooting#HTML format Emails not being processed correctly (Exchange)\|HTML format Emails not being processed correctly (Exchange)]]
	*[[Email Connector Troubleshooting#HTML format Emails not being processed correctly (~~0ffice~~ 365)\|HTML format Emails not being processed correctly (~~0ffice~~ 365)]]		*[[Email Connector Troubleshooting#HTML format Emails not being processed correctly (Office 365)\|HTML format Emails not being processed correctly (Office 365)]]
	*[[Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]		*[[Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]
	*[[Email Connector Troubleshooting#Email Connector stops sending emails, restarting the service required frequently\|Email Connector stops sending emails, restarting the service required frequently]]		*[[Email Connector Troubleshooting#Email Connector stops sending emails, restarting the service required frequently\|Email Connector stops sending emails, restarting the service required frequently]]
Line 113:		Line 113:
	This will allow you to see the text in the history section and not have to click on “Show Original Message”		This will allow you to see the text in the history section and not have to click on “Show Original Message”

	Connect to ~~0365~~ with Powershell		Connect to O365 with Powershell

	1. $LiveCred = Get-Credential		1. $LiveCred = Get-Credential

	2. Enter your admin login to ~~0365~~		2. Enter your admin login to O365
	(You can copy and paste the following three commands or type them one at a time and press enter)		(You can copy and paste the following three commands or type them one at a time and press enter)

Dina at 08:09, 8 July 2020

2020-07-08T08:09:03Z

Show changes

Dina: Dina moved page Commit Email Connector Troubleshooting to Email Connector Troubleshooting

2020-03-21T19:47:55Z

Dina moved page Commit Email Connector Troubleshooting to Email Connector Troubleshooting

← Older revision	Revision as of 19:47, 21 March 2020
(No difference)

Dina at 19:47, 21 March 2020

2020-03-21T19:47:03Z

Dina: /* HTML format Emails not being processed correctly (0ffice 365) */

2018-04-16T11:13:13Z

HTML format Emails not being processed correctly (0ffice 365)

Dina at 09:01, 4 September 2017

2017-09-04T09:01:45Z

← Older revision		Revision as of 09:01, 4 September 2017
Line 13:		Line 13:
	*[[Commit Email Connector Troubleshooting#HTML format Emails not being processed correctly (0ffice 365)\|HTML format Emails not being processed correctly (0ffice 365)]]		*[[Commit Email Connector Troubleshooting#HTML format Emails not being processed correctly (0ffice 365)\|HTML format Emails not being processed correctly (0ffice 365)]]
	*[[Commit Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]		*[[Commit Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]
			*[[Commit Email Connector Troubleshooting#Email Connector stops sending emails, restarting the service required frequently\|Email Connector stops sending emails, restarting the service required frequently]]


Line 184:		Line 185:


	====='''Email Connector stops sending emails, restarting the service required frequently '''=====		====='''Email Connector stops sending emails, restarting the service required frequently'''=====
	The following errors may pop/be logged:		The following errors may pop/be logged:
	* '''Mail server error 1061''' - this error means the connection between the CommitCRM Server service and mail server (Exchange/Office365) was interrupted. It can be a firewall, a server policy, a mail server policy or an anti-virus kind of setting that wrongly suspected that the CommitCRM Server service process is suspicious. <br>Another possible reason is that the sender was blocked by the mail server or the mail server limits a number of emails that can be sent. Increasing the limits may help.		* '''Mail server error 1061''' - this error means the connection between the CommitCRM Server service and mail server (Exchange/Office365) was interrupted. It can be a firewall, a server policy, a mail server policy or an anti-virus kind of setting that wrongly suspected that the CommitCRM Server service process is suspicious. <br>Another possible reason is that the sender was blocked by the mail server or the mail server limits a number of emails that can be sent. Increasing the limits may help.

Dina: /* Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server */

2017-09-04T09:00:09Z

Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server

@@ Line 182: / Line 182: @@
 * Restart Microsoft Exchange Pop3 service. It may help even though it is running and not reporting any errors.
 * Implement the fix discuss here:    http://blog.jasonsherry.net/2014/08/19/exchange-2013-pop3-service-drops-connections-fix/
 ==See Also==

Dina: /* HTML format Emails not being processed correctly (0ffice 365) */

2017-03-14T10:39:26Z

HTML format Emails not being processed correctly (0ffice 365)

← Older revision		Revision as of 10:39, 14 March 2017
Line 120:		Line 120:

	3. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection		3. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection
	~~Import-PSSession $Session~~

	4. Press Enter		4. Press Enter

	5. List the current mailboxes		5. Import-PSSession $Session

			6. Press Enter

			7. List the current mailboxes
	get-casmailbox your mailbox here \| fl pop		get-casmailbox your mailbox here \| fl pop

Line 137:		Line 140:
	PopForceICalForCalendarRetrievalOption : False		PopForceICalForCalendarRetrievalOption : False

	6. set-casmailbox "your mailbox here - support@yourcompany.com" -PopMessagesRetrievalMimeFormat 2		8. set-casmailbox "your mailbox here - support@yourcompany.com" -PopMessagesRetrievalMimeFormat 2

	7. Now run the command to list the settings to confirm everything worked		9. Now run the command to list the settings to confirm everything worked

	8. get-casmailbox support \| fl pop		10. get-casmailbox support \| fl pop

	ExternalPopSettings :		ExternalPopSettings :

Dina: /* Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server */

2015-10-28T13:15:35Z

Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server

← Older revision		Revision as of 13:15, 28 October 2015
Line 175:		Line 175:

	====='''Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server'''=====		====='''Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server'''=====
	This error means that something interrupted the connection between the CommitCRM Server service and mail server. It can be a firewall, a server policy, a mail server policy or an anti-virus kind of setting that wrongly suspected that the CommitCRM Server service process is suspicious.		This error means that something interrupted the connection between the CommitCRM Server service and mail server. It can be a firewall, a server policy, a mail server policy or an anti-virus kind of setting that wrongly suspected that the CommitCRM Server service process is suspicious.<br>
	'''Solution:		'''Solution:
	* Restart Microsoft Exchange Pop3 service. It may help even though it is running and not reporting any errors.		* Restart Microsoft Exchange Pop3 service. It may help even though it is running and not reporting any errors.
	* Implement the fix discuss here: http://blog.jasonsherry.net/2014/08/19/exchange-2013-pop3-service-drops-connections-fix/		* Implement the fix discuss here: http://blog.jasonsherry.net/2014/08/19/exchange-2013-pop3-service-drops-connections-fix/


	==See Also==		==See Also==

Dina at 13:12, 28 October 2015

2015-10-28T13:12:56Z

← Older revision		Revision as of 13:12, 28 October 2015
Line 12:		Line 12:
	*[[Commit Email Connector Troubleshooting#HTML format Emails not being processed correctly (Exchange)\|HTML format Emails not being processed correctly (Exchange)]]		*[[Commit Email Connector Troubleshooting#HTML format Emails not being processed correctly (Exchange)\|HTML format Emails not being processed correctly (Exchange)]]
	*[[Commit Email Connector Troubleshooting#HTML format Emails not being processed correctly (0ffice 365)\|HTML format Emails not being processed correctly (0ffice 365)]]		*[[Commit Email Connector Troubleshooting#HTML format Emails not being processed correctly (0ffice 365)\|HTML format Emails not being processed correctly (0ffice 365)]]
			*[[Commit Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]


Line 172:		Line 173:

	Set-CASMailbox -Identity "support@YourITcompany.com" -PopUseProtocolDefaults $false		Set-CASMailbox -Identity "support@YourITcompany.com" -PopUseProtocolDefaults $false

			====='''Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server'''=====
			This error means that something interrupted the connection between the CommitCRM Server service and mail server. It can be a firewall, a server policy, a mail server policy or an anti-virus kind of setting that wrongly suspected that the CommitCRM Server service process is suspicious.
			'''Solution:
			* Restart Microsoft Exchange Pop3 service. It may help even though it is running and not reporting any errors.
			* Implement the fix discuss here: http://blog.jasonsherry.net/2014/08/19/exchange-2013-pop3-service-drops-connections-fix/


	==See Also==		==See Also==

← Older revision		Revision as of 19:47, 21 March 2020
Line 1:		Line 1:
	{{Troubleshooting}}		{{Troubleshooting}}
	*[[~~Commit~~ Email Connector Troubleshooting#Checking Email Connector Configuration\|Checking Email Connector Configuration]]		*[[Email Connector Troubleshooting#Checking Email Connector Configuration\|Checking Email Connector Configuration]]
	*[[~~Commit~~ Email Connector Troubleshooting#Emails aren't being pulled from the Incoming Email mailbox (Incoming Emails Troubleshooting)\|Emails aren't being pulled from the Incoming Email mailbox (Incoming Emails Troubleshooting)]]		*[[Email Connector Troubleshooting#Emails aren't being pulled from the Incoming Email mailbox (Incoming Emails Troubleshooting)\|Emails aren't being pulled from the Incoming Email mailbox (Incoming Emails Troubleshooting)]]
	*[[~~Commit~~ Email Connector Troubleshooting#Receiving Error: 501 5.5.4 Invalid domain name when using Exchange Server\|Receiving Error: 501 5.5.4 Invalid domain name when using Exchange Server]]		*[[Email Connector Troubleshooting#Receiving Error: 501 5.5.4 Invalid domain name when using Exchange Server\|Receiving Error: 501 5.5.4 Invalid domain name when using Exchange Server]]
	*[[~~Commit~~ Email Connector Troubleshooting#Responses and forwarding of unrecognized emails doesn't work (Outgoing Emails Troubleshooting)\|Responses and forwarding of unrecognized emails doesn't work (Outgoing Emails Troubleshooting)]]		*[[Email Connector Troubleshooting#Responses and forwarding of unrecognized emails doesn't work (Outgoing Emails Troubleshooting)\|Responses and forwarding of unrecognized emails doesn't work (Outgoing Emails Troubleshooting)]]
	*[[~~Commit~~ Email Connector Troubleshooting#Customer replies aren't being filed under the ticket (Email threading troubleshooting)\|Customer replies aren't being filed under the ticket (Email threading troubleshooting)]]		*[[Email Connector Troubleshooting#Customer replies aren't being filed under the ticket (Email threading troubleshooting)\|Customer replies aren't being filed under the ticket (Email threading troubleshooting)]]
	*[[~~Commit~~ Email Connector Troubleshooting#I BCC/CC the Email Connector, but email is not filed in the ticket, just forwarded to the internal support email address\|I BCC/CC the Email Connector, but email is not filed in the ticket, just forwarded to the internal support email address]]		*[[Email Connector Troubleshooting#I BCC/CC the Email Connector, but email is not filed in the ticket, just forwarded to the internal support email address\|I BCC/CC the Email Connector, but email is not filed in the ticket, just forwarded to the internal support email address]]
	*[[~~Commit~~ Email Connector Troubleshooting#The changes I am making to my settings using the setup program aren't taking effect\|The changes I am making to my settings using the setup program aren't taking effect]]		*[[Email Connector Troubleshooting#The changes I am making to my settings using the setup program aren't taking effect\|The changes I am making to my settings using the setup program aren't taking effect]]
	*[[~~Commit~~ Email Connector Troubleshooting#New Tickets are being created when clients reply to the Email Connector Response\|New Tickets are being created when clients reply to the Email Connector Response]]		*[[Email Connector Troubleshooting#New Tickets are being created when clients reply to the Email Connector Response\|New Tickets are being created when clients reply to the Email Connector Response]]
	*[[~~Commit~~ Email Connector Troubleshooting#Attached emails only open in Outlook Express\|Attached emails only open in Outlook Express]]		*[[Email Connector Troubleshooting#Attached emails only open in Outlook Express\|Attached emails only open in Outlook Express]]
	*[[~~Commit~~ Email Connector Troubleshooting#I can't see email attachments on emails that are opened in Outlook Express\|I can't see email attachments on emails that are opened in Outlook Express]]		*[[Email Connector Troubleshooting#I can't see email attachments on emails that are opened in Outlook Express\|I can't see email attachments on emails that are opened in Outlook Express]]
	*[[~~Commit~~ Email Connector Troubleshooting#HTML format Emails not being processed correctly (Exchange)\|HTML format Emails not being processed correctly (Exchange)]]		*[[Email Connector Troubleshooting#HTML format Emails not being processed correctly (Exchange)\|HTML format Emails not being processed correctly (Exchange)]]
	*[[~~Commit~~ Email Connector Troubleshooting#HTML format Emails not being processed correctly (0ffice 365)\|HTML format Emails not being processed correctly (0ffice 365)]]		*[[Email Connector Troubleshooting#HTML format Emails not being processed correctly (0ffice 365)\|HTML format Emails not being processed correctly (0ffice 365)]]
	*[[~~Commit~~ Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]		*[[Email Connector Troubleshooting#Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server\|Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server]]
	*[[~~Commit~~ Email Connector Troubleshooting#Email Connector stops sending emails, restarting the service required frequently\|Email Connector stops sending emails, restarting the service required frequently]]		*[[Email Connector Troubleshooting#Email Connector stops sending emails, restarting the service required frequently\|Email Connector stops sending emails, restarting the service required frequently]]

← Older revision		Revision as of 11:13, 16 April 2018
Line 106:		Line 106:
	'''Solution:''' If you are having a problem with HTML emails which do not display in the Ticket History, this is an issue caused by a setting in Exchange. Even if the original email sent to it was properly structured (and included both 'text/plain' and 'text/html') the Exchange server strips out the important 'text/plain' which is required by CommitCRM. To fix this simply open the '''POP3 Properties''' in Exchange and on the '''Retrieval Settings''' tab just change from '''Best Body Format''' to '''HTML and alternative text'''.		'''Solution:''' If you are having a problem with HTML emails which do not display in the Ticket History, this is an issue caused by a setting in Exchange. Even if the original email sent to it was properly structured (and included both 'text/plain' and 'text/html') the Exchange server strips out the important 'text/plain' which is required by CommitCRM. To fix this simply open the '''POP3 Properties''' in Exchange and on the '''Retrieval Settings''' tab just change from '''Best Body Format''' to '''HTML and alternative text'''.

	====='''HTML format Emails not being processed correctly (~~0ffice~~ 365)'''=====		====='''HTML format Emails not being processed correctly (Office 365)'''=====
	''Contributed by: Rick Cassel''		''Contributed by: Rick Cassel''

	'''Solution:''' By default, ~~0ffice~~ 365 pop mime retrieval format is set to “BestBodyType”		'''Solution:''' By default, Office 365 pop mime retrieval format is set to “BestBodyType”
	In order for CommitCRM to process the email correctly it needs to be reset to Mime type 2, HtmlAndTextAlternative.		In order for CommitCRM to process the email correctly it needs to be reset to Mime type 2, HtmlAndTextAlternative.
	This will allow you to see the text in the history section and not have to click on “Show Original Message”		This will allow you to see the text in the history section and not have to click on “Show Original Message”
Line 172:		Line 172:

	'''Additional configuration''':		'''Additional configuration''':
	''Contributed by: @brainstormcomp''		1. ''Contributed by: @brainstormcomp''

	In cases where the above does not help proceed with attempting to run the following command (in addition to the above):		In cases where the above does not help proceed with attempting to run the following command (in addition to the above):

	Set-CASMailbox -Identity "support@YourITcompany.com" -PopUseProtocolDefaults $false		'''''Set-CASMailbox -Identity "support@YourITcompany.com" -PopUseProtocolDefaults $false'''''

			2. In case employee replies are sent in TNEF format run the following command:

			'''''Set-RemoteDomain Default -TNEFEnabled $false'''''

	====='''Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server'''=====		====='''Receiving Error: WinSock error 10004 Interrupted system call when using Exchange Server'''=====