Sending mail from dedicated server 101?

Which pitfalls do I have to avoid

[the_nerd]

I've been using dedicated serves for years now, but always used the hosting company's mail server for smtp.

Now more and more mails get blocked (especially from customers at universities). "Adress may be forged" / relaying not allowed" ....

So I tried the SMTP Server on my box (using 127.0.0.1 as server-name). First attempt: Using my Private Yahoo acct. They placed the mail directly in the bulk-folder.

Anything I have to configure (someone once mentioned "reverse lookup zone" to me) - so my E-Mails don't wind up in a spam box.

Thankful for any insight, nerd.

[MatthewHSE]

Have you looked into the new SPF guidelines?

[the_nerd]

no. Is there a good description available somewhere?

[richlowe]

I have hosted my email on my own server. It's more trouble than it's worth, in my opinion.

Things to be aware of:

1) New SPF standard
2) Reverse PTR record in zone
3) At least TWO servers in case one is down
4) Ensure your server is not an open relay
5) Check #4 again
6) Check #4 again
7) Have an expert check #4 again

My server was NOT an open relay, yet the spammers tried on multiple occasions to send using it. In fact, at least once a week I would look in my logs and find my server had received over 100,000 emails from some spammer to 100,000 different addresses. All blocked, of course, yet still slowing down the system and straining my patience.

I decided to leave these hassles to professional email services.

Richard

[the_nerd]

richlove,

thanks for your advice. I'll take care of #4 ;-)

I will only use the server to send out mails that are generated on this server (welcome emails, order confirmations, ..)

If the Server is set to not accept any e-mail, could a spammer still succeed in slowing me down? How would he find the server in the first place?

What exactly do you mean with the second server? I guess you also use yours to receive e-mail. If my app server is down, there's nothing to send out anyway.