Gnus development mailing list
 help / color / mirror / Atom feed
From: Sharon Kimble <boudiccas@skimble.plus.com>
To: ding@gnus.org
Subject: Incoming4414ruc
Date: Tue, 17 Jun 2014 19:10:44 +0100	[thread overview]
Message-ID: <8761jzxv8b.fsf@skimble.plus.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

Ever since I've started using GNUs for my email, I've been
accumulating text files in my "/home/boudiccas/Mail" directory. They
have odd names like "Incoming4414ruc" or "Incoming4414rsy", or such
like.

They seem to be generated every time I manually get my email from
"/var/mail/boudiccas", and consist of emails from root, such as this
one -
--8<---------------cut here---------------start------------->8---
From boudiccas@london Tue Jun 17 15:00:18 2014
Return-path: <boudiccas@london>
Envelope-to: boudiccas@localhost
Delivery-date: Tue, 17 Jun 2014 15:00:18 +0100
Received: from boudiccas by london with local (Exim 4.82_1-5b7a7c0-XX)
	(envelope-from <boudiccas@london>)
	id 1Wwtvu-00079W-7W
	for boudiccas@localhost; Tue, 17 Jun 2014 15:00:18 +0100
From: root@london (Cron Daemon)
To: boudiccas@localhost
Subject: Cron <boudiccas@london> /home/boudiccas/bin/radiostreams
Content-Type: text/plain; charset=UTF-8
X-Cron-Env: <MAILTO=boudiccas@localhost>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/boudiccas>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=boudiccas>
Message-Id: <E1Wwtvu-00079W-7W@london>
Date: Tue, 17 Jun 2014 15:00:18 +0100

--8<---------------cut here---------------end--------------->8---

The "boudiccas@london" account does not exist, its just my user-name
and the machine-name.

How can I
- A - get rid of them,
- B - Stop them from being accumulated, and/or generated?

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.91.1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

             reply	other threads:[~2014-06-17 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 18:10 Sharon Kimble [this message]
2014-06-17 18:19 ` Incoming4414ruc Adam Sjøgren
2014-06-18  6:13   ` Fancy citing (was: Incoming4414ruc) Elias Oltmanns
2014-06-18  7:04     ` Fancy citing Thorsten Jolitz
2014-06-18 11:22     ` Sharon Kimble
2014-06-18 11:56     ` Sauli Heinola
2014-06-18 13:06     ` James Cloos
2014-06-18  7:50 ` Incoming4414ruc Steinar Bang
2014-06-18 11:19   ` Incoming4414ruc Sharon Kimble
2014-06-18 13:14     ` Incoming4414ruc Steinar Bang
2014-06-18 19:42       ` Incoming4414ruc Sharon Kimble
2014-06-19 12:49         ` Incoming4414ruc Steinar Bang
2014-06-19 21:59     ` Incoming4414ruc Steinar Bang
2014-06-20  4:13       ` Incoming4414ruc Sharon Kimble
2014-06-20  5:10         ` Incoming4414ruc Steinar Bang
2014-06-20  5:16           ` Incoming4414ruc Steinar Bang

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=8761jzxv8b.fsf@skimble.plus.com \
    --to=boudiccas@skimble.plus.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).