Zeffie,
Just to clarify a bit things for the users. www.bluequartz.org is the
official community members site. If you have your business elsewhere, we
are happy for you, but we are not your personal advertizing agent. Of
course we have others doing business with BQ, but none of them go as far
as you have stating that are "better options" as you have said.
I guess you are also criticizing Redhat as that is what CentOS is. After
redhat releases a patch CentOS will have updates 24 hours later and in
72 hours to the repositories at the most.
Therefore, your web site is misleading and incorrect.
" Currently there are no updates for the BlueQuartz with the CentOS 4.x
operating system. This means important services like Apache, Proftp and
other things can develop Security Holes that will not be closed and
could present a Security Problem!"
But, we just had a bunch of updates correct?
I understand you want more business and that is fine, but doing it at
the expense of trashing someone else's work is another story. The
concept behind BQ is different than yours perhaps, but we don't go as
far as criticizing your code or approach.
Regards,
Paul
-----Original Message-----
From: Zeffie [mailto:bluequartzlist (at mark) hotmail.com]
Sent: Monday, December 17, 2007 8:54 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:11506] What really happeded to the mail
As some of you might of noticed during the huge centos update, Mail
stopped
working... actually it was still working but just going into
/var/spool/mail
instead of the users mbox as expected. This was caused purely by the
procmail update. The version of procmail that BQ uses is patched to use
the
mbox in the users directory. This is done for several good reasons I
won't
go into here... anyway..
When the standard Redhat/centos build is installed it's not patched to
use a
mbox in the users directory... simple as that...
This is the orig BQ patch...
[root (at mark) filter redhat]# cat SOURCES/procmail-3.22-bluequartz.patch
diff -uNr procmail-3.22.orig/src/authenticate.c
procmail-3.22/src/authenticate.c
--- procmail-3.22.orig/src/authenticate.c 2001-06-29
11:20:36.000000000 +0900
+++ procmail-3.22/src/authenticate.c 2004-03-20 18:04:37.000000000
+0900
@@ -47,8 +47,8 @@
#ifndef MAILSPOOLHASH
#define MAILSPOOLHASH 0 /* 2 would deliver to
/var/spool/mail/b/a/bar
*/
#endif
-/*#define MAILSPOOLHOME "/.mail" /* watch the
leading /
*/
- /* delivers to
$HOME/.mail
*/
+#define MAILSPOOLHOME "/mbox" /* watch the leading /
*/
+ /* delivers to
$HOME/mbox
*/
#define STRLEN(x) (sizeof(x)-1)
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. I'd almost want that file to be a daemon :) but it's
not... but hec these days, procmail almost needs to become a daemon...
The
/etc/procmailrc file is not included in the procmail rpm and if it was
it
would surely be marked "config/noreplace". honestly I don't know why
you
folks have a procmailrc file anyway? I just tested it again without the
procmailrc file and it works just fine...
Now that's what broke the mail... Keep in mind though that it's
actually
only a symptom of another problem that's in the forge now.
Fast solution
rpm -Uvh --force
http://bluequartz.org/pub/BlueQuartz/5100R/CentOS4/bluequartz/i386/RPMS/
procmail-3.22-14BQ2.i386.rpm
(it wasn't a security update. it was a maximum letter size update) -
added
large file support (#228487)
Better Solution..
http://www.bqforge.com/
Because there are other things like this and several other problems with
the
current system that are fixed here!
PS. I'll have tell you about httpd another time...
--
Zeffie...
http://www.zeffie.com/
Now I build it and You surf it!
Cobalt RaQ Repairs, Development, and Maintenance.
Home of the Worlds Largest Collection of RaQ Updates!
Cobalt Spam Filter, Security, Firewall, Anti Virus Products.
Yahoo: wwwZeffie ... Aim: wwZeffie ... Msn wwZeffie (at mark) hotmail.com ...
US 734-446-0350 734-454-9117 US Toll Free 800-231-4459 UK 0208-150-6860