Bug 165643

Summary:	improper incoming mail reporting
Product:	Red Hat Enterprise Linux 4	Reporter:	Need Real Name <balemi>
Component:	tcsh	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED NEXTRELEASE	QA Contact:	Bill Huang <bhuang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	billy
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:	2005-08-17 21:45:26 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 Need Real Name 2005-08-11 02:20:23 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511

Description of problem:
There is a problem in the way tcsh reports new received emails. Previously (tcsh-6.12-11.EL3), the shell would show 

You have new mail.

when new mail would arrive for the user. The latest version (tcsh-6.13-9) shows the following:

You have You have %smail.
mail.

I have recompiled the latest tcsh (6.14) and it works fine in reporting new emails to the user. bash works ok also.

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

How reproducible:
Always

Steps to Reproduce:
1. send email to user
2. wait a few minutes and press return



Actual Results:  tcsh printed:

You have You have %smail.
mail.


Expected Results:  tcsh should have printed:

You have new mail.

Additional info:

Comment 1 Miloslav Trmač 2005-08-17 21:45:26 UTC

Thanks for your report.

As you already know, this is fixed in tcsh 6.14 and therefore it will be fixed
in RHEL 5.  This is purely a cosmetic issue, so I don't think this warrants an
RHEL 4 erratum.

Comment 2 Suzanne Hillman 2005-08-24 19:13:27 UTC

*** Bug 166659 has been marked as a duplicate of this bug. ***

Comment 3 Miloslav Trmač 2005-08-29 16:44:07 UTC

*** Bug 166659 has been marked as a duplicate of this bug. ***