Tulsaconnect enforced the limit on that message. Feel free to send me a large attachment if you want to test to be sure.
From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 AM To: MS-Exchange Admin Issues Subject: little help understanding header info I have been asked a number of times by owners to adjust the email size limit up so pictures of grand-babies will not be blocked or filtered off. Our email is routed through our ISP/Datacenter before being handed off to a Brightmail filter, then forwarded to the appropriate exchange server. The 10.1.9.8 address is the internal address of said filter. I should have called them before I posted this, I know, but I would rather stick a fork in my head... Can anyone tell from this header if it is MY problem, either with an exchange setting I have overlooked or a problem with the filter? TulsaConnect has assured me they are enforcing size limits on email. 10 meg seems to be the limit at this point, although I have opened up everything on our end considerably higher than that. thanks for any help. I'm just asking for help understanding the contents of this bounce please, unless you can determine from the content of the header that this may be an exchange problem... thanks for any help: ----- The following addresses had permanent fatal errors ----- <xx...@companymail.com<mailto:xx...@companymail.com> > (reason: 552 message size exceeds fixed maximum message size) ----- Transcript of session follows ----- ... while talking to [67.214.102.28]: >>> MAIL From:<xxxxx...@yahoo.com<mailto:xxxxx...@yahoo.com>> SIZE=30433191 <<< 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; mscan4.tulsaconnect.com<http://mscan4.tulsaconnect.com> Received-From-MTA: DNS; localhost.localdomain Arrival-Date: Fri, 6 May 2011 09:19:39 -0500 Final-Recipient: RFC822; xx...@companymail.com<mailto:xx...@companymail.com> Action: failed Status: 5.3.4 Diagnostic-Code: SMTP; 552 message size exceeds fixed maximum message size Last-Attempt-Date: Fri, 6 May 2011 09:21:19 -0500 Return-Path: xxxx...@yahoo.com<mailto:xxxx...@yahoo.com>> Received: from mscan4.tulsaconnect.com<http://mscan4.tulsaconnect.com> (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com<http://mscan4.tulsaconnect.com> (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com<mailto:xxx...@companymail.com>>; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com<http://omp1029.access.mail.sp2.yahoo.com> (omp1029.access.mail.sp2.yahoo.com<http://omp1029.access.mail.sp2.yahoo.com> [98.139.44.92]) by mscan4.tulsaconnect.com<http://mscan4.tulsaconnect.com> (mscan4.tulsaconnect.com<http://mscan4.tulsaconnect.com> [67.214.101.67]) envelope-from <xxx...@yahoo.com<mailto:xxx...@yahoo.com>> with SMTP id n459Jd1776718739ZQ ret-id none; Fri, 06 May 2011 09:19:39 -0500 Received: (qmail 96059 invoked by uid 1000); 6 May 2011 14:19:38 -0000 Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com<http://yahoo.com>; s=s1024; t=1304691561; bh=pn4FE+SR65YTvA5pXDzmFkRoVIIF7uaA7DxpPitMJ10=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=ri21sjwBmDXi5wwM5pxe0cW+CDbqYGUoouCXCp41ddc86JiGHLRP5/dwFZvTkrzestPC0F/y5ZT95TRn1OEvbqgQxmeiYaHMlbGR4gMiVI59ejEmkpAAUbmNUtURCLE5cHNexwRUvOogoMG8IJbHQV3+his6o1WUsTr3lHoXtyk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com<http://yahoo.com>; --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist