Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Exim4 + spamassassin. It doesn't work...

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
mike

Exim4 + spamassassin. It doesn't work...

#1 Post by mike »

Hi,

i use on my mail-server (debian sarge stable) fetchmail to get mails form different pop3-accounts. Exim4 is used as mta.
Fetchmail and exim4 are working perfect.

Now i want to check all incoming mails with spamassassin.
So i installed the sa-exim package.
I configured spamd and now it runs on startup.

But when i receive mails spamassassin/sa-exim doesn't check them...
i can't find a spamassassin tag in mail headers...

what can i do? where is the problem? some ideas?
thank you!

mike

drdebian
Posts: 80
Joined: 2004-10-09 16:17
Location: austria
Contact:

Re: Exim4 + spamassassin. It doesn't work...

#2 Post by drdebian »

mike wrote:Hi,

i use on my mail-server (debian sarge stable) fetchmail to get mails form different pop3-accounts. Exim4 is used as mta.
Fetchmail and exim4 are working perfect.

Now i want to check all incoming mails with spamassassin.
So i installed the sa-exim package.
I configured spamd and now it runs on startup.

But when i receive mails spamassassin/sa-exim doesn't check them...
i can't find a spamassassin tag in mail headers...

what can i do? where is the problem? some ideas?
thank you!

mike
Are you sure you have defined any rules in spamassassin's configuration directory?

Guest

#3 Post by Guest »

I've just installed spamassassin and configured that it will run on startup.
Special filter-rules or something else i havn't defined...

in sa-exim4.conf i edited following line:
SAEximRunCond: 1

in sa-exim4.conf the port is set to 783 (sa default port).

Guest

#4 Post by Guest »

I just checked the logfiles and found this:

Jul 18 23:20:49 localhost spamd[1175]: server killed by SIGTERM, shutting down
Jul 18 23:22:15 localhost spamd[1178]: spamd starting
Jul 18 23:22:19 localhost spamd[1180]: server started on port 783/tcp (running version 3.0.3)

Jul 18 23:22:20 localhost spamd[1180]: server successfully spawned child process, pid 1269
Jul 18 23:22:20 localhost spamd[1180]: server successfully spawned child process, pid 1272
Jul 18 23:22:20 localhost spamd[1180]: server successfully spawned child process, pid 1276
Jul 18 23:22:20 localhost spamd[1180]: server successfully spawned child process, pid 1277
Jul 18 23:22:20 localhost spamd[1180]: server successfully spawned child process, pid 1278
Jul 18 23:23:51 localhost imapd[1510]: imaps SSL service init from 192.168.0.2
Jul 19 07:20:39 localhost spamc[4815]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jul 19 07:20:40 localhost spamc[4815]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused
Jul 19 07:20:41 localhost spamc[4815]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused
Jul 19 07:20:42 localhost spamc[4815]: connection attempt to spamd aborted after 3 retries

Jul 19 07:20:43 localhost spamd[4816]: spamd starting
Jul 19 07:20:46 localhost spamd[4818]: server started on port 7830/tcp (running version 3.0.3)

Jul 19 07:20:46 localhost spamd[4820]: connection from localhost.localdomain [127.0.0.1] at port 33145
Jul 19 07:20:46 localhost spamd[4818]: server successfully spawned child process, pid 4820
Jul 19 07:20:46 localhost spamd[4818]: server successfully spawned child process, pid 4821
Jul 19 07:20:46 localhost spamd[4818]: server successfully spawned child process, pid 4822
Jul 19 07:20:46 localhost spamd[4818]: server successfully spawned child process, pid 4823
Jul 19 07:20:46 localhost spamd[4818]: server successfully spawned child process, pid 4824

I looks like spamd is running twice !?

drdebian
Posts: 80
Joined: 2004-10-09 16:17
Location: austria
Contact:

#5 Post by drdebian »

Looks more like for some reason the spamd daemon isn't accepting any connections from 127.0.0.1.

Guest

#6 Post by Guest »

But why?

Nmap:
PORT STATE SERVICE
783/tcp open hp-alarm-mgr
993/tcp open imaps
7830/tcp open unknown

Post Reply