We use XWall for a SPAM filter. The XWall server accepts the email from this person fine but when it forwards it on to Exchange 2007 the following errors come up in the log on the XWall pertaining to the transfer of the email from XWall to Exchange. 09-04-02 14:08:30 0807: Connecting with Exchange at 10.0.*.* Port:25 09-04-02 14:08:30 0807: Connection established with Exchange 10.0.*.*[10.0.*.*] 09-04-02 14:08:30 0807: < 220 webmail.*.* Microsoft ESMTP MAIL Service ready at Thu, 2 Apr 2009 14:08:22 -0700 09-04-02 14:08:30 0807: > HELO mx1.*.* 09-04-02 14:08:30 0807: < 250 webmail.*.* Hello [10.0.*.*] 09-04-02 14:08:30 0807: > MAIL FROM:<sales@*.com> 09-04-02 14:08:30 0807: < 250 2.1.0 Sender OK 09-04-02 14:08:30 0807: > RCPT TO:<*@*.com> 09-04-02 14:08:30 0807: < 250 2.1.5 Recipient OK 09-04-02 14:08:30 0807: > DATA 09-04-02 14:08:30 0807: < 354 Start mail input; end with <CRLF>.<CRLF> 09-04-02 14:08:35 0807: < 554 5.6.1 Messages of type message/partial are not supported 09-04-02 14:08:35 0807: Sending DSN (type failed) 5.2.1 (Mailbox exists but is disabled) to sales@******.com Any idea how to allow this content type, As far as i know i dont have any content filtering turned on for the Exchange server becuase we control it all on the XWall.

Hi,Is this issue occuring when messaging coming from any specific users or any specific source IP, If yes then you need to Set up a receive connector in your Hub that allows un-authenticated connections (andno TLS) from coming mail of this source IPPlease look for "How to create receive connector"http://technet.microsoft.com/en-us/library/bb124327.aspxhttp://technet.microsoft.com/en-us/library/aa996395.aspxAnil

It is only happening when this one person is sending an email to anyone inside the company. The SPAM filter already is sending email to an internal unauthenticated RC and has no issue receiving email from any other external source.

Hi,Did you use "break apart messages" feature in the client side when sending the email?If it is, please understand that is by design in the product due to security concerns since using message/partial could be a way for spammers. For this reason, the decision was made to block these types of messages entirely in Exchange 2007.ThanksAllen

It was just for one vendor so we just had him send the email to the staffs personal email. I agree that this should be blocked and dont want to unblock but if for some reason in the future i dont have a choice and need to how would i go about doing it?

Hi,I think the reason for breaking apart messages is the message size which exceedes the limit ofthe Exchange server. Thus, to work around this issue, we need to increase the message size of the Exchange server in order to no need to use break apart message feature for the client.ThanksAllen

Hi, We have the same problem with our copier / scanner that sends the pdf documents in mailboxes ... How to create a connector that accepts these documents?

Has anyone resolved this issueI have the same problem with some Toshiba MFP'sWill this work with authenticated SMTP access??Jens

In the network settings on the webpage of the copier set the smtp email to not break apart, on the Bizhub it is called Binary Division, turn that feature off. We had a new unit installed and the installer were pointing fingers at our exchange server, and I agree it was stopping the email but because it was seen as spammer activity, thus I would never alter an exchange server to allow that activity unless you want to be spammed into non-operation! So turn off the feature and it will work fine after that, you may need to increase the size settings on the exchange hub transport that handles the traffic if you have large pdf's attached. But if you have binary division on no amount of size expansion will fix the issue as it is an illegal mail message format to exchange. I had to route the traffic through another smtp server so I could monitor the network traffic and setup an NDR email to me the message was the not supported message above.