From 8113c80ec9707a567136583a52d49ebabe507804 Mon Sep 17 00:00:00 2001
From: Google Code Exporter <GoogleCodeExporter@users.noreply.github.com>
Date: Sat, 14 Mar 2015 06:11:24 -0400
Subject: [PATCH] Migrating wiki contents from Google Code

---
 FAQ.md         |  9 +++++++++
 PageName.md    | 24 ++++++++++++++++++++++++
 ProjectHome.md |  5 +++++
 3 files changed, 38 insertions(+)
 create mode 100644 FAQ.md
 create mode 100644 PageName.md
 create mode 100644 ProjectHome.md

diff --git a/FAQ.md b/FAQ.md
new file mode 100644
index 0000000..2f3d42e
--- /dev/null
+++ b/FAQ.md
@@ -0,0 +1,9 @@
+# Frequently asked questions #
+
+**1. It is written on your website that script doesn't use any database for scheduling mails. Then how is it doing that?**
+
+We wanted to avoid any extra system requirements so it was simpler to use file system instead. Each mail is encoded in JSON (that's where PHP 5.2.0 or greater requirement comes from) and saved as a separate file.
+
+**2. Is there a facility in your script which allows admin/script installer to set/limit number of mails to be sent in 1 hour? After that script will queue rest of the mails and send it when limit gets reset.**
+
+There is a somewhat similar facility. You can define how many mails you want to be sent in each cron run. For example, you can set your cron to run every 10 minutes and each time send at most 20 mails. You can limit the number of mails sent in one hour only if cron runs once an hour. You set the number of mails sent in properties file, and you set up cron using whatever is provided on your hosting system.
\ No newline at end of file
diff --git a/PageName.md b/PageName.md
new file mode 100644
index 0000000..519e8a6
--- /dev/null
+++ b/PageName.md
@@ -0,0 +1,24 @@
+# Installation instructions #
+
+In short, you have to do the following three steps:
+
+**1. Copy source files**
+
+Source control contains the following files:
+
+**`mail_queue`** - folder where actual mails are queued. This folder contains the file called `dummy` which can be deleted.
+
+**`phpbatchmail.lib.php`** – php source code file where function `batch_mail` is defined. This function takes the same parameters as PHP's function `mail`, and it should be called instead of later one.
+
+**`mail_next.php`** – PHP script that actually sends queued mails. It should be executed by `cron` as often as you like.
+
+**`propeties.ini`** – configuration file necessary for `mail_next.php` script. It defines the maximum number of queued mails that are going to be sent in each script run.
+
+**2. Include `phpbatchmail.lib.php` in your source code and call `batch_mail` instead of `mail`**
+
+**3. Set up `cron` to run `mail_next.php` as frequent as you want**
+
+Instructions for this step are different on each hosting environment. If you don’t know how to set up scheduler to run the script in regular intervals, the best would be to ask your hosting provider for help.
+
+
+**That should be it!**
\ No newline at end of file
diff --git a/ProjectHome.md b/ProjectHome.md
new file mode 100644
index 0000000..7addf14
--- /dev/null
+++ b/ProjectHome.md
@@ -0,0 +1,5 @@
+You are PHP developer and your applications among many other interesting things send e-mails around. However, you are annoyed by the delay that PHP's mail function introduces. Naturally, you would like your scripts to be more responsive to end users. If this is the case, you are at the right spot.
+
+**Prerequisites:** PHP 5.2.0 or newer, cron access
+
+**No DB necessary!**
\ No newline at end of file