While this mailer class can be used with small PHP applications, it lacks some important features related specifically to its object model, since it was built in PHP 4 from the very beginning.

They review the PHP4 version of the script first then move on to the process of porting it to a more standardized PHP5 structure and code.

Let's have a little fun, shall we? Here is what we'll do. I'll ask ZendCon or PHP trivia via twitter (http://twitter.com/zendcon) and the first person to email me the correct answer at contest@zend.com will win a prize.

Up for grabs are ZendCon trading cards, books, elePHPants and copies of Zend Studio. Remember, you have to be following zendcon on twitter to get the questions and answers must be submitted via email (no DM, IM, tweets or IRC answers will count).

In this article, I'm going to show you how to provide the MIME mailer class with the ability to send email messages in HTML format. This will greatly extend its functionality, so don't miss this tutorial.

They start by reviewing the class they've created so far, including an example of its use. From there they modify it slightly to make it easy to embed the HTML content into the email by adding the addHTML and buildHTMLPart methods.

Using PHP's built in function (aptly named mail() ) is relatively straightforward - until you need slightly more advanced features, such as adding and encoding email headers or sending multiple mails efficiently. Fortunately, the Zend Framework comes with a very capable mail component called Zend_Mail.

He shows how to send a simple email, do something a bit more complex with a custom SMTP server, read messages from a remote POP3 email box and how to attach a binary file/message.

For any web developer that's ever had to build a signup routine, email is the necessary evil that takes pride of place among hated activities. Sure, a simple call to the language's mail library will send a message through, but the moment the boss wants a HTML email, or users need attachments, everything starts to get tricky.

They try to solve the mail return issue (it tells if the message has gone to the queue, not been delivered) with a little testing and Fakemail. The software looks for emails based on the configuration given and pulls them out to a local directory. Your script can then look here and check the validity of the message before its sent.

This even allows for integration with things like Phing, SimpleTest and Selenium.

In this second tutorial of the series, I'm going to teach you how to improve the initial structure of the MIME mailer class developed in the first article by giving it the ability to work directly with attachments. Sounds fairly interesting, right? Then don't waste any more time in preliminaries and begin reading this article now!

They refresh you on the code from the former tutorial and show you how to modify it to work with more than just the simple plain-text attachment like before (with binary information, things like JPEGs, PDFs and other text formats like XML and HTML).

One of the most common tasks that a PHP programmer has to tackle is the development of applications that send MIME email in one form or another. In simple terms, MIME email consists of an extension of traditional email technology and comes in handy for sending email messages in fancy HTML and handling file attachments in a wide variety of formats.

In this first part of the series he just lays the groundwork - creating the mailer class they'll use for the series and using it to send a sample email (a basic message with a plain text MIME block).

Sending mails is a web developer's everyday task, and symfony 1.1 let you do this easier than ever using Swift Mailer. Swift Mailer is a well thought, fully featured PHP5 object library that will cover 120% of your mailing needs.

They show how to create a partial or a component in your application that generates the content for the emails and pushes that result out to the Swift Mailer application. They show the (simple) installation from a svn checkout and two examples of sending emails, one simple and another with a multipart message.

• The prd() convenience function
• How to debug your CakePHP emails?
• Use elements where possible and make them belong to the controller
• Combine your h1 titles with Cake's page title
• Avoid long parameter lists

Each tip comes complete with code and a brief explanation of its use.

I've noticed that Richard Heyes, who professes himself to be a php guru, deleted my comment on his "Some common regular expressions" posting which simply pointed out his expressions didn't quite do the job and suggested a few PEAR packages that should be used instead of the expressions that he proffered

His examples have the benefit of what he calls "defense in depth" - the functionality to catch a bit more than just a regular expression can alone. His examples include PEAR_Validate for email addresses, Net_CheckIP2 for IP addresses and the Validate_UK package for the sort code and telephone numbers.