Hey guys, as of 03/03/2014 my respond to Kace emails to update tickets worked great!  Between then and now something changed and I need help finding what.  Our KACE was always sending mail via DNS so there were never any contacts set up in our active directory or mail server, definately not with the address or @OURKACE.OURCOMPANY.COM so it HAD to be setup DNS (as I did not set it up).

I did not make any changes to the SMTP settings but did notice that after the heartbleed patch, in the GENERAL SETTINGS tab the USER EMAIL SUFFIX had been re-defaulted back to kace.com. I never took notice what this was before, so I reset it to our-email-suffix.com (which differs from our DNS suffix and the kace.domain.com suffix, i know, stick with me here).

In between then and now, however, our exchange 2003 did have some failures and we have STARTED transition over to exchange 2010, so the company is split down the middle on which exchange they are hosted on.  Now then, when I send an email to my kace to respond to a ticket (which worked to update tickets) i get a kick back with an error:


Generating server: OUR2010SERVER.DOMAIN.com



#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##

Even if I try to reply to KACE using a user / mailbox on 2003 exchange, I still get THAT kickback from our exchange 2010 server.  WHAT DOES THIS MEAN?  I do NOT want to have to create a user contact and contact smtp (2 accounts/contacts) for every queue as we have more than a dozen. 

Is there a setting in exchange 2010 that can ALLOW the domain?  Why is my exchange 2010 cutting off emails sent TO kace but we can receive them perfectly fine?

Anyways:  Please, any help is appreciated as I am supposed to present this device to other IT members in the next couple days and now one major piece, updating per email, is broken.


0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time


Answer this question or Comment on this question for clarity