Does spamassassin work on email forwarding?

Diemux

Verified User
Joined
Nov 16, 2011
Messages
5
Hi all,

One of my customers is only using email forwarding for their domain. On one of their emailaddresses they receive quite a lot of spam. I got spamassassin installed and I would like to know if spamassassin works on email forwarders.

Thanks!
 
I have many customers that use email forwarders, and I have not done any changes regarding this, and the email forwarders are in fact scanned by SpamAssassin. So to me it seems default is to also scan email forwarders.
 
I changed the exim.conf, the spamcheck director was commented out (#).

This is my current file:

Code:
# Spam Assassin
spamcheck_director:
  driver = accept
  condition = "${if and { \
			{!def:h_X-Spam-Flag:} \
			{!eq {$received_protocol}{spam-scanned}} \
			{!eq {$received_protocol}{local}} \
			{exists{/home/${lookup{$domain}lsearch{/etc/virtual/domainowners}{$value}}/.spamassassin/user_prefs}} \
                        {exists{/etc/virtual/${domain}/passwd}} \
                        { \
                        or \
                        { \
                                {!eq {}{${lookup{$local_part}lsearch{/etc/virtual/${domain}/passwd}}}} \
                                {!eq {}{${lookup{$local_part}lsearch{/etc/virtual/${domain}/aliases}}}} \
                                {eq {$local_part} {${lookup{$domain}lsearch{/etc/virtual/domainowners}}}}  \
                         } \
                         } \
			{<{$message_size}{200k}} \	
		} {1}{0}}"
  retry_use_local_part
  transport = spamcheck
  no_verify

I restarted exim but now when I go to spamassassin admin:

Unable to setup spamassassin

Details

Spamd is not running on your system.
Click Here to learn how to enable it

Any thoughts?
 
Where is it?

Show output of

Code:
ps aux | grep spamd

In directadmin.

When starting spamassassin:

etc/init.d/spamassassin start
Starting spamd: Nov 17 09:31:09.246 [1820] warn: server socket setup failed, ret ry 1: spamd: could not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:10.278 [1820] warn: server socket setup failed, retry 2: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:11.395 [1820] warn: server socket setup failed, retry 3: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:12.397 [1820] warn: server socket setup failed, retry 4: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:13.399 [1820] warn: server socket setup failed, retry 5: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:14.401 [1820] warn: server socket setup failed, retry 6: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:15.406 [1820] warn: server socket setup failed, retry 7: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:16.409 [1820] warn: server socket setup failed, retry 8: spamd: cou ld not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:17.411 [1820] warn: server socket setup failed, retry 9: spamd: could not create INET socket on 127.0.0.1:783: Permission denied
Nov 17 09:31:18.485 [1820] error: spamd: could not create INET socket on 127.0.0.1:783: Permission denied
spamd: could not create INET socket on 127.0.0.1:783: Permission denied
[FAILED]

Requested output:

admin 2104 0.0 0.0 4136 708 pts/0 S+ 09:34 0:00 grep spamd
 
Ah... That was stupid.

Start spamassassin with superuser and now spamd is started correctly.

Thanks!
 
You just start spamassassin with /etc/init.d/exim restart
 
Back
Top