On 30/04/2015 18:08, Kevin A. McGrail wrote:
On 4/30/2015 9:56 AM, Birta Levente wrote:
Spamassassin called through amavisd as a content filter in postfix.
I just see, if I send an emtpy mail (just the subject is test)
through my server, fire the warning.
The mail is sent as an authenticated
On 5/3/2015 2:40 AM, Robert Schetterer wrote:
Hi , i try to understand
this
http://search.cpan.org/dist/Mail-SpamAssassin/lib/Mail/SpamAssassin.pm
need_tags
...
Currently the only tag that needs to be explicitly requested is 'TIMING'
...
the goal would be to have time stats of every rule
On 5/4/2015 9:03 AM, Birta Levente wrote:
On 30/04/2015 18:08, Kevin A. McGrail wrote:
On 4/30/2015 9:56 AM, Birta Levente wrote:
Spamassassin called through amavisd as a content filter in postfix.
I just see, if I send an emtpy mail (just the subject is test)
through my server, fire the
On 04/05/2015 16:51, Kevin A. McGrail wrote:
On 5/4/2015 9:03 AM, Birta Levente wrote:
On 30/04/2015 18:08, Kevin A. McGrail wrote:
On 4/30/2015 9:56 AM, Birta Levente wrote:
Spamassassin called through amavisd as a content filter in postfix.
I just see, if I send an emtpy mail (just the
On 5/4/2015 10:12 AM, Birta Levente wrote:
I see messages in the log by the added code in TxRep.pm with:
amavisd.conf:
$sa_debug = 1;
Is there a way to tighten that to just show TxRep debug messages?
Regards,
KAM
From more discussins, there are two ways with MD to activate the TxRep
debug channel if you using spam_assassin_init in your filter.
Choice A) modify mimedefang.pl directly, i.e. spam_assassin_init to add
the debug channel:
my $sa_args = {
local_tests_only =
On 5/4/2015 7:42 PM, Mark Martinec wrote:
The requirement for timing can be requested by a application using
the SpamAssassin library. Currently amavisd does turn it on and
the SpamAssassin timing report is included in the amavisd log,
but the spamd does not include the timing report in its log.
The infra team will need to update the SpamAssassin Bugzilla instance in
order to replace the SpamAssassin Logo.
The update will take place at 20:00 UTC on Thursday May 7, 2015.
After this, SpamAssassin will be able to update the logo whenever needed by
updating the file at
On 5/3/2015 2:40 AM, Robert Schetterer wrote:
Hi , i try to understand
this
http://search.cpan.org/dist/Mail-SpamAssassin/lib/Mail/SpamAssassin.pm
need_tags
...
Currently the only tag that needs to be explicitly requested is 'TIMING'
...
the goal would be to have time stats of every rule
The requirement for timing can be requested by a application using
the SpamAssassin library. Currently amavisd does turn it on and
the SpamAssassin timing report is included in the amavisd log,
but the spamd does not include the timing report in its log.
On 2015-05-05 1:20, Kevin A. McGrail
On 5/4/2015 7:14 PM, Mark Martinec wrote:
On 2015-05-04 15:42, Kevin A. McGrail wrote:
I believe this setting is solely for profiling of spamassassin. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5356 but I doubt it's
of much use to the general public.
The requirement for timing
my $sa_args = {
local_tests_only = $SALocalTestsOnly,
dont_copy_prefs= 1,
userprefs_filename = $config,
user_dir = $Features{'Path:QUARANTINEDIR'},
debug = 'TxRep'
};
Kevin A. McGrail skrev den 2015-05-02 05:10:
Test of the list.
spf helo test
13 matches
Mail list logo
