Hello!

Currently I'm trying to integrate dovecot's deliver program into procmail. So basically I'd write a patch for procmail to deliver not directly into the mbox file but delivering with the dovecot deliver program.

Do you think this is a good concept?

For testing I use the commands discussed below. Currently I'm having a problem that deliver doesn't recognize the logging configuration from the environment (as non root user): setenv INFO_LOG_PATH $HOME/deliver.log setenv LOG_PATH $HOME/deliver.log setenv LOG_TIMESTAMP "%b %d %H:%M:%S "

cat testmail.txt | /usr/libexec/dovecot/deliver -m testbox cat testmail.txt | strace /usr/libexec/dovecot/deliver -d gerhard -m Mail/testbox cat testmail.txt | strace /usr/libexec/dovecot/deliver -m Mail/testbox

Mail is delivered correctly, but no logging at all.

Any ideas?

Config (currently not security optimized, local testing only): auth default { #Some stuff deleted socket listen { master { path = /var/run/dovecot-auth-master # WARNING: Giving untrusted users access to master socket may be a # security risk, don't give too wide permissions to it!

mode = 0600

   mode = 0660
   # Default user/group is the one who started dovecot-auth (root)
   #user =
   group = users
 }

} }

protocol lda {

Support for dynamically loadable plugins. mail_plugins is a space

separated

list of plugins to load. For example quota plugin is used to enforce

quota. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap

Address from LDA should send MDNs like out of quota

postmaster_address = postmaster@wiesinger.com

Hostname to show in mail headers. Default is the system's

real hostname.

#hostname =

Binary to use for sending mails.

#sendmail_path = /usr/lib/sendmail

If there is no user-specific Sieve-script, global Sieve script is

executed if set.

#global_script_path =

UNIX socket path to master authentication server to find users.

auth_socket_path = /var/run/dovecot-auth-master }

Thank you for your help.

Ciao, Gerhard