On Tue, 11 Nov 2008 00:27:06 -0800, [EMAIL PROTECTED] wrote:
> Hello Patrick,
>
> On Nov 11, 1:53 am, "Patrick J. Anderson" <[EMAIL PROTECTED]>
> wrote:
>>
>> Some of the main requirements are:
>>
>> * Personalised HTML/text messages
>> * Manual delivery twice a week
>> * Message logging/archivi
I would like to share with you some different ideology...
I don't like to use any external software to work aside with main
application. Very often, it's just imposible to use cron on client's
hyper-hostings.
The idea is simple, use ajax.
I got very simple mechanism that uses some javascript to s
Hello Patrick,
On Nov 11, 1:53 am, "Patrick J. Anderson" <[EMAIL PROTECTED]>
wrote:
>
> Some of the main requirements are:
>
> * Personalised HTML/text messages
> * Manual delivery twice a week
> * Message logging/archiving
> * Amount of newsleter issues: ~50
> * Amount of subscribers: 500-5000
I can't claim best way, but the way we do it is to have a few django
models for storing the messages, and some help from the email, and
smptlib libraries.
Models:
Mailserver: model for storing connection information for connecting to
a standard smtp server, with mixin class using smtplib to provi
I'm in the process of writing a simple newsletter managers with a web
interface and since I've been a Django user for the past 2 years, I
thought of using Django for this task.
Some of the main requirements are:
* Personalised HTML/text messages
* Manual delivery twice a week
* Message logging
5 matches
Mail list logo