Re: little help understanding header info
I don't think I said that. (if I did, it was my keyboard's fault)! TC has asserted all along that they enforce NO size limits on email. On Fri, May 6, 2011 at 12:49 PM, Joseph Heaton jhea...@dfg.ca.gov wrote: You say that your TulsaConnect IS enforcing size limits, and you're not. So, besides everything in the header referencing TulsaConnect, I would still be leaning towards at least finding out what their limit is that they're enforcing, and whether or not you can get them to raise that limit. Jeff Brown 2jbr...@gmail.com 5/6/2011 7:49 AM 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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 --- 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 --- 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
RE: little help understanding header info
I wouldn't think it would make any difference in the scenario you described. JPG files are already compressed. If you try to zip a jpg, it actually gets bigger. From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Wednesday, May 11, 2011 8:03 AM To: MS-Exchange Admin Issues Subject: Re: little help understanding header info Wow, is it really possible that the uncompressed size of the attachment is what counts in the over-all size limit That changes things DRAMATICALLY!!! On Mon, May 9, 2011 at 2:00 PM, Cameron cameron.orl...@gmail.commailto:cameron.orl...@gmail.com wrote: Wouldn't happen to be some sort of a .docx/.xlsx/etc type of file would it? I had the same sort of thing drive me crazy until I found out that an 8mb .xlsx file (well within our limits) actually translated to a 57mb expanded file (try using winzip to unzip the file to see it's *true* size). On Fri, May 6, 2011 at 10:56 AM, Campbell, Rob rob_campb...@centraltechnology.netmailto:rob_campb...@centraltechnology.net wrote: From those headers it appears that Exchange was willing to send an email that size, but the server at tulsaconnect.comhttp://tulsaconnect.com/ [67.214.102.28] wouldn't accept it. From: Jeff Brown [mailto:2jbr...@gmail.commailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 9: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.commailto: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:x...@yahoo.commailto:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com/ Received-From-MTA: DNS; localhost.localdomain Arrival-Date: Fri, 6 May 2011 09:19:39 -0500 Final-Recipient: RFC822; xx...@companymail.commailto: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: ...@yahoo.commailto:...@yahoo.com Received: from mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com/ (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com/ (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.commailto:xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.comhttp://omp1029.access.mail.sp2.yahoo.com/ (omp1029.access.mail.sp2.yahoo.comhttp://omp1029.access.mail.sp2.yahoo.com/ [98.139.44.92]) by mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com/ (mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com/ [67.214.101.67]) envelope-from xxx...@yahoo.commailto: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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.comhttp://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.comhttp://yahoo.com/; --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: little help understanding header info
To answer your question, the offending rejected email is almost always jpegs... grandbaby pics. we have tested using jpegs and a collection of pdf's and other random files compressed together in one attachment. On Mon, May 9, 2011 at 2:00 PM, Cameron cameron.orl...@gmail.com wrote: Wouldn't happen to be some sort of a .docx/.xlsx/etc type of file would it? I had the same sort of thing drive me crazy until I found out that an 8mb .xlsx file (well within our limits) actually translated to a 57mb expanded file (try using winzip to unzip the file to see it's *true* size). On Fri, May 6, 2011 at 10:56 AM, Campbell, Rob rob_campb...@centraltechnology.net wrote: From those headers it appears that Exchange was willing to send an email that size, but the server at tulsaconnect.com [67.214.102.28] wouldn’t accept it. *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Friday, May 06, 2011 9: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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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 ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana
Re: little help understanding header info
If they are straight .jpg attachments then I agreebutI have had users drop pictures into word documents and had this issue. I know that Vipre for Exchange actually *does* look at the uncompressed size when determining whether or not to let it through. On Wed, May 11, 2011 at 9:08 AM, Campbell, Rob rob_campb...@centraltechnology.net wrote: I wouldn’t think it would make any difference in the scenario you described. JPG files are already compressed. If you try to zip a jpg, it actually gets bigger. *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Wednesday, May 11, 2011 8:03 AM *To:* MS-Exchange Admin Issues *Subject:* Re: little help understanding header info Wow, is it really possible that the uncompressed size of the attachment is what counts in the over-all size limit That changes things DRAMATICALLY!!! On Mon, May 9, 2011 at 2:00 PM, Cameron cameron.orl...@gmail.com wrote: Wouldn't happen to be some sort of a .docx/.xlsx/etc type of file would it? I had the same sort of thing drive me crazy until I found out that an 8mb .xlsx file (well within our limits) actually translated to a 57mb expanded file (try using winzip to unzip the file to see it's *true* size). On Fri, May 6, 2011 at 10:56 AM, Campbell, Rob rob_campb...@centraltechnology.net wrote: From those headers it appears that Exchange was willing to send an email that size, but the server at tulsaconnect.com [67.214.102.28] wouldn’t accept it. *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Friday, May 06, 2011 9: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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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 ** Note: The information contained in this message may be privileged and confidential and protected from disclosure
Re: little help understanding header info
I wonder if my Brightmail filter is guilty of this behavior, but it LOOKS like it's actually exchange, not Brightmail that is refusing the message. On Wed, May 11, 2011 at 9:15 AM, Cameron cameron.orl...@gmail.com wrote: If they are straight .jpg attachments then I agreebutI have had users drop pictures into word documents and had this issue. I know that Vipre for Exchange actually *does* look at the uncompressed size when determining whether or not to let it through. On Wed, May 11, 2011 at 9:08 AM, Campbell, Rob rob_campb...@centraltechnology.net wrote: I wouldn’t think it would make any difference in the scenario you described. JPG files are already compressed. If you try to zip a jpg, it actually gets bigger. *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Wednesday, May 11, 2011 8:03 AM *To:* MS-Exchange Admin Issues *Subject:* Re: little help understanding header info Wow, is it really possible that the uncompressed size of the attachment is what counts in the over-all size limit That changes things DRAMATICALLY!!! On Mon, May 9, 2011 at 2:00 PM, Cameron cameron.orl...@gmail.com wrote: Wouldn't happen to be some sort of a .docx/.xlsx/etc type of file would it? I had the same sort of thing drive me crazy until I found out that an 8mb .xlsx file (well within our limits) actually translated to a 57mb expanded file (try using winzip to unzip the file to see it's *true* size). On Fri, May 6, 2011 at 10:56 AM, Campbell, Rob rob_campb...@centraltechnology.net wrote: From those headers it appears that Exchange was willing to send an email that size, but the server at tulsaconnect.com [67.214.102.28] wouldn’t accept it. *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Friday, May 06, 2011 9: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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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
Re: little help understanding header info
Wouldn't happen to be some sort of a .docx/.xlsx/etc type of file would it? I had the same sort of thing drive me crazy until I found out that an 8mb .xlsx file (well within our limits) actually translated to a 57mb expanded file (try using winzip to unzip the file to see it's *true* size). On Fri, May 6, 2011 at 10:56 AM, Campbell, Rob rob_campb...@centraltechnology.net wrote: From those headers it appears that Exchange was willing to send an email that size, but the server at tulsaconnect.com [67.214.102.28] wouldn’t accept it. *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Friday, May 06, 2011 9: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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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 ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** --- 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 --- 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
RE: little help understanding header info
From those headers it appears that Exchange was willing to send an email that size, but the server at tulsaconnect.com [67.214.102.28] wouldn't accept it. From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 9: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.commailto: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:x...@yahoo.commailto:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com Received-From-MTA: DNS; localhost.localdomain Arrival-Date: Fri, 6 May 2011 09:19:39 -0500 Final-Recipient: RFC822; xx...@companymail.commailto: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: ...@yahoo.commailto:...@yahoo.com Received: from mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.commailto:xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.comhttp://omp1029.access.mail.sp2.yahoo.com (omp1029.access.mail.sp2.yahoo.comhttp://omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com (mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com [67.214.101.67]) envelope-from xxx...@yahoo.commailto: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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.comhttp://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.comhttp://yahoo.com; --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** --- 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
RE: little help understanding header info
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.commailto: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:x...@yahoo.commailto:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com Received-From-MTA: DNS; localhost.localdomain Arrival-Date: Fri, 6 May 2011 09:19:39 -0500 Final-Recipient: RFC822; xx...@companymail.commailto: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: ...@yahoo.commailto:...@yahoo.com Received: from mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.commailto:xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.comhttp://omp1029.access.mail.sp2.yahoo.com (omp1029.access.mail.sp2.yahoo.comhttp://omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com (mscan4.tulsaconnect.comhttp://mscan4.tulsaconnect.com [67.214.101.67]) envelope-from xxx...@yahoo.commailto: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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.comhttp://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.comhttp://yahoo.com; --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto: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
Re: little help understanding header info
Thank you Rob and Jim. That 67.214.102.28 is one of MY public IP's that the firewall routes to my filter, internal IP 10.1.9.8. I should have included that detail. I AM able to send outbound messages with 15 meg attachements, and I can send internally from one exchange domain to another with same attachments. One of our owners has a daughter in Sweden with the first grandchild, born this year and she would prefer to receive emails to her company email, rather than the hotmail account she is forced to use because I can't figure this out. On Fri, May 6, 2011 at 10:02 AM, Kennedy, Jim kennedy...@elyriaschools.orgwrote: 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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 --- 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 --- 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
RE: little help understanding header info
It's not your fault (oh wait but it still is!) :) I made a little picture a while back to help illustrate why this stupid limit is on email: http://ge.tt/4SGdgWO?c I waited for a quiet period and then sent a 3.2 MB pdf file to my gmail. Granted, our server is a bit long in the tooth with inadequate I/O capability and technically the wording is not entirely correct, but it helps the understanding and passes the point that this very important thing being sent could be annoying everyone for longer than you think. It would be great if the vendor (MS) would take time to do more scientific testing in a lab environment (effect of multiple people sending concurrently, effect of size, etc...) and illustration along these lines since IT is always thrown under the bus! ~JasonG -Original Message- From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com (omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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 /y5ZT95TRn1OEvbqgQxmeiYaHMlbGR4gMiVI59ejEmkpAAUbmNUtURCLE5cHNexwRUvOogoM G8IJbHQV3+his6o1WUsTr3lHoXtyk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; --- 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 --- 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
RE: little help understanding header info
There was LOTS of work done in Exchange 2010 to minimize the impact of sending large emails on transport and mailbox. I believe that work was back-ported to Exchange 2007 sp3, but I'm not 100% on that. I've seen presentations that do exactly what you suggest, but I don't think any of them are public (where public, in this case, means on TechNet or EHLO blog). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 12:06 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info It's not your fault (oh wait but it still is!) :) I made a little picture a while back to help illustrate why this stupid limit is on email: http://ge.tt/4SGdgWO?c I waited for a quiet period and then sent a 3.2 MB pdf file to my gmail. Granted, our server is a bit long in the tooth with inadequate I/O capability and technically the wording is not entirely correct, but it helps the understanding and passes the point that this very important thing being sent could be annoying everyone for longer than you think. It would be great if the vendor (MS) would take time to do more scientific testing in a lab environment (effect of multiple people sending concurrently, effect of size, etc...) and illustration along these lines since IT is always thrown under the bus! ~JasonG -Original Message- From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com (omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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 /y5ZT95TRn1OEvbqgQxmeiYaHMlbGR4gMiVI59ejEmkpAAUbmNUtURCLE5cHNexwRUvOogoM G8IJbHQV3+his6o1WUsTr3lHoXtyk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; --- 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 --- 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 --- To manage subscriptions click here: http://lyris.sunbelt
Re: little help understanding header info
You say that your TulsaConnect IS enforcing size limits, and you're not. So, besides everything in the header referencing TulsaConnect, I would still be leaning towards at least finding out what their limit is that they're enforcing, and whether or not you can get them to raise that limit. Jeff Brown 2jbr...@gmail.com 5/6/2011 7:49 AM 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com ( omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=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; --- 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 --- 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
RE: little help understanding header info
For the love of all that is good I hope we get the project approved in this coming fiscal year! Geez SP2 will be out before we get migrated off the 2003! Interesting note about live@edu... a couple weeks ago, my OWA changed and based on features it seems like 2010 SP1 to me. A classmate still doesn't have it (and was pissed when I showed off the SP1 niceness, heh). I would have thought they'd split people by campus instead of by account, but clearly am wrong. Anyway, super happy to have my preview pane back, available where it belongs on the bottom :) ~JasonG -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, May 06, 2011 13:22 To: MS-Exchange Admin Issues Subject: RE: little help understanding header info There was LOTS of work done in Exchange 2010 to minimize the impact of sending large emails on transport and mailbox. I believe that work was back-ported to Exchange 2007 sp3, but I'm not 100% on that. I've seen presentations that do exactly what you suggest, but I don't think any of them are public (where public, in this case, means on TechNet or EHLO blog). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 12:06 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info It's not your fault (oh wait but it still is!) :) I made a little picture a while back to help illustrate why this stupid limit is on email: http://ge.tt/4SGdgWO?c I waited for a quiet period and then sent a 3.2 MB pdf file to my gmail. Granted, our server is a bit long in the tooth with inadequate I/O capability and technically the wording is not entirely correct, but it helps the understanding and passes the point that this very important thing being sent could be annoying everyone for longer than you think. It would be great if the vendor (MS) would take time to do more scientific testing in a lab environment (effect of multiple people sending concurrently, effect of size, etc...) and illustration along these lines since IT is always thrown under the bus! ~JasonG -Original Message- From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1]) by mscan4.tulsaconnect.com (8.13.8/8.13.8) with ESMTP id p46EJdAI004340 for xxx...@companymail.com; Fri, 6 May 2011 09:19:39 -0500 Received: from omp1029.access.mail.sp2.yahoo.com (omp1029.access.mail.sp2.yahoo.com [98.139.44.92]) by mscan4.tulsaconnect.com (mscan4.tulsaconnect.com [67.214.101.67]) envelope-from 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 - Received: (qmail 74424 invoked by uid 60001); 6 May 2011 14:19:32 - DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t
RE: little help understanding header info
The Live@Edu folks have no knowledge of who is where. :-) And they don't care - it's free, after all. BPOS/S and Office365, they are (and will be) a little nicer about. But yes, R5 started rolling out a couple of weeks ago, which is based on Enterprise SP1, plus a little bit. I have no idea how long a complete rolling upgrade takes. A while. There are millions of mailboxes involved. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 2:41 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info For the love of all that is good I hope we get the project approved in this coming fiscal year! Geez SP2 will be out before we get migrated off the 2003! Interesting note about live@edu... a couple weeks ago, my OWA changed and based on features it seems like 2010 SP1 to me. A classmate still doesn't have it (and was pissed when I showed off the SP1 niceness, heh). I would have thought they'd split people by campus instead of by account, but clearly am wrong. Anyway, super happy to have my preview pane back, available where it belongs on the bottom :) ~JasonG -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, May 06, 2011 13:22 To: MS-Exchange Admin Issues Subject: RE: little help understanding header info There was LOTS of work done in Exchange 2010 to minimize the impact of sending large emails on transport and mailbox. I believe that work was back-ported to Exchange 2007 sp3, but I'm not 100% on that. I've seen presentations that do exactly what you suggest, but I don't think any of them are public (where public, in this case, means on TechNet or EHLO blog). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 12:06 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info It's not your fault (oh wait but it still is!) :) I made a little picture a while back to help illustrate why this stupid limit is on email: http://ge.tt/4SGdgWO?c I waited for a quiet period and then sent a 3.2 MB pdf file to my gmail. Granted, our server is a bit long in the tooth with inadequate I/O capability and technically the wording is not entirely correct, but it helps the understanding and passes the point that this very important thing being sent could be annoying everyone for longer than you think. It would be great if the vendor (MS) would take time to do more scientific testing in a lab environment (effect of multiple people sending concurrently, effect of size, etc...) and illustration along these lines since IT is always thrown under the bus! ~JasonG -Original Message- From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; 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 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: ...@yahoo.com Received: from mscan4.tulsaconnect.com (localhost.localdomain [127.0.0.1
RE: little help understanding header info
The stats they have must be amazing 8-) -JasonG -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, May 06, 2011 14:50 To: MS-Exchange Admin Issues Subject: RE: little help understanding header info The Live@Edu folks have no knowledge of who is where. :-) And they don't care - it's free, after all. BPOS/S and Office365, they are (and will be) a little nicer about. But yes, R5 started rolling out a couple of weeks ago, which is based on Enterprise SP1, plus a little bit. I have no idea how long a complete rolling upgrade takes. A while. There are millions of mailboxes involved. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 2:41 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info For the love of all that is good I hope we get the project approved in this coming fiscal year! Geez SP2 will be out before we get migrated off the 2003! Interesting note about live@edu... a couple weeks ago, my OWA changed and based on features it seems like 2010 SP1 to me. A classmate still doesn't have it (and was pissed when I showed off the SP1 niceness, heh). I would have thought they'd split people by campus instead of by account, but clearly am wrong. Anyway, super happy to have my preview pane back, available where it belongs on the bottom :) ~JasonG -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, May 06, 2011 13:22 To: MS-Exchange Admin Issues Subject: RE: little help understanding header info There was LOTS of work done in Exchange 2010 to minimize the impact of sending large emails on transport and mailbox. I believe that work was back-ported to Exchange 2007 sp3, but I'm not 100% on that. I've seen presentations that do exactly what you suggest, but I don't think any of them are public (where public, in this case, means on TechNet or EHLO blog). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 12:06 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info It's not your fault (oh wait but it still is!) :) I made a little picture a while back to help illustrate why this stupid limit is on email: http://ge.tt/4SGdgWO?c I waited for a quiet period and then sent a 3.2 MB pdf file to my gmail. Granted, our server is a bit long in the tooth with inadequate I/O capability and technically the wording is not entirely correct, but it helps the understanding and passes the point that this very important thing being sent could be annoying everyone for longer than you think. It would be great if the vendor (MS) would take time to do more scientific testing in a lab environment (effect of multiple people sending concurrently, effect of size, etc...) and illustration along these lines since IT is always thrown under the bus! ~JasonG -Original Message- From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; mscan4.tulsaconnect.com Received-From-MTA: DNS; localhost.localdomain
Re: little help understanding header info
Live@edu migrations are split by tenant On Fri, May 6, 2011 at 2:50 PM, Michael B. Smith mich...@smithcons.comwrote: The Live@Edu folks have no knowledge of who is where. :-) And they don't care - it's free, after all. BPOS/S and Office365, they are (and will be) a little nicer about. But yes, R5 started rolling out a couple of weeks ago, which is based on Enterprise SP1, plus a little bit. I have no idea how long a complete rolling upgrade takes. A while. There are millions of mailboxes involved. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 2:41 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info For the love of all that is good I hope we get the project approved in this coming fiscal year! Geez SP2 will be out before we get migrated off the 2003! Interesting note about live@edu... a couple weeks ago, my OWA changed and based on features it seems like 2010 SP1 to me. A classmate still doesn't have it (and was pissed when I showed off the SP1 niceness, heh). I would have thought they'd split people by campus instead of by account, but clearly am wrong. Anyway, super happy to have my preview pane back, available where it belongs on the bottom :) ~JasonG -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, May 06, 2011 13:22 To: MS-Exchange Admin Issues Subject: RE: little help understanding header info There was LOTS of work done in Exchange 2010 to minimize the impact of sending large emails on transport and mailbox. I believe that work was back-ported to Exchange 2007 sp3, but I'm not 100% on that. I've seen presentations that do exactly what you suggest, but I don't think any of them are public (where public, in this case, means on TechNet or EHLO blog). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Friday, May 06, 2011 12:06 PM To: MS-Exchange Admin Issues Subject: RE: little help understanding header info It's not your fault (oh wait but it still is!) :) I made a little picture a while back to help illustrate why this stupid limit is on email: http://ge.tt/4SGdgWO?c I waited for a quiet period and then sent a 3.2 MB pdf file to my gmail. Granted, our server is a bit long in the tooth with inadequate I/O capability and technically the wording is not entirely correct, but it helps the understanding and passes the point that this very important thing being sent could be annoying everyone for longer than you think. It would be great if the vendor (MS) would take time to do more scientific testing in a lab environment (effect of multiple people sending concurrently, effect of size, etc...) and illustration along these lines since IT is always thrown under the bus! ~JasonG -Original Message- From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Friday, May 06, 2011 10:49 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 (reason: 552 message size exceeds fixed maximum message size) - Transcript of session follows - ... while talking to [67.214.102.28]: MAIL From:x...@yahoo.com SIZE=30433191 552 message size exceeds fixed maximum message size 554 5.0.0 Service unavailable Reporting-MTA: dns; mscan4.tulsaconnect.com Received-From-MTA: DNS; localhost.localdomain Arrival-Date: Fri, 6 May 2011 09:19:39 -0500 Final-Recipient: RFC822; xx
