Real names in From: line

Ben Elliston bje@air.net.au
Sun, 2 Dec 2001 08:11:32 +1100 (EST)


I am using IMP 2.2.7 and would like to know why IMP only places the
sender's mail address in the From: line, rather than something like:

	Real Name <real@domain.org>

Surely this information is available to IMP from the web server's passwd
file (or PAM, if IMP uses it?).  Is such a fix easy to make?

Cheers, Ben



>From gla@naxs.com Date:      2001-08-13 23:39:59
Return-Path: <gla@naxs.com>
Mailing-List: contact imp-help@lists.horde.org; run by ezmlm
Delivered-To: mailing list imp@lists.horde.org
Received: (qmail 60291 invoked from network); 1 Dec 2001 21:15:31 -0000
Received: from mailrtr04.ntelos.net (216.12.0.104)
  by clark.horde.org with SMTP; 1 Dec 2001 21:15:31 -0000
Received: from host187.naxs.com (pm3wythe3-218.wythe.naxs.com [216.98.71.218])
	by mailrtr04.ntelos.net (8.12.1/8.12.1) with ESMTP id fB1LEPlT023952
	for <imp@lists.horde.org>; Sat, 1 Dec 2001 16:14:26 -0500
Message-Id: <4.3.2.7.2.20011201154302.00c2a100@pop3.norton.antivirus>
X-Sender: gla/mail.naxs.com@pop3.norton.antivirus
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 01 Dec 2001 16:08:49 -0500
To: imp@lists.horde.org
From: Gary Akers <gla@naxs.com>
In-Reply-To: <Pine.LNX.4.33.0112011256480.28019-100000@kepler.acns.bethe
 l.edu>
References: <1007186473.3c087229aae87@mail.ph.utexas.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [putting the "p" *back* helped] Re: [imp] IMP 2.2.7/RH
  7.1/PostgreSQL

At 12:58 PM 12/1/01 -0600, you wrote:
>On Sat, 1 Dec 2001, Eric Jon Rostetter <eric.rostetter@physics.utexas.edu>...:
> > > > Warning: 5 is not a valid PostgreSQL link resource in
> > > > /var/www/html/horde/imp/lib/db.pgsql on line 113
> > So my point is, you might try to remove the persistent pgsql
> > connections and see if they go away.  Some old messages on the list
> > can help you do this, but basically it is removing the "p" character
> > from some calls (I think it means changing pconnect to connect, but my
> > memory may not be 100%).
>
>That's it exactly.  Check the lists; remove the "p".

After checking the pg_[p]connect lines in
/var/www/html/horde/imp/lib/db.pgsql  that came from imp-2.2.7-1rh7    and
/var/www/html/horde/imp/lib/db.pgsql  from                horde-1.2.7-1rh7
I found that they were *already* using   pg_connect.
v
Changing them back to  pg_pconnect  made the more immediate
problem go away.
v
After learning what to search for in the archives, I found
Subject:  Re:  [imp] Debian security update broke imp
Date:      2001-08-13 23:39:59
which indicates that a "bug in php" prevents pg_pconnect
from working.   I'll have to investigate further to see if the
bug which prevents postgresql connections from being
closed is still there (the bug that probably led the developers
to take the "p" out) in my combination of installed rpms
and if that is a security problem as well as a performance/stability
issue.  What do you think?  Is this apparent requirement
for persistent connections a bug or a RedHat/PHP/Apache/php-pgsql
configuration issue?
v
RedHat 7.1  fully patched
apache-1.3.19-5         **runs as user apache
freetype-2.0.1-4
(N/A) mod_php phpinfo says it's already there
php-4.0.pl1-9
php-imap-4.0.4pl1-9
postgresql-7.0.3-8      **horde database is user "hordemgr"
php-pgsql-4.0.4pl1
c-client 4.1
---end---
having started from scratch on a no-php, no-sql,
no-anything-that-would-help-make-imp-work caldera
1.3 box a while back, the rpms are easier even with
all this trouble.
--------------------------------------------------------------------------------