Hi Zeffie,
> While the idea of using the /etc/procmailrc file is very creative, But
> IMHO it's a bad idea. It means that every email that goes through the
> server has to use that file.
Err ... excuse me, but that's quite cute. As you know (or ought to know) the
manpages for Procmail clearly state how when and if $HOME/.procmailrc
and /etc/procmailrc come into play. See "man procmail".
You probably have spent too much time on the RaQ4's and with the broken
Procmail that Cobalt had hacked together and where several stock features had
been broken. But even there /etc/procmailrc would be used according to design
if and when it was present.
CentOS as well as CentOS + BlueQuartz have been and are using /etc/procmailrc
by design and intent to give the sysadmin the flexibility he needs to switch
mailboxes globally from MBOX format to MAILDIR format or back. That way it
also retains the ability to act as general purpose mailfilter.
> Fast solution rpm -Uvh --force http://bluequartz.org/pub/BlueQuartz/51/[...]
>
>Better Solution.. http://www.bqforge.com/
People who install your unsupported third party deamons and services (may that
be Apache or Procmail) will most likely face quite steep obstacles during the
upgrade process once BlueQuartz goes into the next phase and 5200 (Ellis) is
released. Don't forget to mention that as well.
If you intend to contribute to the BlueQuartz project you should maybe talk to
Hisao or Yasuda and contributions are certainly welcome. If you do, then you
can make sure that the ugrade goes smooth for your users/clients as well.
But If you're just here to advertise your own fork of BlueQuartz and want to
sow dissent, then this is probably the wrong list for that and you should
keep it on bqforge.com.
--
With best regards,
Michael Stauber