diff options
| author | klm | 1998-08-13 15:25:26 +0000 |
|---|---|---|
| committer | klm | 1998-08-13 15:25:26 +0000 |
| commit | d0171b7513aedcf48f3a6366a14c2f12a9d61c1f (patch) | |
| tree | 330d74a25e6151f3356c8969eda26db0bc8cfa7c /Mailman/pythonlib/smtplib.py | |
| parent | 9a3c974600be0382513311f022e6764823219e5f (diff) | |
| download | mailman-d0171b7513aedcf48f3a6366a14c2f12a9d61c1f.tar.gz mailman-d0171b7513aedcf48f3a6366a14c2f12a9d61c1f.tar.zst mailman-d0171b7513aedcf48f3a6366a14c2f12a9d61c1f.zip | |
Changing policy about when notifications are sent for posts held for
approval - notifications are now sent even for suspected spam. I was
experimenting with avoiding alerting spammers to spam filtering, but
i've come to realize that:
- Not notifying prevents non-spammers from getting any feedback when
they inadvertantly trip a spam sensitivity, and
- It's probably best to blast stuff back at spammers. In the common
case that the return addresses are useless, no harm, and if the
return addrs are good, then the more people using the spam
protection, the more spam the spammer gets in response.
The moral is, forthrightness is the best policy. Even if it does
expose our measures and up the ante in the spam war, security via
obscurity is a poor, and often misguided, approach.
Diffstat (limited to 'Mailman/pythonlib/smtplib.py')
0 files changed, 0 insertions, 0 deletions
