I'm not sure what you're asking about Server Performance or Consuming. If you want to know if the "config-dir" option causes spamdyke to run slower, the answer is yes, but just barely. With that option enabled, spamdyke has to do more work to look for additional configuration files, but not very much. I haven't benchmarked it, but I doubt the difference would be measurable, even on a seriously overloaded server.
At this time, spamdyke can't block mail to invalid recipients. That feature is going to be in the next version, which I haven't finished testing yet. As soon as I can find time to finish writing the test scripts (and fix any bugs they find), I'll release it. -- Sam Clippinger On 2/11/10 12:02 AM, Jorge R. Constenla wrote: > Sam, > > Thanks, It's really cool!. Do you know about Server Performance? > Consuming? > > Another question, Can I block invalid users? I need to receive emails > only to a valid users. > Is there any way to accept only valid users and block non-existent users? > > For example: The users in example.com are 3: sa...@example.com, > f...@example.com and supp...@example.com. All emails to this address > run filters as usually, but block the rest rest like > vxsrtua...@example.com > > Thanks in advance. > > Sam Clippinger wrote: >> Yes, you can. The "config-dir" option basically lets you specify a >> different spamdyke configuration file for every domain you host. If you >> want, you can specify different configuration files for each user as >> well. You can also give different configurations for sender addresses, >> rDNS names or IP addresses. It's extremely flexible. >> >> For example, let's say you host the domain example.com, along with many >> others. The users in example.com want to block all mail from senders in >> malware.net, but you don't want to block those senders for your other >> domains. You should create a configuration directory for example.com. >> I'm going to assume you want it in /etc, but feel free to put it anywhere: >> mkdir -p /etc/spamdyke.configdir/_recipient_/com >> In that directory, you want to create a new spamdyke configuration file >> that will block the senders. >> echosender-blacklist-ent...@malware.net > >> /etc/spamdyke.configdir/_recipient_/com/example >> Finally, add the "config-dir" option to your main spamdyke configuration >> file (assuming it's named /etc/spamdyke.conf): >> echo config-dir=/etc/spamdyke.configdir>> /etc/spamdyke.conf >> >> That's it. When a message arrives for a user in example.com (e.g. >> f...@example.com), spamdyke will look in the configuration directory for >> a file named "_recipient_/com/example" within the configuration >> directory. Finding that file, it will load the contents and honor the >> options it finds. It won't load that file for any other users. >> >> You can also use other options within those files. You could turn >> graylisting on or off for a domain, you could turn on or off some >> blacklists, you can even deactivate all of spamdyke's filters for a >> domain if you want to. There are a few options that aren't allowed in >> configuration directories -- see the documentation or spamdyke's "help" >> option for a full list. >> >> -- Sam Clippinger >> >> On 2/10/10 3:53 PM, Jorge R. Constenla wrote: >> >>> The directory configuration is very complex but I think that I can't >>> block senders (domains or email) per domain that I hosts. >>> Do you know if you can do? >>> >>> Thanks in advance. >>> > > > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
