nobaloney
NoBaloney Internet Svcs - In Memoriam †
SpamBlocker is not a plugin. It's my name for my exim.conf file development for servers running DirectAdmin. I'm attempting to avoid confusion: the next version, when released, will be known as a SpamBlocker Technology-powered exim.conf file.
My file simply replaces the exim.conf file on your server, but it does require certain files exist in your /etc/virtual directory path.
DirectAdmin has used various earlier versions of my file for many years; I wrote my first such file soon after DirectAdmin switched from exim 3.x to exim 4.x, as DirectAdmin's original rewrite of exim.conf for Exim.4 used a script written by the author of exim; it didn't take advantage of any of the new features of Exim.4. For example, it accepted mail before checking to see if the user existed on the server.
Today DirectAdmin still uses an earlier version of my file; you can find it here (files.directadmin.com).
Even DirectAdmin's distributed version requires special files in /etc/virtual, but they've added them to the DirectAdmin install when they switched over to my file.
In the past two publishers have offered plugins to edit the files required by SpamBlocker Technology-powered exim.conf files; you can search for them on these forums. I don't know if either of them are still distributed, but I do know that neither of them manage all the files required by my latest version.
You can add the files to the DirectAdmin file editor and edit them as admin, or you can log in and manage them through the shell. I manage them through the shell, but I can't speak for others.
I don't write plugins. If I were to have one written I'd pay someone to write it and to assign copyright to me, and then I'd charge for it. But hopefully I can leave that up to someone else.
Note that documention in my beta RC versions is included mostly inline (with some important ReadMe information), but when finally released documentation will be in a separate file.
Jeff
My file simply replaces the exim.conf file on your server, but it does require certain files exist in your /etc/virtual directory path.
DirectAdmin has used various earlier versions of my file for many years; I wrote my first such file soon after DirectAdmin switched from exim 3.x to exim 4.x, as DirectAdmin's original rewrite of exim.conf for Exim.4 used a script written by the author of exim; it didn't take advantage of any of the new features of Exim.4. For example, it accepted mail before checking to see if the user existed on the server.
Today DirectAdmin still uses an earlier version of my file; you can find it here (files.directadmin.com).
Even DirectAdmin's distributed version requires special files in /etc/virtual, but they've added them to the DirectAdmin install when they switched over to my file.
In the past two publishers have offered plugins to edit the files required by SpamBlocker Technology-powered exim.conf files; you can search for them on these forums. I don't know if either of them are still distributed, but I do know that neither of them manage all the files required by my latest version.
You can add the files to the DirectAdmin file editor and edit them as admin, or you can log in and manage them through the shell. I manage them through the shell, but I can't speak for others.
I don't write plugins. If I were to have one written I'd pay someone to write it and to assign copyright to me, and then I'd charge for it. But hopefully I can leave that up to someone else.
Note that documention in my beta RC versions is included mostly inline (with some important ReadMe information), but when finally released documentation will be in a separate file.
Jeff