First, let's determine how likely it is the domain in question is valid. Now I'm in the states so my arrogant American bias will be showing... but bear with me:
dpvkft -- The local-part of the e-mail address doesn't parse into any first and/or last name combination I recognize as being even remotely valid, nor are there enough vowels to make a word in any language I'm aware of besides Hebrew. @xelero.hu -- The domain extension isn't one I recognize... nut it could be valid.. hu... Hungary? Dunno... but they tend to use lots of vowels in places I'd never imagine in my limited American experience. Fire up a web browser... can you get to www.xelero.hu? Next... let's parse the NDR itself. The NDR is "unroutable address". Well, I'd anticipate host unknown if the host was unknown, but unroutable address taken at face value means the address associated with the host is unroutable. Do they mean mine or theirs? Well... if this guy is your brother Bob and you're confident the address is valid, perhaps they mean yours. But I'm going to betg this isn't your brother Bob, so let's work (at least temporarily) under the assumption its someone else's fault. Let's find out if that is in fact the case... now I could rely on some 3rd party provider (a la dnsstuff.com) to give me an answer or I could look for myself. Well,since this is a fishing lesson, we'll find out on our own. For this task we'll use nslookup. We could use dig instead, but nslookup is good enough... and yes, I'm in a hotel using a wayport... which accounts for the delay between responses to the question: nslookup Default Server: eth0.nmd.lah.dca.wayport.net Address: 64.134.154.1 > xelero.hu Server: eth0.nmd.lah.dca.wayport.net Address: 64.134.154.1 *** eth0.nmd.lah.dca.wayport.net can't find xelero.hu: Non-existent domain > set q=mx > xelero.hu Server: eth0.nmd.lah.dca.wayport.net Address: 64.134.154.1 *** eth0.nmd.lah.dca.wayport.net can't find xelero.hu: Non-existent domain I'll leave it as an exercise to the reader to determine what each of the commands I executed above did, but the results will hopefully parse such that you have an idea as to the validity of the recipient's domain. Hopefully this doesn't mean your hot date last night gave you a bogus e-mail address. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:bounce- > [EMAIL PROTECTED] On Behalf Of Kim Schotanus > Posted At: Thursday, September 16, 2004 4:50 AM > Posted To: swynk > Conversation: another strange NDR > Subject: RE: another strange NDR > > Nothing, what can I do? > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chris > Scharff > Sent: donderdag 16 september 2004 11:50 > To: Exchange Discussions > Subject: RE: another strange NDR > > > <fishing lesson> > Yes. So you've gotten an NDR. What have you tried so far to diagnose the > root cause? > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:bounce- > > [EMAIL PROTECTED] On Behalf Of Kim Schotanus > > Posted At: Thursday, September 16, 2004 4:01 AM Posted To: swynk > > Conversation: another strange NDR > > Subject: another strange NDR > > > > Another strange one; any ideas? Kim > > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
