Teergrube and postfix?
Rusty Carruth
rustyc@descomp.com
Tue, 7 Nov 2000 10:12:01 -0700 (MST)
Well, so close and yet so far.
I've got about 90% of the way to having teergrube run in front
of postfix. I set up postfix, got it working, then changed
master.cf to say 'fakesmtp' as the port (and added a new
port to /etc/services called fakesmtp) and reloaded postfix.
Then I started './antispam ./teergrube.config', and looked
with netstat to see that all the ports were listening that I
expected to be listening.
They were, and everything seemed to work, until I tried to
send mail out from behind the firewall (including from on
the firewall machine itself - the one running postfix,
antispam, etc).
What I got then was:
Nov 7 09:44:14 fw postfix/qmgr[17695]: warning: connect to transport smtp: Connection refused
Nov 7 09:44:41 fw teergrube[17884]: mclib: Got signal 15. Closing connections and exit.
Antispam says:
Nov 7 09:38:10 fw teergrube[17884]: [6] from 210.154.8.242:12317, 10 sec delay (match default), relaying denied (match (null)).
Nov 7 09:38:13 fw teergrube[17884]: [6] coprocess 17920 started. Bind descriptors 8->6->13 10->syslog
Nov 7 09:38:13 fw teergrube[17884]: [10] remote close. pid 17920
earlier on in the logs.
Has anyone tried this? (teergrube and postfix)
Am I crazy (don't answer that!) for trying it this way?
Should I punt back to normal sendmail?
Anybody?
thanks!
rusty