clean mail ending up in quarantine

Sun Nov 18 02:42:41 CET 2012

Hi,

yes a copy of every message (tested only clean, bad header, spam and virus at the moment).

I tried to set each _quarantine_method and each _quarantine_to variable to undef. Only storage_sql_dsn is set. Even in this setup everything gets stored as a copy in the database regardless of the final_*_destiny settings (if they have an influence at all). Only setting storage_sql_dsn to undef deactivates the database storage, but for everything. I thought you could control the behavior of each function by the quarantine_method and _quarantine_to individually. But this seems to be ignored if storage_sql_dsn is set.

I don't know if this is wanted behavior or a bug. Maybe still misconfiguration on my side. Eventually one of the coders knows it better as I'm not into perl.

Best regards,
Daniel

Am 17.11.2012 um 06:33 schrieb Patrick Ben Koetter <p at sys4.de>:

> * Daniel Lopes <professormobilux at web.de>:
>> Hi,
>> 
>> thank you for the answer and sorry my fault, used a web mailer, that's what you get. Hopefully this mail is better formatted.
>> 
>> I've set up an installation of amavis-new 2.7.1 and it is working fine.
>> 
>> The next step was to setup the quarantine to be in a mysql databse what is
>> working also fine besides clean mail is getting there as a copy too.
> 
> Are you saying a copy of _every_ message passing amavis gets stored in the
> quarantine database or are _some_ messages getting there.
> 
> If some messages are delivered to the quarantine, they might be classified 
> SPAM by spamassassin and amavis acts out what it should, i.e. send
> $spam_quarantine_method to sql, which is what you configured.
> The same goes for BANNED.
> 
> Have you tried to unset *_quarantine_method and sent a test message? If the
> messages doesn't get quarantined, you could selectively re-enable
> _quarantine_method one by one sending a test message every time and see which
> _quarantine_method triggers the quarantine.
> 
> Then we could try to find out what filter rule makes the trigger call for an
> action.
> 
> p at rick
> 
> 
>> My configuration looks like this so far:
>> 
>> $final_virus_destiny      = D_DISCARD;
>> $final_banned_destiny     = D_DISCARD;
>> $final_unchecked_destiny  = D_PASS;
>> $final_spam_destiny       = D_DISCARD;
>> $final_bad_header_destiny = D_DISCARD;
>> 
>> $virus_quarantine_to      = 'virus-quarantine';
>> $banned_quarantine_to     = 'banned-quarantine';
>> $unchecked_quarantine_to  = undef;
>> $spam_quarantine_to       = 'spam-quarantine';
>> $bad_header_quarantine_to = 'bad-header-quarantine';
>> $clean_quarantine_to      = undef;
>> $archive_quarantine_to    = undef;
>> 
>> $virus_quarantine_method              = 'sql:';
>> $banned_files_quarantine_method       = 'sql:';
>> $spam_quarantine_method               = 'sql:';
>> $bad_header_quarantine_method         = 'sql:';
>> $unchecked_quarantine_method          = undef;
>> $clean_quarantine_method              = undef;
>> $archive_quarantine_method            = undef;
>> 
>> I would like to have only virus, banned, spam and bad header mails in the db quarantine. I thought the above configuration would accomplish that but it seems I'm missing something.
>> 
>> Can someone point me in the right direction?
>> 
>> Best regards,
>> Daniel
>> 
>> 
>> Am 16.11.2012 um 09:21 schrieb Patrick Ben Koetter <p at sys4.de>:
>> 
>>> Mr. professormobilux,
>>> 
>>> what are you trying to tell us?
>>> 
>>> * Daniel da Silva Lopes <professormobilux at web.de>:
>>>> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi,</div><div><br/></div><div>I've set up an installation of amavis-new 2.7.1 and it is working fine.</div><div><br/></div><div>The next step was to setup the quarantine to be in a mysql databse what is working also fine besides clean mail getting there as a copy too.</div><div><br/></div><div>My configuration looks like this so far:</div><div><div><br/></div><div>$final_virus_destiny      = D_DISCARD;</div><div>$final_banned_destiny     = D_DISCARD;</div><div>$final_unchecked_destiny  = D_PASS;</div><div>$final_spam_destiny       = D_DISCARD;</div><div>$final_bad_header_destiny = D_DISCARD;</div></div><div><br/></div><div><div>$virus_quarantine_to      = 'virus-quarantine';</div><div>$banned_quarantine_to     = 'banned-quarantine';</div></div><div><div>$unchecked_quarantine_to  = undef;</div><div>$spam_quarantine_to       = 'spam-quarantine';</div><div>$bad_header_quarantine_to = 'bad-header-quarantine';</div><div>$clean_quarantine_to      = undef;</div><div>$archive_quarantine_to    = undef;</div><div><br/></div><div><div>$virus_quarantine_method              = 'sql:';</div><div>$banned_files_quarantine_method       = 'sql:';</div><div>$spam_quarantine_method               = 'sql:';</div><div><div>$bad_header_quarantine_method         = 'sql:';</div><div>$unchecked_quarantine_method          = undef;</div><div>$clean_quarantine_method              = undef;<br/></div><div>$archive_quarantine_method            = undef;</div><div><br/></div><div>I would like to have only virus, banned, spam and bad header mails in the db quarantine. I thought the above configuration would accomplish that but it seems I'm missing something.</div><div><br/></div><div>Can someone point me in the right direction?</div><div><br/></div><div>Best regards,</div><div>Daniel</div></div></div></div><div><br/></div></div></body></html>
>>> 
>>> -- 
>>> [*] sys4 AG
>>> 
>>> http://sys4.de, +49 (89) 30 90 46 64
>>> Franziskanerstraße 15, 81669 München
>>> 
>>> Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
>>> Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
>>> Aufsichtsratsvorsitzender: Joerg Heidrich
>> 
> 
> -- 
> [*] sys4 AG
> 
> http://sys4.de, +49 (89) 30 90 46 64
> Franziskanerstraße 15, 81669 München
> 
> Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
> Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
> Aufsichtsratsvorsitzender: Joerg Heidrich
> 