Re: [siesta-dev] some thoughts

[prev] [thread] [next] [lurker] [Date index for 2002/10/11]

From: Richard Clamp
Subject: Re: [siesta-dev] some thoughts
Date: 15:38 on 11 Oct 2002
On Friday, Oct 11, 2002, at 01:53 Europe/London, Gavin Estey wrote:
> I've been having a bit of a poke around the code and here are some 
> thoughts.
> It's more of a few todo items that I think are simple enough for me to 
> start
> hacking on.

Sweet.  Sorry i've been lax in replying - neglects to point 
out filtered email.

> Siesta::Send::SMTP
> For list based templates
>  $list->set_template($name);
>  $list->get_template($name);
> where $name is sub/unsub etc

Wouldn't set_template want extra stuff passed into it?

> hack Siesta::Plugin::Send not to map on list members, speed things up
> by just getting emails from List->members_email (?)

Possibly, but a quick pause.  It's currently rigged so that the 
Siesta::Send::* classes have to do as little thinking as possible, and 
that people can easily opt out of getting mails by configuring their 
attitudes to Plugin::Send.

The current underdocumented message send api is 
C<$message->send(%args);> which gets passed through as 
C<Siesta->sender->send($mail, %args).  %args can have an element C<to>, 
which can be a scalar or an arrayref. if omitted uses that of the 

It seems that you could do what you're suggesting by optionally passing 
to => $list, but then each Send::* class has to do more work.

> Siesta::Plugin::Subscribe / Siesta::Plugin::Unsubscribe
>    have 2 new options: mail list owner on sub/email member on unsub

It's not currently optional, but yes, good call.

>  how are config options handled?

That's the swirling vortex down the corner that Simon set spinning.

> Anyway, Siesta looks promising and hopefully I can churn up some
> interest to stop it being YADSFP (yet another dead soureforge project) 
> :)


Richard Clamp <>

Generated at 13:56 on 01 Jul 2004 by mariachi 0.52