t.
Obviously, since the whole reason for two sites and servers is
redundancy, the syncronization mechanism should not make one of the
two a point of failure. Adding a third system that the two share adds
new failure modes, but might, overall, be acceptable.
Anyone doing this? Anyone have suggestions?
to (a) work at all and (b) filter recipients the way I wanted
to. During my testing, however, I found out that contrary to the
documentation the Net::SMTP::Server module is not actually a
standards compliant server. That kind of kills off that as a
possibility.
Thanks
for
> /var/log/syslog :
>
>postrotate
> /etc/init.d/syslog-ng reload >/dev/null
> /etc/init.d/spamassassin restart >/dev/null
It sounds like you have spamd writing _directly_ to the log file
rather than actually using the
he debug
output), but the children it spawned would all hang _forever_ in the
Razor check rather than timeout. That makes me suspicios that
something was not being reinitialized in the timeout check or some
other issue due to spamd being a bit of a kludge in the first place.
--
D be marked for deletion, but MUST
NOT be destroyed by the mark-up removal process.
The script around 'spamassassin -d' being specified as the $editor,
fulfills this, but like I said, I don't like clobbering the $editor
function for it.
Thanks for any help.
--
Crist J. Clark
