From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] mail rejection handling and spammers
Date: Mon, 23 Sep 2002 15:29:55 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0209231517310.20731-100000@athena> (raw)
In-Reply-To: <20020923200440.GB26329@thefrayedknot.armory.com>
> back again and loops around 20 or so times before it finally gives up
> and returns it to the sender.
>
Something similar to this caused our cpu server to crash every so often,
befuddling us for a long time until we came in early enough to catch it
going down. Turns out we were getting hammered by spammers who like to
send mail to a zillion usernames until one clicks. The smtp processes
returning the mail accumulated until swap was gone and the cpu server fell
over.
We haven't upgraded to 4 yet, so I just hacked our code to drop those
messages (and likely more, based on my least-effort solution).
Anyone else experience this?
Cheers,
Sam
prev parent reply other threads:[~2002-09-23 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 19:13 [9fans] mail and the web John Saylor
2002-09-23 20:04 ` Andrew
2002-09-23 19:29 ` Sam [this message]
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=Pine.LNX.4.30.0209231517310.20731-100000@athena \
--to=sah@softcardsystems.com \
--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).