I recently started receiving this error after things likely changed on the back end due to company restructuring. Has anyone received this error and been able to explain what might fix it, to the Exchange Admin people?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+10- Safer
- 217 replies
Hi @marksedgwick,
There are two things that I can see that may be causing this issue 1) Do you have a version of FME Server pre-2015. StartTLS configuration was added then. 2) Do you have a SSL set up and are you using a self signed certificate? Self signed certificates can cause issues with the Exchange service. In later versions of FME you can turn off the SSL for your specific IMAP Service in your Publication settings.
Hi @marksedgwick,
There are two things that I can see that may be causing this issue 1) Do you have a version of FME Server pre-2015. StartTLS configuration was added then. 2) Do you have a SSL set up and are you using a self signed certificate? Self signed certificates can cause issues with the Exchange service. In later versions of FME you can turn off the SSL for your specific IMAP Service in your Publication settings.
I have 2 servers that are currently both not working with the same error.
The current PROD is FME 2016.1.1 was working, but stopped. The settings are:
Protocol: Email (IMAP)
IMAP Server Host: gtnapezwex001.gtna.gt.ds
IMAP Server Port: 143
IMAP Email Account: gisnow
Connection Security: StartTLS
Verify SSL Certificate: No
The current DEV is FME 2017.1.2 with the same settings and getting the same error.
+2I have 2 servers that are currently both not working with the same error.
The current PROD is FME 2016.1.1 was working, but stopped. The settings are:
Protocol: Email (IMAP)
IMAP Server Host: gtnapezwex001.gtna.gt.ds
IMAP Server Port: 143
IMAP Email Account: gisnow
Connection Security: StartTLS
Verify SSL Certificate: No
The current DEV is FME 2017.1.2 with the same settings and getting the same error.
I know that we use google, so with 2 factor authentication it doesn't work, and I have to open up all the settings to allow things to use my email account, which your exchange admin people may have restricted.
Can you get it working with a personal account?
Have you asked your exchange admin people if the settings on your account are ok to use on FME Server?
I know that we use google, so with 2 factor authentication it doesn't work, and I have to open up all the settings to allow things to use my email account, which your exchange admin people may have restricted.
Can you get it working with a personal account?
+2Hi @marksedgwick
I spoke to our development today who confirmed that this message is coming from your email server.
I would ensure that you have all of the correct settings from them to work on getting FME Server the correct connection details.
Hi @marksedgwick
I spoke to our development today who confirmed that this message is coming from your email server.
I would ensure that you have all of the correct settings from them to work on getting FME Server the correct connection details.
Attached is the settings for Exchange given to me by Admin
RunspaceId : 4c925a22-d3d9-4005-87a6-38261e85437b
AuthMechanism : ExternalAuthoritative
Banner :
BinaryMimeEnabled : True
Bindings : {10.33.195.241:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
SmtpUtf8Enabled : False
BareLinefeedRejectionEnabled : False
DomainSecureEnabled : False
EnhancedStatusCodesEnabled : True
LongAddressesEnabled : False
OrarEnabled : False
SuppressXAnonymousTls : False
ProxyEnabled : False
AdvertiseClientSettings : False
Fqdn : GTNAPEZWEX001.gtna.gt.ds
ServiceDiscoveryFqdn :
TlsCertificateName :
Comment :
Enabled : True
ConnectionTimeout : 00:10:00
ConnectionInactivityTimeout : 00:05:00
MessageRateLimit : Unlimited
MessageRateSource : IPAddress
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize : 128 KB (131,072 bytes)
MaxHopCount : 60
MaxLocalHopCount : 5
MaxLogonFailures : 3
MaxMessageSize : 35 MB (36,700,160 bytes)
MaxProtocolErrors : 5
MaxRecipientsPerMessage : 500
PermissionGroups : ExchangeServers
PipeliningEnabled : True
ProtocolLoggingLevel : None
RequireEHLODomain : False
RequireTLS : False
EnableAuthGSSAPI : False
ExtendedProtectionPolicy : None
LiveCredentialEnabled : False
TlsDomainCapabilities : {}
Server : GTNAPEZWEX001
TransportRole : FrontendTransport
SizeEnabled : Enabled
TarpitInterval : 00:00:05
MaxAcknowledgementDelay : 00:00:30
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Secured Connector ? Enbridge
DistinguishedName : CN=Secured Connector ? Enbridge,CN=SMTP Receive
Connectors,CN=Protocols,CN=GTNAPEZWEX001,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=GTNA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=gt,DC=ds
Identity : GTNAPEZWEX001\\Secured Connector ? Enbridge
Guid : 5f0d4749-46f6-4c31-a8d0-08903b15455a
ObjectCategory : gt.ds/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass : {top, msExchSmtpReceiveConnector}
WhenChanged : 1/15/2018 11:10:53 AM
WhenCreated : 2/23/2017 11:22:24 AM
WhenChangedUTC : 1/15/2018 5:10:53 PM
WhenCreatedUTC : 2/23/2017 5:22:24 PM
OrganizationId :
Id : GTNAPEZWEX001\\Secured Connector ? Enbridge
OriginatingServer : pezwgtnadc002.gtna.gt.ds
IsValid : True
ObjectState : Unchanged