Impact of sending attachment to many recipients?

Topic

New Reply

Hi,

Let’s say a user sends a 1Mb attachment by email to 1000 people, does it add 1000Mb to the Exchange Database?

I put out a post like this before & the replies were negative.

But now a friend pointed out that a recipient who has a mailbox on the Exchange Server could for example open this email & change it.

Then save it (i.e. the email was changed).

So he’s saying that this shows that each person gets their personal copy of the email.

Therefore, the 1Mb attachment in the email to 1000 people DOES increase the Exchange Database size by 1000Mb.

Pls. can you shed some light on this discussion for us?

I’d appreciate some official article from Microsoft (e.g. Technet) to prove my point.

Help!!!!!

Thanks in advance.

Reply | Quote

Replies

• Original File (File0) remains on Exchange Server with a pointer to it.
• User1 opens File0 and changes it. If User1 saves it and saves it with the email, the File1 is created and attached to the email.
• How many of the 1,000 users are going to:
  • open the file, and
  • change it, and
  • decide to keep the changed version, and
  • not save it on their hard drives or a network share, but
  • save the changed version with the emai?[/list][/list]

Reply | Quote

• Original File (File0) remains on Exchange Server with a pointer to it.
• User1 opens File0 and changes it. If User1 saves it and saves it with the email, the File1 is created and attached to the email.
• How many of the 1,000 users are going to:
  • open the file, and
  • change it, and
  • decide to keep the changed version, and
  • not save it on their hard drives or a network share, but
  • save the changed version with the emai?[/list][/list]

Reply | Quote

Official word from Microsoft.

Of course, that article is for Exchange 4.0, which is pretty old (thus the 16 gig limit…which is not appropriate in later versions of Exchange, but the storage process is the same in later versions.

Your friend didn’t really know what he was talking about. Not too mention, who actually saves changes to attachments they receive in email, back into their email system?

Reply | Quote

Official word from Microsoft.

Of course, that article is for Exchange 4.0, which is pretty old (thus the 16 gig limit…which is not appropriate in later versions of Exchange, but the storage process is the same in later versions.

Your friend didn’t really know what he was talking about. Not too mention, who actually saves changes to attachments they receive in email, back into their email system?

Reply | Quote

I prefer to handle large attachments by referring to them in the email and providing a) a URI to the content so that they can browse it that way, or informing them that due to the size of the attachment, it is by request only.

Regardless of what it does to your Exchange server, it flogs bandwidth horribly.

Oh, and I think this reeks of unsolicited email. Be careful what you send, and make sure 1,000 people want it.

Reply | Quote

I prefer to handle large attachments by referring to them in the email and providing a) a URI to the content so that they can browse it that way, or informing them that due to the size of the attachment, it is by request only.

Regardless of what it does to your Exchange server, it flogs bandwidth horribly.

Oh, and I think this reeks of unsolicited email. Be careful what you send, and make sure 1,000 people want it.

Reply | Quote