Yes. The feature uses the same logic used by qmail's processes to determine if a recipient is valid. qmail's internal logic is (supposedly) documented in various man pages (qmail-send, qmail-control, qmail-users, addresses, envelopes, dot-qmail), on DJB's website and in some documentation files included with qmail's source. However, because those sources are often vague, contradictory and (in places) completely wrong, some reverse-engineering of qmail's source code is required to really understand how it works.
Anyway, spamdyke will do what qmail does. That includes (but is not limited to) checking rcpthosts, morercpthosts, virtualdomains, smtproutes, the user's home directory, the home directory of the "alias" user, etc. If I've done my job right, the only messages that will slip through are those that are rejected by add-on programs (e.g. mailing list managers). This will cover all of the "normal" qmail installations, including QmailToaster, QmailRocks, Life With Qmail and others. Heavily patched qmail installations that store their user databases outside of the filesystem (Plesk) won't be able to use this feature yet, because I haven't implemented a way for spamdyke to use external "helper" scripts that can evaluate recipients. I'll probably add that feature in a version soon following this one, however. -- Sam Clippinger [email protected] wrote: > Hello > > Hopefully it will only apply to local domains (like a flag to only do > receipt check for specified domains) and not check for all domains > that reside on remote servers. > > example: I filter many domains via the spamdyke server, but the > domains have their own domains file and smtproutes (dns mx records > point to the spamdyke server), pointing to the second server which > does not run spamdyke. This way I get the benefit of the spamdyke > filtering without need for it to be on the server that will not run it. > > Best > Greg > > | very nice to hear that! looking forward to test it ;) > | > | Otto > | > | Sam Clippinger schrieb: > |> Yes, this suggestion has come up many times. I'm mostly done with > |> implementing this feature now (though not exactly as you describe > it). I > |> have to fix some remaining bugs and finish testing, then it'll be > |> available. > |> > |> -- Sam Clippinger > |> > |> Otto Berger wrote: > |>> Hi all, > |>> > |>> the discussion about this is quite as old as spamdyke. But is there > |>> anything new on this? > |>> > |>> is it maybe a way to provide a simple hook to spamdyke so it can > run an > |>> external check-programm or script? That programm could check via a > |>> ENV-vars the recipient-address an return true or false or something. > |>> > |>> recipient-blacklist-plugin=/bin/check_for_invalid_recipient.sh > |>> recipient-whitelist-plugin=/bin/check_for_valid_recipient.sh > |>> > |>> i know its not the best and high performance solution, but maybe > |>> (relative) easy to implement an i think there will be soon much > |>> "plugins" to check valid recipients against databases, files etc... > |>> > |>> Otto > |>> _______________________________________________ > |>> spamdyke-users mailing list > |>> [email protected] > |>> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > |>> > |> _______________________________________________ > |> spamdyke-users mailing list > |> [email protected] > |> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > | _______________________________________________ > | spamdyke-users mailing list > | [email protected] > | http://www.spamdyke.org/mailman/listinfo/spamdyke-users > | > | > ------------------------------------------------------------------------ > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
