I just got through updating a mailserver that had been running 4.0 to 4.2 using a new HDD, fresh install of OS and required packages. All old scripts settings etc preserved on original HDD now sitting in an accessible older box so I can grab anything forgotten.
The one thing that hit me was the output of spamdb. Back on 4.0 all the entries came out (sort of) sorted. All the SPAMTRAP entries last but sorted on the trap address field. All the GREY, WHITE or TRAPPED entries first sorted on the IP field (but sorted "alphabetically" i.e. 101.x.y.z precedes 99.x.y.z) All that was fine because I could easily see if there were two entries for the one IP which happened when a script that runs every few minutes evaluates a GREY entry and enters it as TRAPPED. It seems that the migrated database works but new entries go on the end - no SORT of order, and SPAMTRAP entries (that I entered using a script) ended up showing in two bunches in the midst of other unordered entries. My question is: Is this normal with spamd a la 4.2 or is it because I migrated a database? I can always use: spamdb |sort -n -t "|" -k 2 |less to get a fully sorted list if I have to, but curiosity makes me ask about expected behaviour. Of course (to cut off pedants) I could have used: spamdb |sort -t "|" -k 2 -n|less to get the output looking like that from 4.0. Thanx, Rod/ /earth: write failed, file system is full cp: /earth/creatures: No space left on device
