Displaying 2 results from an estimated 2 matches for "polite_destination_recipient_limit".
2017 Jul 19
1
Cron sending to root after changing MAILTO
...u
myhostname = mailcampaign1.csusb.edu
mynetworks = 139.182.0.0/16, 198.188.128.0/22, 10.120.76.0/24, 127.0.0.0/8
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases.postfix
non_smtpd_milters = $smtpd_milters
polite_destination_concurrency_limit = 10
polite_destination_rate_delay = 0
polite_destination_recipient_limit = 5
postscreen_upstream_proxy_protocol = haproxy
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES
relay_domains =
sample_directory = /usr/share/doc/postfix-2.10.1/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smt...
2017 Jul 19
2
Cron sending to root after changing MAILTO
Here is the last one I got.? As you can see it was send to root at csusb.edu, a restricted distribution group, not obeying /etc/aliases or MAILTO definition in crontab.
Message Trace:
----------------------
Cron <root at mailcampaign1> run-parts /etc/cron.hourly
Sender:root at csusb.edu
Recipient:root at csusb.edu
ReceivedProcessedNot delivered
StatusThe message was sent to the