Bug 15947 - procmail delivery to an address (with '!') doesn't work in procmail 3.14!
procmail delivery to an address (with '!') doesn't work in procmail 3.14!
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: procmail (Show other bugs)
6.2
All Linux
high Severity high
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-10 16:10 EDT by Jonathan Kamens
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-10 16:11:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to put a space before addresses in address delivery (348 bytes, patch)
2000-08-10 16:11 EDT, Jonathan Kamens
no flags Details | Diff

  None (edit)
Description Jonathan Kamens 2000-08-10 16:10:37 EDT
With procmail 3.14, to which Red Hat updated in 6.2, any delivery rule
which says to deliver to an E-mail address using the '!' action line will
fail to deliver the mail properly.

The problem is that the code sets the delivery command to

	$SENDMAIL $SENDMAILFLAGSaddress

where "address" is the address to which to deliver.  Since it doesn't put a
space between the $SENDMAILFLAGS variable reference and the address, the
whole thing, including the address, is interpreted as the variable name,
and of course that variable doesn't exist, so the expansion fails and
procmail delivers the message to "/usr/sbin/sendmail".  Since sendmail
isn't given any recipients, it simply drops the message on the floor.

The fix is trivial.  I will attach a patch.
Comment 1 Jonathan Kamens 2000-08-10 16:11:30 EDT
Created attachment 2375 [details]
patch to put a space before addresses in address delivery
Comment 2 Jeff Johnson 2000-08-11 11:39:10 EDT
Fixed in procmail-3.14-5. Thanks for reporting.

Note You need to log in before you can comment on or make changes to this bug.