Unsupported scripts and control panel web app for a hosting company
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  1. <?PHP
  2. define('SUPPORT_TITLE', 'Spam prevention');
  3. define('SUPPORT_BTITLE', 'Spam prevention');
  4. if (!defined('LIB_ACCOUNT')) { require('lib/account.php'); }
  5. addDashboardItem('Useful links', 'E-mail settings', 'email');
  6. if (!defined('UID')) {
  7. addDashboardItem('Useful links', 'Login', 'login');
  8. }
  9. $sbody = <<<SUPPORT
  10. <p>
  11. All mail received by UTD-Hosting's mail servers is ran through several filters
  12. to help prevent spam. These filters should never affect any legitimate mail.
  13. </p>
  14. <p>
  15. The checks performed on incoming mail reject messages from servers that do not
  16. identify themselves correctly when connecting. This stops around 45% of all
  17. spam messages sent to UTD-Hosting's servers. All legimate e-mail servers will
  18. identify themselves properly (and are required to do so by the protocol
  19. specifications).
  20. </p>
  21. <p>
  22. The address of the remote server is then checked against four blacklists -
  23. <a href="http://www.sorbs.net/">sorbs</a>, <a href="http://www.ordb.org/">ordb</a>, <a href="http://www.dsbl.org/">dsbl</a> and <a href="http://www.spamhaus.org/">spamhaus</a>. These blacklists block known spammers and vulnerable machines
  24. which may be used to relay spam. Again, legitimate e-mail servers rearely find
  25. their way on to spam blacklists (and when they do, there's a simple de-listing
  26. process), so legitimate mail shouldn't be stopped.
  27. </p>
  28. <p>
  29. In a sample of mail received over twenty four hours, these processes stopped 86% of spam mail, with 0 false positives.
  30. </p>
  31. SUPPORT;
  32. define('SUPPORT_BODY', $sbody);
  33. ?>