Bug 20822 - sendmail removes duplicate headers
Summary: sendmail removes duplicate headers
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sendmail   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: Dale Lovelace
Depends On:
TreeView+ depends on / blocked
Reported: 2000-11-14 08:00 UTC by Alexandre Oliva
Modified: 2007-04-18 16:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-04 16:53:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Alexandre Oliva 2000-11-14 08:00:57 UTC
It seems that sendmail needlessly (?) removes duplicate To: and Cc: headers
from messages it feeds to procmail.  I'd prefer that it left them
untouched, as people (myself included) have made it an habit to have more
than one Cc: line.  Also, some of my mail-splitting rules match
mailing-list names in these fieds and, when sendmail removes the lines that
happen to contain the mailing-list name, I get the message in the wrong folder.

I've noticed that the queue file still contains duplicate headers, and,
when sendmail forwards messages via SMTP, it won't discard duplicates.  By
replacing procmail with a shell-script that cat all of its stdin in a
temporary file and then execed the actual procmail so that it reads from
the temporary file, I've noticed that what sendmail feeds to procmail does
NOT contain the duplicates, so it is not procmail that is removing duplicates.

I couldn't find any mention of this new (mis)feature in the release notes
of sendmail, nor any configuration flags to revert to the original
behavior, so this may well not be something specific to Red Hat Linux 7's
default configuration, but I thought I'd report it here just in case.

I've just verified that the problem does not occur with a hand-built
sendmail 8.11.1, so either the problem was fixed in 8.11.1 or it is
specific to Red Hat Linux.  Please verify.

Comment 1 Florian La Roche 2001-01-04 16:53:29 UTC
I have checked the changes and this was indeed fixed in
8.11.1. I have just updated to 8.11.2 today. Thanks for
this bug-report.

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