blacklist_to does not work?

[Komandur N Kannan <it...@sevenseasgroup.com>]

Hello,

We use MDaemon mail server with SA. I wanted to block certain 
recepient addresses from being receiving email. So I added this 
address as "blacklist_to" in local.cf file. However this does not 
seem to have any effect. Alt-n advised me to use this forum which 
should hopefully provide a solution.

Any assistance would be much appreciated.

Thank you
Kannan


***************************************
K N Kannan
Manager - IT & Communications
Seven Seas Shipchandlers/Group
P O Box 5592
Dubai
United Arab Emirates
Ph : +971 4 8033 300, Fax +971 4 8033 309
Mobile: +971 50 4551920
URL : http://www.sevenseasgroup.com/
***************************************
=====================================================================
THIS EMAIL IS CONFIDENTIAL AND COULD BE PROTECTED BY LEGAL PRIVILEGE.
IF YOU ARE NOT THE INTENDED RECIPIENT, YOU SHOULD NOT COPY IT,
RE-TRANSMIT IT, USE IT OR DISCLOSE ITS CONTENTS, AND SHOULD RETURN IT
TO THE SENDER IMMEDIATELY AND DELETE YOUR COPY FROM THE SYSTEM.
===================================================================== 

Re: blacklist_to does not work?

[Matt Kettler <mk...@verizon.net>]

Komandur N Kannan wrote:
> Hello,
>
> We use MDaemon mail server with SA. I wanted to block certain
> recepient addresses from being receiving email. So I added this
> address as "blacklist_to" in local.cf file. However this does not seem
> to have any effect. Alt-n advised me to use this forum which should
> hopefully provide a solution. 

Well, this won't work based on the recipient unless your MTA inserts
clues in the Received: headers.

In general, this will only work if the message's To: or Cc: header
contains the stated address.

So, if you've blacklist_to'ed demo@example.com, that account can still
receive email without being tagged as spam, provided it's effectively
"bcc'ed" to them, and not addressed To: or Cc: them in the headers.

A much more effective way would be to configure the MTA to just refuse
to accept mail for that user at the transport level. (provided it's not
an RFC required address like postmaster, abuse, etc)


That said, if that's not much help, I'll admit I have no significant
knowledge of MDaemon. MDaemon is a commercial product with it's own
support. I have very little idea of how MDaemon works, or how it has
integrated SA, and I'm not sure if it really is technically SpamAssassin
anymore, or a "derivative work".

For example, my first questions of a normal unix platform SA user would be:

    what file did you add this to? /etc/mail/spamassassin/local.cf? a
user_prefs? Which user?
    Do you use spamd? Did you restart it?

However, I don't know if those questions are even applicable to MDaemon,
and I doubt they would make much sense to you.

I'd suggest trying MDaemon's support, unless you happen to bump into
someone on this list who happens to be familiar with MDaemon's quirks.