preventing backscatter at the source

[Hugo van der Kooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Neuman wrote:
| Come on... like you've never forgotten to put someone important or your
| whitelist... Or sent a message from a less-than-reputable-IP... :D
|
| It's not configured incorrectly, it's not configured correctly enough!  :D

If you use the sender info in ANY spam message after you did content
scanning and send a reply then you have a major problem in your config.

There is no valid reason what so ever to bugger a sender about spam.
With spam you got the following options if you do content scanning:

~ - discard it (with or without logging)
~ - quarantine it
~ - tag it
~ - just let it pass

Warning a sender when fake senders is as close to 100% as one can get is
simply sending out spam. If that is your config you might as well send
spam of your own and make a few bucks.

Hugo.

- --
hvdkooij at vanderkooij.org               http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on http://spamornot.org/ and rate those images.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFH7mMjBvzDRVjxmYERAtPWAJ9MZ/5dAgHnFTiZRGim8UyZwneO7wCeMtcY
qkO2VCXX2nvOz34YmiOloZk=
=es2/
-----END PGP SIGNATURE-----