Bug 13201 – Generates bogus "From" email addresses

Bug 13201 - Generates bogus "From" email addresses

Summary:	Generates bogus "From" email addresses

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-06-28 19:16 EDT by gward
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-06-28 19:16:36 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2000:138	high	SHIPPED_LIVE	New, enhanced Update Agent for Red Hat Linux 6.x, 7.0 available	2000-12-21 00:00:00 EST

Groups: None (edit)

Description gward 2000-06-28 19:16:35 EDT

The email generated by up2date has bogus "From" addresses -- either
"up2date@localhost" or "root@localhost" (client.py, lines 88 and 105).
Paranoid MTAs will reject this, even as a local message: after all,
"root@localhost" is not a valid email address.  Probably a slightly more
general solution would be to put the FQDN ("hostname -f") as the
domain of the address -- eg. replace 'localhost' with "os.uname()[1]" -- of
course, that assumes that the machine is configured so uname() returns the
FQDN, but even so it's better than hard-coding "localhost" (IMHO).

Comment 1 Preston Brown 2000-12-21 14:27:04 EST

fixed in errata being released shortly.

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