Skip to main content
Question

FME Email account delivery failed

  • April 25, 2017
  • 5 replies
  • 27 views
C

Hi folks, 

We are using FME Server 2017. I have setup a topic to receive Email, which tested successfully with notification. I also created a publication using above topic with protocol (Email SMTP). However, when I try to send email to this publication from outlook I received delivery fail message. IT has confirmed the port 25 is open.

Delivery has
failed to these recipients or distribution lists:

 


A problem occurred during the delivery of this message. Microsoft Exchange will
not try to redeliver this message for you. Please try resending this message
later, or provide the following diagnostic text to your system administrator.

 


 


 


 


Diagnostic information for administrators:

Generating
server: mx12.rta.nsw.gov.au

 


#< #5.4.6 smtp; 554 5.4.6 Hop count exceeded - possible mail loop> #SMTP#

Original
message headers:

Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx12.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 E8.8B.24659.CF5D5F85; Tue, 18 Apr 2017 19:01:48 +1000 (EST)
Received: from mx11.rta.nsw.gov.au (163.189.24.68) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:46:48 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx11.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 B9.8C.13130.772D5F85; Tue, 18 Apr 2017 18:46:47 +1000 (EST)
Received: from mx11.rta.nsw.gov.au (163.189.24.68) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:31:47 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx11.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 7C.6C.13130.2FEC5F85; Tue, 18 Apr 2017 18:31:47 +1000 (EST)
Received: from mx12.rta.nsw.gov.au (163.189.24.70) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:16:46 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx12.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 07.3B.24659.E6BC5F85; Tue, 18 Apr 2017 18:16:46 +1000 (EST)
Received: from mx12.rta.nsw.gov.au (163.189.24.70) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:01:46 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx12.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 EC.1B.24659.9E7C5F85; Tue, 18 Apr 2017 18:01:45 +1000 (EST)
Received: from mx12.rta.nsw.gov.au (163.189.24.70) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:01:10 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx12.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 5B.1B.24659.6C7C5F85; Tue, 18 Apr 2017 18:01:10 +1000 (EST)
Received: from mx12.rta.nsw.gov.au (163.189.24.70) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:00:37 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx12.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 5A.1B.24659.4A7C5F85; Tue, 18 Apr 2017 18:00:36 +1000 (EST)
Received: from mx11.rta.nsw.gov.au (163.189.24.68) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:00:36 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx11.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 43.3C.13130.4A7C5F85; Tue, 18 Apr 2017 18:00:36 +1000 (EST)
Received: from mx12.rta.nsw.gov.au (163.189.24.70) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:00:36 +1000
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx12.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 3A.1B.24659.3A7C5F85; Tue, 18 Apr 2017 18:00:35 +1000 (EST)
Received: from mx11.rta.nsw.gov.au (163.189.24.68) by
 corex701.corp.rta.nsw.gov.au (163.189.3.55) with Microsoft SMTP Server id
 8.3.485.1; Tue, 18 Apr 2017 18:00:35 +1000
X-AuditID: a3bd1846-f79e56d000006053-8e-58f5d5fcb3b2
Received: from corex701.corp.rta.nsw.gov.au ( [163.189.3.55])  by
 mx11.rta.nsw.gov.au (Symantec Mail Security) with SMTP id
 03.3C.13130.3A7C5F85; Tue, 18 Apr 2017 18:00:35 +1000 (EST)
Received: from COREXC01.corp.rta.nsw.gov.au ([163.189.3.51]) by
 corex701.corp.rta.nsw.gov.au ([163.189.3.55]) with mapi; Tue, 18 Apr 2017


 18:00:35 +1000

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.

5 replies

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • 671 replies
  • July 4, 2017

Hi @choilon, does your hostname and domain resolve to a publicly accessible IP or DNS? I tried to ping "" but the operation could not resolve the hostname.

This is a key requirement for being able to send email directly to FME Server.

(There may also be firewalls blocking communication – particularly Port 25 for Windows, or 7125 for Linux.)

mygis
Supporter
Forum|alt.badge.img+14
  • mygisSupporter
  • Supporter
  • 307 replies
  • July 5, 2017

Hi @choilon,

1. Just a comment really ... some providers block port 25 as it is a port used by spammers. The internet providers would ask to use port 587 for SMTP instead. Could you check with the internet providers?

2. I have been suing POP3 to receive my emails then SMTP please check with the email admin if you need any kind of authentication before using SMTP as well.

 

 

Cheers.

Lyes

aguan
Supporter
Forum|alt.badge.img+11
  • aguanSupporter
  • Supporter
  • 140 replies
  • July 12, 2017

Has this been resolved? Rylan, I don't understand why it has to be a publicly accessible IP. I have a similar issue, except the outlook does not give any error when sending an email to FME server ( e.g., admin@phoupgisapw108.americas.ent.bhpbilliton.net). But I don't see any message in FME server notification monitoring for this email topic. We do not have a public IP for phoupgisapw108.americas.ent.bhpbilliton.net. It is on the company intranet.

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • 671 replies
  • July 14, 2017

Has this been resolved? Rylan, I don't understand why it has to be a publicly accessible IP. I have a similar issue, except the outlook does not give any error when sending an email to FME server ( e.g., admin@phoupgisapw108.americas.ent.bhpbilliton.net). But I don't see any message in FME server notification monitoring for this email topic. We do not have a public IP for phoupgisapw108.americas.ent.bhpbilliton.net. It is on the company intranet.

That's a great point, @ag, and thank you for commenting! If everything is on the same intranet we would not expect there to be an issue.

 

I'm not sure if @choilon has resolved this problem – I haven't seen anything come in for the Support Team to date.
C

Has this been resolved? Rylan, I don't understand why it has to be a publicly accessible IP. I have a similar issue, except the outlook does not give any error when sending an email to FME server ( e.g., admin@phoupgisapw108.americas.ent.bhpbilliton.net). But I don't see any message in FME server notification monitoring for this email topic. We do not have a public IP for phoupgisapw108.americas.ent.bhpbilliton.net. It is on the company intranet.

we have a similar but different problem. emails directed at our fme server email address sometimes get through, other times an undelivered message is returned.

 

 

(Unable to deliver message. No such domain.)

 

 

 

Community Stats

32,058
Posts
121,723
Replies
39,686
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.