Hi Zac,
Sorry to hear it - couple of questions for you:
is there any more info in the MTA logs?  Do you have an example of one of the domains to which you're unable to send mail?  Were any changes made post upgrade or was it just a straight install.

Jason

Hi Zac,
Sorry to hear it - couple of questions for you:
is there any more info in the MTA logs?  Do you have an example of one of the domains to which you're unable to send mail?  Were any changes made post upgrade or was it just a straight install.

Jason

Hi Jason,

Thanks for the qucik response. Yes  below are the name of the domains

wataniya.com & crowneplaza.com.kw

No changes were made before or after the upgrade. The upgrade was straight from the brightmail.

Please find the MTA logs below: (I am not sure whether I can attach a file to the post and I couldn't find a way for it. So I am pasting the info here)

mail.wataniya.com 0 Apr  5 16:37:00 AST (info) ecelerity: [5320] DNSDS-00402 mail.wataniya.com 1 Apr  5 16:37:00 AST (info) ecelerity: [5320] MQ-00552 no recyclables for #sms#0000004c 2009 Apr  5 16:37:00 AST (notice) ecelerity: [5320] MQ-00560 #sms#0000004c 0 0 0 Apr  5 16:37:00 AST (info) ecelerity: [5320] MQ-00628 #sms#0000004c binding 2 2009 Apr  5 16:36:45 AST (notice) ecelerity: [5320] MQ-00560 #sms#00000000 1 1 1 Apr  5 16:36:45 AST (notice) ecelerity: [5320] MQ-00560 #sms#00000000 0 0 0 Apr  5 16:37:00 AST (info) ecelerity: [5320] MQ-00610 #sms#0000004c binding 0 2009 Apr  5 16:36:45 AST (info) ecelerity: [5320] DNSDS-00402 cpkwtmail.crowneplaza.com.kw 0 Apr  5 16:36:45 AST (info) ecelerity: [5320] DNSDS-00402 cpkwtmail.crowneplaza.com.kw 1 Apr  5 16:36:45 AST (info) ecelerity: [5320] MQ-00552 no recyclables for #sms#00000000 2009 Apr  5 16:36:45 AST (notice) ecelerity: [5320] MQ-00560 #sms#00000000 0 0 0 Apr  5 16:36:45 AST (info) ecelerity: [5320] MQ-00628 #sms#00000000 binding 2 2009 Apr  5 16:36:45 AST (notice) ecelerity: [5320] MQ-00560 #sms#0000004c 1 1 1 Apr  5 16:36:45 AST (notice) ecelerity: [5320] MQ-00560 #sms#0000004c 0 0 0 Apr  5 16:36:45 AST (info) ecelerity: [5320] MQ-00610 #sms#00000000 binding 0 2009 Apr  5 16:36:45 AST (info) ecelerity: [5320] DNSDS-00402 mail.wataniya.com 0 Apr  5 16:36:45 AST (info) ecelerity: [5320] DNSDS-00402 mail.wataniya.com 1 Apr  5 16:36:45 AST (info) ecelerity: [5320] MQ-00552 no recyclables for #sms#0000004c 2009 Apr  5 16:36:45 AST (notice) ecelerity: [5320] MQ-00560 #sms#0000004c 0 0 0 Apr  5 16:36:45 AST (info) ecelerity: [5320] MQ-00628 #sms#0000004c binding 2 2009 Apr  5 16:36:30 AST (notice) ecelerity: [5320] MQ-00560 #sms#00000000 1 1 1 Apr  5 16:36:30 AST (notice) ecelerity: [5320] MQ-00560

Zac.

Hi Jason,

Hope you will come up with a solution soon.I am having a real tough time to slove it.

Zac.

Hi Zac,

Just tested sending outbound messages to both of these domains and I'm not having issues with either.  What queue are you actually seeing these messages in?  The log files you pasted aren't very useful, as they aren't capturing the point in time the message is being sent.  You'll probably also want to bump up the logs to debug as it contains more useful info for troubleshooting, it looks like you only have the MTA logs set to info at the moment.  I've captured sending to both domains with my MTA logs debugged, drop me a PM with your email address and I'll send them on to you so you can compare.

Cheers,

Kevin

Hi Zac,

You should find this resolved by the update that shipped yesterday, 8.0.1.
https://www-secure.symantec.com/connect/articles/s...

HTH

//ian

Mail error 421 4.4.0 [internal] "no MXs for this domain could be reached at this time."

Cause:
This problem has been reported to Symantec Technical Support. At this time, the exact cause or contributing factors to this problem have not been determined. We will update this document when new information or a solution is found.

Possible circumstances that could cause this issue and under investigation:

Masked mail banner - similar to the one found in Cisco Pix Mailguard/SMTP Fixup

Issue with PTR or RDNS enforcement

Invalid Response

Actual Mail Exchange (MX) record(s) missing

DNS query failure for calls larger than 512 bytes

Microsoft KB 828263: http://support.microsoft.com/kb/828263

Upgraded to 8.0.1-7 to enable bounce back Attack!

Since then we always have 10-15 Emails in delivery Queue!

Half of them are destinated and deferred to Yahoo???

Any one have a solution for this???

Greatly Appreciated

Charles
 Status: 4.0.0
Action: delayed
Last-Attempt-Date: Thu, 04 Jun 2009 13:55:38 -0400
Diagnostic-Code: smtp; 451 4.4.2 [internal] connection closed by remote host

X-AuditID: ac10010b-b7b08ae0000043ff-f7-4a27d25a8b56
Received: from mkt-exch-02.ketel.com (Unknown_Domain [192.168.1.232])
by mkt-sms.marketel.com (Symantec Mail Security) with SMTP id DE.96.17407.A52D72A4; Thu, 4 Jun 2009 09:55:38 -0400 (EDT)
Received: from mkt-exch-01.marketel.com ([192.168.1.231]) by mkt-exch-02.ketel.com with Microsoft SMTPSVC(6.0.3790.3959);
Thu, 4 Jun 2009 09:57:44 -0400
Received: from 192.168.0.4 ([192.168.0.4]) by mkt-exch-01.marketel.com ([192.168.1.231]) with Microsoft Exchange Server HTTP-DAV ;
Thu, 4 Jun 2009 13:57:44 +0000
User-Agent: Microsoft-Entourage/12.17.0.090302
Date: Thu, 04 Jun 2009 09:55:37 -0400
Subject: Unity
From: Simon Gauvin <simon.gauvin@ketel.com>
To: Martin Lavoie <martin.lavoie@tel.ca>
Message-ID: <C64D4A99.44E2%simon.gauvin@ketel.com>
Thread-Topic: Unity
Thread-Index: AcnlHCM/8MCRPla9sk+yaDZyeOWRDA==
Mime-version: 1.0
Content-type: multipart/related;
boundary="B_3326954137_537183"
Return-Path: simon.gauvin@ketel.com
X-OriginalArrivalTime: 04 Jun 2009 13:57:44.0497 (UTC) FILETIME=[6F3E5210:01C9E51C]
X-Brightmail-Tracker: AAAAAA==

Does the public IP address of your sending SBG appear in any blacklists?
Check here - symantec.com/brightmail/iqservices

Hope that helps.

//ian

Hello every1,

The error basically come when you didnt define the destination address, kindly go to:

Administration-->Configuration-->edit host-->Smtp-->Advanced-->at the bottom destination address binding here we need to define the IP address.

After changing from from Auto the problem will get resolved.

 HI Ian and Laeek!

I"ve checked our Blaclisting Status and everything is fine, Althought at one time last week our  ISP Backup MX (2nd in preference) was blacklisted on Barracuda last Week.

This may Explain why we have some Yahoo Deferred Email, Now they are gone since 48 Hours.

As for the binding in SMTP Advanced everything is fixed IP Not Auto!

The path we are following is (the DNS query failure for calls larger than 512 bytes)
Since we have Cisco Firewall ASA5005 we're looking in that direction for now.

Thanks for your support!
Greatly Appreciated!

Charles

Hi,

Even I have similar problems with some domains. This is another error which I am facing while sending email to some domain. My SMS runs on 8.0.1-7.

451 4.4.2 [internal] send HELO/EHLO failed

Anybody had got any solution for this?

...rOjU...

The fix we'ved used is to turn off 8-bit MIME advertisement. Go into Protocols > Settings > uncheck 8-bitMIME advertisement. It only occurred to one e-mail domain but was a vital vendor that our company did business with that could not handle SBG's 8bit MIME and reverting to 7bit MIME worked. See info and link below.

http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

Handling of messages containing 8-bit MIME
If Symantec Brightmail Gateway versions 8.0.0 and 8.0.1 received messages containing 8-bit MIME and delivered them to an MTA that cannot handle 8-bit MIME, upon reception the contents may have been malformed. The MTA in Symantec Brightmail Gateway 8.0.2 has been updated to convert messages to quoted-printable encoding when delivering messages to MTAs that cannot handle 8-bit MIME.

If you still encounter issues with Symantec Brightmail Gateway delivering 8-bit MIME messages to MTAs that cannot handle 8-bit MIME, you can force the sending MTA to convert messages containing 8-bit MIME to 7-bit MIME. In Symantec Brightmail Gateway 8.0.1, a check box was added to the following Control Center page:
Protocols > SMTP > Settings. The check box is titled Do not advertise 8BITMIME.
Enable this setting to force the sending MTA to convert messages containing 8-bit MIME to 7-bit MIME. The online help and Administration Guide have not been updated to describe this new setting.