Bug 1106852

Summary: sendmail {client_port} not set correctly on little endian machines
Product: Red Hat Enterprise Linux 6 Reporter: Kelsey Cummings <kgc>
Component: sendmailAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: amahdal, psklenar, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sendmail-8.14.4-9.el6 Doc Type: Bug Fix
Doc Text:
Previously, the "{client_port}" value could not be used on little-endian machines, for example in mail filters, because it was set incorrectly. This update corrects the "{client_port}" value on little-endian machines.
Story Points: ---
Clone Of:
: 1210914 1210915 (view as bug list) Environment:
Last Closed: 2015-07-22 06:24:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1210914, 1210915    
Attachments:
Description Flags
sendmail patch
none
sendmail spec patch none

Description Kelsey Cummings 2014-06-09 17:49:15 UTC
Created attachment 905453 [details]
sendmail patch

Description of problem:

Sendmail does not call ntohs on sin.sin_port when setting {client_port} leading to a useless value being set for use by milters, etc. 

Additional info: 

Patch accepted upstream for future release.

Comment 1 Kelsey Cummings 2014-06-09 17:49:47 UTC
Created attachment 905455 [details]
sendmail spec patch

Comment 4 Jaroslav Škarvada 2015-02-03 16:56:14 UTC
Thanks for the patch.

Comment 6 Alois Mahdal 2015-04-04 03:29:11 UTC
Ran tests on all supported archs and results are as expected:

 *  On Big endian (s390x, ppc64), passing with both old and new,
 *  and on little endian (x86_64, i386), failing with old and passing with new.

Comment 8 errata-xmlrpc 2015-07-22 06:24:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1299.html