552 Requested mail action aborted: exceeded storage allocation

[Todd]

A company is getting this error whenever they send email
to my domain. I do not have any storage limits set nor am
I having problems getting email from anywhere else. Any
Ideas. Exchange 2003 sp1 on a 2003 server.

[Chris Scharff [MVP]]

In the last exciting episode, "Todd"
<anon...@discussions.microsoft.com> wrote:

Improperly configured secondary Mx record? Hard to say without knowing
the domain name.

[Todd]

I'm trying to recieve a monthly news letter. when the
company sends the message they recieve the following
error."552 Requested mail action aborted: exceeded storage
allocation"
I have no storage limits on my Exchange 2003 sp1 server.
When they send the mail without the HTML content I recieve
it. When they add the content it gets the error. Can
anyone help. this is a very important email that my
company needs to recieve. I can recieve at my hotmail
account so it has to be a problem on my server. Could it
be the amount or type of headers? I can't even find any
settings for this in Exchange. Any help would be very much
appreciated.

[Rich Matheisen [MVP]]

"Todd" <anon...@discussions.microsoft.com> wrote:

How big is the message? And how much space do you have on the disk
where the mailroot directory is found?

Are you sure that it's the Exchange server that's sending the 552
error and not somethng between the sender and your server? Exchange
wold normally add the extended DSN code after the 552 (something like
5.3.4).

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm

[todd]

Could my watchguard firbox III be sending that error? the
message is only 1 mb at most. I have plenty of disk space.
What in between the sender and my server would give the
552 error about storage allocation?
>.
>

[Rich Matheisen [MVP]]

"todd" <anon...@discussions.microsoft.com> wrote:

[ snip ]

>Could my watchguard firbox III be sending that error?

Maybe. It should be easy enough to check by using Outlook Express and
sending a large message directly to your Exchange server. If that
works, back up a step and send the same message to your external IP
address and see if it fails. If that works then the problem's not
under your control.

>the
>message is only 1 mb at most. I have plenty of disk space.
>What in between the sender and my server would give the
>552 error about storage allocation?

Any SMTP relay server between the e-mail client anf your Exchange
server.

If you use the SMTP protocol log you'll be able to see whether it's
your Exchange server sending the 552, or not.

[Michael Schipp]

hmmm, I am having the same problem, but I have a Watchguard Fireboox X 1000.

I am using the proxy SMTP and not the filtered SMTP - what about you?

All my searching so far has lead be to believe that it is the FB. We are
running 7.21 - you?

"todd" <anon...@discussions.microsoft.com> wrote in message
news:2a90301c46784$2d5d26c0$a501...@phx.gbl...

[jhdata]

See if this doesnt resolve your problem. It says its for 2003 Exchange
servers but you know how Microsoft is. Dr.Lizzardpoo

http://tinyurl.com/5o33c

Todd wrote:
> *I'm trying to recieve a monthly news letter. when the

> appreciated. *

--
jhdata
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message303357.html

[John Balsillie]

It's most likely your firewall. We had the same problem with people not
being able to send us messages with attachments over 2MB. Under was ok
but over caused the 552 message to be sent to the sender.

There were no limits set anywhere on the Exchange 2003 SP1 box however
it seems that Exchange likes to pump out this error message for a
variety of reasons.

As suggested by Rich, we tested by sending from within using Outlook
Express and no problems. This pointed therefore to the Firewall - a
Watchguard Firebox X700. We are using the proxy SMTP, not the filtered
SMTP object. We reduced (slightly) the security property rules on the
object and problem instantly fixed.

--
John Balsillie
------------------------------------------------------------------------
John Balsillie's Profile: http://www.msusenet.com/member.php?userid=2596
View this thread: http://www.msusenet.com/t-610388