FrontierNet Best Practice Recommendations for Incoming Mail

This page contains FrontierNet Postmaster's best practices for e-mail senders. While following these guidelines will not guarantee that your e-mail will be delivered, it should decrease the incidence of your e-mail being misidentified as Unsolicited Bulk E-Mail (spam).

• All e-mail must be RFC compliant. Please refer to RFC Editor for more information about RFCs pertaining to e-mail.
• All e-mail servers connecting to FrontierNet's mail servers should have valid and matching forward and reverse DNS entries.
• All e-mail servers connecting to FrontierNet's mail servers must be secured to prevent unauthorized use (i.e. may not be an open proxy or open relay).
• Connections from dynamically assigned IP addresses (dial-up or DSL) will not be accepted.
• The sending mail system must limit the number of concurrent SMTP connections so as not to cause a Denial Of Service (DOS).
• Organizations may not hardcode FrontierNet's MX or mail server records into any configurations files.
• Organizations must immediately unsubscribe any FrontierNet e-mail addresses that receive a permanent failure e-mail bounce from the FrontierNet mail system.

• Organizations must not do anything that tries to hide or forge the sender or the e-mail and sending site of e-mail.
• Each mailing should specifically state how the e-mail addresses were obtained and must state whether this is a one-time mailing or a recurring mailing. Additionally, details such as the date and time when the e-mail address was obtained along with the IP address must be available upon request.
• All mailing should contain simple and obvious unsubscribe mechanisms. While we recommend a simple (working!) link to a one-click unsubscription system, a "reply to" address may also be used. In the latter case, the unsubscription address must be valid.
• Any bounce messages should be readily accepted.
• Each message must have valid non-electronic contact information (phone number, physical mailing address, etc.) for the sending organization in the text. If this is not feasible, there must be a link in each e-mail to such information on the sending organization's website.