From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] yahoo calendar spam
Date: Sun, 15 Feb 2009 12:25:23 -0500 [thread overview]
Message-ID: <fc8212df041ea25eefd8a3f61e41e2a0@quanstro.net> (raw)
i'm getting 100-200 connections per hour from
yahoo calendar with nigerian spam stuff. here's
the least aggressive patch fix i could think of
without modifying smtpd to also get the reply-to
address. unfortunately, this means that all mail
from yahoo calendar is blocked. but it's better
than blocking all of yahoo.
this change is in /n/sources/contrib/quanstro/src/nupas.
the funky eval is to allow regular expressions in the list.
; diffy validatesender
20a21,25
> # these particular senders are blacklisted
> # motivated by the fact that yahoo calender
> # is compromised.
> dropuser=(reply.yahoo.com!calendar-invite)
>
57a63,65
>
> if(eval ~ $dom!$addr $dropuser)
> exit 'member of dropuser list'
- erik
next reply other threads:[~2009-02-15 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 17:25 erik quanstrom [this message]
2009-02-15 23:08 ` erik quanstrom
2009-02-15 23:22 ` Russ Cox
2009-02-15 23:45 ` erik quanstrom
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=fc8212df041ea25eefd8a3f61e41e2a0@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).