Agreed. Let someone else take the hit, if there is one. Someone who's
business it is to do bulk emailing knows all the ways to do
permission-oriented bulk emailing without getting in trouble! Stay away from
the "Millions" CDs, though. that'll get you in hot water. J

 

John-AldrichTile-Tools

 

From: James Kerr [mailto:[email protected]] 
Sent: Tuesday, November 17, 2009 9:14 AM
To: NT System Admin Issues
Subject: Re: Not wanting to be a spammer

 

No, your not, use constant contact. if we can afford it, you can too.

----- Original Message ----- 

From: David W. McSpadden <mailto:[email protected]>  

To: NT System Admin Issues <mailto:[email protected]>  

Sent: Tuesday, November 17, 2009 8:51 AM

Subject: Not wanting to be a spammer

 

I have an email mailer I am supposed to send out.

It is going to 12000 customers that have asked to be notified by email.

I got that script late last week and I have it set up to run from my
machine, relay off my exchange server, through my Ironport, and out my
firewall.

I do not host the mail at imcu.com and that is the address space I want to
sent it from.  In testing yesterday it seems that everyone will flag me

as a spammer because the email source can not be reverse looked up properly.
Now I do own a second domain.  imcu.org and I do have an MX record that
points to my

firewall.  This seems to be the better way to do it.  Have it come from
[email protected] but have a reply to of [email protected].

I do host the imcu.org mail server internally so I could just relay off that
smtp server through the ironport and out the firewall with little or no
worries of getting blacklisted.

 

Right???

Am I even close to thinking this through correctly??

 

 

 

 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.69/2508 - Release Date: 11/17/09
07:40:00


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

<<image001.jpg>>

<<image002.jpg>>

Reply via email to