We are using the db-container for the example and a MySQL database. You need to create some tables in the mysql-database to store the messages:

mysql.sql

CREATE TABLE mail_queue (  id bigint(20) NOT NULL default '0',  create_time datetime NOT NULL default '0000-00-00 00:00:00',  time_to_send datetime NOT NULL default '0000-00-00 00:00:00',  sent_time datetime default NULL,  id_user bigint(20) NOT NULL default '0',  ip varchar(20) NOT NULL default 'unknown',  sender varchar(50) NOT NULL default '',  recipient text NOT NULL,  headers text NOT NULL,  body longtext NOT NULL,  try_sent tinyint(4) NOT NULL default '0',  delete_after_send tinyint(1) NOT NULL default '1',  PRIMARY KEY  (id),  KEY id (id),  KEY time_to_send (time_to_send),  KEY id_user (id_user));

First you need to define some options. As you need them two times (once for adding messages, once for sending the messages) its always good to add them to a config-file. Let's call it config.php

config.php

So we are done configuring it, now let's use it.First we need to construct a mail-message and add it to the queue:

add_message.php

NB: the first time you call put(), PEAR::DB and PEAR::MDB2 will create a new table to keep the sequence number, so make sure the db user you are using has "CREATE TABLE" privileges. Or you can create the table separately, calling the createSequence() method of PEAR::DB or PEAR::MDB2 (you should also be aware that the two DBAL will create a table with a different field name: "id" for DB, "sequence" for MDB2).

Ok, now we've used the simple way to add a message ... there are more advanced options, please checkdocs of the put-function for these.Now we need to send the messages. This is most often done by using a cron-job which regularly runsa script to send the messages.Here is a simple script to achieve this:

send_messages.php

We are done.Now run the last script regularly and add your mails to the queue as needed.

Since Mail_Queue v.1.1, the preload()method doesn't preload ALL the mails in memory, but just a few of them each time.When the buffer is empty, it is filled again automatically. You can set the sizeof the buffer via the new setBufferSize() method.

You can also send the stored emails one by one.Here is a simple script to achieve this:

send_messages_one_by_one.php

The sendMailsInQueue method, since version 1.2.3, has callback support. This may be utilised for report generation and postprocessing.

The callback function is called before the relevant entry is deleted from the mail_queue table in the database so if necessary you could add extra fields to it for inserting into your log/report table. The function should accept only one parameter - an associative array of values; 'id', 'queued_as' and 'greeting'.

You'll need to use recent releases of the PEAR::Mail (version 1.2.0b3 or higher) and PEAR::Net_SMTP (version 1.3.3 or higher) packages to be able to retrieve the esmtp id and greeting details if you need them for your reports. Also, if you want to decode the body of the email and store that for your report you'll need to install the PEAR::Mail_mimeDecode package.

Provide the callback function like so: