Am 09.03.2016 um 20:27 schrieb Tom Johnson: > I'm sorry if I wasn't clear - adding to trusted_networks is not an > option. Different users have different needs. One person might want > x.x.x.x whitelisted, but another may not.
perhaps you like http://wiki.policyd.org/policies http://wiki.policyd.org/amavis > > I'm currently using the sa_userconf feature in amavisd to do this, but > it really hurts performance. From the amavisd-new release notes: > >> Each time that currently loaded configuration needs to be replaced by >> another or restored to a systemwide default, an initial SpamAssassin >> configuration is restored through SpamAssassin's copy_config() method. >> Note that saving an original SpamAssassin configuration, loading a >> user configuration, and restoring to the original configuration does >> not come cheap: it can take 200 ms for a load and restore, and 370 ms >> for the initial saving of the configuration (saving is only done once >> per child process, and only if needed). Saved configuration can occupy >> additional 2 MB of virtual memory, so use the feature sparingly. No >> penalty occurs until a child process does its first loading of a user >> configuration, so rarely activated or inactive policy banks or >> per-recipient setting using this feature do not cause any additional >> processing or occupy additional memory. > > I'm trying to avoid this performance hit. > > Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
