Link to home
Start Free TrialLog in
Avatar of jp_tech
jp_tech

asked on

User is having problems receiving large pdf files

We have a SBS 2008 server with Exchange 2007, with about 45 mailboxes.  We suscribe to Spam Soap which is MX Logic technology to filter our mail for spam.  One of our customers is trying to send one of our employees an 8mb pdf file, the message gets kicked back and the user gets an undileverable error.  To test I sent an 8mb pdf from an external address and more or less got the same error he did.  I checked the Spam Soap Console and there are no restrictions set for the pdf file type or size and I added the senders domain to the global accept list.   In Exchange I increased the send and receive size for the employees mailbox.  Below is the message I get.  Any ideas if this is an Exchange issue or is it the Spam service?


message cannot be delivered to the following recipients:

  Recipient address: jpichardo@cablelot.com 
  Reason: SMTP transmission failure has occurred
  Diagnostic code: smtp;552 Backend Replied [311e26b4.0.1174879.00-378.2047162.p02c11m113.mxlogic.net]: 5.3.4 Message size exceeds fixed maximu
  Remote system: dns;cablelot.com.inbound15.mxlogic.net (TCP|167.206.4.198|64502|208.65.144.12|25)
ASKER CERTIFIED SOLUTION
Avatar of MCSA2003
MCSA2003
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It's probably a size limitation on MXlogic.  Can you send that same PDF withing exchange locally?
from my experience with exchange 2003, there are multiple places to set the actual maximum receiving limit within the exchange organization. i've had a change to use exchange 2007 for a little and its definitely different and just a tad bit more complicated. with that said, check out the below link, i think it will have all the info to point you in the right direction.

http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/exchange-2007-message-size-limits.html
here's an additional link with some very good info and instructions on how to set custom limits as well.

http://blogs.technet.com/sbs/archive/2008/10/28/how-do-i-change-message-size-limits-in-exchange-2007.aspx
Avatar of jp_tech
jp_tech

ASKER

I was able to send the 8mb file internally without any errors.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jp_tech

ASKER

ok I will look over those links and apply changes.  I sent the same file to an outside user that uses the same filtering service and this is the message I got.

This message was created automatically by mail delivery software.

A message that you have sent could not be delivered to one or more
recipients.  This is a permanent error.  The following address(es) failed:

  <jim@virtualadministrator.com>: 552 Backend Replied [f68f26b4.d5e4db90.1481095.00-503.2682220.p02c11m102.mxlogic.net]: 5.3.4 Message size exceeds fixed



Included is a copy of the message header:
-----------------------------------------
Received: from unknown [64.18.1.37] (HELO exprod6og116.obsmtp.com)
        by p02c11m102.mxlogic.net(mxl_mta-6.5.0-0)
        with SMTP id 286f26b4.0.1449023.00-303.2621423.p02c11m102.mxlogic.net (envelope-from <jpichardo@cablelot.com>);
        Fri, 29 Jan 2010 07:53:57 -0700 (MST)
Received: from source ([75.99.68.210]) (using TLSv1) by exprod6ob116.postini.com ([64.18.5.12]) with SMTP
        ID DSNKS2L2TGioFNlBiWZ4We1SFXXjOsEy2FXI@postini.com; Fri, 29 Jan 2010 06:53:03 PST
Received: from SERVER01.domain01.local ([fe80::561:9b6b:e65a:6b77]) by
 SERVER01.domain01.local ([fe80::561:9b6b:e65a:6b77%10]) with mapi; Fri, 29
 Jan 2010 09:53:43 -0500
From: Jose Pichardo <JPichardo@cablelot.com>
To: "jim@VirtualAdministrator.com" <jim@VirtualAdministrator.com>
Date: Fri, 29 Jan 2010 09:52:34 -0500
Subject: FW: test internal
Thread-Topic: test internal
Thread-Index: AQHKoO7SZW9g9groeU+T2VP5J0g/zpGso4R5
Message-ID: <963283771C370947BC30EF1103C307CE5889A8DFDC@SERVER01.domain01.local>
References: <963283771C370947BC30EF1103C307CE5889A8DFDA@SERVER01.domain01.local>
In-Reply-To: <963283771C370947BC30EF1103C307CE5889A8DFDA@SERVER01.domain01.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/mixed;
        boundary="_004_963283771C370947BC30EF1103C307CE5889A8DFDCSERVER01domai_"
MIME-Version: 1.0
Avatar of jp_tech

ASKER

Do any of you know if you have to restart the mail services after you change global message limits size?
Have you looked at the mxlogic.net settings yet? It looks like that's where it's giving the max size limit error.
Avatar of jp_tech

ASKER

I did check the MXlogic settings, I even opened up a service request with them.  They say that everything is ok on their end, all the settings are configured to allow the file type and unlimited size.  The next step is to change the global settings at the hub transport level then test some more.  The mistake I made was changing the users mailbox size, but as I read in the links provided that Global settings override individual mailbox settings.
Avatar of jp_tech

ASKER

Thx guys for your help.
We have the same problem with MXLogic with Several different clients and the same response is what we are getting. The actual Tech from MXLogic stated the 552 Backend Replied says that the mail server is denying it. MXlogic just got purchased by MACAFEE and there has been little issues all over because of it. All limits on our Exchange Enterprise are set to no limits or are at 50MB's and also the MXLogic settings are set to Any Size and we are still getting the problem. I might think that a reboot of the server might help.
We're having the same issue (Thank God for Experts Exchange!).  Our Exchange 2007 limits are capped at 50M for sending or receiving, unlimited on the MX Logic side and we're having the same issue.
Hey guys. I am also receiving this NDR and I'm using SpamSoap. Can we safely determine that this is a SpamSoap issue?

Thank you for your help.