# we check only once in a second if new processes should be created - if all # in at the same time more extra processes are created. # usually stays at login_processes_count, but when multiple users start logging # Maximum number of login processes to create. # Number of login processes to keep for listening new connections. # secure, espcially with SSL/TLS enabled. # login process be allowed to process multiple connections (no)? Yes is more # Should each login be processed in it's own process (yes), or should one # login_process_per_connection you might need to grow this. # Note that this user is NOT used to access mails. # only it has access, it's used to control access for authentication process. The user must also belong to a group where # wish to run the whole Dovecot without roots. # everything in this directory is deleted when Dovecot is started. # running as root, so you don't have to worry about permissions. # which login needs to be able to connect to. # Directory where authentication process places authentication UNIX sockets The value is in hours, 0 disables regeneration # How often to regenerate the SSL parameters file. # The CAfile should contain the CA-certificate(s) followed by the matching # File containing trusted SSL certificate authorities. # give it when starting dovecot with -p parameter. # If key file is password protected, give the password here. #ssl_key_file = /etc/ssl/private/dovecot.pem #ssl_cert_file = /etc/ssl/certs/dovecot.pem # dropping root privileges, so keep the key file unreadable by anyone but # PEM encoded X.509 SSL/TLS certificate and private key. # IP or host address where to listen in for SSL connections. # want to use "mail", you'll use local0.local7. # Syslog facility to use if you're logging to syslog. # Prefix for each line written to log file. # For informational messages, use this logfile instead of the default # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). # means that after master process has died, the client processes can't write # forcing existing client connections to close (although that could also be Setting this to "no" means that Dovecot can be upgraded without # Should all IMAP and POP3 processes be killed when Dovecot master process # connection is considered secure and plaintext authentication is allowed. you're connecting from the same computer), the # SSL/TLS is used (LOGINDISABLED capability). # Disable LOGIN command and all other plaintext authentications unless # these settings inside the protocol imap/pop3 section, so you can # If you want to specify ports for each service, you will need to configure # interfaces depending on the operating system. # "" listens in all IPv6 interfaces, but may also listen in all IPv4 # possible to specify multiple addresses. # IP or host address where to listen in for connections. # If you only want to use dovecot-auth, you can set this to "none". # Protocols we want to be serving: imap imaps pop3 pop3s # Base directory where to store runtime data. # are for configure -prefix=/usr -sysconfdir=/etc -localstatedir=/var # the real defaults being based on configure options. ![]() Exception to this are paths, they're just examples with # Default values are shown for each setting, it's not required to uncomment # value inside quotes, eg.: key = "# char and trailing whitespace " If you want to use either of these explicitly, put the # '#' character and everything after it is treated as comments. Wie das Ganze bei RPM-basierten Linuxen funktioniert, weiß ich nicht- das Prinzip wird aber ähnlich sein. Zum "Auseinandernehmen" des originalen Courier-Paketes von Plesk und dem neupacken Deines "Fake-Pakets" leistet Dir übrigens dpkg-deb gute Dienste.ĭie einfachste Idee wäre wohl, das Originalpaket auseinander zu packen, sämtliche Skripte und Binaries zu entfernen und daraus Dein "Fake-Paket" neu zu packen. Oder vielleicht kannst Du es auch selbst signieren?)ĭu müsstest Dir jetzt ein Paket basteln, dass dieselben Meta-Informationen wie das echte Courier-IMAP-Paket enthält! Die Teile a) und b) können und sollten einfach leer bzw. den Paketmanager (dpkg) "überreden" musst, Dein nicht-signiertes Paket zu installieren. (Ich habe mich länger nicht mehr damit beschäftigt, aber ich denke, Debian-Pakete sind inzwischen auch digital signiert, so dass Du evtl. Ich weiss nicht, wie das aktuell ist, aber früher(tm) waren Debians dpkg-Files einfach nur ar-Archive, dieĪ) die zu installierenden Dateien enthieltenī) vier Skripte, die zu bestimmten Zeitpunkten ausgeführt wurden: postinst (vor der Installation), preinst (nach der Installation), postrm (vor der Deinstallation) und prerm (nach der Deinstallation)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |