AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080207091210.2afeda1a@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.keiffer@onstor.com>,<rendell.fong@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E08265809@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 7 Feb 2008 09:12:37 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "John Keiffer" <john.keiffer@onstor.com>
Cc: "Rendell Fong" <rendell.fong@onstor.com>
Subject: Re: 21717
Message-ID: <20080207091237.4c9393c7@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08265809@onstor-exch02.onstor.net>
References: <20080206180047.494f28d3@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E03B1C040@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E08265809@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 7 Feb 2008 07:54:47 -0800 "John Keiffer"
<john.keiffer@onstor.com> wrote:

> 
> This stuff is mostly over my head (as you both probably already know).

I don't know, it sounds like you got it pretty much exactly.

> These are the lines in my Bobcat Cougar system's crontab:
> 
> MAILTO=""
> SHELL=/bin/sh
> PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/agile/bin:/onstor/bin
> HOME=/var/log
> 
> Those lines are not in the Cougar systems. Are you suggesting we add
> the MAILTO line?

Add the MAILTO and HOME lines.  The others aren't necessary on Linux.
 
> Thanks,
> John
> 
> -----Original Message-----
> From: Rendell Fong 
> Sent: Wednesday, February 06, 2008 6:13 PM
> To: Andy Sharp; John Keiffer
> Subject: RE: 21717
> 
> I've seen situations where emrscron (launched via crontab) indirectly
> causes emails to be generated when an error occurs while running an
> nfxsh or sh cmd.  Will setting MAILTO in the crontab suppress emails
> from getting generated this way?  I hope so because it will be a while
> before we can be sure that support.sh and emrscron are fixed for
> Cougar.
> 
> Rendell
> 
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, February 06, 2008 6:01 PM
> To: John Keiffer
> Cc: Rendell Fong
> Subject: Re: 21717
> 
> Hmm, there is a separate bug that is involved here, one that can also
> lead to "queue full" and /var filling up, albeit after a very long
> time.
> 
> For some reason, we aren't getting the line
> 
> MAILTO=""
> 
> at the top of the root crontab.  That can be added by hand until we
> get it straightened out, probably in the next submittal.  Feel free
> to file a new bug report on that.
> 
> Cheers,
> 
> a
> 
> 
> On Wed, 6 Feb 2008 12:26:18 -0800 "John Keiffer"
> <john.keiffer@onstor.com> wrote:
> 
> > I checked the frozen messages on 2 different systems and I found
> > that they have different errors. So the question is where this
> > configuration lives, so that I we can try and edit it.
> > 
> >  
> > 
> > g10r10:~# cat /var/spool/exim4/msglog/1JMqhe-0001BV-5h
> > 
> > 2008-02-06 12:17:06 Received from root@ U=root P=local S=785
> > 
> > 2008-02-06 12:17:09 routing failed for root@: mail domain "" is
> > syntactically invalid
> > 
> > Process failed (1) when writing error message to root@ (frozen)
> > 
> >  
> > 
> > g6r10:~# cat /var/spool/exim4/msglog/1JMqks-0003I1-U6
> > 
> > 2008-02-06 12:20:27 Received from <> R=1JMqiY-000340-EW
> > U=Debian-exim P=local S=4260
> > 
> > 2008-02-06 12:20:27 routing failed for root@g6r10: Unrouteable
> > address
> > 
> > *** Frozen (delivery error message)
> > 
> >  
> > 
> > Thank you,
> > 
> > John Keiffer
> > 
> >  
> > 
> >  
> > 
