I would suggest setting up a mail server (its not hard - I recommend mercury given its not going to be running for long, and the logging screens on that package are useful for diagnostics).
once you find out what the "from" and "to" addresses are that it is attempting to send to, you can contact the "sender" and then remove the server again :)
http://www.pmail.com/overv
(any windows workstation will do to run it on, from win95 onwards :)
Main Topics
Browse All Topics





by: jahboitePosted on 2009-01-16 at 00:43:07ID: 23391142
In order to get the remote host to give away this information, you'd have to open up this port to a machine on your network that could fake an smtp server - at the very least you'd want to send a banner upon successful connection and then hope that the remote host offers up a domain name.
Why not just get the remote hosts IP address from the cisco logs/alerts and figure out who's doing what from there. You could start with a rDNS query and a Whois lookup which should give you enough information to work out whether it's one of yours.