Wiki en »
Restricting access of user groups by means of subnetwork pools¶
Choose a language: RU | EN | ZH
Table of contentsTable of contents
- Quick Start
- Thoughtful reading
- When there was no Internet, there was email
- TEGU server concept
- Server licensing
- How to get TEGU
- TEGU Compatibility
- Preparing for installation
- DNS zone configuration
- Universal acceptance of internationalized domain names
- Server installation
- Starting, Stopping, Logging the Server
- Initial server configuration
- Server Administration
- User Settings
- Configuring BlackList, WhiteList, GreyList, DKIM, SPF, DMARC, server auto-locking
- Restricting access of user groups by means of subnetwork pools
- Local user base and integration with directory servers
- Mailbox management
- Integration with anti-virus and anti-spam systems
- Master User
- Mail migration
- Configuring various server roles
- Server verification by external utilities
- Mailing lists
- IMAP public folders
- Delegation of mail accounts (resource boxes)
- Processing mail messages on the server side
- Restoring deleted messages
- Exporting a mailbox
- Configuring the address books service
- Customizing the calendars service
- Managing private and shared calendars
- Customizing mail clients
- Using MS Outlook mail client
- Algorithm of mail sessions processing
- Using the TEGU server with the RoundeCube interface
- Using the TEGU server with NextCloud interface
- Using the TEGU server with the Р7-Офис interface
- Updating TEGU
- Backup TEGU
- Building a fault-tolerant TEGU cluster
- Building a fault-tolerant Postgres DBMS cluster
- TEGU Test Program and Methodology
- Alphabetical Index
- Technical Forum