Displaying 20 results from an estimated 800 matches similar to: "iptables"
2017 Jul 19
3
Cron sending to root after changing MAILTO
I have ?root: ecssupport at csusb.edu? in my /etc/aliases file already.
---
Chad Cordero
Information Technology Consultant
Enterprise & Cloud Services
Information Technology Services
California State University, San Bernardino
5500 University Pkwy
San Bernardino, CA 92407-2393
Main Line: 909/537-7677
Direct Line: 909/537-7281
Fax: 909/537-7141
http://support.csusb.edu/
---
2017 Jul 20
0
Cron sending to root after changing MAILTO
Well, I feel silly.? There are three places MAILTO can affect crond: /etc/crontab, /etc/crond.d/0hourly, and /etc/anacrontab.? Once I set this in these 3 files, I started getting mail from crond.? Thank you all for your help.
---
Chad Cordero
Information Technology Consultant
Enterprise & Cloud Services
Information Technology Services
California State University, San Bernardino
5500
2017 Jul 19
5
Cron sending to root after changing MAILTO
It?s being rejected before it even reaches the mailbox, so forwarding won?t work.? Crond should really be using the MAILTO variable and it?s not.
---
Chad Cordero
Information Technology Consultant
Enterprise & Cloud Services
Information Technology Services
California State University, San Bernardino
5500 University Pkwy
San Bernardino, CA 92407-2393
Main Line: 909/537-7677
Direct
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
2017 Jul 19
1
Cron sending to root after changing MAILTO
Ah.? Here you go.
# grep A5077100E776C /var/log/maillog
Jul 19 13:15:55 mailcampaign1 postfix/pickup[19675]: A5077100E776C: uid=0 from=<root>
Jul 19 13:15:55 mailcampaign1 postfix/cleanup[19797]: A5077100E776C: warning: header Subject: Cron <root at mailcampaign1> run-parts /etc/cron.hourly from local; from=<root at csusb.edu>
Jul 19 13:15:55 mailcampaign1
2017 Jul 19
0
Cron sending to root after changing MAILTO
Am 19.07.2017 um 22:46 schrieb Chad Cordero:
> I am running CentOS 7 on an outbound gateway server running Postfix. I have a couple of cron jobs I was expecting to see in my email that never showed up. It turns out that they were delivered to root, which is restricted on our exchange server, instead of the address I defined. Please help.
[ ... ]
Best is to define a mail alias for the root
2017 Jul 19
5
Cron sending to root after changing MAILTO
I am running CentOS 7 on an outbound gateway server running Postfix.? I have a couple of cron jobs I was expecting to see in my email that never showed up.? It turns out that they were delivered to root, which is restricted on our exchange server, instead of the address I defined.? Please help.
# cat /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=ecssupport at
2017 Jul 13
1
Postfix fails after reboot
I am running CentOS 7 as an outbound gateway using Postfix, OpenDKIM, and SASLAuthd.? The trouble is Postfix fails if OpenDKIM and SASLAuthd aren?t already running and I have to manually restart these services in order.? My question is, should I modify my After line in the ?[Unit]? section of my postfix.service file to read ?After=syslog.target network.target opendkim.service saslauthd.service? or
2017 Jul 20
4
Cron sending to root after changing MAILTO
> Date: Thursday, July 20, 2017 02:25:52 +0000
> From: Richard <lists-centos at listmail.innovate.net>
>
>> Date: Wednesday, July 19, 2017 23:31:10 +0000
>> From: Chad Cordero <ccordero at csusb.edu>
>>
>> It?s being rejected before it even reaches the mailbox, so
>> forwarding won?t work.? Crond should really be using the MAILTO
>>
2017 Jul 20
0
Cron sending to root after changing MAILTO
> Date: Wednesday, July 19, 2017 23:31:10 +0000
> From: Chad Cordero <ccordero at csusb.edu>
>
> It?s being rejected before it even reaches the mailbox, so
> forwarding won?t work.? Crond should really be using the MAILTO
> variable and it?s not.
>
In my testing, this worked as advertised. Changing the "MAILTO=" in
/etc/crontab from the default
2017 Jul 20
0
Cron sending to root after changing MAILTO
On Thu, July 20, 2017 8:54 am, Richard wrote:
>
>> Date: Thursday, July 20, 2017 02:25:52 +0000
>> From: Richard <lists-centos at listmail.innovate.net>
>>
>>> Date: Wednesday, July 19, 2017 23:31:10 +0000
>>> From: Chad Cordero <ccordero at csusb.edu>
>>>
>>> It???s being rejected before it even reaches the mailbox, so
2017 Jul 19
0
Cron sending to root after changing MAILTO
Am 19.07.2017 um 23:42 schrieb Chad Cordero:
> I have ?root:ecssupport at csusb.edu? in my /etc/aliases file already.
> Chad Cordero
Then please provide log information about the mails to root being
relayed to your Exchange host.
Alexander
2017 Jul 19
0
Cron sending to root after changing MAILTO
Am 20.07.2017 um 00:03 schrieb Chad Cordero:
> Here is the last one I got. As you can see it was send toroot at csusb.edu, a restricted distribution group, not obeying /etc/aliases or MAILTO definition in crontab.
Speaking about log content I meant to show the trace of the relayed mail
in the server's /var/log/maillog log file.
In addition it would be helpful to show `postconf -n'
2005 Dec 28
3
disk mounting madness
I've got a server running CentOS 4.2; installed as 4.1, kept updated by
yum.
A few days ago it crashed.
I picked it up from the datacenter, and brought it back to the office,
where it took a long time to boot because it couldn't find anything.
When it finally booted and I logged in I discovered an interesting
problem.
Only the / partition had loaded. /etc/fstab had all the
2017 Jul 20
1
Cron sending to root after changing MAILTO
> Best is to define a mail alias for the root user. That way you have it
> defined at a single place for all occurances of mail destined to root.
postfix only uses the aliases map for local delivery. If the recipient email address is fully qualified, local delivery is not even in the picture (and I literally mean "the big picture",
2006 Mar 09
0
swat error
hola,
habla usted ingles?
bueno, revise bien que 'xinetd' este instalado y corriedo como servicio:
ps -ae | grep xinetd
si resulta que si, entonces revise el documento de configuracion de swat (/etc/xinetd.d/swat):
# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901
2007 Feb 15
0
Asterisk guru wanted, SoCal (LA/OC/San Bernardino County)
We've mostly gotten our Asterisk install working, but there are a couple
glitches I haven't been able to fix.
I'm looking for someone who knows Asterisk, can do some consulting work,
and is in Southern California. Los Angeles or Orange County are ok, but
I'd prefer someone in the Inland Empire, with strongest preference given
to people here in the High Desert or in the San
2008 Apr 22
1
Convert ssha password to sambaNTpassword?
Is it possible to take a SSHA password from an ldif and create a proper
sambaNTpassword from it? Here's the scenario: the ldap servers in our
organization do not have the samba schema installed and the likelihood
of that happening is slim. I still want to provide clients with as
close to a single sign on solution as possible and I can get an ldif of
the accounts I need. However, the
2005 Jul 07
2
ftp daemon problem
New install of CentOS 4.1; our first try at the 4.x.
On previous 3.x installs we've used proftpd.
On this one we're using (trying to use is a better statement of what
we're going through) the default daemon, /usr/sbin/vsftpd.
But we don't get anywhere.
<snip>
ftp> passiv
Passive mode off.
ftp> put ~/xorg.conf.work
local: /home/jlasman/xorg.conf.work remote:
2006 Jan 18
5
install won't boot
Circumstances:
The system is a hardware duplicate of a system that installed and works
for many months. Running CentOS 4.x.
The system was previously in service with CentOS 3.x and I'm trying to
install CentOS 4.1 on it from downloaded CDs which have worked
previously (these are the same CDs used to install the system that's
working).
Software RAID.
Minimal packages
System