Hi, I read through the links here discussing the above issue. I wonder if we have lets say 20MB limit for attachment, set globally, what will happen if a user sends a 2MB attachment to more than 10 users? is it related? We have found some external users complaining that they receive such emails with a two weeks delay?! I am already informing that large attachments should not be sent to groups with many users, Kind regards, Henry

On Tue, 1 Nov 2011 15:22:25 +0000, HenryMa wrote: >I read through the links here discussing the above issue. I wonder if we have lets say 20MB limit for attachment, set globally, what will happen if a user sends a 2MB attachment to more than 10 users? is it related? Nope. >We have found some external users complaining that they receive such emails with a two weeks delay?! Have them send the RFC822 message headers for the message to you and check the "Received:" headers. If you have e-mail in your queue for more then two days (that's the default) it'll be returned to the sender as undeliverable. >I am already informing that large attachments should not be sent to groups with many users, That depends on your connection to the Internet. Two megabytes isn't a "large" message -- unless you're using a pretty small pipe. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Not quite sure how I can get RFC822. I do not believe you are referring the user to forward me the email; and if it is how I can get the RFC822 format information. By checking Received header, presumably you are pointing me to find which server was the last one sending the email? And you are right, the link between these Charity Organizations are not faster than home ADSL

On Tue, 1 Nov 2011 20:09:05 +0000, HenryMa wrote: >Not quite sure how I can get RFC822. You don't, since you don't have the delivered message. >I do not believe you are referring the user to forward me the email; and if it is how I can get the RFC822 format information. That depends on the e-mail client they use. >By checking Received header, presumably you are pointing me to find which server was the last one sending the email? Not necessisarily. You want to find the server that caused the delay. You have to compare the difference in the time in each of the "Received:" headers (taking into account the time zones in each header). >And you are right, the link between these Charity Organizations are not faster than home ADSL That can be relatively fast. Is it 768Kbps or 6Mbps? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Tue, 1 Nov 2011 15:22:25 +0000, HenryMa wrote: >I read through the links here discussing the above issue. I wonder if we have lets say 20MB limit for attachment, set globally, what will happen if a user sends a 2MB attachment to more than 10 users? is it related? Nope. >We have found some external users complaining that they receive such emails with a two weeks delay?! Have them send the RFC822 message headers for the message to you and check the "Received:" headers. If you have e-mail in your queue for more then two days (that's the default) it'll be returned to the sender as undeliverable. >I am already informing that large attachments should not be sent to groups with many users, That depends on your connection to the Internet. Two megabytes isn't a "large" message -- unless you're using a pretty small pipe. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Many thanks for the information. I could inform users properly based on the information you provided, Regards, Henry