分类：
2010-02-26 13:05:42
POE::Component::Client::SMTP - Asynchronous mail sending with POE
Version 0.22
PoCoClient::SMTP allows you to send email messages in an asynchronous manner, using POE.
Thus your program isn't blocking while busy talking with an (E)SMTP server.
Warning! The following examples are not complete programs, and aren't designed to be run as full blown applications. Their purpose is to quickly introduce you to the module.
For complete examples, check the 'eg' directory that can be found in the distribution's kit.
A simple example:
# load PoCoClient::SMTP
use POE::Component::Client::SMTP;
# spawn a session
POE::Component::Client::SMTP->send(
From => 'foo@baz.com',
To => 'john@doe.net',
Server => 'relay.mailer.net',
SMTP_Success => 'callback_event_for_success',
SMTP_Failure => 'callback_event_for_failure',
);
# and you are all set ;-)
A more complex example:
# load PoCoClient::SMTP
use POE::Component::Client::SMTP;
# spawn a session
POE::Component::Client::SMTP->send(
# Email related parameters
From => 'foo@baz.com',
To => [
'john@doe.net',
'andy@zzz.org',
'peter@z.net',
'george@g.com',
],
Body => \$email_body, # here's where your message is stored
Server => 'relay.mailer.net',
Timeout => 100, # 100 seconds before timeouting
# POE related parameters
Alias => 'pococlsmtpX',
SMTP_Success => 'callback_event_for_success',
SMTP_Failure => 'callback_event_for_failure',
);
# and you are all set ;-)
Below are the methods this Component has:
This immediately spawns a PoCoClient::SMTP Session and registers itself with the Kernel in order to have its job done. This method may be overhead for sending bulk messages, as after sending one message it gets destroyed. Maybe in the future, there will be a spawn method that will keep the Session around forever, until received a 'shutdown' like event.
There are two kinds of parameters PoCoClient::SMTP supports: Email related parameters and POE related parameters:
This holds the sender's email address
Defaults to 'root@localhost', just don't ask why.
Note: that the email address has to be a bare email address (johndoe@example.com), not an RFC2822 email address ("John Q. Public"
This holds a list of recipients. Note that To/CC/BCC fields are separated in your email body. From the SMTP server's point of view (and from this component's too) there is no difference as who is To, who CC and who BCC.
The bottom line is: be careful how you construct your email message.
Defaults to root@localhost', just don't ask why.
Note: that the email address has to be a bare email address (johndoe@example.com), not an RFC2822 email address ("John Q. Public"
Here's the meat. This scalar contains the message you are sending composed of Email Fields and the actual message content. You need to construct this by hand or use another module. Which one you use is a matter of taste ;-)))
Note that MessageFile and FileHandle take precedense over Body.
In case MessageFile or FileHandle are set, Body is discarded.
Defaults to an empty mail body.
Here you specify the relay SMTP server to be used by this component. Currently piping thru sendmail is not supported so you need a SMTP server to actually do the mail delivery (either by storing the mail somewhere on the hard drive, or by relaying to another SMTP server).
Defaults to 'localhost'
Usually SMTP servers bind to port 25. (See /etc/services if you are using a *NIX like O.S.).
Sometimes, SMTP servers are set to listen to other ports, in which case you need to set this parameter to the correct value to match your setup.
Defaults to 25
Set the timeout for SMTP transactions (seconds).
Defaults to 30 seconds
Hostname to present when sending EHLO/HELO command.
Defaults to "localhost"
This attribute is set when creating the socket connection to the SMTP server. See POE::Wheel::SocketFactory for details.
This attribute is set when creating the socket connection to the SMTP server. See POE::Wheel::SocketFactory for details.
Set the debugging level. A value greater than 0 increases the Component's verbosity
Defaults to 0
In case you have multiple PoCoClient::SMTP Sessions, you'd like to handle them separately, so use Alias to differentiate them.
This holds the Session's alias.
Defaults to nothing. Internally it refcounts to stay alive.
You may want to set a context for your POE::Component::Client::SMTP session. This is a scalar.
When the caller session receives SMTP_Success or SMTP_Failure event, the context is also passed to it if defined.
Specify a file name from where the email body is slurped.
Note: that you still need to specify the parameters like From, To etc.
Specify a filehandle from where the email body is slurped.
POE::Component::Client::SMTP does only a basic check on the filehandle it obtains from FileHandle value; in case you need to do some more sophisticated checks on the file and filehandle, please do it on your own, and then pass the handle to the component.
It is important that the handle is readable so please check that before using it.
Note: that you still need to specify the parameters like From, To etc.
In case you want to get back the Log between the client and the server, you need to enable this.
Defaults to disabled.
Event you want to be called by PoCoClient::SMTP in case of success.
Defaults to nothing. This means that the Component will not trigger any event and will silently go away.
Contains Context if any
ARG1 Contains the SMTP Transaction log if TransactionLog is enabled, in the form: <- string received from server -> string to be sent to server Note that it is possible the string sent to server may not arrive there
ARG1 is undefined if TransactionLog is not enabled
Event you want to be called by PoCoClient::SMTP in case of failure.
You will get back the following information:
The Context you've set when spawning the component, or undef if no Context specified
A hash ref that currently has only a key:
* SMTP_Server_Error, in this case, the value is the string as returned by the server (the error code should be included too by the server in the string)
* Timeout, the value is the amount of seconds the timeout was set to
* POE::Wheel::* depending on the wheel that returned error on us ;-) the value is a ref to an array containing ARG0 .. ARG3
* Configure, for AUTH misconfiguration
* MessageFile_Error for not being able to slurp the contents of the file given to MessageFile, in case the parameter was set.
Please note that in case the file is opened successfully and we get an error from the ReadWrite Wheel, then the hash key is 'POE::Wheel::ReadWrite'
ARG2 Contains the SMTP Transaction log if TransactionLog is enabled, in the form: <- string received from server -> string to be sent to server Note that it is possible the string sent to server may not arrive there
ARG2 is undefined if TransactionLog is not enabled
This contains a single line (scalar) describing the error. It's useful for displaying the error in SMTP clients using PoCo
Defaults to nothing. This means that the Component will not trigger any event and will silently go away.
ESMTP Authentication
Currently supported mechanism: PLAIN
If you are interested in implementing other mechanisms, please send me an email, it should be piece of cake.
Hash ref with the following fields:
The mechanism to use. Currently only PLAIN auth is supported
User name
User password
RFC2821
Please report bugs using the project's page interface, at:
Unified format patches are more than welcome.
Note that the SMTP protocol forbids bare LF characters in e-mail messages. PoCoClSMTP doesn't do any checking whether you message is SMTP compliant or not.
Most of the SMTP servers in the wild are tolerant with bare LF characters, but you shouldn't count on that.
The point is you shouldn't send email messages having bare LF characters. See:
ESMTP error codes 1XY are ignored and considered as 2XY codes
George Nistorica,
Copyright 2005 - 2007 George Nistorica, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.