>> On Apr 30, 2015, at 1:29 PM, Kevin A. McGrail wrote:
>>
>> On 4/30/2015 1:15 PM, Kevin A. McGrail wrote:
>> Can you add this block of code above line 1386 in the current TxRep.pm?
>> Then we'll try and figure out how to enable the TxRep debug channel from MD
>> so you can log the info and
On behalf of the project, I am pleased to announce the release of Apache
SpamAssassin v3.4.1.
Downloads are available at http://spamassassin.apache.org/downloads.cgi
regards,
KAM
Release Notes -- Apache SpamAssassin -- Version 3.4.1
Introduction
Apache SpamAssassin 3.4.1 repre
On 4/30/2015 1:15 PM, Kevin A. McGrail wrote:
Can you add this block of code above line 1386 in the current
TxRep.pm? Then we'll try and figure out how to enable the TxRep debug
channel from MD so you can log the info and relay it. It also should
hide the informat
Can you try this in your mil
On 4/30/2015 11:44 AM, J.J. Day wrote:
FWIW, I switched to TxRep several months ago. Every message generates
both error lines. I have added a test to initialize $msgscore to avoid
filling my log files. Spam messages seem to all generate a negative
offset of ~1/3 the total. I copied a sample to
FWIW, I switched to TxRep several months ago. Every message generates both
error lines. I have added a test to initialize $msgscore to avoid filling my
log files. Spam messages seem to all generate a negative offset of ~1/3 the
total. I copied a sample to the end.
My setup is:
FreeBSD 10.0
Send
Am 30.04.2015 um 17:06 schrieb Benny Pedersen:
Matus UHLAR - fantomas skrev den 2015-04-30 12:55:
no, it's the "dig" command that does the trace, not the nameserver.
This says nothing about your nameserver configuration, and it can't since
nameserver does not provide that info.
dig respects
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 user, in amavis I have special
policy bank f
Matus UHLAR - fantomas skrev den 2015-04-30 12:55:
no, it's the "dig" command that does the trace, not the nameserver.
This says nothing about your nameserver configuration, and it can't
since
nameserver does not provide that info.
dig respects resolv.conf with nameserver 127.0.0.1
try it :
Tom Robinson skrev den 2015-04-30 04:35:
Finally that makes sense. I will add the forwarding in as per the
documentation.
remove forwarding is safe, only use forward dns on zones you self build
or have rsync access to
Tom Robinson skrev den 2015-04-30 04:14:
Actually, looking for this config I can't seem to find it. My
spamassassin is linked in with qmail
using qmail-scanner-queue.pl. That script looks in
/home/qscand/.spamassassin/user_prefs but I also
have configs in /etc/mail/spamassassin. What am I lookin
On 4/30/15, 5:55 AM, "Matus UHLAR - fantomas" wrote:
>no, it's the "dig" command that does the trace, not the nameserver.
>This says nothing about your nameserver configuration, and it can't since
>nameserver does not provide that info.
I stand corrected-- I had tested on another machine that us
On 30/04/2015 16:35, Joe Quinn wrote:
On 4/30/2015 9:22 AM, Joe Quinn wrote:
On 4/30/2015 9:10 AM, Birta Levente wrote:
On 30/04/2015 15:55, Joe Quinn wrote:
On 4/30/2015 7:09 AM, Birta Levente wrote:
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in
On 4/30/2015 9:22 AM, Joe Quinn wrote:
On 4/30/2015 9:10 AM, Birta Levente wrote:
On 30/04/2015 15:55, Joe Quinn wrote:
On 4/30/2015 7:09 AM, Birta Levente wrote:
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vend
On 4/30/2015 9:10 AM, Birta Levente wrote:
On 30/04/2015 15:55, Joe Quinn wrote:
On 4/30/2015 7:09 AM, Birta Levente wrote:
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.p
On 30/04/2015 15:55, Joe Quinn wrote:
On 4/30/2015 7:09 AM, Birta Levente wrote:
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line
1415.
_WARN: Use of uninitialized v
On 4/30/2015 7:09 AM, Birta Levente wrote:
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
_WARN: Use of uninitialized value $msgscore in subtraction (-)
I ju
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
_WARN: Use of uninitialized value $msgscore in subtraction (-)
I just wonder if there is any workaroung for tha
On 30/04/15 09:56, Marieke Janssen wrote:
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more informa
Am 30.04.2015 um 12:55 schrieb Matus UHLAR - fantomas:
On 4/30/15, 12:16 AM, "Tom Robinson" wrote:
BTW, where can I see the results of my configuration changes? It
would be
nice to confirm that my
changes have rectified the situation.
On 30.04.15 01:38, Dave Pooser wrote:
On the server (via
>On the server (via SSH or console) use the +trace argument to dig, and
>then look for lines starting with ';;':
>postmstr@smtp:~$ dig +trace example.com.multi.uribl.com | grep ';;'
>;; global options: +cmd
>;; Received 913 bytes from 127.0.0.1#53(127.0.0.1) in 8 ms
>;; Received 760 bytes from 199
On 4/30/15, 12:16 AM, "Tom Robinson" wrote:
BTW, where can I see the results of my configuration changes? It would be
nice to confirm that my
changes have rectified the situation.
On 30.04.15 01:38, Dave Pooser wrote:
On the server (via SSH or console) use the +trace argument to dig, and
then
21 matches
Mail list logo
