NBX 6.0.44 smtp and offsite email configuration (726 Views)
Reply
Occasional Advisor
TargetInfo
Posts: 10
Registered: ‎03-30-2010
Message 1 of 10 (726 Views)

NBX 6.0.44 smtp and offsite email configuration

Hello,



My NBX is configured with offsite notification in system, cos and user. The internal exchange server is configured in smtp domain name with internal dns that work correclty. I can ping nbx from them. But it didn't works i.e. I didnt receive any email. Looking in the nboss log the only mail related info (I suppose) is



0329:125339:0134 Bitmail        W Initialized Bitmail.                                                                                                   


0329:125339:0134 Bitmail        W Bitmail Sender task has started. Ready



After that there are no smtp mail error or messages and my exchange server didn't log any access from nbx



I check all the articles but found no solution. Can anyone help me? Maybe the nboss log level is too low?



PS: if i set the offsite to voicemail all works...



Thanks



 



Please use plain text.
Super Advisor
bosoxfan_1
Posts: 238
Registered: ‎01-13-2009
Message 2 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

look for nbxInetNot0 errors in your nbosslog... usually this is either a dns error or mail server rejecting since it does not know the NBX.. here are some errors that you might have .. let us know how it goes.



















 





















NBoss log errors:



resolvQuery returned: 6b0001 is an unexpected server failure occurred. This is a nonrecoverable error.



resolvQuery returned: 6b0002 is a soft error that indicates that the local server did not receive a response from an authoritative server. A retry at some later time may be successful.  Possible issues that the host is not a DNS server or DNS IP is not a host.



resolvQuery returned: 6b0003 is the host is unknown.  Likely the email host name is invalid.



resolvQuery returned: 6b0004 is no address is available for the name  specified in the server request. This is not a soft error. Another type of name  server request may be successful.  Likely the MX lookup did not resond with a valid MX entries.





0701:165635 nbxINetNot0    E DeliverEMail: SockOpen(64.157.4.82, 25) failed



Indicates that remote host is unreachable on TCP port 25.  Likely causes are no route to host or firewall restrictions.









Please use plain text.
Super Advisor
merlin_1
Posts: 483
Registered: ‎01-23-2009
Message 3 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

 



Upgrade to the latest 6.0.63 code for one thing . Always want to run the latest ...



 



Also there is a 3KB knowledgebase doc that you should review





NBX - Troubleshooting offsite email notification message delivery





 








Solution ID - 2.0.88348627.3458295


Here's how the NBX sends off-site email (NAT is fully supported for off-site email messaging):





1 - In



NetSet it must be enabled in System-Wide, in CoS, and on each User before it will work


2 - NCP performs an MX record lookup using DNS server IP information to return a valid TCP/IP address for each message being sent


3 - NCP acts as an MTA (Message Transfer Agent) - will directly contact each destination mail server for local delivery


4 - NCP establishes a TCP socket to the resolved TCP/IP address on SMTP port 25


5 - NCP must be able to open a TCP session to the resolved IP address of each destination email server


6 - Each destination server the NBX is sending email to may be configured for a rule base and based on certain criteria my reject an email or attachment that other email servers accept. For example, some email servers may at first accept the email from the NBX, and after the NBX gets an OK and disconnects, the destination email server may do one of several validations, including check for a valid sending address. Does NBX@your-smtp-domain-name exist? The NBX will use this as the sending address, which may not itself be a valid return address. This may be only one of many customized rules that destination servers can do, even after accepting an NBX email, that prevents delivery to the recipient.


The SMTP Domain Name should validate to YOUR NCP public IP being used. If you do not own a registered domain, you should put your ISP's domain name here in the form "xxxxx.com"





TROUBLESHOOTING TIPS:


- A packet trace will reveal in MINUTES whether the NBX is able to contact the intended mail server, and whether the message was accepted. There are 4 main reasons why a message will not deliver and possible reasons:





1 - NBX is not trying to send the message


(off-site notify not fully enabled at system, group, and user levels, user has syntax error for the email address - only one address per line - no commas or multi sends per line)





2 - NBX is unable to resolve the IP address of the destination email server as typed in the user settings for delivery (DNS server info wrong, DNS server unavailable, router/firewall preventing this connection)


