On 02/02/2012 09:50 PM, Eric Shubert wrote:
On 02/02/2012 08:47 PM, Casey Price wrote:
Yes. It's not exactly trivial to do, but it can be done using spamdyke
configuration directories.
See http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR
Basically, you would set up separate configuration directories for
each domain.
Thanks Eric. So essentially could I set it up so that there was a config
directory for domain1.com, which had a blacklist_senders file for
change.org? If that is the case, would I need a config directory for
every domain?
I don't think so. Just a default one, and one other for the
non-default domain.
Looks like I'd either want to user the ../_sender_/ or
../_recipient_/ directory. The examples on spamdyke's site look like
they are for individual email addresses. How would I apply it to the
whole domain?
Just leave off the recipient's account.
For example...
To create a file using the sender's email address, first create a
directory structure that begins with|_sender_|and contains directories
using the domain portion of the sender's email address with its words
reversed and ending in|_at_|. For example, if the sender's email address
is|[email protected]|, the directory structure should look like this:
|.../_sender_/com/example/home/_at_|
The sender's username is used as the name of the configuration file. For
example:
|.../_sender_/com/example/home/_at_/mom|
So using the example above, how would I create a rule that applied to
the entire @home.example.com domain?
"home" would be the name of the configuration file instead of being a
directory. The documentation explains this a little further down:
spamdyke will match partial IP addresses, rDNS names, sender email
addresses or recipient email addresses left-most portions of the
directory structure are omitted. Note: spamdyke will never read a
configuration file named _at_. If the sender's or recipient's username
are omitted, the _at_ directory must be omitted as well. For example,
if the IP address is 11.22.33.44, the rDNS name is
mail.internal.headquarters.example.com, the sender's email address is
[email protected] and the recipient's email address is
[email protected], spamdyke will look for configuration files
with the following paths:
.../_ip_/11/22/33/44
.../_ip_/11/22/33
.../_ip_/11/22
.../_ip_/11
.../_rdns_/com/example/headquarters/internal/mail
.../_rdns_/com/example/headquarters/internal
.../_rdns_/com/example/headquarters
.../_rdns_/com/example
.../_rdns_/com
.../_recipient_/com/example/school/_at_/kid
.../_recipient_/com/example/school
.../_recipient_/com/example
.../_recipient_/com
.../_sender_/com/example/home/_at_/mom
.../_sender_/com/example/home
.../_sender_/com/example
.../_sender_/com
HTH.
Another option, remove the blocking from spamdyke and do something like
this in spamassassin:
blacklist_from *@change.com
header __SENT_TO_DOMAIN1 ToCC =~ /\bdomain1\.com/i
header __FROM_CHANGE From =~ /\@change\.org/i
meta ALLOW_CHANGE_TO_DOMAIN1 (__SENT_TO_DOMAIN1 && __FROM_CHANGE)
describe ALLOW_CHANGE_TO_DOMAIN1 Email from change.org to domain1.com
score ALLOW_CHANGE_TO_DOMAIN1 -100.0
This can all go in your local.cf file, probably better if you have
separate files for blacklist entries and local rules.
Brent Gardner
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
