http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
So you can use this with Postfix:
virtual_mailbox_maps = tcp:127.0.0.1:1234
With Dovecot you can enable it with:
service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } }
Anyone have ideas if this could be improved, or used for some other purposes?
On 1/9/2012 8:43 AM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
So you can use this with Postfix:
virtual_mailbox_maps = tcp:127.0.0.1:1234
With Dovecot you can enable it with:
service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } }
Anyone have ideas if this could be improved, or used for some other purposes?
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)?
-- Noel Jones
Am 09.01.2012 16:32, schrieb Noel:
On 1/9/2012 8:43 AM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
So you can use this with Postfix:
virtual_mailbox_maps = tcp:127.0.0.1:1234
With Dovecot you can enable it with:
service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } }
Anyone have ideas if this could be improved, or used for some other purposes?
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)?
if you use dove lmtp with postfix it allready works "like that way" for over quota
-- Noel Jones
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On 1/9/2012 9:37 AM, Robert Schetterer wrote:
Am 09.01.2012 16:32, schrieb Noel:
On 1/9/2012 8:43 AM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
So you can use this with Postfix:
virtual_mailbox_maps = tcp:127.0.0.1:1234
With Dovecot you can enable it with:
service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } }
Anyone have ideas if this could be improved, or used for some other purposes?
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)? if you use dove lmtp with postfix it allready works "like that way" for over quota
That can reject over-quota users during the postfix SMTP conversation?
-- Noel Jones
Am 09.01.2012 16:46, schrieb Noel:
On 1/9/2012 9:37 AM, Robert Schetterer wrote:
Am 09.01.2012 16:32, schrieb Noel:
On 1/9/2012 8:43 AM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
So you can use this with Postfix:
virtual_mailbox_maps = tcp:127.0.0.1:1234
With Dovecot you can enable it with:
service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } }
Anyone have ideas if this could be improved, or used for some other purposes?
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)? if you use dove lmtp with postfix it allready works "like that way" for over quota
That can reject over-quota users during the postfix SMTP conversation?
jep ,it does, i was glad having/testing this feature in dove 2 release, avoiding overquota backscatter etc
-- Noel Jones
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Am 09.01.2012 16:50, schrieb Robert Schetterer:
Am 09.01.2012 16:46, schrieb Noel:
On 1/9/2012 9:37 AM, Robert Schetterer wrote:
Am 09.01.2012 16:32, schrieb Noel:
On 1/9/2012 8:43 AM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
So you can use this with Postfix:
virtual_mailbox_maps = tcp:127.0.0.1:1234
With Dovecot you can enable it with:
service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } }
Anyone have ideas if this could be improved, or used for some other purposes?
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)? if you use dove lmtp with postfix it allready works "like that way" for over quota
That can reject over-quota users during the postfix SMTP conversation?
jep ,it does, i was glad having/testing this feature in dove 2 release, avoiding overquota backscatter etc
i am afraid i wasnt total corect here in fact i havent seen backscatter overquota on my servers since using dove lmtp with postfix
but i guess there may cases left in which it could happen you should ask Timo for exact tec answer
the postfix answer ever was write some policy daemon for it ( which i found extremly complicated at my try, and stopped it )
but i guess its always a problem comparing the size of a mail with space left in mailstore i.e with many reciepts of one mail etc, whatever tec solution is used
so i should have said dove lmtp is the best/easy solution for overquota i know at present and my problems with it are solved for now
-- Noel Jones
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On 9.1.2012, at 18.19, Robert Schetterer wrote:
i am afraid i wasnt total corect here in fact i havent seen backscatter overquota on my servers since using dove lmtp with postfix
LMTP shouldn't matter here. In most configs mails are put to queue first, and only from there they are sent to LMTP, and if LMTP rejects a mail then backscatter is sent. Maybe the difference you're seeing is that it's now Postfix sending the bounce (or perhaps skipping it?) instead of dovecot-lda (unless you gave -e parameter).
Am 09.01.2012 19:12, schrieb Timo Sirainen:
On 9.1.2012, at 18.19, Robert Schetterer wrote:
i am afraid i wasnt total corect here in fact i havent seen backscatter overquota on my servers since using dove lmtp with postfix
LMTP shouldn't matter here. In most configs mails are put to queue first, and only from there they are sent to LMTP, and if LMTP rejects a mail then backscatter is sent. Maybe the difference you're seeing is that it's now Postfix sending the bounce (or perhaps skipping it?) instead of dovecot-lda (unless you gave -e parameter).
Hi Timo, thx for clearing anyway backscatter with overquota was rare ever so no big problem
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On 9.1.2012, at 17.32, Noel wrote:
On 1/9/2012 8:43 AM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask:
get user@domain
and Dovecot answers one of:
- 200 1
- 500 User not found
- 400 Internal failure
Anyone have ideas if this could be improved, or used for some other purposes?
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)?
Hmm. That looked potentially useful, but Postfix doesn't seem to support it at least that way, since the message to SMTP client is the same regardless of what I add after 500 reply. Also that would have required me to move the code somewhere else from auth process, since auth doesn't know the quota usage. And internally Dovecot would still have had to do auth lookup separately, so there's really no benefit in doing this vs. having Postfix do two lookups.
On 1/9/2012 12:09 PM, Timo Sirainen wrote:
On 9.1.2012, at 17.32, Noel wrote:
Cool. Does this just check for valid user existence, or can it also check for over-quota (and respond 500 overquota I suppose)? Hmm. That looked potentially useful, but Postfix doesn't seem to support it at least that way, since the message to SMTP client is the same regardless of what I add after 500 reply. Also that would have required me to move the code somewhere else from auth process, since auth doesn't know the quota usage. And internally Dovecot would still have had to do auth lookup separately, so there's really no benefit in doing this vs. having Postfix do two lookups.
How about a separate TCP lookup for quota status? This would be really useful for sites that don't have that information in a shared sql table (or no SQL in postfix), and get rid of kludgy policy services used to check quota status.
This would be used with a check_recipient_access table, response would be something like: 200 DUNNO quota OK 200 REJECT user over quota 500 user not found
-- Noel Jones
participants (3)
-
Noel
-
Robert Schetterer
-
Timo Sirainen