On Fri, May 17, 2013 at 2:42 AM, Fritz Borgstedt <f...@iworld.de> wrote:
> If 'download only' is selected and a new assp version is available, > this new version will be downloaded to the directory > /Applications/assp/download (assp.pl) and the syntax will be checked. > But what about the currently installed version? If the downloaded one replaces the current one, will it make sure that the current one gets backed up if it's not in the download folder yet? Imagine me installing a custom version, or turning on the auto update for the first time, and then that first auto update breaks my installation. Where's my original version gone then? Do I need to keep my own copies for that? I'd find it more failsafe if the update script would take care of that. Also, when I had a look at a changelog yesterday, it did not seem to be up-to-date with the latest changes, i.e. it did not mention all the recent build numbers along with what they changed. Or did I look at the wrong changelog, are there more than one? I looked at one that was in the downloaded zip file from the website, it starts like this: > ASSP changelog assp.pl 1.99 > -The pair of 250 responses in STARTTLS is now fixed > -There is no developer version 1.98 any longer. Kind of hard to read out of that one what changed. Also, I wonder about the version numbering lately. Before 1.98, it was separate numbers for "major.middle.minor.bugfix". By common standards, this would have allowed 1.10.x.x to be followed by 1.9.x.x. But the new numbering has turned this into a decimal number, and there's no way to do that now. So we'll be stuck with 1.99 and have to regard the build number as the new significant version number. Nothing serious but it looks to me that someone hasn't understood how multi-period version numbering systems work. They're NOT decimal numbers. Well, too late to fix that now. Overall, though, I appreciate your efforts to keep ASSP up-to-date. I just wish it would be better documented. There have been too many additions made in recent years that I do not understand any more. And with every update I have the fear that it changes something that makes my filters not work correctly any more, thereby rejecting or discarding valid emails as spam. It happened to me a few times in the past, e.g. when some blacklists went rogue (which isn't ASSP's fault, though). It's hard to stay on top of all the changes when using ASSP only for a personal email server. -- Thomas Tempelmann, http://www.tempel.org/ Follow me on Twitter: http://twitter.com/#!/tempelorg ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user