One of puposes of &fmldevel; is unification and abstraction of member list operations. Mail distribution is based on the following module Mail::Delivery. Mail::Delivery class provides SMTP, ESMTP and LMTP delivery library interface. Mail::Delivery is an adapter layer for Mail::Delivery subclass ( SMTP ESMTP LMTP ). For example, use Mail::Delivery::SMTP; my $service = new Mail::Delivery::SMTP; if ($service->error) { Log($service->error); return;} $service->deliver( { mta => '127.0.0.1:25', smtp_sender => 'rudo@nuinui.net', recipient_maps => $recipient_maps, recipient_limit => 1000, mesage => $message }); where $message is a Mail::Message object. This object provies message analyzer. It analyzes a message and build the following object chains header -> body header -> preamble -> part1 -> part2 -> trailor (multipart) Mail::Message class provides such data structure described above. §.mailqueue; Only FML::Process::QueueManager uses FML::Mailer. So, independent FML::Mailer class is needed ? In usual codes, reply_message() handles all message operations. FML::Mailer is always behind it. But modules other than reply_message() is created in the future ? Hmm, ... FML::Mailer should be merged into FML::Process::QueueManager class? &recipe.delivery.forward;