How to send Bulk email with SMTP server

If you follow the link it is pretty self explanatory. You need to rate limit your mail and if still blocked contact them. Be prepared to show that that the user opted in with logged date, ip, etc.

Maybe not in this instance but as a general rule you may need to look at the content of your message and see if it looks like spam. By slightly adjusting your mail to remove or change elements commonly seen in spam you can drastically reduce your chances of being blocked.

Consider registering with dnswl.org. There are also a few open services which will verify your configuration.

• Definitely get rDNS right, and use a subdomain for the host. eg. mail.example.com not example.com. Ensure you have a proper static IP address which is not listed with spamhaus.org. Avoid using any part of your IP address in the DNS name.
• Match the mailserver name configured in your software to the DNS name.
• Do setup the required postmaster and abuse email addresses.
• Ensure callouts for the sender addresss works, at least for the target server.
• Consider implementing Bounce Address Tag Verification (BATV) to allow verification of bounce notices.
• Definitely do SPF correctly. While spammers use it, it will help prevent spammers from using your address. Also do SPF for the server. See the FAQ at open http://www.openspf.org/.
• DKIM will authenticate the signed contents which may be useful for your purposes. It doesn't have much impact on spam scores. I am finding that a lot of the existing signers have broken implementations.
• Do setup appropriate policies for email being sent and received. Implement as many of these in the server as possible to limit incoming email.
• Limit the servers you relay for to those inside your LAN which need to send email. Only accept email for your domain.

I have a post on Running an Email Server with some other comments. Its a bit of a rant as several legitimate posters send email that looks very much like Spam due to poor email implemenations.

EDIT: Typically services like smtp, mail, and www have service related names (sub-domains). In some cases these will have numerical suffixes like smtp2 or www1. This makes it simple to provide the services on different servers simple. The servers usually have their own hostname (sub-domain) which is unrelated to the sevice(s) they provide. These days the domain may be used for web traffic, but is is often immediately redirected to the web sub-domain.