The other drawback of a tcpserv approach is that an intelligent spam
sender software will handle it as temporary error (unable to create
connection to smtp server) and will try again and again until the max
queue lifetime of the mail is reached. With spamdyke blacklist it gets a
permanent
Sam Clippinger wrote:
I could do that if it would be useful. Now is the time for changes like
this, since version 4.0 won't be backwards compatible anyway. What
about changing the log message for other reasons too? For example,
ALLOWED_WHITELISTED_IP, ALLOWED_WHITELISTED_SENDER, etc.
Sam Clippinger wrote:
ALLOWED_GRAYLISTED could be useful if graylisting isn't active for all
domains.
I'd be useful if graylisting all domains too, to find out how many senders
did not retry (due to, most probably, being spammers).
Regards,
--
Daddy, what Formatting drive C: means?...
Sam Clippinger wrote:
I can always use help writing documentation. Let me finish making the
updates for the version 4.0 changes, then I'll send them to you to see
if you think they need polishing. Thanks!
BTW: documentation lacks information of default values, for options
like
On Thu, Apr 24, 2008 at 09:51:05AM +0200, Bgs wrote:
The other drawback of a tcpserv approach is that an intelligent spam
sender software will handle it as temporary error (unable to create
connection to smtp server) and will try again and again until the max
queue lifetime of the mail is
On Wed, Apr 23, 2008 at 07:04:09PM +0200, Marcin Orlowski wrote:
I've already made this change in version 4.0.0 -- it has a new flag to
allow spamdyke to create domain folders itself. It can't be automatic
because some sites need the ability to activate/deactivate graylisting
for
The defaults are described in the text of each section in the README
file but not in the table that shows all of the configuration options...
I didn't realize that. The defaults are printed in the help screen when
you run spamdyke -h.
I'll add the defaults to the usage section of the README
Interesting idea. I'll put that on my list for a future version.
-- Sam Clippinger
Andras Korn wrote:
On Thu, Apr 24, 2008 at 11:21:51AM +0200, Bgs wrote:
Add another dot to your me-too-list :)
Adding more info about which rule allowed or disallowed a specific mail
would help both in
Yes, but, by definition, any e-mail that is ALLOWED on a domain that has
greylisting enabled, is an ALLOWED GREYLIST, since all e-mails would be
greylisted prior to being allowed. :-)
Sam's point about the e-mail possibly being sent sufficiently delayed that
it is actually in a different log,
Good point, although, I would think an appropriate log tag would be ALLOWED
GREYLIST_WHITELIST, not ALLOWED GREYLIST... And, that may have been
mentioned in this thread at some point...The e-mails have been flying on
this one! :-)
Michael J. Colvin
NorCal Internet Services
www.norcalisp.com
You are correct -- authenticated connections should bypass graylisting
and all other filters. If that isn't working, your users should be
reporting lots of problems, because their MUAs (e.g. Outlook,
Thunderbird) won't be able to deliver email to your server -- they'll
get the graylist
Hi,
I'd love to see sort of test mode. So I could i.e. enable
log-ip-in-cc-rdns which would work the same way known
reject-ip-in-cc-rdns works but without really denying
matching connection. It shall just log it (i.e. as
TEST_IP_IN_CC_RDNS) and that's it. That would be extremely
useful to run on
Very interesting idea. I'll definitely put that one on the list.
-- Sam Clippinger
Marcin Orlowski wrote:
Hi,
I'd love to see sort of test mode. So I could i.e. enable
log-ip-in-cc-rdns which would work the same way known
reject-ip-in-cc-rdns works but without really denying
matching
Now that one I like. :-)
Michael J. Colvin
NorCal Internet Services
www.norcalisp.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Marcin Orlowski
Sent: Thursday, April 24, 2008 11:50 AM
To: spamdyke users
Subject: [spamdyke-users]
14 matches
Mail list logo
