RE: Removing bad emails from newsletter db

2003-05-29 Thread Neil Middleton
If you are interested only in people who read the mail and you send your mail as HTML, include a CFCONTENT'ed image in the HTML e.g http://server/[EMAIL PROTECTED]" height="1" width="1"> and then collect the email addresses found by your cfm and ditch the rest of them... Neil > -Original M

Re: Removing bad emails from newsletter db

2003-05-29 Thread Critz
oi Blood!! have a gander at http://www.mach5.com mach5 mailer... Wednesday, May 28, 2003, 11:39:45 AM, you wrote: BP> One of my client's has about 103k people in his mailing list. He's running BP> his website since 99 and many of these e-mails are bad one

RE: Removing bad emails from newsletter db

2003-05-29 Thread Ezine
Have the e-mail come back to an address you pick up with cfpop.. then parse the e-mail for keywords.. such as 'Undeliverable' and 'not deliver' and 'delivery failure' and 'quota'.. and 'transient delivery failure' etc... -Zine -Original Message- From: Python Python [mailto:[EMAIL PR

RE: Removing bad emails from newsletter db

2003-05-29 Thread jon roig
: Andre Mohamed [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 11:51 AM To: CF-Talk Subject: RE: Removing bad emails from newsletter db Blood, It's fairly straight forward to code yourself. You can access the undeliverables folder using CFDIRECTORY and then parse the messages fo

RE: Removing bad emails from newsletter db

2003-05-29 Thread Mark W. Breneman
I have the same problem. I have thought up several possible ways, but there is no good answer that I know of. The best method that I have come up with is to assign a very identifiable ID to each email address and include it in the bottom of the email newsletter body. Then use outlook to check t

RE: Removing bad emails from newsletter db

2003-05-29 Thread Andre Mohamed
Blood, It's fairly straight forward to code yourself. You can access the undeliverables folder using CFDIRECTORY and then parse the messages for the e-mail address that bounced and use that to update the database. If on MX I suggest using server.coldfusion.rootDir etc. to locate the undeliverabl