search for: userdb_pass

...; Dovecots %w variable is only available within dovecot-auth, is there any >>>> way to access the password for a mail-filter? >>> >>> Something like this should work in recent versions: >>> >>> passdb { >>> .. >>> override_fields = userdb_pass=%w >>> } >>> >>> plugin { >>> mail_filter = mail-filter %{userdb:pass} >>> } >>> >> >> Thanks for that idea, unfortunately %{ seems to be misinterpreted and >> the mail-filter script recieves the rest of the string "userd...

...users password within a mail-filter script. >> Dovecots %w variable is only available within dovecot-auth, is there any >> way to access the password for a mail-filter? > > Something like this should work in recent versions: > > passdb { > .. > override_fields = userdb_pass=%w > } > > plugin { > mail_filter = mail-filter %{userdb:pass} > } > Thanks for that idea, unfortunately %{ seems to be misinterpreted and the mail-filter script recieves the rest of the string "userdb:pass}" as a parameter, instead of the password. So, do I get th...

Hello, I would like to use the users password within a mail-filter script. Dovecots %w variable is only available within dovecot-auth, is there any way to access the password for a mail-filter? Thanks, Thomas

I just committed a very early initial implementation of "imapc" storage backend to v2.1 hg: http://hg.dovecot.org/dovecot-2.1 You can't really do anything except open INBOX and read mails from it, so it's currently only intended for initial testing. It sucks in many ways right now, but I'll be improving it. The idea is that you could set for example: mail_location =