Unable to start clamsmtpd

2009-06-14 Thread Carmel
I just installed clamsmtpd on a fresh FreeBSD-7.2 installation. When I
attempt to start the program via the start up script supplied by the
port maintainer, I receive this error message:

Clamsmtpd: invalid Outaddress socket name or ip: start

I receive the exact same message when I terminate the program, except
start is replaced by stop.

In the config file, this is listed:

OutAddress: 10026

That is the default setting. I made sure that clamav was running.

I cannot figure out what the problem is. Anyone have any suggestions?

-- 
Carmel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Unable to start clamsmtpd

2009-06-14 Thread Ott Köstner
On Sunday 14 June 2009 9:28:31 pm Carmel wrote:
 I just installed clamsmtpd on a fresh FreeBSD-7.2 installation. When I
 attempt to start the program via the start up script supplied by the
 port maintainer, I receive this error message:
 
 Clamsmtpd: invalid Outaddress socket name or ip: start

I have clamsmtp running fine on my mail server. Hope I can help You.

First, please check that the directory, where clamsmtpd creates socket, is 
writable by clamsmtpd user.
For example, I have yhe following lines in my config file:

[...]
# The address clamd is listening on
ClamAddress: /var/run/clamav/clamd.sock
[...]
# User to switch to
User: clamav

...and...

# ls -ld /var/run/clamav/
drwxr-xr-x  2 clamav  clamav  512 Nov 27  2008 /var/run/clamav/

# ls -l /var/run/clamav/clamd.sock
srwxrwxrwx  1 clamav  clamav  0 Nov 27  2008 /var/run/clamav/clamd.sock



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Unable to start clamsmtpd

2009-06-14 Thread Jerry
On Sun, 14 Jun 2009 22:28:17 +0300
Ott Köstner o...@zzz.ee wrote:

On Sunday 14 June 2009 9:28:31 pm Carmel wrote:
 I just installed clamsmtpd on a fresh FreeBSD-7.2 installation. When
 I attempt to start the program via the start up script supplied by
 the port maintainer, I receive this error message:
 
 Clamsmtpd: invalid Outaddress socket name or ip: start

I have clamsmtp running fine on my mail server. Hope I can help You.

First, please check that the directory, where clamsmtpd creates
socket, is writable by clamsmtpd user. For example, I have yhe
following lines in my config file:

[...]
# The address clamd is listening on
ClamAddress: /var/run/clamav/clamd.sock
[...]
# User to switch to
User: clamav

...and...

# ls -ld /var/run/clamav/
drwxr-xr-x  2 clamav  clamav  512 Nov 27  2008 /var/run/clamav/

# ls -l /var/run/clamav/clamd.sock
srwxrwxrwx  1 clamav  clamav  0 Nov 27  2008 /var/run/clamav/clamd.sock

I had:

ClamAddress: /var/run/clamav/clamd

in my config file. I changed the clamd to clamd.sock but it did not
make a difference.

The clamd.pin, clamd.sock= and freshclam.pid files are in
the /var/run/clamav directory.

This is becoming really annoying. Aparently, clamdsmtp will not create
its own clamsmtpd.pid file.

-- 
Jerry
ges...@yahoo.com

We are not loved by our friends for what we are;
rather, we are loved in spite of what we are.
-- Victor Hugo


signature.asc
Description: PGP signature


Re: Unable to start clamsmtpd

2009-06-14 Thread Ott Köstner
On Sunday 14 June 2009 10:46:01 pm Jerry wrote:

 I had:
 
 ClamAddress: /var/run/clamav/clamd
 
 in my config file. I changed the clamd to clamd.sock but it did not
 make a difference.
 
 The clamd.pin, clamd.sock= and freshclam.pid files are in
 the /var/run/clamav directory.
 
 This is becoming really annoying. Aparently, clamdsmtp will not create
 its own clamsmtpd.pid file.

Name does not matter, but '/var/run/clamav/' should be owned by 'clamsmtp' 
owner. Also 'clamd.conf' should be edited. The socket must be the same in both 
configuration files.

# Path to a local socket file the daemon will listen on.
# Default: disabled (must be specified by a user)
LocalSocket /var/run/clamav/clamd.sock

All 3 programs should run under the same username:

  PID USERNAME   THR PRI NICE   SIZERES STATE  C   TIME   WCPU COMMAND
56863 clamav   3  450   236M 28292K ucond  0   0:03  0.98% clamd
21484 clamav   1   40 15704K   984K accept 1   1:44  0.00% clamsmtpd
56894 clamav   1  200 19188K   636K pause  1   0:39  0.00% freshclam

Works fine. I can send all my conf files, if needed. Probably not a very good 
idea to copy/paste these into this list. My clamd works fine for some time 
already. This very e-mail goes through my clamd...

greetings,
Ott


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Unable to start clamsmtpd

2009-06-14 Thread Jerry
On Sun, 14 Jun 2009 22:55:03 +0300
Ott Köstner o...@zzz.ee wrote:

On Sunday 14 June 2009 10:46:01 pm Jerry wrote:

 I had:
 
 ClamAddress: /var/run/clamav/clamd
 
 in my config file. I changed the clamd to clamd.sock but it did not
 make a difference.
 
 The clamd.pin, clamd.sock= and freshclam.pid files are in
 the /var/run/clamav directory.
 
 This is becoming really annoying. Aparently, clamdsmtp will not
 create its own clamsmtpd.pid file.

Name does not matter, but '/var/run/clamav/' should be owned by
'clamsmtp' owner. Also 'clamd.conf' should be edited. The socket must
be the same in both configuration files.

# Path to a local socket file the daemon will listen on.
# Default: disabled (must be specified by a user)
LocalSocket /var/run/clamav/clamd.sock

All 3 programs should run under the same username:

  PID USERNAME   THR PRI NICE   SIZERES STATE  C   TIME   WCPU
 COMMAND
56863 clamav   3  450   236M 28292K ucond  0   0:03  0.98%
clamd 21484 clamav   1   40 15704K   984K accept 1   1:44
0.00% clamsmtpd 56894 clamav   1  200 19188K   636K pause  1
0:39  0.00% freshclam

Works fine. I can send all my conf files, if needed. Probably not a
very good idea to copy/paste these into this list. My clamd works fine
for some time already. This very e-mail goes through my clamd...


OK, when I reboot, clamsmtpd will install it's 'PID' file in
the /var/run/clamav directory. There are no errors shown. Postfix then
immediately starts.

Now, when I receive a message, the maillog has an error message:

clamsmtpd: 17: CLAMAV: couldn't connect to : /var/run/clamav/clamd:
No such file or directory.

Now, the file and directory do exist. If I stop or restart clamsmtpd,
that error message about clamsmtpd: invalid OutAddress socket or ip:
reappears.

-- 
Jerry
ges...@yahoo.com

How come only your friends step on your new white sneakers?


signature.asc
Description: PGP signature