Closed meelik closed 10 years ago
markleusink
commented
10 years ago The contacts in the demo data you're working with have a @zetacomm.com address. That domain is fictional. That's why you get the mail delivery errors. This wouldn't happen with actual email addresses.
KristiKaljurand
commented
10 years ago Comment from Mark Leusink: The contacts in the demo data you're working with have a @zetacomm.com address. That domain is fictional. That's why you get the mail delivery errors. This wouldn't happen with actual email addresses.
Closed by Continuity
KristiKaljurand
commented
10 years ago Works as designed
Environment:
Steps to reproduce:
Expected result:
Actual result: I received 16 emails "DELIVERY FAILURE: No route found to domain zetacomm.com from server DEMO/LINQED. Check DNS configuration." on my inbox "max.kolesnikov1@gmail.com". See mail:
DELIVERY FAILURE: No route found to domain zetacomm.com from server DEMO/LINQED. Check DNS configuration.
Your message
Subject: [continuity] Incident created
was not delivered to:
adam.callahan@zetacomm.com
because:
No route found to domain zetacomm.com from server DEMO/LINQED. Check DNS configuration.
Final-Recipient: rfc822;adam.callahan@zetacomm.com Action: failed Status: 5.1.2 Diagnostic-Code: X-Notes; No route found to domain zetacomm.com from s erver DEMO/LINQED. Check DNS configuration.
---------- Пересылаемое сообщение ---------- From: max.kolesnikov1@gmail.com To: adam.callahan@zetacomm.com Cc: Date: Thu, 29 May 2014 16:22:59 +0200 Subject: [continuity] Incident created
Max Kolesnikov has just created an incident in Continuity:
Incident: Test description