quota rules for mail users

Dear All, Is it possible to make quota rules under $HOME/Maildir/* mailboxes with a specific command such as 'edquota' when the first email arrives at the $HOME/Maildir/{new,cur,tmp} of a user. In the below example, the is the one who gets an email for the first time. edquota -p

Upgrade to 2.2.9 breaks sasl auth

Hi This is my 1st time here so please be gentle. I have encountered one problem since upgrading from 2.0.19 to 2.2.9 which has me beat. The system provides sasl auth services via inet to a postfix 2.11 system. Since the upgrade postfix complains of no sasl methods available. The same dovecot

Mail dates

Where exactly does dovecot get the date that it reports via IMAP? I have a lot of messages that were restored from an archive and so all have the same date, despite being over the span over several years. I tried setting the timestamps of the files to the date in the Received header, but that

Re: shutdown_clients has no effect on doveadm stop

On Tue, 14 Jun 2016, aki.tu...@dovecot.fi wrote: > Are you using systemd by chance? I did some more testing, stopped dovecot via systemd, started it manually via /opt/dovecot/sbin/dovecot, stopped it via "doveadm stop" and this time the IMAP connection stayed active. So it seems to be systemd,

Alternate Storage and quota limits

Hi all, is there any way of exclude messages storaged in alternate storage (*dbox mailbox format) from being included in the quota usage? I think this is not possible but let me ask.

Re: shutdown_clients has no effect on doveadm stop

Hi Aki! On Tue, 14 Jun 2016, aki.tu...@dovecot.fi wrote: > Are you using systemd by chance? Yes, with the default dovecot.service file provided with 2.2.24: $ systemctl cat dovecot # /lib/systemd/system/dovecot.service # This file is part of Dovecot # # If you want to pass additionally command

Re: Double variable expansion / multiple password mechanisms

On 14/06/16 23:15, Karsten Heiken wrote: Hi Leon, You should be able to add multiple userPassword attributes to your directory: userPassword: {CRAM-MD5}xxx userPassword: {DIGEST-MD5} userPassword: {SCRAM-SHA-1} userPassword: {NTLM} Did try this, didn't end end well. Jun 14

Re: Double variable expansion / multiple password mechanisms

Hi Leon, >> You should be able to add multiple userPassword attributes to your directory: >> >> userPassword: {CRAM-MD5}xxx >> userPassword: {DIGEST-MD5} >> userPassword: {SCRAM-SHA-1} >> userPassword: {NTLM} > > Did try this, didn't end end well. > > Jun 14 12:59:43 auth: Error: >

Re: shutdown_clients has no effect on doveadm stop

> On June 14, 2016 at 6:02 PM Roland Rosenfeld wrote: > > > I try to restart dovecot 2.2.24 (for changing limits) without killing > all IMAP and POP3 sessions. > > dovecot(1) tells me: >When shutdown_clients is set to no, existing sessions will continue to >

Re: Double variable expansion / multiple password mechanisms

Hi Karsten, You should be able to add multiple userPassword attributes to your directory: userPassword: {CRAM-MD5}xxx userPassword: {DIGEST-MD5} userPassword: {SCRAM-SHA-1} userPassword: {NTLM} Karsten Did try this, didn't end end well. Jun 14 12:59:43 auth: Error:

shutdown_clients has no effect on doveadm stop

I try to restart dovecot 2.2.24 (for changing limits) without killing all IMAP and POP3 sessions. dovecot(1) tells me: When shutdown_clients is set to no, existing sessions will continue to use the old settings, after a dovecot reload. Also all sessions will keep alive

Re: Double variable expansion / multiple password mechanisms

Hi Leon, > I had the crazy thought I could do something like the following: > > For each user Store supported password schemes as LDAP attributes: > userPasswordCRAM-MD5: {CRAM-MD5}xxx > userPasswordDIGEST-MD5: {DIGEST-MD5} > userPasswordSCRAM: {SCRAM-SHA-1} > userPasswordNTLM:

Double variable expansion / multiple password mechanisms

Hi, Trying to solve the problem of supporting multiple auth mechanisms + proxy and really don't want to store user passwords in plain test and fine to do master user to backend. I had the crazy thought I could do something like the following: For each user Store supported password schemes

Alternate Storage and quota limits

Hi all, is there any way of exclude messages storaged in alternate storage (*dbox mailbox format) from being included in the quota usage? I think this is not possible but let me ask.