Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Error 451 4.4.2 [internal] no BODY response

Updated: 12 Sep 2010 | 14 comments
wenfeng's picture
0 0 Votes
Login to vote

I recieved this error when i flush the mail. What does the error mean 451 4.4.2 [internal] no BODY response? How do i resolve this problem i see it in several different domains.

Discussion Filed Under:

Comments

AdnanH's picture
08
Dec
2009
1 Vote +1
Login to vote

Known issue in 8.0 versions prior to 8.0.3-11

If you are running an 8.0 version prior to 8.0.3-11, please take a look at the following KB article:

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

wenfeng's picture
09
Dec
2009
0 Votes 0
Login to vote

thanks will update and see

thanks will update and see

wenfeng's picture
09
Dec
2009
0 Votes 0
Login to vote

updated to teh stated version

updated to teh stated version sitll same problem. resending the email also gets stuck. Do i need to clear the older queues only resend or how?

Prashant Thumar's picture
09
Dec
2009
0 Votes 0
Login to vote

Its resolved.

Hi,

I was also facing same issue. But after upgrading the version to 8.0.3.11 it's resolved and I no more receives this error.

In your case you can try by sending mails after deleting older queue and check.

 

Regards,

Prashant Thumar

AdnanH's picture
10
Dec
2009
0 Votes 0
Login to vote

Thank you Prashant for

Thank you Prashant for confirming that upgrading to 8.0.3-11 resolve the issue for you.

Wenfeng, please note that the message that are already stuck in the queue prior to ugprade do not have the dot padding to properly deliver the message to receiving MTA.  The fix does not change the old messages in the queue, rather prevents the issue from happening with any new messages.  So as Prashant sugested, please delete the old messages from the queue and retest with new messages.

wenfeng's picture
10
Dec
2009
0 Votes 0
Login to vote

sadly for me it doesnt work

sadly for me it doesnt work deleted the old emails and re-email the attachment still the same problem for me

AdnanH's picture
10
Dec
2009
0 Votes 0
Login to vote

Hi wenfeng, If you are still

Hi wenfeng,

If you are still seeing the "451 4.4.2 [internal] no BODY response" error for re-sent messages, then it means that you were experiencing an issue different than the one described in the referenced KB.

Most likely the receiving servers are dropping the connection (may be due to policy reasons) when your SBG tries to send the attachment.

Detailed information about your deployment/environment, a packet capture and debug level logs are required to troubleshoot this issue, so I suggest that you open up case with support referencing this forum thread.

Regards,

Adnan

Prashant Thumar's picture
28
Dec
2009
0 Votes 0
Login to vote

Check network

Hi Wenfeng,

If you are still facing this issue do the following things.

Are you using any firewall in your network?
Please confirm outgoing mails flow Client >> Mail Server >> SBG >> Firewall >> Internet.

If it is just like this then check your firewall settings and disable the mail scan in that and then try to send the mail outside with attachments.

I hope this will help you to resolve your issue.

 

Regards,

Prashant Thumar

Don2's picture
14
Jan
2010
0 Votes 0
Login to vote

same problem

Hi,

We have the same problem.

We have the latest version 8.0.3-11 and have the configuration you mentioned Prashant (Client >> Mail Server >> SBG >> Firewall >> Internet). There is no mail scanning in the FW.

The curious thing is that our problem isn't domain specific but USER specific. We can send to some addresses within a domain but not to others!

Any idea what the problem may be?!?! It is very annoying!

Any help will be much appreciated.

Thanks,
Simon

AdnanH's picture
14
Jan
2010
0 Votes 0
Login to vote

Hi Simon, If you are seeing

Hi Simon,

If you are seeing the "451 4.4.2 [internal] no BODY response" error for those mails that are not being delivered, then it is most likely the other end that's dropping the connection.  As I said earlier, detailed information about your deployment/environment, a packet capture and debug level logs are required to troubleshoot this issue, so I suggest that you open up case with support referencing this forum thread.

Regards,

Adnan

Nik93's picture
08
Feb
2010
0 Votes 0
Login to vote

I upgrate version to 8.0.3-11

I upgrate version to 8.0.3-11 but it's not work.

AdnanH's picture
08
Feb
2010
0 Votes 0
Login to vote

Hi Nik93, As I said earlier

Hi Nik93,

As I said earlier in my comment above, that it could be the other end that's causing this problem.  It is best to open a support case and provide them with debug level logs and a packet capture when you are seeing this issue to indentify the root cause.

Thanks

Adnan

AdnanH's picture
22
Feb
2010
0 Votes 0
Login to vote

Hi wenfeng /Simon/Nik93, Were

Hi wenfeng /Simon/Nik93,

Were you able to open up a support case with packet capture and debug level logs? Are you still experiencing the issue?

Can you please provide some feedback?

Thanks

Adnan

AdnanH's picture
11
Mar
2010
0 Votes 0
Login to vote

Hi wenfeng /Simon/Nik93, Are

Hi wenfeng /Simon/Nik93,

Are you still experiencing this issue?  If so, can you please open up support case and if you have already opened up support case, please mention this forum thread to the support person and let them know that I have asked the case to be opened.

Thanks

Adnan