I have an issue where my Dell Equallogic SAN is attempting to send email to my HUB server but a few mails make it through and some do not. According to Equallogics documents I am to disable tarpitting on the receive connector, which I did and still I'm not getting all my messages. The second work around is listed below but I'm not sure the command to do what they are asking. Any assistance would be appreciated. I already have the receive connector created called "SAN Email Connector" #2. Create a new Receive connector specifically for the Equallogic array. Disable the advertising of Chunking and Binary Mime on this connector. This should prevent any sending server from using the BDAT verb against Exchange, and should cause them to default to the DATA command instead. Since there is not a BDAT command on the wire, Exchange should not tarpit, and the mail should deliver. Thanks RS

check this http://technet.microsoft.com/en-us/library/bb125140.aspx

Please check this Summary Transport Neutral Encapsulation Format (STNEF) STNEF is equivalent to TNEF. However, STNEF messages are encoded differently than TNEF messages. Specifically, STNEF messages are always MIME-encoded and always have a Content-Transfer-Encoding value of Binary. Therefore, there's no plain text representation of the message, and there's no distinct Winmail.dat attachment contained in the body of the message. The whole message is represented by using only binary data. Messages that have a Content-Transfer-Encoding value of Binary can only be transferred between SMTP messaging servers that support and advertise the BINARYMIME and CHUNKING SMTP extensions as defined in RFC 3030. The messages are always transferred between SMTP messaging by using the BDAT command, instead of the standard DATA command. from -> http://technet.microsoft.com/en-us/library/bb232174.aspx

So disabling chunking and BinaryMime will fix this issue then? I understand kindof what is said above. The mails that I'm getting through are in plain txt and the attachement is in the txt as garbage... So, If it use the set-receiveconnetor to disable both BinaryMimeEnabled and ChunkingEnabled that is what this work around is referring? Thanks R

I beleive yes.,., Please check it and you can always revert back to original settings "The whole message is represented by using only binary data. Messages that have a Content-Transfer-Encoding value of Binary can only be transferred between SMTP messaging servers that support and advertise the BINARYMIME and CHUNKING SMTP extensions as defined in RFC 3030. The messages are always transferred between SMTP messaging by using the BDAT command, instead of the standard DATA command" Disabling binarymime and Chunking should prevent BDAT command and DATA command should be used .