[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postfix-users
Subject:    Re: reject_unverified_recipient with .forward file
From:       Michael van Es <lists () mves ! nl>
Date:       2014-02-24 15:30:11
Message-ID: 20140224153011.GA7855 () storm ! mves ! nl
[Download RAW message or body]

On Mon, Feb 24, 2014 at 10:21:59AM -0500, Wietse Venema wrote:
> Wietse Venema:
> > Michael van Es:
> > > Hello,
> > > 
> > > Clients on the host can use a procmail filter, the .forward file
> > > forwards the message to procmail [which gives the mail to Cyrus]. 
> > 
> > [how can Postfix "verify" find out that the Cyrus mailbox is over-quota]
> > 
> > It can't, not even when Postfix gives the mail directly to Cyrus.
> > 
> > Instead, you need to populate an access map or transport map based
> > on a periodic scan (or real-time query) of Cyrus quota.
> > 
> > access map:
> > 
> > user@example.com        450 4.2.2 Mailbox is full
> > 
> > transport map:
> > 
> > user@example.com	error: 4.2.2 Mailbox is full
> 
> Forget about the transport map solution.  The "error" results in a
> hard reject. That should be "retry", but unfortunately the Postfix
> SMTP server doesn't know that the "retry" transport rejects mail,
> so it would accept the mail and that is not what you want.
> 
> 	Wietse

Ah, thanks. I had just begun writing a test for the transport map
solution. I will focus on the access map.

--
	Michael
[prev in list] [next in list] [prev in thread] [next in thread]