-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am using the exim + exiscan patch to call spamd, this had been working
fine for a long time now without any problems. However after a cron job
(to update the chicken pox / blackhair etc rule sets) restarted
spamassassin my setup is no longer working. Just to be sure, I removed
all the extra rule sets and the problem still occurs. Nothing else
changed on the system (that I know of anyway :)
Every mail that I scan now fails because of the following error in my
maillog:
spamd[8129]: bad protocol: header error: (closed before headers)
Any one got any idea?
Vince.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
iD8DBQFAJjmnPx/nyuA99rgRAr2mAJ9xepOh08+HXGlEJcYSBpgBMkkhyQCeKUoe
OT0tg1D1VfXa9kviUkIf6zU=
=uyWu
-----END PGP SIGNATURE-----
Hash: SHA1
I am using the exim + exiscan patch to call spamd, this had been working
fine for a long time now without any problems. However after a cron job
(to update the chicken pox / blackhair etc rule sets) restarted
spamassassin my setup is no longer working. Just to be sure, I removed
all the extra rule sets and the problem still occurs. Nothing else
changed on the system (that I know of anyway :)
Every mail that I scan now fails because of the following error in my
maillog:
spamd[8129]: bad protocol: header error: (closed before headers)
Any one got any idea?
Vince.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
iD8DBQFAJjmnPx/nyuA99rgRAr2mAJ9xepOh08+HXGlEJcYSBpgBMkkhyQCeKUoe
OT0tg1D1VfXa9kviUkIf6zU=
=uyWu
-----END PGP SIGNATURE-----