Hi,
the two bugs #990026 and #742880 do address similar issues, but my bug focusses on a different issue: the return-path.
With #990026 it is now possible to use MAILFROM to use arbitrary sender addresses in crontabs, if the crontab user is allowed to do so (by default this is only root). The return-path however is still left untouched.
With #742880 it is possible to use MAILFROM to use arbitrary sender addresses in crontabs for the return-path, if the crontab user is allowed to do so (by default this is only root). In contrary to #990026 it also allows everyone (not only root) to use "<>" as return-path. Additionally it adds an optional switch "-r" to cron to use "<>" as default return-path for all emails (if not specified otherwise by using MAILFROM).
Using the empty address "<>" as return-path prevents email systems from creating and queueing useless automatic out-of-office replies to cron emails.
Thanks for understanding,
Christopher
--
======================================================
Dipl.-Ing. Christopher Odenbach
Zentrum fuer Informations- und Medientechnologien
Universitaet Paderborn
Raum N5.308
odenb...@uni-paderborn.de
Tel.: +49 5251 60 5315
======================================================
smime.p7s
Description: S/MIME Cryptographic Signature
