Nic,
If it was posted on the Internet, it must be true! Don't you see the ads
where you are? :-)
Seriously, when I get errors like this I like to trace the DNS "tree" --
amazing how often I find that there are "DNS traps" "in the wild"...
because, truth be told, you could BOTH be right! (It's amazing to me how
much people take DNS for granted... )
For example:
- the TLD says example.com uses NS servers 1.1.1.1 & 1.1.1.2
- the NS service at 1.1.1.1 says that it truly is a DNS serer for
example.com, and lists 1.1.1.3 & 1.1.1.4 as other NS servers... but not
1.1.1.2
- the NS service at 1.1.1.2 says that it truly is a DNS server for
example.com, and lists 1.1.1.1 as the only other NS server
- the NS service at 1.1.1.1 says the least-cost MX record for
example.com is 2.2.2.1
- the NS service at 1.1.1.2 says the least-cost MX record for
example.com is 2.2.2.1
- the NS service at 1.1.1.3 says the least-cost MX record for
example.com is 2.2.2.4
- the NS service at 1.1.1.4 says the least-cost MX record for
example.com is 2.2.2.16
- The mailserver at 2.2.2.1 says [email protected] is a local mailbox
- The mailserver at 2.2.2.4 says example.com is NOT a valid local
domain and rejects ALL messages for example.com
- The mailserver at 2.2.2.16 says [email protected] is NOT a valid
user, but accepts some OTHER messages for example.com
Now this is an extreme example, but I have found situations like this
"for real" -- the issue is that people migrate from server to server &
don't clean up the configurations behind them. (In the example above,
the 2.2.2.16 server was used years ago, so simply doesn't know
[email protected], and 2.2.2.4 is just an error).
The good news is that there are tools that can help you discover these
kinds of issues: check out _*INTODNS.*__*COM*__*
*_Along with *_MXTOOLBOX.COM_**, *its just one of those tools that I
wouldn't want to live without (as a mail admin, at least)
Dan McAllister
IT4SOHO
QMT DNS/Mirror Admin
PS: Can you see why I was chosen to be the DNS Admin for this project? :-)
___
_On 9/5/2013 1:09 AM, Nicholas Chua wrote:
Hi,
But the specific error stated
Remote host said: 550-5.1.1 The email account that you tried to reach
does not exist.
Regards
Nic
On 5 Sep, 2013, at 12:45 PM, "ChandranManikandan" <[email protected]
<mailto:[email protected]>> wrote:
Hi Nic,
I have checked online to validate this email address is correct.
On Thu, Sep 5, 2013 at 12:21 PM, Nicholas Chua
<[email protected] <mailto:[email protected]>> wrote:
Hi,
Make sure the receiver address is correct
Regards
Nic
On 5 Sep, 2013, at 12:19 PM, "ChandranManikandan"
<[email protected] <mailto:[email protected]>> wrote:
Hi All,
One of our user send email to their clients and other user get
below bounce message and system administrator get the same
bounce message. How to avoid this issue. This problem come very
frequently. Please help me anyone.
I mentioned below message which i got.
Sender address is: [email protected] <mailto:[email protected]>
Sender Domain is: mail.xxxx.net <http://mail.xxxx.net>
Bounce message below.
Hi. This is the qmail-send program at mail.xxxx.net
<http://mail.xxxx.net>.
I tried to deliver a bounce message to this address, but the
bounce bounced!
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
74.125.25.26 does not like recipient.
Remote host said: 550-5.1.1 The email account that you tried to
reach does not exist. Please try
550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at
550 5.1.1
http://support.google.com/mail/bin/answer.py?answer=6596
dz4si19889772pbc.329 - gsmtp Giving up on 74.125.25.26.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
74.125.25.26 does not like recipient.
Remote host said: 550-5.1.1 The email account that you tried to
reach does not exist. Please try
550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at
550 5.1.1
http://support.google.com/mail/bin/answer.py?answer=6596
cr3si19952184pbc.20 - gsmtp Giving up on 74.125.25.26.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
207.5.72.155 does not like recipient.
Remote host said: 550 5.1.1 <[email protected]
<mailto:[email protected]>>: Recipient address rejected: User
unknown in relay recipient table Giving up on 207.5.72.155.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
198.57.229.105 does not like recipient.
Remote host said: 550 No such person at this address"
Giving up on 198.57.229.105.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
208.65.144.2 does not like recipient.
Remote host said: 553 Invalid recipient [email protected]
<mailto:[email protected]> (Mode: normal) Giving up on
208.65.144.2.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
50.79.55.225 does not like recipient.
Remote host said: 550 5.1.1 User unknown Giving up on 50.79.55.225.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
174.79.187.234 does not like recipient.
Remote host said: 550 5.1.1 User unknown Giving up on
174.79.187.234.
<[email protected]
<mailto:[email protected]>>:
User and password not set, continuing without authentication.
64.18.6.10 does not like recipient.
Remote host said: 550 No such user - psmtp Giving up on 64.18.6.10.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
64.26.60.153 does not like recipient.
Remote host said: 550 5.7.1 <[email protected]
<mailto:[email protected]>>: Recipient address rejected:
Invalid recipient Giving up on 64.26.60.153.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
65.254.254.50 does not like recipient.
Remote host said: 550 5.1.1 <[email protected]
<mailto:[email protected]>> recipient rejected Giving up
on 65.254.254.50.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
<[email protected] <mailto:[email protected]>>
63.250.193.253 failed after I sent the message.
Remote host said: 554 delivery error: dd This user doesn't have
a secureapptech.com <http://secureapptech.com> account
([email protected] <mailto:[email protected]>) [0]
- mta1018.biz.mail.gq1.yahoo.com
<http://mta1018.biz.mail.gq1.yahoo.com>
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
65.182.102.90 does not like recipient.
Remote host said: 550 5.1.1 <[email protected]
<mailto:[email protected]>>: Recipient address rejected:
itekcsi.com <http://itekcsi.com> Giving up on 65.182.102.90.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
207.45.187.34 does not like recipient.
Remote host said: 550 No Such User Here. Please email your
queries to [email protected] <mailto:[email protected]>."
Giving up on 207.45.187.34.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
173.164.132.210 does not like recipient.
Remote host said: 550 5.1.1 <[email protected]
<mailto:[email protected]>> User unknown; rejecting Giving up
on 173.164.132.210.
<[email protected]
<mailto:[email protected]>>:
User and password not set, continuing without authentication.
216.69.186.201 does not like recipient.
Remote host said: 550 #5.1.0 Address rejected.
Giving up on 216.69.186.201.
<[email protected] <mailto:[email protected]>>:
User and password not set, continuing without authentication.
216.69.186.201 does not like recipient.
Remote host said: 550 #5.1.0 Address rejected.
Giving up on 216.69.186.201.
--- Below this line is the original bounce.
Return-Path: <>
Received: (qmail 31267 invoked by uid 89); 5 Sep 2013 04:00:04 -0000
Received: by simscan 1.4.0 ppid: 31045, pid: 31249, t: 0.8400s
scanners: attach: 1.4.0 clamav: 0.97.8/m:54/d:17807
spam: 3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
mail.xxxx.net <http://mail.xxxx.net>
X-Spam-Level: ****
X-Spam-Status: No, score=4.4 required=10.0
tests=BAYES_50,EMPTY_MESSAGE,
HTML_MESSAGE,MISSING_MID,RDNS_NONE autolearn=no version=3.3.2
Received: from unknown (HELO jobdivabk.com
<http://jobdivabk.com>) (66.111.12.234)
by mail.xxxx.net <http://mail.xxxx.net> with SMTP; 5 Sep 2013
04:00:03 -0000
Received-SPF: pass (mail.xxxx.net <http://mail.xxxx.net>: SPF
record at jobdivabk.com <http://jobdivabk.com> designates
66.111.12.234 as permitted sender)
Received: from ([10.10.129.14])
by jobdivabk.com <http://jobdivabk.com> (L-Soft HDMail 2.1);
X-VirtualServerGroup: Default
X-MailingID: 00000::00000::00000::00000::00000::13294602
X-SMHeaderMap: mid="X-MailingID"
X-Mailer: L-Soft HDMail 2.1
X-Destination-ID: [email protected] <mailto:[email protected]>
X-SMFBL: c2l2YUBwYW5hc2lhZ3JvdXAubmV0
Content-Type: multipart/report; report-type=delivery-status;
boundary="41AB039EBB4.1102407491/mailer-strongmail"
MIME-Version: 1.0
Subject: "Undelivered Mail Returned to Sender"
Date: Wed, 04 Sep 2013 23:59:41 -0400
To: [email protected] <mailto:[email protected]>
From: [email protected] <mailto:[email protected]>
--41AB039EBB4.1102407491/mailer-strongmail
Content-Description: Notification
Content-Type: text/plain
"Did not reach the following recipient(s):"
[email protected]
<mailto:[email protected]> on Wed, 04 Sep 2013
23:59:41 -0400 [Message Expired]
--41AB039EBB4.1102407491/mailer-strongmail
Content-type: message/delivery-status
Reporting-MTA: dns; jobdivabk.com <http://jobdivabk.com>
Arrival-Date: Wed, 04 Sep 2013 12:27:02 -0400
Final-Recipient: RFC822; [email protected]
<mailto:[email protected]>
Action: failed
Status: 5.4.7
Diagnostic-Code: smtp; [Message Expired]
Last-Attempt-Date: Wed, 04 Sep 2013 23:59:41 -0400
--41AB039EBB4.1102407491/mailer-strongmail
Content-Description: Undelivered Message
Content-Type: message/rfc822
Date: Wed, 4 Sep 2013 11:39:07 -0400 (EDT)
From: Siva Kumar <[email protected] <mailto:[email protected]>>
To: [email protected]
<mailto:[email protected]>
Message-ID: <18446833.536691378309147581.JavaMail.oracle@batch_big1>
Subject: Websphere Message Broker Consultant needed in MA
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_53850_26605867.1378309147580"
-
--
*/Thanks & Best Regards,
Manikandan.C
/*
--
*/Thanks & Best Regards,
Manikandan.C
/*
--
PLEASE TAKE NOTE OF OUR NEW ADDRESS
===================================
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806
CALL TOLL FREE:
877-IT4SOHO
877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax
We have support plans for QMail!
