/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


k1000 7.0 SMTP Settings

12/20/2016 3451 views
We upgraded to K1000 7.0 over the weekend and now our SMTP settings apparently no longer work. E-mails will not send from the box. I've double checked the connector, verified the username/password was being taken successfully, but for some reason the box can no longer send e-mails. Has anyone else experienced this issue?
Answer Summary:
2 Comments   [ + ] Show comments

Comments

  • We are having the same problem! Did you get this resolved? And if so how?
  • Hey abratton,

    I put our resolution in this thread back on 12/28. We just removed the passwords for all SMTP configurations If you allow anonymous sending on exchange, this should be a workaround for now.

Answer Chosen by the Author

0
The way to resolve this for now is to remove all passwords from SMTP settings in both the queues and the network settings. Since we had Exchange set to allow anonymous having a password breaks SMTP as of 7.0. This wasn't the case in previous versions.
Answered 12/28/2016 by: ct253704
White Belt

All Answers

2
Did not see the issue before but what does the diagnostics say?
Go to Settings | Support | Run Diagnostic Utilities and send an email to yourself. This provides you a detailed log regarding the sending process.
If you need help to analyze this, feel free to post it here or contact support (support will ask you to run an additional patch to collect additional logs too)
Answered 12/20/2016 by: Nico_K
Red Belt

  • Hey Nico,

    No matter what configuration for SMTP I use I get the same errors (Below). The internal SMTP has stopped functioning in our environment as well. We've used our SMTP with K1000 for years, not sure what 7.0 could have changed. I've been on 3 calls with support too and they can't seem to figure it out either.

    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN PANIC
    Rewrite of administrator@support.ourdomain.org yielded unqualified address "maincampusadministrator"
    LOG: MAIN PANIC
    Rewrite of administrator@support.ourdomain.org yielded unqualified address "maincampusadministrator"
    LOG: MAIN
    <= administrator@support.ourdomain.org U=www P=local S=581
    delivering 1cK3SX-000KRV-Up
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= helpdesk@ourdomain.org U=www P=local S=483
    delivering 1cK3SY-000KRb-1P
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= facilities@ourdomain.org U=www P=local S=502
    delivering 1cK3SY-000KRh-43
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= echosupport@ourdomain.org U=www P=local S=490
    delivering 1cK3SY-000KRn-6c
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= hr@ourdomain.org U=www P=local S=462
    delivering 1cK3SY-000KRt-98
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= nutritionservices@ourdomain.org U=www P=local S=508
    delivering 1cK3SY-000KRz-Bd
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= payrollkbox@ourdomain.org U=www P=local S=485
    delivering 1cK3SY-000KS5-EF
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= training@ourdomain.org U=www P=local S=480
    delivering 1cK3SY-000KSB-Gm
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    LOG: MAIN
    Warning: purging the environment.
    Suggested action: use keep_environment.
    LOG: MAIN
    <= communications@ourdomain.org U=www P=local S=498
    delivering 1cK3SY-000KSH-Jf
    LOG: retry_defer MAIN
    == cthomas@ourdomain.org R=smart_route T=transport_25 defer (-53): retry time not reached for any host
    • bump... Same issues here...
      • Hey DirtySoc,

        we had those issues for about 3 weeks and the support suggested to upgrade to 7.1 after that the same errors occured.
        I've removed all SMTP settings from the queues. Only in the network settings we've provided the IP-Address and the port for SMTP Settings. Now the errors are gone.
      • We had to remove SMTP username/password and do all of that. Has been working until today and it just magically stopped working again. Seriously worst upgrade ever going to 7.x. We've been back and forth with support and they claim "e-mail had a bug in every single previous version....but they fixed the bug"....well, if you fixed the bug then why is everyone breaking?

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