>What are some of the good tools out there for troubleshooting email
>problems. I mean beyond tracert and telnet. I especially would like to know
>some trade secrets on how to prove other people are having problems with
>their mail servers since a lot of my job deals with troubleshooting and
>proving other networks are having issues not mine. Thanks in advance for any
>assistance.
DNS is always suspect, often guilty. So DNS Expert and dig (on my
Bind site for Win32) are indipsensable for DNS troubleshooting. blow
off nslookup, it sucks. Leave it to MS to deliver nslookup but not
dig and mislead the world.
telnet to port 25 is fast, gives raw data, and very revelatory.
Also, grab eudora pro 5 freebie. It has a byte-level logging feature
(turn on in eudora.ini) that also reveals what's going on when SMTP
client trying to send to a SMTP server. Also logs for POP3 traffic,
priceless and free.
traceroute is pretty useless for mail work.
Brains and experience are sometimes handy.
And if you can pack/politicize the US SC, you can avoid "irreparable
harm" for your airhead son.
Len
http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K
http://IMGate.MEIway.com : Build free, hi-perf, anti-spam mail gateways
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/imail_forum%40list.ipswitch.com/
