We've had a K1000 for a short period of time, and have been working on configuring a queue in the service desk.  We use Microsoft's Office 365 cloud email, so we created a mailbox for the queue to read from, and connected it.  The queue reads email that comes in and creates a ticket, and email is sent out, both from the queue and from the system with no problems.

Where there is a problem, is that two days later, whoever sent the email to create a ticket gets an undeliverable message from Office 365, even though the email was received and the ticket created.

What makes this stranger, is that the mailbox (alternate email) that we send to is testhelp@ourdomain.com, but the in the undeliverable, it says delivery failed to testhelp@k1000.ourdomain.com (the built in queue email).

I opened a ticket with Dell, and after looking at our configuration, the undeliverable message, and checking the logs, they determined that this isn't coming from the K1000 at all.  I understand that the undeliverable is coming from Office 365, but what has me stumped is why it's referencing the built in queue email at all.

Here is the undeliverable error:

7/30/2015 1:31:36 PM - Remote Server at na01-internal.map.protection.outlook.com ( returned '550 4.4.7 QUEUE.Expired; message expired'
7/30/2015 1:23:54 PM - Remote Server at na01-internal.map.protection.outlook.com ( returned '441 4.4.1 Error encountered while communicating with primary target IP address: "451 4.4.0 Socket error ConnectionReset." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was :1101'

Actually, in typing this out, I just realized that last part is strange:  The last endpoint attempted was :1101'  

What is port 1101 for?
Has anyone seen this before, with or without Office 365?
Why is the queue's built in email address being referenced at all, and what's referencing it, if the email is being sent to the alternate email address?

Thanks in advance for any advice that might be given!
Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Answer Chosen by the Author


We resolved the issue over the weekend.  The problem was that the built in address was@k1000.ourdomain.com, and our email in Office 365 has the domain@ourdomain.com, but there is no such thing as the domain k1000.ourdomain.com.  We changed the domain on the K1000 toanotherdomain.org, another domain we own, but does not have an entry in Office 365,and added a DNS entry for @k1000.anotherdomain.org.  Since then, we have gotten nobouncebacks.  

Answered 08/03/2015 by: ondrar
Orange Belt

Please log in to comment


Answer this question or Comment on this question for clarity