Try the following from another machine on the same subnet of the filer
telnet $MAILHOST 25 Helo itsme
250 OK <--- SERVER RESPONSE
MAIL FROM: $AUTOSUPPORT_FROM address (The address you've configured for options autosupport.from)
250 OK <--- SERVER RESPONSE
RCPT TO: $YOUR_EMAIL_ADDRESS
250 OK <--- SERVER RESPONSE
DATA test test test test . <---- final dot and \r\n
250 ok <--- SERVER RESPONSE.
If you can't connect at all, or the exchange server says something other than 250 OK then you've either got a network or name resolution problem (can't connect at all) or the Exchange server is not allowing you to relay (Probably some error message like 550 Relaying Denied.)
If the mailserver gives you a 250, then it's accepted responsibility for delivering the email.
~Max
On Feb 12, 2008, at 11:43 AM, Clark, Andre wrote:
Exchange is set up not to be an open relay. You need to add your system’s IP address to the Exchange server you are using to allow the SMTP messages to go through.
AC
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Daniel Keisling Sent: Tuesday, February 12, 2008 14:08 To: Kenneth Heal; toasters@mathworks.com Subject: RE: Autosupport failing to mailhost
Does the autosupport.support.transport option only use smtp or https when delivering to NetApp? In this case (https), it works fine. NetApp is receiving my autosupports.
What's not working is local mail to me. I tried this on another filer at another site (except for the mailhost (another Exchange 2003 server), all the autosupport settings are the same) and the email to my local account came immediately, as well as a notification from NetApp. The log even said:
Feb 12 14:11:57 EST [wilstore2a: asup.smtp.sent:notice]: Cluster Notification mail sent: Cluster Notification from wilstore2a (USER_TRIGGERED (testing_from_wilstore)) INFO
This was definitely sent via smtp, yet the autosupport.support.transport is set to https.
Daniel
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Kenneth Heal Sent: Tuesday, February 12, 2008 12:33 PM To: Daniel Keisling; toasters@mathworks.com Subject: RE: Autosupport failing to mailhost Hi Daniel
I see a line which says autosupport.support.transport https
Which means the filer will use https to send autosupports, and not smtp.
Can you try options autosupport.support.transport smtp
And see if the mails go through?
cheers Kenneth
Kenneth Heal Databasement BV The Netherlands Subject: Autosupport failing to mailhost Date: Tue, 12 Feb 2008 10:22:51 -0600 From: daniel.keisling@austin.ppdi.com To: toasters@mathworks.com Hello,
From what seems out of the blue, Autosupport emails are no longer able to be sent to my mailhost (Exchange 2003 on the same subnet):
"Autosupport cannot connect to host rtpmail01.americas.ppdi.local (Network comm problem) for message: USER_TRIGGERED (TEST)"
This message will be thrown until the message is eventually dropped. My Exchange administrator does not see any connections coming from the filer to send this email. I can ping the mailhost with no problem:
rtpstore2b> ping rtpmail01.americas.ppdi.local rtpmail01.americas.ppdi.local is alive My routing table:
Destination Gateway Flags Refs Use Interface default 172.20.63.254 UGS 4 222239 e0a 127 localhost UGS 0 22236 lo localhost localhost UH 3 145 lo 172.20.62/23 link#4 UC 0 0 e0a rtpmail01.americ 0:8:2:28:ee:86 UHL 0 11 e0a rtpexchbe01.amer 0:8:2:28:ee:86 UHL 0 0 e0a rtpstore2b 0:a0:98:9:66:53 UHL 0 18112 lo My autosupport options:
rtpstore2b> options autosupport autosupport.cifs.verbose off autosupport.content complete autosupport.doit DONT autosupport.enable on autosupport.from rtpstore2b at rtp.ppdi.com autosupport.local.nht_data.enable off autosupport.local.performance_data.enable off autosupport.mailhost rtpmail01.americas.ppdi.local autosupport.minimal.subject.id hostname autosupport.nht_data.enable on autosupport.noteto autosupport.performance_data.enable on autosupport.retry.count 15 (value might be overwritten in takeover) autosupport.retry.interval 4m (value might be overwritten in takeover) autosupport.support.enable on autosupport.support.proxy autosupport.support.to autosupport at netapp.com autosupport.support.transport https autosupport.support.url support.netapp.com/asupprod/post/1.0/ postAsup autosupport.throttle on autosupport.to storage at wilm.ppdi.com (I've replaced the @'s with 'at')
I have no problems with my SSH session, so I don't know how this could be a network cable/connection problem. Are there any debugging steps I can do? Has anyone seen this before? It has definitely worked in the past. This is DOT 7.2.2 on a FAS3040.
TIA,
Daniel
This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.
Express yourself instantly with MSN Messenger! MSN Messenger
This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.
CONFIDENTIALITY NOTICE
This communication, including any attachment, is confidential. It is intended for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us by telephone or facsimile and immediately delete the communication.