Bug 217252

Summary: Emacs incorrectly compiled with fakemail setting
Product: [Fedora] Fedora Reporter: Eli Barzilay <eli>
Component: emacsAssignee: Chip Coldwell <coldwell>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-11-29 15:38:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eli Barzilay 2006-11-25 23:47:07 UTC
Description of problem:

  The pre-packaged emacs that comes with FC6 (emacs-21.4-17) is incorrectly
  compiled to use the inexistent "fakemail".

Version-Release number of selected component (if applicable):

  emacs-21.4-17

How reproducible:

  Always.

Steps to Reproduce:
1. Start Emacs (can add -q and --no-site-init to be even more sure).
2. Evaluate `sendmail-program' in Emacs
  
Actual results:

  "fakemail"

Expected results:

  "/usr/sbin/sendmail"

Additional info:

  The problem comes from /usr/share/emacs/21.4/lisp/paths.el which defines
  `sendmail-program' as a constant (see line 164) based on the existence of
  a sendmail executable.  My guess is that the build happens in a clean
  environment that does not have a sendmail executable, so this constant gets
  the default "fakemail" value.  Later on, when the Emacs image is dumped, the
  constant is inlined into it (you cen verify that the packaged
  /usr/bin/emacs-x file contains "fakemail" -- so it becomes a permanent part
  of the distributed Emacs.

  (Somehow, this did manage to send emails on my system (where the only
  "fakemail" executable is from Xemacs), but the problem is that fakemail
  inserts an extra newline in the headers, making it ignore the real headers.)

Comment 1 Eli Barzilay 2006-11-25 23:49:39 UTC
*** Bug 217253 has been marked as a duplicate of this bug. ***

Comment 2 Chip Coldwell 2006-11-29 15:38:09 UTC

*** This bug has been marked as a duplicate of 213813 ***