spamassassin

[Tomy666]

Hello

I’m having a problem with SpamAssassin: it isn't generating a report with an attachment when delivering spam.
The option is enabled in the panel. Additionally, I set the following in `/etc/mail/spamassassin/local.cf`:

report_safe 1

I also restarted SpamAssassin and spamd .... it still isn't generating the report. Please help
Debian 12 , DA 1.7.1

 

[zEitEr]

Hello,

The option should be set on a user account or domain bases. Connect to directadmin as a user and do it in SpamAssassin setings.

 

[VPSPioneer]

To add to what zEitEr said: per-user settings live in /home/USERNAME/.spamassassin/user_prefs and that file wins over local.cf. Worth opening it for the affected user. If there's a report_safe 0 line in there, that's what is overriding your global setting.
Easiest way to test after changing it is to send that user a mail with the GTUBE string in the body:
XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X
It always scores as spam, so you'll see straight away whether the original comes through as an attachment.

 

[Tomy666]

Hello, I have 'report' enabled in my SpamAssassin settings.
The `user_prefs` file looks like this:

required_score 5.0
rewrite_header subject *****SPAM*****


report_safe     1




#SAFE AREA start


#SAFE AREA end

The message subject changes correctly, but the attachments are not delivered.
The message is correctly delivered to the SPAM folder, but without the attachment.
I recently migrated the VPS, though I installed SpamAssassin from beginning.

 

[Tomy666]

Hello
I’m still struggling with this issue of missing EML reports. I’m wondering if there might be a missing link between SpamAssassin and Exim.
mail.log

spamd: connection from localhost [127.0.0.1]:59170 to port 783, fd 5
2026-11-03T10:37:40.426610+01:00 vpstest spamd[463547]: spamd: setuid to admin succeeded
2026-11-03T10:37:40.445036+01:00 vpstest spamd[463547]: spamd: checking message <[email protected]> for admin:1000
2026-11-03T10:37:42.311532+01:00 vpstest spamd[463547]: check: dns_block_rule URIBL_BLOCKED hit, creating /root/.spamassassin/dnsblock_multi.uribl.com (This means DNSBL blocked you due to too many queries. Set all affected rules score to 0, or use "dns_query_restriction deny multi.uribl.com" to disable queries)
2026-11-03T10:37:42.312823+01:00 vpstest spamd[463547]: check: dns_block_rule RCVD_IN_DNSWL_BLOCKED hit, creating /root/.spamassassin/dnsblock_list.dnswl.org (This means DNSBL blocked you due to too many queries. Set all affected rules score to 0, or use "dns_query_restriction deny list.dnswl.org" to disable queries)
2026-11-03T10:37:42.315986+01:00 vpstest spamd[463547]: spamd: clean message (0.5/3.0) for admin:1000 in 1.9 seconds, 100742 bytes.
2026-11-03T10:37:42.316989+01:00 vpstest spamd[463547]: spamd: result: .  0 - HTML_MESSAGE,RCVD_IN_DNSWL_BLOCKED,SUBJ_ALL_CAPS,URIBL_BLOCKED scantime=1.9,size=100742,user=admin,uid=1000,required_score=3.0,rhost=localhost,raddr=127.0.0.1,rport=59170,mid=<[email protected]>,autolearn=no autolearn_force=no

 

[Richard G]

I’m wondering if there might be a missing link between SpamAssassin and Exim.

Most likely this problem is caused by both Exim and Spamassasin checking mail on those RBL lists, which should not be the case because then you get these kind of blocks.
So you have to exclude them from one of them.

Now Exim is already checking the DNSWL list so you can exclude that from spamassassin. In the spamassassin local.cf add this line:
dns_query_restriction deny list.dnswl.org
and restart spamassassin.
For the multi.uribl.com you could check this thread (click) and tips in there.
However, seems you might be better of blocking that one too and using other RBL's by Exim.