On Jul 28, 2012, at 12:09 AM, Eric Shubert wrote:
> Sam,
>
> Thanks so much for your very clear and thoughtful reply. I'll comment as
> we go this time so I don't need to establish context.
>
> On 07/26/2012 02:12 PM, Sam Clippinger wrote:
>> You have not yet begun to try my patience. :)
>
> I
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://s
I understand what you're saying -- whitelists shouldn't always override
blacklists. But if I tried to change this, how would it work? Perhaps
whitelisting a specific address (e.g. u...@domain.com) would override a domain
blacklist (e.g. @domain.com) while blacklisting a specific address would
I imagine whenever I get around to implementing SPF and DKIM, I'll add some
options to specify what to do with matching connections -- whether they should
be blocked if they don't match, if headers should be added, if they should
always be trusted, etc.
I can make the change in the TODO file, b
On 07/30/2012 09:58 AM, Sam Clippinger wrote:
> Here's yet another chance for me to say that I *still* don't understand the
> need for a whole separate port
> for authenticated connections. On my servers, I configure ports 25 and 587
> exactly the same and mail clients
> can use whichever one ma
Understood. Thanks.
On 07/30/2012 11:02 AM, Sam Clippinger wrote:
> I imagine whenever I get around to implementing SPF and DKIM, I'll add some
> options to specify what to do with matching connections -- whether they
> should be blocked if they don't match, if headers should be added, if they
Not that it matters, but I agree with Sam on this.
Personally, I don't whitelist yahoo.com, and I wouldn't use a dnswl that
included them (nor any other major ESP). Let the chips otherwise fall
where they may. If one of yahoo's IPs happens to get blacklisted,
there's likely a good reason for it
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
