Olá ...
Bom ... O qmail-scanner não coloca mensagens em quarentena, pelo menos não até a versão que eu tenho :-), quem faz isso é o procmail ... Pq não usa o procmail dessa forma para testar: # cat /etc/procmailrc # Arquivo de LOG LOGFILE=/var/log/procmail.log # Processa e envia o que fugir da regra para stdout DEFAULT="|" # Verificar mensagens com spamassassin :0fw | /usr/bin/spamassassin # REGRA: Tudo que vier com cabeçalho: X-Spam-Status: Yes manda para a pasta abaixo :0: * ^X-Spam-Status: Yes <COLOQUE AQUI UMA PASTA> Onde esta escrito para colocar a pasta, se você colocar ./Maildir que nem vc tem ele vai gravar o spam na pasta Maildir/new Espero q ajude em algo ... []´s Marcio Em algum lugar da terra, em algum momento, essa pessoa : Rodrigo Fortes disse e ainda tem dito até aqui. > > De tanto mecher, acabei fazendo bobagem... > Agora o spam chega com o flag X-Spam-Status: yes, porém o qmail-scanner > não o joga mais em quarentena.... alguma dica? > > > Segue meu procmailrc, local.cf e user_prefs respectivamente: > > ################PROCMAILRC ###################################### > > :0fw > | /usr/bin/spamassassin > :0 > * ^X-Spam-Status: Yes > ./Maildir/ > > _________________________________________ > > ########################## LOCAL.CF > ####################################### > > # SpamAssassin config file for version 2.5x > # generated by http://www.yrex.com/spam/spamconfig.php (version 1.01) > > # How many hits before a message is considered spam. > required_hits 4.0 > > # Whether to change the subject of suspected spam rewrite_subject 1 > > # Text to prepend to subject if rewrite_subject is used subject_tag > *****SPAM***** > > # Encapsulate spam in an attachment > report_safe 1 > > # Use terse version of the spam report > use_terse_report 0 > > # Enable the Bayes system > use_bayes 1 > > # Enable Bayes auto-learning > auto_learn 1 > > # Enable or disable network checks > skip_rbl_checks 0 > use_razor2 1 > use_dcc 1 > use_pyzor 1 > report_header 1 > detailed_phrase_score 1 > spam_level_stars 1 > > ___________________________________________________________ > > ################ USER_PREFS ##################### > > > # SpamAssassin user preferences file. See 'perldoc > Mail::SpamAssassin::Conf' # for details of what can be tweaked. > #* > #* Note: this file is not read by SpamAssassin until copied into the > user > #* directory. At runtime, if a user has no preferences in their home > directory > #* already, it will be copied for them, allowing them to perform > personalised > #* customisation. If you want to make changes to the site-wide > defaults, > #* create a file in /etc/spamassassin or /etc/mail/spamassassin instead. > ######################################################################## > ### > > # How many hits before a mail is considered spam. > required_hits 4 > > # Whitelist and blacklist addresses are now file-glob-style patterns, so > # "[EMAIL PROTECTED]", "[EMAIL PROTECTED]", or "*.domain.net" will all work. > # whitelist_from [EMAIL PROTECTED] > > # Add your own customised scores for some tests below. The default > scores are # read from the installed spamassassin rules files, but you > can override them # here. To see the list of tests and their default > scores, go to # http://spamassassin.org/tests.html . # score > SYMBOLIC_TEST_NAME n.nn > > # Speakers of Asian languages, like Chinese, Japanese and Korean, will > almost # definitely want to uncomment the following lines. They will > switch off some # rules that detect 8-bit characters, which commonly > trigger on mails using CJK # character sets, or that assume a > western-style charset is in use. # > score HEADER_8BITS 0 > score HTML_COMMENT_8BITS 0 > score SUBJ_FULL_OF_8BITS 0 > score UPPERCASE_25_50 0 > score UPPERCASE_50_75 0 > score UPPERCASE_75_100 0 > > > > > > Links do Yahoo! Grupos > Para visitar o site do seu grupo, acesse: > http://br.groups.yahoo.com/group/qmail_br/ > > Para sair deste grupo, envie um e-mail para: > [EMAIL PROTECTED] > > O uso que você faz do Yahoo! Grupos está sujeito aos: > http://br.yahoo.com/info/utos.html > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > >
