a few ideas for great features

After using your module for a while, I had a few ideas for new features, I think these could be really useful. Some might be much easier to implement, and I realize some of these ideas would require a major rewrite, maybe those ideas could be for 2.x. I would really appreciate your feed back on these ideas, please respond here, or use my contact form, or even (best) contact me (joncup) on irc.

1st Idea) I have a few email templates in outlook that I use on a several times a day, after I contact a client, or a client contacts us, I send them all the same email, a few of which I customize, I would like to use mailout for these emails, but the only practical way I could see doing this, is adding all the emails to a list and sending the email once a day. I think it would super useful to be able to create a template and associate it with a mail list, and have a block where you enter an email address and it adds the email address to the list and immediately sends the template email to the new address. I can imagine that the block would have a check box that allows you to customize the mailout for that user before sent, if checked. This leads to idea #2. This is repeated in idea 2, but the idea here is that, we could track the sent/opened status from the same page

2nd Idea) Block to add addresses to a mail out list and send template immediately. Idealy we could track the sent/opened status all on the same page, no matter when the email was sent.

3rd Idea) Option to use token replacement to add &some_string to urls in message. This could allow us to track clicks with out relying on email clients that show images. I imagine that with use of input formats, urls in in messages could be replaced with $url . '&' . [token_email_address] so that "http://example.com/url" becomes "http://example.com/url&[token-emailaddress]". Then when a click comes in it shows that that email has been opened. Better yet would be if we used hashes like, "http://example.com/url" becomes "http://example.com/url&[emailadress_hash]". Ideally drupal would intercept these urls and redirect to an url with out the &[identifier] so that clients are less likely to notice our tracking methods, how ever we would still be able to track reads with the module, maybe even with out analytics modules.

Please contact me and let me know what you think about these ideas, I see that they could be uber useful. I'll be taking some php classes in school this next semester and I would be happy to contribute what i can.