Bug #313103: Amavisd-new is not Volatile.d.o material
Amavisd-new is basically glue that holds the MTA, AV and content-filter
together. As such, it can still do its job just fine if just the AV and
content-filter (spamassassin) gets updated, as long as their APIs don't
change.
If it ever happens that clamav's clamd or spamassassin (should it ship from
volatile.d.n) break their API, then yes, an amavisd-new update would be
required to keep systems up-to-date and working.
We will deal with that bridge if we ever come upon said river. For now,
amavisd-new has no reason to be part of volatile.d.n. Regular backports
are, AFAIK, good enough for those who need the enhanced capabilities of an
up-to-date amavisd-new at the moment.
I am closing bug #313103, which requested that amavisd-new be added to
volatile.d.n.
--
"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
Reply to: