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'm
On 7/28/12 1:09 AM, Eric Shubert wrote:
A potential problem just occurred to me though. QMT uses the (preferred
default) submission port 587, and includes a qmail-smtpd patch which
forces authentication (export REQUIRE_AUTH=1). While spamdyke wouldn't
typically be used on the submission port
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'm certainly glad for that! :)
I hope you'll not hesitate to let me
You have not yet begun to try my patience. :)
I guess I just don't understand the full difference between the way you think
of whitelisting and authentication. Here's how I think of them:
When I have a machine (e.g. a web server) that needs to send mail using
my mail server without
I've been testing spamdyke's auth capabilities a little, anticipating
using it to enforce encrypted passwords (when that feature comes
available). While doing so, I came across what I think is a bug.
When the access-file parameter is specified:
access-file=/etc/tcprules.d/tcp.smtp
then my
This keeps coming up and there doesn't appear to be a good fix for it within
spamdyke. I posted a patch to fix simscan here:
http://www.mail-archive.com/spamdyke-users@spamdyke.org/msg03036.html
As for not setting the RELAYCLIENT variable unless the user authenticates,
unfortunately
On 07/25/2012 10:13 AM, Sam Clippinger wrote:
As for not setting the RELAYCLIENT variable unless the user authenticates,
unfortunately that isn't possible:
http://www.spamdyke.org/documentation/FAQ.html#SUGGESTION8
Isn't possible, or isn't easy to do? Please pardon my ignorance.
In the
Well, enough information in this case refers to the options you're used in
the configuration file. If spamdyke knows what domains it controls
(local-domains-file or local-domains-entry) and knows the relaying rules
(access-file), it has enough information to control relaying and it sets
On 07/25/2012 12:28 PM, Sam Clippinger wrote:
Well, enough information in this case refers to the options you're used in
the configuration file. If spamdyke knows what domains it controls
(local-domains-file or local-domains-entry) and knows the relaying rules
(access-file), it has enough
