Just to be clear though, at some point in the future (hopefully next release) this behavior will change, and whitelisting will have no longer have any effect on relaying, regardless of whether spamdyke or qmail controls relaying. Correct?
On 07/30/2012 10:22 AM, Sam Clippinger wrote: > Correct -- whitelisted connections are only allowed to relay when spamdyke is > controlling relaying (i.e. it has both the "access-file" and > "local-domains-file" options). > > -- Sam Clippinger > > > > > On Jul 28, 2012, at 2:45 PM, Eric Shubert wrote: > >> While (re)reading the documentation here: >> http://spamdyke.org/documentation/README.html#RELAYING >> I noticed the following about the relay-level setting: >> normal: Prevent relaying according to the contents of the access file >> and the list of local domains. Authenticated and whitelisted connections >> will be allowed to relay. This is the default. >> >> Whitelisted connections are only allowed to relay when spamdyke controls >> authentication, no? >> >> Just to repeat my position, I think for consistency and security's sake, >> whitelisted connections should have no effect on relaying. >> Authentication and access file settings are sufficient to control >> relaying. This way, whitelisting works the same regardless of which >> authentication mechanism is used. >> >> In either case, I think the documentation could stand to be modified. >> >> Thanks Sam. >> >> -- >> -Eric 'shubes' >> >> >> _______________________________________________ >> spamdyke-users mailing list >> spamdyke-users@spamdyke.org >> http://www.spamdyke.org/mailman/listinfo/spamdyke-users -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
