Is there a way to make custom Dovecot settings persist through ISPConfig's dovecot.conf rewrites?

Discussion in 'Installation/Configuration' started by Etcetera, Jul 1, 2018.

  1. Etcetera

    Etcetera New Member HowtoForge Supporter

    Like, for example, 'plugin' settings.

    Why I ask: Some of my sieve rules require the editheader plugin, which has to be activated and configured in either /etc/dovecot.conf or /etc/dovecot/conf.d/*.conf, for example 90-plugins.conf. (This is a Ubuntu 16.04 LTS & Apache based 'Perfect Server' setup.)

    As far as I can see, dovecot.conf can and will be overwritten by ISPConfig at times (the one time it did so lately was the ISPConfig update to 3.1.12).

    Any /etc/dovecot/conf.d/*.conf entry for the 'plugin' section, on the other hand, will be ignored, as there's already a 'plugin' section in dovecot.conf – which seems to have precedence over anything I try to configure in /etc/dovecot/conf.d/*.conf.

    Is there some way out of this catch-22 which I failed to see?

    Cheers,
    Etc

    P.S.: Sorry, I wanted to post this in ISPConfig - Installation/Configuration, not Linux - Installation/Configuration. Perhaps someone, if they, too, feel that's where it belongs, can move the posting?
     
  2. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    Ispconfig uses /etc/dovecot.conf and not /etc/dovecot/conf.d/*
    You can copy install/tpl/debian6_dovecot2.conf.master from the archive to to /usr/local/ispconfig/server/conf-custom/install/debian_dovecot2.conf.master and customize this file.
     
  3. Etcetera

    Etcetera New Member HowtoForge Supporter

    Excellent, thank you!

    Is there, perhaps, a document somewhere that states which 'real' files those templates are related to? I guess amavisd_user_config.master is what becomes /etc/amavis/conf.d/50-user?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    No, it's just in the code of the installer.
     
  5. Etcetera

    Etcetera New Member HowtoForge Supporter

    Is that correct in that the target file starts with debian_, not debian6_? I just noticed I had named it debian6_*, after I had found myself without some of my Sieve rules again after upgrading ISPConfig to 3.1.13...

    Cheers,
    Etc
     

Share This Page