hi, appreciate if can give some pointers to why this message is appearing intermittently. From: Microsoft Outlook Sent: Wednesday, 5 September, 2012 12:14 PM To: Rozita Subject: Undeliverable: RE: Symantec Backup Exec User: fnsrvlx4.fnbs.net.my rejected your message to the following e-mail addresses: Dexter Ng <cfng@glocomp.net> (cfng@glocomp.net) (cfng@glocomp.net) fnsrvlx4.fnbs.net.my gave this error: <cfng@glocomp.net>: Relay access denied Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery. Diagnostic information for administrators: Generating server: EX01.ingenuity.com.my cfng@glocomp.net fnsrvlx4.fnbs.net.my #554 5.7.1 <cfng@glocomp.net>: Relay access denied ## Original message headers: Received: from EX01.ingenuity.com.my ([10.10.10.11]) by EX01 ([10.10.10.11]) with mapi; Wed, 5 Sep 2012 12:13:28 +0800 From: Rozita <rozita@ingenuity.com.my> To: "Dexter Ng <cfng@glocomp.net> (cfng@glocomp.net)" <cfng@glocomp.net> Subject: RE: Symantec Backup Exec User: Thread-Topic: Symantec Backup Exec User: Thread-Index: Ac2LDPktSIMj+K51QUSNQTAoDXdhSwADBSyAAABTFRAAAHK20AAAJ67Q Date: Wed, 5 Sep 2012 04:13:26 +0000 Message-ID: <65F7E0ABC77D9442A995E40C75480DCE320ED98E@EX01> References: <004401cd8b1a$8cc25910$a6470b30$@com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Content-Type: multipart/related; boundary="_005_65F7E0ABC77D9442A995E40C75480DCE320ED98EEX01_"; type="multipart/alternative" MIME-Version: 1.0 thanks.

The server generating the NDR is trying to send a message to a server that does not recognize the recipient's e-mail address and it is not configured to allow relay. Without context, that's all I can tell you. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

may i know what other information you need to diagnose the issue? thanks as i am new in this area.

On Wed, 5 Sep 2012 06:40:07 +0000, Andrew5421 wrote: >may i know what other information you need to diagnose the issue? Check your SMTP Send protocol logs and verify that the IP address you're sending that message to is one of those that are found in the set of MX records for the domain. Some domains forget they have a secondary (or tertiary) set of MX records when the move to a new ISP. If your server tries to connect to the primary MX for the domain and it isn't successful it will try the secondary MX. Domains almost always publish the domain name in an "A" record, too. If the DNS MX resolution fails the fallback is to try the "A" record. If that IP address isn't a SMTP server it may be configured to respond in the way you've encountered. >thanks as i am new in this area. The domain glocomp.net has three sets of MX records. Only the one with weight "0" has an associted server name in the glocomp.net domain. I'd guess that the other MXs in the fnbs.net.my domain are either incorrectly configured or they've been abandoned by the glocomp.net domain and they need to clean up their DNS. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks, i believe i have found out the problem. Seems like they are under the blacklisted list.

hi, Very glad to hear that. Please remember to mark as answer. thanks,CastinLu TechNet Community Support