Difference between revisions of "Spamdyke"
From Atomicorp Wiki
| Line 8: | Line 8: | ||
'''RHEL4/CentOS4''' | '''RHEL4/CentOS4''' | ||
| + | |||
Spamdyke under el4 (CentOS4 and RHEL4) does not create dynamic executables, and is therefore in conflict with the stack protection in the ASL kernel. As such spamdyke is not supported under ASL in *ANY WAY*. | Spamdyke under el4 (CentOS4 and RHEL4) does not create dynamic executables, and is therefore in conflict with the stack protection in the ASL kernel. As such spamdyke is not supported under ASL in *ANY WAY*. | ||
'''Plesk''' | '''Plesk''' | ||
| + | |||
As a general recommendation, all RBL's should be implemented in spamdyke, and not through the plesk interface. This allows blacklisted hosts to still send mail using authentication | As a general recommendation, all RBL's should be implemented in spamdyke, and not through the plesk interface. This allows blacklisted hosts to still send mail using authentication | ||
Latest revision as of 13:17, 11 February 2009
[edit] Overview
www.spamdyke.org
[edit] Known Issues
RHEL4/CentOS4
Spamdyke under el4 (CentOS4 and RHEL4) does not create dynamic executables, and is therefore in conflict with the stack protection in the ASL kernel. As such spamdyke is not supported under ASL in *ANY WAY*.
Plesk
As a general recommendation, all RBL's should be implemented in spamdyke, and not through the plesk interface. This allows blacklisted hosts to still send mail using authentication
