Alex Pita wrote:

You can specify static u/gid on postfix - main.cf, so you dont overload your tables making unnecessary lookups.

virtual_uid_maps=static:1234 virtual_gid_maps=static:1234

With static on main.cf you still have to have the correct (same) values on your tables, since courier-imap or maildrop still need them.

Dont know much yet about master.cf, why those flags Rhu?

That's why I use this patch:

http://www.commedia.it/ccontavalli/#courier

with this script:

#!/bin/sh # # Script for use with Carlo Contavalli's courier patch # for automgic maildir creation uppon pop/imap login # http://www.commedia.it/ccontavalli/#courier # # This script assumes a static uid:gid mapping for virtual mail users. # and can be run by hand on command prompt passing a maildir as # argument. # # Script grown by Marcio Merlone (mm...@surf.com.br) based on suggested # script on Carlo's online docs.

# Customize these lines for your needs! staticuid="mail" staticgid="mail" LOGGER=/usr/bin/logger MDIRMAKE=/usr/lib/courier-imap/bin/maildirmake

# Hopefully you don't need to customize any further.

maildir=$1

# Check for arguments. [ -z "$1" ] && printf "Use: `basename $0` <dir>\n" && exit 0

child=`basename $1` parent=`echo $1|sed 's/'${child}'//g'`

# Check for parent dirs (useful for setups for virtual # mailboxes with domain as # /virtual/domain/id/Maildir or something like this... if [ ! -d "$1" ]; then echo "Directory "$parent" does not exists, creating..." mkdir -p $parent $LOGGER -p auth.notice -t courier "Directory "$parent" automagic created." fi

echo $parent" "$child

# Finally creates the maildir. $MDIRMAKE $maildir && $LOGGER -p auth.notice -t courier "Maildir "$parent"/"$child" for uid "$UID" aka "$AUTHADDR" automagiclly created." chown -R $staticuid:$staticgid $maildir chmod -R g+rx $maildir

I was thinking about writing a simple and small script that runs twice (?) a day from cron that reads maildirsize and drops a new file (not using mail delivery agents, but using cat > $FILE << EOF) formatted as a real messages (so it becomes one) with the warn according to some parameters (quota x maildirsize). Done! And regardless quota he _will_ be warned. If user is overquota, even the deliverquota warning message is not delivered. Yes, it does have some implications on quota calculation, but I belive that it is not fair to stat this warning on user quota.

Did not notice that, will take a look.

Hey, calm down. Realize that none on mail list has obligation to answer. If you find that few answer there, become one to answer. Learn about the software and go there help others! And you cannot say "this software is not for production!" based on its mailling list, you have to analyze the software per se, see others experience with, if it meets your requests or not. It does mine, so I use it (in fact the server I am setting up is not yet in production). But even if the software has some improvements to be done, it is stable to use on production envs if you can deal with the features (for me is just the quaota wan, that I can circunvent...).

Just fine, but I will use extended features of maildrop to have mail filtering on server, and give this for my customers so they can block they own spam ;).