From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] fake bounce spam
Date: Mon, 7 Apr 2008 20:11:14 -0400 [thread overview]
Message-ID: <e89fac41fd90c941388e35f7c3d38f87@quanstro.net> (raw)
starting saturday, i've been getting an increasing amount of
fake bounce spam predending to be a undelivered mail
notice from MAILER-DAEMON or similar. overnight i
received >500 such emails. as an emergency measure, i applied
this terrible hack to smtpd:
; 9diff smtpd.c
/n/sources/plan9//sys/src/cmd/upas/smtp/smtpd.c:1175,1180 - smtpd.c:1175,1184
"recipients");
return -1;
}
+ if(1){
+ werrstr("rejected: /dev/null likely spam ");
+ return -1;
+ }
return 0;
}
unfortunately, if i really do send mail that bounces, i won't know
about it.
i suppose it would be much better to accept bounces only from addresses to which
email has been sent. though that may mean maintaining a list (per user?).
- erik
next reply other threads:[~2008-04-08 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 0:11 erik quanstrom [this message]
2008-04-08 0:35 ` Russ Cox
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=e89fac41fd90c941388e35f7c3d38f87@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).