Hi,

It seems that various packagers get into traps when trying to build
maildrop without courier support.

- a long time ago, I submitted a bug for NetBSD pkgsrc. the package diff
patched the configure script in a way that enabled the HAVE_COURIER
variable. This broke the setup when maildrop was used from postfix
(well, not always, but it was the case in my setup, which uses mysql as
a backend). The package maintainer fixed the problem very quickly, and I
thank him.

- Now, I see that the debian package has a diff that causes maildrop to
return 75 in the case of over quota.

While these are packagers issues, wouldn't it be better if maildrop
allowed for run-time configuration, instead of compile-time? the
HAVE_COURIER config could be defined in a config file, or passed (when
necessary) as a command line argument (or as an environment variable).

Is this feasible/reasonable, or should I check what I smoked today?





-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Reply via email to