On Tue, Nov 17, 2009 at 8:51 AM, David W. McSpadden <[email protected]> wrote: > In testing yesterday it seems that everyone will flag me > as a spammer because the email source can not be reverse looked up > properly.
You also have an SPF record. You'll have to set that properly, or your message is likely to get judged as spam. That will in turn be likely to propagate to IP and domain reputation lists. > 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]. If you are going to do things that way, you would want to have the SMTP envelope sender be <[email protected]>, and the RFC-822 "From:" header be <[email protected]>. Don't use "Reply-To:" at all. But, if your problem was only reverse DNS, you could simply get your ISP to provision a PTR with a RHS of <something.imcu.org>, configure your outgoing mail server to HELO as <something.imcu.org.>, and use <imcu.com> everywhere else, including the SMTP envelope. Reverse DNS is not your only problem. > 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. Bulk mail risks blacklisting problems even if your DNS and SMTP infrastructure is configured properly. Lusers will report your mail as spam even though they asked for it. That may cause your IP address and/or domain names to get a spammer reputation. As others have suggested, if you don't have experience in this area, you're better off outsourcing this aspect to a third-party service that specializes in this sort of thing. Constant Contact is just one of many such services. Google "email marketing". Even if you're not, strictly speaking, doing marketing with this, it's close enough. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