** Have the Network Admin confirm that the DNS IP address set in NetSet  is valid, reachable, and will return an MX record with the IP address (not just the MX name), for the target or test email account domain name.  This step is critical so that the NBX will know the IP address of the email server it must reach for every external email address it must contact.





3 - NBX is unable to establish a TCP connection on port 25 directly to the destination email server


(Destination email server down, firewall/router has port 25 blocked, destination email server is In House and router/firewall is preventing looped connection to the public side of the in-house private DNS or MAIL server)





4 - Destination email server, after connection, either rejects the message, or accepts it but may not deliver it due to post-send validation rules they have set up.


(TCP mail connection is poor; Telnet session timed out, SMTP domain name did not verify, various errors reported by destination email server within the TCP connection - must do a packet trace to see these errors)  MANUALLY you may try to do the steps that the NBX does, using a PC on the same sub-net as the NBX to catch problems listed above. Below is a basic outline of what to do, not detailed. Perform these steps at a PC's DOS prompt that can do NSLOOKUP (Win 2000, Win NT, etc).  ** Be sure that the PC you are testing from is on the same subnet as the NCP, and, that the DNS IP address shown on the PC with "ipconfig /all" is the same DNS server IP as has been set in NetSet, to ensure you are testing just as the NBX would be sending.





In this example, we're trying to send an off-site email to "Jerry@Home.Com"





- Perform an NSLOOKUP of the destination domain. Windows NT and 2000 support NSLOOKUP.


From the DOS prompt type:


NSLOOKUP


> set type = MX


> home.com (this is an example)





home.com MX preference = 50, mail exchanger = mx-rr.home.com


(there may be more listings. Often, in the server name list, the mail exchanger IP address may be defined.  If it is, the NCP will have the mail server IP address and not need to do any further DNS lookup.)





- now resolve the IP address for the mx-rr.home.com mail server after exiting NSLOOKUP by typing EXIT





- at the C:\ prompt type


 NSLOOKUP


 > mx-rr.home.com (the name of the mail server you are trying to connect to. Do NOT set type to mx this time)





- you will get at least 1 IP address back for that server, maybe more:


65.10.73.243, 24.0.95.20, 24.0.95.21, 65.10.73.242





- Now try to connect using the PC directly to the destination email server to test tcp port 25 on your LAN 





- type "telnet 65.10.73.243 25" at the DOS prompt. Don't forget the 'space 25' after the IP address to indicate SMTP connection





- You should get a response directly from the destination email server, and you will be in an interactive TCP mail session at this point. This basically tries to prove correct DNS, NSLOOKUP, and router/firewall configuration to allow the NBX to directly establish an email connection to an off-site mail server. This does not mean the message will deliver, there may be an error that comes up during the sending of the message, or the NBX setting may be different from the PC you are testing on. But if you got this far on a PC on the same sub-net as the NCP, the NCP with correct configuration should be able to do the same and send email. If you get this far but still NO email will deliver, even when trying different off-site email domain addresses (send to several different email addresses at different ISP mail providers) then a packet trace will be necessary. The good news is a packet trace will be able to quickly indicate the point of failure, or prove the NBX successfully delivers the message but the destination server is not delivering it after receipt for post-processing reasons.





- If an Office Connect Firewall (5x1 Models)is used with NAT enabled, click
for solution. Upgrade the firmware to 6.03a or later on the Office Connect Product to address an issue with SMTP. (Office Connect 25 Firewall has no issues)

 





Please use plain text.
Occasional Advisor
TargetInfo
Posts: 10
Registered: ‎03-30-2010
Message 4 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

Dear Bosoxfan,



I didn't have any error or warning message like the ones you wrote...



here is my nbosslog :



NBX LOGGING FACILITY LOG FILE                                                                                                                            


Software Version: R6_0_44, Apr 10 2007                                                                                                                   


0330:114906:0999 Logfile Created


                                                                                                                        


0330:114905:0846 DBI            E In m_nRetrieveCustomCompressions, Invalid record                                                                       


0330:114905:0846 DBI            E In m_nRetrieveCustomCompressions, Invalid record                                                                       


