On 24.11.19 12:33, Linkcheck wrote:
As I understand it, altering those values in default/spamass-milter
should be sufficient? Those have been changed for several days now.
the SOCKET value in default/spamass-milter MUST agree with value in
smtpd_milters in main.cf relative to the chroot value.
default value of SOCKET in default/spamass-milter differs on different
systems, as does chroot setting.
You use a clone of Ubundy, which is clone of Debian - I don't know if your
system uses debian defaults.
Following a lead from elsewhere I have altered the owner to
spamass-milter:postfix and the socket permissions follow it in the
file manager. However, the PID file is being created with
spamass-milter:nogroup and I cannot find where to change it - and does
it matter in this case?
no. However you should not change permission of a file.
Instead, you can set values of SOCKETOWNER and SOCKETMODE in
default/spamass-milter.
In System Monitor (task manager) I'm seeing (currently) 2 spamd
processes, 2 spamd-child and a spamass-milter. Is that reasonable?
unrelated.
I'm also seeing the following in the log for each email email...
spamd: connection from ::1 [::1]:55492 to port 783, fd 5
spamd: handle_user (getpwnam) unable to find user: 'admin'
spamd: still running as root: user not specified with -u, not found,
or set to root, falling back to nobody
spamd: processing message <message-id> for admin:65534
... where admin changes according to the target email address (eg
james, ebay etc) - I do not understand why line 2 is seeking user:
admin.
precisely because of that. spamass-milter found out the message is sent to
admin, so it wants to process mail with settings of admin user.
line 3 running as root - according to default/spamassassin it seems -u
is optional for spamd.pid and I'm not even sure that's what it is
referring to.
communicates with spamd by localhost:783
How do I force that?
don't.
What I keep looking for (and fail to find) is a list of all actions I
need in order to set up spamass-milter - permissions, options, where
and what etc for ubuntu. Which is why I began this thread in the first
place.
don't change too many things, especially not once.
And why do all the other milters I'm using not have this difficulty. :(
exactly the line above shows that spamass-milter is working. It clearly did
pass mail and the username (admin) to spamd.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The early bird may get the worm, but the second mouse gets the cheese.
