Bug 203746

Summary: crond should use Auto-Submitted header in outbound mail
Product: [Fedora] Fedora Reporter: James Ralston <ralston>
Component: vixie-cronAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-25 09:19:03 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:
Attachments:
Description Flags
make crond generated the Auto-Submitted header on mail messages none

Description James Ralston 2006-08-23 15:28:44 UTC
Created attachment 134726 [details]
make crond generated the Auto-Submitted header on mail messages

Comment 1 James Ralston 2006-08-23 15:28:44 UTC
RFC3834 (Recommendations for Automatic Responses to Electronic Mail)
makes recommendations for software that automatically responds to
incoming electronic mail messages.  Specifically, RFC3834 defines an
"Auto-Submitted" header that compliant software can use to indicate that a
message has been automatically generated.

Section 5.2 states:

> The auto-generated keyword:
> 
> - SHOULD be used on messages generated by automatic (often periodic)
>   processes (such as UNIX "cron jobs") which are not direct
>   responses to other messages,

Meaning, crond should generate an "Auto-Submitted: auto-generated" header on
each mail message it generates.  Currently, vixie-cron does not do this.

The attached patch makes vixie-cron conform to RFC3834 by generating the
recommended Auto-Submitted header.  It applies cleanly to 4:4.1-58.

Comment 2 James Ralston 2006-08-23 15:34:20 UTC
Also note that I've filed this bug against FC6test2, but it affects all versions
of Fedora Core and Red Hat Enterprise Linux, and should be corrected everywhere
(FC5, FC6, RHEL2.1, RHEL3, RHEL4).


Comment 3 Marcela Mašláňová 2006-08-25 09:19:03 UTC
I fix it in FC-5 update, FC-6. For RHEL it'll be fixed in future release 
because it's incompatible change.

Comment 4 James Ralston 2006-08-26 03:23:57 UTC
For FC: thanks.

For RHEL: when you say "future releases", do you mean future update releases
(e.g., RHEL3 U9, RHEL4 U5), or do you mean that something about this change
means that it will have to wait for RHEL5?

If the latter, then just out of curiosity: why?