Re: [AMaViS-user] Defanging Mails does not work as expected

[Sven <dur...@dy...>]

Mark Martinec schrieb:

Hi
Thanks for your reply. I shortened the mail a bit to make it easier to read.

[...snip...]

>> If one does not want altermime this has to be configured explicitly.
> 
> True, the:
>   $defang_spam = 'attach';
> should suffice.
> 
>> I did set up a corresponding 
>> ruleset for my domain but it doesn't work. Can someone point me into the
>> right direction? This is my rule for defanging incoming mails:
>>
>> $defang_maps_by_ccat{+CC_SPAM} = [
>>     { # a per-recipient hash lookup table
>>     '.dynamik.sytes.net'  => 'attach',
>>    },
>>    $defang_spam,  # fallback to old style setting if no match above
>> ];
> 
> Appears alright.
> Does recipient address match the '.dynamik.sytes.net' ?

Yes it does. All of my users are using a localpart with this domainpart.
(e.g. us...@dy...) At least the user I'm using for testing 
puposes does. Its not a multi-domain setup. The server I'm using is 
responsible only for this domain.

> Are there any other assignments to a %defang_maps_by_ccat hash?

Indeed, there are more assignments. I have made the following assignment 
for adding disclaimers:

$defang_maps_by_ccat{+CC_CLEAN} = [ 'disclaimer' ];
  $policy_bank{'MYUSERS'} = {
      allow_disclaimers => 1,
};
$defang_maps_by_ccat{+CC_SPAM} = [
     { # a per-recipient hash lookup table
     '.dynamik.sytes.net'  => 'attach',
    },
    $defang_spam,  # fallback to old style setting if no match above
];


As this only refers to CC_CLEAN I don't think this is a problem, isn't 
it? In amavisd.conf it is above the +CC_SPAM assignment, so if they are 
concurring, the CC_CLEAN assignment should be overwritten by the CC_SPAM 
assignment.


> You may send me a log privately to save bandwidth or protect privacy.

I attached a anonymized log. May it help others with the same problem. 
It says that amavis is using altermime for mangling. For creating this 
log entry I used an external mailaccount for sending a mail wich should 
be classified as spam to a local recipient (mail from: 
se...@ot...). As I used an external sender, the policy bank 
'MYUSERS' gets not involved and so is discl_allowed=0

> 
>   Mark

regards,
Sven