>From the Spamdyke Documentation:
One form of wildcard address is supported. All usernames within a domain
(and its subdomains) may be blocked by a line starting with @. For example,
if the file contained the following entry:
@example.com
spamdyke will block mail to f...@example.com, f...@m
It works with rdns-blacklist-entry=.info
But NO :
sender-blacklist-entry=.info
for example:
An email from : j...@peru.info was send from server : peru.com is not block
2009/6/23 Ulrich C. Manns
> Ok, do you need to block all email from servers from domains .info?
> This works with r
There seems to me to be a bug in the way that python authenticates smtp
sessions. 'preferred_auths' is an array of authentication types. If the
first type fails, other types are not attempted, and perhaps should be.
I'm not sure if Eudora uses the standard python libraries or not, but if
it doe
Yes i know that cram-md5 doesn't work on my
server, but normally with spamdyke disabled
Eudora after cram-md5 try to auth with login and
finally auth in plain. With spamyke activated
Eudora try to auth in CRAM-MD5 and STOP! This is
the strange issue...with other clients everything works perfec
