Gary W. Smith wrote:
In master.cf we have:
smtp inet n - n - - smtpd -o
content_filter=filter:
filter unix - n n - - pipe flags=Rq
user=filter argv=/etc/mail/spamassassin/filter.sh -f ${sender} --
${recipient}
filter.sh:
spamc -u filter -d 10.0.13.28,10.0.14.22,10.0.13.31 | sendmail -i "$@"
This is very similiar to what I do now, execpt you use an external
script for piping the email to spamc and then to sendamil.. So in your
configuration what occurs when spamc cannot connect to spamd? My guess
and tests show that it just gets passed to sendmail without getting
scanned. Is that what occurs for you?
> Alternatively you can defer it yourself. Nothing says you have to
re-inject it back to sendmail.
There is some pseudo code that we do in dev.
Tee -a sometmpfile | spamc -params-you-see-fix | sometmpfile.sa
Check for sa flag in sometmpfile.sa or return codes, etc
If there is,
cat sometmpfile.sa,
unlink original
Else
Move tmpfile to your queue directory
get some caffine as you will need to write a crontab retests
those queued email
if that job works, reinject into sendmail
I would really like to keep away from dealing with this type of method.
Any other thoughts?
- James
