va ajouter Cci pour php courrier d'économiser des ressources?

Question

Je suis en train d'écrire une notification admin sytem pour mon CMS personnalisé. Donc, je prévois d'ajouter un Cci à tous les utilisateurs de sites. Voici donc mes questions?

• est bcc mieux que le foreach ($ utilisateur) {mail ()} function? en termes d'utilisation des ressources du serveur?
• Combien de Bcc le support du serveur?

Merci.

Answer 1

A direct mail to a user is usually the 'nicer' option, as it allows you to personalize it. The advantage for you is that you may get the chance to get some feedback by adding a unique id for each mail to each url that links back to your site. Using bcc is just one mail (from the view of your php server), but you shouldn't really worry about server resources here.

Limits for bcc seem to depend on your provider. I have seen limits ranging from 5 too 500. Sending too many mails at once may also not work due php processing time limits. For many users you will have to split the sending in both cases.

Answer 2

PHP is just the transporter of your request to the SMTP Server, so there is no limitations in PHP What so ever.

You can check your SMTP Servers limitations to see how many you can actually attach the the email.

using bin carbon copies will not really save you that much resources as the SMTP Server Still has to send an email to all attached recipients, this being said the only thing BCC Does for you is hide the email addresses in each email dispatched.

Answer 3

1. BCC is, lets say, hidden recipients. So if you'll add recipients to BCC users will receive your message, but their emails will not be displayed in "to" or "copy" list.
2. Max count of BCC recipients depends on mail server.

Answer 4

Well, this only works if you send the exactly same message with no personal/individual information in it, like all would receive this same message:

hello world

and not

Dear Mr. XY

or

Dear Ms. AB