I'm not asking for an LDA to deploy. Are you suggesting that I review Dovecot's LDA as an example of how to use a pipe transport? I'm writing a LDA which will be DB native and want some experience based input on which method of delivery is best for my situation. In this case can I implement something that isn't exit code oriented? Mostly I'm concerned about the DSN for when quotas are exceeded or when a mailbox has been temporarily suspended.
GlenB > -----Original Message----- > From: owner-postfix-us...@postfix.org > [mailto:owner-postfix-us...@postfix.org]on Behalf Of Sahil Tandon > Sent: Friday, February 06, 2009 10:34 PM > To: postfix-users@postfix.org > Subject: Re: mailbox integration questions > > > On Fri, 06 Feb 2009, Glen B wrote: > > > I'm working on a DB environment integration with Postfix and > have gotten > > TCP dict lookups to function. Now, I'm working on mail delivery and am > > trying to determine which method of mailbox delivery to take. I > have a few > > limitations in my application, but for the most part I'm open to all > > methods. I want to be able to handle quotas inside my > application and pass > > back information to allow temporary or permanent delivery error > codes and > > messages for Postfix DSN. The biggest limitation I have is that > I can not > > assign exit status codes directly from the application. I would > have to wrap > > it in a scripting language and decipher an interim status code > to a shell > > exit code. What are some recommendations to openly handle external mail > > delivery? I've considered LMTP and mailbox_command but I'm not sure if a > > pipe service would be more viable. Ideas/suggestions? > > The dovecot LDA provides quota functionality and integrates into > Postfix via > the pipe(8) transport. > > -- > Sahil Tandon <sa...@tandon.net>
