On Fri, Feb 14, 2025 at 10:47:43AM +0100, natan wrote:
> 1)Spamassassin3.x:
> spamassassin -D -t w6.elm
>
> -- ---
> 1.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
> blocked. See
Hi
I use only local pdns recursor and this same I set in SA
1)Spamassassin3.x:
spamassassin -D -t w6.elm
-- ---
1.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
blocked. See
http
On Thu, Feb 13, 2025 at 05:13:43PM +0100, natan wrote:
> IP ban may make sense - but there was a similar problem with another machine
> also with spamassin4.x - after returning to 3x there was no problem
Are you SURE there was NO problem? Or is it possible that the problem
*just isn't reported* in
Benny Pedersen skrev den 2025-02-14 00:05:
Bill Cole skrev den 2025-02-13 21:29:
On 2025-02-13 at 11:13:43 UTC-0500 (Thu, 13 Feb 2025 17:13:43 +0100)
natan
Feb 13 17:02:06 amavis5 amavis[9316]: (09316-01) _WARN: check:
dns_block_rule RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating
/var/amavis/v
Bill Cole skrev den 2025-02-13 21:29:
On 2025-02-13 at 11:13:43 UTC-0500 (Thu, 13 Feb 2025 17:13:43 +0100)
natan
is rumored to have said:
Hi
Sorry but University debate
The machines were 1:1 clones
For testing, I also updated debian11 -> debian12 to rule out other
issues and the effect wa
On 2025-02-13 at 11:13:43 UTC-0500 (Thu, 13 Feb 2025 17:13:43 +0100)
natan
is rumored to have said:
Hi
Sorry but University debate
The machines were 1:1 clones
For testing, I also updated debian11 -> debian12 to rule out other
issues and the effect was the same
One machne who
cat /etc/
Hi
Example full log:
https://paste.debian.net/1349829/
/etc/nsswitch.conf
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
W dniu 13.02.2025 o 16:52, Matija Nalis pisze:
On
Hi
Sorry but University debate
The machines were 1:1 clones
For testing, I also updated debian11 -> debian12 to rule out other
issues and the effect was the same
One machne who
cat /etc/resolv.conf
nameserver 127.0.0.1
IP ban may make sense - but there was a similar problem with another
On Thu, Feb 13, 2025 at 04:11:52PM +0100, natan wrote:
> I have a couple of servers on all of them with spamassassin3x and I have no
> problem
> and on one where there is spamassassin4 I have problems as above
>
> To put it even simpler 90% of traffic is handled by servers with
> spamassassin3x
@Benny
Okay what don't you understand in this thread?
I have a couple of servers on all of them with spamassassin3x and I have
no problem
and on one where there is spamassassin4 I have problems as above
To put it even simpler 90% of traffic is handled by servers with
spamassassin3x where I hav
natan skrev den 2025-02-13 15:01:
Hi
Thenx for help but this url is not very clear
I have own resolver
ii pdns-recursor 4.1.11-1+deb10u2 amd64 PowerDNS Recursor
ii rbldnsd 1.0~20210120-2 amd64 small nameserver daemon
designed for DNSBLs
dig test.uribl.com.multi.uribl.
natan skrev den 2025-02-13 12:03:
Spamasaasin4.x gets less traffic than others.
and now please show the real problem, not workarounds
Hi
Thenx for help but this url is not very clear
I have own resolver
ii pdns-recursor 4.1.11-1+deb10u2 amd64 PowerDNS Recursor
ii rbldnsd 1.0~20210120-2 amd64 small nameserver daemon
designed for DNSBLs
dig test.uribl.com.multi.uribl.com txt +short @127.0.0.1
"permanen
natan writes:
> Feb 13 11:48:14 amavis5 amavis[934307]: (934307-01) SA info: async:
> aborting after 4.815 s, deadline shrunk: URIBL,
> A/kra20at.cc.multi.surbl.org, rules: URIBL_ABUSE_SURBL,
> URIBL_CR_SURBL, URIBL_MW_SURBL, URIBL_DM_SURBL, URIBL_PH_SURBL,
> SURBL_BLOCKED, URIBL_CT_SURBL
This c
Hi
Another Problem wher I found when I migrate to Spamassasin-4.x
spamassassin -V
SpamAssassin version 4.0.0
running on Perl version 5.36.0
many times in log I get:
Feb 13 11:48:14 amavis5 amavis[934307]: (934307-01) SA info: async:
aborting after 4.815 s, deadline shrunk: URIBL,
A/kra20at.
Do you have any unmaintained or self-maintained SA Plugins (eg CRM114)?
pat...@patpro.net skrev den 2023-06-21 13:33:
June 21, 2023 12:59 PM, "Matija Nalis"
wrote:
Another way to prove that the problem is exclusively in spamassassin
is to reproduce the problem ONLY with spamassassin (i.e. without
dovecot, amavisd, etc. being involved at all) - e.g. by manually
ru
June 21, 2023 12:59 PM, "Matija Nalis" wrote:
> Another way to prove that the problem is exclusively in spamassassin
> is to reproduce the problem ONLY with spamassassin (i.e. without
> dovecot, amavisd, etc. being involved at all) - e.g. by manually
> running "spamassassin -t /tmp/blah.mbox" and
On Wed, Jun 21, 2023 at 12:00:41PM +0200, natan wrote:
> I tested via configurations
>
> 1)dovecot10 + spamassasin-3.x - problem not exists
> 2)dovecot11 + spamassasin-3.x - problem not exists
> 3)dovecot10 + spamassasin-4.x - problem exists
> 4)dovecot11 + spamassasin-4.x - problem exists
>
> al
check tmp path in all software used, this includes how perl versions
handle tmp dirs and files, in your case its amavisd that create dirs,
and its amavisd that tells spamassassin in with dir to scan email with
embed spamassassin engine in amavisd, check if other spamscanners
works in amavisd
eg change from spamassassin to spamdclient, and then start spamd
does this leave temp files still ?
Note: Look in /tmp then, not in /var/lib/amavis/tmp
natan skrev den 2023-06-21 10:05:
Hi
Files such as .spamassassin are deleted but not all.
Files that are not deleted do not appear to be invalid
I build spamassassin-4.x from cpan - not from repo
Workaound solutions is not good but works
find /var/lib/amavis/tmp/.spam* -mmin +200 -delete;
I'd
Hi
Files such as .spamassassin are deleted but not all.
Files that are not deleted do not appear to be invalid
I build spamassassin-4.x from cpan - not from repo
Workaound solutions is not good but works
find /var/lib/amavis/tmp/.spam* -mmin +200 -delete;
I'd rather not use it though
I thinki
Bill Cole wrote:
On 2023-06-20 at 12:33:05 UTC-0400 (Tue, 20 Jun 2023 18:33:05 +0200)
Patrick Proniewski
is rumored to have said:
On 20 Jun 2023, at 17:49, Bill Cole
wrote:
On 2023-06-20 at 09:39:04 UTC-0400 (Tue, 20 Jun 2023 15:39:04 +0200)
Patrick Proniewski
is rumored to have said:
He
On 2023-06-20 at 12:33:05 UTC-0400 (Tue, 20 Jun 2023 18:33:05 +0200)
Patrick Proniewski
is rumored to have said:
On 20 Jun 2023, at 17:49, Bill Cole
wrote:
On 2023-06-20 at 09:39:04 UTC-0400 (Tue, 20 Jun 2023 15:39:04 +0200)
Patrick Proniewski
is rumored to have said:
Hello,
I'm running
i don't belive debian is more helpfull
reinstall gives same problem as you have now
FWIW, I cannot reproduce the issue either on (Debian bookworm with
standard packages) or (Debian bullseye with SA4 from CPAN), so it is not
categorically broken.
/var/lib/amavis/tmp/ CREATE .spamassassin17
Patrick Proniewski skrev den 2023-06-20 18:33:
I did not upgrade. I did not reconfigure either.
Do you suggest I should deinstall / reinstall Amavisd-new?
if i just did install amavisd-new in gentoo nothing will work unmodified
in amavisd.conf
i don't belive debian is more helpfull
reinsta
On 20 Jun 2023, at 17:49, Bill Cole
wrote:
>
> On 2023-06-20 at 09:39:04 UTC-0400 (Tue, 20 Jun 2023 15:39:04 +0200)
> Patrick Proniewski
> is rumored to have said:
>
>> Hello,
>>
>> I'm running amavisd-new (milter) with spamassassin 4.x on FreeBSD, both from
>> pkg, and I see the same proble
In debian11 with spamasassin-4.x
root@amavis-4:~# su - amavis
$ perl -Mv5.14 -MFile::Spec -e 'say File::Spec->tmpdir'
/tmp
In debian11 with spamassassin-3.4.x
root@amavis5:~# su amavis
$ perl -Mv5.14 -MFile::Spec -e 'say File::Spec->tmpdir'
/tmp
Nevermind, Debian's amavis actually defines TMP
On 2023-06-20 at 09:39:04 UTC-0400 (Tue, 20 Jun 2023 15:39:04 +0200)
Patrick Proniewski
is rumored to have said:
Hello,
I'm running amavisd-new (milter) with spamassassin 4.x on FreeBSD,
both from pkg, and I see the same problem. It appears that my
/var/amavis/tmp holds every single sspamass
W dniu 20.06.2023 o 16:50, Damian pisze:
For test I downgrade one spamassassin from 4.x to 3.4.6 and problem
not exists
Hm, I don't see any significant code-difference regarding tempfiles.
any idea ?
root@a48c6a1d5fb0:~# sudo -u amavis perl -Mv5.14 -MFile::Spec -e 'say
File::Spec->tmpdir'
/tm
For test I downgrade one spamassassin from 4.x to 3.4.6 and problem
not exists
Hm, I don't see any significant code-difference regarding tempfiles.
any idea ?
root@a48c6a1d5fb0:~# sudo -u amavis perl -Mv5.14 -MFile::Spec -e 'say
File::Spec->tmpdir'
/tmp
What output do you get?
Hello,
I'm running amavisd-new (milter) with spamassassin 4.x on FreeBSD, both from
pkg, and I see the same problem. It appears that my /var/amavis/tmp holds every
single sspamassassin tmp file from the day I've upgraded to 4.x.
cheers.
> On 20 Jun 2023, at 15:07, natan wrote:
>
> Hi
> I hav
Hi
I have extrenal serwers with amavis+spamassassin (via cpan)
4 of them debian10 and spamassin-3.4.4
2 of them debian11 and spamassassin-4.x
I have a problem (only debianb10 and spamassassin-4.x) with many many
files like ".spamassassin99712ZzMoDatmp" in /var/lib/amavis/tmp/
example:
debian10
34 matches
Mail list logo
