Return units MTA option

Notification message MTA options:  (0 or 1)
The time unit used by the message return system is controlled with the   MTA option; that is, this option controls the  interpretation  of the values specified for the    channel option. A value of 0 selects units of days; a value of 1 selects units of hours. By default, units of days are used.

On UNIX systems, the scheduling of the execution of the message  is controlled by the Scheduler. In particular, with a Unified Configuration it is the   option that controls how frequently the   runs: this defaults to: 30 0 &#x2a; &#x2a; &#x2a; lib/return_job The argument is in UNIX crontab format, minutes hour day-of-month month-of-year day-of-week script so the default is to run the  every day at 30 minutes  after midnight.

In legacy configuration mode (so in versions prior to 7.0.5), the scheduling of the  was controlled via the configutil parameter , which had a default of   30 0 &#x2a; &#x2a; &#x2a; SERVERROOT/lib/return_job with the same sort of UNIX crontab format argument.

Note: Prior to MS 6.0, the scheduling of the execution of the message return job was controlled by the Job Controller  configuration, an  approach that is now deprecated. With that approach, the scheduling was controlled by the Job Controller&#x27;s   option in the   section of  the   file. For instance, to have the return job run hourly at thirty minutes past the hour, it would be set &#x5b;periodic_job=return&#x5d; command=IMTA_EXE:return.sh time=00:30/1:00 Note that if you choose to set the  MTA option to a value of , then you will likely also need (or want) to adjust other options such as those controlling  MTA transaction log file  rollover.

See also:
 * Notification message MTA options
 * notices Option
 * The optional return_option.opt file
 * Managing the MTA transaction log files
 * return_job options