DX Infrastructure Manager

Expand all | Collapse all

SMTP mail server issue in Emailgtw Probe

  • 1.  SMTP mail server issue in Emailgtw Probe

    Posted 01-17-2018 11:14 PM

    Dear Team,

    We have configure the SMTP server in Emailgtw probe to get email alerts but we are not able to get nay alerts mals.

     

    As we cheked the connection of SMTP is successful there in test section but we have not provided the credential of SMTP, this is because that my mail server has told that you dont require any auth. to send any email. You can ignore this, it should work without auth. But it is not working, as in same server i checked with cmd prompt, from there i am able to send mail from smtp by telneting.

     

     

    Also want to know, how can we use SMTP server without auth. in emailgtw probe

    mentioning the error that getting in emaillogs...

     

    Jan 17 11:07:46:463 emailgtw: ACCEPT: 0000000000BD8E40 0000000000BDA300(1232) 100.64.3.100/48026<-100.64.3.100/52552
    Jan 17 11:07:46:463 emailgtw: NEW CONNECTION 0000000000BDA300, added to session leader
    Jan 17 11:07:46:463 emailgtw: nimSessionWait: 2 sessions, 1000 ms timeout, 1 rounds
    Jan 17 11:07:46:464 emailgtw: 100.64.3.100/48026<-100.64.3.100/52552 (446):
    Jan 17 11:07:46:464 emailgtw: got MSG on session 0000000000BDA300
    Jan 17 11:07:46:464 emailgtw: RREQUEST: test_smtp_login <-100.64.3.100/52552 h=352 d=75
    Jan 17 11:07:46:464 emailgtw: DISPATCHING test_smtp_login, user-data (75 bytes)
    Jan 17 11:07:46:464 emailgtw: test_smtp_login from 100.64.3.100/52552
    Jan 17 11:07:46:464 emailgtw: [Trying IP address [10.20.148.210]]
    Jan 17 11:07:46:780 emailgtw: 220 ESMTP
    Jan 17 11:07:46:780 emailgtw: EHLO HCLSITOCUIM01.ITOC.LOCAL
    Jan 17 11:07:46:984 emailgtw: 250-appmail.hcl.com Hello [10.30.38.34], pleased to meet you
    Jan 17 11:07:46:984 emailgtw: 250-ENHANCEDSTATUSCODES
    Jan 17 11:07:46:984 emailgtw: 250-PIPELINING
    Jan 17 11:07:46:984 emailgtw: 250-8BITMIME
    Jan 17 11:07:46:984 emailgtw: 250-SIZE 18350080
    Jan 17 11:07:46:984 emailgtw: 250-DSN
    Jan 17 11:07:46:984 emailgtw: 250-ETRN
    Jan 17 11:07:46:984 emailgtw: 250-AUTH LOGIN PLAIN
    Jan 17 11:07:46:984 emailgtw: 250-DELIVERBY
    Jan 17 11:07:46:984 emailgtw: 250 HELP
    Jan 17 11:07:46:984 emailgtw: (cmd_test_smtp_login) smtp_open succeeded
    Jan 17 11:07:47:140 emailgtw: AUTH PLAIN
    Jan 17 11:07:47:357 emailgtw: 334
    Jan 17 11:07:47:357 emailgtw: %SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
    Jan 17 11:07:47:357 emailgtw: (mm_login) getting username and password for host [10.20.148.210]
    Jan 17 11:07:47:357 emailgtw: mm_login - found match [10.20.148.210]
    Jan 17 11:07:47:357 emailgtw: <suppressed>
    Jan 17 11:07:47:480 emailgtw: 501 5.0.0 AUTH aborted
    Jan 17 11:07:47:480 emailgtw: ?SMTP Authentication cancelled
    Jan 17 11:07:47:480 emailgtw: (cmd_test_smtp_login) smtp_auth failed
    Jan 17 11:07:47:480 emailgtw: QUIT
    Jan 17 11:07:47:608 emailgtw: 221 2.0.0 appmail.hcl.com closing connection



  • 2.  Re: SMTP mail server issue in Emailgtw Probe

    Posted 05-22-2018 12:49 PM

    Hi,

    I am having the same issue in our environment. I hope to get help and hopefully someone can share additional thoughts. I did the suggested telnet checking and I got the same issue as Yusuf is getting.

    Kindly advice. Thanks.



  • 3.  Re: SMTP mail server issue in Emailgtw Probe

    Posted 01-18-2018 07:58 AM

    Looks like some authorisation issue as from SMTP side the connection is not identified as secure.

    Can you try to test mail flow through command line from the server where the emailgtw probe is installed.
    Below link gives some insight on utilising commandline for mail flow test.
    https://support.managed.com/kb/a2313/how-to-send-email-locally-using-command-prompt.aspx

    Also confirm if you're using TLS at SMTP end and accordingly set it up in probe.



  • 4.  Re: SMTP mail server issue in Emailgtw Probe

    Broadcom Employee
    Posted 05-22-2018 10:45 PM

    My pleasure, glad to help! Yes, for the most part your emailgtw log looked ok, except for the auth.



  • 5.  Re: SMTP mail server issue in Emailgtw Probe

    Broadcom Employee
    Posted 05-22-2018 01:37 PM

    If you set the emailgtw loglevel to 5 and logsize to 10000 and cold start it (Deactivate-Activate) you should be able to see an SMTP error number. The machine (primary hub) where the emailgtw is running should be allowed and able to connect to the upstream mail gateway to send mail. Contact your mail/exchange admin to make sure that the server is allowed to send mail (internally/externally). Your mail admin may also be able to tell you if the mail gateway logs show any related errors.



  • 6.  Re: SMTP mail server issue in Emailgtw Probe

    Broadcom Employee
    Posted 05-22-2018 12:55 PM

    what is the type and version of the smtp server you are using?

    Have you checked with your SMTP server admin on the reason for the auth failure.

    If we assume the username and password are correct and we are still seeing an auth failure the SMTP admin would need to answers this.

    It could be an IP restriction or something else.

     

    There is not much more information from the emailgtw probe side we can provide why the SMTP server does not accept the user name and password being sent.

     

    it was not stated if you tested with Telnet from the same machine as the probe using the same username and password and if this worked or not.

     

    If it did not the probe can not work either.



  • 7.  Re: SMTP mail server issue in Emailgtw Probe

    Posted 01-18-2018 10:53 PM

    Hi Sinab,

     

    Thanks for your reply but as i mentioned earlier we are able to send mail by telnet from command prompt.

     

    Please suggest anything else that can be helpful to rectify this problem...



  • 8.  Re: SMTP mail server issue in Emailgtw Probe

    Broadcom Employee
    Posted 01-19-2018 09:05 AM

    **** Yusuf, please open a support case for this question so we can collect debug log information and investigate to determine the root cause.

     

    Kind regards,

    Britta Hoffner

    CA Support



  • 9.  Re: SMTP mail server issue in Emailgtw Probe

    Posted 05-22-2018 05:38 PM

    Stephen, thanks for the input. Below is what I got in the log after I started the emailgtw probe. I then run the test that is also in the log below. Can you please guide me on the SMTP error number?

     

    May 22 13:56:50:206 emailgtw: **********[ Starting Emailgtw ]***********
    May 22 13:56:50:207 emailgtw: emailgtw 2.84
    May 22 13:56:50:207 emailgtw: Nimsoft Corp.
    May 22 13:56:50:207 emailgtw: About to check bitness of the OS
    May 22 13:56:50:207 emailgtw: 32 bit OS detected
    May 22 13:56:50:208 emailgtw: SREQUEST: probe_checkin ->10.50.95.171/48000
    May 22 13:56:50:208 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48000 h=37 d=455
    May 22 13:56:50:208 emailgtw: sockClose:00F82AB8:10.50.95.171/42975
    May 22 13:56:50:209 emailgtw: SREQUEST: _close ->10.50.95.171/48000
    May 22 13:56:50:209 emailgtw: sslClientSetup - mode=0 cipher=DEFAULT
    May 22 13:56:50:209 emailgtw: nimSessionServer - port = 0
    May 22 13:56:51:214 emailgtw: sockCheckLocalPort: connect to port 48031 failed 10061 (ok - its free)
    May 22 13:56:51:214 emailgtw: sockCheckLocalPort - closesocket 692
    May 22 13:56:51:214 emailgtw: sockServer: next available port is 48031
    May 22 13:56:51:215 emailgtw: sockServer:00F826B0:0.0.0.0/48031
    May 22 13:56:51:215 emailgtw: port=48031 PID=13248
    May 22 13:56:51:216 emailgtw: SREQUEST: port_register ->10.50.95.171/48000
    May 22 13:56:51:217 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48000 h=37 d=0
    May 22 13:56:51:217 emailgtw: sockClose:00F6C080:10.50.95.171/43011
    May 22 13:56:51:217 emailgtw: SREQUEST: _close ->10.50.95.171/48000
    May 22 13:56:51:218 emailgtw: SREQUEST: gethub ->10.50.95.171/48000
    May 22 13:56:51:218 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48000 h=37 d=288
    May 22 13:56:51:219 emailgtw: sockClose:00F6C080:10.50.95.171/43012
    May 22 13:56:51:219 emailgtw: SREQUEST: _close ->10.50.95.171/48000
    May 22 13:56:51:219 emailgtw: SREQUEST: gethub ->10.50.95.171/48000
    May 22 13:56:51:220 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48000 h=37 d=288
    May 22 13:56:51:220 emailgtw: sockClose:00F6C080:10.50.95.171/43013
    May 22 13:56:51:220 emailgtw: SREQUEST: _close ->10.50.95.171/48000
    May 22 13:56:51:220 emailgtw: contacting HUB at 10.50.95.171:48002
    May 22 13:56:51:221 emailgtw: SREQUEST: subscribe ->10.50.95.171/48002
    May 22 13:56:51:410 emailgtw: RREPLY: status=not found(4) <-10.50.95.171/48002 h=37 d=0
    May 22 13:56:51:410 emailgtw: attach failed (not found), trying subscribe
    May 22 13:56:51:410 emailgtw: sockClose:00F6C080:10.50.95.171/43014
    May 22 13:56:51:411 emailgtw: SREQUEST: _close ->10.50.95.171/48002
    May 22 13:56:51:412 emailgtw: SREQUEST: subscribe ->10.50.95.171/48002
    May 22 13:56:52:412 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48002 h=37 d=21
    May 22 13:56:57:413 emailgtw: (doWork) - work in progress...
    May 22 13:56:57:413 emailgtw: (generate_report) no report.txt file present
    May 22 13:57:26:688 emailgtw: RREQUEST: _status <-10.50.95.171/44093 h=292 d=0
    May 22 13:57:26:688 emailgtw: SREPLY: status = 0(OK) ->10.50.95.171/44093
    May 22 13:57:26:690 emailgtw: RREQUEST: _close <-10.50.95.171/44093 h=291 d=0
    May 22 13:57:26:690 emailgtw: sockClose:00F6E500:10.50.95.171/48031
    May 22 13:57:26:894 emailgtw: RREQUEST: get_os <-10.50.95.171/44099 h=291 d=0
    May 22 13:57:26:894 emailgtw: nimSockaddr2Ip - found 10.50.95.171
    May 22 13:57:26:896 emailgtw: SREQUEST: verify_login ->10.50.95.171/48000
    May 22 13:57:26:897 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48000 h=37 d=50
    May 22 13:57:26:897 emailgtw: sockClose:00F6FD78:10.50.95.171/44100
    May 22 13:57:26:897 emailgtw: SREQUEST: _close ->10.50.95.171/48000
    May 22 13:57:26:897 emailgtw: SREPLY: status = 0(OK) ->10.50.95.171/44099
    May 22 13:57:26:897 emailgtw: RREQUEST: _close <-10.50.95.171/44099 h=291 d=0
    May 22 13:57:26:897 emailgtw: sockClose:00F6E500:10.50.95.171/48031
    May 22 13:57:30:912 emailgtw: RREQUEST: get_os <-10.50.95.171/44168 h=291 d=0
    May 22 13:57:30:912 emailgtw: nimSockaddr2Ip - found 10.50.95.171
    May 22 13:57:30:913 emailgtw: SREQUEST: verify_login ->10.50.95.171/48000
    May 22 13:57:30:915 emailgtw: RREPLY: status=OK(0) <-10.50.95.171/48000 h=37 d=50
    May 22 13:57:30:915 emailgtw: sockClose:00F6FD78:10.50.95.171/44169
    May 22 13:57:30:915 emailgtw: SREQUEST: _close ->10.50.95.171/48000
    May 22 13:57:30:915 emailgtw: SREPLY: status = 0(OK) ->10.50.95.171/44168
    May 22 13:57:30:915 emailgtw: RREQUEST: _close <-10.50.95.171/44168 h=291 d=0
    May 22 13:57:30:915 emailgtw: sockClose:00F6E500:10.50.95.171/48031
    May 22 13:57:38:052 emailgtw: RREQUEST: test_smtp_login <-10.50.95.171/44254 h=301 d=76
    May 22 13:57:38:052 emailgtw: test_smtp_login from 10.50.95.171/44254
    May 22 13:57:38:056 emailgtw: [Trying IP address [10.50.84.8]]
    May 22 13:57:38:059 emailgtw: 220 COCAHPRD01.ros.com Microsoft ESMTP MAIL Service ready at Tue, 22 May 2018 16:57:37 -0400
    May 22 13:57:38:059 emailgtw: EHLO COUMHUBPDEV01.ros.com
    May 22 13:57:38:060 emailgtw: 250-COCAHPRD01.ros.com Hello [10.50.86.17]
    May 22 13:57:38:060 emailgtw: 250-SIZE 10485760
    May 22 13:57:38:060 emailgtw: 250-PIPELINING
    May 22 13:57:38:060 emailgtw: 250-DSN
    May 22 13:57:38:060 emailgtw: 250-ENHANCEDSTATUSCODES
    May 22 13:57:38:060 emailgtw: 250-STARTTLS
    May 22 13:57:38:060 emailgtw: 250-AUTH
    May 22 13:57:38:060 emailgtw: 250-8BITMIME
    May 22 13:57:38:060 emailgtw: 250-BINARYMIME
    May 22 13:57:38:060 emailgtw: 250-CHUNKING
    May 22 13:57:38:060 emailgtw: 250-XEXCH50
    May 22 13:57:38:060 emailgtw: 250 XSHADOW
    May 22 13:57:38:060 emailgtw: STARTTLS
    May 22 13:57:38:061 emailgtw: 220 2.0.0 SMTP server ready
    May 22 13:57:38:291 emailgtw: EHLO COUMHUBPDEV01.ros.com
    May 22 13:57:38:292 emailgtw: 250-COCAHPRD01.ros.com Hello [10.50.86.17]
    May 22 13:57:38:292 emailgtw: 250-SIZE 10485760
    May 22 13:57:38:292 emailgtw: 250-PIPELINING
    May 22 13:57:38:292 emailgtw: 250-DSN
    May 22 13:57:38:292 emailgtw: 250-ENHANCEDSTATUSCODES
    May 22 13:57:38:292 emailgtw: 250-AUTH
    May 22 13:57:38:292 emailgtw: 250-8BITMIME
    May 22 13:57:38:293 emailgtw: 250-BINARYMIME
    May 22 13:57:38:293 emailgtw: 250-CHUNKING
    May 22 13:57:38:293 emailgtw: 250-XEXCH50
    May 22 13:57:38:293 emailgtw: 250 XSHADOW
    May 22 13:57:38:293 emailgtw: (cmd_test_smtp_login) smtp_open succeeded
    May 22 13:57:38:293 emailgtw: (cmd_test_smtp_login) smtp_auth failed
    May 22 13:57:38:293 emailgtw: QUIT
    May 22 13:57:38:294 emailgtw: 221 2.0.0 Service closing transmission channel
    May 22 13:57:38:295 emailgtw: [Winsock cleanup]
    May 22 13:57:38:295 emailgtw: SREPLY: status = 6(permission denied) ->10.50.95.171/44254
    May 22 13:57:38:295 emailgtw: RREQUEST: _close <-10.50.95.171/44254 h=291 d=0
    May 22 13:57:38:295 emailgtw: sockClose:00F6E500:10.50.95.171/48031
    May 22 13:58:00:178 emailgtw: RREQUEST: _status <-10.50.95.171/44926 h=270 d=0
    May 22 13:58:00:179 emailgtw: SREPLY: status = 0(OK) ->10.50.95.171/44926
    May 22 13:58:00:179 emailgtw: RREQUEST: _close <-10.50.95.171/44926 h=269 d=0
    May 22 13:58:00:179 emailgtw: sockClose:00F79DE0:10.50.95.171/48031



  • 10.  Re: SMTP mail server issue in Emailgtw Probe

    Posted 05-22-2018 05:35 PM

    what is the type and version of the smtp server you are using?  - Exchange 2010 sp3 ru19
    Have you checked with your SMTP server admin on the reason for the auth failure. - this is now being checked.

    Thanks, Gene, for the guidance.



  • 11.  Re: SMTP mail server issue in Emailgtw Probe

    Broadcom Employee
    Posted 05-22-2018 07:52 PM

    Are you sure you need to enter credentials/need to authenticate?

     

    Have you tested the connection without the username and password, and without TLS?



  • 12.  Re: SMTP mail server issue in Emailgtw Probe

    Posted 05-22-2018 08:13 PM

    Wow! I never thought it would work without the credentials. I removed them and tested successfully. Below is the log of the testing and GUI is showing green. Thanks, Stephen!!!

     

    May 22 17:11:12:984 emailgtw: (cmd_test_smtp_login) smtp_open succeeded
    May 22 17:11:12:984 emailgtw: (cmd_test_smtp_login) no user specified, not testing authentication
    May 22 17:11:12:984 emailgtw: QUIT