Bug 1052161 - if not mta, cronie won't use mailx for delivery to (gmail)
Summary: if not mta, cronie won't use mailx for delivery to (gmail)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cronie
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-13 12:28 UTC by Frank Murphy
Modified: 2015-06-29 14:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:24:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Murphy 2014-01-13 12:28:46 UTC
Description of problem: No mta installed, can't forward using mailx
edit /etc/sysconfig/crond
CRONDARGS="m '/usr/bin/mailx -t' "

Version-Release number of selected component (if applicable):
cronie-1.4.11-4.fc20.x86_64


How reproducible: always


Steps to Reproduce:
1. have no mta installed
2. setup mailx to forward to  eg. gmail
3.

Actual results:
systemctl status crond.service -l
crond.service - Command Scheduler
   Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled)
   Active: active (running) since Mon 2014-01-13 12:14:54 GMT; 9min ago
 Main PID: 7090 (crond)
   CGroup: /system.slice/crond.service
           └─7090 /usr/sbin/crond -n m /usr/bin/mailx -t 

Jan 13 12:14:54 mybox systemd[1]: Starting Command Scheduler...
Jan 13 12:14:54 mybox systemd[1]: Started Command Scheduler.
Jan 13 12:14:54 mybox crond[7090]: (CRON) INFO (Syslog will be used instead of sendmail.)
Jan 13 12:14:54 mybox crond[7090]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 45% if used.)
Jan 13 12:14:54 mybox crond[7090]: (CRON) INFO (running with inotify support)
Jan 13 12:14:54 mybox crond[7090]: (CRON) INFO (@reboot jobs will be run at computer's startup.)


Expected results: use mailx to forward
without requiring yum install mta

Additional info: if
"ln -s /usr/bin/mailx /usr/sbin/sendmail"
mail gets through # but not ideal workaround

Comment 1 Marcela Mašláňová 2014-01-13 12:32:48 UTC
It was decided mail will be dropped from default installation, because many people these days prefer logging. There is already printed in messages "Syslog will be used instead of sendmail."
What do you like to see as fix? Should I change it to - no emails?

Comment 2 Frank Murphy 2014-01-13 12:39:59 UTC
.
it is not local mail I'm talking, it's getting email to gmail.

Can you get it to accept /etc/sysconfig/crond#crondargs?
(In reply to Marcela Mašláňová from comment #1)
> It was decided mail will be dropped from default installation,

MTA was dropped, mail (mailx) was not

 because many
> people these days prefer logging. 

doesn't work so well sending logs via gmail.

There is already printed in messages
> "Syslog will be used instead of sendmail."

Yes but CRONDARGS="m '/usr/bin/mailx -t'  is valid syntax

> What do you like to see as fix? Should I change it to - no emails?

Remove check for sendmail, if possible.
So users who see the advice on @devel\test\users to forward mail to gmail etc. can do so.

Comment 3 Fedora Admin XMLRPC Client 2014-09-04 12:15:12 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2015-05-29 10:28:32 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-06-29 14:24:41 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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