Software: Apache. PHP/8.1.30 

uname -a: Linux server1.tuhinhossain.com 5.15.0-151-generic #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC
2025 x86_64 

uid=1002(picotech) gid=1003(picotech) groups=1003(picotech),0(root)  

Safe-mode: OFF (not secure)

/usr/share/doc/dovecot-core/wiki/   drwxr-xr-x
Free 26.2 GB of 117.98 GB (22.21%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Self remove    Logout    

Viewing file:     Dict.txt (1.6 KB)      -rw-r--r--

Dict Proxy Process
==================

Dict server is used for providing <dictionary> [Dictionary.txt] access via
server processes instead of doing it directly from whichever process wants to
access the dictionary. This is useful for some backends with relatively high
connection cost (e.g. SQL), but not necessarily for others (e.g. Redis).

When a mail process uses the dict proxy, it needs to have access the dict UNIX
socket. By default only the "dovecot" user has access to the dict socket, which
doesn't typically work in any installation. However, giving too wide
permissions by default might allow untrusted users to access the dict and cause
problems.

If all users share a single UNIX UID (e.g. "vmail"), you could make the dict
socket accessible only to it:

---%<-------------------------------------------------------------------------
service dict {
  unix_listener dict {
    mode = 0600
    user = vmail
  }
}
---%<-------------------------------------------------------------------------

If you use multiple UNIX UIDs, you can add an extra group for all Dovecot mail
processes. This works even if you have untrusted system users who have shell
access to the server:

---%<-------------------------------------------------------------------------
mail_access_groups = dovecot

service dict {
  unix_listener dict {
    mode = 0660
    group = dovecot
  }
}
---%<-------------------------------------------------------------------------

However, it works with <LDA.txt> only if it's started as root. If this isn't
possible, look into using <LMTP.txt> instead.

(This file was created from the wiki on 2019-06-19 12:42)