Mididoc Productions wrote: > Hello, > > my name is mike roland. > i'm not a unix expert. > > we have a vps server with for virtual host domains. > everything is working fine so far: > the webs are accessible the mails can be sent and received. > > but we want to install a blacklist to refuse emails from certain > email-addresses for the whole server, say one list for the whole server. > > so we proceeded like in the spamassassin manual and edited the file: > /usr/local/etc/mail/spamassassin/local.cf >
First, is that the right directory? Run spamassassin --lint -D and see what SA claims to be using for the "site rules" directory. You need your local.cf to be in that directory. > we inserted a blacklist entry: blacklist_from [EMAIL PROTECTED] > > we have also rebooted the server, but it is not working. > emails from the address: [EMAIL PROTECTED] are stil beeing received. > > could anybody please help us setting the blacklist? > First, let's clarify.. Are the messages being received with a spam tag, or are they not even tagged as spam? Are you trying to avoid receiving the messages (ie: not accept them to the mailserver at all), or are you trying to force them to be tagged as spam (which may result in being auto-deleted by a mailbox tool of some sort, or may just cause the tag)? Generally speaking, unless you're using a milter or other MTA layer configuration spamassassin will NOT stop the message from being received. Your typical procmail call method happens after the mail has been accepted by the server. At that point, all SA can do is tag the message. From there, other tools can delete, or whatever, based on SA's tagging. In general, things which actually alter message delivery are handled by the tool that calls SA, not SA itself. SA has no control over the mail queue, so it can't delete mail. However, many tools that call SA can take such actions based on what SA reports. Do you know what tool you're using to call SA?
