[Dovecot] dict quota not being updated for all users when receiving a multi-recipient message
I've set up a mysql quota dictionary using the proxy setup as described in the wiki (using Dovecot lda). When I send a single message to multiple users, only the first recipient is getting their usage updated. This behavior occurs if I manually send to more than one user via the To: line, or via aliases set up in postfix. I do have dovecot_destination_recipient_limit set to 1.
I don't even have a guess as to what might be going on here, since each instance of the lda is a separate process. But, let me know if anybody has any ideas or requests for more info.
On Thu, 2007-01-25 at 13:43 -0500, Justin McAleer wrote:
I've set up a mysql quota dictionary using the proxy setup as described in the wiki (using Dovecot lda). When I send a single message to multiple users, only the first recipient is getting their usage updated. This behavior occurs if I manually send to more than one user via the To: line, or via aliases set up in postfix. I do have dovecot_destination_recipient_limit set to 1.
I don't even have a guess as to what might be going on here, since each instance of the lda is a separate process. But, let me know if anybody has any ideas or requests for more info.
Does the dict quota otherwise work for the users? The only thing I can think of is that your primary key isn't both the path and the username, but that would make the whole quota tracking broken.
Timo Sirainen wrote:
On Thu, 2007-01-25 at 13:43 -0500, Justin McAleer wrote:
I've set up a mysql quota dictionary using the proxy setup as described in the wiki (using Dovecot lda). When I send a single message to multiple users, only the first recipient is getting their usage updated. This behavior occurs if I manually send to more than one user via the To: line, or via aliases set up in postfix. I do have dovecot_destination_recipient_limit set to 1.
I don't even have a guess as to what might be going on here, since each instance of the lda is a separate process. But, let me know if anybody has any ideas or requests for more info.
Does the dict quota otherwise work for the users? The only thing I can think of is that your primary key isn't both the path and the username, but that would make the whole quota tracking broken.
Thanks for the reply Timo. I haven't had a chance to debug this any further, and my priorities are on other projects right now... but I'll send more details as soon as i have a chance to work on it some more.
participants (2)
-
Justin McAleer
-
Timo Sirainen