Re: OT - massive newsletter

2007-09-22 Thread John D. Hardin
On Sat, 22 Sep 2007, Dave Koontz wrote: > If I might ask, where are you getting the list "SEED" addresses > from? It's hard for me to imagine you have such a large number of > users that have already requested information you have not > configured to send yet. If this is a purchased list of addr

Re: OT - massive newsletter

2007-09-22 Thread Dave Koontz
If I might ask, where are you getting the list "SEED" addresses from? It's hard for me to imagine you have such a large number of users that have already requested information you have not configured to send yet. If this is a purchased list of addresses ... you may have some problems quickly. Re

Re: OT - massive newsletter

2007-09-22 Thread Mick Pollard
> > > I'm setting up an SMTP server (centos + qmail) on a dell quad core > > > machine for sending out a periodic newsletter (10 millions a > > > month). > > > > > You might consider using mailing-list software such as mailman, which > > allows people to subscribe and unsubscribe and takes care

Re: OT - massive newsletter

2007-09-22 Thread mizzio
Thank you to everyone for the support. Maurizio On mer, 2007-09-19 at 08:17 -0700, John D. Hardin wrote: > On Wed, 19 Sep 2007, mizzio wrote: > > > I'm setting up an SMTP server (centos + qmail) on a dell quad core > > machine for sending out a periodic newsletter (10 millions a > > month). > >

Re: config: failed to parse line

2007-09-22 Thread Daryl C. W. O'Shea
Micah Anderson wrote: Occasionally I am seeing the following log lines, they don't seem to be fatal, but I'd like to know what they are so I can decide if I need to fix something: Sep 21 07:24:07 spamd2 spamd[7749]: config: failed to parse line, skipping, in "(no file)": x-train Sep 21 07:24:07

RE: OT - massive newsletter

2007-09-22 Thread Kenneth Porter
--On Wednesday, September 19, 2007 12:16 PM +0100 "Randal, Phil" <[EMAIL PROTECTED]> wrote: If you don't want to annoy a lot of people your spamming (oops, newsletter sending) software needs to deal with NDRs back from recipient's domains and either put their subscription on hold after a small