Gotchya. Sorry to seem so confused, just trying to get the topography in my head. If you have any other servers at the remote location that the problem filer is at, can you ping the smtp server from one of those?
If the next hop is the actual mail server itself, could it be a local firewall issue that is blocking the filer from the mailhost? If a ping gets through the firewall, a traceroute should as well(unless there are some very granularly defined rules in place). You're routing appears to be good, at least if your IP lookup is good. I assume that you see an internal interface where all I would see is an external one.
That is a lot of hops to get to your SMTP server, a cross country haul? Have you thought about using the HTTPS transport and having the filer post directly to NetApp?
"options autosupport.support.transport https" would set it so the filer posts directly to NetApp. Now the bigger issue with this is, you won't get the alerts, this way. You would have to then go into the NOW autosupport tool and configure your alerts from there. If you have secondary monitoring, this might not be an issue at all, it would depend on your situation.