0330:114905:0846 DBI            E In m_nRetrieveCustomCompressions, Invalid record                                                                       


0330:114905:0865 DBI            E In m_nRetrieveCustomCompressions, Invalid record                                                                       


0330:114905:0865 DBI            E In m_nRetrieveCustomCompressions, Invalid record                                                                       


0330:114905:0865 DBI            E In m_nRetrieveCustomCompressions, Invalid record                                                                       


0330:114947:0576 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x10 0x5af0 0x4397 DOWN ..                                         


0330:114947:0692 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0xe0 0x187a 0x19b4 DOWN ..                                         


0330:114947:0730 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x4 0x75c7 0xb620 DOWN ..                                          


0330:114947:0769 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2f7f 0x5b95 DOWN ..                                         


0330:114948:0807 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x18 0xf38a 0x3bf8 DOWN ..                                         


0330:114948:0884 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x18 0xf3a2 0x8cfc DOWN ..                                         


0330:114948:0923 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x4 0x7574 0x5ae9 DOWN ..                                          


0330:114948:0942 Bitmail        W Initialized Bitmail.                                                                                                   


0330:114948:0942 Bitmail        W Bitmail Sender task has started. Ready.                                                                                


0330:114948:0999 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4401 DOWN ..                                         


0330:114949:0076 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4402 DOWN ..                                         


0330:114949:0115 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4403 DOWN ..                                         


0330:114949:0192 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x1d 0x7db9 0x3bb1 DOWN ..                                         


0330:114949:0230 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x15 0xf23f 0x2ef2 DOWN ..                                         


0330:114949:0384 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x60 0x890 0xbda7 DOWN ..                                          


0330:114949:0423 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0xb 0xace7 0x22e4 DOWN ..                                          


0330:114953:0615 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x10 0x5af0 0x4397 DOWN ..                                         


0330:114955:0076 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0xe0 0x187a 0x19b4 DOWN ..                                         


0330:114955:0884 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x1 0x34d 0x1519 DOWN ..                                           


0330:114956:0480 DBI            W No Personal Operator configured for user at extension:                                                           


0330:114957:0346 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x18 0xf3a2 0x8cfc DOWN ..                                         


0330:114957:0846 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x4 0x7574 0x5ae9 DOWN ..                                          


0330:114958:0076 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4401 DOWN ..                                         


0330:114958:0346 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4402 DOWN ..                                         


0330:114958:0499 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4403 DOWN ..                                         


0330:114959:0615 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x60 0x890 0xbda7 DOWN ..                                          


0330:115000:0076 H3LinkLayer    E


IP sendto() call failed, returnStatus = 0xffffffff                                                                   


0330:115000:0115 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0xb 0xace7 0x22e4 DOWN ..                                          


0330:115001:0634 DBI            W No Personal Operator configured for user at extension:                                                           


0330:115029:0903 Router         E Routing algorithm failed for inDigits=00744548271 RouteId=2                                                            


0330:115053:0115 Router         E Routing algorithm failed for inDigits=00744548271 RouteId=2                                                            


0330:115914:0134 Transfer       W 1050 : OtherParty's extension= 1214                                                                                    


0330:115914:0153 OrigSession    E 1050 : State:Hold in Held State                                                                                        


0330:150453:0269 Router         W Rerouting call to 0571670311 due to the following reason: UNSPECIFIED                                                  


0330:150453:0288 Router         W Rerouting action is: UNSPECIFIED                                                                                       


0330:150457:0538 Router         W Rerouting call to 0571670311 due to the following reason: UNSPECIFIED                                                  


0330:150457:0538 Router         W Rerouting action is: UNSPECIFIED                                                                                       


0330:150457:0538 Router         E Rerouting failed for outpulse digits=                                                                                  


0330:153430:0749 DBI            W Failure bSetTotalTimeOnCallRTS, The Wait time exceeding the Maximum wait time limit.                                   


0330:155555:0403 DBI            W Failure bSetTotalTimeOnCallRTS, The Wait time exceeding the Maximum wait time limit.                                   


0330:175512:0538 DBI            W Failure bSetTotalTimeOnCallRTS, The Wait time exceeding the Maximum wait time limit.                                   


