Skip to main content
Solved

Email received for unknown recipient, so dropped

  • November 7, 2018
  • 2 replies
  • 31 views

fmelizard
Safer
Forum|alt.badge.img+21

I've configured the SMTP Publisher to receive emails, but when I send them to FME Server I get undelivered responses.

 

I looked at the email.log for the FME Server Publishers and I see:

 

"WARN Email received for unknown recipient [email address], so dropped

 

 

What does this mean?

Best answer by jlutherthomas

It looks like FME Server is receiving the email, but doesn't know what to do with it.

 

 

If you've set up an email publication (SMTP) on FME Server to receive emails to and you try sending an email to there's a chance FME Server will still get that email, but because it hasn't been configured to receive emails at that address it will drop them (what you're seeing in the email.log file), and you will get an undelivered response.

 

 

The best thing to do would be to double check your email smtp publications that they are configured correctly.
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.

2 replies

Forum|alt.badge.img+2
  • Best Answer
  • November 7, 2018

It looks like FME Server is receiving the email, but doesn't know what to do with it.

 

 

If you've set up an email publication (SMTP) on FME Server to receive emails to and you try sending an email to there's a chance FME Server will still get that email, but because it hasn't been configured to receive emails at that address it will drop them (what you're seeing in the email.log file), and you will get an undelivered response.

 

 

The best thing to do would be to double check your email smtp publications that they are configured correctly.

siennaatsafe
Safer
Forum|alt.badge.img+12

I had a user with a similar issue but the publication existed. They found that deleting and then adding the publication again fixed the issue. I'm not sure why this is but it's worth a try.