public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@ca.inter.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] weird cron mail problem
Date: Mon, 5 Jan 2009 11:42:40 -0500	[thread overview]
Message-ID: <20090105164240.GA4573@ca.inter.net> (raw)

Starting yesterday IIRC I've been getting one of the messages below
every time my Fetchmail cron job polls my  2  ISPs for new mail.
The content of the msg clearly comes from my own Fetchmail,
as it refers to both ISPs, but the msg itself originates at Uniserve,
as is shown by the list of routings in the full header (not shown).
Perhaps Uniserve has changed its procedures with this result,
but before I phone their tech folks, I'ld like to be sure
that it's not caused by something in my own machine.
I'm not aware of having changed anything to do with mail recently.

Does anyone have any suggestions based on experience ?
Is there any way to tell Procmail to dump the msgs in  /dev/null ?
I have read the various man pages several times & checked Gentoo Forum,
but there's no sign of anything relevant.

-- start of message --

X-Sieve: CMU Sieve 2.3
Envelope-to: purslow@ca.inter.net
Delivery-date: Mon, 05 Jan 2009 07:30:08 -0800
Date: Mon, 05 Jan 2009 10:30:03 -0500
From: Cron Daemon <root@ca-inter-net.uniserve.ca>
To: purslow@ca-inter-net.uniserve.ca
Subject: Cron <purslow@localhost> /usr/bin/fetchmail
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/purslow>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=purslow>
X-Cron-Env: <USER=purslow>
X-Scanner: OK. Scanned.
X-Uniserve-Spam-Score: 2.2 22 (++)
X-Uniserve-Spam-Report: Content analysis details:   (2.2 points)
        pts rule name              description
        ---- ---------------------- --------------------------------------------------
        0.9 TO_MALFORMED           To: has a malformed address
        1.3 ADDRESS_IN_SUBJECT     To: address appears in Subject
X-Scanner: OK. Scanned.
X-Uniserve-Spam-Score: 2.2 22 (++)
X-Uniserve-Spam-Report: Spam detection software, running on this mail system has
        identified this incoming email as possible spam.  An
        analysis of the message is below.
        Content analysis details:   (2.2 points)
        pts rule name              description
        ---- ---------------------- --------------------------------------------------
        0.9 TO_MALFORMED           To: has a malformed address
        1.3 ADDRESS_IN_SUBJECT     To: address appears in Subject

3 messages (3 seen) for purslow at pop.chass.utoronto.ca (22378 octets).
skipping message purslow@artemis.chass.utoronto.ca:1 not flushed
skipping message purslow@artemis.chass.utoronto.ca:2 not flushed
skipping message purslow@artemis.chass.utoronto.ca:3 not flushed
1 message for purslow at pop.ca.inter.net (2763 octets).
reading message purslow@ca-inter-net.uniserve.ca:1 of 1 (2763 octets).. flushed

-- end of message --

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca




             reply	other threads:[~2009-01-05 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 16:42 Philip Webb [this message]
2009-01-05 17:06 ` [gentoo-user] weird cron mail problem Willie Wong
2009-01-05 18:04   ` Philip Webb
2009-01-05 18:18     ` Willie Wong
2009-01-05 22:28       ` Philip Webb
2009-01-06  0:22         ` [gentoo-user] " Harry Putnam
2009-01-06 10:26           ` Philip Webb
2009-01-06 16:56         ` [gentoo-user] " Willie Wong
2009-01-06 17:05           ` Willie Wong
2009-01-06 18:22           ` Philip Webb
2009-01-06 19:31             ` Willie Wong
2009-01-06 20:36               ` Philip Webb
2009-01-06 21:39                 ` [gentoo-user] " Harry Putnam
2009-01-07 18:20                   ` [gentoo-user] Re: weird cron mail problem: basically solved Philip Webb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090105164240.GA4573@ca.inter.net \
    --to=purslow@ca.inter.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox