Hi folks, Sorry, I know this is OT, but I'm hoping someone here will be able to give me a simple 'yes' or 'no'. I now have spamassassin 3.1.0a-0volatile3 (thanks to the addition of an /etc/apt/preferences file as shown on this list) from volatile-sloppy on a sarge server, but mail is being fed to it via an older version of spamc on a different server: SpamAssassin Client version 3.0.2 compiled with SSL support (OpenSSL 0.9.6c 21 dec 2001) Previously, when the sarge server had spamassassin 3.0.3-2sarge1 installed, mails on the older server were having their headers updated to say that they'd been scanned and found clean. Since the bump up to version 3.1.0a-0volatile3 this is no longer happening. The log on the sarge server shows that scanning is happening, things are clean etc, but Does anyone know if I'm going to need to build version 3.1.0a from source on the old box that's feeding mails to the sarge server? Or did the upgrade from 3.0.3-2sarge1 to 3.1.0a-0volatile3 likely lose some config setting I made ages ago and forgot about? Thanks in advance, Andrew. -- Andrew Shugg <andrew@neep.com.au> http://www.neep.com.au/ "Just remember, Mr Fawlty, there's always someone worse off than yourself." "Is there? Well I'd like to meet him. I could do with a good laugh."
Attachment:
pgpPgCddCugVt.pgp
Description: PGP signature