thanks,
vedran
Hi,
I have never used it myself, but a quick glance at the source code
does not show any reason why this would not work. However, keep two
things in mind:
- the emails are first all constructed in memory, which could be a
bit of a problem if the email body is large
- the SMTP server must be able to handle 7000 emails in one go
Hope this helps a bit
Jirka
I've done large mailshots before. It's not fun if you don't have some
method of bounce handling because even if you have a very clean list,
with a list that large, you're bound to get the usual array of soft and
hard bounces. Creating an announcement only mailing list in Mailman is
quite easy. If you do that, your Django app only has to send an email to
one address, the announcement only list's address. Then, you have a
mature body of code to handle bounces, unsubscribes (if you wish), etc.
Mailman is written in Python so it's easy to incorporate with your code
at a lower level, if you need that.
--
Regards,
Clifford Ilkay
Dinamis
1419-3266 Yonge St.
Toronto, ON
Canada M4N 3P6
I know about Mailman but i have to send unique mail to each user, kind
of confirmation with system generated url.
On Mar 11, 12:16 am, CLIFFORD ILKAY <clifford_il...@dinamis.com>
wrote:
take a look at http://code.google.com/p/django-mailer/
I'm using that, though I've now modified it and not had a chance to
release my version.
mails are put into a queue and the queue is fed by a background daemon
loop
I've added html support and actually I don't render out each mail at
send time.
I render one message, then I have various placeholders which can be
replaced at send time for the individual.
there is absolutely no way you can emails to more than 50 users while
the sender waits for the view to return
there will be errors
there will be bounces
<http://wiki.list.org/display/DOC/So+what+is+this+VERP+stuff>