From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LKJeZ-0008P8-0Q for garchives@archives.gentoo.org; Tue, 06 Jan 2009 21:39:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE524E0088; Tue, 6 Jan 2009 21:39:56 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 84CE4E0088 for ; Tue, 6 Jan 2009 21:39:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id F1EC56615D for ; Tue, 6 Jan 2009 21:39:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.529 X-Spam-Level: X-Spam-Status: No, score=-3.529 required=5.5 tests=[AWL=0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTbYN2xmhGdK for ; Tue, 6 Jan 2009 21:39:49 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 11E3B65A42 for ; Tue, 6 Jan 2009 21:39:48 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LKJeK-0002OB-WC for gentoo-user@gentoo.org; Tue, 06 Jan 2009 21:39:45 +0000 Received: from c-98-215-178-6.hsd1.in.comcast.net ([98.215.178.6]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Jan 2009 21:39:44 +0000 Received: from reader by c-98-215-178-6.hsd1.in.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Jan 2009 21:39:44 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Harry Putnam Subject: [gentoo-user] Re: weird cron mail problem Date: Tue, 06 Jan 2009 15:39:34 -0600 Organization: Still searching... Message-ID: <87sknwktbd.fsf@newsguy.com> References: <20090105164240.GA4573@ca.inter.net> <20090105170635.GA27047@math.princeton.edu> <20090105180445.GB4573@ca.inter.net> <20090105181825.GB8629@princeton.edu> <20090105222841.GA4578@ca.inter.net> <20090106165655.GA19012@princeton.edu> <20090106182228.GE4567@ca.inter.net> <20090106193116.GA8188@math.princeton.edu> <20090106203641.GA4575@ca.inter.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-215-178-6.hsd1.in.comcast.net User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:HDBXUia22+F7czqOWkYXOYS0xYQ= Sender: news X-Archives-Salt: 06431da4-9a19-46a5-9797-9489009b1672 X-Archives-Hash: c01c06bc1f82a19a2f266873f6f17dde Philip Webb writes: > 090106 Willie Wong wrote: >> you may want to change the root line to "root=purslow", >> so the mail gets sent to purslow instead of postmaster >> (which according to /etc/mail/aliases becomes root again). > > That doesn't work, but adding '> /dev/null' or '-s' in crontab does. > The latter seems simpler, so that's what I've done. > > It doesn't explain why the problem suddenly arose last Sunday > after I made a simple editing change in .fetchmailrc > & nothing like this had happened before > with the same crontab & ssmtp.conf : perhaps there's an obscure bug, > but the irritating problem has been resolved & I have other jobs today. > > Thanks for the helpful advice (smile). Looking back thru the thread I don't see the actual change made to fetchmailrc. Maybe just blind. >From my experience fetchmail is a very robust (non buggy) and easily configured tool. At least for my simple usage. It's the only config I can think of that is edited much like you might talk to friend while walking along. Something that happens from time to time is introducing an unprintable CHAR into a *.rc file and not being able to see it. I'm not sure if fetchmail would respond poorly to that. If there is any chance of that; you might want to use vim to check each line. You can hit the el (l) lowercase, on each line to expose most kinds of unprintable char. It takes 3 key strokes to show the line. 1) : 2) l 3) enter Then the line appears in the command area along with any unprintable chars, As Willie mentioned the mail mta is capable of rewriting stuff in its configurations. Do you control this machine? Sorry if you've already covered that. Another unlikely thing that can catch you ... happened to me on a remote account I didn't control. The machine underwent some kind of mishap that required serious backup effort replacing all us users files from backups. Turned out the backups were pretty old and further I missed the notification about the mishap... the next thing I knew lots of strange things began to happen. Some of my older configurations were re-introduced in place of things I had changed due to new circumstances.