On Mon, 12 Mar 2012 14:48:45 +0000, FunnyGhost wrote: > > >Hi Folks, > >User not getting the Non Delivery Failure (NDR) message for his internal message, which has been blocked by McAfee's agent... > >One of our user brought to my attention that a message which has been sent to other user that never got delivered. Further to my investigation, McAfeeTxRoutingAgent which has been installed in our HUB servers causing this failure for particular attachment (Cobra_March_06_2012.bak zipped by rar file). I tested it by disabling this particular agent, it is getting delivered. Also, I have tested it by other rar file attachment, it is getting delivered successfully. > >I did the below test from my end; Original file size of Cobra_March_06_2012.bak is 261 MB. Using the WinRAR, if we do zip it became 13.1 MBUsing the WinRAR, zipped and tried sending the file Cobra_March_06_2012.bak,not delivered.Using the WinZip, if we do zip the Cobra_March_06_2012.bak file then it became 23.3 MBUsing the WinZip, zipped and tried sending the file Cobra_March_06_2012.bak,not delivered.Using the WinRAR, zipped other bak file with size 225 MB. After zip, the file size become 32.8 MB. Able to deliver this zipped bak file. > >From the above testing, there is no issues in send/receive mails with bak file using WinZip/WinRAR. In particular, this Cobra_March_06_2012.bak may be corrupt and hence the McAfeeTxRoutingAgent in the server wont allow this file to process further. > >My concern would be if someone sends a message (irrespective of content) and it fails for whatever reason, then the sender should be notified so they can try something different, otherwise you assume the receipient received the message. Fundamental feature of email! > >Does anyone knows, why the user haven't receive the Non Delivery Failure (NDR) message? Configure McAfee to send a notification to the sender that their message hasn't been delivered. It's their agent that swallowed the message and told Exchange "Nothing to see here! Move along!" --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

hi, >>>Does anyone knows, why the user haven't receive the Non Delivery Failure (NDR) message? I think because the Macfee agent isn't a exchange agent,it is a third party software. So if the message is rejected by the Macfee agent,the exchange server will not generate a NDR. If you want to get the NDR,you should enable the notification feature on the agent,if it have. >>>My concern would be if someone sends a message (irrespective of content) and it fails for whatever reason, then the sender should be notified so they can try something different, otherwise you assume the receipient received the message. Fundamental feature of email! Which client do you use. You can enable the delivery report on your client,if the message can't be sent to the recipient,the sender will not receive the report,i think this can help you to know the state of the message delivery. hope can help youCastinLu TechNet Community Support

Hi Folks, User not getting the Non Delivery Failure (NDR) message for his internal message, which has been blocked by McAfee's agent... One of our user brought to my attention that a message which has been sent to other user that never got delivered. Further to my investigation, McAfeeTxRoutingAgent which has been installed in our HUB servers causing this failure for particular attachment (Cobra_March_06_2012.bak zipped by rar file). I tested it by disabling this particular agent, it is getting delivered. Also, I have tested it by other rar file attachment, it is getting delivered successfully. I did the below test from my end; Original file size of Cobra_March_06_2012.bak is 261 MB. Using the WinRAR, if we do zip it became 13.1 MBUsing the WinRAR, zipped and tried sending the file Cobra_March_06_2012.bak,not delivered.Using the WinZip, if we do zip the Cobra_March_06_2012.bak file then it became 23.3 MBUsing the WinZip, zipped and tried sending the file Cobra_March_06_2012.bak,not delivered.Using the WinRAR, zipped other bak file with size 225 MB. After zip, the file size become 32.8 MB. Able to deliver this zipped bak file. From the above testing, there is no issues in send/receive mails with bak file using WinZip/WinRAR. In particular, this Cobra_March_06_2012.bak may be corrupt and hence the McAfeeTxRoutingAgent in the server wont allow this file to process further. My concern would be if someone sends a message (irrespective of content) and it fails for whatever reason, then the sender should be notified so they can try something different, otherwise you assume the receipient received the message. Fundamental feature of email! Does anyone knows, why the user haven't receive the Non Delivery Failure (NDR) message? ThanksFunnyghost

Issue: Internal users arent notify by the McAfee agent, if the attachment is get block in the agent. In the HUB servers, I have added the new DWORD value in the below path for this issue. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\McAfee\GroupShield for Exchange The above change has fixed the issue. Funnyghost

