Bug 1462286 - yum-cron date/time on email
yum-cron date/time on email
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum (Show other bugs)
All Linux
unspecified Severity low
: rc
: ---
Assigned To: Valentina Mukhamedzhanova
BaseOS QE Security Team
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2017-06-16 11:23 EDT by Lloyd Brown
Modified: 2018-06-20 22:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
adds the current date/time to the emails generated (720 bytes, patch)
2017-06-16 11:23 EDT, Lloyd Brown
no flags Details | Diff

  None (edit)
Description Lloyd Brown 2017-06-16 11:23:54 EDT
Created attachment 1288391 [details]
adds the current date/time to the emails generated

Description of problem:
The email emitter built into yum-cron, does not add a "Date" header.  While some MTAs (eg. Postfix or Exim) can be configured to add the header if it is missing, this is not always done.

With most clients (certainly with Mozilla Thunderbird, which I use), if the Date header is missing, the client will assume and show the date/time when it first saw the email.

Since the body of the email doesn't seem to include any date/time information, if the email client happens to be off or disconnected when the email is sent, it isn't clear when the yum-cron actually did anything.

Version-Release number of selected component (if applicable):
I see this using yum-cron-3.4.3-150.el7.noarch on RHEL 7.3, but I suspect it affects all versions.

How reproducible:

- Using a host with upgrades available (yum downgrade something if needed), make sure that the "emit_via" in /etc/yum/yum-cron.conf includes email, and that the "[email]" section is set up appropriately to send emails to a specific destination, etc.
- Have two separate email clients available to access the email account receiving from the yum-cron.  Leave one of the two email clients running and connected, and the other non-running/disconnected.
- Manually run "yum-cron" and let it update the packages
- Using the currently-up email client, see the email, view the headers, and notice the lack of a "Date" header
- Wait an appreciable amount of time (eg. 2-3 minutes), and launch/connect your second email client.  The message will probably be shown with the date/time when your second email client was launched/connected, which will be a few minutes different than the first email client shows.

If you repeat the process after applying my attached patch, the email notification should have a "Date" header, and both clients will show the same date, despite the delay in the second one seeing the message.

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 2 Lloyd Brown 2017-06-16 11:26:01 EDT
Just realized that I filled out the description poorly.  It's easily reproducible, and those steps should've been listed below in the "Steps to Reproduce".  Hopefully the rest should be clear.

I really should read the instructions better.

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