9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spam originating from a Plan 9 installation
Date: Sun, 16 Nov 2003 11:52:45 -0700	[thread overview]
Message-ID: <24083a5d85e5fe796a949845afcdb396@plan9.ucalgary.ca> (raw)
In-Reply-To: <c4583d00e2858ba110d42c84b091ec8b@plan9.ucalgary.ca>

it's fixed now with a much more restrictive networks definition in
smtpd.conf.  in fact, i'm tempted to completely remove any machines
from my relay list, but i'm not sure this won't break anything, so
i've left only the machine running smtpd.

out of the whole thing, my logs are left with a pretty detailed list
of emails and businesses sending spam to them:

plan9% grep 'Bad Forward' smtpd | wc -l
    182
plan9%

and this is for the past 10 minutes since i turned smtpd back on!

here's how it looks like, so others will know what to look for in the
logs:

plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!marialices)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!smileyohio)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!rpiiibc)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!libertyagogo)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!janedugan)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!archiedorsman)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!edpm123)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!kitarou33)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!luckyduck132)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!frost3882)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!jmfdigiovanni)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!zaman90614)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!pfcnut)
plan9 Nov 16 11:46:44 Bad Forward upbitchart.us!lilypye (mail.enddownstatus.us/136.159.139.8) (aol.com!ambuler74)



cheers, and thanx for the help: andrey

ps: smtpd.conf has this:

	saveblockedmsg		on	#save blocked messages

where are those messages stored (i admit not looking for them very
thoroughly)?



  parent reply	other threads:[~2003-11-16 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 16:47 mirtchov
2003-11-16 17:02 ` David Presotto
2003-11-16 17:28   ` andrey mirtchovski
2003-11-16 18:52 ` mirtchov [this message]
2003-11-16 21:31   ` David Presotto
2003-11-16 21:52 David Presotto

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=24083a5d85e5fe796a949845afcdb396@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --cc=9fans@cse.psu.edu \
    /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).