Thanks for the reply, Ben... Actually, after several days of pulling my hair out, I discovered it was the mail server after all. The reason that Witango was releasing the records so slowly to the mail server was that the mail server had taken over the server's resources. (mail and witango on the same box)
I've never seen this behavior before, so I shut down filtering, spam block, etc on the mail server and still got the same results. Thinking back I recalled that earlier in the week I had a viscious spam attack. So I checked the log files. Sure enough the log files were HUGE. I deleted them and Bingo! Mail now runs fine. Thanks again for your reply. Tom btw: I don't use Witango near as much as I used to and haven't changed any of the server settings in over 4 years (yeah, I know... ) so, where is what used to be the config.taf?? I'm only on version 4.5 for Windows. > -----Original Message----- > From: Ben Johansen [mailto:[EMAIL PROTECTED] > Sent: Sunday, July 16, 2006 07:21 > To: [email protected] > Subject: Re: Witango-Talk: mail action > > Question. Has mail server software been upgraded between last > email run and this one? > > With new changes in spam blocking there might be a situation > where the mail server is checking the authenticity of the > smtp coming in (Witango). you might need to add local host ip > to the admin to have it not check emails coming from internal > ip, so the mail server doesn't spend time checking like > reverse DNS on each smtp connection. > > Just some thoughts, > > Ben > > On Jul 14, 2006, at 6:05 AM, Tom Ferguson wrote: > > I have a simple taf that loops through a database of my > customers and sends them an e-Mail whenever I have a new > release of my software for them to upgrade. Right now the > database has about 3000 records. > > This is a fairly straight-forward taf, builds a table, loops > through the table extracting e-mail address and name, then > sends the mail. I've been using this for a couple of years. > I typically have to increase the server timeout when I do > this, and recently have been breaking the mailing into 1000 > record increments. > > Last night when I ran this, I couldn't get hardly any throughput. > Witango > would release a record to the mailserver about every 12-15 seconds. > Normally it sends records to the mailserver just as fast as it can. > Also no > other mail usually gets through until the job is done. But > now, I see other mail being processed in between the mail > coming from Witango. > > I don't recall any changes (famous last words, I know...) and > I'd love to fix the blame on the mail server, but I can see > the records coming to it... > ever so slowly. > > Any ideas on what might cause this throttling of records to > the mail server? > > The mail server and witango are on the same box; not good I > know, but I don't have lots of volume or other users hitting > it. Oh, yeah, I took the database completely out of the > equation. Now all I have is a loop that calls the mail > action. Loops from 1 to 30 sending out a blank > text-formatted e-Mail. Still takes 12-15 seconds to release > each record to the mailserver. Mail Server is Mercury/32 if > that matters. No changes there either. > > Any ideas at all would be a help. > > Thanks, > > Tom Ferguson > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
