mirror of
https://github.com/opensolutions/ViMbAdmin.git
synced 2026-04-26 00:36:00 +03:00
Page:
Export Settings
Pages
About
Announcing ViMbAdmin v3.0.0
Archiving Mailboxes
Configuration
Contributor License Agreement
Deleting Mailboxes
Export Settings
Full setup installation (ViMbAdmin postfix dovecot)
Home
Install Database PostgreSQL
Install Database SQLite
Installation
Mail System Install on Ubuntu
Mailbox Sizes
Migrate from ViMbAdmin2
Migrate from Postfix Admin
Plugins
Plugins: Access Permissions
Quotas
SSL Support
Skinning
Third Party Applications
Updating
V2 Access Permissions
V2 Config Files for full domain aliasing
V2 Install using git
V2 Installation instructions
V2 Migrate from postfixadmin
V2 Password Schemes
V2 Release Procedure
V2 Update Instructions
V2 Postfix and MySQL Integration
Vagrant
No results
1
Export Settings
Barry O'Donovan edited this page 2014-02-14 14:39:51 +00:00
Table of Contents
For a customer install that Open Solutions was working on, we had to create the ability to export mailbox settings to Thunderbird- tying in Thunderbird's auto-configuration mechanism.
This is something we need to improve on (i.e. use access keys rather than simple and awful IP pattern matching) as well as document properly.
This feature is disabled by default.
Settings
defaults.export_settings.disabled = true
;; Export settings alowed subnets
defaults.export_settings.allowed_subnet[] = "10."
defaults.export_settings.allowed_subnet[] = "192.168."
The allowed_subnet array is used for substring pattern matching:
foreach( $this->_options['defaults']['export_settings']['allowed_subnet'] as $pattern )
{
if( substr( $_SERVER['REMOTE_ADDR'], 0, strlen( $pattern ) ) == $pattern )
// grant access
}
This is neither robust nor safe in general.
Exporting the Configuration
The hardcoded Thunderbird configuration can be pulled via:
wget http://www.example.com/vimbadmin/export-settings/thunderbird/email/user@example.com