Project

General

Profile

Tâche #10089

Scénario #9912: En tant qu'administrateur du serveur, je veux une procédure de bascule, pour éviter un arrêt de service trop long

Neutraliser l'anti-spam

Added by Joël Cuissinat almost 8 years ago. Updated almost 8 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Target version:
Start date:
12/15/2014
Due date:
% Done:

0%

Estimated time:
2.00 h
Remaining (hours):
0.0

Description

Laisser tourner l'anti-spam mais sans qu'il bloque les messages dans un premier temps afin d'étudier son comportement => patch à réaliser ?

History

#1 Updated by Joël Cuissinat almost 8 years ago

  • Status changed from Nouveau to En cours

#2 Updated by Daniel Dehennin almost 8 years ago

Au lieu de le neutraliser nous allons éviter qu’il renvoi un code 5XX tout en conservant les logs afin de régler les filtres spamassassins plus tard.

Modifier le fichier /etc/exim4/eole.d/acl/spamassassin.conf afin de mettre en commentaire la commande fakereject et l’ajout des entêtes :

# Invoke SpamAssassin to obtain $spam_score and $spam_report.
# Depending on the classification, $acl_m9 is set to "ham" or "spam".
#
# If the message is classified as spam, pretend to reject it unless
# user is authenticated.
#
warn
  !authenticated = *
  set acl_m9  = ham
  spam        = nobody:true
  condition   = ${if >= {$spam_score_int}{SPAM_SCORE}{1}{0}}
  set acl_m9  = spam
#  control     = fakereject
#  logwrite    = :reject: Rejected spam (score $spam_score)

# Add an appropriate X-Spam-Status: header to the message.
#
warn
  !authenticated = *
#  add_header  = X-Spam-Status: ${if eq {$acl_m9}{spam}{Yes}{No}}
#  add_header  = X-Spam-Score: $spam_score
  logwrite    = :main: Classified as $acl_m9 (score $spam_score)

#3 Updated by Daniel Dehennin almost 8 years ago

  • Status changed from En cours to Résolu

#4 Updated by Daniel Dehennin almost 8 years ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) changed from 2.0 to 0.0

Also available in: Atom PDF