2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Feature Request (Sour...
FromSent OnAttachments
Serge StepanovJan 19, 2004 2:09 pm 
Devin RubiaJan 20, 2004 7:51 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Feature Request (Source included): MySQL result inside of maildroprcActions...
From:Devin Rubia (dev@thezone.net)
Date:Jan 20, 2004 7:51:38 am
List:net.sourceforge.lists.courier-maildrop

On Mon, Jan 19, 2004 at 02:09:56PM -0800, Serge Stepanov wrote:

Good day fellow maildrop users!

I was coming up at the final stop on my path to a perfect installation of Postfix + Courier + SASL + MySQL + SpamAssassin w/ Maildrop and realized that the way to setup maildrop described in major HOWTOs was not the most optimal solution.

What I wanted to do is this: Retrieve homedir and maildir information from a MySQL table based on the email address and deliver to the user's mailbox (/home/vmail/domain.tld/user/Maildir/) all through one file, /etc/maildroprc. The only thing preventing me from doing this was that I had no way to (or at least wasn't aware of any way) to access the variables returned from the MySQL query in my maildroprc file. [SNIP] For those wondering, here is how it comes together in my maildroprc file:

[SNIP]

if (/^X-Spam-Flag: *YES/) { exception { to "$HOME/$MAILDIR/.Spam/" } }

[SNIP]

I'm not really seeing the benefit here. You always seem to be using "$HOME/$MAILDIR". Why couldn't you just use "$DEFAULT" instead?