Todd Lyons writes:
On Tue, Oct 10, 2006 at 06:39:35PM -0400, Sam Varshavchik wrote:
Put "| echo $MAILDIRQUOTA >/tmp/quota.trace" in the .courier file,
temporarily, and see what's in the environment variable.
I put it in $HOME/.courier and $HOME/Maildir/.courier. It didn't use
that file at all. Maybe because I have a global
/etc/courier/maildroprc?
No. Look, you have to know what's going on your box, because nobody else
does.
Furthermore, you _should_ read Courier's documentation, so you'd know where
the .courier file belongs.
If you are not running maildrop from a .courier file, you must be running it
via DEFAULTDELIVERY.
If it's the same, I added in a log statement at the end of the
maildroprc to log the $MAILDIRQUOTA to the logfile:
log "Quota: $MAILDIRQUOTA"
and it showed this:
Normal mail delivery for swca...@receiver.com:
Quota:
Obviously the quota does not get set, after you invoke maildrop in whatever
way you're actually invoking maildrop.
Sam, I have an strace that I can provide to you if you would like. I
will put it up for download or email it directly to you if you would
like.
In the strace I see that it's calling the 'id' and 'sh' commands and
passing the env variable "MAILDIRQUOTA=", just like that, no value. So
something about my system is causing maildrop not to see my quota
settings from authlib.
Stop. strace is of no use, because it's quite clear that maildrop is not
getting invoked properly.
Furthermore, maildrop does not invoke "id" and "sh" on its own, so that
throws a red flag to me.
Again, explain how you've configured Courier to use maildrop for local mail
delivery.
8 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Quota from LDAP not t...
