[Amavisd-new-debian-devel] 2.5.2-1 packages

[Henrique de Moraes Holschuh]

On Wed, 19 Sep 2007, Alexander Wirt wrote:
>   * Instead of interrupting the upgrade process if starting/stopping
>     amavisd-new just warn (Closes: #430028)

That is a bad, bad idea *IF* you actually start amavisd-new with an invalid
configuration (sorry, I don't have time to look the package to check exactly
what you did).  Letting the upgrade complete *with amavisd-new stopped* is
not a problem, as long as you do this by ignoring the status of the
initscript in the maintainer scripts and not by breaking the initscript to
not return failure...

>   * Add suggestion to dspam (Closes: #423737)

I'd ask upstream how well amavisd-new works alongside dspam, and whether
he'd recommend this setup, first.  If Mark says it is fine, it is fine :-)
But if it will cause amavisd-new to be an evern worse memory hog, well...

Alternatively, if dspam is not always a great idea, you could also add the
suggests, but setup amavisd-new to ignore dspam by default and have the user
explicitly enable dspam support in the config file.

> - integration of p0f-analyzer.pl (initscript? daemonmode? any ideas? see: #364328 or #388207) 

I'd say you'd need to make it a proper daemon.  amavisd-new is critical
infrastructure, so please add proper pidfile, setsid(), close all open fds
before forking, and all the rest of the usual crap one needs to do before
daemon() :-)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh