Upgrading should work just as well as a first-time installation. The
failure of the ASSP script to properly initialize new variables and rewrite
the config file after an upgrade/restart is a significant problem. At the
very least, the web interface should have displayed the uriblTestMode
variable accurately after the restart created it. If it had, it would have
shown a checkmark.
Dave
Charles Marcus wrote:
> Moore, Chris ( BIUK ) wrote:
>> Absolutely, I upgraded to 1.3.0 (from 1.2.6) on 7th March
>
> That's most likely how this happened then... - oh well, at least you
> got it fixed... :)
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Charles
>> Marcus
>> Sent: 14 March 2007 15:06
>> To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
>> Subject: Re: [Assp-user] Spam Delivery
>>
>> Moore, Chris ( BIUK ) wrote:
>>> Ah yes, but.
>>>
>>> There was no next one - those were all the testmodes that existed in
>>> my .cfg at that time.
>>
>> Is it possible this was an upgrade from an older version - ie, you
>> already had a config file that may have predated the uribl
>> functionality? Uribl is a relatively new feature...
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
