Yes I took out the _ in them and put the machine in DNS. Thanks, Spencer
-----Original Message----- From: Mark Symons [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 11:40 AM To: Plantier, Spencer Subject: RE: email notifications Spencer, Did you come right with your email actions? Mark Symons Ipswitch, Inc Augusta GA =========== > HELO cary_monitor > 501 5.5.4 Invalid Address. Well. I was both right and wrong. The Exchange server has given a good 5xx response, as I predicted. But the problem was in the HELO command which I thought would be "unlikely". No matter =) >From RFC 2821, the correct syntax for the command is: helo = "HELO" SP Domain CRLF ie: HELO hostx.ipswitch.com Although alternatives can and should work: ie: HELO 192.168.20.30 WhatsUp bases its use of HELO on the PC's TCP/IP config - and, the TCP/IP DNS tab is configured to use the PC's Computer name as the "Host Name". Hence, "cary_monitor" I would guess that the Domain field in the DNS tab is blank. Otherwise WhatsUp should have used: cary_monitor.stratech.com Either way, MS Exchange does not like this because an underscore is an illegal character in a DNS hostname(ignoring SRV records). So, configure your TCP/IP DNS config to use a hostname that Exchange will accept. The safest thing to do is perform a PTR query on your own IP address and use that info. You could Telnet to port 25 on your MS Exchange server and test what will work before you reconfigure WhatsUp. It's possible that: cary-monitor ..would work. ie, not even specifying a domain suffix - just using legal characters. Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Plantier, Spencer Sent: 23 February 2005 15:59 To: [email protected] Subject: RE: [WhatsUp Forum] email notifications 220 xxxx.xxxx.xxxx.xxx Microsoft ESMTP Mail service Version 6.0.3790.0 ready at Wed 23 Feb 2005 15:50:22-0500 HELO cary_monitor 501 5.5.4 Invalid Address. Both send from and send to address are my address and are valid. Thanks, Spencer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Symons Sent: Wednesday, February 23, 2005 3:46 PM To: [email protected] Subject: RE: [WhatsUp Forum] email notifications You need to examine the SMTP communication with the server. I would bet that: a) The Exchange server has something it's not happy about in the use of the protocol. b) It's security related (anti-spam, etc) c) The server is returning a 5xx code that will let out work out what's going on.. and fix the problem. In WhatsUp Gold you can use the Debug log to display the conversation. Simply open the log and then go into the Notification Library and do a "Test". Then close the library and examine what you've got in the Debug window. In WhatsUp Professional 2005, perform the "Test" in the Action Library and then click on "Details" in order to view the conversation. So, what should you be looking at? A couple of candidates are: a) Is Exchange objecting to the use of the HELO command? Perhaps it's expecting something that matches a PTR record in DNS. Unlikely. b) Is Exchange objecting to the MAIL FROM: address? Much more likely.. and should be easy to fix. Just change the Notification definition to use an address that is valid. Mark Symons Ipswitch, Inc Augusta GA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Plantier, Spencer Sent: 18 February 2005 16:27 To: [email protected] Subject: [WhatsUp Forum] email notifications We have just upgraded to a windows 2003 exchange server and now our notifications don't work. Any help would be appreciated. Thanks. Spencer Plantier System Network Administrator 301 Gregson Dr Cary, NC 27511 Office 919-379-8513 Cell 919-272-8833 [EMAIL PROTECTED] Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