0330:175636:0115 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x18 0xf377 0xb987 DOWN ..                                         


0330:182340:0038 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4401 DOWN ..                                         


0330:182524:0807 H3LinkLayer    E Got a Pkto TimeOut - Application Should Mark Device 0x11 0x2233 0x4401 DOWN ..            



 



Please use plain text.
Occasional Advisor
TargetInfo
Posts: 10
Registered: ‎03-30-2010
Message 5 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

Dear Merlin,



I've checked all the thing in that doc including NSLookup, mx record, telnet to the port 25 from a pc on the same internal network where is my nbx



From my point of view the problem is that nbx didn't try to send anything because I din't found error or messages related in the nbosslog and II didn't found nothing in the mail server connections log... 



Maybe a license problem?



Thanks in advance



 



 



Please use plain text.
Super Advisor
bosoxfan_1
Posts: 238
Registered: ‎01-13-2009
Message 6 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

offsite notifcation does not require another license... I would turn on more logging to get to the bottom of the issue:



1. go to ip_address/sec_cont/ops/cfglog.htm



2. Under Event Log filter, click All, Output to Disk, New Omcponent message filter, click on all



and in the Customer settings put in -1



3. scroll down to nbxInetNot0 and select that



4. at bottom of page, click on Apply



5. Now make a test call to leave the offsite notifation



6. go to your NBossLog.txt and see what you have in there..



 



Hope this helps.. please post results here... if this does not work, I would suggest opening a case with 3com.



Please use plain text.
Super Advisor
merlin_1
Posts: 483
Registered: ‎01-23-2009
Message 7 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

Remember that Offsite Notification ONLY works with new messages . Only one notify  attempt per one new message . After that the system will not send out a new notify msg for the 2nd new msg if the first one was not listened to . Once the first one is listened to and the mailbox is empty  , then another attempt will be sent on the next new msg left .



 



So



 



new msg



OSN attempt



2nd new msg



no new  OSN message attempt



Listen / save or delete .



One new Msg



New OSN attempt



 



Please use plain text.
Occasional Advisor
TargetInfo
Posts: 10
Registered: ‎03-30-2010
Message 8 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

Dear bosoxfan,



thanks for your invaluable help.



here is the log0331:115222:0057 nbxINetNot0    L Received DELIVER Msg for User:244, SessionId:2                                                                         


0331:115222:0057 nbxINetNot0    L Received EMail delivery request for User:244, SessionId:2                                                              


0331:115222:0076 nbxINetNot0    L DeliverEMail: No Address Record found: Failed resolving address for mail host with name mail.targetinfo                


0331:115222:0076 nbxINetNot0    L Delivery failed, no more retry attempts                                                                                


0331:115722:0076 nbxINetNot0    L Received CANCEL Msg for User:1, SessionId:15855104                                                                     


0331:115722:0076 nbxINetNot0    W Bad event CANCEL in State Idle                                                                                         


 



I think the problem is in the limit of 15 chars of the name handled by the NBX in reply to the mx request.  My domain name is targetinformatica.it and my Mail Exchanger is mail.targetinformatica.it.  If is not a problem of log truncation, the reply mail.targetinformatica.it is truncated in nbx software so when he tries to resolve mail.targetinfo he get and invalid address.... If this is the problem I didn't know ho to solve it without software intervention of 3com... or maybe creating a dedicated dns with a shorter domain name...



Please use plain text.
Super Advisor
bosoxfan_1
Posts: 238
Registered: ‎01-13-2009
Message 9 of 10 (726 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

The name is just cut off the log so it is not a case of the DNS name being too long.



There was a bug fixed in 6.5.22 where  NBX would recognize a DNS "CNAME" return.



Upgrade to 6.5.22 and that will should fix your issue !



Please use plain text.
Valued Contributor
Justin_Goldberg
Posts: 163
Registered: ‎03-16-2011
Message 10 of 10 (304 Views)

Re: NBX 6.0.44 smtp and offsite email configuration

Rich,

 

Any chance of getting access to the 3com knowledge base? I checked the hp online openview tool, but we have no access to it. 

 

We sold more NBX's than anyone else in our area!

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation