This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 6 and 7
Revision 6 as of 2007-07-30 19:52:51
Size: 3345
Comment: Adding example for IP and USER variables
Revision 7 as of 2009-01-08 20:40:40
Size: 3354
Editor: TimoSirainen
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
exec /usr/local/libexec/dovecot/imap exec /usr/local/libexec/dovecot/imap $*
Line 31: Line 31:
exec /usr/local/libexec/dovecot/imap exec /usr/local/libexec/dovecot/imap $*
Line 45: Line 45:
exec /usr/local/libexec/dovecot/imap exec /usr/local/libexec/dovecot/imap $*

Post-login scripting

If you want to do something special after authentication, but before beginning the IMAP or POP3 session, you can do this by changing the mail_executable setting to run a script. Below are some examples for what this can be used for.

WARNING: The process still runs as root at this point! The privileges are dropped only after the imap process starts. You can change this by setting mail_drop_priv_before_exec=yes.

Running environment

Standard input and output file descriptors are redirected to the client's network socket, so you can send data to client by simply writing to stdout. Standard error fd is redirected to Dovecot's error log, you can write errors there as well.

All of Dovecot's settings are passed via environment variables from master process to mail processes. Usually the settings have same names as in dovecot.conf, except uppercased. So for example mmap_disable setting shows up in MMAP_DISABLE environment variable. You can override any settings you want by modifying the environment before executing the imap/pop3 binary.

Note that boolean settings are enabled simply by having the environment variable exist. So MMAP_DISABLE=1 and MMAP_DISABLE=0 (and =anything) means the same as mmap_disable=yes.

The only list for mapping settings to environment variables exists in the source code (src/master/mail-process.c. Another somewhat easy way would be for you to get a list of all environment variables and find the settings you want to override from it:

set > /tmp/dovecot-environment
exec /usr/local/libexec/dovecot/imap $*

Last-login tracking

If you want to know when the user last logged in, you can do it like this:

# a) Filesystem based timestamp in user's home directory
touch ~/.last_login
# b) SQL based tracking. Beware of potential SQL injection holes if you allow
# users to have ' characters in usernames.
#echo "update last_login = now WHERE user = '$USER'" | mysql mails
# Finally execute the imap/pop3 binary. If you use both, you'll need two scripts.
exec /usr/local/libexec/dovecot/imap $*

Custom mailbox location autodetection

See MailLocation for an example.


If you want to give the user's client some warning notification, you can do it just by writing it to stdout. Although note that not all clients show the alerts, even though IMAP RFC requires it.

if [ -f ~/.out-of-office ]; then
  echo "* OK [ALERT] You're still marked as being out of office."
# Finally execute the imap/pop3 binary. If you use both, you'll need two scripts.
exec /usr/local/libexec/dovecot/imap $*

Denying connection from some IP/User

You can use the IP and USER shell variables that are setup by dovecot in a bash script in order to deny connection (after a successfull login), like this:

if [ "$USER" = "myuser" ] ; then
  echo "* OK [ALERT] The user '$USER' can not login"
  echo "* NO"
  exit 1

if [ ! "$IP" = "" ] ; then
  echo "* OK [ALERT] Access not allowed from the Internet"
  echo "* NO"
  exit 1

Or use the Connect ACL Script for limiting some user from connecting from the Internet. More info here:

None: PostLoginScripting (last edited 2022-02-04 22:55:54 by TimoSirainen)