In this case, mails with the attachment is stuck with McAfee agent...it haven't processed to next level & also haven't declined by the McAfee agent. So if you choose the delivery option in outlook client, it won't let you whether the messages have been relayed/delivered/declined. Something, do with McAfee agent to get process the messages with that attachment or it should send back the user about the status (either delivered or failed) ThanksFunnyghost

On Mon, 12 Mar 2012 14:48:45 +0000, FunnyGhost wrote: > > >Hi Folks, > >User not getting the Non Delivery Failure (NDR) message for his internal message, which has been blocked by McAfee's agent... > >One of our user brought to my attention that a message which has been sent to other user that never got delivered. Further to my investigation, McAfeeTxRoutingAgent which has been installed in our HUB servers causing this failure for particular attachment (Cobra_March_06_2012.bak zipped by rar file). I tested it by disabling this particular agent, it is getting delivered. Also, I have tested it by other rar file attachment, it is getting delivered successfully. > >I did the below test from my end; Original file size of Cobra_March_06_2012.bak is 261 MB. Using the WinRAR, if we do zip it became 13.1 MBUsing the WinRAR, zipped and tried sending the file Cobra_March_06_2012.bak,not delivered.Using the WinZip, if we do zip the Cobra_March_06_2012.bak file then it became 23.3 MBUsing the WinZip, zipped and tried sending the file Cobra_March_06_2012.bak,not delivered.Using the WinRAR, zipped other bak file with size 225 MB. After zip, the file size become 32.8 MB. Able to deliver this zipped bak file. > >From the above testing, there is no issues in send/receive mails with bak file using WinZip/WinRAR. In particular, this Cobra_March_06_2012.bak may be corrupt and hence the McAfeeTxRoutingAgent in the server wont allow this file to process further. > >My concern would be if someone sends a message (irrespective of content) and it fails for whatever reason, then the sender should be notified so they can try something different, otherwise you assume the receipient received the message. Fundamental feature of email! > >Does anyone knows, why the user haven't receive the Non Delivery Failure (NDR) message? Configure McAfee to send a notification to the sender that their message hasn't been delivered. It's their agent that swallowed the message and told Exchange "Nothing to see here! Move along!" --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Which client do you use. You can enable the delivery report on your client,if the message can't be sent to the recipient,the sender will not receive the report,i think this can help you to know the state of the message delivery. I don't think so..it is related to client! Mail has been stuck in McAfee's agent itself..not yet reached the end user client (outlook) then how you enable to delivery report on the client..also..if it reaches the end user client then why we need to NDR? Please explain your view in brief... Thanks Funnyghost

hi, I mean which client do you use to send mail. Such as outlook2010. You should enable it on your side not on the end user side. If you use outlook to send mail,you can go to file->options->mail->tracking->check on the box delivery receipt confirming........ The purpose of enable the delivery report feature can help you get the message state. If you send mail fail,but you can't receive NDR,you can't know whether the mail is sent successful that also is your concern. But if you enable the feature,you or your sender can know whether you send mail successful. Receive the report,it means successful. Not receive the report,no matter what reason,it means fail. It isn't a solution to fix your MACfee agent issue which caused you can't receive NDR,but it is a workaround to help you know you send state when you can't receive the NDR. I hope you can understand my intentions hope can help you thanks, CastinLu TechNet Community Support

hi, >>>Does anyone knows, why the user haven't receive the Non Delivery Failure (NDR) message? I think because the Macfee agent isn't a exchange agent,it is a third party software. So if the message is rejected by the Macfee agent,the exchange server will not generate a NDR. If you want to get the NDR,you should enable the notification feature on the agent,if it have. >>>My concern would be if someone sends a message (irrespective of content) and it fails for whatever reason, then the sender should be notified so they can try something different, otherwise you assume the receipient received the message. Fundamental feature of email! Which client do you use. You can enable the delivery report on your client,if the message can't be sent to the recipient,the sender will not receive the report,i think this can help you to know the state of the message delivery. hope can help youCastinLu TechNet Community Support

hi, What i mean is to let your sender notice the mail state. If you send mail fail and you can't receive NDR as well, you can't know whether the mail is sent successful. But you say:My concern would be if someone sends a message (irrespective of content) and it fails for whatever reason, then the sender should be notified so they can try something different, otherwise you assume the receipient received the message. Fundamental feature of email! So if you enable the feature,you or your sender can know whether the mail is sent successful. Receive the report,it means successful. Not receive the report,no matter what reason,it means fail. Then your sender can try someting different. They will not assume the receipient received the message. hope can help you thanks,CastinLu TechNet Community Support