Index: [Article Count Order] [Thread]

Date:  Mon, 17 Dec 2007 23:04:44 -0500
From:  "Darrell D. Mobley" <dmobley (at mark) uhostme.com>
Subject:  [coba-e:11511] Re: What really happeded to the mail
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <000f01c8412b$1f7b90d0$6400a8c0@HPPAVILION>
In-Reply-To:  <BAY129-DAV6C17D6FA3B74C19C34D6ACA630 (at mark) phx.gbl>
References:  <BAY129-DAV6C17D6FA3B74C19C34D6ACA630 (at mark) phx.gbl>
X-Mail-Count: 11511

How did I escape this?  My BQ server had the /etc/procmailrc already on it
and my mail wasn't disturbed at all.  How did I not get hit with this?

> -----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/pr
> ocmail-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